Nick Boldt created JBDS-2289: -------------------------------- Summary: remove deprecated leftovers from devstudio SVN trunk Key: JBDS-2289 URL: https://issues.jboss.org/browse/JBDS-2289 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Affects Versions: 6.0.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 6.0.0.Alpha2 Remaining files in devstudio/trunk/releng/org.jboss.ide.eclipse.releng are: {code} $ find . -type f ./builders/reports/build.xml ./builders/reports/sun_checks.xml ./builders/reports/build.properties ./builders/reports/style-checks.xml ./builders/reports/pmd-checks.xml ./hudson/jbds-echoproperties.txt ./hudson/devstudio-nightly.local.sh ./hudson/jbosstools-nightly.echoproperties.txt ./hudson/local.sh ./hudson/jbosstools-nightly.sh ./hudson/devstudio-nightly.echoproperties.txt ./hudson/devstudio-nightly.sh ./hudson/cleanup/devstudio-cleanup.sh ./hudson/cleanup/jbosstools-cleanup.sh ./hudson/cleanup/devstudio-product-cleanup.sh ./hudson/cleanup/README.deprecated.txt ./hudson/configs/devstudio-admin.config.xml ./hudson/configs/devstudio-minsk-upload-nightly.config.xml ./hudson/configs/jbosstools-docs-nightly.config.xml ./hudson/configs/jbosstools-cleanup.config.xml ./hudson/configs/devstudio-cleanup.config.xml ./hudson/configs/jbosstools-devstudio-grid.config.xml ./hudson/cleanBuildFolder.sh ./hudson/i18n_logscan_remote.sh ./hudson/i18n_warnings_by_module.pl ./hudson/mp3/12ga_shotgun.mp3 ./hudson/mp3/tpir-sdding.mp3 ./hudson/mp3/tpir-notag.mp3 ./hudson/mp3/README.txt ./art/README.content.moved.txt ./util/copyBuildResults.xml ./util/make_tags.sh ./util/buildSource.xml ./util/fetchDeps.sh ./util/echo_property.sh ./util/copy.properties ./util/renameUpdateSite.sh ./util/getRequirement.xml ./util/diskUsageReport.sh ./util/fetchXulrunner.sh {code} Pretty sure this is all safe to delete, so I'm going to delete it and see if anyone notices. :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira