|
| Re: cvs and Target Platform [message #23135 is a reply to message #23094] |
Tue, 23 September 2008 16:02   |
Eclipse User |
|
|
|
Originally posted by: zx.code9.com
P. Michael Hutchins wrote:
> The way we have Eclipse set up, we have to use an external cvs tool
> (wincvs) to update, etc. our Target Platform.
>
> This tends to cause problems, bec. one tends to drift into assuming that
> Eclipse's cvs support is doing everything for us.
>
> Is there a way to tell Eclipse to pay attention to the repository for
> the files in the Target Platform?
So, I have a suggestion for you. What I usually recommend people do is
if your target platform is in source control, you also have a Target
Definition file accompanied with it. The target definition file would
point to the directory that contains all the plug-ins, you can use
something like ${workspace_loc}/plugins to point relative to where the
project is located. Once you have the .target file, you can simply set
that as the target platform and everything is magically setup.
1) create a new target definition file (File->New->Plug-in
Development->Target Definition
2) the location should point to relative location of the plugins
directory so the target definition could be shared with colleagues
3) click "Set as Target Platform" and bam, you get your target setup
Let me know if that helps.
Cheers,
~ Chris
|
|
|
|
| Re: cvs and Target Platform [message #23210 is a reply to message #23175] |
Tue, 23 September 2008 17:21 |
| Eclipse User |
|
|
|
Originally posted by: zx.code9.com
P. Michael Hutchins wrote:
> Thanks, Chris!
>
> ..but I'm not clear on exactly how this gets Eclipse to pay attention to
> when the TP changes in the Repository (eg).
>
> Are you saying that if I put the .target file in a place in the Repos.
> that Eclipse knows about, that will do it? I wouldn't think so.
>
> That(latter)'s what I want to achieve.
>
> ..but also, I'm interested in how you'd articulate what is the main
> goal/effect of what you suggest.
PDE will become very upset with you if the target changes externally,
you'll see things like "resource out of sync" errors as PDE maintains a
set of timestamps to determine if the internal "pde state" needs to be
recomputed.
My suggestion was to simply have a project that houses your target
platform in CVS and use that as your target platform using the target
definition. When developers update or check things out, they have to
reset the target platform to use anything new with a simple hyperlink.
There is no automatic way to simply have your target platform update
from time to time, at least there's no easy way to do it that I can
think of. This may get easier in the future once PDE starts to integrate
with p2 better and have p2 manage the target platform.
Cheers,
~ Chris
|
|
|
| Re: cvs and Target Platform [message #23505 is a reply to message #23175] |
Wed, 24 September 2008 14:45 |
| Eclipse User |
|
|
|
Originally posted by: zx.code9.com
P. Michael Hutchins wrote:
> Thanks, Chris!
>
> ..but I'm not clear on exactly how this gets Eclipse to pay attention to
> when the TP changes in the Repository (eg).
>
> Are you saying that if I put the .target file in a place in the Repos.
> that Eclipse knows about, that will do it? I wouldn't think so.
>
> That(latter)'s what I want to achieve.
>
> ..but also, I'm interested in how you'd articulate what is the main
> goal/effect of what you suggest.
How are things going ?
Cheers,
~ Chris
|
|
|
|
| Re: cvs and Target Platform [message #24355 is a reply to message #24273] |
Thu, 25 September 2008 21:06 |
| Eclipse User |
|
|
|
Originally posted by: zx.code9.com
P. Michael Hutchins wrote:
> Hi, Chris.
>
> I got interrupted by a major ~fire~ ydy.
>
> I had read your 2nd reply - and had had time to have the thought that we
> didn't seem to be connecting - in some way and for some reason that I
> didn't understand.
>
> Let me try to say again what I'm looking for:
>
> When I do Team Synchronizing, I would like Eclipse to show me if
> anything in the Target Platform has changed..
> (either on my end or the repository's)
>
> .just like it does for all my Projects/Plug-ins.
I may have to demonstrated this over VNC or something :)
What you're describing is basically possible with this setup:
1) store your target platform in a project in CVS
2) create a target definition file inside that project and point it to
the plugins
3) set the target platform using the target definition file
With this setup, anytime you sync with CVS, you'll see if the target
platform has changed... you can choose to update... and accept those
changes. If you're happy, you can than reset the target platform using
the target definition file which acts as the arbiter of what you want to
live in the target.
If you still need help with this a bit, feel free to email me and I'll
see if I can spare sometime to do a quick demo.
Cheers,
~ Chris
|
|
|
| Re: cvs and Target Platform [message #580969 is a reply to message #23094] |
Tue, 23 September 2008 16:02 |
 Chris Aniszczyk
Messages: 674
Registered: July 2009 |
Senior Member |
|
|
P. Michael Hutchins wrote:
> The way we have Eclipse set up, we have to use an external cvs tool
> (wincvs) to update, etc. our Target Platform.
>
> This tends to cause problems, bec. one tends to drift into assuming that
> Eclipse's cvs support is doing everything for us.
>
> Is there a way to tell Eclipse to pay attention to the repository for
> the files in the Target Platform?
So, I have a suggestion for you. What I usually recommend people do is
if your target platform is in source control, you also have a Target
Definition file accompanied with it. The target definition file would
point to the directory that contains all the plug-ins, you can use
something like ${workspace_loc}/plugins to point relative to where the
project is located. Once you have the .target file, you can simply set
that as the target platform and everything is magically setup.
1) create a new target definition file (File->New->Plug-in
Development->Target Definition
2) the location should point to relative location of the plugins
directory so the target definition could be shared with colleagues
3) click "Set as Target Platform" and bam, you get your target setup
Let me know if that helps.
Cheers,
~ Chris
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03806 seconds
] 
Search
Help
Register
Login
Home
