from:"Justin Georgeson"

RE: [EXTERNAL] Anything in pipeline to add functionality to read pom in different formats?

2018-02-01 Thread Justin Georgeson

Polyglot

https://github.com/takari/polyglot-maven

-Original Message-
From: ahardy42 [mailto:adam.ha...@cyberspaceroad.com] 
Sent: Thursday, February 1, 2018 7:48 AM
To: users@maven.apache.org
Subject: [EXTERNAL] Anything in pipeline to add functionality to read pom in 
different formats?

External Sender: Use caution with links/attachments.

Hi All,

as a loyal maven user I appreciate maven for all it does and give kudos to all 
the people who helped build it. Thought I'd say that before I ask my question 
in case you think I'm trolling.

My main problem with maven is colleagues. I constantly hear complaints about 
maven being horrible. Instead of being bothered or dis-inhibiting themselves 
from seeing maven as it should be seen, they say "because it is XML".

Sometimes I think they'd rather use ant or shell script to do their builds, or 
just go with gradle or ivy because someone cool mentioned them.

This leads me naturally to ask, does anyone have any plans to write a maven pom 
reader that can read YAML or even JSON or any other potential non-XML format?

Regards
Adam

--
Sent from: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__maven.40175.n5.nabble.com_Maven-2DUsers-2Df40176.html=DwICAg=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=IaG729QyGh1osYCbh8OX9axItHyepxef_hVPx52Ly1s=jM-l04HsToIfE-yPhEH1XJ69p3svOqXuFAZLeM8yi90=yu7fdEYAqVIT3XiSchebnpkJt6Dyi3Bp_VrX-9y9y2g=

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] Re: how to use both buildnumber-maven-plugin and maven-release-plugin

2017-10-24 Thread Justin Georgeson

> -Original Message-
> From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
> Sent: Tuesday, October 24, 2017 12:25 PM
> To: Justin Georgeson <justin.george...@halliburton.com>;
> i...@soebes.de; Maven Users List <users@maven.apache.org>
> Subject: Re: [EXTERNAL] Re: how to use both buildnumber-maven-plugin
> and maven-release-plugin
> 
> External Sender: Use caution with links/attachments.
> 
> 
> 
> Hi,
> 
> On 24/10/17 15:59, Justin Georgeson wrote:
> > I want to enforce in every build (not just release builds)
>  > that the working copy is pristine
>  >
> (ie doCheck=true for buildnumber plugin),
> 
> On a CI server or locally ?

It is enabled globally in the parent POM, as during transition from older Ant 
builds to Maven it has helped remind developers to do things like use resource 
filtering from source folder to build output folder rather than modifying in 
place (whether that be for source code or unit test resources) and also reduced 
pushing incomplete changes forgetting to include some of the modified files. 
I'm guessing this default setting will be the key distinction why people are 
confused how I'm having an issue with the combination.

> > but release:prepare dirties the working copy before running 'clean verify'.
> 
> Of course it does cause it changes the pom files to represent the correct
> version...and commit this state of the change back to version control...

My impression had been that the release plugin was invoking goals from the tag 
that it creates, rather than from a dirty working copy, for guaranteed 
reproducible results. I can see why that would be undesirable for centralized 
VCS like subversion though. 

> > So when I run release:prepare the buildnumber plugin fails. I can work
> > around it by running 'mvn release:prepare
>  >  -Darguments="-Dmaven.buildNumber.doCheck=false"' but that just
> seems hacky, so I was curious if there's a better way.
> 
> 
> You know about the release:prepare goal what it is exactly doing ?
> 
> https://urldefense.proofpoint.com/v2/url?u=http-
> 3A__maven.apache.org_maven-2Drelease_maven-2Drelease-
> 2Dplugin_examples_prepare-
> 2Drelease.html=DwICaQ=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=IaG729QyGh1osYCbh8OX9axItHyepxef_h
> VPx52Ly1s=WiG6vQ6aiVWMFCcORnOeArhgldg_TZF7xNV8d1YlECI=4f-
> Z8rl_qNhiUE4vBGA0mqAkY7Gb2rBntNqcUT9JwsE=

Clearly I didn't know _exactly_ what it was doing :) Most of our internal Maven 
usage has been for the Eclipse Tycho plugins thus far, and that's just not 
really compatible with maven-release-plugin so there's some technical debt I'm 
trying to get rid of to make our parent POMs more friendly to pure maven 
projects.

> Maybe I misunderstand your question but it sounds like you are trying to
> resolve a thing which has been solved by maven-release-plugin already?...

I just wanted opinions on the cleanest way to configure the two to work 
together. I still need buildnumber-maven-plugin to run during the release 
build. I now know I have to disable its check when preparing a release. 

If I set project.properties.maven.buildNumber.doCheck to true (instead of 
setting it to doCheck true in the plugin ), then have a profile 
that activates on present of maven-release-plugin temporary files and sets the 
property to false (like in example POM [1], corp proxy blocks pastebin), then 
the release:prepare and release:perform goals seem work without having to 
specify any extra -D command-line arguments and with the added benefit that 
developers should then be able to also set maven.buildNumber.doCheck to false 
in their settings.xml if they want to. Is there a better activation rule (than 
what's in the example POM [1)?

[1] https://paste.ee/p/tKYyh

> Kind regards
> Karl Heinz Marbaise
> 
> >
> > Looks like if I configure a default property value for
> maven.buildNumber.doCheck to true, then I can have a profile activate
> when file https://urldefense.proofpoint.com/v2/url?u=http-
> 3A__release.properties=DwICaQ=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=IaG729QyGh1osYCbh8OX9axItHyepxef_h
> VPx52Ly1s=WiG6vQ6aiVWMFCcORnOeArhgldg_TZF7xNV8d1YlECI=DzY
> 1956dm73empQx_us9QzZ5BL5yahhbKcjGLKyMT80= exists to set the
> doCheck property to false, and that gets me through release:prepare. Any
> pitfalls I might be walking into with something like that?
> >
> > -Original Message-
> > From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
> > Sent: Tuesday, October 24, 2017 4:30 AM
> > To: Maven Users List <users@maven.apache.org>; Justin Georgeson
> > <justin.george...@halliburton.com>
> > Subject: [EXTERNAL] Re: how to use both buildnumber-maven-plugin and
> > maven-release-plugin
> >
> > External Sender: Use caution with li

RE: [EXTERNAL] Re: how to use both buildnumber-maven-plugin and maven-release-plugin

2017-10-24 Thread Justin Georgeson

I want to enforce in every build (not just release builds) that the working 
copy is pristine (ie doCheck=true for buildnumber plugin), but release:prepare 
dirties the working copy before running 'clean verify'. So when I run 
release:prepare the buildnumber plugin fails. I can work around it by running 
'mvn release:prepare -Darguments="-Dmaven.buildNumber.doCheck=false"' but that 
just seems hacky, so I was curious if there's a better way. 

Looks like if I configure a default property value for 
maven.buildNumber.doCheck to true, then I can have a profile activate when file 
release.properties exists to set the doCheck property to false, and that gets 
me through release:prepare. Any pitfalls I might be walking into with something 
like that?

-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] 
Sent: Tuesday, October 24, 2017 4:30 AM
To: Maven Users List <users@maven.apache.org>; Justin Georgeson 
<justin.george...@halliburton.com>
Subject: [EXTERNAL] Re: how to use both buildnumber-maven-plugin and 
maven-release-plugin

External Sender: Use caution with links/attachments.



Hi,

the question is what the real problem is?

Can you have an example project which shows the problem? Or can you describe 
more in detail what exactly does not work or not work like you expect it..

Kind regards
Karl Heinz Marbaise

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

how to use both buildnumber-maven-plugin and maven-release-plugin

2017-10-23 Thread Justin Georgeson

The 'clean verify' invoked by release:prepare fails in buildnumber-maven-plugin 
because pom.xml is modified. I can pass arguments to release:prepare have 
buildnumber-maven-plugin skip the check for modifications, but that check is 
one of the main motivations for using it in the first place. What are other 
people doing here?

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

dependencies of plugins and pluginRepositories

2017-10-20 Thread Justin Georgeson

I'm sure this has been discussed before but I could only find this thread from 
2011 with no replies.

https://www.mail-archive.com/users@maven.apache.org/msg118612.html

I had expected that build.plugins.plugin.dependencies would be resolved from 
pluginRepositories, so I have some jars published to a repository which is only 
configured as a pluginRepository, and the plugin execution that depends on 
those jars is failing because it can't resolve them.

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

RE: Maven properties passed to external ant build file

2017-08-18 Thread Justin Georgeson

Looks like if I use nested  elements inside the  call it's 
working. Which is contrary to the maven-antrun-plugin 'Using Maven properties' 
section at http://maven.apache.org/plugins/maven-antrun-plugin/usage.html. Will 
try to reduce and example project and file a bug report. 

> -Original Message-
> From: Justin Georgeson [mailto:justin.george...@halliburton.com]
> Sent: Thursday, August 17, 2017 5:31 PM
> To: Maven Users List (users@maven.apache.org) <users@maven.apache.org>
> Subject: [EXTERNAL] Maven properties passed to external ant build file
> 
> External Sender: Use caution with links/attachments.
> 
> 
> 
> I'm using maven-antrun-plugin to execute targets in an external Ant build 
> file,
> and having an issue with inherited properties.
> 
>   
>   ${skipIvyPublish}
>   
>   https://urldefense.proofpoint.com/v2/url?u=http-3A__-
> 257Bivy.publish.re=DwIFAg=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=IaG729QyGh1osYCbh8OX9axItHyepxef_hVPx
> 52Ly1s=jU_eveXMV4xr4ZGmOAYbmZOCgFUHd7iG3lp8h1UpgFM=qcSKdeR
> 57hGmNWmb6d94uy2ZGp25vlzkIPW0iNOqLec= solver}"/>
>value="$https://urldefense.proofpoint.com/v2/url?u=http-3A__-
> 257Bivy.publish.re=DwIFAg=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=IaG729QyGh1osYCbh8OX9axItHyepxef_hVPx
> 52Ly1s=jU_eveXMV4xr4ZGmOAYbmZOCgFUHd7iG3lp8h1UpgFM=qcSKdeR
> 57hGmNWmb6d94uy2ZGp25vlzkIPW0iNOqLec= solver}"/>
>   https://urldefense.proofpoint.com/v2/url?u=http-3A__-
> 257Bivy.publish.re=DwIFAg=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=IaG729QyGh1osYCbh8OX9axItHyepxef_hVPx
> 52Ly1s=jU_eveXMV4xr4ZGmOAYbmZOCgFUHd7iG3lp8h1UpgFM=qcSKdeR
> 57hGmNWmb6d94uy2ZGp25vlzkIPW0iNOqLec= solver}"/>
>antfile="$https://urldefense.proofpoint.com/v2/url?u=http-3A__-
> 257Bivy.de=DwIFAg=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=IaG729QyGh1osYCbh8OX9axItHyepxef_hVPx
> 52Ly1s=jU_eveXMV4xr4ZGmOAYbmZOCgFUHd7iG3lp8h1UpgFM=j3u9bKQ
> hroNEpQCKrkkRTG5sUpsX2RER9LLvM-V1yiQ= pendencies.dir}/ivy-build.xml"
>   target="ivy.publish"
>   inheritAll="true"
>   inheritRefs="true"/>
>   
>   
> 
> As you might guess from the above, I have a property in my pom.xml named
> ivy.publish.resolver. The two echo lines here show the correct value (either 
> the
> default from my pom.xml or what I supply to Maven with 
> -Divy.publish.resolver).
> But within the ivy-build.xml the very first task executed (the init: target 
> in the
> output below) is the same echo statement, and inevitably the property value is
> always the default from pom.xml, ignoring what I've set with -D command-line
> argument.
> 
> [INFO] --- maven-antrun-plugin:1.8:run (ivy-publish) @ maven-ivy-example 
> ---
> [INFO] Executing tasks
> 
> ivy.publish:
>  [echo] resolver: fred
>  [echo] resolver: fred
> 
> init:
>  [echo] resolver: published.local
> 
> Any suggestions?
> 
> --
> This e-mail, including any attached files, may contain confidential and 
> privileged
> information for the sole use of the intended recipient.  Any review, use,
> distribution, or disclosure by others is strictly prohibited.  If you are not 
> the
> intended recipient (or authorized to receive information for the intended
> recipient), please contact the sender by reply e-mail and delete all copies 
> of this
> message.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven properties passed to external ant build file

2017-08-17 Thread Justin Georgeson

I'm using maven-antrun-plugin to execute targets in an external Ant build file, 
and having an issue with inherited properties.

  
  ${skipIvyPublish}
  
  
  
  
  
  
  

As you might guess from the above, I have a property in my pom.xml named 
ivy.publish.resolver. The two echo lines here show the correct value (either 
the default from my pom.xml or what I supply to Maven with 
-Divy.publish.resolver). But within the ivy-build.xml the very first task 
executed (the init: target in the output below) is the same echo statement, and 
inevitably the property value is always the default from pom.xml, ignoring what 
I've set with -D command-line argument. 

[INFO] --- maven-antrun-plugin:1.8:run (ivy-publish) @ maven-ivy-example ---
[INFO] Executing tasks

ivy.publish:
 [echo] resolver: fred
 [echo] resolver: fred

init:
 [echo] resolver: published.local

Any suggestions?

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] Re: project.basedir in file-based profile activation

2017-06-23 Thread Justin Georgeson



