Re: JUnit module projectization

Tomas Zezula wrote:
> No, this is not allowed behaviour,
> according to the UI spec all the Java sources MUST be mixed under the 
> Packages node.

I'm wondering, is there any way to change the UI spec. IMHO the spec is 
completely wrong on forcing all sources (no matter what they are 
supposed to be for) to live under one node - this will lead just to 
confusion and on bigger projects to unmaintainable mess. Can be issue 
filed against UI spec or anything like that, because I cannot imagine 
JUnit module to work reliably and in an user friendly way without this 
possibility.

B.

>  From API point of view,  it is nearly possible, multiple CU and 
> multiple BT are supported by Java module,
> but the problem will be in Packages node because of the fact, that it 
> HAS to show all
> the Java sources in the project.
> Tomas
> 
> Martin Brehovsky wrote:
> 
>> Hi,
>>
>> I'm working on projectization of JUnit module (I'm not working on 
>> code, but I'm just looking at a possible ways how to 'projectize' the 
>> JUnit module, so the workflow is somewhat similar to non-projectized 
>> version, but still it compatible with the projectized ide).
>>
>> Currently JUnit module utilizes filesystems concept in such way, that 
>> you have sources in one directory mounted as a filesystem to 
>> repository and tests in a different directory again mounted to 
>> repository. The concept of two separate filesystems allows users to 
>> keep their tests separated from tested code, but still the tests can 
>> be in the same package as the tested code, so they can test package 
>> private methods of the code. I believe this functionality is 
>> appreciated by JUnit users, so I'm wondering how this could be 
>> transferred to projectized IDE.
>>
>> I was thinking about the following way (but I don't know if this is 
>> possible). Currently there is Sources node with Packages subnode. 
>> Ideally I would like to see something like 'Unit Tests' or just 
>> 'Tests' node on the same level as Packages node is. Tests subnode 
>> could then contain just tests. The UI could look something like this:
>>
>> Projects
>> |- MyProject (active)
>>    |- Sources
>>       |- Packages
>>          |- my.package
>>             |- HelloWorld
>>       |- Tests
>>          |- my.package
>>             |- HelloWorldTest
>>
>>
>>
>> Needless to say, I would like to differentiate between building 
>> application and building tests (tests should depend on application, 
>> but when making a production build, they should not be included in the 
>> output).
>>
>> Do you think this is possible with current projects?
>>
>> Thanks,
>> B.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>