just relax a constraint' and still get a
coherent result.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Robert Scholte [mailto:rfscho...@apache.org]
> Gesendet: Montag, 1. Dezember 2014 20:00
> An: Maven Users List
> Betreff: Re: AW: Problems with the release pl
y dropping usage oft he
release plugin.
Chris
-Ursprüngliche Nachricht-
Von: Robert Scholte [mailto:rfscho...@apache.org]
Gesendet: Montag, 1. Dezember 2014 20:00
An: Maven Users List
Betreff: Re: AW: Problems with the release plugin
Just to be sure that we are on the same page:
Your req
Just to be sure that we are on the same page:
Your request is if the maven-release-plugin could be changed, so you can
specify versions for external (i.e. non reactor/multimodule) dependencies.
I won't allow this unless it can be automated, hence the introduction of
the VersionPolicy. This is
Oh well ... I give up ... so yet another plugin it will be.
I wasn't talking about changing anything at the workflow, just to have one
enforced constraint loosended a little if required, but I guess this will never
happen.
Chris
-Ursprüngliche Nachricht-
Von: Benson Margulies [mailt
Unfortunately the world isn't as ideal as I would like it to be. There are
sometimes constraints that lie outside of the reach of the developer(s) working
on the projects build.
In one case the company I worked for desperately needed to release parts of a
multi module build separately. I know t
Hi Robert,
Thanks for your reply, but I have encountered numerous situations where this
restriction resulted in people not using the pulugin at all ... doing each step
with alternate plugins and unfortunately leaving away some of the steps.
So ususally they use the versions plugin or manually a
