Re: [VOTE] Release Apache Maven 3.0-alpha-5
On Thu, Dec 3, 2009 at 7:44 PM, Brian Fox bri...@infinity.nu wrote: Something like duplicate dependencies likely means you have a real problem you didn't know about in your poms. I think failing is appropriate in this case. I fail to grok what you just said there. So if i have in my pom dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency and then 25 other dependencies and then again the one above (due to a copy-paste oversight let's say) then I have a real problem in my build you say. How is it different from unused and declared dependencies, or used and undeclared ? For me these all fit in the same boat ie 'potential build optimizations' Jorg PS how about a dependency:scan-duplicates then ? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
MNG-4479 updated with reproducible test case
Hello; a quick note to say that I've updated http://jira.codehaus.org/browse/MNG-4479 with a set of projects that reliably reproduce the (IMHO major) issue. Best, Laird
Re: [VOTE] Release Maven Changes Plugin version 2.3
Benjamin Bentmann wrote: Dennis Lundberg wrote: This vote comes soon after the 2.2 release No need to apologize ;-) Staging repo: https://repository.apache.org/content/repositories/maven-036/ The .pom.asc seems not to match the plugin POM [0]. Looking at the POM, it seems as if it was deployed using Maven 2.1.0 and suffers from MNG-4167/MGPG-14. Darn, you're probably right. I must have switched to 2.1 too soon. Is there one recommended version of Maven that works for both for the deployment of artifacts and the site deployment? I'd like to stay on Java 1.4 when doing plugin releases. What's the best approach to fixing the signatures? Is it possible to re-sign the artifacts and just upload the new signatures? If so, what steps would I need to take. Benjamin [0] https://repository.apache.org/content/repositories/maven-036/org/apache/maven/plugins/maven-changes-plugin/2.3/maven-changes-plugin-2.3.pom - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Changes Plugin version 2.3
On Fri, Dec 4, 2009 at 9:13 PM, Dennis Lundberg denn...@apache.org wrote: Benjamin Bentmann wrote: Dennis Lundberg wrote: This vote comes soon after the 2.2 release No need to apologize ;-) Staging repo: https://repository.apache.org/content/repositories/maven-036/ The .pom.asc seems not to match the plugin POM [0]. Looking at the POM, it seems as if it was deployed using Maven 2.1.0 and suffers from MNG-4167/MGPG-14. Darn, you're probably right. I must have switched to 2.1 too soon. Is there one recommended version of Maven that works for both for the deployment of artifacts and the site deployment? I'd like to stay on Java 1.4 when doing plugin releases. What's the best approach to fixing the signatures? Is it possible to re-sign the artifacts and just upload the new signatures? If so, what steps would I need to take. I had exactly the same problem with the release of doxia 1.1.1 ( http://www.mail-archive.com/dev@maven.apache.org/msg81138.html), I sent the correct signatures to Brian who was so nice to replace them on the staging repo. So it is possible... :) -Lukas Benjamin [0] https://repository.apache.org/content/repositories/maven-036/org/apache/maven/plugins/maven-changes-plugin/2.3/maven-changes-plugin-2.3.pom - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Ant Tasks version 2.1.0
Hi, The vote has passed with the following result: +1 (binding): Benjamin Bentmann, Jason van Zyl, Hervé Boutemy +1 (non-binding): Paul Gier, Stephen Connolly I will promote the artifacts to the central repository and continue with the release. Paul Gier wrote: Hi, I believe it's time for the next release of the Maven Ant Tasks. This release has several enhancements and bug fixes and the dependencies on the core maven libraries have been updated to version 2.2.1. I also created a download page as part of the Ant tasks site. This will allow the Ant task download links to be removed from the main Maven download page. We solved 12 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533version=13522 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+MANTTASKS+AND+status+%3D+Open+ORDER+BY+priority+DESCmode=hide Staging repo: https://repository.apache.org/content/repositories/maven-033/ Staging site (need to sync): http://maven.apache.org/ant-tasks-2.1.0/ SCM Tag: https://svn.apache.org/repos/asf/maven/ant-tasks/tags/maven-ant-tasks-2.1.0 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Changes Plugin version 2.3
2.2.1 is recommended in the release guide now (mostly because the wagon upgrade is necessary to work with scp). I think we should solve the concern about building with JDK 1.4 a different way (toolchains, and/or animal sniffer). Cheers, Brett On 05/12/2009, at 7:13 AM, Dennis Lundberg wrote: Benjamin Bentmann wrote: Dennis Lundberg wrote: This vote comes soon after the 2.2 release No need to apologize ;-) Staging repo: https://repository.apache.org/content/repositories/maven-036/ The .pom.asc seems not to match the plugin POM [0]. Looking at the POM, it seems as if it was deployed using Maven 2.1.0 and suffers from MNG-4167/MGPG-14. Darn, you're probably right. I must have switched to 2.1 too soon. Is there one recommended version of Maven that works for both for the deployment of artifacts and the site deployment? I'd like to stay on Java 1.4 when doing plugin releases. What's the best approach to fixing the signatures? Is it possible to re-sign the artifacts and just upload the new signatures? If so, what steps would I need to take. Benjamin [0] https://repository.apache.org/content/repositories/maven-036/org/apache/maven/plugins/maven-changes-plugin/2.3/maven-changes-plugin-2.3.pom - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0-alpha-5
On Fri, Dec 4, 2009 at 2:16 AM, Jorg Heymans jorg.heym...@gmail.com wrote: On Thu, Dec 3, 2009 at 7:44 PM, Brian Fox bri...@infinity.nu wrote: Something like duplicate dependencies likely means you have a real problem you didn't know about in your poms. I think failing is appropriate in this case. I fail to grok what you just said there. So if i have in my pom dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency and then 25 other dependencies and then again the one above (due to a copy-paste oversight let's say) then I have a real problem in my build you say. How is it different from unused and declared dependencies, or used and undeclared ? Yes that is a problem because if you later go to upgrade to 1.2, you're most likely going to find the first instance and change it, but you're still going to get 1.0 because last time I checked, it was last wins. This is a hidden cancer in your pom that will bite you later. How is it different than undeclared dependencies? It's slightly worse because you have a false sense of security by having it specified. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Upload Apache Pivot artifacts to central repository?
Hi Brian, I managed to install the Pivot artifacts in a local Maven repository and successfully built a sample project that lists them as dependencies. So, I am optimistic that the POMs are structured correctly. Next, I attempted to package the artifacts for manual upload as described on this page: http://maven.apache.org/guides/mini/guide-central-repository-upload.html The results are in this zip file, which contains one JAR per Pivot artifact: http://ixnay.biz/pivot-bundles.zip Would it be possible for you to take a quick look and verify that they are in the correct format for manual upload? If so, what would be the next steps to get them into the central repository? Is there still a way for Apache projects to do this without needing to go through the 4-week process described on the upload page? If not, that's OK - I'm just wondering. (Note that the artifacts themselves are not actually ready for upload - I am just trying to get the process worked out in anticipation of Pivot's graduation. The final artifacts for Pivot 1.4 probably won't be ready for another few weeks.) Thanks again for your help, Greg On Dec 3, 2009, at 11:27 AM, Brian Fox wrote: Hi Greg, I'll take a look later today and ping back on the pivot dev list with what I find. On Thu, Dec 3, 2009 at 6:44 AM, Greg Brown gkbr...@mac.com wrote: Forwarding this message to dev@maven.apache.org in case us...@maven.apache.org wasn't the right place. Also, since sending the original message, I have heard that the document I had been referring to might be outdated. Can anyone help? Thanks! Greg Begin forwarded message: From: Greg Brown gkbr...@mac.com Date: December 2, 2009 12:38:13 PM EST To: us...@maven.apache.org Cc: pivot-...@incubator.apache.org Subject: Upload Apache Pivot artifacts to central repository Reply-To: pivot-...@incubator.apache.org Hi all, Apache Pivot is preparing for graduation, and we would like to upload our next set of release artifacts to the central Maven repository. We don't currently use Maven as a build tool, so I have been trying to follow the manual upload instructions listed here: http://www.apache.org/dev/release-publishing.html#maven-repo There is a section at the bottom that is meant to explain how to create an appropriate POM file, but it does not appear to be complete: http://www.apache.org/dev/release-publishing.html#repository-descriptor I have created some POMs that I think should work, but it would be very helpful if someone with a knowledgeable eye could take a quick look to make sure that they contain the correct information, are structured properly, etc. There is a root POM in the trunk, and a POM in each project-specific subdirectory that we plan to publish to the repository (note that these files refer to the anticipated future name and location of the project, as opposed to its current Incubator name and location): http://svn.apache.org/repos/asf/incubator/pivot/trunk/ Based on the documentation I have read thus far, I assume that we'll want to place our compiled JARs in a pivot/jars directory, and structure our POMs as follows: pivot/poms pom.xml /core/pom.xml /web/pom.xml /wtk/pom.xml /wtk-terra/pom.xml I don't think we'll need to use the distributions directory, and I assume that the licenses directory should simply contain a copy of our main LICENSE file. Is this all correct? Also, one of our mentors, Martijn Dashorst, suggested that there might be a top-level ASF POM that the root Pivot POM could extend (rather than duplicating the ASF info). If so, could you point us to it? Thanks - your assistance is very much appreciated! Greg Brown Apache Pivot - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
