from:"Patricia Shanahan"


Thanks. Any views on whether the archive should be private or public?

Alternative volunteer for moderator?

On 9/2/2016 3:22 PM, Andrea Pescetti wrote:

Patricia Shanahan wrote:

If you can send me a pointer to documentation on the correct moderator
tools, I can also do that. How soon can we get the list started?


Request form is here: https://infra.apache.org/officers/mlreq and
requests are usually honored within 48 hours.

You'll have to specify a second moderator. I'm not so inclined to be
one, but if this speeds up things feel free to put my Apache e-mail
address there, at least for the time being (next month or so).


to strike while the iron is hot, and we can get a lot of publicity for
an appeal for developers.


I'm unsure about this. As you have seen in the last 24 hours, visibility
is only given to what the journalist/blogger likes.

Regards,
  Andrea.

-
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: What would OpenOffice NON-retirement involve?


Do we understand the reason for the old version of OSX etc.?

On 9/2/2016 3:48 PM, Jim Jagielski wrote:

The issue, currently, is that the Mac OS X build requires, last I
checked, an extremely old version of OSX, Xcode, et.al. No one
has such a beast laying around.

I have tried creating a VMware Fusion guest but it is difficult
finding all the bits and pieces.

There was some discussion on (re)purchasing a MacMini to serve
as our OSX build machine. I can host it here in my house or
we can plop it in our NOC. Hell, I may just purchase one myself.


On Sep 2, 2016, at 12:20 PM, toki  wrote:

On 02/09/2016 14:59, Phillip Rhodes wrote:


What is the most important thing/things we could be working on?


On your own hardware:

Repeat:
  Build a Mac OS X Binary;
  Fix the error messages you get;
  Write notes about what you did;
  Test the program functionality;
Until it builds properly and all functions work as expected;

Then submit the patches and notes your you wrote to the SVN.


How do we counter the FUD that is already being promulgated in

response to the "retirement" discussion?

At this stage, the only thing that might be adequate, is a release
before the end of the weekend, followed up by a release before New Years.

jonathon

-
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: What would OpenOffice NON-retirement involve?




On 9/2/2016 10:37 AM, Patricia Shanahan wrote:


On 9/2/2016 10:18 AM, Dennis E. Hamilton wrote:




-Original Message- From: Patricia Shanahan
[mailto:p...@acm.org] Sent: Friday, September 2, 2016 09:26 To:
dev@openoffice.apache.org Subject: Re: What would OpenOffice
NON-retirement involve?

...

I would like a special mailing list
recruitm...@openoffice.apache.org, just for signing up and
organizing new developers. No need for them to start with dev@,
especially the less experienced developers. Just send an e-mail to
recruitment@

[orcmid]

We can, of course, add a mailing list.  That does mean we need
moderators and we also need someone to watch the list and figure out
what to do with the offers.


I've already volunteered to mentor and organize volunteers. How that
works would depend on how many volunteers we get.


If you can send me a pointer to documentation on the correct moderator
tools, I can also do that. How soon can we get the list started? I want
to strike while the iron is hot, and we can get a lot of publicity for
an appeal for developers.

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

Re: What would OpenOffice NON-retirement involve?



On 9/2/2016 10:18 AM, Dennis E. Hamilton wrote:




-Original Message- From: Patricia Shanahan
[mailto:p...@acm.org] Sent: Friday, September 2, 2016 09:26 To:
dev@openoffice.apache.org Subject: Re: What would OpenOffice
NON-retirement involve?

On 9/2/2016 7:59 AM, Phillip Rhodes wrote:

OK, counter-point to the other thread... let's talk specifically
about

what

needs to happen next, given that some (plenty|most|all|???) of us
want

this

project to continue moving forward.

What has to happen next?  What is the most important thing/things
we

could

be working on?  What could I do *right now* to help move things
in a

positive

direction?

How can we attract more developers?  How do we counter the FUD
that is already being promulgated in response to the "retirement"
discussion? etc...


The "other thread" is actually liberating. Let's go public with the
risk that AOO will be shut down, despite the wishes and best
efforts of its remaining developers.

[orcmid]

I think that is a great approach, Patricia.



I would like to see every possible medium used to present one
message: "AOO is at serious risk of dying, unless we get more
volunteer developers, especially C++ programmers."

I know we need other skills as well, but I don't want to dilute or
complicate that message.

I would like a special mailing list
recruitm...@openoffice.apache.org, just for signing up and
organizing new developers. No need for them to start with dev@,
especially the less experienced developers. Just send an e-mail to
recruitment@

[orcmid]

We can, of course, add a mailing list.  That does mean we need
moderators and we also need someone to watch the list and figure out
what to do with the offers.


I've already volunteered to mentor and organize volunteers. How that 
works would depend on how many volunteers we get.




Something we can easily do already [as well], and we have not acted
on it, is add the ASF Help Wanted widget in a number of places.  We
can then populate the database the Widget uses with specific requests
for assistance on Apache OpenOffice.  The benefit is that (1) these
can be focused tasks, (2) the Help Wanted will also be visible in
other places among the Help Wanted from other projects, and (3) the
Help Wanted item provides enough properties about skill requirements
and nature of the task, as well as a link to details that help the
interested volunteer find details enough to decide how to
contribute.

Addition of the help-wanted widget can be done immediately.

I have another promised activity for this US Holiday weekend, but I
will dig into that too.

- Dennis




The message should go out every way it can:

us...@openoffice.apache.org OpenOffice forums Press release
memb...@apache.org d...@community.apache.org

We should also strengthen the current download page appeal for
developers to state the risk of shut down.


-



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: What would OpenOffice NON-retirement involve?

I understand your problem. Until now, I have only owned one Apple 
desktop, the Apple II I bought in 1980. I took a dislike to Macs the 
first time I tried one.


On 9/2/2016 10:32 AM, Phillip Rhodes wrote:

No doubt.  My problem on this is that I hate Apple, Macintosh, and
everything to do with their proprietary, closed-source, walled-garden
ecosystem.  I could possibly pinch my nose shut and buy a cheap Mac to help
with AOO development, but there's a limit to how much I'd be willing to
spend.


Phil


This message optimized for indexing by NSA PRISM

On Fri, Sep 2, 2016 at 1:26 PM, Patricia Shanahan <p...@acm.org> wrote:




On 9/2/2016 10:21 AM, Phillip Rhodes wrote:


On Fri, Sep 2, 2016 at 1:18 PM, Patricia Shanahan <p...@acm.org> wrote:

Looking at it the other way round, for under $500 I could have a Mac Mini

with 500 GB hard disk and Mac OS Yosemite delivered on Sunday. That is
less
than 10 months of macincloud.





Is such a machine sufficiently powerful for building AOO, and doing so in
a
reasonable period of time?



I don't know, but it is more powerful than the macinbcloud offering. If I
were buying myself a Mac, I would go for a more expensive system with more
cores, bigger memory, and a terabyte-scale disk.


-
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: What would OpenOffice NON-retirement involve?




On 9/2/2016 10:21 AM, Phillip Rhodes wrote:

On Fri, Sep 2, 2016 at 1:18 PM, Patricia Shanahan <p...@acm.org> wrote:


Looking at it the other way round, for under $500 I could have a Mac Mini
with 500 GB hard disk and Mac OS Yosemite delivered on Sunday. That is less
than 10 months of macincloud.




Is such a machine sufficiently powerful for building AOO, and doing so in a
reasonable period of time?


I don't know, but it is more powerful than the macinbcloud offering. If 
I were buying myself a Mac, I would go for a more expensive system with 
more cores, bigger memory, and a terabyte-scale disk.


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

Re: What would OpenOffice NON-retirement involve?

Looking at it the other way round, for under $500 I could have a Mac 
Mini with 500 GB hard disk and Mac OS Yosemite delivered on Sunday. That 
is less than 10 months of macincloud.


On 9/2/2016 10:11 AM, Phillip Rhodes wrote:

That's unfortunate.  And Apple doesn't allow running OSX under a VM on
another
OS do they?


Phil


This message optimized for indexing by NSA PRISM

On Fri, Sep 2, 2016 at 1:09 PM, Patricia Shanahan <p...@acm.org> wrote:


I looked at some of those services a few weeks ago. For the ones I
found, the relatively inexpensive options did not have the capability of
building software, let alone the capacity for build a substantial body
of software. The options with the capability and capacity would cost
more than a Mac Mini over a few months.

For example, for macincloud we would need the "Dedicated Server" plan
($49+) with added "Optional Build Server Plan". Even their maximum
upgrade of 250 GB would not be enough for AOO building.

The conclusion I reached was that if I were going to do any Mac
development it would take less of my time and energy to buy one of the
more powerful Macs and manage it directly.




On 9/2/2016 9:53 AM, Phillip Rhodes wrote:


Sadly, I don't own a Mac.  I use one at work, but all of my personal
hardware
is PC based, running Linux.

I wonder if it would work to use something like this:

http://www.macincloud.com/

Anybody have any experience with something like that?


Phil


This message optimized for indexing by NSA PRISM

On Fri, Sep 2, 2016 at 12:20 PM, toki <toki.kant...@gmail.com> wrote:

On 02/09/2016 14:59, Phillip Rhodes wrote:


What is the most important thing/things we could be working on?




On your own hardware:

Repeat:
   Build a Mac OS X Binary;
   Fix the error messages you get;
   Write notes about what you did;
   Test the program functionality;
Until it builds properly and all functions work as expected;

Then submit the patches and notes your you wrote to the SVN.

How do we counter the FUD that is already being promulgated in



response to the "retirement" discussion?

At this stage, the only thing that might be adequate, is a release
before the end of the weekend, followed up by a release before New Years.

jonathon

-
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: What would OpenOffice NON-retirement involve?




On 9/2/2016 10:09 AM, Patricia Shanahan wrote:

I looked at some of those services a few weeks ago. For the ones I
found, the relatively inexpensive options did not have the capability of
building software, let alone the capacity for build a substantial body
of software. The options with the capability and capacity would cost
more than a Mac Mini over a few months.

For example, for macincloud we would need the "Dedicated Server" plan
($49+) with added "Optional Build Server Plan". Even their maximum
upgrade of 250 GB would not be enough for AOO building.


I'm not being quite fair there. I keep multiple versions of AOO around, 
and can afford disk space. We might be able to make do with the basic 50 
GB of disk space if managed the space more carefully.




The conclusion I reached was that if I were going to do any Mac
development it would take less of my time and energy to buy one of the
more powerful Macs and manage it directly.



On 9/2/2016 9:53 AM, Phillip Rhodes wrote:

Sadly, I don't own a Mac.  I use one at work, but all of my personal
hardware
is PC based, running Linux.

I wonder if it would work to use something like this:

http://www.macincloud.com/

Anybody have any experience with something like that?


Phil


This message optimized for indexing by NSA PRISM

On Fri, Sep 2, 2016 at 12:20 PM, toki <toki.kant...@gmail.com> wrote:


On 02/09/2016 14:59, Phillip Rhodes wrote:


What is the most important thing/things we could be working on?


On your own hardware:

Repeat:
   Build a Mac OS X Binary;
   Fix the error messages you get;
   Write notes about what you did;
   Test the program functionality;
Until it builds properly and all functions work as expected;

Then submit the patches and notes your you wrote to the SVN.


How do we counter the FUD that is already being promulgated in

response to the "retirement" discussion?

At this stage, the only thing that might be adequate, is a release
before the end of the weekend, followed up by a release before New
Years.

jonathon

-
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: What would OpenOffice NON-retirement involve?


I looked at some of those services a few weeks ago. For the ones I
found, the relatively inexpensive options did not have the capability of
building software, let alone the capacity for build a substantial body
of software. The options with the capability and capacity would cost
more than a Mac Mini over a few months.

For example, for macincloud we would need the "Dedicated Server" plan
($49+) with added "Optional Build Server Plan". Even their maximum
upgrade of 250 GB would not be enough for AOO building.

The conclusion I reached was that if I were going to do any Mac
development it would take less of my time and energy to buy one of the
more powerful Macs and manage it directly.



On 9/2/2016 9:53 AM, Phillip Rhodes wrote:

Sadly, I don't own a Mac.  I use one at work, but all of my personal
hardware
is PC based, running Linux.

I wonder if it would work to use something like this:

http://www.macincloud.com/

Anybody have any experience with something like that?


Phil


This message optimized for indexing by NSA PRISM

On Fri, Sep 2, 2016 at 12:20 PM, toki  wrote:


On 02/09/2016 14:59, Phillip Rhodes wrote:


What is the most important thing/things we could be working on?


On your own hardware:

Repeat:
   Build a Mac OS X Binary;
   Fix the error messages you get;
   Write notes about what you did;
   Test the program functionality;
Until it builds properly and all functions work as expected;

Then submit the patches and notes your you wrote to the SVN.


How do we counter the FUD that is already being promulgated in

response to the "retirement" discussion?

At this stage, the only thing that might be adequate, is a release
before the end of the weekend, followed up by a release before New Years.

jonathon

-
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: What would OpenOffice NON-retirement involve?


On 9/2/2016 7:59 AM, Phillip Rhodes wrote:

OK, counter-point to the other thread... let's talk specifically about what
needs to happen next, given that some (plenty|most|all|???) of us want this
project to
continue moving forward.

What has to happen next?  What is the most important thing/things we could
be
working on?  What could I do *right now* to help move things in a positive
direction?

How can we attract more developers?  How do we counter the FUD that is
already being promulgated in response to the "retirement" discussion?
 etc...


The "other thread" is actually liberating. Let's go public with the risk 
that AOO will be shut down, despite the wishes and best efforts of its 
remaining developers.


I would like to see every possible medium used to present one message: 
"AOO is at serious risk of dying, unless we get more volunteer 
developers, especially C++ programmers."


I know we need other skills as well, but I don't want to dilute or 
complicate that message.


I would like a special mailing list recruitm...@openoffice.apache.org, 
just for signing up and organizing new developers. No need for them to 
start with dev@, especially the less experienced developers. Just send 
an e-mail to recruitment@


The message should go out every way it can:

us...@openoffice.apache.org
OpenOffice forums
Press release
memb...@apache.org
d...@community.apache.org

We should also strengthen the current download page appeal for 
developers to state the risk of shut down.



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

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)


On 9/2/2016 5:52 AM, RA Stehmann wrote:

Am 02.09.2016 um 14:14 schrieb Jim Jagielski:



What is obvious is that the AOO project cannot support, at the present
time, being an end-user focused effort. I would suggest we focus on not
being one, but instead being a framework or library that can be consumed
by actual end-user implementations.



If AOO is not an end-user focused project a lot of people will leave
this community because they will be useless. People who are doing
end-user support, who are doing end-user documentation and are doing
what we call "marketing" etc.

Also people, who build binaries are obsolet. Only coders will be needed
and I don't know, whether all remained will stay under that conditions.


I certainly won't stay. I am interested in keeping the end user 
application viable. The library/framework idea does not interest me at all.


This discussion has a serious self fulfilling prophecy downside. The 
less ASF's commitment to AOO, the less my commitment is. I had been 
thinking of buying a Mac and learning to do builds on it. That is an 
investment of time, energy, and a small amount of money. Why do it, if 
AOO is just going to get shut down anyway?


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

Re: compiler warnings when building OpenOffice

2016-09-01 Thread Patricia Shanahan

I need a problem to work on. Would you like me to take a particular 
compiler warning and try to sort it out?


On 9/1/2016 3:29 PM, Don Lewis wrote:

On 29 Aug, Don Lewis wrote:

When building OpenOffice trunk revsion r1758161 as a FreeBSD port on
FreeBSD 12.0-CURRENT with clang 3.8.0, I get the following warnings.
I'm mostly interested in the OpenOffice code and not the bundled
external code, so I specifically built the FreeBSD port it uses
--with-system-foo extensively which minimizes the compilation of third
party code.  The total number of warnings is 5105.

1175 -Wtautological-undefined-compare
 949 -Wunused-private-field
 660 -Wshift-negative-value
 391 -Wunused-parameter
 362 -Wunused-const-variable
 312 -Woverloaded-virtual
 177 -Wunused-variable
 116 -Winfinite-recursion
 109 -Wlogical-op-parentheses
  93 -Wsign-compare
  76 -Wdelete-non-virtual-dtor
  72 -Wint-to-void-pointer-cast
  63 -Wshadow
  55 -Wunused-function
  41 -Wformat
  36 -Wreturn-type-c-linkage
  30 -Wchar-subscripts
  27 -Wdeprecated-declarations
  26 -Wundefined-bool-conversion
  26 -Wsizeof-pointer-memaccess
  26 -Wformat-security
  24 -Wunused-local-typedef
  22 -Wmacro-redefined
  21 -Wswitch
  20 -Wbitwise-op-parentheses
  18 -Winvalid-source-encoding
  13 -Wuninitialized
  11 -Wtautological-compare
  11 -Wlogical-not-parentheses
  11 -Wdangling-else
   9 -Wmismatched-new-delete
   8 -Wimplicit-function-declaration
   8 -Wheader-guard
   8 -Wcomment
   7 -Wtautological-constant-out-of-range-compare
   7 -Wself-assign
   6 -Wunused-value
   6 -Wunneeded-internal-declaration
   6 -Wtautological-pointer-compare
   6 -Wpointer-bool-conversion
   6 -Wparentheses-equality
   6 -Wdynamic-class-memaccess
   6 -Wconstant-conversion
   5 -Wpointer-sign
   4 -Wnull-conversion
   3 -Wunsequenced
   3 -Wreorder
   3 -Wknr-promoted-parameter
   3 -Wint-to-pointer-cast
   2 -Wstrncat-size
   2 -Wstring-compare
   2 -Wsometimes-uninitialized
   2 -Wconstant-logical-operand
   2 -Warray-bounds
   1 -Wunused-comparison
   1 -Wunknown-pragmas
   1 -Wstring-plus-int
   1 -Wpotentially-evaluated-expression
   1 -Wnon-literal-null-conversion
   1 -Wmismatched-tags
   1 -Wincompatible-pointer-types-discards-qualifiers
   1 -Wimplicit-int
   1 -Wignored-qualifiers
   1 -Wformat-extra-args
   1 -Wcompare-distinct-pointer-types
   1 -Wc++11-compat-deprecated-writable-strings


Now down to 2708 warnings.  It'll be slower going from this point
forward because each of the remaining issues will have a much smaller
impact on the warning count that many of the ones I have already fixed.

FWIW, bundled icc is getting to be a significant contributer to the
remaining warnings.

One of the -Wunused-parameter warnings led me to this questionable bit
of code in filter/source/xsltfilter/containerhelper.hxx:

template
inline void forEachMem(FuncType pFunc, ParamType aParam) const
{
forEach( ::boost::bind(pFunc, _1, aParam));
}

template
inline void forEachMem(FuncType pFunc, ParamType1 aParam1, ParamType2 
aParam2) const
{
forEach( ::boost::bind(pFunc, -1, aParam1, aParam2 ));
}

template
inline void forEachMem( FuncType pFunc, ParamType1 aParam1, ParamType2 
aParam2, ParamType3 aParam3 ) const
{
forEach( ::boost::bind(pFunc, _1, aParam2, aParam2, aParam3 ));
}

