You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by Dale LaBossiere <dm...@gmail.com> on 2018/02/20 15:49:09 UTC
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: :
Re: release:prepare fails due to the new
edgent-deployment-filter-maven-plugin
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Dale,
today I greatly updated the plugin to filter out unwanted artifacts.
Now the plugin has a configuration section:
<configuration>
<filterRules>
<!-- Filter out all test-jars -->
<filterRule>
<type>test-jar</type>
</filterRule>
<!-- Filter out the signatures of all test-jars -->
<filterRule>
<type>jar.asc</type>
<classifier>tests</classifier>
</filterRule>
<!-- Filter out any source release archives -->
<filterRule>
<classifier>source-release</classifier>
</filterRule>
</filterRules>
</configuration>
Here each "filter" rule is a different rule that would have an artifact excluded. I added the "source-release" rule and it correctly filtered all source-release related artifacts from deployment. Now if we find something else to exclude, we wouldn't have to re-deploy the plugin and even re-release it.
Chris
Am 21.02.18, 20:19 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Hi Dale,
I'll look into this. But not today as I'm not feeling that well.
Chris
Am 21.02.18, 18:43 schrieb "Dale LaBossiere" <dm...@gmail.com>:
Thanks Chris.
I’ve rerun the process and all of the test files are now eliminated from the staged repo. yay!
+1 on starting the vote to release the plugin.
Followup questions:
- are we in agreement that the edgent-parent source-release files in the repo should NOT be present? (to clarify, those files are not the ones in the official source release repo in dist.apache.org/repos/dist <http://dist.apache.org/repos/dist>).
- if so, can the plugin, or some other tweak, eliminate them from the repo?
Thanks,
— Dale
> On Feb 21, 2018, at 6:24 AM, Christofer Dutz <ch...@c-ware.de> wrote:
> ...
> so I updated the plugin to no longer deploy the test-jar asc files and I re-deployed the plugin.
> So now all still existing problems should no longer be a problem.
>
> So if you've tested the plugin and now no problems remain, I thing we could start a vote on releasing the plugin and hopefully never have to think about it again ;-)
Re: release:prepare fails due to the new
edgent-deployment-filter-maven-plugin
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Dale,
I'll look into this. But not today as I'm not feeling that well.
Chris
Am 21.02.18, 18:43 schrieb "Dale LaBossiere" <dm...@gmail.com>:
Thanks Chris.
I’ve rerun the process and all of the test files are now eliminated from the staged repo. yay!
+1 on starting the vote to release the plugin.
Followup questions:
- are we in agreement that the edgent-parent source-release files in the repo should NOT be present? (to clarify, those files are not the ones in the official source release repo in dist.apache.org/repos/dist <http://dist.apache.org/repos/dist>).
- if so, can the plugin, or some other tweak, eliminate them from the repo?
Thanks,
— Dale
> On Feb 21, 2018, at 6:24 AM, Christofer Dutz <ch...@c-ware.de> wrote:
> ...
> so I updated the plugin to no longer deploy the test-jar asc files and I re-deployed the plugin.
> So now all still existing problems should no longer be a problem.
>
> So if you've tested the plugin and now no problems remain, I thing we could start a vote on releasing the plugin and hopefully never have to think about it again ;-)
Re: release:prepare fails due to the new
edgent-deployment-filter-maven-plugin
Posted by Dale LaBossiere <dm...@gmail.com>.
Thanks Chris.
I’ve rerun the process and all of the test files are now eliminated from the staged repo. yay!
+1 on starting the vote to release the plugin.
Followup questions:
- are we in agreement that the edgent-parent source-release files in the repo should NOT be present? (to clarify, those files are not the ones in the official source release repo in dist.apache.org/repos/dist <http://dist.apache.org/repos/dist>).
- if so, can the plugin, or some other tweak, eliminate them from the repo?
Thanks,
— Dale
> On Feb 21, 2018, at 6:24 AM, Christofer Dutz <ch...@c-ware.de> wrote:
> ...
> so I updated the plugin to no longer deploy the test-jar asc files and I re-deployed the plugin.
> So now all still existing problems should no longer be a problem.
>
> So if you've tested the plugin and now no problems remain, I thing we could start a vote on releasing the plugin and hopefully never have to think about it again ;-)
Re: release:prepare fails due to the new
edgent-deployment-filter-maven-plugin
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi all,
so I updated the plugin to no longer deploy the test-jar asc files and I re-deployed the plugin.
So now all still existing problems should no longer be a problem.
So if you've tested the plugin and now no problems remain, I thing we could start a vote on releasing the plugin and hopefully never have to think about it again ;-)
Chris
Am 21.02.18, 09:47 schrieb "Christofer Dutz" <ch...@c-ware.de>:
That's strange ... I know I deployed it there. But as soon as it's released, it will not go away again.
And regarding the signatures which are still deployed. I'll update the Testcase of the plugin and sort that out before we trigger a release of it.
Chris
Outlook for Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Dale LaBossiere <dm...@gmail.com>
Sent: Tuesday, February 20, 2018 9:28:43 PM
To: dev@edgent.apache.org
Subject: Re: release:prepare fails due to the new edgent-deployment-filter-maven-plugin
more bad news…
Travis checking for a PR also fails.
[?[1;31mERROR?[m] Plugin org.apache.edgent.plugins:edgent-deployment-filter-maven-plugin:1.0.0-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact org.apache.edgent.plugins:edgent-deployment-filter-maven-plugin:jar:1.0.0-SNAPSHOT in apache-plugins-snapshots (https://repository.apache.org/content/repositories/snapshots) -> ?[1m[Help 1]?[m
> On Feb 20, 2018, at 2:46 PM, Dale LaBossiere <dm...@gmail.com> wrote:
>
> 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 <ma...@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> <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 <https://aka.ms/ghei36>> herunterladen
>>
>> ________________________________
>> From: Dale LaBossiere <dml.apache@gmail.com <ma...@gmail.com>>
>> Sent: Tuesday, February 20, 2018 4:49:09 PM
>> To: dev@edgent.apache.org <ma...@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: :
>
Re: release:prepare fails due to the new
edgent-deployment-filter-maven-plugin
Posted by Christofer Dutz <ch...@c-ware.de>.
That's strange ... I know I deployed it there. But as soon as it's released, it will not go away again.
And regarding the signatures which are still deployed. I'll update the Testcase of the plugin and sort that out before we trigger a release of it.
Chris
Outlook for Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Dale LaBossiere <dm...@gmail.com>
Sent: Tuesday, February 20, 2018 9:28:43 PM
To: dev@edgent.apache.org
Subject: Re: release:prepare fails due to the new edgent-deployment-filter-maven-plugin
more bad news…
Travis checking for a PR also fails.
[[1;31mERROR[m] Plugin org.apache.edgent.plugins:edgent-deployment-filter-maven-plugin:1.0.0-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact org.apache.edgent.plugins:edgent-deployment-filter-maven-plugin:jar:1.0.0-SNAPSHOT in apache-plugins-snapshots (https://repository.apache.org/content/repositories/snapshots) -> [1m[Help 1][m
> On Feb 20, 2018, at 2:46 PM, Dale LaBossiere <dm...@gmail.com> wrote:
>
> 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 <ma...@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> <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 <https://aka.ms/ghei36>> herunterladen
>>
>> ________________________________
>> From: Dale LaBossiere <dml.apache@gmail.com <ma...@gmail.com>>
>> Sent: Tuesday, February 20, 2018 4:49:09 PM
>> To: dev@edgent.apache.org <ma...@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: :
>
Re: release:prepare fails due to the new
edgent-deployment-filter-maven-plugin
Posted by Dale LaBossiere <dm...@gmail.com>.
more bad news…
Travis checking for a PR also fails.
[[1;31mERROR[m] Plugin org.apache.edgent.plugins:edgent-deployment-filter-maven-plugin:1.0.0-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact org.apache.edgent.plugins:edgent-deployment-filter-maven-plugin:jar:1.0.0-SNAPSHOT in apache-plugins-snapshots (https://repository.apache.org/content/repositories/snapshots) -> [1m[Help 1][m
> On Feb 20, 2018, at 2:46 PM, Dale LaBossiere <dm...@gmail.com> wrote:
>
> 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 <ma...@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> <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 <https://aka.ms/ghei36>> herunterladen
>>
>> ________________________________
>> From: Dale LaBossiere <dml.apache@gmail.com <ma...@gmail.com>>
>> Sent: Tuesday, February 20, 2018 4:49:09 PM
>> To: dev@edgent.apache.org <ma...@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: :
>
Re: release:prepare fails due to the new
edgent-deployment-filter-maven-plugin
Posted by Dale LaBossiere <dm...@gmail.com>.
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 <ch...@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 <dm...@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: :
Re: release:prepare fails due to the new
edgent-deployment-filter-maven-plugin
Posted by Christofer Dutz <ch...@c-ware.de>.
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 <dm...@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: :