[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-5929) Clean up, simplify, and centralize JBT/JBDS dependencies
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Wed Apr 28 13:40:10 EDT 2010
[ https://jira.jboss.org/jira/browse/JBIDE-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt updated JBIDE-5929:
------------------------------
Summary: Clean up, simplify, and centralize JBT/JBDS dependencies (was: Clean up, simplify, and centralize JBT/JBDS dependencies onto repository.jboss.org)
Description:
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?
was:
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
...
> Clean up, simplify, and centralize JBT/JBDS dependencies
> --------------------------------------------------------
>
> Key: JBIDE-5929
> URL: https://jira.jboss.org/jira/browse/JBIDE-5929
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: Build/Releng
> Affects Versions: 3.2.next
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 3.2.next
>
>
> 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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list