Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

SCM problem removing bin from ignore list

Using RTC 2.0.0.2

One of my components is a toolkit that contains (among other things)
programs inside a top-level 'bin' directory.

When I first shared this project with Jazz, I noticed that the 'bin'
directory got ignored (that's default behavior I believe).

So, I right-licked on 'bin' in the project explorer and chose
Team->Jazz->Remove from ignore list.

That caused a new .jazzignore to show up in the PC view along with the
bin directory and all its contents.

Now, when I checkin those changes, the .jazzignore gets checked in, but
the bin directory and its contents don't make it into the workspace.

Back, in Eclipse project explorer, the directory is again showing the
'unshared' icon. I can do this repeatedly, with the same results.


I have found a workaround (sort of)

1) Right-click on bin and choose 'remove from ignore list' again
2) Checkin the bin contents but not the .jazzignore
3) Undo the .jazzignore

For me, that allowed me to get the bin directory and its contents into
my workspace.

What am I doing wrong ?

Cheers
Dave

1 vote



5 answers

Permanent link
By default, the 'bin' directory is marked as derived by eclipse. Jazz doesn't commit derived resources. At the same time, there is a default ignore rule that prevents 'bin' from being included.

When you removed 'bin' from the ignore list, you removed the rule, but didn't change the derived status. Even though the ignore list changed, we still didn't check it in.

If you open the eclipse properties on the 'bin' directory, you can remove the derived bit, which will allow RTC to check it in. Note that there's a hole in the eclipse event story preventing us from discovering that the derived bit changed, so you may need to ignore it and unignore it get RTC to notice that it should be checked in.

I wouldn't recommend committing the bin directory - I don't believe that the derived bit is managed in a way that allows RTC to share its state. Every eclipse user will have to manually change that flag before committing stuff in there. Perhaps you could create another directory and copy the binary resources into that?

e

2 votes

Comments

This works. Thanks.
I had to not only remove the "derived option" from the "bin" folder but also the sub-folders under bin and also the classes I was building.


Permanent link
Using RTC 2.0.0.2

One of my components is a toolkit that contains (among other things)
programs inside a top-level 'bin' directory.

When I first shared this project with Jazz, I noticed that the 'bin'
directory got ignored (that's default behavior I believe).

So, I right-licked on 'bin' in the project explorer and chose
Team->Jazz->Remove from ignore list.

That caused a new .jazzignore to show up in the PC view along with the
bin directory and all its contents.

Now, when I checkin those changes, the .jazzignore gets checked in, but
the bin directory and its contents don't make it into the workspace.

Back, in Eclipse project explorer, the directory is again showing the
'unshared' icon. I can do this repeatedly, with the same results.


I have found a workaround (sort of)

1) Right-click on bin and choose 'remove from ignore list' again
2) Checkin the bin contents but not the .jazzignore
3) Undo the .jazzignore

For me, that allowed me to get the bin directory and its contents into
my workspace.

What am I doing wrong ?

Cheers
Dave


I'm not sure what is wrong here. Your steps appear to be correct. If the .jazzignore file is still in a change set, the bin directory should not be ignored. When the .jazzignore file is checked in and the bin directory is not, what are the changes to the .jazzignore file? Check that it does not list the bin directory.

Maybe this is a bug but I've never seen this before.

0 votes


Permanent link
Below is my .jazzignore file as generated by RTC. The component already
has one of these (checked in). Another (identical) .jazzignore appears
in the unresolved folder after my Step 1 below.

Should I open a defect ?


### Jazz Ignore 0
# Default value for core.ignore.recursive is *.class
# Changing this value changes check-in behaviour for the entire project.
#
# Default value for core.ignore is bin
# Changing this value changes check-in behaviour for the local directory.
#
# Ignore properties should contain a space separated list of filename
patterns.
# Each pattern is case sensitive and surrounded by braces ('{' and '}').
# "*" matches zero or more characters, and "?" matches single characters.
#
# e.g: {*.sh} {\.*} ignores shell scripts and hidden files

# NOTE: modifying ignore files will not change the ignore status of derived
# resources.

core.ignore.recursive= \
{*.class}

core.ignore=




On 1/8/2010 10:53 AM, tmok wrote:
David Wardwrote:
Using RTC 2.0.0.2

One of my components is a toolkit that contains (among other things)

programs inside a top-level 'bin' directory.

When I first shared this project with Jazz, I noticed that the 'bin'

directory got ignored (that's default behavior I believe).

So, I right-licked on 'bin' in the project explorer and chose
Team->Jazz->Remove from ignore list.

That caused a new .jazzignore to show up in the PC view along with
the
bin directory and all its contents.

Now, when I checkin those changes, the .jazzignore gets checked in,
but
the bin directory and its contents don't make it into the
workspace.

Back, in Eclipse project explorer, the directory is again showing
the
'unshared' icon. I can do this repeatedly, with the same results.


I have found a workaround (sort of)

1) Right-click on bin and choose 'remove from ignore list' again
2) Checkin the bin contents but not the .jazzignore
3) Undo the .jazzignore

For me, that allowed me to get the bin directory and its contents
into
my workspace.

What am I doing wrong ?

Cheers
Dave

I'm not sure what is wrong here. Your steps appear to be correct. If
the .jazzignore file is still in a change set, the bin directory
should not be ignored. When the .jazzignore file is checked in and
the bin directory is not, what are the changes to the .jazzignore
file? Check that it does not list the bin directory.

Maybe this is a bug but I've never seen this before.

0 votes


Permanent link
Yes, I think a defect should be opened.

Can you also post in the defect the .jazzignore file before the bin directory was removed from the ignore list?

0 votes


Permanent link
Using RTC 2.0.0.2
Now, when I checkin those changes, the .jazzignore gets checked in, but
the bin directory and its contents don't make it into the workspace.


Similar problems with the CLI. Changes made to the .jazzignore file seem to be ignored due to daemon caching.

CLI commands using scm immediately reflect .jazzignore modifications, but lscm may not. Stopping the lscm daemon is one way to pick up the .jazzignore changes in the next invocation of lscm.

To show scm cache entries for eclipse and the CLI, type
scm list daemon 

Maybe it's possible to solve the eclipse problem using the method I described for the CLI.

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Jan 07 '10, 4:53 p.m.

Question was seen: 14,996 times

Last updated: Mar 01 '15, 2:06 p.m.

Confirmation Cancel Confirm