When I try to export an Eclipse RT bundle project, I get the message: "/src/META-INF/MANIFEST.MF was replaced by the generated MANIFEST.MF and is no longer in the JAR.".
This used to work a few weeks ago and I don't understand what's changed. I've updated all the tools to their latest versions and the problem persists.
If I create a new EclipseRT bundle project, it exports fine. What's even stranger is if I copy & paste an existing project, it also exports fine. I've got to the point where I have two simple and seemingly-identical Eclipse projects and, after importing them into my workspace, one exports and one doesn't (giving the error above). I've run diff on the two projects and the only difference is the project name (obviously).
We've started in on straightening this stuff out, so hopefully we'll have a good solution soon. Right now, we're mixing two different runtime and build models (PDE and Spring/Bundlor). Basically, we need to rationalize and hopefully simplify what is getting generated and what isn't and give users more control and transparency into that.
Thanks for taking the time to reply. Out of curiosity, what is it that distinguishes the two projects I attached, causing the tooling to export one but not the other? They have the same .project, .classpath, .settings files, and the same /src dir.
I think we got this one. Please check out the nightlies when they're ready and reopen the bug if not.
Note that although we've fixed this bug, the manifest error is still going to appear for people when there is something else wrong with their project packaging, for example a bad library. We'll want to look at better error reporting for these kinds of issues. Please raise a bug if that's important to you.