In the three parameter version of this code, it looks like aParam1
should be used instead of using aParam2 twice.  Also, in the two
parameter version of the code, it looks like _1 should be used instead
of -1.  I haven't had a chance to investigate the possible symptoms of
these errors or how to text the appropriate fix.

 493 -Wunused-private-field
 391 -Wunused-parameter
 366 -Wunused-const-variable
 314 -Woverloaded-virtual
 181 -Wunused-variable
 109 -Wlogical-op-parentheses
  93 -Wsign-compare
  77 -Wdelete-non-virtual-dtor
  72 -Wint-to-void-pointer-cast
  63 -Wshadow
  56 -Wunused-function
  41 -Wformat
  36 -Wreturn-type-c-linkage
  30 -Wchar-subscripts
  27 -Wdeprecated-declarations
  26 -Wundefined-bool-conversion
  26 -Wsizeof-pointer-memaccess
  25 -Wtautological-undefined-compare
  24 -Wunused-local-typedef
  22 -Wmacro-redefined
  21 -Wswitch
  20 -Wbitwise-op-parentheses
  18 -Winvalid-source-encoding
  13 -Wuninitialized
  11 -Wtautological-compare
  11 -Wlogical-not-parentheses
  11 -Wdangling-else
   9 -Wmismatched-new-delete
   8 -Wimplicit-function-declaration
   8 -Wcomment
   7 -Wtautological-constant-out-of-range-compare
   7 -Wself-assign
   7 -Wheader-guard
   6 -Wunused-value
   6 -Wunneeded-internal-declaration
   6 -Wtautological-pointer-compare
   6 -Wpointer-bool-conversion
   6 -Wparentheses-equality
   6 -Wdynamic-class-memaccess
   6 -Wconstant-conversion
   5 -Wpointer-sign
   4 -Wnull-conversion
   3 -Wunsequenced
   3 -Wreorder
   3 -Wknr-promoted-parameter
   3 -Wint-to-pointer-cast
   2 -Wstrncat-size
   2 -Wstring-compare

Re: Putting Windows First ( was RE: null)

2016-08-31 Thread Patricia Shanahan


On 8/31/2016 10:25 AM, Dennis E. Hamilton wrote:




-Original Message- From: Patricia Shanahan
[mailto:p...@acm.org] Sent: Wednesday, July 13, 2016 12:57 To:
dev@openoffice.apache.org Subject: Re: Putting Windows First ( was
RE: null)


[ ... ] [orcmid]

I would like to suggest a way of squeezing out from between the
rock and hard place, and getting more developers:

Separate out the Windows build process. Pick one of the common
IDE's, and create a project file that sets all environment
variables for Windows. Get as close as possible to the step-by-step
build instructions for Windows being:

Check out the source from SVN.

Open the project file in $IDE$.

[orcmid]

I don't think it is necessary to have an IDE commitment.

Everything needed to do a build on Windows can be done with
command-line tools that are part of the Windows SDK.  Other externals
needed for builds can be obtained in Windows versions.  It is how
Visual Studio works -- it spawns command-line operations.


To me, direct use of command line tools feels like an awkward half-way
step between the punch cards I used when I started programming, and the
IDE's I use for most of my programming now.

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

Re: Putting Windows First ( was RE: null)

2016-08-31 Thread Patricia Shanahan



On 8/31/2016 10:25 AM, Dennis E. Hamilton wrote:




-Original Message-
From: Patricia Shanahan [mailto:p...@acm.org]
Sent: Wednesday, July 13, 2016 12:57
To: dev@openoffice.apache.org
Subject: Re: Putting Windows First ( was RE: null)


[ ... ]
[orcmid]

I would like to suggest a way of squeezing out from between the rock and
hard place, and getting more developers:

Separate out the Windows build process. Pick one of the common IDE's,
and create a project file that sets all environment variables for
Windows. Get as close as possible to the step-by-step build instructions
for Windows being:

Check out the source from SVN.

Open the project file in $IDE$.

[orcmid]

I don't think it is necessary to have an IDE commitment.

Everything needed to do a build on Windows can be done with command-line tools 
that are part of the Windows SDK.  Other externals needed for builds can be 
obtained in Windows versions.  It is how Visual Studio works -- it spawns 
command-line operations.

So long as the SVN Working copy has the correct ignore settings, once could 
then create projects if desired, and there might be a way to download a .zip of 
project files that could be expanded into a build slot in the Working copy.  
Although, since most of what is needed is in text and XML files, there is a way 
to do this at a lower level that doesn't require binaries in the source tree.

That should get rid of the CygWin dependency for Windows builds and let the 
available tools work at their best.

I think the bigger challenge is to be able to do incremental builds or even 
build libraries shared within AOO separately as a way to get problems of 
massive clean builds that take hours and don't help localize errors much.  
That's probably the way to build up the Windows build case anyhow.

Note: If one is careful about the filepath rewriting business in CygWin, one 
can execute Windows command-line tools pretty easily, using .bat files as 
bridges -- .bat files execute properly in CygWin and MSys where I have tried 
it, and they will work correctly when used directly via cmd.exe.  That is also 
how one gets environment variables set properly, etc.  (One needs to get around 
a couple of glitches where CygWin and its cousins treat the environment as case 
sensitive but the Windows SDK tools do not.)

And then there's [unit] testing to consider.


There are already unit tests that run in Eclipse.


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

Re: Attention: Courtney

2016-08-26 Thread Patricia Shanahan

Don't worry about all the e-mails. It's a bit like walking into the 
middle of a conversation. I would prefer to establish direct 
communication, not through the list, so that we can work out the best 
way for you to help at this point in time.


You should get two copies of this e-mail, one through the list and the 
other direct. Please let me know whether you get both.


On 8/26/2016 10:39 AM, courtneymc...@roadrunner.com wrote:

Hey Patricia! I'm sorry it took so long to reply. Your email got lost
in the river of emails this subscription sends me everyday! I hate to
say it but I think all of this is too advanced for me. I want to help
but. I just still got lost trying to understand the emails everyone
was sending.

 Patricia Shanahan <p...@acm.org> wrote:

Courtney,

I tried to reply directly to your email three days ago. Please
check whether a message from me got caught in a spam filter etc.

-



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: [DISCUSS] Release 4.2: General Topics

2016-08-23 Thread Patricia Shanahan




On 8/23/2016 12:14 PM, Kay sch...@apache.org wrote:
...

2. Update Java requirement from Java 1.5 to *at least* Java 1.7

I am rather adamant that we change our building requirement to Java 1.7
for all platforms. I will be changing that in our Building Guide today.
Java 1.5 went out of support by Oracle in November, 2009. We use OpenJDK
but I'm sure updates for Java 1.5 through that channel are also no
longer available.
Even Java 1.7 has reached end of life by Oracle for public support as of
April, 2015. To avoid undue issues for some of our current users on
older platforms, I am "OK" with java 1.7. I am fairly confident ALL
users can obtain this for whatever platform they are using.

...

The more important, and more difficult, issue is 32-bit vs 64-bit Java.

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

Debug and gbuild

2016-08-21 Thread Patricia Shanahan


I am getting back into OpenOffice debug under Visual Studio. Last time I
tried that, I needed to manually build the gbuild modules to get symbol
generation.

Has that been automated? If so, what configure and/or build flags should
I be using? If not, any ideas on how to get it automated?

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

Re: configure error


On 8/19/2016 2:57 PM, Don Lewis wrote:
...

Hmn, I see that the error that you are seeing is coming from set_soenv
and not configure.  Did you rerun autoconf to regenerate configure after
the update?

...

A very good question. Reminder-to-self: Use the step-by-step 
instructions rather than relying on memory. Thanks.


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

Re: configure error




On 8/19/2016 12:51 PM, Don Lewis wrote:

On 19 Aug, Patricia Shanahan wrote:

I did an "svn update". Now configure is failing:


*  *
*   Setting up the build environment variables.*
*  *

checking solver path... default
configure: writing config.status
configure: creating ./config.status
config.status: creating set_soenv
config.status: creating Makefile
Possible unintended interpolation of @HAMCREST_CORE_JAR in string at
./set_soenv line 1644.
Global symbol "@HAMCREST_CORE_JAR" requires explicit package name (did
you forget to declare "my @HAMCREST_CORE_JAR"?) at ./set_soenv line 1644.
Execution of ./set_soenv aborted due to compilation errors.


Either disable junit or add --with-hamcrest-core.

This is why the Linux buildbots have been failing recently.


I tried adding the hamcrest option, and it just causes an additional 
message:


configure: WARNING: unrecognized options: --with-hamcrest-core

Maybe I need a different configure version from the one checked in under 
https://svn.apache.org/repos/asf/openoffice/trunk


Here are my full configure parameters:

Patricia@Jan2014Desktop /cygdrive/c/OpenOfficeDev/Trunk/main
$ more run_configure.sh
SDK_PATH="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0"
./configure \
--with-frame-home="$SDK_PATH" \
--with-psdk-home="$SDK_PATH" \
--with-midl-path="$SDK_PATH/bin" \
--disable-directx \
--with-ant-home="/cygdrive/c/ant" \

--with-dmake-url="http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2; 
\


--with-epm-url="http://www.msweet.org/files/project2/epm-3.7-source.tar.gz; 
\

--enable-pch \
--disable-atl \
--disable-activex \
--without-junit \
--with-hamcrest-core \
--with-jdk-home="/cygdrive/c/Program Files (x86)/Java/jdk1.7.0_79"

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

configure error


I did an "svn update". Now configure is failing:


*  *
*   Setting up the build environment variables.*
*  *

checking solver path... default
configure: writing config.status
configure: creating ./config.status
config.status: creating set_soenv
config.status: creating Makefile
Possible unintended interpolation of @HAMCREST_CORE_JAR in string at 
./set_soenv line 1644.
Global symbol "@HAMCREST_CORE_JAR" requires explicit package name (did 
you forget to declare "my @HAMCREST_CORE_JAR"?) at ./set_soenv line 1644.

Execution of ./set_soenv aborted due to compilation errors.





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

Re: Release Manager for 4.2.0?




On 8/19/2016 10:41 AM, Kay sch...@apache.org wrote:


On 01/28/2016 04:06 PM, Andrea Pescetti wrote:

As I wrote a few day ago, in theory it would be good to release
OpenOffice 4.2.0 in February. If it happens a bit later it wouldn't be a
big issue, but I believe that, in the constant balance between periods
where we are focused on talks (internal to OpenOffice and with the
enlarged community) and periods where we are more focused on the
OpenOffice product, it's time to start working again towards a release.

For 4.2.0 we need a Release Manager. I would prefer NOT to be the
Release Manager for 4.2.0 since I'm finding that in this period I can
help more productively with tasks that do not require constant
interaction than with tasks that require a constant monitoring of
project channels.

I am surely available to have a significant role in the 4.2.0 release,
especially with getting localization working again (actually, this mail
also serves as announcement that I am going to ask for higher privileges
on the Pootle server in order to check the translation workflow); but if
someone else steps in as a Release Manager we could deliver earlier.

So if anyone is interested feel free to discuss this on list, or to
contact me off-list if you prefer, or to discuss in person at FOSDEM
next weekend!

Regards,
  Andrea.



Hi all--

I am volunteering to be release manager for 4.2.0.  I have been involved
in all the AOO releases since 3.40, and I'm familiar with the process.
Like all of us involved with the project, I am a volunteer. Due to this,
I can not provide an expected release date. Releases, as we know are
community efforts. We'll release when we feel 4.2.0 is ready.

So, I will let this offer stand the weekend just in case someone else
feels they'd LOVE to do this. If we don't have any objections to my
being the next release manager over the next 72 hours, we can get
started next week ironing out what needs to be done. We will need LOTS
of help!


This looks ideal to me. I would like to learn the release processes, and
try to document them as completely as possible. I would prefer to learn
by watching and helping someone who already knows how it is done, than
by jumping in the deep end and splashing about.

I have an agenda of constructing an emergency release procedure but it
will be easier if I can first see how the normal process goes.

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

FOSDEM hacking

Maybe simplifying the Windows build process for AOO could be a FOSDEM 
hacking challenge?


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

Re: Planning for emergency releases

2016-08-14 Thread Patricia Shanahan


On 8/12/2016 2:14 PM, Dennis E. Hamilton wrote:




-Original Message- From: Patricia Shanahan
[mailto:p...@acm.org]

...

Personally, I would like to treat the last stable release as the
base for emergency fixes. I started out suggesting using the
current patch as an exercise to work through the process for doing
that.

However, I have seen a lot of push back on the idea of ever doing
a release that only has one change.

[orcmid]

Yes.  It might be necessary to do triage - choose highly-vulnerable
platforms, common languages, etc.

And, if we are talking about an unpatched vulnerability with an
exploit in the wild, I don't think the ASF Board will be sympathetic
to our reticence.

I agree that we do need to do fire drills simply to be able to
respond when an emergency arises.


I would prefer to see agreement within the PMC on an emergency release
process, followed by a fire drill to test it. My understanding, from
following bo...@apache.org, is that if the ASF Board ever gets involved,
they will swing hammers not scalpels.

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

Attention: Courtney

2016-08-12 Thread Patricia Shanahan


Courtney,

I tried to reply directly to your email three days ago. Please check 
whether a message from me got caught in a spam filter etc.


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

Re: Planning for emergency releases

2016-08-12 Thread Patricia Shanahan




On 8/12/2016 1:40 PM, Dennis E. Hamilton wrote:

-Original Message- From: Patricia Shanahan
[mailto:p...@acm.org] Sent: Thursday, August 11, 2016 11:07 To:
dev@openoffice.apache.org Subject: Re: Planning for emergency
releases


[ ... ]


Meanwhile, it is interesting for contemplating a ready-to-release
strategy. We would need to pick a step at which to hold a release
that minimizes the time to put in one critical fix and ship it.

[orcmid]

It strikes me that an always-existing candidate for a ready to
release is the last-previous stable release.

The biggest reason is that there only needs to be regression testing,
since it is presumably well-established that said release is stable
and that has been confirmed on the ground by the success of users.

There could be something else that is close, but it strikes me that
would probably be a pending maintenance release that is basically
about bug fixes and any simple things.

I note that, for changing the installer, something we would like to
do, the rebuild of a stable release at least needs to be done and
checked to see that the install produces the same result.  If that
were tested to satisfaction, it would also qualify as a
ready-to-release base without having to be put in the wild.


Personally, I would like to treat the last stable release as the base
for emergency fixes. I started out suggesting using the current patch as
an exercise to work through the process for doing that.

However, I have seen a lot of push back on the idea of ever doing a
release that only has one change.

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

Re: [PACKAGING 4.1.2-patch1 Binaries] (was RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows)

2016-08-12 Thread Patricia Shanahan


On 8/12/2016 12:22 PM, Dennis E. Hamilton wrote:
...

[Anecdotal Side Note: I just discovered that the MD5 hash for the
4.1.2 Windows .exe fails to check on my Windows system because of a
defect in the .md5 file.  For reasons unknown, the md5sum tool that I
have requires exactly two spaces between the hash value and the name
of the file the hash is for.  Once I fiddled around and added the
second space, it all checks.  What is intriguing to me is that this
has not been reported by anyone, which is perhaps of greater concern
than the fact that MD5 is used [;<].


I may have encountered this problem, but just attributed it to my lack
of familiarity with the tools. I had no problem using md5sum to compute
the hash, and it matched the one in the file.

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

Re: Planning for emergency releases

2016-08-11 Thread Patricia Shanahan


On 8/11/2016 10:45 AM, Marcus wrote:

Am 08/10/2016 12:25 AM, schrieb Patricia Shanahan:

On 8/9/2016 3:12 PM, Marcus wrote:
...

we have a documented release process here [1]. Of course it's for a full
release. But for a bugfix (or emergency) release it can be derived and
then shortend.

[1]
https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template




That is the documentation I found before. Looking only at the steps
labeled "Release Manager", I do know how to make announcements on
mailing lists, even if I do sometimes get into autocomplete tangles and
pick the wrong list, and how to run votes.

That leaves

[...]


OK, then it's not what you have searched for. As I don't know the
details that are missing I cannot really help more than this.

Sorry


Don't be. It's a starting point. My next step is going to be to try to
fill in the details, doing step-by-step searches.

Meanwhile, it is interesting for contemplating a ready-to-release
strategy. We would need to pick a step at which to hold a release that
minimizes the time to put in one critical fix and ship it.

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

Re: Planning for emergency releases

2016-08-09 Thread Patricia Shanahan


On 8/9/2016 3:12 PM, Marcus wrote:
...

we have a documented release process here [1]. Of course it's for a full
release. But for a bugfix (or emergency) release it can be derived and
then shortend.

[1]
https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template


That is the documentation I found before. Looking only at the steps
labeled "Release Manager", I do know how to make announcements on
mailing lists, even if I do sometimes get into autocomplete tangles and
pick the wrong list, and how to run votes.

That leaves

"Update RN with new languages"

"Start release blocker mode (aka show stopper mode)"

"Commit changes to reflect the upcoming release:

Version number, build ID, build date+time, copyright year"

(I do know how to commit changes to svn, but not which file or files to 
modify)


"Build the RC"

"Update Wiki page to make the files available

Development Snapshot Build
Make sure the files have the correct access permissions"

"Upload files to Apache Dist/SourceForge

Make sure to set the staging bit for the Beta directory"

"Create a "kid" build:

This helpful and often asked for translation testing.
Announce it on dev@, qa@, l10n@"





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

Re: Planning for emergency releases

2016-08-09 Thread Patricia Shanahan


On 8/9/2016 2:41 PM, Andrea Pescetti wrote:

Patricia Shanahan wrote:

How do we go about getting trained as release manager?


By making a release, or two.


If we only do two or three releases a year, we will only be able to
train release managers are a rate of about two a year. Is that fast
enough to be able to ensure we always have a designated release manager?




Documenting the process in more detail?


You can see the whole process documented everywhere (ASF pages and CWiki
for the 4.1.2 release), but it's a matter of tooling at this stage more
than documentation. Documentation was the main aim of 4.1.2.


Last time I tried finding documentation I found a lot about what steps
were needed, but very little about how to actually do the steps.




I envisage always having a branch or tag, managed by the release
manager, that represents the ready release. An emergency release would
take that branch, add one security fix, and complete the release process.


There is really nothing to invent or to do in a special way here. Our
codebase uses a (more or less) conventional approach. It can be tweaked
and perfected, but there's not much to discuss or change in this respect.

Regards,
  Andrea.

-
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: Planning for emergency releases

2016-08-09 Thread Patricia Shanahan




On 8/9/2016 8:52 AM, Kay sch...@apache.org wrote:



On 08/08/2016 09:26 PM, Patricia Shanahan wrote:

On 8/8/2016 11:14 AM, Marcus wrote:

Am 08/08/2016 07:28 PM, schrieb Andrea Pescetti:

On 07/08/2016 Marcus wrote:

Maybe we are not that far aways from each other. What I want to to
avoid
is to provide hundreads of MBs for a single fix. Of course we can do a
4.1.3 with some collected fixes. As I don't know what is coming in the
future I would not love to see another 4.1.4, 4.1.5, 4.1.6, etc. when
the calendar is still showing 2016. ;-)


The right trade-off would be between two and three releases a year
(including maintenance releases).

Based on history, we've never been -and we are not- in a "release now
since there is a known critical exploit circulating", so the "emergency
release" is not likely to happen often.

