Re: Improving Jenkins

Le mardi 20 décembre 2016, 03:45:47 CET Christian Schulte a écrit : > Am 12/19/16 um 08:32 schrieb Hervé BOUTEMY: > > Le lundi 19 décembre 2016, 00:44:48 CET Christian Schulte a écrit : > >> Am 12/18/16 um 10:19 schrieb Hervé BOUTEMY: > >> Thats what the resolver does when requested to collect

Re: Improving Jenkins

I must confess I never investigated why this "provided" recipe worked: it just looked nice :) but you didn't answer the important part of the question: From a purist point of view, I understand From a user point of view, do you have any case where the new behaviour fixes a non-working

Re: Improving Jenkins

Am 12/20/16 um 03:45 schrieb Christian Schulte: > Collaboration is important. It has helped a lot getting those changes > sorted out. In fact, we are still sorting things out now. That's > something very positive. I do use the 3.4.0-SNAPSHOT locally for everything. Whenever I build a new snapshot

Re: Improving Jenkins

Am 12/19/16 um 08:32 schrieb Hervé BOUTEMY: > Le lundi 19 décembre 2016, 00:44:48 CET Christian Schulte a écrit : >> Am 12/18/16 um 10:19 schrieb Hervé BOUTEMY: >> Thats what the resolver does when requested to collect dependencies for >> a POM or for a dependency. I just made two selector

Re: maven-wagon git commit: [MRESOLVER-9] DefaultDependencyCollector does not correctly handle dependency management.

Am 12/20/16 um 01:58 schrieb Christian Schulte: > 2. Collect dependency > - > CollectRequest.setRoot(Dependency): > The dependency passed to this method is some *direct* dependency you got > from somewhere. Management is considered to already be applied. This > will become the

Re: Improving Jenkins

Am 12/19/16 um 23:22 schrieb Hervé BOUTEMY: > Le lundi 19 décembre 2016, 03:39:15 CET Christian Schulte a écrit : >> Am 12/18/16 um 10:19 schrieb Hervé BOUTEMY: > different: IIUC, if the resolution was not different, the failure would have > happened at build time, isn't it? >From what I can

Re: maven-wagon git commit: [MRESOLVER-9] DefaultDependencyCollector does not correctly handle dependency management.

Am 12/19/16 um 18:26 schrieb Stephen Connolly: > We need to clarify. > > There is stuff that is "wrong" but has become expected behaviour because we > never "fixed" it => we cannot "fix" now because it will break too many users > > There is stuff that is "wrong" because we broke it, some users

Re: Scope promotion of managed dependencies in current Maven master

Am 12/19/16 um 15:56 schrieb Michael Osipov: > [DEBUG]net.sf.michael-o.dirctxsrc:dircontextsource:jar:1.3:compile > [DEBUG] org.slf4j:slf4j-simple:jar:1.7.21:runtime (scope managed from > test by com.company.project:project-parent:0.11-SNAPSHOT)

Re: Improving Jenkins

Le lundi 19 décembre 2016, 03:39:15 CET Christian Schulte a écrit : > Am 12/18/16 um 10:19 schrieb Hervé BOUTEMY: > You know what? We want also that libraries classpath are consistent > when built > > > and when used as dependencies: nothing specific to plugins and core > > extensions.

Re: Maven 3.4.0 Release

+1 also Regards, Hervé Le lundi 19 décembre 2016, 20:36:48 CET Robert Scholte a écrit : > +100 > > On Mon, 19 Dec 2016 20:12:33 +0100, Stephen Connolly > > wrote: > > We need to get the project back in the habit of releasing. > > > > My vote is the we

Developing fix that spans across several Apache projects

Hi, There is an issue in the Maven Assembly Plugin cause by a bug in the Plexus Archiver - https://github.com/codehaus-plexus/plexus-archiver/issues/53. To fix the issue I've created a patch for Apache Common Compress - https://issues.apache.org/jira/browse/COMPRESS-375 My understanding is

Re: Maven 3.4.0 Release

Sure... but as close to be ready to release as possible. At a minimum passing ITs... Gary Gregory wrote on 2016-12-19 11:39: > On Mon, Dec 19, 2016 at 11:24 AM, Manfred Moser > wrote: > >> Totally agree. Master should be ready to release all the time imho. >>

Re: Maven 3.4.0 Release

On Mon, Dec 19, 2016 at 11:24 AM, Manfred Moser wrote: > Totally agree. Master should be ready to release all the time imho. > Nothing that isnt tested well and proven to at least pass all IT's should > be merged into master. Experimentation should happen in feature

Re: Maven 3.4.0 Release

