It means that a new change set will get created and closed during every check in. This simulates how other SCM systems work, where you don't have the flexibility of having active change sets and reorganizing your changes after check in.

In fact, this is the default mode of working in the SCM web interface. The option in the Eclipse client was added 4 years ago, but I've personally never used it. We thought it may help simplify things for new users. If you have feedback on it, I'd love to hear about it.

Jean-Michel

It means that a new change set will get created and closed during every check in. This simulates how other SCM systems work, where you don't have the flexibility of having active change sets and reorganizing your changes after check in.

In fact, this is the default mode of working in the SCM web interface. The option in the Eclipse client was added 4 years ago, but I've personally never used it. We thought it may help simplify things for new users. If you have feedback on it, I'd love to hear about it.

Jean-Michel

I understand your explanation, but I can't seem to get it to work on my machine. For every check-in I do, I can still choose which change set I want (existing or new) and I am able to move files between them...

Does it work for you? Maybe I did something wrong, although configuring it is child's play ;)

I see the same behavior as Jan, i.e., setting that property has no
effect that I've been able to discover (I'm using the most recent 3.0
milestone build). In particular, change sets are definitely not
automatically closed for me in any scenario I could come up with.

I've reported this issue in work item 117071.

Cheers,
Geoff

On 6/4/2010 7:08 AM, JanVdP wrote:

jlemieuxwrote:
It means that a new change set will get created and closed during
every check in. This simulates how other SCM systems work, where you
don't have the flexibility of having active change sets and
reorganizing your changes after check in.

In fact, this is the default mode of working in the SCM web
interface. The option in the Eclipse client was added 4 years ago,
but I've personally never used it. We thought it may help simplify
things for new users. If you have feedback on it, I'd love to hear
about it.

Jean-Michel

I understand your explanation, but I can't seem to get it to work on
my machine. For every check-in I do, I can still choose which change
set I want (existing or new) and I am able to move files between
them...

Does it work for you? Maybe I did something wrong, although
configuring it is child's play ;)

I think auto-checkin also has to be on. Although, I don't know if it's supposed to work like that.

I understand your explanation, but I can't seem to get it to work on my machine. For every check-in I do, I can still choose which change set I want (existing or new) and I am able to move files between them...

Does it work for you? Maybe I did something wrong, although configuring it is child's play ;)

Auto-checkin being on is one of the configurations I tried ... that
doesn't help ... the change-sets are still not being auto-completed.

And note that auto-checkin is probably when you *don't* want to have
auto-complete on, since you'd end up with a new change-set every time
you did a save, which is unlikely to be what you want.

Cheers,
Geoff

On 6/4/2010 9:08 AM, tmok wrote:

I think auto-checkin also has to be on. Although, I don't know if it's
supposed to work like that.

JanVdPwrote:
I understand your explanation, but I can't seem to get it to work on
my machine. For every check-in I do, I can still choose which change
set I want (existing or new) and I am able to move files between
them...

Does it work for you? Maybe I did something wrong, although
configuring it is child's play ;)

For folks following this thread, the conclusion reached in work item
117071 is that this option only works if you are working in a private
workspace and if you have auto-checkin set. My vote in 117071 is to
simply get rid of this preference (with the further speculation that not
a single user has this turned on :-). So if there actually is someone
out there that actually uses this feature (and would care if we got rid
of it :-), please post a comment in 117017.

Cheers,
Geoff

On 6/4/2010 8:54 AM, Geoffrey Clemm wrote:

I see the same behavior as Jan, i.e., setting that property has no
effect that I've been able to discover (I'm using the most recent 3.0
milestone build). In particular, change sets are definitely not
automatically closed for me in any scenario I could come up with.

I've reported this issue in work item 117071.

Cheers,
Geoff

On 6/4/2010 7:08 AM, JanVdP wrote:
jlemieuxwrote:
It means that a new change set will get created and closed during
every check in. This simulates how other SCM systems work, where you
don't have the flexibility of having active change sets and
reorganizing your changes after check in.

In fact, this is the default mode of working in the SCM web
interface. The option in the Eclipse client was added 4 years ago,
but I've personally never used it. We thought it may help simplify
things for new users. If you have feedback on it, I'd love to hear
about it.

Jean-Michel

I understand your explanation, but I can't seem to get it to work on
my machine. For every check-in I do, I can still choose which change
set I want (existing or new) and I am able to move files between
them...

Does it work for you? Maybe I did something wrong, although
configuring it is child's play ;)

For folks following this thread, the conclusion reached in work item
117071 is that this option only works if you are working in a private
workspace and if you have auto-checkin set. My vote in 117071 is to
simply get rid of this preference (with the further speculation that not
a single user has this turned on :-). So if there actually is someone
out there that actually uses this feature (and would care if we got rid
of it :-), please post a comment in 117071.

Cheers,
Geoff


On 6/4/2010 8:54 AM, Geoffrey Clemm wrote:

I see the same behavior as Jan, i.e., setting that property has no
effect that I've been able to discover (I'm using the most recent 3.0
milestone build). In particular, change sets are definitely not
automatically closed for me in any scenario I could come up with.

I've reported this issue in work item 117071.

Cheers,
Geoff

On 6/4/2010 7:08 AM, JanVdP wrote:
jlemieuxwrote:
It means that a new change set will get created and closed during
every check in. This simulates how other SCM systems work, where you
don't have the flexibility of having active change sets and
reorganizing your changes after check in.

In fact, this is the default mode of working in the SCM web
interface. The option in the Eclipse client was added 4 years ago,
but I've personally never used it. We thought it may help simplify
things for new users. If you have feedback on it, I'd love to hear
about it.

Jean-Michel

I understand your explanation, but I can't seem to get it to work on
my machine. For every check-in I do, I can still choose which change
set I want (existing or new) and I am able to move files between
them...

Does it work for you? Maybe I did something wrong, although
configuring it is child's play ;)