On Thu, Dec 25, 2008 at 10:20 AM, sverhagen <[email protected]> wrote: > Two questions: > - Why is MANIFEST.MF version controlled to begin with. Isn't it a generated > file?
Depends on your workflow. In OSGi the manifest controls the classes your bundle can even use, and Eclipse's PDE tooling modifies the manifest directly as it is independent of Maven. It's much easier to simply control the manifest than to try to constantly port manifest changes over into POM changes only to regenerate the manifest. Certainly the manifest that ends up in the build is somewhat different than what's controlled - 72-character wrapping, additional Maven-added stuff, etc. - but the template at least is often controlled in order to work more smoothly with other tooling. > - Don't you update MANIFEST.MF on every build? We do so, since we also > appreciate to have package details available when a developer is just > experimenting with something that is a snapshot It's no problem to have Maven touch this file or do whatever with it during the build. But often as I said, a sort of template is often controlled directly. - John --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
