Re: Some thoughts on Maven 5

Am 10/16/16 um 02:03 schrieb Stephen Connolly: >> On 16 Oct 2016, at 00:07, Christian Schulte wrote: >> Any thoughts about how to name that new build pom? > > project.mvn or pom.mvn > > But only if we move to a non-xml DSL > > If we are still XML then I say stick with pom.xml

Re: Some thoughts on Maven 5

Sent from my iPhone > On 16 Oct 2016, at 00:07, Christian Schulte wrote: > >> Am 10/16/16 um 00:57 schrieb Stephen Connolly: >> We only have to generate a "consumer pom" in modelVersion 4.0.0... and that >> need only be best effort, and will be generated off the PDT ... the

Re: Some thoughts on Maven 5

On Sunday 16 October 2016, Christian Schulte wrote: > Am 10/16/16 um 00:57 schrieb Stephen Connolly: > > We only have to generate a "consumer pom" in modelVersion 4.0.0... and > that > > need only be best effort, and will be generated off the PDT ... the new > Pom > > schema is

Re: Some thoughts on Maven 5

Am 10/16/16 um 00:57 schrieb Stephen Connolly: > We only have to generate a "consumer pom" in modelVersion 4.0.0... and that > need only be best effort, and will be generated off the PDT ... the new Pom > schema is what drives generating the PDT If a scope is used not known to POM 4.0.0, just

Re: Some thoughts on Maven 5

Ahh *version* ok... (glad I asked) On Saturday 15 October 2016, Robert Scholte wrote: > Those are the component: "Features dependent on POM Format Changes" > Also have a look at version: "Issues to be reviewed for 4.x" > > > On Sat, 15 Oct 2016 23:13:19 +0200, Stephen

Re: Some thoughts on Maven 5

On Saturday 15 October 2016, Christian Schulte wrote: > Am 10/15/16 um 15:20 schrieb Stephen Connolly: > > * does Maven 5 build Maven 2/3 projects? > > No need for this, IMHO. Maven 2 could not build Maven 1 projects. Maven > 3 could build Maven 2 projects but added warnings for

Re: Some thoughts on Maven 5

Am 10/15/16 um 15:20 schrieb Stephen Connolly: > * does Maven 5 build Maven 2/3 projects? No need for this, IMHO. Maven 2 could not build Maven 1 projects. Maven 3 could build Maven 2 projects but added warnings for various things and some internal model transformations like for the 'reporting'

Re: Some thoughts on Maven 5

Those are the component: "Features dependent on POM Format Changes" Also have a look at version: "Issues to be reviewed for 4.x" On Sat, 15 Oct 2016 23:13:19 +0200, Stephen Connolly wrote: I assume that is any issues in the FDPFC component... or is there

Re: Some thoughts on Maven 5

I assume that is any issues in the FDPFC component... or is there additional issues I need to scan? On 15 October 2016 at 19:37, Robert Scholte wrote: > We should have a look at the MNG jira issues for those marked for Maven 4 > too > > > On Sat, 15 Oct 2016 15:20:40

Support for getting local metadata in RepositoryManager

Hi Karl Heinz, So I went ahead and created https://issues.apache.org/jira/browse/MSHARED-596 for this. The ticket is about adding "getPathForLocalMetadata" on the RepositoryManager. In turn, this would simplify DefaultProjectInstaller. I attached a patch to it but would like some comments

Re: Some thoughts on Maven 5

Yep. I'll probably take a stab at that while I try and turn this into an RFC / specification. Is there anything specific you think we could be adding? ("an" because RFC is pronounced Or Eff See, which starts with a vowel) On Saturday 15 October 2016, Robert Scholte

Re: Some thoughts on Maven 5

We should have a look at the MNG jira issues for those marked for Maven 4 too On Sat, 15 Oct 2016 15:20:40 +0200, Stephen Connolly wrote: So now that I have a spec for the PDTs drafted, I have been thinking of how that could influence Maven 5. Some

