The point is this:

1. I've made a lot of changes in my workspace.
2. I want to check in a small subset of those changes, but certainly not
all of them.
3. There are many dependancies between the changed files.
4. The quickest way to figure out which files I _need_ to check in (at the
moment) would be to check in the ones I really want to check in, then check
them out in someone elses workspace and see what's missing when you try to
compile. This is (a) messy and (b) potentially disaterous, as you may
ultimately discover that there is an Nth-level deep dependancy to the
classes that you really didn't want to check in.

I want IDEA to tell me that if I check in a modified class or classes, what
other (modified) classes I will have to check in in order to make the
repository compile.
Thinking about it a bit, it could probably be implemented pretty easily by
using the Find Usages code iteratively through all modified files.

>From: "Michael Kirby" <[EMAIL PROTECTED]>
>Organization: Xerox Corporation
>To: [EMAIL PROTECTED]
>Date: Tue, 19 Mar 2002 06:36:51 -0500
>Subject: Re: [Eap-features] Inspect Change dependancies
>Reply-to: [EMAIL PROTECTED]
>Reply-To: [EMAIL PROTECTED]
>
>What would I use the information for?
>
>Mike
>
>
>On 19 Mar 2002 at 13:20, Graham Lea wrote:
>
>> It'd be really time-saving if there was some sort of inspection
>> utility where you could select a group of classes that have been
>> modified (according to CVS or MSS integration) and ask the question
>> "Do the modifications in these files rely on modifications made in any
>> other files in the project?"
>>
>> Example:
>> 1. I've changed Classes A, B and C.
>> 2. A has no relation to B or C whatsoever, but B calls a *new* method
>> on C. 3. I would like to check B in. 4. I want IntelliJ to tell me
>> what other changes I should check in with Class B, at least to make
>> the repository compile.
>>
>> Now, this sounds like a pretty huge task to me (most obviously the
>> decoding of CVS diffs to figure out what methods have been added or
>> removed!), so if it's too big a problem, don't even bother considering
>> it. It'd be nice if you could think of a way to do it that wouldn't
>> consume too much of your time, though. : )
>>
>> Graham Lea
>>
>> --
>> Software Engineer
>> Forge Research Pty Ltd
>> Suite 116, Bay 9, Locomotive Workshop
>> Australian Technology Park, Cornwallis Street
>> Eveleigh NSW 1430 Australia
>> Phone: +61 2 9209 4152   Fax: +61 2 9209 4172
>> www.forge.com.au
>>
>> ----------------------------------------------------------------------
>> This message contains privileged and confidential information intended
>> only for the use of the addressee named above.  If you are not the
>> intended recipient of this message you must not disseminate, copy or
>> take any action in reliance on it.  If you have received this message
>> in error please notify the sender immediately.  Any views expressed in
>> this message are those of the individual sender, except where the
>> sender specifically states them to be the views of another (including
>> a Body Corporate).
>> ----------------------------------------------------------------------

Graham Lea

--
Software Engineer
Forge Research Pty Ltd
Suite 116, Bay 9, Locomotive Workshop
Australian Technology Park, Cornwallis Street
Eveleigh NSW 1430 Australia
Phone: +61 2 9209 4152   Fax: +61 2 9209 4172
www.forge.com.au

----------------------------------------------------------------------
This message contains privileged and confidential information intended
only for the use of the addressee named above.  If you are not the
intended recipient of this message you must not disseminate, copy or
take any action in reliance on it.  If you have received this message
in error please notify the sender immediately.  Any views expressed in
this message are those of the individual sender, except where the
sender specifically states them to be the views of another (including
a Body Corporate).
----------------------------------------------------------------------


_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-features

Reply via email to