Hi all,
Jörg Schaible wrote:
> I can assure you, you'll *need* such (nested) "builder poms"
I agree, if you need a single build of all modules from the command line
for some reason. Not everyone needs that, though.
For example, if you develop in Eclipse with actively-developed projects
open, M2E
Still wearing my newbie hat,...
So, is there some way people embed the git repository information in their
POMs to indicate which parts of the POM tree are part of a specific
repository?
I guess what I am hoping for is that if you can define your git
relationships in Maven POMs then all your tool
On Friday, 22 February 2013, Jörg Schaible wrote:
> Thomas Broyer wrote:
>
> > On Thu, Feb 21, 2013 at 4:22 PM, Jörg Schaible
> > >wrote:
> >
> >> Hi Eric,
> >>
> >> Eric Kolotyluk wrote:
> >>
> >> > OK, I think I've got it.
> >> >
> >> > The answer depends more on what artifacts will always have
Thomas Broyer wrote:
> On Thu, Feb 21, 2013 at 4:22 PM, Jörg Schaible
> wrote:
>
>> 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.
>> >
>> >
Gesendet: Donnerstag, 21. Februar 2013 15:54
> An: Maven Users List
> Betreff: Re: Git Repositories
>
> 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...
n.alan.conno...@gmail.com]
> Gesendet: Donnerstag, 21. Februar 2013 15:54
> An: Maven Users List
> Betreff: Re: Git Repositories
>
> You would imaging somewhere like:
> http://docs.codehaus.org/display/MAVENUSER/Maven+Best+Practice+Guide
>
> But documentation of best practices i
n 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 somewhere like:
> htt
On Thu, Feb 21, 2013 at 4:22 PM, Jörg Schaible
wrote:
> 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
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 th
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
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.
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 into
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
model
13 matches
Mail list logo
