| How to attach source to Plugin Dependencies in 3.0 [message #168028] |
Sat, 10 July 2004 13:44  |
|
Hi,
I am trying to attach the Eclipse source of the various plugins that we have
dependcies on in our PDE projects. I have looked in the Prefences pages to
see if there was a way to do this once and for all, but there is none that
I see. I also try to attach it locally in the Plugin project by using, for
instance, Project-->Properties-->Java Build Path-->Libraries-->Plug-in
Dependencies-->runtime.jar-->Source attachment-->Edit. I have tried this
for both External File and External Folder. In both cases I can enter in
the location of the source, but there is no effect. When I revist the
assingmnet I find that it is not set.
Am I doing something wrong or is this as bug in 3.0?
Thanks,
Joel
|
|
|
| Re: How to attach source to Plugin Dependencies in 3.0 [message #168040 is a reply to message #168028] |
Sat, 10 July 2004 16:43  |
Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
You shouldn't have to for Eclipse plugins if:
1) You have the Eclipse SDK (this contains the source)
2) You have the Windows->Preferences->Plugin Development->Target
Platform pointing to this Eclipse SDK
If you had that then any of the Eclipse plugins should of had the source
already attached.
--
Thanks, Rich Kulp
|
|
|
| Re: How to attach source to Plugin Dependencies in 3.0 [message #168075 is a reply to message #168040] |
Sun, 11 July 2004 14:15 |
|
Thanks Rich. That is very interesting and makes perfect sense and it also
explains why this used to work for us way back when and then stopped at
some point (I totally forgot about that). But (:-) here are the problems
that that introduces:
1) It presumes that one is using the same release and version of Eclipse
for the develpment platform as the target environment. For a long time now
we have been using 3.0 but continued to target 2.1.x for our Plugins. Even
though we are now migrating with a clean break, there has to be plenty of
folks who have to support both.
2) At some point in time we stopped pointing to the SDK on which we were
developing becuase we found that using a complile environement that was
different than the taget deployment environment sometimes caused unexpected
side effects. Of course this can be controlled by *carefully* selecting the
plugins that are exposed to the plugins under development, but that can be
error prone.
I totally forgot that these were the reasons the led us astray to start
with. I fully argee that both can resolved by carefully crafting the PDE
environment, Is there, however, no other way to get the proper source
attached for a plugin under development?
Thanks kindly,
Joel
Rich Kulp wrote:
> You shouldn't have to for Eclipse plugins if:
>
> 1) You have the Eclipse SDK (this contains the source)
> 2) You have the Windows->Preferences->Plugin Development->Target
> Platform pointing to this Eclipse SDK
>
> If you had that then any of the Eclipse plugins should of had the source
> already attached.
>
>
|
|
|
| Re: How to attach source to Plugin Dependencies in 3.0 [message #168083 is a reply to message #168075] |
Sun, 11 July 2004 14:38 |
|
Okay, I'll answer my own question.
I investigated how the source is made available in SDK. No big surprise it
is all packaged up in a few plugins. I copied the ones I was insterested in
over to my platform release and the problem of not having source
attachments was solved. Of course this requires a little management on our
part, but I can live with that just fine.
Cheers,
Joel
Joel Rosi-Schwartz wrote:
> Thanks Rich. That is very interesting and makes perfect sense and it also
> explains why this used to work for us way back when and then stopped at
> some point (I totally forgot about that). But (:-) here are the problems
> that that introduces:
>
> 1) It presumes that one is using the same release and version of
> Eclipse
> for the develpment platform as the target environment. For a long time now
> we have been using 3.0 but continued to target 2.1.x for our Plugins. Even
> though we are now migrating with a clean break, there has to be plenty of
> folks who have to support both.
>
> 2) At some point in time we stopped pointing to the SDK on which
> we were
> developing becuase we found that using a complile environement that was
> different than the taget deployment environment sometimes caused
> unexpected side effects. Of course this can be controlled by *carefully*
> selecting the plugins that are exposed to the plugins under development,
> but that can be error prone.
>
> I totally forgot that these were the reasons the led us astray to start
> with. I fully argee that both can resolved by carefully crafting the PDE
> environment, Is there, however, no other way to get the proper source
> attached for a plugin under development?
>
> Thanks kindly,
> Joel
>
> Rich Kulp wrote:
>
>> You shouldn't have to for Eclipse plugins if:
>>
>> 1) You have the Eclipse SDK (this contains the source)
>> 2) You have the Windows->Preferences->Plugin Development->Target
>> Platform pointing to this Eclipse SDK
>>
>> If you had that then any of the Eclipse plugins should of had the source
>> already attached.
>>
>>
|
|
|
| Re: How to attach source to Plugin Dependencies in 3.0 [message #181879 is a reply to message #168083] |
Sun, 10 October 2004 16:07 |
 Klaus Wenger
Messages: 31
Registered: July 2009 |
Member |
|
|
Hello JDT community,
I guess the universal answer to the question is the existence of the new
extension point "org.eclipse.pde.core.source". If you create your own
plug-in or use wrappers around third party libraries that do not yet have
this extension, you may want to add an extension following this description:
http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse. pde.doc.user/reference/extension-points/org_eclipse_pde_core _source.html.
Example:
For a wrapper plug-in around the open source JasperReports this looks as
following:
[plugin.xml]
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin
id="net.sf.jasperreports"
name="JasperReports"
version="0.6.1"
provider-name="">
<runtime>
<library name="dist/jasperreports-0.6.1.jar">
<export name="*"/>
</library>
...
</runtime>
<extension point = "org.eclipse.pde.core.source">
<location path="src"/>
</extension>
</plugin>
The file structure looks like:
\eclipse\plugins\net.sf.jasperreports_0.6.1\dist\jasperrepor ts-0.6.1.jar
\eclipse\plugins\net.sf.jasperreports_0.6.1\src\net.sf.jaspe rreports_0.6.1\d
ist\jasperreports-0.6.1src.zip
Please note that the relative library path, the relative source path, the
runtime library name and the zip file name for the sources have quite some
parallels. Since the library in this example resides in the subdirectory
named dist, the source archive also has to reside in an according
subdirectory. The base name of the jar file of the open source library is
jasperreports-0.6.1. Therefore, the base name of the source archive needs to
be jasperreports-0.6.1src.
Have fun!
"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@etish.org> wrote in message
news:ccrjbo$i33$1@eclipse.org...
> Okay, I'll answer my own question.
>
> I investigated how the source is made available in SDK. No big surprise it
> is all packaged up in a few plugins. I copied the ones I was insterested
in
> over to my platform release and the problem of not having source
> attachments was solved. Of course this requires a little management on our
> part, but I can live with that just fine.
>
> Cheers,
> Joel
>
> Joel Rosi-Schwartz wrote:
>
> > Thanks Rich. That is very interesting and makes perfect sense and it
also
> > explains why this used to work for us way back when and then stopped at
> > some point (I totally forgot about that). But (:-) here are the problems
> > that that introduces:
> >
> > 1) It presumes that one is using the same release and version of
> > Eclipse
> > for the develpment platform as the target environment. For a long time
now
> > we have been using 3.0 but continued to target 2.1.x for our Plugins.
Even
> > though we are now migrating with a clean break, there has to be plenty
of
> > folks who have to support both.
> >
> > 2) At some point in time we stopped pointing to the SDK on which
> > we were
> > developing becuase we found that using a complile environement that was
> > different than the taget deployment environment sometimes caused
> > unexpected side effects. Of course this can be controlled by *carefully*
> > selecting the plugins that are exposed to the plugins under development,
> > but that can be error prone.
> >
> > I totally forgot that these were the reasons the led us astray to start
> > with. I fully argee that both can resolved by carefully crafting the PDE
> > environment, Is there, however, no other way to get the proper source
> > attached for a plugin under development?
> >
> > Thanks kindly,
> > Joel
> >
> > Rich Kulp wrote:
> >
> >> You shouldn't have to for Eclipse plugins if:
> >>
> >> 1) You have the Eclipse SDK (this contains the source)
> >> 2) You have the Windows->Preferences->Plugin Development->Target
> >> Platform pointing to this Eclipse SDK
> >>
> >> If you had that then any of the Eclipse plugins should of had the
source
> >> already attached.
> >>
> >>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03367 seconds
] 
Search
Help
Register
Login
Home
