sverhagen wrote:
I just opened a new enhancement proposal to exclude in an aggregator
project its submodules.
http://jira.codehaus.org/browse/MNGECLIPSE-635
I'm entirely with Arnaud on this issue. But in JIRA I'm not getting the
"ooh, aah, that's great, let's build that"-vibe.
At the time issue been reported, few people showed some interest in
working on it, but I haven't heard back since then. Now issue gained few
votes and making its way to the top of the list of most voted issues, so
if no one contribute implementation soon, we may have to do it ourselves
in one of the next releases. But it would really help if we can get
better understanding what the expectations are.
So I'm wondering if there's
another way to work around this? What I do now is just close the aggregator
projects in Eclipse, but on the other hand I often like to edit their POM's
(in Eclipse, preferably) so I'd want them to be open. How are others doing
this? They must be having the same problems after importing all their
aggregator and module projects?
Can you please elaborate little more what problems exactly you have
with same folders shown more then once in Package Explorer? It seem like
more a cosmetic and perhaps a bit confusing issue. Is there any harm in
it? Can you please explain little more and maybe provide a sequence of
steps that would demonstrate erroneous behavior?
Igor, we can try to mark module folders as derived on project import
or update project configuration to address duplicated entries in the
search results and refactorings. What do you think?
Though I don't see how can we can hide those folders from the version
control provider that is not using models and as far as I know, only
Team/CVS provider support common navigator models.
Thanks
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
