maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Hammar <and...@hammar.net>
Subject Re: Attached artifacts and dependencies
Date Sat, 05 Jan 2013 22:52:50 GMT
I always argue for having the API (e.g. ejb client) as a separate module
and then the impl (e.g. the ejb) as a separate module.

/Anders


On Sat, Jan 5, 2013 at 11:45 PM, Manfred Moser <manfred@mosabuam.com> wrote:

> On Sat, January 5, 2013 2:43 pm, Stanimir Stamenkov wrote:
> > Sat, 5 Jan 2013 14:38:38 -0800, /Manfred Moser/:
> >
> >> If the dependencies are not applicable for this artifact (e.g. the pom
> >> is
> >> not valid for it because it is generated against Maven convention) then
> >> it
> >> should not be an artifact in the same coordinates but rather be a
> >> different module with different GAV coordinates
> >
> > All right.  That's pretty much what I've thought, but then revisit
> > the EJB plugin case I've given:
> >
> >
> http://maven.apache.org/plugins/maven-ejb-plugin/examples/ejb-client-dependency.html
> >
> > Seems like not the best practice - why it has been introduced, then?
>
> A mistake? I don't know. But nothing stops you from having two modules
> with different coordinates for the ejb and the ejb client from what I
> understand.. but I have not used ejb for ages so I might be completely
> off.
>
> manfred
>
>
> ---------------------------------------------------------------------
> 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