maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrien Rivard <adrien.riv...@gmail.com>
Subject Re: Circular dependency and assembly plugin
Date Mon, 01 Apr 2013 17:20:15 GMT
Yes.
Have a look at the example for the maven-assembly-plugin :

http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html


On Mon, Apr 1, 2013 at 6:03 PM, Kevin Krumwiede <kjkrum@gmail.com> wrote:

> So if I'm thinking correctly, I could create a project C that contains
> no code of its own, but depends on A and B and creates the
> distribution zip.  Project C's artifact packaging would be pom, but I
> could still attach the zip artifact to it and deploy it to my repo...
> right?
>
> ~K
>
> On 4/1/13, Vincent Latombe <vincent.latombe@gmail.com> wrote:
> > Hi,
> >
> > generally, the good answer to this kind of problem is to extract the
> > assembly part to an artifact C, that depends on both A and B.
> >
> > Cheers,
> >
> > Vincent
> >
> >
> > 2013/4/1 Baptiste MATHUS <bmathus@batmat.net>
> >
> >> Hi,
> >> 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.
> >>
> >> Cheers
> >>
> >>
> >> 2013/4/1 Kevin Krumwiede <kjkrum@gmail.com>
> >>
> >> > 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: users-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: users-help@maven.apache.org
> >> >
> >> >
> >>
> >>
> >> --
> >> Baptiste <Batmat> MATHUS - http://batmat.net
> >> Sauvez un arbre,
> >> Mangez un castor !
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Adrien Rivard

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