I have no idea why this didn't occur to me before, but what if we just
created a javaee-api *zip* file containing all the jars. You could
then just delete the javaee-api.jar and unzip the javaee-api.zip in
its place and you're good to go. You could then replace any number of
library jars.
Seems like a small price to ask people to pay if they want to be
mucking about with individual api versions.
Thoughts?
-David
On Sep 2, 2009, at 5:51 AM, Jean-Louis MONTEIRO wrote:
Hi,
The artifact javaee-api containing apis can lead to some issues.
I would like to know if you plan to split (deliver Geronimo jars) in
assemblies ?
This artifact seems useful internal (unique dependency in our
modules) but
at runtime it's probably convenient for end users to have all jars
instead
of one.
Is it relevant ?
Jean-Louis
--
View this message in context:
http://www.nabble.com/Splitting-org.apache.openejb%3Ajavaee-api%3Ajar-artifact-tp25256876p25256876.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
