Project is duplicated in the reactor

[Graham Leggett <mi...@sharp.fm>]

Hi all,

I am getting a very strange problem with a multiproject build using maven
v2.0.4. I get the error "project foo is duplicated in the reactor":

[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Project 'alchemy:alchemy-validation' is duplicated in the reactor
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Wed Nov 01 18:37:35 CAT 2006
[INFO] Final Memory: 1M/3M
[INFO]
------------------------------------------------------------------------

Trouble is, I see no evidence of the project being duplicated in the reactor:

  <modules>
    <module>alchemy-client</module>
    <module>alchemy-hdf</module>
    <module>alchemy-mx</module>
    <module>alchemy-testing</module>
    <module>alchemy-ui</module>
    <module>alchemy-validation</module>
    <module>LoginModule</module>
    <module>alchemy-trader</module>
    <module>alchemy-trader-ear</module>
    <module>alchemy-eclipse</module>
  </modules>

Does anyone know if this is a known bug, or is the error message trying to
tell me something completely different?

I worked around this previously by commenting out all modules but the
first one, and slowly adding all the modules back in. Once all the modules
were commented back in, it worked fine. Now suddenly the problem is back.
Anyone have any ideas?

Regards,
Graham
--



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: Project is duplicated in the reactor

[Kenney Westerhof <ke...@apache.org>]

Hi, this is a user question and should be posted on the user list.
Posting the answer on the user list.

Quick answer: you probably have 2 projects with the same groupId/artifactId
(copy paste error when creating pom.xml files?).
The other possible cause is that you define the same module twice (for instance
in a child project you have <module>../modulename</module> somewhere, 
and the parent has <module>modulename</module>.

-- Kenney


Graham Leggett wrote:
> Hi all,
> 
> I am getting a very strange problem with a multiproject build using maven
> v2.0.4. I get the error "project foo is duplicated in the reactor":
> 
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Project 'alchemy:alchemy-validation' is duplicated in the reactor
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: < 1 second
> [INFO] Finished at: Wed Nov 01 18:37:35 CAT 2006
> [INFO] Final Memory: 1M/3M
> [INFO]
> ------------------------------------------------------------------------
> 
> Trouble is, I see no evidence of the project being duplicated in the reactor:
> 
>   <modules>
>     <module>alchemy-client</module>
>     <module>alchemy-hdf</module>
>     <module>alchemy-mx</module>
>     <module>alchemy-testing</module>
>     <module>alchemy-ui</module>
>     <module>alchemy-validation</module>
>     <module>LoginModule</module>
>     <module>alchemy-trader</module>
>     <module>alchemy-trader-ear</module>
>     <module>alchemy-eclipse</module>
>   </modules>
> 
> Does anyone know if this is a known bug, or is the error message trying to
> tell me something completely different?
> 
> I worked around this previously by commenting out all modules but the
> first one, and slowly adding all the modules back in. Once all the modules
> were commented back in, it worked fine. Now suddenly the problem is back.
> Anyone have any ideas?
> 
> Regards,
> Graham
> --
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org