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]>
