Moin,
I have the SDBC interface of release 4.2.0-dev-m1
tested with different database servers.
In addition to the respective JDBC connection, an ODBC connection was also
tested.
Here is a supplement to the link on MariaDB:
Using MYSQL-driver 8.0 the connection runs cleanly.
I was able to find
Hi Jan,
Am 23.05.19 um 00:25 schrieb Jan-Christian Wienandt:
> Moin,
>
>
>
> I have the SDBC interface of release 4.2.0-dev-m1
>
> tested with different database servers.
>
>
>
> In addition to the respective JDBC connection, an ODBC connection was al
Moin,
I have the SDBC interface of release 4.2.0-dev-m1
tested with different database servers.
In addition to the respective JDBC connection, an ODBC connection was also
tested.
The result is available at the following link.
<http://www.wienandt.de/download/t
Moin Jan,
Am 21.05.19 um 21:52 schrieb Jan-Christian Wienandt:
> Moin Liste,
>
>
>
> ich habe die neue SDBC-Schnittstelle mit unterschiedlichen Datenbankservern
> getestet.
>
> Die Tests liefen ausschließlich unter Windows über JDBC und ODBC.
>
>
>
> Das Ergebnis findet Ihr hier:
>
>
>
>
Moin Liste,
ich habe die neue SDBC-Schnittstelle mit unterschiedlichen Datenbankservern
getestet.
Die Tests liefen ausschließlich unter Windows über JDBC und ODBC.
Das Ergebnis findet Ihr hier:
http://www.wienandt.de/download/test/Testing_SDBC.zip
Vielleicht gibt es da noch Ideen
yeah... for some reason, openoffice.lst is not parsed (or the results of such
parsing) are not available at some stages of the build process, meaning that
the Dev and Beta specific names are not honored. I'm trying to various things
but none are elegant :(
> On Apr 5, 2019, at 1:39 PM,
Hi Jim,
Am 04.04.19 um 20:14 schrieb Jim Jagielski:
> Linux 64bit builds for en-US and de (both dpkg and rpm) can
> be found at:
>
> http://home.apache.org/~jim/AOO-builds/Dev-r1856914/
>
> These SHOULD fix the desktop integration issues with Linux
> builds when building Dev and/or Beta
> On Apr 4, 2019, at 5:31 PM, Pedro Lino wrote:
>
> Hi Jim, all
>
>> Linux 64bit builds for en-US and de (both dpkg and rpm) can
>> be found at:
>>
>>http://home.apache.org/~jim/AOO-builds/Dev-r1856914/
>>
>> These SHOULD fix the desktop integration issues with Linux
>> builds when
Hi Jim, all
> Linux 64bit builds for en-US and de (both dpkg and rpm) can
> be found at:
>
> http://home.apache.org/~jim/AOO-builds/Dev-r1856914/
>
> These SHOULD fix the desktop integration issues with Linux
> builds when building Dev and/or Beta releases.
Unfortunately it is not
Linux 64bit builds for en-US and de (both dpkg and rpm) can
be found at:
http://home.apache.org/~jim/AOO-builds/Dev-r1856914/
These SHOULD fix the desktop integration issues with Linux
builds when building Dev and/or Beta releases.
Please try asap and let me know how these work. TIA!
> On Apr 3, 2019, at 1:23 PM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 03.04.19 um 17:03 schrieb Jim Jagielski:
>> Do our Betas implement desktop integration?
> I really don't know (for Linux), I only tested Beta builds on Windows.
>> There is a var in openoffice.lst called
Hi Jim,
Am 03.04.19 um 17:03 schrieb Jim Jagielski:
> Do our Betas implement desktop integration?
I really don't know (for Linux), I only tested Beta builds on Windows.
> There is a var in openoffice.lst called ADDSYSTEMINTEGRATION which
> is set to 1 for real builds and 0 for Beta builds and
>
Do our Betas implement desktop integration? There is
a var in openoffice.lst called ADDSYSTEMINTEGRATION which
is set to 1 for real builds and 0 for Beta builds and
missing for Dev builds.
-
To unsubscribe, e-mail:
Hi Jim,
Am 02.04.19 um 14:18 schrieb Jim Jagielski:
> Any feedback yet?
Unfortunately my changes didn't solve this issue. I am out of ideas...
What is missing from the tar.gz (full installation) is a folder called
"desktop-integration" containing something like "openoffice ...
-debian-menus_
Any feedback yet?
> On Apr 1, 2019, at 10:57 AM, Jim Jagielski wrote:
>
> Linux64 bit builds for de and en-US (dpkg and rpm) can be found at
>
>http://home.apache.org/~jim/AOO-builds/
>
> these are builds of AOO42X HEAD and just to check that
> desktop integration is fixed.
>
>
Am 01.04.19 um 13:01 schrieb Jim Jagielski:
> Which languages should I post for people to try?
My personal preferences would be en-US and de.
Matthias
>
>> On Mar 31, 2019, at 10:59 AM, Matthias Seidel
>> wrote:
>>
>> Am 31.03.19 um 16:56 schrieb Jim Jagielski:
>>> Give me a few hours :)
>>
Which languages should I post for people to try?
> On Mar 31, 2019, at 10:59 AM, Matthias Seidel
> wrote:
>
> Am 31.03.19 um 16:56 schrieb Jim Jagielski:
>> Give me a few hours :)
> No hurry, I am just curious if it works... ;-)
>>
>>
Am 31.03.19 um 16:56 schrieb Jim Jagielski:
> Give me a few hours :)
No hurry, I am just curious if it works... ;-)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail:
Give me a few hours :)
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Hi Jim,
Am 29.03.19 um 12:23 schrieb Jim Jagielski:
> Does the lack of desktop integration in m1 mean that this dev release is DOA?
Can you do a Linux build based on r1856556 and see if the desktop
integration is included now?
https://svn.apache.org/viewvc?view=revision=1856556
Regards,
Hi Peter,
Am 30.03.19 um 14:13 schrieb Peter Kovacs:
> added the below List to the cWiki.
>
> I add a connection from the 4.2.0 Release page. Maybe we can create an
> overview of tasks related.
Good idea!
Should we also add the most annoying bugs from Bugzilla there?
Matthias
>
>
added the below List to the cWiki.
I add a connection from the 4.2.0 Release page. Maybe we can create an
overview of tasks related.
https://cwiki.apache.org/confluence/display/OOOUSERS/Open+List+from+Discussion
On 30.03.19 11:09, Damjan Jovanovic wrote:
> 1. Library audit.
> 1.1 Did we lose or
Hi Damjan,
Am 30.03.19 um 11:09 schrieb Damjan Jovanovic:
> >From my email on 15 February 2019:
>
> My own release checklist would include:
> 1. Library audit.
> 1.1 Did we lose or gain any public symbols in our libraries since the
> 4.1.0? Gbuild requires explicit export instead of exporting
>From my email on 15 February 2019:
My own release checklist would include:
1. Library audit.
1.1 Did we lose or gain any public symbols in our libraries since the
4.1.0? Gbuild requires explicit export instead of exporting everything and
then possibly controlling visibility with a .map file, so
Hello
Am 29. März 2019 19:40:47 MEZ schrieb Damjan Jovanovic :
>I have a lot of experience with desktop integration but am too busy to
>have
>a look.
>
>Also I posted a checklist of things we should do for the release. None
>of
>them are done yet.
Can you please post the list again
Mechtilde
>
Am 29.03.19 um 17:15 schrieb Matthias Seidel:
Am 29.03.19 um 12:23 schrieb Jim Jagielski:
Does the lack of desktop integration in m1 mean that this dev release is DOA?
Not in my (personal) opinion.
After all, this is a developer build and people should know how to start
it from commandline
Hi Damjan,
Am 29.03.19 um 19:40 schrieb Damjan Jovanovic:
> I have a lot of experience with desktop integration but am too busy to have
> a look.
I have committed a change to "openoffice.lst" that hopefully fixes this
issue for the Developer build.
>
> Also I posted a checklist of things we
I have a lot of experience with desktop integration but am too busy to have
a look.
Also I posted a checklist of things we should do for the release. None of
them are done yet.
On Fri, Mar 29, 2019 at 1:23 PM Jim Jagielski wrote:
> Does the lack of desktop integration in m1 mean that this
+1
Am 29. März 2019 17:15:50 MEZ schrieb Matthias Seidel
:
>Am 29.03.19 um 12:23 schrieb Jim Jagielski:
>> Does the lack of desktop integration in m1 mean that this dev release
>is DOA?
>
>Not in my (personal) opinion.
>
>After all, this is a developer build and people should know how to
>start
Am 29.03.19 um 12:23 schrieb Jim Jagielski:
> Does the lack of desktop integration in m1 mean that this dev release is DOA?
Not in my (personal) opinion.
After all, this is a developer build and people should know how to start
it from commandline or how to create a shortcut.
Of course we should
IMO we should take it as a first Dev build. See my other comment too
Am 29. März 2019 12:23:15 MEZ schrieb Jim Jagielski :
>Does the lack of desktop integration in m1 mean that this dev release
>is DOA?
>
>
>-
>To unsubscribe,
Does the lack of desktop integration in m1 mean that this dev release is DOA?
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
32 matches
Mail list logo
