You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Gary Gregory <ga...@gmail.com> on 2018/06/13 18:21:54 UTC
[release-plugin] fail on dist
Hi Rob,
I just tried to use the release plugin and I am getting this problem
(again?).
Is there a workaround?
mvn -Dcommons.release-plugin.version=1.3-SNAPSHOT -Prelease clean package
site deploy
[INFO] --- commons-release-plugin:1.3-SNAPSHOT:stage-distributions
(stage-distributions) @ commons-dbcp2 ---
[INFO] Preparing to stage distributions
[INFO] Checking out dist from: scm:svn:
https://dist.apache.org/repos/dist/dev/commons/dbcp
Executing: cmd.exe /X /C "svn --username ggregory --no-auth-cache
--non-interactive checkout
https://dist.apache.org/repos/dist/dev/commons/dbcp
C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm"
Working directory:
C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin
[INFO] Copying RELEASE-NOTES.txt to working directory.
Executing: cmd.exe /X /C "svn add --parents --non-recursive --targets
C:\Users\ggregory\AppData\Local\Temp\maven-scm-3697247083144163331-targets"
Working directory:
C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm
[ERROR] Adding dist files failed: svn: E155007:
'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs' is not a
working copy
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 05:36 min
[INFO] Finished at: 2018-06-13T12:18:34-06:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.commons:commons-release-plugin:1.3-SNAPSHOT:stage-distributions
(stage-distributions) on project commons-dbcp2: Adding dist files failed:
svn: E155007: 'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs'
is not a working copy
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Gary
Re: [release-plugin] fail on dist
Posted by Gary Gregory <ga...@gmail.com>.
On Wed, Jun 13, 2018 at 12:52 PM Rob Tompkins <ch...@gmail.com> wrote:
>
>
> > On Jun 13, 2018, at 2:21 PM, Gary Gregory <ga...@gmail.com>
> wrote:
> >
> > Hi Rob,
> >
> > I just tried to use the release plugin and I am getting this problem
> > (again?).
> >
> > Is there a workaround?
> >
> > mvn -Dcommons.release-plugin.version=1.3-SNAPSHOT -Prelease clean package
> > site deploy
>
> The main work around would be to cd into
> `target/commons-release-plugin/scm` and svn commit everything in there.
> This bug was a quick fix (which I’ll commit right now), but it lead to the
> following:
>
> The issue at hand here becomes that we’re committing files and not
> explicitly committing their parent directories before hand. I’ve been
> chipping away at writing code to do that, but am still working on it.
>
Thanks Rob.
Gary
>
>
> -Rob
>
> >
> > [INFO] --- commons-release-plugin:1.3-SNAPSHOT:stage-distributions
> > (stage-distributions) @ commons-dbcp2 ---
> > [INFO] Preparing to stage distributions
> > [INFO] Checking out dist from: scm:svn:
> > https://dist.apache.org/repos/dist/dev/commons/dbcp
> > Executing: cmd.exe /X /C "svn --username ggregory --no-auth-cache
> > --non-interactive checkout
> > https://dist.apache.org/repos/dist/dev/commons/dbcp
> > C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm"
> > Working directory:
> > C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin
> > [INFO] Copying RELEASE-NOTES.txt to working directory.
> > Executing: cmd.exe /X /C "svn add --parents --non-recursive --targets
> >
> C:\Users\ggregory\AppData\Local\Temp\maven-scm-3697247083144163331-targets"
> > Working directory:
> > C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm
> > [ERROR] Adding dist files failed: svn: E155007:
> > 'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs' is not a
> > working copy
> >
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 05:36 min
> > [INFO] Finished at: 2018-06-13T12:18:34-06:00
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] Failed to execute goal
> >
> org.apache.commons:commons-release-plugin:1.3-SNAPSHOT:stage-distributions
> > (stage-distributions) on project commons-dbcp2: Adding dist files failed:
> > svn: E155007:
> 'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs'
> > is not a working copy
> > [ERROR]
> > [ERROR] -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> >
> > Gary
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [release-plugin] fail on dist
Posted by Rob Tompkins <ch...@gmail.com>.
> On Jun 13, 2018, at 2:21 PM, Gary Gregory <ga...@gmail.com> wrote:
>
> Hi Rob,
>
> I just tried to use the release plugin and I am getting this problem
> (again?).
>
> Is there a workaround?
>
> mvn -Dcommons.release-plugin.version=1.3-SNAPSHOT -Prelease clean package
> site deploy
The main work around would be to cd into `target/commons-release-plugin/scm` and svn commit everything in there. This bug was a quick fix (which I’ll commit right now), but it lead to the following:
The issue at hand here becomes that we’re committing files and not explicitly committing their parent directories before hand. I’ve been chipping away at writing code to do that, but am still working on it.
-Rob
>
> [INFO] --- commons-release-plugin:1.3-SNAPSHOT:stage-distributions
> (stage-distributions) @ commons-dbcp2 ---
> [INFO] Preparing to stage distributions
> [INFO] Checking out dist from: scm:svn:
> https://dist.apache.org/repos/dist/dev/commons/dbcp
> Executing: cmd.exe /X /C "svn --username ggregory --no-auth-cache
> --non-interactive checkout
> https://dist.apache.org/repos/dist/dev/commons/dbcp
> C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm"
> Working directory:
> C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin
> [INFO] Copying RELEASE-NOTES.txt to working directory.
> Executing: cmd.exe /X /C "svn add --parents --non-recursive --targets
> C:\Users\ggregory\AppData\Local\Temp\maven-scm-3697247083144163331-targets"
> Working directory:
> C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm
> [ERROR] Adding dist files failed: svn: E155007:
> 'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs' is not a
> working copy
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 05:36 min
> [INFO] Finished at: 2018-06-13T12:18:34-06:00
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.commons:commons-release-plugin:1.3-SNAPSHOT:stage-distributions
> (stage-distributions) on project commons-dbcp2: Adding dist files failed:
> svn: E155007: 'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs'
> is not a working copy
> [ERROR]
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
> Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org