Hi -
Is this available as a Maven2 plugin?
Thanks,
Rk
x77309
-Original Message-
From: Torsten Curdt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 11, 2005 3:22 AM
To: Maven Users List
Subject: adding subversion revision to manifest
I've come up with a simple maven plugin that
Is there an equivalent of this for m1.0.2?
Thanks,
Rk
x77309
On Wed, 19 Oct 2005, Jason van Zyl wrote:
On Wed, 2005-10-19 at 13:42 +0200, Roy van der Kuil wrote:
Hi All,
We are currently moving (or at least trying too) from ant to maven. Mostly
because we'd really like to solve those
With m102, a project apps uses artifactId dcm-apps and uses
war plugin with the settings
maven.war.final.name: Foo.war
However, while war:war generates Foo.war, the war:deploy goal
chooses to rename it to ${pom.artifactId}.war
$ maven war:deply
war:deploy:
[echo] maven.repo.list is
I do not mind if war:deploy wants to append ${pom.currentVersion}
or SNAPSHOT to the deploted artifact on the remote repo; but
my issue is that it is changing the name of the artifact
from
${maven.war.final.name}.war
to
${pom.artifactId}.war
Thanks,
Rk
x77309
On Wed, 19 Oct 2005,
This is a stage when you'd get a number of
How do I do this m1.x function in m2? questions
from m1.x users. For this reason - and considering
that we could prefix the subject with m1 or m2 -
it seems like having separate lists right now is
a bad idea, unless people largely Cc such topics
to both
I have a static manifest that is used by the jar plugin;
in addition, I need to add a build timestamp (in a format
specific to our project) to the static manifest.
Is there a way to have the jar plugin take some properties
and append them to the specific manifest for the artifact?
Thanks,
Rk
Thanks, that did it.
Rk
x77309
On Sat, 15 Oct 2005, Brett Porter wrote:
Sorry about that. I remember what it was - set the property:
maven.download.meter=bootstrap
On 10/15/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
'maven -q' makes it worse: it suppresses other useful info,
It would be ideal if I could write my manifest as follows
and have the jar plugin fill in the property values:
Manifest-Version: 1.0
Name: com/bar/mypackage
Sealed: True
Specification-Title: My Project
Specification-Version: 1.0
Specification-Vendor: Bar Systems Inc.
'maven -q' makes it worse: it suppresses other useful info,
continues to display artifact download progress but without
listing the name of the artifact being downloaded:
$ cd acceptance; /vob/enm_jdk/maven1.0.2/bin/maven -q
Directory /vob/nm_dcm/acceptance/../maven/repository does not exist.
Env:
JDK 5.0
Maven 1.0.2
Multiproject plugin: 1.3.1
Context:
I have setup a multiproject dependency as follows:
(rh
(common)
(dcm-cs)
)
where both rh and dcm-cs extend ${basedir}common/project.xml
and rh depends on dcm-cs.
I have also
A minor(?) correction: the directory of dcm-cs
is named cs, while its artifact is named dcm-cs.
So the dir structure is as follows:
(rh
(common)
(cs) ;; produces dcm-cs.jar
)
Thanks,
Rk
x77309
On Thu, 15 Sep 2005, [EMAIL PROTECTED] wrote:
Env:
JDK 5.0
Maven 1.0.2
Hi,
Thanks for your clarification. One thing puzzles me:
You should be aware that when you run a goal on a Maven project, one of
the first things that is done is resolving/retrieving the dependencies.
So running 'rh:build' in the folder 'rh' will first try to resolve the
I am missing something fundmental. Even with this layout,
the goals in comp1/ do not trigger the attainment of
goals in comp1/:
$ cd comp1; maven
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
build:start:
13 matches
Mail list logo
