Discussion:
[VOTE] Apache 3.1.0-alpha-1
(too old to reply)
Jason van Zyl
2013-04-01 12:12:09 UTC
Permalink
Here are the release bits for 3.1.0-alpha-1:

Release notes:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967

Staging repository:
https://repository.apache.org/content/repositories/maven-042/

Staged distribution:
https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/

Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it.

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

We know what we are, but know not what we may be.

-- Shakespeare
Igor Fedorenko
2013-04-01 12:19:26 UTC
Permalink
Tycho is not compatible with 3.1.0-alpha-1 either.

--
Regards,
Igor
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
Baptiste MATHUS
2013-04-01 13:36:20 UTC
Permalink
Just tried it, seems like there's a missing newline when using -V.
With m3.0.4:

*$ mvn -V clean verify*
*Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)*
*Maven home: /home/tiste/tools/Mavens/maven*
*Java version: 1.6.0_37, vendor: Sun Microsystems Inc.*
*Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre*
*Default locale: fr_FR, platform encoding: UTF-8*
*OS name: "linux", version: "3.5.0-26-generic", arch: "amd64", family:
"unix"*
*[INFO] Scanning for projects...*
*[INFO] *



With m3.1.0-alpha-1:

*$ mvn -V clean verify*
*Apache Maven 3.1.0-alpha-1 (262b9bb1ef91d1414e5162d9dd0f5522e7186202;
2013-03-30 22:38:49+0100)*
*Maven home: /home/tiste/tools/Mavens/maven*
*Java version: 1.6.0_37, vendor: Sun Microsystems Inc.*
*Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre*
*Default locale: fr_FR, platform encoding: UTF-8*
*OS name: "linux", version: "3.5.0-26-generic", arch: "amd64", family:
"unix"[INFO] Scanning for projects...*
*[INFO] *


Is this confirmed by someone else? Should I file an issue about this one?

Thanks
Post by Igor Fedorenko
Tycho is not compatible with 3.1.0-alpha-1 either.
--
Regards,
Igor
https://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=10500&version=18967<https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967>
https://repository.apache.org/**content/repositories/maven-**042/<https://repository.apache.org/content/repositories/maven-042/>
https://repository.apache.org/**content/repositories/maven-**
042/org/apache/maven/apache-**maven/3.1.0-alpha-1/<https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/>
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
------------------------------**----------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
------------------------------**---------------------------
We know what we are, but know not what we may be.
-- Shakespeare
------------------------------**------------------------------**---------
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Jason van Zyl
2013-04-01 14:09:16 UTC
Permalink
Sure, log an issue. I don't consider it a show stopper.
Post by Baptiste MATHUS
Just tried it, seems like there's a missing newline when using -V.
*$ mvn -V clean verify*
*Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)*
*Maven home: /home/tiste/tools/Mavens/maven*
*Java version: 1.6.0_37, vendor: Sun Microsystems Inc.*
*Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre*
*Default locale: fr_FR, platform encoding: UTF-8*
"unix"*
*[INFO] Scanning for projects...*
*[INFO] *
*$ mvn -V clean verify*
*Apache Maven 3.1.0-alpha-1 (262b9bb1ef91d1414e5162d9dd0f5522e7186202;
2013-03-30 22:38:49+0100)*
*Maven home: /home/tiste/tools/Mavens/maven*
*Java version: 1.6.0_37, vendor: Sun Microsystems Inc.*
*Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre*
*Default locale: fr_FR, platform encoding: UTF-8*
"unix"[INFO] Scanning for projects...*
*[INFO] *
Is this confirmed by someone else? Should I file an issue about this one?
Thanks
Post by Igor Fedorenko
Tycho is not compatible with 3.1.0-alpha-1 either.
--
Regards,
Igor
https://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=10500&version=18967<https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967>
https://repository.apache.org/**content/repositories/maven-**042/<https://repository.apache.org/content/repositories/maven-042/>
https://repository.apache.org/**content/repositories/maven-**
042/org/apache/maven/apache-**maven/3.1.0-alpha-1/<https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/>
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
------------------------------**----------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
------------------------------**---------------------------
We know what we are, but know not what we may be.
-- Shakespeare
------------------------------**------------------------------**---------
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Three people can keep a secret provided two of them are dead.

-- Benjamin Franklin
Baptiste MATHUS
2013-04-01 14:14:19 UTC
Permalink
Sure, neither do I, even less for an alpha release.
http://jira.codehaus.org/browse/MNG-5458

Cheers
Post by Jason van Zyl
Sure, log an issue. I don't consider it a show stopper.
Post by Baptiste MATHUS
Just tried it, seems like there's a missing newline when using -V.
*$ mvn -V clean verify*
*Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)*
*Maven home: /home/tiste/tools/Mavens/maven*
*Java version: 1.6.0_37, vendor: Sun Microsystems Inc.*
*Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre*
*Default locale: fr_FR, platform encoding: UTF-8*
"unix"*
*[INFO] Scanning for projects...*
*[INFO] *
*$ mvn -V clean verify*
*Apache Maven 3.1.0-alpha-1 (262b9bb1ef91d1414e5162d9dd0f5522e7186202;
2013-03-30 22:38:49+0100)*
*Maven home: /home/tiste/tools/Mavens/maven*
*Java version: 1.6.0_37, vendor: Sun Microsystems Inc.*
*Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre*
*Default locale: fr_FR, platform encoding: UTF-8*
"unix"[INFO] Scanning for projects...*
*[INFO] *
Is this confirmed by someone else? Should I file an issue about this one?
Thanks
Post by Igor Fedorenko
Tycho is not compatible with 3.1.0-alpha-1 either.
--
Regards,
Igor
https://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=10500&version=18967<
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
Post by Baptiste MATHUS
Post by Igor Fedorenko
https://repository.apache.org/**content/repositories/maven-**042/<
https://repository.apache.org/content/repositories/maven-042/>
Post by Baptiste MATHUS
Post by Igor Fedorenko
https://repository.apache.org/**content/repositories/maven-**
042/org/apache/maven/apache-**maven/3.1.0-alpha-1/<
https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/
Post by Baptiste MATHUS
Post by Igor Fedorenko
Anyone trying this in advance should know that the Site, Dependency,
and
Post by Baptiste MATHUS
Post by Igor Fedorenko
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
------------------------------**----------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
------------------------------**---------------------------
We know what we are, but know not what we may be.
-- Shakespeare
------------------------------**------------------------------**---------
Post by Baptiste MATHUS
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Three people can keep a secret provided two of them are dead.
-- Benjamin Franklin
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Jason van Zyl
2013-04-01 14:20:13 UTC
Permalink
Are you on Windows?
Post by Baptiste MATHUS
Sure, neither do I, even less for an alpha release.
http://jira.codehaus.org/browse/MNG-5458
Cheers
Post by Jason van Zyl
Sure, log an issue. I don't consider it a show stopper.
Post by Baptiste MATHUS
Just tried it, seems like there's a missing newline when using -V.
*$ mvn -V clean verify*
*Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)*
*Maven home: /home/tiste/tools/Mavens/maven*
*Java version: 1.6.0_37, vendor: Sun Microsystems Inc.*
*Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre*
*Default locale: fr_FR, platform encoding: UTF-8*
"unix"*
*[INFO] Scanning for projects...*
*[INFO] *
*$ mvn -V clean verify*
*Apache Maven 3.1.0-alpha-1 (262b9bb1ef91d1414e5162d9dd0f5522e7186202;
2013-03-30 22:38:49+0100)*
*Maven home: /home/tiste/tools/Mavens/maven*
*Java version: 1.6.0_37, vendor: Sun Microsystems Inc.*
*Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre*
*Default locale: fr_FR, platform encoding: UTF-8*
"unix"[INFO] Scanning for projects...*
*[INFO] *
Is this confirmed by someone else? Should I file an issue about this one?
Thanks
Post by Igor Fedorenko
Tycho is not compatible with 3.1.0-alpha-1 either.
--
Regards,
Igor
https://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=10500&version=18967<
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
Post by Baptiste MATHUS
Post by Igor Fedorenko
https://repository.apache.org/**content/repositories/maven-**042/<
https://repository.apache.org/content/repositories/maven-042/>
Post by Baptiste MATHUS
Post by Igor Fedorenko
https://repository.apache.org/**content/repositories/maven-**
042/org/apache/maven/apache-**maven/3.1.0-alpha-1/<
https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/
Post by Baptiste MATHUS
Post by Igor Fedorenko
Anyone trying this in advance should know that the Site, Dependency,
and
Post by Baptiste MATHUS
Post by Igor Fedorenko
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
------------------------------**----------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
------------------------------**---------------------------
We know what we are, but know not what we may be.
-- Shakespeare
------------------------------**------------------------------**---------
Post by Baptiste MATHUS
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Three people can keep a secret provided two of them are dead.
-- Benjamin Franklin
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

-- Thoreau
Baptiste MATHUS
2013-04-01 14:28:09 UTC
Permalink
Nope, Linux x64.
Post by Jason van Zyl
Are you on Windows?
Post by Baptiste MATHUS
Sure, neither do I, even less for an alpha release.
http://jira.codehaus.org/browse/MNG-5458
Cheers
Post by Jason van Zyl
Sure, log an issue. I don't consider it a show stopper.
Post by Baptiste MATHUS
Just tried it, seems like there's a missing newline when using -V.
*$ mvn -V clean verify*
*Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)*
*Maven home: /home/tiste/tools/Mavens/maven*
*Java version: 1.6.0_37, vendor: Sun Microsystems Inc.*
*Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre*
*Default locale: fr_FR, platform encoding: UTF-8*
"unix"*
*[INFO] Scanning for projects...*
*[INFO] *
*$ mvn -V clean verify*
*Apache Maven 3.1.0-alpha-1 (262b9bb1ef91d1414e5162d9dd0f5522e7186202;
2013-03-30 22:38:49+0100)*
*Maven home: /home/tiste/tools/Mavens/maven*
*Java version: 1.6.0_37, vendor: Sun Microsystems Inc.*
*Java home: /home/tiste/tools/JDKs/jdk1.6.0_37/jre*
*Default locale: fr_FR, platform encoding: UTF-8*
"unix"[INFO] Scanning for projects...*
*[INFO] *
Is this confirmed by someone else? Should I file an issue about this
one?
Post by Baptiste MATHUS
Post by Jason van Zyl
Post by Baptiste MATHUS
Thanks
Post by Igor Fedorenko
Tycho is not compatible with 3.1.0-alpha-1 either.
--
Regards,
Igor
https://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=10500&version=18967<
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
Post by Baptiste MATHUS
Post by Jason van Zyl
Post by Baptiste MATHUS
Post by Igor Fedorenko
https://repository.apache.org/**content/repositories/maven-**042/<
https://repository.apache.org/content/repositories/maven-042/>
Post by Baptiste MATHUS
Post by Igor Fedorenko
https://repository.apache.org/**content/repositories/maven-**
042/org/apache/maven/apache-**maven/3.1.0-alpha-1/<
https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/
Post by Baptiste MATHUS
Post by Jason van Zyl
Post by Baptiste MATHUS
Post by Igor Fedorenko
Anyone trying this in advance should know that the Site, Dependency,
and
Post by Baptiste MATHUS
Post by Igor Fedorenko
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
------------------------------**----------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
------------------------------**---------------------------
We know what we are, but know not what we may be.
-- Shakespeare
------------------------------**------------------------------**---------
Post by Baptiste MATHUS
Post by Jason van Zyl
Post by Baptiste MATHUS
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Three people can keep a secret provided two of them are dead.
-- Benjamin Franklin
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Andrei Pozolotin
2013-04-02 15:26:39 UTC
Permalink
I am curious if 3.1.0 will be more relaxed with custom tags inside
<dependency>?

Use case: karaf-maven-plugin uses bizarre conventions
on how to map from <scope> into osgi bundle properties (like start level)
because there is no way to have a custom tag in <dependency> and express
this requirement.

-------- Original Message --------
Subject: [VOTE] Apache 3.1.0-alpha-1
From: Jason van Zyl <***@tesla.io>
To: Maven Developers List <***@maven.apache.org>
Date: Mon 01 Apr 2013 07:12:09 AM CDT
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
Hervé BOUTEMY
2013-04-02 17:00:36 UTC
Permalink
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/

Regards,

Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/mave
n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
Jason van Zyl
2013-04-02 17:04:18 UTC
Permalink
Thanks.
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/mave
n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people.

