I have component A & B. A has projects 1,2,3,4,5
I want to move projects 1,2 from project A to B.
I did that from a workspace based on my stream.
Then I loaded the 2 components.
When I do history on one of the files in that project, It shows me
only 1 changeset while this file has been modified many times in the
past before it was moved.

So the question here is
a) how do I get the history back?

Now I am also trying to figure out if I can undo what I just did -
moving the projects from component A to B and get back to the
original state.

Project A is part of 2 different streams - X & Y. X is my main
stream and Y is the one I have been working with where I have made
all these changes. If I look at component A in a workspace based on
stream X, I still see projects 1 & 2 there which is what I want
to get back to.

So my second question is:
a) if I simply delete the workspace on stream Y, do I throw away my
move of projects from component A to B ?
b) If not, if I delete the stream Y itself (I can recreate another
stream no problem), can I undo the changes I made, since I haven;t
really delivered from stream Y to stream X or any other stream yet.

akmathur wrote:
I have component A & B. A has projects 1,2,3,4,5
I want to move projects 1,2 from project A to B.
I did that from a workspace based on my stream.
Then I loaded the 2 components.
When I do history on one of the files in that project, It shows me
only 1 changeset while this file has been modified many times in the
past before it was moved.

So the question here is
a) how do I get the history back?

The history is there. If you are using beta2, it is not properly
exposed in the UI. If you are using M5, it should be.

Now I am also trying to figure out if I can undo what I just did -
moving the projects from component A to B and get back to the
original state.

Project A is part of 2 different streams - X & Y. X is my main
stream and Y is the one I have been working with where I have made
all these changes. If I look at component A in a workspace based on
stream X, I still see projects 1 & 2 there which is what I want
to get back to.

So my second question is:
a) if I simply delete the workspace on stream Y, do I throw away my
move of projects from component A to B ? b) If not, if I delete the
stream Y itself (I can recreate another
stream no problem), can I undo the changes I made, since I haven;t
really delivered from stream Y to stream X or any other stream yet.


The cross component links are preserved outside of a workspace's change
history, and in M5, any workspace which contains the "moved into"
change-set should be able to follow the history all the way back to the
originating component.

HTH,
JohnC
SCM Server

To be (more) clear : in order to move an item across component
boundaries, you need to do so using the "Move ..." button off of the
"Projects In Component" section of the Repository Workspace Editor.
At this time all that is supported is moving projects from the root
folder of one component into the root folder of another.

We are looking at providing more flexibility for cross-component moves
in future releases.

JohnC
SCM Server

John Camelon wrote:


akmathur wrote:
I have component A & B. A has projects 1,2,3,4,5
I want to move projects 1,2 from project A to B.
I did that from a workspace based on my stream.
Then I loaded the 2 components.
When I do history on one of the files in that project, It shows me
only 1 changeset while this file has been modified many times in the
past before it was moved.

So the question here is
a) how do I get the history back?

The history is there. If you are using beta2, it is not properly
exposed in the UI. If you are using M5, it should be.

Now I am also trying to figure out if I can undo what I just did -
moving the projects from component A to B and get back to the
original state.

Project A is part of 2 different streams - X & Y. X is my main
stream and Y is the one I have been working with where I have made
all these changes. If I look at component A in a workspace based on
stream X, I still see projects 1 & 2 there which is what I want
to get back to.

So my second question is:
a) if I simply delete the workspace on stream Y, do I throw away my
move of projects from component A to B ? b) If not, if I delete the
stream Y itself (I can recreate another
stream no problem), can I undo the changes I made, since I haven;t
really delivered from stream Y to stream X or any other stream yet.


The cross component links are preserved outside of a workspace's change
history, and in M5, any workspace which contains the "moved into"
change-set should be able to follow the history all the way back to
the originating component.

HTH,
JohnC
SCM Server

I wasn't able to find the "Projects in Component" section of the
Repository Workspace Editor. Is it still there in 2.0Beta1? (The only
sections I see are: "Details" "Components", and "Flow Targets".)

And if it isn't there anymore, how does one move items across component
boundaries without losing history?

Cheers,
Geoff

John Camelon wrote:
To be (more) clear : in order to move an item across component
boundaries, you need to do so using the "Move ..." button off of the
"Projects In Component" section of the Repository Workspace Editor.
At this time all that is supported is moving projects from the root
folder of one component into the root folder of another.

We are looking at providing more flexibility for cross-component moves
in future releases.

JohnC
SCM Server

John Camelon wrote:


akmathur wrote:
I have component A & B. A has projects 1,2,3,4,5
I want to move projects 1,2 from project A to B.
I did that from a workspace based on my stream.
Then I loaded the 2 components.
When I do history on one of the files in that project, It shows me
only 1 changeset while this file has been modified many times in the
past before it was moved.

So the question here is
a) how do I get the history back?

The history is there. If you are using beta2, it is not properly
exposed in the UI. If you are using M5, it should be.

Now I am also trying to figure out if I can undo what I just did -
moving the projects from component A to B and get back to the
original state.

