"About To Delete Source Files" ???

Upon installing 1113, I went to compile, and I guess it wants to do a rebuild.

Then it asks me this:

About To Delete Source Files
Rebuild is about to clear output directories.
Files from the following source directories will be deleted:
C:\path_to_my_src
Would you like to continue compilation without clearing output directories?

Yes|No

i'm scared
My output directory == my source directory.

Is this really going to delete my source files (as it says in the title) if I click Yes or No? The question is kind of ambiguous, and I don't know whether to press Yes or No. Basically, I don't want my source files deleted at all. That would seem silly.

So, will this only delete my *.class files? And which option should I choose??

Ian.

16 comments
Comment actions Permalink

Ian Zabel wrote:

Upon installing 1113, I went to compile, and I guess it wants to do a rebuild.

Then it asks me this:

About To Delete Source Files
Rebuild is about to clear output directories.
Files from the following source directories will be deleted:
C:\path_to_my_src
Would you like to continue compilation without clearing output directories?

Yes|No

i'm scared
My output directory == my source directory.

Is this really going to delete my source files (as it says in the title) if I click Yes or No? The question is kind of ambiguous, and I don't know whether to press Yes or No. Basically, I don't want my source files deleted at all. That would seem silly.

So, will this only delete my *.class files? And which option should I choose??


You should choose to NOT compile in your SOURCE directory dude!

You're lucky JetBrains added that!

R

0
Comment actions Permalink

"Robert S. Sfeir" <robert@codepuccino.com> wrote in message
news:buhoes$q2o$1@is.intellij.net...

Ian Zabel wrote:

Upon installing 1113, I went to compile, and I guess it wants to do a

rebuild.

>

Then it asks me this:

>

About To Delete Source Files
Rebuild is about to clear output directories.
Files from the following source directories will be deleted:
C:\path_to_my_src
Would you like to continue compilation without clearing output

directories?

>

Yes|No

>

i'm scared
My output directory == my source directory.

>

Is this really going to delete my source files (as it says in the title)

if I click Yes or No? The question is kind of ambiguous, and I don't know
whether to press Yes or No. Basically, I don't want my source files deleted
at all. That would seem silly.

>

So, will this only delete my *.class files? And which option should I

choose??
>

You should choose to NOT compile in your SOURCE directory dude!

>

You're lucky JetBrains added that!


Well, they do not have to delete .java files anyway. Do they delete them?


0
Comment actions Permalink

Michael Jouravlev wrote:

"Robert S. Sfeir" <robert@codepuccino.com> wrote in message
news:buhoes$q2o$1@is.intellij.net...

>>Ian Zabel wrote:
>>
>>>Upon installing 1113, I went to compile, and I guess it wants to do a


rebuild.

>>>Then it asks me this:
>>>
>>>About To Delete Source Files
>>>Rebuild is about to clear output directories.
>>>Files from the following source directories will be deleted:
>>>C:\path_to_my_src
>>>Would you like to continue compilation without clearing output


directories?

>>>Yes|No
>>>
>>>i'm scared
>>>My output directory == my source directory.
>>>
>>>Is this really going to delete my source files (as it says in the title)


if I click Yes or No? The question is kind of ambiguous, and I don't know
whether to press Yes or No. Basically, I don't want my source files deleted
at all. That would seem silly.

>>>So, will this only delete my *.class files? And which option should I


choose??

>>You should choose to NOT compile in your SOURCE directory dude!
>>
>>You're lucky JetBrains added that!


Well, they do not have to delete .java files anyway. Do they delete them?


This is the Clear output dir on compile, he's got it checked off, it's
warning him. He should have it checked on in his case. And yes
clearing output path means clearing output path.

R

0
Comment actions Permalink

This is the Clear output dir on compile, he's got it checked off, it's
warning him. He should have it checked on in his case. And yes
clearing output path means clearing output path.


It's late... reverse that. It's on it should be off.

R

0
Comment actions Permalink

On Mon, 19 Jan 2004 22:06:08 +0000, Ian Zabel wrote:

i'm scared
My output directory == my source directory.


I'm scared you use your source directory as your output directory in the
first place.

0
Comment actions Permalink

