You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Henning Schmiedehausen <he...@schmiedehausen.org> on 2013/10/22 04:12:47 UTC
[CONFIGURATION] trying an RC release
Hi,
so I was trying to cut an RC for config but it fails with
Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single
(source-release-assembly) on project commons-configuration: site did not
exist in the target directory - please run site:site before creating the
assembly: Mojo configuration is invalid: site did not exist in the target
directory - please run site:site before creating the assembly -> [Help 1]
so the assemblies require the site to be present before release:prepare? Or
how is that supposed to work. When running release:prepare it will execute
the build lifecycle and then the site lifecycle. But in the build verify
phase the site must be present which it obviously not is.
Or is it not possible to use release:prepare for config and I have to do it
by hand?
Thanks for helping me out here,
Henning
Re: [CONFIGURATION] trying an RC release
Posted by sebb <se...@gmail.com>.
On 22 October 2013 07:29, Henning Schmiedehausen
<he...@schmiedehausen.org> wrote:
> On Mon, Oct 21, 2013 at 4:20 PM, sebb <se...@gmail.com> wrote:
> [...]
>
>> I don't like the release plugin; I think it is badly designed [1] so I
>> don't use it; so I cannot help with it.
>>
>> [1] https://jira.codehaus.org/browse/MRELEASE-845
>
>
> If that bothers you, use a modern SCM and set
> <pushChanges>false</pushChanges>. This addresses all of the points in that
> issue. Some of them are unfixable in online SCMs such as CVS or Subversion.
The problems are _not_ unfixable in SVN (*), otherwise the manual
method would not work either.
It's just that they are easier to solve when the SCM supports deferred changes.
(*) I have done some work on a plugin that replicates the manual
steps; it works OK for me in limited testing.
[I hope to release it for use in Commons one day]
> Still, thanks for helping me out, I figured out earlier that the assemblies
> for configuration are ancient and comparing them to other components, none
> has the site requirement. So I already had removed that.
>
> Thanks,
> Henning
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [CONFIGURATION] trying an RC release
Posted by Henning Schmiedehausen <he...@schmiedehausen.org>.
On Mon, Oct 21, 2013 at 4:20 PM, sebb <se...@gmail.com> wrote:
[...]
> I don't like the release plugin; I think it is badly designed [1] so I
> don't use it; so I cannot help with it.
>
> [1] https://jira.codehaus.org/browse/MRELEASE-845
If that bothers you, use a modern SCM and set
<pushChanges>false</pushChanges>. This addresses all of the points in that
issue. Some of them are unfixable in online SCMs such as CVS or Subversion.
Still, thanks for helping me out, I figured out earlier that the assemblies
for configuration are ancient and comparing them to other components, none
has the site requirement. So I already had removed that.
Thanks,
Henning
Re: [CONFIGURATION] trying an RC release
Posted by sebb <se...@gmail.com>.
On 22 October 2013 03:12, Henning Schmiedehausen
<he...@schmiedehausen.org> wrote:
> Hi,
>
> so I was trying to cut an RC for config but it fails with
>
> Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single
> (source-release-assembly) on project commons-configuration: site did not
> exist in the target directory - please run site:site before creating the
> assembly: Mojo configuration is invalid: site did not exist in the target
> directory - please run site:site before creating the assembly -> [Help 1]
>
> so the assemblies require the site to be present before release:prepare?
Not in other components I have RMed.
> Or how is that supposed to work.
I don't think so.
Check the assembly descriptors.
Compare the pom with another component pom.
> When running release:prepare it will execute
> the build lifecycle and then the site lifecycle. But in the build verify
> phase the site must be present which it obviously not is.
>
> Or is it not possible to use release:prepare for config and I have to do it
> by hand?
I don't like the release plugin; I think it is badly designed [1] so I
don't use it; so I cannot help with it.
> Thanks for helping me out here,
> Henning
[1] https://jira.codehaus.org/browse/MRELEASE-845
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org