And similar SVN issue appears with removed directory
              working_jdktools\modules\launcher

- it should be removed manually. SVN didn't removed it while updating
w/copy because some built files remain in the
launcher\src\main\native\launcher subdirectory. My CC installation
reports failure (head of the log is below).

-----Original Message-----
From: Neverov, Ilya V
Sent: Thursday, May 03, 2007 5:01 PM
To: Neverov, Ilya V
Subject: [build-test alert] HDK build FAILED windows-x86-32-debug

######## Build failed with the message:
  C:\bt2\H.1\checkouts\hdk\trunk\build-adaptor.xml:204: The following
error occurred while executing this line:
C:\bt2\H.1\checkouts\hdk\trunk\working_jdktools\build.xml:150: The
following error occurred while executing this line:
C:\bt2\H.1\checkouts\hdk\trunk\working_jdktools\make\build-java.xml:57:
The following error occurred while executing this line:
C:\bt2\H.1\checkouts\hdk\trunk\working_jdktools\make\properties.xml:319:
Invalid file: 
C:\bt2\H.1\checkouts\hdk\trunk\working_jdktools\modules\launcher\build.xml
########

Build date: 05/03/2007 16:43:17
. Apache Harmony Federated Build
           ==========================================
           svn rev          :  r534756
           operating system :  windows
           architecture     :  x86-32
           ant os name/arch :  Windows 2003/x86
           build mode       :  debug
           output location  :  target
           DRLVM classlib   :  ../../../working_classlib
.......

On 5/3/07, Vladimir Ivanov <[EMAIL PROTECTED]> wrote:
On 5/3/07, Tim Ellison <[EMAIL PROTECTED]> wrote:
[snip]
> Note that if you now update a workspace that had the launcher in LUNI
> already, and you didn't update to remove it, the fact that is has now
> come back will likely confuse SVN, and you will get an "object of the
> same name already exists" error.  You can just remove
> modules/luni/src/main/native/launcher/ and update again.

Yes, all my CC/CI systems were updated manually.
 thanks, Vladimir

>
> Regards,
> Tim
>


--
Thank you.
Ilya Neverov

Reply via email to