adding manifest.mf

[maxandersen]

today i tried running jbosside from inside eclipse 3.1, but got a few issues with it.

Firstly the aop plugin were pointing to a 3.0 eclipse runtime.jar - is that intentional ? It cannot run from eclipse 3.1 without me changing it.

javax.servlet.Exception seem to be impossible to find for some plugins - how did you make it compile without this ?

Anyhow I saw that we still don't have MANIFEST.MF which is something that we should do as it gives better control over plugin and classloading (it also can give some more work, but at least it is now easier to solve ;)

I have changed them all, but wanted to know if anyone know of issues with respect to doing this ? (E.g. will the auto build still work?)

[maxandersen]

forgot to mention that one of the reasons for me to upgrade to MANIFEST.MF was that i found that some plugins did not load their classes probably (eclipse complained about bad hiearchy yada yada) - and making them use MANIFEST.MF solved that (apparently)

[mculpepper]

The build is able to build plugins that use both the MANIFEST or the plugin.xml.. you've changed all the JBossIDE plugins to use MANIFEST?

[maxandersen]

on my local box - and now i can actually run this stuff ;)

wanted to make sure the build stuff would work with manifest.mf driven builds....

Any objections against me committing it ?

[mculpepper]

have a ball =)

[maxandersen]

would do if ryan would let me commit ;)

when is 6 PM EST anyway ?

[maxandersen]

done - let me know if it works in your end ;)