Jason,
On Jul 13, 2013, at 12:44 PM, Jason van Zyl wrote:
> I will try and automate for everyone to have a correct set of attributions.
>
> If you want to manually update the correct files that's fine too.
I think this is now done on master, but requires a release of the
remote-resources. J
I will try and automate for everyone to have a correct set of attributions.
If you want to manually update the correct files that's fine too.
On Jul 13, 2013, at 11:24 AM, sebb wrote:
> On 13 July 2013 15:11, Jason van Zyl wrote:
>> Sorry about that. I did register the issue
>
> OK.
>
>> and
On 13 July 2013 15:11, Jason van Zyl wrote:
> Sorry about that. I did register the issue
OK.
> and I'll make something to generate the correct attributions for the next
> release.
There should be need to auto-generate anything for the source release;
just ensure the correct N&L files are prese
Sorry about that. I did register the issue and I'll make something to generate
the correct attributions for the next release. Hopefully the next one will not
take 7 months. I sent the first email out for the first 3.1.0 on December 2nd,
2012 :-)
On Jul 13, 2013, at 10:00 AM, sebb wrote:
> On
On 13 July 2013 14:54, Jason van Zyl wrote:
> The vote has passed with the following:
>
> +1 Binding: Arnaud, Stephen, Olivier, Hervé
> +1 Non-binding: Stevo, Anders, Tony, Tamas, Baptiste, Mark, Mirko
I voted -1 (non-binding) because of the invalid NOTICE file (amongst
other reasons).
>
> I'll
The vote has passed with the following:
+1 Binding: Arnaud, Stephen, Olivier, Hervé
+1 Non-binding: Stevo, Anders, Tony, Tamas, Baptiste, Mark, Mirko
I'll promote the release in Nexus and update the docs and announce Monday when
it's all done.
On Jun 30, 2013, at 3:00 PM, Jason van Zyl wrote:
AWESOME!!! Thanks for getting this out the door.
manfred
> I will send out the vote result and do the release over the weekend.
>
> On Jun 30, 2013, at 3:00 PM, Jason van Zyl wrote:
>
>> Here are the release bits for 3.1.0:
>>
>> Release notes:
>> https://jira.codehaus.org/secure/ReleaseNote.jsp
I will send out the vote result and do the release over the weekend.
On Jun 30, 2013, at 3:00 PM, Jason van Zyl wrote:
> Here are the release bits for 3.1.0:
>
> Release notes:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>
> Staging repository:
> https://r
Can't reproduce it on my Win7 machine either. I'll close it.
Robert
Op Wed, 10 Jul 2013 20:51:09 +0200 schreef Anders Hammar
:
Not yet tested but is there someone who could have a look at this one :
https://jira.codehaus.org/browse/MNG-5492
This regression seems strange
I can't reproduc
> Not yet tested but is there someone who could have a look at this one :
> https://jira.codehaus.org/browse/MNG-5492
> This regression seems strange
>
I can't reproduce that issue. Introducing an error in the global
settings.xml makes Maven 3.1.0 fail on my MBP.
/Anders
>
>
> On Wed, Jul 10, 2
Not yet tested but is there someone who could have a look at this one :
https://jira.codehaus.org/browse/MNG-5492
This regression seems strange
On Wed, Jul 10, 2013 at 2:29 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> +1
>
>
> On 4 July 2013 20:35, Stephen Connolly >wrote:
>
+1
On 4 July 2013 20:35, Stephen Connolly wrote:
> I am withdrawing my -1 on the basis of the feedback I have received from
> legal-discuss.
>
> My vote is now +0 as I have not tested the distribution and I am waiting
> for somebody else on the PMC to do the running and make a call on whether
>
+1
2013/7/7 Hervé BOUTEMY :
> +1
>
> works fine here
>
> Regards,
>
> Hervé
>
> Le dimanche 30 juin 2013 15:00:40 Jason van Zyl a écrit :
>> Here are the release bits for 3.1.0:
>>
>> Release notes:
>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
>> 967
>>
>> Stagin
+1 (non-binding)
Apache Mahout builds OK with Apache Maven 3.1.0.
Kind regards,
Stevo Slavić.
On Sun, Jul 7, 2013 at 6:00 PM, Anders Hammar wrote:
> +1 (non-binding)
>
> Didn't try any of the new stuff explicitly though.
>
> /Anders
>
>
> On Sun, Jun 30, 2013 at 9:00 PM, Jason van Zyl wrote:
+1 (non-binding)
Didn't try any of the new stuff explicitly though.
/Anders
On Sun, Jun 30, 2013 at 9:00 PM, Jason van Zyl wrote:
> Here are the release bits for 3.1.0:
>
> Release notes:
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>
> Staging repositor
On Sun, 30 Jun 2013 15:00:40 -0400
Jason van Zyl wrote:
+1,
works fine for our projects.
thanks,
tony.
> Here are the release bits for 3.1.0:
>
> Release notes:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>
> Staging repository:
> https://repository.apa
+1
works fine here
Regards,
Hervé
Le dimanche 30 juin 2013 15:00:40 Jason van Zyl a écrit :
> Here are the release bits for 3.1.0:
>
> Release notes:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
> 967
>
> Staging repository:
> https://repository.apache.org/co
On 4 July 2013 23:47, Jason van Zyl wrote:
>
> On Jul 4, 2013, at 6:06 PM, sebb wrote:
>
>> On 4 July 2013 20:35, Stephen Connolly
>> wrote:
>>> I am withdrawing my -1 on the basis of the feedback I have received from
>>> legal-discuss.
>>
>> The question to legal-discuss was specifically about
On Thursday, 4 July 2013, sebb wrote:
> On 4 July 2013 20:35, Stephen Connolly
> >
> wrote:
> > I am withdrawing my -1 on the basis of the feedback I have received from
> > legal-discuss.
>
> The question to legal-discuss was specifically about test data, not test
> code.
That "code" is actuall
On Jul 4, 2013, at 6:06 PM, sebb wrote:
> On 4 July 2013 20:35, Stephen Connolly
> wrote:
>> I am withdrawing my -1 on the basis of the feedback I have received from
>> legal-discuss.
>
> The question to legal-discuss was specifically about test data, not test code.
>
> Does the reply to you
On 4 July 2013 20:35, Stephen Connolly wrote:
> I am withdrawing my -1 on the basis of the feedback I have received from
> legal-discuss.
The question to legal-discuss was specifically about test data, not test code.
Does the reply to your query about test data also apply to test code?
As I read
I am withdrawing my -1 on the basis of the feedback I have received from
legal-discuss.
My vote is now +0 as I have not tested the distribution and I am waiting
for somebody else on the PMC to do the running and make a call on whether
we need to fix the NOTICE file for this release.
I intend test
On 4 July 2013 14:18, Barrie Treloar wrote:
> On 4 July 2013 22:29, Stephen Connolly
> wrote:
>> I will let Barrie decide on whether we *have to* cancel this vote because
>> of the issues he identified in the NOTICE file.
>
> Sebb noticed it.
>
> I just dig the version control sleuthing that sho
On 4 July 2013 22:29, Stephen Connolly wrote:
> I will let Barrie decide on whether we *have to* cancel this vote because
> of the issues he identified in the NOTICE file.
Sebb noticed it.
I just dig the version control sleuthing that showed we have been
failing this for a long time.
I think ha
Fair enough.
On Jul 4, 2013, at 8:59 AM, Stephen Connolly
wrote:
> I will let Barrie decide on whether we *have to* cancel this vote because
> of the issues he identified in the NOTICE file.
>
> Until I hear back from legal-discuss, I do not know whether the test data
> issue has any changes r
I will let Barrie decide on whether we *have to* cancel this vote because
of the issues he identified in the NOTICE file.
Until I hear back from legal-discuss, I do not know whether the test data
issue has any changes required, so I do not know whether (on the bits I am
focusing) there is a requir
On 4 July 2013 13:14, sebb wrote:
> On 4 July 2013 12:52, Stephen Connolly
> wrote:
> > On 4 July 2013 12:32, sebb wrote:
> >
> >> On 4 July 2013 11:05, Stephen Connolly >
> >> wrote:
> >> > I have asked the legal-discuss list for an opinion on test data sets
> and
> >> > license headers. From
Then just make the changes you see fit and I'll roll it again. It will only
take a few minutes. If we know what it should be like then we might as well
just do it, as it's likely to take less time than asking if an exception can be
made.
I can cancel the vote. Make the changes you think are req
On 4 July 2013 12:52, Stephen Connolly wrote:
> On 4 July 2013 12:32, sebb wrote:
>
>> On 4 July 2013 11:05, Stephen Connolly
>> wrote:
>> > I have asked the legal-discuss list for an opinion on test data sets and
>> > license headers. From my reading of the current ASF position:
>> > http://www
On 4 July 2013 12:32, sebb wrote:
> On 4 July 2013 11:05, Stephen Connolly
> wrote:
> > I have asked the legal-discuss list for an opinion on test data sets and
> > license headers. From my reading of the current ASF position:
> > http://www.apache.org/legal/src-headers.html#faq-exceptions we do
On 4 July 2013 11:05, Stephen Connolly wrote:
> I have asked the legal-discuss list for an opinion on test data sets and
> license headers. From my reading of the current ASF position:
> http://www.apache.org/legal/src-headers.html#faq-exceptions we do not
> currently have an exception for test da
I have asked the legal-discuss list for an opinion on test data sets and
license headers. From my reading of the current ASF position:
http://www.apache.org/legal/src-headers.html#faq-exceptions we do not
currently have an exception for test data sets.
Pending the outcome of that discussion I will
+1
On Thu, Jul 4, 2013 at 11:18 AM, Baptiste MATHUS wrote:
> +1 (non-binding)
>
>
> 2013/7/1 sebb
>
> > On 1 July 2013 03:56, Barrie Treloar wrote:
> > > On 1 July 2013 06:52, sebb wrote:
> > >> Another problem: the NOTICE file contains the following spurious text:
> > >>
> > >>
> >
> =
+1 (non-binding)
2013/7/1 sebb
> On 1 July 2013 03:56, Barrie Treloar wrote:
> > On 1 July 2013 06:52, sebb wrote:
> >> Another problem: the NOTICE file contains the following spurious text:
> >>
> >>
> =
> >>== NOT
On 1 July 2013 03:56, Barrie Treloar wrote:
> On 1 July 2013 06:52, sebb wrote:
>> Another problem: the NOTICE file contains the following spurious text:
>>
>>=
>>== NOTICE file corresponding to the section 4 d of
On 1 July 2013 06:52, sebb wrote:
> Another problem: the NOTICE file contains the following spurious text:
>
>=
>== NOTICE file corresponding to the section 4 d of==
>== the Apache License, Ve
Jason van Zyl wrote:
Staged distribution:
https://repository.apache.org/content/repositories/maven-084/org/apache/maven/apache-maven/3.1.0/
+1 non-binding on the binary/execution, seems to work fine on a mixture
of my projects.
--
Another problem: the NOTICE file contains the following spurious text:
=
== NOTICE file corresponding to the section 4 d of==
== the Apache License, Version 2.0,
On 30 June 2013 20:00, Jason van Zyl wrote:
> Here are the release bits for 3.1.0:
>
> Release notes:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-084/
>
> Staged distribution:
>
So probably this is:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=893ca28a1da9d5f51ac03827af98bb730128f9f2
:-)
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/
On Sun, Jun 30, 2013 at 9:00 PM, Jaso
+1 (non-binding) tested with some projects.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/
On Sun, Jun 30, 2013 at 9:00 PM, Jason van Zyl wrote:
> Here are the release bits for 3.1.0:
>
> Release notes:
> https:/
Here are the release bits for 3.1.0:
Release notes:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
Staging repository:
https://repository.apache.org/content/repositories/maven-084/
Staged distribution:
https://repository.apache.org/content/repositories/maven-084/
+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
>
1 - 100 of 180 matches
Mail list logo
