I'll rewrite :- Is it a good idea to use
<build> <finalName>myEjb.jar</finalName> in an EJB's pom.xml (when building an ejb jar) so that when this ejb jar is included in an EAR artifact, it already has the simple name (without the SNAPSHOT... suffix), without resorting to <bundleFileName> entries in the EAR's pom.xml I believe this will still install the ejb jar with SNAPSHOT... suffix in the repository So is this the best practice ? On 10/11/05, Pete <[EMAIL PROTECTED]> wrote: > Apologies I meant to write 'in a EJB's pom.xml' i.e when building an ejb jar > > On 09/11/05, Stephane Nicoll <[EMAIL PROTECTED]> wrote: > > I don't get the "in an EAR's pom". Do you mean with an EAR packaging? > > > > Stéphane. > > > > On 11/9/05, Pete <[EMAIL PROTECTED]> wrote: > > > > > > Is it a good idea to use > > > > > > <build> > > > <finalName>myEjb.jar</finalName> > > > > > > in an EAR's pom.xml > > > > > > so that when this ejb jar is included in an EAR, it already has the > > > simple name (without the SNAPSHOT... suffix), without resorting to > > > <bundleFileName> entries in the EAR's pom.xml > > > > > > I believe this will still install the ejb jar with SNAPSHOT... suffix > > > in the repository > > > > > > So is this the best practice ? > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > .::You're welcome ::. > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
