On Dec 15, 2006, at 3:34 AM, Graham Leggett wrote:
On Thu, December 14, 2006 9:05 pm, Stephane Nicoll wrote:
This has been tackled a dozen of times and I am not sure it has
anything to do with the EAR plugin, at least if we follow the
spec. If
I am wrong, please let me know.
The valid
On Thu, December 14, 2006 9:05 pm, Stephane Nicoll wrote:
This has been tackled a dozen of times and I am not sure it has
anything to do with the EAR plugin, at least if we follow the spec. If
I am wrong, please let me know.
The valid way to bundle shared components/libs in a EAR is to
On 12/15/06, Graham Leggett [EMAIL PROTECTED] wrote:
On Thu, December 14, 2006 9:05 pm, Stephane Nicoll wrote:
This has been tackled a dozen of times and I am not sure it has
anything to do with the EAR plugin, at least if we follow the spec. If
I am wrong, please let me know.
The valid
Hi all,
Using the v2.3-SNAPSHOT version of the ear plugin, I am struggling to get
the application.xml file built correctly.
Between maven1 and maven2, the ejb plugin lost it's ability to bundle
dependencies inside the ejb.
This means (as I understand it) that it's now up to the ear plugin to
Hi,
This has been tackled a dozen of times and I am not sure it has
anything to do with the EAR plugin, at least if we follow the spec. If
I am wrong, please let me know.
The valid way to bundle shared components/libs in a EAR is to define
the Class-Path entry of the manifest in EJB module(s)
On Dec 14, 2006, at 11:05 AM, Stephane Nicoll wrote:
Hi,
This has been tackled a dozen of times and I am not sure it has
anything to do with the EAR plugin, at least if we follow the spec. If
I am wrong, please let me know.
The valid way to bundle shared components/libs in a EAR is to define
On 12/14/06, David Jencks [EMAIL PROTECTED] wrote:
I agree that spec support is the way to go.
the jee5 ear lets you specify a lib directory (default is lib)
where all the jars inside get added to the classpath. We could work
on jee5 support, that ought to keep everyone happy. Does the
