> > >> >> Do you want to have a jboss:ejbdoclet and a weblogic:ejbdoclet goal >> when both of them are going to be 80% the same? >> > > Yeap! I would like to see them as two separate projects.
I guess I'm having trouble figuring out how you would do that cleanly without duplicating a lot of jelly script. In jboss:ejbdoclet you would have this: <ejbdoclet ... lots of attributes > ... lots of common stuff like <session/> <jboss subtask /> </ejbdoclet> Then in weblogic:ejbdoclet you would have this: <ejbdoclet ... lots of attributes > ... lots of common stuff like <session/> <weblogic subtask /> </ejbdoclet> How do we avoid duplicating all of the common stuff (ejbdoclet attributes and subtasks) in an easy to maintain way? > AFAIK XDoclet team (I know this from mailing lists not from developers) > is not going to maintain as many plugin as it has place now when version > 2.0 will be out. > > They just want to concentrate on writing XDoclet core and maybe few core > plugins (@jakarata) and give the control over plugins to community > (@sourceforge ?). So they want to do exactly the same thing as seems to > me to be a right thing for Maven. > > Note for example that when XDoclet 2.0 will be out probably jboss plugin > for it will most likely be released much faster then e.g. the plugin for > Borland Application Server. So then some users will be still willing to > use XDoclet 2.0 some others them will want to use 1.x while some others > would prefer to use some other doclet. > > It will be a horror to see a code supporting all those tools inside > maven-ejb plugin. Yea. As I've currently structured it that would be a buttload of j:if tags. I'm attaching the patch that's currently working for me and I'm about to post it to jira as well. You'll probably hate it :-)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
