maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriel Moreira (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-2626) System scope dependencies in parent POM cause validation warnings for most plugins and errors in assembly plugin
Date Tue, 12 May 2009 01:04:45 GMT

    [ http://jira.codehaus.org/browse/MNG-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176043#action_176043
] 

Gabriel Moreira commented on MNG-2626:
--------------------------------------

Has any accepted solution for this bug or another related open bug?


Im trying to create these maven projects:
 - WebSphere 6.1 Runtime Libraries (using system scoped dependency path ${was61.home}/lib/XXXX.jar
from developer machine settings.xml)
 - WebSphere 5.1 Runtime Libraries (using system scoped dependency path ${was51.home}/lib/YYYY.jar
from developer machine settings.xml)
 - JBoss 4 Runtime Libraries ... (using system scoped dependency ...)
 - JBoss 5 Runtime Libraries ..(using system scoped dependency ...)
 - "My Framework" Libraries ... 
 - "My Portal" Runtime Libraries ... 

to use with our corporate applications:
  
  MyApp01 depends 'WebSphere 6.1 Runtime Libraries' and 'My Framework Libraries'
  MyApp02 depends 'WebSphere 5.1 Runtime Libraries' and 'My Portal Runtime Libraries'

but with maven (2.0 and 2.1)  we are getting error:

"system-scoped dependency must specify an absolute path systemPath."  for every system scoped
dependency on imported POM.xml



> System scope dependencies in parent POM cause validation warnings for most plugins and
errors in assembly plugin
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-2626
>                 URL: http://jira.codehaus.org/browse/MNG-2626
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Errors
>    Affects Versions: 2.0-alpha-1
>            Reporter: Brian Topping
>            Assignee: Jason van Zyl
>            Priority: Blocker
>             Fix For: 2.0.11
>
>         Attachments: interpolation-good.patch, interpolation.patch, MNG-2626it.tgz
>
>
> When system scope dependencies are in a parent POM and the systemPath for those variables
contain a variable to be interpolated as a root path, maven throws off a lot of spurious warnings
that the POM does not validate because system paths need to be absolute.  An example of this
in a parent POM (where ${jboss.home} is defined in ~/.m2/settings.xml):
> {code:xml}
> 		<dependency>
> 			<groupId>jboss</groupId>
> 			<artifactId>activation</artifactId>
> 			<version>4.0.4.GA</version>
> 			<scope>system</scope>
> 			<systemPath>${jboss.home}/server/default/lib/activation.jar</systemPath>
> 		</dependency>
> {code}
> In discussing this with John and Jason online, both apparently have generic implementations
that can go in at some point, but this is something I would like to get into 2.0.5.  The patch
is ~25 lines of new code with one replaced.  
> It's marked as blocker because we use the assembly plugin, which fails the build on the
validation problem where most other plugins just enumerate every system scope dependency.
 For now, I will distribute the patched version around the company though :-)
> thanks

-- 
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