edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dale LaBossiere <dml.apa...@gmail.com>
Subject Re: release:prepare fails due to the new edgent-deployment-filter-maven-plugin
Date Tue, 20 Feb 2018 19:46:12 GMT
Thanks Chris.  Good news, bad news :-)   

-DignoreSnapshots=true got me through it.
The *-<ver>-tests.jar  files are no longer present in the snapshot.  Yay!

These unwanted files are still present:
    …/*-<ver>-tests.jar.asc   # i.e., the signature file for the no longer present
tests.jar
    edgent-parent/…/edgent-parent-<ver>-source-release.*

See the orgapacheedgent-1006 staging repo at https://repository.apache.org/#stagingRepositories
<https://repository.apache.org/#stagingRepositories>

I say release the plugin ASAP :-)

— Dale

> On Feb 20, 2018, at 11:05 AM, Christofer Dutz <christofer.dutz@c-ware.de> wrote:
> 
> Hi Dale,
> 
> We need to release the plugin first. Otherwise we will not be able to do a release.
> 
> If you agree it's stable and doing its job, we should think about doing that.
> 
> We could use a timestamped snapshot and set the http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#<http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#allowTimestampedSnapshots>allowTimestampedSnapshots<http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#allowTimestampedSnapshots>
option for testing.
> 
> Chris
> 
> Outlook for Android<https://aka.ms/ghei36> herunterladen
> 
> ________________________________
> From: Dale LaBossiere <dml.apache@gmail.com>
> Sent: Tuesday, February 20, 2018 4:49:09 PM
> To: dev@edgent.apache.org
> Subject: release:prepare fails due to the new edgent-deployment-filter-maven-plugin
> 
> 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: :


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message