new definition of paths (#816)

I know there have been lots of postings on the new project structure, so
maybe my questions have already been answered sometime.

1) At the moment I can define contents with source and test paths, but
there is one global output path for each of these types (src/test). Is
it planned to have the output paths set per content?

2) Is it planned to have content definitions which are not being
compiled, e.g. for having sources for debugging purposes for classes
included via the classpath (not library definitions)?

3) In IDEA 3.0.x I can set the output path to any directory, even those
being ignored through "IDE settings -> ignore files and folders". In
aurora I cannot see those paths in the file choser. Is this a bug or an
intended change of behaviour?

Michael

8 comments
Comment actions Permalink

Michael Descher wrote:

I know there have been lots of postings on the new project structure, so
maybe my questions have already been answered sometime.

1) At the moment I can define contents with source and test paths, but
there is one global output path for each of these types (src/test). Is
it planned to have the output paths set per content?


What you see in "Main Module" tab is a configuration of one module. In the
near future you will be able to add more modules. For each module, it will
be possible to define an output path.


2) Is it planned to have content definitions which are not being
compiled, e.g. for having sources for debugging purposes for classes
included via the classpath (not library definitions)?


What you describe is called a library ;).

3) In IDEA 3.0.x I can set the output path to any directory, even those
being ignored through "IDE settings -> ignore files and folders". In
aurora I cannot see those paths in the file choser. Is this a bug or an
intended change of behaviour?


It is a bug - please file an SCR.

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

0
Comment actions Permalink

>>1) At the moment I can define contents with source and test paths, but
>>there is one global output path for each of these types (src/test). Is
>>it planned to have the output paths set per content?


What you see in "Main Module" tab is a configuration of one module. In the
near future you will be able to add more modules. For each module, it will
be possible to define an output path.


But what's the use of the different contents in a module then? I don't
see much difference between adding one content with several source paths
and multiple contents with one source path each for example.

Michael

0
Comment actions Permalink

"Michael Descher" <michael.descher@gmx.de> wrote in message
news:baqda7$s6a$1@is.intellij.net...

>>1) At the moment I can define contents with source and test paths, but
>>there is one global output path for each of these types (src/test). Is
>>it planned to have the output paths set per content?
>
>

What you see in "Main Module" tab is a configuration of one module. In

the

near future you will be able to add more modules. For each module, it

will

be possible to define an output path.

>

But what's the use of the different contents in a module then? I don't
see much difference between adding one content with several source paths
and multiple contents with one source path each for example.


Source path have to be (not strict and not direct) subdirectory of content.

--
Best regards,
Dmitry Peshehonov
JetBrains, Inc, http://www.intellij.com


0
Comment actions Permalink

i thought every content is a module. why have you several contens for one module? in which case can i use this?

0
Comment actions Permalink

Every module can have several contents paths for same reason as previous
projects can have several project paths. You may think of modules as old
projects, but there are several (to be implemented) modules per frame (still
one project per frame) and modules can depend on each other.

--
Best regards,
Dmitry Peshehonov
JetBrains, Inc, http://www.intellij.com

"Michael Seele" <mseele@guh-software.de> wrote in message
news:29596326.1053943121683.JavaMail.jrun@is.intellij.net...

i thought every content is a module. why have you several contens for one

module? in which case can i use this?


0
Comment actions Permalink

will it possible that you define a module that several project can use? i think on a tools/util package that includes classes that every java-project need(like Logger, a Debug-class...). you can define this package as module and include it into all the java projects you work...

0
Comment actions Permalink

Michael Seele wrote:

will it possible that you define a module that several project can use? i think on a tools/util package that includes classes that every java-project need(like Logger, a Debug-class...). you can define this package as module and include it into all the java projects you work...


A module is a part of the project that would be actively worked on.
Utility classes like you describe that are shared amongst multiple
projects should be a separate project themselves and supplied as a
library to each project that uses it.

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919

0
Comment actions Permalink

Michael Seele wrote:
> will it possible that you define a module that several project can use? i
> think on a tools/util package that includes classes that every
> java-project need(like Logger, a Debug-class...). you can define this
> package as module and include it into all the java projects you work...

From what I've understood of the discussion on modules, this is exactly the
sort of thing you would use them for.

Gordon Tyler wrote:

A module is a part of the project that would be actively worked on.
Utility classes like you describe that are shared amongst multiple projects

> should be a separate project themselves and supplied as a library to each
> project that uses it.

This is only true if the utilty classes are a fixed set. If they are being
evolved as projects proceed, libraries are not as convenient a way to manage
them as modules will be. The two main advantages of modules are that you
won't have to open a separate IDEA project in order to update the library
and that refactorings will be picked up across all the dependent modules.
For the way I work, both of these will be a big win.

Vil.
--
Vilya Harvey, Consultant
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/

Disclaimer

This e-mail and any attachments may be confidential and/or legally
privileged. If you have received this email and you are not a named
addressee, please inform the sender at Digital Steps Ltd by phone on
+44 (0)1483 469 480 or by reply email and then delete the email from
your system. If you are not a named addressee you must not use,
disclose, distribute, copy, print or rely on this email. Although
Digital Steps Ltd routinely screens for viruses, addressees should
check this email and any attachments for viruses. Digital Steps Ltd
makes no representation or warranty as to the absence of viruses in this
email or any attachments.

0

Please sign in to leave a comment.