Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363727 - Add a simple hot-deploy mechanism to Nano
Summary: Add a simple hot-deploy mechanism to Nano
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: 3.5.0.M02   Edit
Assignee: Borislav Kapukaranov CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 364571
  Show dependency tree
 
Reported: 2011-11-14 12:33 EST by Borislav Kapukaranov CLA
Modified: 2012-01-17 03:34 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Borislav Kapukaranov CLA 2011-11-14 12:33:26 EST 
Nano should have its own p2-integrated hot-deploy mechanism to ease the developers that build on top of it. This should be a really simple hot-deployer, aiming at deploying only jars and wars.
Comment 1 Borislav Kapukaranov CLA 2012-01-17 03:32:54 EST 
Fixed with commits:
nano - 6f0ff6b
kernel - 2c33716

These reuse the hot-deployer from the kernel's repository and factors it as a separate entity/bundle. Also tests and deployer APIs are migrated to the nano repository.
Comment 2 Borislav Kapukaranov CLA 2012-01-17 03:34:13 EST 
Note this deployer is performing pure Equinox install, not p2. 
Warm start of the hot-deployed artifacts will be covered in a separate bug and makes sense to be achieved with the help of a p2 install.