Re: "mvn clean verify deploy" causes jar plugin to execute twice

On 2016-08-05T18:48:25 +0200 Anders Hammar wrote: > > Executing > mvn verify deploy > will execute the build lifecycle twice. No need to do that. Just execute > mvn deploy > as the deploy phase comes after the verify phase. On 2016-08-05T18:09:46 +0100 Stephen Connolly

Deploying independently versioned modules

Hello. For years, I've been developing libraries as sets of modules sharing a (semantic) version number. For each project, the project's root Maven module defines the version number for all modules in the project. As a result, intra-project dependencies can be efficiently declared like this:

Re: Deploying independently versioned modules

On 2017-02-08T19:25:01 -0800 Charles Honton wrote: > Take a look at maven exists plugin > [https://chonton.github.io/exists-maven-plugin/0.0.2/ > ]. This has goals to > prevent deployment or installation of artifacts

Re: "mvn clean verify deploy" causes jar plugin to execute twice

On 2016-08-05T15:19:05 + org.apache.maven.u...@io7m.com wrote: > > Note that there are no sources in src/main as this is a module containing > the unit tests for all other modules. However, this has not been a problem > to date and have used this arrangement without issue in some 40 or so >

"mvn clean verify deploy" causes jar plugin to execute twice

Hello. I've run into a bizarre problem when trying to deploy a project. If I run "mvn clean verify", the project builds without issue. If I run "mvn clean verify deploy", the project fails to build (on the very last module, naturally). The error is: [ERROR] Failed to execute goal

Re: Single-page sites?

'Ello. On 2017-02-28T02:38:02 +0100 Hervé BOUTEMY wrote: > Hi, > > No, this is not a current option of maven-site-plugin. Right, that's what I suspected. > > Pdf plugin does such equivalent one doc from every report. Do you mean one large pdf that contains the

Re: Defining a property designed to be overridden?

Hello! On 2017-03-01T15:49:10 -0600 Curtis Rueden wrote: > > If what you want is to ensure the property is simply non-empty, or matching > a particular regex, then take a look at the requireProperty enforcer rule > [1]. > > Or if your goal is to make sure that a property

Single-page sites?

Hello. I realize this may be a long shot: Is there any way to get the site plugin to produce one large HTML file instead of one file per report? If not, does anyone happen to know how much work would be involved in perhaps writing an alternative site plugin that can do this? M

Distinguishing between host and container dependencies

Hello. I'm working on an application that uses an embedded OSGi container to provide a plugin system. The problem I'm running into is that I don't seem to have any way to distinguish between dependencies that are dependencies of the host, and dependencies that will only be present in the

Slightly more advanced resource filtering (templating)?

Hello. I have a small project that contains a plugin for Blender[0]. Plugins in Blender are Python files that must contain a hash value at the top of the file containing version information. The version information has to be numeric constants as Blender actually parses this data rather than

Re: Slightly more advanced resource filtering (templating)?

On 2017-01-03T19:32:59 +0100 Guillaume Boué wrote: > It sounds like you're looking for the parse-version goal of the > build-helper-maven-plugin: On 2017-01-03T19:36:16 +0100 Karl Heinz Marbaise wrote: > Hi, > > have you taken a look at the

Re: Using the Maven API outside of a plugin?

On 2016-12-28T12:20:20 + org.apache.maven.u...@io7m.com wrote: > Hello. > > I'm writing a small program to analyze the dependencies of Maven > projects. There are numerous examples of how to do this from within a > Maven plugin, but I can't work out how to simply load a POM file and > derive

Using the Maven API outside of a plugin?

Hello. I'm writing a small program to analyze the dependencies of Maven projects. There are numerous examples of how to do this from within a Maven plugin, but I can't work out how to simply load a POM file and derive a ProjectDependencyGraph from it outside of the context of a plugin. How do I

Disabling javadoc doclint for generated sources?

Hello. My hand-written code passes Java 8's JavaDoc doclint checks. However, I also have some code (that has to be in the same package) generated by an external tool. The JavaDoc that this tool produces doesn't always pass the doclint checks. Is there a way to exclude the generated-sources

Re: Defining a property designed to be overridden?

On 2017-03-02T10:29:30 -0600 Curtis Rueden wrote: > > it seems that I can only require that the XML elements be overridden > > in *all* descendant POMs, and this introduces too much redundancy. > > I see. > > Would it be sufficient if the requireElements rule had a

Re: Enforcer requirePropertyDiverges not propagated to descendants?

On 2017-03-06T10:58:30 -0600 Curtis Rueden wrote: > Hi, > > For what it's worth, I agree that the requirePropertyDiverges rule is > difficult to use (and maybe buggy?). After playing with it some months ago, > I concluded that it was not going to work for me. That's why I

Enforcer requirePropertyDiverges not propagated to descendants?

Hello. I'm trying to use the Enforcer plugin to ensure that projects set a ${project.description} that is different to their parent. I'm using an organization-wide POM, and the rule is specified here: https://github.com/io7m/primogenitor/blob/develop/pom.xml#L540 I have an example

Re: Enforcer requirePropertyDiverges not propagated to descendants?

Hello. On 2017-03-05T01:18:34 +0100 Hervé BOUTEMY wrote: > first, you'll have to talk about rules, not only the plugin: there are many > rules, some implemented by the plugin and some implemented by MojoHaus extra- > enforcer-rules Right, yes. It's the

Re: Defining a property designed to be overridden?

On 2017-03-02T11:12:58 -0600 Curtis Rueden wrote: > Hi, > > > I'd need to think a bit more about it, but I personally dislike > > relativePath and have never used it (across hundreds of projects), > > pretty much for the sorts of reasons you've described. Hard-coding > >

Defining a property designed to be overridden?

Hello. I'm looking to move to an organization-wide parent POM but am not sure how to handle the following configuration case. The japicmp [0] plugin takes a configuration parameter that specifies the previous version of a module against which the current version of the module will be checked for

Re: Defining a property designed to be overridden?

On 2017-03-01T12:46:45 -0600 Curtis Rueden wrote: > > In this way, I ensure that all projects which extend our parent add all the > useful metadata and properties needed for successful builditude. > > We released scijava-maven-plugin 1.0.0 on Maven Central; feel free to use >

Re: Defining a property designed to be overridden?

On 2017-03-01T12:46:45 -0600 Curtis Rueden wrote: > > In this way, I ensure that all projects which extend our parent add all the > useful metadata and properties needed for successful builditude. > Hm, slight issue with this. If you take a look at how my projects are

Re: Defining a property designed to be overridden?

'Ello. On 2017-03-02T08:16:43 -0600 Curtis Rueden wrote: > Hi, > > > I do actually want to enforce this, the issue is that I only want to > > enforce it as far as the first ancestor. > > Sorry if you stated otherwise in your writeup, but my understanding is that > you

Re: Accessing licenses/license as POM properties?

On 2018-05-18T17:01:52 +0200 Andreas Sewe wrote: > Hi, > > > Is there a way to access the contents of the element as POM > > properties? I'd like to reference the URL of the first license element > > in a plugin execution, but there doesn't appear to be a >

Running maven-checkstyle-plugin from the root module

Hello! I've been using the maven-checkstyle-plugin for many years now. Almost all of my projects are heavily multi-module, and I have a fairly traditional setup where a checkstyle plugin execution is defined in my organization-wide POM, and inherited by all modules in all projects. I run

Re: Running maven-checkstyle-plugin from the root module

On 21/04/2024 19:03, Jeff Jensen wrote: > Sorry for the vagueness. I meant something even simpler - running the > Checkstyle goal separately, probably in two Maven executions similar to: > mvn checkstyle:checkstyle > mvn install -Dcheckstyle.skip=true I have ended up having to do something

Re: Running maven-checkstyle-plugin from the root module

On 21/04/2024 15:59, Jeff Jensen wrote: > Have you considered only running the checkstyle goal, from the parent so it > processes all modules, before the full build goal(s)? > There are two ways that I can interpret this: 1. Set the execution in the parent so that all of the child modules