Optional In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus.
Then we'll see what are the pros/cons of this approach.
Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it.
- is blocked by
-
JBIDE-16309 Move inter-JBT dependencies to component poms
-
- Closed
-
- is related to
-
JBIDE-14610 Design http://download.jboss.org/jbosstools structure
-
- Closed
-
-
-
- Closed
-
-
JBIDE-21012 Why do we deploy JBT components to Nexus snapshots repo?
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
