maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Curtis Rueden <ctrue...@wisc.edu>
Subject Re: How to tell release:perform only to deploy specific modules
Date Tue, 12 Feb 2013 21:02:14 GMT
Hi Chris,

> Unfortunately I would like to invoke release:perform and use mavens
> "-projects" property to limit the reactor to a specific subset of
> artifacts. Otherwise the build would try to deploy artifacts that have
> been previously released and would instantly fail.

This probably does not completely solve your problem, but my team had a
vaguely similar issue with incremental deployment [1], and decided to write
a script that deploys only changed artifacts:


https://github.com/scijava/scijava-common/blob/master/bin/incremental-deploy.sh

Maybe it is useful to you.

Regards,
Curtis

[1]
http://mail-archives.apache.org/mod_mbox/maven-users/201205.mbox/%3CCADN69ynMmyS-V%2BeROd44Z1qeCKZvJBfc828fumphsvvmnx8Wrg%40mail.gmail.com%3E


On Sat, Feb 9, 2013 at 12:13 PM, christofer.dutz@c-ware.de <
christofer.dutz@c-ware.de> wrote:

> Hi,
>
> this is a relatively special case and I am sort of running out of options.
>
> I am trying to setup a build that it allows minor releases of individual
> projects (I don't want to get into a discussion about if this is a good
> thing ... please).
>
> Now I am using release:prepare to prepare the release by providing version
> numbers for all modules in the project. This is working great.
>
> Unfortunately I would like to invoke release:perform and use mavens
> "-projects" property to limit the reactor to a specific subset of
> artifacts. Otherwise the build would try to deploy artifacts that have been
> previously released and would instantly fail. Unfortunately the "-projects"
> is only picked up by the main maven process, the setting is not passed to
> the spawned "deploy" maven build in the checkout-directory.
>
> How could I configure the build to act as I want? I have noticed the
> "additionalArguments" property in the release.properties, and was thinking
> about putting my "-projects" in there, but I guess this would be applied to
> several executions and not only the "deploy" build in the separate checkout.
>
> Chris
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message