On Tue, 19 Oct 2004 22:32:35 +1000, Brett Porter [EMAIL PROTECTED] wrote:
[snip]
This is right - you need to know what the single build artifact is, and
that should be {maven.final.name}.jar
Did you really mean this? Having a jar as the only artifact is very restrictive.
--
On Wed, 2004-10-20 at 07:04, Dion Gillard wrote:
Did you really mean this? Having a jar as the only artifact is very restrictive.
Exactly. I guess that's the reason the maven.war.final.name was created
at first instance.
-
To
Yes, I meant it in terms of there being one main output. There may be
others, but they are offshoots of the original. You can read back
through this thread, the previous discussions, and the discussions on
m2-dev (I think eyebrowse is still the only one archiving this
unfortunately) for more
I'll start by rounding up thoughts, with specific answer below to the
last email.
Let me sum up where I think we're at here:
- artifact separation. We've talked about this on the maven and m2-dev
lists a lot in the last 6 months and thinking through all the issues
concluded that one project =
Message meant for the list, Brett your reply-to points to you :-)
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on
: Is maven.final.name deprecated?
From:
Jason van Zyl [EMAIL PROTECTED]
Date:
19 Oct 2004 09:24:03 -0400
To:
[EMAIL PROTECTED]
To:
[EMAIL PROTECTED]
On Tue, 2004-10-19 at 08:32, Brett Porter wrote:
I'll start by rounding up thoughts, with specific answer below to the
last email.
Let me sum up where I think
Hi all,
I've started fixing MPJAVA-8, and have a question: is the propertie
maven.final.name still valid or is it deprecated and I should just use
pom.artifactId instead? And if it is still valid, where is it defined?
I'm asking because I don't want to fix this bug leaving some plugins
On Mon, 2004-10-18 at 13:13, Felipe Leme wrote:
Hi all,
I've started fixing MPJAVA-8, and have a question: is the propertie
maven.final.name still valid or is it deprecated and I should just use
pom.artifactId instead? And if it is still valid, where is it defined?
It's still valid, it
Hi Jason,
On 18 Oct 2004 13:51:40 -0400, Jason van Zyl [EMAIL PROTECTED] wrote:
It's still valid, it gives the user the only way to change the resultant
name of the generated artifact. It is highly recommended not to change
this but people still need to do it for some reason.
Ok, I will use
On Mon, 2004-10-18 at 14:20, Felipe Leme wrote:
Hi Jason,
I've asked the same question (see
http://jira.codehaus.org/browse/MPJAVA-8#action_23633), but nobody answered .
So, I'd say we are 2x0 for changing these 2 properties and if nobody gives a good
reason for keeping them as is, I will
I'm asking because I don't want to fix this bug leaving some plugins
inconsistent. For instance, maven-war sets:
maven.war.final.name = ${pom.artifactId}.war
Why on earth does that not have the version in it?
This is something which has a very long history.
I change in many months ago
I agree with Jason - if you really need the WAR withouth the version, than just
overwrite the property in your project.
Besides, the war is deployed/installed with the version in the name anyway, so the
plugin is already inconsistent.
What about a [VOTE] message to decide the final answer?
--
Felipe Leme wrote:
Hi Jason,
On 18 Oct 2004 13:51:40 -0400, Jason van Zyl [EMAIL PROTECTED] wrote:
It's still valid, it gives the user the only way to change the resultant
name of the generated artifact. It is highly recommended not to change
this but people still need to do it for some
It's for this reason that it may stay as it is for now. The repository
is king, and it will always have a version when it gets there.
Generating it in target without it is not ideal, but is convenient and
backwards compatible. I don't see any issue with it.
That said, for consistency - how
On Tue, 19 Oct 2004 06:47:53 +1000, Brett Porter [EMAIL PROTECTED] wrote:
It's for this reason that it may stay as it is for now. The repository
What do you mean stay as it is? Does it means no plugin should have the
.final.name (relying only on maven.final.name) or leaving it in the
What do you mean stay as it is? Does it means no plugin should have the
.final.name (relying only on maven.final.name) or leaving it in the
current inconsistent way (where some plugins have the property but some
others don't)?. Or are you just talking about the specific
On Tue, 2004-10-19 at 02:53, Brett Porter wrote:
Context docRoot=/home/bporter/cvs/.../target/foo.war
Convenient :)
As I said, you need to update the war (ok, you could usen maven console
for that, but it's not the same). What about:
Context docRoot=/home/bporter/cvs/.../${maven.war.src
(+
17 matches
Mail list logo
