Which is better plug-in development style as runtime classes specify [message #50701] |
Fri, 28 March 2003 06:17 |
Eclipse User |
|
|
|
Originally posted by: narushima_to.ybb.ne.jp
Plug-ins need to specify how to load Eclipse runtime classes.
It is two way:
1) specify in ".classpath" file. e.g,
<classpathentry kind="var"
path="ECLIPSE_HOME/plugins/org.eclipse.ui_2.0.2/workbench.jar "/>
2)
Download eclipse runtime package from CVS. and specify in
".project" file.
In case (1), It is light weight. when developer installs eclipse
default install, no problem to create plug-in.
In case (2), It need to download sources from CVS. Developer can
programming and debugging in eclipse lastest version with plug-in
development.
(But, Plug-in depend on Eclipse Main branch that may be desirable
on XP practice "Continuous Integration")
Which is better development style?
--
Narushima Hironori mailto:narushima_to@ybb.ne.jp
|
|
|
Re: Which is better plug-in development style as runtime classes specify [message #50729 is a reply to message #50701] |
Fri, 28 March 2003 06:29 |
Eclipse User |
|
|
|
Originally posted by: burner.zclipse.org
On Fri, 28 Mar 2003 15:17:10 +0900, Narushima Hironori wrote:
This question should go in the eclipse.tools newsgroups. However, to get
your question answered quickly...
> Plug-ins need to specify how to load Eclipse runtime classes.
>
> It is two way:
>
> 1) specify in ".classpath" file. e.g,
>
> <classpathentry kind="var"
> path="ECLIPSE_HOME/plugins/org.eclipse.ui_2.0.2/workbench.jar "/>
>
> 2)
>
> Download eclipse runtime package from CVS. and specify in
> ".project" file.
3) Import external plugins. (File/import/external plug-ins and
fragments/don't extract source/select all/...) Then you can build your
plug-in against those binary plugins. This is probably the best way.
Use the eclipse wiki [http://eclipsewiki.swiki.net/] to find answers to
similar frequently asked questions.
mike
|
|
|
Re: Which is better plug-in development style as runtime classes specify [message #50927 is a reply to message #50701] |
Mon, 31 March 2003 15:23 |
Eclipse User |
|
|
|
Originally posted by: daniel.megert.gmx.net
Narushima Hironori wrote:
>Plug-ins need to specify how to load Eclipse runtime classes.
>
>It is two way:
>
>1) specify in ".classpath" file. e.g,
>
><classpathentry kind="var"
> path="ECLIPSE_HOME/plugins/org.eclipse.ui_2.0.2/workbench.jar "/>
>
>2)
>
>Download eclipse runtime package from CVS. and specify in
>".project" file.
>
>In case (1), It is light weight. when developer installs eclipse
>default install, no problem to create plug-in.
>
>In case (2), It need to download sources from CVS. Developer can
>programming and debugging in eclipse lastest version with plug-in
>development.
>
>(But, Plug-in depend on Eclipse Main branch that may be desirable
>on XP practice "Continuous Integration")
>
>
>Which is better development style?
>
>
Both files may or may not be under (CVS) version control. They are used
for different purposes:
..project is owned by Platform core to manage the project meta data
(independent from Jdt).
..classpath is owned by JDT Core to manage the project's build path
HTH
Dani
|
|
|
Re: Which is better plug-in development style as runtime classes specify [message #592210 is a reply to message #50701] |
Fri, 28 March 2003 06:29 |
Eclipse User |
|
|
|
Originally posted by: burner.zclipse.org
On Fri, 28 Mar 2003 15:17:10 +0900, Narushima Hironori wrote:
This question should go in the eclipse.tools newsgroups. However, to get
your question answered quickly...
> Plug-ins need to specify how to load Eclipse runtime classes.
>
> It is two way:
>
> 1) specify in ".classpath" file. e.g,
>
> <classpathentry kind="var"
> path="ECLIPSE_HOME/plugins/org.eclipse.ui_2.0.2/workbench.jar "/>
>
> 2)
>
> Download eclipse runtime package from CVS. and specify in
> ".project" file.
3) Import external plugins. (File/import/external plug-ins and
fragments/don't extract source/select all/...) Then you can build your
plug-in against those binary plugins. This is probably the best way.
Use the eclipse wiki [http://eclipsewiki.swiki.net/] to find answers to
similar frequently asked questions.
mike
|
|
|
Re: Which is better plug-in development style as runtime classes specify [message #592292 is a reply to message #50701] |
Mon, 31 March 2003 15:23 |
Eclipse User |
|
|
|
Originally posted by: daniel.megert.gmx.net
Narushima Hironori wrote:
>Plug-ins need to specify how to load Eclipse runtime classes.
>
>It is two way:
>
>1) specify in ".classpath" file. e.g,
>
><classpathentry kind="var"
> path="ECLIPSE_HOME/plugins/org.eclipse.ui_2.0.2/workbench.jar "/>
>
>2)
>
>Download eclipse runtime package from CVS. and specify in
>".project" file.
>
>In case (1), It is light weight. when developer installs eclipse
>default install, no problem to create plug-in.
>
>In case (2), It need to download sources from CVS. Developer can
>programming and debugging in eclipse lastest version with plug-in
>development.
>
>(But, Plug-in depend on Eclipse Main branch that may be desirable
>on XP practice "Continuous Integration")
>
>
>Which is better development style?
>
>
Both files may or may not be under (CVS) version control. They are used
for different purposes:
..project is owned by Platform core to manage the project meta data
(independent from Jdt).
..classpath is owned by JDT Core to manage the project's build path
HTH
Dani
|
|
|
Powered by
FUDForum. Page generated in 0.03600 seconds