Re: buildbot failure in on openoffice-linux64-nightly

[Damjan Jovanovic]

Am I the only one seeing the Windows build crash on startup? :(

On Tue, Apr 10, 2018 at 7:03 PM, Matthias Seidel  wrote:

> Am 10.04.2018 um 18:58 schrieb Damjan Jovanovic:
> > On Tue, Apr 10, 2018 at 6:24 PM, Matthias Seidel <
> matthias.sei...@hamburg.de
> >> wrote:
> >> Am 10.04.2018 um 18:02 schrieb Damjan Jovanovic:
> >>> Thank you. Windows worked for me too, probably because I used
> >>> --without-junit and skipped the tests that way.
> >> That is also in my configure...
> >> (Should it be enabled?)
> >>
> > If you want the Java unit tests to run, then enable JUnit.
> >
> > Unit tests should always run, IMO. Testing during the build catches
> > problems as early as possible, and isolates bugs at a much finer level
> than
> > integration tests and graphical tests.
>
> Makes sense!
> I will now enable it for my test builds...
>
> For release versions we built without it.
>
> >
> >
> >>> In 1828829 I committed a check for whether tests are present before
> >> trying
> >>> to compile them. I think it should fix this problem.
> >> Great!
> >>
> > Thank you :).
>
> Buildbot is running right now. ;-)
>
> >
>
>
>

Re: Time to push on for 4.2.0

[Damjan Jovanovic]

Hi

Before we start on 4.2.0 I would like to finish off porting one final
module, main/jvmfwk, to gbuild. Then I'll take a break from the build
changes, and would like to contribute these improvements:

* Overhaul our Java support. Support newer Java versions. Enhance Java
detection on *nix, adding OpenJDK and matching on prefixes (like openjdk*
for FreeBSD, eg. /usr/local/openjdk7, /usr/local/openjdk8) instead of fixed
strings such as "jdk". Look in /usr/lib too on 64 bit Linux instead of the
RedHat-only /usr/lib64. Accelerate Java autodetection by resolving symbolic
links and caching results to avoid the slowness of multiple unnecessary
checks of the same Java directory through different symlinks.
* GStreamer 0.1 and 1.0.
* Audit the new SDBC-JDBC bridge and ensure it's 100% compatible with the
old one.
* Library naming and symbol versioning audit of all libraries against 4.1.x.
* Run all tests against 4.1.x and trunk, and fix the regressions.
* Full PostgreSQL support (views, indexes, users, groups, GUI dialogs) if
there is time.
* Get the Mediawiki plugin working again, if there is time.


On Tue, Apr 10, 2018 at 2:54 PM, Jim Jagielski  wrote:

> We have still not yet made any strategic determination... We have
> a possible scenario where gstreamer can be built regardless of
> what version the build system has in place, but, afaict, that has
> not yet been folded in.
>
> My suggestion would be that that gets committed ASAP so we
> can test it. We then svn copy trunk to a AOO420 branch and
> start focusing on getting a 4.2.0 GA release out.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: Time to push on for 4.2.0

[Marcus]

Am 10.04.2018 um 14:54 schrieb Jim Jagielski:

We have still not yet made any strategic determination... We have
a possible scenario where gstreamer can be built regardless of
what version the build system has in place, but, afaict, that has
not yet been folded in.

My suggestion would be that that gets committed ASAP so we
can test it. We then svn copy trunk to a AOO420 branch and
start focusing on getting a 4.2.0 GA release out.


thanks for the reminder.

I also think it's time to start with splitting from the continued 
developement and make a branch for 4.2.0.


The advantage is that we can start to create a stable code base - at the 
moment at least for building, later on also for the code quality.


The disadvantage is that we then need to deal with merging code snippets 
to trunk *and* 420_branch. But also at a later time this has to be done 
anyway - so not really a disadvantage.


Marcus


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Search for duplicates

[Miriam Robarts]

Hello,

I was just writing a book review & thinking of my pet peeve regarding
repetition of words, when I realized that this could be a useful tool in
word processing programs.

