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/11/04 09:07:06 UTC
[jira] Updated: (MNG-1384) optional dependencies not resolved while compiling from a master project
[ http://jira.codehaus.org/browse/MNG-1384?page=all ]
Brett Porter updated MNG-1384:
------------------------------
Description:
project-A has a dependency defined as optional but required to compile.
Running "mvn install" directly on project-A works.
If project-A is referenced as a module in master-project, running "mvn install" from master-project will result in a build failure, since direct optional dependencies will not be included in project-A compile classpath.
A related issue (currently fixed by manually resolving artifacts) is that optional direct dependencies were not included in the classpath file generated by the m2 eclipse plugin (direct optional dependencies are missing from project.getTestArtifacts() with @requiresDependencyResolution test)
Shouldn't optional dependencies only be excluded from referenced projects or am I missing something?
was:
project-A has a dependency defined as optional but required to compile.
Running "mvn install" directly on project-A works.
If project-A is referenced as a module in master-project, running "mvn install" from master-project will result in a build failure, since direct optional dependencies will not be included in project-A compile classpath.
A related issue (currently fixed by manually resolving artifacts) is that optional direct dependencies were not included in the classpath file generated by the m2 eclipse plugin (direct optional dependencies are missing from project.getTestArtifacts() with @requiresDependencyResolution test)
Shouldn't optional dependencies only be excluded from referenced projects or am I missing something?
Fix Version: 2.0.1
Environment:
> optional dependencies not resolved while compiling from a master project
> ------------------------------------------------------------------------
>
> Key: MNG-1384
> URL: http://jira.codehaus.org/browse/MNG-1384
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0
> Reporter: fabrizio giustina
> Priority: Critical
> Fix For: 2.0.1
>
>
> project-A has a dependency defined as optional but required to compile.
> Running "mvn install" directly on project-A works.
> If project-A is referenced as a module in master-project, running "mvn install" from master-project will result in a build failure, since direct optional dependencies will not be included in project-A compile classpath.
> A related issue (currently fixed by manually resolving artifacts) is that optional direct dependencies were not included in the classpath file generated by the m2 eclipse plugin (direct optional dependencies are missing from project.getTestArtifacts() with @requiresDependencyResolution test)
> Shouldn't optional dependencies only be excluded from referenced projects or am I missing something?
--
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