Fwd: How to include my application.xml and unversioned artifacts
-- Forwarded message --
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: 27 juil. 2005 12:46
Subject: Re: How to include my application.xml and unversioned artifacts
To: [EMAIL PROTECTED]
Hi
I think i've found the reason why my application.xml is not being included
in the ear. In the plugin .jelly there is this condition...
util:available file=${maven.ear.src}/META-INF/application.xml
Now in my ear module the META-INF folder is directly under the project
folder and i've not overriden the value of the property maven.ear.src..
Therefore it looks for the availability of the file in the location
'myEarProject/src/application' and not finding it there skips the following
instructions to copy it in the resulting ear.
Now the question is...
Is the condition correct?
Should it not be like.
util:available file=${maven.earappxml
Any comment welcom.
Thanks and Regards
Bhaskar Pathak
Software Engineer
Xansa India Ltd
Whilst this email has been checked for all known viruses, recipients
should undertake their own virus checking as Xansa will not accept any
liability whatsoever.
This email and any files transmitted with it are confidential and
protected by client privilege. It is solely for the use of the
intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.
Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
Xansa, Registered Office: 420 Thames Valley Park Drive,
Thames Valley Park, Reading, RG6 1PU, UK.
Registered in England No.1000954.
t +44 (0)8702 416181
w www.xansa.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: How to include my application.xml and unversioned artifacts
Bhaskar can you send your message directly to the list (I forward them
to) because your comment about util:available
file=${maven.earappxml test seems to be an issue.
Nicolas
-- Forwarded message --
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: 27 juil. 2005 13:00
Subject: Re: How to include my application.xml and unversioned artifacts
To: [EMAIL PROTECTED]
Hi,
This is in continuation to my last mail.
If i override the 'maven.ear.src' propert in the 'project.property' file
and make it ${basedir}, the build process will later on include everything
that is in the basedirectory in the resulting ear. This is not what is
needed in my case. Because the basediectory includes the 'project.xml' and
the 'project.properties' files as well.
Thanks and regards
Bhaskar pathak
Software Engineer
Xansa India Ltd.
Whilst this email has been checked for all known viruses, recipients
should undertake their own virus checking as Xansa will not accept any
liability whatsoever.
This email and any files transmitted with it are confidential and
protected by client privilege. It is solely for the use of the
intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.
Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
Xansa, Registered Office: 420 Thames Valley Park Drive,
Thames Valley Park, Reading, RG6 1PU, UK.
Registered in England No.1000954.
t +44 (0)8702 416181
w www.xansa.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How to include my application.xml and unversioned artifacts
being new to maven i've started by creating one 'project.xml' per module without inheritence. My project consists of one ejeb module, one web module and two java modules. after generating all the articats individually from command prompt i'm trying to build the ear. However i'm facing a couple of problems. I'm using maven1.0.2. My problems are... 1. I'm not able to include my own application.xml in the ear no matter what. Maven generates a message that though it is copying 'applcation .xml' in the ear folder but it will ignore this file when installing. 2. I've included the ibm specific file in the ear(include**/META-INF/**/include ). These files refer to the unversioned artifacts(war, ejb, jars). However the ear has this artifatcs in their versioned form. I reckon there are two ways to solve this 1. i find a way to include my own application.xml and the unversioned artifacts in the ear. Or 2. I generate the ibm specific file which refer to the versioned artifacts. However i dont know how to accomplish any of the two. Can any one help me out. Regards Bhaskar Pathak Software Enginner Xansa India Ltd. Whilst this email has been checked for all known viruses, recipients should undertake their own virus checking as Xansa will not accept any liability whatsoever. This email and any files transmitted with it are confidential and protected by client privilege. It is solely for the use of the intended recipient. Please delete it and notify the sender if you have received it in error. Unauthorised use is prohibited. Any opinions expressed in this email are those of the individual and not necessarily the organisation. Xansa, Registered Office: 420 Thames Valley Park Drive, Thames Valley Park, Reading, RG6 1PU, UK. Registered in England No.1000954. t +44 (0)8702 416181 w www.xansa.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to include my application.xml and unversioned artifacts
2005/7/26, [EMAIL PROTECTED] [EMAIL PROTECTED]: being new to maven i've started by creating one 'project.xml' per module without inheritence. My project consists of one ejeb module, one web module and two java modules. after generating all the articats individually from command prompt i'm trying to build the ear. However i'm facing a couple of problems. I'm using maven1.0.2. My problems are... 1. I'm not able to include my own application.xml in the ear no matter what. Maven generates a message that though it is copying 'applcation .xml' in the ear folder but it will ignore this file when installing. tell maven not to genarate it with the maven.ear.appxml.generate=false properties The application.xml location is indicate with maven.ear.appxml Nicolas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Unversioned artifacts
The war is created properly under the target directory.
It looks like the problem is with artifact:install. It insists to copy
the artifact (in this case war with the explicitly final name) to the
local repository with the version name.
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 22:06
To: Oren Berenson
Cc: Maven Users List
Subject: Re: Unversioned artifacts
If you build the war plugin from CVS (checkout maven-plugins/war
maven-plugins/plugin-parent, run maven plugin:install in war
directory), it has been fixed there.
On Tue, 12 Oct 2004 15:30:26 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Do i need to apply the patches of bug MPJAVA-8?
If so how do i apply patches?
Thanks
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 14:27
To: Oren Berenson
Cc: Maven Users List
Subject: Re: Unversioned artifacts
theoretically maven.war.final.name.
But that might be a bug that was being referred to before (jira is
playing up - can't look).
- Brett
On Tue, 12 Oct 2004 14:24:14 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Ok,
So how can i control the war name in the ear file? Instead of
xxx-1.0.war in the ear i need xxx.war.
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 14:13
To: Oren Berenson
Cc: Maven Users List
Subject: Re: Unversioned artifacts
sorry, I was thinking of ejb plugin (adding -client to the
artifact),
and it relates to deployment, not generation.
Files in ${maven.repo.local} or remote repositories will always have
versions. This is a Maven-controlled area, and Maven relies on
certain
things being there.
- Brett
On Tue, 12 Oct 2004 14:07:56 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Sorry, but i don't understand how to fix it.
Can you please provide some help.
Thanks
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:50
To: Maven Users List
Subject: Re: Unversioned artifacts
I think this is correct. Please read the resolution to
MPARTIFACT-35... a fix is needed in maven-ear-plugin.
On Tue, 12 Oct 2004 13:45:35 +0100,
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I think this is already filed as a bug - MPWAR-31 /
MPARTIFACT-35
James
-Original Message-
From: Oren Berenson [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:40
To: Maven Users List
Subject: RE: Unversioned artifacts
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under
${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs ,
${maven.repo.local}/${pom.name}/wars
and ${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED]
[EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven
automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong
Re: Unversioned artifacts
Let me reiterate what I said earlier:
Files in ${maven.repo.local} or remote repositories will always have
versions. This is a Maven-controlled area, and Maven relies on certain
things being there.
On Wed, 13 Oct 2004 10:10:21 +0200, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Contact me off the list if you need more help.I manged to get things
going with the unversioned artifact
Jeff
Registered Linux user number 366042
This e-mail is intended exclusively for the addressee.
If you are not the addressee you must not read, copy, use or disclose
the e-mail nor the content; please notify us immediately (by clicking Reply) and
delete this e-mail.
-
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]
Unversioned artifacts
Hi, We are trying to generate artifacts without maven automatically appending the version number to the end. For example, when building an EAR file, we use a pre-existing application.xml and simply direct it to be included in the META-INF of the ear. It is not built at build-time, so to speak. This configuration file refers to MyWebApp.war, which is an artifact produced by the maven build - except that maven is determined to append the version to the end of the war file. The reason we don't want maven to build the application.xml file is that WebSphere has already put a module id in the application.xml that is referred to in other WebSphere specific files. I am assuming that if this id is not retained in application.xml then the other parts break. I guess there are a number of possible solutions to my problem 1. My understanding of the module id is wrong, and everything would work just fine if maven generated the application.xml, and put version numbers on everything 2. I will need to rename the maven artifact after it is created to remove the version number (yuk!) 3. Maven has a neat way for me to tell it not to append the version number. Am I looking at this right? Has anyone got any suggestions for this one? Thanks, Colin Colin Hawkett Technical Architect Morpheus - eBusiness Solutions Morpheus Limited, Unit 6, The Courtyard, Eastern Road, Bracknell, Berkshire, RG12 2XB Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Tel: 01344 458188; Fax: 01344 458189 Web: http://www.morpheus.co.uk/ http://www.morpheus.co.uk This email and any files transmitted with it contain information that may be confidential or privileged, and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient any disclosure, copying, distribution or use of the information is prohibited. If you have received this email in error, please notify me by return email immediately. Any opinions expressed are those of the author, not of Morpheus Limited. This message has been checked for all known viruses by UUNET delivered through the MessageLabs Virus Control Centre.
Re: Unversioned artifacts
use maven.final.name to force maven to produce artifact with name like
${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED] [EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven automatically
appending the version number to the end. For example, when building an
EAR file, we use a pre-existing application.xml and simply direct it to
be included in the META-INF of the ear. It is not built at build-time,
so to speak. This configuration file refers to MyWebApp.war, which is
an artifact produced by the maven build - except that maven is
determined to append the version to the end of the war file.
The reason we don't want maven to build the application.xml file is that
WebSphere has already put a module id in the application.xml that is
referred to in other WebSphere specific files. I am assuming that if
this id is not retained in application.xml then the other parts break.
I guess there are a number of possible solutions to my problem
1. My understanding of the module id is wrong, and
everything would
work just fine if maven generated the application.xml, and put version
numbers on everything
2. I will need to rename the maven artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell it not to append the
version
number.
Am I looking at this right? Has anyone got any suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk/ http://www.morpheus.co.uk
This email and any files transmitted with it contain information that may
be
confidential or privileged, and are intended solely for the use of the
individual or entity to whom they are addressed. If you are not the
intended
recipient any disclosure, copying, distribution or use of the information
is
prohibited. If you have received this email in error, please notify me by
return email immediately. Any opinions expressed are those of the author,
not of Morpheus Limited.
This message has been checked for all known viruses by UUNET delivered
through the MessageLabs Virus Control Centre.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under
${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs ,
${maven.repo.local}/${pom.name}/wars and
${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED]
[EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven
automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell
it not to append the
version
number.
Am I looking at this right? Has anyone got any
suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern
Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk/
http://www.morpheus.co.uk
This email and any files transmitted with it contain
information that may
be
confidential or privileged, and are intended solely
for the use of the
individual or entity to whom they are addressed. If
you are not the
intended
recipient any disclosure, copying, distribution or
use of the information
is
prohibited. If you have received this email in
error, please notify me by
return email immediately. Any opinions expressed are
those of the author,
not of Morpheus Limited.
This message has been checked for all known viruses
by UUNET delivered
through the MessageLabs Virus Control Centre.
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Unversioned artifacts
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under
${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs ,
${maven.repo.local}/${pom.name}/wars and
${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED]
[EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven
automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell
it not to append the
version
number.
Am I looking at this right? Has anyone got any
suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern
Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk/
http://www.morpheus.co.uk
This email and any files transmitted with it contain
information that may
be
confidential or privileged, and are intended solely
for the use of the
individual or entity to whom they are addressed. If
you are not the
intended
recipient any disclosure, copying, distribution or
use of the information
is
prohibited. If you have received this email in
error, please notify me by
return email immediately. Any opinions expressed are
those of the author,
not of Morpheus Limited.
This message has been checked for all known viruses
by UUNET delivered
through the MessageLabs Virus Control Centre.
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This email and any files transmitted with it contain information that may be
confidential or privileged, and are intended solely for the use of the
individual or entity to whom they are addressed. If you are not the intended
recipient any disclosure, copying, distribution or use of the information is
prohibited. If you have received this email in error, please notify me by
return email immediately. Any opinions expressed are those of the author,
not of Morpheus Limited.
This message has been checked for all known viruses by UUNET delivered
through the MessageLabs Virus Control Centre.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
RE: Unversioned artifacts
Maybe one of the maven gurus could give us some light
here...Please :)
jeff mutonho
--- Oren Berenson [EMAIL PROTECTED]
wrote:
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under
${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs ,
${maven.repo.local}/${pom.name}/wars and
${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as
well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED]
[EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without
maven
automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml
and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I
am
assuming that if
this id is not retained in application.xml then
the
other parts break.
I guess there are a number of possible solutions
to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to
tell
it not to append the
version
number.
Am I looking at this right? Has anyone got any
suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern
Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk/
http://www.morpheus.co.uk
This email and any files transmitted with it
contain
information that may
be
confidential or privileged, and are intended
solely
for the use of the
individual or entity to whom they are addressed.
If
you are not the
intended
recipient any disclosure, copying, distribution or
use of the information
is
prohibited. If you have received this email in
error, please notify me by
return email immediately. Any opinions expressed
are
those of the author,
not of Morpheus Limited.
This message has been checked for all known
viruses
by UUNET delivered
through the MessageLabs Virus Control Centre.
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
=== message truncated ===
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unversioned artifacts
just a wild suggestion, I haven't tried..
1. use the final name trick to produce the non-versioned artifact.
2. if jar:install, ejb:install etc copy the versioned artifact, use a
custom goal to copy the non-versioned one (you'll have to write that one
in maven.xml)
3. in your dependency in the pom file use the jar element to point to
the non-versioned artifact
this could work, no guarantees though..
Milos Kleint
Oren Berenson wrote:
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under
${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs ,
${maven.repo.local}/${pom.name}/wars and
${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED]
[EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven
automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell
it not to append the
version
number.
Am I looking at this right? Has anyone got any
suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern
Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk/
http://www.morpheus.co.uk
This email and any files transmitted with it contain
information that may
be
confidential or privileged, and are intended solely
for the use of the
individual or entity to whom they are addressed. If
you are not the
intended
recipient any disclosure, copying, distribution or
use of the information
is
prohibited. If you have received this email in
error, please notify me by
return email immediately. Any opinions expressed are
those of the author,
not of Morpheus Limited.
This message has been checked for all known viruses
by UUNET delivered
through the MessageLabs Virus Control Centre.
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This email and any files transmitted with it contain information that may be
confidential or privileged, and are intended solely for the use of the
individual or entity to whom they are addressed. If you are not the intended
recipient any disclosure, copying, distribution or use of the information is
prohibited. If you have received this email in error, please notify me by
return email immediately. Any opinions expressed are those of the author,
not of Morpheus Limited.
This message has been checked for all known viruses by UUNET delivered
through
RE: Unversioned artifacts
I think this is already filed as a bug - MPWAR-31 / MPARTIFACT-35
James
-Original Message-
From: Oren Berenson [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:40
To: Maven Users List
Subject: RE: Unversioned artifacts
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under ${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs , ${maven.repo.local}/${pom.name}/wars
and ${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED] [EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell
it not to append the
version
number.
Am I looking at this right? Has anyone got any
suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern
Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk/
http://www.morpheus.co.uk
This email and any files transmitted with it contain information that
may be
confidential or privileged, and are intended solely
for the use of the
individual or entity to whom they are addressed. If
you are not the
intended
recipient any disclosure, copying, distribution or
use of the information
is
prohibited. If you have received this email in
error, please notify me by
return email immediately. Any opinions expressed are
those of the author,
not of Morpheus Limited.
This message has been checked for all known viruses
by UUNET delivered
through the MessageLabs Virus Control Centre.
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This email and any files transmitted with it contain information that may be
confidential or privileged, and are intended solely for the use of the
individual or entity to whom they are addressed. If you are not the intended
recipient any disclosure, copying, distribution or use of the information is
prohibited. If you have received this email in error, please notify me by
return email immediately. Any opinions expressed are those of the author,
not of Morpheus Limited.
This message has been checked for all known viruses by UUNET delivered
through the MessageLabs Virus Control Centre
Re: Unversioned artifacts
I think this is correct. Please read the resolution to
MPARTIFACT-35... a fix is needed in maven-ear-plugin.
On Tue, 12 Oct 2004 13:45:35 +0100, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I think this is already filed as a bug - MPWAR-31 / MPARTIFACT-35
James
-Original Message-
From: Oren Berenson [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:40
To: Maven Users List
Subject: RE: Unversioned artifacts
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under ${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs , ${maven.repo.local}/${pom.name}/wars
and ${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED] [EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell
it not to append the
version
number.
Am I looking at this right? Has anyone got any
suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern
Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk/
http://www.morpheus.co.uk
This email and any files transmitted with it contain information that
may be
confidential or privileged, and are intended solely
for the use of the
individual or entity to whom they are addressed. If
you are not the
intended
recipient any disclosure, copying, distribution or
use of the information
is
prohibited. If you have received this email in
error, please notify me by
return email immediately. Any opinions expressed are
those of the author,
not of Morpheus Limited.
This message has been checked for all known viruses
by UUNET delivered
through the MessageLabs Virus Control Centre.
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This email and any files transmitted with it contain information that may be
confidential or privileged, and are intended solely for the use of the
individual or entity to whom they are addressed. If you are not the intended
recipient any disclosure, copying, distribution or use
RE: Unversioned artifacts
Sorry, but i don't understand how to fix it.
Can you please provide some help.
Thanks
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:50
To: Maven Users List
Subject: Re: Unversioned artifacts
I think this is correct. Please read the resolution to
MPARTIFACT-35... a fix is needed in maven-ear-plugin.
On Tue, 12 Oct 2004 13:45:35 +0100, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I think this is already filed as a bug - MPWAR-31 / MPARTIFACT-35
James
-Original Message-
From: Oren Berenson [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:40
To: Maven Users List
Subject: RE: Unversioned artifacts
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under ${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs ,
${maven.repo.local}/${pom.name}/wars
and ${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED] [EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell
it not to append the
version
number.
Am I looking at this right? Has anyone got any
suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern
Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk/
http://www.morpheus.co.uk
This email and any files transmitted with it contain information
that
may be
confidential or privileged, and are intended solely
for the use of the
individual or entity to whom they are addressed. If
you are not the
intended
recipient any disclosure, copying, distribution or
use of the information
is
prohibited. If you have received this email in
error, please notify me by
return email immediately. Any opinions expressed are
those of the author,
not of Morpheus Limited.
This message has been checked for all known viruses
by UUNET delivered
through the MessageLabs Virus Control Centre.
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This email and any files transmitted
Re: Unversioned artifacts
sorry, I was thinking of ejb plugin (adding -client to the artifact),
and it relates to deployment, not generation.
Files in ${maven.repo.local} or remote repositories will always have
versions. This is a Maven-controlled area, and Maven relies on certain
things being there.
- Brett
On Tue, 12 Oct 2004 14:07:56 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Sorry, but i don't understand how to fix it.
Can you please provide some help.
Thanks
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:50
To: Maven Users List
Subject: Re: Unversioned artifacts
I think this is correct. Please read the resolution to
MPARTIFACT-35... a fix is needed in maven-ear-plugin.
On Tue, 12 Oct 2004 13:45:35 +0100, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I think this is already filed as a bug - MPWAR-31 / MPARTIFACT-35
James
-Original Message-
From: Oren Berenson [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:40
To: Maven Users List
Subject: RE: Unversioned artifacts
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under ${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs ,
${maven.repo.local}/${pom.name}/wars
and ${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED] [EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell
it not to append the
version
number.
Am I looking at this right? Has anyone got any
suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern
Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk/
http://www.morpheus.co.uk
This email and any files transmitted with it contain information
that
may be
confidential or privileged, and are intended solely
for the use of the
individual or entity to whom they are addressed. If
you are not the
intended
recipient any disclosure, copying, distribution or
use of the information
is
prohibited. If you have received this email in
error, please notify me by
return email immediately. Any opinions expressed are
those of the author,
not of Morpheus Limited.
This message has been checked for all known viruses
by UUNET delivered
through the MessageLabs Virus Control Centre
RE: Unversioned artifacts
Ok,
So how can i control the war name in the ear file? Instead of
xxx-1.0.war in the ear i need xxx.war.
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 14:13
To: Oren Berenson
Cc: Maven Users List
Subject: Re: Unversioned artifacts
sorry, I was thinking of ejb plugin (adding -client to the artifact),
and it relates to deployment, not generation.
Files in ${maven.repo.local} or remote repositories will always have
versions. This is a Maven-controlled area, and Maven relies on certain
things being there.
- Brett
On Tue, 12 Oct 2004 14:07:56 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Sorry, but i don't understand how to fix it.
Can you please provide some help.
Thanks
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:50
To: Maven Users List
Subject: Re: Unversioned artifacts
I think this is correct. Please read the resolution to
MPARTIFACT-35... a fix is needed in maven-ear-plugin.
On Tue, 12 Oct 2004 13:45:35 +0100, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I think this is already filed as a bug - MPWAR-31 / MPARTIFACT-35
James
-Original Message-
From: Oren Berenson [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:40
To: Maven Users List
Subject: RE: Unversioned artifacts
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under ${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs ,
${maven.repo.local}/${pom.name}/wars
and ${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED] [EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell
it not to append the
version
number.
Am I looking at this right? Has anyone got any
suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern
Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk/
http://www.morpheus.co.uk
This email and any files transmitted with it contain information
that
may be
confidential or privileged, and are intended solely
for the use of the
individual or entity to whom they are addressed. If
you are not the
intended
recipient any disclosure, copying, distribution or
use of the information
is
prohibited. If you have received this email in
error, please notify me by
return email immediately. Any opinions expressed are
those of the author,
not of Morpheus Limited
Re: Unversioned artifacts
theoretically maven.war.final.name.
But that might be a bug that was being referred to before (jira is
playing up - can't look).
- Brett
On Tue, 12 Oct 2004 14:24:14 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Ok,
So how can i control the war name in the ear file? Instead of
xxx-1.0.war in the ear i need xxx.war.
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 14:13
To: Oren Berenson
Cc: Maven Users List
Subject: Re: Unversioned artifacts
sorry, I was thinking of ejb plugin (adding -client to the artifact),
and it relates to deployment, not generation.
Files in ${maven.repo.local} or remote repositories will always have
versions. This is a Maven-controlled area, and Maven relies on certain
things being there.
- Brett
On Tue, 12 Oct 2004 14:07:56 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Sorry, but i don't understand how to fix it.
Can you please provide some help.
Thanks
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:50
To: Maven Users List
Subject: Re: Unversioned artifacts
I think this is correct. Please read the resolution to
MPARTIFACT-35... a fix is needed in maven-ear-plugin.
On Tue, 12 Oct 2004 13:45:35 +0100, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I think this is already filed as a bug - MPWAR-31 / MPARTIFACT-35
James
-Original Message-
From: Oren Berenson [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:40
To: Maven Users List
Subject: RE: Unversioned artifacts
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under ${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs ,
${maven.repo.local}/${pom.name}/wars
and ${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED] [EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell
it not to append the
version
number.
Am I looking at this right? Has anyone got any
suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern
Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk/
http://www.morpheus.co.uk
This email and any files transmitted with it contain information
that
may be
confidential or privileged
RE: Unversioned artifacts
Do i need to apply the patches of bug MPJAVA-8?
If so how do i apply patches?
Thanks
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 14:27
To: Oren Berenson
Cc: Maven Users List
Subject: Re: Unversioned artifacts
theoretically maven.war.final.name.
But that might be a bug that was being referred to before (jira is
playing up - can't look).
- Brett
On Tue, 12 Oct 2004 14:24:14 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Ok,
So how can i control the war name in the ear file? Instead of
xxx-1.0.war in the ear i need xxx.war.
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 14:13
To: Oren Berenson
Cc: Maven Users List
Subject: Re: Unversioned artifacts
sorry, I was thinking of ejb plugin (adding -client to the artifact),
and it relates to deployment, not generation.
Files in ${maven.repo.local} or remote repositories will always have
versions. This is a Maven-controlled area, and Maven relies on certain
things being there.
- Brett
On Tue, 12 Oct 2004 14:07:56 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Sorry, but i don't understand how to fix it.
Can you please provide some help.
Thanks
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:50
To: Maven Users List
Subject: Re: Unversioned artifacts
I think this is correct. Please read the resolution to
MPARTIFACT-35... a fix is needed in maven-ear-plugin.
On Tue, 12 Oct 2004 13:45:35 +0100, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I think this is already filed as a bug - MPWAR-31 / MPARTIFACT-35
James
-Original Message-
From: Oren Berenson [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:40
To: Maven Users List
Subject: RE: Unversioned artifacts
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under
${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs ,
${maven.repo.local}/${pom.name}/wars
and ${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED]
[EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven
automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell
it not to append the
version
number.
Am I looking at this right? Has anyone got any
suggestions for this
one? Thanks,
Colin
Colin Hawkett
Technical Architect
Morpheus - eBusiness Solutions
Morpheus Limited, Unit 6, The Courtyard, Eastern
Road, Bracknell,
Berkshire, RG12 2XB
Email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Tel: 01344 458188; Fax: 01344 458189
Web: http://www.morpheus.co.uk
Re: Unversioned artifacts
If you build the war plugin from CVS (checkout maven-plugins/war
maven-plugins/plugin-parent, run maven plugin:install in war
directory), it has been fixed there.
On Tue, 12 Oct 2004 15:30:26 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Do i need to apply the patches of bug MPJAVA-8?
If so how do i apply patches?
Thanks
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 14:27
To: Oren Berenson
Cc: Maven Users List
Subject: Re: Unversioned artifacts
theoretically maven.war.final.name.
But that might be a bug that was being referred to before (jira is
playing up - can't look).
- Brett
On Tue, 12 Oct 2004 14:24:14 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Ok,
So how can i control the war name in the ear file? Instead of
xxx-1.0.war in the ear i need xxx.war.
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 14:13
To: Oren Berenson
Cc: Maven Users List
Subject: Re: Unversioned artifacts
sorry, I was thinking of ejb plugin (adding -client to the artifact),
and it relates to deployment, not generation.
Files in ${maven.repo.local} or remote repositories will always have
versions. This is a Maven-controlled area, and Maven relies on certain
things being there.
- Brett
On Tue, 12 Oct 2004 14:07:56 +0100, Oren Berenson
[EMAIL PROTECTED] wrote:
Sorry, but i don't understand how to fix it.
Can you please provide some help.
Thanks
Oren
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:50
To: Maven Users List
Subject: Re: Unversioned artifacts
I think this is correct. Please read the resolution to
MPARTIFACT-35... a fix is needed in maven-ear-plugin.
On Tue, 12 Oct 2004 13:45:35 +0100, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I think this is already filed as a bug - MPWAR-31 / MPARTIFACT-35
James
-Original Message-
From: Oren Berenson [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:40
To: Maven Users List
Subject: RE: Unversioned artifacts
True. I am battling with it now.
Oren
-Original Message-
From: jeff mutonho [mailto:[EMAIL PROTECTED]
Sent: 12 October 2004 13:37
To: Maven Users List
Subject: Re: Unversioned artifacts
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
That seems to only fix it for the jar,ejb , war or
ear files created under the targets directory.The
jar,war and ear created under
${maven.repo.local}/${pom.name}/jars/
,${maven.repo.local}/${pom.name}/ejbs ,
${maven.repo.local}/${pom.name}/wars
and ${maven.repo.local}/${pom.name}/ears
will still have version numbers
I've been battling with the same problem , as well...
jeff mutonho
Registered Linux user number 366042
--- [EMAIL PROTECTED] wrote:
use maven.final.name to force maven to produce
artifact with name like ${maven.final.name}.ear
Nicolas,
Colin Hawkett [EMAIL PROTECTED]
12/10/2004 13:08
Veuillez répondre à Maven Users List
Pour : [EMAIL PROTECTED]
[EMAIL PROTECTED]
cc :
Objet : Unversioned artifacts
Hi,
We are trying to generate artifacts without maven
automatically
appending the version number to the end. For
example, when building an
EAR file, we use a pre-existing application.xml and
simply direct it to
be included in the META-INF of the ear. It is not
built at build-time,
so to speak. This configuration file refers to
MyWebApp.war, which is
an artifact produced by the maven build - except
that maven is
determined to append the version to the end of the
war file.
The reason we don't want maven to build the
application.xml file is that
WebSphere has already put a module id in the
application.xml that is
referred to in other WebSphere specific files. I am
assuming that if
this id is not retained in application.xml then the
other parts break.
I guess there are a number of possible solutions to
my problem
1. My understanding of the module id
is wrong, and
everything would
work just fine if maven generated the
application.xml, and put version
numbers on everything
2. I will need to rename the maven
artifact after it is
created to
remove the version number (yuk!)
3. Maven has a neat way for me to tell
it not to append the
version
number.
Am I looking at this right? Has anyone
