27 comments

Now we are changing the project structure. In new structure project will
consist of several modules. New modules will be much like current
projects (they will have sources, additional classpathes, ..., but will
live in same frame with their project).


Do you mean, every sub-project (== source path) has it's own frame? I hope
not, because this would definitely would clutter my screen.

Tom


On Mon, 12 May 2003 11:27:19 +0000 (UTC), Dmitry Peshehonov
<dyoma@intellij.com> wrote:

Now we are changing the project structure. In new structure project will
consist of several modules. New modules will be much like current
projects (they will have sources, additional classpathes, ..., but will
live in same frame with their project). New project structure will be
available in nearest Aurora build (but with simple module per project). I
thing your problem can be solved by creating a module for each plugin.
Also see request
http://www.intellij.net/tracker/idea/viewSCR?publicId=3132 I thing it
will help you to manage you code (after splitting it in several modules).
Any comments?
http://www.intellij.net/tracker/viewSCR?threadId=29244

>


0

>

Do you mean, every sub-project (== source path) has it's own frame? I hope
not, because this would definitely would clutter my screen.


Surely not. Still one frame per project.


--

Best regards,
Maxim Shafirov
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"



0

That's why I started this thread.

Tom


On Mon, 12 May 2003 11:53:43 +0000 (UTC), Michael Seele <mseele@guh-
software.de> wrote:

http://www.intellij.net/tracker/idea/viewSCR?publicId=12122
http://www.intellij.net/tracker/idea/viewSCR?publicId=3132

>


0

Does only modules might depend on other modules or does different *source
paths* have an dependency option, too?

Why I ask? Because I want to ensure, that -- for instance -- the source
path "xxx-test" should depend on source path "xxx", but "xxx" must not
depend on "xxx-test".

Tom


On Mon, 12 May 2003 15:41:07 +0400, Maxim Shafirov <max@intellij.net>
wrote:

>>
>> Do you mean, every sub-project (== source path) has it's own frame? I
>> hope
>> not, because this would definitely would clutter my screen.
>

Surely not. Still one frame per project.

>
>


0

Does only modules might depend on other modules or does different

*source

paths* have an dependency option, too?

Generally no. Only modules have dependencies between.

But

Why I ask? Because I want to ensure, that -- for instance -- the source
path "xxx-test" should depend on source path "xxx", but "xxx" must not
depend on "xxx-test".

There would be an option to setup separate specially marked "test source"
with implied dependencies you ask about.
>

Tom

>
>

On Mon, 12 May 2003 15:41:07 +0400, Maxim Shafirov <max@intellij.net>
wrote:

>

>>
>> Do you mean, every sub-project (== source path) has it's own frame? I
>> hope
>> not, because this would definitely would clutter my screen.
>

Surely not. Still one frame per project.

>
>

>
>


0

Generally no. Only modules have dependencies between.


... and modules always have it's own frame. That's a pitty, because when I
need dependencies, it means to have multiple frames. For example we have
three modules in SmartCVS: the JavaCVS module, an application-independend
part and an SmartCVS-specific part; each with it's own unit tests. This
would mean at least 3 frames :(

Tom

0

Well, once again, modules do not have their own frames. Projects do have
instead. And each project consists of several modules with dependencies
defined between them.

--

Best regards,
Maxim Shafirov
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"


"Thomas Singer" <thomas.singer@noregnisspam.de> wrote in message
news:opro17uojwmxlxr0@news.intellij.net...

Generally no. Only modules have dependencies between.

>

... and modules always have it's own frame. That's a pitty, because when I
need dependencies, it means to have multiple frames. For example we have
three modules in SmartCVS: the JavaCVS module, an application-independend
part and an SmartCVS-specific part; each with it's own unit tests. This
would mean at least 3 frames :(

>

Tom



0

Thomas Singer wrote:

>> Generally no. Only modules have dependencies between.


... and modules always have it's own frame. That's a pitty, because when I
need dependencies, it means to have multiple frames. For example we have
three modules in SmartCVS: the JavaCVS module, an application-independend
part and an SmartCVS-specific part; each with it's own unit tests. This
would mean at least 3 frames :(

Tom


Thomas,
as Maxim has already replied in this thread, we will still have one frame
per project system - that is, all modules in project will share a frame.

Dmitry

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

0

Well, in this case, it's fine. Sorry, if I misunderstood something.

Should modules be shown like different source paths now? Is it possible to
simply replace different source paths with different modules (that have
different source paths)?

Tom

0

Thomas,

stay tuned for the next build :) You'll see (almost) all of it with your own
eyes :). We'll also post a brief description here.

Friendly,
Dmitry


Thomas Singer wrote:

Well, in this case, it's fine. Sorry, if I misunderstood something.

Should modules be shown like different source paths now? Is it possible to
simply replace different source paths with different modules (that have
different source paths)?

Tom


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

0

I'm really exited to see a >= 814 build. Looks like it will be a complete
new IDEA under the hood. Maybe changing the build number to 900 would be
useful -- forget it, just day-dreaming :)

Tom

0

I'm also really exited to see the next eap build!!! can you tell us, how long you need to provide the next eap-build? can't wait to work with it! :)

