[
https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi...
]
Mickael Istria edited comment on JBIDE-18772 at 6/4/15 4:51 AM:
----------------------------------------------------------------
jbosstools-integration-tests job seems to have been successfully updated.
Remaining:
* devstudio.product : requires more specific steps, so pom has to be changed
* jbosstools-browsersim-standalone : doesn't match the generic deployment procedure,
so its pom requires some customization => PR
https://github.com/jbosstools/jbosstools-browsersim/pull/65 /[~kmarmaliykov] can you
please have a look at it?
* jbosstools-discovery : requires more specific steps, as generic process isn't
covering this case
* jbosstools-integration-stack-tests.aggregate : Needs adoption of a more recent parent
pom +needs additional configuration to publish also to snapshot location. see
jbosstools-integration-tests/site/pom.xml as reference
* RedDeer_master : Does NOT use JBoss Tools parent, so configuration of the
deploy-to-jboss profile from JBT parent pom has to be duplicated to Red Deer before
updating the job
was (Author: mickael_istria):
jbosstools-integration-tests job seems to have been successfully updated.
Remaining:
* devstudio.product : requires more specific steps, so pom has to be changed
* jbosstools-browsersim-standalone : doesn't match the generic deployment procedure,
so its pom requires some customization
* jbosstools-discovery : requires more specific steps, as generic process isn't
covering this case
* jbosstools-integration-stack-tests.aggregate : Needs adoption of a more recent parent
pom +needs additional configuration to publish also to snapshot location. see
jbosstools-integration-tests/site/pom.xml as reference
* RedDeer_master : Does NOT use JBoss Tools parent, so configuration of the
deploy-to-jboss profile from JBT parent pom has to be duplicated to Red Deer before
updating the job
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.Beta2
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)