[
http://jira.codehaus.org/browse/MECLIPSE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106299
]
Andrea Aime commented on MECLIPSE-197:
--------------------------------------
Oh, an easier way would be to just be able to specify groups whose artifact
references should be generated as project names, assuming something or someone
already loaded those projects in the workspace. Something like:
<forceProjectReferences>
<groupId>org.geotools</groupId>
</forceProjectReferences>
or like:
<forceProjectReferences>
<forceGroup>
<groupId>org.geotools</groupId>
</forceGroup>
<forceArtifact>
<groupId>commons-beanutils</groupId>
<artifactId>commons-beanutils-core</artifactId>
</forceArtifact>
</forceProjectReferences>
> Automatic reference of dependee projects
> ----------------------------------------
>
> Key: MECLIPSE-197
> URL: http://jira.codehaus.org/browse/MECLIPSE-197
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: dependency resolution
> Reporter: Alessandro Evangelista
> Assignee: fabrizio giustina
> Attachments: referenceDependeeProjects-patch.txt
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> It would very useful to have the ability to automatically reference dependee
> project for which the project source code is locally found.
> Let's assume that module y depends on module x. The project description of
> module y will contain directly or indirectly - i.e. transitively - a
> dependency to module x.
> The execution of the goal "eclipse:eclipse" on the module y would normally
> generate an eclipse project with a jar dependency to module x.
> Often it is convenient to directly reference the module x as eclipse project
> to allow concurrent modification and compilation of both module x and y.
> The attached patch allows to automatically reference projects if the dependee
> project's source code is found in same directory as the dependent project. A
> project is a candidate match if the group-id and artifact-id properties of
> the two project equal and the two version equal or the dependee's version is
> the requested version but SNAPSHOT tagged.
> Example of directory structure:
> /usr/src/product/com.company.product.x/pom.xml
> /usr/src/product/com.company.product.y/pom.xml
> The feature can be enabled via the maven's boolean property
> eclipse.referenceDependeeProjects
> The property default value is false and therefore the feature is disabled per
> default.
> The following is an example of execution with the feature enabled:
> # mvn eclipse:eclipse -Declipse.referenceDependeeProjects=true
>
> Currently it is assumed that the dependee project sources are within a
> directory named after the project's artifact-id.
> Future extensions could consider the more general maven's version matching
> strategy - is this coded anywhere specific in maven's source code? - and
> possibly allowing for locating the dependee source in directories with
> generic names or paths.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
