> Does anyone vehemently object to putting -project back into > the names for > the 0.9.7 release?
I don't vehemently object for the 0.9.7 release, but I do vehemently object for the 1.0 release. I don't like these random bugs / limitations of our build process making their way into the project artifacts. > 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-tf1449780s17 > 7.html#a3916784 Any chance that we can convince the people involved that while it may be working as designed, it's a common difficulty? -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: Michael Dick [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 11, 2007 8:34 AM > To: open-jpa-dev@incubator.apache.org > Subject: Artifact names > > 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-tf1449780s17 > 7.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 > 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.
