Passing config parameters to a plugin goal on the command line

with the Maven Java 5 annotations? Thanks, Robert -- Robert Patrick HYPERLINK mailto:robert.patr...@oracle.comrobert.patr...@oracle.com VP, FMW Architects Team: The A-Team Oracle CorporationOffice: +1.940.725.0011 1148 Triple Crown Court

RE: Wrong info in Maven: The Complete Reference, chapter 3.6.1

artifactIdpersistence-deps/artifactId version1.0/version typepom/type /dependency /dependencies /project -- Robert Patrick robert.patr...@oracle.com VP, Oracle Corporation 7460 Warren Pkwy, Ste. 300 Office: +1.972.963.2872 Frisco, TX 75034, USA Mobile

Re: Proper Project and Module Configuration

Typically, you would make each module produce a single artifact (e.g., application). The parent POM can be the multi-module POM used to build all of its modules. Any module can, itself, be an aggregator and parent of its modules so you can nest things in whatever way makes sense... Robert

RE: What is the best way to get the single jar and pom.xml from multiple maven modules?

Add module E that generates the JAR and make module E's POM the JAR's POM. If you want to remove some of the "development" items from the POM, see http://www.mojohaus.org/flatten-maven-plugin/flatten-mojo.html -Original Message- From: Bhavesh K Shah

RE: How easy/reliable is a maven repo hosted on webdav?

+1 on not trying to use some other solution. Some people I know were trying to use WebDAV and the WebDAV wagon to work around some network limitation that they had and it was extremely painful and the WebDAV wagon seems to have not really been tested very well. I stood up an artifactory

RE: Convention for shipped artefacts?

We use http://www.mojohaus.org/flatten-maven-plugin/ to strip out "development-related" stuff, parent POMs, etc. from our POMs for our "leaf" artifacts so that they have standalone POMs with only their dependencies in them. -Original Message- From: Francois MAROT

Release plugin behavior anomoly

Hi, I am trying to use the release plugin with a new project where I want the entire project to use a single version number (vs. one version number per module). I have the single version number part working like this: 1.)In my parent pom, I do the following: test

RE: How to use 5 digit version numbers with Maven ?

ject: Re: How to use 5 digit version numbers with Maven ? Is there documentation on the mercury scheme ? I tried following the link at http://www.mojohaus.org/versions-maven-plugin/version-rules.html, but that just gives me a "Page Not Found". cheers, mehul On Thu, Jan 7,

Re: How to use 5 digit version numbers with Maven ?

Yes, you can use the Mercury version numbering scheme for artifacts having the 5 digit version number. Create a version rules XML file that specifies which artifacts use Mercury and which artifacts use Maven version schemes. Pass the file using the versions plugin's rulesUri or

Re: class path within framework

I assume that you don't want to put the properties file inside the framework jar (which is the easiest solution). If the properties file is always at the same relative path to the framework jar, then you can simply add a Class-Path element in the framework jar's Manifest to include the

RE: Maven javadoc plugin's aggregate-jar goal, multi-module project, and code generation

To: Maven Users List Cc: Robert Patrick Subject: Re: Maven javadoc plugin's aggregate-jar goal, multi-module project, and code generation To execute plugin during certain phase, add to . Plugin should be fired: attach-javadocs install<-- HERE aggreg

Maven javadoc plugin's aggregate-jar goal, multi-module project, and code generation

I am beating my head against the wall on this and surely I am just being stupid so hopefully someone will take pity on me and point me in the right direction. I am trying to add Javadoc generation into my normal build process for my multi-module project. It all works fine if I run "mvn

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 <m2spr...@springdot.org> wrote: > > Hi Curtis, > > I don't want to have the URL of my in-house Maven r

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 Mo

Re: I want to separate the 3rd party jar in war file.

Seems like a bad idea. Many would argue that you are invalidating all of your tests run prior to creating the new binary with "extra stuff" in it. You really should try to avoid rebuilding the application after testing it... Robert Patrick Sent from my iDevice > On Mar 18, 201

RE: Maven and Continous Integration / Continous Delivery

I just glanced through the current article but I suspect that this doesn’t work with POMs that have parent references where the version is the same as the project (e.g., the parent is the aggregate POM in the directory above each module). In my current projects, I would only have a single

Re: AW: Maven and Continous Integration / Continous Delivery

