How to delete certain snapshots from Nexus
We use Nexus as our corporate Maven repository and would like to periodically delete certain SNAPSHOT artifacts. We need to be able to filter/select by groupId and by version...so delete all where groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT. Our use case is that when we refactor part of the build to use new groupIds the old ones are not valid anymore however sometimes there is a lingering reference to the old groupId, if we can delete all the old SNAPSHOTS we could find those errors now instead of when we release. Any ideas on how to do this are much appreciated. -Dave
Re: How to delete certain snapshots from Nexus
On 21/07/2015 5:53 PM, David Hoffer wrote:
I'm not sure I understand your reply. We use dependency management to
specify versions (for both external project dependencies), however that's
not the issue, we have no problem specifying the version to use for both of
those. What is only in view here are the multi-module project dependencies
and by definition they are all SNAPSHOTS as we have not released yet.
What do you mean by definition?
If the modules use the parent version as their version, they will be
SNAPSHOTS or releases depending on the parent pom having a version of
x.x.x-SNAPSHOT or x.x.x.
i.e. the module version is missing so that the parent's version is the
version of the module.
Any dependency in another module that is part of the project is set to
version${project.version}/version
dependency
groupIdcom.example/groupId
artifactIdanything-core/artifactId
version${project.version}/version
scopeprovided/scope
/dependency
Ron
Let me give an example that might help. The multi-module project is large
and is growing...you start out with these modules (all the versions are
1.0-SNAPSHOT).
groupId=com.mycompany.myproject
artifactId=artifactA, artifactB, artifactC, artifact1, artifact2, artifact3
This has been building with your CI system for 1 month when you realize you
really want these modules.
groupId=com.mycompany.myproject
artifactId=app-parent
groupId=com.mycompany.myproject.service
artifactId=artifactA, artifactB, artifactC
groupId=com.mycompany.myproject.transform
artifactId=artifact1, artifact2, artifact3
This too builds fine, however in reality somewhere in this new build is a
reference to com.mycompany.myproject:artifactA:1.0-SNAPSHOT...perhaps for
an unpack goal. The build is fine as Nexus will always have this artifact
although it was removed from the build during the refactor.
We want to purge all com.mycompany.myproject.* snapshots from Nexus so the
CI build will fail until the build is correct.
-Dave
On Tue, Jul 21, 2015 at 3:20 PM, Ron Wheeler rwhee...@artifact-software.com
wrote:
Using the parent pom to specify the versions of dependencies solves this
problem for most people.
If there are no SNAPSHOTS in the parent's properties and the parent poms
version is not a SNAPSHOT, then your project is not being built with
SNAPSHOTS.
We never worry about the SNAPSHOTs in the repo.
Ron
On 21/07/2015 2:42 PM, David Hoffer wrote:
Yeah it appears our IT group is right...Nexus doesn't have a UI/feature to
do what we want. What other options are there?
This would seem a common need, major project does a refactor of Maven GA
and want to delete all SNAPSHOTS used by the project to verify the
refactor
is 100% complete. We have had too many cases where the build is still
pointing to an old artifact that isn't part of the build anymore yet the
build is happy because old artifacts are still in Nexus.
-Dave
On Tue, Jul 21, 2015 at 12:36 PM, Karl Heinz Marbaise khmarba...@gmx.de
wrote:
Hi David,
On 7/21/15 6:03 PM, David Hoffer wrote:
We use Nexus as our corporate Maven repository and would like to
periodically delete certain SNAPSHOT artifacts. We need to be able to
filter/select by groupId and by version...so delete all where
groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT.
You can only delete all kind of SNAPSHOT's in Nexus based on a time
frame
for example delete all SNAPSHOT's which are older than 30 days etc..
Our use case is that when we refactor part of the build to use new
groupIds
the old ones are not valid anymore however sometimes there is a
lingering
reference to the old groupId, if we can delete all the old SNAPSHOTS we
could find those errors now instead of when we release.
Any ideas on how to do this are much appreciated.
-Dave
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to delete certain snapshots from Nexus
I didn't say x.x.x is the only version in the parent. I said it is a
SNAPSHOT. The version varies (of course) but in my prior example I said it
was 1.0-SNAPSHOT.
-Dave
On Tue, Jul 21, 2015 at 9:36 PM, Ron Wheeler rwhee...@artifact-software.com
wrote:
Where are the possible SNAPSHOT versions creeping into the build if x.x.x
is the only versions in your parent and the dependencies do not have any
versions (as I suggested).
Ron
On 21/07/2015 10:54 PM, David Hoffer wrote:
Yes we use one version for all modules...comes from top level. What I
mean
is this is a non-release build so by maven definition is a snapshot. E.g.
x.x.x is built only once at release, x.x.x-SNAPSHOT is built on every CI
build.
-Dave
On Tue, Jul 21, 2015 at 8:38 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
On 21/07/2015 5:53 PM, David Hoffer wrote:
I'm not sure I understand your reply. We use dependency management to
specify versions (for both external project dependencies), however
that's
not the issue, we have no problem specifying the version to use for both
of
those. What is only in view here are the multi-module project
dependencies
and by definition they are all SNAPSHOTS as we have not released yet.
What do you mean by definition?
If the modules use the parent version as their version, they will be
SNAPSHOTS or releases depending on the parent pom having a version of
x.x.x-SNAPSHOT or x.x.x.
i.e. the module version is missing so that the parent's version is the
version of the module.
Any dependency in another module that is part of the project is set to
version${project.version}/version
dependency
groupIdcom.example/groupId
artifactIdanything-core/artifactId
version${project.version}/version
scopeprovided/scope
/dependency
Ron
Let me give an example that might help. The multi-module project is
large
and is growing...you start out with these modules (all the versions are
1.0-SNAPSHOT).
groupId=com.mycompany.myproject
artifactId=artifactA, artifactB, artifactC, artifact1, artifact2,
artifact3
This has been building with your CI system for 1 month when you realize
you
really want these modules.
groupId=com.mycompany.myproject
artifactId=app-parent
groupId=com.mycompany.myproject.service
artifactId=artifactA, artifactB, artifactC
groupId=com.mycompany.myproject.transform
artifactId=artifact1, artifact2, artifact3
This too builds fine, however in reality somewhere in this new build is
a
reference to com.mycompany.myproject:artifactA:1.0-SNAPSHOT...perhaps
for
an unpack goal. The build is fine as Nexus will always have this
artifact
although it was removed from the build during the refactor.
We want to purge all com.mycompany.myproject.* snapshots from Nexus so
the
CI build will fail until the build is correct.
-Dave
On Tue, Jul 21, 2015 at 3:20 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
Using the parent pom to specify the versions of dependencies solves
this
problem for most people.
If there are no SNAPSHOTS in the parent's properties and the parent
poms
version is not a SNAPSHOT, then your project is not being built with
SNAPSHOTS.
We never worry about the SNAPSHOTs in the repo.
Ron
On 21/07/2015 2:42 PM, David Hoffer wrote:
Yeah it appears our IT group is right...Nexus doesn't have a
UI/feature
to
do what we want. What other options are there?
This would seem a common need, major project does a refactor of Maven
GA
and want to delete all SNAPSHOTS used by the project to verify the
refactor
is 100% complete. We have had too many cases where the build is still
pointing to an old artifact that isn't part of the build anymore yet
the
build is happy because old artifacts are still in Nexus.
-Dave
On Tue, Jul 21, 2015 at 12:36 PM, Karl Heinz Marbaise
khmarba...@gmx.de
wrote:
Hi David,
On 7/21/15 6:03 PM, David Hoffer wrote:
We use Nexus as our corporate Maven repository and would like to
periodically delete certain SNAPSHOT artifacts. We need to be able
to
filter/select by groupId and by version...so delete all where
groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT.
You can only delete all kind of SNAPSHOT's in Nexus based on a
time
frame
for example delete all SNAPSHOT's which are older than 30 days etc..
Our use case is that when we refactor part of the build to use new
groupIds
the old ones are not valid anymore however sometimes there is a
lingering
reference to the old groupId, if we can delete all the old SNAPSHOTS
we
could find those errors now instead of when we release.
Any ideas on how to do this are much appreciated.
-Dave
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
How to fix this error?
Hello My name is Simone Sciarretta, I am student at the University of Pisa in the Communications Engineering Department I am experimenting a problem with the OpenIoT platform, and particularly when I am following the example of executing the command mvn clean package jboss-as:deploy in the library scheduler.core described in the deliverable D4.3.1. I get an error that restrict me to create the file .war and I have not find the way to resolve this problem. I am including a screen shot of the error and I will appreciate if you can help me to understand and tell me what is the problem? If I have to enforce some changes in the repository or modify something in th pom.xml file please let me know? In advance thank you very much for your help. Regards Simone Sciarretta --- Questa e-mail è stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to fix this error?
Hello My name is Simone Sciarretta, I am student at the University of Pisa in the Communications Engineering Department I am experimenting a problem with the OpenIoT platform, and particularly when I am following the example of executing the command mvn clean package jboss-as:deploy in the library scheduler.core described in the deliverable D4.3.1. I get an error that restrict me to create the file .war and I have not find the way to resolve this problem. I am including a screen shot of the error and I will appreciate if you can help me to understand and tell me what is the problem? If I have to enforce some changes in the repository or modify something in th pom.xml file please let me know? In advance thank you very much for your help. Regards Simone Sciarretta --- Questa e-mail è stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to delete certain snapshots from Nexus
Nexus tasks ? Jeff Le 21 juil. 2015 18:03, David Hoffer dhoff...@gmail.com a écrit : We use Nexus as our corporate Maven repository and would like to periodically delete certain SNAPSHOT artifacts. We need to be able to filter/select by groupId and by version...so delete all where groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT. Our use case is that when we refactor part of the build to use new groupIds the old ones are not valid anymore however sometimes there is a lingering reference to the old groupId, if we can delete all the old SNAPSHOTS we could find those errors now instead of when we release. Any ideas on how to do this are much appreciated. -Dave
Unsupported protocol: ‘http’” during maven threaded build.
We’re using maven 3.2.5 and recently migrated to a threaded build and I now get this error: [ERROR] Unsupported protocol: 'http' [ERROR] Unsupported protocol: 'https' [ERROR] Unsupported protocol: 'http' [ERROR] Unsupported protocol: 'http' [ERROR] Unsupported protocol: 'https' [ERROR] Unsupported protocol: 'http' [ERROR] Unsupported protocol: 'http' I get about 40 of those and the build fails. It only happens intermittently so I think on of the plugins isn’t thread safe. Any recommendation of a fix and how to resolve this? -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile https://plus.google.com/102718274791889610666/posts
Re: How to delete certain snapshots from Nexus
Our IT group handles managing Nexus and they say there is no Nexus interface/feature to do this. The last time we requested this they ended up deleting these directly on the file system. Ideally I'd like to find a way developers could do this, either using a Maven plugin or something similar, or by a Nexus API if that exists. -Dave On Tue, Jul 21, 2015 at 12:07 PM, Jeff MAURY jeffma...@jeffmaury.com wrote: Nexus tasks ? Jeff Le 21 juil. 2015 18:03, David Hoffer dhoff...@gmail.com a écrit : We use Nexus as our corporate Maven repository and would like to periodically delete certain SNAPSHOT artifacts. We need to be able to filter/select by groupId and by version...so delete all where groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT. Our use case is that when we refactor part of the build to use new groupIds the old ones are not valid anymore however sometimes there is a lingering reference to the old groupId, if we can delete all the old SNAPSHOTS we could find those errors now instead of when we release. Any ideas on how to do this are much appreciated. -Dave
Re: How to delete certain snapshots from Nexus
Apparently our communication has broken down, it seems your not
understanding the issue/question.
I did find that Nexus does have an API we can use for this...I sure wish
there was a more 'packaged' solution but I've discussed it with our IT
department and between us I think we can solve this issue using that
approach. If anyone knows of a better solution please let me know.
-Dave
On Tue, Jul 21, 2015 at 10:32 PM, Ron Wheeler
rwhee...@artifact-software.com wrote:
If you have SNAPSHOTs specified, you will get SNAPSHOTs in the build.
When you remove the SNAPSHOT from the parent, there should not be any way
for a SNAPSHOT to be included.
I am not sure where the SNAPSHOTS are being brought in to a x.x.x release
unless you are allowing modules to specify the versions of their
dependencies.
Stop that.
Modules should have no versions on an dependency unless it is a reference
to a property in the parent.
Modules should have no references to a version on a dependency that is one
of the modules that your wrote - version${project.version}/version
Ron
On 21/07/2015 11:40 PM, David Hoffer wrote:
I didn't say x.x.x is the only version in the parent. I said it is a
SNAPSHOT. The version varies (of course) but in my prior example I said
it
was 1.0-SNAPSHOT.
-Dave
On Tue, Jul 21, 2015 at 9:36 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
Where are the possible SNAPSHOT versions creeping into the build if x.x.x
is the only versions in your parent and the dependencies do not have any
versions (as I suggested).
Ron
On 21/07/2015 10:54 PM, David Hoffer wrote:
Yes we use one version for all modules...comes from top level. What I
mean
is this is a non-release build so by maven definition is a snapshot.
E.g.
x.x.x is built only once at release, x.x.x-SNAPSHOT is built on every CI
build.
-Dave
On Tue, Jul 21, 2015 at 8:38 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
On 21/07/2015 5:53 PM, David Hoffer wrote:
I'm not sure I understand your reply. We use dependency management
to
specify versions (for both external project dependencies), however
that's
not the issue, we have no problem specifying the version to use for
both
of
those. What is only in view here are the multi-module project
dependencies
and by definition they are all SNAPSHOTS as we have not released yet.
What do you mean by definition?
If the modules use the parent version as their version, they will be
SNAPSHOTS or releases depending on the parent pom having a version of
x.x.x-SNAPSHOT or x.x.x.
i.e. the module version is missing so that the parent's version is the
version of the module.
Any dependency in another module that is part of the project is set to
version${project.version}/version
dependency
groupIdcom.example/groupId
artifactIdanything-core/artifactId
version${project.version}/version
scopeprovided/scope
/dependency
Ron
Let me give an example that might help. The multi-module project is
large
and is growing...you start out with these modules (all the versions
are
1.0-SNAPSHOT).
groupId=com.mycompany.myproject
artifactId=artifactA, artifactB, artifactC, artifact1, artifact2,
artifact3
This has been building with your CI system for 1 month when you
realize
you
really want these modules.
groupId=com.mycompany.myproject
artifactId=app-parent
groupId=com.mycompany.myproject.service
artifactId=artifactA, artifactB, artifactC
groupId=com.mycompany.myproject.transform
artifactId=artifact1, artifact2, artifact3
This too builds fine, however in reality somewhere in this new build
is
a
reference to com.mycompany.myproject:artifactA:1.0-SNAPSHOT...perhaps
for
an unpack goal. The build is fine as Nexus will always have this
artifact
although it was removed from the build during the refactor.
We want to purge all com.mycompany.myproject.* snapshots from Nexus so
the
CI build will fail until the build is correct.
-Dave
On Tue, Jul 21, 2015 at 3:20 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
Using the parent pom to specify the versions of dependencies solves
this
problem for most people.
If there are no SNAPSHOTS in the parent's properties and the parent
poms
version is not a SNAPSHOT, then your project is not being built with
SNAPSHOTS.
We never worry about the SNAPSHOTs in the repo.
Ron
On 21/07/2015 2:42 PM, David Hoffer wrote:
Yeah it appears our IT group is right...Nexus doesn't have a
UI/feature
to
do what we want. What other options are there?
This would seem a common need, major project does a refactor of
Maven
GA
and want to delete all SNAPSHOTS used by the project to verify the
refactor
is 100% complete. We have had too many cases where the build is
still
pointing to an old artifact that isn't part of the build anymore yet
the
build is happy because old artifacts
Re: How to delete certain snapshots from Nexus
If you have SNAPSHOTs specified, you will get SNAPSHOTs in the build.
When you remove the SNAPSHOT from the parent, there should not be any
way for a SNAPSHOT to be included.
I am not sure where the SNAPSHOTS are being brought in to a x.x.x
release unless you are allowing modules to specify the versions of their
dependencies.
Stop that.
Modules should have no versions on an dependency unless it is a
reference to a property in the parent.
Modules should have no references to a version on a dependency that is
one of the modules that your wrote - version${project.version}/version
Ron
On 21/07/2015 11:40 PM, David Hoffer wrote:
I didn't say x.x.x is the only version in the parent. I said it is a
SNAPSHOT. The version varies (of course) but in my prior example I said it
was 1.0-SNAPSHOT.
-Dave
On Tue, Jul 21, 2015 at 9:36 PM, Ron Wheeler rwhee...@artifact-software.com
wrote:
Where are the possible SNAPSHOT versions creeping into the build if x.x.x
is the only versions in your parent and the dependencies do not have any
versions (as I suggested).
Ron
On 21/07/2015 10:54 PM, David Hoffer wrote:
Yes we use one version for all modules...comes from top level. What I
mean
is this is a non-release build so by maven definition is a snapshot. E.g.
x.x.x is built only once at release, x.x.x-SNAPSHOT is built on every CI
build.
-Dave
On Tue, Jul 21, 2015 at 8:38 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
On 21/07/2015 5:53 PM, David Hoffer wrote:
I'm not sure I understand your reply. We use dependency management to
specify versions (for both external project dependencies), however
that's
not the issue, we have no problem specifying the version to use for both
of
those. What is only in view here are the multi-module project
dependencies
and by definition they are all SNAPSHOTS as we have not released yet.
What do you mean by definition?
If the modules use the parent version as their version, they will be
SNAPSHOTS or releases depending on the parent pom having a version of
x.x.x-SNAPSHOT or x.x.x.
i.e. the module version is missing so that the parent's version is the
version of the module.
Any dependency in another module that is part of the project is set to
version${project.version}/version
dependency
groupIdcom.example/groupId
artifactIdanything-core/artifactId
version${project.version}/version
scopeprovided/scope
/dependency
Ron
Let me give an example that might help. The multi-module project is
large
and is growing...you start out with these modules (all the versions are
1.0-SNAPSHOT).
groupId=com.mycompany.myproject
artifactId=artifactA, artifactB, artifactC, artifact1, artifact2,
artifact3
This has been building with your CI system for 1 month when you realize
you
really want these modules.
groupId=com.mycompany.myproject
artifactId=app-parent
groupId=com.mycompany.myproject.service
artifactId=artifactA, artifactB, artifactC
groupId=com.mycompany.myproject.transform
artifactId=artifact1, artifact2, artifact3
This too builds fine, however in reality somewhere in this new build is
a
reference to com.mycompany.myproject:artifactA:1.0-SNAPSHOT...perhaps
for
an unpack goal. The build is fine as Nexus will always have this
artifact
although it was removed from the build during the refactor.
We want to purge all com.mycompany.myproject.* snapshots from Nexus so
the
CI build will fail until the build is correct.
-Dave
On Tue, Jul 21, 2015 at 3:20 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
Using the parent pom to specify the versions of dependencies solves
this
problem for most people.
If there are no SNAPSHOTS in the parent's properties and the parent
poms
version is not a SNAPSHOT, then your project is not being built with
SNAPSHOTS.
We never worry about the SNAPSHOTs in the repo.
Ron
On 21/07/2015 2:42 PM, David Hoffer wrote:
Yeah it appears our IT group is right...Nexus doesn't have a
UI/feature
to
do what we want. What other options are there?
This would seem a common need, major project does a refactor of Maven
GA
and want to delete all SNAPSHOTS used by the project to verify the
refactor
is 100% complete. We have had too many cases where the build is still
pointing to an old artifact that isn't part of the build anymore yet
the
build is happy because old artifacts are still in Nexus.
-Dave
On Tue, Jul 21, 2015 at 12:36 PM, Karl Heinz Marbaise
khmarba...@gmx.de
wrote:
Hi David,
On 7/21/15 6:03 PM, David Hoffer wrote:
We use Nexus as our corporate Maven repository and would like to
periodically delete certain SNAPSHOT artifacts. We need to be able
to
filter/select by groupId and by version...so delete all where
groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT.
You can only delete all kind of SNAPSHOT's in Nexus based on a
time
frame
for example delete all SNAPSHOT's which are older than 30 days etc..
Re: How to delete certain snapshots from Nexus
Nexus has a REST api:
http://blog.sonatype.com/2012/07/learning-the-nexus-rest-api-read-the-docs-or-fire-up-a-browser/#.Va8oFhOqpBc
It allows deleting files and folders, it will even reconstruct the
metadata. I've done a few CURL to delete file on the past.
Anyway, maven provides an offline mode, if the problem is only testing if
it's not getting dependencies from outside the reactor. Or you can use
versions:set and set something completely arbitrary
Other option is not deploy snapshots at all.
http://developer-blog.cloudbees.com/2012/12/should-you-deploy-snapshots.html
Or deploy to a repo that your CI won't fetch.
But no, it's not really a common need. Deleting non-unique and released
snapshots is the mainstream feature, and that's all I've seen being used.
On 22 July 2015 at 15:11, David Hoffer dhoff...@gmail.com wrote:
Apparently our communication has broken down, it seems your not
understanding the issue/question.
I did find that Nexus does have an API we can use for this...I sure wish
there was a more 'packaged' solution but I've discussed it with our IT
department and between us I think we can solve this issue using that
approach. If anyone knows of a better solution please let me know.
-Dave
On Tue, Jul 21, 2015 at 10:32 PM, Ron Wheeler
rwhee...@artifact-software.com wrote:
If you have SNAPSHOTs specified, you will get SNAPSHOTs in the build.
When you remove the SNAPSHOT from the parent, there should not be any way
for a SNAPSHOT to be included.
I am not sure where the SNAPSHOTS are being brought in to a x.x.x release
unless you are allowing modules to specify the versions of their
dependencies.
Stop that.
Modules should have no versions on an dependency unless it is a reference
to a property in the parent.
Modules should have no references to a version on a dependency that is
one
of the modules that your wrote - version${project.version}/version
Ron
On 21/07/2015 11:40 PM, David Hoffer wrote:
I didn't say x.x.x is the only version in the parent. I said it is a
SNAPSHOT. The version varies (of course) but in my prior example I said
it
was 1.0-SNAPSHOT.
-Dave
On Tue, Jul 21, 2015 at 9:36 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
Where are the possible SNAPSHOT versions creeping into the build if
x.x.x
is the only versions in your parent and the dependencies do not have
any
versions (as I suggested).
Ron
On 21/07/2015 10:54 PM, David Hoffer wrote:
Yes we use one version for all modules...comes from top level. What I
mean
is this is a non-release build so by maven definition is a snapshot.
E.g.
x.x.x is built only once at release, x.x.x-SNAPSHOT is built on every
CI
build.
-Dave
On Tue, Jul 21, 2015 at 8:38 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
On 21/07/2015 5:53 PM, David Hoffer wrote:
I'm not sure I understand your reply. We use dependency management
to
specify versions (for both external project dependencies), however
that's
not the issue, we have no problem specifying the version to use for
both
of
those. What is only in view here are the multi-module project
dependencies
and by definition they are all SNAPSHOTS as we have not released
yet.
What do you mean by definition?
If the modules use the parent version as their version, they will be
SNAPSHOTS or releases depending on the parent pom having a version of
x.x.x-SNAPSHOT or x.x.x.
i.e. the module version is missing so that the parent's version is
the
version of the module.
Any dependency in another module that is part of the project is set
to
version${project.version}/version
dependency
groupIdcom.example/groupId
artifactIdanything-core/artifactId
version${project.version}/version
scopeprovided/scope
/dependency
Ron
Let me give an example that might help. The multi-module project
is
large
and is growing...you start out with these modules (all the versions
are
1.0-SNAPSHOT).
groupId=com.mycompany.myproject
artifactId=artifactA, artifactB, artifactC, artifact1, artifact2,
artifact3
This has been building with your CI system for 1 month when you
realize
you
really want these modules.
groupId=com.mycompany.myproject
artifactId=app-parent
groupId=com.mycompany.myproject.service
artifactId=artifactA, artifactB, artifactC
groupId=com.mycompany.myproject.transform
artifactId=artifact1, artifact2, artifact3
This too builds fine, however in reality somewhere in this new build
is
a
reference to
com.mycompany.myproject:artifactA:1.0-SNAPSHOT...perhaps
for
an unpack goal. The build is fine as Nexus will always have this
artifact
although it was removed from the build during the refactor.
We want to purge all com.mycompany.myproject.* snapshots from Nexus
so
the
Re: How to delete certain snapshots from Nexus
Yes we use one version for all modules...comes from top level. What I mean
is this is a non-release build so by maven definition is a snapshot. E.g.
x.x.x is built only once at release, x.x.x-SNAPSHOT is built on every CI
build.
-Dave
On Tue, Jul 21, 2015 at 8:38 PM, Ron Wheeler rwhee...@artifact-software.com
wrote:
On 21/07/2015 5:53 PM, David Hoffer wrote:
I'm not sure I understand your reply. We use dependency management to
specify versions (for both external project dependencies), however
that's
not the issue, we have no problem specifying the version to use for both
of
those. What is only in view here are the multi-module project
dependencies
and by definition they are all SNAPSHOTS as we have not released yet.
What do you mean by definition?
If the modules use the parent version as their version, they will be
SNAPSHOTS or releases depending on the parent pom having a version of
x.x.x-SNAPSHOT or x.x.x.
i.e. the module version is missing so that the parent's version is the
version of the module.
Any dependency in another module that is part of the project is set to
version${project.version}/version
dependency
groupIdcom.example/groupId
artifactIdanything-core/artifactId
version${project.version}/version
scopeprovided/scope
/dependency
Ron
Let me give an example that might help. The multi-module project is large
and is growing...you start out with these modules (all the versions are
1.0-SNAPSHOT).
groupId=com.mycompany.myproject
artifactId=artifactA, artifactB, artifactC, artifact1, artifact2,
artifact3
This has been building with your CI system for 1 month when you realize
you
really want these modules.
groupId=com.mycompany.myproject
artifactId=app-parent
groupId=com.mycompany.myproject.service
artifactId=artifactA, artifactB, artifactC
groupId=com.mycompany.myproject.transform
artifactId=artifact1, artifact2, artifact3
This too builds fine, however in reality somewhere in this new build is a
reference to com.mycompany.myproject:artifactA:1.0-SNAPSHOT...perhaps for
an unpack goal. The build is fine as Nexus will always have this artifact
although it was removed from the build during the refactor.
We want to purge all com.mycompany.myproject.* snapshots from Nexus so the
CI build will fail until the build is correct.
-Dave
On Tue, Jul 21, 2015 at 3:20 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
Using the parent pom to specify the versions of dependencies solves this
problem for most people.
If there are no SNAPSHOTS in the parent's properties and the parent poms
version is not a SNAPSHOT, then your project is not being built with
SNAPSHOTS.
We never worry about the SNAPSHOTs in the repo.
Ron
On 21/07/2015 2:42 PM, David Hoffer wrote:
Yeah it appears our IT group is right...Nexus doesn't have a UI/feature
to
do what we want. What other options are there?
This would seem a common need, major project does a refactor of Maven GA
and want to delete all SNAPSHOTS used by the project to verify the
refactor
is 100% complete. We have had too many cases where the build is still
pointing to an old artifact that isn't part of the build anymore yet the
build is happy because old artifacts are still in Nexus.
-Dave
On Tue, Jul 21, 2015 at 12:36 PM, Karl Heinz Marbaise
khmarba...@gmx.de
wrote:
Hi David,
On 7/21/15 6:03 PM, David Hoffer wrote:
We use Nexus as our corporate Maven repository and would like to
periodically delete certain SNAPSHOT artifacts. We need to be able to
filter/select by groupId and by version...so delete all where
groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT.
You can only delete all kind of SNAPSHOT's in Nexus based on a time
frame
for example delete all SNAPSHOT's which are older than 30 days etc..
Our use case is that when we refactor part of the build to use new
groupIds
the old ones are not valid anymore however sometimes there is a
lingering
reference to the old groupId, if we can delete all the old SNAPSHOTS
we
could find those errors now instead of when we release.
Any ideas on how to do this are much appreciated.
-Dave
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
Re: How to delete certain snapshots from Nexus
Where are the possible SNAPSHOT versions creeping into the build if
x.x.x is the only versions in your parent and the dependencies do not
have any versions (as I suggested).
Ron
On 21/07/2015 10:54 PM, David Hoffer wrote:
Yes we use one version for all modules...comes from top level. What I mean
is this is a non-release build so by maven definition is a snapshot. E.g.
x.x.x is built only once at release, x.x.x-SNAPSHOT is built on every CI
build.
-Dave
On Tue, Jul 21, 2015 at 8:38 PM, Ron Wheeler rwhee...@artifact-software.com
wrote:
On 21/07/2015 5:53 PM, David Hoffer wrote:
I'm not sure I understand your reply. We use dependency management to
specify versions (for both external project dependencies), however
that's
not the issue, we have no problem specifying the version to use for both
of
those. What is only in view here are the multi-module project
dependencies
and by definition they are all SNAPSHOTS as we have not released yet.
What do you mean by definition?
If the modules use the parent version as their version, they will be
SNAPSHOTS or releases depending on the parent pom having a version of
x.x.x-SNAPSHOT or x.x.x.
i.e. the module version is missing so that the parent's version is the
version of the module.
Any dependency in another module that is part of the project is set to
version${project.version}/version
dependency
groupIdcom.example/groupId
artifactIdanything-core/artifactId
version${project.version}/version
scopeprovided/scope
/dependency
Ron
Let me give an example that might help. The multi-module project is large
and is growing...you start out with these modules (all the versions are
1.0-SNAPSHOT).
groupId=com.mycompany.myproject
artifactId=artifactA, artifactB, artifactC, artifact1, artifact2,
artifact3
This has been building with your CI system for 1 month when you realize
you
really want these modules.
groupId=com.mycompany.myproject
artifactId=app-parent
groupId=com.mycompany.myproject.service
artifactId=artifactA, artifactB, artifactC
groupId=com.mycompany.myproject.transform
artifactId=artifact1, artifact2, artifact3
This too builds fine, however in reality somewhere in this new build is a
reference to com.mycompany.myproject:artifactA:1.0-SNAPSHOT...perhaps for
an unpack goal. The build is fine as Nexus will always have this artifact
although it was removed from the build during the refactor.
We want to purge all com.mycompany.myproject.* snapshots from Nexus so the
CI build will fail until the build is correct.
-Dave
On Tue, Jul 21, 2015 at 3:20 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:
Using the parent pom to specify the versions of dependencies solves this
problem for most people.
If there are no SNAPSHOTS in the parent's properties and the parent poms
version is not a SNAPSHOT, then your project is not being built with
SNAPSHOTS.
We never worry about the SNAPSHOTs in the repo.
Ron
On 21/07/2015 2:42 PM, David Hoffer wrote:
Yeah it appears our IT group is right...Nexus doesn't have a UI/feature
to
do what we want. What other options are there?
This would seem a common need, major project does a refactor of Maven GA
and want to delete all SNAPSHOTS used by the project to verify the
refactor
is 100% complete. We have had too many cases where the build is still
pointing to an old artifact that isn't part of the build anymore yet the
build is happy because old artifacts are still in Nexus.
-Dave
On Tue, Jul 21, 2015 at 12:36 PM, Karl Heinz Marbaise
khmarba...@gmx.de
wrote:
Hi David,
On 7/21/15 6:03 PM, David Hoffer wrote:
We use Nexus as our corporate Maven repository and would like to
periodically delete certain SNAPSHOT artifacts. We need to be able to
filter/select by groupId and by version...so delete all where
groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT.
You can only delete all kind of SNAPSHOT's in Nexus based on a time
frame
for example delete all SNAPSHOT's which are older than 30 days etc..
Our use case is that when we refactor part of the build to use new
groupIds
the old ones are not valid anymore however sometimes there is a
lingering
reference to the old groupId, if we can delete all the old SNAPSHOTS
we
could find those errors now instead of when we release.
Any ideas on how to do this are much appreciated.
-Dave
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
Re: How to delete certain snapshots from Nexus
Yeah it appears our IT group is right...Nexus doesn't have a UI/feature to do what we want. What other options are there? This would seem a common need, major project does a refactor of Maven GA and want to delete all SNAPSHOTS used by the project to verify the refactor is 100% complete. We have had too many cases where the build is still pointing to an old artifact that isn't part of the build anymore yet the build is happy because old artifacts are still in Nexus. -Dave On Tue, Jul 21, 2015 at 12:36 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi David, On 7/21/15 6:03 PM, David Hoffer wrote: We use Nexus as our corporate Maven repository and would like to periodically delete certain SNAPSHOT artifacts. We need to be able to filter/select by groupId and by version...so delete all where groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT. You can only delete all kind of SNAPSHOT's in Nexus based on a time frame for example delete all SNAPSHOT's which are older than 30 days etc.. Our use case is that when we refactor part of the build to use new groupIds the old ones are not valid anymore however sometimes there is a lingering reference to the old groupId, if we can delete all the old SNAPSHOTS we could find those errors now instead of when we release. Any ideas on how to do this are much appreciated. -Dave Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Update non-unique snapshots from Artifactory to local repository
Hello, I am new to maven and do not know how to solve this issue: I decided not to keep timestampped artifacts in Aritfactory but now maven is not downloading newer artifacts from Artifactory, although in metadata the versions differ. I do not want to manually delete my local copy of an artifact in order to download the latest version, it beats the hole purpose of maven. Is there an workaround for this? I can't seem to find any solution. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unsupported protocol: ‘http’” during maven threaded build.
Hi Kevin, On 7/21/15 6:59 PM, Kevin Burton wrote: We’re using maven 3.2.5 and recently migrated to a threaded build and I now get this error: [ERROR] Unsupported protocol: 'http' [ERROR] Unsupported protocol: 'https' [ERROR] Unsupported protocol: 'http' [ERROR] Unsupported protocol: 'http' [ERROR] Unsupported protocol: 'https' [ERROR] Unsupported protocol: 'http' [ERROR] Unsupported protocol: 'http' I get about 40 of those and the build fails. It only happens intermittently so I think on of the plugins isn’t thread safe. Any recommendation of a fix and how to resolve this? First it would be helpful to have full log output. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to fix this error?
Hi Simone: The mailing list appears to block screenshots. Could you copy/paste the text of the error message? Thanks, Greg Trasuk On Jul 21, 2015, at 2:17 PM, Simone simone.sciarre...@hotmail.it wrote: Hello My name is Simone Sciarretta, I am student at the University of Pisa in the Communications Engineering Department I am experimenting a problem with the OpenIoT platform, and particularly when I am following the example of executing the command mvn clean package jboss-as:deploy in the library scheduler.core described in the deliverable D4.3.1. I get an error that restrict me to create the file .war and I have not find the way to resolve this problem. I am including a screen shot of the error and I will appreciate if you can help me to understand and tell me what is the problem? If I have to enforce some changes in the repository or modify something in th pom.xml file please let me know? In advance thank you very much for your help. Regards Simone Sciarretta --- Questa e-mail è stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to delete certain snapshots from Nexus
Hi David, On 7/21/15 6:03 PM, David Hoffer wrote: We use Nexus as our corporate Maven repository and would like to periodically delete certain SNAPSHOT artifacts. We need to be able to filter/select by groupId and by version...so delete all where groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT. You can only delete all kind of SNAPSHOT's in Nexus based on a time frame for example delete all SNAPSHOT's which are older than 30 days etc.. Our use case is that when we refactor part of the build to use new groupIds the old ones are not valid anymore however sometimes there is a lingering reference to the old groupId, if we can delete all the old SNAPSHOTS we could find those errors now instead of when we release. Any ideas on how to do this are much appreciated. -Dave Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to fix this error?
This is the error: Failed to execute goal on project scheduler.core: Could not resolve dependencies for project org.openiot:scheduler.core:war:0.0.1: The following artifacts could not be resolved: org.openiot:utils.commons:jar:0.0.1, org.openiot:lsm-light.client:jar:0.0.1: Failure to find org.openiot:utils.commons:jar:0.0.1 in http://maven.repository.redhat.com/techpreview/all was cached in the local repository, resolution will not be reattempted until the update interval of jboss-ga-repository has elapsed or updates are forced - [Help1] Il 21/07/2015 20:28, Greg Trasuk ha scritto: Hi Simone: The mailing list appears to block screenshots. Could you copy/paste the text of the error message? Thanks, Greg Trasuk On Jul 21, 2015, at 2:17 PM, Simone simone.sciarre...@hotmail.it wrote: Hello My name is Simone Sciarretta, I am student at the University of Pisa in the Communications Engineering Department I am experimenting a problem with the OpenIoT platform, and particularly when I am following the example of executing the command mvn clean package jboss-as:deploy in the library scheduler.core described in the deliverable D4.3.1. I get an error that restrict me to create the file .war and I have not find the way to resolve this problem. I am including a screen shot of the error and I will appreciate if you can help me to understand and tell me what is the problem? If I have to enforce some changes in the repository or modify something in th pom.xml file please let me know? In advance thank you very much for your help. Regards Simone Sciarretta --- Questa e-mail è stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --- Questa e-mail è stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to delete certain snapshots from Nexus
Hi Dave, Our IT group handles managing Nexus and they say there is no Nexus interface/feature to do this. You can use the Remove Snapshots from Repository scheduled task. See: https://books.sonatype.com/nexus-book/reference/scheduled-tasks.html Regards, Curtis On Tue, Jul 21, 2015 at 1:20 PM, David Hoffer dhoff...@gmail.com wrote: Our IT group handles managing Nexus and they say there is no Nexus interface/feature to do this. The last time we requested this they ended up deleting these directly on the file system. Ideally I'd like to find a way developers could do this, either using a Maven plugin or something similar, or by a Nexus API if that exists. -Dave On Tue, Jul 21, 2015 at 12:07 PM, Jeff MAURY jeffma...@jeffmaury.com wrote: Nexus tasks ? Jeff Le 21 juil. 2015 18:03, David Hoffer dhoff...@gmail.com a écrit : We use Nexus as our corporate Maven repository and would like to periodically delete certain SNAPSHOT artifacts. We need to be able to filter/select by groupId and by version...so delete all where groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT. Our use case is that when we refactor part of the build to use new groupIds the old ones are not valid anymore however sometimes there is a lingering reference to the old groupId, if we can delete all the old SNAPSHOTS we could find those errors now instead of when we release. Any ideas on how to do this are much appreciated. -Dave
Re: Update non-unique snapshots from Artifactory to local repository
Hello, not sure if you are asking about the general handling or a specific problem with Artifactory. But with mvn you can use the -U switch to force a snapshot update. Otherwise it will use the updatePolicy from your settings.xml (I think daily would be the default for snapshots repo). Gruss Bernd Am Tue, 21 Jul 2015 22:28:30 +0300 schrieb Alex Ditu ditu.alexan...@gmail.com: Hello, I am new to maven and do not know how to solve this issue: I decided not to keep timestampped artifacts in Aritfactory but now maven is not downloading newer artifacts from Artifactory, although in metadata the versions differ. I do not want to manually delete my local copy of an artifact in order to download the latest version, it beats the hole purpose of maven. Is there an workaround for this? I can't seem to find any solution. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to delete certain snapshots from Nexus
I'm not sure I understand your reply. We use dependency management to specify versions (for both external project dependencies), however that's not the issue, we have no problem specifying the version to use for both of those. What is only in view here are the multi-module project dependencies and by definition they are all SNAPSHOTS as we have not released yet. Let me give an example that might help. The multi-module project is large and is growing...you start out with these modules (all the versions are 1.0-SNAPSHOT). groupId=com.mycompany.myproject artifactId=artifactA, artifactB, artifactC, artifact1, artifact2, artifact3 This has been building with your CI system for 1 month when you realize you really want these modules. groupId=com.mycompany.myproject artifactId=app-parent groupId=com.mycompany.myproject.service artifactId=artifactA, artifactB, artifactC groupId=com.mycompany.myproject.transform artifactId=artifact1, artifact2, artifact3 This too builds fine, however in reality somewhere in this new build is a reference to com.mycompany.myproject:artifactA:1.0-SNAPSHOT...perhaps for an unpack goal. The build is fine as Nexus will always have this artifact although it was removed from the build during the refactor. We want to purge all com.mycompany.myproject.* snapshots from Nexus so the CI build will fail until the build is correct. -Dave On Tue, Jul 21, 2015 at 3:20 PM, Ron Wheeler rwhee...@artifact-software.com wrote: Using the parent pom to specify the versions of dependencies solves this problem for most people. If there are no SNAPSHOTS in the parent's properties and the parent poms version is not a SNAPSHOT, then your project is not being built with SNAPSHOTS. We never worry about the SNAPSHOTs in the repo. Ron On 21/07/2015 2:42 PM, David Hoffer wrote: Yeah it appears our IT group is right...Nexus doesn't have a UI/feature to do what we want. What other options are there? This would seem a common need, major project does a refactor of Maven GA and want to delete all SNAPSHOTS used by the project to verify the refactor is 100% complete. We have had too many cases where the build is still pointing to an old artifact that isn't part of the build anymore yet the build is happy because old artifacts are still in Nexus. -Dave On Tue, Jul 21, 2015 at 12:36 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi David, On 7/21/15 6:03 PM, David Hoffer wrote: We use Nexus as our corporate Maven repository and would like to periodically delete certain SNAPSHOT artifacts. We need to be able to filter/select by groupId and by version...so delete all where groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT. You can only delete all kind of SNAPSHOT's in Nexus based on a time frame for example delete all SNAPSHOT's which are older than 30 days etc.. Our use case is that when we refactor part of the build to use new groupIds the old ones are not valid anymore however sometimes there is a lingering reference to the old groupId, if we can delete all the old SNAPSHOTS we could find those errors now instead of when we release. Any ideas on how to do this are much appreciated. -Dave Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to delete certain snapshots from Nexus
Using the parent pom to specify the versions of dependencies solves this problem for most people. If there are no SNAPSHOTS in the parent's properties and the parent poms version is not a SNAPSHOT, then your project is not being built with SNAPSHOTS. We never worry about the SNAPSHOTs in the repo. Ron On 21/07/2015 2:42 PM, David Hoffer wrote: Yeah it appears our IT group is right...Nexus doesn't have a UI/feature to do what we want. What other options are there? This would seem a common need, major project does a refactor of Maven GA and want to delete all SNAPSHOTS used by the project to verify the refactor is 100% complete. We have had too many cases where the build is still pointing to an old artifact that isn't part of the build anymore yet the build is happy because old artifacts are still in Nexus. -Dave On Tue, Jul 21, 2015 at 12:36 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi David, On 7/21/15 6:03 PM, David Hoffer wrote: We use Nexus as our corporate Maven repository and would like to periodically delete certain SNAPSHOT artifacts. We need to be able to filter/select by groupId and by version...so delete all where groupId=com.mycomp.mygroupid.* and version=X.SNAPSHOT. You can only delete all kind of SNAPSHOT's in Nexus based on a time frame for example delete all SNAPSHOT's which are older than 30 days etc.. Our use case is that when we refactor part of the build to use new groupIds the old ones are not valid anymore however sometimes there is a lingering reference to the old groupId, if we can delete all the old SNAPSHOTS we could find those errors now instead of when we release. Any ideas on how to do this are much appreciated. -Dave Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
