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

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-18772 at 6/4/15 3:28 PM:
------------------------------------------------------------

[~mickael_istria] PR 65 doesn't include renaming the output zip to conform to expected filename of jbosstools-4.3.0.Beta1-browsersim-standalone.zip.

Instead you get browsersim-3.7.0-SNAPSHOT-Beta1-v20150604-0824-BtestNumber-standalone.zip

Instead of http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-browsersim-standalone_master/2015-06-04_02-37-03-B233/ you produced http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-browsersim-standalone_master/testId-BtestNumber/

Can you add a rename step so that the artifact produced is the filename we need for publishing to sourceforge / jboss.org?




was (Author: nickboldt):
[~mickael_istria] PR 65 doesn't include renaming the output zip to conform to expected filename of jbosstools-4.3.0.Beta1-browsersim-standalone.zip	

Instead of http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-browsersim-standalone_master/2015-06-04_02-37-03-B233/ you produced http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-browsersim-standalone_master/testId-BtestNumber/

Can you add a rename step so that the artifact produced is the filename we need for publishing to sourceforge / jboss.org?



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