For those who wants another use case for custom unique version is:
At our legacy application based on JPA has persistence.xml. Our domain jars
were divided into the two module and they are included at our
persistence.xml at like this:
persistence-unit name=SearchV2PU
jta-data
Am 24.01.2012 10:58, schrieb Cem Koc:
For those who wants another use case for custom unique version is:
At our legacy application based on JPA has persistence.xml. Our domain jars
were divided into the two module and they are included at our
persistence.xml at like this:
persistence
Am 23.01.2012 08:36 schrieb Thomas Scheffler thomas.scheff...@uni-jena.de
:
Am 20.01.2012 16:27, schrieb Ron Wheeler:
Of all of the developers that have built thousands of applications using
Maven, you are the only one who wants to do this.
Does that not raise any red flags?
There must be
Am 23.01.2012 09:34, schrieb Ansgar Konermann:
Am 23.01.2012 08:36 schrieb Thomas Schefflerthomas.scheff...@uni-jena.de
:
Am 20.01.2012 16:27, schrieb Ron Wheeler:
Of all of the developers that have built thousands of applications using
Maven, you are the only one who wants to do this.
Does
You could reach out to the Hudson user community.
I do not use Hudson although many people here do use Maven and Hudson
together.
We have a large project with over 90 maven projects of which 70 produce
artifacts based on our code.
We have a small team but have some rules about releases and
On 23 January 2012 13:25, Ron Wheeler rwhee...@artifact-software.comwrote:
You could reach out to the Hudson user community.
I do not use Hudson although many people here do use Maven and Hudson
together.
Most use Jenkins rather than that scurrilous fork Hudson ;-)
We have a large
We use SNAPSHOTs extensively and deploy them when they are ready to be
used by a consuming project.
For example, we often have one person working on the database and the
DAOs, another person working on the Web services and a third person
working on the GUI components.
The GUI person often needs
See when Maven is the build tool, I usually find it easier to just checkout
my -SNAPSHOT deps locally and build them. That way I have complete control
over when they get updated.
On 23 January 2012 15:17, Ron Wheeler rwhee...@artifact-software.comwrote:
We use SNAPSHOTs extensively and deploy
On 23/01/2012 10:30 AM, Stephen Connolly wrote:
See when Maven is the build tool, I usually find it easier to just
checkout my -SNAPSHOT deps locally and build them. That way I have
complete control over when they get updated.
Some times the guys do that as well.
Ron
On 23 January 2012
Deploying SNAPSHOTS can work when there is a clear, one-directional,
flow, from producers to consumers. It produces nothing but horror
otherwise, when developers find Maven downloading a 'new' snapshot
that is actually 'old' with respect to their pending changes.
On Mon, Jan 23, 2012 at 1:06 PM,
Am 21.01.2012 16:49, schrieb Vincent Latombe:
http://mojo.codehaus.org/buildnumber-maven-plugin/ could be your solution
Vincent
Hi Vincent,
thank you for your suggestion but sadly the buildnumber from
buildnumber-maven-plugin is completely unrelated to the unique version
number that is
Am 20.01.2012 16:27, schrieb Ron Wheeler:
Of all of the developers that have built thousands of applications using
Maven, you are the only one who wants to do this.
Does that not raise any red flags?
There must be a best practice for what you are trying to achieve.
This is clearly not it.
Hi
http://mojo.codehaus.org/buildnumber-maven-plugin/ could be your solution
Vincent
2012/1/20 Ron Wheeler rwhee...@artifact-software.com
Of all of the developers that have built thousands of applications using
Maven, you are the only one who wants to do this.
Does that not raise any red
Hi,
I want to create a unique SNAPSHOT version that does not consist of
timestamp and buildnumber but is created by a defined property.
I read the docs and googled for a solution but found no way to alter the
unique version string. How can this be achieved?
regards
Thomas
It cannot.
That is part of the spec for the layout of a Maven repository.
-Stephen
2012/1/20 Thomas Scheffler thomas.scheff...@uni-jena.de:
Hi,
I want to create a unique SNAPSHOT version that does not consist of
timestamp and buildnumber but is created by a defined property.
I read the
Am 20.01.2012 10:32, schrieb Stephen Connolly:
It cannot.
That is part of the spec for the layout of a Maven repository.
Is there a way to embed the unique version string into the JAR manifest
then? If I test an application with a snapshot jar I want stick with
that specific version when
You can stuff what ever you want in tge manifest.
Google is your friend: maven jar plugin manifest customization
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On Jan 20,
Am 20.01.2012 12:40, schrieb Stephen Connolly:
You can stuff what ever you want in tge manifest.
Google is your friend: maven jar plugin manifest customization
Hi,
yeah I know that. But how can I put the unique version number into the
JAR manifest?
Thomas
Am 20.01.2012 10:32, schrieb
Am 20.01.2012 15:30, schrieb Stephen Connolly:
2012/1/20 Thomas Schefflerthomas.scheff...@uni-jena.de:
Am 20.01.2012 12:40, schrieb Stephen Connolly:
You can stuff what ever you want in tge manifest.
Google is your friend: maven jar plugin manifest customization
Hi,
yeah I know that. But
2012/1/20 Thomas Scheffler thomas.scheff...@uni-jena.de:
Am 20.01.2012 15:30, schrieb Stephen Connolly:
2012/1/20 Thomas Schefflerthomas.scheff...@uni-jena.de:
Am 20.01.2012 12:40, schrieb Stephen Connolly:
You can stuff what ever you want in tge manifest.
Google is your friend: maven jar
Of all of the developers that have built thousands of applications using
Maven, you are the only one who wants to do this.
Does that not raise any red flags?
There must be a best practice for what you are trying to achieve.
This is clearly not it.
Ron
On 20/01/2012 10:14 AM, Stephen Connolly
21 matches
Mail list logo