From open-jpa-dev-return-3755-apmail-incubator-open-jpa-dev-archive=incubator.apache.org@incubator.apache.org Wed Apr 25 02:54:21 2007 Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 36848 invoked from network); 25 Apr 2007 02:54:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Apr 2007 02:54:20 -0000 Received: (qmail 13317 invoked by uid 500); 25 Apr 2007 02:54:27 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 13190 invoked by uid 500); 25 Apr 2007 02:54:27 -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 13181 invoked by uid 99); 25 Apr 2007 02:54:27 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2007 19:54:27 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of mprudhomapache@gmail.com designates 64.233.162.233 as permitted sender) Received: from [64.233.162.233] (HELO nz-out-0506.google.com) (64.233.162.233) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2007 19:54:19 -0700 Received: by nz-out-0506.google.com with SMTP id j2so88634nzf for ; Tue, 24 Apr 2007 19:53:59 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=MHfYD7BAKiTdGwacFPJD0oMGV2713vJeOdL1EYVAgRXiUZdCsv+QjaB5LiTnbabtBdAimDeGWXPbESHN+C1c+NB5+PJ0xa7ikDXd1XqEvitdC6MtsDsYbOePoAF577h+Iw0JaA6q12fdpKM2xXfIENPGFErYZzJ5wtWheWs/Mf0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=aN7GPyYxbulsLlyhHZDmoypdiQnUAI8FN4XRhnG4Xt/W00EunyP+WurtJPqYHvR557LC1oTUya2CtiIVNsiVTJKnnYApiOkQxNubg7WOiaJhgVxLDoKM+VlYyx2kaIP6yKy6d30+Y6ywzotQ8zKFISuB1DQeb20XwOEIVQM+ONA= Received: by 10.115.106.7 with SMTP id i7mr86075wam.1177469638564; Tue, 24 Apr 2007 19:53:58 -0700 (PDT) Received: from ?192.168.15.104? ( [67.189.29.203]) by mx.google.com with ESMTP id q20sm627020pog.2007.04.24.19.53.57; Tue, 24 Apr 2007 19:53:58 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <7D856CDFE035FF45A0420ACBD71BDD630401B2F5@repbex02.amer.bea.com> References: <72c1350f0704110834r65770cdbtb1b03ba0870e18cb@mail.gmail.com> <72c1350f0704241239k67ab9100t1fcec95e110bdf01@mail.gmail.com> <7D856CDFE035FF45A0420ACBD71BDD630401B2EE@repbex02.amer.bea.com> <7D856CDFE035FF45A0420ACBD71BDD630401B2F5@repbex02.amer.bea.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <75526BA3-D048-4FFC-A66A-647C7E950D72@apache.org> Content-Transfer-Encoding: 7bit From: Marc Prud'hommeaux Subject: Re: Artifact names Date: Tue, 24 Apr 2007 19:53:44 -0700 To: open-jpa-dev@incubator.apache.org X-Mailer: Apple Mail (2.752.3) Sender: Marc Prud'hommeaux X-Virus-Checked: Checked by ClamAV on apache.org > It's just a bit odd to have the '-all' bit in there. Is it possible to > make the top-level pom publish the same stuff that openjpa-all > currently > does? Not that I've ever been able to figure out. IIRC, a parent project is not allowed to depend on child modules, and a child module is not allowed to rename the artifact that it publishes. On Apr 24, 2007, at 7:40 PM, Patrick Linskey wrote: >>> I do think that we should have something that's easy to >> depend on that >>> pulls in the openjpa-persistence-jdbc module, without making people >>> have to know about that level of modularity detail. >> >> Why can't they just depend on openjpa-all? That brings >> everything in... > > It's just a bit odd to have the '-all' bit in there. Is it possible to > make the top-level pom publish the same stuff that openjpa-all > currently > does? > > -Patrick > > -- > Patrick Linskey > BEA Systems, Inc. > ______________________________________________________________________ > _ > 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. > >> -----Original Message----- >> From: Marc Prud'hommeaux [mailto:mprudhomapache@gmail.com] On >> Behalf Of Marc Prud'hommeaux >> Sent: Tuesday, April 24, 2007 7:37 PM >> To: open-jpa-dev@incubator.apache.org >> Subject: Re: Artifact names >> >> >> On Apr 24, 2007, at 7:27 PM, Patrick Linskey wrote: >> >>> Hmm. I wonder if we're really using Maven repositories correctly. >>> Do we >>> need our dist to be in Maven at all? >> >> We don't need to. It was just easy to set up that way. >> >> >>> I do think that we should have something that's easy to >> depend on that >>> pulls in the openjpa-persistence-jdbc module, without making people >>> have to know about that level of modularity detail. >> >> Why can't they just depend on openjpa-all? That brings >> everything in... >> >> >> >>> -Patrick >>> >>> -- >>> Patrick Linskey >>> BEA Systems, Inc. >>> >> _____________________________________________________________________ >> _ >>> _ >>> 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. >>> >>>> -----Original Message----- >>>> From: Eddie O'Neil [mailto:ekoneil@gmail.com] >>>> Sent: Tuesday, April 24, 2007 7:05 PM >>>> To: open-jpa-dev@incubator.apache.org >>>> Subject: Re: Artifact names >>>> >>>> >>>> +1 -- I'd prefer to have the binary / source >> uber-archives outside >>>> of the Maven repro, though that's more due to convention than >>>> anything else. >>>> >>>> I agree that it's not worth worrying about this for 0.9.7. >>>> >>>> Cheers, >>>> Eddie >>>> >>>> >>>> On 4/24/07, Michael Dick wrote: >>>>> I'm finally getting back to this thread, sorry for the delay. >>>>> >>>>> I got a similar answer from the maven mailing list. Their >> stance is >>>>> that the maven repository is for artifacts which are used >> by maven, >>>>> which wouldn't be the same as a final destination for our >>>> distribution. >>>>> >>>>> I'm in favor of moving the source and binary archives to a >>>> different >>>>> location, if there's a good spot available to us. Does >>>> anyone object >>>>> to putting the releases somewhere outside of a maven repository? >>>>> >>>>> I don't think this is urgent for the 0.9.7 release since we >>>> can't get >>>>> rid of the ugly -project names now, but it might be nice >> to have a >>>>> solution for when OpenJPA graduates. >>>>> >>>>> On 4/12/07, Dain Sundstrom wrote: >>>>>> >>>>>> In Geronimo, we publish to the maven repo as maven likes, >>>> but when >>>>>> we publish to the apache distribution mirrors (for website >>>>>> downloads), we name the files as we like. >>>>>> >>>>>> -dain >>>>>> >>>>>> On Apr 11, 2007, at 8:34 AM, Michael Dick wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I'm hitting a bit of a snag with the staging repository for >>>>>>> release 0.9.7. >>>>>>> Recently we made changes to remove -project from our >>>> the zip file >>>>>>> names. The problem is that the maven install and deploy goals >>>>>>> ignore the names we provide and generate their own names ( >>>>>>> openjpa-project-0.9.7-incubating-xxx.zip). >>>>>>> >>>>>>> I searched through the users@maven.apache.org mailing list >>>>>>> archives and it turns out this is a fairly common problem - >>>>>>> usually resulting in a response of "working as >>>> designed". Here's >>>>>>> an example >>>>>>> http://www.nabble.com/Installation-and-deployment- >>>>>>> tf1449780s177.html#a3916784 >>>>>>> >>>>>>> Does anyone vehemently object to putting -project back into the >>>>>>> names for the 0.9.7 release? >>>>>>> >>>>>>> The only other way I know of to fix the names that get deployed >>>>>>> would be to change the artifactId in the pom files (basically >>>>>>> switch openjpa with openjpa-project). Switching the names will >>>>>>> impact anyone who has a dependency on the base openjpa project. >>>>>>> They'll have to update the version number anyway, but it will >>>>>>> still be a little confusing if they used to depend on >>>>>>> openjpa-0.9.6 and now they depend on openjpa-project-0.9.7. >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> -- >>>>>>> -Michael Dick >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> -Michael Dick >>>>> >>>> >>> >>> 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. >> >> > > 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.