Re: WikiPublisher extension (was Re: servlet-api.jar)

[Andrea Pescetti]

Guy Waterval wrote:

I do not know if such a collaboration is allowed
by Apache


No problem. Apache won't pay developers directly, but it doesn't forbid 
that developers are paid of course! So whoever is the sponsor, there is 
no problem as long as the code is under the Apache License version 2 and 
the contributor is willing to see it used in OpenOffice. And actually, 
if this is still going to be an extension, we don't even need this.


This is a good task also for our recruitment list.

Regards,
  Andrea.

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

Re: WikiPublisher extension (was Re: servlet-api.jar)

[Guy Waterval]

Hi Keith,


2017-10-14 5:52 GMT+02:00 Keith N. McKenna :

[...]

What is relevant is that having it
> functional would be a good enhancement to the product as well as
> provicing the potential of benefit to the project.
>

I entirely agree with your position an I have a suggestion.
Why not to try a win-win with The Wikimedia Foundation ?
Due to the decrease of their number of editors, they absolutely need new
ones and try to find them, among others, in the educational area, where
AOO/LibO are often used by students.
A good functionality in AOO allowing to edit wiki articles could also raise
the visibility and use of AOO.
Perhaps also an opportunity for some coders of the AOO project, since WMF
often offers financial support to projects which help them to
maintain/develop their encyclopedy.
Only my personal opinion. I do not know if such a collaboration is allowed
by Apache, but perhaps it could boost the AOO project and its visibility.

Cheers

>
> gw
>
>

Re: WikiPublisher extension (was Re: servlet-api.jar)

[FR web forum]

>Do we have a bug # for this longstanding issue? We still advertise this
>feature but it is not working since 4.1.0 (?).

https://bz.apache.org/ooo/buglist.cgi?quicksearch=wikipublisher
But none specific to this problem

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

Re: WikiPublisher extension (was Re: servlet-api.jar)

[Keith N. McKenna]

On 10/13/2017 2:43 PM, Matthias Seidel wrote:
> Am 06.10.2017 um 03:40 schrieb Don Lewis:
> 
>> I think I understand what is going wrong with WikiPublisher on Windows.
>> The FreeBSD port sets the --with-system-apache-commons=yes, and lists
>> the all the commons-*.jar files as dependencies, so when AOO is
>> installed on a machine, the commons-*.jar files will also get installed
>> because they are dependencies.
>>
>> On Windows, and probably Linux and Mac, we don't set
>> --with-system-apache-commons=yes.  Instead we rely on bootstrap to
>> download the source for these .jar files and we build the actual .jar
>> files during the build.  Only commons-lang.jar is needed for the base
>> package and it gets packaged along with the rest of the AOO files.  The
>> WikiPublisher extension also requires commons-codec.jar,
>> commons-httpclient.jar, and commons-logging.jar, but these don't get
>> packaged along with the AOO files, and they also don't get packaged into
>> the .oxt file for the extension.  The only .jar files bundled with the
>> extension are help.jar and mediawiki.jar.
> 
> Do we have a bug # for this longstanding issue? We still advertise this
> feature but it is not working since 4.1.0 (?).
> 
> I really would love to have it back working in 4.2.0.
> 
> Matthias
> 
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>
> 
> 
A little further testing on my Windows 7 machine shows that neither
OpenOffice.org version 3.3 nor Apache OpenOffice version 3.4.1 installed
the MediaWiki code by default. However installing the Sun MediaWike
extension in AOO 3.4.1 got further towards working than it did in AOO 4.1.3.

In 4.1.3 when you go to options and try to add the connection to the
OpenOffice wiki it just grays out the input box and never tries to make
the connection. With 3.4.1 it attempts to make a connection and fails
with the error message A connection could not be created because the URL
is invalid. This corresponds to
https://bz.apache.org/ooo/show_bug.cgi?id=115449. Since the wiki uses a
redirect to https this could be the reason it does not work in 4.1.3 or
4.1.4.

This leads me to believe that the extension code on the extension site
that was last updated in 2009 may have fallen victim to the API changes
with AOO v4.0.0.

I also would like to see this working in AOO 4.2.0 as I see it as a way
to possibly rejuvenate the documentation effort. Whether it is done as
an update to the external extension or done inside the source is
irrelevant from my point of view. What is relevant is that having it
functional would be a good enhancement to the product as well as
provicing the potential of benefit to the project.

Regards
Keith



signature.asc
Description: OpenPGP digital signature

Re: WikiPublisher extension (was Re: servlet-api.jar)

[Matthias Seidel]

Am 06.10.2017 um 03:40 schrieb Don Lewis:

> I think I understand what is going wrong with WikiPublisher on Windows.
> The FreeBSD port sets the --with-system-apache-commons=yes, and lists
> the all the commons-*.jar files as dependencies, so when AOO is
> installed on a machine, the commons-*.jar files will also get installed
> because they are dependencies.
>
> On Windows, and probably Linux and Mac, we don't set
> --with-system-apache-commons=yes.  Instead we rely on bootstrap to
> download the source for these .jar files and we build the actual .jar
> files during the build.  Only commons-lang.jar is needed for the base
> package and it gets packaged along with the rest of the AOO files.  The
> WikiPublisher extension also requires commons-codec.jar,
> commons-httpclient.jar, and commons-logging.jar, but these don't get
> packaged along with the AOO files, and they also don't get packaged into
> the .oxt file for the extension.  The only .jar files bundled with the
> extension are help.jar and mediawiki.jar.

