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

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-18772:
---------------------------------------

RedDeer is finally done.
There are several caveats there.
1. The target url is now both in the job config and the pom, so it's harder to update them and keep in sync (this is true for all jobs, not just RedDeer)
2. We don't use JBoss Tools parent pom, which brings some complications.
2.1 mvn deploy will not work unless we set up the target repository in our pom. For now I disabled deployment in the job using "-Dmaven.deploy.skip=true"
2.2 Using project.version in the pom to specify the version of the publish artifact will not work for us, since for RedDeer it's currently 0.8.0, so we need to hardcode a version (or pass it in the jenkins job) - so that's another thing to keep in sync manually. (We're trying to keep RedDeer independent of JBoss Tools releases, but this is one example that shows that it's not always 100 % - we still need to use *a* version of the publish script.)
3. People in our team wanted to remove mars or luna from the update site url, so now it's this:
http://download.jboss.org/jbosstools/snapshots/builds/RedDeer_master/

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