You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/09/28 03:06:14 UTC
[jira] Updated: (MNG-955) There should be possible to use artifacts instead of project references in multi module projects
[ http://jira.codehaus.org/browse/MNG-955?page=all ]
Brett Porter updated MNG-955:
-----------------------------
Fix Version: 2.0-beta-4
> There should be possible to use artifacts instead of project references in multi module projects
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-955
> URL: http://jira.codehaus.org/browse/MNG-955
> Project: Maven 2
> Type: Bug
> Components: maven-eclipse-plugin
> Reporter: Kaare Nilsen
> Fix For: 2.0-beta-4
>
>
> One of the fine things with maven is that one can have several modules in a project.
> But in the eclipse plugin all dependent modules in the project is added as a project reference instead of using the delivered artifact.
> As a result i have to have all my modules (eclipse projects) opened just to compile in eclipse.
> I think this should be an option. e.g.
> <useProjectReference>true</useProjectReference>
> with this set to true as default, but when false, the classpath should use a reference to the jar in local repos as all other artifacts
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org