Disappearing source

So after opening a project in 5162, i see that the many of the project's
modules show no source files in the project explorer. In project properties,
under the module's path settings, the source path is still set correctly,
and I can even see the sub-folders under the source path, but from my project
view, there are no source files. In fact, when I re-opened my project, my
workspace still had a few source files opened that were in the disappearing
paths, and the editor icons for those files is now the little "j" with a
red circle around it, like a file that isn't part of my project.

Anyone find a way around this? I tried removing the source files from the
module definition, then re-adding them, but that didn't fix it.


3 comments

Hello Russ,

Indeed, we've changed meaning of exclude option in 5162. Previously exclude
folder (especially that exlude compile output folder) only exluded from the
module content where defined. Now excludes work globally meaning once defined
in a module it excludes from whatever module attached to the project.

Thus, please check out excluded folders defined in all of your modules.

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

So after opening a project in 5162, i see that the many of the
project's modules show no source files in the project explorer. In
project properties, under the module's path settings, the source path
is still set correctly, and I can even see the sub-folders under the
source path, but from my project view, there are no source files. In
fact, when I re-opened my project, my workspace still had a few source
files opened that were in the disappearing paths, and the editor icons
for those files is now the little "j" with a red circle around it,
like a file that isn't part of my project.

Anyone find a way around this? I tried removing the source files from
the module definition, then re-adding them, but that didn't fix it.



0

Yep, that was it. We'll see how it works. I was using those exclusions
because I've modules whose content roots were nested within other modules,
and I was using exclusions in the parent module to hide the child module's
files.

Looks ok so far: the parent module doesn't show the folders of the child
modules that are included in the same project.

Hello Maxim,

Hello Russ,

Indeed, we've changed meaning of exclude option in 5162. Previously
exclude folder (especially that exlude compile output folder) only
exluded from the module content where defined. Now excludes work
globally meaning once defined in a module it excludes from whatever
module attached to the project.

Thus, please check out excluded folders defined in all of your
modules.



0

Maxim Shafirov (JetBrains) wrote:

Indeed, we've changed meaning of exclude option in 5162. Previously
exclude folder (especially that exlude compile output folder) only
exluded from the module content where defined. Now excludes work
globally meaning once defined in a module it excludes from whatever
module attached to the project.

Thus, please check out excluded folders defined in all of your modules.


I fell into exactly the same trap. Project setup is very much like Russ described.
IMHO you should deal with such setups when loading an old project for the first
time (for the final Demetra).
It will clearly be perceived as a bug when old project setups do not work anymore.

On second thought it would be much nicer to have a setup that works with both
Irida and Demetra. Currently I am working on a project on my own, but before that
we had a team of five developers sharing a common project via svn. I was the only
one ever using an EAP version. That would be quite hard to do with this
project incompatibility.

0

Please sign in to leave a comment.