+1
2013/6/1 Jason van Zyl :
> 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-046/
>
> Staged distribution:
> https:/
Another late +1 from me. Looks good.
I'm on vacation this week in Florida but found some time last night to run
it against a handful of projects and didn't run into any issues. :)
Wayne
On Sat, Jun 1, 2013 at 8:13 AM, Jason van Zyl wrote:
> Here are the release bits for 3.1.0-alpha-1:
>
> Rel
+1
did run it the last 2 days on many of my projects without any issues.
LieGrue,
strub
- Original Message -
> From: Brian Fox
> To: Maven Developers List
> Cc:
> Sent: Tuesday, 4 June 2013, 18:13
> Subject: Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
>
> +1
>
W00t - congrats to the Apache Maven Team
Now... about that Maven 4.0 release... ;p
Manfred Moser wrote:
Awesome! Congrats to everyone involved.
I am looking forward to adapting the Android Maven Plugin and releasing a
new version asap!
Manfred
+1: Arnaud, Hervé, Brian, Baptiste, Mirko
Awesome! Congrats to everyone involved.
I am looking forward to adapting the Android Maven Plugin and releasing a
new version asap!
Manfred
> +1: Arnaud, Hervé, Brian, Baptiste, Mirko
>
> Vote passes. I will roll out the release later today.
>
> On Jun 4, 2013, at 12:13 PM, Brian Fox wrote:
>
>
+1 (binding)
On 1 June 2013 14:13, Jason van Zyl wrote:
> 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-046/
>
+1: Arnaud, Hervé, Brian, Baptiste, Mirko
Vote passes. I will roll out the release later today.
On Jun 4, 2013, at 12:13 PM, Brian Fox wrote:
> +1
>
> On Sat, Jun 1, 2013 at 9:13 AM, Jason van Zyl wrote:
>> Here are the release bits for 3.1.0-alpha-1:
>>
>> Release notes:
>> https://jira.cod
+1
On Sat, Jun 1, 2013 at 9:13 AM, Jason van Zyl wrote:
> 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-046/
>
> S
+1.
2013/6/2 Arnaud Héritier
> +1
>
> Le dimanche 2 juin 2013, Hervé BOUTEMY a écrit :
>
> > +1
> >
> > Regards,
> >
> > Hervé
> >
> > Le samedi 1 juin 2013 09:13:17 Jason van Zyl a écrit :
> > > Here are the release bits for 3.1.0-alpha-1:
> > >
> > > Release notes:
> > >
> >
> https://jira.co
+1
Le dimanche 2 juin 2013, Hervé BOUTEMY a écrit :
> +1
>
> Regards,
>
> Hervé
>
> Le samedi 1 juin 2013 09:13:17 Jason van Zyl a écrit :
> > Here are the release bits for 3.1.0-alpha-1:
> >
> > Release notes:
> >
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
> >
+1
Regards,
Hervé
Le samedi 1 juin 2013 09:13:17 Jason van Zyl a écrit :
> Here are the release bits for 3.1.0-alpha-1:
>
> Release notes:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
> 967
>
> Staging repository:
> https://repository.apache.org/content/reposi
+1 (non-binding) for (c726cdd3a9ad5c3a419e1171f8c1925e336ead18):
- I successfully ran mvn verify site for some of my own projects
(pom-only, one jar, multi-module).
- the current trunk of maven-javadoc-plugin encountered some failing ITs.
[ERROR] * additionnal-dependencies-non-aggregate/pom.xml
[
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-046/
Staged distribution:
https://repository.apache.org/content/repositories/ma
ok, the auto installer ant_maven.groovy script gets every released Maven
version from our official release area [1]
Then *any released* version will be available: once Maven 3.1.0-alpha-1 will
be released, it will be shown by this script, ready to have many eyes, even if
this release is only al
If one was to push this out for Jenkins to pick them - then this puts a cobwash on the other thread of reusing version numbers IMHO.If you're going to let alpha-1 bleed out to the greater internet, IT IS RELEASED :)IMHO. --Mark DerricuttSent with AirmailOn 31 May 2013 at 11:18:52 PM, Stephen Connol
On 31 May 2013 12:01, jieryn wrote:
> Greetings,
>
> On Fri, May 31, 2013 at 1:34 AM, Hervé BOUTEMY
> wrote:
> > I don't know what you mean by "send pull requests to Jenkins", if you're
> > talking about Apache's Jenkins instance or something more general from
> the
> > Jenkins project
>
> There
Greetings,
On Fri, May 31, 2013 at 1:34 AM, Hervé BOUTEMY wrote:
> I don't know what you mean by "send pull requests to Jenkins", if you're
> talking about Apache's Jenkins instance or something more general from the
> Jenkins project
There is something called the backend-crawler which locates c
I don't know what you mean by "send pull requests to Jenkins", if you're
talking about Apache's Jenkins instance or something more general from the
Jenkins project
but I'm interested by the "it would be auto-installable" objective at least on
Apache's Jenkins instance
so I'll read any pointer
Greetings,
On Thu, May 30, 2013 at 4:29 PM, Stephen Connolly
wrote:
> (Aside: not sure that we'll get that much more eyes for 3.1.0-alpha-x... I
> think the eyes will only hit it when we get to 3.1.0...)
It would be nice if someone sent pull requests to Jenkins so that it
would be auto-installab
Go for it!
(Aside: not sure that we'll get that much more eyes for 3.1.0-alpha-x... I
think the eyes will only hit it when we get to 3.1.0...)
On Thursday, 30 May 2013, Jason van Zyl wrote:
> I'm going to stick to alpha-1. No one has looked at it save 10 people
> which doesn't, to me, constitute
I'm going to stick to alpha-1. No one has looked at it save 10 people which
doesn't, to me, constitute any reasonably sized population. I'll roll it out in
the morning.
On May 30, 2013, at 4:15 PM, Stephen Connolly
wrote:
> You are the release manager. My vote on respinning specifically state
You are the release manager. My vote on respinning specifically stated that
any releases in progress, the release manager can decide.
If it were me I'd call it 3.1.0-beta-1 as we have had enough eyes by now
that its better than alpha... I'd also be happy going straight for the
3.1.0 end game... Bu
Ok, we're just waiting now for Stephen to summarize the vote and then when we
figure out what to call it I'll roll out the release.
On May 30, 2013, at 2:32 PM, Hervé BOUTEMY wrote:
> https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
>
> page created
> improvements welcome
https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
page created
improvements welcome
Regards,
Hervé
Le jeudi 30 mai 2013 09:10:50 Arnaud Héritier a écrit :
> Perfect. Thx
>
> On Thu, May 30, 2013 at 3:27 AM, Hervé BOUTEMY wrote:
> > MNG-5482 fixed: ok for me to go for take 4
Perfect. Thx
On Thu, May 30, 2013 at 3:27 AM, Hervé BOUTEMY wrote:
> MNG-5482 fixed: ok for me to go for take 4
>
> when a plugin cannot be loaded due to missing Sonatype Aether class, hint
> url
> will be
> http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
>
> the Wiki articl
MNG-5482 fixed: ok for me to go for take 4
when a plugin cannot be loaded due to missing Sonatype Aether class, hint url
will be http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
the Wiki article still needs to be written...
Regards,
Hervé
Le mercredi 29 mai 2013 09:34:46
On Wed, May 29, 2013 at 10:17 AM, Arnaud Héritier wrote:
>>
>> But having said all that, if we can find a good way to flag versions as not
>> released (e.g. a release history page or something) I am not against
>> skipping version numbers. Might confuse people though if that meant that
>> the firs
DOAP issues have been fixed. Let's wait for Hervé before spinning a new
release.
Robert
Op Wed, 29 May 2013 01:21:52 +0200 schreef Jason van Zyl :
I'll see if Robert wants to fix the DOAP file and I'll respin tomorrow
after he's commented.
On May 28, 2013, at 7:17 PM, Stephen Connolly
Sure, go for it. The less confusing to users the better.
On May 29, 2013, at 1:36 AM, Hervé BOUTEMY wrote:
> I'd like to work on Arnaud's idea of error message enhancement in case a
> plugin fails because of unavailable Sonatype Aether: if you can let me 12
> more
> hours from now, I'll do it
Yup tomcat does it.
compare
http://archive.apache.org/dist/tomcat/tomcat-7/
with
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/
and
http://archive.apache.org/dist/tomcat/tomcat-6/
with
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/
2013/5/29 Kristian Rosenvold :
> Isn't the main sour
I am fine with it if there is a clear page which shows the status of each
release (i.e. linked from the downloads page:
http://maven.apache.org/download.cgi)
And if we want to go that way, I say let's just drop all the alpha crap.
and go for 3.1.0 straight.
My point is that there is a trade off..
Isn't the main source of confusion here that the "vote" thread is not
detached from the previous thread and that "Take X" is not added to
the subject ?
Kristian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For addit
>
> But having said all that, if we can find a good way to flag versions as not
> released (e.g. a release history page or something) I am not against
> skipping version numbers. Might confuse people though if that meant that
> the first release of Maven 3.1.0 was 3.1.4 (i.e. if we had not been doi
2013/5/29 Stephen Connolly :
> On 29 May 2013 06:49, jieryn wrote:
>
>> Greetings,
>>
>> On Wed, May 29, 2013 at 1:36 AM, Hervé BOUTEMY
>> wrote:
>> > I'd like to work on Arnaud's idea of error message enhancement in case a
>> > plugin fails because of unavailable Sonatype Aether: if you can let
On 29 May 2013 06:49, jieryn wrote:
> Greetings,
>
> On Wed, May 29, 2013 at 1:36 AM, Hervé BOUTEMY
> wrote:
> > I'd like to work on Arnaud's idea of error message enhancement in case a
> > plugin fails because of unavailable Sonatype Aether: if you can let me
> 12 more
> > hours from now, I'll
On Wed, May 29, 2013 at 10:01 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> There were method signature changes as well, so its not just a package
> rename IIRC
>
Ok that explains it
I remember there were some threads about it but I didn't read all of them.
>
>
> On 29 May
There were method signature changes as well, so its not just a package
rename IIRC
On 29 May 2013 08:57, Jörg Schaible wrote:
> Arnaud Héritier wrote:
>
> > On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY
> > wrote:
> >
> >> good idea: can you open a Jira issue?
> >>
> >
> > Done : https://jira
Arnaud Héritier wrote:
> On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY
> wrote:
>
>> good idea: can you open a Jira issue?
>>
>
> Done : https://jira.codehaus.org/browse/MNG-5482
> Another probably more stupid idea : Wasn't it possible to use the shade
> plugin or something like this to provid
On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY wrote:
> good idea: can you open a Jira issue?
>
Done : https://jira.codehaus.org/browse/MNG-5482
Another probably more stupid idea : Wasn't it possible to use the shade
plugin or something like this to provide a version of aether under the old
grou
alpha-1 to n works fine imo. We should not loose pace by holding up the effort
with such minor stuff.
LieGrue,
strub
- Original Message -
> From: Baptiste Mathus
> To: Maven Developers List
> Cc:
> Sent: Wednesday, 29 May 2013, 8:47
> Subject: Re: [VOTE] Apach
Le 29 mai 2013 08:07, "Mirko Friedenhagen" a
écrit :
>
> On May 29, 2013 7:49 AM, "jieryn" wrote:
> >
> > Greetings,
> >
> > On Wed, May 29, 2013 at 1:36 AM, Hervé BOUTEMY
> wrote:
> > > I'd like to work on Arnaud's idea of error message enhancement in
case a
> > > plugin fails because of unavai
On May 29, 2013 7:49 AM, "jieryn" wrote:
>
> Greetings,
>
> On Wed, May 29, 2013 at 1:36 AM, Hervé BOUTEMY
wrote:
> > I'd like to work on Arnaud's idea of error message enhancement in case a
> > plugin fails because of unavailable Sonatype Aether: if you can let me
12 more
> > hours from now, I'l
Greetings,
On Wed, May 29, 2013 at 1:36 AM, Hervé BOUTEMY wrote:
> I'd like to work on Arnaud's idea of error message enhancement in case a
> plugin fails because of unavailable Sonatype Aether: if you can let me 12 more
> hours from now, I'll do it tonight
Version numbers are cheap. Can't we ju
good idea: can you open a Jira issue?
notice, at a first pass, improving content of
http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException to
explain the special case of Aether is easy. But I'll try to have a dedicated
link tonight: I know that the code will go in DefaultExce
I'd like to work on Arnaud's idea of error message enhancement in case a
plugin fails because of unavailable Sonatype Aether: if you can let me 12 more
hours from now, I'll do it tonight
Regards,
Hervé
Le mardi 28 mai 2013 19:21:52 Jason van Zyl a écrit :
> I'll see if Robert wants to fix the
Pushed a small additional fix for typo and clarification based on the names in
the POMs.
On 28/05/2013, at 4:07 PM, Jason van Zyl wrote:
> This should suffice for the notice:
>
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f62
>
> On May 28, 2013, at 5:48 PM, Steph
I'll respin in the morning with an identifying subject line.
On May 28, 2013, at 7:27 PM, Stephen Connolly
wrote:
> OK. You should probably send out a Cancel notice for this vote and when
> launching the take 4 (I think this will be take 4 but I could be wrong)
> vote I recommend putting take 4
OK. You should probably send out a Cancel notice for this vote and when
launching the take 4 (I think this will be take 4 but I could be wrong)
vote I recommend putting take 4 in the subject line as Gmail folded the
-044 staging repo into the same thread as -038 so it was harder for some
people to
I'll see if Robert wants to fix the DOAP file and I'll respin tomorrow after
he's commented.
On May 28, 2013, at 7:17 PM, Stephen Connolly
wrote:
> Yep looks fine to me. If you want to respin now, from _my_ PoV *should*
> be no issues now... of course who knows what will crop up with the n
Yep looks fine to me. If you want to respin now, from _my_ PoV *should*
be no issues now... of course who knows what will crop up with the next
review ;-)
On 29 May 2013 00:07, Jason van Zyl wrote:
> This should suffice for the notice:
>
> https://git-wip-us.apache.org/repos/asf?p=maven.git
This should suffice for the notice:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f62
On May 28, 2013, at 5:48 PM, Stephen Connolly
wrote:
> From my PoV the only outstanding issue is that the NOTICE.txt does not
> reflect the fact that it is now Eclipse Aether and no
>From my PoV the only outstanding issue is that the NOTICE.txt does not
reflect the fact that it is now Eclipse Aether and no longer Sonatype
Aether.
I am unclear what the exact wording that is required, I am hoping that
somebody else can correct the file. All the license header issues are, to
my
It's very easy to cut another release. If all the fixes are in that the PMC
wishes it takes minutes to roll the release again.
On May 28, 2013, at 4:43 PM, Robert Scholte wrote:
> Some additional remarks:
> - The copyright doesn't include current year (I've already fixed that on the
> trunk)
>
Some additional remarks:
- The copyright doesn't include current year (I've already fixed that on
the trunk)
- doap:generate fails: The generated DOAP doesn't respect ASF rules.
Just to be sure I understand correctly: these alpha-versions will never be
released. They are created so users can
Done, see http://git-wip-us.apache.org/repos/asf/maven/commit/e1807abf
Op Tue, 28 May 2013 21:02:24 +0200 schreef Stephen Connolly
:
Go for it. I committed the license header fix-ups Not sure myself
what
the exact wording is that should go in the NOTICE.txt but I know it is
wrong... Th
Go for it. I committed the license header fix-ups Not sure myself what
the exact wording is that should go in the NOTICE.txt but I know it is
wrong... Therefore AIUI that is a blocker for the PMC permitting the
release as is...
In any case if the rest of the PMC do not see it as a blocker migh
One small comment regarding the packaging.html files:
IMO any package.html under src/main/java should be replaced
package-info.java, because it doesn't make sense to have html-files
between the java-sources.
Robert
Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly
:
[x] Buil
Would it help to catch NoClassDefFoundError
DefaultBuildPluginManager.executeMojo and if it's
anything in the org/sonatype/aether/ space, give a warning about
requiring newer plugin?
Kristian
2013/5/28 Arnaud Héritier :
> For now I had no issue with this release after an upgrade of few plugins
>
For now I had no issue with this release after an upgrade of few plugins
In the future (another Alpha ..) couldn't you catch such error and provide
a more user friendly message asking to upgrade the plugin :
[INFO] Dependency-reduced POM written at:
/Users/arnaud/Code/eXo/platform-public-distribu
[x] Builds from source bundle
[x] Builds some complex projects
[x] Contains correct LICENSE.txt
[ ] NOTICE.txt correctly attributes 3rd party components (See observation 1)
[?] All source files, where appropriate, contain the ASL header (See
observation 2)
[?] Binary archives bundled within the sou
Developers List
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
Tested on my Tycho (0.17.0 and latest staged 0.18.0) build and it fails but
I think this is a Tycho issue.
Regards
Jeff
On Tue, May 28, 2013 at 10:03 AM, Baptiste MATHUS wrote:
> OK, you're right. Jason's cancellation mail was
Tested on my Tycho (0.17.0 and latest staged 0.18.0) build and it fails but
I think this is a Tycho issue.
Regards
Jeff
On Tue, May 28, 2013 at 10:03 AM, Baptiste MATHUS wrote:
> OK, you're right. Jason's cancellation mail was
> http://mail-archives.apache.org/mod_mbox/maven-dev/201305.mbox/br
OK, you're right. Jason's cancellation mail was
http://mail-archives.apache.org/mod_mbox/maven-dev/201305.mbox/browser and
is actually for -038.
Gmail has merged threads for me so I mixed up things.
Thanks
2013/5/28 Stephen Connolly
> I think staging 044 is the respin
>
>
> On 28 May 2013 08:
I think staging 044 is the respin
On 28 May 2013 08:10, Baptiste MATHUS wrote:
> I *think* that vote was also cancelled, isn't it?
>
>
> 2013/5/27 Hervé BOUTEMY
>
> > +1
> >
> > works fine for me
> >
> > Regards,
> >
> > Hervé
> >
> > Le samedi 25 mai 2013 08:51:00 Jason van Zyl a écrit :
> >
I *think* that vote was also cancelled, isn't it?
2013/5/27 Hervé BOUTEMY
> +1
>
> works fine for me
>
> Regards,
>
> Hervé
>
> Le samedi 25 mai 2013 08:51:00 Jason van Zyl a écrit :
> > Here are the release bits for 3.1.0-alpha-1:
> >
> > Release notes:
> >
> https://jira.codehaus.org/secure/R
+1
works fine for me
Regards,
Hervé
Le samedi 25 mai 2013 08:51:00 Jason van Zyl a écrit :
> Here are the release bits for 3.1.0-alpha-1:
>
> Release notes:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
> 967
>
> Staging repository:
> https://repository.apache
n Zyl [mailto:ja...@tesla.io]
Envoyé : samedi 25 mai 2013 14:51
À : Maven Developers List
Objet : [VOTE] Apache 3.1.0-alpha-1
Here are the release bits for 3.1.0-alpha-1:
Release notes:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
967
Staging reposito
update dependency shared:maven-dependency-tree from 2.0 to 2.1
Regards,
Eric
-Message d'origine-
De : Jason van Zyl [mailto:ja...@tesla.io]
Envoyé : samedi 25 mai 2013 14:51
À : Maven Developers List
Objet : [VOTE] Apache 3.1.0-alpha-1
Here are the release bits for 3.1.0-al
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-044/
Staged distribution:
https://repository.apache.org/content/repositories/ma
And one more time. The snapshot repository is still in there.
On May 23, 2013, at 2:02 PM, Jason van Zyl wrote:
> 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://
Not intentional, I'm working in a branch from the first time I cut the release
and I changed that one. I'll re-cut it shortly.
On May 25, 2013, at 3:25 AM, Hervé BOUTEMY wrote:
> the snapshot repository in parent pom is still here: IIUC, it was one of the
> reason you cancelled previous vote
>
Well that's just showing off now isn't it :)
Hervé BOUTEMY wrote:
I deployed Maven 3.1.0-alpha-1 site with itself:)
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apa
the snapshot repository in parent pom is still here: IIUC, it was one of the
reason you cancelled previous vote
is this intentional?
what impact does it have?
Regards,
Hervé
Le jeudi 23 mai 2013 14:02:44 Jason van Zyl a écrit :
> Here are the release bits for 3.1.0-alpha-1:
>
> Release notes:
I deployed Maven 3.1.0-alpha-1 site with itself :)
Regards,
Hervé
Le samedi 25 mai 2013 17:30:50 Mark Derricutt a écrit :
> +1 Looking good for me on my multi-module OSGi builds,
> clojure-maven-plugin and ITs, releases made to both projects and so far
> nothing jumping out at me - tho I'm not b
+1 Looking good for me on my multi-module OSGi builds,
clojure-maven-plugin and ITs, releases made to both projects and so far
nothing jumping out at me - tho I'm not building any maven sites or
anything.
Jason van Zyl wrote:
Thanks.
On May 23, 2013, at 6:40 PM, Hervé BOUTEMY wrote:
site
Thanks.
On May 23, 2013, at 6:40 PM, Hervé BOUTEMY wrote:
> site published (sync pending):
> http://maven.apache.org/ref/3.1.0-alpha-1
>
> Regards,
>
> Hervé
>
> Le jeudi 23 mai 2013 16:52:13 Jason van Zyl a écrit :
>> If you are to test the source you're suppose to actually test the source
site published (sync pending):
http://maven.apache.org/ref/3.1.0-alpha-1
Regards,
Hervé
Le jeudi 23 mai 2013 16:52:13 Jason van Zyl a écrit :
> If you are to test the source you're suppose to actually test the source
> distribution.
>
> If you want to test via the sha1 here you go:
> 32d720ea0
If you are to test the source you're suppose to actually test the source
distribution.
If you want to test via the sha1 here you go:
32d720ea0c669d4f55c0f71e4f3e054695648732
If someone else can publish the site I'd appreciate it.
On May 23, 2013, at 4:26 PM, Stephen Connolly
wrote:
> What i
What is the tag or git hash (as votes are on source not on binary builds)
and is the site staged?
On Thursday, 23 May 2013, Jason van Zyl wrote:
> Here are the release bits for 3.1.0-alpha-1:
>
> Release notes:
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>
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-038/
Staged distribution:
https://repository.apache.org/content/repositories/ma
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 plugi
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.
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
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
wr
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)
On Thursday, 2 May 2013, Stephen Connolly wrote:
> I think we are just waiting for one more binding vote from a PMC mem
I think we are just waiting for one more binding vote from a PMC member...
But somebody should double check the count
On Thursday, 2 May 2013, ceki wrote:
> Hello all,
>
> Out of curiosity, are there any other non-resolved issues holding up this
> release?
>
> Best regards,
>
> On 23.04.2013 12:2
Hello all,
Out of curiosity, are there any other non-resolved issues holding up
this release?
Best regards,
On 23.04.2013 12:24, Stephen Connolly wrote:
+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.codehau
On 27 Apr 2013, at 18:52, Karl Heinz Marbaise wrote:
> -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)
-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
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.
On 19 Apr 2013, at 07:53, Anders Hammar wrote:
> Does anyone (Igor?) know if there is work going on to make Tycho work with
> this?
>
> /Anders
>
>
> On Fri, Apr
Does anyone (Igor?) know if there is work going on to make Tycho work with
this?
/Anders
On Fri, Apr 19, 2013 at 8:16 AM, Hervé BOUTEMY wrote:
> 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
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 an
this will work as well, thank you for the idea.
Original Message
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Nigel Magnay
To: Maven Developers List
Date: Tue 09 Apr 2013 03:47:21 AM CDT
> This keeps coming up, over and over and over.
>
> e.g:
> http://ma
that's it, it works
thank you Stuart: I knew I was missing something like this = few code but
major structure :)
Regards,
Hervé
Le mardi 9 avril 2013 12:30:31 Stuart McCulloch a écrit :
> On 9 Apr 2013, at 03:33, Hervé BOUTEMY wrote:
> > I just did the reimport and changed API to let the code
On 9 Apr 2013, at 03:33, Hervé BOUTEMY wrote:
> 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 ne
rc/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
>
> Origi
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
Le mard
Le dimanche 7 avril 2013 22:29:29 Jason van Zyl a écrit :
> On Apr 7, 2013, at 7:32 PM, Hervé BOUTEMY wrote:
> > 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
On Apr 7, 2013, at 7:32 PM, Hervé BOUTEMY wrote:
> 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 y
Hervé BOUTEMY wrote:
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 "gi
1 - 100 of 138 matches
Mail list logo