Community
Participate
Working Groups
Unless it is important that the content of buildTools.jar (and others) NOT match the content in the source folders, we should be able to write an external tool builder file which will build the JARs correctly in the workspace when they are being developed. This would save the Releng team from having to remember to export and release the new JARs every time a change is made to a source file.
This could be done as part of bug 324682.
Created attachment 179979 [details] patch This patch will delete the buildTools.jar file and replace it with newly JAR'd results from the plugins/bin folder. It is currently set to do it during any build, including auto-build, but can be adjusted so that it only does it when you manually invoke a build, if necessary. Note: this is done during a workspace build and you still have to release the new JAR to the repo. This is separate from bug 324682 where it talks about building the bundle. If the JAR isn't needed in your workspace, then we can make changes to the classpath and build.properties file to generate the JAR file when we do a real (headless) build. In this case, we can delete the JAR from the repository as well.
patch applied, thanks!
released for N20100930-2000.