Re: MRELEASE: Release only modules, not project itself

What is the problem with releasing the parent pom ? Jeff Le 24 sept. 2015 10:58, "Wouter Lievens" a écrit : > Hello, > > I would like to run the release plugin (prepare/perform) for a top-level > POM (packaging "pom") that has a big list of modules. > The top project

Re: MRELEASE: Release only modules, not project itself

First of all, the top-level pom has no real meaning. It just aggregates the modules, and the "end deliverable" projects (that uses maven-shade to build an executable jar etc) are among the modules. I take advantage of the top-level pom's topological sorting of the modules that way, of course.

MRELEASE: Release only modules, not project itself

Hello, I would like to run the release plugin (prepare/perform) for a top-level POM (packaging "pom") that has a big list of modules. The top project itself doesn't need to be tagged, released and deployed, because it's there only to build the modules in good order. So, I want the release

Re: MRELEASE: Release only modules, not project itself

Hi Wouter, Is the top-level POM also the parent pom of the modules? Or only an aggregator? If it's the parent, then you have to release it [1], because consuming the modules later will require the parent POM as a "dependency" of sorts in order to fully interpolate each module POM. If it's only

How to run junit test suite class but still see individual test class progress information on stdout?

When I run a junit test suite class via the surefire plugin, I see only the progress information for the test suite itself. So if the suite contains 100 test classes, I see output like this on stdout: Running my.package.MySuite Tests run: 1257, Failures: 0, Errors: 0, Skipped: 1, Time elapsed:

Re: MRELEASE: Release only modules, not project itself

Hi, it is not possible to do a tag-per-project. Several times we get this request, but for hierarchical (i.e. non-flat) multimodule projects it is impossible to do this atomically. And since this the most common structure, I didn't find it not important enough to solve the release with an

Parent version is ignored if referenced parent pom.xml available from local filesystem in maven 3.3.x

I have simple project structure: test-module |-pom.xml |-child1 |-pom.xml test-module/pom.xml http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; xmlns="http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;> 4.0.0 org.name

How to handle multiple plugins with the same goal prefix

I'm trying to add the following plugin to my build but the goal prefix is license which conflicts with maven-license-plugin used in my parent pom. I can't change the parent so how do I handle multiple plugins that both have a goal prefix of license? Note in my pom I want to run some license

Re: How to handle multiple plugins with the same goal prefix

Hi, if there is generated documentation for the goal, you should be able to see it. E.g. compile:compile [1] You can call this by its full name, i.e. org.apache.maven.plugins:maven-compiler-plugin:3.3:compile The version is optional, Maven will look for a matching version in the pom.xml

Re: How to handle multiple plugins with the same goal prefix

I was missing the groupId...that fixes it...many thanks. -Dave On Thu, Sep 24, 2015 at 12:28 PM, Robert Scholte wrote: > Hi, > > if there is generated documentation for the goal, you should be able to > see it. > E.g. compile:compile [1] > > You can call this by its full

Re: How to run junit test suite class but still see individual test class progress information on stdout?

Hi Wayne, Thanks for the tips. I've gone through the surefire plugin's config documentation and the "useFile" option seems to control where the detailed results are written (default is in target/surefire-reports/ but if you set useFile=false, then the detailed results go to the console). I

Re: Parent version is ignored if referenced parent pom.xml available from local filesystem in maven 3.3.x

Regression filed and fixed... you are just waiting for the next release in the 3.3.x line On 24 September 2015 at 19:40, Denis Golovin wrote: > I have simple project structure: > > test-module > |-pom.xml > |-child1 > |-pom.xml > > test-module/pom.xml > >

Re: Parent version is ignored if referenced parent pom.xml available from local filesystem in maven 3.3.x

Stephen, I guess this is the regression issue you are talking about https://issues.apache.org/jira/browse/MNG-5840. I've verified on master build and it still have the same behavior. It works where it was not working in previous version up to 3.2.5. I blame version ranges that now supported in

Re: How to run junit test suite class but still see individual test class progress information on stdout?

There is probably some configuration available that will satisfy your needs (e.g. useFile): http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html If not, you may need to just cat some files under target/surefire-reports when your build is done. Also look here, it may be

Re: Parent version is ignored if referenced parent pom.xml available from local filesystem in maven 3.3.x

I am running my tests on locally built maven master and it seems that dependencies/dependency/version node content like 1.0.0 is considered to be the single version range which is [1.0.0]. Shouldn't the same version format have the same interpretation throughout the pom? Now from my tests I can

Re: Best strategy for using lots of modules/projects with some private and some OSS

Pretty impressive. I think another issue I hadn't thought of is the overhead of having a CI server/project for each project. If anything, you have to enumerate each project so you can see inside of it and what's happening. Having one macro one means you can see everything in one place but of

Re: Best strategy for using lots of modules/projects with some private and some OSS

Shouldn't require any additional CI servers -- we have one master with hundreds of builds. Depending on build frequency, you likely want a couple slaves -- we have 7 but easily get by with 4. Setting up all the builds is some work but Jenkins will help you a lot. We have a template project