[
https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-18772 at 5/28/15 8:03 PM:
-------------------------------------------------------------
The same build produces identical content for JBT/JBDS Central and JBT/JBDS EA, and is
published to two places -- once for JBT and again for JBDS. Because JBDS content has to
live on a different server, even if it's the identical bits.
So, the deploy step performs 4 rsync.sh calls, requiring both sets of rsync_path values.
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
was (Author: nickboldt):
The same build produces identical content for JBT/JBDS Central and JBT/JBDS EA are
published to two places -- once for JBT and again for JBDS. Because JBDS content has to
live on a different server, even if it's the identical bits.
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
Include publish steps in pom files
----------------------------------
Key: JBIDE-18772
URL:
https://issues.jboss.org/browse/JBIDE-18772
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Reporter: Max Rydahl Andersen
Assignee: Mickael Istria
Priority: Critical
Fix For: 4.3.0.Beta1
Attachments: jbds-publish-to-snapshots.png
instead of relying to publish.sh being on master, we should use a versioned publish.sh
(or maybe even mojo) that the build then uses.
suggestion:
publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform
publishing.
What this helps with is:
a) can do changes to publish mechanism without affecting every past builds.
b) more movable build system
c) isolated testing possible
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)