Re: [VOTE] Release Surefire 2.5 (take 3)
Stephen Connolly wrote: Staging repo: https://repository.apache.org/content/repositories/maven-034/ +1 Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Surefire 2.5 (take 3)
+1 Vincent 2010/1/13 Stephen Connolly stephen.alan.conno...@gmail.com: Hi, We solved 16 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=14119styleName=Html There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10541status=1 Staging repo: https://repository.apache.org/content/repositories/maven-034/ Staging site(s): http://maven.apache.org/plugins/maven-surefire-plugin-2.5/ http://maven.apache.org/plugins/maven-failsafe-plugin-2.5/ http://maven.apache.org/plugins/maven-surefire-report-plugin-2.5/ http://maven.apache.org/surefire/staging/ 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Surefire 2.5 (take 3)
+1 2010/1/13 Stephen Connolly stephen.alan.conno...@gmail.com: Hi, We solved 16 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=14119styleName=Html There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10541status=1 Staging repo: https://repository.apache.org/content/repositories/maven-034/ Staging site(s): http://maven.apache.org/plugins/maven-surefire-plugin-2.5/ http://maven.apache.org/plugins/maven-failsafe-plugin-2.5/ http://maven.apache.org/plugins/maven-surefire-report-plugin-2.5/ http://maven.apache.org/surefire/staging/ 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 -- Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
New Release Tree Maven Module
Hi I would like to write my first maven module that does releases over all the dependencies of a main module. I am interested in your opinion, recommondations and critical feedback. Let me first illustrate why I would like to do that. The maven-release-plugin does a release in a way that it: 1. Adds a tag to the repository for the main module 2. Releases al artifacts of the main module (JARs, website) 3. Deploys all artifacts of the main module to the remote repository (JARs for bitecode, sources and javadoc) 4. Allows to change the development versions of the dependent modules What I miss in this approach is: 1. The sites of all dependent modules (including test results and coverage, javadocs, dependencies) 2. Dependent modules artifacts in the repository (distinctly versioned JARs for bitecode, sources and javadoc) 3. Distinct versions of the dependent modules when copying all the needed libraries to the official website (say in a JNLP release) The idea of the new module would be to iterate through all dependent modules from dependency tree leaf towards its root and: 1. Investigate the existing tags on the SVN repository to find one for the dependent module 2. If the dependent module has code changes since the tags revision: 2a. Alter the POM dependent module so it reflects the dependencies to its dependent modules correctly by replacing SNAPSHOT versions with distinct tagged versions 2b. Release the dependent module 3. Else do not release the module but keep the tagged version as the one to replace SNAPSHOTs in subsequent dependent modules Let me illustrate that with a concrete example. Say I have the following multi-module project dependencies for my main module ch.xmatrix.ups.tools.ust (filtering out only my own dependencies): ch.xmatrix.ups.tools.ust 2.1-SNAPSHOT +- ch.xmatrix.ups.tools.common 2.0-SNAPSHOT | +- ch.xmatrix.common.utils-all 2.3-SNAPSHOT | | \- ch.xmatrix.common.icon1.4-SNAPSHOT | +- ch.xmatrix.ups.data.taxa 2.0-SNAPSHOT | \- ch.xmatrix.ups.data.constraints SNAPSHOT +- ch.xmatrix.ups.data.sessionsSNAPSHOT +- ch.xmatrix.ups.data.courses SNAPSHOT \- ch.xmatrix.ups.server.client2.0-SNAPSHOT \- ch.xmatrix.ups.server.interface 2.0-SNAPSHOT And there would be no current tag for ch.xmatrix.common.utils-all, ch.xmatrix.ups.data.constraints, ch.xmatrix.ups.server.interface and ch.xmatrix.ups.tools.ust without any changes in the meantime. I would like to be prompted for the desired development version change of each these remaining dependent modules. If I choose to keep the same development version, then the release order, the current development version would stay and the release version of this example would be: ch.xmatrix.common.utils-all 2.3-SNAPSHOT 2.3 ch.xmatrix.ups.data.constraints SNAPSHOT 1.0 ch.xmatrix.ups.server.interface 2.0-SNAPSHOT 2.0 ch.xmatrix.ups.tools.ust 2.1-SNAPSHOT 2.1 I currently achive that with a perl script. However, I wonder whether such a task would make sense to be done as a maven module (maven-releasetree-module). If it would make sense, I would see the following main limitation: My approach would use other maven modules like maven-dependency-modules and maven-release-module. Having had a quick look at the maven modules howto, this seem not to be a valid approach. Each module should be self-contained and independent of others. Any advices, recommondations, critical feedback, thoughts would be highly appreciated... Thanks for feedback in advance Daniel http://www.xmatrix.ch/ Daniel Frey Senior Software Engineerxmatrix Kellerweg 65 CH-8055 Zürich daniel.f...@xmatrix.ch http://www.xmatrix.ch http://www.xmatrix.ch/ tel: mobile: +41 (44) 241 64 46 http://www.plaxo.com/click_to_call?src=jj_signatureTo=%2B41+(44)+241+64+46 email=daniel.f...@xmatrix.ch +41 (77) 425 28 57 http://www.plaxo.com/click_to_call?src=jj_signatureTo=%2B41+(77)+425+28+57 email=daniel.f...@xmatrix.ch
Re: [VOTE] Release Surefire 2.5 (take 3)
+1 Hervé Le mercredi 13 janvier 2010, Stephen Connolly a écrit : Hi, We solved 16 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=14 119styleName=Html There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10541st atus=1 Staging repo: https://repository.apache.org/content/repositories/maven-034/ Staging site(s): http://maven.apache.org/plugins/maven-surefire-plugin-2.5/ http://maven.apache.org/plugins/maven-failsafe-plugin-2.5/ http://maven.apache.org/plugins/maven-surefire-report-plugin-2.5/ http://maven.apache.org/surefire/staging/ 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Surefire 2.5 (take 3)
+1 Nicolas 2010/1/16 Hervé BOUTEMY herve.bout...@free.fr +1 Hervé Le mercredi 13 janvier 2010, Stephen Connolly a écrit : Hi, We solved 16 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=14 119styleName=Html There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10541st atus=1 Staging repo: https://repository.apache.org/content/repositories/maven-034/ Staging site(s): http://maven.apache.org/plugins/maven-surefire-plugin-2.5/ http://maven.apache.org/plugins/maven-failsafe-plugin-2.5/ http://maven.apache.org/plugins/maven-surefire-report-plugin-2.5/ http://maven.apache.org/surefire/staging/ 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
a bit of help on MEAR-116
Hi guys, I am wondering if someone could have a look to the EarMojo to figure out if it contains a potential misuse of the API. The rationale behind it is MEAR-116[0]: artifacts are not resolved the same way through the reactor and from the project itself. Interesting code is probably in the AbstractEarMojo[1] Thanks, Stéphane [0] http://jira.codehaus.org/browse/MEAR-116 [1] http://maven.apache.org/plugins/maven-ear-plugin/xref/org/apache/maven/plugin/ear/AbstractEarMojo.html#208
Re: [ANNOUNCE] Doxygen Maven Plugin - Release 1.0
Hello to all, Unfortunately, i have to admit that the plugin is currently not in one of the Maven Repositories available... Now the Plugin is available via the following Maven Repository: http://mvn.supose.org The Maven generated site is available: http://site.supose.org/doxygen-maven-plugin/ If you have any questions concerning the Plugin don't hesitate to contact me Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