It will be enough to be in a permanent "ready to release" mode (where
work is still mostly on the infrastructure side, the rest is OK) and use
this readiness to ship emergency releases in the unlikely case we need
one, and a few maintenance/feature releases from time to time.


it seems we have the same wish with regard to releases. We can just hope
that this can come true.



+1 on "ready to release" mode. However, rather than just hoping it can
come true, I would like to work on a plan to make it come true.



Some ideas about steps:

* an "ongoing" or permanent release manager.


I think several of us should train as release manager, and the role
should be moved around. For example, I can't commit as "permanent"
release manager, or even as release manager for the next year, because I
have vacations planned that will leave me with no access to my home
computers and limited Internet access for two or three weeks at a time.
That should not prevent me from serving as release manager for limited
terms during which I expect to be home.

I do think that there should always be a designated release manager.

How do we go about getting trained as release manager? Documenting the
process in more detail?

Once we get into the ready-to-release mode it will get a lot easier to
train. We will be doing most of the steps regularly, stopping just short
of actually releasing.


* a quick turnarond on issues inclusion. Currently, we take quite a
while with this.


I envisage always having a branch or tag, managed by the release
manager, that represents the ready release. An emergency release would
take that branch, add one security fix, and complete the release process.



This would be at a minimum.

It is not impossible and really not all that difficult to spin off JUST
the rpms or deb packages to deal with specific issues for Linux. This
would be an enhancement to just distributing files as with our current
patches. The same probably can not be said of Windows or Mac, however.




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

Re: Planning for emergency releases

2016-08-08 Thread Patricia Shanahan


On 8/8/2016 11:14 AM, Marcus wrote:

Am 08/08/2016 07:28 PM, schrieb Andrea Pescetti:

On 07/08/2016 Marcus wrote:

Maybe we are not that far aways from each other. What I want to to avoid
is to provide hundreads of MBs for a single fix. Of course we can do a
4.1.3 with some collected fixes. As I don't know what is coming in the
future I would not love to see another 4.1.4, 4.1.5, 4.1.6, etc. when
the calendar is still showing 2016. ;-)


The right trade-off would be between two and three releases a year
(including maintenance releases).

Based on history, we've never been -and we are not- in a "release now
since there is a known critical exploit circulating", so the "emergency
release" is not likely to happen often.

It will be enough to be in a permanent "ready to release" mode (where
work is still mostly on the infrastructure side, the rest is OK) and use
this readiness to ship emergency releases in the unlikely case we need
one, and a few maintenance/feature releases from time to time.


it seems we have the same wish with regard to releases. We can just hope
that this can come true.



+1 on "ready to release" mode. However, rather than just hoping it can
come true, I would like to work on a plan to make it come true.

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

Special project for newcomers

2016-08-08 Thread Patricia Shanahan


There is a current project for which newcomers to the OpenOffice team
may be able to make a particularly valuable contribution. The objective
is to find out whether a set of instructions are usable and work. For
this, being unfamiliar with the background is an advantage.

To participate, you need to subscribe to dev@openoffice.apache.org, if
you have not already done so. Review the archive at
http://mail-archives.apache.org/mod_mbox/openoffice-dev/ and read the
thread with subject "[TESTING] Applying openoffice-4.1.2-patch1 for
Windows". I have quoted the base message, which contains the most
important information, below.

Please report success, failure, questions, suggestions etc.



On 8/2/2016 8:31 PM, Dennis E. Hamilton wrote:
> Testing of an Apache OpenOffice 4.1.2-patch1 procedure is requested.
>
> The files to be used in testing are at
> 
.

>
> The files to be tested and reviewed are
>
>  * README-4.1.2-patch1-apply-Windows.txt
>The description of the procedure for applying a corrected
>library file to installed copies of Apache OpenOffice 4.1.2
>on Windows.  Read this first before deciding to download
>the Zip file and attempting the procedure.
>
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip
>The Zip archive containing the files to be used in the
>procedure.  There is a copy of the README within the
>archive as well.
>
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.asc
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.md5
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.sha256
>Files that provide a digital signature, an MD5 hash,
>and an SHA256 hash that can be used to verify the
>integrity of the download and, in the case of the
>digital signature, the authenticity and accuracy of
>the download.
>
> REQUESTED TESTING
>
>  * [OPTIONAL] If you are able to check any of the .asc,
>.md5, and .sha256 files against the .zip, report any
>difficulties that may have been encountered.
>
>  * If you performed the procedure, report
> * the version of Microsoft Windows and the type of
>   account used (administrator or standard user).
> * report whether the procedure succeeded
> * if the procedure failed or met with difficulties,
>   please summarize the problems and how you over-
>   came any of them
>
>  * [IMPORTANT] Identify any missing, incomplete or
>confusing information in the README.  Describe what you
>see as important improvements before making general
>release of the procedure for use by non-expert users of
>Apache OpenOffice on Windows.
>
> The goal is to provide as much as we can to assist Windows users in 
applying this fix with confidence and success.  The experience of 
more-knowledgable users who appreciate the difficulties of non-experts 
is important in achieving that.

>
> Thank you for any effort you invest and the feedback you provide.
>
>  - Dennis
>
>
>
>
>
>
>  -- Dennis E. Hamilton
> orc...@apache.org
> dennis.hamil...@acm.org+1-206-779-9430
> https://keybase.io/orcmid  PGP F96E 89FF D456 628A
> X.509 certs used and requested for signed e-mail
>
>
>
> -
> 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: branches/gbuild-reintegration merged


On 8/7/2016 2:30 PM, Kay Schenk wrote:

On Sun, Aug 7, 2016 at 12:59 PM, Damjan Jovanovic  wrote:


Hi

branches/gbuild-reintegration has been merged to trunk. It has > 136
patches and makes many changes throughout the code, so you probably need to
"dmake clean" before rebuilding.

I haven't fixed the Windows build performance regression caused by issue
#117845, so if you're building on Windows use --disable-pch which only
extends your build time by around 2 hours instead of 6. If you aren't happy
with this, please help me figure out the problem.

Damjan



Thank you, Damjan! Any pointers on how to use the gbuild process for those
not familiar with it?




Preferably, update the step-by-step instructions with any changes.

-
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.2-patch1 Source


+1

Because of whitespace differences from the patch I had previously tests, 
I applied the patch to a clean 4.1.2 checkout, built from scratch, and 
tested the result.


I have checked the signature and hashes. The signature file shows the 
web-of-trust issues previously discussed.


On 8/2/2016 7:48 PM, Dennis E. Hamilton wrote:

[BCC to PMC]

The Apache OpenOffice 4.1.2-patch1 source code mitigates the security vulnerability 
described in the CVE-2016-1513 advisory 
.

The patch has been applied in the building of modified Apache 4.1.2 binaries.  
The modified binaries have been successfully used as the source of single 
modified shared-library files that can be copied into existing Apache 4.1.2 
programs in order to eliminate the vulnerability.

This ballot is for release of the source code on which replacement or patched 
Apache 4.1.2 binaries can be based.  The candidate source-code release for 
patch1 is the archive
apache-openoffice-4.1.2-patch1.zip located at
.
There are accompanying hash files (.md5 and .sha256) and a digital signature 
file (.asc) for the source-code archive.

Please vote by reply to this dev@-list thread on the approval of the candidate 
for release.

 [  ] +1 Approve, with description
 [  ]  0 Abstain
 [  ] -1 Disapprove, with explanation

For +1 Approve votes, please describe the results of verifying the patch 
materials and success in building a 4.1.2 binary having the patch applied to a 
particular 4.1.2 binary build.

Please do not do anything but [VOTE] (with any +1 descriptions and -1 
explanations) on this thread.

To discuss this vote or the process, please use a [DISCUSS][VOTE] reply rather 
than discussing on the [VOTE] thread.

The [VOTE] will conclude no sooner than Monday, 2016-08-08T15:00Z.

 - Dennis E. Hamilton
   For the Apache OpenOffice Project Management Committee


-
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: Planning for emergency releases


On 8/7/2016 10:16 AM, Marcus wrote:

Am 08/07/2016 06:14 PM, schrieb Patricia Shanahan:

...

but meanwhile work on getting competent at preparing a full release
promptly if needed.


Maybe we are not that far aways from each other. What I want to to avoid
is to provide hundreads of MBs for a single fix. Of course we can do a
4.1.3 with some collected fixes. As I don't know what is coming in the
future I would not love to see another 4.1.4, 4.1.5, 4.1.6, etc. when
the calendar is still showing 2016. ;-)


I think our basic disagreement is a priorities issue.

I don't see any value at all in conserving version numbers.

I do see a benefit to limiting download bandwidth, but to my mind that 
is an utterly insignificant issue compared to the convenience of each of 
a few hundred thousand relatively unskilled end users.



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

Re: Planning for emergency releases




On 8/7/2016 8:29 AM, Marcus wrote:

Am 08/06/2016 12:57 AM, schrieb Patricia Shanahan:

...

I don't agree with the car analogy - bits are relatively cheap, and I
will personally promise to recycle any obsoleted bits that are returned
to us, without taking up any landfill space. I would not do that for a
car recall.


I don't understand what you meant. At the end you would repaint your
whole car when you have just a scratch?

...

To make that analogy work, we have to assume that fixing a single
scratch is far, far more complicated and expensive than repainting the car.

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

Re: Planning for emergency releases



On 8/7/2016 8:29 AM, Marcus wrote:
...

I don't want to have it perfect. And we are already in this emergency
situation. We have either a patch process nor a full-release process.


We don't have what I consider to be the full emergency, a live exploit
in the field.

Why not both strategies? Go ahead with the inferior, clumsy,
user-hostile patch process because that is the best we can do this week,
but meanwhile work on getting competent at preparing a full release
promptly if needed.

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

Re: Building AOO for Windows 10


The instructions need clarifying - I'll look into it later.

The final argument "aoo-trunk" is the destination folder for the 
checkout. If you want to checkout into a folder called "aoo-trunk" do a 
"mkdir aoo-trunk" first. If you want a different destination, replace 
"aoo-trunk" with the folder name.


On 8/7/2016 5:35 AM, Kirsten S wrote:

Hello together,

I am new to this list and new to the AOO-Project. I've been trying to build
AOO and to get the source code since yesterday. I followed the step by step
guide in this link: https://wiki.openoffice.org/wiki/Documentation/
Building_Guide_AOO/Step_by_step

Everything went fine until i wanted to check out the source code from the
svn-repository. It seems that the directory aoo-trunk doesn't exist
anymore. At least this is what cygwin keeps on telling me.

I tried to execute the command line: svn co https://svn.apache.org./repos/
asf/openoffice/trunk aoo-trunk and then cd aoo-trunk --> Here i get the
message  No such file or directory.

Can anybody help me?

Thanks a lot in advance,
Dany



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

Draft report

2016-08-06 Thread Patricia Shanahan

Here is a draft of the August 2016 board report. As always, suggested 
changes are welcome.


==

## Description:
  - Apache River software provides a standards-compliant JINI service.

## Issues:

  - There are no issues requiring board attention at this time. 
Although the troubles discussed last quarter persist, there is on-going 
discussion of possible future directions.


## Activity:

  - There has been little activity.

## Health report:

  - The technical and people problems discussed last quarter have not 
yet been solved, but neither have they killed the project. In the last 
two months there have been threads on d...@river.apache.org, involving a 
total of 6 people, discussing how to support languages other than Java 
and how to take River in an IoT direction.


## PMC changes:

  - Currently 13 PMC members.
  - No new PMC members added in the last 3 months
  - Last PMC addition was Bryan Thompson on Sun Aug 30 2015

## Committer base changes:

  - Currently 15 committers.
  - Dan Creswell was added as a committer on Mon Jun 20 2016

## Releases:

  - Last release was river-jtsk-2.2.3 on Sat Feb 20 2016




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

Re: Planning for emergency releases

2016-08-05 Thread Patricia Shanahan




On 8/5/2016 2:20 PM, Marcus wrote:

Am 08/05/2016 10:43 PM, schrieb Patricia Shanahan:

This is mainly a summary of opinions I've already expressed on
security@. The discussion does not actually involve anything that needs
to be confidential, so it should be taking place on dev@ instead.

This is controversial - I expect replies disagreeing with my views. The
point of this thread is to hash out the diverging opinions and reach a
consensus:

[...]


I don't expect many of this kind of issues. Nevertheless, I don't want
to install everytime a complete new release for a fix that is related to
1% (?) of the AOO installation. For me it would be like taking a
sledgehammer to crack a nut.

Furthermore, what needs to be done on our side:

- more testing if the application is still working when we build every
  byte new from scratch.
- upload the files of hundreads of megabytes to SourceForge
- the connected mirrors need to sync them all
- earliest after x days the new release is distributed and the downlod
  is actually working
- agreement how to increase the version number. Everytime x.y.z+1 just
  for a little fix?

I hate this comparison but OK. Microsoft has a similar big office suite.
But I've never seen a new release with just a fix. They always provide
(more or less) little patch files. Sure, they will be searched,
downloaded and installed automtically, so the user doesn't need to do
much. But still, they are little files.

Or compare it with a car: You have a little scratch in your paint. Do
you really request a new paint for the complete car in the painter garage?

So, for me this sounds not smart. ;-)

Better would be really to deliver selected patched files.

Sure for this we need to:
- straighten the build process
- provide a smarter install routine than just a detailed readme text
- create new separate download webpages for the fixes with different
  content - at least for the describing text

My 2 ct.


If we actually had a smooth, automatic patch facility I would, of
course, prefer using that to redistributing the complete binaries.

I don't agree with the car analogy - bits are relatively cheap, and I
will personally promise to recycle any obsoleted bits that are returned
to us, without taking up any landfill space. I would not do that for a
car recall.

If we had the resources of the Microsoft Office team, I would agree with
assigning half a dozen programmers per platform to produce a smooth,
user-friendly, upgrade process.

To me, having a process we can do reasonably quickly, that real end
users can apply is essential. Making that work with small downloads
would be nice to have. Is it so important that we want to spend the
resources to do it?

This is a situation in which the perfect is the enemy of the good. If we
wait to rehearse an emergency fix until after we have a usable patch
facility, we will be caught unprepared if an emergency happens.

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

Planning for emergency releases

2016-08-05 Thread Patricia Shanahan


This is mainly a summary of opinions I've already expressed on
security@. The discussion does not actually involve anything that needs
to be confidential, so it should be taking place on dev@ instead.

This is controversial - I expect replies disagreeing with my views. The
point of this thread is to hash out the diverging opinions and reach a
consensus:

Although I has not yet happened, there is a risk that AOO could be the
subject of an in-the-field exploit of some, as yet unknown, security
vulnerability. If that happened, users would have to suspend using AOO
until we get a fix to them in a form they can use. If that suspension
went on too long, or any significant number of users were harmed, AOO
would be dead.

We need a plan for releasing an emergency fix, and we need to rehearse
the plan, possibly by picking a relatively minor, not yet exploited, bug
and following the emergency process for it.

The only effective way to get a fix distributed to most of the end users
is to create and upload to SourceForge a new set of binaries. My
reasoning is that anyone using AOO can either download and install
software, or has someone who can and will do it for them. There is
nothing else we can depend on. In particular, we cannot depend on the
ability to follow an unfamiliar set of instructions accurately.

Note that most Apache projects distribute software that is installed and
managed by programmers or system administrators, who are experienced in
following non-trivial instructions accurately. AOO can be installed and
managed by non-technical end users.

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

Re: Help wanted

2016-08-02 Thread Patricia Shanahan


Free work only - no paid positions.

If you are looking for programming experience, you will probably be most 
interested in development. What programming languages do you use? Build 
tools?


Patricia

On 8/2/2016 12:30 PM, Courtney wrote:

Hello! My name is Courtney and I was working on a project when I came
upon your help wanted page. I was just curious if this was a position
open or just free work needed? I graduate this December from college
in programming and would love to gain some experience. Please let me
know what you have if anything. Thanks.

Sent from my iPhone

-



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: Interested in volunteering with Apache

2016-08-01 Thread Patricia Shanahan


Welcome.

The current writing project is constructing instruction files for
applying a patch. The process is fairly complicated, and needs to be
explained clearly for end users with limited technical skills. Perhaps
you could review the drafts and see if you can suggest any improvements?

Can you use subversion to check out files?

Thanks,

Patricia

On 8/1/2016 3:48 PM, Woody Arnold wrote:

To Whom It May Concern,

Hello. My goal is to get into the technical writing field. I have a BS degree in civil 
engineering that I completed at California State University, Long Beach and did some 
graduate coursework in environmental engineering from San Diego State University. I also 
studied and intern abroad in Austria and Germany respectively. I'm interested in 
volunteering because I want to gain some experience related to technical writing to build 
up my portfolio and felt compelled to introduce myself to you all. Attached is my resume 
and also just started a blog related to technical writing, life, innovations, and book 
reviews, but its a project in the making for now and will soon get its own domain name to 
replace the ".wordpress.com".

Here's the link to my personal blog:

https://theoutlawthinker.wordpress.com/

When you click on the "Portfolio" tab on my blog, it will link you to my 
LinkedIn account that some samples of my
writing. Hope to hear from you soon. Thank you very much.

Sincerely,

Woody Arnold, EIT
(619)817-1043
woodyarnol...@yahoo.com




-
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: Officially releasing a patch for CVE-2016-1513

2016-07-31 Thread Patricia Shanahan




On 7/31/2016 5:17 PM, Dennis E. Hamilton wrote:




-Original Message-
From: Kay sch...@apache.org [mailto:ksch...@apache.org]
Sent: Sunday, July 31, 2016 14:42
To: dev@openoffice.apache.org
Subject: Re: Officially releasing a patch for CVE-2016-1513

OK, I think I'm done with the LInux64 bit area as well.

And see below 


On 07/31/2016 01:10 PM, Marcus wrote:

[ ... ]

I'm preparing the hotfix webpage. For this I've some questions:

1. Do we want to provide zip files for every platform or just single
files for the library and other files?


H... I assumed we would just be point people directly at
/dist/release/openoffice/patches.
(Right now, these are in /dist/dev/openoffice/patches.)

It would be easiest to just setup the hotfix page with three links per
distro.

Linux32
* link to Linux32.README
* link to linux32 libtl.so
* link to linux32 libtl.so.asc (sig)

etc.

If not, the READMEs I wrote will need to change.

[orcmid]

I recommend there should be single-file (e.g., Zip) distributions, just like 
all other binaries.  That gives just one thing to download.  The MD5, SHA512, 
and ASC signatures should be on the whole package and stay in the dev/ and 
release/ folders, just as they are on download pages.  (The ASC signatures on 
the individual library-file binaries should be inside the package.)  I suspect, 
on the dev/ side, we might need copies of the READMEs alongside the archives, 
and revised more regularly, so they can be reviewed and revised easily as we 
get QA and trial use.  When we move over to release/ we might want to do the 
same, even though the README is in the archive, so that people can read it 
without downloading the package.

Finally, please use README.txt, etc., so that line-ending adjustments will 
happen properly when folks move these in and out of SVN and also out of archive 
files.  This will also help browsers when folks retrieve these directly from 
the repository.

PS: If we are concerned about the README.txt outside of the archive being 
authenticated, it can have an embedded PGP signature.  (Then the final 
archive-internal one would be a copy of the signed README.txt -- no biggie, 
nice chain of custody).

