Thanks, this look great to me.
According your website, Pendora should be released today! Since you extended the EAP license up to november 15, I assume this has been delayed. If this is correct, when do you expect to release Pendora?
Thanks again,
Manuel Laflamme (an addicted IDEA user)
> -----Original Message-----
> From: Eugene Belyaev <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: RE: [Eap-list] Output path reset as IDEA start if it doesn't exist
> Date: Wed, 31 Oct 2001 23:10:46 +0300
> boundary="----_=_NextPart_001_01C16248.20ADE840"
> Reply-To: [EMAIL PROTECTED]
>
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
>
> ------_=_NextPart_001_01C16248.20ADE840
> Content-Type: text/plain
>
> We plan to provide this funtionality right after the Pandora release. All
> non-existent paths will be preserved but indicated with red in the UI.
>
> Best regards,
>
> Eugene Belyaev,
> IntelliJ Software, http://www.intellij.com <http://www.intellij.com/>
> "Develop with pleasure"
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On
> Behalf Of Manuel Laflamme
> Sent: Wednesday, October 31, 2001 23:01
> To: '[EMAIL PROTECTED]'
> Subject: [Eap-list] Output path reset as IDEA start if it doesn't exist
>
>
>
> If I delete a project output path (I often do that to cleanup my
> environment) and then launch IDEA, the output path is reset in my project...
> IDEA should rather create it (like JBuilder) or at least it should not reset
> it.
>
> My output path is two levels deep (/build/classes) and my whole build
> structure look like this (I use Ant to recreate it):
>
> /build
> /classes
> /release
> /tests
>
> So, if forget to run the Ant script before launching IDEA in a clean
> environment, I have to reenter the output path in my project... This is
> annoying when you do this several times in a day and that your project is
> read-only...
>
> Manuel
>
> P.S.: I posted a similar message in the feature list that took a totally
> different direction on code analysis. I realized this list seems to be more
> appropriate...
>
