RE: Question about new release

Yes, I suppose that might be prudent.... except that it should only include 
barracuda-core.jar and plankton.jar rather than also including the contents 
of all jars such as admin, config, examples, testbed, and tutorials, and 
the taskdefs.  barracuda.jar should just be the runtime libraries.  Is this 
what you have in mind?  If people really want to add stuff like the admin 
or config app to their project, they can add the specific jars.

Jake

At 08:17 AM 5/28/2003 -0600, you wrote:
> > I think the single jar is simpler to deal with and causes less
> > confusion that using individual jars.... especially the xerces
> > jar which isn't "really* xerces for all intents and purposes.
> > This just caused needless confusion.  The fact is, xmlc's xerces
> > library is for xmlc's internal use only.
>
>Yes, I agree, actually.
>
>Along these lines, I think we ought to reconsider making a single
>barracuda.jar that combines the core and plankton stuff needed for
>runtime...we can actually do this right now, using the jars.master taskdef -
>it creates a single barracuda.jar, but it just leaves it in /lib-cvs, rather
>than deploying inot /lib. We deploy all of our webapps using that single jar
>just because fewer jars seems to make it easier to keep track of. I suspect
>most people would probably prefer this (and we could still build the
>barracuda-core.jar and plankton.jar in /lib-cvs...just not deploy them).
>
>Anyway...just a thought...not a burning issue or anything.
>
>Christian
>
>----------------------------------------------
>Christian Cryder [[email protected]]
>Internet Architect, ATMReports.com
>Barracuda - http://barracudamvc.org
>----------------------------------------------
>"Coffee? I could quit anytime, just not today"
>
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]]On Behalf Of Jacob Kjome
> > Sent: Tuesday, May 27, 2003 7:43 PM
> > To: [email protected]
> > Subject: Re: [Barracuda] Question about new release
> >
> >
> >
> > almost.  Here's the actual list...
> >
> > wireless
> > xhtml
> > xmlc
> > xerces
> >
> > Xalan has nothing to do with the XMLC stuff.   And note that
> > xmlc-taskdef is still a separate jar as it isn't part of the xmlc
> > runtime libraries.
> >
> > The reason why I did this is twofold...
> >
> > 1.  XMLC's xerces libraries were moved into the
> > org.enhydra.apache.xerces namespace which hides it from other
> > versions of Xerces such as the ubiquitous Xerces2 that comes, by
> > default, with Ant, Tomcat, and lots of other packages.
> >
> > 2.  #1 is great, but there were still endorsed package such as
> > javax.xml.*, org.w3c.dom.*, and org.xml.* that existed in the
> > xerces jar.  This is a problem in webapps because it is against
> > the Sun classloader spec and the servlet spec to load endorsed
> > packages from a child classloader (ie... the WebappClassLoader).
> > XMLC beta1 was released with these endorsed packages still
> > included in the xerces.jar file.  I decided that there was no
> > need for this and removed the endorsed packages.  This makes
> > XMLC's xerces libraries totally free of any classloader issues.
> > As such, the xmlc-runtime jar file is able to be added directly
> > into WEB-INF/lib which makes deploying Barracuda an absolute
> > no-brainer now that there is no extra copy-step (ie... copying
> > xerces.jar to CATALINA_HOME/shared/lib).
> >
> > Now, you may say "isn't this what we were trying to get away from
> > before...an integrated jar file that might collide with existing
> > jars"?  Well, that used to be the case, but now since the single
> > xmlc-runtime jar file no longer contains libraries that would
> > conflict with anything else out there, this is not an issue.
> > "But, now I have this big jar."  "What if I don't need wireless
> > and xhtml libraries"?  Well, for one, they are very small parts
> > of the xmlc-runtime jar file and secondly, you can switch out the
> > xmlc-runtime for individual jars in the xmlc distribution
> > (currently under XMLC's CVS with the tag
> > "XMLC_2_2_POST_BETA_1_BARRACUDA_1_2_0").
> >
> > I think the single jar is simpler to deal with and causes less
> > confusion that using individual jars.... especially the xerces
> > jar which isn't "really* xerces for all intents and purposes.
> > This just caused needless confusion.  The fact is, xmlc's xerces
> > library is for xmlc's internal use only.
> >
> > One thing you need to make sure of is that the JAXP, DOM, and SAX
> > libraries exist in the classpath.  This is usually provide by
> > Xerces and the xmlParserAPIs.jar or xml-apis.jar that it comes
> > with.  So, if you didn't have these in ANT_HOME/lib and
> > CATALNIA_HOME/common/endorsed, you definitely should now.
> >
> > Hopefully that clears things up.
> >
> > Jake
> >
> >
> > At 03:53 PM 5/27/2003 -0600, you wrote:
> >
> > Hey Jake, it looks like there's been some consolidation of jars in the
> > Barracuda WEB-INF/jars directory...can you confirm that
> >
> > /WEB-INF/jars/wireless-xmlc-2.2.jar
> > /WEB-INF/jars/xalan-2.5.0.jar
> > /WEB-INF/jars/xhtml-xmlc-2.2.jar
> >
> > have all been collapsed into
> >
> > /WEB-INF/jars/xmlc-all-runtime-2.2.jar
> >
> > Thanks,
> > Christian
> > ----------------------------------------------
> > Christian Cryder [[email protected]]
> > Internet Architect, ATMReports.com
> > Barracuda - http://barracudamvc.org
> > ----------------------------------------------
> > "Coffee? I could quit anytime, just not today"
> >
> > _______________________________________________
> > Barracuda mailing list
> > [email protected]
> > http://barracudamvc.org/lists/listinfo/barracuda
>
>_______________________________________________
>Barracuda mailing list
>[email protected]
>http://barracudamvc.org/lists/listinfo/barracuda