- This topic has 2 replies, 2 voices, and was last updated 9 years ago by Brian Fernandes.
-
AuthorPosts
-
Stu ShannonParticipantHi,
I received a message that you took away my hot reload capability, more on that later, but now I get the following error while attempting to run my web app in debug mode:Error occurred during initialization of VM
agent library failed to init: instrument
Error opening zip file or JAR manifest missing : C:\Users\sshannon\AppData\Local\MyEclipse 2015 CI\plugins\com.genuitec.eclipse.server.hotreload_13.0.2.me201508120931\lib\hotreload.jarIf you told me that my update would get rid of my hot reload I never would have done it. I want to roll back please. No where did it say that you were doing so even in the delivery log. Not a cool move guys!
MyEclipse CI Stream Delivery Log2015 CI 15
Release date: 05 Oct, 2015
MyEclipse 2015 CI 15
Show details
The CI 15 release brings several program enhancements, including externally deployed JavaScript debugging, improvements to REST Inspect, new server connectors, WebSphere enhancements and fixes, and a variety of other improvements.Included in this release:
JavaScript Debugging – Externally Deployed Debugging Support
REST Explorer Displays MIME Types
New Server Connectors
WebSphere
Stu ShannonParticipantOK, I saw the dependency in the existing debug configurations. Your “remove my functionality without telling me” ci script only removed the hot reload jar file, not update dependencies in run and debug settings. You should warn your customers of this. Maybe by telling them that you’re going to remove that functionality first would be a good idea. I do however want you to give me a path to get back to CI 14 please. You may not mislead me to reduce the functionality of my development environment.
Thank you,
Stu
Brian FernandesModeratorStu,
I’m sorry the removal of the reloading capability caused your configurations to break. Internally, we worked hard to ensure that the removal would be smooth; to prevent exactly the sort of problem you’re describing. Ideally, you would be informed about the change, as you indicate you were:
…and everything would still continue to function, minus the reloading capabilities, and no additional warning should have been necessary. Evidently, we missed an area, or there was a bug in the removal code, leaving your configuration broken – our team is looking into this.
Unfortunately timing of this release was out of our control and we cannot provide a path back to the earlier CI release with this capability.
Again, I apologize for the inconvenience and feature removal, but I’m afraid our reload tech. cannot continue to remain available. It pains us to know that a feature just out for a few weeks became so valuable to you, and yet we could not keep it in.
If you have further questions, please email sales@genuitec.com.
-
AuthorPosts