> -Original Message-
> From: Jörg Schaible [mailto:joerg.schai...@bpm-inspire.com]
> Sent: Friday, June 23, 2017 1:03 AM
> To: users@maven.apache.org
> Subject: [EXTERNAL] Re: project.basedir in file-based profile activation
> 
> External Sender: Use caution with links/attachments.
> 
> 
> 
> Justin Georgeson wrote:
> 
> > With 3.3.9 and 3.5.0 When I use this
> >
> >   
> > 
> >   my-profile-id
> >   
> > 
> >   ${project.basedir}${file.separator}somefile.txt
> > 
> >   
> >   
> > 
> >   
> >
> > I see this warning
> >
> > [WARNING] Some problems were encountered while building the effective
> > [model for com.example:basedir:jar:1.0-SNAPSHOT WARNING]
> > ['profiles.profile[my-profile-id].activation.file.exists' Failed to
> > [interpolate file location
> > ${project.basedir}${file.separator}somefile.txt
> > [for profile jacoco-read-manifest: ${project.basedir} expression not
> > [supported during profile activation, use ${basedir} instead
> >
> > I was under the impression that ${basedir} is deprecated in favor of
> > ${project.basedir}, many years ago at that.
> 
> That won't help, because string substitution did not happen yet at the time
> profiles are activated. There's only a special support for ${user.home} and
> ${env.HOME}, but that's it. Anything else cannot not work.

So it's a bad message in that the problem is having used a property at all, 
rather than having used that specific property?

> > Side note, is it actually worthwhile to use ${file.separator} like
> > this, or is that generally only useful when you're outputting stuff to
> > the user and want it to look pretty?
> 
> Use normal slashes.
> 
> Cheers,
> Jörg
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org


--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

project.basedir in file-based profile activation

2017-06-22 Thread Justin Georgeson

With 3.3.9 and 3.5.0 When I use this

  

  my-profile-id
  

  ${project.basedir}${file.separator}somefile.txt

  
  

  

I see this warning

[WARNING] Some problems were encountered while building the effective model for 
com.example:basedir:jar:1.0-SNAPSHOT
[WARNING] 'profiles.profile[my-profile-id].activation.file.exists' Failed to 
interpolate file location ${project.basedir}${file.separator}somefile.txt for 
profile jacoco-read-manifest: ${project.basedir} expression not supported 
during profile activation, use ${basedir} instead

I was under the impression that ${basedir} is deprecated in favor of 
${project.basedir}, many years ago at that.

Side note, is it actually worthwhile to use ${file.separator} like this, or is 
that generally only useful when you're outputting stuff to the user and want it 
to look pretty? 

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Follow up: Building projects for multiple platforms

2017-06-16 Thread Justin Georgeson

Instead of tweaking the version, I would configure an executions of the 
compiler plugins compile and testcompile goals to a separate output folders, 
like ${build.directory}${file.separator}classes-java7 and 
${build.directory}${file.separator}test-classes-java7 and then an execution of 
the jar plugin to create/attach a jar with classifier set to 'java7'.

https://maven.apache.org/plugins/maven-jar-plugin/examples/attached-jar.html

That way you can have both versions build/deploy together in one pipeline with 
the same version. 

You can use properties in the version if you use Maven 3.5 with some other 
tricks, there was a recent thread on the list about it

http://www.mail-archive.com/users@maven.apache.org/msg139475.html


> -Original Message-
> From: Christofer Dutz [mailto:christofer.d...@c-ware.de]
> Sent: Friday, June 16, 2017 3:54 AM
> To: Maven List 
> Subject: [EXTERNAL] Follow up: Building projects for multiple platforms
> 
> External Sender: Use caution with links/attachments.
> 
> 
> 
> Hi,
> 
> A short follow up question regarding my last one.
> In the Edgent maven build, which I am working on, we need to produce java8,
> java7 and android versions of jars. This is done by running the retrolambda-
> maven-plugin on the classes when building the java7 version. To make the
> dependency resolution work correctly with all variants we decided to use the
> normal version number for the java8 output and add a suffix of “–java7” to the
> version in case of a java7 build (for SNAPSHOT versions the “-java7” is 
> included
> between the version and the “SNAPSHOT”). In order to be able to switch the
> versions by selecting profiles, I used variables for the artifact versions.
> As I know variables for versions of parent poms is a really bad idea (Don’t 
> even
> know if it works), I setup the project to have constant versions in the parent
> poms and only use these for configuring the reactor and the plugins – no
> dependencies are handled here. The build is working nicey, unfortunately the
> build is outputting hundreds of warnings like this:
> 
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.edgent.analytics:edgent-analytics-sensors:jar:1.2.0-SNAPSHOT
> [WARNING] 'version' contains an expression but should be a constant. @
> org.apache.edgent.analytics:edgent-analytics-sensors:${edgent.version},
> /Users/christoferdutz/Projects/Apache/Edgent/incubator-
> edgent/analytics/sensors/pom.xml, line 31, column 12
> 
> Is there a “maven way” (TM) to achieve this sort of thing without the 
> warnings?
> 
> Chris

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

2017-05-04 Thread Justin Georgeson

Yup :)

-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] 
Sent: Thursday, May 4, 2017 4:52 PM
To: Justin Georgeson <jgeorge...@lgc.com>; Maven Users List 
<users@maven.apache.org>; i...@soebes.de
Subject: Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

External Sender: Use caution with links/attachments.



Hi,

On 04/05/17 22:52, Justin Georgeson wrote:
> Also I believe the partial reactor switches don't work for Tycho builds.

You mean -pl ..option I suppose?

As far as I know Tycho is handling that at the wrong time of the maven build 
and furthermore handles in this relationship some other things wrong which 
results in not working things like this..

Kind regards
Karl Heinz Marbaise

>
> -Original Message-
> From: Robert Patrick [mailto:robert.patr...@oracle.com]
> Sent: Thursday, May 4, 2017 3:18 PM
> To: Maven Users List <users@maven.apache.org>; i...@soebes.de
> Subject: [EXTERNAL] RE: Continuous Delivery with Maven now possible?
>
> External Sender: Use caution with links/attachments.
>
>
>
> Hard to train developers to break old habits but thanks... :-)
>
>
>
> -Original Message-
> From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
> Sent: Thursday, May 04, 2017 3:16 PM
> To: Robert Patrick; Maven Users List; i...@soebes.de
> Subject: Re: Continuous Delivery with Maven now possible?
>
> Hi Robert,
>
> Ah now I see the issue.
>
> If you have a multi module build you should use
>
> mvn -pl moduleToBuild clean install
>
> but from root location and don't change into the module directory cause this 
> can't work like this.
>
> Kind regards
> Karl Heinz Marbaise
>
> On 04/05/17 22:08, Robert Patrick wrote:
>> Hi Karl,
>>
>> If I define the revision property in the top-level POM, I cannot refer to it 
>> in the module POMs'  elements *and* still retain the ability to 
>> build from the module directory, right?  I tried this and it failed because 
>> it was unable to resolve the revision property variable.
>>
>> C:\rpatrick\work\projects\jcs-las\util>mvn clean install [INFO] 
>> Scanning for projects...
>> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
>> [FATAL] Non-resolvable parent POM for 
>> oracle.jcs.lifecycle:util:[unknown-version
>> ]: Failure to find oracle.jcs.lifecycle:app-to-cloud:pom:${revision}
>> in
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__a=DwIDaQ=RoP1
>> Y 
>> umCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBG
>> r 
>> _pt_OzwdxJosG0=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=by9uci
>> i pxSZU0-Wn16t7grG7a5Djk4ZH9440pGIayRE=
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__rtifactory-2Dslc.
>> o 
>> raclecorp.com_artifactory_repo1=DwIFaQ=PskvixtEUDK7wuWU-tIg6oKuGY
>> B 
>> RbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=mQrJ
>> O
>> CEKXlLF5VNECH6aqvyAu4kATrZgYUsiitvnfwY=oPO-3-7EEwzSMAr8-re0YxZdReMu
>> 1 5_A4OMXDtdtFyA=  was cached in the local reposito ry, resolution 
>> will not be reattempted until the update interval of repo1 has el apsed or 
>> updates are forced and 'parent.relativePath' points at wrong local POM @ 
>> line 7, column 13  @ [ERROR] The build could not read 1 project -> [Help 1] 
>> [ERROR]
>> [ERROR]   The project oracle.jcs.lifecycle:util:[unknown-version] 
>> (C:\rpatrick\w
>> ork\projects\jcs-las\util\pom.xml) has 1 error
>> [ERROR] Non-resolvable parent POM for 
>> oracle.jcs.lifecycle:util:[unknown-ver
>> sion]: Failure to find
>> oracle.jcs.lifecycle:app-to-cloud:pom:${revision} in http
>> ://artifactory-slc.oraclecorp.com/artifactory/repo1 was cached in the 
>> local repo sitory, resolution will not be reattempted until the 
>> update interval of repo1 ha s elapsed or updates are forced and 
>> 'parent.relativePath' points at wrong local POM @ line 7, column 13 
>> -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the 
>> errors, re-run Maven with the -e swit ch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions, 
>> please rea d the following articles:
>> [ERROR] [Help 1]
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__cwiki.apache.org_
>> c
>> onfluence_display_MAVEN_ProjectBuildin=DwIDaQ=RoP1YumCXCgaWHvlZYR
>> 8 
>> PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBGr_pt_OzwdxJosG0
>> & 
>> m=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=Gpqh8tXn87EJPGvORYVRo
>> H
>> s2ncTiyaZSJWc3AEyEsUQ=
&g

RE: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

2017-05-04 Thread Justin Georgeson

Also I believe the partial reactor switches don't work for Tycho builds.

-Original Message-
From: Robert Patrick [mailto:robert.patr...@oracle.com] 
Sent: Thursday, May 4, 2017 3:18 PM
To: Maven Users List ; i...@soebes.de
Subject: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

External Sender: Use caution with links/attachments.



Hard to train developers to break old habits but thanks... :-)



-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
Sent: Thursday, May 04, 2017 3:16 PM
To: Robert Patrick; Maven Users List; i...@soebes.de
Subject: Re: Continuous Delivery with Maven now possible?

Hi Robert,

Ah now I see the issue.

If you have a multi module build you should use

mvn -pl moduleToBuild clean install

but from root location and don't change into the module directory cause this 
can't work like this.

Kind regards
Karl Heinz Marbaise

On 04/05/17 22:08, Robert Patrick wrote:
> Hi Karl,
>
> If I define the revision property in the top-level POM, I cannot refer to it 
> in the module POMs'  elements *and* still retain the ability to build 
> from the module directory, right?  I tried this and it failed because it was 
> unable to resolve the revision property variable.
>
> C:\rpatrick\work\projects\jcs-las\util>mvn clean install [INFO] 
> Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for
> oracle.jcs.lifecycle:util:[unknown-version
> ]: Failure to find oracle.jcs.lifecycle:app-to-cloud:pom:${revision}
> in
> https://urldefense.proofpoint.com/v2/url?u=http-3A__a=DwIDaQ=RoP1Y
> umCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBGr
> _pt_OzwdxJosG0=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=by9ucii
> pxSZU0-Wn16t7grG7a5Djk4ZH9440pGIayRE=
> https://urldefense.proofpoint.com/v2/url?u=http-3A__rtifactory-2Dslc.o
> raclecorp.com_artifactory_repo1=DwIFaQ=PskvixtEUDK7wuWU-tIg6oKuGYB
> RbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=mQrJO
> CEKXlLF5VNECH6aqvyAu4kATrZgYUsiitvnfwY=oPO-3-7EEwzSMAr8-re0YxZdReMu1
> 5_A4OMXDtdtFyA=  was cached in the local reposito ry, resolution will not 
> be reattempted until the update interval of repo1 has el apsed or updates are 
> forced and 'parent.relativePath' points at wrong local POM @ line 7, column 
> 13  @ [ERROR] The build could not read 1 project -> [Help 1] [ERROR]
> [ERROR]   The project oracle.jcs.lifecycle:util:[unknown-version] 
> (C:\rpatrick\w
> ork\projects\jcs-las\util\pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM for 
> oracle.jcs.lifecycle:util:[unknown-ver
> sion]: Failure to find
> oracle.jcs.lifecycle:app-to-cloud:pom:${revision} in http
> ://artifactory-slc.oraclecorp.com/artifactory/repo1 was cached in the 
> local repo sitory, resolution will not be reattempted until the update 
> interval of repo1 ha s elapsed or updates are forced and 
> 'parent.relativePath' points at wrong local POM @ line 7, column 13 -> 
> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, 
> re-run Maven with the -e swit ch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, 
> please rea d the following articles:
> [ERROR] [Help 1]
> https://urldefense.proofpoint.com/v2/url?u=http-3A__cwiki.apache.org_c
> onfluence_display_MAVEN_ProjectBuildin=DwIDaQ=RoP1YumCXCgaWHvlZYR8
> PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBGr_pt_OzwdxJosG0&
> m=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=Gpqh8tXn87EJPGvORYVRoH
> s2ncTiyaZSJWc3AEyEsUQ=
> gException
> [ERROR] [Help 2]
> https://urldefense.proofpoint.com/v2/url?u=http-3A__cwiki.apache.org_c
> onfluence_display_MAVEN_UnresolvableMo=DwIDaQ=RoP1YumCXCgaWHvlZYR8
> PQcxBKCX5YTpkKY057SbK10=Ql5uwmbofQMW0iErugdCnFgO-CBGr_pt_OzwdxJosG0&
> m=3nZZwc0AT7pfHVI5gfXOLR0kIk5Pd5HKhazn6HJu6HY=kjqcy_wD0H5qwfISMGTZrq
> XoHWM-jV5GAbTtEvug-bc=
> delException
>
>
> Did I miss something?
>
> Thanks,
> Robert
>
> -Original Message-
> From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
> Sent: Thursday, May 04, 2017 3:02 PM
> To: Maven Users List
> Subject: Re: Continuous Delivery with Maven now possible?
>
> Hi Robert,
>
>
> On 04/05/17 21:55, Robert Patrick wrote:
>
>> With 3.5, you can now use a variable *but* that variable
>  > has to be accessible to the POM prior to finding its  > parent so 
> the only solution is to move the  >  version number outside the POM 
> hierarchy and into a -D defined
>> variable.
>
> Which is not true. You can define the property inside the pom file if you 
> like and can overwrite the version via command line (-Drevision=...).
>
>
>
>  > While this works, it seems to have some undesirable  > aspects to 
> it.  In my opinion, it would be better if  > Maven could find a way to 
> resolve this issue  > without resorting to -Ds to specify the  > value 
> of the variable.
>  > I am

RE: [EXTERNAL] Re: Any way to change the color scheme in Maven 3.5.0?

2017-04-12 Thread Justin Georgeson

I vote for a help plugin goal, like help:color-style. It could show a brief 
summary and how to customize, list available settings, and print active 
settings.

-Original Message-
From: Hervé BOUTEMY [mailto:herve.bout...@free.fr] 
Sent: Tuesday, April 11, 2017 8:10 PM
To: Maven Users List 
Subject: [EXTERNAL] Re: Any way to change the color scheme in Maven 3.5.0?

External Sender: Use caution with links/attachments.



the big question for me is: how to make that list available? A new CLI option?
A new goal in a plugin? which one? help? other ideas?

Once we know where to put the feature, the content can be reworked adapted to 
the context

Regards,

Hervé

Le mardi 11 avril 2017, 21:35:19 CEST Robert Scholte a écrit :
> I still wonder if we want to have this.
> It is less interesting which colors are used, but instead more 
> interesting the colors you want.
> So having a list with the available options would be good enough for me.
>
> Robert
>
> On Tue, 11 Apr 2017 00:42:15 +0200, Hervé BOUTEMY 
>  ree.fr=DwIFAw=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3
> PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=2L1RhrmrIqeZgpxGINVHucet-6gs3s
> qlQV0EAtYNCEw=nYBx902DpsALmMqWPOBqbilCAvKsThvCi1wMNZvOomE= >
>
> wrote:
> > there is no feature now to dump effective config as text: didn't 
> > think at this scenario
> >
> > PRs welcome or at least ideas on where to add this feature to make 
> > it usable
> >
> > Regards,
> >
> > Hervé
> >
> > Le lundi 10 avril 2017, 07:35:49 CEST Francesco ChicchiriccÃ² a écrit :
> >> On 2017-04-10 09:16 (+0200), Karl Heinz Marbaise 
> >> 
> >>
> >> wrote:
> >> > Hi,
> >> >
> >> > On 10/04/17 09:11, Francesco Chicchiriccï¿½ wrote:
> >> > > On 2017-04-10 08:58 (+0200), Karl Heinz Marbaise 
> >> > > 
> >
> > wrote:
> >> > >> Hi,
> >> > >>
> >> > >> On 10/04/17 08:45, Francesco ChicchiriccÃ² wrote:
> >> > >>> Thanks HervÃ©,
> >> > >>> appending
> >> > >>>
> >> > >>> -Dstyle.success=green
> >> > >>>
> >> > >>> to my MAVEN_OPTS did the trick.
> >> > >>>
> >> > >>> Is there any place where defaults for all styles (debug, 
> >> > >>> info, warning, error, success, warning, failure, strong, mojo 
> >> > >>> and
> >>
> >> project)
> >>
> >> > >>> are reported? Thanks!> >>
> >> > >>
> >> > >> Yes if you do a mvn -X clean:
> >> > >> ...
> >> > >>
> >> > >> [DEBUG]   Imported: org.slf4j.helpers.* 
> >> > >>  >> > >>  > >> > >> [DEBUG]   Imported: org.slf4j.spi.* 
> >> > >>  >> > >>  > >> > >> [DEBUG] Populating class realm maven.api
> >> > >> [INFO] Error stacktraces are turned on.
> >> > >> [DEBUG] Message scheme: color
> >> > >> [DEBUG] Message styles: debug info warning error success 
> >> > >> failure
> >>
> >> strong
> >>
> >> > >> mojo project
> >> > >> [DEBUG] Reading global settings from
> >>
> >> /usr/local/maven/conf/settings.xml
> >>
> >> > >> [DEBUG] Reading user settings from 
> >> > >> /Users/kama/.m2/settings.xml [DEBUG] Reading global toolchains 
> >> > >> from /usr/local/maven/conf/toolchains.xml
> >> > >> [DEBUG] Reading user toolchains from 
> >> > >> /Users/kama/.m2/toolchains.xml
> >> > >
> >> > > Sorry, I don't get it: where do I see, i.e., that 
> >> > > https://urldefense.proofpoint.com/v2/url?u=http-3A__style.info;
> >> > > d=DwIFAw=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3
> >> > > PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=2L1RhrmrIqeZgpxGINVHuce
> >> > > t-6gs3sqlQV0EAtYNCEw=qxOWjrA4IAwf-c9x4Tj4feaA6XHKd--2MpsU3ZaF
> >> > > Tas=  is
> >>
> >> blue by
> >>
> >> > > default?>
> >> >
> >> > The following line is colored by the appropriate colors which are 
> >> > used...you should not do a redirect into a pipe via less/more etc..
> >> >
> >> > >> [DEBUG] Message styles: debug info warning error success 
> >> > >> failure
> >>
> >> strong
> >>
> >> I see:
> >>
> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__pasteboard.co_2
> >> wnAdZx8P.png=DwIFAw=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo
> >> =dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=2L1RhrmrIqeZgpxGIN
> >> VHucet-6gs3sqlQV0EAtYNCEw=DsBpenyyfz6ZTQ0kf3ynnjMnVQwN8mHlS9Gss3C
> >> z5ho=
> >>
> >> but still do not have the equivalent color name (e.g. that info is
> >> 'blue': I
> >> can guess it, naturally...).
> >>
> >> Regards.
> >>
> >> ---
> >> -- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For

RE: [EXTERNAL] Re: Getting maven to create a bundle manifest incrementally in eclipse

2017-03-21 Thread Justin Georgeson

It's a 2 or 3 stage approach:

1. Use a traditional jar project with bnd-maven-plugin or bundle-maven-plugin 
to either build your source code as an OSGI jar or to take a non-OSGI 
dependency from a Maven repo and generate an OSGI version of it. Publish with 
standard 'mvn deploy' to Maven repo. This is the 'build01' part from the page 
you linked. The example uses the Apache Felix bundle-maven-plugin but my 
personal preference is the bnd-maven-plugin since it's from the same people who 
provide the underlying bnd tool that's generating the MANIFEST.

2. Use an eclipse-repository packaging type project with pom-first dependencies 
and the pomDependencies == consider mode to package and a P2 software site of 
all the dependencies you wrapped and published in #1.

3. Build your plugins/features/software sites with only eclipse-* packaging and 
MANIFEST-first dependencies, using the P2 site published in #2. This is the 
'build02' part of the page you linked.

The #2 stage is optional and can be replaced by putting  in the 
pom.xml of your eclipse-* packaging type projects, duplicating them in MANIFEST 
(or feature.xml, or category.xml as appropriate per packaging type), and using 
pomDependencies == consider. This is where you really appreciate the limitation 
that these pom dependencies are not transitive. That is to say, if pluginA has 
pom dependency on lib1, and featureA includes pluginA, and repositoryA includes 
pluginA, then you need to have the pom dependency on lib1 in featureA and 
repositoryA. But you _don't_ put lib1 in featureA's feature.xml or 
repositoryA's category.xml if you don't want to package lib1 in your software 
site (like a provided scope pom dependency that should be installed already at 
runtime but you need it at compile time).

So including #2 makes life easier in #3 because you're then relying purely on 
Tycho's expected project setup, which incidentally is Eclipse compatible 
without involving m2e (after all the whole point of Tycho is to have a 
CLI/Maven build that works the same as Eclipse IDE for 
Plug-In/Feature/Product/Repository/Target projects).

-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] 
Sent: Tuesday, March 21, 2017 5:06 PM
To: Justin Georgeson <jgeorge...@lgc.com>; Maven Users List 
<users@maven.apache.org>; i...@soebes.de
Subject: Re: [EXTERNAL] Re: Getting maven to create a bundle manifest 
incrementally in eclipse

