Home » Archived » EPF » Eclipse shell sharing with EPF Composer 1.2: an example
|
| Re: Eclipse shell sharing with EPF Composer 1.2: an example [message #41141 is a reply to message #36657] |
Tue, 25 September 2007 17:15   |
Eclipse User |
|
|
|
Originally posted by: TBFowler.cox.net
Peter,
I did the copy/paste and EPF works fine and mylyn works nicely with it.
Thanks for the tip! I must have answered yes to some file replacements
where I should have ansered no because I now have two groupings of 'help,
dynamic help, and search help' entries in the help menu. If someone is
using an updated Eclipse could they just say no to all on the replacements?
I'm guessing that to have the tutorials and documentation they need to be
set up seperately? (I haven't learned how to do that yet.)
Thanks again for the hard work!
Thell
"Peter Haumer" <phaumer@us.ibm.com> wrote in message
news:f97qbs$q3k$1@build.eclipse.org...
> Hello. I thought I share this.
>
> One of the cool new features in version 1.2 is that EPF Composer supports
> shell sharing with Eclipse 3.3. So, if you already have Eclipse 3.3 on
> your machine you can install EPF Composer just right into it. Just
> copy-paste everything from EPFC's features and plugins directories into
> the respective directories of Eclipse 3.3 and start it. (It will prompt
> you to override files, but if you use the Eclipse and EPF release versions
> it will just override the same files. If you do this with updated versions
> of Eclipse, check which files you are overriding one by one).
>
> You can now take advantage of useful Eclipse plugins for EPF Composer. For
> example, you can use Mylyn to directly and graphically search, modify, and
> create bugzillas on bugs.eclipse.org . See this screen shot for an
> example: http://haumer.net/images/epfc-with-mylyn.gif
>
> All you need to do is to open the Mylyn views inside your authoring view.
> The "Task Repositories" view already has bugs.eclipse.org pre-configured.
> All you have to add is you username and password (double-click). The Task
> List shows bugs that yo manually added here. Click on the little arrow
> symbol on the right and "Search Repository.." to run a query. You add the
> bugs to your list via a right-click on the search results. Very handy
> extension.
>
> Go here to learn more about Mylyn: http://www.eclipse.org/mylyn/
>
> Get Eclipse 3.3 here: http://www.eclipse.org/downloads/
>
> Get EPF Composer 1.2 here:
> http://www.eclipse.org/epf/downloads/tool/epf1.2.0_downloads .php
>
>
>
> Thanks and best regards,
>
> Peter Haumer.
>
>
|
|
|
| Re: Eclipse shell sharing with EPF Composer 1.2: an example [message #42389 is a reply to message #41141] |
Tue, 02 October 2007 17:41 |
| Eclipse User |
|
|
|
Originally posted by: storaskar.xx.xxx.xxx
You got two groupings of "dynamic help, search help" due to our EPF RCP
plugin. Theoretically, when you shell-share there shouln't be any of EPF
RCP plugins.
We have those plugins in the case we don't shell-share.
There are 2 rcp plugins - one is "org.eclipse.epf.rcp_xx.xx..." and
"org.eclipse.epf.rcp.ui_xx...." and one EPF RCP feature. None of these
should be copied over when you shell-share. You could actually leave EPF
RCP feature and "org.eclipse.epf.rcp.." plugin and it won't harm anything.
But important one to take it out would be
"org.eclipse.epf.rcp.ui_xx.xx....jar". You could just rename that now and
restart your eclipse. You will see that extra groupings of help is gone.
Our EPF rcp.ui plugin customization of the standard Eclipse stuff, like it
re-creates the menu items like the Help & search.
NOTE: Also, make sure not to touch "org.eclipse.rcp" plugin since that's
standard Eclipse RCP plugin. I almost accidentally changed name of that
plugin.
Regd. putting EPF composer plugins on updated Eclipse, it may not work
based on API changes. Here is list of dependent plugins EPFC [Version
1.2/1.2.0.1] is based on.
http://www.eclipse.org/epf/composer_dev_guide/dev_env.php
Now, e.g. Let's say you are using EMF 2.3.1 rather than 2.3.0. Assume
there are significant EMF API changes from 2.3.0 to 2.3.1. And EPF
composer happen to use those APIs from 2.3.0, when you have 2.3.1 EMF,
EPFC will fail expecting 2.3.0 APIs. Most of the time, Eclipse teams are
pretty good in keeping backward compatibility, but again you never know.
So, We would recommend you to shell-share when there is version
compatibility.
Regards,
Shilpa
|
|
|
| Re: Eclipse shell sharing with EPF Composer 1.2: an example [message #44752 is a reply to message #42389] |
Fri, 19 October 2007 20:01 |
| Eclipse User |
|
|
|
Originally posted by: TBFowler.cox.net
Thank you Shilpa. I disabled the org.eclipse.epf.rcp feature in
configuration manager and all looks good so far.
"Shilpa Toraskar" <storaskar@xx.xxx.xxx> wrote in message
news:1982f3e161b9fe1b2fc586d3e1136b73$1@www.eclipse.org...
> You got two groupings of "dynamic help, search help" due to our EPF RCP
> plugin. Theoretically, when you shell-share there shouln't be any of EPF
> RCP plugins. We have those plugins in the case we don't shell-share.
> There are 2 rcp plugins - one is "org.eclipse.epf.rcp_xx.xx..." and
> "org.eclipse.epf.rcp.ui_xx...." and one EPF RCP feature. None of these
> should be copied over when you shell-share. You could actually leave EPF
> RCP feature and "org.eclipse.epf.rcp.." plugin and it won't harm anything.
> But important one to take it out would be
> "org.eclipse.epf.rcp.ui_xx.xx....jar". You could just rename that now and
> restart your eclipse. You will see that extra groupings of help is gone.
> Our EPF rcp.ui plugin customization of the standard Eclipse stuff, like it
> re-creates the menu items like the Help & search.
>
> NOTE: Also, make sure not to touch "org.eclipse.rcp" plugin since that's
> standard Eclipse RCP plugin. I almost accidentally changed name of that
> plugin.
>
> Regd. putting EPF composer plugins on updated Eclipse, it may not work
> based on API changes. Here is list of dependent plugins EPFC [Version
> 1.2/1.2.0.1] is based on.
> http://www.eclipse.org/epf/composer_dev_guide/dev_env.php
>
> Now, e.g. Let's say you are using EMF 2.3.1 rather than 2.3.0. Assume
> there are significant EMF API changes from 2.3.0 to 2.3.1. And EPF
> composer happen to use those APIs from 2.3.0, when you have 2.3.1 EMF,
> EPFC will fail expecting 2.3.0 APIs. Most of the time, Eclipse teams are
> pretty good in keeping backward compatibility, but again you never know.
> So, We would recommend you to shell-share when there is version
> compatibility.
>
> Regards,
>
> Shilpa
>
>
|
|
|
| Re: Eclipse shell sharing with EPF Composer 1.2: an example [message #583484 is a reply to message #36657] |
Tue, 25 September 2007 17:15 |
 Thell
Messages: 4
Registered: July 2009 |
Junior Member |
|
|
Peter,
I did the copy/paste and EPF works fine and mylyn works nicely with it.
Thanks for the tip! I must have answered yes to some file replacements
where I should have ansered no because I now have two groupings of 'help,
dynamic help, and search help' entries in the help menu. If someone is
using an updated Eclipse could they just say no to all on the replacements?
I'm guessing that to have the tutorials and documentation they need to be
set up seperately? (I haven't learned how to do that yet.)
Thanks again for the hard work!
Thell
"Peter Haumer" <phaumer@us.ibm.com> wrote in message
news:f97qbs$q3k$1@build.eclipse.org...
> Hello. I thought I share this.
>
> One of the cool new features in version 1.2 is that EPF Composer supports
> shell sharing with Eclipse 3.3. So, if you already have Eclipse 3.3 on
> your machine you can install EPF Composer just right into it. Just
> copy-paste everything from EPFC's features and plugins directories into
> the respective directories of Eclipse 3.3 and start it. (It will prompt
> you to override files, but if you use the Eclipse and EPF release versions
> it will just override the same files. If you do this with updated versions
> of Eclipse, check which files you are overriding one by one).
>
> You can now take advantage of useful Eclipse plugins for EPF Composer. For
> example, you can use Mylyn to directly and graphically search, modify, and
> create bugzillas on bugs.eclipse.org . See this screen shot for an
> example: http://haumer.net/images/epfc-with-mylyn.gif
>
> All you need to do is to open the Mylyn views inside your authoring view.
> The "Task Repositories" view already has bugs.eclipse.org pre-configured.
> All you have to add is you username and password (double-click). The Task
> List shows bugs that yo manually added here. Click on the little arrow
> symbol on the right and "Search Repository.." to run a query. You add the
> bugs to your list via a right-click on the search results. Very handy
> extension.
>
> Go here to learn more about Mylyn: http://www.eclipse.org/mylyn/
>
> Get Eclipse 3.3 here: http://www.eclipse.org/downloads/
>
> Get EPF Composer 1.2 here:
> http://www.eclipse.org/epf/downloads/tool/epf1.2.0_downloads .php
>
>
>
> Thanks and best regards,
>
> Peter Haumer.
>
>
|
|
|
| Re: Eclipse shell sharing with EPF Composer 1.2: an example [message #584090 is a reply to message #41141] |
Tue, 02 October 2007 17:41 |
Shilpa Toraskar
Messages: 102
Registered: July 2009 |
Senior Member |
|
|
You got two groupings of "dynamic help, search help" due to our EPF RCP
plugin. Theoretically, when you shell-share there shouln't be any of EPF
RCP plugins.
We have those plugins in the case we don't shell-share.
There are 2 rcp plugins - one is "org.eclipse.epf.rcp_xx.xx..." and
"org.eclipse.epf.rcp.ui_xx...." and one EPF RCP feature. None of these
should be copied over when you shell-share. You could actually leave EPF
RCP feature and "org.eclipse.epf.rcp.." plugin and it won't harm anything.
But important one to take it out would be
"org.eclipse.epf.rcp.ui_xx.xx....jar". You could just rename that now and
restart your eclipse. You will see that extra groupings of help is gone.
Our EPF rcp.ui plugin customization of the standard Eclipse stuff, like it
re-creates the menu items like the Help & search.
NOTE: Also, make sure not to touch "org.eclipse.rcp" plugin since that's
standard Eclipse RCP plugin. I almost accidentally changed name of that
plugin.
Regd. putting EPF composer plugins on updated Eclipse, it may not work
based on API changes. Here is list of dependent plugins EPFC [Version
1.2/1.2.0.1] is based on.
http://www.eclipse.org/epf/composer_dev_guide/dev_env.php
Now, e.g. Let's say you are using EMF 2.3.1 rather than 2.3.0. Assume
there are significant EMF API changes from 2.3.0 to 2.3.1. And EPF
composer happen to use those APIs from 2.3.0, when you have 2.3.1 EMF,
EPFC will fail expecting 2.3.0 APIs. Most of the time, Eclipse teams are
pretty good in keeping backward compatibility, but again you never know.
So, We would recommend you to shell-share when there is version
compatibility.
Regards,
Shilpa
|
|
|
| Re: Eclipse shell sharing with EPF Composer 1.2: an example [message #585197 is a reply to message #42389] |
Fri, 19 October 2007 20:01 |
Thell
Messages: 4
Registered: July 2009 |
Junior Member |
|
|
Thank you Shilpa. I disabled the org.eclipse.epf.rcp feature in
configuration manager and all looks good so far.
"Shilpa Toraskar" <storaskar@xx.xxx.xxx> wrote in message
news:1982f3e161b9fe1b2fc586d3e1136b73$1@www.eclipse.org...
> You got two groupings of "dynamic help, search help" due to our EPF RCP
> plugin. Theoretically, when you shell-share there shouln't be any of EPF
> RCP plugins. We have those plugins in the case we don't shell-share.
> There are 2 rcp plugins - one is "org.eclipse.epf.rcp_xx.xx..." and
> "org.eclipse.epf.rcp.ui_xx...." and one EPF RCP feature. None of these
> should be copied over when you shell-share. You could actually leave EPF
> RCP feature and "org.eclipse.epf.rcp.." plugin and it won't harm anything.
> But important one to take it out would be
> "org.eclipse.epf.rcp.ui_xx.xx....jar". You could just rename that now and
> restart your eclipse. You will see that extra groupings of help is gone.
> Our EPF rcp.ui plugin customization of the standard Eclipse stuff, like it
> re-creates the menu items like the Help & search.
>
> NOTE: Also, make sure not to touch "org.eclipse.rcp" plugin since that's
> standard Eclipse RCP plugin. I almost accidentally changed name of that
> plugin.
>
> Regd. putting EPF composer plugins on updated Eclipse, it may not work
> based on API changes. Here is list of dependent plugins EPFC [Version
> 1.2/1.2.0.1] is based on.
> http://www.eclipse.org/epf/composer_dev_guide/dev_env.php
>
> Now, e.g. Let's say you are using EMF 2.3.1 rather than 2.3.0. Assume
> there are significant EMF API changes from 2.3.0 to 2.3.1. And EPF
> composer happen to use those APIs from 2.3.0, when you have 2.3.1 EMF,
> EPFC will fail expecting 2.3.0 APIs. Most of the time, Eclipse teams are
> pretty good in keeping backward compatibility, but again you never know.
> So, We would recommend you to shell-share when there is version
> compatibility.
>
> Regards,
>
> Shilpa
>
>
|
|
|
Goto Forum:
Current Time: Tue Apr 23 06:36:29 GMT 2024
Powered by FUDForum. Page generated in 0.04250 seconds |
] 
Search
Help
Register
Login
Home
