Re: Site Plugin 3.5 URL behavior and multi-module builds

yes, it is expected behaviour: see "inheritance assembly" step of model builder [1] in your case, your config cause artifactId to be added twice: one on project.url and one on site.url before ${project.url} is interpolated You should just not use ${project.url} in distributionManagement/site:

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

On 03/10/2016 10:10 PM, Mark Eggers wrote: David, Are you perhaps running this inside Eclipse? If so, do you have the m2e-connector for maven-dependency-plugin installed? Can you run mvn package from the command line if you're only packaging this from Eclipse? I have run my project from

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

On 03/10/2016 09:43 PM, Uwe Barthel wrote: I tried: 'mvn clean' removes the lib/ and target/ folder. 'mvn package' puts the libs into lib/ again. I delete all libs in lib/ folder but let the lib/ folder itself and the target folder untouched. ‘mvn package’ works as expected. As usual, this

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

David, Are you perhaps running this inside Eclipse? If so, do you have the m2e-connector for maven-dependency-plugin installed? Can you run mvn package from the command line if you're only packaging this from Eclipse? I have run my project from Eclipse Mars.1, but I have the m2e-connector

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

I tried: 'mvn clean' removes the lib/ and target/ folder. 'mvn package' puts the libs into lib/ again. I delete all libs in lib/ folder but let the lib/ folder itself and the target folder untouched. ‘mvn package’ works as expected. -- bart...@x-reizend.de > On 11 Mar 2016, at 06:05, David

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

Ok. Could you remove the jars and then run it again? On Thu, Mar 10, 2016, 20:58 Uwe Barthel wrote: > Hi David, > > I use your pom.xml (but removed parent and org.opendaylight dependencies) > and it works well with: > > Apache Maven 3.3.9

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

Hi David, I use your pom.xml (but removed parent and org.opendaylight dependencies) and it works well with: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Maven home: /usr/local/Cellar/maven/3.3.9/libexec Java version: 1.8.0_31, vendor: Oracle

Re: "conditional" parent POM?

In this case I actually want to add something, or to be precise, I want my Jenkins job to add something on the fly with each build. So I can build an open source project deploying to my organization's repository manager. The property approach Manfred pointed out earlier seems to be the most

Re: "conditional" parent POM?

The flatten plugin can remove sections of the POM that are not needed by consumers of your software binaries, such as the repositories and pluginRepositories sections. Isn't that what you are trying to achieve? Robert Patrick Sent from my iDevice > On Mar 10, 2016, at 4:29 PM, Manfred Moser

Re: "conditional" parent POM?

How so? The flatten plugin just flattens the poms right. If they point to an internal repo manager .. its still wrong.. Manfred Robert Patrick wrote on 2016-03-10 14:43: > Take a look at the flatten plugin...this is a much simpler way to solve that > problem! > > Robert Patrick > Sent from

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

On 03/10/2016 03:54 PM, Mark Eggers wrote: David, I just upgraded to 3.3.9, and ran the following on one of my projects (twice): mvn clean package In both cases the JAR files were copied to my output directory and included in both the zip and tar.gz files. I guess a little more information

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

David, I just upgraded to 3.3.9, and ran the following on one of my projects (twice): mvn clean package In both cases the JAR files were copied to my output directory and included in both the zip and tar.gz files. I guess a little more information is needed?? . . . just my two cents /mde/ On

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

On 03/10/2016 03:36 PM, Mark Eggers wrote: David, If you're providing a list of dependencies, then yes you'll use the copy instead of copy-dependencies. See the following for that information: https://maven.apache.org/plugins/maven-dependency-plugin/index.html Also, I notice that you don't

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

David, If you're providing a list of dependencies, then yes you'll use the copy instead of copy-dependencies. See the following for that information: https://maven.apache.org/plugins/maven-dependency-plugin/index.html Also, I notice that you don't have outputDirectory specified. If you don't,

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

Thanks, but replacing my "manual" copy goal with "copy-dependencies" and implicit dependency declarations made no difference. No error at this phase, it just doesn't do anything. On 03/10/2016 02:57 PM, Mark Eggers wrote: David, On 3/10/2016 2:31 PM, David M. Karr wrote: Several days ago,

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

David, On 3/10/2016 2:31 PM, David M. Karr wrote: > Several days ago, on the advice of someone on another list, I configured > the use of the "maven-dependency-plugin" in my POM so that the build > would copy some dependencies into a local folder, not inside the target > folder. > > This worked

Re: "conditional" parent POM?

Take a look at the flatten plugin...this is a much simpler way to solve that problem! Robert Patrick Sent from my iDevice > On Mar 10, 2016, at 2:38 PM, Max Spring wrote: > > Hi Curtis, > > I don't want to have the URL of my in-house Maven repository manager out in

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

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

Re: "conditional" parent POM?

Hi Manfred, you're right, "property-injection" is what I want. I updated my example: https://github.com/m2spring/wild-inhouse-hybrid-example/tree/property-approach Thank you! Regards, -Max On 03/10/2016 12:40 PM, Manfred Moser wrote: You should not use different rool poms. The whole

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?

Why isn't maven-dependency-plugin copying my artifacts anymore?

Several days ago, on the advice of someone on another list, I configured the use of the "maven-dependency-plugin" in my POM so that the build would copy some dependencies into a local folder, not inside the target folder. This worked the very first time I ran the build with it, and I've been

Re: "conditional" parent POM?

You should not use different rool poms. The whole upstream parents for your open source project should be open source as well. And if you want to deploy to a different repo manager you can make the URLs configurable as a property that you set in the pom and e.g. override in your internal

Re: "conditional" parent POM?

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].

"conditional" parent POM?

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

Re: variable doesn't work for version

the core On 10 March 2016 at 16:43, Benson Margulies wrote: > On Thu, Mar 10, 2016 at 3:04 AM, Stephen Connolly > wrote: > > Also I suspect this doesn't fully include logic to ensure that the > > 'this' = my code, or 'this' = the core

Re: variable doesn't work for version

On Thu, Mar 10, 2016 at 3:04 AM, Stephen Connolly wrote: > Also I suspect this doesn't fully include logic to ensure that the 'this' = my code, or 'this' = the core implementation for properties in the version? > substitution resolved pom is installed/deployed,

Site Plugin 3.5 URL behavior and multi-module builds

Hi, I'm using the Maven site plugin with a multi-module build. The generated site is going to be deployed to GitHub, so I'm only using the Maven site plugin to generate and stage content locally, not deploy. I have a placeholder distributionManagement/site element in my POM so that site:stage

Document No 6001285

Thanks for using electronic billing Please find your document attached Regards Accounts - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org

Re: variable doesn't work for version

Also I suspect this doesn't fully include logic to ensure that the substitution resolved pom is installed/deployed, so may cause issues for out-of-reactor consumption as a dependency, or GPG signature validation if you try to "fix" with a hack On Thursday 10 March 2016, Stephen Connolly

Re: variable doesn't work for version

It's ${revision} or ${changelist} or a third one I cannot recall, ${rev} is on the "moan and wail" list On Wednesday 9 March 2016, Benson Margulies wrote: > Almost really working. The only gripe is that it is still warning me > that I have an expression in , even when I