project B, use the versions plugin to update the project B dependency in Project A to a non-snapshot version, and then release project A. One could argue that if A and B need to be built/released together, they are not really Independent projects... Robert Patrick > On Apr 20, 2016, at 5:07

Re: Maven and Continous Integration / Continous Delivery

While having the developers update the POM may sound ok, it turns out to be problematic in practice when there are more than a handful of developers. In a previously life, we had an elaborate scheme where we had scripts that the developer had to run to update the POM and dependency version

RE: AW: Maven and Continous Integration / Continous Delivery

want to reuse our components more than we did in the past. Regards, Gerrit -Ursprüngliche Nachricht- Von: Robert Patrick [mailto:robert.patr...@oracle.com] Gesendet: Mittwoch, 20. April 2016 14:24 An: Maven Users List Betreff: Re: Maven and Continous Integration / Continous Delivery

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

This should be treated as a bug. Many builds, including ours, relies on being able to override properties defined in the parent hierarchy in a module POM. This change you are describing would break a lot of builds... > On Aug 12, 2016, at 8:41 AM, Samuel Langlois

RE: [EXTERNAL] Re: help with version range

: [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 <robert.patr...@oracle.com> VP, OPC Development, Oracle Corporation 7460 Warren Pkwy, Ste. 300 Office: +1.972.963.2872 Frisco, TX 7

RE: [EXTERNAL] Re: help with version range

version], C:\myproject\zipinsall\pom.xml, line 196, column 22 -Original Message- From: Christian Schulte [mailto:c...@schulte.it] Sent: Friday, September 23, 2016 5:17 PM To: Maven Users List Subject: Re: [EXTERNAL] Re: help with version range Am 09/23/16 um 23:38 schrieb Rob

RE: [EXTERNAL] Re: help with version range

Message- From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] Sent: Friday, September 23, 2016 3:30 PM To: Maven Users List Subject: Re: [EXTERNAL] Re: help with version range Hi, On 23/09/16 18:38, Robert Patrick wrote: > > What I am questioning is the "engineer's approach"

RE: [EXTERNAL] Re: help with version range

e this that does not require me to do something like this: > > [1.0,1. > 999) > > > -Original Message- > From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] > Sent: Friday, September 23, 2016 3:30 PM > To: Maven Users List > Subject: Re: [EXTERNA

RE: Aw: Re: Re: [Regression] Declared properties could not be modified anymore within a plugin

I can confirm that it is not possible to override a project property in a plugin with Maven 3.3.9. I am not sure what the expected behavior is but trying to override a pre-initialized value (from command-line -Ds, .mvn/maven.config, or the POM) from a plugin has no effect... -Original

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,

RE: [EXTERNAL] Re: help with version range

th your own projects at least. .. you can just call your snapshot version 1.99-SNAPSHOT or whatever while developing and at releas time switch to 2.0 .. Manfred Robert Patrick wrote on 2016-09-23 08:56: > This does seem non-intuitive.If I say that I want versions between 1.0 > and >

RE: [EXTERNAL] Re: help with version range

h breaking a TON of other stuff. And I am not even sure if it would be more intuitive instead of just being different. Manfred Robert Patrick wrote on 2016-09-23 09:38: > No, you are making an invalid assumption about what I understand! I > completely understand the relationship of SNA

RE: [EXTERNAL] Re: help with version range

Maven will consider 2.0-alpha-1 to be before 2.0-SNAPSHOT. This is documented in ComparableVersion: https://maven.apache.org/ref/3.3.9/maven-artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html. Guillaume Le 23/09/2016 à 18:49, Robert Patrick a écrit : >

Maven Compiler Plugin 3.5.1 bug

Periodically, I update the versions of the Maven plugins for my projects. Today was one of those days. What I found is that the maven-compiler-plugin 3.5.1's compile goal no longer seems to not be including the ${project.build.directory}/generated-sources/annotations directory in the

RE: Maven Compiler Plugin 3.5.1 bug

] Sent: Saturday, October 22, 2016 5:48 PM To: Maven Users List Subject: RE: Maven Compiler Plugin 3.5.1 bug You can add source directories using the build-helper-maven-plugin. On Oct 22, 2016 4:39 PM, "Robert Patrick" <robert.patr...@oracle.com> wrote: > I am using the

