Yes certainly you are right the ejb.jar is nothing else than a normal .jar, but I expected the ejb3 task to optionally produce the ejb-client.jar, containing of the the interfaces and its dependencies, plus creating the Class-Path: entry to the ejb-client.jar in the ejb.jar. So I have to do all that manuall now? This is taken away the magic I hoped maven2 would bring to my builds... :-(
Markus Alexander Sack wrote: > Well Maven doc isn't exactly great since its not really centralized. > > But as many have stated custom packaging part of the EJB3 spec never > made it > and as such, the JAR plugin is your best bet! :D > > -aps > > On 9/8/06, Markus KARG <[EMAIL PROTECTED]> wrote: >> >> Alexandre Russel wrote: >> >>>> According to "BetterBuildsWithMaven.pdf" I switched from >> >>>> <packaging>ejb</packaging> to <packaging>ejb3</packaging>. >> Unfortunately >> >>>> >> >>> change it to jar. >> >>> Alex >> >>> >> >> You mean there is no difference between ejb3 and jar? For what is >> ejb3 >> >> good then? >> >> >> > no, I mean the packaging is the same. It is just a jar with a >> persistence.xml >> > file. the Ejb3 extension/packaging comes from an early draft of the >> spec. >> > That didn't make to the final draft. >> > The packaging and what ejb3 are good for are unrelated :-) >> > alex >> > >> >> So there actually is no more ejb3 plugin but users shall use jar? Cool. >> Would be great if this would be found in the description of the ejb >> plugin on the web (or in the "BetterBuildsWithMaven.pdf") so people do >> not spend days with boring questions like mine. ;-) >> >> >> > >
smime.p7s
Description: S/MIME Cryptographic Signature