-- Paul Graham
Andrei Pozolotin
2013-04-03 13:51:01 UTC
Permalink
I am curious if 3.1.0 will be more relaxed with custom tags inside
<dependency>?

Use case: karaf-maven-plugin uses bizarre conventions
on how to map from <scope> into osgi bundle properties (like start level)
because there is no way to have a custom tag in <dependency> and express
this requirement.

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Jason van Zyl <***@tesla.io>
To: Maven Developers List <***@maven.apache.org>
Date: Tue 02 Apr 2013 12:04:18 PM CDT
Post by Jason van Zyl
Thanks.
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/mave
n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
Manfred Moser
2013-04-03 15:58:36 UTC
Permalink
+1 from me (non binding whatsoever but anyway)

I tested it with the build for the android maven plugin and ksoap2-android
and a few other projects.

Apart from the expected problems with shade, site and dependency plugin
the android maven plugin also fails with this due to accessing Aether
directly (as expected)

Anyway... I would really like to move on and get 3.1.0 out, then adapt the
android maven plugin to it and make 3.1 required asap.

Is there something happening with this vote at all? Is somebody from the
PMC at least looking?

And lastly.. about the site.. I am not sure where this will go in the form
it is on the staging site .. what content on the current site would it
replace?

Thanks for all the hard work so far. Lets get this out the door!

manfred
Post by Andrei Pozolotin
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Tue 02 Apr 2013 12:04:18 PM CDT
Post by Jason van Zyl
Thanks.
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/mave
n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people can
fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
Stephen Connolly
2013-04-03 16:08:50 UTC
Permalink
I am still poking around with it... when I am happy that I trust it I will
vote... AFAIR we are not running with the strict 72h anyways given the
scope of this change in terms of moving APIs
Post by Manfred Moser
+1 from me (non binding whatsoever but anyway)
I tested it with the build for the android maven plugin and ksoap2-android
and a few other projects.
Apart from the expected problems with shade, site and dependency plugin
the android maven plugin also fails with this due to accessing Aether
directly (as expected)
Anyway... I would really like to move on and get 3.1.0 out, then adapt the
android maven plugin to it and make 3.1 required asap.
Is there something happening with this vote at all? Is somebody from the
PMC at least looking?
And lastly.. about the site.. I am not sure where this will go in the form
it is on the staging site .. what content on the current site would it
replace?
Thanks for all the hard work so far. Lets get this out the door!
manfred
Post by Andrei Pozolotin
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Tue 02 Apr 2013 12:04:18 PM CDT
Post by Jason van Zyl
Thanks.
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
Post by Andrei Pozolotin
Post by Jason van Zyl
Post by Hervé BOUTEMY
Post by Jason van Zyl
967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/mave
Post by Andrei Pozolotin
Post by Jason van Zyl
Post by Hervé BOUTEMY
Post by Jason van Zyl
n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people can
fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
---------------------------------------------------------------------
Manfred Moser
2013-04-03 18:41:51 UTC
Permalink
Thats fine.. it was just very quiet.

Thanks Stephen.

manfred
Post by Stephen Connolly
I am still poking around with it... when I am happy that I trust it I will
vote... AFAIR we are not running with the strict 72h anyways given the
scope of this change in terms of moving APIs
Post by Manfred Moser
+1 from me (non binding whatsoever but anyway)
I tested it with the build for the android maven plugin and
ksoap2-android
and a few other projects.
Apart from the expected problems with shade, site and dependency plugin
the android maven plugin also fails with this due to accessing Aether
directly (as expected)
Anyway... I would really like to move on and get 3.1.0 out, then adapt the
android maven plugin to it and make 3.1 required asap.
Is there something happening with this vote at all? Is somebody from the
PMC at least looking?
And lastly.. about the site.. I am not sure where this will go in the form
it is on the staging site .. what content on the current site would it
replace?
Thanks for all the hard work so far. Lets get this out the door!
manfred
Post by Andrei Pozolotin
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Tue 02 Apr 2013 12:04:18 PM CDT
Post by Jason van Zyl
Thanks.
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
Post by Andrei Pozolotin
Post by Jason van Zyl
Post by Hervé BOUTEMY
Post by Jason van Zyl
967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/mave
Post by Andrei Pozolotin
Post by Jason van Zyl
Post by Hervé BOUTEMY
Post by Jason van Zyl
n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site,
Dependency,
Post by Andrei Pozolotin
Post by Jason van Zyl
Post by Hervé BOUTEMY
Post by Jason van Zyl
and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people
can
Post by Andrei Pozolotin
Post by Jason van Zyl
fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
---------------------------------------------------------------------
Hervé BOUTEMY
2013-04-04 06:22:30 UTC
Permalink
Post by Manfred Moser
And lastly.. about the site.. I am not sure where this will go in the form
it is on the staging site .. what content on the current site would it
replace?
I don't understand, please explain

Regards,

Hervé
Post by Manfred Moser
+1 from me (non binding whatsoever but anyway)
I tested it with the build for the android maven plugin and ksoap2-android
and a few other projects.
Apart from the expected problems with shade, site and dependency plugin
the android maven plugin also fails with this due to accessing Aether
directly (as expected)
Anyway... I would really like to move on and get 3.1.0 out, then adapt the
android maven plugin to it and make 3.1 required asap.
Is there something happening with this vote at all? Is somebody from the
PMC at least looking?
And lastly.. about the site.. I am not sure where this will go in the form
it is on the staging site .. what content on the current site would it
replace?
Thanks for all the hard work so far. Lets get this out the door!
manfred
Post by Andrei Pozolotin
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Tue 02 Apr 2013 12:04:18 PM CDT
Post by Jason van Zyl
Thanks.
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&versi
on=18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache
/mave n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people can
fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
---------------------------------------------------------------------
Hervé BOUTEMY
2013-04-04 06:21:32 UTC
Permalink
AFAIK, there is nothing "relaxed" from Mven 3.0.x planned

But I don't really understand your case (and miss time to investigate in
Karaf).
Can you give us a pointer to SCM, or paste such a dependency "with custom
tags"?

Regards,

Hervé
Post by Andrei Pozolotin
I am curious if 3.1.0 will be more relaxed with custom tags inside
<dependency>?
Use case: karaf-maven-plugin uses bizarre conventions
on how to map from <scope> into osgi bundle properties (like start level)
because there is no way to have a custom tag in <dependency> and express
this requirement.
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Tue 02 Apr 2013 12:04:18 PM CDT
Post by Jason van Zyl
Thanks.
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&versio
n=18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/
mave n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people can
fix bad ideas, but good ideas can't save bad people.>
-- Paul Graham
Andrei Pozolotin
2013-04-04 13:57:36 UTC
Permalink
Hervé:

thank you for taking the time to respond.

issue at hand:

karaf
http://karaf.apache.org/

has features.xml, which are built from pom.xml
http://karaf.apache.org/manual/latest-2.3.x/users-guide/provisioning.html

what is missing from maven is the ability to communicate arbitrary
custom attributes
on per-dependency basis, such as:

provide osgiStartLevel value, to specify to osgi runtime bundle start level:
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
<osgiStartLevel>99</osgiStartLevel>
</dependency>

or provide karafBootInstall flag, to specify that karaf runtime should
install this dependency at boot-time vs build-time:
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle-feature</artifactId>
<version>1.0.1</version>
<classifier>features</classifier>
<type>xml</type>
<karafBootInstall>true</karafBootInstall>
</dependency>

in lieu of these, karaf-maven-plugin is trying to encode this
information via <scope>
https://github.com/apache/karaf/blob/trunk/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/features/InstallKarsMojo.java#L215

which contradicts the dependency resolution rules and really does not work.

hence my request to "relax". is there any other ways to address this need?

Andrei

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Hervé BOUTEMY <***@free.fr>
To: Maven Developers List <***@maven.apache.org>
Date: Thu 04 Apr 2013 01:21:32 AM CDT
Post by Hervé BOUTEMY
AFAIK, there is nothing "relaxed" from Mven 3.0.x planned
But I don't really understand your case (and miss time to investigate in
Karaf).
Can you give us a pointer to SCM, or paste such a dependency "with custom
tags"?
Regards,
Hervé
Post by Andrei Pozolotin
I am curious if 3.1.0 will be more relaxed with custom tags inside
<dependency>?
Use case: karaf-maven-plugin uses bizarre conventions
on how to map from <scope> into osgi bundle properties (like start level)
because there is no way to have a custom tag in <dependency> and express
this requirement.
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Tue 02 Apr 2013 12:04:18 PM CDT
Post by Jason van Zyl
Thanks.
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&versio
n=18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/
mave n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people can
fix bad ideas, but good ideas can't save bad people.>
-- Paul Graham
---------------------------------------------------------------------
.
Wayne Fay
2013-04-04 14:43:24 UTC
Permalink
Post by Andrei Pozolotin
what is missing from maven is the ability to communicate arbitrary
custom attributes
...
Post by Andrei Pozolotin
or provide karafBootInstall flag, to specify that karaf runtime should
...
Post by Andrei Pozolotin
in lieu of these, karaf-maven-plugin is trying to encode this
information via <scope>
https://github.com/apache/karaf/blob/trunk/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/features/InstallKarsMojo.java#L215
which contradicts the dependency resolution rules and really does not work.
hence my request to "relax". is there any other ways to address this need?
IMO this can and should all be handled via configuration in the
karaf-m-p and not via adding attributes in dependencies which are
specific to one plugin. Otherwise the Assembly plugin could reasonably
ask to put "outputFileNameMapping" as an (optional) attribute of the
dependency, and the Ear plugin could ask to put "bundleFileName" as an
(optional) attribute, etc. That way lies madness.

Look at how Assembly and Ear plugins (and others) are doing similar
things for guidance on how to implement these features in the karaf
plugin itself. FWIW I agree that doing it via <scope> is the wrong way
to do it.

Wayne
Andrei Pozolotin
2013-04-04 14:52:28 UTC
Permalink
Wayne:

the way I understand your suggestions is essentially I must duplicate
configuration:

1) first I have to mention the <dependency>, because I need the dependency

2) second, I need some extra entry somewhere to map same <dependency> to
custom properties.

am I getting you right?

Andrei.

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Wayne Fay <***@gmail.com>
To: Maven Developers List <***@maven.apache.org>
Date: Thu 04 Apr 2013 09:43:24 AM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
what is missing from maven is the ability to communicate arbitrary
custom attributes
...
Post by Andrei Pozolotin
or provide karafBootInstall flag, to specify that karaf runtime should
...
Post by Andrei Pozolotin
in lieu of these, karaf-maven-plugin is trying to encode this
information via <scope>
https://github.com/apache/karaf/blob/trunk/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/features/InstallKarsMojo.java#L215
which contradicts the dependency resolution rules and really does not work.
hence my request to "relax". is there any other ways to address this need?
IMO this can and should all be handled via configuration in the
karaf-m-p and not via adding attributes in dependencies which are
specific to one plugin. Otherwise the Assembly plugin could reasonably
ask to put "outputFileNameMapping" as an (optional) attribute of the
dependency, and the Ear plugin could ask to put "bundleFileName" as an
(optional) attribute, etc. That way lies madness.
Look at how Assembly and Ear plugins (and others) are doing similar
things for guidance on how to implement these features in the karaf
plugin itself. FWIW I agree that doing it via <scope> is the wrong way
to do it.
Wayne
---------------------------------------------------------------------
Wayne Fay
2013-04-04 14:56:40 UTC
Permalink
Post by Andrei Pozolotin
the way I understand your suggestions is essentially I must duplicate
Yes, just like you do with the other plugins mentioned.

Wayne
Andrei Pozolotin
2013-04-04 15:03:25 UTC
Permalink
*Wayne*

1) in this case "I choose madness" :-)

2) here is my request:
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.

Thank you,

Andrei

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Wayne Fay <***@gmail.com>
To: Andrei Pozolotin <***@gmail.com>
Cc: Maven Developers List <***@maven.apache.org>
Date: Thu 04 Apr 2013 09:56:40 AM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
the way I understand your suggestions is essentially I must duplicate
Yes, just like you do with the other plugins mentioned.
Wayne
Fred Cooke
2013-04-04 15:31:57 UTC
Permalink
Can you not programatically access the dependencies by index? Sure it would
be fragile to dep order changes, but it would not be duplication. +1 to
everything Wayne said.
Post by Andrei Pozolotin
*Wayne*
1) in this case "I choose madness" :-)
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 09:56:40 AM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
the way I understand your suggestions is essentially I must duplicate
Yes, just like you do with the other plugins mentioned.
Wayne
Andrei Pozolotin
2013-04-04 15:53:22 UTC
Permalink
Fred

