Community
Participate
Working Groups
The jarprocessor.jar used by the foundation for signing is slowly diverging from the version in update.core because of patches hanging around on bugs. This bug will serve as a staging point for fixes we should get released and then deliver to the foundation.
Note that bug 178882 and bug 178884 are complex enough that they won't be in for M6. We should try to do this early in M7
In addition, it would be good to give this version to Bjorn to use when processing the Europa update site.
I think the best way of making sure everyone stays in sync is to have the build process automatically generate a standalone jarprocessor.jar from the class files in update.core. (Similar to ecj.jar from the jdt) I will look at custom callbacks to do this.
I have written a customCallback script for update.core that will produce a jarprocessor.jar during the regular build. If all is good, consumers will be able to get it from the download page.
Andrew, I'm using the latest jar processor (I20070417-0800) in my builds and it is working fine. Are there any more changes that you anticipate releasing? If not, would like to open a bug against the foundation asking them to update to the latest jar processor so we are ready for M7.
I think I'm done for now, we should go ahead and get the foundation to update.
Marking as fixed. eclipse.org has been updated, see bug 183035