Re: Building on Windows

Hi Patricia, I had sometimes curious build breaks because of parallelism and virus scan. So please try to make a build without any parallelism and disable virus scan. Additional benefit: without parallelism, the log tells you the actual module order. Kind regards Regina Patricia Shanahan

Re: Query on C++ UCB XInteractionHandler interface - is it possible to have/write a non-UI-based interface to respond on?

On 02/02/2016 09:56 PM, John Dougrez-Lewis wrote: I'm looking at coding a pet C++ project to use the Content Brokers provided by the UCB/UNO subsystem. I note that the XInteractionHandler-derived classes can be used to handle responses to supply e.g. user/pswd details for Authentication etc.

Re: Building on Windows

On Thu, Feb 4, 2016 at 11:47 PM, Patricia Shanahan wrote: > On 2/4/2016 12:40 PM, Regina Henschel wrote: > >> Hi Patricia, >> >> Patricia Shanahan schrieb: >> >>> I think maybe I need to clean up and start again. What is the best way >>> to clean, short of doing a fresh checkout?

Re: Building on Windows

On 2/4/2016 12:40 PM, Regina Henschel wrote: Hi Patricia, Patricia Shanahan schrieb: I think maybe I need to clean up and start again. What is the best way to clean, short of doing a fresh checkout? I remove the output-tree manually Starting in main: find . -maxdepth 2 -name "wntmsci12*" |

Re: netbeans-integration Japanese language update

On 02/04/2016 01:23 PM, Yu Tang wrote: Hi All, I just created the issue #126823 for netbeans-integration Japanese language update. https://bz.apache.org/ooo/show_bug.cgi?id=126823 I don't have committer karma, so please commit the patch. Use my name and email in the commit message if it's

RE: [PROPOSAL] Distribute only one source package