Mark Derricutt wrote:

I'm scared you use your source directory as your output directory in the
first place.


Regardless of his choice of source and build directory structures -
surely the IDE should be flexable enough to accomodate?

I used to use this same format before I came to use IDEA, and (if using
CVS for source safing) then I dont see any problem with that choice at
all. Sure its messy, but its a matter of taste.

0
Comment actions Permalink


There are so many good reasons not to have your source and output in the same place that it's really hard to justify special support for it in the tool. Frankly, he's lucky IDEA gave him a warning.

--Dave

0
Comment actions Permalink

On Tue, 20 Jan 2004 14:53:47 +0000, Dave Griffith wrote:

There are so many good reasons not to have your source and output
in the same place that it's really hard to justify special support for
it in the tool. Frankly, he's lucky IDEA gave him a warning.


While I agree that it's asking for trouble to do this, didn't IDEA 3.x
offer "compile to source" as an option (perhaps even as the default?).
If so then it seems a little harsh not to cater for the situation in a
more user-friendly fashion in 4.0.

--
Mark Scott

0
Comment actions Permalink

Hey, there even IS special support for that: disable the 'Clear output dir on compile' option and everything works.

0
Comment actions Permalink

On 2004/01/20 15:53, Dave Griffith wrote:

There are so many good reasons not to have your source and
output in the same place that it's really hard to justify special
support for it in the tool. Frankly, he's lucky IDEA gave him a
warning.


Is there a web page or something somewhere describing these reasons? A
sort of best practices document maybe? I need as much information as I
can get to convert a particularly stubborn co-worker:-(

Bas

0
Comment actions Permalink

Yeah, what's the big deal? It's just how we've always done it at my company, and it's worked fine.

What are some good reasons to not compile to sources?

A good reason TO compile to sources is that IDEA doesn't copy over my .properties if I compile elsewhere, and none of my translations get updated in Tomcat. I understand that using a web module, you can copy to an exploded dir, but that takes FOREVER every time I compile. (especially since I start two debuggers in my project, it copies everything twice).

0
Comment actions Permalink

BTW, I clicked on Yes, and it didn't delete my source files.

0
Comment actions Permalink

A good reason TO compile to sources is that IDEA
doesn't copy over my .properties if I compile
elsewhere...


Oh yes, it does! (At least for me...)

...and none of my translations get updated in
Tomcat. I understand that using a web module, you can
copy to an exploded dir, but that takes FOREVER every
time I compile. (especially since I start two
debuggers in my project, it copies everything
twice).


The nice thing about using web modules is that in most cases you don't have to stop the debugger. Just make the project and everything is ready to continue.

It's true that the make process takes more time, but without having to restart tomcat over and over again I get much lesser turnaround times.

0
Comment actions Permalink


"Ian Zabel" <ian@ezabel.com> wrote in message
news:3441598.1074615967181.JavaMail.itn@is.intellij.net...

Yeah, what's the big deal? It's just how we've always done it at my

company, and it's worked fine.
>

What are some good reasons to not compile to sources?

>

A good reason TO compile to sources is that IDEA doesn't copy over my

.properties if I compile elsewhere

Your properties are THAT large? Someone out there is very lucky ;)

and none of my translations get updated in Tomcat.


???

I understand that using a web module, you can copy to an exploded dir


You can just compile to an exploded dir, that is what we were doing for
our last Weblogic project and it worked quite nicely.



0
Comment actions Permalink

Ok I so, if compiling to a directory copies over .properties files, then I'm good to go. I'll try it out soon.

0
Comment actions Permalink


Can't think of any resources off the top of my head, just years of finding issues with it. Here's a few:

1)It complicates jar creation, and makes war/ear creation a nightmare.

2)It complicates source control usage.

3)It complicates grep usage.

4)If your IDE is smart enough to do file synchronization, it may complicate that.

5)I turns the first time you do a "clean" build into an exercise in faith.

6)If your project directory is on a shared drive, you'll have better performance if your output directory is local.

Note that many of these arguments imply that your outputs shouldn't be anywhere in your project directory, not just into your source tree. I do that on larger projects, and it's always been worth the extra effort.

0

Please sign in to leave a comment.