[ANN] Maven Dependency Plugin 2.6 Released
The Apache Maven team is pleased to announce the release of the Maven Dependency Plugin, version 2.6 The dependency plugin provides the capability to manipulate artifacts. It can copy and/or unpack artifacts from local or remote repositories to a specified location. http://maven.apache.org/plugins/maven-dependency-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-dependency-plugin 2.6 Release Notes - Maven Dependency Plugin - Version 2.6 ** Bug * [MDEP-122] - Analyze target does not work correctly when only using a constant defined in a different module * [MDEP-124] - Dependency incorrectly reported as "Unused declared" * [MDEP-176] - excludes not considered in analyze? * [MDEP-205] - type configuration ignored in sources goal * [MDEP-253] - Purge does not purge released artifacts * [MDEP-256] - invoking purge-local-repository leads to deletion of %JDK_HOME%/lib/tools.jar * [MDEP-272] - purge-local-repository does nothing if certain dependencies are included * [MDEP-298] - mvn dependency:sources lists parameters 'classifier' and 'type', but manually overrides them * [MDEP-300] - Unpacking artifacts should be based on type, with fallback on file-extension * [MDEP-328] - scriptableOutput/scriptableFlag have no effect * [MDEP-353] - Unit tests fail on Windows * [MDEP-366] - NPE when running site * [MDEP-371] - useJvmChmod true by default * [MDEP-376] - -Dexcludes filtering not working anymore * [MDEP-383] - Update purge-local-repository to work in Maven 3 * [MDEP-388] - NPE in analyze-report ** Improvement * [MDEP-173] - Support 'includes' in purge-local-repository * [MDEP-246] - purge-local-repository inclusions * [MDEP-285] - Document abstract method org.apache.maven.plugin.dependency.AbstractDependencyFilterMojo.getMarkedArtifactFilter() * [MDEP-287] - Make maven-dependency-plugin @threadSafe * [MDEP-343] - Add "skip" parameter for copy-dependencies * [MDEP-360] - Allow using folder as dependency:get destination parameter * [MDEP-377] - use last plexus-utils 3.0.7 which is faster on copying files. * [MDEP-384] - build-classpath should be able to use the artifact's baseVersion * [MDEP-385] - Default fuzziness level should be version instead of file * [MDEP-386] - Split purge-local-repository into manual and transitive ** New Feature * [MDEP-210] - Support includes/excludes configuration in analyze * [MDEP-380] - copy-dependencies should be able to use the artifact's baseVersion * [MDEP-381] - Unpack an artifact from commandline Enjoy, -The Apache Maven team
[RESULT] Re: [VOTE] Release Maven Dependency Plugin 2.6 and Maven Dependency Analyzer 1.3 - Attempt #2
Hi, The vote has passed with the following result : +1 (binding): Arnaud Héritier, Olivier Lamy, Hervé Boutemy, +1 (non binding): Anders Hammar, Tony Chemit I will promote the artifacts to the central repo. Thx On Fri, Nov 23, 2012 at 10:24 AM, Tony Chemit wrote: > On Fri, 23 Nov 2012 07:31:26 +0100 > Hervé BOUTEMY wrote: > > > 2*+1 > > 2*1 (nb) > > works fine to me. > > thanks, > > tony. > > > > > Regards, > > > > Hervé > > > > Le mardi 20 novembre 2012 23:28:41 Arnaud HERITIER a écrit : > > > Hi, > > > > > > Sorry for the long delay since the first attempt. I have more free > time now > > > to be back on this subject. > > > > > > We solved 3 issues in Maven Dependency Analyzer : > > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=H > > > tml&version=17832 > > > > > > There are still one issue left in JIRA: > > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=comp > > > > onent+%3D+maven-dependency-analyzer+AND+project+%3D+MSHARED+AND+resolution+% > > > 3D+Unresolved+ORDER+BY+updated+DESC > > > > > > We solved 29 issues in Maven Dependency Plugin : > > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&styleName=H > > > tml&version=18696 > > > > > > There are still a couple of issues left in JIRA: > > > > > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jql > > > > Query=project+%3D+MDEP+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-058/ > > > > https://repository.apache.org/content/repositories/maven-058/org/apache/mave > > > > n/shared/maven-dependency-analyzer/1.3/maven-dependency-analyzer-1.3-source- > > > release.zip > > > > > > > https://repository.apache.org/content/repositories/maven-058/org/apache/mave > > > > n/plugins/maven-dependency-plugin/2.6/maven-dependency-plugin-2.6-source-rel > > > ease.zip > > > > > > Staging sites (in few hours after the sync) : > > > http://maven.apache.org/shared/maven-dependency-analyzer-1.3/ > > > http://maven.apache.org/plugins/maven-dependency-plugin-2.6/ > > > > > > Guide to testing staged releases: > > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > > > Vote open for 72 hours. > > > > > > [ ] +1 > > > [ ] +0 > > > [ ] -1 > > > > > > > > > My +1 (x2) > > > > > > Cheers, > > > > > > - > > > Arnaud Héritier > > > http://aheritier.net > > > Mail/GTalk: aherit...@gmail.com > > > Twitter/Skype : aheritier > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > -- > Tony Chemit > > tél: +33 (0) 2 40 50 29 28 > email: che...@codelutin.com > http://www.codelutin.com > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud
[VOTE] Release Maven Dependency Plugin 2.6 and Maven Dependency Analyzer 1.3 - Attempt #2
Hi, Sorry for the long delay since the first attempt. I have more free time now to be back on this subject. We solved 3 issues in Maven Dependency Analyzer : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=17832 There are still one issue left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=component+%3D+maven-dependency-analyzer+AND+project+%3D+MSHARED+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC We solved 29 issues in Maven Dependency Plugin : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&styleName=Html&version=18696 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MDEP+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-058/ https://repository.apache.org/content/repositories/maven-058/org/apache/maven/shared/maven-dependency-analyzer/1.3/maven-dependency-analyzer-1.3-source-release.zip https://repository.apache.org/content/repositories/maven-058/org/apache/maven/plugins/maven-dependency-plugin/2.6/maven-dependency-plugin-2.6-source-release.zip Staging sites (in few hours after the sync) : http://maven.apache.org/shared/maven-dependency-analyzer-1.3/ http://maven.apache.org/plugins/maven-dependency-plugin-2.6/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 My +1 (x2) Cheers, - Arnaud Héritier http://aheritier.net Mail/GTalk: aherit...@gmail.com Twitter/Skype : aheritier
[VOTE] Release Maven Dependency Plugin 2.6 and Maven Dependency Analyzer 1.3
Hi, We solved 3 issues in Maven Dependency Analyzer :http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=17832 There are still one issue left in JIRA:http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=component+%3D+maven-dependency-analyzer+AND+project+%3D+MSHARED+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC We solved 28 issues in Maven Dependency Plugin :http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&styleName=Html&version=18696 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MDEP+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo:https://repository.apache.org/content/repositories/maven-174/https://repository.apache.org/content/repositories/maven-174/org/apache/maven/shared/maven-dependency-analyzer/1.3/maven-dependency-analyzer-1.3-source-release.zip https://repository.apache.org/content/repositories/maven-174/org/apache/maven/plugins/maven-dependency-plugin/2.6/maven-dependency-plugin-2.6-source-release.zip Staging sites (in few hours after the sync):http://maven.apache.org/shared/maven-dependency-analyzer-1.3/http://maven.apache.org/plugins/maven-dependency-plugin-2.6/ Guide to testing staged releases:http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 My +1 (x2) -- Arnaud
Release of the dependency plugin 2.6
Hi all, i would like to release the dependency plugin soon. There only too old issues not closed attached to the current version ( http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel) but I suppose they are migrated release after release without any real work on them. I'm interested especially by this fix to use it as report ( http://jira.codehaus.org/browse/MDEP-366) and it has the perf improvement with the plexus-utils upgrade (http://jira.codehaus.org/browse/MDEP-377) Nobody against it ? Cheers - Arnaud Héritier http://aheritier.net Mail/GTalk: aherit...@gmail.com Twitter/Skype : aheritier
Apache Maven has its Google+ Page
Hi all, I created a Google+ page for maven. Sadly we cannot yet share the ability to manage it and to post content. As soon as it will be possible I'll give the access to PMCs and probably dev members. For now ping me if you want that we publish something. On my side I'll try to forward announcements and things like that. https://plus.google.com/u/0/b/114843822427522708527/ Cheers, Arnaud
Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses
My vote : +1 as I don't see for now (sadly it is sure) another good solution to serve ours users. Arnaud On Wed, Aug 17, 2011 at 4:19 PM, Arnaud HERITIER wrote: > Hi all, > > Next releases of SISU and Aether will be done at Eclipse.org under EPL > 1.0 license. > Before they were published under ASL or dual ASL/EPL licenses thus as > defined in our policy [1] this change put them in Category B [2] and we need > to validate this change by a vote with a majority of the PMC in favor (but > the vote is open to everybody). > I push only one vote for both dependencies as for now I see no reason to > accept one and not the other. > This vote will be open for 1 week as we are in august (If we have not > enough votes at the end of next wednesday will see if we really need to > extend it). > > The vote : > [+1] I'm in favor to use as Maven core dependencies SISU and AETHER > libraries published under EPL 1.0 License. > [+0] No opinion, do what you want. > [-1] I'm against because (please elaborate) > > Arnaud > > [1] http://maven.apache.org/developers/dependency-policies.html > [2] http://www.apache.org/legal/resolved.html#category-b >
[VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses
Hi all, Next releases of SISU and Aether will be done at Eclipse.org under EPL 1.0 license. Before they were published under ASL or dual ASL/EPL licenses thus as defined in our policy [1] this change put them in Category B [2] and we need to validate this change by a vote with a majority of the PMC in favor (but the vote is open to everybody). I push only one vote for both dependencies as for now I see no reason to accept one and not the other. This vote will be open for 1 week as we are in august (If we have not enough votes at the end of next wednesday will see if we really need to extend it). The vote : [+1] I'm in favor to use as Maven core dependencies SISU and AETHER libraries published under EPL 1.0 License. [+0] No opinion, do what you want. [-1] I'm against because (please elaborate) Arnaud [1] http://maven.apache.org/developers/dependency-policies.html [2] http://www.apache.org/legal/resolved.html#category-b
3.0.4 release ?
Hi all, 3.0.3 was released a little bit more than 6 weeks ago but Benjamin doesn't have the time to work on a 3.0.4 for now. It was a good thing for our community to have regularly a bugfix release. Is there someone else in the team who may find some time to fix some issues and push a new release ? Arnaud
Re: Releasing maven-eclipse-plugin
> > > Arnaud is the one with all the outstanding issues - he should comment > if they can get bumped to the next version. > All those unassigned look suitable for bumping. > I'm not working on it and I won't be able soon I unassign all my issues. You can postpone issues you don't want to fix. You can try to deploy a SNAPSHOT and ask feedback from users before releasing it because our ITs doesn't validate many things (just that we always generate the same files, but it doesn't validate that you can use them in new/current eclipse versions). This plugin is widely used and the major part of users didn't upgrade to last releases because w have regressions in them. Thus if you want to have a wide usage of this new version you should take care to regressions found in 2 previous releases. cheers Arnaud
Re: [VOTE] Release Apache Maven 3.0-alpha-6
+1 I built successfully eXo enterprise (287 modules). 32min with alpha 06 vs 65 min with 2.2.1 (tests are deactivated). The only problem I have is MNG-3283 but it is not a regression in 3.x I did some others tests and didn't find issues Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Wed, Jan 6, 2010 at 9:19 PM, Igor Fedorenko wrote: > +1. > > -- > Regards, > Igor > > > Benjamin Bentmann wrote: > >> Hi, >> >> We solved 29 issues: >> >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=15996 >> >> There are still a couple of issues left in JIRA: >> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1 >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-014/ >> >> Staged source and binary distros: >> >> https://repository.apache.org/content/repositories/maven-014/org/apache/maven/apache-maven/3.0-alpha-6/ >> >> Guide to testing staged releases: >> http://maven.apache.org/guides/development/guide-testing-releases.html >> >> Vote open for 72 hours. >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> >> +1 from me >> >> >> Benjamin >> >> - >> 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 Maven Patch Plugin 1.1.1
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Jan 4, 2010 at 8:53 PM, Jason van Zyl wrote: > +1 > > On 2010-01-01, at 9:42 AM, Benjamin Bentmann wrote: > > > Hi, > > > > We solved 1 issue: > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11714&version=15200 > > > > There are no issues left in JIRA: > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11714&status=1 > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-013/ > > > > Staging site: > > http://maven.apache.org/plugins/maven-patch-plugin-1.1.1/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > +1 from me > > > > > > Benjamin > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > -- > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [Vote/Proposal]: failsafe and surefire
+1 to merge failsafe within surefire.
But I wouldn't like to have ITs bound to the default lifecycle. In theory we
always put them in a profile to activate them only on demand.
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Mon, Jan 4, 2010 at 6:43 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> OK,
>
> maven-surefire-plugin is well known to everyone
>
> it's lesser-known sister is failsafe-maven-plugin
>
> failsafe was written (by me) to solve some of the issues of running
> integration tests with the maven lifecycle.
>
> the lifecycle has a number of phases
>
> * some crappy phases
> * test
> * some more crappy phases
> * pre-integration-test
> * integration-test
> * post-integration-test
> * verify
> * yet more crappy phases
>
> surefire binds to the test phase, and by default will fail your build
> at the test phase if any of the tests it runs fail.
>
> That is all well and good when running unit tests...
>
> when we want to run integration tests, we usually want to set up some
> environment which we are integrating with, e.g. start a jetty server
> and deploy the current application to that server, or start a database
> server (e.g. derby) and configure the data source, etc
>
> so we use the pre-integration-test phase to do this set-up, and we
> tidy-up in the post-integration-test phase...
>
> when our pre-integration-test stuff is all running in the maven JVM,
> everything is hunky-dory
> (http://www.taytohunkydorys.ie/brands/hunky_dorys.asp). we bind a
> second execution of surefire:test to the integration-test phase and
> when/if the tests fail, the JVM gets killed and our integration test
> environment gets destroyed...
>
> however, if our pre-integration-test stuff affects external processes,
> we are stuck because we have no way to tidy-up in the
> post-integration-test phase (BTW, IMHO nobody should ever run "mvn
> integration-test". 1. it's too long to type, and 2, you reallly want
> to run "mvn verify" as that will give the post-integration-test phase
> a chance to run)
>
> failsafe solves the issue by decoupling failing the build from running
> the tests, failsafe:integration-test never fails the build, that is
> left up to failsafe:verify, and thus (as long as you never invoke a
> phase in the range [pre-integration-test,post-integration-test]) your
> tidy-up plugin configuration will always run.
>
> So, as part of rolling the 2.5 release of surefire, I was looking into
> merging the two plugins...
>
> My initial idea was to just move the mojo's into m-surefire-p as is,
> thus m-s-p would have three mojos: test, integration-test and verify
>
> However, there are advantages to keeping them as separate plugins:
>
> * Use case 1: Ignore Unit Test Failures and run the integration tests
> (I know Bob has broken the unit tests for that new feature he is
> writing, but I want to check I have not created a regression in the
> stuff I'm working on) - the verify mojo parses the xml result files to
> see if any tests failed. If we use the same plugin, we should really
> use the same directory (e.g. surefire-reports) It does not make sense
> for surefire to have one goal report to surefire-reports and the other
> report to failsafe-reports... and it we change the directory for the
> unit tests to e.g. test-reports that could have a regression imact.
>
> * Use case 2: Separate Reporting (as separate plugins, they generate
> reports in separate directories as before)
>
> * Use case 3: Separate default binding... consider the case where
> pluginManagement specifies executions, with separate plugins I can
> safely define /project/build/plugins/plugin/m-surefire-p and not drag
> in the default execution of failsafe:integration-test and
> failsafe-verify
>
> So my proposal is as follows:
>
> 1. Move failsafe-maven-plugin to
> https://svn.apache.org/repos/asf/maven/surefire/trunk/maven-failsafe-plugin
>
> 2. Refactor maven-surefire-plugin taking the code that is common with
> failsafe into common module
>
> 3. Refactor maven-failsafe-plugin to use the common module.
>
> In pseudo code SurefirePlugin would be reduced to
>
> execute() {
> common.runTests();
> }
>
> Failsafe's integration-test mojo would become
>
> execute() {
> try {
>common.runTests();
> } catch (Throwable t) {
>// ignore
> }
> }
>
> 4. Refactor maven-surefire-reporting-plugin to move the xml results
> parser into the common module
>
> 5. Refactor Failsafe's verify mojo to use the xml results parse from
> the common module.
>
> OK, so that's a tad long, but what do people think?
>
> Any objections?
>
> -Stephen
>
> Lazy consensus, 72hrs, i.e. you have until 18:00GMT on 7th Jan 2010 to
> -1 this (after which you'll have to -1 the commit if you feel strongly
> against the direction I'm suggesting)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additiona
Re: [VOTE] Commit access for Kristian Rosenvold
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Jan 4, 2010 at 9:02 AM, Milos Kleint wrote: > +1 > > Milos > > On Mon, Jan 4, 2010 at 8:47 AM, Jason van Zyl wrote: > > > Hi, > > > > I have reviewed the patches for the parallel build support and I think > they > > are great. > > > > I think we should just give Kristian access to work with Dan and other > > developers who want to support this work. > > > > +1 > > > > Thanks, > > > > Jason > > > > -- > > Jason van Zyl > > Founder, Apache Maven > > http://twitter.com/jvanzyl > > -- > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
Re: [DISCUSS] Semantics of version range in JDK profile activator
It is many more logical. But we'll have to clearly document it because
many users will wrongly suppose they avoid all 1.4 versions with (1.4
Arnaud
On Saturday, January 2, 2010, Benjamin Bentmann
wrote:
> Benjamin Bentmann wrote:
>
>
>
> test
>
> (1.4,1.5]
>
>
>
> Now, when do you think does this profile get activated in case the current
> Java version (as given by ${java.version}) happens to be
>
> a) 1.4.0_07
> b) 1.4.0_14
> c) 1.4.2_07
> d) 1.5.0_07
> e) 1.5.0_14
> f) 1.5.1_14
>
>
> For better illustration, this would be the results when employing the
> approach of the Enforcer Plugin with the proposed deviation to consider only
> the first three numeric parts, thereby ignoring the build number:
>
> a) inactive *
> b) inactive *
> c) active
> d) active *
> e) active *
> f) inactive
>
> The lines marked with * denote differences from the plain/original Enforcer
> results.
>
>
> Benjamin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
--
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
failsafe plugin Re: Test Plan for releasing maven-surefire-plugin 2.5
And what about the failsafe plugin This one is very useful and is a copy of surefire dedicated to its with junit. Couldn't we move it to Apache and use a shared lib to update them all together ? Couldn't we integrate it by default in maven 3 in the lifecycle ? WDYT ? Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Sat, Jan 2, 2010 at 12:47 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Here is the test plan. > > 1. We (=benjamin) run all the builds that are currently working with > m3+plugin-enfocer+new surefire plugin -SNAPHOT. If all builds still > pass with the new surefire plugin, then we say all is good > > 2. If all is good, we (=benjamin or me or somebody else) stage a > release of maven-surefire plugin. > > 3. We (=benjamin) run all the builds that are currently working with > m3+plugin-enfocer+new surefire plugin (staged release). If all builds > still pass with the new surefire plugin, then we say all is good and > call a vote > > Any body got any objections / additional test cases to add? > > I have deployed updated 2.5-SNAPSHOT, Step 1 has been started already. > If anyone has any issues they are willing to fix this week, scream > now (in the next 24h) and I will hold off until Friday before starting > step 2. > > -Stephen > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Maven 3.? and settings and more
Thank you and happy new year !!! Arnaud On Thursday, December 31, 2009, Brett Porter wrote: > > On 01/01/2010, at 2:54 AM, Arnaud HERITIER wrote: > >> ok cool >> I'll try to start to work on them this WE (Yes, I know I'm a nolife) >> I cannot edit pages, nor administrate the space. >> If someone can give me privileges. >> Thx. > > Done > >> >> Arnaud Héritier >> Software Factory Manager >> eXo platform - http://www.exoplatform.com >> --- >> http://www.aheritier.net >> >> >> On Thu, Dec 31, 2009 at 4:22 PM, Jason van Zyl wrote: >> >>> I believe it is in sync, and I removed most of the content from the front >>> page of the Codehaus space and ask Ben to put in place the redirect. >>> >>> If you work out of here: >>> >>> http://cwiki.apache.org/confluence/display/MAVEN >>> >>> I would just leave most of the old proposals in >>> http://cwiki.apache.org/confluence/display/MAVENOLD/Home. When people are >>> prepared to work on them they can migrate them over or if folks have new >>> stuff they can work in the new space. >>> >>> On 2009-12-31, at 3:55 AM, Arnaud HERITIER wrote: >>> >>>> ok, let me know when the space @ Apache will be in sync to the one in >>>> codehaus and when the one in codehaus will be in RO or removed. >>>> I'll start to cleanup its content. >>>> >>>> Cheers, >>>> >>>> Arnaud Héritier >>>> Software Factory Manager >>>> eXo platform - http://www.exoplatform.com >>>> --- >>>> http://www.aheritier.net >>>> >>>> >>>> On Thu, Dec 31, 2009 at 12:59 AM, Jason van Zyl >>> wrote: >>>> >>>>> Sure, not a problem. >>>>> >>>>> On 2009-12-30, at 6:46 PM, Dennis Lundberg wrote: >>>>> >>>>>> Jason van Zyl wrote: >>>>>>> On 2009-12-30, at 6:34 PM, Brett Porter wrote: >>>>>>> >>>>>>>> On 31/12/2009, at 2:11 AM, Jason van Zyl wrote: >>>>>>>> >>>>>>>>> Arnaud, >>>>>>>>> >>>>>>>>> If you really want to help to let people see what's going to be >>>>> planned then help cleanup this Confluence page: >>>>>>>>> >>>>>>>>> http://docs.codehaus.org/display/MAVEN/Home >>>>>>>>> >>>>>>>>> and >>>>>>>>> >>>>>>>>> http://docs.codehaus.org/display/MAVEN/All+Proposals >>>>>>>>> >>>>>>>>> There are bits and pieces of all that you've talked about below and >>> if >>>>> we culled out the dead stuff and things that have been done then it >>> would be >>>>> easier for people to see what can be done. >>>>>>>> >>>>>>>> I thought I'd made those readonly, but remember now that I don't have >>>>> Codehaus confluence admin privs. I've added a notice on the front page. >>>>>>>> >>>>>>>> This was already migrated to: >>>>>>>> http://cwiki.apache.org/confluence/display/MAVENOLD >>>>>>>> >>>>>>> >>>>>>> I can ask Ben to just shut this down. Are you done with your >>> migration? >>>>>> >>>>>> It would be good if it's possible to have a redirect page for the whole >>>>>> Codehaus wiki, that points to the new location. That'll give us, and >>> the >>>>>> search engines, time to update any links to it. >>>>>> >>>>>>>> With the intent of migrating anything meaningful into a clean slate >>> at: >>>>>>>> http://cwiki.apache.org/confluence/display/M -- Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 3.? and settings and more
ok cool I'll try to start to work on them this WE (Yes, I know I'm a nolife) I cannot edit pages, nor administrate the space. If someone can give me privileges. Thx. Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Thu, Dec 31, 2009 at 4:22 PM, Jason van Zyl wrote: > I believe it is in sync, and I removed most of the content from the front > page of the Codehaus space and ask Ben to put in place the redirect. > > If you work out of here: > > http://cwiki.apache.org/confluence/display/MAVEN > > I would just leave most of the old proposals in > http://cwiki.apache.org/confluence/display/MAVENOLD/Home. When people are > prepared to work on them they can migrate them over or if folks have new > stuff they can work in the new space. > > On 2009-12-31, at 3:55 AM, Arnaud HERITIER wrote: > > > ok, let me know when the space @ Apache will be in sync to the one in > > codehaus and when the one in codehaus will be in RO or removed. > > I'll start to cleanup its content. > > > > Cheers, > > > > Arnaud Héritier > > Software Factory Manager > > eXo platform - http://www.exoplatform.com > > --- > > http://www.aheritier.net > > > > > > On Thu, Dec 31, 2009 at 12:59 AM, Jason van Zyl > wrote: > > > >> Sure, not a problem. > >> > >> On 2009-12-30, at 6:46 PM, Dennis Lundberg wrote: > >> > >>> Jason van Zyl wrote: > >>>> On 2009-12-30, at 6:34 PM, Brett Porter wrote: > >>>> > >>>>> On 31/12/2009, at 2:11 AM, Jason van Zyl wrote: > >>>>> > >>>>>> Arnaud, > >>>>>> > >>>>>> If you really want to help to let people see what's going to be > >> planned then help cleanup this Confluence page: > >>>>>> > >>>>>> http://docs.codehaus.org/display/MAVEN/Home > >>>>>> > >>>>>> and > >>>>>> > >>>>>> http://docs.codehaus.org/display/MAVEN/All+Proposals > >>>>>> > >>>>>> There are bits and pieces of all that you've talked about below and > if > >> we culled out the dead stuff and things that have been done then it > would be > >> easier for people to see what can be done. > >>>>> > >>>>> I thought I'd made those readonly, but remember now that I don't have > >> Codehaus confluence admin privs. I've added a notice on the front page. > >>>>> > >>>>> This was already migrated to: > >>>>> http://cwiki.apache.org/confluence/display/MAVENOLD > >>>>> > >>>> > >>>> I can ask Ben to just shut this down. Are you done with your > migration? > >>> > >>> It would be good if it's possible to have a redirect page for the whole > >>> Codehaus wiki, that points to the new location. That'll give us, and > the > >>> search engines, time to update any links to it. > >>> > >>>>> With the intent of migrating anything meaningful into a clean slate > at: > >>>>> http://cwiki.apache.org/confluence/display/MAVEN > >>>>> > >>>>> - Brett > >>>>> > >>>>> -- > >>>>> 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 > >>>>> > >>>> > >>>> Thanks, > >>>> > >>>> Jason > >>>> > >>>> -- > >>>> Jason van Zyl > >>>> Founder, Apache Maven > >>>> http://twitter.com/jvanzyl > >>>> -- > >>>> > >>>> > >>>> - > >>>> 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 > >>> > >> > >> Thanks, > >> > >> Jason > >> > >> -- > >> Jason van Zyl > >> Founder, Apache Maven > >> http://twitter.com/jvanzyl > >> -- > >> > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > -- > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Maven 3.? and settings and more
ok, let me know when the space @ Apache will be in sync to the one in codehaus and when the one in codehaus will be in RO or removed. I'll start to cleanup its content. Cheers, Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Thu, Dec 31, 2009 at 12:59 AM, Jason van Zyl wrote: > Sure, not a problem. > > On 2009-12-30, at 6:46 PM, Dennis Lundberg wrote: > > > Jason van Zyl wrote: > >> On 2009-12-30, at 6:34 PM, Brett Porter wrote: > >> > >>> On 31/12/2009, at 2:11 AM, Jason van Zyl wrote: > >>> > Arnaud, > > If you really want to help to let people see what's going to be > planned then help cleanup this Confluence page: > > http://docs.codehaus.org/display/MAVEN/Home > > and > > http://docs.codehaus.org/display/MAVEN/All+Proposals > > There are bits and pieces of all that you've talked about below and if > we culled out the dead stuff and things that have been done then it would be > easier for people to see what can be done. > >>> > >>> I thought I'd made those readonly, but remember now that I don't have > Codehaus confluence admin privs. I've added a notice on the front page. > >>> > >>> This was already migrated to: > >>> http://cwiki.apache.org/confluence/display/MAVENOLD > >>> > >> > >> I can ask Ben to just shut this down. Are you done with your migration? > > > > It would be good if it's possible to have a redirect page for the whole > > Codehaus wiki, that points to the new location. That'll give us, and the > > search engines, time to update any links to it. > > > >>> With the intent of migrating anything meaningful into a clean slate at: > >>> http://cwiki.apache.org/confluence/display/MAVEN > >>> > >>> - Brett > >>> > >>> -- > >>> 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 > >>> > >> > >> Thanks, > >> > >> Jason > >> > >> -- > >> Jason van Zyl > >> Founder, Apache Maven > >> http://twitter.com/jvanzyl > >> -- > >> > >> > >> - > >> 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 > > > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > -- > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Maven 3.? and settings and more
Hi, I think there is no change in maven 3.0 about settings.xml ? Actually there are several problems (from my point of view) : * Mirrors don't support something to catch all releases repo or all snasphots repo. ** It creates a problem because you have to use a unique group in repo managers and then you download SNAPSHOTs versions for CLI plugins. ** Using repoIDs for mirror is unusable because repoIDs aren't unique * Profiles are confusing and can be source of problems if they are badly used. Moreover many things have to be put in profiles (repositories for example) whereas it could be outside. * There is no inheritance/mixins mechanisms to share settings accross an organization / a company / a project thus it is difficult to deploy/keep up to date them Not really related to settings but to the infrastructure and how maven works we talked several times about having several local repositories. The most interesting feature was to have one dedicated for each build and binaries was moved to another when all the project was build. It could allow to have a form of transaction in the build to not install a part of a project and having inconsistencies. (The problem also exists for deployment - how could we deploy all binaries only when the project is entirely built). I'm pushing all those questions because you are reviewing our backlog and I don't know if some of these remarks are already filled in Jira. Cheers, Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net
Re: Maven 2.2.2 soon?
On Wed, Dec 30, 2009 at 2:45 AM, Jason van Zyl wrote: > > On 2009-12-29, at 8:05 PM, Arnaud HERITIER wrote: > > >> > >>> What I recall discussing with Brian at ApacheCon was having a new > project > >> descriptor but making sure that when projects are installed or deployed > a > >> pom compatible with the current format would also be deployed along with > the > >> new descriptor. If the new project descriptor allows extension then this > >> could continue to work as things change. > >> > >> > >> Yah, I think we've been beating this around for a while... in my mind, > it's > >> still a unified repository metadata format that the POM translates to > (and a > >> parallel 4.0.0 POM / maven-metadata for old clients). > >> > >> It seems like that and the POM and the deprecations can be the single > focus > >> for 3.1... we just need to ship "Snow Maven" at this point so we can > move on > >> to new things. > >> > >> > >> > > Do we have in 3.0 a mechanism to have a constraint when we develop a > plugin > > to say that it requires a minimal version of POM. > > I would argue this should never happen in the future. A plugin should > define what it needs in its own configuration. I'm also going to push for > getting plugin specific POM elements back into the plugins that operate on > that data. Like pushing the resources elements into the resources plugin, > the distribution management information back into the deploy plugin, source > roots to the compiler plugin and anything akin to it. It's the only way to > continue scaling. There are changes that need to be made to the POM but I > really don't want to see proliferation of POM elements to service specific > plugins. > > I don't agree with Ralph that there needs to be a general POM extension > mechanism. It's going to happen primarily inside plugins. > ok for me to push what we can in plugins configurations but won't we have quickly some plugins incompatibilities because they'll share some info like resources, sources and many others (encoding, compiler version) and if the plugin which stores this info changes the name of the config or something like that, all others will be broken ? I wouldn't like we have again the maven 1 experience where plugins used others and finally we didn't control them ! Another thing if we move more data in plugins is the verbosity of our config. Even if we'll have alternative format, instead of overriding/extending build/resource we'll have to do it in build/plugins/plugin/config/resources . (many lines for a little change). To end another disadvantage to have more things in plugins config is that we won't validate them (with a schema and at runtime) and we'll ignore wrong settings which is always a big issues for our users because they don't quickly see if they made a misprint in the config. > > > Let's imagine we add a new data in the pom in 4.1.0 and a plugin needs to > > use them, thus maven shouldn't automatically check when it load a plugin > > that it is compatible with the POM version. > > Sure, we can augment whatever is necessary in preparation for 3.1. > > > > > Another question about 3.0, did we reintroduce // dowloads ? I think it > > wasn't here in the last alpha. > > One form of it is in the Jetty Wagon we have at Sonatype. There is a new > interface called the RepositorySystem which encapsulates everything with far > fewer interfaces then the legacy system. We also have another set of > interfaces which is a complete internal replacement. Benjamin has this on a > branch. So if someone wants to try and implement or backport Don's work then > that's cool too. If we want to get a 3.0 sometime around the beginning of > February then I'm not sure that will make it into 3.0. Might be soon after > that. > > I'm still more in favour IT quality, getting the JIRA issues cleaned up and > getting out the 3.0. > > If people want this released soonish and want specific features then speak > now and commit your time. > > > > > Arnaud > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > -- > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Maven 2.2.2 soon?
> > > What I recall discussing with Brian at ApacheCon was having a new project > descriptor but making sure that when projects are installed or deployed a > pom compatible with the current format would also be deployed along with the > new descriptor. If the new project descriptor allows extension then this > could continue to work as things change. > > > Yah, I think we've been beating this around for a while... in my mind, it's > still a unified repository metadata format that the POM translates to (and a > parallel 4.0.0 POM / maven-metadata for old clients). > > It seems like that and the POM and the deprecations can be the single focus > for 3.1... we just need to ship "Snow Maven" at this point so we can move on > to new things. > > > Do we have in 3.0 a mechanism to have a constraint when we develop a plugin to say that it requires a minimal version of POM. Let's imagine we add a new data in the pom in 4.1.0 and a plugin needs to use them, thus maven shouldn't automatically check when it load a plugin that it is compatible with the POM version. Another question about 3.0, did we reintroduce // dowloads ? I think it wasn't here in the last alpha. Arnaud
Re: Maven 2.2.2 soon?
On Tuesday, December 29, 2009, Jason van Zyl wrote: > > On 2009-12-29, at 11:54 AM, Arnaud HERITIER wrote: > >>> >>> >>>>> >>>> >>>> I agree. The problem will be in 3.1. We'll be able to remove things >>>> deprecated in 3.0 but nothing more. >>>> We'll have to see what we'll do if we have big changes. >>>> For me the most important problem to work on (post 3.0), will be how we >>>> manage different versions of POMs and metadata. This will have an >>> important >>>> impact for our users. >>>> >>>> cheers, >>>> >>>> >>> I think this depends on what model changes we want. >>> >>> My Idea is to deploy the new version pom as a pom with a classifier and >>> co-deploy a v4.0.0 translated pom as the pom without a classifier. >>> >>> That way we can have m4 look for the pom with classifier (if missing it >>> looks for the v4.0.0 pom) everything older will only see the pom without a >>> classifier >>> >>> -Stephen >>> >>> P.S. I think Brian Fox had a similar idea >>> >>> >>> In the future if we have 4.0.0, 4.1.0, 4.2.0 ... models, we'll try to >> deploy one per version with a different classifier ? >> And what will happen when we'll do a change in a model that we cannot >> convert to 4.0.0 model? We don't deploy it ? >> > > Trust me, we'll be talking about this for a while. If it's simply binary > consumption it's the dependencies that matter and the 4.0.0 of the POM can > probably be used forever, that's not really a big deal. But I think we have > to take a larger view here with respect to projects that want to rebuild > projects from source, integrating 3rd party tools, and syncing this up with > metadata changes that might happen in the repository. > > But I really think this is going to be done in a branching by abstraction > fashion and it's just all going to have to work in the trunk. We just can't > ever afford to go off into branches because this developer community cannot > support it. > I trust you ;). I'm just doing the advocate of devil. For dependencies I agree it is easy. But not too easy. We already broke backward compat with the import scope in 2.0.9 I think the problem will be more for inheritence (and perhaps mixins) ? >> Arnaud > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > -- > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 2.2.2 soon?
> > > > > > > > > I agree. The problem will be in 3.1. We'll be able to remove things > > deprecated in 3.0 but nothing more. > > We'll have to see what we'll do if we have big changes. > > For me the most important problem to work on (post 3.0), will be how we > > manage different versions of POMs and metadata. This will have an > important > > impact for our users. > > > > cheers, > > > > > I think this depends on what model changes we want. > > My Idea is to deploy the new version pom as a pom with a classifier and > co-deploy a v4.0.0 translated pom as the pom without a classifier. > > That way we can have m4 look for the pom with classifier (if missing it > looks for the v4.0.0 pom) everything older will only see the pom without a > classifier > > -Stephen > > P.S. I think Brian Fox had a similar idea > > > In the future if we have 4.0.0, 4.1.0, 4.2.0 ... models, we'll try to deploy one per version with a different classifier ? And what will happen when we'll do a change in a model that we cannot convert to 4.0.0 model? We don't deploy it ? Arnaud
Re: Maven 2.2.2 soon?
On Tue, Dec 29, 2009 at 4:24 PM, Brett Porter wrote: > > On 29/12/2009, at 8:18 PM, Arnaud HERITIER wrote: > > > +1 with Ralph. It is what I have in mind. the problem is that we already > > moved from 2.1 to 3.0 and finally we should produce a 2.5 (our users will > be > > lost). > > But I agree, 3.0 isn't a 3.0, it is 100% backward compatible with 2.X. > And > > more annoying we are talking about having backward incompatibilities > > (removing some stuffs) in 3.1. > > I'm not comfortable with that. > > I tend to agree, but I think the target has moved so much, especially with > a lot of public talks about the versions, that changing anything might cause > further confusion. > yes. it's impossible to change. > > What about something like this: > - 2.3 (or 2.9?) release that just adds all the deprecations (kind of like > what Lucene did before a major rev). > - 3.0 release retains deprecated functionality, with a --strict mode to > fail instead of warning (I haven't seen this, but ISTR Brian saying this was > going to be added, or is already there, at ApacheCon) > - 3.1 can then drop the functionality > > So, 3.0 essentially drops the functionality, with a "grace period" - which > is closer to what users might expect without changing the current story. > +1, with the strict mode activated by default in 3.0. We could have an option in settings.xml to deactivate it for example. > > WDYT? > I agree. The problem will be in 3.1. We'll be able to remove things deprecated in 3.0 but nothing more. We'll have to see what we'll do if we have big changes. For me the most important problem to work on (post 3.0), will be how we manage different versions of POMs and metadata. This will have an important impact for our users. cheers, > > - Brett > > -- > 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: Maven 2.2.2 soon?
+1 with Ralph. It is what I have in mind. the problem is that we already moved from 2.1 to 3.0 and finally we should produce a 2.5 (our users will be lost). But I agree, 3.0 isn't a 3.0, it is 100% backward compatible with 2.X. And more annoying we are talking about having backward incompatibilities (removing some stuffs) in 3.1. I'm not comfortable with that. Cheers Arnaud On Tue, Dec 29, 2009 at 10:14 AM, Ralph Goers wrote: > As I understand it, 3.0 now consists of significant refactoring of the > internals but no major changes externally. I originally expected 3.0 would > have some impact on the pom schema but I don't think even that has occurred. > Given all this is 3.0 really the appropriate version number? I usually > associate a change to the major release number with something that will > significantly impact the customer. I understand that all of this stuff is > foundationally necessary to make some of these changes but it would seem > more appropriate for this to be 2.5 and go to 3.0 when something significant > is added that an end user will notice. > > Ralph > > On Dec 28, 2009, at 9:12 PM, Jason van Zyl wrote: > > > > > On 2009-12-28, at 10:34 PM, Brett Porter wrote: > > > >> > >> On 29/12/2009, at 1:39 PM, Brian Fox wrote: > >> > >>> Is there anything pressing that calls for a 2.2.2? The 3.0's are > >>> moving along and are quite usable. > >> > >> I was just thinking of shipping the existing fixes and anything obvious > or regressed in 2.2.1. > >> > >> On 29/12/2009, at 1:44 PM, Jason van Zyl wrote: > >> > >>> I think that the 3.x code is far enough along that if anyone is going > to do any work I think that enough work has been done in 3.x to stop working > on 2.x. > >>> > >>> So much has been fixed, tested and tuned that at this point after using > 3.x for a long time and with the tests that are in place that I'd really > like to flatten all the 2.x versions in JIRA and toss them into the 3.x > bucket. Then scour the issues and just throw out anything that remotely > looks like garbage, close things out and get people to test against 3.x and > try and get the issue count down to the nuggets that are really going to be > new features or are really bugs. > >> > >> Might as well, that's realistically the situation anyway. Nobody is > going to do major work on 2.x faced with uncertain prospects in porting it > over to 3.x. Keep anything purely specific to 2.x in the 2.2.x bucket and > move bigger stuff out. > > > > There's not really much to port really at this point. The ITs can always > be improved but there is a pretty rock solid set of tests there. > > > >> > >> But we have to be 100% focused on shipping 3.0 if that's the case. You > can't put an end to 2.2.x when there's no end in sight to 3.0. > > > > I am not interested in 2.x, but that's why I asked if anyone else was > interested in working on it. I'm not putting an end to 2.x, I'm just not > going to work on it anymore. > > > >> JIRA needs to reflect exactly what needs to be done for 3.0-alphas, > betas and final so we can start counting down. It's fair enough to not > specify a date, but at least the target needs to be in sight to get anyone > inclined to help with polishing work. > > > > It's primarily testing work that needs to be done. The site plugin is > probably the only hole that needs to be filled as that one will affect a lot > of users. > > > >> > >> For example, where are the issues that reflect switching to Guice and > OSGi that we keep hearing about? > > > > Neither of those are going to happen in the 3.0 time line. We've got > Nexus running on Guice (with a Plexus shim) now and we need to run that > through the grinder for a while. When that works we can take a look at > Maven. Nexus uses almost everything in Plexus that Maven does and we've not > had to change any of code. The Plexus shim adapts everything necessary. But > we'll have to add to the shim to account for some Maven particulars because > all the old code has to work. This is not a small job, but we've got to get > Maven off Plexus pronto. We are not attempting to do the Guice + OSGi in one > shot in Nexus and we shouldn't attempt this with Maven in one shot either. > Stuart could probably get Maven working with Guice for 3.0 but I think that > would be pushing it. So I think it best to take Guice out of the 3.0 > deliverable. > > > > The OSGi runtime will likely follow what we're doing in Nexus. After > getting Guice working as a replacement for Plexus we will attempt to get > Nexus running on Guice + Peaberry for OSGi and then we'll run that through > the grinder as well. We don't know how long that will take, the Guice stuff > is working now but the OSGi is a whole other story. A repository of bundles > doesn't really exist (we're trying to fix that with osgi.sonatype.org) and > all the dependencies would need to be bundle-ized. So we're trying to add a > feature to Nexus to turn any JAR into a bundle on the fly. This is fraught > with problems. So
Re: [VOTE] Release Apache Parent POM 7
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Dec 28, 2009 at 9:19 AM, Olivier Lamy wrote: > +1 > > -- > Olivier > > 2009/12/26 Benjamin Bentmann : > > Hi, > > > > Besides updates to some plugin versions, this version of the parent POM > > contains the configuration to create ASF-compliant source distributions > to > > finally share those bits with other ASF projects. > > > > Diff to previous version: > > > http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?r1=766951&r2=893966 > > > > Staging repo: > > https://repository.apache.org/content/repositories/orgapacheapache-010/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > +1 from me > > > > > > Benjamin > > > > - > > 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 > >
Re: Local Repository Optimizations should be removed
If we want to study the impact on performances, I think we have to create a test case with a project creating wars and ears of several dozen of Mb. I already saw some projects like that (an EAR of 100Mb with 2 wars of 50Mb). Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Dec 28, 2009 at 2:47 AM, Igor Fedorenko wrote: > Benjamin, > > Out of curiosity, what kind of performance difference you get with this > optimization vs without it? > > Also, I think implementation should behave the same for pom and other > artifacts. I would not want to have to troubleshoot "strange" build > failures should pom get out of sync with the rest. > > -- > Regards, > Igor > > > > Benjamin Bentmann wrote: > >> Brian Fox wrote: >> >> I'm in favor of pulling this back or changing it to check for exact >>> timestamp and size. >>> >> >> I consider both the workflow outlined by Tamás and the need for >> optimization valid points so instead of pulling it out completely I opted to >> improve the existing logic. In the next alpha of Maven 3.0, artifact >> installation is only skipped if all of the following conditions hold: >> * destination has exact same timestamp as source >> * destination has exact same length as source >> * artifact is not of type "pom" >> >> >> Benjamin >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Deploy Plugin 2.5
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Dec 21, 2009 at 12:47 AM, Jason van Zyl wrote: > +1 > > On 2009-12-20, at 3:09 PM, Benjamin Bentmann wrote: > > > Hi, > > > > We solved 9 issues: > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11131&version=14498 > > > > There are still a couple of issues left in JIRA: > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11131&status=1 > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-003/ > > > > Staging site: > > http://maven.apache.org/plugins/maven-deploy-plugin-2.5/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > +1 from me > > > > > > Benjamin > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > -- > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Site Plugin version 2.1
+1 (I think we can postpone the fix of CSS for 2.1.1 ?) Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Sun, Dec 20, 2009 at 5:15 PM, Dennis Lundberg wrote: > Yes I noticed that as well on some pages. > > It is due to a fix in Doxia: > http://jira.codehaus.org/browse/DOXIA-360 > > Hervé BOUTEMY wrote: > > I just tested it on one of my projects and found a surprising change: > some > > tables get a border="1", while most of them stay with border="0". > > > > For example tables generated from APT [1], or "Dependency File Details" > of > > MPIR [2] > > > > Is it me or does anybody see the same issue? > > > > Regards, > > > > Hervé > > > > [1] http://logdistiller.sourceforge.net/tmp/ > > > > [2] http://logdistiller.sourceforge.net/tmp/dependencies.html > > > > Le jeudi 17 décembre 2009, Dennis Lundberg a écrit : > >> Hi, > >> > >> We solved 29 issues: > >> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146&styleName= > >> Html&version=14324 > >> > >> There are still a couple of issues left in JIRA: > >> > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11146&st > >> atus=1 > >> > >> Staging repo: > >> https://repository.apache.org/content/repositories/maven-060/ > >> > >> Staging site: > >> http://maven.apache.org/plugins/maven-site-plugin-2.1/ > >> > >> 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 > > > > > > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Jira project's name
I'll let others give their opinion and change it if they want. I don't know what is easier for users. Now I'm in holidays :-) Bye bye Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Thu, Dec 10, 2009 at 10:15 PM, Siarhei Dudzin wrote: > well, I'd say - let it be "Maven 1" who does it hurt? :) To me it is a > better alternative than having two versions in the project name. > > Just my 2 cents though. > > On Dec 10, 2009 10:03 PM, "Arnaud HERITIER" wrote: > > The old one is called "Maven 1" > http://jira.codehaus.org/browse/MAVEN > > Arnaud Héritier Software Factory Manager eXo platform - > http://www.exoplatform.com --- http://www.a... > On Thu, Dec 10, 2009 at 9:59 PM, Siarhei Dudzin >wrote: > > > Why not just call it "Maven"? > > Regards, > Siarhei > > On Dec 10, 2009 > 9:53 PM, "Arnaud HERITIE... >
Re: Jira project's name
The old one is called "Maven 1" http://jira.codehaus.org/browse/MAVEN Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Thu, Dec 10, 2009 at 9:59 PM, Siarhei Dudzin wrote: > Why not just call it "Maven"? > > Regards, > Siarhei > > On Dec 10, 2009 9:53 PM, "Arnaud HERITIER" < > arnaud.herit...@exoplatform.com> > wrote: > > Hi all, > > This is not the first time a user asked me where to find issues about > Maven 3. > The reason is that in Jira the project MNG is named "Maven 2" > I renamed it "Maven 2 & 3". If you have better,feel free to update it. > > Cheers, > > Arnaud Héritier > Software Factory Manager > eXo platform - http://www.exoplatform.com > --- > http://www.aheritier.net >
Jira project's name
Hi all, This is not the first time a user asked me where to find issues about Maven 3. The reason is that in Jira the project MNG is named "Maven 2" I renamed it "Maven 2 & 3". If you have better,feel free to update it. Cheers, Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net
Re: Local Repository Optimizations should be removed
I agree to fix the behavior like you propose Paul. It will reduce probably a little bit current performances but if it solves the case explained by Tamas, why not ... On Mon, Dec 7, 2009 at 4:01 PM, Paul Gier wrote: > It seems that the copyFileIfModified implementation should be changed. > Since currently it only checks if the source timestamp is newer. Maybe > this should be changed to check for the timestamps not equal (and maybe size > not equal also) instead of just a newer timestamp. That would allow the > optimization, but also handle the use case described in the jira issue. > > > Tamás Cservenák wrote: > >> Well, how about a "feature branch" (short lived branches)? Or you modify >> all >> the modules to have different GAV upon branch? This is kinda nonsense to >> me, >> since I branch it to do some feature that I know will get back into trunk. >> "Renaming" (changing GAVs of modules, maybe a LOT of them) is PITA in this >> case, IMHO. >> >> But even then, I dislike very much the idea that Maven "optimizes" this, >> and >> does less then I tell it to do ;) >> >> ~t~ >> >> On Mon, Dec 7, 2009 at 3:18 PM, Arnaud HERITIER >> wrote: >> >> You have the same version in 2 branches in a project ? >>> For me it is a bad practice >>> Each branch has it own version to avoid those sort of conflict. >>> >>> >>> Arnaud Héritier >>> Software Factory Manager >>> eXo platform - http://www.exoplatform.com >>> --- >>> http://www.aheritier.net >>> >>> >>> 2009/12/7 Tamás Cservenák >>> >>> Hi there, >>>> >>>> this is mainly about this issue: >>>> http://jira.codehaus.org/browse/MNG-4368 >>>> >>>> It caused a lot of grief (and lost hours) to me, until I figured what >>>> happens on me. >>>> >>>> IMHO, no "optimization" like this should be done against local >>>> >>> repository. >>> >>>> Please undo it. >>>> >>>> >>>> Thanks, >>>> ~t~ >>>> >>>> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Local Repository Optimizations should be removed
ok. I don't know enough GIT and DSCMs. I understand that many people want to work on various branches but I find that dangerous if you kkep the same version. What happens if you deploy SNAPSHOTs binairies in a repository to do continuous integration ? About your problem of optimization, I could understand we need to add a switch to deactivate it in cases like yours. But I'm not in favor to remove it. Your usecase (switching between several branches with the same "maven version") isn't "common" and the gain given by the optimization is important. I think that we need more optimizations like that to redo the minimal number of things (like we did many many years ago with make). Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net 2009/12/7 Tamás Cservenák > Okay, let's put it this way: > > are you saying that all the different GIT reposes out there containing > "project A" mirrors should have different versions? Who will coordinate > those? > > It's somehow incompatible with Git (and probably any other distributed SCM) > in very fundamental way > > ~t~ > > On Mon, Dec 7, 2009 at 3:30 PM, Arnaud HERITIER > wrote: > > > ... > > "Renaming" (changing GAVs of modules, maybe a LOT of them) is PITA in > this > > case, IMHO. > > ... > > mvn versions:set -DnewVersion=A.B.C-optim-SNAPSHOT > > > > And it's done ? > > > > > > Arnaud Héritier > > Software Factory Manager > > eXo platform - http://www.exoplatform.com > > --- > > http://www.aheritier.net > > > > > > 2009/12/7 Tamás Cservenák > > > > > Well, how about a "feature branch" (short lived branches)? Or you > modify > > > all > > > the modules to have different GAV upon branch? This is kinda nonsense > to > > > me, > > > since I branch it to do some feature that I know will get back into > > trunk. > > > "Renaming" (changing GAVs of modules, maybe a LOT of them) is PITA in > > this > > > case, IMHO. > > > > > > But even then, I dislike very much the idea that Maven "optimizes" > this, > > > and > > > does less then I tell it to do ;) > > > > > > ~t~ > > > > > > On Mon, Dec 7, 2009 at 3:18 PM, Arnaud HERITIER > > > wrote: > > > > > > > You have the same version in 2 branches in a project ? > > > > For me it is a bad practice > > > > Each branch has it own version to avoid those sort of conflict. > > > > > > > > > > > > Arnaud Héritier > > > > Software Factory Manager > > > > eXo platform - http://www.exoplatform.com > > > > --- > > > > http://www.aheritier.net > > > > > > > > > > > > 2009/12/7 Tamás Cservenák > > > > > > > > > Hi there, > > > > > > > > > > this is mainly about this issue: > > > > > http://jira.codehaus.org/browse/MNG-4368 > > > > > > > > > > It caused a lot of grief (and lost hours) to me, until I figured > what > > > > > happens on me. > > > > > > > > > > IMHO, no "optimization" like this should be done against local > > > > repository. > > > > > > > > > > Please undo it. > > > > > > > > > > > > > > > Thanks, > > > > > ~t~ > > > > > > > > > > > > > > >
Re: Local Repository Optimizations should be removed
... "Renaming" (changing GAVs of modules, maybe a LOT of them) is PITA in this case, IMHO. ... mvn versions:set -DnewVersion=A.B.C-optim-SNAPSHOT And it's done ? Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net 2009/12/7 Tamás Cservenák > Well, how about a "feature branch" (short lived branches)? Or you modify > all > the modules to have different GAV upon branch? This is kinda nonsense to > me, > since I branch it to do some feature that I know will get back into trunk. > "Renaming" (changing GAVs of modules, maybe a LOT of them) is PITA in this > case, IMHO. > > But even then, I dislike very much the idea that Maven "optimizes" this, > and > does less then I tell it to do ;) > > ~t~ > > On Mon, Dec 7, 2009 at 3:18 PM, Arnaud HERITIER > wrote: > > > You have the same version in 2 branches in a project ? > > For me it is a bad practice > > Each branch has it own version to avoid those sort of conflict. > > > > > > Arnaud Héritier > > Software Factory Manager > > eXo platform - http://www.exoplatform.com > > --- > > http://www.aheritier.net > > > > > > 2009/12/7 Tamás Cservenák > > > > > Hi there, > > > > > > this is mainly about this issue: > > > http://jira.codehaus.org/browse/MNG-4368 > > > > > > It caused a lot of grief (and lost hours) to me, until I figured what > > > happens on me. > > > > > > IMHO, no "optimization" like this should be done against local > > repository. > > > > > > Please undo it. > > > > > > > > > Thanks, > > > ~t~ > > > > > >
Re: Local Repository Optimizations should be removed
You have the same version in 2 branches in a project ? For me it is a bad practice Each branch has it own version to avoid those sort of conflict. Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net 2009/12/7 Tamás Cservenák > Hi there, > > this is mainly about this issue: > http://jira.codehaus.org/browse/MNG-4368 > > It caused a lot of grief (and lost hours) to me, until I figured what > happens on me. > > IMHO, no "optimization" like this should be done against local repository. > > Please undo it. > > > Thanks, > ~t~ >
Re: The Maven web site has the wrong skin
> > Hmm, I updated the site not to add the skin since it is inherited from the > parent. Maybe it's not actually being read from the repository? > > It's sure because I just updated parent poms. I didn't install them. Arnaud
Re: The Maven web site has the wrong skin
On Mon, Nov 23, 2009 at 10:39 PM, Brett Porter wrote: > What version of Maven are you building it with? > I suppose/hope I did it with 2.2.1 before the trying 3.0 > > I suggest always doing a sanity check with "mvn site" before deploying > something. > I did it, but I focused only on the content I changed. I didn't noticed about the skin because I'm seeing this one everyday ... I just tested with 3.0-alpha-5, 2.2.1 and 2.0.11-RC1 : same problem I removed the org/apache/maven/skins dir from my local repo : same problem And I see maven downloading : Downloading: http://repository.exoplatform.org/content/groups/all/org/apache/maven/skins/maven-default-skin/1.0/maven-default-skin-1.0.jar I updated my /pom dir in our svn (I don't know why it wasn't up to date) and ... it works I don't know what I had in my maven/asf pom to have this behavior. Sorry for the annoyance. I'll be more conscientious the next time (I'm too used that Maven just works ...) Arnaud > - Brett > > On 24/11/2009, at 8:16 AM, Arnaud HERITIER wrote: > > > Hi, > > > > This is probably me. Can someone fix it? I deployed it today after > > adding my book on the list. I did it several days ago after updating > > the plugins list to add versions and animal sniffer from mojo. > > Is there someone who can help me to analyze the problem ? I'm not > > sure to have many times to spend on it but if you have some ideas ... > > in the meantime I won't redeploy websites. Is there someone who > > already had a similar issue ? > > > > Arnaud > > > > On Monday, November 23, 2009, Dennis Lundberg > wrote: > >> Hi > >> > >> It seems that someone has problems with their local > >> environment/repository. For the second time in a week the Maven site has > >> been published with maven-default-skin instead of maven-stylus-skin that > >> is specified in maven-parent. > >> > >> I'm not sure why this is happening, but we need to get to the bottom of > it. > >> > >> -- > >> Dennis Lundberg > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > > > -- > > Arnaud Héritier > > Software Factory Manager > > eXo platform - http://www.exoplatform.com > > --- > > http://www.aheritier.net > > > > - > > 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: The Maven web site has the wrong skin
Hi, This is probably me. Can someone fix it? I deployed it today after adding my book on the list. I did it several days ago after updating the plugins list to add versions and animal sniffer from mojo. Is there someone who can help me to analyze the problem ? I'm not sure to have many times to spend on it but if you have some ideas ... in the meantime I won't redeploy websites. Is there someone who already had a similar issue ? Arnaud On Monday, November 23, 2009, Dennis Lundberg wrote: > Hi > > It seems that someone has problems with their local > environment/repository. For the second time in a week the Maven site has > been published with maven-default-skin instead of maven-stylus-skin that > is specified in maven-parent. > > I'm not sure why this is happening, but we need to get to the bottom of it. > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net - 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
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Nov 23, 2009 at 5:38 PM, Jason van Zyl wrote: > +1 > > > On 2009-11-23, at 11:33 AM, Benjamin Bentmann wrote: > > Hi, >> >> We solved some more issues: >> >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14952 >> >> There are still a couple of issues left in JIRA: >> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1 >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-018/ >> >> Staged source and binary distros: >> >> https://repository.apache.org/content/repositories/maven-018/org/apache/maven/apache-maven/3.0-alpha-5/ >> >> Guide to testing staged releases: >> http://maven.apache.org/guides/development/guide-testing-releases.html >> >> Vote open for 72 hours. >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> >> +1 from me >> >> >> Benjamim >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > -- > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Doxia Tools Shared Component version 1.1
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Sat, Nov 21, 2009 at 12:48 AM, Dennis Lundberg wrote: > Hi, > > This is the first of a series of releases to get Maven Site Plugin 2.1 > released. > > > We solved 4 issues: > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=14385 > > There are no issues left in JIRA! > > Staging repo: > https://repository.apache.org/content/repositories/maven-014/ > > Staging site: > http://maven.apache.org/shared/maven-doxia-tools-1.1/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > -- > 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.2
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Fri, Nov 20, 2009 at 11:37 PM, Michael wrote: > Dennis Lundberg schrieb: > > Hi, >> >> We solved 18 issues: >> >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&version=14696 >> >> There are still a couple of issues left in JIRA: >> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&status=1 >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-012/ >> >> Staging site: >> http://maven.apache.org/plugins/maven-changes-plugin-2.2/ >> >> Guide to testing staged releases: >> http://maven.apache.org/guides/development/guide-testing-releases.html >> >> Vote open for 72 hours. >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> > > +1 > > I am waiting for the properties interpolation! > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven JAR Plugin version 2.3
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Sat, Nov 21, 2009 at 12:23 AM, Dennis Lundberg wrote: > Hi, > > We solved 4 issues: > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137&version=13995 > > There are still a couple of issues left in JIRA: > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11137&status=1 > > Staging repo: > https://repository.apache.org/content/repositories/maven-013/ > > Staging site: > http://maven.apache.org/plugins/maven-jar-plugin-2.3/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > -- > 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 Plugin Testing 2.0-alpha-1
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Tue, Nov 17, 2009 at 9:03 AM, Olivier Lamy wrote: > +1 > > 2009/11/17 Benjamin Bentmann : > > Hi, > > > > this is the first release of the plugin testing harness branch for usage > > with Maven 3.0. > > > > We solved 2 issues: > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=15444 > > > > There are still a couple of issues left in JIRA: > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11740&status=1 > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-003/ > > > > Staging site (sync pending): > > http://maven.apache.org/plugin-testing/maven-plugin-testing-2.0-alpha-1/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > +1 from me > > > > > > Benjamim > > > > > > - > > 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 > >
Re: [VOTE] Release Apache Maven 3.0-alpha-4
+1 Tested on several projects Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Sat, Nov 14, 2009 at 11:54 AM, Jason van Zyl wrote: > > On 2009-11-14, at 4:47 AM, Dan Fabulich wrote: > > >> I was waiting until alpha-3 was out to merge in the MNG-3004 branch. >> MNG-3004 passes all ITs, including a few new ITs of the experimental >> multithreaded mode. >> >> Can we recut alpha-4 with MNG-3004 in it? >> >> > I'd personally still like to see a little more design around the > multi-threading first. We are going to roll out alpha after alpha based on > feedback we get from users to fix common problems first. I think that is the > real priority we have. I honestly do not see the urgent rush to push this > is. If we have fixes for users I want to push those out first. I want to be > cautious about new features. We haven't added any new features to the core > yet. I have 5-10 things on git branches but I just don't think it's the > priority. > > Honestly there's not really any public proposal or design to look at, and I > really think that we should try your branch against the performance > framework and make sure everything is ok. I'm not just doing this with your > feature, I've done it with all the ones that I have. I've refrained from > putting in because I want to make sure we don't ever go backward and I don't > think there is anything wrong with erring on the side of caution and waiting > a couple weeks. > > We'll probably keep doing 1-2 alphas a week so there isn't going to be a > huge time span you have to wait. I think we need a proposal and I think that > we have to get into the habit of having two other people review new features > at a bare minimum. I don't think this is an unreasonable approach. > > > -Dan >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > -- > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Checkstyle plugin version 2.4
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Sat, Nov 14, 2009 at 1:32 PM, Benjamin Bentmann < benjamin.bentm...@udo.edu> wrote: > Mark Hobson wrote: > > Staging repo: >> https://repository.apache.org/content/repositories/maven-001/ >> >> Staging site: >> http://maven.apache.org/plugins/maven-checkstyle-plugin-2.4/ >> > > +1 > > > Benjamin > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Site Update for Maven 3.0-alpha-3
Can't we keep 2.0.10 only in archives ? I don't think it is necessary to do some advertisement for it. Latest stable is 2.2.1 and latest Alpha/Beta is 3.0-alpha-3 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Nov 16, 2009 at 1:17 PM, Brett Porter wrote: > > On 13/11/2009, at 11:50 PM, Benjamin Bentmann wrote: > > > Brett Porter wrote: > > > >> I've staged a sample site here: > http://people.apache.org/~brett/staged-maven-site/ > > > > +1, I like the proposed structure. > > > > Just one minor thing: I believe the JAR/PDF of the site should be listed > separately as currently and not be part of the table listing the 2.2.1 > downloads. The site is meant to cover various Maven versions so I consider > the structure at > > > > http://people.apache.org/~brett/staged-maven-site/download.html > > > > irritating as it suggests the docs are meant specifically for 2.2.1. > > Done that, thanks. > > > > >> Alpha 3 is on the download page only, and release notes are drafted: > http://people.apache.org/~brett/staged-maven-site/docs/3.0-alpha-3/release-notes.html > > > > Thanks, I happily grabbed that and copied it over to the trunk. > > > > Before we completely merge the branch to trunk, we should look into > releasing the updated plexus-velocity component. There are already enough > snapshot things involved in the site for my taste. > > Agreed. I'll start that process now and merge it once it's released. > > - Brett > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Ant Plugin 2.3
+1 Arnaud On Tuesday, November 10, 2009, Olivier Lamy wrote: > +1 > > 2009/11/10 Benjamin Bentmann : >>> Vote open for 72 hours. >> >> Ping. >> >> >> Benjamin >> >> - >> 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 > > -- Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net - 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-3
+1 Tested with success on several projects It becomes to be interesting :-) Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Nov 9, 2009 at 5:44 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > +1 from me > > 2009/11/9 Benjamin Bentmann : > > Hi, > > > > OK, here we go, another alpha release of Maven, for all those brave guys > > that want to take it for a test drive ;-) > > > > We solved many issues: > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14719 > > > > There are still a couple of issues left in JIRA: > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1 > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-004/ > > > > Staged source and binary distros: > > > https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > +1 from me > > > > > > Benjamim > > > > - > > 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] Apache (parent POM) version 7
+1
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
On Thu, Nov 5, 2009 at 8:50 PM, John Casey wrote:
> Hi,
>
> I've included the source-release assembly configuration in the Apache
> parent POM since it's working pretty well here in Maven. This will allow
> other projects to take advantage of the descriptor automatically.
>
> Additionally, I've setup the descriptorRef to be used in the source-release
> assembly in the form of an expression (${sourceReleaseAssemblyDescriptor}).
> This should allow other projects to substitute a custom source-release
> descriptor by adding their own plugin-level dependency to the assembly
> plugin, then changing the value of ${sourceReleaseAssemblyDescriptor} (in
> the properties).
>
> The POM is here:
>
>
> https://repository.apache.org/content/repositories/orgapacheapache-001/org/apache/apache/7/
>
> Anyway, let's vote! 72h, +1/+0/-1.
>
> Here's my +1.
>
> Thanks,
>
> -john
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
Re: [VOTE] Release Maven Runtime version 1.0-alpha-2 (take 2)
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Wed, Nov 4, 2009 at 1:02 PM, Olivier Lamy wrote: > +1 > > 2009/11/4 Benjamin Bentmann : > > Mark Hobson wrote: > > > >> Staging repo: > >> https://repository.apache.org/content/repositories/maven-012/ > >> > >> Staging site: > >> http://maven.apache.org/shared/maven-runtime-1.0-alpha-2/ > > > > +1 > > > > > > Benjamin > > > > - > > 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 > >
Re: devoxx?
Lucky guys !!! Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Wed, Nov 4, 2009 at 9:39 AM, nicolas de loof wrote: > I do, 5 days > Nicolas > > 2009/11/3 Stephane Nicoll > > > Hey guys, > > > > Who's coming at the devoxx conference this year? > > > > _o/ > > > > S. > > > > -- > > Large Systems Suck: This rule is 100% transitive. If you build one, you > > suck" -- S.Yegge > > >
Re: [VOTE] Release Maven Toolchains plugin version 1.0 (take 2)
+1 Arnaud On Sunday, November 1, 2009, Vincent Siveton wrote: > +1 > > Vincent > > 2009/10/29 Stephen Connolly : >> Hi, >> >> This is the first official release. >> >> There are still a couple of issues left in JIRA: >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=12063&resolution=-1&sorter/field=updated&sorter/order=DESC >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-004 >> >> Staging site: >> http://maven.apache.org/plugins/maven-toolchains-plugin-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 >> >> P.S. >> The project site may not have finished syncing to all the mirrors yet. >> >> - >> 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 > > -- Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Parent POM 15, Maven Plugins Parent POM 16 and Maven Shared Components Parent POM 14
+1 Arnaud On Fri, Oct 30, 2009 at 12:29 AM, Olivier Lamy wrote: > +1 > > -- > Olivier > > 2009/10/30 Benjamin Bentmann : > > Hi, > > > > if some of you have a déjà vu while regarding the mail title, that's > fine... > > my previous attempt at making our release processes smoother failed due > to > > missing site descriptors in the deployment. So if you liked the > predecessor > > versions of the parents being voted on, I hope you also like these ones > that > > now even ship with a site descriptor next to them, isn't that awesome? > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-005/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > +1 from me > > > > > > Benjamin > > > > - > > 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 > >
Re: [DISCUSS] Handling of repositories in POMs of dependencies
I agree we can have tooling for that. We can imagine we add in user's settings a dedicated profile for the project with all repositories (but for that we have to reactivate the repositories chain to discover them ;-) ) On Wed, Oct 28, 2009 at 4:56 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > 2009/10/28 Stephen Connolly > > > 2009/10/28 Arnaud HERITIER > > > > I would like also that we don't use repositories defined in poms for all > >> reasons explained above. > >> It's right that changing this behavior will have an important impact > >> because > >> it could be difficult in certain cases to have an OOTB Build (svn co + > mvn > >> install). Having to update user's settings isn't fun but at least they > >> have > >> to understand what they are doing and they don't rely on some Maven > magic. > >> > > > > Also there is nothing stopping us from writting a plugin that imports the > > repositories into your settings.xml > > > > In which case for an out of the box build, you would do something like > > > > svn co > > mvn bootstrap:settings > > > > Note that this would print out big ugly warning messages and prompt for > each > repository... but at least people don't have to figure out how to edit > their > settings.xml ;-) > > > > mvn install > > > > > >> For corporate environment they are already doing it to define the global > >> proxy and it is now easier with plugins like the one in nexus. > >> If we continue to define repositories in POM not to resolve artifacts > but > >> just to document the build with a nice warning from maven with repo > lists > >> when an artifact isn't found, I think we could have a good compromise. > >> > >> Arnaud > >> > >> On Wed, Oct 28, 2009 at 4:16 PM, John Casey > >> wrote: > >> > >> > Most debian packagers that don't have their apps in the default APT > >> sources > >> > provide a standard page somewhere on their website for adding a new > >> source. > >> > This would be pretty easy for third-party repository providers to do, > >> and > >> > would have the added benefit of making them really think about it and > >> > support that repository as public infrastructure...along with > providing > >> > ticket/bug tracking for that repository's reachability along with the > >> build > >> > files or the source code for the app itself. > >> > > >> > Of course, there's not much reason I can think of that an OSS project > >> > wouldn't just configure synchronization with central if they're going > to > >> go > >> > to all this trouble...but for non-OSS I can see them using the above. > In > >> > that case, there's a chance they would want to authenticate/control > >> access > >> > to that repository anyway, in which case the user would need to modify > >> his > >> > settings.xml anyway... > >> > > >> > -john > >> > > >> > > >> > Jesse McConnell wrote: > >> > > >> >> The problem I see is that without being able to push up repositories > >> >> with third party artifacts that are not in central yet you still > >> >> depend on for integrations or things like that...you are out of luck > >> >> and need some mechanism of pushing that knowledge/information to the > >> >> user of the artifact...and a wiki page or a webpage detailing that is > >> >> not acceptable imo as it makes it difficult for the user as they need > >> >> to _find_ that page. > >> >> > >> >> Now I would be pro notification as well, along the lines that brett > >> >> was mentioning I think > >> >> > >> >> I can declare a repo in a third party integration, perhaps against a > >> >> corporate repo that has some open source component they are not > >> >> syncing to centraland that is _ignored_ in the build, ie never > >> >> consulted, but when that is detected and if the build is not able to > >> >> complete it should pump out that information to the user declaring > >> >> that other repositories have been detected and that perhaps missing > >> >> dependencies are located in there... > >> >> > >> >> jess
Re: [DISCUSS] Handling of repositories in POMs of dependencies
I would like also that we don't use repositories defined in poms for all reasons explained above. It's right that changing this behavior will have an important impact because it could be difficult in certain cases to have an OOTB Build (svn co + mvn install). Having to update user's settings isn't fun but at least they have to understand what they are doing and they don't rely on some Maven magic. For corporate environment they are already doing it to define the global proxy and it is now easier with plugins like the one in nexus. If we continue to define repositories in POM not to resolve artifacts but just to document the build with a nice warning from maven with repo lists when an artifact isn't found, I think we could have a good compromise. Arnaud On Wed, Oct 28, 2009 at 4:16 PM, John Casey wrote: > Most debian packagers that don't have their apps in the default APT sources > provide a standard page somewhere on their website for adding a new source. > This would be pretty easy for third-party repository providers to do, and > would have the added benefit of making them really think about it and > support that repository as public infrastructure...along with providing > ticket/bug tracking for that repository's reachability along with the build > files or the source code for the app itself. > > Of course, there's not much reason I can think of that an OSS project > wouldn't just configure synchronization with central if they're going to go > to all this trouble...but for non-OSS I can see them using the above. In > that case, there's a chance they would want to authenticate/control access > to that repository anyway, in which case the user would need to modify his > settings.xml anyway... > > -john > > > Jesse McConnell wrote: > >> The problem I see is that without being able to push up repositories >> with third party artifacts that are not in central yet you still >> depend on for integrations or things like that...you are out of luck >> and need some mechanism of pushing that knowledge/information to the >> user of the artifact...and a wiki page or a webpage detailing that is >> not acceptable imo as it makes it difficult for the user as they need >> to _find_ that page. >> >> Now I would be pro notification as well, along the lines that brett >> was mentioning I think >> >> I can declare a repo in a third party integration, perhaps against a >> corporate repo that has some open source component they are not >> syncing to centraland that is _ignored_ in the build, ie never >> consulted, but when that is detected and if the build is not able to >> complete it should pump out that information to the user declaring >> that other repositories have been detected and that perhaps missing >> dependencies are located in there... >> >> jesse >> >> -- >> jesse mcconnell >> jesse.mcconn...@gmail.com >> >> >> >> On Wed, Oct 28, 2009 at 09:17, Paul Gier wrote: >> >>> I really think it should not be allowed, since it makes the builds less >>> predictable/reproduceable/secure. Most people I've talked to think it's >>> a >>> bug when they first see it happening because they are trying to figure >>> out >>> why Maven is downloading files from a random location on the Internet. >>> >>> The people who have a corporate policy to only download from central are >>> already breaking their policy whether they list the alternate repo in >>> settings.xml or it is added from a dependency. >>> >>> With that said, I'm ok with having it configurable as Jesse suggests as >>> long >>> as the default behaviour is to not add the repositories to the build. >>> >>> Jesse McConnell wrote: >>> judging from the response I have gotten from people both wanting and not wanting repositories declared for various integrations with jetty, the problem folks seem to be ones where their corporate policy dictate they can not use any repo other then central but they do not have a repo manager setup. since we can't rightly force people to install and maintain repository managers, at first blush I would probably error on the side of a option in the settings.xml a la offline true/false jesse -- jesse mcconnell jesse.mcconn...@gmail.com On Wed, Oct 28, 2009 at 07:03, Brett Porter wrote: > I would advocate not allowing them, but using them to provide useful > information in the case of a resolution exception that can easily guide > the > user on what to do. > > If folks strongly want to continue to allow it, I would go with a > prominent > warning (which is the case for several other things now). > > As to what the user is guided to do - I assume that is to declare them > as > repositories in the current project, or to refer to their repository > manager's documentation to add it there (with this being recommended). > In > the long run I'd hope Maven can better handle multipl
Re: [VOTE] Release Maven Parent POM 14, Maven Plugins Parent POM 15 and Maven Shared Components Parent POM 13
+1 Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Mon, Oct 26, 2009 at 1:07 PM, Vincent Siveton wrote: > +1 > > Vincent > > 2009/10/25 Benjamin Bentmann : > > Hi, > > > > these releases are primarily meant to incorporate the fixed source > release > > assembly descriptor into our projects, thereby addressing the issue > outlined > > in http://jira.codehaus.org/browse/MASSEMBLY-446. > > > > Furthermore, maven-parent:14 also contains an update to the configuration > of > > the maven-checkstyle-plugin to fix the recently reported problems during > > site generation for releases. For maven-plugins:15, I also updated to > > maven-plugin-plugin:2.5.1. In both maven-plugins:15 and > > maven-shared-components:13, I additionally removed the (now inherited) > skin > > declaration from the site descriptor as pointed out by Vincent during the > > last release. > > > > Staging repo: > > https://repository.apache.org/content/repositories/orgapachemaven-003/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > +1 from me > > > > > > Benjamin > > > > - > > 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 Apache Source Release Assembly Descriptor 1.0.1
+1 Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Mon, Oct 26, 2009 at 1:06 PM, Vincent Siveton wrote: > +1 > > Vincent > > 2009/10/25 Benjamin Bentmann : > > Hi, > > > > This is a maintenance release for the assembly descriptor that we use to > > create ASF-compliant source distros. This release fixes a bug in version > 1.0 > > that erroneously includes paths like "target/**/src/**" in the distro. > > > > Note: If you want to test this descriptor with the Maven Assembly Plugin, > be > > sure to also specify plexus-utils:2.0.1 as a plugin dependency. See > > http://jira.codehaus.org/browse/MASSEMBLY-446 for further information. > > > > Staging repo: > > https://repository.apache.org/content/repositories/orgapacheapache-002/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > +1 from me > > > > > > Benjamin > > > > - > > 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 Maven Javadoc plugin version 2.6.1
+1 Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Sun, Oct 25, 2009 at 12:21 AM, Olivier Lamy wrote: > +1 > -- > Olivier > > 2009/10/23 Vincent Siveton : > > Hi, > > > > We solved 12 issues: > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14533&styleName=Text&projectId=11138 > > > > There are still a couple of issues left in JIRA: > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11138&status=1 > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-staging-011 > > > > Staging site: > > http://maven.apache.org/plugins/maven-javadoc-plugin-2.6.1 > > > > 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 > >
Re: [VOTE] Release Maven Invoker plugin version 1.5
+1 Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Sat, Oct 24, 2009 at 3:39 PM, Hervé BOUTEMY wrote: > +1 > > Hervé > > Le vendredi 23 octobre 2009, Stephen Connolly a écrit : > > Hi, > > > > We solved 2 issues: > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11441&styleName= > >Html&version=15898 > > > > There are still a couple of issues left in JIRA: > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pi > >d=11441&resolution=-1&sorter/field=updated&sorter/order=DESC > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-staging-013/ > > > > Staging site: > > http://maven.apache.org/plugins/maven-invoker-plugin-1.5/ > > > > 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 > >
Fwd: ASF Board Meeting Summary - October 21, 2009
Congrats Brian, It's now official, you are PMC chair. Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net -- Forwarded message -- From: Jim Jagielski Date: Thu, Oct 22, 2009 at 1:33 AM Subject: ASF Board Meeting Summary - October 21, 2009 To: committ...@apache.org The October board meeting took place on the 21th. The following directors were present: Shane Curcuru Doug Cutting Justin Erenkrantz Roy T. Fielding Jim Jagielski Geir Magnusson, Jr. Brian McCallister Brett Porter Greg Stein Many guests were present. The September minutes were approved. All of the received reports to the board were approved. The following reports were not received and are expected next month: Status report for the Apache Beehive Project Status report for the Apache Incubator Project The following resolutions were passed unaminously: A. Update Public Relations Committee Membership (Harvey, VP) B. Change of Maven PMC Chair (Brian Fox, VP) C. Change the Apache James Project Chair (Norman Maurer, VP) D. Change the Apache Xerces Project Chair (Michael Glavassevich, VP) E. Change the Public Relations Committee Chair (Shane Curcuru, VP) F. Change the Apache Abdera Project Chair (Ant Elder, VP) G. Change the Apache Velocity Project Chair (Henning Schmiedehausen, VP) H. Establish the Apache PDFBox Project (Andreas Lehmk¸hler, VP) I. Update Legal Affairs Committee Membership (Sam Ruby, VP) The next board meeting will be on the 18th of November.
Re: site stage-deploy broken?
You're right.I didn't notice this bug : http://maven.apache.org/plugins/maven-source-plugin-2.1.1/ Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Sat, Oct 17, 2009 at 9:25 AM, Stephane Nicoll wrote: > Hi, > > I noticed that too. All I did was a mvn site:stage-deploy from the > target/checkout directory and the links seems totally broken. For > instance a click on "introduction" targets > > > http://maven.apache.org/plugins/Users/snicoll/people.apache.org/www/maven.apache.org/plugins/maven-ear-plugin > > We had the sources plugin released recently. Did you had a similar problem? > > S. > > -- Forwarded message -- > From: Milos Kleint > Date: Fri, Oct 16, 2009 at 2:54 PM > Subject: Re: [VOTE] Release Maven ear plugin version 2.4 > To: Maven Developers List > > > +1 tested the javaee6 related functionality primarily. > > The website at the given url is not properly generated? clicking on Usages > or Introduction leads to nowhere? > > Milos > > On Fri, Oct 16, 2009 at 2:07 PM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > > +1, limited testing, but works for me > > > > -Stephen > > > > 2009/10/16 Stephane Nicoll > > > > > Hi, > > > > > > We solved 5 issues: > > > > > > > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?version=15180&styleName=Html&projectId=11132 > > > > > > There are still a couple of issues left in JIRA: > > > > > > > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11132&status=1 > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-staging-004/ > > > > > > Staging site: > > > http://maven.apache.org/plugins/maven-ear-plugin-2.4/ > > > > > > Guide to testing staged releases: > > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > > > Vote open for 72 hours. > > > > > > [ ] +1 > > > [ ] +0 > > > [ ] -1 > > > > > > My +1 > > > > > > Thanks, > > > Stéphane > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > -- > Large Systems Suck: This rule is 100% transitive. If you build one, > you suck" -- S.Yegge > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
[ANN] Maven Source Plugin 2.1.1 Released
Hi, The Maven team is pleased to announce the release of the Maven Source Plugin, version 2.1.1 The Source Plugin creates a jar archive of the source files of the current project. http://maven.apache.org/plugins/maven-source-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-source-plugin 2.1.1 Release Notes - Maven 2.x Souce Plugin - Version 2.1.1 ** Bugs fixed : * [MSOURCES-44] - If project doesn't contain sources (contains only test sources) source:jar will fail * [MSOURCES-47] - test-jar goal fails if no source files exist Enjoy, -The Maven team # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net
[RESULT] [VOTE] Release Maven source plugin version 2.1.1
Hi, The vote has passed with the following result : +1 (binding): Benjamin B, Olivier L, John C, Vincent S, and myself +1 (non binding): Oleg I will promote the artifacts to the central repo. Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Tue, Oct 13, 2009 at 7:45 PM, Vincent Siveton wrote: > +1 > > Vincent > > 2009/10/13 Arnaud HERITIER : > > ok :-) > > Others votes ? > > > > > > On Mon, Oct 12, 2009 at 3:17 PM, Benjamin Bentmann < > > benjamin.bentm...@udo.edu> wrote: > > > >> Arnaud HERITIER wrote: > >> > >> Benjamin, should I fix something ? :-( > >>> > >> > >> For this release? No, not because of me. The stuff from target is > >> superfluos but should not hurt, unless you discover files that reveal > >> sensitive information. > >> > >> If you wanted to look into working on the underlying assembly > descriptor, > >> then please go ahead :-) > >> > >> > >> > >> Benjamin > >> > >> - > >> 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 Maven source plugin version 2.1.1
ok :-) Others votes ? On Mon, Oct 12, 2009 at 3:17 PM, Benjamin Bentmann < benjamin.bentm...@udo.edu> wrote: > Arnaud HERITIER wrote: > > Benjamin, should I fix something ? :-( >> > > For this release? No, not because of me. The stuff from target is > superfluos but should not hurt, unless you discover files that reveal > sensitive information. > > If you wanted to look into working on the underlying assembly descriptor, > then please go ahead :-) > > > > Benjamin > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Release guide outdated
Yes, Myself I didn't have issue to navigate in its screens.Thx. Arnaud On Mon, Oct 12, 2009 at 4:53 AM, Brian Fox wrote: > I'll get them updated, the steps are substantially the same but > screens slightly different. > > On Sun, Oct 11, 2009 at 7:52 PM, Arnaud HERITIER > wrote: > > Hi, > > I'm doing a release and noticed that many screenshots of Nexus are > > outdated in the current version we are using. > > I don't have the time to update them now and I don't know where I can > fill > > a TODO to not forget to update this doc. > > If you have an idea. > > > > Cheers, > > > > Arnaud > > > > # Arnaud Héritier > > # Software Factory Manager > > # eXo Platform > > # http://www.exoplatform.com > > # http://blog.aheritier.net > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven source plugin version 2.1.1
> +1 > > The source distro again contains target/** so we probably should look into > another assembly descriptor, something simple without regex that simply > works for single-module projects. > > Benjamin, should I fix something ? :-( Arnaud
[VOTE] Release Maven source plugin version 2.1.1
Hi, We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11147&styleName=Html&version=15244 Those one are very important for many projects because the plugin failed in a project without sources which is really annoying when we use it in a multi-modules project. There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11147&status=1 Staging repo: https://repository.apache.org/content/repositories/maven-staging-017/ Staging site: http://maven.apache.org/plugins/maven-source-plugin-2.1.1/ (Will be available in few hours after the next rsync) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 My +1. Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net
Release guide outdated
Hi, I'm doing a release and noticed that many screenshots of Nexus are outdated in the current version we are using. I don't have the time to update them now and I don't know where I can fill a TODO to not forget to update this doc. If you have an idea. Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net
Re: [VOTE] Release Maven Plugin Tools 2.5.1
+1 Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Sun, Oct 4, 2009 at 8:12 PM, Dennis Lundberg wrote: > +1 > > Thanks! Works for me. > > Benjamin Bentmann wrote: > > Hi, > > > > We solved 10 issues: > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?version=15018&styleName=Html&projectId=11139 > > > > > > There are still a couple of issues left in JIRA: > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11139&status=1 > > > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-staging-002/ > > > > Staging site (sync pending): > > http://maven.apache.org/plugins/maven-plugin-plugin-2.5.1/ > > http://maven.apache.org/plugin-tools-2.5.1/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > +1 from me. > > > > > > Benjamin > > > > - > > 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 > >
Stephen's credentials Re: [VOTE] maven-resources-plugin 2.4.1
I think your vote count but for infra I don't know what to do. On Thu, Oct 1, 2009 at 9:33 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > +1 (anyone know at what stage my votes count, or what's keeping infra?) > > -Stephen > > 2009/10/1 Olivier Lamy > > > +1 > > > > > > 2009/9/30 John Casey : > > > Hi everyone, > > > > > > This release is meant to fix a couple of the biggest bugs introduced in > > 2.4. > > > > > > We fixed 2 issues: > > > > > > > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145&styleName=Text&version=15760 > > > > > > There are still plenty of issues left in JIRA for 2.5 and beyond: > > > > > > > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=11145 > > > > > > Staging repo: > > > > > > https://repository.apache.org/content/repositories/maven-staging-013/ > > > > > > Staging site (should be showing up in a couple hours or so): > > > http://maven.apache.org/plugins/maven-resources-plugin-2.4.1/ > > > > > > 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 > > > > >
Re: Eclipse as a dependency
No idea in the dev list ? Sent from my iPhone On 25 sept. 2009, at 11:00, Emmanuel Hugonnet wrote: > Hi, > I have created a small Maven plugin which uses the Eclipse code > formatter to > format my code. > I would like to release it but the available librairies of Eclipse > are quite > old and I don't want my users to have Eclipse installed (that's the > whole > point of the plugin). Is there a repository with Eclipse jars > somewhere ? I > think that m2eclipse/tycho should be using them but I can't seem to > find the > jars. What's the policy concerning these jars ? > Thans, > Emmanuel - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: moving the MAVEN space to cwiki (was: make cwiki publicly writeable?)
let's go Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Thu, Sep 24, 2009 at 3:07 AM, Brett Porter wrote: > Changing the subject to get more visibility... Codehaus is upgrading to > Confluence 3.0 this weekend which will limit migration options if we make > any further edits over there. > > Any objections to disabling write to the Codehaus MAVEN space and pointing > people to cwiki as described below? > > On 11/09/2009, at 9:14 PM, Brett Porter wrote: > > I migrated the MAVEN space as is to here: >> http://cwiki.apache.org/confluence/display/MAVENOLD/Home >> >> Everything is intact except for usernames that couldn't be matched up on >> the CWIKI instance. (I fixed those already listed in maven-committers >> though). It can be re-imported pretty easily now if necessary. >> >> I moved one doc over which looks out of date but relevant for the new >> efforts to see how it would go: >> http://cwiki.apache.org/confluence/display/MAVEN/Creating+a+Maven+Integration+Test >> >> Before I move any other content over - given this, does it make sense to >> pull down the old Codehaus wiki (and change it to direct folks to the new >> one) and then just move over the bits that are still relevant? >> >> Thoughts? >> >> Cheers, >> Brett >> >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Invoker 2.0.11
+1 Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Sun, Sep 20, 2009 at 8:17 PM, Olivier Lamy wrote: > +1 > > 2009/9/20 Benjamin Bentmann : > > Hi, > > > > This is a prerequisite for the upcoming release of > maven-invoker-plugin:1.4 > > which I will stage next. > > > > We solved 1 issue: > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14534&styleName=Html&projectId=11761 > > > > There are still a couple of issues left in JIRA: > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&status=1&component=13271 > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-staging-038/ > > > > Staging site (sync pending): > > http://maven.apache.org/shared/maven-invoker-2.0.11/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > > > Benjamin > > > > - > > 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 > >
Re: [VOTE] Release Maven Invoker Plugin 1.4
+1 Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Sun, Sep 20, 2009 at 8:17 PM, Olivier Lamy wrote: > +1 > > 2009/9/20 Benjamin Bentmann : > > Hi, > > > > We solved 21 issues: > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14609&styleName=Html&projectId=11441 > > > > There are still a couple of issues left in JIRA: > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11441&status=1 > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-staging-039/ > > > > Staging site (sync pending): > > http://maven.apache.org/plugins/maven-invoker-plugin-1.4/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > > > Benjamin > > > > - > > 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 > >
Re: [VOTE] Maven Verifier 1.2
+1 Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Tue, Sep 15, 2009 at 11:51 PM, Hervé BOUTEMY wrote: > +1 > > Hervé > > Le mardi 15 septembre 2009, Olivier Lamy a écrit : > > +1 > > > > 2009/9/15 John Casey : > > > Hi, > > > > > > This library has been pretty stable for awhile now, and I think it's > time > > > to release it before we start adding any more new features. I've been > > > using the verifier more and more for integration testing outside of the > > > Maven core (for plugins, shared components, etc.) and it has a very > > > reliable, stable feature-set that works well on continuous-integration > > > platforms as well as local builds. > > > > > > The staging repository is here: > > > > > > https://repository.apache.org/content/repositories/maven-staging-016/ > > > > > > Please vote: +1/+0/-1. I'll leave the vote open for 72h. > > > > > > Here's my +1. > > > > > > -john > > > > > > - > > > 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] Maven Artifact Resolver 1.0
+1 Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Tue, Sep 15, 2009 at 11:51 PM, Hervé BOUTEMY wrote: > +1 > > Hervé > > Le mardi 15 septembre 2009, Benjamin Bentmann a écrit : > > John Casey wrote: > > > The staging repository is here: > > > > > > https://repository.apache.org/content/repositories/maven-staging-017/ > > > > +1 > > > > > > Benjamin > > > > - > > 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 Maven Remote Resources Plugin version 1.1
+1 Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Tue, Sep 15, 2009 at 10:27 AM, Jason van Zyl wrote: > +1 > > Using it everyday as part of 3.x. From the CLI and from m2eclipse. > > > On 2009-09-15, at 2:23 AM, John Casey wrote: > > Hi, >> >> Along with other features and bugfixes, this release will provide >> compatibility with Maven 3.x, so we have a released version to depend on by >> the time we release Maven 3.0-alpha-3. >> >> We solved 12 issues: >> >> >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11391&styleName=Html&version=14382 >> >> >> There is still 1 issue remaining: >> >> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11391&fixfor=15620 >> >> >> Staging Repository: >> >> https://repository.apache.org/content/repositories/maven-staging-018/ >> >> >> Staging Site: >> >> http://maven.apache.org/plugins/maven-remote-resources-plugin-1.1/ >> >> >> Guide to testing staged releases: >> >> http://maven.apache.org/guides/development/guide-testing-releases.html >> >> Vote is open for 72h. >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> >> Here's my +1. >> >> Thanks, >> >> -john >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > http://twitter.com/SonatypeNexus > http://twitter.com/SonatypeM2E > -- > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Shared Components Parent 12
+1 Arnaud On Sun, Sep 13, 2009 at 2:06 AM, Hervé BOUTEMY wrote: > +1 > > Hervé > > Le samedi 12 septembre 2009, Benjamin Bentmann a écrit : > > Hi, > > > > sorry to bug you guys again, but there is another POM that would be > > handy once released :-) > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-staging-009/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > > > Benjamin > > > > - > > 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 Maven Plugins Parent 14
+1 Arnaud On Sun, Sep 13, 2009 at 2:01 AM, Hervé BOUTEMY wrote: > +1 > > Hervé > > Le samedi 12 septembre 2009, Benjamin Bentmann a écrit : > > Hi, > > > > I was hoping to get some plugin release done but figured there is still > > some tiny bit missing so first I would like to get maven-plugins:14 > > released which inherits from maven-parent:13 and as such provides the > > configuration for the ASF-compliant source distros. > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-staging-008/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > > > Benjamin > > > > - > > 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] Invite Stephen Connolly to join Maven committers
I'm back :-)I close the vote. It passed with : 14 binding votes : Arnaud, Barrie, Benjamin, Brett, Brian, Dennis, Emmanuel, Hervé, John, Lukas, Olivier, Stephane, Ralph, Vincent 4 non binding votes : Jeff, Nicolas, Fabrice, Mark, Stephen, Welcome to Maven! Please sign this agreement as soon as possible and fax it to the number given: http://www.apache.org/licenses/icla.txt Note that if your contributions to the project may be the intellectual property of your employer through your employment agreement, they will need to submit: http://www.apache.org/licenses/cla-corporate.txt. It can take a couple of weeks to get your account created - please be patient. To help expedite this, please provide the following details: Preferred Unix ID: Full name (as stated on CLA): Forwarding email address: For your Unix ID, please provide alternatives and check http://people.apache.org/~jim/committers.html to see if it is already used For the PMC's records, the vote threads are: http://www.nabble.com/-vote--Invite-Stephen-Connolly-to-join-Maven-committers-td25323185.html#a25323185 Congratulations, The Maven Team. # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Wed, Sep 9, 2009 at 1:58 PM, Jason van Zyl wrote: > Stephen, > > If you're already an Apache committer just let me know what your id is, if > fill out a CLA[1] and follow the instructions to send it in. When the CLA is > processed we'll get your account setup. > > [1]: http://www.apache.org/licenses/ > > > On 2009-09-09, at 12:45 PM, Vincent Siveton wrote: > > +1 >> >> Vincent >> >> 2009/9/6 Arnaud HERITIER : >> >>> Hi all, >>> I'd like to propose giving commit access to Stephen Connolly. >>> He is already a committer @ Mojo for many monthes and did a great work >>> on >>> several plugins. >>> He is the author of the very useful versions plugin. He is working on >>> several others plugins like animal-sniffer. >>> He's doing a job of quality (with unit and integration tests) and >>> follows >>> our best practices. >>> He's participating on our mailing lists for a least 2 years. >>> I helped him several time to apply some patches on our plugins and >>> shared >>> components. >>> Now he would like to help on toolchains and adding its support in >>> enforcer. >>> >>> I think we need more people as involved as Stephen has been. >>> >>> Please vote. 72h +1/+0/-1 >>> >>> Here is my +1. >>> >>> Cheers, >>> >>> Arnaud >>> >>> # Arnaud Héritier >>> # Software Factory Manager >>> # eXo Platform >>> # http://www.exoplatform.com >>> # http://blog.aheritier.net >>> >>> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > http://twitter.com/SonatypeNexus > http://twitter.com/SonatypeM2E > -- > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
[vote] Invite Stephen Connolly to join Maven committers
Hi all, I'd like to propose giving commit access to Stephen Connolly. He is already a committer @ Mojo for many monthes and did a great work on several plugins. He is the author of the very useful versions plugin. He is working on several others plugins like animal-sniffer. He's doing a job of quality (with unit and integration tests) and follows our best practices. He's participating on our mailing lists for a least 2 years. I helped him several time to apply some patches on our plugins and shared components. Now he would like to help on toolchains and adding its support in enforcer. I think we need more people as involved as Stephen has been. Please vote. 72h +1/+0/-1 Here is my +1. Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net
Re: dropping non-unique snapshots in Maven 3
I would prefer to deprecate them in 2.x and definitively remove them in 3.x. It seems more logical. Arnaud On Friday, September 4, 2009, Jason van Zyl wrote: > I think it can be in the same vein as the no versions for plugins. Not a very > good idea and potentially harmful. > > We put it in, deprecate it over 3.0 and it becomes taboo in 3.1. If it's a > bad practice in the majority of cases then we eliminate it. Over the life of > 3.0 to 3.1 should be long enough. We can also start deprecating things like > this in the 2.x line. > > On 2009-09-04, at 4:49 PM, Brian Fox wrote: > > > I saw this on Benjamin's compat page yesterday and thought I'd throw > it up for discussion: > Non-unique Snapshot Deployments > > The setting false for a distribution > repository has no effect in version 3.x, snapshot artifacts will > always be deployed using a timestamped version. > > I personally am not a fan of this feature as I've seen it cause more > problems than it solves. It also harkens back to a time when > Repository Managers didn't exist and seems like a work around to > cleaning up old snapshots. So my life would be easier if this didn't > exist. > > That said, I know of at least one instance where this is required > (will send a separate thread about that because it's a flaw in Maven > that should be addressed separately). > > With the focus on 3.0 being a drop in for M2, this clearly would cause > some heartache for users. Does anyone feel strongly enough that this > should go back? (and is willing to write the new code for it?) > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > http://twitter.com/SonatypeNexus > http://twitter.com/SonatypeM2E > -- > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: What's block maven-toolchains-plugin getting *any* release at all?
+1 to propose you to join us as committer :-) Arnaud On Fri, Sep 4, 2009 at 3:08 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > +1 for Arnaud being leader > > 2009/9/4 Arnaud HERITIER > > > A leader ? > > > > On Fri, Sep 4, 2009 at 10:32 AM, Stephen Connolly < > > stephen.alan.conno...@gmail.com> wrote: > > > > > Any king of release whatsoever... as long as it's not -SNAPSHOT > > > > > > -Stephen > > > > > >
Re: What's block maven-toolchains-plugin getting *any* release at all?
A leader ? On Fri, Sep 4, 2009 at 10:32 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Any king of release whatsoever... as long as it's not -SNAPSHOT > > -Stephen >
Did you upgrade to Snow Leopard (Java 6 & Animal Sniffer)
Hi team and his MacOs users, Did you upgrade to Snow Leopard ? I would like to do it but my main issue is that there is only Java 6 on it and animal sniffer isn't yet ready to controle that our projects are compatible with Java 1.4 (Shared, Plugins, Core <2.2) or 1.5 (Core >= 2.2). I know that Stephen Connolly is working on it with kohsuke to real a new version of the plugin on mojo.codehaus.org. Do we plan to use it in all our builds when it will be ready ? I don't know if this sort of control has to be launched for all build. I would prefer to have it in the release profile and to have this profile activated in our continuous integration builds. WDYT ? Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net
Re: Adding a "Looking for Code Quality Managers" section into the Maven web site ?
+1 it's a really good idea. Cheers arnaud On Thursday, September 3, 2009, Freddy Mallet wrote: > Oups Fabrice, I'm really sorry and of course Squale must join this list. > If you can handle this modification by yourself, that's perfect ! > > cheers > > Freddy Mallet > http://www.SonarSource.com > http://Sonar.codehaus.org > http://twitter.com/FreddyMallet > > > > On Wed, Sep 2, 2009 at 11:45 PM, Fabrice Bellingard > wrote: > >> Hi Freddy, >> >> +1 for me as well, excellent idea. >> And I will also add Squale - the OSS project I'm leading [1] - to this >> already nice list. :-) >> >> Olivier, I can handle that if you want - if there's no objection with this >> idea, of course. >> >> Cheers, >> >> - Fabrice >> belling...@apache.org >> >> [1] http://www.squale.org >> >> >> On Wed, Sep 2, 2009 at 11:19 PM, Freddy Mallet > >wrote: >> >> > Hi all, >> > >> > This proposal is submitted by >> > >> > Romain Pelisse, leader of XRadar >> > Khosuke Kawaguchi, leader of a well known CI server >> > David Vincente, leader of the Maven Dashboard plugin >> > and myself, co-leader of Sonar >> > >> > The idea is simply to add a new "Looking for Code Quality Managers" >> section >> > into the right sidebar of the Maven web site homepage bellow "Looking for >> > Repository Managers" and "Looking for CI Servers". >> > >> > This section would contain a short text "Take a look at the Code Quality >> > Management platforms available from the community". Clicking on "Take a >> > look" would display a list of tools with XRadar, Sonar, Maven Dashboard >> and >> > Hudson (as it contains on the shelf quality reports). >> > >> > It has never been so easy with those tools to monitor source code's >> health >> > and beginning to combine metrics. Good part of software development >> > departments, which are using Maven, are progressively adopting such >> quality >> > platforms. We think the Maven ecosystem would be reinforced if it >> welcomed >> > those quality platforms which are highly based and fully integrated with >> > Maven. >> > >> > Any feedback, bad or good, is welcome. >> > >> > Thanks >> > >> > Romain, Khosuke, David and Freddy >> > >> > -- Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Hibernate feedback about Maven usage.
I think it could be an interesting feature (and will help to fight against others tools siren like graddle ;-) )I agree that it is strange to see this behavior from another OSS project. But it's often done like that. I opened this issue to keep a trace of it : http://jira.codehaus.org/browse/MNG-4324 thanks Arnaud On Tue, Aug 25, 2009 at 9:47 PM, Brett Porter wrote: > We could surely add that. For example: > > some-module$ mvn -amd clean install > > The -amd without -pl means use the current project and search up through > available parents iff the modules also match to construct the reactor > instead. > > Perhaps if it was posted in a JIRA entry instead of a "maven doesn't work" > blog someone would JDI :) > > > On 25/08/2009, at 12:44 PM, Arnaud HERITIER wrote: > > Partially, in fact they would like to have something easier to use.Instead >> of using command line args from the reactor project to say what to build, >> they would prefer to go directly in the submodule and to launch the build. >> >> On Tue, Aug 25, 2009 at 6:37 PM, Brett Porter wrote: >> >> As the commenters said, the new reactor modes in 2.1 (and the reactor >>> plugin in 2.0) already satisfy those needs. >>> >>> - Brett >>> >>> On 25/08/2009, at 12:09 PM, Arnaud HERITIER wrote: >>> >>> What do you think about this post and comments : >>> >>>> http://relation.to/12116.laceOne thing that it seems to annoy them is >>>> how >>>> our reactor is working. >>>> We cannot call a build from a submodule which will automa(g)ically call >>>> necessary builds in others modules. >>>> >>>> Cheers, >>>> >>>> Arnaud >>>> >>>> # Arnaud Héritier >>>> # Software Factory Manager >>>> # eXo Platform >>>> # http://www.exoplatform.com >>>> # http://blog.aheritier.net >>>> >>>> >>> >>> - >>> 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: Hibernate feedback about Maven usage.
Partially, in fact they would like to have something easier to use.Instead of using command line args from the reactor project to say what to build, they would prefer to go directly in the submodule and to launch the build. On Tue, Aug 25, 2009 at 6:37 PM, Brett Porter wrote: > As the commenters said, the new reactor modes in 2.1 (and the reactor > plugin in 2.0) already satisfy those needs. > > - Brett > > On 25/08/2009, at 12:09 PM, Arnaud HERITIER wrote: > > What do you think about this post and comments : >> http://relation.to/12116.laceOne thing that it seems to annoy them is how >> our reactor is working. >> We cannot call a build from a submodule which will automa(g)ically call >> necessary builds in others modules. >> >> Cheers, >> >> Arnaud >> >> # Arnaud Héritier >> # Software Factory Manager >> # eXo Platform >> # http://www.exoplatform.com >> # http://blog.aheritier.net >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Hibernate feedback about Maven usage.
What do you think about this post and comments : http://relation.to/12116.laceOne thing that it seems to annoy them is how our reactor is working. We cannot call a build from a submodule which will automa(g)ically call necessary builds in others modules. Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net
Re: [ANN] Apache Source-Release Assembly Descriptor 1.0 Released
Before moving it to apache pom, we could ask to some others projects to validate it ? Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Sun, Aug 23, 2009 at 10:17 PM, Brian Fox wrote: > We still have some fixes to make before we promote it apache wide. > Once it's working for all our stuff we can upgrade the apache pom. > > On Fri, Aug 21, 2009 at 7:08 PM, Arnaud HERITIER > wrote: > > perhaps you could forward this to all PMCs ? > > Cheers, > > > > Arnaud > > > > # Arnaud Héritier > > # Software Factory Manager > > # eXo Platform > > # http://www.exoplatform.com > > # http://blog.aheritier.net > > > > > > On Sat, Aug 22, 2009 at 1:00 AM, John Casey wrote: > > > >> It appears that the site/repository synchronization is moving slowly, so > >> please be patient and these artifacts and site updates should be showing > up > >> before long. I want to make sure I get this announcement out before I > forget > >> it, though. > >> > >> --- > >> > >> The Maven team is pleased to announce the release of Apache > >> Source-Release Assembly Descriptor, version 1.0. > >> > >> This is a standardized assembly descriptor for use in the > >> maven-assembly-plugin. Source-release artifacts are archives which > >> contain the full project structure (sources only, no build output) that > >> are the subject of an ASF release vote. > >> > >> > >> > http://maven.apache.org/apache-resource-bundles/apache-source-release-assembly-descriptor/ > >> > >> This assembly descriptor should be coming to a parent POM near you, and > >> should eventually be an automatic part of every ASF release. For now, it > >> has been configured into the release process for Maven projects that > >> inherit from maven-parent version 13 (also recently released). If you > >> want to try out the source-release descriptor in the meantime, you can > >> include a configuration like the following: > >> > >> > >> > >> > >> maven-assembly-plugin > >> 2.2-beta-4 > >> > >> > >> > >> org.apache.apache.resources > >> > >> apache-source-release-assembly-descriptor > >> 1.0 > >> > >> > >> > >> > >> > >> source-release > >> package > >> > >>single > >> > >> > >> > >> source-release > >> > >>gnu > >>true > >> > >> > >> > >> > >> > >> > >> > >> Enjoy, > >> > >> The Maven Team > >> > >> -- > >> John Casey > >> Developer, PMC Member - Apache Maven (http://maven.apache.org) > >> Blog: http://www.ejlife.net/blogs/buildchimp/ > >> > >> > >> - > >> 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: [plexus-dev] [jira] Created: (PLXUTILS-117) The classes from org.codehaus.plexus.utils.interpolation are not self-contained
In theory, we remove things only in a major version (2.0).Otherwise : +1
Cheers,
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Sat, Aug 22, 2009 at 5:44 PM, Benjamin Bentmann <
benjamin.bentm...@udo.edu> wrote:
> The classes from org.codehaus.plexus.utils.interpolation are not
>> self-contained
>>
>> ---
>>
>> Key: PLXUTILS-117
>> URL: http://jira.codehaus.org/browse/PLXUTILS-117
>> Project: Plexus Utils
>> Issue Type: Bug
>>Affects Versions: 1.5.15
>>Reporter: Benjamin Bentmann
>> Attachments: pu-vs-pi.zip
>>
>> [r8255|http://fisheye.codehaus.org/changelog/plexus/?cs=8255] caused
>> exclusion of the plexus-interpolation classes from the plexus-utils JAR.
>> This in turn makes usage of the {{org.codehaus.plexus.utils.intepolation.*}}
>> classes from a standalone plexus-utils JAR impossible as their super classes
>> can't be resolved. See the attached demo project that fails upon "mvn clean
>> compile".
>>
>> Note sure whether the change in the above commit was actually necessary
>> given that previous plexus-utils versions like 1.5.12 apparently shipped
>> with a [dependency reduced POM|
>> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.5.12/plexus-utils-1.5.12.pom]
>> that already declared plexus-interpolation as provided.
>>
>> Declaring plexus-interpolation as provided in the original POM causes the
>> dependency to be ignored by the Shade Plugin because that uses
>> {...@requiresdependencyresolution runtime}} but provided dependencies are not
>> resolved for this resolution scope...
>>
>>
> How about if we just remove the org.codehaus.plexus.utils.intepolation
> package from plexus-utils, bump the version number for plexus-utils to 1.6
> and get back to a simple project that doesn't need fancy shading?
>
>
> Benjamin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
Re: [ANN] Apache Source-Release Assembly Descriptor 1.0 Released
perhaps you could forward this to all PMCs ? Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Sat, Aug 22, 2009 at 1:00 AM, John Casey wrote: > It appears that the site/repository synchronization is moving slowly, so > please be patient and these artifacts and site updates should be showing up > before long. I want to make sure I get this announcement out before I forget > it, though. > > --- > > The Maven team is pleased to announce the release of Apache > Source-Release Assembly Descriptor, version 1.0. > > This is a standardized assembly descriptor for use in the > maven-assembly-plugin. Source-release artifacts are archives which > contain the full project structure (sources only, no build output) that > are the subject of an ASF release vote. > > > http://maven.apache.org/apache-resource-bundles/apache-source-release-assembly-descriptor/ > > This assembly descriptor should be coming to a parent POM near you, and > should eventually be an automatic part of every ASF release. For now, it > has been configured into the release process for Maven projects that > inherit from maven-parent version 13 (also recently released). If you > want to try out the source-release descriptor in the meantime, you can > include a configuration like the following: > > > > > maven-assembly-plugin > 2.2-beta-4 > > > > org.apache.apache.resources > > apache-source-release-assembly-descriptor > 1.0 > > > > > > source-release > package > >single > > > > source-release > >gnu >true > > > > > > > > Enjoy, > > The Maven Team > > -- > John Casey > Developer, PMC Member - Apache Maven (http://maven.apache.org) > Blog: http://www.ejlife.net/blogs/buildchimp/ > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [RESULT] [VOTE] [2nd try] Release Maven Common Artifact Filters version 1.2
Artifacts are uploaded : http://repo2.maven.org/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.2/But the website isn't sync : http://maven.apache.org/shared/maven-common-artifact-filters/ When is it synchronized ? Do we have to announce shared components? Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Thu, Aug 20, 2009 at 10:55 AM, Arnaud HERITIER wrote: > The vote has passed with : > > 3 binding votes : Benjamin, John and myself > 1 non-binding vote : Stephen > > I finalize the release process. > > Cheers, > > Arnaud > > # Arnaud Héritier > # Software Factory Manager > # eXo Platform > # http://www.exoplatform.com > # http://blog.aheritier.net > > > On Wed, Aug 19, 2009 at 12:22 PM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> damn me and my counting... I though the new vote was up last night >> >> 2009/8/19 Arnaud HERITIER : >> > The new vote was launched at Sun, Aug 16, 2009 at 11:20 PM >> > We have to wait for 72h thus tonight at 11:20PM >> > Arnaud >> > >> > On Wed, Aug 19, 2009 at 11:20 AM, Stephen Connolly < >> > stephen.alan.conno...@gmail.com> wrote: >> > >> >> Has this vote passed? >> >> >> >> By my counting we have: >> >> >> >> +1: Arnaud, Benjamin, John >> >> 0: >> >> -1: >> >> >> >> Arnaud, I know you're busy, but when can we get this promoted so I can >> >> call the vote for versions-maven-plugin 1.0 >> >> >> >> -Stephen >> >> >> >> 2009/8/17 John Casey : >> >> > +1 >> >> > >> >> > Arnaud HERITIER wrote: >> >> >> >> >> >> Hi, >> >> >> >> >> >> We solved 4 >> >> >> issues: >> >> >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14868 >> >> >> >> >> >> I added the standard source distribution for Apache. >> >> >> >> >> >> >> >> >> There are no issue left in JIRA. We need this release for the next >> >> >> version of the versions-maven-plugin @ mojo. >> >> >> >> >> >> Staging >> >> >> repo: >> >> https://repository.apache.org/content/repositories/maven-staging-027/ >> >> >> >> >> >> Staging >> >> >> site: >> http://maven.apache.org/shared/maven-common-artifact-filters-1.2/ >> >> >> >> >> >> Guide to testing staged >> >> >> >> >> >> releases: >> >> http://maven.apache.org/guides/development/guide-testing-releases.html >> >> >> >> >> >> Vote open for 72 hours. >> >> >> >> >> >> [ ] +1 >> >> >> [ ] +0 >> >> >> [ ] -1 >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> My +1 >> >> >> >> >> >> >> >> >> >> >> >> Cheers, >> >> >> >> >> >> Arnaud >> >> >> >> >> >> # Arnaud Héritier >> >> >> # Software Factory Manager >> >> >> # eXo Platform >> >> >> # http://www.exoplatform.com >> >> >> # http://blog.aheritier.net >> >> >> Cheers, >> >> >> >> >> >> Arnaud >> >> >> >> >> >> # Arnaud Héritier >> >> >> # Software Factory Manager >> >> >> # eXo Platform >> >> >> # http://www.exoplatform.com >> >> >> # http://blog.aheritier.net >> >> >> >> >> > >> >> > - >> >> > 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 >> >> >> >> >> > >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >
[RESULT] [VOTE] [2nd try] Release Maven Common Artifact Filters version 1.2
The vote has passed with : 3 binding votes : Benjamin, John and myself 1 non-binding vote : Stephen I finalize the release process. Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Wed, Aug 19, 2009 at 12:22 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > damn me and my counting... I though the new vote was up last night > > 2009/8/19 Arnaud HERITIER : > > The new vote was launched at Sun, Aug 16, 2009 at 11:20 PM > > We have to wait for 72h thus tonight at 11:20PM > > Arnaud > > > > On Wed, Aug 19, 2009 at 11:20 AM, Stephen Connolly < > > stephen.alan.conno...@gmail.com> wrote: > > > >> Has this vote passed? > >> > >> By my counting we have: > >> > >> +1: Arnaud, Benjamin, John > >> 0: > >> -1: > >> > >> Arnaud, I know you're busy, but when can we get this promoted so I can > >> call the vote for versions-maven-plugin 1.0 > >> > >> -Stephen > >> > >> 2009/8/17 John Casey : > >> > +1 > >> > > >> > Arnaud HERITIER wrote: > >> >> > >> >> Hi, > >> >> > >> >> We solved 4 > >> >> issues: > >> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14868 > >> >> > >> >> I added the standard source distribution for Apache. > >> >> > >> >> > >> >> There are no issue left in JIRA. We need this release for the next > >> >> version of the versions-maven-plugin @ mojo. > >> >> > >> >> Staging > >> >> repo: > >> https://repository.apache.org/content/repositories/maven-staging-027/ > >> >> > >> >> Staging > >> >> site: > http://maven.apache.org/shared/maven-common-artifact-filters-1.2/ > >> >> > >> >> Guide to testing staged > >> >> > >> >> releases: > >> http://maven.apache.org/guides/development/guide-testing-releases.html > >> >> > >> >> Vote open for 72 hours. > >> >> > >> >> [ ] +1 > >> >> [ ] +0 > >> >> [ ] -1 > >> >> > >> >> > >> >> > >> >> > >> >> My +1 > >> >> > >> >> > >> >> > >> >> Cheers, > >> >> > >> >> Arnaud > >> >> > >> >> # Arnaud Héritier > >> >> # Software Factory Manager > >> >> # eXo Platform > >> >> # http://www.exoplatform.com > >> >> # http://blog.aheritier.net > >> >> Cheers, > >> >> > >> >> Arnaud > >> >> > >> >> # Arnaud Héritier > >> >> # Software Factory Manager > >> >> # eXo Platform > >> >> # http://www.exoplatform.com > >> >> # http://blog.aheritier.net > >> >> > >> > > >> > - > >> > 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 > >> > >> > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] [2nd try] Release Maven Common Artifact Filters version 1.2
The new vote was launched at Sun, Aug 16, 2009 at 11:20 PM We have to wait for 72h thus tonight at 11:20PM Arnaud On Wed, Aug 19, 2009 at 11:20 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Has this vote passed? > > By my counting we have: > > +1: Arnaud, Benjamin, John > 0: > -1: > > Arnaud, I know you're busy, but when can we get this promoted so I can > call the vote for versions-maven-plugin 1.0 > > -Stephen > > 2009/8/17 John Casey : > > +1 > > > > Arnaud HERITIER wrote: > >> > >> Hi, > >> > >> We solved 4 > >> issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14868 > >> > >> I added the standard source distribution for Apache. > >> > >> > >> There are no issue left in JIRA. We need this release for the next > >> version of the versions-maven-plugin @ mojo. > >> > >> Staging > >> repo: > https://repository.apache.org/content/repositories/maven-staging-027/ > >> > >> Staging > >> site:http://maven.apache.org/shared/maven-common-artifact-filters-1.2/ > >> > >> Guide to testing staged > >> > >> releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > >> > >> Vote open for 72 hours. > >> > >> [ ] +1 > >> [ ] +0 > >> [ ] -1 > >> > >> > >> > >> > >> My +1 > >> > >> > >> > >> Cheers, > >> > >> Arnaud > >> > >> # Arnaud Héritier > >> # Software Factory Manager > >> # eXo Platform > >> # http://www.exoplatform.com > >> # http://blog.aheritier.net > >> Cheers, > >> > >> Arnaud > >> > >> # Arnaud Héritier > >> # Software Factory Manager > >> # eXo Platform > >> # http://www.exoplatform.com > >> # http://blog.aheritier.net > >> > > > > - > > 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 > >
[VOTE] [2nd try] Release Maven Common Artifact Filters version 1.2
Hi, We solved 4 issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14868 I added the standard source distribution for Apache. There are no issue left in JIRA. We need this release for the next version of the versions-maven-plugin @ mojo. Staging repo:https://repository.apache.org/content/repositories/maven-staging-027/ Staging site:http://maven.apache.org/shared/maven-common-artifact-filters-1.2/ Guide to testing staged releases:http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 My +1 Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net
Re: [VOTE] Release Maven Common Artifact Filters version 1.2
I did a mix and copied the future descriptor in thé project. I Will call for another vote this evening. Thanks for your help. Do we have an idea about when we won't have to do that. If it's not in a few delay we could update the release guide? Envoyé de mon iPhone Le 16 août 2009 à 14:47, Benjamin Bentmann a écrit : Arnaud HERITIER wrote: Must I add this : release [...] Or this : apache-release [...] ?? Given the effective POM for the artifact filters says maven-release-plugin 2.0-beta-8 -Prelease ... you would need a profile named "release" or otherwise perform addition steps to ensure "apache-release" gets activated. Benjamin - 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: svn commit: r804685 - /maven/shared/trunk/maven-common-artifact-filters/pom.xml
No I wanted something simple but it isn't because this snapshot isn't deployed.I have to copy the descriptor On Sun, Aug 16, 2009 at 3:01 PM, Benjamin Bentmann < benjamin.bentm...@udo.edu> wrote: > Hi Arnaud, > > Author: aheritier >> Date: Sun Aug 16 12:54:37 2009 >> New Revision: 804685 >> >> URL: http://svn.apache.org/viewvc?rev=804685&view=rev >> Log: >> Add source distrib for apache >> >> Modified: >>maven/shared/trunk/maven-common-artifact-filters/pom.xml >> >> Modified: maven/shared/trunk/maven-common-artifact-filters/pom.xml >> URL: >> http://svn.apache.org/viewvc/maven/shared/trunk/maven-common-artifact-filters/pom.xml?rev=804685&r1=804684&r2=804685&view=diff >> >> == >> --- maven/shared/trunk/maven-common-artifact-filters/pom.xml (original) >> +++ maven/shared/trunk/maven-common-artifact-filters/pom.xml Sun Aug 16 >> 12:54:37 2009 >> + >> +maven-assembly-plugin >> +2.2-beta-4 >> + >> + >> +org.apache >> + >> apache-source-release-assembly-descriptor >> +1.0-SNAPSHOT >> + >> > > Are you sure you want to use a SNAPSHOT for the release? > > > Benjamin > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
