maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arnaud Heritier (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MECLIPSE-197) Automatic reference of dependee projects
Date Thu, 31 Jan 2008 14:07:58 GMT

     [ http://jira.codehaus.org/browse/MECLIPSE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arnaud Heritier closed MECLIPSE-197.
------------------------------------

         Assignee: Arnaud Heritier  (was: fabrizio giustina)
       Resolution: Duplicate
    Fix Version/s: 2.5

This issue is considered as fixed with MECLIPSE-344.
To try the latest SNAPSHOT (2.5-20080131.135640-18) of the incoming version you have to define
and activate this profile :
{code}
    <profile>
      <id>apache.snapshots</id>
      <repositories>
        <repository>
          <releases>
            <enabled>false</enabled>
          </releases>
          <snapshots/>
          <id>apache.snapshots</id>
          <name>Maven Snapshots</name>
          <url>http://people.apache.org/maven-snapshot-repository</url>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <releases>
            <enabled>false</enabled>
          </releases>
          <snapshots/>
          <id>apache.plugin.snapshots</id>
          <name>Maven Plugin Snapshots</name>
          <url>http://people.apache.org/maven-snapshot-repository</url>
        </pluginRepository>
      </pluginRepositories>
    </profile>
{code}
Then you have to call this command :
{code}
mvn org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
{code}
If you think that your problem isn't resolved, please give us your feedback and we'll reopen
the issue.

> 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: Dependencies resolution and build path
>            Reporter: Alessandro Evangelista
>            Assignee: Arnaud Heritier
>             Fix For: 2.5
>
>         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

        

Mime
View raw message