Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Move snapshot repo to profile so that CI servers can use it

Description

I have a contrib tool that I have hooked up to Travis.

However the build fails because org.sakaiproject.master:master:12-SNAPSHOT pom.xml is not in a snapshot repository.

The old snapshots used to be in oss-snapshots but are really out of date:
https://oss.sonatype.org/content/repositories/snapshots/org/sakaiproject/master/

There is also no 12-SNAPSHOT.

Discussed a couple of years ago:
https://groups.google.com/a/apereo.org/forum/#!searchin/sakai-dev/snapshot/sakai-dev/v7QPCVKyu1I/D5_uZhRzqMQJ

Discussion on the logic for removing the snapshots here:
http://stackoverflow.com/questions/32403153/how-does-maven-resolve-snapshot-dependencies-when-there-are-snapshots-with-diffe

It looks like you can specify repositories in profiles, one idea to both keep external snapshots out of the main build but enable for external is to deploy them but have the sonatype-nexus-snapshots repo inside a profile so you'd have to activate the profile it (in your contrib tool) to grab the snapshot externally. Then jenkins could deploy.

Activity

Show:

Steve Swinsburg May 16, 2017 at 4:15 PM

Steve Swinsburg May 16, 2017 at 4:06 PM
Edited

To verify the repositories being used:

gives:

and

gives:

Steve Swinsburg May 16, 2017 at 4:01 PM
Edited

-Dsnapshots will activate the profile and snapshots repositories will be considered. Snapshot publishing will need to be activated in jenkins.

Duplicate

Details

Priority

Components

Assignee

Reporter

Created May 16, 2017 at 4:00 PM
Updated March 23, 2022 at 3:03 PM
Resolved May 16, 2017 at 4:15 PM