[jbosstools-issues] [JBoss JIRA] (JBIDE-15928) Tweak publish.sh to allow copying of javadoc along with the p2 repo

[Martin Malina (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-15928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina resolved JBIDE-15928.
-----------------------------------

    Fix Version/s: 4.2.0.Alpha2
                       (was: 4.2.x)
       Resolution: Won't Fix


I'm resolving this as Won't fix. I decided that it would be too cumbersome to use publish.sh for this.
I used openshift to host the javadoc - it's not something critical, so I think openshift is fine here.
If you're interested in more details, see here: https://github.com/jboss-reddeer/reddeer/pull/46

                
> Tweak publish.sh to allow copying of javadoc along with the p2 repo
> -------------------------------------------------------------------
>
>                 Key: JBIDE-15928
>                 URL: https://issues.jboss.org/browse/JBIDE-15928
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>    Affects Versions: 4.1.1.Beta1
>            Reporter: Martin Malina
>            Assignee: Martin Malina
>             Fix For: 4.2.0.Alpha2
>
>
> We would like to be able to publish javadoc regularly along with the p2 repo.
> E.g. we have this:
> http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/all/repo/
> Generated by:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/RedDeer_master/
> Using publish.sh:
> http://raw.github.com/jbosstools/jbosstools-build-ci/master/publish/publish.sh
> We would like to get something like this:
> http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/all/javadoc/
> To generate javadoc of RedDeer, you need to run:
> mvn install
> mvn javadoc:javadoc
> See this PR that adds javadoc support for RedDeer:
> https://github.com/jboss-reddeer/reddeer/pull/46

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira