> the web servers. I would prefer not to have different EJB projects just for
> the web server. Is this possible, I didn't see an overlay option for the
> ejb plugin.
We're done this before (still using modules) by having one ejb project
with the common stuff and then one module each for the various
targets. Then you use the dependency plugin to unpack the ejb artifact
and then your resource files get copied over it, then jar up the
results as that module's artifact/output.
I am not a big fan of classifiers for these purposes, so we used
artifactIds with -${server} type names.
But an overlay option for the ejb plugin is not a bad idea -- perhaps
you should post it in Jira as an RFE? It would basically do what I've
suggested above except it would be more automatic rather than manual.
As for profiles, if you only need to build 1 server at at time, or
your devs only need to target 1 at a time, that may be better. I just
use profiles for very specific/limited things, and this is not one of
them.
I have to admit that I'm kinda curious what servers/versions you are
targeting and what kinds of server-specific files you need to include.
At this point, I'm finding that we very rarely need to go down this
road.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