0

I guess, instead of having one classpath table for the whole project, each
module will have one, isn't it?

Tom

0

Yes, you are right. Any module will have it's own "classpath" consisted of libraries (we've unified "just jar/director" and set of jars/directories early named "library"), JDK, module source (classes compiled from your source) and (new) other modules (which this one depends on).

0

On Mon, 12 May 2003 14:33:50 +0200, Thomas Singer wrote:

three modules in SmartCVS: the JavaCVS module, an application-independend


SmartCVS! I knew I knew you're name from somewhere ;)

--
...turn to the light - don't be frightened by the shadows it creates,
...turn to the light - turning away could be a terrible mistake
...dream theater - the great debate


0

On Mon, 12 May 2003 16:47:56 +0400, Dmitry Lomov wrote:

stay tuned for the next build :) You'll see (almost) all of it with your
own eyes :). We'll also post a brief description here.


Awee man now I'm getting realllllly eager to see this new EAP build ;)
So much goodness sounds like its coming. Can't wait ;)

--
...turn to the light - don't be frightened by the shadows it creates,
...turn to the light - turning away could be a terrible mistake
...dream theater - the great debate


0

On Mon, 12 May 2003 17:30:18 +0000, Dmitry Peshehonov wrote:

Yes, you are right. Any module will have it's own "classpath" consisted of
libraries (we've unified "just jar/director" and set of jars/directories
early named "library"), JDK, module source (classes compiled from your
source) and (new) other modules (which this one depends on).


Are project level libraries available yet?

--
...turn to the light - don't be frightened by the shadows it creates,
...turn to the light - turning away could be a terrible mistake
...dream theater - the great debate


0

Are you going to allow plugins to register properties on a Module basis? Right now we have properties at the IDE level and project level. For some plugin that deal with what I will call "code convention" for the lack of better term, it might be good to have specific settings for each module. Examples:

  • Different VCS or the abscence of.

  • Different testing organization (JUnitTestPlugin)

  • Different workspaces (WorkspacePlugin)

  • Different Webapp server

...

Jacques

0

Jacques Morel wrote:

Are you going to allow plugins to register properties on a Module basis?
Right now we have properties at the IDE level and project level. For some
plugin that deal with what I will call "code convention" for the lack of
better term, it might be good to have specific settings for each module.
Examples:
...


Yes, there is such a thing as module component. As soon as things
stabilize enough, it will become OpenAPI.

Friendly,
Dmitry

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

0

Yes, you are right. Any module will have it's own "classpath" consisted

of

libraries (we've unified "just jar/director" and set of jars/directories
early named "library"), JDK, module source (classes compiled from your
source) and (new) other modules (which this one depends on).

>

Are project level libraries available yet?

>
Yes, there are module level libraries (module classpath) and project
libraries which can be shared between modules in project.

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


0

On Tue, 13 May 2003 18:30:24 +0400, Dmitry Peshehonov wrote:

Yes, there are module level libraries (module classpath) and project
libraries which can be shared between modules in project.


Cool - one thing I was just thinking in the shower as well, is the
multiple projects interface implemented with multiple, separate .ipr's for
each sub project ( which could be opened and worked on individually ) or
one giant .ipr?
--
...turn to the light - don't be frightened by the shadows it creates,
...turn to the light - turning away could be a terrible mistake
...dream theater - the great debate


0


"Mark Derricutt" <pinhead@satinism.org> wrote in message

Cool - one thing I was just thinking in the shower as well


What was the other thing? ;)

is the
multiple projects interface implemented with multiple, separate .ipr's for
each sub project ( which could be opened and worked on individually ) or
one giant .ipr?


What if we have, say, I big project which deals with subprojects, so some
team members need to compile and run only the portion, pertaining to them,
and, say, team leader or "build master" may need to build all subprojects
separately or the project as one big piece? How this kind of stuff will be
handled? And do not forget about protection of team codebase from other
teams :)

Michael Jouravlev.


0


>>Are project level libraries available yet?
>>


Yes, there are module level libraries (module classpath) and project
libraries which can be shared between modules in project.


Does this mean that the location of module/library definitions can be
located such that they can be stored in CM, controlled, and shared
across developers (not just projects)? (ie, vs the current library
definitions which live in the user settings location.)

0

Libraries defined on module level are stored in module file (.iml).
Libraries on project level are stored in project file (.ipr). So both can be
kept in version control. Libraries on defined globally (that is, for all
projects) will be stored somewhere in '/options' (which is not intended to be kept in version control). -- Valentin Kipiatkov JetBrains, Inc http://www.intellij.com "Develop with pleasure!" "Barry Kaplan" wrote in message news:b9tdfl$9bv$1@is.intellij.net... >]]>

>>Are project level libraries available yet?
>>
>

Yes, there are module level libraries (module classpath) and project
libraries which can be shared between modules in project.

>

Does this mean that the location of module/library definitions can be
located such that they can be stored in CM, controlled, and shared
across developers (not just projects)? (ie, vs the current library
definitions which live in the user settings location.)

>


0

Please sign in to leave a comment.