[ ... ]


For the end user, this is incredibly, painfully more complicated than 
downloading and installing a new version.


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

Re: FW: buildbot success in on aoo-win7

2016-07-27 Thread Patricia Shanahan


Congratulations!

On 7/27/2016 2:17 AM, Damjan Jovanovic wrote:

2 successful aoo-win7 builds in a row, so I think it's safe to conclude it
works now :-).

The build script still needs a bit of cleaning up, and we need to fix the
snapshot buildbots. But how? Can we just randomly merge patches to that
branch?

Damjan

On Wed, Jul 27, 2016 at 5:31 AM, Dennis E. Hamilton

Re: Editing Download page

2016-07-25 Thread Patricia Shanahan


On 7/24/2016 1:59 PM, JZA wrote:

I would also suggest to revisit the intro programs for development which
were put on hold indefinetly and at the momento there is really no good way
to 'learn' the AOO sourcecode.


Even if we were hiring full time programmers, AOO is too big for 
learning the AOO source code to be a reasonable objective for people new 
to it.


Recruits are just going to have to live with reading and studying the 
area around a particular issue.


Patricia

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

Re: Editing Download page

2016-07-23 Thread Patricia Shanahan


Marcus:

Please add "Experienced lead technical writers" to the requested skills. 
See the "Is it time to shut down this effort?" thread.


On 7/22/2016 1:14 PM, Marcus wrote:

Am 07/22/2016 08:35 PM, schrieb Patricia Shanahan:

On 7/22/2016 11:05 AM, Marcus wrote:

Am 07/22/2016 07:45 PM, schrieb Patricia Shanahan:

I am trying to edit www.openoffice.org/download/ to add a box for
recruiting developers. It seems to be a rather complicated page, with
internationalization.


yes, to give the L10n groups the possibility to translate their
webpages. But only the strings. Everything else should be the same look
& feel. Therefore the heavy use of scripting.


The new box should probably follow conventions, but we really need
written English competence for AOO developers, because this mailing list
and a lot of the web pages are in English.


this is not mentioned in any way on the "get-involved.html" webpage.
Should we add this there also?

Of course no native speaker level is need. But somehow a level that
makes it not too difficult to communicate (mails, Bugzilla, source code
comments, etc.).


If anyone is familiar with how to edit it, and has time to help me,
please reply.


Maybe you have overlooked my previous answer on your "Attracting new
developers" thread. ;-) I'll look on the weekend for the necessary
updates.


I didn't interpret it as a commitment to do the changes, and I am in a
Just Do It mood this week. If you can do the changes, great.

The images etc. for an orange box are already there, are not currently
being used, and I think orange would be an appropriate color. I would
like to see it go fairly high up on the page, perhaps immediately above
the "share" box.


OK, I'll take this into account. Unfortunately, the orange icon is the
one for a download and not the share icon.


The key skills we need most urgently right now seem to be application
build tools and C++ programming. Anything else?


My technical additions need a bit more time but in the meantime here are
my text suggestions:

Box headline:
"Developers Needed"

Box text:
"Are you a software developer with C++ skills or have you deeper
knowledge about building software? Do you like to work in open source
projects and you are familar with the English language? Then come to us
and help Apache OpenOffice to grow."

Box mouse-over:
"The Apache OpenOffice project need software developers to grow its base"

Not perfect but a start - for discussion and improvement.

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: Is it time to shut down this effort?

2016-07-23 Thread Patricia Shanahan

Should we add "Experienced lead technical writers" to the list for the 
download web page changes?


On 7/23/2016 6:23 PM, Keith N. McKenna wrote:

Dennis E. Hamilton wrote:

[BCC dev@ (really, this time)]


-Original Message-
From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
Sent: Saturday, July 23, 2016 10:28
To: d...@openoffice.apache.org
Subject: Re: Is it time to shut down this effort?

Dennis E. Hamilton wrote:

[BCC dev@]

Please be specific about what you mean by "this effort."

The current documentation approach is to develop materials on the

MediaWiki.  This wiki is typical in that it operates like an open-source
project with commit then review (although there is a nice "Discuss"
feature).


If you mean the particular approach to reviewing and approving pages

and having a kind of editor-in-chief, please say so.


 - Dennis


-Original Message-
From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
Sent: Friday, July 22, 2016 20:36
To: d...@openoffice.apache.org
Subject: Is it time to shut down this effort?

My answer to the question posed in the tittle of this e-mail
unfortunately is yes. We have been moving by fits and starts for

almost

4 years and have very little to show for it. I would like to hear the
opinions of others though.

Keith


Dennis;

This mailing list came into existence to coordinate the development of
documentation for Version 4 under the Apache License. There never was
and was never intended to be an editor-in-chief. For a lot of reasons
this particular effort has produced a very limited amount of usable
documentation.

My personal feeling is that it should be recognized that it is not doing
what it was intended to and either retired or reconstituted in a
different form.

I think that my personal position is pretty obvious from my original
message and I wanted to solicit comment from other participants.

[orcmid]

I am still unclear on what it means to "shut down this effort."

Close the doc@ list?

What action do you have in mind that would result in a shut down?

Also, perhaps a broader request for assistance in documentation is called for.  
This might go with the adjustments just made to the download page.  And there 
are lists (and the Community Forum) where power users might be encouraged to 
contribute to documentation on the wiki.

The nice thing about the documentation is that there is always room for 
additions and improvements. Whatever there is at the moment is what there is.  
Positive effort is not wasted.



Regards
Keith

Dennis;
I specifically did not bring this to the dev list because I wanted to
illicit responses from the members of the documentation list as to their
thoughts before I came to the dev list with a concrete proposal. Since
you insist on bringing it here I will bow to your insistence and express
my thoughts her.

It is very simple. The documentation list serves no purpose and should
be closed down. We have tried numerous times to generate more interest
in gaining volunteers to help with documentation to no avail. Your board
reports have succinctly stated that the "documentation effort" is
stalled. Trying to get more people is doomed to failure unless we can
attract experienced tech writers that are willing to take the time to
mentor new volunteers and to overhaul the wiki editing policy and the
style guide to reflect current conditions and practices in the
discipline. This has not happened and I do not see it happening in the
future.

It is time that we realize that writing documentation is a unique skill
set and requires as much coaching and mentoring of new volunteers as
does writing code. We need up to date policies and procedures on how to
edit the wiki pages and we desperately need a coherent style guide on
what documentation looks like. To the best of my knowledge we do not
have anyone with the requisite skills actively engaged in the project
that can provide those.

Regards
Keith




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

Re: Editing Download page

2016-07-22 Thread Patricia Shanahan


On 7/22/2016 11:05 AM, Marcus wrote:

Am 07/22/2016 07:45 PM, schrieb Patricia Shanahan:

I am trying to edit www.openoffice.org/download/ to add a box for
recruiting developers. It seems to be a rather complicated page, with
internationalization.


yes, to give the L10n groups the possibility to translate their
webpages. But only the strings. Everything else should be the same look
& feel. Therefore the heavy use of scripting.


The new box should probably follow conventions, but we really need 
written English competence for AOO developers, because this mailing list 
and a lot of the web pages are in English.





If anyone is familiar with how to edit it, and has time to help me,
please reply.


Maybe you have overlooked my previous answer on your "Attracting new
developers" thread. ;-) I'll look on the weekend for the necessary updates.


I didn't interpret it as a commitment to do the changes, and I am in a 
Just Do It mood this week. If you can do the changes, great.


The images etc. for an orange box are already there, are not currently 
being used, and I think orange would be an appropriate color. I would 
like to see it go fairly high up on the page, perhaps immediately above 
the "share" box.


The key skills we need most urgently right now seem to be application 
build tools and C++ programming. Anything else?


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

Editing Download page

2016-07-22 Thread Patricia Shanahan

I am trying to edit www.openoffice.org/download/ to add a box for 
recruiting developers. It seems to be a rather complicated page, with 
internationalization.


If anyone is familiar with how to edit it, and has time to help me, 
please reply.


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

Re: Buildbots update

2016-07-22 Thread Patricia Shanahan


On 7/22/2016 12:09 AM, Damjan Jovanovic wrote:
...

I'll experiment a lot more over the weekend, but right now I think the
problem could be that the buildbot runs VSVARS.BAT to set up the Visual
Studio environment, which (presumably) contains the evil DEVENV that break
the build and locks files while hung. On my own Windows VM I don't run
VSVARS.BAT, and I can't reproduce the problem. Do the rest of you that
build on Windows use it?

...

I don't explicitly run it, and cannot find it in any of the scripts such 
as configure that I do run. I copy pieces of Visual Studio into 
main/external/ directories, as described in 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1


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

Re: Donations?

2016-07-21 Thread Patricia Shanahan

I find this rather disturbing. Most non-profits to which I donate have 
some provision for designating a subgroup to benefit from the money. For 
example, if I write a check to "San Diego City College Foundation" and 
write "Robotics" in the memo field, it shows up as money the San Diego 
City College Robotics team can spend.


If Apache only manages funds on a whole foundation basis, I will 
probably never add ASF to my donation list.


On 7/21/2016 5:02 PM, Dennis E. Hamilton wrote:

Apache OpenOffice does not receive donations and does not manage a budget.

It happens there are some funds "on-account" at the ASF that are available to 
OpenOffice.  Those arrived in an unusual manner in the early history of the project.  
That exception is unlikely to repeat.

Generally, the Apache Software Foundation has a budget and manages funds.  
There are treasurer reports in every monthly Board Report at the foundation 
level.  You can see those at
 <http://www.apache.org/foundation/board/calendar.html>.

In some case, projects can request that funds available for some purpose be 
expended on behalf of the project.  For example, application for and renewal of 
trademark registrations is done by requests to the VP Branding.  That VP will 
make requests for budget to cover anticipated expenses of that kind.  
Similarly, Infrastructure might be worked with to fund the contract labor and 
any hardware and operating costs of build slaves dedicated for OpenOffice use.

 - Dennis


-Original Message-
From: Alexandro Colorado [mailto:j...@gultab.org]
Sent: Thursday, July 21, 2016 15:22
To: dev@openoffice.apache.org
Subject: Re: Donations?

Unfortunately this community hasnt been very vocal about budgeting and
is
very lurky to know if we have any funds at all at the end of the day, we
used to have very clear reports:
https://wiki.openoffice.org/wiki/Community_Council/Funding_And_Budgets/B
udget_2011

On Thu, Jul 21, 2016 at 4:55 PM, Marcus <marcus.m...@wtnet.de> wrote:


Am 07/21/2016 09:26 PM, schrieb Patricia Shanahan:


In looking at the web pages to see where to insert mentoring offers
etc., I noticed that https://openoffice.apache.org/get-involved.html

has

a link to "make a small donation". Does that collect any money, and

if




good question. But only the Apache treasury can answer this. Please

note

the you don't donate to a special project but to the whole foundation.

And

the foundation is giving it to the projects.

so might it help with buildbot costs?




You mean getting the hardware and the Infra maintenance paid? I don't

know

of other costs.

Marcus



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





--
Alexandro Colorado
GULTab.org
Linux User # 319286
Blog: http://www.alexandrocolorado.org/
<http://www.alexandrocolorado.com/blog/>



-
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

Donations?

2016-07-21 Thread Patricia Shanahan

In looking at the web pages to see where to insert mentoring offers 
etc., I noticed that https://openoffice.apache.org/get-involved.html has 
a link to "make a small donation". Does that collect any money, and if 
so might it help with buildbot costs?


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

Re: Attracting new developers

2016-07-20 Thread Patricia Shanahan




On 7/20/2016 12:03 PM, Marcus wrote:

Am 07/20/2016 07:51 PM, schrieb Patricia Shanahan:

OpenOffice really needs more developers, especially build experts but
also programmers in general.

We do have a web page, http://openoffice.apache.org/get-involved.html,
but it it not very obvious and tends to emphasize non-programming
contributions. Those are very valuable, but we have far too few
developers.

I only found out about the need for developers by reading
bo...@apache.org, a mailing list that is available to a few hundred
people. Meanwhile, it's a quiet day if there are less than 100,000
downloads.

The download page, https://www.openoffice.org/download/, could have a
"Developers Needed" block similar to the "Help Spread the Word" block,
linking to http://openoffice.apache.org/get-involved.html.


that's possible. But an additional message box on the main webpage could
also help to get the attention.

Let me think about all this in the next days (maybe weekend?).


The more places we call attention to the need, the more likely users are 
to find out about it. I picked the page I did because when I want to 
install software package X I type in Google "download X", and usually 
pick the first hit. For "Download OpenOffice" that is the download page.



If this does get us some more developers, I am volunteering to shepherd
and organize them. I don't think just telling them to pick something to
work on is an effective way of getting them started - we seem to lose a
lot of people at that point.


Thats great as this would be a question because it is a key point that
we need to satisfy: How to please new devs with mentors and work? ;-)


If we only get a few responses I plan to work with them individually. In 
many cases my role will be to answer questions for which I happen to 
know the answer and not be embarrassed to ask questions that reveal my 
ignorance if necessary.


If we get a lot of responses I'll try to form them into mixed-skill 
teams such that the members of each team can help each other.


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

Attracting new developers

2016-07-20 Thread Patricia Shanahan

OpenOffice really needs more developers, especially build experts but 
also programmers in general.


We do have a web page, http://openoffice.apache.org/get-involved.html, 
but it it not very obvious and tends to emphasize non-programming 
contributions. Those are very valuable, but we have far too few developers.


I only found out about the need for developers by reading 
bo...@apache.org, a mailing list that is available to a few hundred 
people. Meanwhile, it's a quiet day if there are less than 100,000 
downloads.


The download page, https://www.openoffice.org/download/, could have a 
"Developers Needed" block similar to the "Help Spread the Word" block, 
linking to http://openoffice.apache.org/get-involved.html.


If this does get us some more developers, I am volunteering to shepherd 
and organize them. I don't think just telling them to pick something to 
work on is an effective way of getting them started - we seem to lose a 
lot of people at that point.


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

Re: Putting Windows First ( was RE: null)

2016-07-17 Thread Patricia Shanahan


On 7/17/2016 9:38 AM, Damjan Jovanovic wrote:

Windows lacks many of the external libraries present on *nix (jpeg, zlib,
curl, etc.),  meaning we have to build them internally. They build using
GNU autotools, which need a *nix shell like Cygwin. In other words, it
isn't even only AOO that needs Cygwin, it's our dependencies as well.


I'll have to think about that aspect. It may be the case that we need
two stages to the build process, one that every Windows developer can
do, and another that is done by specialists with *nix shell experience.

Most work on AOO is not going to require changes to those libraries, so
a C++ programmer could do useful work using prepared copies of them
rather than building them from scratch.


Also we need a portable build system, which any Visual Studio based
solution isn't.


Why do we need a portable build system?

Whether the build system is portable or not makes no difference at all
to end users. It is not part of the AOO functionality. It is merely a
tool that may save costs by avoiding duplication of effort compared to
having separate build systems for different target environments.

In this case I suspect that the total cost of the portable build system
is far higher than the total cost of having separate build systems for
Windows and for the *nix derived operating systems. That total cost
includes every Windows C++ programmer who is a user of AOO, and has been
scared off contributing to AOO by the arcane and fragile build process.



Damjan

On Wed, Jul 13, 2016 at 11:52 PM, Kay Schenk <kay.sch...@gmail.com> wrote:




On 07/13/2016 12:56 PM, Patricia Shanahan wrote:

On 7/13/2016 10:38 AM, Dennis E. Hamilton wrote:




-Original Message- From: Damjan Jovanovic
[mailto:dam...@apache.org]

..

By the way, AOO code and build process are very *nix-centric,
leading to Windows being such a pain to develop for, that we would
gain more by dropping Windows support, than by dropping all other
platforms ;-).

[orcmid]

Yes.  I already made the point that, from the perspective of
developers, development of Windows is very contorted and development
for Linux is a pleasure.  It was done that way for the convenience of
Linux-oriented developers.  It creates an awful on-ramp for
cultivation of new developers.

The question: How does ceasing support for Windows serve the 87% of
our current user base?  The technical act is within the power of the
PMC to determine, and release managers could force the outcome. In my
estimation, the consequences would be quite terrible.

We may be "stuck between a rock and a hard place."


Damjan


I would like to suggest a way of squeezing out from between the rock
and hard place, and getting more developers:

Separate out the Windows build process. Pick one of the common IDE's,
and create a project file that sets all environment variables for
Windows. Get as close as possible to the step-by-step build
instructions for Windows being:

Check out the source from SVN.

Open the project file in $IDE$.

Build it.

In particular, use of a UNIX-derived shell must not be required for
Windows builds.

In this vision, the core work would be done on Windows, using an IDE.
There would still be a need for a small number of Linux etc. people to
handle building for their environments, and to keep the Windows-based
developers from building in unwarranted assumptions.


Patricia --

I think this approach was actually started as a Capstone Project in
2013. You might want to have a look at the information in:

http://svn.apache.org/viewvc/openoffice/branches/capstone2013/


--

MzK

"Time spent with cats is never wasted."
   -- Sigmund Freud


-
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: Putting Windows First ( was RE: null)

2016-07-13 Thread Patricia Shanahan


On 7/13/2016 10:38 AM, Dennis E. Hamilton wrote:




-Original Message- From: Damjan Jovanovic
[mailto:dam...@apache.org]

..

By the way, AOO code and build process are very *nix-centric,
leading to Windows being such a pain to develop for, that we would
gain more by dropping Windows support, than by dropping all other
platforms ;-).

[orcmid]

Yes.  I already made the point that, from the perspective of
developers, development of Windows is very contorted and development
for Linux is a pleasure.  It was done that way for the convenience of
Linux-oriented developers.  It creates an awful on-ramp for
cultivation of new developers.

The question: How does ceasing support for Windows serve the 87% of
our current user base?  The technical act is within the power of the
PMC to determine, and release managers could force the outcome. In my
estimation, the consequences would be quite terrible.

We may be "stuck between a rock and a hard place."


Damjan


I would like to suggest a way of squeezing out from between the rock and 
hard place, and getting more developers:


Separate out the Windows build process. Pick one of the common IDE's, 
and create a project file that sets all environment variables for 
Windows. Get as close as possible to the step-by-step build instructions 
for Windows being:


Check out the source from SVN.

Open the project file in $IDE$.

Build it.

In particular, use of a UNIX-derived shell must not be required for 
Windows builds.


In this vision, the core work would be done on Windows, using an IDE. 
There would still be a need for a small number of Linux etc. people to 
handle building for their environments, and to keep the Windows-based 
developers from building in unwarranted assumptions.


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

Re: Smoke Test to run on a built office

2016-07-07 Thread Patricia Shanahan


Thanks, I'll try that.

Meanwhile, how do I get to do a second test run after killing the first 
one? "ant clean" does not help. Killing and restarting Cygwin does not 
help. Rebooting the system does let me run again, but is inconvenient.


On 7/7/2016 12:11 AM, Damjan Jovanovic wrote:

