Multi-module projects

I've tried some searching on the forums and in the tracker, but I can't
find a recent status on having a project with multiple output paths.
From what I gather, this is supposed to be effected via multiple modules
in a single project.

Is there any status update or guess as to when we'll see that? Barring
that, is there a work-around that I'm too blind to see? It's kind of
preventing me from using Aurora on my work project right now.


~Mike

7 comments
Comment actions Permalink

Use Ant to build your project. You can have as many output paths as you want.

Regards, Stefan Freyr.

0
Comment actions Permalink

Concerning multiple output paths, why are test sources treated as a special case of the multiple output paths feature? It seems a little inconsistent and adds complexity to the project settings.

0
Comment actions Permalink

I thought of this, but it makes for difficulty in debugging. I guess I
would just have to add the "real" output paths to my project's
classpath, but that seems like such a kludge. Also, I'm not 100% sure it
would work.

I'll give it a shot, I guess. Anyway, is there any update on when we'll
have multi-module projects?


~Mike


Stefan Freyr Stefansson <stefan_freyr_stefansson@hotmail.com> wrote in
news:25167880.1054729715122.JavaMail.jrun@is.intellij.net:

Use Ant to build your project. You can have as many output paths as
you want.

Regards, Stefan Freyr.

0
Comment actions Permalink

In article <2083637.1054730173217.JavaMail.jrun@is.intellij.net>,
russegan@email.com says...

Concerning multiple output paths, why are test sources treated as a special case of the multiple output paths feature? It seems a little inconsistent and adds complexity to the project settings.


Isolating the test classes ensures that (1) they don't end up in your
jarfile when you build it from your "normal" output directory, and, (2)
they don't end up in your classpath when you run the program normally,
which ensures that your runtime code doesn't have any unintended
dependency on your test code.

- Danny

0
Comment actions Permalink

>Isolating the test classes ensures that (1) they don't end up in your
>jarfile when you build it from your "normal" output directory, and, (2)
>they don't end up in your classpath when you run the program normally,
>which ensures that your runtime code doesn't have any unintended
>dependency on your test code.

Well, isn't this possible with multiple modules (when they become
available)?

Tom


On Wed, 4 Jun 2003 10:10:33 -0700, Daniel Burkes <i@dont.want.spam>
wrote:

>In article <2083637.1054730173217.JavaMail.jrun@is.intellij.net>,
>russegan@email.com says...
>> Concerning multiple output paths, why are test sources treated as a special case of the multiple output paths feature? It seems a little inconsistent and adds complexity to the project settings.
>>
>
>Isolating the test classes ensures that (1) they don't end up in your
>jarfile when you build it from your "normal" output directory, and, (2)
>they don't end up in your classpath when you run the program normally,
>which ensures that your runtime code doesn't have any unintended
>dependency on your test code.
>
>- Danny

0
Comment actions Permalink

In article <ffrtdvcpisk1rmfkv4sqrondjpc9kmpo1k@4ax.com>,
thomas.singer@NOregnisSPAM.de says...

>Isolating the test classes ensures that (1) they don't end up in your
>jarfile when you build it from your "normal" output directory, and, (2)
>they don't end up in your classpath when you run the program normally,
>which ensures that your runtime code doesn't have any unintended
>dependency on your test code.

Well, isn't this possible with multiple modules (when they become
available)?


Sure, it sounds like it would be. Perhaps it's just a matter of
convenience to not have to create a separate module for your test
classes?

- Danny

0
Comment actions Permalink

Daniel Burkes wrote:

In article <ffrtdvcpisk1rmfkv4sqrondjpc9kmpo1k@4ax.com>,
thomas.singer@NOregnisSPAM.de says...

>> >Isolating the test classes ensures that (1) they don't end up in your
>> >jarfile when you build it from your "normal" output directory, and, (2)
>> >they don't end up in your classpath when you run the program normally,
>> >which ensures that your runtime code doesn't have any unintended
>> >dependency on your test code.
>>
>> Well, isn't this possible with multiple modules (when they become
>> available)?
>>


Sure, it sounds like it would be. Perhaps it's just a matter of
convenience to not have to create a separate module for your test
classes?

- Danny


Yes indeed. Seprationg a source and a test source is just a matter
convenience.

Cheers,
Dmitry

--
Dmitry Lomov
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0

Please sign in to leave a comment.