I would be very interested to hear other peoples opinion on this as well.
I'm currently working on 4 separate EJB projects and have gone through this
same situation.  I have heard talk on the mailing list about adding support
for an artifact type "ejb-client.jar", but I don't remember who was looking
into that.  I've used the multiproject setup you've listed above, and with a
little hack on the xdoclet plugin, got it up and running without any major
problems.  I would really like to flesh out some kind of "maven methodology"
on this subject as I know it is a big area of question.  I might put some
time into putting something on the wiki regarding this.

Ryan


-----Original Message-----
From: Ebersole, Steven [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 14, 2004 7:25 AM
To: Maven Users List
Subject: single artifact mantra and ejb projects

I have a question about the mantra that a single project should produce a
single artifact.  I can buy into that in every case I have run across or
have thought about, except for projects involving ejb creation.  Typically
an ejb project will produce both an ejb-jar file as well as a client-jar
file.  But wouldn't that be two artifacts?

I have read a lot of external docs on setting up j2ee projects using maven,
most of which suggest a multi project layout.  I can totally justify that
for say a j2ee project producing an ear made up of sub ejb-jars and wars.
But in the case of a stand-alone ejb-jar producing project or an ejb-jar
producing subproject of an ear project it seems like overkill to define a
subproject for the ejb-jar generation and the client-jar generation,
especially when both are  ultimately logically tied to the attainment of an
ejb goal.

Could someone help me out in my understanding here?

Thanks,
Steve

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