[
http://jira.codehaus.org/browse/MECLIPSE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier closed MECLIPSE-158.
------------------------------------
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.
> Add the ability to selectively treat a referenced project as a local
> repository file
> ------------------------------------------------------------------------------------
>
> Key: MECLIPSE-158
> URL: http://jira.codehaus.org/browse/MECLIPSE-158
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: Multi-projects
> Affects Versions: 2.2
> Reporter: Tim O'Brien
> Assignee: Arnaud Heritier
> Fix For: 2.5
>
>
> The issue is that I have a large project with many interdependent submodules.
> One of the submodules uses XML Beans to generate a set of objects from an
> XML Schema. This works perfectly, but Eclipse has a problem with the class
> names used in XMLBeans, and I have to close that particular project for
> Eclipse not to complain. But, if I close that project, all of the projects
> that depend on it directly (through a referenced project), then complain that
> they are missing a referenced project.
> The solution is to relate the project via the local repository (M2_REPO/...)
> not via a project reference, but in EclipseClasspathWriter, all projects
> available via the reactor are treated as referenced projects:
> if ( dep.isReferencedProject() && !config.isPde() )
> {
> path = "/" + dep.getArtifactId(); //$NON-NLS-1$
> kind = ATTR_SRC;
> }
> One solution would be to not use project references, but the problem only
> happens with specific projects, and I want to be able to selectively mark
> dependencies as not being referenced.
> Something as simple as, this:
> <config>
> <localReference>
> <groupId>blah</groupId>
> <artifactId>blah</artifactId>
> </localReference>
> </config>
> Where the dependency identified by that groupId and artifactId would be
> treated not as a direct project reference but as a link to the local
> repository.
> Does that make any sense?
--
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
