[ https://jira.jboss.org/browse/JBIDE-6834?page=com.atlassian.jira.plugin.s... ] Denis Golovin updated JBIDE-6834: --------------------------------- Priority: Blocker (was: Major) -- 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

[ https://jira.jboss.org/browse/JBIDE-6834?page=com.atlassian.jira.plugin.s... ] Nick Boldt commented on JBIDE-6834: ----------------------------------- Could this instead be added to the end of publish.sh so that a) all the existing jobs need not be modified, and b) cleanup only happens after a successful build, rather than before every build ? -- 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

[ https://jira.jboss.org/browse/JBIDE-6834?page=com.atlassian.jira.plugin.s... ] Denis Golovin edited comment on JBIDE-6834 at 8/20/10 12:12 PM: ---------------------------------------------------------------- I don't see the reason to have publish.sh at all. All work should be done by maven, or at least ant called from maven. It would let to have platform independent build that could be executed on both platforms windows and linux. Publishing would be matter of one rsync command. a) open issue for hudson to provide an option not just use local repository for project but also option to clean it up before/after build b) if that happens only after successful build in some cases we will never get to successful build as in case with xulrunner-1.9.2 was (Author: dgolovin): I don't see the reason to have publish.sh at all. All work should be done by maven, or at least ant called from maven. It would let to have platform independent build that could be executed on both platforms windows and linux. Publishing would be matter of one rsynccommand. a) open issue for hudson to provide ane option not just use local repository for project but also option to clean it up before/after build b) if that happens only after successful build in some cases we will never get to sucessfull build as in case with xulrunner-1.9.2 -- 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

[ https://jira.jboss.org/browse/JBIDE-6834?page=com.atlassian.jira.plugin.s... ] Denis Golovin commented on JBIDE-6834: -------------------------------------- nope, I'm not suggesting use unix rm -rf from maven. I'm suggesting that during development if local repo keep all snapshots from previous build it is a potential source of errors. We bumped in it at least twice. So it might be a good option for hudson to have a way to control it. Yo can control it the way you like with shell script. -- 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

[ https://jira.jboss.org/browse/JBIDE-6834?page=com.atlassian.jira.plugin.s... ] Denis Golovin resolved JBIDE-6834. ---------------------------------- Resolution: Done XL 1.9.1.2. is is included in last build -- 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

[ https://jira.jboss.org/browse/JBIDE-6834?page=com.atlassian.jira.plugin.s... ] Denis Golovin updated JBIDE-6834: --------------------------------- Attachment: jbt-m2-nstall.png -- 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

[ https://jira.jboss.org/browse/JBIDE-6834?page=com.atlassian.jira.plugin.s... ] Nick Boldt commented on JBIDE-6834: ----------------------------------- (also did same change for pom.xml, of course.) -- 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

[ https://jira.jboss.org/browse/JBIDE-6834?page=com.atlassian.jira.plugin.s... ] Vlado Pakan closed JBIDE-6834. ------------------------------ Verified using update site http://download.jboss.org/jbosstools/updates/nightly/jbosstools-3.2.0.M2/ -- 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