search

akhikhl / wuff

Gradle plugin for automating assembly of OSGi/Eclipse bundles and applications
MIT License
153 stars 51 forks source link

Use existing manifest.mf #101

Open aonoiwa opened 8 years ago

aonoiwa commented 8 years ago

Hi,

i had a look into this plugin to build one of my old RCP applications. So far it works as expected, but i have one issue that i could not solve instantly. I am talking about the manifest.mf merging. My plugins have already created manifest.mf files, that should not be changed by the build. When i am building my application with wuff the build works fine, but the application would not start, because of a lot of excpetions regarding to the changed manifest.mf files. I have solved this by replacing the wuff created manifest.mf files after the build with a gradle task. Downside is that the incremental build does not work, because the build always recognizes a change.

Is there a method to tell wuff, that he should use my already existing manifest files. I had quick look into the code, but could not exactly figure out, where the manifest actually will be created. I believe that the Gradle OSGI Plugin plays a role, but the quick and dirty option to uncomment the merge method did not work.

@akhikhl Is there a possibility to tell wuff, that he should use the original manifist.mf file. No merging no creating of a new one.

I have seen that others also have problems with this, what are you doing?

nedtwigg commented 8 years ago

Might wanna take a look at Goomph and its example project. Currently on 3.0.0-SNAPSHOT, actively seeking feedback before 3.0.0 release.