-archives.apache.org/mod_mbox/maven-announce/ archives
29. Update the site history with the announce email
30. Publish the site again
31. Celebrate!!!
On 7 April 2017 at 09:59, Stephen Connolly
wrote:
> 23. Mark the version in JIRA as released
>
> On 7 April 2017 at 09:40, Stephen Connolly com> wr
The Apache Maven team would like to announce the release of Apache Maven
3.5.0.
You can download the appropriate sources etc. from the download page
http://maven.apache.org/download.cgi
Notable changes
===
- ANSI colors added to the console output
- Fix various bugs in mvn scripts r
te too. legally we
only vote on the source distribution. we can look into providing the
checksums as a convenience but 30 steps is too much for a release... I want
to strip that way way down
> That's it. :-)
>
> On 8 April 2017 at 09:05, Stephen Connolly com>
> wrote:
&g
Perhaps
On Sat 8 Apr 2017 at 13:22, Robert Scholte wrote:
> Time to think of a release:finalize?
>
> On Fri, 07 Apr 2017 23:13:08 +0200, Stephen Connolly
> wrote:
>
> > On 7 April 2017 at 22:10, Fred Cooke wrote:
> >
> >> Thanks for all of your hard work on
All done now: https://maven.apache.org/docs/history.html has the announce
link for 3.5.0
P A R T Y !!!
On 7 April 2017 at 22:05, Stephen Connolly
wrote:
> 24. Publish the website with https://cms.apache.org/maven/publish
> 25. Send the announcement email
> 26. (PMC only) Record the r
https://twitter.com/ppalaga/status/851344375502319621
I think it was the use of nested name that contributed too:
origin/MNG-6169/updated-MCOMPILER
On Wed 12 Apr 2017 at 05:47, Karl Heinz Marbaise wrote:
> Hi Hervé,
>
> On 12/04/17 04:35, Hervé BOUTEMY wrote:
> > I suppose this is tied to lots of intermittent failures on git clone
> updates
> > tha
arning about / use in branch names, that may not be
> such
> a good idea
>
> Regards,
>
> Hervé
>
> Le mercredi 12 avril 2017, 06:08:55 CEST Stephen Connolly a écrit :
> > I think it was the use of nested name that contributed too:
> > origin/MNG-6169/updated
On Wed 12 Apr 2017 at 20:21, Dirk Mahler wrote:
> Hi Bindul,
>
> sadly it's not that easy (or it's so easy that I don't see the
> solution...). As a default and for compatibility reasons I'd like to
> declare the dependencies of the Neo4j 2.x artifacts for my Maven plugin:
>
> - org.neo4j:neoj
>
Is it you want the profiles activated during the release:perform fork?
If that is the case you need to modify the "arguments" parameter of the
release goal. Depending on how your pom is set up this could be as simple
as "-Darguments=-P+viennacl -P+..." or you may have to modify the pom
(though if
ely agree we need to prove each code change does not break
> > existing integration tests (and I did run the tests locally with my
> > changes, fwiw)
> >
> > --
> > Regards,
> > Igor
> >
> > On Fri, Apr 7, 2017, at 11:58 AM, Stephen Connolly wrote:
> >
Are your branch jobs here:
https://builds.apache.org/job/maven-3.x-jenkinsfile/
On Thu 13 Apr 2017 at 21:17, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Should trigger automatically
>
> On Thu 13 Apr 2017 at 21:09, Igor Fedorenko wrote:
>
>> I push
t;
> >>
> >> On April 7, 2017 9:24:06 AM Igor Fedorenko wrote:
> >>
> >>> I completely agree we need to prove each code change does not break
> >>> existing integration tests (and I did run the tests locally with my
> >>> changes, fwiw)
&
Just be sure to delete the branch after merging so that the job will get
cleaned up (in 3 days time - retention strategy)
On Thu 13 Apr 2017 at 23:53, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> None here!
>
> On Thu 13 Apr 2017 at 23:30, Igor Fedorenko wrote:
On Sun 16 Apr 2017 at 11:32, Marco Vermeulen wrote:
> Hi Maven folks,
>
> I really haven't come here to start a flame war or to give justification
> about why/how I built SDKMAN. Even less, justifying why I gave it such a
> "silly" name. I have come here with friendly intent to help your communit
I'd like people to take this next week to consider what issues we want to
pull in scope for 3.5.1.
If you are a committer, just add the issues to Fix Version of
3.5.1-candidate, ideally adding a comment at the same time with your
reasoning.
If once we have a seconding committer, they can just com
Progress seems to be being made... I'm willing to let current progress
continue for the next 1-2 weeks before starting a whip-round to drive
towards a release... anyone want me to accelerate?
On Tue 25 Apr 2017 at 21:43, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> I
On Sun 14 May 2017 at 08:51, Hervé BOUTEMY wrote:
> thank you Robert: this is exactly the logic I was looking for, and
> explanation
> of changes over time to improve user experience through reproducibility.
>
> Now the question is: should we change default plugin versions in Maven
> core?
> Does
On 16 May 2017 at 06:53, Michael Osipov wrote:
> MNG-6167
+1
On Tue 16 May 2017 at 22:40, Hervé BOUTEMY wrote:
> Le lundi 15 mai 2017, 07:20:08 CEST Stephen Connolly a écrit :
> > On Sun 14 May 2017 at 08:51, Hervé BOUTEMY
> wrote:
> > > thank you Robert: this is exactly the logic I was looking for, and
> > > explanation
tibor_: @stephenc Hi Stephen. Would these two work on OSX the same like on
linux and freebsd?
tibor_: ps -o start,args -p 27000
tibor_: java -Dppid=$PPID ...
I'd need more context to answer
Sent from my iPhone
On Thu 1 Jun 2017 at 18:21, Paul Hammant wrote:
> So the only one that worked as the -D arg to the maven invocation. I
> checked the 10K jar into source control to avoid the bootstrap problem, and
> Circle CI does exactly what I'd hope for. Proof being the intended result -
> https://buildradiato
Jesse Glick needs this release for some downstream fixes in the Jenkins
project.
If nobody objects I'll cut the release on Monday.
-Stephen
They are now adding user grouping... I wonder how long before repo grouping
too
On Sun 18 Jun 2017 at 17:12, Paul Hammant wrote:
> Choose one to start with, is what I would do.
>
> git svn clone of a trunk only, then make that master. branch/tag history
> can be retained in Subversion but also u
. but alas)
On 18 June 2017 at 10:12, Paul Hammant wrote:
> Good thought. We could ask about a timeline.
>
> On Sun, Jun 18, 2017 at 1:00 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > They are now adding user grouping... I wonder how long befor
> - Paul
>
> On Sun, Jun 18, 2017 at 4:39 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Liable to get an answer like:
> >
> > > We don't comment our roadmap publicly I'm afraid
> >
> > (I've gotten tha
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&version=1253&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317520%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20
on on the version
number in light of MENFORCER-267 having snuck in
On 20 June 2017 at 02:02, Stephen Connolly
wrote:
> Hi,
>
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12317520&version=1253&styleName=Text
>
> There are
Nope IIRC the intent of MENFORCER-267 is that the version should be 3.0.0
(hence the Fix Version)
On 20 June 2017 at 04:14, Anders Hammar wrote:
> v2.0.0?
>
> /Anders
>
> On Tue, Jun 20, 2017 at 12:53 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
; CMS. I
> > > >
> > > > >> suggested that if they could add themes for "high school",
> > "community
> > > > >> group", etc they could pull in another category of user of the
> > > >
> > > > platform, and
>
Ok, I'm dropping this and respinning as 3.0.0
On 20 June 2017 at 10:02, Stephen Connolly
wrote:
> Hi,
>
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12317520&version=1253&styleName=Text
>
> There are sti
So IIRC one of the blockers is moving the code to use the new graph
stuff... some of the rules were failing when I tried to convert to the new
APIs and that blocked my release attempt... I haven't had the time to pick
it up since
On 17 July 2017 at 13:09, Robert Scholte wrote:
> Vote for maven-j
/asf?p=maven.git;a=commit
> ;h=fd57754218e749305be1dd745fda9407960cf985
>
>
>
>> thanks,
>> Robert
>>
>> On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly <
>> stephen.alan.conno...@gmail.com> wrote:
>>
>> I'd like people to ta
B please,
On Sat 19 Aug 2017 at 06:54, Karl Heinz Marbaise wrote:
> Hi,
>
> so based on the feedback I will go back to INFRA and let them configure
> a separate Configuration type "Maven Issue Type Scheme" which contains
> the issue type "Dependency Upgrade"...
>
> Kind regards
> Karl Heinz Marb
Advance warning, my intent is to start cutting RCs towards the end of next
week.
Focus on bugs and Java 9 compatibility would be best at this stage
(Getting to an actual release will take as long as it takes, but I intend
actively triage of the scope and RCs every 1-2 weeks until we get there)
-
verybody! :)
>
> Regards,
>
> Hervé
>
> Le mercredi 23 août 2017, 19:09:03 CEST Stephen Connolly a écrit :
> > Advance warning, my intent is to start cutting RCs towards the end of
> next
> > week.
> >
> > Focus on bugs and Java 9 compatibility would be best at this
; Robert
>
> [1] https://s.apache.org/maven-3.5.1-RC_jira
> [2] https://issues.apache.org/jira/browse/MNG-6275
> [3]
> https://git1-us-west.apache.org/repos/asf?p=maven.git;a=commit;h=c829bdcf
> [4] https://builds.apache.org/job/maven-3.x-jenkinsfile/job/MNG-6275/1/
>
>
>
I am seeing two issues remaining for 3.5.1:
https://issues.apache.org/jira/browse/MNG-6216:
ArrayIndexOutOfBoundsException when parsing POM
and
https://issues.apache.org/jira/browse/MNG-5868: Adding serval times the
same artifact via MavenProjectHelper (attachArtifact) does not produce a
failure
Should support but not require same names integration branch... likely the
Jenkinsfile needs updating after JENKINS-43507
On Tue 29 Aug 2017 at 19:17, Karl Heinz Marbaise wrote:
> Hi,
>
> currently I'm observing that I can a branch in Maven Core for example
> MNG-6216 but it looks like I need a
Let's see how
https://builds.apache.org/blue/organizations/jenkins/maven-3.x-jenkinsfile/branches/
goes now...
On 29 August 2017 at 19:40, Karl Heinz Marbaise wrote:
> Hi,
>
> On 29/08/17 20:35, Stephen Connolly wrote:
>
>> Should support but not require same n
https://builds.apache.org/blue/organizations/jenkins/maven-3.x-jenkinsfile/detail/master/128/pipeline
more corectly
On 29 August 2017 at 21:49, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Let's see how https://builds.apache.org/blue/organizations/jenkins/
> mave
Ok, it's running the integration tests again... we are back in business
On 29 August 2017 at 21:51, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> https://builds.apache.org/blue/organizations/jenkins/
> maven-3.x-jenkinsfile/detail/master/128/pipeline more corectly
https://github.com/apache/maven/commit/e44c39c2eb5afda9efe60b9dd0ffc32c62501c5f
fixes the Jenkinsfile after the changes introduced by JENKINS-43507 so in
order to get those two branches to have a realistic integration test result
status I have `git push --force-with-lease` these two branches after
Please see
https://builds.apache.org/blue/organizations/jenkins/maven-3.x-jenkinsfile/branches
for the status of the core branches.
Please delete branches if they have been merged to master already or if
they are no longer relevant
Thanks
-Stephen
Failure is in testBootstrap, probably something obvious, here's the
problematic build log... you can inspect for yourself at
https://builds.apache.org/blue/organizations/jenkins/maven-3.x-jenkinsfile/detail/master/128/tests
but there is no point in looking at any tests other than testBootstrap as
i
I have pushed bisect-1, bisect-2 and bisect-3 to see if we can identify the
problematic commit since the last known good build of master (#123 for
commit 4f2a2dba89251d9045fe9944783509a397491da3)
On 29 August 2017 at 22:09, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> F
Another build based on master is well failing on all four exec environments:
https://builds.apache.org/job/maven-3.x-jenkinsfile/job/MNG-6216/4/testReport/junit/org.apache.maven.it/MavenITBootstrapTest/
So clearly the build failure is real
On 29 August 2017 at 22:13, Stephen Connolly
bisect-0 is the last known good commit with the Jenkinsfile fix to confirm
that the failures are not another infra related change
On 29 August 2017 at 22:13, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> I have pushed bisect-1, bisect-2 and bisect-3 to see if we can ident
/f047ea143766fd22ae42040e6805bef287f3cc3e
On 29 August 2017 at 22:17, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> bisect-0 is the last known good commit with the Jenkinsfile fix to confirm
> that the failures are not another infra related change
>
> On 29 August 2017 at 22:13, Stephen Co
I'll delete branches bisect-0 through bisect-3 once Robert ACKs my analysis
On 29 August 2017 at 16:57, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Ok, looking a the results of the bisect-0 through bisect-3 builds, 0 and 1
> both fail just for the MNG-6127
27, so the build passes... bisect-3 also passes, so the smoking
>> gun is...
>>
>> https://github.com/apache/maven/commit/f047ea143766fd22ae420
>> 40e6805bef287f3cc3e
>>
>> On 29 August 2017 at 22:17, Stephen Connolly <
>> stephen.alan.conno...@gmail.com&
0
On 30 August 2017 at 02:26, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> https://github.com/apache/maven/commit/39004f6aee634a0ac6daa1f99add29
> 9ff439f5ec should fix
>
> On 30 August 2017 at 02:09, Robert Scholte wrote:
>
>> Now that the ITs are all i
I have deleted bisect-0 through -3 as they have served their purpose
On Wed 30 Aug 2017 at 10:31, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
> https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/job/mng-6275/
> will report the status... I am
docs this change makes sense.
> I was too fast with the revert, meaning you could reintroduce the
> unit-test, which was the original symptom.
>
> Robert
>
>
> On Wed, 30 Aug 2017 11:31:30 +0200, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> ht
Kristian, FYI
https://github.com/codehaus-plexus/plexus-interpolation/commit/0714af6ce3b4371a8a914496f3632c405b2e3e0c
broke binary compatibility
On 30 August 2017 at 03:54, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hmmm so my fix has 24 failing tests... most of whic
) interpolator,
recursionInterceptor );
}
style chaining
Unclear at this point if the change for MNG-6275 is exposing this breaking
change
On 30 August 2017 at 03:56, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Kristian, FYI
>
> https://github.com/codehaus-plexus/plexus-inter
, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> https://github.com/codehaus-plexus/plexus-interpolation/commit/
> 0714af6ce3b4371a8a914496f3632c405b2e3e0c#diff-
> 95342973516cd90dd54ef6a15afa1961 should have *added* the methods taking
> BasicInterpolator rather than r
On 30 August 2017 at 04:13, Stuart McCulloch wrote:
> On Wednesday, 30 August 2017 at 10:26, Stephen Connolly wrote:
> > https://github.com/apache/maven/commit/39004f6aee634a0ac6daa1f99add29
> 9ff439f5ec
> > should fix
> >
> >
>
> Is it worth storing the chos
fef668789f6abe79f603b96a8ee6f13ea52de4df should verify if that fixes things
On 30 August 2017 at 04:13, Stuart McCulloch wrote:
> On Wednesday, 30 August 2017 at 10:26, Stephen Connolly wrote:
> > https://github.com/apache/maven/commit/39004f6aee634a0ac6daa1f99add29
> 9ff439f5ec
&g
Hmmm... looking like we may have to descope MNG-6275... I'll do some more
digging first though
On 30 August 2017 at 04:34, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> fef668789f6abe79f603b96a8ee6f13ea52de4df should verify if that fixes
> things
>
> On
I think we'll de-scope 6275 for 3.5.1
On Wed 30 Aug 2017 at 16:04, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hmmm... looking like we may have to descope MNG-6275... I'll do some more
> digging first though
>
>
> On 30 August
>
> On Wed, 30 Aug 2017 18:01:12 +0200, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> I think we'll de-scope 6275 for 3.5.1
>>
>>
>>
>>
>> On Wed 30 Aug 2017 at 16:04, Stephen Connolly <
>> stephen.alan.conno...@gmail
Unit test is still present in my branch, so should be a yes (if your unit
test works)
On Wed 30 Aug 2017 at 21:50, Robert Scholte wrote:
> But can you access classes via the ServiceLoader?
>
> On Wed, 30 Aug 2017 22:48:40 +0200, Stephen Connolly
> wrote:
>
> >
good to merge...
On 31 August 2017 at 01:27, Robert Scholte wrote:
> Cool
>
>
> On Wed, 30 Aug 2017 23:22:14 +0200, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> Unit test is still present in my branch, so should be a yes (if your unit
>> test w
e what to use
> for the base class loader (atm it doesn’t have that information to hand)
>
> But as a first step this one-line change looks ok, as long as we give
> integrators a heads-up so they can test the snapshot / early release
> candidate.
>
> --
> Cheers, Stuart
>
&
Classifieds are limited to the same character set as s and
s for the same reason that they will form part of the filename.
On Thu 7 Sep 2017 at 08:26, Chris Graham wrote:
> Hi Karl,
>
> Did you ever find what you were looking for?
>
> I came across this in a search on classifiers as I want to be
https://twitter.com/asfmavenproject/status/906451059966693376
--
Sent from my phone
So poll results:
493 votes cast
25% want Java 7,8&9 for Maven 3.6.x
65% want Java 8&9 for Maven 3.6.x
10% want Java 8&9 for Maven 3.6.x and 6 months of backporting to 3.5.x
On Sat 9 Sep 2017 at 11:50, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
Hi,
We solved 25 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338964&styleName=Text&projectId=12316922
There are 350 issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20
distribution but not in the source
revision:
DEPENDENCIES
On 10 September 2017 at 16:39, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 25 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12338964&styleName=Text&pro
lte" wrote:
> >
> > So what would be the conclusion?
> >
> > 35% want to keep Java7 as JRE for Maven for a shorter or longer period?
> >
> > IMHO that's a lot
> >
> >
> > but less than the 65% who do not, an overwhelming majority
t; >
> > 35% want to keep Java7 as JRE for Maven for a shorter or longer period?
> >
> > IMHO that's a lot
> >
> > Robert
> >
> > On Sun, 10 Sep 2017 11:55:20 +0200, Stephen Connolly <
> > stephen.alan.conno...@gmail.com> wrote:
> >
&g
Well I ran the release with 1.7.0_80 which iirc is the last public release
of Oracle Java 7...
On Sun 10 Sep 2017 at 21:08, Michael Osipov wrote:
> Folks,
>
> tried running master on
> Maven home: /usr/local/share/java/maven
> Java version: 1.7.0_151, vendor: Oracle Corporation
> Java home: /us
> >>>
> >>>
> >>> On Sun, Sep 10, 2017 at 11:12 PM, Michael Osipov
> wrote:
> >>>
> >>>>
> >>>> Am 2017-09-10 um 23:07 schrieb Tibor Digana:
> >>>>
> >>>>>
> >>>>> M
erService seems to blowing up
> when using 3.5.1 - need to do some more digging and see if I can spot whats
> going on.
>
> Will try and dig into this after work tonight.
>
> Mark
>
> On 11 Sep 2017, at 8:01, Arnaud Héritier wrote:
>
> Tested on several projects
>
&
family: "unix"
mvn verify => SUCCESS
If I get time later I'll run the integration tests.
On 11 September 2017 at 00:20, Dan Tran wrote:
> False alarm, I missed configure global settings.xml, it is missing the
> default repository setup
>
> -D
>
> On Sun, Se
stMNG6275_projectRealmDefaultParentClassLoader(DefaultClassRealmManagerTest.java:83)
investigating...
On 11 September 2017 at 01:44, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Building the source bundles with the binary bundles in the staging repo
> using the Docker
valid test when the default classloader does not have any
ScriptEngineFactory...
I'm going to commit a fix, but this should not invalidate the 3.5.1 release
On 11 September 2017 at 01:53, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> With https://github.com/apache/maven-
uot;
mvn verify => SUCCESS
On 11 September 2017 at 02:00, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> So Azul's Zulu 7 does not have
>
> com.sun.script.javascript.RhinoScriptEngineFactory or any
> ScriptEngineFactory in the base classloader...
>
> Z
loader
jdk.nashorn.api.scripting.NashornScriptEngineFactory
Main classloader
jdk.nashorn.api.scripting.NashornScriptEngineFactory
Now IIUC, Nashorn is part of Java 8 but Rhino was not required as part of
Java 7, hence from Java 8 onwards there should always be a
ScriptEngineFactory,
ember 2017 at 11:51, Tibor Digana
wrote:
> ServiceLoader in Java takes System ClassLoader by default.
>
> On Mon, Sep 11, 2017 at 11:41 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > https://github.com/apache/maven/commit/542a7a89156263b34d1472e9
arty plugins (so to say).
>
> Everything looks good with one notable regression:
> https://issues.apache.org/jira/browse/MNG-6282 Console output has no
> colors (regression in Maven 3.5.1)
>
> Regards,
> Dejan
>
> On 2017-09-10 17:39, Stephen Connolly
> wrote:
>
ls to detect that it should auto-activate)
>
> details on issue in https://issues.apache.org/jira/browse/MNG-6282 , and a
> future JAnsi issue...
>
> Regards,
>
> Hervé
>
> Le lundi 11 septembre 2017, 12:53:46 CEST Stephen Connolly a écrit :
> > So that is windows
On 13 September 2017 at 00:26, Anders Hammar wrote:
> On Tue, Sep 12, 2017 at 8:54 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Have we got any feedback from the embedder integrations yet?
> >
>
> I haven't heard anything from the
On 13 September 2017 at 01:05, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On 13 September 2017 at 00:26, Anders Hammar wrote:
>
>> On Tue, Sep 12, 2017 at 8:54 PM, Stephen Connolly <
>> stephen.alan.conno...@gmail.com> wrote:
>>
>> &g
On Wed 13 Sep 2017 at 23:30, Mark Derricutt wrote:
> On 14 Sep 2017, at 10:26, Mark Derricutt wrote:
>
> Calling -2 for vote if not too late.
>
> Actually - looking at the commit diff, I see in our code we did have
> true for the jasmine-maven-plugin which we don't
> actually need. Removing that
On 14 September 2017 at 04:43, Mark Derricutt wrote:
> > +2 non-binding from Mark!
>
> I was discussing this with a coworker and he made the comment that if this
> change could break Mojos, maybe it shouldn't be in a point release - whats
> the policy on changes that may potentially break existin
tps://github.com/psiroky/reproducers/tree/mvn351-kie-maven-plugin
>>>> (works
>>>> fine with maven 3.5.0, but fails with NPE with the RC of maven 3.5.1).
>>>>
>>>> I am not yet sure if the plugin is just doing something it's not
>>
d Bricon hasn't been able to
> > > > reproduce.
> > > > > >
> > > > >
> > > > > To follow up on this, my tests indicate that Maven 3.5.1 causes
> changed
> > > > > class loading that could cause issues for plugins in
. but this should have been fixed by 6275
unless I am mistaken
>
> --
> Regards,
> Igor
>
> On Fri, Sep 15, 2017, at 12:09 PM, Stephen Connolly wrote:
> > I'm going to hold off closing the vote over the weekend to give Igor a
> > chance to:
> >
> >
On Sat 16 Sep 2017 at 10:51, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On Sat 16 Sep 2017 at 04:07, Igor Fedorenko wrote:
>
>> I don't really have much to add, but let me answer anyways :-)
>>
>> 1) I am reasonably confident we can
things should work?
Right now I am unclear as to whether we should go ahead with releasing
3.5.1 given the effects of MNG-6209... at least in terms of exposing some
strangeness in the classloaders
On 16 September 2017 at 03:51, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
&
are first, followed by plugin specific extensions, followed by
> global extensions, finally core maven. (This allows resources to be
> specialized.)
>
> regards,
> chas
>
> > On Sep 18, 2017, at 3:20 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
> >
I think you will need a link to the PDF as attachments are stripped from
the ML
On Tue 19 Sep 2017 at 19:57, Robert Scholte wrote:
> Attached a single page overview.
>
> Per block you'll see in the upper left corner the executed plugin
> The left column contains the extensions and plugin in orde
On Tue, Sep 19, 2017, at 03:52 PM, Robert Scholte wrote:
> > Let's do it like this:
> >
> https://cwiki.apache.org/confluence/download/attachments/2329841/classrealms.pdf?api=v2
> >
> > Robert
> >
> > On Tue, 19 Sep 2017 21:08:39 +0200, Stephen Connolly
>
ds,
> Igor
>
> On Tue, Sep 19, 2017, at 05:12 PM, Stephen Connolly wrote:
> > Yes, the expectations are key. Depending on what they are we may either
> > drop 3.5.1 or go ahead as it depends on whether this is more correct than
> > 3.5.0 or swapping one fix for a bug
>
n/blob/maven-3.5.1/maven-
> core/src/main/java/org/apache/maven/project/DefaultProjectBuildingHelper.
> java#L210-L219
>
> --
> Regards,
> Igor
>
> On Wed, Sep 20, 2017, at 03:29 AM, Robert Scholte wrote:
> > On Wed, 20 Sep 2017 09:12:47 +0200, Stephen Connolly
> >
in favour of reverting both MNG-6209 and MNG-6275
(the TCCL one) as I have found documentation stating that TCCL is the
plugin classloader, which makes me wary of changing that in a patch release
(but I can be convinced otherwise)
>
> thanks,
> Robert
>
>
> On Sun, 24 Sep 2017
eed to decide who we need and an actual agenda.
If Monday is too soon I can see if I have a window later this week
On Sun 24 Sep 2017 at 18:58, Igor Fedorenko wrote:
> See my answers/comments inline
>
>
> On Sun, Sep 24, 2017, at 12:07 PM, Stephen Connolly wrote:
> >
mess with classloading in bug fix release, then maybe do what Anders
> suggests (I think), bump the version to 3.6.0, document the behaviour we
> have on master and move on.
>
> --
> Regards,
> Igor
>
> On Sun, Sep 24, 2017, at 02:28 PM, Stephen Connolly wrote:
> > I wo
901 - 1000 of 2711 matches
Mail list logo
