Exactly what I was thinking. Thanks for the clarification.
Nikunj Mehta
BJ Hargrave wrote:
The OSGi spec says nothing about the Main-Class manifest header. It
must be ignored by an OSGi framework. Only the Bundle-Activator header
should be used to activate a bundle. This allows a jar to be a bundle
and a jar. See the BND bundle from Peter Kriens. This one jar is a
java application, a bundle (eclipse plugin), an ant task and a maven
plugin.
So this sounds like a bug/feature of knopflerfish.
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
[EMAIL PROTECTED]
Office: +1 386 848 1781 Mobile: +1 386 848 3788
----- Original Message -----
From: Nikunj Mehta [EMAIL PROTECTED]
Sent: 03/07/2007 05:29 PM
To: [email protected]
Subject: [osgi-dev] Main-Class mainfest header
Is there a defined standard interpretation of Main-Class in the OSGi
world? I am having a lot of trouble taking regular jars and converting
them in to bundles because they have a Main-Class directive, and my
OSGi runtime (Knopflerfish) tries to look for an activate method in
the declared Main-Class.
Thank you
Nikunj Mehta
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
