Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EPF » Method plugin vs Eclipse project/plugin
Method plugin vs Eclipse project/plugin [message #34243] Tue, 03 July 2007 06:33 Go to next message
Roman Smirak is currently offline Roman Smirak
Messages: 136
Registered: July 2009
Senior Member
Hi,

I'm describing a process based on OpenUP/Basic; it is spread over
several Method plugins; I would manage them separately from OpenUP basis
(base_concepts and openup_basic + logs folder) and to some extent -
separately from each other (a parallel: plugin development in eclipse).

I would like to manage a method plugin as an eclipse project - is there any
possibility?

Roman
Re: Method plugin vs Eclipse project/plugin [message #34479 is a reply to message #34243] Fri, 06 July 2007 17:15 Go to previous message
Peter Haumer is currently offline Peter Haumer
Messages: 228
Registered: July 2009
Senior Member
Hello Roman.
Unfortunately not. In EPF Composer the whole library is an Eclipse project.
You need to always manually import the latest version of OpenUP from the EPF
website into your method library. However, the File -> Import -> Method
Plugin wizard should make this a really easy thing to do; e.g. with OpenUP
you could do this once a week when the latest integration build is
available.

IBM's Rational Method Composer however aims at addressing such enterprise
needs of distributed method development, which is not in the scope of EPF
Composer. Therefore the upcoming version 7.2 of RMC (due in Q307) will
support Eclipse workspaces and the ability to make every method plugin a
project that can be managed on separate servers using even separate version
control systems.

Hope this helps,
Peter Haumer.


"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:f6d8md$rm6$1@build.eclipse.org...
> Hi,
>
> I'm describing a process based on OpenUP/Basic; it is spread over
> several Method plugins; I would manage them separately from OpenUP basis
> (base_concepts and openup_basic + logs folder) and to some extent -
> separately from each other (a parallel: plugin development in eclipse).
>
> I would like to manage a method plugin as an eclipse project - is there
> any possibility?
>
> Roman
>
Re: Method plugin vs Eclipse project/plugin [message #579775 is a reply to message #34243] Fri, 06 July 2007 17:15 Go to previous message
Peter Haumer is currently offline Peter Haumer
Messages: 228
Registered: July 2009
Senior Member
Hello Roman.
Unfortunately not. In EPF Composer the whole library is an Eclipse project.
You need to always manually import the latest version of OpenUP from the EPF
website into your method library. However, the File -> Import -> Method
Plugin wizard should make this a really easy thing to do; e.g. with OpenUP
you could do this once a week when the latest integration build is
available.

IBM's Rational Method Composer however aims at addressing such enterprise
needs of distributed method development, which is not in the scope of EPF
Composer. Therefore the upcoming version 7.2 of RMC (due in Q307) will
support Eclipse workspaces and the ability to make every method plugin a
project that can be managed on separate servers using even separate version
control systems.

Hope this helps,
Peter Haumer.


"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:f6d8md$rm6$1@build.eclipse.org...
> Hi,
>
> I'm describing a process based on OpenUP/Basic; it is spread over
> several Method plugins; I would manage them separately from OpenUP basis
> (base_concepts and openup_basic + logs folder) and to some extent -
> separately from each other (a parallel: plugin development in eclipse).
>
> I would like to manage a method plugin as an eclipse project - is there
> any possibility?
>
> Roman
>
Previous Topic:Improvement suggestions
Next Topic:Error in published site
Goto Forum:
  


Current Time: Sat Aug 30 04:33:50 EDT 2014

Powered by FUDForum. Page generated in 0.08645 seconds