I know you can use the find feature to look for similar words to the search
term, but it would be great to have a tool that could identify duplicate
words (and their related forms) without entering a search term (while
excluding articles and pronouns, etc., of course--as well as a field to
enter other words to be excluded from the search, e.g. names). This would
be much more useful for finding similar words, since people usually aren't
aware of when they repeat them.

It would be good to have a tool like this, so if I used the same adjective
more than once, or if I used two forms of the same word (e.g. amazing, and
amazingly), I could consider changing one to a synonym.

It'd probably be most useful for the result to be a list of words that you
could click on to highlight and find in the document, so you could deal
with one set at a time if there were duplicates of several words. It would
also be nice if you could choose to ignore words that come up in the result
and remove them from the list.

Thank you for your consideration!

-Miriam

Re: buildbot failure in on openoffice-linux64-nightly

[Matthias Seidel]

Am 10.04.2018 um 18:58 schrieb Damjan Jovanovic:
> On Tue, Apr 10, 2018 at 6:24 PM, Matthias Seidel > wrote:
>> Am 10.04.2018 um 18:02 schrieb Damjan Jovanovic:
>>> Thank you. Windows worked for me too, probably because I used
>>> --without-junit and skipped the tests that way.
>> That is also in my configure...
>> (Should it be enabled?)
>>
> If you want the Java unit tests to run, then enable JUnit.
>
> Unit tests should always run, IMO. Testing during the build catches
> problems as early as possible, and isolates bugs at a much finer level than
> integration tests and graphical tests.

Makes sense!
I will now enable it for my test builds...

For release versions we built without it.

>
>
>>> In 1828829 I committed a check for whether tests are present before
>> trying
>>> to compile them. I think it should fix this problem.
>> Great!
>>
> Thank you :).

Buildbot is running right now. ;-)

>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: buildbot failure in on openoffice-linux64-nightly

[Damjan Jovanovic]

On Tue, Apr 10, 2018 at 6:24 PM, Matthias Seidel  wrote:

> Am 10.04.2018 um 18:02 schrieb Damjan Jovanovic:
> > Thank you. Windows worked for me too, probably because I used
> > --without-junit and skipped the tests that way.
>
> That is also in my configure...
> (Should it be enabled?)
>

If you want the Java unit tests to run, then enable JUnit.

Unit tests should always run, IMO. Testing during the build catches
problems as early as possible, and isolates bugs at a much finer level than
integration tests and graphical tests.


>
> >
> > In 1828829 I committed a check for whether tests are present before
> trying
> > to compile them. I think it should fix this problem.
>
> Great!
>

Thank you :).

Re: buildbot failure in on openoffice-linux64-nightly

[Matthias Seidel]

Am 10.04.2018 um 18:02 schrieb Damjan Jovanovic:
> Thank you. Windows worked for me too, probably because I used
> --without-junit and skipped the tests that way.

That is also in my configure...
(Should it be enabled?)

>
> In 1828829 I committed a check for whether tests are present before trying
> to compile them. I think it should fix this problem.

Great!

>
> On Tue, Apr 10, 2018 at 4:31 PM, Matthias Seidel > wrote:
>> This time it seems to be Linux failing, while Windows builds fine...
>>
>> 1 module(s):
>>  ridljar
>> need(s) to be rebuilt
>>
>> Reason(s):
>>
>> ERROR: error 65280 occurred while making 
>> /home/buildslave/slave/openoffice-linux64-nightly/build/main/ridljar/prj
>>
>>
>>
>>  Weitergeleitete Nachricht 
>> Betreff: buildbot failure in on openoffice-linux64-nightly
>> Datum: Tue, 10 Apr 2018 11:01:59 +
>> Von: build...@apache.org
>> Antwort an: dev@openoffice.apache.org
>> An: comm...@openoffice.apache.org
>>
>> The Buildbot has detected a new failure on builder 
>> openoffice-linux64-nightly while building . Full details are available at:
>> https://ci.apache.org/builders/openoffice-linux64-nightly/builds/414
>>
>> Buildbot URL: https://ci.apache.org/
>>
>> Buildslave for this Build: bb_slave4_ubuntu
>>
>> Build Reason: forced: by IRC user  (privmsg): None
>> Build Source Stamp: HEAD
>> Blamelist:
>>
>> BUILD FAILED: failed build --all
>>
>> Sincerely,
>>  -The Buildbot
>>
>>
>>
>>
>>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: buildbot failure in on openoffice-linux64-nightly

