If i read it correctly it seems that we just need to rebuild and install. Then if there is something wrong, move an Eclipse.inf file into manifest directory of the Rogue plugin.
David mentions that this happens to older byte code. Are we still building against older jvm's a lot?
Sent from Blue Mail
On Apr 13, 2015, at 18:35, Scott Lewis < slewis@xxxxxxxxxxxxx> wrote:
Markus and Wim: There have recently been some changes announced by
David Williams on the cross-projects-mailing list about the EF signing
procedure's use of pack200:
https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11739.html
Given our previous issues WRT the use of pack200 (i.e. the embedded
smack jar), I would like to verify that this change is not going to
cause a problem for our Mars release, but I don't know enough about what
we are currently doing WRT signing. Could one or both of you please
read the announcement from David above and advise or discuss?
Thanksinadvance,
Scott
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To
change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
|
