+1 This really helps when people want to use the code standalone
But we must provide a rollup jar so our users don't have to hunt down
10 spec jars.
-dain
On Nov 9, 2005, at 11:40 PM, Alan D. Cabrera wrote:
I am of the same opinion.
Regards,
Alan
David Jencks wrote, On 11/9/2005 9:08 PM
I am of the same opinion.
Regards,
Alan
David Jencks wrote, On 11/9/2005 9:08 PM:
I have a REALLY REALLY REALLY strong preference that ALL geronimo
modules depend ONLY on the specs they actually use. I would prefer
that we don't build the universal spec jar or that we build it after
everyt
>From a Maven point of view with transitive dependencies, this is
imperative. The universal jar should just be a distribution
convenience (if it is built at all).
- Brett
On 11/10/05, David Jencks <[EMAIL PROTECTED]> wrote:
> I have a REALLY REALLY REALLY strong preference that ALL geronimo
> mod
I have a REALLY REALLY REALLY strong preference that ALL geronimo
modules depend ONLY on the specs they actually use. I would prefer
that we don't build the universal spec jar or that we build it after
everything else is built and all the configurations are built. I
really prefer to know what
I think referring to one is simpler. That way exceptions will stand out. I'm
not sure I see a downside.
Aaron Mulder wrote:
So I notice that the JSR-88 code is in
geronimo-spec-j2ee-deployment-1.1-rc4.jar and also
geronimo-spec-j2ee-1.4-rc4.jar. I guess "spec-j2ee" is a rollup of
all (or mos
So I notice that the JSR-88 code is in
geronimo-spec-j2ee-deployment-1.1-rc4.jar and also
geronimo-spec-j2ee-1.4-rc4.jar. I guess "spec-j2ee" is a rollup of
all (or most of) the others? Is there a preference for whether other
modules should depend on the individual spec modules or the overall
"sp