[Damjan Jovanovic]

Thank you. Windows worked for me too, probably because I used
--without-junit and skipped the tests that way.

In 1828829 I committed a check for whether tests are present before trying
to compile them. I think it should fix this problem.

On Tue, Apr 10, 2018 at 4:31 PM, Matthias Seidel  wrote:

> This time it seems to be Linux failing, while Windows builds fine...
>
> 1 module(s):
>   ridljar
> need(s) to be rebuilt
>
> Reason(s):
>
> ERROR: error 65280 occurred while making 
> /home/buildslave/slave/openoffice-linux64-nightly/build/main/ridljar/prj
>
>
>
>  Weitergeleitete Nachricht 
> Betreff: buildbot failure in on openoffice-linux64-nightly
> Datum: Tue, 10 Apr 2018 11:01:59 +
> Von: build...@apache.org
> Antwort an: dev@openoffice.apache.org
> An: comm...@openoffice.apache.org
>
> The Buildbot has detected a new failure on builder openoffice-linux64-nightly 
> while building . Full details are available at:
> https://ci.apache.org/builders/openoffice-linux64-nightly/builds/414
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: bb_slave4_ubuntu
>
> Build Reason: forced: by IRC user  (privmsg): None
> Build Source Stamp: HEAD
> Blamelist:
>
> BUILD FAILED: failed build --all
>
> Sincerely,
>  -The Buildbot
>
>
>
>
>

Fwd: buildbot failure in on openoffice-linux64-nightly

[Matthias Seidel]

This time it seems to be Linux failing, while Windows builds fine...

1 module(s): ridljar need(s) to be rebuilt Reason(s): ERROR: error 65280
occurred while making
/home/buildslave/slave/openoffice-linux64-nightly/build/main/ridljar/prj



 Weitergeleitete Nachricht 
Betreff:buildbot failure in on openoffice-linux64-nightly
Datum:  Tue, 10 Apr 2018 11:01:59 +
Von:build...@apache.org
Antwort an: dev@openoffice.apache.org
An: comm...@openoffice.apache.org



The Buildbot has detected a new failure on builder openoffice-linux64-nightly 
while building . Full details are available at:
https://ci.apache.org/builders/openoffice-linux64-nightly/builds/414

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: bb_slave4_ubuntu

Build Reason: forced: by IRC user  (privmsg): None
Build Source Stamp: HEAD
Blamelist: 

BUILD FAILED: failed build --all

Sincerely,
 -The Buildbot





smime.p7s
Description: S/MIME Cryptographic Signature

Re: Time to push on for 4.2.0

[Matthias Seidel]

Am 10.04.2018 um 14:54 schrieb Jim Jagielski:
> We have still not yet made any strategic determination... We have
> a possible scenario where gstreamer can be built regardless of
> what version the build system has in place, but, afaict, that has
> not yet been folded in.
>
> My suggestion would be that that gets committed ASAP so we
> can test it. We then svn copy trunk to a AOO420 branch and
> start focusing on getting a 4.2.0 GA release out.

+1

Matthias

>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature

Time to push on for 4.2.0

[Jim Jagielski]

We have still not yet made any strategic determination... We have
a possible scenario where gstreamer can be built regardless of
what version the build system has in place, but, afaict, that has
not yet been folded in.

My suggestion would be that that gets committed ASAP so we
can test it. We then svn copy trunk to a AOO420 branch and
start focusing on getting a 4.2.0 GA release out.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Thesis Survey - Personality and Burnout in Software Developers

[Emanuel Mellblom]

Thesis Survey - Personality and Burnout in Software Developers

Hello,

We are two university students conducting a thesis research project which 
investigates the correlation between a software developer’s personality traits 
and their susceptibility to workplace burnout. If you are currently employed as 
a software developer, we invite you to participate by taking a survey measuring 
your personality and burnout to help us gain a better understanding of the 
subject. The survey should take no more than 5-10 minutes to complete. A link 
to the survey may be found below.

