[
https://jira.jboss.org/jira/browse/JBIDE-3918?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-3918:
-----------------------------------
I've been playing with Ivy and EasyAnt to see if there's a better way to manage
input deps for the builds than how we do it now. The Athena way is a list of URLs but
that's at the per-build level, and since we're moving from 1 build to 17, I'd
like something that's less overhead / scales better.
Also, since we're this close to M7, I may just hold off until that's declared,
unless there's a compelling reason to get on 3.5M6 immediately.
Adopt Galileo M5 requirements when building JBT 3.1 / JBDS 2.1
--------------------------------------------------------------
Key: JBIDE-3918
URL:
https://jira.jboss.org/jira/browse/JBIDE-3918
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.1.0
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.1.0
Increment
eclipse.org reqs (and any others I can find?) to use Galileo M5 values.
Let's see what breaks. :)
--
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