I'm curious - are you checking in the binaries to your SCM and building against that? Is it not possible to download and extract the zip at build time?
On Wed, Feb 6, 2013 at 5:48 PM, Alex The Rocker <[email protected]>wrote: > Okay great, so as I understand it we can renamed ourselves the .jar to > versionless names, so TomEE+ won't care and it will be fine for our upgrade > process. > > Thanks you very much !! > > Alex > > > On Wed, Feb 6, 2013 at 11:44 PM, Romain Manni-Bucau > <[email protected]>wrote: > > > TomEE respects Tomcat classloading. If you kept default settings it is > > something like: > > > > classpath = bin/bootstrap.jar + bin/tomcat-juli.jar > > | > > |- common.loader = lib/*.jar > > | > > ` webapp = web-inf/lib + web-inf/classes > > > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > *Github: https://github.com/rmannibucau* > > > > > > > > 2013/2/6 Alex The Rocker <[email protected]> > > > > > Okay I understand versions in TomEE jars are here to stay. > > > Our installer is not a public one. > > > How about my other questions : how TomEE knows which .jar files must be > > > loaded? does it "scans" the lib/ directory? > > > Can we safely rename TomEE's .jar files without changing anything else? > > > > > > thanks, > > > Alex. > > > > > > > > > On Wed, Feb 6, 2013 at 11:34 PM, Romain Manni-Bucau > > > <[email protected]>wrote: > > > > > > > if you keep multiple versions all will be broken (excepted if you are > > > lucky > > > > but i'd not bet on it) > > > > > > > > you can remove the version in your process no? > > > > > > > > Tomcat and TomEE are different because Tomcat doesn't rely on > external > > > > libraries (they either forked or rewrote everything) so they can > manage > > > > easily their deps. TomEE relies on external deps so keeping the > version > > > is > > > > mandatory for production and it is nice in prod. > > > > > > > > what you call fix pack is a public installer (i dont know it)? i > think > > > the > > > > work should be done here and not on TomEE. > > > > > > > > To be honest you are the first one saying you dont want version and i > > > heard > > > > a bunch of time tomcat sould put them :p > > > > > > > > my 2cts... > > > > > > > > *Romain Manni-Bucau* > > > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > > > *Blog: **http://rmannibucau.wordpress.com/*< > > > > http://rmannibucau.wordpress.com/> > > > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > > > *Github: https://github.com/rmannibucau* > > > > > > > > > > > > > > > > 2013/2/6 Alex The Rocker <[email protected]> > > > > > > > > > Thanks all for your answers, and for your questions which mean my > > > > question > > > > > wasn't clear. > > > > > Here's the scenario: > > > > > - We don't built ourselves TomEE+ > > > > > - Our product "GA" = Generally Available version embeds TomEE+ > 1.5.1+ > > > > > release (not a snapshot) > > > > > - Our next fix pack will embedded TomEE 1.5.2 release (not a > > snapshot, > > > > only > > > > > "GA" = "Generally Available" version). > > > > > - Our products fix pack installer doesn't know that files not part > of > > > > > fixpack must be deleted > > > > > - So for our customers having installed our product, they will have > > in > > > > > TomEE+ lib/ directory this mix: > > > > > lib/openejb-api-4.5.1.jar > > > > > lib/openejb-api-4.5.2.jar > > > > > lib/openejb-client-4.5.1.jar > > > > > lib/openejb-client-4.5.2.jar > > > > > lib/openejb-core-4.5.1.jar > > > > > lib/openejb-core-4.5.2.jar > > > > > ... etc ... > > > > > > > > > > My questions: > > > > > a) beyond eating up some disk space, will this "mixup" of JAR > > > versions > > > > > break Apache TomEE+ runtime? > > > > > b) Is TomEE+ relying on a CLASSPATH referencing the exact name of > > > each > > > > > JAR in lib/ directory? if not, how does it load its jar files? > > > > > c) if the answer to my problem is to rename the .jar file before > > > > checking > > > > > out them into our own source code control system before building > our > > > > > service packs, then do we need to update references to these .jar > > files > > > > and > > > > > if yes where? > > > > > d) any hope to have versionless .jar file, like Tomcat has in its > > own > > > > > lib/ directory? why deviating from Tomcat habits? > > > > > > > > > > Thanks, > > > > > Alex. > > > > > > > > > > > > > > > > > > > > On Wed, Feb 6, 2013 at 8:41 PM, Howard W. Smith, Jr. < > > > > > [email protected] > > > > > > wrote: > > > > > > > > > > > +1 to Jesse's response. > > > > > > > > > > > > As a user, i have no issues with JAR filenames, and plus, I don't > > > > > download > > > > > > a new version 'every day'. I usually only download a JAR from > > > snapshot > > > > > > repository folder...every now and then, unless I see/hear > something > > > in > > > > > > issue/mail list that motivates me to download latest snapshot. :) > > > > > > > > > > > > > > > > > > On Wed, Feb 6, 2013 at 11:38 AM, Jesse Farinacci < > [email protected] > > > > > > > > wrote: > > > > > > > > > > > > > Greetings, > > > > > > > > > > > > > > On Wed, Feb 6, 2013 at 11:09 AM, Alex The Rocker < > > > > [email protected] > > > > > > > > > > > > > wrote: > > > > > > > > Could TomEE have versionless JAR files naming? > > > > > > > > > > > > > > As a user, I would -1 to this change request as it is fairly > > > dramatic > > > > > > > packaging change. It would possibly break all the existing > > > consumers. > > > > > > > > > > > > > > -Jesse > > > > > > > > > > > > > > -- > > > > > > > There are 10 types of people in this world, those > > > > > > > that can read binary and those that can not. > > > > > > > > > > > > > > > > > > > > > > > > > > > >
