Bug 10558 - Create Nexus instance (a java repository manager)
Summary: Create Nexus instance (a java repository manager)
Status: RESOLVED WORKSFORME
Alias: None
Product: CROPS
Classification: Yocto Project Subprojects
Component: eclipse-crops (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: High enhancement
Target Milestone: 2.3 M3
Assignee: Michael Halstead
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-10-28 21:35 UTC by Tim Orling
Modified: 2017-02-09 16:07 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Orling 2016-10-28 21:35:50 UTC
The new Eclipse CROPS plugin will be using Maven as the build mechanism on the AutoBuilders. We do not want to count on external Maven Central mirrors being available for our builds. A best-practice solution to mirroring artifacts (for example Java jar files and Maven pom files) is Nexus. There are several LF projects already using Nexus, we just need to add an instance for Yocto Project usage.
Comment 1 Michael Halstead 2016-11-03 07:34:29 UTC
Earlier we decided that Nexus 3.x would be
a better fit for us but there is no Pro version of 3 yet. So we can
decide between Nexus 3.x OSS edition or Nexus 2 Pro.

Pro adds staging repositories and built in zip unpack. Do we need those
features?
Comment 2 Tim Orling 2016-11-03 14:41:37 UTC
I am inclined to go with Nexus 3.x OSS.
Comment 3 Michael Halstead 2017-01-13 23:26:35 UTC
Test server up and e-mail sent.
Comment 4 Tim Orling 2017-01-13 23:42:58 UTC
Basic functionality is confirmed. A few server-side plugins will be needed. More info to follow via email.
Comment 5 Tim Orling 2017-02-09 16:07:32 UTC
The basic functionality has been proven and now we need a production instance with SSH authentication. Opening a new bug to track this.