| Dave,
If two workspaces are referencing the same git repo, then modifications to the git repo will be reflected in both workspaces. If you don't want this to happen, you'll need to clone another copy of the repo and import that into your workspace. I'm currently doing this so that I can have ptp_5_0 in one workspace and master in another.
I've added PTP_5_0_4 tags to the ptp and photran repos, so this should make it easier to check out the 5.0.4 version.
This is what I did:
1. Create a new workspace. 2. Import the plugins from each of the subdirectories (core, debug, etc.) 3. Select one of the plugins and select Team>Reset... 4. From the Tags folder, choose PTP_5_0_4 5. Set the "Reset type" to "Hard". 6. Click the Reset button
Your workspace should be at 5.0.4 at this point. If you have an existing workspace, you can just reset it to the PTP_5_0_4 tag. Make sure you don't have any changes you want to keep as they will be removed.
Greg
On Jan 10, 2012, at 9:36 PM, Dave Wootton wrote:
Once I did this, I switched back to
my original workspace which was imported from this same git repository
and noticed that it apparently was updated to PTP 5.0.4 level. Also, since
I wanted a zip file of the source at PTP 5.0.4 level I think I needed to
use the export to archive option and exclude all .class files, since the
source files don't physically reside in my workspace.
Dave
|
|
| Re: [ptp-dev] Getting
a copy of PTP 5.0.4 source |
| Dave Wootton
| to:
| Parallel Tools Platform general developers
|
01/10/2012 09:16 PM |
Please respond to Parallel Tools
Platform general developers
|
|
|
Greg
I couldn't find anything in the PTP wiki that explained the steps to check
out by commit id so want to verify that I have this right.
I did the following, starting with a git repository I cloned at the ptp_5_0
level
1) Create a new workspace to work in
2) Import all plugin source from my local git repository at the ptp_5_0
level
3) To test the steps I selected only the org.eclipse.ptp plugin then right
clicked in package explorer and clicked Replace with->commit
4) I got a 'Select a commit' dialog which I scrolled to until I found what
think is the commit id where the dialog only shows me the first 8 characters
of the id. The commit was labeled 'Put includeemptydirs in correct place'
with a timestamp of 11/12/2011 09:34:14
5) This ran and when it completed, most of the PTP plugins in package
explorer were updated with '>' indicating they were modified. For the
few I spot-checekd it looked like the only updated file was pom.xml.
6) I selected all the remaining plugins and repeated step 4. This blocked
for about 5 minutes at the 'discard local changes' and finally completed,
where it looked like more, but still not all plugins were updated to show
'>' status
7) After I did this, I repeated steps 3 and 4 thinking I could find a way
to get the 'Select a commit' dialog to shoow me a full commit id. I couldn't
find anything and double clicked the same commit id. THis appeared to run
again, but since I picked the same commit id, I think this didn't change
anything.
Is this a correct set of steps?
Thanks
Dave
|
|
| Re: [ptp-dev] Getting
a copy of PTP 5.0.4 source |
| Greg Watson
| to:
| Parallel Tools Platform general
developers
|
01/09/2012 05:22 PM |
Please respond to Parallel Tools Platform general developers
| |
|
Dave,
The commit ID for 5.0.4 is a3efe7a2a670e1bb8cbb3b8c34a4998a75fb7889
You should check out this version.
Greg
On Jan 9, 2012, at 5:09 PM, Dave Wootton wrote:
>
> Hi
> I have extracted a GIT repository with ptp_5_0 code, and where I need
to
> extract PTP source code at the 5.0.4 level. What is the set of steps
I need
> to do to extract this level of source code?
>
> Thanks
> Dave
>
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
|
