hi Brett,
thanks so much the following tag is working fine!
outputDirectory${project.build.directory}/lib/outputDirectory
firstly, I would like to thanks to all Maven's developer for the hard
work.
M2 is exactly what I am dreaming to have for a long time.
I just hope m2 could be more
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
With the changes you *can* now do this in the jar-plugin: ...
to achieve what you are doing, you *can* also use a custom
assembly descriptor, ...
I think he was saying that its not just a matter of what *can* be done,
On 1/7/06, Christopher Cobb [EMAIL PROTECTED] wrote:
I think he was saying that its not just a matter of what *can* be done, it's
a matter of things just working. The constellation of maven plugins
should be set up so that you *normally* don't have customize a descriptor
over here to make
Man-Chi Leung wrote:
how can I change the generated jar location from default
project_dir/target/ to project_dir/target/lib?
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
Henry Isidro wrote:
Man-Chi Leung wrote:
how can I change the generated jar location from default
project_dir/target/ to project_dir/target/lib?
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
It's intentional. It's meant to be the location of the project.
What should go in JIRA is the ability to change the output location.
- Brett
On 1/6/06, Henry Isidro [EMAIL PROTECTED] wrote:
Henry Isidro wrote:
Man-Chi Leung wrote:
how can I change the generated jar location from default
if I want to remove the readonly restriction. do I need to rebuild
from the maven svn source trunk ? so I will use 2.1-SNAPSHOT instead
of 2.0.1?
can u guide me on which file and perhaps which line to do this change?
thanks for help
~manchi
On Jan 6, 2006, at 9:43 AM, Henry Isidro wrote:
Hmm.
I just saw that basedir is not basedir, but the directory I was
expecting. And outputDirectory is already used.
Since both are readonly, I think there is no harm in renaming them.
I'll do that now.
- Brett
On 1/6/06, Henry Isidro [EMAIL PROTECTED] wrote:
Brett Porter wrote:
It's
hi Brett,
I believe this issue is more important than just a path configuration.
the reason I want to change this location is very relevant to
package and assemble goal
1) $mvn package
firstly I copied all my dependencies to target/lib/ during my
package goal
!--
On 1/6/06, Man-Chi Leung [EMAIL PROTECTED] wrote:
hi Brett,
I believe this issue is more important than just a path configuration.
You've misunderstood. With the changes you can now do this in the jar-plugin:
outputDirectory${project.build.directory}/lib/outputDirectory
so the jar appears in
/war into your artifact for install or deploy)
-Original Message-
From: Man-Chi Leung [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 05, 2006 11:52 PM
To: Maven Users List
Subject: Re: [m2] how to change maven-jar-plugin's basedir ?
hi Brett,
I believe this issue is more important
how can I change the generated jar location from default
project_dir/target/ to project_dir/target/lib?
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
12 matches
Mail list logo