nabble.
> com/javafx-maven-plugin-seems-to-ignore-finalName-parameter-tp5907231.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven
-plugin-seems-to-ignore-finalName-parameter-tp5907231.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h
Folks,
Environment: Maven 3.1.1, JDK 1.7.0_45
I'm having some challenges with the Maven WAR plugin (2.4),
archiveClasses, and finalName. In addition, I am using the Freemarker
preprocessor plugin (FMPP plugin) to generate some output.
Here's what I've tried (without the FMPP plugin).
1
The only way I've found to accomplish this is to make a module with the
resources / source code and have the parent depend on this module. That
certainly feels like a hack to get around a packaging problem.
To me, this is not a hack. Maven does not really want you to have
source code in WAR
We have a POM, where the build specifies a final name like this:
finalNameorg.apache.uima.textmarker.engine_${parsedVersion.osgiVersion}/finalName
We use the maven-build-helper plugin to set the variable to be the same as the
version, except with a period before the SNAPSHOT qualifier
Please read this:
http://stackoverflow.com/questions/14725197/reading-properties-file-from-pom-file-in-maven/14727072#14727072
You will conclude that the only solution is to make the finalName a
configuration parameter of the mojo so that the recursive property
evaluation code can compute
into the property variable in
the finalname. So, if you look into /target, it's got the wrong name.
But, when the install plugin installs, it
(a) ignores the incorrectly named ...pom in the /target, and instead, copies
the original pom to the install spot. You can see that in the run output for
the install
, and then signs that, without substituting into the property
variable in
the finalname. So, if you look into /target, it's got the wrong name.
But, when the install plugin installs, it
(a) ignores the incorrectly named ...pom in the /target, and instead,
copies
the original pom
I all,
Is there a way to programmatically define the finalName build property?
Regards,
Romain
I have a project which specifies in the build a finalName which has 2
substitutable parts:
finalName${project.artifactId}_${parsedVersion.osgiVersion}/finalName
where the parsedVersion.osgiVersion property is set by the
build-helper-maven-plugin, in the first life-cycle-phase.
This property
Wed, 12 Oct 2011 17:42:59 -0700, /Manfred Moser/:
11-10-12 05:30 PM, Yuen-Chi Lian wrote:
parent
groupIdy/groupId
artifactIdx/artifactId
versionv/version
relativePath../parent/relativePath
Dont use relative path
I want to configure the 'finalName' for a parent module and all its
child modules as:
build
finalName${artifactId}/fileName
/build
Is there a way to configure this as a default pattern in the parent
and avoid repeating it in the 'build' section for all child modules
Yes. Have you tried?
$ cat parent/pom.xml | grep finalName
finalName${project.artifactId}-${project.version}-b${buildNumber}/finalName
In the child:
parent
groupIdy/groupId
artifactIdx/artifactId
versionv/version
Dont use relative path ...
11-10-12 05:30 PM, Yuen-Chi Lian wrote:
Yes. Have you tried?
$ cat parent/pom.xml | grep finalName
finalName${project.artifactId}-${project.version}-b${buildNumber}/finalName
In the child:
parent
groupIdy/groupId
Thu, 13 Oct 2011 08:30:49 +0800, /Yuen-Chi Lian/:
Yes. Have you tried?
$ cat parent/pom.xml | grep finalName
finalName${project.artifactId}-${project.version}-b${buildNumber}/finalName
Ah, yes - thank you. I've already tried it before but for some
reason I had determined it doesn't work
Hey,
I am trying to get a jar to be uploaded in the maven repository (local as
well as our online repo) under a different name than its default
${project.build.finalName}. I tried changing the finalName under the
build tag as well as under the configuration of the maven-jar-plugin
as
well as our online repo) under a different name than its default
${project.build.finalName}. I tried changing the finalName under the
build tag as well as under the configuration of the maven-jar-plugin.
These attempts did change the name of the jar in my project/target
directory, however
repo) under a different name than its default
${project.build.finalName}. I tried changing the finalName under the
build tag as well as under the configuration of the maven-jar-plugin.
These attempts did change the name of the jar in my project/target
directory, however when it's being uploaded
, fhomasp
thomas.peet...@realdolmen.comwrote:
Hey,
I am trying to get a jar to be uploaded in the maven repository (local
as
well as our online repo) under a different name than its default
${project.build.finalName}. I tried changing the finalName under the
build tag as well as under
, but that's
something completely different and you did this already with the
finalName option.
Changing the internal data storage of maven (the repository) is a bad idea
and therefore not easy to achieve!
hth,
- martin
signature.asc
Description: This is a digitally signed message part.
Well that's out of the question. But ok, at least I'll be able to tell them
why it is the way it is ^^
Thanks
--
View this message in context:
http://maven.40175.n5.nabble.com/Jar-finalName-to-m2-repository-tp2639096p2639309.html
Sent from the Maven - Users mailing list archive at Nabble.com
change the name of the JAR in the local or remote repository with
the assembly plugin? I doubt this!
You can change the name of the JAR in your targt folder, but that's
something completely different and you did this already with the
finalName option.
Changing the internal data storage
Hi again!
On Wednesday 18 August 2010 fhomasp wrote:
However it would be nice to be able to actually do this using the jar
plugin. I know my client is going to want this library to be called
edp-version.jar.
Eventually you could find some solution with the maven-dependency-plugins'
goal
-dependencies in combination with the antrun-plugin.
However, it seems you are doing something strange here, which is likely to
cause more problems later on.
- martin
--
View this message in context:
http://maven.40175.n5.nabble.com/Jar-finalName-to-m2-repository-tp2639096p2639374.html
In my build I set the build final name for some things using
finalNamea.b.c_${parsedVersion.osgiVersion}/finalName
where ${parsedVersion.osgiVersion} is a parameter value set by executing the
maven-build-helper plugin which is the first plugin run when the build executes
(I checked
I know there is already a lot of discussion around the topic of artifacts
not using finalName when they are installed into a repository (remote or
local), but is there a way to enforce that the dependencies, when packaged
into the using project, are packaged with their finalNames?
example
://maven.apache.org/plugins/maven-assembly-plugin/component.html).
Kalle
On Tue, Jul 20, 2010 at 1:26 PM, Shan Syed shan...@gmail.com wrote:
I know there is already a lot of discussion around the topic of artifacts
not using finalName when they are installed into a repository (remote or
local
maven to manage this: I have a POM for each delivery, which
just has the dependencies listed, and an assembly descriptor that ZIPs them
all conveniently, for deployment/DL to various environments.
Each developer has specified a finalName for their WAR, but there is no
convention, some require just
, for deployment/DL to various environments.
Each developer has specified a finalName for their WAR, but there is no
convention, some require just the version info lopped off, some need a
totally different name from their artifact, etc.. there is no reliable way
to calculate the desired finalName
PM, Timothy Mcginnis
tmcgi...@aessuccess.orgwrote:
What is the purpose of the finalName tag in the Ear plugin?
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
==
This message contains privileged and confidential
What is the purpose of the finalName tag in the Ear plugin?
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
==
This message contains privileged and confidential information intended for the
above addressees only
Hello,
Trying to use buildnumber and tomcat:deploy. In my parent-pom, I've
defined buildnumber. In my application-webapp (war), I define the tomcat
deploy configuration. However,
when tomcat deploy tries to install it, for some reason the
buildnumber variable comes across as null.
[INFO]
Hi Kent,
Kent Närling wrote:
What IS really the purpose of finalName?
It is used to give the resulting artifact a different name locally in your
target directory.
Apparently, the install plugin ignores the artifact name when
deploying it to the repository anyway??
Definitely. The filename
finalNamemycontextpath/finalName
and use e.g. the jetty plugin to start your webserver in 1 go:
$ mvn package jetty:run
Then your finalName is being used for 'deployment' and you may access your
webapp via
http://localhost:8080/mycontextpath/
which may then automatically be regression tested via
2008/10/24 Mark Struberg [EMAIL PROTECTED]:
To give Kent an example:
Consider a pom for building a WAR.
If you set
finalNamemycontextpath/finalName
and use e.g. the jetty plugin to start your webserver in 1 go:
$ mvn package jetty:run
Then your finalName is being used for 'deployment
plugin or from the tomcat or cargo plugin i've
worked with. Anyway, it's good to know that this works now.)
LieGrue,
strub
--- Mark Hobson [EMAIL PROTECTED] schrieb am Fr, 24.10.2008:
Von: Mark Hobson [EMAIL PROTECTED]
Betreff: Re: What is the purpose of finalName? really?
An: Maven Users List
2008/10/24 Mark Struberg [EMAIL PROTECTED]:
Sorry Mark, should have mentioned that I usually use the following config
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
configuration
2008/10/24 Jörg Schaible [EMAIL PROTECTED]
Hi Kent,
Kent Närling wrote:
What IS really the purpose of finalName?
It is used to give the resulting artifact a different name locally in your
target directory.
only locally? a bit limited usefulness, but ok if that is the defined
purpose
You may either use the local file directly for a hot
deployment on your developer machine or you can use
additional plugins to process the file further.
To give Kent an example:
Consider a pom for building a WAR.
If you set
finalNamemycontextpath/finalName
and use e.g. the jetty
On Fri, Oct 24, 2008 at 1:56 PM, Kent Närling [EMAIL PROTECTED] wrote:
Ok, but I was kind of hoping that we could use the maven repository as a
product download repository as well, which would have been nice?
(anyone else see the logic in this?)
...
- updating a project site with product
What IS really the purpose of finalName?
Apparently, the install plugin ignores the artifact name when deploying it
to the repository anyway??
We would like to have a version-less filename on the artifact in the
repository (the version is in the path anyway), is this possible?
If not, what
]
What IS really the purpose of finalName?
Apparently, the install plugin ignores the artifact name when deploying it
to the repository anyway??
We would like to have a version-less filename on the artifact in the
repository (the version is in the path anyway), is this possible
:\Documents and
Settings\kent\.m2\repository\com\seamless\ers\requestparser-servlet\1.0rc3-SNAPSHOT\requestparser-servlet-1.0rc3-SNAPSHOT.war
ie, it seems the install plugin simply ignores the finalName tag?!?
I mean, obviously it is nice to have a war file have a fixed name since it
usually dictates
:\Documents and
Settings\kent\.m2\repository\com\seamless\ers\requestparser-servlet\1.0rc3-SNAPSHOT\requestparser-servlet-1.0rc3-SNAPSHOT.war
ie, it seems the install plugin simply ignores the finalName tag?!?
I mean, obviously it is nice to have a war file have a fixed name since it
usually
\main\requestparser\requestparser-servlet\target\requestparser-servletxx.war
to C:\Documents and
Settings\kent\.m2\repository\com\seamless\ers\requestparser-servlet\1.0rc3-SNAPSHOT\requestparser-servlet-1.0rc3-SNAPSHOT.war
ie, it seems the install plugin simply ignores the finalName tag?!?
I
structure on that webserver...which leads me to my real point:
The intention with all of this was that Maven would index/name artifacts the
way it needed to in order to retrieve them when they're in the repository.
The finalName configurations are preserved in the POM, which is deployed
alongside
Hi,
I've noticed that the finalName configuration option for an assembly is
ignored when you install or deploy your project. Is this intended behavior?
I have a project named openjpa-project which contains the a source and
binary assembly which packages various OpenJPA sub-projects. We'd like
On 4/11/07, Michael Dick [EMAIL PROTECTED] wrote:
Hi,
I've noticed that the finalName configuration option for an assembly is
ignored when you install or deploy your project. Is this intended behavior?
I have a project named openjpa-project which contains the a source and
binary assembly which
Thank you for the explanation,
Wouldn't it be possible to store the finalName in the
maven-metadata.xmlfile or another xml file in the repository? We
already have a unique path in
the repository ${groupId}/${artifactId}/${version}. I'm not interested in
changing the path, just the name
On Wed, Apr 11, 2007 at 01:27:42PM -0500, Michael Dick spake thus:
*snip*
It seems that the finalName *could* be added in an xml file in the
repository. Whether it *should* be added is another issue.
FTR I'm just curious whether this is a possibility, or if anyone else thinks
it would
On 4/11/07, Alan D. Salewski [EMAIL PROTECTED] wrote:
On Wed, Apr 11, 2007 at 01:27:42PM -0500, Michael Dick spake thus:
*snip*
It seems that the finalName *could* be added in an xml file in the
repository. Whether it *should* be added is another issue.
I did not think too much about
On Wed, Apr 11, 2007 at 09:45:17PM +0200, Heinrich Nirschl spake thus:
*snip*
On 4/11/07, Alan D. Salewski [EMAIL PROTECTED] wrote:
Maybe we need an attribute for 'finalName' that indicates yes I know
this name will not be accessible by maven once installed or deployed;
when set maven would
11, 2007 at 09:45:17PM +0200, Heinrich Nirschl spake thus:
*snip*
On 4/11/07, Alan D. Salewski [EMAIL PROTECTED] wrote:
Maybe we need an attribute for 'finalName' that indicates yes I know
this name will not be accessible by maven once installed or deployed;
when set maven would deploy the file
Hi,
I pasted below part of my pom file. I'd like the EJB jar file to be called
myEjbJar.jar.
Instead the file is named {artifactId}-{version}.jar.
Is there a way to make it work? I thought finalName inside build should
override the default jar file name.
Any help on the subject would be greatly
On 10/30/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Okay, so the docs for finalName differ on
http://maven.apache.org/maven-v4_0_0.xsd
and
http://maven.apache.org/ref/2.0.4/maven-model/maven.html
My guess is that the xsd needs to be re-generated, since the 2.0.4
docs describe the current
The 4.0.0 POM schema indicates that the finalName includes the extension [1],
but when running package, the default packaging type extension is
automatically appended. For example, if finalNametest.zip/finalName is
used for a jar project, the resulting artifact is test.zip.jar
On 10/30/06, Shelley Lock [EMAIL PROTECTED] wrote:
The 4.0.0 POM schema indicates that the finalName includes the extension [1], but when running
package, the default packaging type extension is automatically appended. For example, if
finalNametest.zip/finalName is used for a jar project
On 10/30/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Shelley, the xsd for Maven 2.0.4 differs from the comments that you
pasted on MNG-1676. What version did you copy that from?
Must read footnotes. :)
Okay, so the docs for finalName differ on
http://maven.apache.org/maven-v4_0_0.xsd
Doug,
thanks for your reply.
Yes that's true, Maven has no knowledge of projet A. But it knows that A
is a dependency. So it should include A as a reference in module B using
the finalName: is it completly non sens?
Moreover I found dangerous that the behavior is not the same when
building
as an enchancement request, something along these
lines:
dep
groupId/
artifactId/
version/
scope/
finalNameblah.jar/finalName
/dep
Ultimately, arguing over how this should work in Maven 2.0 is an
exercise in futility. Your time will be better spent convincing the
Maven Dev team to somehow make it work
Yann,
This is to be expected. When running maven in your B project, maven has no
knowledge of project A as a module to be built and referenced, only as a
dependency that needs to be retrieved from a repository and added to the
classpath.
In addition, finalName only effects the name
Hi,
I try to use the finalName in my parent pom as following:
finalName${artifactId}/finalName (without the version number)
If I run maven from the parent pom everything works fine: all my
artifacts are generated without the version number. and also the
classpath entry of the manifest.mf
I configured the finalname in the pom to something
like this:
finelNameabcfinalName
After mvn install there is a file with the name
abc.jar in the target folder, as expected.
But in the maven repository the filename still has the
form artifactid-version.jar, the finalName seems
to be ignored
Such files (abc.jar) should be uploaded using assembly plugin, which can
attach another artifact to the instlal phase.
I guess the standard jar is always deployed, to be available for
dependency...
Denis.
Tom Will wrote:
I configured the finalname in the pom to something
like
Hello,
I've set, in the configuration of the assembly plugin, the finalName property.
Unfortunately, the plugin keeps appending in the file name -src between the
finalName value and the extension (.zip, .tar.gz) specified in the assembly config file.
Does anybody know if it's possible to get
hi,
if src is the id specified in your assembly XML file, try add
appendAssemblyIdfalse/appendAssemblyId in your assembly
configuration's section in your pom.xml.
Stéphane.
Sebastien Pennec a écrit :
Hello,
I've set, in the configuration of the assembly plugin, the finalName
property
set, in the configuration of the assembly plugin, the finalName
property. Unfortunately, the plugin keeps appending in the file name
-src between the finalName value and the extension (.zip, .tar.gz)
specified in the assembly config file.
Does anybody know if it's possible to get rid of this -src
I guess this was missed when I sent a couple weeks ago, does anyone have
any thoughts on this? Should I file a JIRA issue?
Thanks,
Chad
Chad Brandon wrote:
Hi,
I'm using maven 2.0.1 for AndroMDA's build (its a fairly large
multiproject build).
It appears that if I have a version
Hi,
I'm using maven 2.0.1 for AndroMDA's build (its a fairly large
multiproject build).
It appears that if I have a version property in my System properties,
it sometimes gets picked up and used for the version of my project when
creating the final name (during pom interpolation I'm
#unversioned-jars
On 11/25/05, Wim Deblauwe [EMAIL PROTECTED] wrote:
Done: http://jira.codehaus.org/browse/MNG-1676
Wim
2005/11/24, Jason van Zyl [EMAIL PROTECTED]:
Wim Deblauwe wrote:
Hi,
when I set finalName/ in my pom.xml, the install plugin does not
take
Hi,
when I set finalName/ in my pom.xml, the install plugin does not take this
name into account.
Just for testing I added finalNametest.jar/finalName to the pom.xml of a
custom plugin of mine. When doing 'mvn install', I get this:
[INFO] Installing
Y:\wimd_test_vob\modules\maven-plugins\maven
Wim Deblauwe wrote:
Hi,
when I set finalName/ in my pom.xml, the install plugin does not take this
name into account.
Just for testing I added finalNametest.jar/finalName to the pom.xml of a
custom plugin of mine. When doing 'mvn install', I get this:
[INFO] Installing
Y:\wimd_test_vob
Done: http://jira.codehaus.org/browse/MNG-1676
Wim
2005/11/24, Jason van Zyl [EMAIL PROTECTED]:
Wim Deblauwe wrote:
Hi,
when I set finalName/ in my pom.xml, the install plugin does not take
this
name into account.
Just for testing I added finalNametest.jar/finalName
/faq.html#unversioned-jars
On 11/25/05, Wim Deblauwe [EMAIL PROTECTED] wrote:
Done: http://jira.codehaus.org/browse/MNG-1676
Wim
2005/11/24, Jason van Zyl [EMAIL PROTECTED]:
Wim Deblauwe wrote:
Hi,
when I set finalName/ in my pom.xml, the install plugin does not
take
finalNamemyEjb.jar/finalName
in an EAR's pom.xml
so that when this ejb jar is included in an EAR, it already has the
simple name (without the SNAPSHOT... suffix), without resorting to
bundleFileName entries in the EAR's pom.xml
I believe this will still install the ejb jar
I'll rewrite :-
Is it a good idea to use
build
finalNamemyEjb.jar/finalName
in an EJB's pom.xml (when building an ejb jar)
so that when this ejb jar is included in an EAR artifact, it already has the
simple name (without the SNAPSHOT... suffix), without resorting to
bundleFileName entries
Is it a good idea to use
build
finalNamemyEjb.jar/finalName
in an EAR's pom.xml
so that when this ejb jar is included in an EAR, it already has the
simple name (without the SNAPSHOT... suffix), without resorting to
bundleFileName entries in the EAR's pom.xml
I believe this will still install
I don't get the in an EAR's pom. Do you mean with an EAR packaging?
Stéphane.
On 11/9/05, Pete [EMAIL PROTECTED] wrote:
Is it a good idea to use
build
finalNamemyEjb.jar/finalName
in an EAR's pom.xml
so that when this ejb jar is included in an EAR, it already has the
simple name
I have a project to build / deploy for three different enviroments
(test,integration, production with different configs) and want to set the
jar file name depending on the active profile.
I know one possibility is with the finalName Element. The jar process uses
the finalName and generate
This is a bug we are hoping to fix shortly. While finalName can't be
completely modified for installing in the repository, it should be possible
to add a classifier for the environment. For reference, the JIRA bug is the
one referring to attaching an artifact with a classifier via a profile
80 matches
Mail list logo