+100 On Mon, 19 Dec 2016 20:12:33 +0100, Stephen Connolly wrote: We need to get the project back in the habit of releasing. My vote is the we rebuild master with a clean history. keep current master as a reference branch, and cherry-pick as we go. The

Re: Scope promotion of managed dependencies in current Maven master

Hi Michael, I can reproduce that behaviour as well. In the current 3.4.0, a dependency management that declares a dependency with scope runtime will manage a transitive dependency of scope test. A reproducer is org.slf4j slf4j-simple 1.7.21

Re: Maven 3.4.0 Release

Totally agree. Master should be ready to release all the time imho. Nothing that isnt tested well and proven to at least pass all IT's should be merged into master. Experimentation should happen in feature branches.. Just my 2c. Manfred Stephen Connolly wrote on 2016-12-19 11:12: > We need

Re: Maven 3.4.0 Release

On Mon, Dec 19, 2016 at 11:12 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > We need to get the project back in the habit of releasing. > +1! Gary > > My vote is the we rebuild master with a clean history. keep current master > as a reference branch, and cherry-pick as we

Re: Maven 3.4.0 Release

We need to get the project back in the habit of releasing. My vote is the we rebuild master with a clean history. keep current master as a reference branch, and cherry-pick as we go. The aim should be kept tight in scope and focus on the aether replacement only. Minimum change for aether

Re: Maven 3.4.0 Release

We're already trying to push a new release for quite some time. And it seems the discussion is not over yet. There are a lot of improvements which deserve a release, so personally I'd like to push the discussion to 3.5.0 Robert On Mon, 19 Dec 2016 14:12:25 +0100, Stephane Nicoll

Re: maven-wagon git commit: [MRESOLVER-9] DefaultDependencyCollector does not correctly handle dependency management.

We need to clarify. There is stuff that is "wrong" but has become expected behaviour because we never "fixed" it => we cannot "fix" now because it will break too many users There is stuff that is "wrong" because we broke it, some users have legitimate bugs and other users have hacks around the

Can I get some other measures of the ITs?

https://builds.apache.org/view/M-R/view/Maven/job/maven-jenkinsfile/job/master/26/testReport/ Is currently the best I have... and with 1084 failing tests it is *not* good... anyone else have a measure? Package

Scope promotion of managed dependencies in current Maven master

Hi folks, I just tried a fresh Maven master (7d1d8ac0c14bdea6c92356436bfc6f8548cbae8b; 2016-12-19T15:22:22+01:00) on an in-house project. My project's parent POM states in depMgmt: org.slf4j slf4j-api ${slf4j.version} org.slf4j jcl-over-slf4j ${slf4j.version} runtime

Re: Improving Jenkins

No. my son is only in school during the AM, so you might have a chance to try some iterations to get it working sooner... we are only prodding the dark! (And I'm validating my complaints about how literate is better than jenkinsfile... but I lost that popularity contest) Or anyone else can too

Re: Improving Jenkins

For windows? Am I punished ? Bouhhh Le lun. 19 déc. 2016 à 15:17, Stephen Connolly < stephen.alan.conno...@gmail.com> a écrit : > https://builds.apache.org/view/M-R/view/Maven/job/maven-jenkinsfile > > > > Working on a Jenkinsfile... should work for linux on Java 7 & 8... getting > > the

Re: Improving Jenkins

https://builds.apache.org/view/M-R/view/Maven/job/maven-jenkinsfile Working on a Jenkinsfile... should work for linux on Java 7 & 8... getting the Windows builds working will be "fun"... perhaps Arnaud can assist! On 19 December 2016 at 09:41, Stephen Connolly < stephen.alan.conno...@gmail.com>

Re: Maven 3.4.0 Release

Isn't that postponing the discussion we're having here on those controversial changes? I'd rather give it an extra effort rather than pushing it back and loosing all the context once we have to tackle 3.5. On Sun, Dec 18, 2016 at 10:02 PM, Stephen Connolly < stephen.alan.conno...@gmail.com>

Re: IPv6

I would hope that IPv6 records would be recognized from DNS. Another question is using RFC2732 style host URLs like http://[1080::8:800:200C:417A]/foo https://www.ietf.org/rfc/rfc2732.txt One tiny isuse for a pure IPv6 deployment is that Maven Central don't seem to be available on IPv6.

Re: Improving Jenkins

We should probably look at switching to multi-branch / org folders... I released a set of -beta-1 releases on Friday (due to some scaredy-cats not being comfortable with pushing full releases to the update centre on a Friday afternoon before I start a 2 week break! Chickens!) These releases

Re: Re: Improving Jenkins

> > And updating plugins for Maven own builds to work now won't help Maven > > users > > to update their builds > > Notice I use the word "update", not "fix": I don't care if you think that > > the > > required update is a positive fix because everything was buggy for 10 years > > and > >