[
http://jira.codehaus.org/browse/MECLIPSE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier closed MECLIPSE-256.
------------------------------------
Assignee: Arnaud Heritier
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.
> [PATCH]Flat Maven2 Multiproject Structures and Classpath Resolution as
> Projects (not binaries)
> -----------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-256
> URL: http://jira.codehaus.org/browse/MECLIPSE-256
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: Dependencies resolution and build path, Multi-projects
> Affects Versions: 2.3
> Reporter: Kevin Ross
> Assignee: Arnaud Heritier
> Fix For: 2.5
>
>
> In a project structure where 'root' projects are flat/siblings with child
> projects or modules, we need to resolve actual projects on the local system
> as eclipse project dependencies for ease of debugging, hot deployment etc.
> The following code is a hack, perhaps should be an option to be turned
> on/off, but PLEASE include it. It is certainly doubtful to hurt...
> In AbstractIdeSupportMojo.doDependencyResolution() towards the end of the
> method and before the instantiation of the IdeDependency object please:
> <<<<add this>>>>
> if (new File( project.getBasedir(), "../" +
> artifact.getArtifactId() ).exists()) {
> getLog().info( "Adding project dependency: "
> + artifact.getArtifactId() );
> isReferencedProject = true;
> }
> <<<</add this>>>>
> // for reference:
> IdeDependency dep = new IdeDependency(
> artifact.getGroupId(), artifact.getArtifactId(), artifact.getVersion(),
> isReferencedProject, Artifact.SCOPE_TEST.equals( artifact.getScope() ),
> Artifact.SCOPE_SYSTEM.equals( artifact.getScope() ),
> Artifact.SCOPE_PROVIDED.equals( artifact.getScope() ),
> artifact.getArtifactHandler().isAddedToClasspath(), artifact
> .getFile(), artifact.getType(),
> isOsgiBundle, osgiSymbolicName, dependencyDepth );
--
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