I am sorry I do not understand what you mean. Can you please clarify?

The only reason am I bothering people on maven dev list is because
maven refuses to work at all when I add custom xml entries to the
<dependency>.
I would assume it would be easy change just to ignore things maven
does not expect, and do not blow up.

Thank you,

Andrei

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Fred Cooke <***@gmail.com>
To: Maven Developers List <***@maven.apache.org>
Date: Thu 04 Apr 2013 10:31:57 AM CDT
Post by Fred Cooke
Can you not programatically access the dependencies by index? Sure it would
be fragile to dep order changes, but it would not be duplication. +1 to
everything Wayne said.
Post by Andrei Pozolotin
*Wayne*
1) in this case "I choose madness" :-)
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 09:56:40 AM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
the way I understand your suggestions is essentially I must duplicate
Yes, just like you do with the other plugins mentioned.
Wayne
Fred Cooke
2013-04-04 16:14:46 UTC
Permalink
I mean, you can grab any array pom properties by index in a variable, why
not do it in code, if you don't want duplication. This way the fragility is
limited to index and easily fixed if it gets messed up by an added
dependency.

http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
http://jira.codehaus.org/browse/PLXUTILS-37

It's just an idea, and not something I'd do.

Fred.
Post by Andrei Pozolotin
Fred
I am sorry I do not understand what you mean. Can you please clarify?
The only reason am I bothering people on maven dev list is because
maven refuses to work at all when I add custom xml entries to the
<dependency>.
I would assume it would be easy change just to ignore things maven does
not expect, and do not blow up.
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 10:31:57 AM CDT
Can you not programatically access the dependencies by index? Sure it would
be fragile to dep order changes, but it would not be duplication. +1 to
everything Wayne said.
*Wayne*
1) in this case "I choose madness" :-)
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 09:56:40 AM CDT
the way I understand your suggestions is essentially I must duplicate
Yes, just like you do with the other plugins mentioned.
Wayne
Andrei Pozolotin
2013-04-04 16:33:25 UTC
Permalink
got it, thank you. I still would like you to conciser my change request.

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Fred Cooke <***@gmail.com>
To: Andrei Pozolotin <***@gmail.com>
Cc: Maven Developers List <***@maven.apache.org>
Date: Thu 04 Apr 2013 11:14:46 AM CDT
Post by Fred Cooke
I mean, you can grab any array pom properties by index in a variable,
why not do it in code, if you don't want duplication. This way the
fragility is limited to index and easily fixed if it gets messed up by
an added dependency.
http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
http://jira.codehaus.org/browse/PLXUTILS-37
It's just an idea, and not something I'd do.
Fred.
On Thu, Apr 4, 2013 at 5:53 PM, Andrei Pozolotin
Fred
I am sorry I do not understand what you mean. Can you please clarify?
The only reason am I bothering people on maven dev list is because
maven refuses to work at all when I add custom xml entries to
the <dependency>.
I would assume it would be easy change just to ignore things
maven does not expect, and do not blow up.
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 10:31:57 AM CDT
Post by Fred Cooke
Can you not programatically access the dependencies by index? Sure it would
be fragile to dep order changes, but it would not be duplication. +1 to
everything Wayne said.
Post by Andrei Pozolotin
*Wayne*
1) in this case "I choose madness" :-)
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 09:56:40 AM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
the way I understand your suggestions is essentially I must duplicate
Yes, just like you do with the other plugins mentioned.
Wayne
Tamás Cservenák
2013-04-04 16:19:01 UTC
Permalink
Andrei,

Wayne is right, the dependencies (or even depMgt) section is NOT a place
for information like these.
This is Karaf plugin specific, it must go into plugin configuration.

As _similar_ example, here is a quite simple example, but with very similar
intention (true, the amount of params here is 1, but the plugin config is
easily extensible to receive whatever you want):
https://github.com/sonatype/nexus-plugin-bundle

This plugin above is meant to create Nexus Plugin Bundles. While those are
NOT OSGi plugins, they are "designed" similarly. Every Nexus plugin (might)
have a set of dependencies, and it might choose to keep the "private" or
"export" them (make those available for other plugin bundles depending on
this plugin).

A good example plugin configuration is the one for
nexus-indexer-lucene-plugin (that bundles Maven Indexer as Nexus plugin).
The Maven Indexer API sadly has Lucene refefences, so it _has_ to export
Lucene too. Hence, the nexus-plugin-bundle-plugin config looks like this:

https://github.com/sonatype/nexus/blob/master/plugins/indexer/nexus-indexer-lucene-plugin/pom.xml#L135

As you see, the plugin defines dependencies "as usual", and the plugin
configuration simply enlists the GAs of deps needed to make them public.

This means that change for plugin config is needed only when G or A changes
of a dependency, or a new dependency needs to be exported...


Now, in your case, this list here
https://github.com/sonatype/nexus-plugin-bundle/blob/master/maven-plugin/src/main/java/org/sonatype/nexus/pluginbundle/maven/GenerateMetadataMojo.java#L83

Might be something other than List<String>, it might be a list of some
beans, or even list of maps (can maven do that from plugin config?) that
can hold ANY property you want to use in your plugin.


HTH,
~t~
Post by Andrei Pozolotin
*Wayne*
1) in this case "I choose madness" :-)
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 09:56:40 AM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
the way I understand your suggestions is essentially I must duplicate
Yes, just like you do with the other plugins mentioned.
Wayne
Andrei Pozolotin
2013-04-04 17:02:02 UTC
Permalink
Tamás

Thank you very much for the complete nexus plugin example, it seems
like one-to-one mapping to our osgi problem domain.

I now totally get what you are saying, and yes, we could use the
approach similar to nexus plugin declarations in the karaf maven plugin.

However (unfortunately?), I was watching Jason Van Zyl presentation
about maven 3.1.0
and got (over?) inspired by the promise "to get free from the
constrains of the past" :-)

And the approach the nexus plugin is taking seems like a needless
kludge work around basic need
to be able to annotate <dependency> with user properties - the kind
of constrains I would like maven to remove in 3.1.0.

So: can I please respectfully request a formal PMC vote on my change
request or should I just go away and leave you all alone? :-)

Thank you,

Andrei

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Tamás Cservenák <***@cservenak.net>
To: Maven Developers List <***@maven.apache.org>
Cc: Wayne Fay <***@gmail.com>
Date: Thu 04 Apr 2013 11:19:01 AM CDT
Post by Tamás Cservenák
Andrei,
Wayne is right, the dependencies (or even depMgt) section is NOT a place
for information like these.
This is Karaf plugin specific, it must go into plugin configuration.
As _similar_ example, here is a quite simple example, but with very similar
intention (true, the amount of params here is 1, but the plugin config is
https://github.com/sonatype/nexus-plugin-bundle
This plugin above is meant to create Nexus Plugin Bundles. While those are
NOT OSGi plugins, they are "designed" similarly. Every Nexus plugin (might)
have a set of dependencies, and it might choose to keep the "private" or
"export" them (make those available for other plugin bundles depending on
this plugin).
A good example plugin configuration is the one for
nexus-indexer-lucene-plugin (that bundles Maven Indexer as Nexus plugin).
The Maven Indexer API sadly has Lucene refefences, so it _has_ to export
https://github.com/sonatype/nexus/blob/master/plugins/indexer/nexus-indexer-lucene-plugin/pom.xml#L135
As you see, the plugin defines dependencies "as usual", and the plugin
configuration simply enlists the GAs of deps needed to make them public.
This means that change for plugin config is needed only when G or A changes
of a dependency, or a new dependency needs to be exported...
Now, in your case, this list here
https://github.com/sonatype/nexus-plugin-bundle/blob/master/maven-plugin/src/main/java/org/sonatype/nexus/pluginbundle/maven/GenerateMetadataMojo.java#L83
Might be something other than List<String>, it might be a list of some
beans, or even list of maps (can maven do that from plugin config?) that
can hold ANY property you want to use in your plugin.
HTH,
~t~
Post by Andrei Pozolotin
*Wayne*
1) in this case "I choose madness" :-)
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 09:56:40 AM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
the way I understand your suggestions is essentially I must duplicate
Yes, just like you do with the other plugins mentioned.
Wayne
Wayne Fay
2013-04-04 17:10:07 UTC
Permalink
Post by Andrei Pozolotin
to be able to annotate <dependency> with user properties - the kind
of constrains I would like maven to remove in 3.1.0.
Doubtful to be removed in 3.1.0.
Post by Andrei Pozolotin
So: can I please respectfully request a formal PMC vote on my change
request or should I just go away and leave you all alone? :-)
No need to "go away" but please appreciate this is an issue that we
are aware of and will continue to discuss for enhancement/change in
some future release of Maven. Calling for a formal vote of the PMC at
this time is unlikely to provide the result you desire.

Wayne
Andrei Pozolotin
2013-04-04 17:28:01 UTC
Permalink
Wayne and ALL:

Thank you very much for considering this request, I got my answer.

Does it make sense to file a jira at this point?

Andrei

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Wayne Fay <***@gmail.com>
To: Maven Developers List <***@maven.apache.org>
Date: Thu 04 Apr 2013 12:10:07 PM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
to be able to annotate <dependency> with user properties - the kind
of constrains I would like maven to remove in 3.1.0.
Doubtful to be removed in 3.1.0.
Post by Andrei Pozolotin
So: can I please respectfully request a formal PMC vote on my change
request or should I just go away and leave you all alone? :-)
No need to "go away" but please appreciate this is an issue that we
are aware of and will continue to discuss for enhancement/change in
some future release of Maven. Calling for a formal vote of the PMC at
this time is unlikely to provide the result you desire.
Wayne
---------------------------------------------------------------------
Jason van Zyl
2013-04-04 17:47:18 UTC
Permalink
Are you talking about properties on dependencies like we used to have in Maven 1.x?
Post by Andrei Pozolotin
Thank you very much for considering this request, I got my answer.
Does it make sense to file a jira at this point?
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 12:10:07 PM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
to be able to annotate <dependency> with user properties - the kind
of constrains I would like maven to remove in 3.1.0.
Doubtful to be removed in 3.1.0.
Post by Andrei Pozolotin
So: can I please respectfully request a formal PMC vote on my change
request or should I just go away and leave you all alone? :-)
No need to "go away" but please appreciate this is an issue that we
are aware of and will continue to discuss for enhancement/change in
some future release of Maven. Calling for a formal vote of the PMC at
this time is unlikely to provide the result you desire.
Wayne
---------------------------------------------------------------------
Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

There's no sense in being precise when you don't even know what you're talking about.

-- John von Neumann
Andrei Pozolotin
2013-04-04 17:54:50 UTC
Permalink
yes:
http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-WhytherearenodependencypropertiesinMaven2

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Jason van Zyl <***@tesla.io>
To: Maven Developers List <***@maven.apache.org>
Date: Thu 04 Apr 2013 12:47:18 PM CDT
Post by Jason van Zyl
Are you talking about properties on dependencies like we used to have in Maven 1.x?
Post by Andrei Pozolotin
Thank you very much for considering this request, I got my answer.
Does it make sense to file a jira at this point?
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 12:10:07 PM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
to be able to annotate <dependency> with user properties - the kind
of constrains I would like maven to remove in 3.1.0.
Doubtful to be removed in 3.1.0.
Post by Andrei Pozolotin
So: can I please respectfully request a formal PMC vote on my change
request or should I just go away and leave you all alone? :-)
No need to "go away" but please appreciate this is an issue that we
are aware of and will continue to discuss for enhancement/change in
some future release of Maven. Calling for a formal vote of the PMC at
this time is unlikely to provide the result you desire.
Wayne
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
There's no sense in being precise when you don't even know what you're talking about.
-- John von Neumann
Hervé BOUTEMY
2013-04-04 21:18:09 UTC
Permalink
if we add such relaxed load during build, how do you expect to retrieve the
info?
I suppose you'll need an API to catch the info

Regards,

Hervé
Post by Andrei Pozolotin
*Wayne*
1) in this case "I choose madness" :-)
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 09:56:40 AM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
the way I understand your suggestions is essentially I must duplicate
Yes, just like you do with the other plugins mentioned.
Wayne
Andrei Pozolotin
2013-04-04 21:28:42 UTC
Permalink
ideally, yes, I would expect to get user properties from dependencies as
part of standard maven api.