I have some afterthoughts about this, 1. Because of line-ending issues, and the use of POSIX/*nix permissions or not, a Zip of the kind mainly used by Windows developers and a .tar.gz/.bz2 used by mainly POSIX-oriented developers (e.g., within Cygwin or on a Linux platform) might not be

Re: [PROPOSAL] Distribute only one source package

Dennis E. Hamilton wrote: 1. one of tar.gz/.bz2 is probably the best choice. ... That's a pragmatic solution, not a community-building one [;<). So be it. Well, as we discussed so far, anybody willing to build on Windows has to download tools capable of handling .tar.bz2 anyway, and

Re: Let's fix the Windows build bots

On 02/04/2016 10:11 AM, Damjan Jovanovic wrote: > On Thu, Feb 4, 2016 at 7:42 PM, Kay Schenk wrote: > >> >> On 02/04/2016 06:05 AM, Damjan Jovanovic wrote: >>> On Wed, Feb 3, 2016 at 1:48 PM, Jochen Nitschke >> wrote: >>> On Wed, 3 Feb 2016

RE: Building on Windows

> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Thursday, February 4, 2016 13:48 > To: dev@openoffice.apache.org > Subject: Re: Building on Windows > > On 2/4/2016 12:40 PM, Regina Henschel wrote: > > Hi Patricia, > > > > Patricia Shanahan schrieb: > >> I

Re: Building on Windows

On 2/4/2016 3:36 PM, Damjan Jovanovic wrote: On Thu, Feb 4, 2016 at 11:47 PM, Patricia Shanahan wrote: On 2/4/2016 12:40 PM, Regina Henschel wrote: Hi Patricia, Patricia Shanahan schrieb: I think maybe I need to clean up and start again. What is the best way to clean,

Re: Building on Windows

Remember what I told you about main/icu: it doesn't build deterministically, sometimes it fails and sometimes it passes for no apparent reason, keep cleaning and rebuilding in its directory until it builds then "deliver" and continue as before. On Thu, Feb 4, 2016 at 4:21 PM, Patricia Shanahan

Re: Building on Windows

Thanks for the reminder. My plan for this morning was to search my mail archive for "icuin". I had hoped that getting rid of MP would get rid of this sort of non-determinism. On 2/4/2016 6:30 AM, Damjan Jovanovic wrote: Remember what I told you about main/icu: it doesn't build

Including Gradle Wrapper Jar in SVN

Hi All, For Gradle build based projects is it acceptable to include the gradle-wrapper.jar file (along with the scripts) in Apache SVN? More here [1]. The reason is so users wanting to build the code do not need to manually install Gradle. [1]

Re: Building on Windows

I had 25 consecutive "build --all" attempts fail, at different places, due to the retryable errors. The general behavior, and the fact that the frequency of failure varies from environment to environment, supports the theory that the failures are due to poorly managed multiprocessing.

Re: Let's fix the Windows build bots

On Wed, Feb 3, 2016 at 1:48 PM, Jochen Nitschke wrote: > On Wed, 3 Feb 2016 13:15:23 +0200 Damjan Jovanovic wrote: > > So builds@ replied saying the buildbot was broken by an earlier bad > commit > > (not mine) and should be working now, and it was, but I ended up needing > to

RE: Building on Windows

> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Wednesday, February 3, 2016 08:16 > To: dev@openoffice.apache.org > Subject: Re: Building on Windows > [ ... ] > > I have some hypotheses about my current problems. Is there a master list > of build targets and

Re: Building on Windows

I got icu to build. Here is my latest failure: C:\OpenOfficeDev\Trunk\main\offapi\com\sun\star\sdb\XRowSetChangeListener.idl(45) : WARNING, type or identifier doesn't fulfill the UNO naming convention: i_Event dmake: /cygdrive/c/OpenOfficeDev/Trunk/main/solenv/inc/target.mk: line 583:

Re: Building on Windows

That's just a unit test, although main/cppu/qa/makefile.mk should really be ignoring failures in rm: $(MISC)$/$(TARGET).rdb: $(MISC)$/$(TARGET)$/types.urd - rm $@ $(REGMERGE) $@ /UCR $< Try "ENABLE_UNIT_TESTS=NO build" On Thu, Feb 4, 2016 at 6:51 PM, Patricia Shanahan

RE: Including Gradle Wrapper Jar in SVN

GENERIC THOUGHTS This is a generic response without consideration of the merits of the particular proposal. 1. Normally, we are discouraged from keeping binaries (i.e., non source) in the SVN. Now I wonder if we already have .jar files in the Source Release. (I am afraid to look [;<). 2.

Re: Let's fix the Windows build bots

On 02/04/2016 06:05 AM, Damjan Jovanovic wrote: > On Wed, Feb 3, 2016 at 1:48 PM, Jochen Nitschke wrote: > >> On Wed, 3 Feb 2016 13:15:23 +0200 Damjan Jovanovic wrote: >>> So builds@ replied saying the buildbot was broken by an earlier bad >> commit >>> (not mine) and should

Re: Building on Windows

I think maybe I need to clean up and start again. What is the best way to clean, short of doing a fresh checkout? Patricia@Jan2014Desktop /cygdrive/c/OpenOfficeDev/Trunk/main/instsetoo_native $ ENABLE_UNIT_TESTS=NO build 2>&1 |tee wk3 build -- version: 275224 = Building module

Re: Let's fix the Windows build bots

On Thu, Feb 4, 2016 at 7:42 PM, Kay Schenk wrote: > > On 02/04/2016 06:05 AM, Damjan Jovanovic wrote: > > On Wed, Feb 3, 2016 at 1:48 PM, Jochen Nitschke > wrote: > > > >> On Wed, 3 Feb 2016 13:15:23 +0200 Damjan Jovanovic wrote: > >>> So builds@ replied

netbeans-integration Japanese language update

Hi All, I just created the issue #126823 for netbeans-integration Japanese language update. https://bz.apache.org/ooo/show_bug.cgi?id=126823 I don't have committer karma, so please commit the patch. Use my name and email in the commit message if it's needed. Thanks in advance. Yu Tang

Re: Building on Windows

Cleaning is covered in https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO which currently seems down? Personally I use "dmake clean" in main, and if I really want to delete absolutely every new file since SVN checkout: svn revert * -R svn status | while read i; do rm -rf "${i:8}";

Re: Building on Windows

Hi Patricia, Patricia Shanahan schrieb: I think maybe I need to clean up and start again. What is the best way to clean, short of doing a fresh checkout? I remove the output-tree manually Starting in main: find . -maxdepth 2 -name "wntmsci12*" | xargs rm -rf In addition delete wntmsci12*

RE: [PROPOSAL][DEVTOOLS] Stage Java BootstrapConnector to Maven Repository

Summary: 1. I think the use of the openoffice "class path" and packaging that is already accepted for use be continued, rather than disturb the Java and maven identifiers that people are already using and expect. 2. Creating a distribution is complicated by the absence of a new Apache