From open-jpa-dev-return-489-apmail-incubator-open-jpa-dev-archive=incubator.apache.org@incubator.apache.org Thu Aug 24 05:42:16 2006 Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 63834 invoked from network); 24 Aug 2006 05:42:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Aug 2006 05:42:16 -0000 Received: (qmail 28105 invoked by uid 500); 24 Aug 2006 05:42:16 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 28079 invoked by uid 500); 24 Aug 2006 05:42:16 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 28067 invoked by uid 99); 24 Aug 2006 05:42:16 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Aug 2006 22:42:16 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of david.blevins@visi.com designates 208.42.156.2 as permitted sender) Received: from [208.42.156.2] (HELO conn.mc.mpls.visi.com) (208.42.156.2) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Aug 2006 22:42:15 -0700 Received: from [10.0.1.2] (68-171-58-68.vnnyca.adelphia.net [68.171.58.68]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by conn.mc.mpls.visi.com (Postfix) with ESMTP id F2AC98384; Thu, 24 Aug 2006 00:41:53 -0500 (CDT) In-Reply-To: <44ECE2C6.8080404@gmail.com> References: <7D856CDFE035FF45A0420ACBD71BDD6301B91E88@repbex02.amer.bea.com> <11A2FAE5-494A-435D-A19F-C84C9178D502@SUN.com> <6CD2E70B-EDF2-435A-9D0A-57084B10DA38@visi.com> <44ECE2C6.8080404@gmail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <27A5DD00-72FE-4A43-8686-34C331471B3F@visi.com> Cc: Brett Porter Content-Transfer-Encoding: 7bit From: David Blevins Subject: Re: Update version to SNAPSHOT Date: Wed, 23 Aug 2006 22:41:45 -0700 To: open-jpa-dev@incubator.apache.org X-Mailer: Apple Mail (2.752.2) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Aug 23, 2006, at 4:20 PM, Bryan Noll wrote: > So... I saw that David created the following two JIRA's, so I > wanted to follow up on the thread. > > http://issues.apache.org/jira/browse/OPENJPA-29 > http://issues.apache.org/jira/browse/OPENJPA-30 > > > Regarding OPENJPA-29: > > openjpa-0.9.0-full.jar // contains all openjpa code, openjpa- > *.jars merged > openjpa-0.9.0-nodep.jar // contains all openjpa code and all third > party dependency jars > > Do you have your descriptions backwards or am I misunderstanding > what you're saying? I very well could have them backwards. As I said, "There's a naming convention for this kind of thing, hope I've got it right." > Seems like 'nodep' would mean "no dependencies for this project are > bundled into this jar" to me. > IIUC (which I'm not sure that I do, so please correct me) then... > > openjpa-0.9.0-nodep.jar would extract to: > - org/apache/openjpa/*/**.class > - META-INF/* ............ (we still need to resolve the 'merge > multiple files of the same name and locations (eg.. > ProductDerivations) problem for this) > > openjpa-0.9.0-full.jar would extract to: > - org/apache/openjpa/*/**.class > - thirdPartyJars.jar (many of these) > - META-INF/* .......... (same issue as above) The classes from the third party jars would also have been extracted into the jar. > Would the openjpa-*.jar files be there instead of the unpacked > classes? Classes. > Should the names actually be openjpa-nodep-0.9.0-SNAPSHOT.jar and > openjpa-full-0.9.0-SNAPSHOT.jar? That'd be possible. You'd have to have one maven module for each jar and poke at the assembly plugin setup to not use the default name of --.. The maven guys may know a better way. > > Regarding OPENJPA-30: > > - I saw that Marc got the newly named SNAPSHOT jars up to a > repo.... good stuff. Yep. Thanks again, Marc! Very appreciated! > - The next step would have one jar somewhere like http:// > people.apache.org/repo/m2-snapshot-repository/org/apache/openjpa/ > openjpa/0.9.0-SNAPSHOT/ for people to depend on, instead of many, > correct? We (Geronimo and OpenEJB) use maven 2 which has transitive dependencies, so it's not critical for us. But it'd be real handy for anyone using maven 1 or ant. Or anyone really who just wants to throw that jar in their webapp and say "go!" > - David... if you catch this... I would be glad to help > (translation... observe and learn) you get the thing publishing > nightly from the apache continuum server you spoke of. I added it in (that's the easy part). See http://vmbuild.apache.org/ continuum/servlet/continuum That machine is terribly slow.... The tricky part with any CI system is the whole question of "Gee, what credentials do we use to deploy snapshots?" To skirt the issue of what user to "push" jars as, I've typically setup an rsync on the destination box and "pulled" the jars down. That worked fine with maven 1, but maven 2 has these wonderful index files in the repo that make that impossible to my knowledge. Maybe Brett can confirm. -David > > > Thanks... > > Bryan > > > David Blevins wrote: >> >> On Aug 15, 2006, at 7:42 AM, Craig L Russell wrote: >> >>> >>> On Aug 15, 2006, at 6:38 AM, Patrick Linskey wrote: >>> >>>>> Check out the Assembly plugin and it's predefined >>>>> "jar-with-dependencies" descriptor[1]. I'm pretty sure that >>>>> most people >>>>> using Maven will just have a runtime dependency on the core >>>>> OpenJPA >>>>> library and be done with it, but it's always nice for Ant users. >>>> >>>> Exactly -- mvn users will use the dependencies, but people who >>>> want to >>>> download and use the distribution directly may not want a >>>> billion little >>>> jars. >>> >>> Yes, my experience says it's ok to have 10 dependencies on e.g. >>> commons-logger, antlr, etc. but having 10 dependencies on openjpa- >>> kernel4, openjpa-kernel5, openjpa-api, openjpa-blah is annoying. >>> >>> So if possible, I'd also like to have a jar with all the stuff in >>> it. >> >> That'd be nice. Some jar that contains all the openjpa-*.jar >> files is perfect for my needs. The good news is that the maven- >> assembly-plugin allows you to define several assembly xml files >> and build multiple archives containing whatever you like. So if >> people want, we could have: >> >> openjpa-0.9.0-full.jar // contains all openjpa code, openjpa- >> *.jars merged >> openjpa-0.9.0-nodep.jar // contains all openjpa code and all >> third party dependency jars >> >> There's a naming convention for this kind of thing, hope I've got >> it right. >> >> -David >> >>> >>> Craig >>>> >>>> -Patrick >>>> ___________________________________________________________________ >>>> ____ >>>> Notice: This email message, together with any attachments, may >>>> contain >>>> information of BEA Systems, Inc., its subsidiaries and >>>> affiliated >>>> entities, that may be confidential, proprietary, copyrighted >>>> and/or >>>> legally privileged, and is intended solely for the use of the >>>> individual >>>> or entity named in this message. If you are not the intended >>>> recipient, >>>> and have received this message in error, please immediately >>>> return this >>>> by email and then delete it. >>> >>> Craig Russell >>> Architect, Sun Java Enterprise System http://java.sun.com/ >>> products/jdo >>> 408 276-5638 mailto:Craig.Russell@sun.com >>> P.S. A good JDO? O, Gasp! >>> >> >> >