The hung test method from your log is testInsertFunctionViaFormulaBar. What
I'd recommend is getting a stack trace of the Java test process, eg. using
jstack (since you probably didn't run it with remote debugging enabled),
and seeing where in that test method it is stuck.

On Thu, Jul 7, 2016 at 1:08 AM, Patricia Shanahan <p...@acm.org> wrote:


How does one find out whether the tests have hung, or are just taking
their time? I started them by running ant in the test folder using a cygwin
shell that has the winenv.set.sh parameters for my AOO412 build.

It started doing AOO things, with windows appearing, changing, and
disappearing, so I left it to get on with the job. The next time I looked
in on it, there was an empty spreadsheet on the screen. The last few shell
lines were:

 [exec]
 [exec] setup -> ok
 [exec] write_status -> ok
 [exec] ---
 [exec]
 [exec] Jul 06, 2016 2:43:03 PM org.openoffice.test.common.Logger
finish
 [exec] INFO: Finish running test method [smokeTest]
 [exec] Jul 06, 2016 2:43:03 PM org.openoffice.test.common.Logger start
 [exec] INFO: Start running test method
[testInsertFunctionViaFormulaBar]
 [exec] Jul 06, 2016 2:43:03 PM org.openoffice.test.common.Logger start
 [exec] INFO: Clean up temp directory for test method
[C:\OpenOfficeDev\AOO412\test\testspace\temp]
 [exec] Jul 06, 2016 2:43:04 PM org.openoffice.test.OpenOffice start
 [exec] INFO:
"C:\OpenOfficeDev\AOO412\test\testspace\install\OpenOffice
4\program\soffice.exe" "-automationport=12479" "-enableautomation"
"-c8ebd53ec8fb426fbe3e4a4beba2533b" "-nofirststartwizard" "-norestore"
"-quickstart=no"



On 7/5/2016 4:42 PM, Damjan Jovanovic wrote:


Plz see
http://www.mail-archive.com/dev@openoffice.apache.org/msg27036.html

You probably want the qa tests, which run the (copied) Smoketest nowdays.

Damjan

On Wed, Jul 6, 2016 at 12:25 AM, Carl Marcum <cmar...@apache.org> wrote:

Hi all,


Are there other automated smoke test macros or scripts other than noted
below that can be ran on a built office to test basic functionality and
make sure nothing major is broken?

I found this wiki page [1] that references a sxw document that contains
macros and will display a report but I'm not sure how recent it is due to
the file extension.

The file is smoketestdoc.sxw in main/smoketestdoc/unxlngx6.pro/misc/zip
of a build.

[1] https://wiki.openoffice.org/wiki/SmokeTest

Thanks,
Carl


-
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: Smoke Test to run on a built office

2016-07-06 Thread Patricia Shanahan

How does one find out whether the tests have hung, or are just taking 
their time? I started them by running ant in the test folder using a 
cygwin shell that has the winenv.set.sh parameters for my AOO412 build.


It started doing AOO things, with windows appearing, changing, and 
disappearing, so I left it to get on with the job. The next time I 
looked in on it, there was an empty spreadsheet on the screen. The last 
few shell lines were:


 [exec]
 [exec] setup -> ok
 [exec] write_status -> ok
 [exec] ---
 [exec]
 [exec] Jul 06, 2016 2:43:03 PM org.openoffice.test.common.Logger 
finish

 [exec] INFO: Finish running test method [smokeTest]
 [exec] Jul 06, 2016 2:43:03 PM org.openoffice.test.common.Logger start
 [exec] INFO: Start running test method 
[testInsertFunctionViaFormulaBar]

 [exec] Jul 06, 2016 2:43:03 PM org.openoffice.test.common.Logger start
 [exec] INFO: Clean up temp directory for test method 
[C:\OpenOfficeDev\AOO412\test\testspace\temp]

 [exec] Jul 06, 2016 2:43:04 PM org.openoffice.test.OpenOffice start
 [exec] INFO: 
"C:\OpenOfficeDev\AOO412\test\testspace\install\OpenOffice 
4\program\soffice.exe" "-automationport=12479" "-enableautomation" 
"-c8ebd53ec8fb426fbe3e4a4beba2533b" "-nofirststartwizard" "-norestore" 
"-quickstart=no"



On 7/5/2016 4:42 PM, Damjan Jovanovic wrote:

Plz see http://www.mail-archive.com/dev@openoffice.apache.org/msg27036.html

You probably want the qa tests, which run the (copied) Smoketest nowdays.

Damjan

On Wed, Jul 6, 2016 at 12:25 AM, Carl Marcum  wrote:


Hi all,

Are there other automated smoke test macros or scripts other than noted
below that can be ran on a built office to test basic functionality and
make sure nothing major is broken?

I found this wiki page [1] that references a sxw document that contains
macros and will display a report but I'm not sure how recent it is due to
the file extension.

The file is smoketestdoc.sxw in main/smoketestdoc/unxlngx6.pro/misc/zip
of a build.

[1] https://wiki.openoffice.org/wiki/SmokeTest

Thanks,
Carl


-
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: Interns?

2016-07-06 Thread Patricia Shanahan


Thanks.

On 7/5/2016 11:48 PM, Damjan Jovanovic wrote:

Hi Patricia

I think you meant to this send this to the Apache River mailing list, where
Bishnu Gautam asked the question?

On Wed, Jul 6, 2016 at 4:39 AM, Patricia Shanahan <p...@acm.org> wrote:


Bishnu Gautam has suggested that we should start taking interns, with
assigned mentors, and might be able to steer some students our way.

What do you think? Would the proposed projects be able to use students? To
be fair to the students, they would need mentors they could learn from, not
just to be thrown a project and left to sink or swim.

In the longer terms, Apache participates in the Google Summer of Code each
year, so we might be able to get one or more summer interns into that.

Patricia


-
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

Interns?

2016-07-05 Thread Patricia Shanahan

Bishnu Gautam has suggested that we should start taking interns, with 
assigned mentors, and might be able to steer some students our way.


What do you think? Would the proposed projects be able to use students? 
To be fair to the students, they would need mentors they could learn 
from, not just to be thrown a project and left to sink or swim.


In the longer terms, Apache participates in the Google Summer of Code 
each year, so we might be able to get one or more summer interns into that.


Patricia


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

Re: Building on Windows

2016-07-01 Thread Patricia Shanahan

Could this patch also be modified to apply to 4.1.2? It may be the issue 
preventing me from doing Windows builds of that release.


On 2/10/2016 3:57 PM, Damjan Jovanovic wrote:

icu supports building on Cygwin using Cygwin's make, but for some bizarre
reason AOO builds it with MSVC's nmake using makefiles generated by a Perl
script and even completely bypassing ./configure (makefile.mk has
CONFIGURE_ACTION+= $(PERL) ..$/..$/..$/..$/..$/createmak.pl
..$/..$/..$/..$/..$/createmak.cfg .). It could not have been easy to set
that up, nor does the nmake build parallelize at all, which is why icu
wastes 5 minutes building while using only a single thread, so you have to
wonder why it was done that way.

Building with mingw or building on any other platform does use ./configure
and GNU make instead, which explains why we only see this bug with MSVC.

Anyway I think I've hacked icu into working. In allinone.sln I've made
layoutex project depend on the i18n project containing icuin.lib, and the
Perl script should convert that dependency into the makefiles it creates.
So far icu has been rebuilt 10 times with this patch (attached), succeeding
every time, so please test it and see if it works for you as well.

Damjan

On Tue, Feb 9, 2016 at 7:51 PM, Patricia Shanahan <p...@acm.org> wrote:


I have already done some of this. The key difference between failing and
non-failing is whether layoutex is built early or later in the build. See
the attached files for sample build outputs.

I believe layoutex has a dependency on icuin.lib that is not properly
declared in the makefile etc., allowing layoutex to be built too soon. If
so, the best fix would be to declare the dependency, but I don't know
enough about the dmake and configuration stuff to make that change without
some study first.

Patricia


On 2/9/2016 9:40 AM, Damjan Jovanovic wrote:


The icu module has a complicated build with scripts generating
makefiles...

I am not sure what approach to even take debugging this, but some ideas
might be:
* make a copy of a main/icu[/wntmsci12.pro] directory that builds and a
copy of one that doesn't, then diff the files to see what's different
* compare build logs with it working and not working, to see what steps
differ (eg. build order of some files might be different)
* try and follow the makefile to understand the problem analytically; my
first try didn't get me far
* give up completely, and just hack it. Make a loop in build.pl that just
keeps cleaning and rebuilding the module. If it builds 50% of the time,
with 10 retries only 1 in 1024 builds will fail, with 20 retries only 1 in
2^20 will fail, etc. Something like this might already have been tried in
the past, as build.pl contains the following code which is only run on
Windows:

sub give_second_chance {
 my $pid = shift;
 # A malicious hack for mysterious windows problems - try 2 times
 # to run dmake in the same directory if errors occurs
 my $child_nick = $processes_hash{$pid};
 $running_children{$folders_hashes{$child_nick}}--;
 delete $processes_hash{$pid};
 start_child($child_nick, $folders_hashes{$child_nick});
};


On Sun, Feb 7, 2016 at 1:42 AM, Patricia Shanahan <p...@acm.org> wrote:

My next step is to try to get rid of the intermittent failure of the icu

build. It seems to be the one thing standing between me a repeatable
unattended build. If you know anything about its cause, please let me
know.

Here is a typical failure output:

Generating Code...
 link.exe @C:\cygwin32\tmp\nm2E74.tmp
Creating library .\..\..\lib\icule.lib and object
.\..\..\lib\icule.exp
 if exist ..\..\bin\icule40.dll.manifest mt.exe -manifest
..\..\bin\icule40.dll.manifest -outputresource:..\..\bin\icule40.dll;2
 copy ".\LEFontInstance.h" ..\..\include\layout
 1 file(s) copied.
 copy ".\LEGlyphFilter.h" ..\..\include\layout
 1 file(s) copied.
 copy ".\LEGlyphStorage.h" ..\..\include\layout
 1 file(s) copied.
 copy ".\LEInsertionList.h" ..\..\include\layout
 1 file(s) copied.
 copy ".\LELanguages.h" ..\..\include\layout
 1 file(s) copied.
 copy ".\LEScripts.h" ..\..\include\layout
 1 file(s) copied.
 copy ".\LESwaps.h" ..\..\include\layout
 1 file(s) copied.
 copy ".\LETypes.h" ..\..\include\layout
 1 file(s) copied.
 copy ".\LayoutEngine.h" ..\..\include\layout
 1 file(s) copied.
 copy ".\loengine.h" ..\..\include\layout
 1 file(s) copied.
 cd "..\allinone"
 cd "C:\OpenOfficeDev\Trunk\main\icu\wntmsci12.pro
\misc\build\icu\source\allinone\..\layoutex"
 C:\PROGRA~2\MICROS~1.0\VC\bin\nmake.exe /   /F
layoutex.mak EXCEPTIONSWITCH="-EHa -Zc:wchar_t-"

Microsoft (R) Program Maintenance Utility Version

Building AOO412 on Windows

2016-06-30 Thread Patricia Shanahan

I am trying to build AOO412 on my Windows 8.1 system. Back in the 
previous "Building on Windows" thread I described a series of failures 
that were ultimately cured by adding "--disable-pch" to my configure 
parameters.


Those problems have reappeared in the 4.1.2 build. Is there something 
different I need to do to get rid of precompiled headers for that build?


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

Re: Configure failure

2016-06-29 Thread Patricia Shanahan

I retried configure, in case it was a temporary glitch in the Internet,
and it worked this time. Thanks.

On 6/29/2016 4:12 PM, Damjan Jovanovic wrote:

The problem (near the end) is that it can't download libxml2:

download from http://xmlsoft.org/sources/libxml2-2.9.3.tar.gz failed (500
Can't connect to xmlsoft.org:80)
download failed
downloading to
C:/OpenOfficeDev/Trunk/ext_sources/daece17e045f1c107610e137ab50c179-libxml2-2.9.3.tar.gz.part
download from
http://iweb.dl.sourceforge.net/project/oooextras.mirror/daece17e045f1c107610e137ab50c179-libxml2-2.9.3.tar.g
z failed (404 Not Found)
download failed

On Thu, Jun 30, 2016 at 12:58 AM, Patricia Shanahan <p...@acm.org> wrote:

Full output:

checking whether configure is up-to-date... yes

* *
* Apache OpenOffice build configuration. *
* *
* The configure process checks your platform to see whether *
* you can build Apache OpenOffice on it. *
* This process checks all pre-requisites and generates a file*
* containing the necessary environment variables.*
* Source this file after configure has ended successfully. *
* *
* Warnings that are generated during the configure process *
* must be taken into account since it can be a reason for*
* an unsuccessful build of Apache OpenOffice.*
* *

* *
* Checking the platform pre-requisites. *
* *

checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for gawk... gawk
checking for gawk... /usr/bin/gawk
checking for sed... /usr/bin/sed
checking for solenv environment... default
checking for custom pack.lst... no
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
cygwin
checking Cygwin version... 2.4.1(0.293/5/3)
head: cannot open '/etc/*-release' for reading: No such file or directory
CYGWIN_NT-6.3-WOW Jan2014Desktop 2.4.1(0.293/5/3) 2016-01-24 11:24 i686
Cygwin
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether to enable crashdump feature... no
checking whether to use the standard non-optimizing compiler... no
checking whether to build/use the Windows 64bit shell extensions... no
checking whether to turn warnings to errors... no
checking whether to do a debug build... no
checking whether to build with additional debug utilities... no, full
product build
checking whether to include symbols into final build... no
checking whether to strip the solver or not yes
checking whether to enable category B components... no: disabled modules
nss, hunspell, hyphen, saxon, rhino, graphite, co
inmp
checking whether to enable the Online Update support... yes
checking whether to enable unit tests... yes
checking whether to enable native CUPS support... no
checking whether to enable fontconfig support... no
checking whether to use DirectX... no
checking whether to use ActiveX... no
checking whether to use ATL... no
checking whether to use RPATH in shared libraries... yes
checking whether to use dicts from external paths... no
checking Windows build environment sanity... ok
checking for cygwin gcc/g++... found
checking for bash... /usr/bin/bash
checking gcc home... /usr
checking whether to enable pch feature... no
checking for GNU make... make
checking the GNU make version... make 4.1
3+:
checking for dmake... configure: no system or user-provided dmake found
dmake will be downloaded and compiled in bootstrap
checking for GNU or compatible BSD tar... tar
checking for perl... /usr/bin/perl
checking the Perl version... checked (perl 5)
checking for required Perl modules... all modules found
checking for friendly registry keys... done
checking the Microsoft C/C++ Compiler... found
(/cygdrive/c/PROGRA~2/MICROS~1.0/VC/bin/cl.exe)
checking the Version of Microsoft C/C++ Compiler... found Compiler version
00153072 in "Microsoft (R) 32-bit C/C++ Opt
"mizing Compiler Version 15.00.30729.01
for 80x86
found .NET 2008 / VS 9.0.
checking for midl.exe... no
checking for csc.exe... no
checking .NET Framework... found
checking

Re: Configure failure

2016-06-29 Thread Patricia Shanahan

r.gz.part
download from 
http://iweb.dl.sourceforge.net/project/oooextras.mirror/daece17e045f1c107610e137ab50c179-libxml2-2.9.3.tar.g 


z failed (404 Not Found)
download failed
downloading to 
C:/OpenOfficeDev/Trunk/ext_sources/9667bf6f9310b957254fdcf6596600b7-libxslt-1.1.28.tar.gz.part

MD5 checksum is OK
some needed files could not be downloaded! at 
C:/OpenOfficeDev/Trunk/main/solenv/bin/download_external_dependencies.pl 
lin 
   e 492, <$in> line 345.
*** Error downloading external dependencies, please fix the previous 
problems and try again ***



On 6/29/2016 3:49 PM, Damjan Jovanovic wrote:

Please post the full output. The problem is earlier.



On Thu, Jun 30, 2016 at 12:46 AM, Patricia Shanahan <p...@acm.org> wrote:


As part of my return-from-vacation, I did an "svn update" on my trunk
checkout followed by an attempt to configure with my usual parameters:

SDK_PATH="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0"
./configure \
--with-frame-home="$SDK_PATH" \
--with-psdk-home="$SDK_PATH" \
--with-midl-path="$SDK_PATH/bin" \
--disable-directx \
--with-ant-home="/cygdrive/c/ant" \

--with-dmake-url="
http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2; \

--with-epm-url="http://www.msweet.org/files/project2/epm-3.7-source.tar.gz;
\
--disable-pch \
--disable-atl \
--disable-activex \
--without-junit \
--with-jdk-home="/cygdrive/c/Program Files (x86)/Java/jdk1.7.0_79"
./bootstrap
source winenv.set.sh

The configure run failed with:

some needed files could not be downloaded! at
C:/OpenOfficeDev/Trunk/main/solenv/bin/download_external_dependencies.pl
line 492, <$in> line 345.
*** Error downloading external dependencies, please fix the previous
problems and try again ***


What causes this, and what can I do about it?




-
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

Configure failure

2016-06-29 Thread Patricia Shanahan

As part of my return-from-vacation, I did an "svn update" on my trunk 
checkout followed by an attempt to configure with my usual parameters:


SDK_PATH="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0"
./configure \
--with-frame-home="$SDK_PATH" \
--with-psdk-home="$SDK_PATH" \
--with-midl-path="$SDK_PATH/bin" \
--disable-directx \
--with-ant-home="/cygdrive/c/ant" \

--with-dmake-url="http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2; 
\


--with-epm-url="http://www.msweet.org/files/project2/epm-3.7-source.tar.gz; 
\

--disable-pch \
--disable-atl \
--disable-activex \
--without-junit \
--with-jdk-home="/cygdrive/c/Program Files (x86)/Java/jdk1.7.0_79"
./bootstrap
source winenv.set.sh

The configure run failed with:

some needed files could not be downloaded! at 
C:/OpenOfficeDev/Trunk/main/solenv/bin/download_external_dependencies.pl 
lin 
   e 492, <$in> line 345.
*** Error downloading external dependencies, please fix the previous 
problems and try again ***



What causes this, and what can I do about it?




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

Re: A Question about Open Office Password Protected Text Documenets

2016-06-10 Thread Patricia Shanahan

That said, if I had a set of business-critical documents, I would test 
some sample documents at each major OS, hardware, or office software 
upgrade. Before decommissioning the last instance of the old system, 
load and read a few sample documents on the new system. If there is a 
problem, use the old system to convert to an updated format.


On 6/10/2016 7:29 AM, Damjan Jovanovic wrote:

Hi Roger

If you saved them in OpenOffice's default format, OpenDocument (.odt / .ods
/ .odb etc.), then yes. Password protection is part of the OpenDocument
standard, and should be supported by us and other OpenDocument software
such as AbiWord, Gnumeric, Microsoft Office, etc. for a long time. The
encryption techniques are all well documented and use common well
established ciphers, hash functions and password strengthening procedures.

With long term storage, the problem won't be data becoming inaccessible due
to encryption (provided you remember your passwords), so much as the
opposite problem, of data becoming too easily accessible, since older
versions of OpenDocument used weaker encryption ciphers, potentially making
document encryption too easy to crack by future weaknesses discovered in
those ciphers and with more powerful computers in the future.

Regards
Damjan

On Fri, Jun 10, 2016 at 3:42 PM, Roger Bentley 
wrote:


Dear Sir/Madam

I have a large number of important documents that I have created over the
years in Open Office, which were created as password protected documents.

