> -----Original Message-----
> From: Tim Stephenson [mailto:[EMAIL PROTECTED]]
> Sent: 18 November 2002 23:38
> To: 'Turbine Maven Developers List'
> Subject: RE: maven J2EE plugin contrib
> 
> I cant see the ejb or ear plugins in CVS, could you send them Michal
or
> Nathan? Thanks in advance.
> 
> I don't think I have a strong opinion about whether the plugins should
be
> integrated as one or not - would those who have commit rights care to
set
> a
> direction?

+1 for several plugins: ejb, rar, war, ear, j2ee-deploy

We already have the war one.

Thanks
-Vincent

> 
> regards, tim
> -----Original Message-----
> From: Michal Maczka [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, 19 November 2002 1:05 AM
> To: 'Turbine Maven Developers List'
> Subject: RE: maven J2EE plugin contrib
> 
> What about job which Nathan Coast [[EMAIL PROTECTED]] did?
> 
> He created ejb, ear plugins which are similar to war plugin.
> I am using them and they work fine for me.
> He sent notification to mailing list some time ago.
> 
> If I can add my 1 cent I think that what he did it was a step in a
right
> direction
> and j2ee plugin should be deprecated and work should continue
separately
> on
> plugins like
> 
> ejb:
> war:
> ear:
> appserver:
> cactus:
> struts:
> 
> 
> etc..
> 
> Once  they are more advanced, j2ee plugin might integrate them and
provide
> even higher level of abstraction.
> I believe also that this work cannot be correctly done if there is no
way
> to
> have other types of dependencies than jars
> (Nathan described also this problem)..
> 
> 
> Michal
> 
> -----Original Message-----
> From: Tim Stephenson [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 18, 2002 6:23 AM
> To: 'Turbine Maven Developers List'
> Subject: RE: maven J2EE plugin contrib
> 
> 
> Thanks Peter
> 
> I'll go to work on the deployment goals using the props in the j2ee
plugin
> and the names you suggested
> 
> Rgds, tim
> 
> -----Original Message-----
> From: Peter Lynch [mailto:[EMAIL PROTECTED]]
> Sent: Monday, 18 November 2002 3:16 PM
> To: Turbine Maven Developers List
> Subject: Re: maven J2EE plugin contrib
> 
> Tim,
> 
> ----- Original Message -----
> From: "Tim Stephenson" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, November 17, 2002 8:27 PM
> Subject: maven J2EE plugin contrib
> 
> 
> >
> > I noticed after I submitted the client jar creating patch last night
> that
> > the j2ee plugin documents a similar functionality in the j2ee:ejb
goal,
> > though that goal has not been implemented at this stage. My question
is
> will
> > it ever be and if so what distinguishes this from the more general
> java:jar?
> >
> 
> sorry don't have that answer.
> 
> >
> > If 'j2ee:ejb' is the preferred way to go and if no one else is
working
> on
> it
> > I am happy to submit a patch to provide this goal shortly.
> >
> > Secondly, the doco for j2ee also states that the appserver:xxx tasks
are
> > explicitly not to deploy wars / ears / etc but to deploy the servers
> 
> Yup, except due to some limitations I have yet to resolve with jelly,
they
> don't
> quite work yet. Nice theory of mine though :-). The tomcat one used to
> work
> in
> the pre beta 5 days...
> 
> > themselves. In this case would anyone object to a set of j2ee-
> deploy:war,
> > j2ee-deploy:ear, j2ee-deploy:ejb-jar goals? I was intending to add
these
> > within the j2ee plugin - would this be the most appropriate
location?
> >
> 
> It would be cool if I had the appserver stuff working. Then u could
use
> the
> appserver properties to figure out where to deploy those
> things.....actually
> I
> suppose u still could.
> 
> Regardless deploy goals for those things seem to fit there. I would
> recommend
> naming though like j2ee:ear-deploy, j2ee:war-deploy, etc. but that is
my
> personal preference.
> 
> -Peter
> 
> 
> 
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 
> 
> 
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:turbine-maven-dev-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:turbine-maven-dev-
> [EMAIL PROTECTED]>



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

Reply via email to