You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Rob Tompkins <ch...@gmail.com> on 2018/02/15 14:17:14 UTC
Re: [jira] [Created] (COMMONSSITE-102) Commons Release Plugin doesn't
work with Commons Release Plugin
@Gary - I definitely need to fix this before taking 1.1 up and out. It shouldn’t be a problem for our other components because the unit tests of those components don’t do anything with the directory in question, namely “./target/commons-release-plugin”. I think it may be fairly quick to sort out, but I just wanted to give you (and folks) a heads up.
-Rob
> On Feb 15, 2018, at 9:15 AM, Rob Tompkins (JIRA) <ji...@apache.org> wrote:
>
> Rob Tompkins created COMMONSSITE-102:
> ----------------------------------------
>
> Summary: Commons Release Plugin doesn't work with Commons Release Plugin
> Key: COMMONSSITE-102
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-102
> Project: Commons All
> Issue Type: Bug
> Components: Commons Release Plugin
> Affects Versions: 1.0
> Reporter: Rob Tompkins
> Assignee: Rob Tompkins
> Fix For: 1.1
>
>
> The tests for the commons release plugin dirty the {{./target/commons-release-plugin}} folder for the sake of releasing. When this directory get's created in the mojos, we should check if the component we are building is the {{commons-release-plugin}}, and if that is the case and the mojo is the first one, namely {{detach-distributions}} we should delete the {{./target/commons-release-plugin}} directory.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org