Hi Chris, I updated my workspace to the latest develop bits and am trying to run through the release process to verify the doc etc.
I’m running into a problem with the new plugin. What’s the scoop? Is this the flow and one just needs to ask to resolve it to 1.0.0? $ mvn release:prepare... ... [INFO] ------------------------------------------------------------------------ [INFO] Building Apache Edgent 1.3.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ ... [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @ edgent-parent --- [INFO] Verifying that there are no local modifications... [INFO] ignoring changes on: **/pom.xml.releaseBackup, **/pom.xml.next, **/pom.xml.tag, **/pom.xml.branch, **/release.properties, **/pom.xml.backup [INFO] Executing: /bin/sh -c cd /Users/dlaboss/git/mgmt-edgent-9.10.0 && git rev-parse --show-toplevel [INFO] Working directory: /Users/dlaboss/git/mgmt-edgent-9.10.0 [INFO] Executing: /bin/sh -c cd /Users/dlaboss/git/mgmt-edgent-9.10.0 && git status --porcelain . [INFO] Working directory: /Users/dlaboss/git/mgmt-edgent-9.10.0 [INFO] Checking dependencies and plugins for snapshots ... There are still some remaining snapshot dependencies. : Do you want to resolve them now? (yes/no) no: : yes Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: : 0 Dependency 'org.apache.edgent.plugins:edgent-deployment-filter-maven-plugin' is a snapshot (1.0.0-SNAPSHOT) : Which release version should it be set to? 1.0.0: :