Is there any likelihood in the future of any ‘redundancy’ or suchlike
where these documents would be no longer accessible by future then current
software etc?  Or will the files always remain safe, in that there will
always be an Open Office allied program capable of unlocking their password
protected format?

I will be very grateful of your reply.

With sincere regards

Roger Bentley




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

Re: failed to build aoo420 dev on win32

2016-06-09 Thread Patricia Shanahan


I just completed a successful debug compile! Thanks.

On 6/8/2016 12:33 PM, Damjan Jovanovic wrote:

Hi

Patricia, with that patch, you were going in the right direction by moving
the declaration of OSQLParser_Data to the publicly visible
inc/connectivity/sqlparse.hxx, but since that header doesn't (and
shouldn't?) have "using namespace ::com::sun::star::...", this needed
changing:

-::connectivity::OSQLParser_Data( const Reference<
XMultiServiceFactory >& _xServiceFactory );
+::connectivity::OSQLParser_Data( const
::com::sun::star::uno::Reference<
::com::sun::star::lang::XMultiServiceFactory >& _xServiceFactory );

and sqlparse.cxx needed to have the declaration removed while leaving the
constructor's definition.

I've committed your patch in #1747439 with you as the author, then
committed my fixes to it in #1747440.

You did most of the work, so thank you!

Damjan

On Wed, May 11, 2016 at 12:08 AM, Patricia Shanahan <p...@acm.org> wrote:


I decided to try to fix the underlying error/warning, by making the header
file declaration complete. Unfortunately, I think my C++ rustiness is
getting in the way. I get an error suggesting a constructor is being
treated as a function.

I've attached a diff in the hope that someone else can fix my attempt.


On 4/30/2016 2:01 AM, Oliver Brinzing wrote:



My previous, successful, debug compile was revision 1734822, March



13th 2016, so the problem has to


be something that has changed since then.



i checked output from pro an debug build:

debug creates an error C4150 while pro will continue with a warning

the different compiler setting are:

pro   -Gy -Oxs -Oy- -DPRODUCT -DNDEBUG -DOSL_DEBUG_LEVEL=0 -DOPTIMIZE

dbg   -Zi -Od -Z7 -Yd -D_STLP_DEBUG -DDEBUG -DDBG_UTIL
-DOSL_DEBUG_LEVEL=2
   -Fd../../wntmsci12/misc/sqliterator.pdb

Oliver




debug:
Compiling: connectivity/source/parse/sqliterator.cxx
C:/PROGRA~2/MICROS~1.0/VC/bin/cl.exe  -Zm500 -Zc:wchar_t- -GR -GS -c
-nologo -Gs  -Ob1 -Zi -Fd../../wntmsci12/misc/sqliterator.pdb  -Od
-DENABLE_LAYOUT=0 -DENABLE_LAYOUT_EXPERIMENTAL=0 -Gd -I.
-I../../wntmsci12/misc -I../../wntmsci12/inc/sql -I../inc
-I../../inc/pch -I../../inc -I../../WIN/inc -I../../wntmsci12/inc -I.
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/stl
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/external
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/inc -IC:/build_tmp/trunk/main/res
-IC:/build_tmp/trunk/main/tools/inc
-IC:/build_tmp/trunk/main/comphelper/inc
-IC:/PROGRA~2/Java/JDK17~1.0/include/win32
-IC:/PROGRA~2/Java/JDK17~1.0/include
-IC:/PROGRA~1/MICROS~1/Windows/v7.0/include
-IC:/PROGRA~2/MICROS~1.0/VC/include -IC:/PROGRA~2/MICROS~1/include
-IC:/PROGRA~2/MICROS~1/include
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/offuh -I. -I../../res
-I. -Z7 -Yd -Wall -wd4061 -wd4127 -wd4191 -wd4217 -wd4250 -wd4251
-wd4275 -wd4290 -wd4294 -wd4355 -wd4511 -wd4512 -wd4514 -wd4611
-wd4625 -wd4626 -wd4640 -wd4675 -wd4710 -wd4711 -wd4786 -wd4800
-wd4820 -wd4503 -wd4619-wd4365 -wd4668 -wd4738 -wd4826 -wd4350
-wd4505 -wd4692 -wd4189 -wd4005 -wd4180   -DWNT -DWNT -DNT351 -DMSC
-DM1500 -DINTEL -D_STLP_DEBUG -D_X86_=1 -D_CRT_SECURE_NO_DEPRECATE
-D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NON_CONFORMING_SWPRINTFS -DFULL_DESK
-DBOOST_MEM_FN_ENABLE_CDECL -D_MT -DWINVER=0x0500 -D_WIN32_WINNT=0x0500
-D_WIN32_IE=0x0500 -DCPPU_ENV=msci -DSUPD=420 -DDEBUG -DDBG_UTIL
-DOSL_DEBUG_LEVEL=2 -DCUI -DSOLAR_JAVA   -DOOO_DLLIMPLEMENTATION_DBTOOLS
-DSHAREDLIB -D_DLL_ -DWIN32 -D_MT -D_DLL -DWIN32 -D_MT -D_DLL  -EHa
-DEXCEPTIONS_ON -Fo../../wntmsci12/slo/sqliterator.obj
C:/build_tmp/trunk/main/connectivity/source/parse/sqliterator.cxx
sqliterator.cxx
C:\PROGRA~2\MICROS~1.0\VC\include\memory(721) : error C4150: deletion of
pointer to incomplete type 'connectivity::OSQLParser_Data'; no
destructor called




pro:
Compiling: connectivity/source/parse/sqliterator.cxx
C:/PROGRA~2/MICROS~1.0/VC/bin/cl.exe   -Zm500 -Zc:wchar_t- -GR -GS -c
-nologo -Gs  -Gy -Ob1 -Oxs -Oy- -DENABLE_LAYOUT=0
-DENABLE_LAYOUT_EXPERIMENTAL=0 -Gd  -I. -I../../wntmsci12.pro/misc
-I../../wntmsci12.pro/inc/sql -I../inc -I../../inc/pch -I../../inc
-I../../WIN/inc -I../../wntmsci12.pro/inc -I.
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc/stl
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc/external
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc
-IC:/build_tmp/trunk/main/solenv/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/inc -IC:/build_tmp/trunk/main/res
-IC:/build_tmp/trunk/main/tools/inc
-IC:/build_tmp/trunk/main/comphelper/inc
-IC:/PROGRA~2/Java/JDK17~1.0/include/win32
-IC:/PROGRA~2/Java/JDK17~1.0/include
-IC:/PROGRA~1/MICROS~1/Windo

Re: failed to build aoo420 dev on win32

2016-06-08 Thread Patricia Shanahan

That is the sort of problem that should be expected when trying to 
revive my C++ skills - I last used it extensively before "namespace" 
became popular. I know in theory how it works, but that is not the same 
as having worked for a few years with a feature.


On 6/8/2016 12:33 PM, Damjan Jovanovic wrote:

Hi

Patricia, with that patch, you were going in the right direction by moving
the declaration of OSQLParser_Data to the publicly visible
inc/connectivity/sqlparse.hxx, but since that header doesn't (and
shouldn't?) have "using namespace ::com::sun::star::...", this needed
changing:

-::connectivity::OSQLParser_Data( const Reference<
XMultiServiceFactory >& _xServiceFactory );
+::connectivity::OSQLParser_Data( const
::com::sun::star::uno::Reference<
::com::sun::star::lang::XMultiServiceFactory >& _xServiceFactory );

and sqlparse.cxx needed to have the declaration removed while leaving the
constructor's definition.

I've committed your patch in #1747439 with you as the author, then
committed my fixes to it in #1747440.

You did most of the work, so thank you!

Damjan

On Wed, May 11, 2016 at 12:08 AM, Patricia Shanahan <p...@acm.org> wrote:


I decided to try to fix the underlying error/warning, by making the header
file declaration complete. Unfortunately, I think my C++ rustiness is
getting in the way. I get an error suggesting a constructor is being
treated as a function.

I've attached a diff in the hope that someone else can fix my attempt.


On 4/30/2016 2:01 AM, Oliver Brinzing wrote:



My previous, successful, debug compile was revision 1734822, March



13th 2016, so the problem has to


be something that has changed since then.



i checked output from pro an debug build:

debug creates an error C4150 while pro will continue with a warning

the different compiler setting are:

pro   -Gy -Oxs -Oy- -DPRODUCT -DNDEBUG -DOSL_DEBUG_LEVEL=0 -DOPTIMIZE

dbg   -Zi -Od -Z7 -Yd -D_STLP_DEBUG -DDEBUG -DDBG_UTIL
-DOSL_DEBUG_LEVEL=2
   -Fd../../wntmsci12/misc/sqliterator.pdb

Oliver




debug:
Compiling: connectivity/source/parse/sqliterator.cxx
C:/PROGRA~2/MICROS~1.0/VC/bin/cl.exe  -Zm500 -Zc:wchar_t- -GR -GS -c
-nologo -Gs  -Ob1 -Zi -Fd../../wntmsci12/misc/sqliterator.pdb  -Od
-DENABLE_LAYOUT=0 -DENABLE_LAYOUT_EXPERIMENTAL=0 -Gd -I.
-I../../wntmsci12/misc -I../../wntmsci12/inc/sql -I../inc
-I../../inc/pch -I../../inc -I../../WIN/inc -I../../wntmsci12/inc -I.
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/stl
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/external
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/inc -IC:/build_tmp/trunk/main/res
-IC:/build_tmp/trunk/main/tools/inc
-IC:/build_tmp/trunk/main/comphelper/inc
-IC:/PROGRA~2/Java/JDK17~1.0/include/win32
-IC:/PROGRA~2/Java/JDK17~1.0/include
-IC:/PROGRA~1/MICROS~1/Windows/v7.0/include
-IC:/PROGRA~2/MICROS~1.0/VC/include -IC:/PROGRA~2/MICROS~1/include
-IC:/PROGRA~2/MICROS~1/include
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/offuh -I. -I../../res
-I. -Z7 -Yd -Wall -wd4061 -wd4127 -wd4191 -wd4217 -wd4250 -wd4251
-wd4275 -wd4290 -wd4294 -wd4355 -wd4511 -wd4512 -wd4514 -wd4611
-wd4625 -wd4626 -wd4640 -wd4675 -wd4710 -wd4711 -wd4786 -wd4800
-wd4820 -wd4503 -wd4619-wd4365 -wd4668 -wd4738 -wd4826 -wd4350
-wd4505 -wd4692 -wd4189 -wd4005 -wd4180   -DWNT -DWNT -DNT351 -DMSC
-DM1500 -DINTEL -D_STLP_DEBUG -D_X86_=1 -D_CRT_SECURE_NO_DEPRECATE
-D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NON_CONFORMING_SWPRINTFS -DFULL_DESK
-DBOOST_MEM_FN_ENABLE_CDECL -D_MT -DWINVER=0x0500 -D_WIN32_WINNT=0x0500
-D_WIN32_IE=0x0500 -DCPPU_ENV=msci -DSUPD=420 -DDEBUG -DDBG_UTIL
-DOSL_DEBUG_LEVEL=2 -DCUI -DSOLAR_JAVA   -DOOO_DLLIMPLEMENTATION_DBTOOLS
-DSHAREDLIB -D_DLL_ -DWIN32 -D_MT -D_DLL -DWIN32 -D_MT -D_DLL  -EHa
-DEXCEPTIONS_ON -Fo../../wntmsci12/slo/sqliterator.obj
C:/build_tmp/trunk/main/connectivity/source/parse/sqliterator.cxx
sqliterator.cxx
C:\PROGRA~2\MICROS~1.0\VC\include\memory(721) : error C4150: deletion of
pointer to incomplete type 'connectivity::OSQLParser_Data'; no
destructor called




pro:
Compiling: connectivity/source/parse/sqliterator.cxx
C:/PROGRA~2/MICROS~1.0/VC/bin/cl.exe   -Zm500 -Zc:wchar_t- -GR -GS -c
-nologo -Gs  -Gy -Ob1 -Oxs -Oy- -DENABLE_LAYOUT=0
-DENABLE_LAYOUT_EXPERIMENTAL=0 -Gd  -I. -I../../wntmsci12.pro/misc
-I../../wntmsci12.pro/inc/sql -I../inc -I../../inc/pch -I../../inc
-I../../WIN/inc -I../../wntmsci12.pro/inc -I.
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc/stl
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc/external
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc
-IC:/build_tmp/trunk/main/solenv/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/in

Blocked from AOO work: Re: failed to build aoo420 dev on win32

2016-06-07 Thread Patricia Shanahan

I can no longer build debug versions of AOO due to this issue, making 
further AOO work difficult to impossible. Because of other commitments, 
I don't expect to do anything further on it until the end of June. Is 
there any chance someone with less rusty C++ could look into this before 
then?


On 5/10/2016 3:08 PM, Patricia Shanahan wrote:

I decided to try to fix the underlying error/warning, by making the
header file declaration complete. Unfortunately, I think my C++
rustiness is getting in the way. I get an error suggesting a constructor
is being treated as a function.

I've attached a diff in the hope that someone else can fix my attempt.

On 4/30/2016 2:01 AM, Oliver Brinzing wrote:



My previous, successful, debug compile was revision 1734822, March

13th 2016, so the problem has to

be something that has changed since then.


i checked output from pro an debug build:

debug creates an error C4150 while pro will continue with a warning

the different compiler setting are:

pro   -Gy -Oxs -Oy- -DPRODUCT -DNDEBUG -DOSL_DEBUG_LEVEL=0 -DOPTIMIZE

dbg   -Zi -Od -Z7 -Yd -D_STLP_DEBUG -DDEBUG -DDBG_UTIL
-DOSL_DEBUG_LEVEL=2
   -Fd../../wntmsci12/misc/sqliterator.pdb

Oliver




debug:
Compiling: connectivity/source/parse/sqliterator.cxx
C:/PROGRA~2/MICROS~1.0/VC/bin/cl.exe  -Zm500 -Zc:wchar_t- -GR -GS -c
-nologo -Gs  -Ob1 -Zi -Fd../../wntmsci12/misc/sqliterator.pdb  -Od
-DENABLE_LAYOUT=0 -DENABLE_LAYOUT_EXPERIMENTAL=0 -Gd -I.
-I../../wntmsci12/misc -I../../wntmsci12/inc/sql -I../inc
-I../../inc/pch -I../../inc -I../../WIN/inc -I../../wntmsci12/inc -I.
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/stl
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/external
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/inc -IC:/build_tmp/trunk/main/res
-IC:/build_tmp/trunk/main/tools/inc
-IC:/build_tmp/trunk/main/comphelper/inc
-IC:/PROGRA~2/Java/JDK17~1.0/include/win32
-IC:/PROGRA~2/Java/JDK17~1.0/include
-IC:/PROGRA~1/MICROS~1/Windows/v7.0/include
-IC:/PROGRA~2/MICROS~1.0/VC/include -IC:/PROGRA~2/MICROS~1/include
-IC:/PROGRA~2/MICROS~1/include
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/offuh -I. -I../../res
-I. -Z7 -Yd -Wall -wd4061 -wd4127 -wd4191 -wd4217 -wd4250 -wd4251
-wd4275 -wd4290 -wd4294 -wd4355 -wd4511 -wd4512 -wd4514 -wd4611
-wd4625 -wd4626 -wd4640 -wd4675 -wd4710 -wd4711 -wd4786 -wd4800
-wd4820 -wd4503 -wd4619-wd4365 -wd4668 -wd4738 -wd4826 -wd4350
-wd4505 -wd4692 -wd4189 -wd4005 -wd4180   -DWNT -DWNT -DNT351 -DMSC
-DM1500 -DINTEL -D_STLP_DEBUG -D_X86_=1 -D_CRT_SECURE_NO_DEPRECATE
-D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NON_CONFORMING_SWPRINTFS -DFULL_DESK
-DBOOST_MEM_FN_ENABLE_CDECL -D_MT -DWINVER=0x0500 -D_WIN32_WINNT=0x0500
-D_WIN32_IE=0x0500 -DCPPU_ENV=msci -DSUPD=420 -DDEBUG -DDBG_UTIL
-DOSL_DEBUG_LEVEL=2 -DCUI -DSOLAR_JAVA   -DOOO_DLLIMPLEMENTATION_DBTOOLS
-DSHAREDLIB -D_DLL_ -DWIN32 -D_MT -D_DLL -DWIN32 -D_MT -D_DLL  -EHa
-DEXCEPTIONS_ON -Fo../../wntmsci12/slo/sqliterator.obj
C:/build_tmp/trunk/main/connectivity/source/parse/sqliterator.cxx
sqliterator.cxx
C:\PROGRA~2\MICROS~1.0\VC\include\memory(721) : error C4150: deletion of
pointer to incomplete type 'connectivity::OSQLParser_Data'; no
destructor called




pro:
Compiling: connectivity/source/parse/sqliterator.cxx
C:/PROGRA~2/MICROS~1.0/VC/bin/cl.exe   -Zm500 -Zc:wchar_t- -GR -GS -c
-nologo -Gs  -Gy -Ob1 -Oxs -Oy- -DENABLE_LAYOUT=0
-DENABLE_LAYOUT_EXPERIMENTAL=0 -Gd  -I. -I../../wntmsci12.pro/misc
-I../../wntmsci12.pro/inc/sql -I../inc -I../../inc/pch -I../../inc
-I../../WIN/inc -I../../wntmsci12.pro/inc -I.
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc/stl
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc/external
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc
-IC:/build_tmp/trunk/main/solenv/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/inc -IC:/build_tmp/trunk/main/res
-IC:/build_tmp/trunk/main/tools/inc
-IC:/build_tmp/trunk/main/comphelper/inc
-IC:/PROGRA~2/Java/JDK17~1.0/include/win32
-IC:/PROGRA~2/Java/JDK17~1.0/include
-IC:/PROGRA~1/MICROS~1/Windows/v7.0/include
-IC:/PROGRA~2/MICROS~1.0/VC/include -IC:/PROGRA~2/MICROS~1/include
-IC:/PROGRA~2/MICROS~1/include
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc/offuh -I.
-I../../res -I. -Wall -wd4061 -wd4127 -wd4191 -wd4217 -wd4250 -wd4251
-wd4275 -wd4290 -wd4294 -wd4355 -wd4511 -wd4512 -wd4514 -wd4611
-wd4625 -wd4626 -wd4640 -wd4675 -wd4710 -wd4711 -wd4786 -wd4800
-wd4820 -wd4503 -wd4619-wd4365 -wd4668 -wd4738 -wd4826 -wd4350
-wd4505 -wd4692 -wd4189 -wd4005 -wd4180   -DWNT -DWNT -DNT351 -DMSC
-DM1500 -DINTEL -D_X86_=1 -D_CRT_SECURE_NO_DEPRECATE
-D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NON_CONFORMING_SWPRINTFS -DFULL_DESK

Re: Mentor

2016-05-25 Thread Patricia Shanahan


Hi Yacine,

I'll do what I can to help you, though I'm relatively new to OpenOffice. 
I am a very experienced developer, just not on this program.


Are you planning to use a Microsoft Windows system for building it? If 
so, you need to read 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1


The build process for OpenOffice is not simple. The code has to run on 
many different systems so there is a pre-compilation configuration 
process that runs scripts to prepare for your system. Do not assume that 
what you do for smaller, simpler programs will work for AOO.


