Andrey Hihlovskiy

I will think in the direction of general solution for OSGi-aware hot reloading.

@mcmil , did you succeed starting e(fx)clipse under Wuff? And, yes, what you say is cool news!

Good point. I'll think on improving in this area. Maybe we'll do manifest merge only after specific instruction.

@tschulte, @nedtwigg, @aalmiray: I created tiny draft on the improvement in this area (MANIFEST.MF and plugin.xml handling in Wuff): https://github.com/akhikhl/wuff-drafts/blob/master/Wuff-bundle-files-draft.md The coding effort related to this improvement will be probably...

@tschulte, @nedtwigg, @aalmiray: Just one more addition to the draft, regarding build lifecycle. Please criticize: https://github.com/akhikhl/wuff-drafts/blob/master/Wuff-bundle-files-draft.md#build-cycle Correct build cycle might be critical from the perspective of how Wuff is used...

I just realized the idea of processBundleFiles task is probably defect. Imagine, src/main/bundle/META-INF/MANIFEST.MF contains imports from other bundles. It will be natural to expect that these "other bundles" are also...

Ned, you are right, performance should be of top priority to us.

Overwrite or not overwrite, that is the question :smile: We will follow "least surprise" principle. By default the feature will be turned off. No generation/merge, no overwrite. When somebody enables...

I just reread what @radimk [suggested](https://github.com/akhikhl/wuff/issues/25#issuecomment-55587136) regarding BUNDLE_ROOT_PATH and generated files in buildDir. I think it will work that way. Need to try.

On 09/11/2014 03:18 PM, Alexander Eliseyev wrote: > |java.lang.IncompatibleClassChangeError: the number of constructors > during runtime and compile time for > org.akhikhl.unpuzzle.osgi2maven.Deployer do not match. Expected -1 but > got...