Home » Eclipse Projects » Eclipse Platform » PDE self-hosting versus clean packaging
| PDE self-hosting versus clean packaging [message #294751] |
Thu, 17 November 2005 09:29  |
Eclipse User |
|
|
|
Originally posted by: bim2005.basistech.com
The PDE build tab allows/encourages the creation of JAR files. However, this
seems to conflict with the self-hosting functionalty.
In MANIFEST.MF, the self-hosting environment depends on having your class
directory listed as part of Bundle-Classpath. However, if you then turn
around and tell the build tab to package that class directory as a JAR, it's
the JAR that has to be on the bundle classpath.
The PDE can't / won't maintain a JAR file as part of the ordinary build
cycle, you have to run the Ant build to get this to happen. So, what do
people do? Run Ant all the time? put both the class dir and the jar name in
the bundle classpath, on the theory that the directory is harmless when
deployed?
|
|
| |
| Re: PDE self-hosting versus clean packaging [message #294753 is a reply to message #294752] |
Thu, 17 November 2005 09:42  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
In fact, your manifest should say the jar if you want a jar when it is
finally deployed. Again the PDE takes care of this.
See:
http://eclipse.org/articles/Article-PDE-does-plugins/PDE-int ro.html
For how the PDE works.
Rich Kulp wrote:
> The PDE understands this and when you run under self-hosting it puts the
> output classpath automatically. No need to change the manifest.
>
> Benson Margulies wrote:
>
>> The PDE build tab allows/encourages the creation of JAR files.
>> However, this seems to conflict with the self-hosting functionalty.
>>
>> In MANIFEST.MF, the self-hosting environment depends on having your
>> class directory listed as part of Bundle-Classpath. However, if you
>> then turn around and tell the build tab to package that class
>> directory as a JAR, it's the JAR that has to be on the bundle classpath.
>>
>> The PDE can't / won't maintain a JAR file as part of the ordinary
>> build cycle, you have to run the Ant build to get this to happen. So,
>> what do people do? Run Ant all the time? put both the class dir and
>> the jar name in the bundle classpath, on the theory that the directory
>> is harmless when deployed?
>>
>>
>
--
Thanks,
Rich Kulp
|
|
|
| Re: PDE self-hosting versus clean packaging [message #294757 is a reply to message #294753] |
Thu, 17 November 2005 10:14 |
| Eclipse User |
|
|
|
Originally posted by: bim2005.basistech.com
Let me see if I'm following here. If I set up build.properties to call for a
jar, and put the jar in the classpath, then the self-hosting will infer the
contents of the jar from this information and manage classpath?
I got into this because I'm failing to find any way to make a
java.nio.charset.spi.Provider work in self-hosting. This requires a META-INF
file, and my META-INF file is never seen by the JRE. I thought that
jar-ifying would do the job.
"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> wrote in message
news:dli4ss$u47$3@news.eclipse.org...
> In fact, your manifest should say the jar if you want a jar when it is
> finally deployed. Again the PDE takes care of this.
>
> See:
>
> http://eclipse.org/articles/Article-PDE-does-plugins/PDE-int ro.html
>
> For how the PDE works.
>
> Rich Kulp wrote:
>> The PDE understands this and when you run under self-hosting it puts the
>> output classpath automatically. No need to change the manifest.
>>
>> Benson Margulies wrote:
>>
>>> The PDE build tab allows/encourages the creation of JAR files. However,
>>> this seems to conflict with the self-hosting functionalty.
>>>
>>> In MANIFEST.MF, the self-hosting environment depends on having your
>>> class directory listed as part of Bundle-Classpath. However, if you then
>>> turn around and tell the build tab to package that class directory as a
>>> JAR, it's the JAR that has to be on the bundle classpath.
>>>
>>> The PDE can't / won't maintain a JAR file as part of the ordinary build
>>> cycle, you have to run the Ant build to get this to happen. So, what do
>>> people do? Run Ant all the time? put both the class dir and the jar name
>>> in the bundle classpath, on the theory that the directory is harmless
>>> when deployed?
>>>
>>>
>>
>
> --
> Thanks,
> Rich Kulp
|
|
|
| Re: PDE self-hosting versus clean packaging [message #294758 is a reply to message #294757] |
Thu, 17 November 2005 10:29 |
| Eclipse User |
|
|
|
Originally posted by: bim2005.basistech.com
I've done more of the reading, and I seem to have discovered the following:
1) There doesn't seem to be a way in build.properties to request that an
arbitrary META-INF file be incorporated in a jar.
2) I don't really want to build a JAR at all. I want my java.nio.charset.spi
provider to work.
3) Perhaps I should build a JAR with non-PDE means and incorporate it in
some other plugin, instead.
"Benson Margulies" <bim2005@basistech.com> wrote in message
news:dli6nv$1pn$1@news.eclipse.org...
> Let me see if I'm following here. If I set up build.properties to call for
> a jar, and put the jar in the classpath, then the self-hosting will infer
> the contents of the jar from this information and manage classpath?
>
> I got into this because I'm failing to find any way to make a
> java.nio.charset.spi.Provider work in self-hosting. This requires a
> META-INF file, and my META-INF file is never seen by the JRE. I thought
> that jar-ifying would do the job.
>
>
> "Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> wrote in message
> news:dli4ss$u47$3@news.eclipse.org...
>> In fact, your manifest should say the jar if you want a jar when it is
>> finally deployed. Again the PDE takes care of this.
>>
>> See:
>>
>> http://eclipse.org/articles/Article-PDE-does-plugins/PDE-int ro.html
>>
>> For how the PDE works.
>>
>> Rich Kulp wrote:
>>> The PDE understands this and when you run under self-hosting it puts the
>>> output classpath automatically. No need to change the manifest.
>>>
>>> Benson Margulies wrote:
>>>
>>>> The PDE build tab allows/encourages the creation of JAR files. However,
>>>> this seems to conflict with the self-hosting functionalty.
>>>>
>>>> In MANIFEST.MF, the self-hosting environment depends on having your
>>>> class directory listed as part of Bundle-Classpath. However, if you
>>>> then turn around and tell the build tab to package that class directory
>>>> as a JAR, it's the JAR that has to be on the bundle classpath.
>>>>
>>>> The PDE can't / won't maintain a JAR file as part of the ordinary build
>>>> cycle, you have to run the Ant build to get this to happen. So, what do
>>>> people do? Run Ant all the time? put both the class dir and the jar
>>>> name in the bundle classpath, on the theory that the directory is
>>>> harmless when deployed?
>>>>
>>>>
>>>
>>
>> --
>> Thanks,
>> Rich Kulp
>
>
|
|
|
| Re: PDE self-hosting versus clean packaging [message #294780 is a reply to message #294751] |
Thu, 17 November 2005 14:44 |
| Eclipse User |
|
|
|
Originally posted by: automatic.javalobby.org
I feel your pain. As of right now I do not care for the PDE Build, so I set up my Eclipse PDE Projects to run under self hosting and build a homegrown script to generate the desired output for production.
Good Luck,
James E. Ervin
|
|
|
Goto Forum:
Current Time: Sun Jul 27 10:03:42 EDT 2025
Powered by FUDForum. Page generated in 0.09545 seconds |
Home