Update Cwiki Roadmap 2017

Hi Hervé, Stephen, another bus load of candidates have been seconded/blessed for FIX-3.5.0 recently by Karl Heinz, me, Christian and you two. Can you update the wiki page accordingly? I'd like to continue to work on agreed changes. Michael

Always get the false value when calling org.apache.maven.shared.invoker.InvovationRequest.isUpdateSnapshots()

Hello, Using the org.apache.maven.shared.invoker.InvovationRequest leads to get always the false value, even if the "-U" or "--update-snapshots" option is set. InvocationRequest request = new DefaultInvocationRequest(); updateSnapshots = request.isUpdateSnapshots(); Posts @

Re: Maven Jenkinsfile Job is Gone

no mistake, I renamed it to better find it in the too long jobs list [1]: I just forgot to add it to the view definition, I just did it (Jenkins does not do it automatically when renaming, it seems) We should probably do some cleanup between these core-integration-testing- maven-3*,

Re: Requesting a single Monorepo enhancement for Maven

It is the last big problem, yes. Sent from my iPhone > On Jan 24, 2017, at 10:10 AM, Igor Fedorenko wrote: > > Don't mean to derail the discussion, but I am wondering if sparse > checkout is the last/biggest problem you have to solve to use maven for > your "one bg ass

Re: Requesting a single Monorepo enhancement for Maven

Hi Paul, Paul Hammant wrote: > OK, so I'm a documenter of Google's Monorepo (one bg ass trunk) and > it's usage of shell scripts to subset the checkout for speedy development: > >http://paulhammant.com/2014/01/06/googlers-subset-their-trunk/ >

Re: Update Cwiki Roadmap 2017

No, I don't. Read-only. I will create an INFRA ticket. Can you meanwhile update the page? Thank you! Am 2017-01-24 um 19:45 schrieb Hervé BOUTEMY: you don't have edit karma on Confluence? if you need it, please open a Jira issue for INFRA like I did for Christian [1]: we learned that

Re: svn commit: r1779527 - in /maven/plugins/trunk/maven-checkstyle-plugin: ./ src/main/java/org/apache/maven/plugin/ src/main/java/org/apache/maven/plugins/ src/main/java/org/apache/maven/plugins/che

Done On Tue, 24 Jan 2017 20:54:20 +0100, Guillaume Boué wrote: Could the 2.18 version on JIRA be renamed to 3.0.0? I'll close the issue and start looking at all the others we can fix with this upgrade (like MCHECKSTYLE-275 for a start). Guillaume Le 20/01/2017 à

Re: Update Cwiki Roadmap 2017

Hi Michael, When you do, can you ask edit privileges for me as well? That would avoid creating another one. Thanks, Guillaume Le 24/01/2017 à 20:01, Michael Osipov a écrit : No, I don't. Read-only. I will create an INFRA ticket. Can you meanwhile update the page? Thank you! Am 2017-01-24

Re: Update Cwiki Roadmap 2017

Thanks, this is what I was after. Didn't want to fiddle with issues/pages without consent first. Am 2017-01-24 um 20:26 schrieb Stephen Connolly: Well they should show up in the jira table once the issues have been changed to have Fix Version 3.5.0. I can clear out the bits of hard code from

Re: Update Cwiki Roadmap 2017

https://issues.apache.org/jira/browse/INFRA-13388 Am 2017-01-24 um 20:39 schrieb Guillaume Boué: Hi Michael, When you do, can you ask edit privileges for me as well? That would avoid creating another one. Thanks, Guillaume Le 24/01/2017 à 20:01, Michael Osipov a écrit : No, I don't.

Re: Update Cwiki Roadmap 2017

Well they should show up in the jira table once the issues have been changed to have Fix Version 3.5.0. I can clear out the bits of hard code from the wiki page later if Hervé doesn't beat me to it On 24 January 2017 at 19:01, Michael Osipov wrote: > No, I don't. Read-only.

Re: Requesting a single Monorepo enhancement for Maven