IIRC it was just a string-only property bag multimap in maven 1.x

but I am not even asking that, I can parse pom.xml again in my plugin
and find what I need.

where I need your help is not to enforce the model - I can not seem to
find a way to bypass current behavior

alternatively, lets revert to how it was in maven 1.x

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Hervé BOUTEMY <***@free.fr>
To: Maven Developers List <***@maven.apache.org>
Date: Thu 04 Apr 2013 04:18:09 PM CDT
Post by Hervé BOUTEMY
if we add such relaxed load during build, how do you expect to retrieve the
info?
I suppose you'll need an API to catch the info
Regards,
Hervé
Post by Andrei Pozolotin
*Wayne*
1) in this case "I choose madness" :-)
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 09:56:40 AM CDT
Post by Wayne Fay
Post by Andrei Pozolotin
the way I understand your suggestions is essentially I must duplicate
Yes, just like you do with the other plugins mentioned.
Wayne
---------------------------------------------------------------------
Jörg Schaible
2013-04-05 07:35:06 UTC
Permalink
Hi Andrei,
Post by Andrei Pozolotin
*Wayne*
1) in this case "I choose madness" :-)
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.
Then why don't you use custom properties that follow simple naming
conventions? Just run in your mojo through the list of (resolved)
dependencies and look if an appropriate custom property has been defined:

<dependencies>
...
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
</dependency>
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
<classifier>features</classifier>
<type>xml</type>
</dependency>
...
</dependencies>
...
<properties>
...
<karaf.com.example.bundle.osgiStartLevel>99</karaf.com.example.bundle.osgiStartLevel>
<karaf.com.example.bundle.features.bootInstall>true</karaf.com.example.bundle.features.bootInstall>
...
</properties>

Obvious naming convention: karaf.groupId.artifactId[.classifier].variable

- Jörg
Andrei Pozolotin
2013-04-05 15:15:52 UTC
Permalink
Jörg:

you are right. but for me it feels like violation of
http://en.wikipedia.org/wiki/Don't_repeat_yourself
<http://en.wikipedia.org/wiki/Don%27t_repeat_yourself>
especially if I have half a hundred entries in pom.xml.

Andrei

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Jörg Schaible <***@scalaris.com>
To: ***@maven.apache.org
Date: Fri 05 Apr 2013 02:35:06 AM CDT
Post by Jörg Schaible
Hi Andrei,
Post by Andrei Pozolotin
*Wayne*
1) in this case "I choose madness" :-)
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.
Then why don't you use custom properties that follow simple naming
conventions? Just run in your mojo through the list of (resolved)
<dependencies>
...
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
</dependency>
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
<classifier>features</classifier>
<type>xml</type>
</dependency>
...
</dependencies>
...
<properties>
...
<karaf.com.example.bundle.osgiStartLevel>99</karaf.com.example.bundle.osgiStartLevel>
<karaf.com.example.bundle.features.bootInstall>true</karaf.com.example.bundle.features.bootInstall>
...
</properties>
Obvious naming convention: karaf.groupId.artifactId[.classifier].variable
- Jörg
---------------------------------------------------------------------
Michael-O
2013-04-04 16:08:01 UTC
Permalink
Post by Andrei Pozolotin
thank you for taking the time to respond.
karaf
http://karaf.apache.org/
has features.xml, which are built from pom.xml
http://karaf.apache.org/manual/latest-2.3.x/users-guide/provisioning.html
what is missing from maven is the ability to communicate arbitrary
custom attributes
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
<osgiStartLevel>99</osgiStartLevel>
</dependency>
or provide karafBootInstall flag, to specify that karaf runtime should
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle-feature</artifactId>
<version>1.0.1</version>
<classifier>features</classifier>
<type>xml</type>
<karafBootInstall>true</karafBootInstall>
</dependency>
I think that variations of depenencies must go either in classifiers or
build qualiafiers. If we start allow arbitrary elements in <dependency>,
people will start to ask for custom elements in X. Therefore custom
elements are allow in a plugin's <configuration> only.

Michael
Andrei Pozolotin
2013-04-04 16:32:18 UTC
Permalink
Michael:

re "classifiers or build qualiafiers" - these are not variations on
dependency
this is same dependency, but in different poms this dependency have
different custom property.
think of it like @Inject annotation in guice

Thank you,

Andrei

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Michael-O <1983-01-***@gmx.net>
To: Maven Developers List <***@maven.apache.org>
Date: Thu 04 Apr 2013 11:08:01 AM CDT
Post by Michael-O
Post by Andrei Pozolotin
thank you for taking the time to respond.
karaf
http://karaf.apache.org/
has features.xml, which are built from pom.xml
http://karaf.apache.org/manual/latest-2.3.x/users-guide/provisioning.html
what is missing from maven is the ability to communicate arbitrary
custom attributes
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
<osgiStartLevel>99</osgiStartLevel>
</dependency>
or provide karafBootInstall flag, to specify that karaf runtime should
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle-feature</artifactId>
<version>1.0.1</version>
<classifier>features</classifier>
<type>xml</type>
<karafBootInstall>true</karafBootInstall>
</dependency>
I think that variations of depenencies must go either in classifiers
or build qualiafiers. If we start allow arbitrary elements in
<dependency>, people will start to ask for custom elements in X.
Therefore custom elements are allow in a plugin's <configuration> only.
Michael
---------------------------------------------------------------------
Nigel Magnay
2013-04-09 08:47:21 UTC
Permalink
This keeps coming up, over and over and over.

e.g:
http://maven.40175.n5.nabble.com/Meta-information-about-dependencies-in-a-pom-td4971927.html

The maven 'answer' seems to amount to 'hard cheese, you must re-specify
each and every one of your dependencies again in your plugin config'. And
then pointing to the configuration horror that is the assembly plugin, and
completely ignoring the duplication of, like, every single dependency in
your use-case. And if your language has scopes other than the burnt-in ones
in maven, double-hard cheese with a cherry on top - welcome to screenfuls
of warnings and a non-working transitive dependency mechanism.

Despite the fact you're already paying the XML tax (so each dependency
takes 5 lines in your POM file, compared to single lines in other tools),
*and* the fact that XML has a well-defined capability with namespaces to
compatibly extend the data (and have those extensions easy to strip out),
maven refuses to contemplate this, it seems.

How about

<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:karaf="maven:plugin:com.apache:karaf"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">

....

<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
<karaf:osgiStartLevel>99</karaf:osgiStartLevel>
<karaf:bootInstall>true</karaf:bootInstall>
</dependency>
Post by Andrei Pozolotin
thank you for taking the time to respond.
karaf
http://karaf.apache.org/
has features.xml, which are built from pom.xml
http://karaf.apache.org/manual/latest-2.3.x/users-guide/provisioning.html
what is missing from maven is the ability to communicate arbitrary
custom attributes
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
<osgiStartLevel>99</osgiStartLevel>
</dependency>
or provide karafBootInstall flag, to specify that karaf runtime should
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle-feature</artifactId>
<version>1.0.1</version>
<classifier>features</classifier>
<type>xml</type>
<karafBootInstall>true</karafBootInstall>
</dependency>
in lieu of these, karaf-maven-plugin is trying to encode this
information via <scope>
https://github.com/apache/karaf/blob/trunk/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/features/InstallKarsMojo.java#L215
which contradicts the dependency resolution rules and really does not work.
hence my request to "relax". is there any other ways to address this need?
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 01:21:32 AM CDT
Post by Hervé BOUTEMY
AFAIK, there is nothing "relaxed" from Mven 3.0.x planned
But I don't really understand your case (and miss time to investigate in
Karaf).
Can you give us a pointer to SCM, or paste such a dependency "with custom
tags"?
Regards,
Hervé
Post by Andrei Pozolotin
I am curious if 3.1.0 will be more relaxed with custom tags inside
<dependency>?
Use case: karaf-maven-plugin uses bizarre conventions
on how to map from <scope> into osgi bundle properties (like start
level)
Post by Hervé BOUTEMY
Post by Andrei Pozolotin
because there is no way to have a custom tag in <dependency> and express
this requirement.
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Tue 02 Apr 2013 12:04:18 PM CDT
Post by Jason van Zyl
Thanks.
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&versio
Post by Hervé BOUTEMY
Post by Andrei Pozolotin
Post by Jason van Zyl
Post by Hervé BOUTEMY
Post by Jason van Zyl
n=18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/
Post by Hervé BOUTEMY
Post by Andrei Pozolotin
Post by Jason van Zyl
Post by Hervé BOUTEMY
Post by Jason van Zyl
mave n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency,
and
Post by Hervé BOUTEMY
Post by Andrei Pozolotin
Post by Jason van Zyl
Post by Hervé BOUTEMY
Post by Jason van Zyl
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people
can
Post by Hervé BOUTEMY
Post by Andrei Pozolotin
Post by Jason van Zyl
fix bad ideas, but good ideas can't save bad people.>
-- Paul Graham
---------------------------------------------------------------------
.
Andrei Pozolotin
2013-04-10 00:20:56 UTC
Permalink
this will work as well, thank you for the idea.

-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Nigel Magnay <***@gmail.com>
To: Maven Developers List <***@maven.apache.org>
Date: Tue 09 Apr 2013 03:47:21 AM CDT
Post by Nigel Magnay
This keeps coming up, over and over and over.
http://maven.40175.n5.nabble.com/Meta-information-about-dependencies-in-a-pom-td4971927.html
The maven 'answer' seems to amount to 'hard cheese, you must re-specify
each and every one of your dependencies again in your plugin config'. And
then pointing to the configuration horror that is the assembly plugin, and
completely ignoring the duplication of, like, every single dependency in
your use-case. And if your language has scopes other than the burnt-in ones
in maven, double-hard cheese with a cherry on top - welcome to screenfuls
of warnings and a non-working transitive dependency mechanism.
Despite the fact you're already paying the XML tax (so each dependency
takes 5 lines in your POM file, compared to single lines in other tools),
*and* the fact that XML has a well-defined capability with namespaces to
compatibly extend the data (and have those extensions easy to strip out),
maven refuses to contemplate this, it seems.
How about
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:karaf="maven:plugin:com.apache:karaf"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">
....
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
<karaf:osgiStartLevel>99</karaf:osgiStartLevel>
<karaf:bootInstall>true</karaf:bootInstall>
</dependency>
Post by Andrei Pozolotin
thank you for taking the time to respond.
karaf
http://karaf.apache.org/
has features.xml, which are built from pom.xml
http://karaf.apache.org/manual/latest-2.3.x/users-guide/provisioning.html
what is missing from maven is the ability to communicate arbitrary
custom attributes
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
<osgiStartLevel>99</osgiStartLevel>
</dependency>
or provide karafBootInstall flag, to specify that karaf runtime should
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle-feature</artifactId>
<version>1.0.1</version>
<classifier>features</classifier>
<type>xml</type>
<karafBootInstall>true</karafBootInstall>
</dependency>
in lieu of these, karaf-maven-plugin is trying to encode this
information via <scope>
https://github.com/apache/karaf/blob/trunk/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/features/InstallKarsMojo.java#L215
which contradicts the dependency resolution rules and really does not work.
hence my request to "relax". is there any other ways to address this need?
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Thu 04 Apr 2013 01:21:32 AM CDT
Post by Hervé BOUTEMY
AFAIK, there is nothing "relaxed" from Mven 3.0.x planned
But I don't really understand your case (and miss time to investigate in
Karaf).
Can you give us a pointer to SCM, or paste such a dependency "with custom
tags"?
Regards,
Hervé
Post by Andrei Pozolotin
I am curious if 3.1.0 will be more relaxed with custom tags inside
<dependency>?
Use case: karaf-maven-plugin uses bizarre conventions
on how to map from <scope> into osgi bundle properties (like start
level)
Post by Hervé BOUTEMY
Post by Andrei Pozolotin
because there is no way to have a custom tag in <dependency> and express
this requirement.
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Date: Tue 02 Apr 2013 12:04:18 PM CDT
Post by Jason van Zyl
Thanks.
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&versio
Post by Hervé BOUTEMY
Post by Andrei Pozolotin
Post by Jason van Zyl
Post by Hervé BOUTEMY
Post by Jason van Zyl
n=18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/
Post by Hervé BOUTEMY
Post by Andrei Pozolotin
Post by Jason van Zyl
Post by Hervé BOUTEMY
Post by Jason van Zyl
mave n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency,
and
Post by Hervé BOUTEMY
Post by Andrei Pozolotin
Post by Jason van Zyl
Post by Hervé BOUTEMY
Post by Jason van Zyl
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
What matters is not ideas, but the people who have them. Good people
can
Post by Hervé BOUTEMY
Post by Andrei Pozolotin
Post by Jason van Zyl
fix bad ideas, but good ideas can't save bad people.>
-- Paul Graham
---------------------------------------------------------------------
.
Hervé BOUTEMY
2013-04-19 06:16:03 UTC
Permalink
back to the vote
+1

