Releasing a subset of the Reactor

Hello everyone, Does anyone know if it's possible to release justa subset of the Reactor when using the maven-release-plugin? The Layrry build includes a set of modules (examples and integration tests) that should not be part of the release. And added hurdle is that there are "duplicate"

Re: exclusive execution scheduling

I would say this is a windows problem rather than a maven problem. I have had  similar problems trying to build simpler things where only solution is to reboot windows to unlock NTFS (NoT a File System).  I'm very seriously considering getting VMWare and installing a Linux Mint 20 and  work in

Re: Releasing a subset of the Reactor

Hi Andres, If its just about deploying the modules to a remote repo, you could set the skip property of the maven-deploy-plugin. I've applied that trick in a Maven plug-in I've made [1]; their integration tests don't need to be in Central, but all other modules should. In this scenario, the

Re: Releasing a subset of the Reactor

Hi Maarten, Yup, this is a matter of fact an attempt to configure the Layrry build to publish its artifacts to Maven Central and make it happen with a single release commit. I’ve got the deploy plugin configured in such a way they it will skip tests and examples. That works. However the

Resolve root directory in a multi-project build

Hello everyone, Is there a way to reliably resolve the value of the root directory for a given multi-project build? Unfortunately ${session.executionRootDirectory} does not seem to work for all cases, it might work when used inside a plugin's section but does not when used outside of plugins

Re: exclusive execution scheduling

I completely get what you're saying, in fact it hasn't been 48hrs since I've had to reboot an NTFS machine to unlock a file. But here the problem as it manifests is with msbuild itself (if you're interested https://github.com/dotnet/sdk/issues/9585) That might be where we leave it. But I think

Re: exclusive execution scheduling

Hi. It should already be possible for you to build a dependency graph or execution order the way you need for multi-threaded builds. Example: A and B are required executions for C and D can then be executed after all, A, B and C. So just package every execution into a separate Maven submodule and

Re: Resolve root directory in a multi-project build

Using directory-maven-plugin and highest-basedir goal from it has worked just fine for me. https://github.com/jdcasey/directory-maven-plugin#highest-basedir-goal pe 5. helmik. 2021 klo 18.53 Tamás Cservenák (ta...@cservenak.net) kirjoitti: > Howdy, > Grab somehow (you did not state from where if

Re: Resolve root directory in a multi-project build

@Tamás: Right, should had explained the use case. I want to deploy all artifacts to a local directory so that I can inspect everything which will be deployed given certain conditions. I managed to do that by forcing a stable, absolute directory as shown at

Re: Resolve root directory in a multi-project build

Howdy, Grab somehow (you did not state from where if "outside of plugins") MavenSession, it has getExecutionRootDirectory method, BUT it may not be what you want, as one may use -f param for example... So, I'd shoot back: WHY do you need the root of a multi module build and FROM WHAT you need it?

Re: Resolve root directory in a multi-project build

Unsure will it help, but your description reminded me of nexus-staging plugin, there we similarly "deploy locally" (defer actual deploy) to fire the deployables at the project end:

Re: Releasing a subset of the Reactor

@Thomas: I think you just solved my problem. I had to check if profiles let you modify and they do! There's one issue left though, if tests and demos are left out of the release then their versions won't be updated, which means their POMs will have to be updated after a release. I guess I can

Re: Resolve root directory in a multi-project build

I've been using maven.multiModuleProjectDirectory in various projects (and have also seen it in others). You'll need a .mvn directory in your root directory to make it work. PS: I know that there has been some controvery about this property but well, it works! ;-) Cheers, Falko Am 05.02.2021

Re: Resolve root directory in a multi-project build

Maybe for you Falko, but not my Jenkins server with Maven 3.6.3, or these other users https://issues.apache.org/jira/plugins/servlet/mobile#issue/MNG-5830 Delany On Fri, 5 Feb 2021, 22:25 Falko Modler, wrote: > I've been using maven.multiModuleProjectDirectory in various projects > (and have

Re: Releasing a subset of the Reactor

How about (in addition to disabling the deploy plugin, just in case) putting those submodules into a profile, enabled by default, but disabled during release? (e.g. through a "-P !tests" or "-Dit-tests=false" in and the appropriate activation for the profile) On Fri, Feb 5, 2021 at 2:16 PM

Re: Resolve root directory in a multi-project build

For me, no problem on Jenkins either (using "withMaven" pipeline step). There used to be this issue: https://issues.jenkins.io/browse/JENKINS-35335 Which turned out to be a Maven bug which was fixed in 3.5.0: https://issues.apache.org/jira/browse/MNG-5889 As far as MNG-5830 is concerned, I don't

Re: Resolve root directory in a multi-project build

I had some discussion with Karl Heinz Marbaise about maven.multiModuleProjectDirectory a while ago (cannot remember where exactly) and he strongly advised me not to use it as it is for internal use only. Even so, other tools such as IntelliJ IDEA use it internally, but not consequently, the

Maven compiler plugin Unsupported major.minor version

Hi, I hope this is the right channel. I have a multi module project that I'm trying to modularize in the JPMS sense. It's configured to run maven with java 11 and run the compiler plugin using java 15 through the toolchain plugin and this is what I get: [INFO] ---