|
|
| Re: "patch.jar" in MANIFEST.MF [message #66493 is a reply to message #66451] |
Fri, 14 December 2007 14:47   |
Eclipse User |
|
|
|
Originally posted by: just4lists.nospammail.net
Rüdiger,
This means that in order to avoid the following type of warnings at runtime,
we need to create a fake/empty patch.jar?
1150 [Framework Event Dispatcher] INFO [undefined] - FrameworkEvent INFO
org.osgi.framework.BundleException: The bundle class path entry "patch.jar"
could not be found for the bundle
"initial@reference:file:org.eclipse.rap.jface.jar/"
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findCla ssPathEntry(ClasspathManager.java:161)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.buildCl asspath(ClasspathManager.java:138)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.initial ize(ClasspathManager.java:72)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.ini tialize(DefaultClassLoader.java:177)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.create BCL(BundleLoader.java:714)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.create BCLPrevileged(BundleLoader.java:689)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.create ClassLoader(BundleLoader.java:318)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:340)
at
org.eclipse.osgi.framework.internal.core.SingleSourcePackage .loadClass(SingleSourcePackage.java:37)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:405)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:369)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:357)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:83)
Best regards,
Joel Oliveira
"Rüdiger Herrmann" <rherrmann@innoopract.com> escreveu na mensagem
news:fjtsnb$b0c$1@build.eclipse.org...
> Tiago,
>
> since version 1.0.1
> (http://www.eclipse.org/rap/noteworthy/relnotes101.php) RAP allows to
> patch plug-ins by providing a so called patch-fragments.
> See this wiki page for more information:
> http://wiki.eclipse.org/RAP/Patch_Fragments
>
> HTH,
> Rüdiger
>
> Tiago wrote:
>> Hi,
>>
>> I have found references of a "patch.jar" in the classpath entry of the
>> MANIFEST.MF in some RAP bundles, namely "org.eclipse.rap.ui.workbench" or
>> "org.eclipse.rap.rwt".
>>
>> Just out of curiosity what is this "patch.jar"?
>>
>> Tiago
|
|
|
|
| Re: "patch.jar" in MANIFEST.MF [message #66759 is a reply to message #66741] |
Sun, 16 December 2007 23:36 |
 Benjamin Muskalla
Messages: 237
Registered: July 2009 |
Senior Member |
|
|
And no, there should be no need to have an empty/fake patch fragment.
Benjamin Muskalla wrote:
> Hi Joel,
>
> is there a way how to reproduce this error? Even with -errorlog enabled
> I don't see such a problem.
>
> Greets
> Benny
>
> Joel Oliveira wrote:
>> Rüdiger,
>>
>> This means that in order to avoid the following type of warnings at
>> runtime, we need to create a fake/empty patch.jar?
>>
>> 1150 [Framework Event Dispatcher] INFO [undefined] - FrameworkEvent
>> INFO
>> org.osgi.framework.BundleException: The bundle class path entry
>> "patch.jar" could not be found for the bundle
>> "initial@reference:file:org.eclipse.rap.jface.jar/"
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findCla ssPathEntry(ClasspathManager.java:161)
>>
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.buildCl asspath(ClasspathManager.java:138)
>>
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.initial ize(ClasspathManager.java:72)
>>
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.ini tialize(DefaultClassLoader.java:177)
>>
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.create BCL(BundleLoader.java:714)
>>
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.create BCLPrevileged(BundleLoader.java:689)
>>
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.create ClassLoader(BundleLoader.java:318)
>>
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:340)
>>
>> at
>> org.eclipse.osgi.framework.internal.core.SingleSourcePackage .loadClass(SingleSourcePackage.java:37)
>>
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:405)
>>
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:369)
>>
>> at
>> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:357)
>>
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:83)
>>
>>
>> Best regards,
>>
>> Joel Oliveira
>>
>> "Rüdiger Herrmann" <rherrmann@innoopract.com> escreveu na mensagem
>> news:fjtsnb$b0c$1@build.eclipse.org...
>>> Tiago,
>>>
>>> since version 1.0.1
>>> (http://www.eclipse.org/rap/noteworthy/relnotes101.php) RAP allows to
>>> patch plug-ins by providing a so called patch-fragments.
>>> See this wiki page for more information:
>>> http://wiki.eclipse.org/RAP/Patch_Fragments
>>>
>>> HTH,
>>> Rüdiger
>>>
>>> Tiago wrote:
>>>> Hi,
>>>>
>>>> I have found references of a "patch.jar" in the classpath entry of
>>>> the MANIFEST.MF in some RAP bundles, namely
>>>> "org.eclipse.rap.ui.workbench" or "org.eclipse.rap.rwt".
>>>>
>>>> Just out of curiosity what is this "patch.jar"?
>>>>
>>>> Tiago
>>
|
|
|
Powered by
FUDForum. Page generated in 0.03769 seconds
] 
Search
Help
Register
Login
Home
