See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4356783 and http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/java.html
The -jar options states this ... "When you use this option, the JAR file is the source of all user classes, and other user class path settings are ignored. ". You will need to use some form of the following command to add your extension to the classpath of the framework: java -cp equinox.jar;extension.jar org.eclipse.core.runtime.adaptor.EclipseStarter Tom |------------> | From: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"Kirchev, Lazar" <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Equinox development mailing list <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |10/13/2009 12:52 AM | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |RE: [equinox-dev] Problem with defining a custom adaptor hook in a framework extension | >--------------------------------------------------------------------------------------------------------------------------------------------------| I did not explained it clearly. I launch the framework with java -jar <equinox.jar> - I haven't tryed with the launcher. And it fails in all caises - both with and without adding the extension fragment to the classpath with the -cp java command option. In both cases the extension gets resolved (at least such is the status returned by the ss command), but the framework classloader is not set up with the extension, therefore the hookconfigurators.properties file of the extension is not read. Lazar From: [email protected] [ mailto:[email protected]] On Behalf Of Thomas Watson Sent: Monday, October 12, 2009 7:08 PM To: Equinox development mailing list Subject: Re: [equinox-dev] Problem with defining a custom adaptor hook in a framework extension Can you clarify the different ways you launch equinox and what cases fail and what cases succeed? You mention that it fails but that it also succeeds if you add the fragment to the class path while launching with java -jar <equinox.jar>. The equinox launcher (org.eclipse.equinox.launcher jar) is what reads the osgi.framework.extensions property then it sets up the framework class loader with the proper content (the framework + extensions etc.) But if you are not using the equinox launcher (i.e. java -jar <equinox.jar>) then you must add the extension fragments to the class path yourself. Tom Inactive hide details for "Kirchev, Lazar" ---10/12/2009 10:29:09 AM---Hello,"Kirchev, Lazar" ---10/12/2009 10:29:09 AM---Hello, From: "Kirchev, Lazar" <[email protected]> To: "[email protected]" <[email protected]> Date: 10/12/2009 10:29 AM Subject: [equinox-dev] Problem with defining a custom adaptor hook in a framework extension Hello, I am trying to define a custom adaptor hook in a framework extension, but it seems as if the hookconfigurators.properties file in the extending fragment bundle jar is not read. When debugging the HooksRegistry code I found that the hookconfigurators.properties file in the bundle is not returned as a resource by the framework classloader. I have set the osgi.framework.extensions property in the config.ini file, and when starting equinox (I start it with java -jar <equinox.jar>), I add the extension bundle to the classpath. The extension fragment is correctly recognized as such, and gets successfully resolved. The framework and extension bundles are in one and the same folder. I am using 3.5 release. Any idea what the problem may be? Best regards, Lazar Kirchev_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
