maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: Misunderstanding modules: "Two or more projects in the reactor have the same identifier"
Date Tue, 07 Jan 2014 13:58:45 GMT
FYI I call that a local aggregator pom. I typically set them up for the
various projects I jump between. I can then just open the whole set of
projects from intellij in one go and as this is maven I can safely discard
all the IDE's project info and have it regenerated from the pom and the
pom's reactor.

When I check a local aggregator into SCM I typically use the file based
activation to add each module via a profile for that module... but usually
I just keep them local only


On 7 January 2014 13:25, Patrick Turcotte <patrek@gmail.com> wrote:

>
> We are doing something similar with what I call an assembly project.
>
> I have the following structure:
>
> assembly
>   - pom.xml
>   - projectA
>     - pom.xml
>   - projectB
>     - pom.xml
>   - projectC
>     - pom.xml
>   - projectX
>     - pom.xml
>
> Where the assembly's pom.xml contains like:
>
> <packaging>pom</packaging>
> <modules>
>   <module>projectA</module>
>   <module>projectB</module>
>   <module>projectC</module>
>   <module>projectX</module>
> </modules>
>
> And dependencies between projects are set within each module (versions may
> be in a parent pom)
>
> Then, in my "assembly" project, I do
> mvn install
>
> Or, with multiple windows open, I would do a mvn install for projectA and
> then switch to projectX and build it.
>
> Hope this helps.
>
> Patrick
>
>
> On 07/01/14 12:49 AM, Barrie Treloar wrote:
>
>> On 7 January 2014 15:29, Mark Derricutt <mark@talios.com> wrote:
>>
>>> When the project is relatively new and the internally-developed
>>>>> dependency
>>>>> "A" is no where near being mature, nearly every change being made to
>>>>> "Project X" requires a corresponding change to A. At this point in the
>>>>> development cycle (and for many months in the foreseeable future) I
>>>>> actually
>>>>> /do/ need to rebuild A every time I build X.
>>>>>
>>>> What I've often done here is create a new workspace area that contains
>>> symlinks ( or git submodule checkouts ) of each of the modules I'm working
>>> on, and having a simple pom.xml in the top level that sets up a reactor
>>> build, then just build that.
>>>
>> There was also some talk about automating this step.
>> But its vapourware at the moment.
>>
>> It would work by checking your current pom for any -SNAPSHOT
>> dependencies and then pulling out the source code for those and
>> sitting them in the parent directory.
>> And as you say the parent pom is just a helper that has a bunch of
>> modules to make building things easier - and you would never check
>> that pom into version control.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message