Re: expand war deps
You don't need to have common-war as a dependency if you provide all
details in the ArtifactItem section of the configuration.
Removing the dependency and add the version to ArtifactItem will just
run fine and it's not a hack (Note if you unpack the jar in the war,
it is provided so it's not a hack either ; it's just provided by you
instead of the container).
On 8/17/07, John Coleman [EMAIL PROTECTED] wrote:
Thanks for these tips I now have it working just right. The method as
follows...
dependency
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
version1.3-SNAPSHOT/version
scopeprovided/scope
typejar/type
/dependency
I have to mark the dependency as provided, so the jar is not left in /lib -
to me this doesn't quite look right 'cos the dependency is not provided by
the container, so this is a hack.
The include/excludes are not required, so I stripped them out and I get just
what I want. :)
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack/id
phasegenerate-resources/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
typejar/type
outputDirectory${project.build.directory}/${project.build.finalName}/WEB-INF/classes/outputDirectory
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
Excellent.
Regards,
John
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: 16 August 2007 19:56
To: Maven Users List
Subject: RE: expand war deps
Hi John,
I see two issues below. The first is that the includes/excludes is only
available in 2.0-alpha-5-SNAPSHOT. The second is more to your question. You
can skip specifying a version in the artifactItems if you put that dependency
version in your dependencyManagement section. Then you can also omit it in
your dependencies declaration and have only one place to control the version.
--Brian
-Original Message-
From: John Coleman [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 16, 2007 8:09 AM
To: Maven Users List
Subject: RE: expand war deps
Hi Stephane,
I grafted an example off the dependency plugin site, but it didn't go too
well as you can see below! I just want to unpack that JAR instead of add it
to lib directory.
Any ideas what is wrong? I'm a bit concerned that I have both a declared
dependency at the top of my pom and then this plugin configuration - could
that lead to version conflicts, will the plugin config default to the
previously declared version?
TIA
John
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack/id
phasepackage/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
!--version1.3-SNAPSHOT/version--
typejar/type
overWritefalse/overWrite
outputDirectory${project.build.directory}/${project.build.finalName}/WEB-INF/classes/outputDirectory
includes**/*.class,**/*.xml/includes
excludes**/*test.class/excludes
/artifactItem
/artifactItems
includes**/*.java/includes
excludes**/*.properties/excludes
outputDirectory${project.build.directory}/wars/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
/configuration
/execution
/executions
/plugin
[INFO]Failed
RE: expand war deps
Actually, it looks like you put the entry below in dependencies, not
dependencyManagement. But if you don't want it in lib, then you should only
specify it in the artifactItems so it's not handled like a normal dependency.
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 21, 2007 4:13 PM
To: Maven Users List
Subject: Re: expand war deps
You don't need to have common-war as a dependency if you provide all
details in the ArtifactItem section of the configuration.
Removing the dependency and add the version to ArtifactItem will just
run fine and it's not a hack (Note if you unpack the jar in the war,
it is provided so it's not a hack either ; it's just provided by you
instead of the container).
On 8/17/07, John Coleman [EMAIL PROTECTED] wrote:
Thanks for these tips I now have it working just right. The method as
follows...
dependency
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
version1.3-SNAPSHOT/version
scopeprovided/scope
typejar/type
/dependency
I have to mark the dependency as provided, so the jar is not left in /lib -
to me this doesn't quite look right 'cos the dependency is not provided by
the container, so this is a hack.
The include/excludes are not required, so I stripped them out and I get just
what I want. :)
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack/id
phasegenerate-resources/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
typejar/type
outputDirectory${project.build.directory}/${project.build.finalName}/WEB-INF/classes/outputDirectory
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
Excellent.
Regards,
John
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: 16 August 2007 19:56
To: Maven Users List
Subject: RE: expand war deps
Hi John,
I see two issues below. The first is that the includes/excludes is only
available in 2.0-alpha-5-SNAPSHOT. The second is more to your question. You
can skip specifying a version in the artifactItems if you put that dependency
version in your dependencyManagement section. Then you can also omit it in
your dependencies declaration and have only one place to control the version.
--Brian
-Original Message-
From: John Coleman [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 16, 2007 8:09 AM
To: Maven Users List
Subject: RE: expand war deps
Hi Stephane,
I grafted an example off the dependency plugin site, but it didn't go too
well as you can see below! I just want to unpack that JAR instead of add it
to lib directory.
Any ideas what is wrong? I'm a bit concerned that I have both a declared
dependency at the top of my pom and then this plugin configuration - could
that lead to version conflicts, will the plugin config default to the
previously declared version?
TIA
John
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack/id
phasepackage/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
!--version1.3-SNAPSHOT/version--
typejar/type
overWritefalse/overWrite
outputDirectory${project.build.directory}/${project.build.finalName}/WEB-INF/classes/outputDirectory
includes**/*.class,**/*.xml/includes
excludes**/*test.class/excludes
/artifactItem
/artifactItems
includes**/*.java/includes
excludes
RE: expand war deps
Thanks for these tips I now have it working just right. The method as follows...
dependency
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
version1.3-SNAPSHOT/version
scopeprovided/scope
typejar/type
/dependency
I have to mark the dependency as provided, so the jar is not left in /lib -
to me this doesn't quite look right 'cos the dependency is not provided by the
container, so this is a hack.
The include/excludes are not required, so I stripped them out and I get just
what I want. :)
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack/id
phasegenerate-resources/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
typejar/type
outputDirectory${project.build.directory}/${project.build.finalName}/WEB-INF/classes/outputDirectory
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
Excellent.
Regards,
John
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: 16 August 2007 19:56
To: Maven Users List
Subject: RE: expand war deps
Hi John,
I see two issues below. The first is that the includes/excludes is only
available in 2.0-alpha-5-SNAPSHOT. The second is more to your question. You can
skip specifying a version in the artifactItems if you put that dependency
version in your dependencyManagement section. Then you can also omit it in your
dependencies declaration and have only one place to control the version.
--Brian
-Original Message-
From: John Coleman [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 16, 2007 8:09 AM
To: Maven Users List
Subject: RE: expand war deps
Hi Stephane,
I grafted an example off the dependency plugin site, but it didn't go too well
as you can see below! I just want to unpack that JAR instead of add it to lib
directory.
Any ideas what is wrong? I'm a bit concerned that I have both a declared
dependency at the top of my pom and then this plugin configuration - could that
lead to version conflicts, will the plugin config default to the previously
declared version?
TIA
John
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack/id
phasepackage/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
!--version1.3-SNAPSHOT/version--
typejar/type
overWritefalse/overWrite
outputDirectory${project.build.directory}/${project.build.finalName}/WEB-INF/classes/outputDirectory
includes**/*.class,**/*.xml/includes
excludes**/*test.class/excludes
/artifactItem
/artifactItems
includes**/*.java/includes
excludes**/*.properties/excludes
outputDirectory${project.build.directory}/wars/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
/configuration
/execution
/executions
/plugin
[INFO]Failed to configure plugin parameters for:
org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
Cause: Cannot find setter nor field in
org.apache.maven.plugin.dependency.fromConfiguration.ArtifactItem for 'includes'
[INFO]
[DEBUG]Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring:
org.apache.maven.plugins:maven-dependency-plugin. Reason: Unable to parse the
created DOM for plugin configuration
RE: expand war deps
Hi Stephane,
I grafted an example off the dependency plugin site, but it didn't go too well
as you can see below! I just want to unpack that JAR instead of add it to lib
directory.
Any ideas what is wrong? I'm a bit concerned that I have both a declared
dependency at the top of my pom and then this plugin configuration - could that
lead to version conflicts, will the plugin config default to the previously
declared version?
TIA
John
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack/id
phasepackage/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
!--version1.3-SNAPSHOT/version--
typejar/type
overWritefalse/overWrite
outputDirectory${project.build.directory}/${project.build.finalName}/WEB-INF/classes/outputDirectory
includes**/*.class,**/*.xml/includes
excludes**/*test.class/excludes
/artifactItem
/artifactItems
includes**/*.java/includes
excludes**/*.properties/excludes
outputDirectory${project.build.directory}/wars/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
/configuration
/execution
/executions
/plugin
[INFO]Failed to configure plugin parameters for:
org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
Cause: Cannot find setter nor field in
org.apache.maven.plugin.dependency.fromConfiguration.ArtifactItem for 'includes'
[INFO]
[DEBUG]Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring:
org.apache.maven.plugins:maven-dependency-plugin. Reason: Unable to parse the
created DOM for plugin configuration
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:639)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:551)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:530)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:309)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:276)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760)
at
org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:257)
at
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131)
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: 15 August 2007 19:26
To: Maven Users List
Subject: Re: expand war deps
Hi,
Yep you'll need to setup resources:unpack in the generate-resources
phase. Next version of the WAR plugin has a new overlay handling but
we do not consider handling jars for the moment.
Regards,
Stéphane
On 8/15/07, John Coleman [EMAIL PROTECTED] wrote:
Hi,
I have a WAR project that depends on a JAR.
Can I expand the contents of the JAR dependency into my webapps classes
directory automatically with a setting, or do I have to do something
more manual like setting up a dependency:unpack? Anyone got an example
pls.
TIA
John
Eurobase International Limited and its subsidiaries (Eurobase) are unable to
exercise control over the content of information in E-Mails. Any views and
opinions expressed may be personal to the sender and are not necessarily
those of Eurobase. Eurobase will not enter into any contractual obligations
in respect of any part of its business in any E-mail.
Privileged / confidential information may be contained in this message and
/or any attachments. This E-mail is intended for the use of the addressee(s)
only and may contain confidential
RE: expand war deps
Hi John,
I see two issues below. The first is that the includes/excludes is only
available in 2.0-alpha-5-SNAPSHOT. The second is more to your question. You can
skip specifying a version in the artifactItems if you put that dependency
version in your dependencyManagement section. Then you can also omit it in your
dependencies declaration and have only one place to control the version.
--Brian
-Original Message-
From: John Coleman [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 16, 2007 8:09 AM
To: Maven Users List
Subject: RE: expand war deps
Hi Stephane,
I grafted an example off the dependency plugin site, but it didn't go too well
as you can see below! I just want to unpack that JAR instead of add it to lib
directory.
Any ideas what is wrong? I'm a bit concerned that I have both a declared
dependency at the top of my pom and then this plugin configuration - could that
lead to version conflicts, will the plugin config default to the previously
declared version?
TIA
John
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack/id
phasepackage/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
!--version1.3-SNAPSHOT/version--
typejar/type
overWritefalse/overWrite
outputDirectory${project.build.directory}/${project.build.finalName}/WEB-INF/classes/outputDirectory
includes**/*.class,**/*.xml/includes
excludes**/*test.class/excludes
/artifactItem
/artifactItems
includes**/*.java/includes
excludes**/*.properties/excludes
outputDirectory${project.build.directory}/wars/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
/configuration
/execution
/executions
/plugin
[INFO]Failed to configure plugin parameters for:
org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
Cause: Cannot find setter nor field in
org.apache.maven.plugin.dependency.fromConfiguration.ArtifactItem for 'includes'
[INFO]
[DEBUG]Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring:
org.apache.maven.plugins:maven-dependency-plugin. Reason: Unable to parse the
created DOM for plugin configuration
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:639)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:551)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:530)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:309)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:276)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760)
at
org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:257)
at
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131)
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: 15 August 2007 19:26
To: Maven Users List
Subject: Re: expand war deps
Hi,
Yep you'll need to setup resources:unpack in the generate-resources
phase. Next version of the WAR plugin has a new overlay handling but
we do not consider handling jars for the moment.
Regards,
Stéphane
On 8/15/07, John Coleman [EMAIL PROTECTED] wrote:
Hi,
I have a WAR project that depends on a JAR.
Can I expand the contents of the JAR dependency into my webapps classes
directory automatically with a setting, or do I have to do something
more manual like setting up a dependency:unpack? Anyone got an example
pls.
TIA
Re: expand war deps
Anyway an ArtifactItem does not need the version, the plugin is able
to detect it automatically from the project's dependencies. You only
need to specify all parameters if you want to act on an artifact that
is not a dependency of the project.
Stéphane
On 8/16/07, Brian E. Fox [EMAIL PROTECTED] wrote:
Hi John,
I see two issues below. The first is that the includes/excludes is only
available in 2.0-alpha-5-SNAPSHOT. The second is more to your question. You
can skip specifying a version in the artifactItems if you put that dependency
version in your dependencyManagement section. Then you can also omit it in
your dependencies declaration and have only one place to control the version.
--Brian
-Original Message-
From: John Coleman [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 16, 2007 8:09 AM
To: Maven Users List
Subject: RE: expand war deps
Hi Stephane,
I grafted an example off the dependency plugin site, but it didn't go too
well as you can see below! I just want to unpack that JAR instead of add it
to lib directory.
Any ideas what is wrong? I'm a bit concerned that I have both a declared
dependency at the top of my pom and then this plugin configuration - could
that lead to version conflicts, will the plugin config default to the
previously declared version?
TIA
John
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack/id
phasepackage/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.eurobase/groupId
artifactIdcommon-wac/artifactId
!--version1.3-SNAPSHOT/version--
typejar/type
overWritefalse/overWrite
outputDirectory${project.build.directory}/${project.build.finalName}/WEB-INF/classes/outputDirectory
includes**/*.class,**/*.xml/includes
excludes**/*test.class/excludes
/artifactItem
/artifactItems
includes**/*.java/includes
excludes**/*.properties/excludes
outputDirectory${project.build.directory}/wars/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
/configuration
/execution
/executions
/plugin
[INFO]Failed to configure plugin parameters for:
org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
Cause: Cannot find setter nor field in
org.apache.maven.plugin.dependency.fromConfiguration.ArtifactItem for
'includes'
[INFO]
[DEBUG]Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring:
org.apache.maven.plugins:maven-dependency-plugin. Reason: Unable to parse the
created DOM for plugin configuration
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:639)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:551)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:530)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:309)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:276)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760)
at
org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:257)
at
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131)
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: 15 August 2007 19:26
To: Maven Users List
Subject: Re: expand war deps
Hi,
Yep you'll need to setup resources:unpack in the generate-resources
phase. Next version of the WAR plugin has a new overlay handling but
we do
Re: expand war deps
Hi, Yep you'll need to setup resources:unpack in the generate-resources phase. Next version of the WAR plugin has a new overlay handling but we do not consider handling jars for the moment. Regards, Stéphane On 8/15/07, John Coleman [EMAIL PROTECTED] wrote: Hi, I have a WAR project that depends on a JAR. Can I expand the contents of the JAR dependency into my webapps classes directory automatically with a setting, or do I have to do something more manual like setting up a dependency:unpack? Anyone got an example pls. TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