External Sender: Use caution with links/attachments.

Hi,

as far as i know you can generate the MANIFEST file from that...?? Not 100%sure 
about this [1] cause I never used it myself..

Furthermore if you create an appropriate target platform and create a p2 repo 
from it (using tycho, upload to Nexus for example) this can be used to be 
integrated in your build in Eclipse (using tycho) which than will solve it also 
inside Eclipse...

Kind regards
Karl Heinz

[1]:
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.eclipse.org_Tycho_How-5FTos_Dependency-5Fon-5Fpom-2Dfirst-5Fartifacts=DwICaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Ht2mGcb7bKFhSYqPX9TkDkGR1_Ws4bXVOXQr6DHeYfc=RN498eCCq5qCVS9Wmn_z28u9DUGt85S5PSjKpU9qXxU=

On 21/03/17 22:42, Justin Georgeson wrote:
> POM-first dependencies in Tycho is just for resolution of plugin jars from 
> Maven repo (when they're not available in a P2 software site). It doesn't 
> handle writing your MANIFEST file to reflect those POM-first dependencies, so 
> you have to declare them in both files in that case.
>
> -Original Message-
> From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
> Sent: Tuesday, March 21, 2017 3:34 PM
> To: Maven Users List <users@maven.apache.org>
> Subject: [EXTERNAL] Re: Getting maven to create a bundle manifest 
> incrementally in eclipse
>
> External Sender: Use caution with links/attachments.
>
>
>
> Hi Bill,
>
> On 21/03/17 16:01, Bill Mair wrote:
>> Hi,
>>
>> I'm attempting to switch to maven to create my packages but I have 
>> hit a snag that I can't find a solution for.
>>
>> Up until now, I have been controlling the dependencies of my ant 
>> build process with the contents of "META-INF/MANIFEST.MF". Maven 
>> works the other way around and generates that based on what I have 
>> actually used, which I think is fantastic.
>
> You can use Maven Tycho which gives you back the switch of requirement.
> In Tycho you can either work MANIFEST first or POM first setup...
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__eclipse.org_tycho
> _=DwICaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAq
> FnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Afq0-NWD7K5pqCrTDV4FppklgbeyRakFBIP
> qJoSP43Y=bGPk9-NRTEIkBgx-D3uOAMwB-b2itE0bf0pzjbKlZs0=
>
>
> And of course if your working on OSGi it makes sense to control the 
> de

RE: [EXTERNAL] Re: Getting maven to create a bundle manifest incrementally in eclipse

2017-03-21 Thread Justin Georgeson

POM-first dependencies in Tycho is just for resolution of plugin jars from 
Maven repo (when they're not available in a P2 software site). It doesn't 
handle writing your MANIFEST file to reflect those POM-first dependencies, so 
you have to declare them in both files in that case.

-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] 
Sent: Tuesday, March 21, 2017 3:34 PM
To: Maven Users List 
Subject: [EXTERNAL] Re: Getting maven to create a bundle manifest incrementally 
in eclipse

External Sender: Use caution with links/attachments.



Hi Bill,

On 21/03/17 16:01, Bill Mair wrote:
> Hi,
>
> I'm attempting to switch to maven to create my packages but I have hit 
> a snag that I can't find a solution for.
>
> Up until now, I have been controlling the dependencies of my ant build 
> process with the contents of "META-INF/MANIFEST.MF". Maven works the 
> other way around and generates that based on what I have actually 
> used, which I think is fantastic.

You can use Maven Tycho which gives you back the switch of requirement.
In Tycho you can either work MANIFEST first or POM first setup...

https://urldefense.proofpoint.com/v2/url?u=https-3A__eclipse.org_tycho_=DwICaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Afq0-NWD7K5pqCrTDV4FppklgbeyRakFBIPqJoSP43Y=bGPk9-NRTEIkBgx-D3uOAMwB-b2itE0bf0pzjbKlZs0=


And of course if your working on OSGi it makes sense to control the 
dependencies via MANIFEST via Eclipse which can handle that very good 
(dependencies, tree etc., target platforms etc.).



>
> I already have the git hash being included by buildnumber-maven-plugin 
> (which required the additional pluginManagement section to work 
> correctly in eclipse).

Than you are using an old version cause 3.0.0 already includes this mapping for 
m2e...


>
> My problem is that this is only generated when I build the bundle and 
> not during incremental saves.

The reason is simply cause you changed the side which means pom first..which I 
would say is not a good idea in OSGi and Eclipse...


Kind regards
Karl Heinz Marbaise

>
> What do I have to change in this pom.xml to make eclipse, m2e, maven 
> and the maven-bundle-plugin play nicely together?
>
> --
> Bill Mair
>
> pom.xml
> 
>  xmlns="https://urldefense.proofpoint.com/v2/url?u=http-3A__maven.apache.org_POM_4.0.0=DwICaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Afq0-NWD7K5pqCrTDV4FppklgbeyRakFBIPqJoSP43Y=Kd-TDhLw1iVBaAqGOI6edW5kxuY1JW2ncBCQDTakR0Y=
>  "
> xmlns:xsi="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_2001_XMLSchema-2Dinstance=DwICaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Afq0-NWD7K5pqCrTDV4FppklgbeyRakFBIPqJoSP43Y=UiQcEFOTpLzlDZ2bGKUP0roZmZ-lekq-ckzXz77Yxhk=
>  "
> 
> xsi:schemaLocation="https://urldefense.proofpoint.com/v2/url?u=http-3A
> __maven.apache.org_POM_4.0.0=DwICaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbr
> MXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Afq0-NWD
> 7K5pqCrTDV4FppklgbeyRakFBIPqJoSP43Y=Kd-TDhLw1iVBaAqGOI6edW5kxuY1JW2n
> cBCQDTakR0Y= 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__maven.apache.org_x
> sd_maven-2D4.0.0.xsd=DwICaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF
> 0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Afq0-NWD7K5pqCrT
> DV4FppklgbeyRakFBIPqJoSP43Y=w_BXwgMpPrHERwc7gqdgadG__EXBDlY4TbMX5iap
> Kqw= ">
>
> 
> 
>   >test.iface
> 
>   >test.iface
> 
>   >UTF-8
> 
>   >/MM/dd HH:mm:ss z
> 
>
> 4.0.0
> test
> test.iface
> 1.0.1
>
> 
> scm:git:file://.
> scm:git:file://.
> scm:git:file://.
> HEAD
> 
>
> 
> 
>  
> org.osgi
> org.osgi.core
> 5.0.0
> provided
> true
> 
> 
>

RE: [EXTERNAL] Maven password encryption by project

2017-03-17 Thread Justin Georgeson

You might want to look into secrets management tools such as Vault from 
HashiCorp and KeyWhiz from Square.

-Original Message-
From: Alix Lourme [mailto:alix.lou...@gmail.com] 
Sent: Friday, March 17, 2017 8:39 AM
To: Maven Users List 
Subject: [EXTERNAL] Maven password encryption by project

External Sender: Use caution with links/attachments.



Dear community,

I'm searching the best practice for password encryption in a maven POM file *by 
project*, could by used by properties (like in ANT or WAGON). Sample :
---

maven-antrun-plugin
1.8




https://urldefense.proofpoint.com/v2/url?u=http-3A__-257Bdocker.pa=DwIBaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=VrtzR6_x6JB1w8nnS08BGhRk_R1CJcVu8q5OmN6WM6c=NvWeAVdU_1jCUfassq_nuT8MNeX1wbaM8rZzff6JlYE=
 ssword}@10.xx.xx.xx:/root/.docker/*"
todir="cert" trust="yes" />



---

In this case, my *docker.password* could be a properties (pom or
settings.xml) but must not be in clear text.

The problem with Maven encryption
:
- I have a master password defined in *settings-security.xml* (locally) for my 
user need (like proxy password encryption in MY *settings.xml*)
- The CI tools contains the same mechanism (own *settings-security.xml*) for 
global needs, like server encryption used in *settings.xml* for jar publication 
in repository ; and I can't retrieve this file

=> I can't use this mechanism for password encryption who works locally and on 
the CI server.

*Is there a way to have a encryption mechanism for the project's perimeter
?* (and not for user's perimeter, current Maven encryption works perfectly for 
that).

---

Using -s and -gs Maven options (=> user/global settings override) could be a 
workaround but :
- Server item definition or properties defining password must be in clear text
- Using this Maven settings for each build depending the project workspace is a 
little boring

Perhaps is there a best way like a "private key by project" ... but I didn't 
found entry point about that.

Thanks in advance. Best regards
*NB*: This question was firstly on stackoverflow 
, but no really interest ^^.
--
Alix Lourme

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

profile activation on property set but !value vs property not set

2017-03-11 Thread Justin Georgeson

Seeing that I can ! the property value in a profile activation, I assumed there
were three states to consider when evaluating the property activation:

1. Property not set
2. Property set and value does not match
3. Property set and value does match

With this assumption I thought that with profiles such as these

default-reactor
!platform

platform-reactor

platform!all

all-platforms-reactor

platformall

I would only see one of the three profiles active at a time. However when I run
Maven 'mvn help:active-profiles' with no 'platform' property then both the
'default-reactor' and 'platform-reactor' are active. When I set the 'platform'
property then I see the behavior I expected. Looking at the source

https://github.com/apache/maven/blob/38300cf2832e9a40198091aa9e0bf6d3dbc3268d/maven-model-builder/src/main/java/org/apache/maven/model/profile/activation/PropertyProfileActivator.java#L95

It's doing a string compare of the activation's declared property value against
the context's property value, but it's not checking the context has a property
set. But I would infer from the comment on L94 ("we have a value, so it has to
match the system value...") that an unset property should not match a !value
activation.

Should I open a JIRA issue as a bug, or as a feature request?

--
This e-mail, including any attached files, may contain confidential and
privileged information for the sole use of the intended recipient. Any review,
use, distribution, or disclosure by others is strictly prohibited. If you are
not the intended recipient (or authorized to receive information for the
intended recipient), please contact the sender by reply e-mail and delete all
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] [ANN] Apache Maven Version 3.5.0-alpha-1 Released

2017-03-02 Thread Justin Georgeson

There's already MNG-5585 [1] for declaring credentials for authentication 
realms insettings.xml, so that Maven could choose the credentials that match 
the challenge by realm instead of hard coding the mapping of each  
to a .

[1] https://issues.apache.org/jira/browse/MNG-5585

-Original Message-
From: Andreas Sewe [mailto:s...@st.informatik.tu-darmstadt.de] 
Sent: Thursday, March 2, 2017 6:05 AM
To: users@maven.apache.org
Cc: Justin Georgeson <jgeorge...@lgc.com>
Subject: Re: [EXTERNAL] [ANN] Apache Maven Version 3.5.0-alpha-1 Released

Stephen Connolly wrote:
> Can you create an issue against the MNG project in the issue tracker 
> and we will consider it from there

I'll leave that to Justin, as he has the need for this feature and can probably 
describe his requirements best:

  <https://issues.apache.org/jira/browse/MNG>

I just pointed out that Eclipse Tycho already does something similar "on top 
of" Maven's setting.xml for repository mirrors. Would be great if the two 
mechanisms would be similar syntactically as well.

Best wishes,

Andreas

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

RE: [EXTERNAL] [ANN] Apache Maven Version 3.5.0-alpha-1 Released

2017-03-01 Thread Justin Georgeson

Thanks for all the hard work that goes into maintaining and improving the tool!

Any chance the Aether work would somehow enable declaring server credentials 
only once in settings.xml and then reusing them for multiple 
build.repositories.repository nodes in pom.xml (such as when you have multiple 
independent repositories within the same authentication realm of a single 
host)? 

-Original Message-
From: stephen.alan.conno...@gmail.com [mailto:stephen.alan.conno...@gmail.com] 
On Behalf Of Stephen Connolly
Sent: Wednesday, March 1, 2017 11:10 AM
To: annou...@maven.apache.org; Maven Users List 
Cc: Maven Developers List 
Subject: [EXTERNAL] [ANN] Apache Maven Version 3.5.0-alpha-1 Released

External Sender: Use caution with links/attachments.



The Apache Maven team would like to announce the release of Maven 3.5.0-alpha-1.

https://urldefense.proofpoint.com/v2/url?u=http-3A__maven.apache.org_=DwIBaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=lM1dtQUOVnlEbaG-BvvxiSaA84FnZZtxyGWvRz4um_E=uxDjp7NPkWNGHWVqZzg9bAu8heEy1B3ZwWbXgvLKq7A=

NOTE: This is an ALPHA release. There is the potential that features may be 
added/removed between this release and the first GA release in the 3.5.x 
release line.
Please consult the Known Issues section below before use

You can download the appropriate sources, etc. from the archives section on the 
download page as Maven 3.3.9 is still the recommended GA release

https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.apache.org_dist_maven_maven-2D3_3.5.0-2Dalpha-2D1_=DwIBaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=lM1dtQUOVnlEbaG-BvvxiSaA84FnZZtxyGWvRz4um_E=LedMpLI_nCjtY6oTmjvQ1eaJJf3HSz1rSRm8mMNENzc=

Known Issues

The following issues were identified during release testing of this ALPHA 
release but have not been deemed as release blockers:

* [MNG-6177] The `--file` and `-f` option to specify a `pom.xml` to use does 
not work if the path includes characters that need quoting such as whitespace 
or `&`.
* [MNG-6115] If Maven is installed in a writable location, every build will 
create a new `lib/ext/jansi-` file.

Why not Maven 3.4.0?

After Maven 3.3.9 was released, the Eclipse Aether project was retired and the 
code base was migrated to the Apache Maven project.

The original goal for the 3.4.0 release was to replace Aether with the exact 
same code after migration to the Apache Maven project and then proceed with bug 
fixes to the resolver code as well as other areas of Maven.

The migration of the code between the two foundations took longer than expected 
and as a result there were other changes committed to Maven core that were 
outside the scope of intent for 3.4.0.

In order to refocus on the original intent for 3.4.0, the decision was taken to 
revert the Maven core history to the point of the 3.3.9 release and merge in 
the desired changes one at a time.

Because there had been a lot of communication about different features being 
delivered and bugs fixed in Maven 3.4.0 and the new history may not contain 
them in the first release, the decision was taken to forever burn the 3.4.x 
release line.

More detail on this decision can be read in the [mailing list archive]( 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mail-2Darchive.com_dev-40maven.apache.org_msg112103.html=DwIBaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=lM1dtQUOVnlEbaG-BvvxiSaA84FnZZtxyGWvRz4um_E=400J7D2MFpk6_R1xoqNaJueydenDV3DM0eRrVoejMp4=
 ).


Release Notes - Maven - Version 3.5.0-alpha-1

Bugs:
* [MNG-5297] - Site should tell 'prerequisites.maven is deprecated'
* [MNG-5368] - UnsupportedOperationException thrown when version range is 
not correct in dependencyManagement definitions
* [MNG-5629] - ClosedChannelException from DefaultUpdateCheckManager.read
* [MNG-5815] - "mvn.cmd" does not indicate failure properly when using "&&"
* [MNG-5823] - mvnDebug doesn't work with M2_HOME with spaces - missing 
quotes
* [MNG-5829] - mvn shell script fails with syntax error on Solaris 10
* [MNG-5836] - logging config is overridden by $M2_HOME/lib/ext/*.jar
* [MNG-5852] - mvn shell script invokes /bin/sh but requires Bash functions
* [MNG-5958] - java.lang.String cannot be cast to 
org.apache.maven.lifecycle.mapping.LifecyclePhase
* [MNG-5961] - Maven possibly not aware of log4j2
* [MNG-5962] - mvn.cmd fails when the current directory has spaces in 
between
* [MNG-5963] - mvn.cmd does not return ERROR_CODE
* [MNG-6022] - mvn.cmd fails if directory contains an ampersand (&)
* [MNG-6053] - Unsafe System Properties copy in MavenRepositorySystemUtils, 
causing NPEs
* [MNG-6105] -
properties.internal.SystemProperties.addSystemProperties() is not really 
thread-safe
* [MNG-6109] - PluginDescriptor doesn't read since value of parameter

RE: [EXTERNAL] Re: buildnumber-maven-plugin's buildNumber property unset during deploy goal

2017-02-27 Thread Justin Georgeson

Hi Karl, have you been able to find anything regarding this issue?

-Original Message-
From: Justin Georgeson 
Sent: Monday, February 13, 2017 2:45 PM
To: Maven Users List <users@maven.apache.org>; 'i...@soebes.de' <i...@soebes.de>
Subject: RE: [EXTERNAL] Re: buildnumber-maven-plugin's buildNumber property 
unset during deploy goal

Plain old 'mvn deploy' results in the failure

[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ artifact ---   
 
Downloading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=${timestamp};build.number=${buildNumber}/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
 
[WARNING] Could not transfer metadata 
com.example:artifact:1.0-SNAPSHOT/maven-metadata.xml from/to snapshots 
(http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=${timestamp};build.number=${buildNumber}):
 Illegal character in path at index 100: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=${timestamp};build.number=${buildNumber}/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
  

Using 'mvn deploy -Dtimestamp=1234 -DbuildNumber=5678' succeeds (confirming I 
have permission). In the latter case where I supply the property via 
command-line or in the  element in pom.xml, the Maven console 
output shows those properties resolved in the URL.

[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ artifact ---
Downloading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
 (742 B at 1.6 KB/sec)
Uploading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/artifact-1.0-20170213.204205-2.jar
Uploaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/artifact-1.0-20170213.204205-2.jar
 (3 KB at 15.6 KB/sec)
Uploading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/artifact-1.0-20170213.204205-2.pom
Uploaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/artifact-1.0-20170213.204205-2.pom
 (3 KB at 26.1 KB/sec)
Downloading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/maven-metadata.xml
Downloaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/maven-metadata.xml
 (345 B at 8.0 KB/sec)
Uploading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
Uploaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
 (763 B at 16.2 KB/sec)
Uploading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/maven-metadata.xml
Uploaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/maven-metadata.xml
 (358 B at 5.6 KB/sec)

The full example pom.xml that I'm using to test is now posted on the GitHub 
issue.

-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] 
Sent: Sunday, February 12, 2017 5:17 AM
To: Maven Users List <users@maven.apache.org>
Subject: [EXTERNAL] Re: buildnumber-maven-plugin's buildNumber property unset 
during deploy goal

External Sender: Use caution with links/attachments.



Hi,



first how are you calling Maven ? Can you show a complete

call...Furthermore a full example pom ?



Based on the docs..Do you have the permission to use the property ?



You must have the 'Annotate' permission in order to add properties to

deployed artifacts.





?



Kind regards

Karl Heinz Marbaise



On 12/02/17 02:24, Justin Georgeson wrote:

> Slight correction, the timestamp property as set by buildnumber-maven-plugin 
> is also not set. I noticed I am defaulting the timestamp property with 
> maven.build.timestamp. When I remove that then the failure also includes a 
> literal "${

RE: Strategies for overriding parent plugin configuration in some modules without duplicating config code?

2017-02-20 Thread Justin Georgeson

Have you looked at combine.children="append" or combine.self="override" 
attributes to the  element?

http://blog.sonatype.com/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/
https://maven.apache.org/pom.html


-Original Message-
From: KARR, DAVID [mailto:dk0...@att.com] 
Sent: Monday, February 20, 2017 10:33 AM
To: Maven Users List 
Subject: [EXTERNAL] Strategies for overriding parent plugin configuration in 
some modules without duplicating config code?

External Sender: Use caution with links/attachments.



Although my issue is about configuring the "jacoco-maven-plugin", I think it's 
really more of a pure Maven configuration issue, as I don't think this 
situation is unique to JaCoCo.

I have a somewhat large multi-module project.  Each of the child modules has a 
parent pom that configures the "jacoco-maven-plugin" to do offline 
instrumentation (at present, all the modules having unit tests using PowerMock, 
which doesn't work with online instrumentation).

I've designed a change that I'll have to make in a few classes in each module 
that will allow the unit tests to use Mockito, and for JaCoCo to use online 
instrumentation.  I'll eventually fix all of them to work this way, but it will 
take a little while.  In the meantime, I just want to override the 
configuration in the "fixed" modules with online instrumentation and let the 
other modules use the default of offline instrumentation.

The simple-minded way to do this is just to define the same configuration using 
online instrumentation in each "fixed" module, so it will override the parent 
pom.  Copying that block to every "fixed" module is not a great idea.  I'd like 
a solution that requires less code duplication.

I suppose I could define ANOTHER parent pom, that specifies the existing parent 
as its parent, and have that second parent use online instrumentation, and have 
the fixed modules use that second parent instead.  I will eventually delete 
this second parent pom once all of the modules are "fixed".

Note that I have a separate aggregator pom that is not a parent pom.

Are there other reasonable strategies for this "use original parent for some, 
override in same way for others" situation?



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] Re: buildnumber-maven-plugin's buildNumber property unset during deploy goal

2017-02-13 Thread Justin Georgeson

Plain old 'mvn deploy' results in the failure

[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ artifact ---   
 
Downloading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=${timestamp};build.number=${buildNumber}/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
 
[WARNING] Could not transfer metadata 
com.example:artifact:1.0-SNAPSHOT/maven-metadata.xml from/to snapshots 
(http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=${timestamp};build.number=${buildNumber}):
 Illegal character in path at index 100: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=${timestamp};build.number=${buildNumber}/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
  

Using 'mvn deploy -Dtimestamp=1234 -DbuildNumber=5678' succeeds (confirming I 
have permission). In the latter case where I supply the property via 
command-line or in the  element in pom.xml, the Maven console 
output shows those properties resolved in the URL.

[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ artifact ---
Downloading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
 (742 B at 1.6 KB/sec)
Uploading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/artifact-1.0-20170213.204205-2.jar
Uploaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/artifact-1.0-20170213.204205-2.jar
 (3 KB at 15.6 KB/sec)
Uploading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/artifact-1.0-20170213.204205-2.pom
Uploaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/artifact-1.0-20170213.204205-2.pom
 (3 KB at 26.1 KB/sec)
Downloading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/maven-metadata.xml
Downloaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/maven-metadata.xml
 (345 B at 8.0 KB/sec)
Uploading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
Uploaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/1.0-SNAPSHOT/maven-metadata.xml
 (763 B at 16.2 KB/sec)
Uploading: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/maven-metadata.xml
Uploaded: 
http://art.example.com/artifactory/test-deploy-snapshots;build.name=artifact;build.timestamp=1234;build.number=5678/com/example/artifact/maven-metadata.xml
 (358 B at 5.6 KB/sec)

The full example pom.xml that I'm using to test is now posted on the GitHub 
issue.

-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] 
Sent: Sunday, February 12, 2017 5:17 AM
To: Maven Users List <users@maven.apache.org>
Subject: [EXTERNAL] Re: buildnumber-maven-plugin's buildNumber property unset 
during deploy goal

External Sender: Use caution with links/attachments.



Hi,



first how are you calling Maven ? Can you show a complete

call...Furthermore a full example pom ?



Based on the docs..Do you have the permission to use the property ?



You must have the 'Annotate' permission in order to add properties to

deployed artifacts.





?



Kind regards

Karl Heinz Marbaise



On 12/02/17 02:24, Justin Georgeson wrote:

> Slight correction, the timestamp property as set by buildnumber-maven-plugin 
> is also not set. I noticed I am defaulting the timestamp property with 
> maven.build.timestamp. When I remove that then the failure also includes a 
> literal "${timestamp}" in the URL. I've tested using a stub project generated 
> with the quickstart archetype and submitted it as an issue to 
> buildnumber-maven-plugin [2].

>

> [2] 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mojohaus_buildnumber-2Dmaven-2Dplugin_issues_58=DwIGaQ=

RE: buildnumber-maven-plugin's buildNumber property unset during deploy goal

2017-02-11 Thread Justin Georgeson

Slight correction, the timestamp property as set by buildnumber-maven-plugin is 
also not set. I noticed I am defaulting the timestamp property with 
maven.build.timestamp. When I remove that then the failure also includes a 
literal "${timestamp}" in the URL. I've tested using a stub project generated 
with the quickstart archetype and submitted it as an issue to 
buildnumber-maven-plugin [2]. 

[2] https://github.com/mojohaus/buildnumber-maven-plugin/issues/58

-Original Message-----
From: Justin Georgeson [mailto:jgeorge...@lgc.com] 
Sent: Saturday, February 11, 2017 6:51 PM
To: Maven Users List (users@maven.apache.org) <users@maven.apache.org>
Subject: [EXTERNAL] buildnumber-maven-plugin's buildNumber property unset 
during deploy goal

External Sender: Use caution with links/attachments.



Posting here in case the issue is in maven-deploy-plugin rather than 
buildnumber-maven-plugin. Using 1.4 of buildnumber-maven-plugin, with both 
3.2.5 and 3.3.9 of Maven.

I'm trying to make use of Artifactory's matrix parameters in the 
distributionManagement URL to attach properties in Artifactory [1].



snapshots
artprod.example.com-releases

https://urldefense.proofpoint.com/v2/url?u=https-3A__artprod.example.com_artifactory_test-2Ddeploy-2Dreleases-3Bbuild.name-3D-24=DwIFAg=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Mm2YhlLYr2DTRM6a_kyb26TI7xMWKrVcvbOxyD948FA=GVz2IAufbzRlIuXon0_49qAdNYDX4euVAE4cvOgIvc4=
 
{project.artifactId};build.timestamp=${timestamp};build.number=${buildNumber}


snapshots
artprod.example.com-snapshots

https://urldefense.proofpoint.com/v2/url?u=https-3A__artprod.example.com_artifactory_test-2Ddeploy-2Dsnapshots-3Bbuild.name-3D-24=DwIFAg=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Mm2YhlLYr2DTRM6a_kyb26TI7xMWKrVcvbOxyD948FA=NF5fsk4I_uEc7eqXlyxPW5XGhNPjIQ8WwAsgVVKFV4Q=
 
{project.artifactId};build.timestamp=${timestamp};build.number=${buildNumber}



The deploy is failing because it has a literal "${buildNumber}" in the URL 
while all the other property references (including the ${timestamp} property 
also set by buildnumber-maven-plugin) are resolving ok.

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on 
project com.example.artifact: Failed to retrieve remote metadata 
com.example:com.example.artifact:10.5.4-SNAPSHOT/maven-metadata.xml: Could not 
transfer metadata 
com.example:com.example.artifact:10.5.4-SNAPSHOT/maven-metadata.xml from/to 
snapshots 
(https://urldefense.proofpoint.com/v2/url?u=https-3A__artprod.example.com_artifactory_test-2Ddeploy-2Dsnapshots-3Bbuild.name-3Dcom.example.artifact-3Bbuild.timestamp-3D20170212002949-3Bbuild.number-3D-24=DwIFAg=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Mm2YhlLYr2DTRM6a_kyb26TI7xMWKrVcvbOxyD948FA=bxuoJXilYzFlOI-TuOn6OzgHIZ43HYBt6ptPIk8eF6Q=
 {buildNumber}): Illegal character in path at index 155: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__artprod.example.com_artifactory_test-2Ddeploy-2Dsnapshots-3Bbuild.name-3Dcom.example.artifact-3Bbuild.timestamp-3D20170212002949-3Bbuild.number-3D-24=DwIFAg=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Mm2YhlLYr2DTRM6a_kyb26TI7xMWKrVcvbOxyD948FA=bxuoJXilYzFlOI-TuOn6OzgHIZ43HYBt6ptPIk8eF6Q=
 
{buildNumber}/com/lgc/dsg-installables/com.example.artifact/10.5.4-SNAPSHOT/maven-metadata.xml
 -> [Help 1]

I've tried changing the build number property name set by 
buildnumber-maven-plugin with 
-Dmaven.buildNumber.buildNumberPropertyName=build.blah and referencing that 
alternate property in the distributionManagement URL, with the same ill result.

[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.jfrog.com_confluence_display_RTF_Using-2BProperties-2Bin-2BDeployment-2Band-2BResolution-23UsingPropertiesinDeploymentandResolution-2DDynamicallyAddingPropertiestoArtifactsonDeployment=DwIFAg=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=Mm2YhlLYr2DTRM6a_kyb26TI7xMWKrVcvbOxyD948FA=7ySqBaHpasb8itCASvlLnjFRDfVoBt7Xc075kMUwcKI=

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

buildnumber-maven-plugin's buildNumber property unset during deploy goal

2017-02-11 Thread Justin Georgeson

Posting here in case the issue is in maven-deploy-plugin rather than 
buildnumber-maven-plugin. Using 1.4 of buildnumber-maven-plugin, with both 
3.2.5 and 3.3.9 of Maven.

I'm trying to make use of Artifactory's matrix parameters in the 
distributionManagement URL to attach properties in Artifactory [1].



snapshots
artprod.example.com-releases

https://artprod.example.com/artifactory/test-deploy-releases;build.name=${project.artifactId};build.timestamp=${timestamp};build.number=${buildNumber}


snapshots
artprod.example.com-snapshots

https://artprod.example.com/artifactory/test-deploy-snapshots;build.name=${project.artifactId};build.timestamp=${timestamp};build.number=${buildNumber}



The deploy is failing because it has a literal "${buildNumber}" in the URL 
while all the other property references (including the ${timestamp} property 
also set by buildnumber-maven-plugin) are resolving ok.

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on 
project com.example.artifact: Failed to retrieve remote metadata 
com.example:com.example.artifact:10.5.4-SNAPSHOT/maven-metadata.xml: Could not 
transfer metadata 
com.example:com.example.artifact:10.5.4-SNAPSHOT/maven-metadata.xml from/to 
snapshots 
(https://artprod.example.com/artifactory/test-deploy-snapshots;build.name=com.example.artifact;build.timestamp=20170212002949;build.number=${buildNumber}):
 Illegal character in path at index 155: 
https://artprod.example.com/artifactory/test-deploy-snapshots;build.name=com.example.artifact;build.timestamp=20170212002949;build.number=${buildNumber}/com/lgc/dsg-installables/com.example.artifact/10.5.4-SNAPSHOT/maven-metadata.xml
 -> [Help 1]

I've tried changing the build number property name set by 
buildnumber-maven-plugin with 
-Dmaven.buildNumber.buildNumberPropertyName=build.blah and referencing that 
alternate property in the distributionManagement URL, with the same ill result.

[1] 
https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-DynamicallyAddingPropertiestoArtifactsonDeployment

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

RE: [EXTERNAL] Re: help with version range

2016-09-23 Thread Justin Georgeson

I tried these four version ranges with the 3.4.0-SNAPSHOT from your link 

[1.1.min,1.1.max]
[1.1.*]
[1.2.min,1.2.max]
[1.2.*]

All four downloaded the expected parent POM without the warnings.

I like the colorized output.

-Original Message-
From: Christian Schulte [mailto:c...@schulte.it] 
Sent: Friday, September 23, 2016 8:47 PM
To: Maven Users List <users@maven.apache.org>
Subject: Re: [EXTERNAL] Re: help with version range

Am 09/24/16 um 02:15 schrieb Justin Georgeson:
> The Aether doc shows both bounds being inclusive with the min/max form, but 
> you have an exclusive upper bound. Using "[1.1.min,1.1.max]" is working for 
> me with both 3.2.5 and 3.3.9. So that's awesome! The .* form is working for 
> me too. I'm using JDK 1.8.0_102, and my projects are pretty much all Tycho 
> packaging-types.
> 
> I am seeing these warnings
> 
> [WARNING] Failed to canonicalize path 
> C:\Code\caches\m2\com\lgc\master\[1.1.*]\master-[1.1.*].pom.lastUpdate
> d: The filename, direc tory name, or volume label syntax is incorrect
> Downloading: 
> http://cmartifacts3.lgc.com/artifactory/maven-virtual/com/lgc/master/%
> 5B1.1.*%5D/master-%5B1.1.*%5D.pom [WARNING] Failed to canonicalize 
> path 
> C:\Code\caches\m2\com\lgc\master\[1.1.*]\master-[1.1.*].pom.lastUpdate
> d: Invalid argument [WARNING] Failed to create parent directories for 
> tracking file 
> C:\Code\caches\m2\com\lgc\master\[1.1.*]\master-[1.1.*].pom.lastUp
> dated
> [WARNING] Failed to build parent project for 
> com.lgc.lowest:lowest-parent:pom:10.5.2-SNAPSHOT
> 
> Which are reported in the original JIRA ticket for the feature
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org
> _jira_browse_MNG-2D2199=DQICaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2F
> ZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=leobnERpx7eIg
> IvKmjTYhgj8buTHbUXeP5uyujIxsBY=WtN5v0mIkuOLd0hI4m_OpYLLsyZGYi6ivI7n6
> lvH6gw=
> 
> But it is ultimately working.

Can you please test a recent 3.4.0-SNAPSHOT and report if those messages 
disappear? Parent version ranges are broken in the Maven versions you mentioned.

<https://urldefense.proofpoint.com/v2/url?u=https-3A__builds.apache.org_view_All_job_maven-2D3.3-2Drelease-2Dstatus-2Dbuild_=DQICaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=leobnERpx7eIgIvKmjTYhgj8buTHbUXeP5uyujIxsBY=R4EYmMCVXobVq6h9SfS4A9EtWGvXSOLvTqmjLIMelbY=
 >

Regards,
--
Christian


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

RE: [EXTERNAL] Re: help with version range

2016-09-23 Thread Justin Georgeson

The Aether doc shows both bounds being inclusive with the min/max form, but you 
have an exclusive upper bound. Using "[1.1.min,1.1.max]" is working for me with 
both 3.2.5 and 3.3.9. So that's awesome! The .* form is working for me too. I'm 
using JDK 1.8.0_102, and my projects are pretty much all Tycho packaging-types.

I am seeing these warnings

[WARNING] Failed to canonicalize path 
C:\Code\caches\m2\com\lgc\master\[1.1.*]\master-[1.1.*].pom.lastUpdated: The 
filename, direc
tory name, or volume label syntax is incorrect
Downloading: 
http://cmartifacts3.lgc.com/artifactory/maven-virtual/com/lgc/master/%5B1.1.*%5D/master-%5B1.1.*%5D.pom
[WARNING] Failed to canonicalize path 
C:\Code\caches\m2\com\lgc\master\[1.1.*]\master-[1.1.*].pom.lastUpdated: 
Invalid argument
[WARNING] Failed to create parent directories for tracking file 
C:\Code\caches\m2\com\lgc\master\[1.1.*]\master-[1.1.*].pom.lastUp
dated
[WARNING] Failed to build parent project for 
com.lgc.lowest:lowest-parent:pom:10.5.2-SNAPSHOT

Which are reported in the original JIRA ticket for the feature

https://issues.apache.org/jira/browse/MNG-2199

But it is ultimately working.

-Original Message-
From: Robert Patrick [mailto:robert.patr...@oracle.com] 
Sent: Friday, September 23, 2016 4:39 PM
To: Maven Users List 
Subject: RE: [EXTERNAL] Re: help with version range

This is nice, but it doesn’t work in Maven 3.3.9...

[ERROR] org.apache.maven.project.artifact.InvalidDependencyVersionException: 
Invalid version: [0.8.min,0.8.max] found for: Dependency: myproject:util in 
project: myproject:zip-installer:pom:0.9-SNAPSHOT. Reason: Range defies version 
ordering: [0.8.min,0.8.max) for project 
myproject:zip-installer:pom:0.9-SNAPSHOT at C:\tmp\myproject\zipinstall\pom.xml 
-> [Help 1]

--
Robert Patrick 
 VP, OPC Development, Oracle Corporation
7460 Warren Pkwy, Ste. 300  Office: +1.972.963.2872
Frisco, TX 75034, USA   Mobile: +1.469.556.9450

Professional Oracle WebLogic Server
by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul 
Done Book Home Page: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.wrox.com_=DQIFaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=5-lYd2DM46_1xLARlg3yqwPE5xDzWM8s_z59bPNPfQU=pyMmnscielr3hC7gWtaVNqyUIqmy1jf4wWg996YlkUI=
Kindle Version: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.amazon.com_=DQIFaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=5-lYd2DM46_1xLARlg3yqwPE5xDzWM8s_z59bPNPfQU=hTJHlTeI3Pk6q1pSEHNHzc-xHC9n3wIYawL8FK3y5Qk=
 


-Original Message-
From: Christian Schulte [mailto:c...@schulte.it] 
Sent: Friday, September 23, 2016 4:23 PM
To: Maven Users List
Cc: i...@soebes.de
Subject: Re: [EXTERNAL] Re: help with version range

Am 09/23/16 um 23:07 schrieb Robert Patrick:
> There is already a syntax to give you pre-release versions, right?  
> According to 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__maven.apache.org_ref_3.3.9_maven-2Dartifact_apidocs_org_apache_m=DQIFaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=5-lYd2DM46_1xLARlg3yqwPE5xDzWM8s_z59bPNPfQU=9TNP5ldPDafRzXnPjonmLhbp5M5SK1htUhzsTE-Xp4Y=
>  
> aven/artifact/versioning/ComparableVersion.html, the range 
> [1.0,2.0-SNAPSHOT] will give you the newest release including all 2.0 
> prerelease versions but not the 2.0 GA release so there is no reason 
> you need [1.0,2.0) to do the exact same thing... :-)
> 

I haven't tested this but I think what is written here also applies to Maven. 
You would need to test that yourself.



Regards,
--
Christian


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or

RE: [EXTERNAL] Re: help with version range

2016-09-23 Thread Justin Georgeson

Similarly I wouldn't want a range like "[1.2.0,1.3.0)" to give me a pre-release 
1.2.0 artifact. 

-Original Message-
From: Robert Patrick [mailto:robert.patr...@oracle.com] 
Sent: Friday, September 23, 2016 10:56 AM
To: Maven Users List
Subject: RE: [EXTERNAL] Re: help with version range

This does seem non-intuitive.If I say that I want versions  between 1.0 and 
up to but NOT including 2.0 by saying [1.0,2.0), in what use case would I ever 
want this to resolve to 2.0-SNAPSHOT or any other pre-release 2.0 artifact?  
Personally, I cannot think of a single one.

Typically, what I mean when I say [1.0,2.0) is any 1.x version but nothing 
related to 2.0...

-Original Message-----
From: Justin Georgeson [mailto:jgeorge...@lgc.com]
Sent: Friday, September 23, 2016 10:11 AM
To: Maven Users List
Subject: RE: [EXTERNAL] Re: help with version range

Yeah, I was hoping there was something more elegant like 1.1+ or something, so 
I can at least move forward with that.

Logically, does it make sense to resolve 1.2.0-alpha-1 when the user has 
excluded 1.2.0 from their range? If I explicitly don't want the release version 
why would I want the pre-release versions?

-Original Message-
From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf Of 
Curtis Rueden
Sent: Friday, September 23, 2016 9:01 AM
To: Maven Users List
Subject: [EXTERNAL] Re: help with version range

Hi Justin,

You could write "[1.1.0,1.1.9]", no? A bit hacky, but would match the 
versions you want in practice.

Regards,
Curtis

On Sep 23, 2016 8:38 AM, "Justin Georgeson" <jgeorge...@lgc.com> wrote:

> I’m using the parent version range feature with “[1.1.0,1.2.0)” and it 
> had been going well. However I wanted to start working on 1.2.0 of the 
> parent, so I published a 1.2.0-alpha-1 version. And all the projects 
> with te “[1.1.0,1.2.0)” picked it up. I recognize that this is in 
> keeping with the implementation that x.y.z-(alpha|beta|…) precedes 
> x.y.z, but it is unintuitive to me. First in that I’ve stated I don’t 
> want 1.2.0, and second that once I do release 1.2.0 the projects which 
> were receiving the alpha builds will not get 1.2.0. I tried with both
> 3.2.5 and 3.3.9. Can the version range syntax express the range I want?
>
>
>
> *Justin Georgeson*
> Landmark Cloud Platforms & DevOps - RM
>
> Email: *jgeorge...@lgc.com* <jgeorge...@lgc.com>
>
> Follow Halliburton: *LinkedIn*
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__logw332.ati-2Dhos
> t.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignature
> s-255d-26url-3Dhttp-3A__www.linkedin.com_company_halliburton=DQIFaQ&
> c=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OV
> ZL1uyui4QoEmBCjCmEiTk=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8=
> 9g208ksOttPVrCNlOx459-qzk0wWAei89_zhZnej5vM= >
> | *Facebook*
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__logw332.ati-2Dho
> st.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignatur
> es-255d-26url-3Dhttps-3A__www.facebook.com_halliburton=DQIFaQ=Pskv
> ixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyu
> i4QoEmBCjCmEiTk=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8=NgT-wO
> jrb7gpKDJVcRDMmKUQqGfR-PSnXe3I98Lp1c4= >
> | *Twitter*
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__logw332.ati-2Dho
> st.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignatur
> es-255d-26url-3Dhttps-3A__twitter.com_halliburton=DQIFaQ=PskvixtEU
> DK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoE
> mBCjCmEiTk=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8=-swEvm-8NW2
> 18tPAkOpg46kdPblTNts2y7dbe_w82wM= >
> | *YouTube*
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__logw332.ati-2Dhos
> t.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignature
> s-255d-26url-3Dhttp-3A__youtube.com_halliburton=DQIFaQ=PskvixtEUDK
> 7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmB
> CjCmEiTk=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8=dTvvV1RKdjYSK
> _Hc5JX55QI7b2j-A4O9RAX2Dg9qbrU= >
> | *Blog*
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__logw332.ati-2Dhos
> t.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignature
> s-255d-26url-3Dhttp-3A__halliburtonblog.com=DQIFaQ=PskvixtEUDK7wuW
> U-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCm
> EiTk=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8=Or-LJ9tIt99DaFT0-
> BpnvVYmC73xtz0gLUBwIg5Woho= >
>
>
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.landmark.sol
> utions_=DQIFaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM
> 3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=y4-iycjs7jCDUAa82A-SQP4DqefDD
> ZjCpFKXFWCrmu8=f4P54iKSAZYutrqVX1iHAWO9C7nP1vrd3OJGBT9g4LE

RE: [EXTERNAL] Re: help with version range

2016-09-23 Thread Justin Georgeson

Yeah, I was hoping there was something more elegant like 1.1+ or something, so 
I can at least move forward with that.

Logically, does it make sense to resolve 1.2.0-alpha-1 when the user has 
excluded 1.2.0 from their range? If I explicitly don't want the release version 
why would I want the pre-release versions?

-Original Message-
From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf Of 
Curtis Rueden
Sent: Friday, September 23, 2016 9:01 AM
To: Maven Users List
Subject: [EXTERNAL] Re: help with version range

Hi Justin,

You could write "[1.1.0,1.1.9]", no? A bit hacky, but would match the 
versions you want in practice.

Regards,
Curtis

On Sep 23, 2016 8:38 AM, "Justin Georgeson" <jgeorge...@lgc.com> wrote:

> I’m using the parent version range feature with “[1.1.0,1.2.0)” and it 
> had been going well. However I wanted to start working on 1.2.0 of the 
> parent, so I published a 1.2.0-alpha-1 version. And all the projects 
> with te “[1.1.0,1.2.0)” picked it up. I recognize that this is in 
> keeping with the implementation that x.y.z-(alpha|beta|…) precedes 
> x.y.z, but it is unintuitive to me. First in that I’ve stated I don’t 
> want 1.2.0, and second that once I do release 1.2.0 the projects which 
> were receiving the alpha builds will not get 1.2.0. I tried with both 
> 3.2.5 and 3.3.9. Can the version range syntax express the range I want?
>
>
>
> *Justin Georgeson*
> Landmark Cloud Platforms & DevOps - RM
>
> Email: *jgeorge...@lgc.com* <jgeorge...@lgc.com>
>
> Follow Halliburton: *LinkedIn*
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__logw332.ati-2Dhos
> t.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignature
> s-255d-26url-3Dhttp-3A__www.linkedin.com_company_halliburton=DQIFaQ&
> c=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OV
> ZL1uyui4QoEmBCjCmEiTk=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8=
> 9g208ksOttPVrCNlOx459-qzk0wWAei89_zhZnej5vM= >
> | *Facebook*
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__logw332.ati-2Dho
> st.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignatur
> es-255d-26url-3Dhttps-3A__www.facebook.com_halliburton=DQIFaQ=Pskv
> ixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyu
> i4QoEmBCjCmEiTk=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8=NgT-wO
> jrb7gpKDJVcRDMmKUQqGfR-PSnXe3I98Lp1c4= >
> | *Twitter*
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__logw332.ati-2Dho
> st.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignatur
> es-255d-26url-3Dhttps-3A__twitter.com_halliburton=DQIFaQ=PskvixtEU
> DK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoE
> mBCjCmEiTk=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8=-swEvm-8NW2
> 18tPAkOpg46kdPblTNts2y7dbe_w82wM= >
> | *YouTube*
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__logw332.ati-2Dhos
> t.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignature
> s-255d-26url-3Dhttp-3A__youtube.com_halliburton=DQIFaQ=PskvixtEUDK
> 7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmB
> CjCmEiTk=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8=dTvvV1RKdjYSK
> _Hc5JX55QI7b2j-A4O9RAX2Dg9qbrU= >
> | *Blog*
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__logw332.ati-2Dhos
> t.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignature
> s-255d-26url-3Dhttp-3A__halliburtonblog.com=DQIFaQ=PskvixtEUDK7wuW
> U-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCm
> EiTk=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8=Or-LJ9tIt99DaFT0-
> BpnvVYmC73xtz0gLUBwIg5Woho= >
>
>
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.landmark.sol
> utions_=DQIFaQ=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM
> 3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk=y4-iycjs7jCDUAa82A-SQP4DqefDD
> ZjCpFKXFWCrmu8=f4P54iKSAZYutrqVX1iHAWO9C7nP1vrd3OJGBT9g4LE= >
>
>
>
>
> --
> This e-mail, including any attached files, may contain confidential 
> and privileged information for the sole use of the intended recipient. 
> Any review, use, distribution, or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to receive 
> information for the intended recipient), please contact the sender by 
> reply e-mail and delete all copies of this message.
>

help with version range

2016-09-23 Thread Justin Georgeson

I'm using the parent version range feature with "[1.1.0,1.2.0)" and it had been 
going well. However I wanted to start working on 1.2.0 of the parent, so I 
published a 1.2.0-alpha-1 version. And all the projects with te "[1.1.0,1.2.0)" 
picked it up. I recognize that this is in keeping with the implementation that 
x.y.z-(alpha|beta|...) precedes x.y.z, but it is unintuitive to me. First in 
that I've stated I don't want 1.2.0, and second that once I do release 1.2.0 
the projects which were receiving the alpha builds will not get 1.2.0. I tried 
with both 3.2.5 and 3.3.9. Can the version range syntax express the range I 
want?



Justin Georgeson
Landmark Cloud Platforms & DevOps - RM

Email: jgeorge...@lgc.com<mailto:jgeorge...@lgc.com>


Follow Halliburton: 
LinkedIn<http://logw332.ati-host.net/gopc.url?xts=553058=EPR-25-%5bHAL-signatures%5d=http://www.linkedin.com/company/halliburton>
 | 
Facebook<https://logw332.ati-host.net/gopc.url?xts=553058=EPR-25-%5bHAL-signatures%5d=https://www.facebook.com/halliburton>
 | 
Twitter<https://logw332.ati-host.net/gopc.url?xts=553058=EPR-25-%5bHAL-signatures%5d=https://twitter.com/halliburton>
 | 
YouTube<http://logw332.ati-host.net/gopc.url?xts=553058=EPR-25-%5bHAL-signatures%5d=http://youtube.com/halliburton>
 | 
Blog<http://logw332.ati-host.net/gopc.url?xts=553058=EPR-25-%5bHAL-signatures%5d=http://halliburtonblog.com>



 
[http://www.halliburton.com/public/pubsdata/social_media/images/hal_lmk-200x15.jpg]
 <https://www.landmark.solutions/>




--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

RE: [EXTERNAL] re: re-using server credentials for repositories

2016-07-20 Thread Justin Georgeson

Thank you for the decisive answer on the current implementation. I definitely 
think making the mapping more automatic based on matching a pattern to the URL 
and/or specifying authentication realm for which the credentials apply is the 
best solution. That seems (to me) the most intuitive.

I'll start voting/commenting on related JIRA tickets.

> -Original Message-
> From: guillaume_b...@orange.fr [mailto:guillaume_b...@orange.fr] On
> Behalf Of Guillaume Boué
> Sent: Tuesday, July 19, 2016 7:31 PM
> To: Maven Users List <users@maven.apache.org>
> Subject: [EXTERNAL] re: re-using server credentials for repositories
> 
> Hi,
> 
> Looking at the code, there is really a one-to-one implicit mapping between the
> repository id and the server id used to look-up authentication information.
> 
> Maven adds to a DefaultAuthenticationSelector the server id [1] as key of a
> map Id -> authentication info [2]. Then, a possible authentication info is
> retrieved for a repository by asking it to the AuthenticationSelector for a 
> given
> repo [3], and this method internally fetches it from the repository id [4].
> 
> 
> 
> I didn't test with all Maven versions but with Maven 3, I'd expect an error. I
> tracked this commit [5] where you can see that the warning was changed to an
> error for Maven 3.0-alpha5.
> 
> 
> 
> Perhaps it would be possible to add an element "serverId" inside "repository"?
> Without it, default to the repository id as before and, with it, use it as 
> the key to
> search for the authentication info. I don't know about a possible road-map for
> this feature (or for MNG-5585).
> 
> 
> 
> [1]: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_apache_maven_blob_maven-2D3.3.9_maven-
> 2Dcore_src_main_java_org_apache_maven_internal_aether_DefaultRepositor
> ySystemSessionFactory.java-23L200=CwIFaQ=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm
> BCjCmEiTk=kxV_OBrfrqA3HJvQpLbw6RBzFx4wh2DAkwYYUa2HVbk=XOQr
> IG06vlPdi5Jhpu760B-ngiTlNdR_0ObF1fPN12I=
> [2]: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_eclipse_aether-2Dcore_blob_aether-
> 2D1.0.2.v20150114_aether-
> 2Dutil_src_main_java_org_eclipse_aether_util_repository_DefaultAuthenticati
> onSelector.java-23L40=CwIFaQ=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm
> BCjCmEiTk=kxV_OBrfrqA3HJvQpLbw6RBzFx4wh2DAkwYYUa2HVbk=RZRr-
> q_qRCC2RdCYeuKVTG1BAwKeZRf9o3t1IHCHI0w=
> [3]: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_apache_maven_blob_maven-2D3.3.9_maven-
> 2Dcore_src_main_java_org_apache_maven_bridge_MavenRepositorySystem.j
> ava-23L246=CwIFaQ=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm
> BCjCmEiTk=kxV_OBrfrqA3HJvQpLbw6RBzFx4wh2DAkwYYUa2HVbk=dvV7
> E6mQaTeMWRdJGuay6rltjw8KXYBNgwDWt7U2NXk=
> [4]: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_eclipse_aether-2Dcore_blob_aether-
> 2D1.0.2.v20150114_aether-
> 2Dutil_src_main_java_org_eclipse_aether_util_repository_DefaultAuthenticati
> onSelector.java-23L52=CwIFaQ=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm
> BCjCmEiTk=kxV_OBrfrqA3HJvQpLbw6RBzFx4wh2DAkwYYUa2HVbk=I_M3
> AFPTjkRHoDOEKTe13MTWPfEy573zQVQ2QDO1A00=
> [5]: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_apache_maven_commit_1068ab557c476a291f3f16bc2b2523d
> 5613c5e17-23diff-
> 2D62baa3a3145d2df18244b7d719fc9686L42=CwIFaQ=PskvixtEUDK7wuW
> U-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm
> BCjCmEiTk=kxV_OBrfrqA3HJvQpLbw6RBzFx4wh2DAkwYYUa2HVbk=8-
> vVUeqE0X9Nl8y3W1-CJEMBLhrVt0IeuDGpt7dc3us=
> 
> Regard,
> Guillaume
> 
> 
> 
> > Message du 19/07/16 23:57
> > De : "Justin Georgeson"
> > A : "Maven Users List"
> > Copie à :
> > Objet : re-using server credentials for repositories
> >
> >
> I’m curious why there doesn’t seem to be a way to reuse server credentials
> across multiple repositories (at least without a warning for those fortunate 
> few
> on stack-java-script who claim success). For reference I mean as exemplified 
> in
> [1], I have to define in my settings.xml a unique settings.servers.server for 
> each
> projects.repositories.repository in my pom.xml, even if the credentials are 
> the
> same. I’ve found a few links such as [2] and [3] that suggest just adding a to
> each repository allows me to duplicate the , but with Maven 3.2.5 and 3.3.9 I
> get a failure
> 
> [ERROR] 'repositories.repository.id' must be unique: artifactory-lmk ->
> https://urldefense.proofpoint.com/v2/url?u=http-
> 3A__

re-using server credentials for repositories

2016-07-19 Thread Justin Georgeson

I'm curious why there doesn't seem to be a way to reuse server credentials 
across multiple repositories (at least without a warning for those fortunate 
few on stack-overflow who claim success). For reference I mean as exemplified 
in [1], I have to define in my settings.xml a unique settings.servers.server 
for each projects.repositories.repository in my pom.xml, even if the 
credentials are the same. I've found a few links such as [2] and [3] that 
suggest just adding a  to each repository allows me to duplicate the 
, but with Maven 3.2.5 and 3.3.9 I get a failure

[ERROR] 'repositories.repository.id' must be unique: artifactory-lmk -> 
http://example.com/url1 vs http://example.com/url2 @ line 26, column 13

There's also [4] which says that nope, unique ID is required. Link [2] is the 
newest and Manfred says it works, and that's the accepted answer there. Does it 
only work for distributionManagement.repositories and not for 
build.repositories? Is there anything on the roadmap to address this in 
near-future release? There's MNG-5585 [5] which would side-step the issue by 
presumably letting the HTTP wagon match the correct credentials automatically 
by authentication realm, without the user having to map them out explicitly. 
That'd be nice.

[1] - https://maven.apache.org/guides/mini/guide-multiple-repositories.html
[2] - 
http://stackoverflow.com/questions/17511469/setting-a-single-server-credentials-in-maven-for-multiple-repositories
[3] - 
http://stackoverflow.com/questions/21836539/sonatype-nexus-how-to-set-a-single-server-credentials-for-multiple-repositories
[4] - http://stackoverflow.com/questions/15011250/maven-meaning-of-repository-id
[5] - https://issues.apache.org/jira/browse/MNG-5585



Justin Georgeson
Release Management

Email: jgeorge...@lgc.com<mailto:jgeorge...@lgc.com>
Office: +1 713-839-3010
Fax: +1 713-839-2285

Follow Halliburton: 
LinkedIn<http://logw332.ati-host.net/gopc.url?xts=553058=EPR-25-%5bHAL-signatures%5d=http://www.linkedin.com/company/halliburton>
 | 
Facebook<https://logw332.ati-host.net/gopc.url?xts=553058=EPR-25-%5bHAL-signatures%5d=https://www.facebook.com/halliburton>
 | 
Twitter<https://logw332.ati-host.net/gopc.url?xts=553058=EPR-25-%5bHAL-signatures%5d=https://twitter.com/halliburton>
 | 
YouTube<http://logw332.ati-host.net/gopc.url?xts=553058=EPR-25-%5bHAL-signatures%5d=http://youtube.com/halliburton>
 | 
Blog<http://logw332.ati-host.net/gopc.url?xts=553058=EPR-25-%5bHAL-signatures%5d=http://halliburtonblog.com>



 
[http://www.halliburton.com/public/pubsdata/social_media/images/hal_lmk-200x15.jpg]
 <https://www.landmarksoftware.com/>




--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

RE: [EXTERNAL] SCM APIs cause "ref HEAD is not a symbolic ref"

2016-06-15 Thread Justin Georgeson

Is the failure happening during CI with a shallow clone? I've seen a few systems

> -Original Message-
> From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On
> Behalf Of Simone Tripodi
> Sent: Tuesday, June 14, 2016 6:14 PM
> To: Maven Users List 
> Subject: [EXTERNAL] SCM APIs cause "ref HEAD is not a symbolic ref"
> 
> Hi all mates,
> I've been happily using the Maven SCM APIs to perform few operations "under
> the hood" for my users, everything was working fine until stumbled in the
> SCMException "Detecting the current branch failed: fatal: ref HEAD is not a
> symbolic ref"
> The scenario is: I am using the libraries below
> 
>
> org.apache.maven.scm
> maven-scm-api
> ${maven.scm.version}
> 
> 
> org.apache.maven.scm
> maven-scm-provider-gitexe
> ${maven.scm.version}
> 
> where 1.9.4, the sequence of
> operations that cause the error are:
> 
> ScmVersion version = new ScmTag(version);
> ScmResult result = scmManager.checkOut(repository, new
> ScmFileSet(appDir), version);
> ...
> result = scmManager.add(repository, new ScmFileSet(appDir, 
> newFile),
> commitMessage);
> ...
>result = scmManager.checkIn(repository, new ScmFileSet( 
> quickstartDir),
> version, commitMessage); The error happens when invoking the checkIn, do
> you have any recommendation on how to modify the operations sequence in
> order to make it working, when checking out a tag?
> 
> Many thanks in advance, all the best!
> -Simo
> 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__people.apache.org_-
> 7Esimonetripodi_=CwIBaQ=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm
> BCjCmEiTk=tM-
> Hfs5kq996kh6XWQPMEf0VpmT8uuezxYNm_GWNuv0=4ojqjCiL_L4n0-ZS5-
> nOZWuDL7KVEaCJAt4oj3oucyI=
> https://urldefense.proofpoint.com/v2/url?u=http-
> 3A__twitter.com_simonetripodi=CwIBaQ=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm
> BCjCmEiTk=tM-
> Hfs5kq996kh6XWQPMEf0VpmT8uuezxYNm_GWNuv0=wpUd7oZEIMSyoQq2a
> t3elxk9yOkeyR4NN6GUd3K8ahs=

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] mvn deploy without rebuilding?

2016-05-03 Thread Justin Georgeson

The deploy and install plugins act on attached artifacts, which I believe 
generally requires the package phase. For a given packaging type, there should 
be a plugin goal which is by default bound to the package phase to creates and 
attaches the artifacts for the project. So for a standard single-artifact jar 
project you would need to run something like 'jar:jar deploy:deploy' and it 
will repackage and deploy the jar file. If you're using Tycho I think it would 
be 'tycho-packaging:package-plugin deploy:deploy'. However if you have 
secondary artifacts like configuring an extra execution of jar:jar during the 
package phase to create a modified jar (maybe without the OSGi manifest headers 
for example) then those will be missed by explicitly running the packaging and 
deploying goals like this.

I'd suggest that when you're building a release candidate you build with the 
deploy phase so that they're all deployed to a standard M2 repo pro-actively as 
part of the normal Maven lifecycle. If you're concerned about plugins having 
been deployed from projects low in the reactor only for the overall build to 
fail higher in the reactor, look at the deploy plugin's deployAtEnd feature 
which delays deploying until all projects in the reactor have otherwise 
succeeded.

Also you could maybe create a deploy-only profile that executes the 
build-helper-maven-plugin to attach already-built packaged files and then the 
deploy:deploy plugin goal, binding both to an early phase like initialize so it 
doesn't redo any code generation or compilation. 

> -Original Message-
> From: thully [mailto:tmh...@eng.ucsd.edu]
> Sent: Monday, May 02, 2016 1:09 PM
> To: users@maven.apache.org
> Subject: [EXTERNAL] mvn deploy without rebuilding?
> 
> Hi,
> 
> Our project has many Maven artifacts, the vast majority of which are OSGi
> bundles. These bundles are distributed together as part of our application
> (Cytoscape), but may also be used by third-party developers using our API.
> 
> Given this, we have been deploying our artifacts to a Maven repository each
> time we make a new release of our application. However, we've run into an
> issue with this - every time we run mvn deploy, the bundles are rebuilt with
> new time-stamps and checksums. This makes it impossible to ensure that
> what's in the Maven repository matches a tested release version of the code
> unless we deploy when we build (suboptimal when we have code we're not sure
> is release-ready, but has non-SNAPSHOT version numbers in preparation for
> release).
> 
> I've seen that mvn deploy:deploy supposedly should do what we want (deploy
> without rebuilding). However, this fails on every one of our bundles with an
> error like the following:
> 
> "The packaging for this project did not assign a file to the build artifact."
> 
> mvn deploy:deploy-file works, but has to be done a file at a time with each
> POM and artifact specified on the command line. That would be a pain with
> 100+ artifacts/POMs in different locations. Does anybody know of a
> 100+ better
> way to do this?
> 
> 
> 
> --
> View this message in context: https://urldefense.proofpoint.com/v2/url?u=http-
> 3A__maven.40175.n5.nabble.com_mvn-2Ddeploy-2Dwithout-2Drebuilding-
> 2Dtp5866812.html=CwICAg=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm
> BCjCmEiTk=Xz_0L6GMpakwuIrvdS8rmwwVvG4ICSqiZEtDVJHMOs4=ZcThl
> 4rMzxKkMuZmrS5XqZjAKrgLV_EAYpkF0jKPy7g=
> Sent from the Maven - Users mailing list archive at Nabble.com.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] Re: "conditional" parent POM?

2016-03-10 Thread Justin Georgeson

Use a property for the URL, with the default in the pom set to a public Maven 
repository, and then in your settings.xml have a profile that sets the property 
to your internal repo URL, and activate the profile with the  
section of the settings.xml

> -Original Message-
> From: Max Spring [mailto:m2spr...@springdot.org]
> Sent: Thursday, March 10, 2016 4:39 PM
> To: users@maven.apache.org
> Subject: [EXTERNAL] Re: "conditional" parent POM?
> 
> Hi Curtis,
> 
> I don't want to have the URL of my in-house Maven repository manager out
> in the open.
> 
> Regards,
> -Max
> 
> 
> On 03/10/2016 12:29 PM, Curtis Rueden wrote:
> > Hi Max,
> >
> > Why do you need two different parents? What configuration is different
> > between your "wild" parent and your internal one?
> >
> > Would it be sufficient to enclose the internal-specific configuration
> > (e.g., distributionManagement) in a profile? This technique is what my
> > OSS projects do [1].
> >
> > Regards,
> > Curtis
> >
> > [1]
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_scijav
> > a_pom-2Dscijava_blob_pom-2Dscijava-2D9.6.0_pom.xml-23L1686-
> 2DL1701=C
> > wICaQ=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7
> > uKz_OVZL1uyui4QoEmBCjCmEiTk=q26B8pPsbJBwPvNe2YgwT4-
> T7fxuX6KEhm9sVrJS
> > KWs=jNLyxJFuERJhA4bv_2IVAUFuReUhwN4Btuj-I7G5QMo=
> >
> >
> > On Thu, Mar 10, 2016 at 2:20 PM, Max Spring 
> wrote:
> >
> >> What's the best structure for a (multi-module) Maven project which
> >> should build "in the wild" without any Maven repository manager and
> >> can easily build within my organization where deployments should
> >> happen to my Maven repository manager?
> >>
> >> Ideally, I would have two different paren POMs for each situation.
> >> But unfortunately, I can't use a Maven property to pass the correct
> >> value for each situation, because the property expression in the
> >> parent POM reference doesn't get interpolated, if I try something
> >> like
> >>
> >>
> >>  org.example
> >>  ${root.pom}
> >>  1.0-SNAPSHOT
> >>  
> >>
> >>...
> >>
> >>  wild-parent
> >>
> >>
> >> Added a minimalistic project which shows a crude approach to solve
> >> this by patching the parent POM via sed:
> >> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_m2spr
> >> ing_wild-2Dinhouse-2Dhybrid-
> 2Dexample=CwICaQ=PskvixtEUDK7wuWU-tIg
> >>
> 6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm
> BCjCmEiTk
> >> =q26B8pPsbJBwPvNe2YgwT4-
> T7fxuX6KEhm9sVrJSKWs=T9sLgQIupfXCVV3jLJgO
> >> Jm0tcc8qulu_xD4TN7YyI5Q=
> >>
> >> -Max
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] How best to override maven-javadoc-plugin to do nothing?

2016-01-14 Thread Justin Georgeson

Try setting property maven.javadoc.skip to true in your pom.xml

https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#skip
https://maven.apache.org/plugins/maven-javadoc-plugin/jar-mojo.html#skip


> -Original Message-
> From: David M. Karr [mailto:davidmichaelk...@gmail.com]
> Sent: Thursday, January 14, 2016 4:36 PM
> To: users@maven.apache.org
> Subject: [EXTERNAL] How best to override maven-javadoc-plugin to do
> nothing?
> 
> Simple question: How do I best override the maven-javadoc-plugin to make
> it do nothing?
> 
> I'm integrating a non-API project into a much larger build where everything
> else is an API, so maven-javadoc-plugin is specified in the parent.  It would 
> be
> best to just have it not run javadoc on this project, or do nothing.
> 
> Is the best strategy to specify "*" for the "excludePackageNames" property?
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org

RE: profile activation with multiple conditions

2015-11-10 Thread Justin Georgeson

So here's a minimal parent pom.xml, which lists 2 child modules that I created 
with 'mvn archetype:generate' choosing the 'maven-archetype-quickstart' 
archetype. My goal was that if I 

mvn package

Then the compile/test/package occurs with no attempt to sign. But then by 
changing the command to 

mvn package -Djarsigner.keystore.scm.url=... 
-Djarsigner.keystore.scm.user=... -Djarsigner.keystore.scm.password=... \
 -Djarsigner.storepass=...

Then it checks out a single copy of the keystore during the package phase of 
the parent project, and the jarsigner profile automatically activates during 
each of the modules due to the presence of the keystore file.

Instead it's deleting the keystore and checking out the keystore file during 
every project (or instead of and of profile activation conditions), and the 
jarsigner profile is not automatically activated.

> -Original Message-
> From: Justin Georgeson [mailto:jgeorge...@lgc.com]
> Sent: Friday, November 06, 2015 9:39 AM
> To: Maven Users List
> Subject: [EXTERNAL] RE: profile activation with multiple conditions
> 
> Sorry about that crazy URL, I think that's a network security service my
> employer just signed up with.
> 
> > -Original Message-
> > From: Justin Georgeson [mailto:jgeorge...@lgc.com]
> > Sent: Friday, November 06, 2015 9:34 AM
> > To: users@maven.apache.org
> > Subject: [EXTERNAL] profile activation with multiple conditions
> >
> > I have a profile defined in my parent POM which I'm trying to activate
> > like this
> >
> > 
> > 
> > jarsigner.keystore.scm.url
> > 
> > 
> > ${keystore.dir}
> > 
> > 
> >
> > The goal is that when run with -Djarsigner.keystore.scm.url the
> > keystore will be checked out from SCM, but I don't want it to do that
> > for every module in a multi-module build. I thought that activation
> > was switched from OR to AND in 3.2.2[1] but I'm using 3.2.5 and I'm
> > seeing this profile as active when the property is set even though the
> > path exists. I thought maybe it's because ${keystore.dir} is a folder
> > instead of a file, so I tried it with a file but that had no effect. I
> > can work around it by having an extra checkout in the CI configuration
> > but I'd prefer to keep it self-contained in the 'mvn package' lifecycle of 
> > the
> build.
> >
> > [1] https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__issues.apache.org_jira_browse_MNG-
> > 2D4565=CwIFAg=PskvixtEUDK7wuWU-
> >
> tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm
> >
> BCjCmEiTk=qSnekx007UIfFuC5Su7wwnAxDOG6yBCpBC5PyZFv2d0=ypg5E
> > ApiZkSAidXlZV394CNaIG3j8JF9HTM0DLm3rRQ=
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org

http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
com.lgc
parent
1.0.0-SNAPSHOT
pom

module1
module2



keystore


jarsigner.keystore.scm.url


${user.dir}/target/keystore/iacode.keystore





maven-scm-plugin
1.9.1


scm-get-keystore
prepare-package

export


${jarsigner.keystore.scm.url}
${user.dir}/target/keystore
${jarsigner.keystore.scm.user}
${jarsigner.keystore.scm.password}








jarsigner


${user.dir}/target/keystore/iacode.keystore





org.apache.maven.plugins
maven-jarsigner-plugin
1.3.2

RE: [EXTERNAL] RE: profile activation with multiple conditions

2015-11-10 Thread Justin Georgeson

Thanks. I was hoping that it would evaluate the file-based activation per 
project. I was treating it as a separate issue than the multiple conditions. 
But I think what you're saying is that the profile activation happens once for 
the whole reactor, and not per project within the reactor. I gather that you're 
saying if the keystore file doesn't exist when I first run maven, then the 
keystore profile will be activated for all projects in the reactor. Is that 
correct? I'm still seeing the keystore profile activate from the property alone 
even if the keystore file already exists before I run the mvn command. So that 
still suggests that it's doing an or of the conditions rather than an and. 
Running 'mvn -N -X help:active-profiles -Djarsigner.keystore.scm.url' isn't 
giving any debug info on the profile activation unfortunately. 

My goal here is to have as much of the build process as possible self-contained 
in the POM files and executed from a single mvn command.

> -Original Message-
> From: Jörg Schaible [mailto:joerg.schai...@gmx.de]
> Sent: Tuesday, November 10, 2015 4:26 PM
> To: users@maven.apache.org
> Subject: [EXTERNAL] RE: profile activation with multiple conditions
> 
> Justin Georgeson wrote:
> 
> > So here's a minimal parent pom.xml, which lists 2 child modules that I
> > created with 'mvn archetype:generate' choosing the
> > 'maven-archetype-quickstart' archetype. My goal was that if I
> >
> > mvn package
> >
> > Then the compile/test/package occurs with no attempt to sign. But then
> > by changing the command to
> >
> > mvn package -Djarsigner.keystore.scm.url=...
> > -Djarsigner.keystore.scm.user=... -Djarsigner.keystore.scm.password=... \
> >  -Djarsigner.storepass=...
> >
> > Then it checks out a single copy of the keystore during the package
> > phase of the parent project, and the jarsigner profile automatically
> > activates during each of the modules due to the presence of the keystore 
> > file.
> >
> > Instead it's deleting the keystore and checking out the keystore file
> > during every project (or instead of and of profile activation
> > conditions), and the jarsigner profile is not automatically activated.
> 
> Profile activation is quite the first thing Maven does. So, the file has to be
> already there when Maven starts.
> 
> Form your description I got the impression that you "create" somehow the file
> during the build and expects then that Maven takes it into consideration for
> profile activation. That will never happen. And this has nothing to do with
> multiple profile conditions.
> 
> Cheers,
> Jörg
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org

profile activation with multiple conditions

2015-11-06 Thread Justin Georgeson

I have a profile defined in my parent POM which I'm trying to activate like this



jarsigner.keystore.scm.url


${keystore.dir}



The goal is that when run with -Djarsigner.keystore.scm.url the keystore will 
be checked out from SCM, but I don't want it to do that for every module in a 
multi-module build. I thought that activation was switched from OR to AND in 
3.2.2[1] but I'm using 3.2.5 and I'm seeing this profile as active when the 
property is set even though the path exists. I thought maybe it's because 
${keystore.dir} is a folder instead of a file, so I tried it with a file but 
that had no effect. I can work around it by having an extra checkout in the CI 
configuration but I'd prefer to keep it self-contained in the 'mvn package' 
lifecycle of the build.

[1] https://issues.apache.org/jira/browse/MNG-4565

RE: profile activation with multiple conditions

2015-11-06 Thread Justin Georgeson

Sorry about that crazy URL, I think that's a network security service my 
employer just signed up with.

> -Original Message-
> From: Justin Georgeson [mailto:jgeorge...@lgc.com]
> Sent: Friday, November 06, 2015 9:34 AM
> To: users@maven.apache.org
> Subject: [EXTERNAL] profile activation with multiple conditions
> 
> I have a profile defined in my parent POM which I'm trying to activate like 
> this
> 
> 
> 
> jarsigner.keystore.scm.url
> 
> 
> ${keystore.dir}
> 
> 
> 
> The goal is that when run with -Djarsigner.keystore.scm.url the keystore will 
> be
> checked out from SCM, but I don't want it to do that for every module in a
> multi-module build. I thought that activation was switched from OR to AND in
> 3.2.2[1] but I'm using 3.2.5 and I'm seeing this profile as active when the
> property is set even though the path exists. I thought maybe it's because
> ${keystore.dir} is a folder instead of a file, so I tried it with a file but 
> that had no
> effect. I can work around it by having an extra checkout in the CI 
> configuration
> but I'd prefer to keep it self-contained in the 'mvn package' lifecycle of the
> build.
> 
> [1] https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__issues.apache.org_jira_browse_MNG-
> 2D4565=CwIFAg=PskvixtEUDK7wuWU-
> tIg6oKuGYBRbrMXk2FZvF0UfTo=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm
> BCjCmEiTk=qSnekx007UIfFuC5Su7wwnAxDOG6yBCpBC5PyZFv2d0=ypg5E
> ApiZkSAidXlZV394CNaIG3j8JF9HTM0DLm3rRQ=


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] Re: POM file downloaded by Maven different than what was deployed.

2015-09-23 Thread Justin Georgeson

Good idea. The wireshark packet reassembly suggests that it's the 'magic' is 
happening on the server side. So will have to wait for reply from jFrog.

> -Original Message-
> From: Wayne Fay [mailto:wayne...@gmail.com]
> Sent: Wednesday, September 23, 2015 2:57 PM
> To: Maven Users List
> Subject: [EXTERNAL] Re: POM file downloaded by Maven different than
> what was deployed.
> 
> > I have a parent pom deployed to Artifactory (3.9.3), which when
> > downloaded into local Maven repo by Maven itself (3.2.5, as a normal
> > part of the Maven build lifecycle), is not the same as what is
> > deployed. If I download the
> 
> Maybe also try watching/capturing the network traffic to confirm what is
> being received by the Maven process on your local machine...?
> 
> Wayne
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org


--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

RE: [EXTERNAL] Re: POM file downloaded by Maven different than what was deployed.

2015-09-23 Thread Justin Georgeson

Just found this

http://dev.eclipse.org/mhonarc/lists/tycho-user/msg02463.html

Turns out it's a configurable behavior when using Artifactory's virtual 
repository feature. After disabling that it's working. 

> -Original Message-
> From: Justin Georgeson [mailto:jgeorge...@lgc.com]
> Sent: Wednesday, September 23, 2015 4:15 PM
> To: Maven Users List
> Subject: RE: [EXTERNAL] Re: POM file downloaded by Maven different than
> what was deployed.
> 
> Good idea. The wireshark packet reassembly suggests that it's the 'magic' is
> happening on the server side. So will have to wait for reply from jFrog.
> 
> > -Original Message-
> > From: Wayne Fay [mailto:wayne...@gmail.com]
> > Sent: Wednesday, September 23, 2015 2:57 PM
> > To: Maven Users List
> > Subject: [EXTERNAL] Re: POM file downloaded by Maven different than
> > what was deployed.
> >
> > > I have a parent pom deployed to Artifactory (3.9.3), which when
> > > downloaded into local Maven repo by Maven itself (3.2.5, as a normal
> > > part of the Maven build lifecycle), is not the same as what is
> > > deployed. If I download the
> >
> > Maybe also try watching/capturing the network traffic to confirm what
> > is being received by the Maven process on your local machine...?
> >
> > Wayne
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> --
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient.  Any
> review, use, distribution, or disclosure by others is strictly prohibited.  
> If you
> are not the intended recipient (or authorized to receive information for the
> intended recipient), please contact the sender by reply e-mail and delete all
> copies of this message.

POM file downloaded by Maven different than what was deployed.

2015-09-23 Thread Justin Georgeson

I have a parent pom deployed to Artifactory (3.9.3), which when downloaded into 
local Maven repo by Maven itself (3.2.5, as a normal part of the Maven build 
lifecycle), is not the same as what is deployed. If I download the file 
directly with curl, I get the expected file. I have confirmed that the file put 
in my local cache from a 'mvn install' or 'mvn deploy' is the unmodified file, 
and the file deployed in Artifactory is also correct. The .sha1 file in my 
local M2 cache has a different value than the SHA1 reported for this file in 
artifactory. It _mostly_ looks like innocuous XML cleanup (replacing 
 with  and removing newlines between attributes in elements 
leaving a very long line that had been formatted for readability. The part that 
caused me to even look into this is I have a  element which is 
being completely removed from the copy that Maven downloads into the M2 cache, 
so my build fails because it can't find any dependencies. However this does not 
happen if I put the  in a profile. Attached is a stripped down 
version of the pom which exhibits the problem for me (internal hostnames in the 
url have been sanitized with art.example.com, releaseName property is set in 
the aggregator/parent POM of each source repository, and if necessary the 
eclipse.release property is overridden in the same pom.xml as releaseName, the 
p2.type is set on the command-line in CI so developers get the URL it).



I've already emailed jFrog to see if it's on the Artifactory end but I get the 
right file when I download it with anything other than Maven. Wanted to cover 
my bases for fast resolution by checking here too.

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.
http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0

com.lgc
master
1.1.0-SNAPSHOT
pom


juno


0.22.0





org.eclipse.tycho
tycho-maven-plugin
${tychoVersion}
true
true


org.eclipse.tycho
target-platform-configuration
${tychoVersion}

p2
JavaSE-1.8

linuxgtkx86








rm_daily
rm_daily
p2
http://art.example.com/artifactory/OSGI/daily/${releaseName}/${p2.type}/


eclipse.platform
eclipse.platform
p2
http://art.example.com/artifactory/eclipse-${eclipse.release}/

 



snapshots
art.example.com-releases
http://art.example.com/artifactory/maven-lgc


snapshots
art.example.com-snapshots
http://art.example.com/artifactory/maven-lgc




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] Re: Use 2 pom.xml files with different names

2015-08-10 Thread Justin Georgeson

Do you have the same groupId, artifactId, and version specified in both POM 
files?

 -Original Message-
 From: Alex Ditu [mailto:ditu.alexan...@gmail.com]
 Sent: Monday, August 10, 2015 10:17 AM
 To: Maven Users List
 Subject: [EXTERNAL] Re: Use 2 pom.xml files with different names

 So the answer is: one cannot use a pom file with a different name than
 'pom.xml'.

 In such case, why the -f option exists?
 On Aug 10, 2015 6:13 PM, Benson Margulies bimargul...@gmail.com
 wrote:

  On Mon, Aug 10, 2015 at 11:04 AM, Alex Ditu ditu.alexan...@gmail.com
  wrote:
   I know how to solve my problem (by changing the project configuration).

   My question is: why mvn -f otherPomName.xml deploy doesen't work?
   And I said above how it fails.

  It does not _fail_. It does precisely what it is designed to do.

  mvn -f says, 'read the model of this project from an alternative
  location, and then do what you do.'

  Once Maven has read the XML, it has no idea where the file came from,
  and it's not supposed to have any idea where the file came from.
  Maven's job is to do the build as specified by the POM abstract data
  model. That makes no provisions for your scheme.

   On Aug 10, 2015 5:59 PM, Barrie Treloar baerr...@gmail.com wrote:

   On 10 August 2015 at 23:22, Alex Ditu ditu.alexan...@gmail.com
 wrote:

Ok, look what I am trying to achieve: I have a project with 2
profileDeployments (it produces 2 types of artifacts: a jar and a
war) but from the same sources. So, I did the following thing: I
have written 2 pom.xml files with 2 different names (for example:
pom.xml and pom2.xml). When I want to build the .jar artifact I
would use the command 'mvn deploy' when I want the .war artifact
I would use: 'mvn -f pom2.xml' --- after this, I encounter the
problem I mentioned earlier.

Note that the artifactIds are different.

   You solution is simple: do not have one project, split it into
   multiple projects.

   A war file should not have any java code in it. So there is no need
   for
  you
   do be having two poms. You war project depends on the jar project
   and
  you
   are done.

   There are plenty of examples on how to do this in the freely
   available maven books at http://maven.apache.org/articles.html

  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] Re: mvn deploy:deploy-file with same groupId artifactId but different classifiers

2015-06-29 Thread Justin Georgeson

Regardless of using Maven, I've always felt that for a multi-platform codebase, 
a build isn't successful/publishable/shippable if it hasn't succeeded on all 
required platforms (if the fix requires a change in the source code). So I've 
always favored the gather-and-deploy approach.

 -Original Message-
 From: Francois Marot [mailto:francois.ma...@gmail.com]
 Sent: Monday, June 29, 2015 9:50 AM
 To: Maven Users List
 Subject: [EXTERNAL] Re: mvn deploy:deploy-file with same groupId 
 artifactId but different classifiers

 @Jeff, thank you I think I'll try that. I thnink it will solve my problem
 @Wolf: you're totally right. That is the only solution I thought of before 
 Jeff's.
 It's the cleaner solution, but as I'm in the middle of a migration, I will 
 take
 some shortcuts to finish sooner. But at the same time I fear the obscure
 behaviour. Hope I won't face it soon ;)
 @Sandra: no problem, at least thanks for helping !

 On a more general discussion, what do you people think ? Is Wolf's solution
 the closest to The Maven Way™ or is Jeff's solution totally acceptable (even 
 if
 it's not, I'll take it for now !) ?

 - - - - -

 *François Marot06-50-91-96-38*

 On 29 June 2015 at 11:18, Jeff MAURY jeffma...@jeffmaury.com wrote:

  I think you should have a look at the generatePom parameter (

  https://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-
 mojo.
  html#generatePom
  )
  which is true by default and should be false for the second call.

  Jeff

  On Mon, Jun 29, 2015 at 11:11 AM, Francois Marot
  francois.ma...@gmail.com

  wrote:

   Thanks Sandra,

   but I'm not sure I understand: I already use the -Dclassifier=
   parameter
  in
   the 2 command I copy/pasted above.
   Do you mean setting linux/windows instead of
   natives-linux/natives-win would change something ? I think
  classifiers
   are form-free and I kind of need the prefix native- in front of
   it so that other parts of the build can handle those dependencies as
   native
  ones
   (for example this plugni: https://code.google.com/p/mavennatives/)

   - - - - -

   *François Marot06-50-91-96-38*

   On 29 June 2015 at 09:57, Sandra Parsick spars...@web.de wrote:

Hi,

you can use the property -Dclassifier. For the Linux build I would
use -Dclassifier=linux and for the Windows build -Dclassifier=win.

Best regards,

Sandra

Am 29.06.2015 um 09:53 schrieb Francois MAROT:
 Hello all,

 I'm in the process of converting an existing build to Maven. I
 have
 2 Jenkins jobs building the same native library on 2 different
 systems (win / lin). At the end of each one, I want to deploy
 them on my Archiva repo. So I execute the following commands :

 On a Linux computer: mvn deploy:deploy-file
 -Dfile=myLib-x64-natives-linux.zip -Dclassifier=natives-linux
 -DgroupId=com.myCompany  -DartifactId=myLib -Dversion=1.0.0
 -DrepositoryId=archiva.internal
 -Durl=http://centos-dev:8090/repository/internal/

 On a Windows computer: mvn deploy:deploy-file
 -Dfile=jre-x64-natives-win.zip -Dclassifier=natives-win
 -DgroupId=com.myCompany  -DartifactId=myLib -Dversion=1.0.0
 -DrepositoryId=archiva.internal
 -Durl=http://centos-dev:8090/repository/internal/

 Problem is the second command leads to a build failed because
 the pom of the project in version 1.0.0 is already deployed...
 BUT, I am lucky because the artifact with classifier
 natives-win has already been uploaded so both artifact end up
 on the server correctly. So builds depending on them can
 retreive them correctly and everything is fine... ... except
 that I don't want to base my build on luck and would like to
 know what is the correct way to deploy 2 artifacts with
 everything being the same except the qualifier.

 How do you pepole deploy a same artifact but built by different
 computers, architectures ?

 I'm using Maven 3.3.1  Apache Archiva 2.1.1

 -- View this message in context:

  http://maven.40175.n5.nabble.com/mvn-deploy-deploy-file-with-same-
 grou
  pId-artifactId-but-different-classifiers-tp5838931.html

Sent from the Maven - Users mailing list archive at Nabble.com.

 -

To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

--
--- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

  --
  Jeff MAURY

  Legacy code often differs from its suggested alternative by actually
  working and scaling.
   - Bjarne Stroustrup

  http://www.jeffmaury.com

RE: [EXTERNAL] dependency management with ant quick question

2015-05-14 Thread Justin Georgeson

Thanks for the correction. 

 -Original Message-
 From: Manfred Moser [mailto:manf...@mosabuam.com]
 Sent: Wednesday, May 13, 2015 11:20 PM
 To: users@maven.apache.org
 Subject: Re: [EXTERNAL] dependency management with ant quick question

 Do NOT use the Maven Ant tasks.. they are outdated and based on Maven 2.

 Instead use the dep resolution library used in Maven itself called Eclipse
 Aether and its Ant tasks..

 http://eclipse.org/aether/

 http://wiki.eclipse.org/Aether/Ant_Tasks

 Zk W wrote on 13.05.2015 20:25:

  Hi Justin

  Thanks for replying.
  Let us think more of your suggestion here and update.

  Thanks

  On Wed, May 13, 2015 at 8:14 PM, Justin Georgeson
 jgeorge...@lgc.com
  wrote:

  https://maven.apache.org/ant-tasks/

  1. There is a task to resolve/retrieve dependencies.

  2. The dependency task can create classpath and fileset refids for
  the dependencies, and per-dependency properties, so you shouldn't
  have to worry about copy jars to and fro.

  3. There are examples at the link above.

  From: Zk W [mpc8...@gmail.com]
  Sent: Wednesday, May 13, 2015 10:00 PM
  To: users@maven.apache.org
  Subject: [EXTERNAL] dependency management with ant quick question

  Hi All

  We are new to Maven and we are an ant shop.
  We like to use Maven's dependency management feature, not ivy.

  1- Can we just use Maven's dependency management feature to work
 with
  our ant build script ?

  2- Since .m2 is the default folder for all the jars, do we use ant
  copy task to copy jars from .m2 folder to different project folders
  to compile properly ?

  3. Are there examples out there that use ant for build purpose in
  conjunction with maven's dependency management ?

  Thank you.

  -
  - This e-mail, including any attached files, may contain confidential
  and privileged information for the sole use of the intended
  recipient.  Any review, use, distribution, or disclosure by others is
  strictly prohibited.
  If you are not the intended recipient (or authorized to receive
  information for the intended recipient), please contact the sender by
  reply e-mail and delete all copies of this message.

  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: [EXTERNAL] dependency management with ant quick question

2015-05-13 Thread Justin Georgeson

https://maven.apache.org/ant-tasks/ 

1. There is a task to resolve/retrieve dependencies.

2. The dependency task can create classpath and fileset refids for the 
dependencies, and per-dependency properties, so you shouldn't have to worry 
about copy jars to and fro.

3. There are examples at the link above.


From: Zk W [mpc8...@gmail.com]
Sent: Wednesday, May 13, 2015 10:00 PM
To: users@maven.apache.org
Subject: [EXTERNAL] dependency management with ant quick question

Hi All

We are new to Maven and we are an ant shop.
We like to use Maven's dependency management feature, not ivy.

1- Can we just use Maven's dependency management feature to work with our
ant build script ?

2- Since .m2 is the default folder for all the jars, do we use ant copy
task to copy jars from .m2 folder to different project folders to compile
properly ?

3. Are there examples out there that use ant for build purpose in
conjunction with maven's dependency management ?

Thank you.

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

deploy and include properties files along with parent POM

2014-11-06 Thread Justin Georgeson

We have an organizational parent POM deployed to Artifactory, 
com.lgc:master:1.0.0-SNAPSHOT. The top-level aggregator POM in each repo uses 
this as the parent, with relativePath/. Then the individual projects in that 
repo use the aggregator as the parent. In the com.lgc:master POM I would like 
to have something like this

properties
globalProp1defaultValue/globalProp1

/properties

profiles
profile
idproduct-properties/id
activation
file${productName}.properties/file
activation
build
filters
filter${productName}.properties/filter
/filters
/build
/profile
/profiles

Each of these properties files would just be overriding the global defaults, 
and only when necessary. I want those properties files to be deployed to 
Artifactory as secondary artifacts to the com.lgc:master POM so that no matter 
what subfolder/repo someone is building in, it's consistent and predictable. I 
know how to do the deploy? but how do I specify the path to the properties 
files. Are secondary artifacts automatically retrieved or is there something 
special I need to setup?

Or if I'm going about this all wrong, feel free to say so and point me in the 
right direction [1].

Thanks,
-Justin

[1] - When I said the individual projects use the aggregator as the parent, you 
might suggest just putting the properties in the aggregator. The caveat here is 
that in a few places we have a mostly empty SVN repo with the aggregator POM, 
the folder structure, and a ton of svn:externals to the individual projects (so 
essentially an aggregator _repo_). We end up sometimes using a common branch of 
some of the projects in 2 or more aggregator repos because the only thing we 
would need to branch them for is to change the parent GAV, but we can't put a 
property reference in the parent section of the pom, so those projects only 
have the 'correct' aggregator POM GAV as the parent in at most one aggregator 
repo. So we can't reliably set properties in the aggregator POMs, so they have 
to be in either the com.lgc:master or directly in the 
jar|war|eclipse-plugin|etc POM files (which would be horrible to have all that 
redundancy) to be reliably set. 

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

jarsigner plugin: specifying multiple arguments on the CLI

2014-09-11 Thread Justin Georgeson

Apologies if this has been answered before. I don't see an entry in the plugin 
page's FAQ and find it with a quick Google search. I am behind a proxy so in 
order to specify a TSA I need to use -J-Dhttp.proxyHost=host 
-J-Dhttp.proxyPort=port as arguments. If I use -Djarsigner.arguments=... 
then it seems to enclose the whole value in single quotes on the exec'ed 
jarsign command, and soe the command fails. If I specify the two arguments in 
my pom (as an array), it works. So how do I specify multiple arguments on the 
command line?

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

RE: Jococo report using Jenkins without the need to configure jacoco-maven-plugin? possible?

2014-08-06 Thread Justin Georgeson

I believe you still need to configure jacoco-maven-plugin so that your tests 
are run with instrumentation, but you don't need to do the reporting part with 
maven. Jenkins will read the .exec file that Jacoco generates during test 
execution and publish reports from that. 

 -Original Message-
 From: Dan Tran [mailto:dant...@gmail.com]
 Sent: Tuesday, August 05, 2014 9:31 PM
 To: Maven Users List
 Subject: Jococo report using Jenkins without the need to configure jacoco-
 maven-plugin? possible?

 Hello,

 I have an impression that I dont need bring in jacoco-maven-plugin to my
 poms, and just have Jenkins to run it at post build and magic will happen at
 Jenkins page.

 So far, I have no luck with that

 Any got this working?

 Thanks

 -Dan

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

RE: MD5 checksum validation tool [Windows]?

2014-08-05 Thread Justin Georgeson

Yeah, I was just hoping someone else here had already invented/discovered this 
wheel.

 -Original Message-
 From: Wayne Fay [mailto:wayne...@gmail.com]
 Sent: Tuesday, August 05, 2014 8:58 AM
 To: Maven Users List
 Subject: Re: MD5 checksum validation tool [Windows]?

 Perhaps you need to whip something up then? I'm sure it would not be
 terribly difficult. All the source code for the md5 checking is open source, 
 so
 you just need to pretty it up with a front end.

 Even better (from my POV) would be a tool that could be run and take a
 directory/path as input, then run across all .md5 files it ran across with
 optional recursion.

 Wayne

 On Mon, Aug 4, 2014 at 11:41 AM, Justin Georgeson jgeorge...@lgc.com
 wrote:

  Thanks Paul. I don't see HashTab as being able to directly read the
  .md5 file. Users would have to open the .md5 file in a text editor,
  then copy/paste. And sadly this tiny bit of effort is actually being
  deemed an undue burden. It literally has to be as simple as
  double-click the .md5 file and get nice green graphic that says
  everything is ok. HashCheck is the tool people are wanting to use, but
  that requires the relative path be included in the md5 file. I've
  submitted an enhancement request but their last release was in 2009 so
 I'm not hopeful.

   -Original Message-
   From: paulus.benedic...@gmail.com
   [mailto:paulus.benedic...@gmail.com]
   On Behalf Of Paul Benedict
   Sent: Monday, August 04, 2014 11:18 AM
   To: Maven Users List
   Subject: Re: MD5 checksum validation tool [Windows]?

   Yup. I've used HashTab for years.
   http://www.implbits.com/hashtab.aspx

   Cheers,
   Paul

   On Mon, Aug 4, 2014 at 11:16 AM, Justin Georgeson
   jgeorge...@lgc.com
   wrote:

All the checksum validation tools I've found only seem to support
files with format produced by the md5sum tool, ie -

checksum1 relative/path/file1
checksum2 relative/path/to/file2
...

But Maven publishes sibling files of the same name with .md5
appended, and no relative path in the file. Does anyone know of a
tool on Windows (shell extension, standalone GUI) that people
could use after downloading the artifact (in this particular case
it's an executable installer) and the
md5 file and just double-click the md5 file to validate the
download (or drag/drop the artifact and md5 file)?

--
 This e-mail, including any attached files, may contain
confidential and privileged information for the sole use of the
intended recipient.
Any review, use, distribution, or disclosure by others is strictly
  prohibited.
 If you are not the intended recipient (or authorized to receive
information for the intended recipient), please contact the sender
by reply e-mail and delete all copies of this message.

  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

MD5 checksum validation tool [Windows]?

2014-08-04 Thread Justin Georgeson

All the checksum validation tools I've found only seem to support files with 
format produced by the md5sum tool, ie -

checksum1 relative/path/file1
checksum2 relative/path/to/file2
...

But Maven publishes sibling files of the same name with .md5 appended, and no 
relative path in the file. Does anyone know of a tool on Windows (shell 
extension, standalone GUI) that people could use after downloading the artifact 
(in this particular case it's an executable installer) and the md5 file and 
just double-click the md5 file to validate the download (or drag/drop the 
artifact and md5 file)?

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

RE: MD5 checksum validation tool [Windows]?

2014-08-04 Thread Justin Georgeson

Thanks Paul. I don't see HashTab as being able to directly read the .md5 file. 
Users would have to open the .md5 file in a text editor, then copy/paste. And 
sadly this tiny bit of effort is actually being deemed an undue burden. It 
literally has to be as simple as double-click the .md5 file and get nice green 
graphic that says everything is ok. HashCheck is the tool people are wanting to 
use, but that requires the relative path be included in the md5 file. I've 
submitted an enhancement request but their last release was in 2009 so I'm not 
hopeful.

 -Original Message-
 From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com]
 On Behalf Of Paul Benedict
 Sent: Monday, August 04, 2014 11:18 AM
 To: Maven Users List
 Subject: Re: MD5 checksum validation tool [Windows]?
 
 Yup. I've used HashTab for years.
 http://www.implbits.com/hashtab.aspx
 
 
 Cheers,
 Paul
 
 
 On Mon, Aug 4, 2014 at 11:16 AM, Justin Georgeson jgeorge...@lgc.com
 wrote:
 
  All the checksum validation tools I've found only seem to support
  files with format produced by the md5sum tool, ie -
 
  checksum1 relative/path/file1
  checksum2 relative/path/to/file2
  ...
 
  But Maven publishes sibling files of the same name with .md5
  appended, and no relative path in the file. Does anyone know of a tool
  on Windows (shell extension, standalone GUI) that people could use
  after downloading the artifact (in this particular case it's an
  executable installer) and the
  md5 file and just double-click the md5 file to validate the download
  (or drag/drop the artifact and md5 file)?
 
  --
  This e-mail, including any attached files, may contain confidential
  and privileged information for the sole use of the intended recipient.
  Any review, use, distribution, or disclosure by others is strictly 
  prohibited.
   If you are not the intended recipient (or authorized to receive
  information for the intended recipient), please contact the sender by
  reply e-mail and delete all copies of this message.
 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: MD5 checksum validation tool [Windows]?

2014-08-04 Thread Justin Georgeson

Thanks, but the MD5 checksums file for the Tomcat installers have the filename
in them (in the contents of the .md5 file, versus implied by the name of the
.md5 file)

https://www.apache.org/dist/tomcat/tomcat-8/v8.0.9/bin/apache-tomcat-8.0.9.zip.md5

versus

http://repo.maven.apache.org/maven2/org/eclipse/tycho/org.eclipse.tycho.embedder.shared/0.20.0/org.eclipse.tycho.embedder.shared-0.20.0.jar.md5

The Tomcat md5 file is one that a tool like md5sum generates, and is the
standard format that checksum validation tools expect. The tycho one is a
standard maven-generated checksum file. It only contains the checksum, no path
to the file because it's inferred by removing the .md5, and consequently all
these tools to validate the checksum don't work with the checksum files
published in M2 repo.

-Original Message-
From: Mark Eggers [mailto:its_toas...@yahoo.com.INVALID]
Sent: Monday, August 04, 2014 12:00 PM
To: Maven Users List
Subject: Re: MD5 checksum validation tool [Windows]?

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Justin,

This seems to work. It's marked as beta software, so read and use with
caution. I just downloaded it and ran it against a download of Apache Tomcat.
The check worked as expected.

http://www.exactfile.com/

. . . just my two cents
/mde/

On 8/4/2014 9:41 AM, Justin Georgeson wrote:
Thanks Paul. I don't see HashTab as being able to directly read the
.md5 file. Users would have to open the .md5 file in a text editor,
then copy/paste. And sadly this tiny bit of effort is actually being
deemed an undue burden. It literally has to be as simple as
double-click the .md5 file and get nice green graphic that says
everything is ok. HashCheck is the tool people are wanting to use, but
that requires the relative path be included in the md5 file.
I've submitted an enhancement request but their last release was in
2009 so I'm not hopeful.

-Original Message- From: paulus.benedic...@gmail.com
[mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict
Sent: Monday, August 04, 2014 11:18 AM To: Maven Users List
Subject: Re: MD5 checksum validation tool [Windows]?

Yup. I've used HashTab for years.
http://www.implbits.com/hashtab.aspx

Cheers, Paul

On Mon, Aug 4, 2014 at 11:16 AM, Justin Georgeson
jgeorge...@lgc.com wrote:

All the checksum validation tools I've found only seem to support
files with format produced by the md5sum tool, ie -

checksum1 relative/path/file1 checksum2 relative/path/to/file2 ...

But Maven publishes sibling files of the same name with .md5
appended, and no relative path in the file. Does anyone know of a
tool on Windows (shell extension, standalone GUI) that people could
use after downloading the artifact (in this particular case it's an
executable installer) and the md5 file and just double-click the md5
file to validate the download (or drag/drop the artifact and md5
file)?

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJT37v+AAoJEEFGbsYNeTwtp94IAKJtHuPL/glPl3Gxxd9aqvD
A
Hau/0nrphJWPSrKmhGV+K3U9Psh7ZnwA5/SDtFtMo3Oa7seGZ/DPYqxwI3oZ
XDcM
7O+20YNvxCiO7fhMg/bcR/HsbqkCreijj2nkeJRKTcTSx0p68GJf/V3Kh9c70ZuA
RuP3otwcHx2x+Yl7CbumGm+i+ayIkM0SYiArjhjnozAA3xb+Q7HCRuWk/hJREH
3T
nqce0pWx4t71kkBuF+r7clGC5kGm+XdzD+SzlJKoPO6UHFS/Ujql/a/jpqQRI363
vKdMbpwgZDUEZFGP4TmX6oEV6+oHylQLWWlXCNS9cGfgf2uaBY3uevXSeQh
/7SU=
=/+sR
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: OutOfMemoryError with maven-javadoc-plugin

2014-03-28 Thread Justin Georgeson

The maven-javadoc-plugin has a maxmemory configuration parameter. In my parent 
POM I set a default property docs.maxMemory and then configure 
maven-javadoc-plugin with

maxmemory${docs.maxMemory}/maxmemory

So each team can override that default setting in their pom.xml if they have an 
unusually large codebase, or set it really high on the command line for an 
aggregate javadoc of the entire multi-project workspace.

-Original Message-
From: Martin Hoeller [mailto:mar...@xss.co.at] 
Sent: Friday, March 28, 2014 8:39 AM
To: Baptiste Mathus
Cc: Maven Users List
Subject: Re: OutOfMemoryError with maven-javadoc-plugin

Yes I did. If I tried without -J I got some error.

On 28 Mär 2014, Baptiste Mathus wrote:

 Did you make sure you put -J-Xmx and not only -Xmx ?
 
 
 2014-03-28 12:24 GMT+01:00 Martin Hoeller mar...@xss.co.at:
 
  Hi Baptiste!
 
  I tried it but it didn't change anything. Still OutOfMemoryError :(
 
  -martin
 
  On 28 Mär 2014, Baptiste Mathus wrote:
 
   Sorry, I haven't used javadoc for years now, but as javadoc is an
  external
   tool, I guess you should specify additionalJOption?
  
  http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.ht
  ml#additionalJOption
  
   Cheers
  
  
   2014-03-28 10:36 GMT+01:00 Martin Hoeller mar...@xss.co.at:
  
Hi!
   
I have a quite large multimodule project with 150 modules. When 
executing mvn site the maven-javadoc-plugin is executed with 
default configuration. After some time of execution it fails in 
aggregate
  goal
and I get a
   
  Exception in thread main java.lang.OutOfMemoryError: GC 
overhead
  limit
exceeded
   
I know, I can adjust MAVEN_OPTS to give it more memory and I 
tried it
  with
MAVEN_OPTS=-Xmx1536m -Xms512m -XX:MaxPermSize=512m and with 
MAVEN_OPTS=-Xmx1280m -Xms256m -XX:MaxPermSize=768m. Both just 
leading to another OutOfMemoryError (but no GC overhead limit exceeded).
   
I'm currently using maven 3.1.1 and tested with m-javadoc-p 2.8 
and
  2.9.1
(no difference).
   
So my question is: does any body have some idea how to tweak 
parameters to solve this issue?
   
My current workaround is to disable aggregation in reporting 
section
  as
described here [0]. But this is really just a workaround, no 
solution
  :(
   
thx for your help,
- martin
   
[0]
   
  https://maven.apache.org/plugins/maven-javadoc-plugin/examples/selec
  tive-javadocs-report.html
   
  
  
  
   --
   Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, 
   Mangez un castor !
 
 
  --
  Martin Höller   | martin.hoel...@xss.co.at
  *x Software + Systeme   | http://www.xss.co.at/
  Karmarschgasse 51/2/20  | Tel: +43-1-6060114-40
  A-1100 Vienna, Austria  | Fax: +43-1-6060114-71
 
 
 
 
 --
 Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez 
 un castor !


-- 
Martin Höller   | martin.hoel...@xss.co.at
*x Software + Systeme   | http://www.xss.co.at/
Karmarschgasse 51/2/20  | Tel: +43-1-6060114-40
A-1100 Vienna, Austria  | Fax: +43-1-6060114-71

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

RE: javadoc:aggregate project filter

2014-01-15 Thread Justin Georgeson

I'm in a similar environment and use profiles in my aggregator POM to specify 
different reactors for different things. I have a profile for a javadoc reactor 
which doesn't include any eclipse-feature, eclipse-test-plugin, or 
eclipse-repository projects (ie it only includes the projects for the actual 
plugins that constitute the product).

-Original Message-
From: Christian Pontesegger [mailto:christian.ponteseg...@web.de] 
Sent: Wednesday, January 15, 2014 12:52 PM
To: users@maven.apache.org
Subject: javadoc:aggregate project filter

Hi,

I'd like to create API documentation for an eclipse RCP project. 
Therefore I use the javadoc:aggregate goal which nicely builds documentation 
for all my projects.

Now I want to filter some of them. When building with tycho junit tests are 
typically kept in a separate project. Still the package names for a test class 
ae the same as for the main class. This seems to be the best practice approach 
right now.

Currently API documentation for test classes is built too. Is there a way to 
filter a whole project from the aggregation step?

The only other approach I found was to use the javadoc:javadoc goal and to 
manually add paths using the sourcepath parameter. For a big project this is an 
error prone task which I would like to avoid.

regards
Christian

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Why does maven-javadoc-plugin:javadoc execute from an aggregator POM?

2014-01-14 Thread Justin Georgeson

I'm working with a set of eclipse-plugin projects using the Tycho plugins. We 
are trying to embed the javadocs in the plugin jar file, with an extension 
point so that the Javadocs show-up inline in the IDE. Since I need the javadoc 
to be generated prior to the package phase, I have configured the javadoc goal 
in the pluginManagement section of my parent POM, bound to the process-sources 
phase. This works fine when building the eclipse-plugin POM. But when I build 
from an aggregator POM, it fails with the error No public or protected classes 
found to document. I can run the aggregate goal to get one giant apidocs index 
of all the projects, but that doesn't generate the per-project apidocs to embed 
in each project's jar file because the aggregate goal skips all the 
non-aggregator POMs. So shouldn't the non-aggregate javadoc goals quietly not 
fork and execute the javadoc executable when it's processing an aggregator POM 
within the reactor?

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

56 matches

Mail list logo