Start following the steps, carefully and methodically. If anything goes 
wrong, ask for help.


Patricia

On 5/25/2016 2:42 AM, Yacine Abbes wrote:

Hi
Thank you for the reply. I've read link but i find it confusing and I'm not a 
developer although i do have some very basic experience.
Basically I need answers for the following:
(1) Which Window based SDK can edit OO source files?
(2) My personal objectives for OO is to be able to:
(2.a) Edit and redesign the graphical interface (menus, icons, ...) and change 
default settings in submenus, etc.  (2.b) Recompile and create an installer 
program
(3) Which project file should i open to do the above?
I would appreciate any guidance that will help with the above.
Best regards
Yacine



From: j...@oooes.org
To: dev@openoffice.apache.org
Subject: Re: Mentor
Date: Wed, 25 May 2016 01:24:03 -0500



On Wednesday, May 25, 2016 6:14:47 AM CDT Yacine Abbes wrote:

Hi
I'm new to OO development. I would appreciate if anyone would like like to
be a mentor? Best regards
Yacine

We have had mentoring programs in the past but most of the mentorage is done on 
the list mainly. Not everyone knows everything that happens on the code so 
asking the dev list allows to point more on the domains of the level of code.
For starter I would suggest to read on the wiki development pages including how 
the code is organized, and worked on.
https://wiki.openoffice.org/wiki/Development

Also try to compile the AOO version so your patches can be tested locally.



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

Re: Development updates

2016-05-13 Thread Patricia Shanahan

With the current instructions, it takes me a total of less than an hour 
to do the downloads, signature checks, build, and test the built software.


On 5/13/2016 5:05 PM, Carl Marcum wrote:
...

Hopefully I can get ONE more binding vote on the Groovy UNO Extension
vote so I can finish up the extension generators ;-)

...

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

Re: failed to build aoo420 dev on win32

2016-05-10 Thread Patricia Shanahan

I decided to try to fix the underlying error/warning, by making the 
header file declaration complete. Unfortunately, I think my C++ 
rustiness is getting in the way. I get an error suggesting a constructor 
is being treated as a function.


I've attached a diff in the hope that someone else can fix my attempt.

On 4/30/2016 2:01 AM, Oliver Brinzing wrote:



My previous, successful, debug compile was revision 1734822, March

13th 2016, so the problem has to

be something that has changed since then.


i checked output from pro an debug build:

debug creates an error C4150 while pro will continue with a warning

the different compiler setting are:

pro   -Gy -Oxs -Oy- -DPRODUCT -DNDEBUG -DOSL_DEBUG_LEVEL=0 -DOPTIMIZE

dbg   -Zi -Od -Z7 -Yd -D_STLP_DEBUG -DDEBUG -DDBG_UTIL
-DOSL_DEBUG_LEVEL=2
   -Fd../../wntmsci12/misc/sqliterator.pdb

Oliver



debug:
Compiling: connectivity/source/parse/sqliterator.cxx
C:/PROGRA~2/MICROS~1.0/VC/bin/cl.exe  -Zm500 -Zc:wchar_t- -GR -GS -c
-nologo -Gs  -Ob1 -Zi -Fd../../wntmsci12/misc/sqliterator.pdb  -Od
-DENABLE_LAYOUT=0 -DENABLE_LAYOUT_EXPERIMENTAL=0 -Gd -I.
-I../../wntmsci12/misc -I../../wntmsci12/inc/sql -I../inc
-I../../inc/pch -I../../inc -I../../WIN/inc -I../../wntmsci12/inc -I.
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/stl
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/external
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/inc -IC:/build_tmp/trunk/main/res
-IC:/build_tmp/trunk/main/tools/inc
-IC:/build_tmp/trunk/main/comphelper/inc
-IC:/PROGRA~2/Java/JDK17~1.0/include/win32
-IC:/PROGRA~2/Java/JDK17~1.0/include
-IC:/PROGRA~1/MICROS~1/Windows/v7.0/include
-IC:/PROGRA~2/MICROS~1.0/VC/include -IC:/PROGRA~2/MICROS~1/include
-IC:/PROGRA~2/MICROS~1/include
-IC:/build_tmp/trunk/main/solver/420/wntmsci12/inc/offuh -I. -I../../res
-I. -Z7 -Yd -Wall -wd4061 -wd4127 -wd4191 -wd4217 -wd4250 -wd4251
-wd4275 -wd4290 -wd4294 -wd4355 -wd4511 -wd4512 -wd4514 -wd4611
-wd4625 -wd4626 -wd4640 -wd4675 -wd4710 -wd4711 -wd4786 -wd4800
-wd4820 -wd4503 -wd4619-wd4365 -wd4668 -wd4738 -wd4826 -wd4350
-wd4505 -wd4692 -wd4189 -wd4005 -wd4180   -DWNT -DWNT -DNT351 -DMSC
-DM1500 -DINTEL -D_STLP_DEBUG -D_X86_=1 -D_CRT_SECURE_NO_DEPRECATE
-D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NON_CONFORMING_SWPRINTFS -DFULL_DESK
-DBOOST_MEM_FN_ENABLE_CDECL -D_MT -DWINVER=0x0500 -D_WIN32_WINNT=0x0500
-D_WIN32_IE=0x0500 -DCPPU_ENV=msci -DSUPD=420 -DDEBUG -DDBG_UTIL
-DOSL_DEBUG_LEVEL=2 -DCUI -DSOLAR_JAVA   -DOOO_DLLIMPLEMENTATION_DBTOOLS
-DSHAREDLIB -D_DLL_ -DWIN32 -D_MT -D_DLL -DWIN32 -D_MT -D_DLL  -EHa
-DEXCEPTIONS_ON -Fo../../wntmsci12/slo/sqliterator.obj
C:/build_tmp/trunk/main/connectivity/source/parse/sqliterator.cxx
sqliterator.cxx
C:\PROGRA~2\MICROS~1.0\VC\include\memory(721) : error C4150: deletion of
pointer to incomplete type 'connectivity::OSQLParser_Data'; no
destructor called



pro:
Compiling: connectivity/source/parse/sqliterator.cxx
C:/PROGRA~2/MICROS~1.0/VC/bin/cl.exe   -Zm500 -Zc:wchar_t- -GR -GS -c
-nologo -Gs  -Gy -Ob1 -Oxs -Oy- -DENABLE_LAYOUT=0
-DENABLE_LAYOUT_EXPERIMENTAL=0 -Gd  -I. -I../../wntmsci12.pro/misc
-I../../wntmsci12.pro/inc/sql -I../inc -I../../inc/pch -I../../inc
-I../../WIN/inc -I../../wntmsci12.pro/inc -I.
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc/stl
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc/external
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc
-IC:/build_tmp/trunk/main/solenv/wntmsci12/inc
-IC:/build_tmp/trunk/main/solenv/inc -IC:/build_tmp/trunk/main/res
-IC:/build_tmp/trunk/main/tools/inc
-IC:/build_tmp/trunk/main/comphelper/inc
-IC:/PROGRA~2/Java/JDK17~1.0/include/win32
-IC:/PROGRA~2/Java/JDK17~1.0/include
-IC:/PROGRA~1/MICROS~1/Windows/v7.0/include
-IC:/PROGRA~2/MICROS~1.0/VC/include -IC:/PROGRA~2/MICROS~1/include
-IC:/PROGRA~2/MICROS~1/include
-IC:/build_tmp/trunk/main/solver/420/wntmsci12.pro/inc/offuh -I.
-I../../res -I. -Wall -wd4061 -wd4127 -wd4191 -wd4217 -wd4250 -wd4251
-wd4275 -wd4290 -wd4294 -wd4355 -wd4511 -wd4512 -wd4514 -wd4611
-wd4625 -wd4626 -wd4640 -wd4675 -wd4710 -wd4711 -wd4786 -wd4800
-wd4820 -wd4503 -wd4619-wd4365 -wd4668 -wd4738 -wd4826 -wd4350
-wd4505 -wd4692 -wd4189 -wd4005 -wd4180   -DWNT -DWNT -DNT351 -DMSC
-DM1500 -DINTEL -D_X86_=1 -D_CRT_SECURE_NO_DEPRECATE
-D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NON_CONFORMING_SWPRINTFS -DFULL_DESK
-DBOOST_MEM_FN_ENABLE_CDECL -D_MT -DWINVER=0x0500 -D_WIN32_WINNT=0x0500
-D_WIN32_IE=0x0500 -DCPPU_ENV=msci -DSUPD=420 -DPRODUCT -DNDEBUG
-DOSL_DEBUG_LEVEL=0 -DOPTIMIZE -DCUI -DSOLAR_JAVA
-DOOO_DLLIMPLEMENTATION_DBTOOLS -DSHAREDLIB -D_DLL_ -DWIN32 -D_MT -D_DLL
-DWIN32 -D_MT -D_DLL  -EHa -DEXCEPTIONS_ON
-Fo../../wntmsci12.pro/slo/sqliterator.obj

Re: [VOTE] Release Groovy UNO Extension 0.1.5-RC1

2016-05-07 Thread Patricia Shanahan


+1 Approve

On 4/23/2016 8:23 AM, Carl Marcum wrote:

This is for a source release of Groovy UNO Extension 0.1.5 from Apache
OpenOffice
and binaries made available from Maven via Apache Nexus.

Source packages for RC1 are available at:
https://dist.apache.org/repos/dist/dev/openoffice/devtools/
and the reference revision is r1740645.

Binary Maven packages are staged here:
https://repository.apache.org/content/repositories/orgapacheopenoffice-1021/



Please review the release testing instruction wiki page:
https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing

The [VOTE] will conclude no sooner than Thursday 28 April, 14:00 UTC.

Please do not do anything but [VOTE] (with any -1 explanation) on this
thread.

To discuss this vote or the process, please use a [DISCUSS][VOTE] reply
rather than discussing on the [VOTE] thread.

3 binding +1 votes and a simple majority of votes are necessary for
approval.

So please VOTE on releasing RC1 (as defined above) as Groovy UNO
Extension 0.1.5:
[  ] +1 Approve
[  ]  0 Abstain
[  ] -1 Disapprove, with explanation

Thanks,
Carl


-
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: failed to build aoo420 dev on win32

2016-04-25 Thread Patricia Shanahan


On 4/25/2016 9:07 AM, Oliver Brinzing wrote:

I checked out the latest, and tried to build it. My debug build also

failed on sqliterator.cxx. I

used exactly the same configure parameters as on previous successful

debug builds.

thanks for testing, hopefully i will find some time to do further
investigation.


My previous, successful, debug compile was revision 1734822, March 13th 
2016, so the problem has to be something that has changed since then.


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

Re: failed to build aoo420 dev on win32

2016-04-23 Thread Patricia Shanahan

I checked out the latest, and tried to build it. My debug build also 
failed on sqliterator.cxx. I used exactly the same configure parameters 
as on previous successful debug builds.

Patricia

On 4/17/2016 12:34 PM, Oliver Brinzing wrote:

Hi,

this weekend i tried again and was able to build current aoo420 (product)
i had only one build break:

C:/build/cygwin/bin/perl checkdeliver.pl  -l
../wntmsci12.pro/misc/checkdeliver_log.txt &&
C:/build/cygwin/bin/touch.exe ../wntmsci12.pro/misc/checkdeliver.done
checkdeliver.pl - checking delivered binaries
Error: delivered file is older than it's source
'C:/build_tmp/trunk/main/sd/wntmsci12.pro/lib/sdi.lib'
'C:/build_tmp/trunk/main/solver/420/wntmsci12.pro/lib/sdi.lib'
1 errors found: Module 'sd' not delivered correctly?
dmake:  Error code 1, while making
'../wntmsci12.pro/misc/checkdeliver.done'

easy to fix, the delivered "sdi.lib" timestamp was older than that from
the source...

after that i tried to build a debug version - and failed again:

[...]
--disable-strip-solver \
--enable-symbols \
--enable-dbgutil \
--enable-crashdump \
--disable-unit-tests   -> will avoid windows build breaks in module
crashrep - Assertion Failed
 https://bz.apache.org/ooo/show_bug.cgi?id=126918

build debug=true --all --html -P2 -- -P2

same build breaks as mentioned before:

 >> windows build breaks in module
connectivity/source/parse/sqliterator.cxx
 >> https://bz.apache.org/ooo/show_bug.cgi?id=126917

 >> windows build breaks in module formula
 >> https://bz.apache.org/ooo/show_bug.cgi?id=126916

Regards
Oliver

-
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: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4-RC2


On 4/21/2016 3:12 PM, Carl Marcum wrote:

On 04/21/2016 02:09 PM, Patricia Shanahan wrote:

The .class files in the uploaded .jar were compiled with Java 1.8:

Patricia@Jan2014Desktop
/cygdrive/c/Users/Patricia/.groovy/grapes/org.openoffice/guno-extension/jars

$ !find
find . -type f -name '*.class' -exec file '{}' ';' -print
./org/openoffice/guno/SpreadsheetExtension.class: compiled Java class
data, version 52.0 (Java 1.8)
./org/openoffice/guno/SpreadsheetExtension.class
./org/openoffice/guno/UnoExtension.class: compiled Java class data,
version 52.0 (Java 1.8)
./org/openoffice/guno/UnoExtension.class

so Groovy will need a 1.8 JRE to run them.

On 4/21/2016 10:47 AM, Patricia Shanahan wrote:

After some more testing: It works with JDK1.8 or JRE1.8, 32-bit or
64-bit in each case.

However, it fails with the following output using jdk1.7.0_79.


Looks like I overlooked that.

If that gives people any issues I can add

|sourceCompatibility=  1.6
targetCompatibility=  1.6

to the gradle.build file to fix it and create a new RC.


I think it's your call. I have no need to use anything before 1.8 - I 
was just testing for completeness. 1.8 is the current version.


On the other hand, it takes less than an hour to do the complete test 
sequence, so no big deal if you decide to make a new release candidate.


Patricia


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

Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4-RC2


The .class files in the uploaded .jar were compiled with Java 1.8:

Patricia@Jan2014Desktop 
/cygdrive/c/Users/Patricia/.groovy/grapes/org.openoffice/guno-extension/jars

$ !find
find . -type f -name '*.class' -exec file '{}' ';' -print
./org/openoffice/guno/SpreadsheetExtension.class: compiled Java class 
data, version 52.0 (Java 1.8)

./org/openoffice/guno/SpreadsheetExtension.class
./org/openoffice/guno/UnoExtension.class: compiled Java class data, 
version 52.0 (Java 1.8)

./org/openoffice/guno/UnoExtension.class

so Groovy will need a 1.8 JRE to run them.

On 4/21/2016 10:47 AM, Patricia Shanahan wrote:

After some more testing: It works with JDK1.8 or JRE1.8, 32-bit or
64-bit in each case.

However, it fails with the following output using jdk1.7.0_79.

Patricia@Jan2014Desktop /cygdrive/c/OpenOfficeDev/GroovyUNO/test
$ !gr
groovy *.groovy
Apr 21, 2016 10:03:31 AM
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [guno-module] - Unable to load extension class
[org.openoffice.guno.UnoExtension]
Apr 21, 2016 10:03:31 AM
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [guno-module] - Unable to load extension class
[org.openoffice.guno.SpreadsheetExtension]
Apr 21, 2016 10:03:50 AM
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [guno-module] - Unable to load extension class
[org.openoffice.guno.UnoExtension]
Apr 21, 2016 10:03:50 AM
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [guno-module] - Unable to load extension class
[org.openoffice.guno.SpreadsheetExtension]
Connected to a running office ...
No signature of method: com.sun.proxy.$Proxy5.guno() is applicable for
argument types: (java.lang.Class) values: [interface
com.sun.star.frame.XComponentLoader]
Possible solutions: any(), dump(), find(), grep(),
find(groovy.lang.Closure), any(groovy.lang.Closure)
groovy.lang.MissingMethodException: No signature of method:
com.sun.proxy.$Proxy5.guno() is applicable for argument types:
(java.lang.Class) values: [interface com.sun.star.frame.XComponentLoader]
Possible solutions: any(), dump(), find(), grep(),
find(groovy.lang.Closure), any(groovy.lang.Closure)
 at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:58)

 at
org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:49)

 at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)

 at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)

 at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)

 at
HelloTextTableShape.newDocComponent(HelloTextTableShape.groovy:415)
 at HelloTextTableShape.useWriter(HelloTextTableShape.groovy:130)
 at
HelloTextTableShape.useDocuments(HelloTextTableShape.groovy:122)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

 at java.lang.reflect.Method.invoke(Method.java:606)
 at
org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:210)

 at
org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.call(PogoMetaMethodSite.java:71)

 at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)

 at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)

 at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)

 at HelloTextTableShape.main(HelloTextTableShape.groovy:109)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

 at java.lang.reflect.Method.invoke(Method.java:606)
 at
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
 at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
 at
groovy.lang.MetaClassImpl.invokeStaticMethod(MetaClassImpl.java:1445)
 at
org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:897)

 at
groovy.lang.GroovyShell.runScriptOrMainOrTestOrRunnable(GroovyShell.java:287)

 at groovy.lang.GroovyShell.run(GroovyShell.java:518)
 at groovy.lang.GroovyShell.run(GroovyShell.java:507)
 at groovy.ui.GroovyMain.processOnce(GroovyMain.java:652)
 at groovy.ui.GroovyMain.run(GroovyMain.java:384)
 at groovy.ui.GroovyMain.process(GroovyMain.java:370)
 at groovy.ui.GroovyMain.processArgs

Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4-RC2

After some more testing: It works with JDK1.8 or JRE1.8, 32-bit or 
64-bit in each case.


However, it fails with the following output using jdk1.7.0_79.

Patricia@Jan2014Desktop /cygdrive/c/OpenOfficeDev/GroovyUNO/test
$ !gr
groovy *.groovy
Apr 21, 2016 10:03:31 AM 
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [guno-module] - Unable to load extension class 
[org.openoffice.guno.UnoExtension]
Apr 21, 2016 10:03:31 AM 
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [guno-module] - Unable to load extension class 
[org.openoffice.guno.SpreadsheetExtension]
Apr 21, 2016 10:03:50 AM 
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [guno-module] - Unable to load extension class 
[org.openoffice.guno.UnoExtension]
Apr 21, 2016 10:03:50 AM 
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [guno-module] - Unable to load extension class 
[org.openoffice.guno.SpreadsheetExtension]

Connected to a running office ...
No signature of method: com.sun.proxy.$Proxy5.guno() is applicable for 
argument types: (java.lang.Class) values: [interface 
com.sun.star.frame.XComponentLoader]
Possible solutions: any(), dump(), find(), grep(), 
find(groovy.lang.Closure), any(groovy.lang.Closure)
groovy.lang.MissingMethodException: No signature of method: 
com.sun.proxy.$Proxy5.guno() is applicable for argument types: 
(java.lang.Class) values: [interface com.sun.star.frame.XComponentLoader]
Possible solutions: any(), dump(), find(), grep(), 
find(groovy.lang.Closure), any(groovy.lang.Closure)
at 
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:58)
at 
org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:49)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
at 
HelloTextTableShape.newDocComponent(HelloTextTableShape.groovy:415)

