[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5929) Clean up, simplify, and centralize JBT/JBDS dependencies

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-5929:
-----------------------------------

With Denis' work in JBDS-1351, we only need to publish a JBDS Target Platform as a repo zip, and rely on that instead of umpteen Eclipse.org zips.

https://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.releng/builders/jbds-all-package/jbds.target

> Clean up, simplify, and centralize JBT/JBDS dependencies
> --------------------------------------------------------
>
>                 Key: JBIDE-5929
>                 URL: https://jira.jboss.org/browse/JBIDE-5929
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: Build/Releng
>    Affects Versions: 3.2.x
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 3.3.x
>
>
> 1. create document cataloguing all the deps against which we currently build - both @ Eclipse, @ JBoss, and elsewhere
> 2. copy deps hosted on sourceforge & porkchop to repository.jboss
> 3. clean out old deps which are no longer used (caution: we may still need a JBT 3.0.4 or JBDS 2.1.2 build)
> 4. where possible, replace multiple SDKs with a single repo zip
> ...
> Note that  repository.jboss.org is essentially read-only now, and the sync between svn and the repository.jboss.org filesystem is disabled. So... is it time to move everything to download.jboss.org?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira