Matthieu Brouillard est absent(e).

Je serai absent(e) du 20/02/2009 au 22/02/2009. Je répondrai à votre message dès mon retour. I am actually out of office. I will answer you once I am back.

Matthieu Brouillard est absent(e).

Je serai absent(e) du 20/07/2009 au 10/08/2009. Je répondrai à votre message dès mon retour. I am actually out of office. I will answer you once I am back.

Re: where to specify pluginRepositories for a custom maven core extension

the repositories I push them to (in my case central). Regards, Matthieu Brouillard On Wed, Jun 27, 2018 at 10:59 AM Nicolas Brasey wrote: > Hi, > > I developed a maven core extension which controls the project version and > the distribution managment repository depending on the git b

Re: Announcing OSSIndex plugins for Apache Maven: Scan your dependencies for known vulnerabilities

Excellent enhancement ; thank you Brian & Sonatype. > Report issues or ideas here: > https://github.com/sonatype/ossindex-maven/issues As requested I submitted my feedback as an RFE ( https://github.com/sonatype/ossindex-maven/issues/10) to report possible fixes on the vulnerabilities.

Re: Distribution management

Hi Adam, 'distributionManagement' is part of the pom not part of settings : maven is like that. If you do not want to expose some company repositories or if those ones are often changing then you can: - either use placeholders in some predefined `distributionManagement` tags (in project or in

Re: Re: Release a snapshot version

here is no more unnecessary pom modifications. - Matthieu Brouillard On Thu, Jun 28, 2018 at 6:23 AM Ravindranatha Panikar, Renjith < rr...@allstate.com> wrote: > Thanks Thomas, that did the job. > > regards, > > > -Original Message- > From: Thomas Br

Re: Extension works from lib/ext and CLI but not extensions.xml

Not sure but I think the mechanism extension does not work for SNAPSHOT versions. Try to install a non SNAPSHOT version in your local maven repository. I think I have already faced the same in the past while producing with my own extension https://github.com/jgitver/jgitver-maven-plugin Hope it

Re: Using POJO Tests: setUp() and tearDown() methods

I wasn't even aware that surefire had such a functionnality. I even do not understand why it does. If you want to do unit tests I would suggest you to use a real unit test framework like junit, testng, ... IMHO surefire should just be an orcherstrator and should not provide functionnalities to

Re: How to rewrite POMs retaining the XML structure

tion purposes without having to touch the original pom.xml file. Matthieu On Fri, Nov 30, 2018 at 12:13 PM Matthieu BROUILLARD wrote: > @Marc Rohlfs : AFAIK if you do a modification in the POM (as project > object model) in memory (via a plugin probably) then the pom.xml file is > alrea

Re: How to rewrite POMs retaining the XML structure

@Marc Rohlfs : AFAIK if you do a modification in the POM (as project object model) in memory (via a plugin probably) then the pom.xml file is already behind you and comments are already lost during the loading phase of the POM. Whatever the materialization of the POM you choose, comments will be

Re: Applying Jenkins build number

You can also use jgitver (https://jgitver.github.io/) that was demoed at Devoxx this year to compute automatically the project version, even for each commit. Using a jgitver configuration of false true true You can get the versions computed for each commit, for example 1.2.0-1,

Re: Applying Jenkins build number

Fine that you found your way. The only issue with the technics relying on injection of some external value is that they make your build not reproducible. It might not be an issue if those injections are only for intermediate builds and that you tag your build at some point in time with real X.Y.Z

invoker tests using multiple maven versions

. Matthieu Brouillard

Re: invoker tests using multiple maven versions

Thank you, I will go for the CI solution for now. Matthieu

Re: Regarding config param dependencyReducedPomLocation for maven-shade-plugin

Hi, I have faced the same problem recently on jgitver maven core dependency ( https://github.com/jgitver/jgitver-maven-plugin/issues/109). In fact, the problem popped up when a *fork* execution occures after that the pom file has been relocated. When this occures the basedir is computed as the

Re: A import B and B should import A where it is included

As Anthony said as you have a chicken-egg problem and you need to break the cycle somehow. To cut the loop I would eventually either: Solution 1: split the projects into: 1. the library itself without tests 2. the test library, depending on the lib 3. the library tests depending on both

Re: Would it make sense to publish a WAR to maven central?

Why couldn't you publish as a war? AFAIK Central is not restricted to be a jar library. You can already find wars in central : https://search.maven.org/search?q=p:war Regards Matthieu On Thu, May 30, 2019 at 2:40 PM Russell Gold wrote: > The open source Weblogic Monitoring Exporter < >

Re: Maven question - how to pull code from bitbucket repository as dependency

If your script is hosted on SVN or git then you can also perhaps do a simple GET on a well know resources (SHA1 or tag) on the raw file directly. That way the download is easy and you have a reproducible build because you target a fixed version of the script. Matthieu On Wed, Jun 12, 2019 at

Re: Using Git tags to cut releases to Maven Central from TravisCI

LEASE to NEXT-SNAPSHOT > And even the fact that: > - you can't really predict how RELEASE value will really be related to PREV > - you'll have to make a guess at choosing NEXT > proves that these changes at source level are useful. > What we should do is making them easie

Re: Failures building Eclipse 4.13 with maven-3.6.2

Hello, it looks like maven-3.6.2 really introduced a non compatible change with [core?] extensions and not just on polyglot-maven. In my own core extension project (jgitver-maven-plugin), when using maven-3.6.2, the ModelProcessor that I provide is not called anymore. Hope that helps to track

MNG-6685, JSR330, & ModelBuilder provided by extensions

Hi, the issue MNG-6685 & commits associated ( https://github.com/apache/maven/pull/256) seem to have broken extensions that provide their own ModelProcessor implementation via ` @Component(role = ModelProcessor.class)` How should extension declare the ModelProcessor they provide now? Is there a

Re: Using Git tags to cut releases to Maven Central from TravisCI

Hi Ben, several years ago I created jgitver to cover such a use case and even more. It uses git information (tags, branches, commits, metadatas, ...) to automatically compute a version based on configurable rules. So like you I can simply do: `git tag X.Y.Z && mvn

Re: Use latest versions vs use latest releases

Hi Nick, In several companies I have worked for, including the current one, we: - used 'update-properties' & 'update-parent' goals only - defined a property for each dependency/plugin version in all our poms - provided a global enterprise wide 'rules.xml' see [1] & [2] - used

Re: Launching full Maven programmatically

Hi, If I remember well I think maven-flatten-plugin loads the model in a way that even core-extensions are used; you should have a look there. Matthieu

Re: Launching full Maven programmatically

e mode. > > Cheers, > Andres > > On Thu, Apr 16, 2020 at 3:13 PM Matthieu BROUILLARD < > matth...@brouillard.fr> > wrote: > > > Hi, > > > > If I remember well I think maven-flatten-plugin loads the model in a way > > that even core-extensions are used; you should have a look there. > > > > Matthieu > > >

Re: Launching full Maven programmatically

ree to send a PR :P ) > But it's not the subject of the thread :) > But did you try without all the Jenkins but only the mentioned library? > It's not too hard to fix (the code pointed in this thread may have the same > issue) > > > On Fri, 17 Apr 2020 at 18:49, Matthieu BROUILLARD

Re: Launching full Maven programmatically

Olivier, If the project you are pointing is what is behind "Maven Integration" in Jenkins then it does things wrong by not taking into account maven core-extensions. I just retested now: - download Jenkins.war 2.232 - launch as java -jar - default installation - add plugin "Maven integration" -

Re: Best Practice for distributing test utilities?

Hi Andreas, In your use case I would keep everything in the same foo project but I would generate a kind of 'testutils' jar. >From what I understood your project structure is a bit like foo src/main/java src/test/java com.yourcompany.tests.utils com.yourcompany.tests.yourtests

Re: Maven versions plugin check far too many versions

You can filter the dependencies to look at using https://www.mojohaus.org/versions-maven-plugin/use-latest-releases-mojo.html#includesList . Hope it helps. Matthieu On Wed, Oct 14, 2020 at 12:47 AM wrote: > When I run "mvn versions:use-latest-releases" it checks for example for > versions of

Re: Maven moving to the next level: the build/consumer pom

model, where the required versions are added. Are those replacements still part of the pom loading by ModelProcessor? I'll give it a try especially to see the compliance with my existing core extensions. Matthieu Brouillard On Mon, Jun 22, 2020 at 11:18 PM Robert Scholte wrote: > Hi, > >

Re: BOM vs Parent inheritance

Not sure the behavior in your particular case is exactly documented. but it is sure that the depth in the dependency tree and order at the same level plays a role. You can find some hints inside an Andres Almiray blog post: http://andresalmiray.com/maven-dependencies-pop-quiz-results/ One