- maven-report-exec 1.1 makes m-site-p work with this release: no need to wait
for m-site-p 3.3, we can add instructions on how to use p-site-p 3.x + maven-
report-exec 1.1 like http://svn.apache.org/r1467751
- maven-dependency-tree 2.1-SNAPSHOT makes dependency:tree, shade and
MPIr:dependencies work too, and I don't mind if the compoentn release hasn't
been done for the moment, I prefer continue work on it to improve it as much
as possible

I didn't have time to test the release on much other components, but for the
moment, I didn't found any other problem than the previous expected ones

I hope experience from others is the same

Regards,

Hervé
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=
18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/ma
ve n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Anders Hammar
2013-04-19 06:53:53 UTC
Permalink
Does anyone (Igor?) know if there is work going on to make Tycho work with
this?

/Anders
Post by Hervé BOUTEMY
back to the vote
+1
- maven-report-exec 1.1 makes m-site-p work with this release: no need to wait
for m-site-p 3.3, we can add instructions on how to use p-site-p 3.x + maven-
report-exec 1.1 like http://svn.apache.org/r1467751
- maven-dependency-tree 2.1-SNAPSHOT makes dependency:tree, shade and
MPIr:dependencies work too, and I don't mind if the compoentn release hasn't
been done for the moment, I prefer continue work on it to improve it as much
as possible
I didn't have time to test the release on much other components, but for the
moment, I didn't found any other problem than the previous expected ones
I hope experience from others is the same
Regards,
Hervé
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=
Post by Hervé BOUTEMY
Post by Jason van Zyl
18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/ma
Post by Hervé BOUTEMY
Post by Jason van Zyl
ve n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency,
and
Post by Hervé BOUTEMY
Post by Jason van Zyl
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Stuart McCulloch
2013-04-19 08:35:34 UTC
Permalink
Not sure, but I've just logged https://bugs.eclipse.org/bugs/show_bug.cgi?id=406056 in the Tycho project so it's at least tracked.
Post by Anders Hammar
Does anyone (Igor?) know if there is work going on to make Tycho work with
this?
/Anders
Post by Hervé BOUTEMY
back to the vote
+1
- maven-report-exec 1.1 makes m-site-p work with this release: no need to wait
for m-site-p 3.3, we can add instructions on how to use p-site-p 3.x + maven-
report-exec 1.1 like http://svn.apache.org/r1467751
- maven-dependency-tree 2.1-SNAPSHOT makes dependency:tree, shade and
MPIr:dependencies work too, and I don't mind if the compoentn release hasn't
been done for the moment, I prefer continue work on it to improve it as much
as possible
I didn't have time to test the release on much other components, but for the
moment, I didn't found any other problem than the previous expected ones
I hope experience from others is the same
Regards,
Hervé
Post by Hervé BOUTEMY
Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/
Regards,
Hervé
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=
Post by Hervé BOUTEMY
Post by Jason van Zyl
18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/ma
Post by Hervé BOUTEMY
Post by Jason van Zyl
ve n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency,
and
Post by Hervé BOUTEMY
Post by Jason van Zyl
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Hervé BOUTEMY
2013-04-07 23:32:43 UTC
Permalink
while working on site publication, I found that all my work on maven-aether-
provider unit tests had simply been pruned when merging Aether. I will need to
re-do the work, step by step :(
From my perspective, maven-reporting-exec is ready to release: I'll do it
tomorrow if nobody objects.

I'd like some review on DOXIA-484 before releasing Doxia 1.4

And I still didn't have a look at dependency:tree...


Regards,

Hervé
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/mave
n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
Mark Derricutt
2013-04-08 02:25:56 UTC
Permalink
Post by Hervé BOUTEMY
while working on site publication, I found that all my work on maven-aether-
provider unit tests had simply been pruned when merging Aether. I will need to
re-do the work, step by step:(
Hervé - if this is all in git, you should be able to still find all your
commits via "git reflog", if you find them via there, you can checkout
the SHA1 of the commit, create a new branch and merge/cherry pick/rebase
etc. etc. and hopefully retrace your steps in a much more simpler
fashion than starting from scratch.

Mark
Jason van Zyl
2013-04-08 02:29:29 UTC
Permalink
Post by Hervé BOUTEMY
while working on site publication, I found that all my work on maven-aether-
provider unit tests had simply been pruned when merging Aether. I will need to
re-do the work, step by step :(
I don't think you need to redo anything. If you can find the commits I can work them back in. I'd like to figure out how they got pruned.
Post by Hervé BOUTEMY
From my perspective, maven-reporting-exec is ready to release: I'll do it
tomorrow if nobody objects.
I'd like some review on DOXIA-484 before releasing Doxia 1.4
And I still didn't have a look at dependency:tree...
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/mave
n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.

-- Jakob Burckhardt
Hervé BOUTEMY
2013-04-09 01:33:58 UTC
Permalink
Post by Jason van Zyl
Post by Hervé BOUTEMY
while working on site publication, I found that all my work on
maven-aether- provider unit tests had simply been pruned when merging
Aether. I will need to re-do the work, step by step :(
I don't think you need to redo anything. If you can find the commits I can
work them back in. I'd like to figure out how they got pruned.
yes, I know that using a SCM means that I won't completely "re-do" it from
scratch but dig into history to find relevant commits then re-apply them.

I already had a look, but these are non-trivial merges because it all starts
with MavenRepositorySystemSession (in maven-aether-provider) class being
removed in favor of MavenRepositorySystemUtils in commit
82b345e0094813b34fcac85e64dde2d5e02b4cc9. Since it was the basis for unit
tests started with commit 5f92449d5d628f3c40f8a4082bcedc369e96bd2d, I fully
understand that there is a strong conflict, even if I can't find where my
classes were removed (if file modification is easy to track, file removal isn't,
or I don't know how to do).

I just tried to cherry pick a commit, but it causes too much conflicts: I'll
better manually get the latest state before delete and work on reimport.

Regards,

Hervé
Post by Jason van Zyl
Post by Hervé BOUTEMY
From my perspective, maven-reporting-exec is ready to release: I'll do it
tomorrow if nobody objects.
I'd like some review on DOXIA-484 before releasing Doxia 1.4
And I still didn't have a look at dependency:tree...
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version
=18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/m
ave n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.
-- Jakob Burckhardt
Hervé BOUTEMY
2013-04-09 02:33:10 UTC
Permalink
I just did the reimport and changed API to let the code compile [1]

but I get Guice provisioning exceptions during tests: probably something
stupid in initialization, but I don't know what to do
Can you help me at this step, please?

Regards,

Hervé

[1] https://github.com/hboutemy/maven
Post by Hervé BOUTEMY
Post by Jason van Zyl
Post by Hervé BOUTEMY
while working on site publication, I found that all my work on
maven-aether- provider unit tests had simply been pruned when merging
Aether. I will need to re-do the work, step by step :(
I don't think you need to redo anything. If you can find the commits I can
work them back in. I'd like to figure out how they got pruned.
yes, I know that using a SCM means that I won't completely "re-do" it from
scratch but dig into history to find relevant commits then re-apply them.
I already had a look, but these are non-trivial merges because it all starts
with MavenRepositorySystemSession (in maven-aether-provider) class being
removed in favor of MavenRepositorySystemUtils in commit
82b345e0094813b34fcac85e64dde2d5e02b4cc9. Since it was the basis for unit
tests started with commit 5f92449d5d628f3c40f8a4082bcedc369e96bd2d, I fully
understand that there is a strong conflict, even if I can't find where my
classes were removed (if file modification is easy to track, file removal
isn't, or I don't know how to do).
I just tried to cherry pick a commit, but it causes too much conflicts: I'll
better manually get the latest state before delete and work on reimport.
Regards,
Hervé
Post by Jason van Zyl
Post by Hervé BOUTEMY
From my perspective, maven-reporting-exec is ready to release: I'll do it
tomorrow if nobody objects.
I'd like some review on DOXIA-484 before releasing Doxia 1.4
And I still didn't have a look at dependency:tree...
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&versi
on
=18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache
/m
ave n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.
-- Jakob Burckhardt
---------------------------------------------------------------------
Stuart McCulloch
2013-04-09 11:30:31 UTC
Permalink
Post by Hervé BOUTEMY
I just did the reimport and changed API to let the code compile [1]
but I get Guice provisioning exceptions during tests: probably something
stupid in initialization, but I don't know what to do
Can you help me at this step, please?
You need to enable container auto-wiring in the test because Eclipse/Aether uses this feature, for example:

diff --git a/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/AbstractRepositoryTestCase.java b/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/AbstractRepositoryTestCase.java
index f615a5c..eea3830 100644
--- a/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/AbstractRepositoryTestCase.java
+++ b/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/AbstractRepositoryTestCase.java
@@ -23,6 +23,7 @@

import org.apache.maven.repository.internal.util.ConsoleRepositoryListener;
import org.apache.maven.repository.internal.util.ConsoleTransferListener;
+import org.codehaus.plexus.ContainerConfiguration;
import org.codehaus.plexus.PlexusTestCase;
import org.eclipse.aether.DefaultRepositorySystemSession;
import org.eclipse.aether.RepositorySystem;
@@ -38,6 +39,13 @@
protected RepositorySystemSession session;

@Override
+ protected void customizeContainerConfiguration( ContainerConfiguration containerConfiguration )
+ {
+ super.customizeContainerConfiguration( containerConfiguration );
+ containerConfiguration.setAutoWiring( true );
+ }
+
+ @Override
protected void setUp()
throws Exception
{


MavenCLI turns auto-wiring on, but these unit tests extend PlexusTestCase which has this off by default (to mimic the original Plexus behaviour).

HTH
Post by Hervé BOUTEMY
Regards,
Hervé
[1] https://github.com/hboutemy/maven
Post by Hervé BOUTEMY
Post by Jason van Zyl
Post by Hervé BOUTEMY
while working on site publication, I found that all my work on
maven-aether- provider unit tests had simply been pruned when merging
Aether. I will need to re-do the work, step by step :(
I don't think you need to redo anything. If you can find the commits I can
work them back in. I'd like to figure out how they got pruned.
yes, I know that using a SCM means that I won't completely "re-do" it from
scratch but dig into history to find relevant commits then re-apply them.
I already had a look, but these are non-trivial merges because it all starts
with MavenRepositorySystemSession (in maven-aether-provider) class being
removed in favor of MavenRepositorySystemUtils in commit
82b345e0094813b34fcac85e64dde2d5e02b4cc9. Since it was the basis for unit
tests started with commit 5f92449d5d628f3c40f8a4082bcedc369e96bd2d, I fully
understand that there is a strong conflict, even if I can't find where my
classes were removed (if file modification is easy to track, file removal
isn't, or I don't know how to do).
I just tried to cherry pick a commit, but it causes too much conflicts: I'll
better manually get the latest state before delete and work on reimport.
Regards,
Hervé
Post by Jason van Zyl
Post by Hervé BOUTEMY
From my perspective, maven-reporting-exec is ready to release: I'll do it
tomorrow if nobody objects.
I'd like some review on DOXIA-484 before releasing Doxia 1.4
And I still didn't have a look at dependency:tree...
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&versi
on
=18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache
/m
ave n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.
-- Jakob Burckhardt
---------------------------------------------------------------------
---------------------------------------------------------------------
Hervé BOUTEMY
2013-04-09 23:44:13 UTC
Permalink
that's it, it works

thank you Stuart: I knew I was missing something like this = few code but
major structure :)

Regards,

Hervé
Post by Stuart McCulloch
Post by Hervé BOUTEMY
I just did the reimport and changed API to let the code compile [1]
but I get Guice provisioning exceptions during tests: probably something
stupid in initialization, but I don't know what to do
Can you help me at this step, please?
You need to enable container auto-wiring in the test because Eclipse/Aether
diff --git
a/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/
AbstractRepositoryTestCase.java
b/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/
AbstractRepositoryTestCase.java index f615a5c..eea3830 100644
---
a/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/
AbstractRepositoryTestCase.java +++
b/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/
import org.apache.maven.repository.internal.util.ConsoleRepositoryListener;
import org.apache.maven.repository.internal.util.ConsoleTransferListener;
+import org.codehaus.plexus.ContainerConfiguration;
import org.codehaus.plexus.PlexusTestCase;
import org.eclipse.aether.DefaultRepositorySystemSession;
import org.eclipse.aether.RepositorySystem;
@@ -38,6 +39,13 @@
protected RepositorySystemSession session;
@Override
+ protected void customizeContainerConfiguration( ContainerConfiguration
containerConfiguration ) + {
+ super.customizeContainerConfiguration( containerConfiguration );
+ containerConfiguration.setAutoWiring( true );
+ }
+
protected void setUp()
throws Exception
{
MavenCLI turns auto-wiring on, but these unit tests extend PlexusTestCase
which has this off by default (to mimic the original Plexus behaviour).
HTH
Post by Hervé BOUTEMY
Regards,
Hervé
[1] https://github.com/hboutemy/maven
Post by Hervé BOUTEMY
Post by Jason van Zyl
Post by Hervé BOUTEMY
while working on site publication, I found that all my work on
maven-aether- provider unit tests had simply been pruned when merging
Aether. I will need to re-do the work, step by step :(
I don't think you need to redo anything. If you can find the commits I can
work them back in. I'd like to figure out how they got pruned.
yes, I know that using a SCM means that I won't completely "re-do" it from
scratch but dig into history to find relevant commits then re-apply them.
I already had a look, but these are non-trivial merges because it all
starts with MavenRepositorySystemSession (in maven-aether-provider)
class being removed in favor of MavenRepositorySystemUtils in commit
82b345e0094813b34fcac85e64dde2d5e02b4cc9. Since it was the basis for unit
tests started with commit 5f92449d5d628f3c40f8a4082bcedc369e96bd2d, I fully
understand that there is a strong conflict, even if I can't find where my
classes were removed (if file modification is easy to track, file removal
isn't, or I don't know how to do).
I'll better manually get the latest state before delete and work on
reimport.
Regards,
Hervé
Post by Jason van Zyl
Post by Hervé BOUTEMY
From my perspective, maven-reporting-exec is ready to release: I'll do it
tomorrow if nobody objects.
I'd like some review on DOXIA-484 before releasing Doxia 1.4
And I still didn't have a look at dependency:tree...
Regards,
Hervé
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&vers
i
on
=18 967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apach
e
/m
ave n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.
-- Jakob Burckhardt
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
Stephen Connolly
2013-04-23 10:24:11 UTC
Permalink
+1 (binding) for 3.1.0-alpha-1

The following issue needs to be resolved before I will vote +1 on a
non-alpha release:

http://jira.codehaus.org/browse/MNG-5470

RAT is reporting the 391 files are either missing license headers or have
not been flagged as files that cannot support a license header. Most of
these are test data files and I would be happy to argue that the test may
require a specific exact content for reproducibility, but the following I
do not feel I can make a case for. I will require these 39 files to be
addressed in some way before the final 3.1.0 release or I cannot provide a
binding vote for the release. (the MANIFEST.MF may be one where a header
does not make sense, but it is a non-generated file)

I cannot speak for the rest of the PMC, but my understanding is that as a
PMC member it is one of our duties to ensure that the source (which is what
the vote is on) has met with the ASF requirements for license headers.

*******************************

Unapproved licenses:

apache-maven/src/bin/m2.conf
apache-maven/src/conf/logging/simplelogger.properties

maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html
maven-aether-provider/src/site/apt/index.apt
maven-artifact/src/site/apt/index.apt
maven-compat/compatibility.cfl
maven-compat/src/main/resources/META-INF/maven/plugin.xml
maven-core/lifecycle-executor.txt
maven-core/plugin-manager.txt
maven-core/project-builder.txt
maven-core/src/main/resources/org/apache/maven/messages/build.properties
maven-core/src/site/apt/artifact-handlers.apt
maven-core/src/site/apt/configuration-management.apt
maven-core/src/site/apt/default-bindings.apt.vm
maven-core/src/site/apt/getting-to-container-configured-mojos.apt
maven-core/src/site/apt/index.apt
maven-core/src/site/apt/inheritance.apt
maven-core/src/site/apt/lifecycles.apt.vm
maven-core/src/site/apt/offline-mode.apt
maven-core/src/site/apt/plugin-execution-isolation.apt
maven-core/src/site/apt/scripting-support/marmalade-support.apt
maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle

maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java

maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java
maven-embedder/src/main/resources/META-INF/MANIFEST.MF

maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties
maven-embedder/src/site/apt/cli.apt.vm
maven-embedder/src/site/apt/index.apt.vm
maven-embedder/src/site/apt/logging.apt
maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html
maven-model/src/main/java/org/apache/maven/model/merge/package.html
maven-model/src/main/java/org/apache/maven/model/package.html
maven-model/src/site/apt/index.apt
maven-model-builder/src/site/apt/index.apt
maven-model-builder/src/site/apt/super-pom.apt.vm
maven-plugin-api/src/site/apt/index.apt
maven-plugin-api/src/test/resources/plugin.xml
maven-repository-metadata/src/site/apt/index.apt
maven-settings/src/site/apt/index.apt

Attached is the full report (if it makes it through the mailing list
filters)

-Stephen
Post by Jason van Zyl
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency, and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
Karl Heinz Marbaise
2013-04-27 17:52:31 UTC
Permalink
-1 (non binding)

I've found an issue with an integration of my plugin developments which
works with Maven 3.0.X without any problem but with Maven 3.1-alpha-1 it
fails.
I've created a gist (https://gist.github.com/khmarbaise/5473941) which
shows the whole debug output following only an excerpt:

[DEBUG] (f) project = MavenProject:
org.codehaus.mojo:build-metadata-maven-plugin-report-it:1.0-SNAPSHOT @
/Users/km/ws-git/build-metadata-maven-plugin/target/it/metadatareport/pom.xml
[DEBUG] -- end configuration --
[DEBUG] executing Site Mojo
[WARNING] Error injecting:
org.apache.maven.reporting.exec.DefaultMavenReportExecutor
java.lang.NoClassDefFoundError: org/sonatype/aether/graph/DependencyFilter
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getDeclaredConstructors(Class.java:1836)

Is that a known issue ?

Kind regards
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
Stuart McCulloch
2013-04-27 19:03:04 UTC
Permalink
Post by Karl Heinz Marbaise
-1 (non binding)
I've found an issue with an integration of my plugin developments which works with Maven 3.0.X without any problem but with Maven 3.1-alpha-1 it fails.
[DEBUG] -- end configuration --
[DEBUG] executing Site Mojo
[WARNING] Error injecting: org.apache.maven.reporting.exec.DefaultMavenReportExecutor
java.lang.NoClassDefFoundError: org/sonatype/aether/graph/DependencyFilter
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getDeclaredConstructors(Class.java:1836)
Is that a known issue ?
Yes: http://jira.codehaus.org/browse/MSITE-683 and http://www.mail-archive.com/***@maven.apache.org/msg96501.html

See earlier messages in this vote thread for more information about why this happens and what's been done to address it.
Post by Karl Heinz Marbaise
Kind regards
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
ceki
2013-05-02 17:47:50 UTC
Permalink
Hello all,

Out of curiosity, are there any other non-resolved issues holding up
this release?

Best regards,
Post by Stephen Connolly
+1 (binding) for 3.1.0-alpha-1
The following issue needs to be resolved before I will vote +1 on a
http://jira.codehaus.org/browse/MNG-5470
RAT is reporting the 391 files are either missing license headers or
have not been flagged as files that cannot support a license header.
Most of these are test data files and I would be happy to argue that the
test may require a specific exact content for reproducibility, but the
following I do not feel I can make a case for. I will require these 39
files to be addressed in some way before the final 3.1.0 release or I
cannot provide a binding vote for the release. (the MANIFEST.MF may be
one where a header does not make sense, but it is a non-generated file)
I cannot speak for the rest of the PMC, but my understanding is that as
a PMC member it is one of our duties to ensure that the source (which is
what the vote is on) has met with the ASF requirements for license headers.
*******************************
apache-maven/src/bin/m2.conf
apache-maven/src/conf/logging/simplelogger.properties
maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html
maven-aether-provider/src/site/apt/index.apt
maven-artifact/src/site/apt/index.apt
maven-compat/compatibility.cfl
maven-compat/src/main/resources/META-INF/maven/plugin.xml
maven-core/lifecycle-executor.txt
maven-core/plugin-manager.txt
maven-core/project-builder.txt
maven-core/src/main/resources/org/apache/maven/messages/build.properties
maven-core/src/site/apt/artifact-handlers.apt
maven-core/src/site/apt/configuration-management.apt
maven-core/src/site/apt/default-bindings.apt.vm
maven-core/src/site/apt/getting-to-container-configured-mojos.apt
maven-core/src/site/apt/index.apt
maven-core/src/site/apt/inheritance.apt
maven-core/src/site/apt/lifecycles.apt.vm
maven-core/src/site/apt/offline-mode.apt
maven-core/src/site/apt/plugin-execution-isolation.apt
maven-core/src/site/apt/scripting-support/marmalade-support.apt
maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle
maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java
maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java
maven-embedder/src/main/resources/META-INF/MANIFEST.MF
maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties
maven-embedder/src/site/apt/cli.apt.vm
maven-embedder/src/site/apt/index.apt.vm
maven-embedder/src/site/apt/logging.apt
maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html
maven-model/src/main/java/org/apache/maven/model/merge/package.html
maven-model/src/main/java/org/apache/maven/model/package.html
maven-model/src/site/apt/index.apt
maven-model-builder/src/site/apt/index.apt
maven-model-builder/src/site/apt/super-pom.apt.vm
maven-plugin-api/src/site/apt/index.apt
maven-plugin-api/src/test/resources/plugin.xml
maven-repository-metadata/src/site/apt/index.apt
maven-settings/src/site/apt/index.apt
Attached is the full report (if it makes it through the mailing list
filters)
-Stephen
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
https://repository.apache.org/content/repositories/maven-042/
https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency,
and Shade plugin are not going to work. We are aware of this and
those responsible for those plugins are looking into it.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
--
Ceki
65% of statistics are made up on the spot
Stephen Connolly
2013-05-02 21:13:37 UTC
Permalink
I think we are just waiting for one more binding vote from a PMC member...
But somebody should double check the count
Post by ceki
Hello all,
Out of curiosity, are there any other non-resolved issues holding up this
release?
Best regards,
Post by Stephen Connolly
+1 (binding) for 3.1.0-alpha-1
The following issue needs to be resolved before I will vote +1 on a
http://jira.codehaus.org/**browse/MNG-5470<http://jira.codehaus.org/browse/MNG-5470>
RAT is reporting the 391 files are either missing license headers or
have not been flagged as files that cannot support a license header.
Most of these are test data files and I would be happy to argue that the
test may require a specific exact content for reproducibility, but the
following I do not feel I can make a case for. I will require these 39
files to be addressed in some way before the final 3.1.0 release or I
cannot provide a binding vote for the release. (the MANIFEST.MF may be
one where a header does not make sense, but it is a non-generated file)
I cannot speak for the rest of the PMC, but my understanding is that as
a PMC member it is one of our duties to ensure that the source (which is
what the vote is on) has met with the ASF requirements for license headers.
*********************************
apache-maven/src/bin/m2.conf
apache-maven/src/conf/logging/**simplelogger.properties
maven-aether-provider/src/**main/java/org/apache/maven/**
repository/internal/package.**html
maven-aether-provider/src/**site/apt/index.apt
maven-artifact/src/site/apt/**index.apt
maven-compat/compatibility.cfl
maven-compat/src/main/**resources/META-INF/maven/**plugin.xml
maven-core/lifecycle-executor.**txt
maven-core/plugin-manager.txt
maven-core/project-builder.txt
maven-core/src/main/resources/**org/apache/maven/messages/**
build.properties
maven-core/src/site/apt/**artifact-handlers.apt
maven-core/src/site/apt/**configuration-management.apt
maven-core/src/site/apt/**default-bindings.apt.vm
maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt
maven-core/src/site/apt/index.**apt
maven-core/src/site/apt/**inheritance.apt
maven-core/src/site/apt/**lifecycles.apt.vm
maven-core/src/site/apt/**offline-mode.apt
maven-core/src/site/apt/**plugin-execution-isolation.apt
maven-core/src/site/apt/**scripting-support/marmalade-**support.apt
maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**
graffle
maven-embedder/src/examples/**simple-project/src/main/java/**
org/apache/maven/embedder/App.**java
maven-embedder/src/examples/**simple-project/src/test/java/**
org/apache/maven/embedder/**AppTest.java
maven-embedder/src/main/**resources/META-INF/MANIFEST.MF
maven-embedder/src/main/**resources/META-INF/maven/**
slf4j-configuration.properties
maven-embedder/src/site/apt/**cli.apt.vm
maven-embedder/src/site/apt/**index.apt.vm
maven-embedder/src/site/apt/**logging.apt
maven-model/src/main/java/org/**apache/maven/model/io/xpp3/**
package.html
maven-model/src/main/java/org/**apache/maven/model/merge/**
package.html
maven-model/src/main/java/org/**apache/maven/model/package.**html
maven-model/src/site/apt/**index.apt
maven-model-builder/src/site/**apt/index.apt
maven-model-builder/src/site/**apt/super-pom.apt.vm
maven-plugin-api/src/site/apt/**index.apt
maven-plugin-api/src/test/**resources/plugin.xml
maven-repository-metadata/src/**site/apt/index.apt
maven-settings/src/site/apt/**index.apt
Attached is the full report (if it makes it through the mailing list
filters)
-Stephen
https://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=10500&version=18967<https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967>
https://repository.apache.org/**content/repositories/maven-**042/<https://repository.apache.org/content/repositories/maven-042/>
https://repository.apache.org/**content/repositories/maven-**
042/org/apache/maven/apache-**maven/3.1.0-alpha-1/<https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/>
Anyone trying this in advance should know that the Site, Dependency,
and Shade plugin are not going to work. We are aware of this and
those responsible for those plugins are looking into it.
Thanks,
Jason
------------------------------**----------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
------------------------------**---------------------------
We know what we are, but know not what we may be.
-- Shakespeare
--
Ceki
65% of statistics are made up on the spot
------------------------------**------------------------------**---------
--
Sent from my phone
Stephen Connolly
2013-05-02 21:16:51 UTC
Permalink
Currently it's

+1 (binding): Hervé & me

Some other +1's and -1's

I'd expect the release manager for ths release to have made some noise by
now (as any release manager should)
Post by Stephen Connolly
I think we are just waiting for one more binding vote from a PMC member...
But somebody should double check the count
Hello all,
Out of curiosity, are there any other non-resolved issues holding up this
release?
Best regards,
+1 (binding) for 3.1.0-alpha-1
The following issue needs to be resolved before I will vote +1 on a
http://jira.codehaus.org/**browse/MNG-5470<http://jira.codehaus.org/browse/MNG-5470>
RAT is reporting the 391 files are either missing license headers or
have not been flagged as files that cannot support a license header.
Most of these are test data files and I would be happy to argue that the
test may require a specific exact content for reproducibility, but the
following I do not feel I can make a case for. I will require these 39
files to be addressed in some way before the final 3.1.0 release or I
cannot provide a binding vote for the release. (the MANIFEST.MF may be
one where a header does not make sense, but it is a non-generated file)
I cannot speak for the rest of the PMC, but my understanding is that as
a PMC member it is one of our duties to ensure that the source (which is
what the vote is on) has met with the ASF requirements for license headers.
*********************************
apache-maven/src/bin/m2.conf
apache-maven/src/conf/logging/**simplelogger.properties
maven-aether-provider/src/**main/java/org/apache/maven/**
repository/internal/package.**html
maven-aether-provider/src/**site/apt/index.apt
maven-artifact/src/site/apt/**index.apt
maven-compat/compatibility.cfl
maven-compat/src/main/**resources/META-INF/maven/**plugin.xml
maven-core/lifecycle-executor.**txt
maven-core/plugin-manager.txt
maven-core/project-builder.txt
maven-core/src/main/resources/**org/apache/maven/messages/**
build.properties
maven-core/src/site/apt/**artifact-handlers.apt
maven-core/src/site/apt/**configuration-management.apt
maven-core/src/site/apt/**default-bindings.apt.vm
maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt
maven-core/src/site/apt/index.**apt
maven-core/src/site/apt/**inheritance.apt
maven-core/src/site/apt/**lifecycles.apt.vm
maven-core/src/site/apt/**offline-mode.apt
maven-core/src/site/apt/**plugin-execution-isolation.apt
maven-core/src/site/apt/**scripting-support/marmalade-**support.apt
maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle
maven-embedder/src/examples/**simple-project/src/main/java/**
org/apache/maven/embedder/App.**java
maven-embedder/src/examples/**simple-project/src/test/java/**
org/apache/maven/embedder/**AppTest.java
maven-embedder/src/main/**resources/META-INF/MANIFEST.MF
maven-embedder/src/main/**resources/META-INF/maven/**
slf4j-configuration.properties
maven-embedder/src/site/apt/**cli.apt.vm
maven-embedder/src/site/apt/**index.apt.vm
maven-embedder/src/site/apt/**logging.apt
maven-model/src/main/java/org/**apache/maven/model/io/xpp3/**
package.html
maven-model/src/main/java/org/**apache/maven/model/merge/**package.html
maven-model/src/main/java/org/**apache/maven/model/package.**html
maven-model/src/site/apt/**index.apt
maven-model-builder/src/site/**apt/index.apt
maven-model-builder/src/site/**apt/super-pom.apt.vm
maven-plugin-api/src/site/apt/**index.apt
maven-plugin-api/src/test/**resources/plugin.xml
maven-repository-metadata/src/**site/apt/index.apt
maven-settings/src/site/apt/**index.apt
Attached is the full report (if it makes it through the mailing list
filters)
-Stephen
https://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=10500&version=18967<https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967>
S
--
Sent from my phone
--
Sent from my phone
Jason van Zyl
2013-05-04 14:12:25 UTC
Permalink
I will cancel the vote and respin it. No one has looked that hard: there's a snapshot repository in the top-level POM.

I haven't made any noise as Hervé is trying to release all the prerequisites so that some of the standard plugins don't fail.
Post by Stephen Connolly
Currently it's
+1 (binding): Hervé & me
Some other +1's and -1's
I'd expect the release manager for ths release to have made some noise by
now (as any release manager should)
Post by Stephen Connolly
I think we are just waiting for one more binding vote from a PMC member...
But somebody should double check the count
Hello all,
Out of curiosity, are there any other non-resolved issues holding up this
release?
Best regards,
+1 (binding) for 3.1.0-alpha-1
The following issue needs to be resolved before I will vote +1 on a
http://jira.codehaus.org/**browse/MNG-5470<http://jira.codehaus.org/browse/MNG-5470>
RAT is reporting the 391 files are either missing license headers or
have not been flagged as files that cannot support a license header.
Most of these are test data files and I would be happy to argue that the
test may require a specific exact content for reproducibility, but the
following I do not feel I can make a case for. I will require these 39
files to be addressed in some way before the final 3.1.0 release or I
cannot provide a binding vote for the release. (the MANIFEST.MF may be
one where a header does not make sense, but it is a non-generated file)
I cannot speak for the rest of the PMC, but my understanding is that as
a PMC member it is one of our duties to ensure that the source (which is
what the vote is on) has met with the ASF requirements for license headers.
*********************************
apache-maven/src/bin/m2.conf
apache-maven/src/conf/logging/**simplelogger.properties
maven-aether-provider/src/**main/java/org/apache/maven/**
repository/internal/package.**html
maven-aether-provider/src/**site/apt/index.apt
maven-artifact/src/site/apt/**index.apt
maven-compat/compatibility.cfl
maven-compat/src/main/**resources/META-INF/maven/**plugin.xml
maven-core/lifecycle-executor.**txt
maven-core/plugin-manager.txt
maven-core/project-builder.txt
maven-core/src/main/resources/**org/apache/maven/messages/**
build.properties
maven-core/src/site/apt/**artifact-handlers.apt
maven-core/src/site/apt/**configuration-management.apt
maven-core/src/site/apt/**default-bindings.apt.vm
maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt
maven-core/src/site/apt/index.**apt
maven-core/src/site/apt/**inheritance.apt
maven-core/src/site/apt/**lifecycles.apt.vm
maven-core/src/site/apt/**offline-mode.apt
maven-core/src/site/apt/**plugin-execution-isolation.apt
maven-core/src/site/apt/**scripting-support/marmalade-**support.apt
maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle
maven-embedder/src/examples/**simple-project/src/main/java/**
org/apache/maven/embedder/App.**java
maven-embedder/src/examples/**simple-project/src/test/java/**
org/apache/maven/embedder/**AppTest.java
maven-embedder/src/main/**resources/META-INF/MANIFEST.MF
maven-embedder/src/main/**resources/META-INF/maven/**
slf4j-configuration.properties
maven-embedder/src/site/apt/**cli.apt.vm
maven-embedder/src/site/apt/**index.apt.vm
maven-embedder/src/site/apt/**logging.apt
maven-model/src/main/java/org/**apache/maven/model/io/xpp3/**
package.html
maven-model/src/main/java/org/**apache/maven/model/merge/**package.html
maven-model/src/main/java/org/**apache/maven/model/package.**html
maven-model/src/site/apt/**index.apt
maven-model-builder/src/site/**apt/index.apt
maven-model-builder/src/site/**apt/super-pom.apt.vm
maven-plugin-api/src/site/apt/**index.apt
maven-plugin-api/src/test/**resources/plugin.xml
maven-repository-metadata/src/**site/apt/index.apt
maven-settings/src/site/apt/**index.apt
Attached is the full report (if it makes it through the mailing list
filters)
-Stephen
https://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=10500&version=18967<https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967>
S
--
Sent from my phone
--
Sent from my phone
Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Script timed out
Hervé BOUTEMY
2013-05-04 15:26:51 UTC
Permalink
uh, I didn't see this one :(
if the check can be automated through an enforcer rule, this would be a Good
Thing (TM)

I finally found my way with maven-dependency-tree (vote in progress) +
dependency:tree (re-added verbose mode, which was a big users expectation).
And since I have some time this week (holidays), I should be able to release
everything during these holidays.
It would be nice to update default plugins in Maven core before the next
release candidate.

Regards,

Hervé
Post by Jason van Zyl
I will cancel the vote and respin it. No one has looked that hard: there's a
snapshot repository in the top-level POM.
I haven't made any noise as Hervé is trying to release all the prerequisites
so that some of the standard plugins don't fail.
On May 2, 2013, at 5:16 PM, Stephen Connolly
Post by Stephen Connolly
Currently it's
+1 (binding): Hervé & me
Some other +1's and -1's
I'd expect the release manager for ths release to have made some noise by
now (as any release manager should)
Post by Stephen Connolly
I think we are just waiting for one more binding vote from a PMC member...
But somebody should double check the count
Hello all,
Out of curiosity, are there any other non-resolved issues holding up this
release?
Best regards,
+1 (binding) for 3.1.0-alpha-1
The following issue needs to be resolved before I will vote +1 on a
http://jira.codehaus.org/**browse/MNG-5470<http://jira.codehaus.org/brows
e/MNG-5470>
RAT is reporting the 391 files are either missing license headers or
have not been flagged as files that cannot support a license header.
Most of these are test data files and I would be happy to argue that the
test may require a specific exact content for reproducibility, but the
following I do not feel I can make a case for. I will require these 39
files to be addressed in some way before the final 3.1.0 release or I
cannot provide a binding vote for the release. (the MANIFEST.MF may be
one where a header does not make sense, but it is a non-generated file)
I cannot speak for the rest of the PMC, but my understanding is that as
a PMC member it is one of our duties to ensure that the source (which is
what the vote is on) has met with the ASF requirements for license headers.
*********************************
apache-maven/src/bin/m2.conf
apache-maven/src/conf/logging/**simplelogger.properties
maven-aether-provider/src/**main/java/org/apache/maven/**
repository/internal/package.**html
maven-aether-provider/src/**site/apt/index.apt
maven-artifact/src/site/apt/**index.apt
maven-compat/compatibility.cfl
maven-compat/src/main/**resources/META-INF/maven/**plugin.xml
maven-core/lifecycle-executor.**txt
maven-core/plugin-manager.txt
maven-core/project-builder.txt
maven-core/src/main/resources/**org/apache/maven/messages/**
build.properties
maven-core/src/site/apt/**artifact-handlers.apt
maven-core/src/site/apt/**configuration-management.apt
maven-core/src/site/apt/**default-bindings.apt.vm
maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt
maven-core/src/site/apt/index.**apt
maven-core/src/site/apt/**inheritance.apt
maven-core/src/site/apt/**lifecycles.apt.vm
maven-core/src/site/apt/**offline-mode.apt
maven-core/src/site/apt/**plugin-execution-isolation.apt
maven-core/src/site/apt/**scripting-support/marmalade-**support.apt
maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle
maven-embedder/src/examples/**simple-project/src/main/java/**
org/apache/maven/embedder/App.**java
maven-embedder/src/examples/**simple-project/src/test/java/**
org/apache/maven/embedder/**AppTest.java
maven-embedder/src/main/**resources/META-INF/MANIFEST.MF
maven-embedder/src/main/**resources/META-INF/maven/**
slf4j-configuration.properties
maven-embedder/src/site/apt/**cli.apt.vm
maven-embedder/src/site/apt/**index.apt.vm
maven-embedder/src/site/apt/**logging.apt
maven-model/src/main/java/org/**apache/maven/model/io/xpp3/**
package.html
maven-model/src/main/java/org/**apache/maven/model/merge/**package.html
maven-model/src/main/java/org/**apache/maven/model/package.**html
maven-model/src/site/apt/**index.apt
maven-model-builder/src/site/**apt/index.apt
maven-model-builder/src/site/**apt/super-pom.apt.vm
maven-plugin-api/src/site/apt/**index.apt
maven-plugin-api/src/test/**resources/plugin.xml
maven-repository-metadata/src/**site/apt/index.apt
maven-settings/src/site/apt/**index.apt
Attached is the full report (if it makes it through the mailing list
filters)
-Stephen
https://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=10500&version=18967<https://jira.codehaus.org/secure/ReleaseNot
e.jspa?projectId=10500&version=18967>>>
S
--
Sent from my phone
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Script timed out
Jason van Zyl
2013-05-04 15:40:10 UTC
Permalink
Sure, update all the plugins. We might as well do all that maintenance work now before the next release. I can look at making an enforcer rule. It's been something I've been meaning at looking at is breaking out all the checks in the release plugin to enforcer rules so they can be used anywhere. Inside and outside the release plugin.
Post by Hervé BOUTEMY
uh, I didn't see this one :(
if the check can be automated through an enforcer rule, this would be a Good
Thing (TM)
I finally found my way with maven-dependency-tree (vote in progress) +
dependency:tree (re-added verbose mode, which was a big users expectation).
And since I have some time this week (holidays), I should be able to release
everything during these holidays.
It would be nice to update default plugins in Maven core before the next
release candidate.
Regards,
Hervé
Post by Jason van Zyl
I will cancel the vote and respin it. No one has looked that hard: there's a
snapshot repository in the top-level POM.
I haven't made any noise as Hervé is trying to release all the prerequisites
so that some of the standard plugins don't fail.
On May 2, 2013, at 5:16 PM, Stephen Connolly
Post by Stephen Connolly
Currently it's
+1 (binding): Hervé & me
Some other +1's and -1's
I'd expect the release manager for ths release to have made some noise by
now (as any release manager should)
Post by Stephen Connolly
I think we are just waiting for one more binding vote from a PMC member...
But somebody should double check the count
Hello all,
Out of curiosity, are there any other non-resolved issues holding up this
release?
Best regards,
+1 (binding) for 3.1.0-alpha-1
The following issue needs to be resolved before I will vote +1 on a
http://jira.codehaus.org/**browse/MNG-5470<http://jira.codehaus.org/brows
e/MNG-5470>
RAT is reporting the 391 files are either missing license headers or
have not been flagged as files that cannot support a license header.
Most of these are test data files and I would be happy to argue that the
test may require a specific exact content for reproducibility, but the
following I do not feel I can make a case for. I will require these 39
files to be addressed in some way before the final 3.1.0 release or I
cannot provide a binding vote for the release. (the MANIFEST.MF may be
one where a header does not make sense, but it is a non-generated file)
I cannot speak for the rest of the PMC, but my understanding is that as
a PMC member it is one of our duties to ensure that the source (which is
what the vote is on) has met with the ASF requirements for license headers.
*********************************
apache-maven/src/bin/m2.conf
apache-maven/src/conf/logging/**simplelogger.properties
maven-aether-provider/src/**main/java/org/apache/maven/**
repository/internal/package.**html
maven-aether-provider/src/**site/apt/index.apt
maven-artifact/src/site/apt/**index.apt
maven-compat/compatibility.cfl
maven-compat/src/main/**resources/META-INF/maven/**plugin.xml
maven-core/lifecycle-executor.**txt
maven-core/plugin-manager.txt
maven-core/project-builder.txt
maven-core/src/main/resources/**org/apache/maven/messages/**
build.properties
maven-core/src/site/apt/**artifact-handlers.apt
maven-core/src/site/apt/**configuration-management.apt
maven-core/src/site/apt/**default-bindings.apt.vm
maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt
maven-core/src/site/apt/index.**apt
maven-core/src/site/apt/**inheritance.apt
maven-core/src/site/apt/**lifecycles.apt.vm
maven-core/src/site/apt/**offline-mode.apt
maven-core/src/site/apt/**plugin-execution-isolation.apt
maven-core/src/site/apt/**scripting-support/marmalade-**support.apt
maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle
maven-embedder/src/examples/**simple-project/src/main/java/**
org/apache/maven/embedder/App.**java
maven-embedder/src/examples/**simple-project/src/test/java/**
org/apache/maven/embedder/**AppTest.java
maven-embedder/src/main/**resources/META-INF/MANIFEST.MF
maven-embedder/src/main/**resources/META-INF/maven/**
slf4j-configuration.properties
maven-embedder/src/site/apt/**cli.apt.vm
maven-embedder/src/site/apt/**index.apt.vm
maven-embedder/src/site/apt/**logging.apt
maven-model/src/main/java/org/**apache/maven/model/io/xpp3/**
package.html
maven-model/src/main/java/org/**apache/maven/model/merge/**package.html
maven-model/src/main/java/org/**apache/maven/model/package.**html
maven-model/src/site/apt/**index.apt
maven-model-builder/src/site/**apt/index.apt
maven-model-builder/src/site/**apt/super-pom.apt.vm
maven-plugin-api/src/site/apt/**index.apt
maven-plugin-api/src/test/**resources/plugin.xml
maven-repository-metadata/src/**site/apt/index.apt
maven-settings/src/site/apt/**index.apt
Attached is the full report (if it makes it through the mailing list
filters)
-Stephen
https://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=10500&version=18967<https://jira.codehaus.org/secure/ReleaseNot
e.jspa?projectId=10500&version=18967>>>
S
--
Sent from my phone
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Script timed out
---------------------------------------------------------------------
Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Script timed out
Jason van Zyl
2013-05-07 14:02:18 UTC
Permalink
The vote for 3.1.0-alpha-1 is cancelled. There is a snapshot repository in the parent POM and the vote has gone on for far longer than acceptable.

Hervé go ahead and update any versions of the POMs you like, I have some small changes I'm going to make and when you're happy with the updated plugins I'll cut the release again.
Post by Jason van Zyl
Sure, update all the plugins. We might as well do all that maintenance work now before the next release. I can look at making an enforcer rule. It's been something I've been meaning at looking at is breaking out all the checks in the release plugin to enforcer rules so they can be used anywhere. Inside and outside the release plugin.
Post by Hervé BOUTEMY
uh, I didn't see this one :(
if the check can be automated through an enforcer rule, this would be a Good
Thing (TM)
I finally found my way with maven-dependency-tree (vote in progress) +
dependency:tree (re-added verbose mode, which was a big users expectation).
And since I have some time this week (holidays), I should be able to release
everything during these holidays.
It would be nice to update default plugins in Maven core before the next
release candidate.
Regards,
Hervé
Post by Jason van Zyl
I will cancel the vote and respin it. No one has looked that hard: there's a
snapshot repository in the top-level POM.
I haven't made any noise as Hervé is trying to release all the prerequisites
so that some of the standard plugins don't fail.
On May 2, 2013, at 5:16 PM, Stephen Connolly
Post by Stephen Connolly
Currently it's
+1 (binding): Hervé & me
Some other +1's and -1's
I'd expect the release manager for ths release to have made some noise by
now (as any release manager should)
Post by Stephen Connolly
I think we are just waiting for one more binding vote from a PMC member...
But somebody should double check the count
Hello all,
Out of curiosity, are there any other non-resolved issues holding up this
release?
Best regards,
+1 (binding) for 3.1.0-alpha-1
The following issue needs to be resolved before I will vote +1 on a
http://jira.codehaus.org/**browse/MNG-5470<http://jira.codehaus.org/brows
e/MNG-5470>
RAT is reporting the 391 files are either missing license headers or
have not been flagged as files that cannot support a license header.
Most of these are test data files and I would be happy to argue that the
test may require a specific exact content for reproducibility, but the
following I do not feel I can make a case for. I will require these 39
files to be addressed in some way before the final 3.1.0 release or I
cannot provide a binding vote for the release. (the MANIFEST.MF may be
one where a header does not make sense, but it is a non-generated file)
I cannot speak for the rest of the PMC, but my understanding is that as
a PMC member it is one of our duties to ensure that the source (which is
what the vote is on) has met with the ASF requirements for license headers.
*********************************
apache-maven/src/bin/m2.conf
apache-maven/src/conf/logging/**simplelogger.properties
maven-aether-provider/src/**main/java/org/apache/maven/**
repository/internal/package.**html
maven-aether-provider/src/**site/apt/index.apt
maven-artifact/src/site/apt/**index.apt
maven-compat/compatibility.cfl
maven-compat/src/main/**resources/META-INF/maven/**plugin.xml
maven-core/lifecycle-executor.**txt
maven-core/plugin-manager.txt
maven-core/project-builder.txt
maven-core/src/main/resources/**org/apache/maven/messages/**
build.properties
maven-core/src/site/apt/**artifact-handlers.apt
maven-core/src/site/apt/**configuration-management.apt
maven-core/src/site/apt/**default-bindings.apt.vm
maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt
maven-core/src/site/apt/index.**apt
maven-core/src/site/apt/**inheritance.apt
maven-core/src/site/apt/**lifecycles.apt.vm
maven-core/src/site/apt/**offline-mode.apt
maven-core/src/site/apt/**plugin-execution-isolation.apt
maven-core/src/site/apt/**scripting-support/marmalade-**support.apt
maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle
maven-embedder/src/examples/**simple-project/src/main/java/**
org/apache/maven/embedder/App.**java
maven-embedder/src/examples/**simple-project/src/test/java/**
org/apache/maven/embedder/**AppTest.java
maven-embedder/src/main/**resources/META-INF/MANIFEST.MF
maven-embedder/src/main/**resources/META-INF/maven/**
slf4j-configuration.properties
maven-embedder/src/site/apt/**cli.apt.vm
maven-embedder/src/site/apt/**index.apt.vm
maven-embedder/src/site/apt/**logging.apt
maven-model/src/main/java/org/**apache/maven/model/io/xpp3/**
package.html
maven-model/src/main/java/org/**apache/maven/model/merge/**package.html
maven-model/src/main/java/org/**apache/maven/model/package.**html
maven-model/src/site/apt/**index.apt
maven-model-builder/src/site/**apt/index.apt
maven-model-builder/src/site/**apt/super-pom.apt.vm
maven-plugin-api/src/site/apt/**index.apt
maven-plugin-api/src/test/**resources/plugin.xml
maven-repository-metadata/src/**site/apt/index.apt
maven-settings/src/site/apt/**index.apt
Attached is the full report (if it makes it through the mailing list
filters)
-Stephen
https://jira.codehaus.org/**secure/ReleaseNote.jspa?**
projectId=10500&version=18967<https://jira.codehaus.org/secure/ReleaseNot
e.jspa?projectId=10500&version=18967>>>
S
--
Sent from my phone
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Script timed out
---------------------------------------------------------------------
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Script timed out
Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Script timed out

Loading...