Ben Alex wrote:
Carlos Sanchez wrote:
Hi,
I'd really encourage the use of two jars, core and core-tiger, instead
of packaging the tiger classes inside core jar, because the core-tiger
probably depends on core and you don't want core to depend on tiger.
You'll notice the problem of that approach in any tool with transitive
dependency resolution like Maven2, Ivy or any other.
Thanks Carlos
Given Carlos' advice, it seems to me like we should stick to separate
acegi-security-xx.jar and acegi-security-tiger-xx.jar files to
properly support transitive dependencies. Do others agree?
FWIW, for spring-webflow what Keith did based on my suggestion is split
off the annotations code into a separate spring-webflow-annotations.jar,
different from the normal spring-webflow.jar. What mostly drove this in
the Web Flow case was the need to build things differently (JDK 1.3 vs
JDK 1.5) as the source/target settings. In Web Flow we're using an
Ivy-based common build system, so it was trivial to do things like this
(just set a different property in the separate project), whereas it
would have been very hard to produce one combined jar or two separate
jars, from one project. I assume Maven presents some of the same issues.
In the case of Spring itself, it's easier because it's a totally custom
ant script that just produces two jars from two totally separate code
trees. When/if core Spring itself moves to the common-build system
itself, we'll probably also have ot split things out there for the same
reason.
Colin
--
Colin Sampaleanu
Interface21 Principal Consultant
Spring Training, Consulting and Support - "From the Source"
http://www.springframework.com
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Home: http://acegisecurity.sourceforge.net
Acegisecurity-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
