+1 with the fact pom.xml are only files for git (or svn).
So this is actually not a Maven release plugin question, but more a git
one. It's up to you to know which commit you want to merge with. Might be
difficult though (easier than with svn though ;)). Cherry-picking could be
a solution but
From personal experience single artifact repositories work best. Mostly
due to the way git's branching/tagging model works ( over the whole
repository ).
Also, the maven-release-plugin in its default configuration only
releases from the root of the repository so unless you want ALL your
One git repository for everything that is always released together and has
the same version number.
If there are some sub-modules that have a different lifecycle, they should
be in a separate git repository. That may force you to split the other
modules you thought were always released as one
OK, I think I've got it.
The answer depends more on what artifacts will always have the same
version number, than how many artifacts there are.
In a nutshell, one repository for the entire multi-module project is
best, where all the artifacts keep their versions in sync with the
parent pom.
You would imaging somewhere like:
http://docs.codehaus.org/display/MAVENUSER/Maven+Best+Practice+Guide
But documentation of best practices is something we are weak on...
We are great at telling people what isn't best practice... not so great at
documenting that stuff ;-)
A wise user would add a
Hi Eric,
Eric Kolotyluk wrote:
OK, I think I've got it.
The answer depends more on what artifacts will always have the same
version number, than how many artifacts there are.
In a nutshell, one repository for the entire multi-module project is
best, where all the artifacts keep their
Unfortunately the link below does not show anything to read in English ...
Josef
-Ursprüngliche Nachricht-
Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Gesendet: Donnerstag, 21. Februar 2013 15:54
An: Maven Users List
Betreff: Re: Git Repositories
You would imaging
Hi...
I have a project with a lot of unit test and I really like the features of
this plugin.. I put it in my maven project but I don't know how to use it..
Could you explain me that, please.. and, if possible, how to use inside
eclipse ide.
Thanks.
Ivo
On Thu, Dec 27, 2012 at 11:24 PM,
On Thu, Feb 21, 2013 at 4:22 PM, Jörg Schaible
joerg.schai...@scalaris.comwrote:
Hi Eric,
Eric Kolotyluk wrote:
OK, I think I've got it.
The answer depends more on what artifacts will always have the same
version number, than how many artifacts there are.
In a nutshell, one
I did warn that you would imagine that would be the place to find such
things... and that somebody should remove the placeholder text
On 21 February 2013 17:20, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
Unfortunately the link below does not show anything to read in English
This plugin is called just when you do mvn test.
If what you need is using this precise version, just configure it under the
build/pluginManagement tag.
Cheers
Le 21 févr. 2013 18:25, Alberto Ivo alberto...@gmail.com a écrit :
Hi...
I have a project with a lot of unit test and I really like
I made that page a long, long time ago based on a complaint (on this
list) that such a page did not exist. I had nothing specific to post
there myself at the time and expected that other Maven users (or even
myself) might, at some point, replace the lorem ipsum text with
something more
OK, I have added my two cents at
http://docs.codehaus.org/display/MAVENUSER/Maven+Best+Practice+Guide?focusedCommentId=230398624#comment-230398624
Someone need to replace the Latin in front matter. If you want I could do
that, and promote my comment into the article.
Cheers, Eric
On Thu, Feb
hmmm... ok... is there a way to run this automatically when one runs mvn
install ?
Ivo
On Thu, Feb 21, 2013 at 2:36 PM, Baptiste MATHUS m...@batmat.net wrote:
This plugin is called just when you do mvn test.
If what you need is using this precise version, just configure it under the
Thanks Wayne Fay
Your solution worked for me
I am using maven 3.0.3 in Windows XP SP3
I have also included the M2 variable value in PATH variable before changing
the path of Maven to a path that doesnt have any spaces.
--
View this message in context:
Hi Ivo,
is there a way to run this automatically when one runs mvn install ?
The test phase runs automatically when one runs mvn install unless you
explicitly tell it to skip tests (e.g., mvn -DskipTests install).
For details, see:
Hello everyone,
I'm using maven-assembly-plugin to generate a zip package with some
artifacts in it. It works fine, now the only missing step is I need to
generate an XML file with some information about the artifacts. This XML
will be used by another program to basically know about the
I'm using maven-assembly-plugin to generate a zip package with some
artifacts in it. It works fine, now the only missing step is I need to
generate an XML file with some information about the artifacts. This XML
You probably need to write your own plugin to do this. You should
write the file
Thomas Broyer wrote:
On Thu, Feb 21, 2013 at 4:22 PM, Jörg Schaible
joerg.schai...@scalaris.comwrote:
Hi Eric,
Eric Kolotyluk wrote:
OK, I think I've got it.
The answer depends more on what artifacts will always have the same
version number, than how many artifacts there are.
On Friday, 22 February 2013, Jörg Schaible wrote:
Thomas Broyer wrote:
On Thu, Feb 21, 2013 at 4:22 PM, Jörg Schaible
joerg.schai...@scalaris.com javascript:;wrote:
Hi Eric,
Eric Kolotyluk wrote:
OK, I think I've got it.
The answer depends more on what artifacts will
20 matches
Mail list logo
