Airtight projects

I would if you would consider optionally allowing slightly less
airtightness between projects.

Let us as that Project B uses classes from Project A.

When you compile in Project B, either out of date project A classes
get automatically recompiled, or you get warned you are using out of
date classes from project A.

I don't know how many hours I have wasted because I was unwittingly
using out of date code.



--
Roedy Green Canadian Mind Products
http://mindprod.com
Computers are useless. They can only give you answers.
~ Pablo Picasso (born: 1881-10-25 died: 1973-04-08 at age: 91)

5 comments
Comment actions Permalink

Hello Roedy,

Why don't you use modules in this case?

I would if you would consider optionally allowing slightly less
airtightness between projects.

Let us as that Project B uses classes from Project A.

When you compile in Project B, either out of date project A classes
get automatically recompiled, or you get warned you are using out of
date classes from project A.

I don't know how many hours I have wasted because I was unwittingly
using out of date code.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

On Thu, 28 Jan 2010 12:42:23 +0000 (UTC), Dmitry Jemerov
<yole@jetbrains.com> wrote, quoted or indirectly quoted someone who
said :

>
>Why don't you use modules in this case?

There is a project for code that will work with each JDK 1.1 .. 1.6

Since my code is opensource, and distributed as about 100 different
bundlings,  I like to keep each package limited to as old as possible
a JDK.
--
Roedy Green Canadian Mind Products
http://mindprod.com
Computers are useless. They can only give you answers.
~ Pablo Picasso (born: 1881-10-25 died: 1973-04-08 at age: 91)

0
Comment actions Permalink

Hello Roedy,

>> Why don't you use modules in this case?
>>

There is a project for code that will work with each JDK 1.1 .. 1.6

Since my code is opensource, and distributed as about 100 different
bundlings,  I like to keep each package limited to as old as possible
a JDK.


So how exactly does this preclude you from using modules? You can set a different
JDK for each module.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

On Wed, 3 Feb 2010 10:25:54 +0000 (UTC), Dmitry Jemerov
<yole@jetbrains.com> wrote, quoted or indirectly quoted someone who
said :

>So how exactly does this preclude you from using modules? You can set a different
>JDK for each module.

I was under the delusion a project had to be the same target.
reorganising should solve my problem. Thanks.
--
Roedy Green Canadian Mind Products
http://mindprod.com

Every compilable program in a sense works. The problem is with your unrealistic expections on what it will do.

0
Comment actions Permalink

On Wed, 3 Feb 2010 10:25:54 +0000 (UTC), Dmitry Jemerov
<yole@jetbrains.com> wrote, quoted or indirectly quoted someone who
said :

>So how exactly does this preclude you from using modules? You can set a different
>JDK for each module.

I was under the delusion a project had to be the same target.
reorganising should solve my problem. Thanks.
--
Roedy Green Canadian Mind Products
http://mindprod.com

Every compilable program in a sense works. The problem is with your unrealistic expections on what it will do.

0

Please sign in to leave a comment.