[jbosstools-issues] [JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072990#comment-13072990 ] 

Mickael Istria edited comment on JBIDE-18772 at 6/2/15 4:47 AM:
----------------------------------------------------------------

Needs changes:
* 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 additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c5565ec1a20dc26d6dd194b9f37b55 as example. cc [~mmalina]
* jbosstools-integration-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c5565ec1a20dc26d6dd194b9f37b55 as example. cc [~mmalina]
* 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. cc [~mmalina]

Nothing to change:
* jbosstools-locus.site : Latest version only seems to be published and consumed only through Nexus (in all .target definition I've checked), so it's just a regular "mvn deploy", without any other publish step necessary (more like JBIDE-16128 ). Nothing to change on the job.


was (Author: mickael_istria):
* 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 additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c5565ec1a20dc26d6dd194b9f37b55 as example. cc [~mmalina]
* jbosstools-integration-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c5565ec1a20dc26d6dd194b9f37b55 as example. cc [~mmalina]
* jbosstools-locus.site : Latest version only seems to be published and consumed only through Nexus (in all .target definition I've checked), so it's just a regular "mvn deploy", without any other publish step necessary (more like JBIDE-16128 ). Nothing to change on the job.
* 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. cc [~mmalina]

> 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)