scope definitions and dependency rules

Is the disconnect of scope definitions between the dependency rules and the Project View
intentional?

I can specify a scope from the project view to do dependency analysis on, but once I am
there, if I want to set up dependency rules, I have to set up the scopes all over again;
The ones I defined in the project view are not available.

Also, it would be really nice if there were settings panels for scope definitions and
dependency rules. This functionality seems hidden where it currently resides.

Tim

2 comments

Hello Tim,

Is the disconnect of scope definitions between the dependency rules
and the Project View intentional?


Project view shows all types of scopes.


I can specify a scope from the project view to do dependency analysis
on, but once I am there, if I want to set up dependency rules, I have
to set up the scopes all over again; The ones I defined in the project
view are not available.


The problem is that 'dependency scopes' are project wide (you can assign
profiles or specify illegal dependencies for project) while other scopes
are your own preferences. I think that mixing them all together is not a
very good idea.
If I provide a way to "save as other type scope" would it be a solution?

Also, it would be really nice if there were settings panels for scope
definitions and dependency rules. This functionality seems hidden
where it currently resides.


Indeed, we should make it more clear ...

Thank you.

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"


0

Hello Anna,

Anna Kozlova wrote:

Project view shows all types of scopes.


Yes it does. I had not yet created the dependency scopes in Demetra when I wrote the
message. However, that only confuses things further. I now have duplicate entries in the
project view that I cannot tell apart (and I don't think IDEA can either).

The problem is that 'dependency scopes' are project wide (you can assign
profiles or specify illegal dependencies for project) while other scopes
are your own preferences. I think that mixing them all together is not a
very good idea. If I provide a way to "save as other type scope" would
it be a solution?


I'm confused. The scope editor: "Edit Project Scopes" is identical regardless of which way
you get to it. You can always specify the module in the scope pattern or tree selector.
All scopes other than "Production" and "Tests" are my own preferences. So, what is the
difference?
Is the difference only where the configuration information is stored? If so, yes, being
able to save a scope as either project or personal would be a good solution as long as it is
made clear in the UI that only project scopes will be made available in the dependency
rules. I would also want to be able to move or copy a scope from one to the other.

> Indeed, we should make it more clear ...

I think that moving the scope and dependency rule definitions to configuration panels would
help to make it more clear since they would be either under "Project Settings", or "IDE
Settings".


Thanks,

Tim

0

Please sign in to leave a comment.