Re: maven git commit: MNG-5878 added project.directory property to configure module directory when not equals to artifactId

2015-08-26 Thread Dan Tran
Hi Hervé I implemented p4maven the java scm provider for Perforce which stores client info at server side. As long as user follow same artifactId/folder convention, it works great. However most of the time, it is not the case, I have to go thru some hook to get it just barely behave. Great to se

[jira] [Commented] (MNG-5878) Subversion SCM module URLs incorrectly build when module name != artifactId

2015-08-26 Thread Jason van Zyl (JIRA)
[ https://issues.apache.org/jira/browse/MNG-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715970#comment-14715970 ] Jason van Zyl commented on MNG-5878: Seems perfectly reasonable. > Subversion SCM modul

Re: maven git commit: MNG-5878 added project.directory property to configure module directory when not equals to artifactId

2015-08-26 Thread Hervé BOUTEMY
it is currently not merged to master, just in a MNG-5878 branch for review: for such a code change, I chose Review Then Commit process (instead of our classical Commit Then Review) But I'm happy that you are interested For years, I heard many people (I can name a few I know personnally :) ) who

Re: Account on issues.apache.org/jira

2015-08-26 Thread Hervé BOUTEMY
ok, I gave a first answer on infrastructure@a.o, since this is the best place and for quick summary here, since that can be useful for others, this is a bug in Jira account deduplication when we migrated Maven Jira projets from Codehaus to ASF (INFRA-9116) There is no hijack associated Regards

Re: maven git commit: MNG-5878 added project.directory property to configure module directory when not equals to artifactId

2015-08-26 Thread Dan Tran
Very excited to see how I can use this property. Good stuff Thanks -Dan On Wed, Aug 26, 2015 at 1:50 PM, Hervé BOUTEMY wrote: > I think I have found a way to support module directory in SCM & site that > is > not artifactId > AFAIK, it's a long awaited feature that was until now feared to wre

Re: [jira] [Moved] (MNG-5878) Subversion SCM module URLs incorrectly build when module name != artifactId

2015-08-26 Thread Hervé BOUTEMY
Le jeudi 27 août 2015 06:36:09 Barrie Treloar a écrit : > On 27 August 2015 at 05:02, Hervé Boutemy (JIRA) wrote: > > > Say you have this project structure: > > > {noformat} > > > / > > > > > > |-- module1 > > > |-- module2 > > > > > > {noformat} > > > and artifactIds are named: > > > {nofor

Re: Account on issues.apache.org/jira

2015-08-26 Thread Norbert Wnuk
My account was assigned to someone else, decided to sent an email to infrastruct...@apache.org to clarify this situation. NW On Thu, Aug 27, 2015 at 1:22 AM, Martin Gainty wrote: > Norbert > > what is a *non-standard problem* > > ? > Martin > > > > From: norbertw...@gmail.com > > Date: Wed, 26

RE: Account on issues.apache.org/jira

2015-08-26 Thread Martin Gainty
Norbert what is a *non-standard problem* ? Martin > From: norbertw...@gmail.com > Date: Wed, 26 Aug 2015 19:02:39 +0200 > Subject: Account on issues.apache.org/jira > To: dev@maven.apache.org > > Hi, > What is the email address to report (non standard) problems with the JIRA > account? > > R

Re: [jira] [Moved] (MNG-5878) Subversion SCM module URLs incorrectly build when module name != artifactId

2015-08-26 Thread Barrie Treloar
On 27 August 2015 at 05:02, Hervé Boutemy (JIRA) wrote: > > > Say you have this project structure: > > {noformat} > > / > > |-- module1 > > |-- module2 > > {noformat} > > and artifactIds are named: > > {noformat} > > my-parent > > |-- my-module1 > > |-- my-module2 > > {noformat} > > Prefi

Re: maven git commit: MNG-5878 added project.directory property to configure module directory when not equals to artifactId

2015-08-26 Thread Hervé BOUTEMY
I think I have found a way to support module directory in SCM & site that is not artifactId AFAIK, it's a long awaited feature that was until now feared to wreck havock please review and tell what you think about it Regards, Hervé Le mercredi 26 août 2015 20:26:37 hbout...@apache.org a écrit :

[jira] [Commented] (MNG-5878) Subversion SCM module URLs incorrectly build when module name != artifactId

2015-08-26 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715455#comment-14715455 ] Hervé Boutemy commented on MNG-5878: feature added in branch [812e1e9d|http://git-wip-u

Re: [VOTE] Release Apache Maven Enforcer version 1.4.1

2015-08-26 Thread Hervé BOUTEMY
+1 Regards, Hervé Le dimanche 23 août 2015 21:57:25 Karl Heinz Marbaise a écrit : > Hi, > > We solved 10 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&ve > rsion=12330766 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira

Re: [VOTE] Release Apache Maven Enforcer version 1.4.1

2015-08-26 Thread Karl Heinz Marbaise
Hi, here is my +1... someone else ? Kind regards Karl Heinz Marbaise On 8/23/15 9:57 PM, Karl Heinz Marbaise wrote: Hi, We solved 10 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&version=12330766 There are still a couple of issues left in JIRA: https://is

Account on issues.apache.org/jira

2015-08-26 Thread Norbert Wnuk
Hi, What is the email address to report (non standard) problems with the JIRA account? Regards, NW

Re: Writing poms from mojos

2015-08-26 Thread Barrie Treloar
On 26 August 2015 at 20:41, Robert Scholte wrote: > depending on what you want, maybe flattened-maven-plugin[1] can come to > the rescue. I need the mojo I am hacking to rewrite the pom's to bend to my will. I'm probably a week away from having a working git magic plugin working.

Re: Writing poms from mojos

2015-08-26 Thread Robert Scholte
depending on what you want, maybe flattened-maven-plugin[1] can come to the rescue. [1] http://www.mojohaus.org/flatten-maven-plugin/ Op Wed, 26 Aug 2015 13:07:14 +0200 schreef Barrie Treloar : On 26 August 2015 at 20:10, Robert Scholte wrote: I still have this wish to replace the JD

Re: Writing poms from mojos

2015-08-26 Thread Barrie Treloar
On 26 August 2015 at 20:10, Robert Scholte wrote: > I still have this wish to replace the JDom implementation with Woodstox, > so all kinds of dirty tricks can be removed. > I would gamble on that approach. I can't wait :) My itch is already burning so I'll live with the damned version now. I

Re: Writing poms from mojos

2015-08-26 Thread Robert Scholte
I still have this wish to replace the JDom implementation with Woodstox, so all kinds of dirty tricks can be removed. I would gamble on that approach. Robert Op Wed, 26 Aug 2015 09:40:09 +0200 schreef Barrie Treloar : The release plugin has AbstractRewritePomsPhase which uses a lot of pr

Writing poms from mojos

2015-08-26 Thread Barrie Treloar
The release plugin has AbstractRewritePomsPhase which uses a lot of private methods to do its work. Is there a more utilitarian way of writing a pom? I really only need to fiddle with a couple of values in an existing pom (keeping whitespaces/formatting/etc) and re-write it.