We are using Tycho to allow us to use maven to build artifacts for our eclipse RCP GUI products - this allows a 'manifest-first' approach to dependency declaration. Some of these artifacts are also being used in the server runtime, which is (for the moment) a pure maven build. While we can get grapes to follow the dependencies in the pure maven build and generate the reports, it seems to be having problems following the tycho dependencies, which originate in the manifest rather than the pom. Is there any support currently in grapes to work with tycho? Has anyone else any experience working with tycho and grapes together?

When using semantic versioning, it's not possible to check if a module can be promoted because it has a SNAPSHOT version.
The check for promotion should only check if all internal (corporate) dependencies are promoted (and not if it is not released yet).

Currently there is no way to get the module of an Artifact via the REST API.
As a user of the REST API I want to be able to get the Module of an Artifact

As a client, I want to be able to get the module of an artifact using grapes-utils library.

When module are deleted from the database, it could brake dependency reports of ancestors. The aim of this task is to generate dependencies from module dependency information when the artifact is not stored in the database.

Let's take an example. If my project has the following module section, the report aggregation will failed:

        ...
        <modules>
                <module>plugins/bottle<module>
                ...
        </modules>

While a module is post, a check should be perform if an organization could match the module. If yes, the organization should be set in the module.

When we fill formular of a library, we need to many field each time. This operation is very fastidious when we have several libraries to treat. I would be very interesting to put in place auto completion system to suggest existing values when we fill fields. After settings can change between 2 major version of a library like the licence. In this case it could be intersting to suggest value of the previous version and the user will be able to change them if there are not correct for the new one.

At this moment only the pom's root dependencies element is being taken into consideration. Since some plugins require dependencies to be declared within their definition, these will be ignored by grapes unless these are duplicated.

Even if we duplicate them, there is still the problem that some assemblies rely on what is defined in the pom's root dependencies, so a lot of refactoring would be required just for the sake of duplicating the plugin dependencies into the root dependencies.

Feature

As a developer
I want to know how many times an artifact has been downloaded
In order to select the artifact which meet my needs and which is the most used by the developer community.

Acceptance Criteria

The user can list some artifacts and sort them by download score.

If a user has notification rights, he can send all the information he want to the server. The aim of this task is to be able to restrict the notification to some modules.

As a Grapes notifier, I should be able to send modules if the module ID match a regular expression. If the Regexp does not match the module I am sending, I should get a 401 error. Default behavior (no regexp define), I should have no restriction on notification.

Since the implementation of Organization concept on server side, there is no way on client side to get the corporate groupid prefixes of a module.

As a client using grapes-utils, I want to be able to get the organization of a module.

Currently there is no way to get the organization of an Artifact via the REST API.

As a user of the REST API I want to be able to get the Organization that provides an Artifact

Currently when we perform a GET /module/{name}/{version}/dependencies we get a list of artifact gavc. The aim of this task is to get the modules of these artifacts.

Ancestors lists are supposed to get the list of modules that depend on your module. But if you have internal dependencies, the ancestor list contains your module itself.

Work for version two is being done on a fork, that will be periodically merged. To follow the progress please see www.github.com/jfry-axway/Grapes

Currently, only dependency lists are sortable. The aim is to implement sortable HTML table also for module view.

Grapes let us know who depends on my module given a specific version.
But it would be usefull to know who depends on my module whatever its version is.
So I can check which versions of my module are used, and who are the users of my module in one request.

Grapes is based on Dropwizard:
http://dropwizard.github.io/dropwizard/

The aim of this task is to migrate on the very last release of this library. It will provide new features and enhancements to the HTTP server support.

When a notification if done to the server, license names can be very different even for on single license: ASL 2.0 == Apache License 2.0.

To avoid to duplicate the licenses on Grapes server side, it would be great to use a regexp to identify licenses. The resolution will be performed at the notification time.

To reproduce, flag an artifact as DoNotUse and try to display the Promotion Plan of a module that depends on it (in my case, transitively).

NB: promotion failed also

Maven client is called for each submodule of multi-module Maven project. The aim is to generate and send a JSON that contains all the modules/sub-modules. Currently, a notification with an incomplete JSON is sent at each sub-module.

Is it possible to know which modules my module depends on? instead of knowing the artifacts....
Examples
GET /module//dependencies returns
{
[ "name" : "depmodule1", ...],
[ "name" : "depmodule2", ...],
...
}
Could be cool to have also the module ancestors this way.
This way we can navigate from modules to modules with the same API.

Add Jersey caching for costly methods:

• get ancestors
• get dependencies
• get dependency report
• get all

Feature

As a developer
I want to know how much dependencies will I pull if I use this artifact
In order to select the artifact which meet my needs and which has the lower level of coupling.

Acceptance Criteria

The user can list some artifacts and sort them by coupling score.

Add a Map<String,String> field to modules that contains information about the module. The stored information should be free. Users should be able to put the information they want.

As a user, I want to be able to store/retrieve key/value information related to a module.

Currently, the objects stored in Mongo database use auto generated Ids. These technical Ids are used by Mongo to differentiates elements of the database. These Ids are automatically indexed by the database and it is very efficient to retrieve elements using these Ids.

The problem is that there is no way for Grapes to forecast the Id of an element. Until now, to retrieve an element, Grapes applies a certain amount of filters.

The aim of this task is to handle element Ids manually (as it is described here http://jongo.org) to be able to get database element by Ids which will enhance the performances, lighten the code and reduce the number of DB calls at runtime.

Currently the grapes maven plug-in only sends information about dependencies. A feature should be added to send license information of the built project and its dependencies.

A Jenkins plug-in should be implemented to notify Grapes directly from Jenkins.
A first step would be to create a plug-in for maven jobs. This way we could re-use Grapes Maven plug-in.