Hi Gregory,
we had this problem no more than a week ago.
See http://www.nabble.com/Re-use-existing-MANIFEST.MF-td21909779.html#a21909779
There is a jira issue on this topic. you can track the progress of
this issue on: http://jira.codehaus.org/browse/GRADLE-395
regards,
René Gröschke
Am 19.02.2009 um 17:32 schrieb Gregory Boissinot:
The Gradle OSGi plugin enables the generation of an OSGi manifest.
But I am building Eclipse RCP applications. In my case, the
developers are
creating and are maintaining the MANIFESF.MF file, because it's
assisted in
Eclipse with a lot of Eclipse wizards. Also the MANIFEST.MF file is
required
when developing applications.
So, in this situation, at build time, I don’t create a new
MANIFEST.MF file
at but I am re-using the existing one.
In this situation, I only use "usePlugin('java')" and not
"usePlugin('osgi')". And I tell to use the actual MANIFEST.MF file.
Is it the right way?
Thanks
--
View this message in context:
http://www.nabble.com/The-Gradle-OSGi-plugin-for-Eclipse-RCP-applications-tp22104286p22104286.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
