maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Baptiste MATHUS <>
Subject Re: Circular dependency and assembly plugin
Date Mon, 01 Apr 2013 09:45:21 GMT
Difficult to be sure what you're trying to do, but having circular dep is
in fact unsupported and generally not a good idea from many points of view.
I might answer that yes having a third project to break the circular dep is
one of the general solution to break the cycle.

If ever possible, having a demo project github might encourage people here
to help and propose a way to solve your problem?

My 2 cents.


2013/4/1 Kevin Krumwiede <>

> I have a project -- let's call it A -- in which maven-assembly-plugin
> is bound to the package phase.  It creates a zip file containing the
> main artifact and all the project's dependencies.  This works as
> intended.
> I have a second project -- call it B -- that consists of plugins for
> project A.  As part of building A, I'd like to have the assembly
> plugin create a scripts/ directory in the zip file and unpack the
> classes from B into it.
> The problem is that B must depend on A.  So if I make the assembly
> plugin depend on B, A won't have been installed yet when B is built,
> creating a circular dependency.
> What's the Maven way to solve this?  I'm thinking I could create the
> zip file in a different project that is a peer or parent of A and B...
> Thanks,
> Krum
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Baptiste <Batmat> MATHUS -
Sauvez un arbre,
Mangez un castor !

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