WikiPublisher extension (was Re: servlet-api.jar)
On 4 Oct, Don Lewis wrote: > On 4 Oct, Matthias Seidel wrote: >> Am 04.10.2017 um 18:27 schrieb Keith N. McKenna: >>> On 10/4/2017 11:49 AM, Matthias Seidel wrote: Am 04.10.2017 um 17:42 schrieb Keith N. McKenna: > On 9/30/2017 8:42 AM, Don Lewis wrote: >> On 29 Sep, Matthias Seidel wrote: >>> That might explain why I have never seen a working WikiPublisher in the >>> last releases. >>> (Since at least 4.1.2 we build with that option on Windows) >>> >>> The question is: Do we need to build with that option if no one missed >>> the plugin? >> I've never tried to use it, so I don't know if it works or not. >> > Currently in version 4.1.3 the send to MediaWiki option does not work. > My SWAG is that the Sun Wiki Publisher Extension was never updated to > work with the API changes introduced with the 4.0.0 Release. Confirmed (also for 4.1.4 RC4) However it can still be installed as an extension: https://extensions.openoffice.org/en/project/sun-wiki-publisher Last time I tried it the "send to" option was there, but I never tested further... Matthias >>> Mathias; >>> >>> It is the extension that I tested and it does not work. There were API >>> changes introduced in AOO Version 4.0.0 that were most likely never >>> updated in the extension. It is the extension that adds to MediaWiki >>> into File/Send. >>> >>> Regards >>> Keith >> >> OK, I misunderstood. >> >> My hope was that at least this old extension would work, since building >> with --enable-wiki-publisher (tried also the additional >> --with-servlet-api-jar) does not have any effect on a build. >> We build releases with that option, so normally there should be no need >> to install this (old) extension. > > The --enable-wiki-publisher should cause the .oxt file for the extension > to be built. On FreeBSD that ends up getting packaged along with > everything else and gets installed along with the rest. By default, if > you want to use it, you have to go into Extension Manager and dig around > in the installed tree to find the .oxt file and add it. > > I haven't tried building this extension on either Linux or Windows, so I > don't know if/how it gets packaged. I rebuilt trunk on Windows with --enable-wiki-publisher. The first problem is that the extension does not appear to get packaged. If you have the Windows build tree handy, then you can find the extension here: mail/solver/420/wntmsci12.pro/bin/swext/wiki-publisher.oxt I went into the extension manager and told it to add this extension. The extension manager appears to successfully add the extension, and when I look at the File->Send submenu, I see an entry for "To MediaWiki..." menu entry, but it is grayed out and can't be selected. I don't know how to debug this. Can someone with a Linux or Mac build tree try this experiment? A 4.1.4 build tree should be fine as long as you configured with --enable-wiki-publisher. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Java 9 32-bit
Hmm I was not answering you. Should have picked Damian mal. The suggestion to use .net is to translate to c#. Or I misread. Sorry. Am 4. Oktober 2017 20:50:06 MESZ schrieb Marcus : >Am 04.10.2017 um 08:54 schrieb Peter kovacs: > >are you answering my mail or was this just a random reply? >I'm wondering as I don't see anything new in your mail. > >> How relevant is Win 32 bit in future? > >0,0 % > >> Shouldn't we offer a Win 64bit in long run? > >Of course. > >> Why move to C#? I do not see the benefit. > >Nobody wants to move to C#. > >Marcus > > > >> Am 3. Oktober 2017 23:18:12 MESZ schrieb Marcus >: >>> Am 03.10.2017 um 22:26 schrieb Kay Schenk: On Tue, Oct 3, 2017 at 8:02 AM, Fernando Cassia >>> wrote: > On 10/3/17, Damjan Jovanovic wrote: >> Now what: >> 1. Ship our own builds of OpenJDK, in matching bitness. Do the >>> licences >> (GPL for JVM, GPL-with-classpath-exception for class library) >allow >>> us > to? >> 2. Drop Windows as a platform, since it's the only affected >>> platform > (*nix >> users usually install distro OpenJDK packages so 32 bit OpenJDK >>> will be >> available for 32 bit AOO). We have no Win64 AOO. >> 3. Drop 32 bit versions of AOO and add Win64 support. >> 4. Or drop Java entirely and port our Java code to eg. .NET core, >>> which > is >> liberally licensed and private copies of it can be shipped? >> >> Damjan > > Tempest in a teapot. You do know that Oracle isn't the only >provider > of Java or OpenJDK, right? > > Options > 1. You can buiild your own 32-bit x86 binary based on OpenJDK >>> sources. > 2. make AOO compile OK on 64 bit thus making AOO a 64-bit Windows >>> app, > able to use any 64-bit JRE (Oracle JRE, IBM JRE, Azul's Zulu JRE) > 3. Have you asked Azul Systems if they can provide a 32-bit build? > 4. Compile the Java code in AOO as native with Java 9's AOT >>> compiler? > http://openjdk.java.net/jeps/295 > > Just my $0.02 > FC > > As a bystander, I'm wondering just how alarming this news is to >>> Apache OpenOffice. >>> >>> IMHO not at all. Java 9 was published just 2 weeks ago. So, it will >>> take >>> some time until it's the favorite one. Until then 8 is developer's >>> darling. >>> The builds are using Java 6 or 7, right? >>> >>> With the next larger release (probably 4.2.0) we will use Java 8 >which >>> should last a longer time. Time enough to decide what to do with the >>> dependency of Java 32-bit. >>> I'm still on 32-bit Linux for now but my default OpenJDK is 1.8. >I >>> can run AOO fine with it but must use 1.7 for building. > > >- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: servlet-api.jar
On 10/4/2017 4:43 PM, Don Lewis wrote: > On 4 Oct, Keith N. McKenna wrote: >> On 10/4/2017 3:03 PM, Don Lewis wrote: >>> On 4 Oct, Matthias Seidel wrote: Am 04.10.2017 um 18:27 schrieb Keith N. McKenna: > On 10/4/2017 11:49 AM, Matthias Seidel wrote: >> Am 04.10.2017 um 17:42 schrieb Keith N. McKenna: >>> On 9/30/2017 8:42 AM, Don Lewis wrote: On 29 Sep, Matthias Seidel wrote: > That might explain why I have never seen a working WikiPublisher in > the > last releases. > (Since at least 4.1.2 we build with that option on Windows) > > The question is: Do we need to build with that option if no one missed > the plugin? I've never tried to use it, so I don't know if it works or not. >>> Currently in version 4.1.3 the send to MediaWiki option does not work. >>> My SWAG is that the Sun Wiki Publisher Extension was never updated to >>> work with the API changes introduced with the 4.0.0 Release. >> Confirmed (also for 4.1.4 RC4) >> >> However it can still be installed as an extension: >> https://extensions.openoffice.org/en/project/sun-wiki-publisher >> >> Last time I tried it the "send to" option was there, but I never tested >> further... >> >> Matthias >> > Mathias; > > It is the extension that I tested and it does not work. There were API > changes introduced in AOO Version 4.0.0 that were most likely never > updated in the extension. It is the extension that adds to MediaWiki > into File/Send. > > Regards > Keith OK, I misunderstood. My hope was that at least this old extension would work, since building with --enable-wiki-publisher (tried also the additional --with-servlet-api-jar) does not have any effect on a build. We build releases with that option, so normally there should be no need to install this (old) extension. >>> >>> The --enable-wiki-publisher should cause the .oxt file for the extension >>> to be built. On FreeBSD that ends up getting packaged along with >>> everything else and gets installed along with the rest. By default, if >>> you want to use it, you have to go into Extension Manager and dig around >>> in the installed tree to find the .oxt file and add it. >>> >>> I haven't tried building this extension on either Linux or Windows, so I >>> don't know if/how it gets packaged. >>> >>> I've got some patches in the FreeBSD port of the snapshot of trunk that >>> causes the extensions that are built along with the rest of the source >>> to be treated as integrated extensions so they automatically show up as >>> installed in Extension Manager. With that I get a functional send >>> button that pops up a dialog box that asks for MediaWiki server and some >>> other info. >>> >>> There is a bunch of stuff scattered around the wiki about bundled and >>> integrated extensions and how they should be packaged. >>> >> This gets more and more interesting. I have added the Sun Wiki Publisher >> extension to my Windows installation and It adds a "to MediaWiki" entry >> to the File/Send options. If clicked it opens the dialog box looking for >> the wiki URL and username and password however it does nothing with the >> information which is what led me to believe that the API changes from >> AOO 4.0 had not been added to the extension. That they hadn't would make >> sense since the last time it had been uploaded to the extension site was >> 2009-09-06. Does the extension code that the FreeBSD port builds and >> installs actually use the information and create the a page on the wiki >> based on the document it is run against? > > I stopped where I did because I don't have a wiki that I can test > against. > Don; I can create an mwiki account for you if you are interested in testing your changes further. Just reply with a user name that you would like. Regards Keith signature.asc Description: OpenPGP digital signature
Re: servlet-api.jar
On 4 Oct, Keith N. McKenna wrote: > On 10/4/2017 3:03 PM, Don Lewis wrote: >> On 4 Oct, Matthias Seidel wrote: >>> Am 04.10.2017 um 18:27 schrieb Keith N. McKenna: On 10/4/2017 11:49 AM, Matthias Seidel wrote: > Am 04.10.2017 um 17:42 schrieb Keith N. McKenna: >> On 9/30/2017 8:42 AM, Don Lewis wrote: >>> On 29 Sep, Matthias Seidel wrote: That might explain why I have never seen a working WikiPublisher in the last releases. (Since at least 4.1.2 we build with that option on Windows) The question is: Do we need to build with that option if no one missed the plugin? >>> I've never tried to use it, so I don't know if it works or not. >>> >> Currently in version 4.1.3 the send to MediaWiki option does not work. >> My SWAG is that the Sun Wiki Publisher Extension was never updated to >> work with the API changes introduced with the 4.0.0 Release. > Confirmed (also for 4.1.4 RC4) > > However it can still be installed as an extension: > https://extensions.openoffice.org/en/project/sun-wiki-publisher > > Last time I tried it the "send to" option was there, but I never tested > further... > > Matthias > Mathias; It is the extension that I tested and it does not work. There were API changes introduced in AOO Version 4.0.0 that were most likely never updated in the extension. It is the extension that adds to MediaWiki into File/Send. Regards Keith >>> >>> OK, I misunderstood. >>> >>> My hope was that at least this old extension would work, since building >>> with --enable-wiki-publisher (tried also the additional >>> --with-servlet-api-jar) does not have any effect on a build. >>> We build releases with that option, so normally there should be no need >>> to install this (old) extension. >> >> The --enable-wiki-publisher should cause the .oxt file for the extension >> to be built. On FreeBSD that ends up getting packaged along with >> everything else and gets installed along with the rest. By default, if >> you want to use it, you have to go into Extension Manager and dig around >> in the installed tree to find the .oxt file and add it. >> >> I haven't tried building this extension on either Linux or Windows, so I >> don't know if/how it gets packaged. >> >> I've got some patches in the FreeBSD port of the snapshot of trunk that >> causes the extensions that are built along with the rest of the source >> to be treated as integrated extensions so they automatically show up as >> installed in Extension Manager. With that I get a functional send >> button that pops up a dialog box that asks for MediaWiki server and some >> other info. >> >> There is a bunch of stuff scattered around the wiki about bundled and >> integrated extensions and how they should be packaged. >> > This gets more and more interesting. I have added the Sun Wiki Publisher > extension to my Windows installation and It adds a "to MediaWiki" entry > to the File/Send options. If clicked it opens the dialog box looking for > the wiki URL and username and password however it does nothing with the > information which is what led me to believe that the API changes from > AOO 4.0 had not been added to the extension. That they hadn't would make > sense since the last time it had been uploaded to the extension site was > 2009-09-06. Does the extension code that the FreeBSD port builds and > installs actually use the information and create the a page on the wiki > based on the document it is run against? I stopped where I did because I don't have a wiki that I can test against. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: servlet-api.jar
On 10/4/2017 3:03 PM, Don Lewis wrote: > On 4 Oct, Matthias Seidel wrote: >> Am 04.10.2017 um 18:27 schrieb Keith N. McKenna: >>> On 10/4/2017 11:49 AM, Matthias Seidel wrote: Am 04.10.2017 um 17:42 schrieb Keith N. McKenna: > On 9/30/2017 8:42 AM, Don Lewis wrote: >> On 29 Sep, Matthias Seidel wrote: >>> That might explain why I have never seen a working WikiPublisher in the >>> last releases. >>> (Since at least 4.1.2 we build with that option on Windows) >>> >>> The question is: Do we need to build with that option if no one missed >>> the plugin? >> I've never tried to use it, so I don't know if it works or not. >> > Currently in version 4.1.3 the send to MediaWiki option does not work. > My SWAG is that the Sun Wiki Publisher Extension was never updated to > work with the API changes introduced with the 4.0.0 Release. Confirmed (also for 4.1.4 RC4) However it can still be installed as an extension: https://extensions.openoffice.org/en/project/sun-wiki-publisher Last time I tried it the "send to" option was there, but I never tested further... Matthias >>> Mathias; >>> >>> It is the extension that I tested and it does not work. There were API >>> changes introduced in AOO Version 4.0.0 that were most likely never >>> updated in the extension. It is the extension that adds to MediaWiki >>> into File/Send. >>> >>> Regards >>> Keith >> >> OK, I misunderstood. >> >> My hope was that at least this old extension would work, since building >> with --enable-wiki-publisher (tried also the additional >> --with-servlet-api-jar) does not have any effect on a build. >> We build releases with that option, so normally there should be no need >> to install this (old) extension. > > The --enable-wiki-publisher should cause the .oxt file for the extension > to be built. On FreeBSD that ends up getting packaged along with > everything else and gets installed along with the rest. By default, if > you want to use it, you have to go into Extension Manager and dig around > in the installed tree to find the .oxt file and add it. > > I haven't tried building this extension on either Linux or Windows, so I > don't know if/how it gets packaged. > > I've got some patches in the FreeBSD port of the snapshot of trunk that > causes the extensions that are built along with the rest of the source > to be treated as integrated extensions so they automatically show up as > installed in Extension Manager. With that I get a functional send > button that pops up a dialog box that asks for MediaWiki server and some > other info. > > There is a bunch of stuff scattered around the wiki about bundled and > integrated extensions and how they should be packaged. > This gets more and more interesting. I have added the Sun Wiki Publisher extension to my Windows installation and It adds a "to MediaWiki" entry to the File/Send options. If clicked it opens the dialog box looking for the wiki URL and username and password however it does nothing with the information which is what led me to believe that the API changes from AOO 4.0 had not been added to the extension. That they hadn't would make sense since the last time it had been uploaded to the extension site was 2009-09-06. Does the extension code that the FreeBSD port builds and installs actually use the information and create the a page on the wiki based on the document it is run against? Regards Keith signature.asc Description: OpenPGP digital signature
Re: [VOTE] Release Apache OpenOffice 4.1.4-RC4 as GA
Despite it's way too late, I wish to add my +1 (binding), since it works nicely on my AirBook now! 2017-10-04 22:11 GMT+02:00 Roberto Galoppini : > > > 2017-10-04 0:40 GMT+02:00 Andrea Pescetti : > >> On 30/09/2017 Jim Jagielski wrote: >> >>> I am calling a VOTE on releasing Apache OpenOffice 4.1.4-RC4 >>> as GA!! >>> >> >> +1 (binding) >> >> I did several tests, including: >> - downloading and verifying the .bz2 sources (checksums, hashes) >> - making sure these match with SVN: they don't but it is just a cosmetic >> difference, see https://bz.apache.org/ooo/show_bug.cgi?id=127544 (not a >> blocker; it was worse in previous releases) >> - configured (English+Italian) and built source on Linux-64 >> - verified that the build works (tested with Writer and Calc) >> - verified LICENSE and NOTICE files >> >> Additionally, I've used the 4.1.4-RC "convenience binaries" for several >> weeks (and recently switched to 4.1.4-RC4): >> - I didn't notice regressions with respect to 4.1.3. >> - I verified that the update connects to the expected internal URL on >> https://ooo-updates.apache.org/ >> >> I still recommend that we verify better the issue reported by Roberto: if >> we determine the cause and find a workaround then, depending on how common >> it is, we may add it to the release notes (assuming we conclude it is not a >> blocker). More in the dedicated thread. >> > > I confirm the problem persist, but it's NOT related to the actual release, > it's happening also with older versions (followed Patricia's hint, good > spot!). > For the sake of it I have also installed Java, but it does not depend on > that. > > Whatever is the root cause, it's clearly not an Apache OpenOffice * > problem. > > Roberto > > > >> >> Regards, >> Andrea. >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> >
Re: [VOTE] Release Apache OpenOffice 4.1.4-RC4 as GA
2017-10-04 0:40 GMT+02:00 Andrea Pescetti : > On 30/09/2017 Jim Jagielski wrote: > >> I am calling a VOTE on releasing Apache OpenOffice 4.1.4-RC4 >> as GA!! >> > > +1 (binding) > > I did several tests, including: > - downloading and verifying the .bz2 sources (checksums, hashes) > - making sure these match with SVN: they don't but it is just a cosmetic > difference, see https://bz.apache.org/ooo/show_bug.cgi?id=127544 (not a > blocker; it was worse in previous releases) > - configured (English+Italian) and built source on Linux-64 > - verified that the build works (tested with Writer and Calc) > - verified LICENSE and NOTICE files > > Additionally, I've used the 4.1.4-RC "convenience binaries" for several > weeks (and recently switched to 4.1.4-RC4): > - I didn't notice regressions with respect to 4.1.3. > - I verified that the update connects to the expected internal URL on > https://ooo-updates.apache.org/ > > I still recommend that we verify better the issue reported by Roberto: if > we determine the cause and find a workaround then, depending on how common > it is, we may add it to the release notes (assuming we conclude it is not a > blocker). More in the dedicated thread. > I confirm the problem persist, but it's NOT related to the actual release, it's happening also with older versions (followed Patricia's hint, good spot!). For the sake of it I have also installed Java, but it does not depend on that. Whatever is the root cause, it's clearly not an Apache OpenOffice * problem. Roberto > > Regards, > Andrea. > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: servlet-api.jar
On 4 Oct, Matthias Seidel wrote: > Am 04.10.2017 um 18:27 schrieb Keith N. McKenna: >> On 10/4/2017 11:49 AM, Matthias Seidel wrote: >>> Am 04.10.2017 um 17:42 schrieb Keith N. McKenna: On 9/30/2017 8:42 AM, Don Lewis wrote: > On 29 Sep, Matthias Seidel wrote: >> That might explain why I have never seen a working WikiPublisher in the >> last releases. >> (Since at least 4.1.2 we build with that option on Windows) >> >> The question is: Do we need to build with that option if no one missed >> the plugin? > I've never tried to use it, so I don't know if it works or not. > Currently in version 4.1.3 the send to MediaWiki option does not work. My SWAG is that the Sun Wiki Publisher Extension was never updated to work with the API changes introduced with the 4.0.0 Release. >>> Confirmed (also for 4.1.4 RC4) >>> >>> However it can still be installed as an extension: >>> https://extensions.openoffice.org/en/project/sun-wiki-publisher >>> >>> Last time I tried it the "send to" option was there, but I never tested >>> further... >>> >>> Matthias >>> >> Mathias; >> >> It is the extension that I tested and it does not work. There were API >> changes introduced in AOO Version 4.0.0 that were most likely never >> updated in the extension. It is the extension that adds to MediaWiki >> into File/Send. >> >> Regards >> Keith > > OK, I misunderstood. > > My hope was that at least this old extension would work, since building > with --enable-wiki-publisher (tried also the additional > --with-servlet-api-jar) does not have any effect on a build. > We build releases with that option, so normally there should be no need > to install this (old) extension. The --enable-wiki-publisher should cause the .oxt file for the extension to be built. On FreeBSD that ends up getting packaged along with everything else and gets installed along with the rest. By default, if you want to use it, you have to go into Extension Manager and dig around in the installed tree to find the .oxt file and add it. I haven't tried building this extension on either Linux or Windows, so I don't know if/how it gets packaged. I've got some patches in the FreeBSD port of the snapshot of trunk that causes the extensions that are built along with the rest of the source to be treated as integrated extensions so they automatically show up as installed in Extension Manager. With that I get a functional send button that pops up a dialog box that asks for MediaWiki server and some other info. There is a bunch of stuff scattered around the wiki about bundled and integrated extensions and how they should be packaged. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Java 9 32-bit
Am 04.10.2017 um 08:54 schrieb Peter kovacs: are you answering my mail or was this just a random reply? I'm wondering as I don't see anything new in your mail. How relevant is Win 32 bit in future? 0,0 % Shouldn't we offer a Win 64bit in long run? Of course. Why move to C#? I do not see the benefit. Nobody wants to move to C#. Marcus Am 3. Oktober 2017 23:18:12 MESZ schrieb Marcus : Am 03.10.2017 um 22:26 schrieb Kay Schenk: On Tue, Oct 3, 2017 at 8:02 AM, Fernando Cassia wrote: On 10/3/17, Damjan Jovanovic wrote: Now what: 1. Ship our own builds of OpenJDK, in matching bitness. Do the licences (GPL for JVM, GPL-with-classpath-exception for class library) allow us to? 2. Drop Windows as a platform, since it's the only affected platform (*nix users usually install distro OpenJDK packages so 32 bit OpenJDK will be available for 32 bit AOO). We have no Win64 AOO. 3. Drop 32 bit versions of AOO and add Win64 support. 4. Or drop Java entirely and port our Java code to eg. .NET core, which is liberally licensed and private copies of it can be shipped? Damjan Tempest in a teapot. You do know that Oracle isn't the only provider of Java or OpenJDK, right? Options 1. You can buiild your own 32-bit x86 binary based on OpenJDK sources. 2. make AOO compile OK on 64 bit thus making AOO a 64-bit Windows app, able to use any 64-bit JRE (Oracle JRE, IBM JRE, Azul's Zulu JRE) 3. Have you asked Azul Systems if they can provide a 32-bit build? 4. Compile the Java code in AOO as native with Java 9's AOT compiler? http://openjdk.java.net/jeps/295 Just my $0.02 FC As a bystander, I'm wondering just how alarming this news is to Apache OpenOffice. IMHO not at all. Java 9 was published just 2 weeks ago. So, it will take some time until it's the favorite one. Until then 8 is developer's darling. The builds are using Java 6 or 7, right? With the next larger release (probably 4.2.0) we will use Java 8 which should last a longer time. Time enough to decide what to do with the dependency of Java 32-bit. I'm still on 32-bit Linux for now but my default OpenJDK is 1.8. I can run AOO fine with it but must use 1.7 for building. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CLOSED] Was: Re: [VOTE] Release Apache OpenOffice 4.1.4-RC4 as GA
+1 I just want to say, this makes me very happy. I regret that I haven't had enough free time to make any real contribution myself, but massive props to everybody who made this happen! AOO lives on! :-) I still have some ideas for Calc I want to work on, so maybe I'll finally be able to carve out some time for that stuff in the near future. Phil This message optimized for indexing by NSA PRISM On Wed, Oct 4, 2017 at 11:57 AM, Jim Jagielski wrote: > After waiting giving us a bit more than the required and > normal 72 hours, we have plenty more than the required 3 > +1 (binding) votes. > > As such, I call the Vote CLOSED with the RESULT that the > Vote Passes!! 4.1.4-RC4 will be released as GA ! > > Thanks to all who helped in every and all ways in getting this > puppy out! > >> On Sep 30, 2017, at 3:54 PM, Jim Jagielski wrote: >> >> I am calling a VOTE on releasing Apache OpenOffice 4.1.4-RC4 >> as GA!! >> >> You can find these gems at: >> >> https://dist.apache.org/repos/dist/dev/openoffice/4.1.4-RC4/ >> >> The vote will last at least the normal 72 hours. >> >> Cheers! >> -- >> Jim Jagielski >> On behalf of the Apache OpenOffice Project >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: servlet-api.jar
On 10/4/2017 12:47 PM, Matthias Seidel wrote: > Am 04.10.2017 um 18:27 schrieb Keith N. McKenna: >> On 10/4/2017 11:49 AM, Matthias Seidel wrote: >>> Am 04.10.2017 um 17:42 schrieb Keith N. McKenna: On 9/30/2017 8:42 AM, Don Lewis wrote: > On 29 Sep, Matthias Seidel wrote: >> That might explain why I have never seen a working WikiPublisher in the >> last releases. >> (Since at least 4.1.2 we build with that option on Windows) >> >> The question is: Do we need to build with that option if no one missed >> the plugin? > I've never tried to use it, so I don't know if it works or not. > Currently in version 4.1.3 the send to MediaWiki option does not work. My SWAG is that the Sun Wiki Publisher Extension was never updated to work with the API changes introduced with the 4.0.0 Release. >>> Confirmed (also for 4.1.4 RC4) >>> >>> However it can still be installed as an extension: >>> https://extensions.openoffice.org/en/project/sun-wiki-publisher >>> >>> Last time I tried it the "send to" option was there, but I never tested >>> further... >>> >>> Matthias >>> >> Mathias; >> >> It is the extension that I tested and it does not work. There were API >> changes introduced in AOO Version 4.0.0 that were most likely never >> updated in the extension. It is the extension that adds to MediaWiki >> into File/Send. >> >> Regards >> Keith > > OK, I misunderstood. > > My hope was that at least this old extension would work, since building > with --enable-wiki-publisher (tried also the additional > --with-servlet-api-jar) does not have any effect on a build. > We build releases with that option, so normally there should be no need > to install this (old) extension. > > Developers might have a look into it. It would be nice to have it > working again in 4.2.0. > > Matthias > >> I believe that it has always been an extension but not really sure. The question becomes since the extension was written by Sun, was it included in the original transfer from Oracle so that we as a project can change it. I will start a new thread so that this does not get lost in the bowels of a thread initially started for a very technical purpose. Regards Keith signature.asc Description: OpenPGP digital signature
Re: servlet-api.jar
Am 04.10.2017 um 18:27 schrieb Keith N. McKenna: > On 10/4/2017 11:49 AM, Matthias Seidel wrote: >> Am 04.10.2017 um 17:42 schrieb Keith N. McKenna: >>> On 9/30/2017 8:42 AM, Don Lewis wrote: On 29 Sep, Matthias Seidel wrote: > That might explain why I have never seen a working WikiPublisher in the > last releases. > (Since at least 4.1.2 we build with that option on Windows) > > The question is: Do we need to build with that option if no one missed > the plugin? I've never tried to use it, so I don't know if it works or not. >>> Currently in version 4.1.3 the send to MediaWiki option does not work. >>> My SWAG is that the Sun Wiki Publisher Extension was never updated to >>> work with the API changes introduced with the 4.0.0 Release. >> Confirmed (also for 4.1.4 RC4) >> >> However it can still be installed as an extension: >> https://extensions.openoffice.org/en/project/sun-wiki-publisher >> >> Last time I tried it the "send to" option was there, but I never tested >> further... >> >> Matthias >> > Mathias; > > It is the extension that I tested and it does not work. There were API > changes introduced in AOO Version 4.0.0 that were most likely never > updated in the extension. It is the extension that adds to MediaWiki > into File/Send. > > Regards > Keith OK, I misunderstood. My hope was that at least this old extension would work, since building with --enable-wiki-publisher (tried also the additional --with-servlet-api-jar) does not have any effect on a build. We build releases with that option, so normally there should be no need to install this (old) extension. Developers might have a look into it. It would be nice to have it working again in 4.2.0. Matthias > >>> It would be nice this were fixed as it would be a great aid in writing >>> documentation. >>> >>> regards >>> Keith >>> >>> >> > smime.p7s Description: S/MIME Cryptographic Signature
Re: servlet-api.jar
On 10/4/2017 11:49 AM, Matthias Seidel wrote: > Am 04.10.2017 um 17:42 schrieb Keith N. McKenna: >> On 9/30/2017 8:42 AM, Don Lewis wrote: >>> On 29 Sep, Matthias Seidel wrote: That might explain why I have never seen a working WikiPublisher in the last releases. (Since at least 4.1.2 we build with that option on Windows) The question is: Do we need to build with that option if no one missed the plugin? >>> I've never tried to use it, so I don't know if it works or not. >>> >> Currently in version 4.1.3 the send to MediaWiki option does not work. >> My SWAG is that the Sun Wiki Publisher Extension was never updated to >> work with the API changes introduced with the 4.0.0 Release. > > Confirmed (also for 4.1.4 RC4) > > However it can still be installed as an extension: > https://extensions.openoffice.org/en/project/sun-wiki-publisher > > Last time I tried it the "send to" option was there, but I never tested > further... > > Matthias > Mathias; It is the extension that I tested and it does not work. There were API changes introduced in AOO Version 4.0.0 that were most likely never updated in the extension. It is the extension that adds to MediaWiki into File/Send. Regards Keith >> It would be nice this were fixed as it would be a great aid in writing >> documentation. >> >> regards >> Keith >> >> > > signature.asc Description: OpenPGP digital signature
[CLOSED] Was: Re: [VOTE] Release Apache OpenOffice 4.1.4-RC4 as GA
After waiting giving us a bit more than the required and normal 72 hours, we have plenty more than the required 3 +1 (binding) votes. As such, I call the Vote CLOSED with the RESULT that the Vote Passes!! 4.1.4-RC4 will be released as GA ! Thanks to all who helped in every and all ways in getting this puppy out! > On Sep 30, 2017, at 3:54 PM, Jim Jagielski wrote: > > I am calling a VOTE on releasing Apache OpenOffice 4.1.4-RC4 > as GA!! > > You can find these gems at: > > https://dist.apache.org/repos/dist/dev/openoffice/4.1.4-RC4/ > > The vote will last at least the normal 72 hours. > > Cheers! > -- > Jim Jagielski > On behalf of the Apache OpenOffice Project > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: servlet-api.jar
Am 04.10.2017 um 17:42 schrieb Keith N. McKenna: > On 9/30/2017 8:42 AM, Don Lewis wrote: >> On 29 Sep, Matthias Seidel wrote: >>> That might explain why I have never seen a working WikiPublisher in the >>> last releases. >>> (Since at least 4.1.2 we build with that option on Windows) >>> >>> The question is: Do we need to build with that option if no one missed >>> the plugin? >> I've never tried to use it, so I don't know if it works or not. >> > Currently in version 4.1.3 the send to MediaWiki option does not work. > My SWAG is that the Sun Wiki Publisher Extension was never updated to > work with the API changes introduced with the 4.0.0 Release. Confirmed (also for 4.1.4 RC4) However it can still be installed as an extension: https://extensions.openoffice.org/en/project/sun-wiki-publisher Last time I tried it the "send to" option was there, but I never tested further... Matthias > It would be nice this were fixed as it would be a great aid in writing > documentation. > > regards > Keith > > smime.p7s Description: S/MIME Cryptographic Signature
Re: servlet-api.jar
On 9/30/2017 8:42 AM, Don Lewis wrote: > On 29 Sep, Matthias Seidel wrote: >> That might explain why I have never seen a working WikiPublisher in the >> last releases. >> (Since at least 4.1.2 we build with that option on Windows) >> >> The question is: Do we need to build with that option if no one missed >> the plugin? > > I've never tried to use it, so I don't know if it works or not. > Currently in version 4.1.3 the send to MediaWiki option does not work. My SWAG is that the Sun Wiki Publisher Extension was never updated to work with the API changes introduced with the 4.0.0 Release. It would be nice this were fixed as it would be a great aid in writing documentation. regards Keith signature.asc Description: OpenPGP digital signature
Re: Release Apache OpenOffice 4.1.4-RC4 crashes on Mac
On 10/4/2017 3:03 AM, Roberto Galoppini wrote: ... I've just tried this on another Mac, with the very same operating system, and it works. I need to wait until later today to retry on the other machine, let's say in 6 hours from now. ... Given this, and the other reports of it working on Macs, I suggest going ahead with closing the vote 72 hours after it started and proceeding with the release. Meanwhile, perhaps those with Mac skills can work with Roberto Galoppini to try to understand the failure, with a view to discussing it in the release notes. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Release Apache OpenOffice 4.1.4-RC4 crashes on Mac
Works for me. FWIW, I tested on 3 other Macs, none of which were the build server. > On Oct 3, 2017, at 9:25 AM, Roberto Galoppini > wrote: > > I've re-downloaded again, it does not work. Does anyone else have tried > that? I'm really the only one facing problem with this build? > > 2017-10-03 15:04 GMT+02:00 Patricia Shanahan : > >> Did you happen to check keys or do a sumcheck on the download? This is >> sounding like it could be a file that was corrupted somewhere in the build, >> upload, download, install chain. >> >> >> On 10/3/2017 5:13 AM, Roberto Galoppini wrote: >> >>> Double-clicking. >>> >>> 2017-10-03 13:42 GMT+02:00 Jim Jagielski : >>> >>> How do you open it? Dbl-click the Icon? Select it and choose Open? Alt-click Open? On Oct 3, 2017, at 5:51 AM, Roberto Galoppini < > roberto.galopp...@gmail.com> wrote: > > It never launched, actually. It crashes before anything else. > > 2017-10-03 11:24 GMT+02:00 Patricia Shanahan : > > Do you do anything in particular, such as open some type of document, >> before it crashes? >> >> >> On 10/3/2017 12:28 AM, Roberto Galoppini wrote: >> >> I was trying to test >>> Apache_OpenOffice_4.1.4_MacOS_x86-64_install_en-US.dmg but I >>> >> couldn't, it > keeps crashing. >>> >>> Best, >>> >>> Roberto >>> >>> >>> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> >> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Release Apache OpenOffice 4.1.4-RC4 crashes on Mac
Il 04 Ott 2017 00:49, "Andrea Pescetti" ha scritto: On 03/10/2017 Roberto Galoppini wrote: 2017-10-03 19:47 GMT+02:00 Dave Fisher: > >> What do you have in /Users//Library/Application >> Support/OpenOffice/4/user? >> > Nothing, I've simulated a fresh new start. > I see that you had 4.1.3 installed and it was working correctly. You renamed the user profile (to simulate a fresh installation) and installed 4.1.4. How far do you get when you start OpenOffice? For example: - Does the new profile folder get created or OpenOffice dies before creating it? It does that. - Can you see, even for a fraction of a second, the OpenOffice splash screen? No way. Probably it would be best if you can start OpenOffice from a terminal (look for an executable called "soffice"). It should output something to the terminal before dying and that will probably give some clues to understand what the problem is due to and how common we can expect it to be. I've just tried this on another Mac, with the very same operating system, and it works. I need to wait until later today to retry on the other machine, let's say in 6 hours from now. Best, Roberto As I wrote in the vote thread: it might be that this bug is not so common to be considered a blocker, but if it is not due to your particular configuration then we should mention it in the Release Notes once it is clarified/explained. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Release Apache OpenOffice 4.1.4-RC4 crashes on Mac
If I remember it correctly, the last time we had problems with AOO and macOS (Sierra) it had something to do with the graphics card. Maybe there is a difference between Robertos mac and all the others? @Roberto: Just to make sure that it is not the splash screen causing trouble, can you delete (move away) "intro.png" from the (OpenOffice) program folder? AOO then normally starts without splash screen. Regards, Matthias Am 04.10.2017 um 00:48 schrieb Andrea Pescetti: > On 03/10/2017 Roberto Galoppini wrote: >> 2017-10-03 19:47 GMT+02:00 Dave Fisher: >>> What do you have in /Users//Library/Application >>> Support/OpenOffice/4/user? >> Nothing, I've simulated a fresh new start. > > I see that you had 4.1.3 installed and it was working correctly. You > renamed the user profile (to simulate a fresh installation) and > installed 4.1.4. > > How far do you get when you start OpenOffice? For example: > - Does the new profile folder get created or OpenOffice dies before > creating it? > - Can you see, even for a fraction of a second, the OpenOffice splash > screen? > > Probably it would be best if you can start OpenOffice from a terminal > (look for an executable called "soffice"). It should output something > to the terminal before dying and that will probably give some clues to > understand what the problem is due to and how common we can expect it > to be. > > As I wrote in the vote thread: it might be that this bug is not so > common to be considered a blocker, but if it is not due to your > particular configuration then we should mention it in the Release > Notes once it is clarified/explained. > > Regards, > Andrea. > > - > 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: Java 9 32-bit
How relevant is Win 32 bit in future? Shouldn't we offer a Win 64bit in long run? Why move to C#? I do not see the benefit. I would rather opt for a clean modern C++ library design with hourglass APIs. With that we can support all languages people want to use in an extention. And we reduce complexity on our side. No license issues whatsoever is also on the boon fact. All the best Peter Am 3. Oktober 2017 23:18:12 MESZ schrieb Marcus : >Am 03.10.2017 um 22:26 schrieb Kay Schenk: >> On Tue, Oct 3, 2017 at 8:02 AM, Fernando Cassia >wrote: >> >>> On 10/3/17, Damjan Jovanovic wrote: Now what: 1. Ship our own builds of OpenJDK, in matching bitness. Do the >licences (GPL for JVM, GPL-with-classpath-exception for class library) allow >us >>> to? 2. Drop Windows as a platform, since it's the only affected >platform >>> (*nix users usually install distro OpenJDK packages so 32 bit OpenJDK >will be available for 32 bit AOO). We have no Win64 AOO. 3. Drop 32 bit versions of AOO and add Win64 support. 4. Or drop Java entirely and port our Java code to eg. .NET core, >which >>> is liberally licensed and private copies of it can be shipped? Damjan >>> >>> Tempest in a teapot. You do know that Oracle isn't the only provider >>> of Java or OpenJDK, right? >>> >>> Options >>> 1. You can buiild your own 32-bit x86 binary based on OpenJDK >sources. >>> 2. make AOO compile OK on 64 bit thus making AOO a 64-bit Windows >app, >>> able to use any 64-bit JRE (Oracle JRE, IBM JRE, Azul's Zulu JRE) >>> 3. Have you asked Azul Systems if they can provide a 32-bit build? >>> 4. Compile the Java code in AOO as native with Java 9's AOT >compiler? >>> http://openjdk.java.net/jeps/295 >>> >>> Just my $0.02 >>> FC >>> >>> >> As a bystander, I'm wondering just how alarming this news is to >Apache >> OpenOffice. > >IMHO not at all. Java 9 was published just 2 weeks ago. So, it will >take >some time until it's the favorite one. Until then 8 is developer's >darling. > >> The builds are using Java 6 or 7, right? > >With the next larger release (probably 4.2.0) we will use Java 8 which >should last a longer time. Time enough to decide what to do with the >dependency of Java 32-bit. > >> I'm still on 32-bit Linux for now but my default OpenJDK is 1.8. I >can run >> AOO fine with it but must use 1.7 for building. > >Marcus > >- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Java 9 32-bit
Also we could use the java c compiler to build machine code for win32 in future. No license problem if the compiler is part of our build toolset. Am 3. Oktober 2017 23:18:12 MESZ schrieb Marcus : >Am 03.10.2017 um 22:26 schrieb Kay Schenk: >> On Tue, Oct 3, 2017 at 8:02 AM, Fernando Cassia >wrote: >> >>> On 10/3/17, Damjan Jovanovic wrote: Now what: 1. Ship our own builds of OpenJDK, in matching bitness. Do the >licences (GPL for JVM, GPL-with-classpath-exception for class library) allow >us >>> to? 2. Drop Windows as a platform, since it's the only affected >platform >>> (*nix users usually install distro OpenJDK packages so 32 bit OpenJDK >will be available for 32 bit AOO). We have no Win64 AOO. 3. Drop 32 bit versions of AOO and add Win64 support. 4. Or drop Java entirely and port our Java code to eg. .NET core, >which >>> is liberally licensed and private copies of it can be shipped? Damjan >>> >>> Tempest in a teapot. You do know that Oracle isn't the only provider >>> of Java or OpenJDK, right? >>> >>> Options >>> 1. You can buiild your own 32-bit x86 binary based on OpenJDK >sources. >>> 2. make AOO compile OK on 64 bit thus making AOO a 64-bit Windows >app, >>> able to use any 64-bit JRE (Oracle JRE, IBM JRE, Azul's Zulu JRE) >>> 3. Have you asked Azul Systems if they can provide a 32-bit build? >>> 4. Compile the Java code in AOO as native with Java 9's AOT >compiler? >>> http://openjdk.java.net/jeps/295 >>> >>> Just my $0.02 >>> FC >>> >>> >> As a bystander, I'm wondering just how alarming this news is to >Apache >> OpenOffice. > >IMHO not at all. Java 9 was published just 2 weeks ago. So, it will >take >some time until it's the favorite one. Until then 8 is developer's >darling. > >> The builds are using Java 6 or 7, right? > >With the next larger release (probably 4.2.0) we will use Java 8 which >should last a longer time. Time enough to decide what to do with the >dependency of Java 32-bit. > >> I'm still on 32-bit Linux for now but my default OpenJDK is 1.8. I >can run >> AOO fine with it but must use 1.7 for building. > >Marcus > >- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
