If so, I may have what you’re looking for. The release-plugin skips by default, unless you set some properties in the pom.xml as to not break existing projects’ release processes.
-Rob > On May 16, 2018, at 4:32 PM, Rob Tompkins <[email protected]> wrote: > > You over on master on [collections]? > >> On May 16, 2018, at 4:24 PM, Gary Gregory (JIRA) <[email protected]> wrote: >> >> >> [ >> https://issues.apache.org/jira/browse/COMMONSSITE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478051#comment-16478051 >> ] >> >> Gary Gregory commented on COMMONSSITE-113: >> ------------------------------------------ >> >> I just saw your commit for this ticket to creates a {{sha1.properties}} >> file. I built the release plugin with {{mvn clean install >> -Danimal.sniffer.skip}} >> >> For Commons Collection at git master, I do not get a {{sha1.properties}} >> when I run: >> {noformat} >> mvn -Ptest-deploy -Prelease clean deploy >> -Dcommons.release-plugin.version=1.3-SNAPSHOT -DskipTests >> {noformat} >> Am I testing this too soon? ;) >> >>> [release-plugin] Accommodate for the RC version in the dist location. >>> --------------------------------------------------------------------- >>> >>> Key: COMMONSSITE-113 >>> URL: https://issues.apache.org/jira/browse/COMMONSSITE-113 >>> Project: Commons All >>> Issue Type: Improvement >>> Reporter: Rob Tompkins >>> Priority: Major >>> >>> Want two things: >>> (1) To have the uncompressed site in the dist location >>> (2) To have the dist location be subdirectoried by the tag name?? >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v7.6.3#76005) > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