i thought about that too, except that in a monorepo situation, I don't want the don't want the changed pom to get pushed back in a commit, and I don't want one of the those changelists in my IDE labeled "do not commit" to facilitate that. Rationale: Just because I've subset my checkout/clone

Always get the false value when calling org.apache.maven.shared.invoker.InvovationRequest.isUpdateSnapshots()

Hello, Using the org.apache.maven.shared.invoker.InvovationRequest leads to get always the false value, even if the "-U" or "--update-snapshots" option is set. InvocationRequest request = new DefaultInvocationRequest(); updateSnapshots = request.isUpdateSnapshots(); Posts

Re: Requesting a single Monorepo enhancement for Maven

Versus profiles, I would rather have pom.xml exhaustively renamed to pom.xml.template in SCM, and a Python script to generate as we have it today (pom.xml marked as .gitignore) before invoking 'maven install' - Paul On Tue, Jan 24, 2017 at 7:31 AM, Stephen Connolly <

Re: [VOTE] Maven Shade Plugin 3.0.0

+1 On Tue, Jan 24, 2017 at 4:34 AM, Olivier Lamy wrote: > Hi > We solved 13 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > version=12331395=Text=12317921=Create > > Staging repo: > https://repository.apache.org/content/repositories/maven-1319/ >

Re: Requesting a single Monorepo enhancement for Maven

It's an interesting idea for model version 5.0.0 to consider. At present, I would handle it by using profiles with activation to pull in the modules: if your activation in the root is based on the presence of the module's pom.xml then it will only add the module if you checked it out: (approx

Re: Requesting a single Monorepo enhancement for Maven

Hi Paul, the problem with the proposals is that it doesn't fit the modelversion 4.0.0 (XSD) However, what I could think of having a module with a protocol and provide an extension which can locate the actual module locations. The extension kicks in at startup while creating the BuildPlan.

Maven Jenkinsfile Job is Gone

Hi friends, the pipeline Jenkinsfile job is gone from Jenkins. Can someone with the appropriate permissions have a look? Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:

Re: [VOTE] Release Apache Maven Artifact Resolver version 1.0.3

+1 Regards, Hervé Le dimanche 22 janvier 2017, 16:41:44 CET Hervé BOUTEMY a écrit : > Hi, > > We solved 1 issue: we renamed Aether to Maven Artifact Resolver, with exact > same code as Aether 1.0.2. > > Staging repo: > https://repository.apache.org/content/repositories/maven-1315/ >

Re: Jenkins Jobs

We probably can delete those jobs. I'll do an inventory and put the proposal the the list On Tue 24 Jan 2017 at 19:43, Karl Heinz Marbaise wrote: > Hi the Jenkins Job: > > > > > https://builds.apache.org/job/maven-master-release-status-test-plugins-windows/36/console > > > >

Re: Update Cwiki Roadmap 2017

done On 24 January 2017 at 19:26, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Well they should show up in the jira table once the issues have been > changed to have Fix Version 3.5.0. I can clear out the bits of hard code > from the wiki page later if Hervé doesn't beat me to it

Re: Update Cwiki Roadmap 2017

you don't have edit karma on Confluence? if you need it, please open a Jira issue for INFRA like I did for Christian [1]: we learned that Confluence is not tied to LDAP yet, then require manual addition of account into maven-committers group. Regards, Hervé [1]

Jenkins Jobs

Hi the Jenkins Job: https://builds.apache.org/job/maven-master-release-status-test-plugins-windows/36/console hangs with Exception in thread "main" java.lang.OutOfMemoryError: PermGen space for a little bit longer time (3 Days ...).. I have aborted that job... Kind regards Karl Heinz

Re: svn commit: r1779527 - in /maven/plugins/trunk/maven-checkstyle-plugin: ./ src/main/java/org/apache/maven/plugin/ src/main/java/org/apache/maven/plugins/ src/main/java/org/apache/maven/plugins/che

Could the 2.18 version on JIRA be renamed to 3.0.0? I'll close the issue and start looking at all the others we can fix with this upgrade (like MCHECKSTYLE-275 for a start). Guillaume Le 20/01/2017 à 16:37, Robert Scholte a écrit : Very nice, another plugin moving forward Robert On Thu,

[GitHub] maven-release pull request #11: MRELEASE-979: Allow VersionPolicies to manag...

GitHub user hgschmie opened a pull request: https://github.com/apache/maven-release/pull/11 MRELEASE-979: Allow VersionPolicies to manage Branch and Tag names Adds a new method to the VersionPolicy interface to allow configuration of Branch and Tag names in a version policy.

Re: Requesting a single Monorepo enhancement for Maven

Thanks Jörg - I'll keep that in mind for a fallback. For a hacky maven3 modification towards Robert's def:.full-module- list.txt I have found: https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/project/MavenProject.java#L1480 It looks like that method can

Re: [VOTE] Release Apache Maven Invoker version 3.0.0 (shared component)

+1 Regards, Hervé Le dimanche 22 janvier 2017, 21:03:31 CET Robert Scholte a écrit : > Hi, > > We solved 9 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922 > rsion=12331463=Text > > There are still a couple of issues left in JIRA: >

Re: Requesting a single Monorepo enhancement for Maven

OK, take a look at https://github.com/paul-hammant/maven-monorepo-experiment/compare/trick-maven-monorepo Branch 1 - vanilla-recursive is a branch with HazelCast's core and samples checked in - a 14 minute build IF YOU SKIP TESTS AND YOU

[GitHub] maven-release pull request #10: [MRELEASE-977] makes the release:branch goal...

Github user hgschmie closed the pull request at: https://github.com/apache/maven-release/pull/10 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

Re: Requesting a single Monorepo enhancement for Maven

Don't mean to derail the discussion, but I am wondering if sparse checkout is the last/biggest problem you have to solve to use maven for your "one bg ass trunk". We are using maven for a monorepo (maybe not as "bg ass" as google's but pretty big nonetheless) for few years now and lack