Do we have a bug # for this longstanding issue? We still advertise this
feature but it is not working since 4.1.0 (?).

I really would love to have it back working in 4.2.0.

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

Re: WikiPublisher extension (was Re: servlet-api.jar)

[Don Lewis]

On  4 Oct, To: dev@openoffice.apache.org wrote:
> 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.

I think I understand what is going wrong with WikiPublisher on Windows.

The FreeBSD port sets the --with-system-apache-commons=yes, and lists
the all the commons-*.jar files as dependencies, so when AOO is
installed on a machine, the commons-*.jar files will also get installed
because they are dependencies.

On Windows, and probably Linux and Mac, we don't set
--with-system-apache-commons=yes.  Instead we rely on bootstrap to
download the source for these .jar files and we build the actual .jar
files during the build.  Only commons-lang.jar is needed for the base
package and it gets packaged along with the rest of the AOO files.  The
WikiPublisher extension also requires commons-codec.jar,
commons-httpclient.jar, and commons-logging.jar, but these don't get
packaged along with the AOO files, and they also don't get packaged into
the .oxt file for the extension.  The only .jar files bundled with the
extension are help.jar and mediawiki.jar.



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

WikiPublisher extension (was Re: servlet-api.jar)

[Don Lewis]

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: servlet-api.jar

[Keith N. McKenna]

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

[Don Lewis]

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

[Don Lewis]

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: servlet-api.jar

[Keith N. McKenna]

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

[Matthias Seidel]

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

[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

>> 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: servlet-api.jar

[Matthias Seidel]

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

[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.

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: servlet-api.jar

[Matthias Seidel]

I am just doing a build from branch with that option to see if the
plugin works...

Am 30.09.2017 um 14:42 schrieb Don Lewis:
> 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.
>
> I think I've figured out what is going on.  The reason that tomcat isn't
> getting built when --enable-wiki-publisher is specified is that the
> swext module doesn't list tomcat as a dependency.  That said, I didn't
> find any references to servlet-api.jar in the swext module.  The only
> references that I found in the tree were in the commons-logging makefile
> in the apache-commons module.  As near as I can tell, servlet-api.jar is
> an optional dependency for unit testing.
>
> The FreeBSD port specifies --with-system-apache-commons=yes, so I think
> it should be fine as is.  The ports that bundle apache-commons are
> probably unlikely to specify an external servlet-api.jar, and I think
> they should work OK because apache-commons lists tomcat as a dependency
> and configure adds TOMCAT to $BUILD_TYPE.
>
> I think that the code in configure that handles
> --with-system-servlet-api is misplaced.  I think it should be in the
> section that handles the --without-system-apache-commons case.  If a
> user specifies --with-system-servlet-api, then running tomcat should not
> be necessary when building the bundled apache-commons .jar files.  The
> only reason that I can think of for why it ended up here is that the
> WikiPublisher was the first in-tree consumer of commons-logging.
>
>
> -
> 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: servlet-api.jar

[Don Lewis]

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.

I think I've figured out what is going on.  The reason that tomcat isn't
getting built when --enable-wiki-publisher is specified is that the
swext module doesn't list tomcat as a dependency.  That said, I didn't
find any references to servlet-api.jar in the swext module.  The only
references that I found in the tree were in the commons-logging makefile
in the apache-commons module.  As near as I can tell, servlet-api.jar is
an optional dependency for unit testing.

The FreeBSD port specifies --with-system-apache-commons=yes, so I think
it should be fine as is.  The ports that bundle apache-commons are
probably unlikely to specify an external servlet-api.jar, and I think
they should work OK because apache-commons lists tomcat as a dependency
and configure adds TOMCAT to $BUILD_TYPE.

I think that the code in configure that handles
--with-system-servlet-api is misplaced.  I think it should be in the
section that handles the --without-system-apache-commons case.  If a
user specifies --with-system-servlet-api, then running tomcat should not
be necessary when building the bundled apache-commons .jar files.  The
only reason that I can think of for why it ended up here is that the
WikiPublisher was the first in-tree consumer of commons-logging.


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

Re: servlet-api.jar

[Matthias Seidel]

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?

Matthias

Am 29.09.2017 um 10:42 schrieb Don Lewis:
> If we enable the mediawiki option but don't specify
> --with-servlet-api-jar, then configure selects an internal copy of
> servlet-api.jar and appends TOMCAT to BUILD_TYPE, but the build never
> attempts to build the tomcat module (which will generate a copy of
> servlet-api.jar) or bundle this .jar file with the extension.  The build
> appears to succeed, but I suspect that the extension will not be
> functional without the .jar file.
>
>
>
> -
> 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