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
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
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
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
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
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
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]
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
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
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
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
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
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
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
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
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'
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
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
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
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
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
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
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
23 matches
Mail list logo
