yeah that's a known issue with Sun ;-)

for a getting-started kind of tutorial - I recommend JBoss's
TrailBlazer (can't remember the url - google finds it though).

for more in depth info - currently there's only the jcp spec and some
material on the net. Oh oracle's OTN (http://otn.oracle.com) has some
info about it too - but I think it's oc4j-oriented, like Sun's...

good luck :)

On 11/20/05, Adam Hardy <[EMAIL PROTECTED]> wrote:
> You guys doing EJB3, can you recommend a decent tutorial on the new
> technology? Did you go to Sun or JBoss?
>
> I see with Sun's glassfish EJB3 server, the bundled tutorial is actually
> a tutorial for Netbeans users, rather than just a pure EJB3 tutorial :(
>
> Or are there others?
>
> Thanks
> Adam
>
> Bruno Aranda on 18/11/05 14:43, wrote:
> > Thanks Stéphane! I've finally got it working...
> > I've checked out the current SVN maven, and maven ear plugin and
> > rebuilt everything. I've used the maven-par-plugin from the mojo
> > codehaus sandbox. After building everything I reproduced an issue
> > discussed some days ago in this mailing list [1], where it is said
> > that ejb3 and pars do not expose its classes to the classpath in order
> > to be used by other modules. I've created a JIRA for that [2] and
> > attached the plugin there with the solution proposed by Thomas Marek,
> > in order to be available in the next release.
> > Now, everything is working as expected,
> >
> > Thanks,
> >
> > Bruno
> >
> > [1] http://mail-archives.apache.org/mod_mbox/maven-users/200511.mbox/[EMAIL 
> > PROTECTED]
> > [2] http://jira.codehaus.org/browse/MNG-1620
> >
> > 2005/11/17, Stephane Nicoll <[EMAIL PROTECTED]>:
> >
> >>Bruno,
> >>
> >>Yes but you need to use latest SVN et rebuild the maven ear plugin. It works
> >>but it's not released yet. Regarding the lifecyle, same answer, it's applied
> >>to maven core but not as part of the 2.0 release.
> >>
> >>Hope it helps,
> >>Stéphane
> >>
> >>On 11/17/05, Bruno Aranda <[EMAIL PROTECTED]> wrote:
> >>
> >>>Thanks, I know, to summarise, my question was if someone has
> >>>successfully included a par generated with that plugin inside an
> >>>ear...
> >>>
> >>>Thanks,
> >>>
> >>>Bruno
> >>>
> >>>2005/11/17, Arik Kfir <[EMAIL PROTECTED]>:
> >>>
> >>>>I think you need to use the 'maven-par-plugin' (in the mojo project,
> >>>>at http://mojo.codehaus.org/)
> >>>>
> >>>>However, AFAIK its not released yet.
> >>>>
> >>>>On 11/17/05, Bruno Aranda <[EMAIL PROTECTED]> wrote:
> >>>>
> >>>>>Hi all,
> >>>>>
> >>>>>I am doing my first steps with maven... I have a multi-module setup
> >>>>>that involves the creation of jars, wars, pars and an ear with
> >>>>>everything inside. I've been told to use a plugin to create the par
> >>>>>file [1]. However, when the par is set as a dependency in the pom.xml
> >>>>>file to create the ear, a jar (with the same name of the par) is
> >>>>>included in the ear instead. I do not know anything about the maven
> >>>>>insights so I am not able right now to modify the code in order to see
> >>>>>what fails now, although I could do an ant task to rename again the
> >>>>>jar file to par inside the ear. But that will be the last solution...
> >>>>>I've seen that there is also a maven-par-plugin in the sandbox and
> >>>>>I've tried to use it. Then I got this exception: Cannot find lifecycle
> >>>>>mapping for packaging: 'par'.
> >>>>>I've compared the two plugins and I've seen than the plugin from JIRA
> >>>>>contains a components.xml file, so I've copied that file to the
> >>>>>sandbox plugin and I've installed it again (yeah, you now, trial and
> >>>>>error). The lifecycle seems ok now, but I keep getting this exception
> >>>>>
> >>>>>org.apache.maven.lifecycle.LifecycleExecutionException: Error
> >>>
> >>>assembling PAR
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to