Re: dependency:unpack vs. eclipse:eclipse
OK, I filed it under
http://jira.codehaus.org/browse/MNG-3401
Am Donnerstag 14. Februar 2008 schrieb Brian E. Fox:
No, this is a maven core bug and will probably have to be fixed in 2.1, but
file an issue anyway.
-Original Message-
From: Michael Heß [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 14, 2008 12:57 AM
To: Maven Users List
Subject: RE: dependency:unpack vs. eclipse:eclipse
Thanks Brian, for finding this out.
I have created a workaround as suggested. Only additional thing I had to
do, was to also bind the resources:resources to process-resources phase,
because otherwise the filtering occured before the dependency:unpack. It's
dirty, but at least it works now.
Have you already taken care of filing a bug? If not, I would take care of
this. The bug is in the dependency-plugin, right?
bye, Michael
Brian E. Fox schrieb:
I am able to reproduce this and it's an unfortunate bug in 2.0.x. The
only workaround I can suggest is to change the dependency plugin binding
to a later phase than is invoked by the eclipse plugin. According to [1]
the phase is generate-resources so you can bump it to process-resources.
[1]:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
-Original Message-
From: Michael Heß [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 13, 2008 1:07 AM
To: Maven Users List
Subject: RE: dependency:unpack vs. eclipse:eclipse
Sure,
here you go, I hope it somehow survives the transfer to the list. If it's
completely garbled I can also send you the file directly as an
attachment.
Furthermore I'd like to add the error I'm getting when binding the
dependendy-plugin unpack goal to a specific phase:
ERROR -
[INFO] One or more required plugin parameters are invalid/missing for
'dependency:unpack'
[0] Inside the definition for plugin 'maven-dependency-plugin' specify
the following:
configuration
...
artifactItemsVALUE/artifactItems
/configuration.
ERROR -
But as you can see in the pom below, I do have the wanted configuration
settings. Thanks for looking into this.
bye, Michael
---pom starts here---
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
parent
artifactIdabc/artifactId
groupIdde.customer/groupId
version1.0.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
groupIdde.customer.abc/groupId
artifactIdproduct-config/artifactId
packagingjar/packaging
version${parent.version}/version
nameproduct-config/name
dependencies
dependency
groupIdde.customer.abc.common/groupId
artifactIdabc-basis-config/artifactId
version${abc.common.version}/version
scopecompile/scope
/dependency
/dependencies
profiles
profile
idlocal/id
activation
property
namelocal/name
/property
/activation
build /
properties
maven.test.skiptrue/maven.test.skip
mvn.filter.file
${basedir}/src/main/filters/local.properties
/mvn.filter.file
/properties
/profile
!--other profiles here as well - intentionally left them out
--
/profiles
build
filters
filter${mvn.filter.file}/filter
/filters
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
resource
directorytarget/work/conf/directory
!-- copies the contents of conf to
target/conf --
targetPath../conf/targetPath
filteringtrue/filtering
/resource
/resources
plugins
!-- Java 1.5 --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
RE: dependency:unpack vs. eclipse:eclipse
Thanks Brian, for finding this out.
I have created a workaround as suggested. Only additional thing I had to
do, was to also bind the resources:resources to process-resources phase,
because otherwise the filtering occured before the dependency:unpack. It's
dirty, but at least it works now.
Have you already taken care of filing a bug? If not, I would take care of
this. The bug is in the dependency-plugin, right?
bye, Michael
Brian E. Fox schrieb:
I am able to reproduce this and it's an unfortunate bug in 2.0.x. The only
workaround I can suggest is to change the dependency plugin binding to a
later phase than is invoked by the eclipse plugin. According to [1] the
phase is generate-resources so you can bump it to process-resources.
[1]:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
-Original Message-
From: Michael Heß [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 13, 2008 1:07 AM
To: Maven Users List
Subject: RE: dependency:unpack vs. eclipse:eclipse
Sure,
here you go, I hope it somehow survives the transfer to the list. If it's
completely garbled I can also send you the file directly as an attachment.
Furthermore I'd like to add the error I'm getting when binding the
dependendy-plugin unpack goal to a specific phase:
ERROR -
[INFO] One or more required plugin parameters are invalid/missing for
'dependency:unpack'
[0] Inside the definition for plugin 'maven-dependency-plugin' specify the
following:
configuration
...
artifactItemsVALUE/artifactItems
/configuration.
ERROR -
But as you can see in the pom below, I do have the wanted configuration
settings. Thanks for looking into this.
bye, Michael
---pom starts here---
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
parent
artifactIdabc/artifactId
groupIdde.customer/groupId
version1.0.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
groupIdde.customer.abc/groupId
artifactIdproduct-config/artifactId
packagingjar/packaging
version${parent.version}/version
nameproduct-config/name
dependencies
dependency
groupIdde.customer.abc.common/groupId
artifactIdabc-basis-config/artifactId
version${abc.common.version}/version
scopecompile/scope
/dependency
/dependencies
profiles
profile
idlocal/id
activation
property
namelocal/name
/property
/activation
build /
properties
maven.test.skiptrue/maven.test.skip
mvn.filter.file
${basedir}/src/main/filters/local.properties
/mvn.filter.file
/properties
/profile
!--other profiles here as well - intentionally left them out
--
/profiles
build
filters
filter${mvn.filter.file}/filter
/filters
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
resource
directorytarget/work/conf/directory
!-- copies the contents of conf to
target/conf --
targetPath../conf/targetPath
filteringtrue/filtering
/resource
/resources
plugins
!-- Java 1.5 --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
version2.0/version
inheritedfalse/inherited
configuration
artifactItems
RE: dependency:unpack vs. eclipse:eclipse
No, this is a maven core bug and will probably have to be fixed in 2.1, but
file an issue anyway.
-Original Message-
From: Michael Heß [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 14, 2008 12:57 AM
To: Maven Users List
Subject: RE: dependency:unpack vs. eclipse:eclipse
Thanks Brian, for finding this out.
I have created a workaround as suggested. Only additional thing I had to
do, was to also bind the resources:resources to process-resources phase,
because otherwise the filtering occured before the dependency:unpack. It's
dirty, but at least it works now.
Have you already taken care of filing a bug? If not, I would take care of
this. The bug is in the dependency-plugin, right?
bye, Michael
Brian E. Fox schrieb:
I am able to reproduce this and it's an unfortunate bug in 2.0.x. The only
workaround I can suggest is to change the dependency plugin binding to a
later phase than is invoked by the eclipse plugin. According to [1] the
phase is generate-resources so you can bump it to process-resources.
[1]:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
-Original Message-
From: Michael Heß [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 13, 2008 1:07 AM
To: Maven Users List
Subject: RE: dependency:unpack vs. eclipse:eclipse
Sure,
here you go, I hope it somehow survives the transfer to the list. If it's
completely garbled I can also send you the file directly as an attachment.
Furthermore I'd like to add the error I'm getting when binding the
dependendy-plugin unpack goal to a specific phase:
ERROR -
[INFO] One or more required plugin parameters are invalid/missing for
'dependency:unpack'
[0] Inside the definition for plugin 'maven-dependency-plugin' specify the
following:
configuration
...
artifactItemsVALUE/artifactItems
/configuration.
ERROR -
But as you can see in the pom below, I do have the wanted configuration
settings. Thanks for looking into this.
bye, Michael
---pom starts here---
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
parent
artifactIdabc/artifactId
groupIdde.customer/groupId
version1.0.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
groupIdde.customer.abc/groupId
artifactIdproduct-config/artifactId
packagingjar/packaging
version${parent.version}/version
nameproduct-config/name
dependencies
dependency
groupIdde.customer.abc.common/groupId
artifactIdabc-basis-config/artifactId
version${abc.common.version}/version
scopecompile/scope
/dependency
/dependencies
profiles
profile
idlocal/id
activation
property
namelocal/name
/property
/activation
build /
properties
maven.test.skiptrue/maven.test.skip
mvn.filter.file
${basedir}/src/main/filters/local.properties
/mvn.filter.file
/properties
/profile
!--other profiles here as well - intentionally left them out
--
/profiles
build
filters
filter${mvn.filter.file}/filter
/filters
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
resource
directorytarget/work/conf/directory
!-- copies the contents of conf to
target/conf --
targetPath../conf/targetPath
filteringtrue/filtering
/resource
/resources
plugins
!-- Java 1.5 --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
RE: dependency:unpack vs. eclipse:eclipse
Sure,
here you go, I hope it somehow survives the transfer to the list. If it's
completely garbled I can also send you the file directly as an attachment.
Furthermore I'd like to add the error I'm getting when binding the
dependendy-plugin unpack goal to a specific phase:
ERROR -
[INFO] One or more required plugin parameters are invalid/missing for
'dependency:unpack'
[0] Inside the definition for plugin 'maven-dependency-plugin' specify the
following:
configuration
...
artifactItemsVALUE/artifactItems
/configuration.
ERROR -
But as you can see in the pom below, I do have the wanted configuration
settings. Thanks for looking into this.
bye, Michael
---pom starts here---
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
parent
artifactIdabc/artifactId
groupIdde.customer/groupId
version1.0.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
groupIdde.customer.abc/groupId
artifactIdproduct-config/artifactId
packagingjar/packaging
version${parent.version}/version
nameproduct-config/name
dependencies
dependency
groupIdde.customer.abc.common/groupId
artifactIdabc-basis-config/artifactId
version${abc.common.version}/version
scopecompile/scope
/dependency
/dependencies
profiles
profile
idlocal/id
activation
property
namelocal/name
/property
/activation
build /
properties
maven.test.skiptrue/maven.test.skip
mvn.filter.file
${basedir}/src/main/filters/local.properties
/mvn.filter.file
/properties
/profile
!--other profiles here as well - intentionally left them out
--
/profiles
build
filters
filter${mvn.filter.file}/filter
/filters
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
resource
directorytarget/work/conf/directory
!-- copies the contents of conf to
target/conf --
targetPath../conf/targetPath
filteringtrue/filtering
/resource
/resources
plugins
!-- Java 1.5 --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
version2.0/version
inheritedfalse/inherited
configuration
artifactItems
artifactItem
groupIdde.customer.abc.common/groupId
artifactIdabc-basis-config/artifactId
version${abc.common.version}/version
typejar/type
outputDirectory
${project.build.directory}/work
/outputDirectory
/artifactItem
/artifactItems
excludes
excludeMETA-INF/**/exclude
/excludes
/configuration
RE: dependency:unpack vs. eclipse:eclipse
I am able to reproduce this and it's an unfortunate bug in 2.0.x. The only
workaround I can suggest is to change the dependency plugin binding to a later
phase than is invoked by the eclipse plugin. According to [1] the phase is
generate-resources so you can bump it to process-resources.
[1]: http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
-Original Message-
From: Michael Heß [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 13, 2008 1:07 AM
To: Maven Users List
Subject: RE: dependency:unpack vs. eclipse:eclipse
Sure,
here you go, I hope it somehow survives the transfer to the list. If it's
completely garbled I can also send you the file directly as an attachment.
Furthermore I'd like to add the error I'm getting when binding the
dependendy-plugin unpack goal to a specific phase:
ERROR -
[INFO] One or more required plugin parameters are invalid/missing for
'dependency:unpack'
[0] Inside the definition for plugin 'maven-dependency-plugin' specify the
following:
configuration
...
artifactItemsVALUE/artifactItems
/configuration.
ERROR -
But as you can see in the pom below, I do have the wanted configuration
settings. Thanks for looking into this.
bye, Michael
---pom starts here---
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
parent
artifactIdabc/artifactId
groupIdde.customer/groupId
version1.0.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
groupIdde.customer.abc/groupId
artifactIdproduct-config/artifactId
packagingjar/packaging
version${parent.version}/version
nameproduct-config/name
dependencies
dependency
groupIdde.customer.abc.common/groupId
artifactIdabc-basis-config/artifactId
version${abc.common.version}/version
scopecompile/scope
/dependency
/dependencies
profiles
profile
idlocal/id
activation
property
namelocal/name
/property
/activation
build /
properties
maven.test.skiptrue/maven.test.skip
mvn.filter.file
${basedir}/src/main/filters/local.properties
/mvn.filter.file
/properties
/profile
!--other profiles here as well - intentionally left them out
--
/profiles
build
filters
filter${mvn.filter.file}/filter
/filters
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
resource
directorytarget/work/conf/directory
!-- copies the contents of conf to
target/conf --
targetPath../conf/targetPath
filteringtrue/filtering
/resource
/resources
plugins
!-- Java 1.5 --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
version2.0/version
inheritedfalse/inherited
configuration
artifactItems
artifactItem
groupIdde.customer.abc.common/groupId
artifactIdabc-basis-config/artifactId
version${abc.common.version}/version
typejar/type
RE: dependency:unpack vs. eclipse:eclipse
The faq entry about the executions/non executions would only apply when running dependency:unpack directly...it shouldn't have any issues with eclipse:eclipse. (although I haven't tested it recently). Can you paste your pom so I can look at it? -Original Message- From: Michael Heß [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 12, 2008 10:34 AM To: users@maven.apache.org Subject: dependency:unpack vs. eclipse:eclipse Hi list, I've been searching and fiddling around all day, with no success so far. So this is my only hope of finding an answer. My basic setup looks like the following: I have an artifact which creates a ZIP-assembly. Lets call it artifact-resources.zip Furthermore I have anotherArtifact which depends on artifact-resources.zip. As the name states, the artifact does not contain any sources, but resources. These resources I want to have unpacked and filtered during anotherArtifacts build. So what I did, was to add a dependency-plugin-configuration to anotherArtifacts pom.xml, and I bound it to the generate-resources phase. At that point everything was still fine. My build went all the way through, the resources got unpacked and filtered, and were used correctly afterwards as the build lifecycle went on. Then I wanted to use maven-eclipse-plugin on anotherArtifact. At that point, I ran into the problem, that dependency:unpack fails, because eclipse:eclipse seems to trigger it in the CLI way. Although I do not really know what it maven internally means, I did as I was told in the maven-dependency-plugin faq, and removed my execution entries out of the configuration. This fixed the eclipse:eclipse problem. But, now this again leads to the following problems: Since my maven-dependency-plugin configuration is no longer bound to any specific phase it should run during process-sources. At least the plugins documentation says so. But it does not, I don't know why. So, right now my conclusion for today is (and I really do hope someone can prove me wrong): Either - I can have dependency:unpack attached to a specific phase OR - I can have eclipse:eclipse working As stated before. I spent the whole afternoon trying things out. Although I probably learned a lot, I'm desperate for help. I really do not have any more ideas what to do. Thanks for reading all this, and maybe providing any insight. bye, Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
