Yup (well roughly) in the working with manifest document. On 2/17/06, Wayne Fay <[EMAIL PROTECTED]> wrote: > Now that I have discovered the: > > <build> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-ejb-plugin</artifactId> > <configuration> > <archive> > <manifest> > <addClasspath>true</addClasspath> > </manifest> > </archive> > </configuration> > </plugin> > </build> > > bit of configuration "code", my problems seem to be resolved. > > Is this configuration-archive-manifest-mainClass/addClasspath/etc tag > stuff documented somewhere? > > Thanks. > Wayne > > On 2/17/06, Tomislav Stojcevich <[EMAIL PROTECTED]> wrote: > > The ear plugin does this for you. > > > > I don't think it's part of the j2ee spec to have dependent jars > > bundled inside the ejb.jar. I believe that they normally get grouped > > together inside of an ear file. > > > > You setup a seperate project with packaging of ear and add your > > ejb.jar as a dependency. Your ejb.jar project will have dependencies > > on the vo.jar, etc... etc..... which will all get pulled into your ear > > via the transitive dependency mechanism. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
-- Alexandre Poitras Québec, Canada --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