Re: Maven 3.4 : batch-mode for download progress disabling => impact on color logs feature ?

Hi Michael, Thanks for the reply ... and ok, I understand the point of view. Note that I have added several improvements to the progress meter in master. > Thanks for the information, I will look at MNG-5977 concretely. Still keep in mind that

Re: Maven 3.4 : batch-mode for download progress disabling => impact on color logs feature ?

Am 2016-10-15 um 19:07 schrieb Alix Lourme: Hi Maven (Core) maintainers, Currently the download progress for dependencies/plugins is displayed by default : --- Downloading: http://.../repository/org/foo/bar/x.y.z/bar-x.y.z.jar 4/2122 KB 8/2122 KB

Re: Some thoughts on Maven 5

I'm thinking that we still want a dependency management section, so I'd probably just have that as a dependency tag at the top level or aggregate them in a dependencies tag at the top level... mostly that section though becomes about specifying versions... and really it's only useful from the

Maven 3.4 : batch-mode for download progress disabling => impact on color logs feature ?

Hi Maven (Core) maintainers, Currently the download progress for dependencies/plugins is displayed by default : --- Downloading: http://.../repository/org/foo/bar/x.y.z/bar-x.y.z.jar 4/2122 KB 8/2122 KB --- The common fix is to use

Re: Some thoughts on Maven 5

So building the effective build time model would be: Start with parent, add in matching packaging from parent, in Pom order, add each mix-in (including matching packaging from mix-in before processing subsequent mix-ins), finally apply local pom. To compute effective lifecycle and build plan,

Re: Some thoughts on Maven 5

Hmmm shower thinking now has me pondering if a custom DSL might be better... something close to human friendly JSON with exceptions for dependency declaration so that they are always specified as g:a:p:v:c:t with the optional p and c being empty, e.g. g:a::v::t On 15 October 2016 at 15:26,

Re: Some thoughts on Maven 5

Thinking out loud... perhaps something like [] [] ... [] [ ... ] [ ... ] ... [ ... ] [ ... ] [ ... ] ... [ ... ] [ ] [ ] [ [] [ ... ]

Re: Some thoughts on Maven 5

Sent from my iPhone > On 15 Oct 2016, at 14:20, Stephen Connolly > wrote: > > So now that I have a spec for the PDTs drafted, I have been thinking of how > that could influence Maven 5. Some things that came to mind, in no particular > order: > > * scope

Some thoughts on Maven 5

So now that I have a spec for the PDTs drafted, I have been thinking of how that could influence Maven 5. Some things that came to mind, in no particular order: * scope becomes a build time only concern. Thus we can let users define custom scopes in their pom. If we let plugin executions

Re: Maven 3.3.9 build error using intellij 2016

Am 2016-10-15 um 13:48 schrieb Karl Heinz Marbaise: Hi, The first test I would suggest to delete your whole local cache $HOME/.m2/repository. I personally do: mvn clean install -Dmaven.repo.local=$(mktemp -d) with a local Nexus instance it is blazingly fast.

Re: Maven 3.3.9 build error using intellij 2016

Hi, what I have missed. This is question for the users list and not for the dev list On 14/10/16 21:39, ggo...@hushmail.com wrote: Hi: My name is Gopal. I am getting a strange error. Most of the common libraries are stored in artifactory. The entire project builds without any error using

Re: Maven 3.3.9 build error using intellij 2016

Hi, The first test I would suggest to delete your whole local cache $HOME/.m2/repository. Afterwards build the whole project on command line via: mvn clean package That should work without any issue...otherwise you have a issue in your build which should be fixed first Apart from

Re: [VOTE] Release Apache Maven PMD Plugin version 3.7

+1 Le jeudi 13 octobre 2016, Hervé BOUTEMY a écrit : > same issue with maven-pmd-plugin-3.6: there's something strange on my > machine... > > then +1 > > Regards, > > Hervé > > Le jeudi 13 octobre 2016 20:02:27 Andreas Dangel a écrit : > > That's weird. I don't see