[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-1349) Teiid Designer bits are from M2 version. Need to updated to latest bits

[ https://jira.jboss.org/browse/JBDS-1349?page=com.atlassian.jira.plugin.sy... ] Nick Boldt commented on JBDS-1349: ---------------------------------- This is due to the fact that I'm pulling a snapshot manually for the sake of stability, rather than pulling the "latest" as I do for JBT. (See also JBDS-1336.) JBT pulls from an update site URL [1]: http://download.jboss.org/jbosstools/builds/staging/jbosstools-teiid-desi... (see http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/pom.xml) JBDS pulls from a zip, because it can't (currently) fetch from a site URL [2]: teiid.uri=http://download.jboss.org/jbosstools/updates/JBossTools-TeiidDe... teiid.archive=jbosstools-teiid-designer-Update-7.1.zip (see http://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.r...) Now, there are 4 ways to improve this situation: a) when you're ready to push what's in [1] to the canned location in [2], you email/irc ping/JIRA me to say it's ready/stable. b) I create a Hudson job to publish from [1] to [2] which you can use as you see fit, pushing when you want to w/o having to ask me. c) Your existing build job could just publish a snapshot zip into the updates/staging/ dir directly, for every build. d) I change the aggregateRepos scripts to be able to pull from a URL instead of a zip, so that your latest is always in JBDS as it it in JBT --- Ultimately the question is one of code stability and of your alignment w/ JBT's schedule. If you want to continue to follow your own path, then (a) or (b) work for me; if you want to more closely align w/ JBT and therefore have the same degree of milestone code freezes, then I'm down w/ (c) or (d). What's the best approach for your project? -- 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