[jbosstools-issues] [JBoss JIRA] (JBIDE-13336) create target platform using Kepler dependencies

Nick Boldt (JIRA) jira-events at lists.jboss.org
Fri Jan 11 12:23:08 EST 2013


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

Nick Boldt commented on JBIDE-13336:
------------------------------------

Note that I've renamed s/6.0/7.0/g and disabled .maximum in favour of running the .minimum because then the TP jobs will properly cascade into each other. 

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-7.0_trunk.target-platforms.maximum/ (disabled)
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-7.0_trunk.target-platforms.minimum/ (enabled)

Also switch the zip filename from 610 to 700 in the publish.sh script.
                
> create target platform using Kepler dependencies
> ------------------------------------------------
>
>                 Key: JBIDE-13336
>                 URL: https://issues.jboss.org/browse/JBIDE-13336
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: target-platform
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>             Fix For: 4.1.0.Alpha1
>
>         Attachments: multiple.target, multiple.target_update_hints.txt
>
>
> Along with the refactoring we talked about doing in JBIDE-13232, it's time to create a new Kepler M4 target platform.
> I've pulled mirrors for the three largest pieces: Kepler M4, Eclipse 4.3M4, WTP 3.5M4:
> http://download.jboss.org/jbosstools/updates/requirements/kepler/20121221-1430-M/
> http://download.jboss.org/jbosstools/updates/requirements/eclipse/S-4.3M4-201212140730/
> http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5.0M4-20121217201101/
> Do you need anything else mirrored? If so bounce this to me and I'll get the bits copied to download.jboss.org for you.

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


More information about the jbosstools-issues mailing list