I've been working with the ejb plugin a bit, considering what I need to
add to it to make it do what I want, same for the ear plugin. I am
confused as to why there is duplicate ear functionality in the j2ee
plugin, as well as a number of properties in the j2ee plugin docs, for
ejbs and other artifacts that it doesn't actually have any code to
handle (not that it would be bad if the ejb plugin did have similar
properties). Looking in the mailing list archives didn't really clear
this up for me.
At this point I find the ejb plugin (and ear) plugin useless except for
some very simplistic cases, so am interested in enhancing it, or will
just bypass it completely if people don't want to see any changes to it...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- Some JARs are going away Jason van Zyl
- Re: Some JARs are going away John Casey
- Re: Some JARs are going away Jason van Zyl
- Re: Some JARs are going away Henri Yandell
- Re: Some JARs are going away Ben Walding
- Re: Some JARs are going away Henri Yandell
- RE: What is the history of the j2ee plugin, and ... Colin Sampaleanu
- RE: What is the history of the j2ee plugin, ... Darren Collins
- Re: What is the history of the j2ee plug... Colin Sampaleanu
- RE: What is the history of the j2ee plug... dion
