Clearcase plugin poll

Hi Jacques

I sound all great. I love your plugin and this will make et even better.

One thing... It's very hard for me to use the check out when it check out
unreserved. Could you please change that for reserved or maybe even make an
option so you could choose if you want reserve/unreserved check out?

Just change NavtiveClearCase.java checkOut method:
public void checkOut(File file) {
String comment = "transparent checkout of " + file.getPath();
System.out.println(comment);
// checkStatus(Clearcase.checkout(file.getPath(), comment, false,
true));
checkStatus(Clearcase.checkout(file.getPath(), comment, true, true));
}

If you fix that I will send you a box of virtual beers :)

Thanks again
Michael Bertelsen
SPSS Inc.


"Jacques Morel" <jacmorel@yahoo.com> wrote in message
news:ammbqe$ou9$1@is.intellij.net...

I am considering having file moving&renaming immediately impact CC before
project check-in (right now everything except file check out is batched

for

the project check in). Obviously the target/source directories won't be
checked in until the project is checked in.
The reason is that I could not find an elegant solution to make
miscellaneous functions like history/diff work after a direct move/rename
that didn't go through CC.
If anybody has a comment or a better solution, now is the time.

>

Thanks

>

Jacques

>
>

I prefer 'unreserved' checkouts as opposed to reserved. Hence I would
request the choice to be optional.

"Bertel" <bertel@spss.com> wrote in message
news:amn7vl$skb$1@is.intellij.net...

Hi Jacques

>

I sound all great. I love your plugin and this will make et even better.

>

One thing... It's very hard for me to use the check out when it check out
unreserved. Could you please change that for reserved or maybe even make

an

option so you could choose if you want reserve/unreserved check out?

>

Just change NavtiveClearCase.java checkOut method:
public void checkOut(File file) {
String comment = "transparent checkout of " + file.getPath();
System.out.println(comment);
// checkStatus(Clearcase.checkout(file.getPath(), comment, false,
true));
checkStatus(Clearcase.checkout(file.getPath(), comment, true, true));
}

>

If you fix that I will send you a box of virtual beers :)

>

Thanks again
Michael Bertelsen
SPSS Inc.

>
>

"Jacques Morel" <jacmorel@yahoo.com> wrote in message
news:ammbqe$ou9$1@is.intellij.net...

I am considering having file moving&renaming immediately impact CC

before

project check-in (right now everything except file check out is batched

for

the project check in). Obviously the target/source directories won't be
checked in until the project is checked in.
The reason is that I could not find an elegant solution to make
miscellaneous functions like history/diff work after a direct

move/rename

that didn't go through CC.
If anybody has a comment or a better solution, now is the time.

>

Thanks

>

Jacques

>
>

>
>

Jacques,
Great plugin. Direct impact on CC will be good on rename/move.
"Jacques Morel" <jacmorel@yahoo.com> wrote in message
news:ammbqe$ou9$1@is.intellij.net...

I am considering having file moving&renaming immediately impact CC before
project check-in (right now everything except file check out is batched

for

the project check in). Obviously the target/source directories won't be
checked in until the project is checked in.
The reason is that I could not find an elegant solution to make
miscellaneous functions like history/diff work after a direct move/rename
that didn't go through CC.
If anybody has a comment or a better solution, now is the time.

>

Thanks

>

Jacques

>
>

Personally I'd rather have them be reserved, but I can see that an option
would probably be good. It's a shame that we don't have a similar interface
to the one that cleardlg presents for checkout and checkin - though I can
see that that might be quite a change to implement given how the plugin
batches stuff up.

Guy

"Arun Batchu" <arun_batchu@cnt.com> wrote in message
news:amnc20$3jt$1@is.intellij.net...

I prefer 'unreserved' checkouts as opposed to reserved. Hence I would
request the choice to be optional.

>

"Bertel" <bertel@spss.com> wrote in message
news:amn7vl$skb$1@is.intellij.net...

Hi Jacques

>

I sound all great. I love your plugin and this will make et even better.

>

One thing... It's very hard for me to use the check out when it check

out

unreserved. Could you please change that for reserved or maybe even make

an

option so you could choose if you want reserve/unreserved check out?

>

Just change NavtiveClearCase.java checkOut method:
public void checkOut(File file) {
String comment = "transparent checkout of " + file.getPath();
System.out.println(comment);
// checkStatus(Clearcase.checkout(file.getPath(), comment, false,
true));
checkStatus(Clearcase.checkout(file.getPath(), comment, true,

true));

}

>

If you fix that I will send you a box of virtual beers :)

>

Thanks again
Michael Bertelsen
SPSS Inc.

>
>

"Jacques Morel" <jacmorel@yahoo.com> wrote in message
news:ammbqe$ou9$1@is.intellij.net...

I am considering having file moving&renaming immediately impact CC

before

project check-in (right now everything except file check out is

batched

for

the project check in). Obviously the target/source directories won't

be

checked in until the project is checked in.
The reason is that I could not find an elegant solution to make
miscellaneous functions like history/diff work after a direct

move/rename

that didn't go through CC.
If anybody has a comment or a better solution, now is the time.

>

Thanks

>

Jacques

>
>

>
>

>
>