The natural progression of all this separation of config and implementation is that we will begin encouraging people to take all the resources out of their ears and deploy them in lib/, then just drop the dds into deploy/.
Ok, so they can edit their descriptors - but it's not J2EE, is it ? Likewise, the sar is a nice extension of the J2EE packaging metaphor. It may not be perfect, but this is the platform that we are implementing, and I think consistency is important. Comments ? Jules Scott M Stark wrote: > That is fine but why not just create a single jetty-service.jar that > includes all > Jetty specific files and have a seperate jetty-service.xml descriptor with > your > config that references the required jar: > <server> > <classpath codebase="." archives="jetty-service.jar"/> > ... > > This is how I'm packaging the tomcat service except there I also reference > the external catalina dist jars as well. > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > ----- Original Message ----- > From: "Jules Gosnell" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Cc: "Jan Bartel" <[EMAIL PROTECTED]> > Sent: Friday, May 31, 2002 4:31 PM > Subject: [JBoss-dev] Where should the Jasper jar live ? > > > >>Scott, >> >>Would you mind if I moved the jasper.jar from lib/ to jetty-plugin.sar ? >> >>I figure: >>- jasper is an implementation >>- jasper version is tightly bound to Jetty version >>- Tomcat users will have their own version of Jasper >> >>I think the servlet api jar should stay in lib, seeing as this is part >>of the definition of the JBoss platform and will be needed by users to >>compile against (whilst they should not need Jetty and Jasper classes) >> >>My preemptive advice to anyone concerned that a sar is awkward to work >>with, because the configuration is, hidden is : "run it unpacked". >> >>Concerns ? >> >> >>Jules >> >>P.S. >> >>What is the arrangement between HEAD and Branch_3_0 - would I be >>correct in assuming that bug-fixes should be merged, but new features >>not ? >> >> >> >>_______________________________________________________________ >> >>Don't miss the 2002 Sprint PCS Application Developer's Conference >>August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm >> >>_______________________________________________ >>Jboss-development mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/jboss-development >> > > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
