>>>> * I'm OK with the Source folder at this point ... It's really a
>>>> Maven-only thing, but it needs to be there as a result, so we
>>>> have to suck that one up, I think (though technically it could
>>>> only appear if it's a Maven project)
>>> Is there any need to show it, if there is only one? Is this not
>>> also set at the project level for Maven projects?
>> Well, it's mostly true, though i suppose you could CONCEIVABLY have
>> test components that you only generate in dev and not in
>> deployment. I was willing to give in on this one just to not have
>> to think to hard about the alternative uses.
> I have two source folders, one for real source and one for unit
> tests. They have the same package structure which allows for
> "friendly" member access while keeping the code free of test
> clutter. That said, I rarely (never?) make test components. But as
> I have two source folders, I am willing to have to see a place to
> select the source folder. If I only have one folder, why do I need
> to select it? Or am I missing something here?
I agree, if you have a single source folder, it should at worst be
preselected, at best possibly just hide the UI.
ms
This archive was generated by hypermail 2.0.0 : Mon Feb 23 2009 - 15:09:17 EST