https://goo.gl/forms/cOmsqJlAmVUaW3zq1 
Your survey response will be anonymous and strictly confidential, and all data 
collected will be reported only in aggregate. If you would like to receive a 
copy of the results, you may reply to this email and they will be forwarded to 
you once the findings have been published.

With thanks,
Emanuel Mellblom
gusmell...@student.gu.se 
University of Gothenburg, Sweden

Isar Arason
gusar...@student.gu.se 
University of Gothenburg, Sweden

Re: Minimum Ant version is now 1.9.1

[Damjan Jovanovic]

I've also updated our Java policy wiki page with the new requirements:
https://wiki.openoffice.org/wiki/Policies/Java_Usage

On Tue, Apr 10, 2018 at 1:20 PM, Matthias Seidel  wrote:

> Hi,
>
> Maybe we should set:
>
>   ant_minver=1.7.0
>
> in main/configure.ac to the new minimum version?
>
> Regards,
>
>Matthias
>
>
> Am 08.04.2018 um 14:59 schrieb Damjan Jovanovic:
> > Hi
> >
> > In porting main/jurt to gbuild in commits 1828636 and 1828638, I've ended
> > up doing considerable development in Ant, adding the ability to call IDL
> > tools (idlc, regmerge, javamaker) from Ant, and with the features I've
> > used, the minimum Ant version is now 1.9.1.
> >
> > Please let me know if you have any problems.
> >
> > Regards
> > Damjan
> >
>
>
>

Re: Minimum Ant version is now 1.9.1

[Matthias Seidel]

Am 10.04.2018 um 13:26 schrieb Jim Jagielski:
> No prob... I've been using at least that version on the Linux and macOS
> builds for 4.1.x

The same for the Windows builds.

It seems that the minimum Ant version was indeed 1.6.0 and only 1.7.0 if
MedaiWiki was enabled.

---
ant_minver=1.6.0
# update for more extensions...
if test "$ENABLE_MEDIAWIKI" = "YES"; then
  ant_minver=1.7.0
fi
---

But MediaWiki is broken anyway [1] and hopefully we can get it working
with a newer Ant?
That said, should we set both to 1.9.1?

Regards,

  Matthias

[1] https://bz.apache.org/ooo/show_bug.cgi?id=92492


>> On Apr 8, 2018, at 8:59 AM, Damjan Jovanovic  wrote:
>>
>> Hi
>>
>> In porting main/jurt to gbuild in commits 1828636 and 1828638, I've ended
>> up doing considerable development in Ant, adding the ability to call IDL
>> tools (idlc, regmerge, javamaker) from Ant, and with the features I've
>> used, the minimum Ant version is now 1.9.1.
>>
>> Please let me know if you have any problems.
>>
>> Regards
>> Damjan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Minimum Ant version is now 1.9.1

[Jim Jagielski]

No prob... I've been using at least that version on the Linux and macOS
builds for 4.1.x

> On Apr 8, 2018, at 8:59 AM, Damjan Jovanovic  wrote:
> 
> Hi
> 
> In porting main/jurt to gbuild in commits 1828636 and 1828638, I've ended
> up doing considerable development in Ant, adding the ability to call IDL
> tools (idlc, regmerge, javamaker) from Ant, and with the features I've
> used, the minimum Ant version is now 1.9.1.
> 
> Please let me know if you have any problems.
> 
> Regards
> Damjan


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Minimum Ant version is now 1.9.1

[Matthias Seidel]

Hi,

Maybe we should set:

  ant_minver=1.7.0

in main/configure.ac to the new minimum version?

Regards,

   Matthias


Am 08.04.2018 um 14:59 schrieb Damjan Jovanovic:
> Hi
>
> In porting main/jurt to gbuild in commits 1828636 and 1828638, I've ended
> up doing considerable development in Ant, adding the ability to call IDL
> tools (idlc, regmerge, javamaker) from Ant, and with the features I've
> used, the minimum Ant version is now 1.9.1.
>
> Please let me know if you have any problems.
>
> Regards
> Damjan
>




smime.p7s
Description: S/MIME Cryptographic Signature