[jbosstools-issues] [JBoss JIRA] (JBIDE-13835) Improve publish script (split? Move to maven?)

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-13835:
----------------------------------------

{quote}4. Publish bits; REQUIRED
* generate MD5 sums
* push update site into /builds/staging/JOB_NAME/all/repo/
* push update zip into /builds/staging/JOB_NAME/all/ [unless JBDS]
* push source zip into /builds/staging/JOB_NAME/all/ [create if not already present?]
{quote}

I support the underlying opinion of [~dgolovin], which I read as "let's get rid of those zips" (at that time). AFAIK, they are very rarely used, we can generate the zip from the repository on-demand, and the repository contains the Git commit reference, so we can generate the source zip on demand.
If we get rid of them, then we're basically just doing an rsync (when git commit is different). We can more easily automate that in a pom.xml, using the rsync-maven-wagon.


> Improve publish script (split? Move to maven?)
> ----------------------------------------------
>
>                 Key: JBIDE-13835
>                 URL: https://issues.jboss.org/browse/JBIDE-13835
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>            Reporter: Mickael Istria
>             Fix For: 4.3.x
>
>
> Publish script deals with a lot of different and not-always-related things. It makes it difficult to maintain it. We should think about some improvements such as
> * different conventions from different stream
> * components vs aggregate
> * devstudio vs jbosstools.
> Or,
> * Make publishing part of a "mvn deploy" step.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)