This doesn’t preclude anyone from using commons-parent 45, as the commons-release-plugin is disabled by default. Further it can be used in staging, you just manually have to commit the files to the staging distribution location by running an “svn commit” from “./target/commons-release-plugin/scm”.
I will finish the commons-text, commons-rng, and commons-validator releases and then go back and work on another version of the commons-releas-plugin and commons-parent. Cheers, -Rob > On Mar 16, 2018, at 11:17 AM, Rob Tompkins (JIRA) <j...@apache.org> wrote: > > Rob Tompkins created COMMONSSITE-107: > ---------------------------------------- > > Summary: [release-plugin] Adding incorrect RELEASE-NOTES.txt > file/directory to scm. > Key: COMMONSSITE-107 > URL: https://issues.apache.org/jira/browse/COMMONSSITE-107 > Project: Commons All > Issue Type: Bug > Components: Commons Release Plugin > Affects Versions: 1.1 > Reporter: Rob Tompkins > Assignee: Rob Tompkins > Fix For: 1.2 > > > When attempting to commit the releases, the {{commons-release-plugin}} > attempts to add {{./RELEASE-NOTES.txt} to the staging repo (which is outside > the svn directory structure) as opposed to the RELEASE-NOTES in > {{./target/commons-release-plugin/scm/RELEASE-NOTES.txt}}. > > > > -- > This message was sent by Atlassian JIRA > (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
