[
https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-18772:
------------------------------------
[~mickael_istria] I see you've updated these jobs. Please update the _4.3.mars ones,
too.
{code}
DevStudio_Master/job/jbosstools-aerogear_master/config.xml
DevStudio_Master/job/jbosstools-arquillian_master/config.xml
DevStudio_Master/job/jbosstools-base_master/config.xml
DevStudio_Master/job/jbosstools-birt_master/config.xml
DevStudio_Master/job/jbosstools-browsersim_master/config.xml
DevStudio_Master/job/jbosstools-central_master/config.xml
DevStudio_Master/job/jbosstools-forge_master/config.xml
DevStudio_Master/job/jbosstools-freemarker_master/config.xml
DevStudio_Master/job/jbosstools-hibernate_master/config.xml
DevStudio_Master/job/jbosstools-javaee_master/config.xml
DevStudio_Master/job/jbosstools-jst_master/config.xml
DevStudio_Master/job/jbosstools-livereload_master/config.xml
DevStudio_Master/job/jbosstools-openshift_master/config.xml
DevStudio_Master/job/jbosstools-playground_master/config.xml
DevStudio_Master/job/jbosstools-portlet_master/config.xml
DevStudio_Master/job/jbosstools-server_master/config.xml
DevStudio_Master/job/jbosstools-TEMPLATE_master/config.xml
DevStudio_Master/job/jbosstools-TEMPLATE.NESTED_master/config.xml
DevStudio_Master/job/jbosstools-vpe_master/config.xml
DevStudio_Master/job/jbosstools-webservices_master/config.xml {code}
Also, I see you've removed some configuration... was that intentional?
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
Include publish.sh in parent pom as versioned maven dependency
--------------------------------------------------------------
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
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)