Re: Requesting a single Monorepo enhancement for Maven

100% agree that teams not using this feature should be able to carry on unchanged. If the likes of JetBrains have to do extra code for the short-hand inside that Robert proposed, then I'm sure they'll agree with me that that is the cost of doing business. And from that they can choose to delay

Re: Maven Jenkinsfile Job is Gone

Shouldn't be 3.x as it will include 5.x when we start that and I was planning a 2.x Jenkinsfile just for completeness and to assist re-checking the integration tests against 2.x On Tue 24 Jan 2017 at 13:34, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Somebody mistakenly renamed

Re: Requesting a single Monorepo enhancement for Maven

Yep I hear you. We cannot change the 4.0.0 schema And changing to a new modelVersion requires ensuring that we can evolve without breaking consumers of the older model. Basically we have one chance to make a "breaking" change to something that allows us to evolve going forward So what I

Re: Maven Jenkinsfile Job is Gone

I recommend filing a ticket with infra On Tue 24 Jan 2017 at 13:11, Michael Osipov wrote: > Hi friends, > > > > the pipeline Jenkinsfile job is gone from Jenkins. Can someone with the > > appropriate permissions have a look? > > > > Michael > > > >

Re: Requesting a single Monorepo enhancement for Maven

Stephen - I think think Robert's def:.full-module-list.txt is compatible hacking that is POM 4 friendly (and 3 for that matter) until you revisit in 5. I'd be horrified to write more XML than I already write in Maven. I'm able to face Gradle advocates re a particular enterprise app and without

Re: Maven Jenkinsfile Job is Gone

Somebody mistakenly renamed it: https://builds.apache.org/job/maven-3.x-jenkinsfile/ On Tue 24 Jan 2017 at 13:25, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > I recommend filing a ticket with infra > > On Tue 24 Jan 2017 at 13:11, Michael Osipov wrote: > >>

Re: Requesting a single Monorepo enhancement for Maven

I don't disagree... but There is tooling that parses the Pom directly and has made assumptions about the modules tag and its structure We would break such tooling with such a seemingly trivial change (I know of at least 5 of my employer's customers who I would be quite upset... any my employer