testCompile goal fails periodically on Windows because it cannot find test-classes directory

Hi, I am seeing a periodic error when running our builds on Windows. When running "mvn clean verify" I occasionally see errors like the following: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:testCompile (test-compile) on project

RE: Maven Compiler Plugin 3.5.1 bug

introduced in 3.2, fixed in 3.5.1 (see release notes for that version). Your plugin should use its own output directory and add it as a source root. Le sam. 22 oct. 2016 23:18, Robert Patrick <robert.patr...@oracle.com> a écrit : > Periodically, I update the versions of the Maven plugi

RE: Maven Compiler Plugin 3.5.1 bug

is "inferior" due to requiring this manual configuration, it is really not a big deal to do this one-time operation... :-) -Original Message- From: Christopher [mailto:ctubb...@apache.org] Sent: Sunday, October 23, 2016 12:02 PM To: Maven Users List; Robert Patrick Subject:

RE: Maven Compiler Plugin 3.5.1 bug

followed that behavior. For now, build-helper is required for this to work in Eclipse (I don't know about other IDEs). If the compiler plugin did this, and IDEs followed suit, I'd think that would be useful. On Sat, Oct 22, 2016 at 6:50 PM Robert Patrick <robert.patr...@oracle.com> wrote: &g

RE: Comparing specifying repositories in pom vs. settings.xml?

But in a large corporate environment, the centralized repository manager can house hundreds/thousands of repositories so unless you want to virtualize the entire set of repositories (which tends to make the repository manager slower), you still need to specify the repositories to search, right?

RE: Jenkins and Maven

opinions however you see fit On 13 October 2016 at 15:24, Robert Patrick <robert.patr...@oracle.com> wrote: > Well... Some of us, my team included, are using the Maven jobs in > Jenkins and they generally works fine for our projects (and is much > simpler to configure). Be warned

RE: Jenkins and Maven

To make concurrent Jenkins builds work, simply enable the "Use private Maven repository" option in the Jenkins Maven build jobs and select the appropriate "Strategy" (e.g., "Local to the workspace" or "Local to the executor"). This works fine for us... -Original Message- From: Nigel

RE: Jenkins and Maven

Well... Some of us, my team included, are using the Maven jobs in Jenkins and they generally works fine for our projects (and is much simpler to configure). Be warned that Maven 3.3 support is still busted for projects that use .mvn/maven.config waiting on

RE: Comparing specifying repositories in pom vs. settings.xml?

My team always favors defining repos in the top-level (parent) POM. If we require special project-specific settings that must be in settings.xml, we put settings.xml in the top-level of the project source tree and check it in... For publishing projects to our binary repo for consumption by

Re: ${project.parent.parent.version} does not work

versions:update-property seems like a good choice. Sent from my iDevice > On Dec 4, 2016, at 8:22 AM, Florian Schätz wrote: > > Hello, > >> For now, you can make that property a constant in the grandparent like >> "1.0.0-SNAPSHOT" and use that >> property itself in

RE: ${project.parent.parent.version} does not work

[mailto:fscha...@assona.net] Sent: Monday, December 05, 2016 7:51 AM To: users@maven.apache.org Subject: Re: ${project.parent.parent.version} does not work Am Sonntag, den 04.12.2016, 14:56 -0600 schrieb Robert Patrick: > versions:update-property seems like a good choice. Unfortunat

RE: How to add class file to build & classpath?

Can't you generated class files in the expected location (in ${project.build.directory}/classes directory) during the compile phase? I would expect these classes to be included in classpath for later pahses and in the JAR created during the packaging phase of the module build (assuming

RE: How to add class file to build & classpath?

er I don't know why Maven doesn't add/use all files in the ./target/classes folder but only uses files that it put there itself. What am I missing here? It seems this should just work because the files are in the ./target/classes folder. -Dave On Thu, Apr 6, 2017 at 10:55 AM, Robert Pat

RE: dependency question

The other way is to use a version range in your dependency, which gives you a similar behavior as using a snapshot dependency. Both approaches have their advantages and drawbacks... -Original Message- From: Russell Gold Sent: Thursday, April 06, 2017 2:27 PM To: Maven Users List

RE: How to add class file to build & classpath?

e so I can manually run that when needed. Not ideal but its working. Will investigate the other projects. -Dave On Thu, Apr 6, 2017 at 1:27 PM, Robert Patrick <robert.patr...@oracle.com> wrote: > I also built a little sample project where I simulated a generated > class using the

RE: dependency question

Patrick <robert.patr...@oracle.com> 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 an

RE: dependency question

Typically, whenever you run a build that includes a snapshot dependency, Maven will go out to the remote repository(ies), if any, and download the maven-metadata.xml file for that dependency to compare it against the snapshot stored in your local Maven repository to see if there is a newer

RE: Jenkins Maven build not seeing my .mvn folder?

The problem is that Jenkins always builds from a directory other than your project root directory, so it uses -f to point at the root project POM. Before I changed the shell scripts, the search for the .mvn directory was always starting at the current directory (which is why Jenkins never

RE: Continuous Delivery with Maven now possible?

..@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 i

RE: Continuous Delivery with Maven now possible?

The problem is that I really want to control the version number for a project from a single place. Ideally, this would be the element of the project's top-level POM. The problem is that there is no way to do this because the module POMs have to declare a parent element that can be resolved

RE: Continuous Delivery with Maven now possible?

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

RE: Version Information needed.

[Removing Maven dev list from the email thread via BCC] This plugin is not part of the Maven core so you can likely use any modern version of the plugin with Maven 3.2.5. As for how to use it, probably best to start with http://www.mojohaus.org/cobertura-maven-plugin/ and then ask more

Re: Need to pass properties to the dependency POM file

Why not just use a top-level POM’s dependencyManagement section, in conjunction with top-level POM-defined properties if desired, to control the dependency versions? > On Oct 10, 2017, at 6:56 AM, Bikash Chandra Barad > wrote: > > Hi Russell, > > I am

Re: Local jar not recognized from maven repository

That error message does not look like a Maven error message. Try running your build with -X and look at the output of the maven-compiler-plugin. If the class was not found during compilation, I would expect a different error message from the Java compiler... > On Oct 5, 2017, at 4:25 AM,

RE: dll hell

Since you mentioned DLLs in the subject, I assume this is Windows. Is the %JAVA_HOME%/jre/bin directory (where jpeg.dll lives) in the PATH? -Original Message- From: Martin Gainty [mailto:mgai...@hotmail.com] Sent: Monday, August 28, 2017 4:25 PM To: users@maven.apache.org Subject:

Re: dll hell

to explicitly load the native library. In fact, when I tried to load it explicitly, I got an error saying that the library had already been loaded... > On Aug 29, 2017, at 7:14 AM, Martin Gainty <mgai...@hotmail.com> wrote: > > > > > _______

Re: Problems Using ANTLR4 (Packaged Classes Not Found in Generated Code)

Most likely, you need to add a compile-time dependency on the antlr runtime library, where the missing class is located. org.antlr antlr4-runtime 4.7 > On Oct 29, 2017, at 2:43 AM, Karl Heinz Marbaise wrote: > > Hi, > > can make a test project on

RE: IT test in src/test/java is not executed by failsafe:integration-test, or fails oddly with verify

In our integration tests' parent POM, we configured the compiler plugin to run the test-compile goal: org.apache.maven.plugins maven-compiler-plugin test-compile

Re: maven-war-plugin addClasspath useless, because it cannot add absolute paths

Well...I suspect that it is skipping the dependency because it is system-scoped. If so, this doesn’t make it useless for most people since most of use do not use “system-scoped” dependencies... > On Jan 25, 2018, at 4:43 AM, Basin Ilya wrote: > > Hi List. > As far as I

RE: Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end

While Nexus may not support "staging repositories", it certainly supports more than one repository so why not just create one or more repositories that serve as staging repositories. For example, Pipeline Steps: 1.) Trigger a build based on source check-in and push to stage1 repo if build

RE: Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end

On Wed, Feb 14, 2018 at 10:01 AM, Robert Patrick <robert.patr...@oracle.com> wrote: > While Nexus may not support "staging repositories", it certainly > supports more than one repository so why not just create one or more > repositories that serve as staging repositori

RE: Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end

y the multi-module project in order to do a dependency:copy, and then similarly, use a build-helper:attach all the artifacts that were just downloaded. But that seems like a painful solution. Am hoping there is something easier? Thanks, Eric On Wed, Feb 14, 2018 at 9:45 PM, Robert Patrick