grr, seems I'm the culprit of this regression :(
I saw the commit before the report on the ML...
this doesn't change the question of tracking: do we cancel the 3.3.7 vote and
respin 3.3.8? or publish 3.3.7 with this known issue?
Regards,
Hervé
Le jeudi 29 octobre 2015 20:21:45 Igor Fedorenko
I will respin it. It only takes me a few minutes now.
> On Oct 30, 2015, at 12:24 AM, Hervé BOUTEMY wrote:
>
> grr, seems I'm the culprit of this regression :(
> I saw the commit before the report on the ML...
>
> this doesn't change the question of tracking: do we
Yes, that commit fixed the problem and I am able to run our entire build
successfully with the current master. Thank you for looking into this,
Jason.
Very unscientific, but I do see small-ish performance degradation
compared to 3.3.3, the build too 25m50s with 3.3.3 and 26m35s with the
current
Well I cannot build with 3.3.3 because it picks the wrong parent
projects from the reactor so I can only compare with a 3.3.6-SNAPSHOT
that I have been running for the past 4+ months while intermitently
pestering Jason to cut a release ;-)
On 30 October 2015 at 14:09, Igor Fedorenko
This vote is cancelled.
> On Oct 30, 2015, at 9:15 AM, Stephen Connolly
> wrote:
>
> Well I cannot build with 3.3.3 because it picks the wrong parent
> projects from the reactor so I can only compare with a 3.3.6-SNAPSHOT
> that I have been running for the past
It's a smooth ride. Here's my +1 ... not legally, but morally binding ;)
2015-10-28 14:30 GMT+01:00 Jason van Zyl :
> Hi,
>
> Time to release Maven 3.3.7!
>
> Here is a link to the issues resolved:
>
>
+1 beer
On Thu, Oct 29, 2015, 21:29 Andreas Gudian wrote:
> It's a smooth ride. Here's my +1 ... not legally, but morally binding ;)
>
> 2015-10-28 14:30 GMT+01:00 Jason van Zyl :
>
> > Hi,
> >
> > Time to release Maven 3.3.7!
> >
> > Here is a link to
Tested with a few projects, I see no issues with this release. Thank you,
+1 non-binding.
On Oct 29, 2015 17:15, "Tamás Cservenák" wrote:
> +1 beer
>
> On Thu, Oct 29, 2015, 21:29 Andreas Gudian
> wrote:
>
> > It's a smooth ride. Here's my +1 ...
Tried out with a couple of projects that contributed to burning two of the
previous release attempts plus a couple more. All good!
+1
2015-10-29 23:37 GMT+02:00 jieryn :
> Tested with a few projects, I see no issues with this release. Thank you,
> +1 non-binding.
> On Oct 29,
On 29 Oct 2015, at 19:13, Stephen Connolly wrote:
> FYI Mark, your vote is binding as a contributor... i.e. if you voted
> -1 the release manager would have to consider aborting the release,
> your vote just does not provide one of the three required +1's by PMC
*nod* I think I implicitly
-1
3.3.7 fails with string-index-out-of-range exception when parent pom has
scm and I assume other elements with empty child
I think the problem was introduced with recent changes in
DefaultInheritanceAssembler, at least the problem goes away if I replace
the class with the
FYI Mark, your vote is binding as a contributor... i.e. if you voted
-1 the release manager would have to consider aborting the release,
your vote just does not provide one of the three required +1's by PMC
members required to invoke the foundation legal protections for
contributors.
(A release
I took a look and added a test. Can you see if master
(f684761dee739b4ec8a7e6db5a0a6a0b809e66c9) fixes your issue?
> On Oct 29, 2015, at 5:21 PM, Igor Fedorenko wrote:
>
> -1
>
> 3.3.7 fails with string-index-out-of-range exception when parent pom has
> scm and I assume
Hi,
Time to release Maven 3.3.7!
Here is a link to the issues resolved:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12333074
Staging repo:
https://repository.apache.org/content/repositories/maven-1228/
The distributable binaries and sources for testing can be
My point, if I was unclear my apologies, was that the backlog should just
be where work is to be found. And if you find work, then move it into the
next release version. I think that's a simple "one-stop shopping" way to
look at this. It's just a suggestion I thought could help.
Cheers,
Paul
On
FYI, 14 unresolved issues need to move to 3.3.x to make the JIRA list
correct.
PS: Instead of moving the unresolved forward to a 3.3.8 bucket, how come
they aren't put in the Backlog? It would save churn. The Backlog should be
cherry-picked and tickets pulled into the next release when work is
If I put them in the backlog I will completely forget about them. If someone
else wants to shuffle the issues go for it.
jvz
> On Oct 28, 2015, at 7:32 AM, Paul Benedict wrote:
>
> FYI, 14 unresolved issues need to move to 3.3.x to make the JIRA list
> correct.
>
> PS:
Here is my vote:
* As a community member on the technical merit of making this specific release
+1: I have tested this build on the projects that I know are
troublesome and the regressions in 3.3.1 and 3.3.3 are resolved.
* As a member of the committee established by the ASF board with
Am 2015-10-28 um 18:28 schrieb Stephen Connolly:
Thanks for contributions from non-committers go to:
* Martin Schäf
* Joseph Walton
* Keith Turner
* Anton Tanasenko
* Stephen Kitt
* "tssp at web dot de" (whoever you are - a small commit with clear
intent of Apache License grant)
* "sugartxy "
Am 2015-10-28 um 14:30 schrieb Jason van Zyl:
Hi,
Time to release Maven 3.3.7!
Here is a link to the issues resolved:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12333074
Staging repo:
https://repository.apache.org/content/repositories/maven-1228/
The
On 29 Oct 2015, at 2:30, Jason van Zyl wrote:
> Time to release Maven 3.3.7!
+1 non-binding. Works fine on our builds using heavy maven-tiles, and my
largish IT test project all works fine.
Been doing releases and builds all day with no issue.
Mark
--
Mark Derricutt
Hi,
just a note on this conclusion which remembers me that we should add
those cotributors to the final announcment mail and put them on the
release notes as well...to give them the credit they deserve instead of
only mention them here on the dev list...
BTW: Thanks to Stephen to summarize
I
On Wednesday 28 October 2015, Michael Osipov wrote:
> Am 2015-10-28 um 18:28 schrieb Stephen Connolly:
>
>> Thanks for contributions from non-committers go to:
>> * Martin Schäf
>> * Joseph Walton
>> * Keith Turner
>> * Anton Tanasenko
>> * Stephen Kitt
>> * "tssp at web
Hi,
I have cleaned up JIRA ...moved all not solved issues to Backlog for 3.X
Furthermore checked with several projects...maven-jar-plugin,
maven-assembly-plugin (current trunk), some of my own projects
(uptodate-maven-plugin, iterator-maven-plugin, test-maven-eventspy etc.)
without any
Sure you can close the PR. Put 'Closes #nn.' in a commit message.
On Oct 28, 2015 4:38 PM, "Stephen Connolly"
wrote:
> I
>
> On Wednesday 28 October 2015, Michael Osipov wrote:
>
> > Am 2015-10-28 um 18:28 schrieb Stephen Connolly:
> >
> >>
Thanks very much for cleaning up JIRA.
jvz
> On Oct 28, 2015, at 2:11 PM, Karl Heinz Marbaise wrote:
>
> Hi,
>
> I have cleaned up JIRA ...moved all not solved issues to Backlog for 3.X
>
> Furthermore checked with several projects...maven-jar-plugin,
>
26 matches
Mail list logo