at HelloTextTableShape.useWriter(HelloTextTableShape.groovy:130)
at HelloTextTableShape.useDocuments(HelloTextTableShape.groovy:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:210)
at 
org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.call(PogoMetaMethodSite.java:71)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)

at HelloTextTableShape.main(HelloTextTableShape.groovy:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)

at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at 
groovy.lang.MetaClassImpl.invokeStaticMethod(MetaClassImpl.java:1445)
at 
org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:897)
at 
groovy.lang.GroovyShell.runScriptOrMainOrTestOrRunnable(GroovyShell.java:287)

at groovy.lang.GroovyShell.run(GroovyShell.java:518)
at groovy.lang.GroovyShell.run(GroovyShell.java:507)
at groovy.ui.GroovyMain.processOnce(GroovyMain.java:652)
at groovy.ui.GroovyMain.run(GroovyMain.java:384)
at groovy.ui.GroovyMain.process(GroovyMain.java:370)
at groovy.ui.GroovyMain.processArgs(GroovyMain.java:129)
at groovy.ui.GroovyMain.main(GroovyMain.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:109)
at 
org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:131)

Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4-RC2

Like all sane Java-using programs, Groovy seems to be perfectly happy 
with a 64-bit JDK. In the shell I have been using for my UNO-testing:


Patricia@Jan2014Desktop /cygdrive/c/OpenOfficeDev/GroovyUNO/test
$ echo $JAVA_HOME
C:/Program Files/Java/jdk1.8.0_71

which is a 64-bit release 8 JDK.

I'll do some tests and enhance the instructions to deal with JAVA_HOME. 
We also need explicit instructions on installing Groovy and Gradle so 
that people who are not already familiar with them can do the tests.


Patricia

On 4/21/2016 8:47 AM, Dennis E. Hamilton wrote:

I am having a different kind of difficulty.  I think this experience is more for the 
Apache Groovy project, but some of it might apply to our prerequisites at 
.

  1. I chose to use the Groovy 2.4.6 Windows Installer (.exe).

  2. I do have a JRE and a JDK installed, but there is a confusing report, as 
if Groovy can't find it or is not clear which to use.  (I think I have both 
32-bit and a 64-bit installed.)

  3. Although there is a report that JAVA_HOME needs to be set (it isn't), 
Groovy does find the JRE anyhow.  I think that is because it defaulted to 
32-bit for the install.

  4. The installer sets the search path for Groovy incorrectly.  I am going to 
correct the search path and see how much farther I can get.

  5. I will report some of this to Apache Groovy.

Meanwhile, this awkward since my goal is not to become adept with Groovy and 
Gradle but to see if I can reproduce the tests and confirm the Release 
Candidate.  It is difficult to be confident in what I am doing.

  - Dennis


-Original Message-
From: Carl Marcum [mailto:cmar...@apache.org]
Sent: Wednesday, April 20, 2016 15:38
To: dev@openoffice.apache.org
Subject: Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4-RC2


[ ... ]


[]$ gpg --verify guno-extension-0.1.4-r1740035-src.zip.asc
gpg: assuming signed data in `guno-extension-0.1.4-r1740035-src.zip'
gpg: Signature made Wed 20 Apr 2016 06:20:30 PM EDT using RSA key ID
9553BF9A
gpg: Good signature from "Carl Marcum (CODE SIGNING KEY)
"
gpg: aka "Carl Marcum (CODE SIGNING KEY)
"
[]$ gpg --verify guno-extension-0.1.4-r1740035-src.tar.gz.asc
gpg: assuming signed data in `guno-extension-0.1.4-r1740035-src.tar.gz'
gpg: Signature made Tue 19 Apr 2016 10:00:01 PM EDT using RSA key ID
9553BF9A
gpg: Good signature from "Carl Marcum (CODE SIGNING KEY)
"
gpg: aka "Carl Marcum (CODE SIGNING KEY)
"

[]$ md5sum --check guno-extension-0.1.4-r1740035-src.zip.md5
guno-extension-0.1.4-r1740035-src.zip: OK
[]$ md5sum --check guno-extension-0.1.4-r1740035-src.tar.gz.md5
guno-extension-0.1.4-r1740035-src.tar.gz: OK

Sorry for the inconvenience.

Thanks,
Carl


-
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: [VOTE] Release Groovy UNO Extension 0.1.4-RC2

2016-04-20 Thread Patricia Shanahan


+1 Approve (binding)

On 4/19/2016 7:35 PM, Carl Marcum wrote:

This is for a source release of Groovy UNO Extension 0.1.4 from Apache
OpenOffice
and binaries made available from Maven via Apache Nexus.

Source packages for RC2 are available at:
https://dist.apache.org/repos/dist/dev/openoffice/devtools/
and the reference revision is r1740035.

Binary Maven packages are staged here:
https://repository.apache.org/content/repositories/orgapacheopenoffice-1019/



Please review the release testing instruction wiki page:
https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing

The [VOTE] will conclude no sooner than Monday 25 April, 14:00 UTC.

Please do not do anything but [VOTE] (with any -1 explanation) on this
thread.

To discuss this vote or the process, please use a [DISCUSS][VOTE] reply
rather than discussing on the [VOTE] thread.

3 binding +1 votes and a simple majority of votes are necessary for
approval.

So please VOTE on releasing RC2 (as defined above) as Groovy UNO
Extension 0.1.4:
[  ] +1 Approve
[  ]  0 Abstain
[  ] -1 Disapprove, with explanation

Thanks,
Carl

-
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

[DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4-RC2

2016-04-20 Thread Patricia Shanahan

I did a signature check on the files. The md5 checks both passed. The 
tar.gz.asc check also passed, but the .zip.asc check failed:


Patricia@Jan2014Desktop /cygdrive/c/OpenOfficeDev/GroovyUNO/signatures
$ gpg --verify guno-extension-0.1.4-r1740035-src.tar.gz.asc
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/documentation/faqs.html for more 
information

gpg: assuming signed data in `guno-extension-0.1.4-r1740035-src.tar.gz'
gpg: Signature made Tue, Apr 19, 2016  7:00:01 PM PDT using RSA key ID 
9553BF9A
gpg: Good signature from "Carl Marcum (CODE SIGNING KEY) 
"
gpg: aka "Carl Marcum (CODE SIGNING KEY) 
"

gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the 
owner.

Primary key fingerprint: 813A C3C2 48B3 F26F B5D1  EB32 F1DA 7E3B 9553 BF9A

Patricia@Jan2014Desktop /cygdrive/c/OpenOfficeDev/GroovyUNO/signatures
$ gpg --verify guno-extension-0.1.4-r1740035-src.zip.asc
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/documentation/faqs.html for more 
information

gpg: assuming signed data in `guno-extension-0.1.4-r1740035-src.zip'
gpg: Signature made Tue, Apr 19, 2016  6:57:12 PM PDT using RSA key ID 
9553BF9A
gpg: BAD signature from "Carl Marcum (CODE SIGNING KEY) 
"


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

Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4 - PLEASE VOTE

2016-04-19 Thread Patricia Shanahan


On 4/19/2016 3:22 PM, Patricia Shanahan wrote:

On 4/19/2016 4:20 AM, Carl Marcum wrote:

On 04/18/2016 07:04 AM, Carl Marcum wrote:

...

I have the most of what I wanted to add to the release testing page [1]
done.

If you would like to review and make any changes or additions feel
free. :)


I have added a process I devised for verifying that the test procedure
really does test the locally built jar. I'm not sure that step is
necessary for every PMC member intended to cast a binding +1 vote, but I
did feel it should be done at least once.

Now that we have a documented build and test procedure, I hope more PMC
members will run the test and cast binding votes.


The test procedure is described in
https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing

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

Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4

2016-04-19 Thread Patricia Shanahan


On 4/19/2016 4:20 AM, Carl Marcum wrote:

On 04/18/2016 07:04 AM, Carl Marcum wrote:

...

I have the most of what I wanted to add to the release testing page [1]
done.

If you would like to review and make any changes or additions feel free. :)


I have added a process I devised for verifying that the test procedure 
really does test the locally built jar. I'm not sure that step is 
necessary for every PMC member intended to cast a binding +1 vote, but I 
did feel it should be done at least once.


Now that we have a documented build and test procedure, I hope more PMC 
members will run the test and cast binding votes.


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

Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4

2016-04-17 Thread Patricia Shanahan


Test successful!

The jar-copying procedure worked. I think we do need a step-by-step Wiki 
page covering both Linux and MS-Windows. Do you want to start it? I can 
add details of what I did for Windows.


I need to do some signature checks, and then I'll +1 in the VOTE thread.

We will need a third PMC members to cast a binding +1 vote, but I'm 
hoping having step-by-step instructions will inspire someone.


Patricia

On 4/17/2016 4:27 PM, Carl Marcum wrote:

On 04/15/2016 10:01 PM, Patricia Shanahan wrote:



On 4/15/2016 6:52 PM, Carl Marcum wrote:

On 04/15/2016 09:21 PM, Patricia Shanahan wrote:

...

Do I need to run it in any particular directory? How does it find the
.jar I built?



It doesn't need to find the jar you built.

There is one pre-built from the RC and staged in Apache Nexus
repository.

...

I need to test the code I built before voting on the release. I think
the intent is that each PMC member casting a binding +1 vote knows the
supplied source code can be used to build a working version of the
software.

"Before voting +1 PMC members are required to download the signed
source code package, compile it as provided, and test the resulting
executable on their own platform..."

http://www.apache.org/dev/release.html#approving-a-release



Hi Patricia,

After going to Legal about this problem I got a great suggestion that
requires running the test script once, thus downloading the staged
release jar and setting up the local Groovy Ivy cache. Then build the
test jar from the RC sources and replace the jar in the Ivy cache.

Apologies in advance for the below instructions as I didn't have a lot
of time this weekend. I should create a wiki page for this as it's kind
of long.

Testing the guno-extension staged in Apache Nexus
-
Download the HelloTextTableShape.groovy test script from bugzilla

If using Windows or a Linux with a soffice executable location other
than "/opt/openoffice4/program/".
Edit the test script for the location of the soffice executable.
A Windows example would look like: "C:/Program Files (x86)/OpenOffice
4/program"

Run the script from the download location
groovy HelloTextTableShape.groovy

The script should bootstrap the office and add sample content to some of
the applications using the guno-extension jar.
Close OpenOffice after the test.

running the script should download the jars to the local Groovy Ivy cache
On my Fedora Linux machine it is here:
~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.jar



Testing the downloaded source
---

unpack the source jar
This will be the guno-extension test directory

If using Windows or a Linux with a soffice executable location other
than "/opt/openoffice4/program/".
Edit the two Spock test files for the location of the soffice executable.
src/test/groovy/org/openoffice/guno/SpreadsheetSpec.groovy and
UnoSpec.groovy
The default location is:
String oooExeFolder = "/opt/openoffice4/program/"

Do the test build.
(From guno-extension test directory)
gradle jar

rename the downloaded jar in the local Groovy Ivy cache
(From guno-extension test directory)
mv
~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.jar
~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.save


copy the test jar into it's place
cp ./build/libs/guno-extension-0.1.4.jar
~/.groovy/grapes/org.openoffice/guno-extension/jars/

edit the HelloTextTableShape.groovy script and comment out the grab
resolver for the staging area. This will make sure it can't see the
staged jar.
Groovy should find the newly built jar in the Ivy cache.
// @GrabResolver(name = 'guno', root =
'https://repository.apache.org/content/repositories/orgapacheopenoffice-1019/')


run the test script again to test the newly built jar.

groovy HelloTextTableShape.groovy

Once finished you can remove the test jar from Ivy and rename the
guno-extension-0.1.4.save back to .jar

Please let me know if you have any questions.

Thanks,
Carl


-
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: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4

2016-04-17 Thread Patricia Shanahan


On 4/17/2016 5:48 PM, Patricia Shanahan wrote:



On 4/17/2016 4:27 PM, Carl Marcum wrote:



I'll try to work with these instructions, and go on asking questions
whenever I get stuck. I have saved all the e-mails in this thread, and
in any case they are in the archive. I think we should aim for a
step-by-step Wiki page that may inspire another Windows-using PMC member
to attempt the build and test.



Testing the guno-extension staged in Apache Nexus
-
Download the HelloTextTableShape.groovy test script from bugzilla

If using Windows or a Linux with a soffice executable location other
than "/opt/openoffice4/program/".
Edit the test script for the location of the soffice executable.
A Windows example would look like: "C:/Program Files (x86)/OpenOffice
4/program"

Run the script from the download location
groovy HelloTextTableShape.groovy


Running the groovy script requires either a javac in the path or 
JAVA_HOME set to a jdk.


For example:
export JAVA_HOME='C:/Program Files/Java/jdk1.8.0_71'

With that addition, the test of the downloaded jar was successful. I'll 
try the next step later.





The script should bootstrap the office and add sample content to some of
the applications using the guno-extension jar.
Close OpenOffice after the test.

running the script should download the jars to the local Groovy Ivy cache
On my Fedora Linux machine it is here:
~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.jar




Testing the downloaded source
---

unpack the source jar
This will be the guno-extension test directory

If using Windows or a Linux with a soffice executable location other
than "/opt/openoffice4/program/".
Edit the two Spock test files for the location of the soffice executable.
src/test/groovy/org/openoffice/guno/SpreadsheetSpec.groovy and
UnoSpec.groovy
The default location is:
String oooExeFolder = "/opt/openoffice4/program/"

Do the test build.
(From guno-extension test directory)
gradle jar

rename the downloaded jar in the local Groovy Ivy cache
(From guno-extension test directory)
mv
~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.jar

~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.save



copy the test jar into it's place
cp ./build/libs/guno-extension-0.1.4.jar
~/.groovy/grapes/org.openoffice/guno-extension/jars/

edit the HelloTextTableShape.groovy script and comment out the grab
resolver for the staging area. This will make sure it can't see the
staged jar.
Groovy should find the newly built jar in the Ivy cache.
// @GrabResolver(name = 'guno', root =
'https://repository.apache.org/content/repositories/orgapacheopenoffice-1019/')



run the test script again to test the newly built jar.

groovy HelloTextTableShape.groovy

Once finished you can remove the test jar from Ivy and rename the
guno-extension-0.1.4.save back to .jar

Please let me know if you have any questions.

Thanks,
Carl


-
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: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4

2016-04-17 Thread Patricia Shanahan




On 4/17/2016 4:27 PM, Carl Marcum wrote:

On 04/15/2016 10:01 PM, Patricia Shanahan wrote:



On 4/15/2016 6:52 PM, Carl Marcum wrote:

On 04/15/2016 09:21 PM, Patricia Shanahan wrote:

...

Do I need to run it in any particular directory? How does it find the
.jar I built?



It doesn't need to find the jar you built.

There is one pre-built from the RC and staged in Apache Nexus
repository.

...

I need to test the code I built before voting on the release. I think
the intent is that each PMC member casting a binding +1 vote knows the
supplied source code can be used to build a working version of the
software.

"Before voting +1 PMC members are required to download the signed
source code package, compile it as provided, and test the resulting
executable on their own platform..."

http://www.apache.org/dev/release.html#approving-a-release



Hi Patricia,

After going to Legal about this problem I got a great suggestion that
requires running the test script once, thus downloading the staged
release jar and setting up the local Groovy Ivy cache. Then build the
test jar from the RC sources and replace the jar in the Ivy cache.

Apologies in advance for the below instructions as I didn't have a lot
of time this weekend. I should create a wiki page for this as it's kind
of long.


I'll try to work with these instructions, and go on asking questions 
whenever I get stuck. I have saved all the e-mails in this thread, and 
in any case they are in the archive. I think we should aim for a 
step-by-step Wiki page that may inspire another Windows-using PMC member 
to attempt the build and test.




Testing the guno-extension staged in Apache Nexus
-
Download the HelloTextTableShape.groovy test script from bugzilla

If using Windows or a Linux with a soffice executable location other
than "/opt/openoffice4/program/".
Edit the test script for the location of the soffice executable.
A Windows example would look like: "C:/Program Files (x86)/OpenOffice
4/program"

Run the script from the download location
groovy HelloTextTableShape.groovy

The script should bootstrap the office and add sample content to some of
the applications using the guno-extension jar.
Close OpenOffice after the test.

running the script should download the jars to the local Groovy Ivy cache
On my Fedora Linux machine it is here:
~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.jar



Testing the downloaded source
---

unpack the source jar
This will be the guno-extension test directory

If using Windows or a Linux with a soffice executable location other
than "/opt/openoffice4/program/".
Edit the two Spock test files for the location of the soffice executable.
src/test/groovy/org/openoffice/guno/SpreadsheetSpec.groovy and
UnoSpec.groovy
The default location is:
String oooExeFolder = "/opt/openoffice4/program/"

Do the test build.
(From guno-extension test directory)
gradle jar

rename the downloaded jar in the local Groovy Ivy cache
(From guno-extension test directory)
mv
~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.jar
~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.save


copy the test jar into it's place
cp ./build/libs/guno-extension-0.1.4.jar
~/.groovy/grapes/org.openoffice/guno-extension/jars/

edit the HelloTextTableShape.groovy script and comment out the grab
resolver for the staging area. This will make sure it can't see the
staged jar.
Groovy should find the newly built jar in the Ivy cache.
// @GrabResolver(name = 'guno', root =
'https://repository.apache.org/content/repositories/orgapacheopenoffice-1019/')


run the test script again to test the newly built jar.

groovy HelloTextTableShape.groovy

Once finished you can remove the test jar from Ivy and rename the
guno-extension-0.1.4.save back to .jar

Please let me know if you have any questions.

Thanks,
Carl


-
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: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4




On 4/15/2016 6:52 PM, Carl Marcum wrote:

On 04/15/2016 09:21 PM, Patricia Shanahan wrote:

...

Do I need to run it in any particular directory? How does it find the
.jar I built?



It doesn't need to find the jar you built.

There is one pre-built from the RC and staged in Apache Nexus repository.

...

I need to test the code I built before voting on the release. I think 
the intent is that each PMC member casting a binding +1 vote knows the 
supplied source code can be used to build a working version of the software.


"Before voting +1 PMC members are required to download the signed source 
code package, compile it as provided, and test the resulting executable 
on their own platform..."


http://www.apache.org/dev/release.html#approving-a-release


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

Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4




On 4/15/2016 5:05 PM, Carl Marcum wrote:

On 04/15/2016 07:12 PM, Patricia Shanahan wrote:

On 4/15/2016 3:40 AM, Carl Marcum wrote:
...

Did you have a chance to try the HelloTextTableShape.groovy test script
that I placed in Bugzilla [3]?

...

Instructions for running it? What do I need to set up?



Hi Patricia,

Download it from the bugzilla issue attached to:
https://bz.apache.org/ooo/show_bug.cgi?id=126770

It's a rewrite of HelloTextTableShape.java provided with the SDK.
It will pull down the guno-extension artifact from Apache Nexus.

Edit the script (if needed) for the location of AOO soffice executable
as you did with the guno-extension script.

run with 'groovy HelloTextTableShape.groovy'

Please let me know if you have any questions.


Do I need to run it in any particular directory? How does it find the 
.jar I built?


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

Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4


On 4/15/2016 3:40 AM, Carl Marcum wrote:
...

Did you have a chance to try the HelloTextTableShape.groovy test script
that I placed in Bugzilla [3]?

...

Instructions for running it? What do I need to set up?

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

Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4