[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=182145#action_182145
]
Brett Porter commented on MNG-2626:
---
Gabriel, do you have a test project? Like Torben, I can't reproduce using the
original example provided.
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.2.1
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=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/.jar from developer machine settings.xml)
- WebSphere 5.1 Runtime Libraries (using system scoped dependency path
${was51.home}/lib/.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
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=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=173325#action_173325
]
Benjamin Bentmann commented on MNG-2626:
Cimballi, can you provide a test project to easily demonstrate your issue?
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] 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=163392#action_163392
]
Torben S. Giesselmann commented on MNG-2626:
Has this been fixed? I can't reproduce the problem; works perfectly with
2.0.11-SNAPSHOT.
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-tabpanel#action_110913
]
Brian Fox commented on MNG-2626:
Can we get updated patches and ITs for this? I can try to get it into 2.0.8
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: Reviewed Pending Version Assignment
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=comments#action_78134 ]
Brian Topping commented on MNG-2626:
Hmm, that XML was supposed to be as follows:
{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}
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.1
Reporter: Brian Topping
Priority: Blocker
Attachments: interpolation.patch
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=comments#action_78135 ]
Jon commented on MNG-2626:
--
Please accept this patch as soon as possible as I really don't feel like having
to install Brian's hacked version on my box. Who knows what sort of crazy shit
backdoors he included in it. ;-)
Thank you.
jon
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.1
Reporter: Brian Topping
Priority: Blocker
Attachments: interpolation.patch
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