Project A is part of 2 different streams - X & Y. X is my main
stream and Y is the one I have been working with where I have made
all these changes. If I look at component A in a workspace based on
stream X, I still see projects 1 & 2 there which is what I want
to get back to.

So my second question is:
a) if I simply delete the workspace on stream Y, do I throw away my
move of projects from component A to B ? b) If not, if I delete the
stream Y itself (I can recreate another
stream no problem), can I undo the changes I made, since I haven;t
really delivered from stream Y to stream X or any other stream yet.


The cross component links are preserved outside of a workspace's change
history, and in M5, any workspace which contains the "moved into"
change-set should be able to follow the history all the way back to
the originating component.

HTH,
JohnC
SCM Server

It changed towards the end of 1.0. Now projects have a "Move in
Repository" action off of them.

HTH,
JohnC

Geoffrey Clemm wrote:
I wasn't able to find the "Projects in Component" section of the
Repository Workspace Editor. Is it still there in 2.0Beta1? (The
only sections I see are: "Details" "Components", and "Flow Targets".)

And if it isn't there anymore, how does one move items across
component boundaries without losing history?

Cheers,
Geoff

John Camelon wrote:
To be (more) clear : in order to move an item across component
boundaries, you need to do so using the "Move ..." button off of the
"Projects In Component" section of the Repository Workspace Editor.
At this time all that is supported is moving projects from the root
folder of one component into the root folder of another.

We are looking at providing more flexibility for cross-component moves
in future releases.

JohnC
SCM Server

John Camelon wrote:


akmathur wrote:
I have component A & B. A has projects 1,2,3,4,5
I want to move projects 1,2 from project A to B.
I did that from a workspace based on my stream.
Then I loaded the 2 components.
When I do history on one of the files in that project, It shows me
only 1 changeset while this file has been modified many times in the
past before it was moved.

So the question here is
a) how do I get the history back?

The history is there. If you are using beta2, it is not properly
exposed in the UI. If you are using M5, it should be.

Now I am also trying to figure out if I can undo what I just did -
moving the projects from component A to B and get back to the
original state.

Project A is part of 2 different streams - X & Y. X is my main
stream and Y is the one I have been working with where I have made
all these changes. If I look at component A in a workspace based on
stream X, I still see projects 1 & 2 there which is what I want
to get back to.

So my second question is:
a) if I simply delete the workspace on stream Y, do I throw away my
move of projects from component A to B ? b) If not, if I delete the
stream Y itself (I can recreate another
stream no problem), can I undo the changes I made, since I haven;t
really delivered from stream Y to stream X or any other stream yet.


The cross component links are preserved outside of a workspace's change
history, and in M5, any workspace which contains the "moved into"
change-set should be able to follow the history all the way back to
the originating component.

HTH,
JohnC
SCM Server

Thanks, John ...

So I was able to move a single file from one component to another (and
preserve its history) by moving the project containing that file to the
other component, then moving the file, then moving the project back. Is
there a simpler way?

Cheers,
Geoff

johnc wrote:
It changed towards the end of 1.0. Now projects have a "Move in
Repository" action off of them.

HTH,
JohnC

Geoffrey Clemm wrote:
I wasn't able to find the "Projects in Component" section of the
Repository Workspace Editor. Is it still there in 2.0Beta1? (The
only sections I see are: "Details" "Components", and "Flow Targets".)

And if it isn't there anymore, how does one move items across
component boundaries without losing history?

Cheers,
Geoff

John Camelon wrote:
To be (more) clear : in order to move an item across component
boundaries, you need to do so using the "Move ..." button off of the
"Projects In Component" section of the Repository Workspace Editor.
At this time all that is supported is moving projects from the root
folder of one component into the root folder of another.

We are looking at providing more flexibility for cross-component moves
in future releases.

JohnC
SCM Server

John Camelon wrote:


akmathur wrote:
I have component A & B. A has projects 1,2,3,4,5
I want to move projects 1,2 from project A to B.
I did that from a workspace based on my stream.
Then I loaded the 2 components.
When I do history on one of the files in that project, It shows me
only 1 changeset while this file has been modified many times in the
past before it was moved.

So the question here is
a) how do I get the history back?

The history is there. If you are using beta2, it is not properly
exposed in the UI. If you are using M5, it should be.

Now I am also trying to figure out if I can undo what I just did -
moving the projects from component A to B and get back to the
original state.

Project A is part of 2 different streams - X & Y. X is my main
stream and Y is the one I have been working with where I have made
all these changes. If I look at component A in a workspace based on
stream X, I still see projects 1 & 2 there which is what I want
to get back to.

So my second question is:
a) if I simply delete the workspace on stream Y, do I throw away my
move of projects from component A to B ? b) If not, if I delete
the stream Y itself (I can recreate another
stream no problem), can I undo the changes I made, since I haven;t
really delivered from stream Y to stream X or any other stream yet.


The cross component links are preserved outside of a workspace's
change
history, and in M5, any workspace which contains the "moved into"
change-set should be able to follow the history all the way back to
the originating component.

HTH,
JohnC
SCM Server