[jira] Commented: (MNG-2626) System scope dependencies in parent POM cause validation warnings for most plugins and errors in assembly plugin
[
http://jira.codehaus.org/browse/MNG-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=173312#action_173312
]
Cimballi commented on MNG-2626:
---
On my side, the problem is still present.
I have a main POM, and one of the modules as a system dependency, and it
generates the system-scoped dependency must specify an absolute path
systemPath. error.
The dependency is not present in the main POM, only in the POM of the module.
I tested with versions apache-maven-2.0.11-20090213.232410-1 and
apache-maven-2.1.0.
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
groupIdjboss/groupId
artifactIdactivation/artifactId
version4.0.4.GA/version
scopesystem/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
[jira] Commented: (MNG-2626) System scope dependencies in parent POM cause validation warnings for most plugins and errors in assembly plugin
[
http://jira.codehaus.org/browse/MNG-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=173332#action_173332
]
Cimballi commented on MNG-2626:
---
Well, sorry guys, it was a false alarm. I was using a property in the path and
the property was not well setted. It works well with 2.0.9, 2.0.11 and 2.1.0.
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
groupIdjboss/groupId
artifactIdactivation/artifactId
version4.0.4.GA/version
scopesystem/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
[jira] Created: (MNG-3992) Maven dependency go-offline doesn't download surefire-api jar
Maven dependency go-offline doesn't download surefire-api jar - Key: MNG-3992 URL: http://jira.codehaus.org/browse/MNG-3992 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Environment: Windows XP, JDK 1.5.x, Maven 2.0.9 Reporter: Cimballi Priority: Minor I have this in my pom.xml : plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.4.3/version ... /plugin And if I run the goal dependency:go-offline, the surefire-api-2.4.3.jar is not downloaded and so the project cannot be run offline. The surefire plugin and the surefire-boot jars are downloaded. -- 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
