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

2016-04-22 Thread Carl Marcum 

On 04/21/2016 08:35 PM, Patricia Shanahan wrote:

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



I think it is important enough to create a new RC.

I know Java 7 is EOL but I'm aware there are reasons for some 
environments to stay on 7.


Plus this will give me a chance to finalize my RC instructions :)

Carl


-
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

2016-04-21 Thread Patricia Shanahan 

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

2016-04-21 Thread Carl Marcum 

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.

Thanks,
Carl

|



-
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

2016-04-21 Thread Patricia Shanahan 

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

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

2016-04-21 Thread Patricia Shanahan 
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

2016-04-21 Thread Patricia Shanahan 
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 
<https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing>.

  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)
<cmar...@apache.org>"
gpg: aka "Carl Marcum (CODE SIGNING KEY)
<carl.mar...@codebuilders.net>"
[]$ 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)
<cmar...@apache.org>"
gpg: aka "Carl Marcum (CODE SIGNING KEY)
<carl.mar...@codebuilders.net>"

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

2016-04-21 Thread Dennis E. Hamilton 
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 <https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing>.

 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)
> <cmar...@apache.org>"
> gpg: aka "Carl Marcum (CODE SIGNING KEY)
> <carl.mar...@codebuilders.net>"
> []$ 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)
> <cmar...@apache.org>"
> gpg: aka "Carl Marcum (CODE SIGNING KEY)
> <carl.mar...@codebuilders.net>"
> 
> []$ 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

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

2016-04-20 Thread Carl Marcum 

On 04/20/2016 12:50 PM, Patricia Shanahan wrote:
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



I must not have verified that one.

It should be fixed now.  I corrected the one .zip.asc file.

I downloaded them and verified:

[]$ 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

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

2016-04-19 Thread Carl Marcum 

On 04/19/2016 06:29 PM, Patricia Shanahan wrote:

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



Thanks Patricia,

It does no harm to make sure.

I think I should create a new RC with the updated gradle.properties file 
included.


I will post a new VOTE thread with the updated information.

Thanks for the great help !!

Regards,
Carl

-
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-19 Thread Carl Marcum 

On 04/18/2016 07:04 AM, Carl Marcum wrote:

On 04/17/2016 08:48 PM, Patricia Shanahan wrote:



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.



Hi Patricia,

I have created a testing page [1] and a RC release prep page [2] and
added links to the original page [3].

I can start on them this evening.

[1] https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing
[2] https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Preparation
[3] https://wiki.openoffice.org/wiki/Groovy_UNO_Extension

Thanks for your help !!



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



Hi Patricia,

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 can start on the release preparation page next.

Thanks,
Carl

[1] 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-18 Thread Dennis E. Hamilton 
Nice collaborative work, as always [;<).

 - Dennis

> -Original Message-
> From: Carl Marcum [mailto:cmar...@apache.org]
> Sent: Monday, April 18, 2016 04:04
> To: dev@openoffice.apache.org
> Subject: Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4
> 
> On 04/17/2016 08:48 PM, Patricia Shanahan 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.
> >
> 
> Hi Patricia,
> 
> I have created a testing page [1] and a RC release prep page [2] and
> added links to the original page [3].
> 
> I can start on them this evening.
> 
> [1] https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing
> [2] https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Preparation
> [3] https://wiki.openoffice.org/wiki/Groovy_UNO_Extension
> 
> Thanks for your help !!
[ ... ]


-
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-18 Thread Carl Marcum 

On 04/17/2016 08:48 PM, Patricia Shanahan wrote:



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.




Hi Patricia,

I have created a testing page [1] and a RC release prep page [2] and 
added links to the original page [3].


I can start on them this evening.

[1] https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing
[2] https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Preparation
[3] https://wiki.openoffice.org/wiki/Groovy_UNO_Extension

Thanks for your help !!



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




-
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

2016-04-17 Thread Carl Marcum 

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

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

2016-04-15 Thread Patricia Shanahan 



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

2016-04-15 Thread Carl Marcum 

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



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?




It doesn't need to find the jar you built.

There is one pre-built from the RC and staged in Apache Nexus repository.

Gradle will pull it from the Apache Nexus staging area and place it in a 
local cache.


The other Java UNO jars and the bootstrap-connector are pulled from the 
main Maven Repository as they have been previously released.


You can run it from where ever you download it to.

Thanks,
Carl


-
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-15 Thread Patricia Shanahan 



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

2016-04-15 Thread Carl Marcum 

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.

Thanks,
Carl


-
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-15 Thread Patricia Shanahan 

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

2016-04-15 Thread Patricia Shanahan 



On 4/15/2016 3:40 AM, Carl Marcum wrote:

On 04/14/2016 10:18 PM, Patricia Shanahan wrote:

On 4/14/2016 6:29 PM, Carl Marcum wrote:

On 04/14/2016 08:10 PM, Patricia Shanahan wrote:

On 4/14/2016 3:28 AM, Carl Marcum wrote:

On 04/14/2016 12:57 AM, Patricia Shanahan wrote:



On 4/6/2016 3:27 AM, Carl Marcum wrote:

On 04/05/2016 09:57 PM, Patricia Shanahan wrote:

I think you will get more votes with more instructions.

I've never done a gradle build, and have no idea how to do one. I'm
sure I could find out, but that is going to take time.



...

If you don't go that route you can get Gradle here:
http://gradle.org/gradle-download/

Once you have it installed you can build the project with 'gradle
jar'



$ gradle jar

FAILURE: Build failed with an exception.

* Where:
Build file
'C:\OpenOfficeDev\GroovyUNO\guno-extension-0.1.4\build.gradle'
line: 83

* What went wrong:
A problem occurred evaluating root project 'guno-extension-0.1.4'.
> No such property: mavenUser for class:
org.gradle.api.publication.maven.internal.deployer.DefaultGroovyMavenDeployer





Hi Patricia,

Looks like Gradle is evaluating variables that are read from my
~/.gradle/gradle.properties file.
These are variables that a user needs to keep out of SVN.

There is also a gradle.properties file under the project root, please
add this and retry the build.
Here is what I have in my gradle.properties:

signing.keyId=12345678
signing.password=my key password
signing.secretKeyRingFile=/path/to/keyring.gpg
mavenUser=mavenUser
mavenPassword=mavenPassword

You don't need to edit the values.

If this solves it for you I can patch the RC and try again.


Are you sure I should need to use a maven account to do this test?


No you don't need a maven account to run the jar task.  Only add the
properties and values to the currently empty gradle.properties file
under the project directory.
Edit this file:
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4/gradle.properties

by adding this text as-is:

signing.keyId=12345678
signing.password=my key password
signing.secretKeyRingFile=/path/to/keyring.gpg
mavenUser=mavenUser
mavenPassword=mavenPassword


  The gradle.build script will look for undefined variables in this
gradle.properties file first and then in ~/.groovy/gradle.properties
which is where my real ones were so the didn't end up in SVN.

These will not actually be used for anything unless the uploadArchives
task is ran which will create jars, sign them, and upload to Maven
repository.


Thanks. It built, though with one error code message:

Patricia@Jan2014Desktop
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4
$ gradle jar
:clean UP-TO-DATE
:compileJava UP-TO-DATE
:compileGroovy
:processResources
:classes
:groovydoc
Could not open/create prefs root node Software\JavaSoft\Prefs at root
0x8002. Windows RegCreateKeyEx(...) returned error code 5.
:jar

BUILD SUCCESSFUL

Total time: 48.871 secs



Hi Patricia,

That's great.

What java version of JDK are you running?  It may be related to [1] or [2].

Did you have a chance to try the HelloTextTableShape.groovy test script
that I placed in Bugzilla [3]?

I'll create a new RC to add that content to build.properties this evening.

[1]
http://stackoverflow.com/questions/16428098/groovy-shell-warning-could-not-open-create-prefs-root-node

[2] http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6790382
[3] https://bz.apache.org/ooo/show_bug.cgi?id=126770


I have not yet tested the script. That is on my todo list for today. I 
suggest holding off on creating a new RC until I get all the way through 
the process. That way, you can do it once for any and all changes we find.


Java version:

Patricia@Jan2014Desktop 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4

$ java -version
java version "1.8.0_73"
Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)


-
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-15 Thread Carl Marcum 

On 04/14/2016 10:18 PM, Patricia Shanahan wrote:

On 4/14/2016 6:29 PM, Carl Marcum wrote:

On 04/14/2016 08:10 PM, Patricia Shanahan wrote:

On 4/14/2016 3:28 AM, Carl Marcum wrote:

On 04/14/2016 12:57 AM, Patricia Shanahan wrote:



On 4/6/2016 3:27 AM, Carl Marcum wrote:

On 04/05/2016 09:57 PM, Patricia Shanahan wrote:

I think you will get more votes with more instructions.

I've never done a gradle build, and have no idea how to do one. I'm
sure I could find out, but that is going to take time.



...

If you don't go that route you can get Gradle here:
http://gradle.org/gradle-download/

Once you have it installed you can build the project with 'gradle 
jar'



$ gradle jar

FAILURE: Build failed with an exception.

* Where:
Build file
'C:\OpenOfficeDev\GroovyUNO\guno-extension-0.1.4\build.gradle' 
line: 83


* What went wrong:
A problem occurred evaluating root project 'guno-extension-0.1.4'.
> No such property: mavenUser for class:
org.gradle.api.publication.maven.internal.deployer.DefaultGroovyMavenDeployer 






Hi Patricia,

Looks like Gradle is evaluating variables that are read from my
~/.gradle/gradle.properties file.
These are variables that a user needs to keep out of SVN.

There is also a gradle.properties file under the project root, please
add this and retry the build.
Here is what I have in my gradle.properties:

signing.keyId=12345678
signing.password=my key password
signing.secretKeyRingFile=/path/to/keyring.gpg
mavenUser=mavenUser
mavenPassword=mavenPassword

You don't need to edit the values.

If this solves it for you I can patch the RC and try again.


Are you sure I should need to use a maven account to do this test?


No you don't need a maven account to run the jar task.  Only add the
properties and values to the currently empty gradle.properties file
under the project directory.
Edit this file:
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4/gradle.properties 


by adding this text as-is:

signing.keyId=12345678
signing.password=my key password
signing.secretKeyRingFile=/path/to/keyring.gpg
mavenUser=mavenUser
mavenPassword=mavenPassword


  The gradle.build script will look for undefined variables in this
gradle.properties file first and then in ~/.groovy/gradle.properties
which is where my real ones were so the didn't end up in SVN.

These will not actually be used for anything unless the uploadArchives
task is ran which will create jars, sign them, and upload to Maven
repository.


Thanks. It built, though with one error code message:

Patricia@Jan2014Desktop 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4

$ gradle jar
:clean UP-TO-DATE
:compileJava UP-TO-DATE
:compileGroovy
:processResources
:classes
:groovydoc
Could not open/create prefs root node Software\JavaSoft\Prefs at root 
0x8002. Windows RegCreateKeyEx(...) returned error code 5.

:jar

BUILD SUCCESSFUL

Total time: 48.871 secs



Hi Patricia,

That's great.

What java version of JDK are you running?  It may be related to [1] or [2].

Did you have a chance to try the HelloTextTableShape.groovy test script 
that I placed in Bugzilla [3]?


I'll create a new RC to add that content to build.properties this evening.

[1] 
http://stackoverflow.com/questions/16428098/groovy-shell-warning-could-not-open-create-prefs-root-node

[2] http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6790382
[3] https://bz.apache.org/ooo/show_bug.cgi?id=126770

Thanks again !!
Carl

-
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-14 Thread Patricia Shanahan 

On 4/14/2016 6:29 PM, Carl Marcum wrote:

On 04/14/2016 08:10 PM, Patricia Shanahan wrote:

On 4/14/2016 3:28 AM, Carl Marcum wrote:

On 04/14/2016 12:57 AM, Patricia Shanahan wrote:



On 4/6/2016 3:27 AM, Carl Marcum wrote:

On 04/05/2016 09:57 PM, Patricia Shanahan wrote:

I think you will get more votes with more instructions.

I've never done a gradle build, and have no idea how to do one. I'm
sure I could find out, but that is going to take time.



...

If you don't go that route you can get Gradle here:
http://gradle.org/gradle-download/

Once you have it installed you can build the project with 'gradle jar'



$ gradle jar

FAILURE: Build failed with an exception.

* Where:
Build file
'C:\OpenOfficeDev\GroovyUNO\guno-extension-0.1.4\build.gradle' line: 83

* What went wrong:
A problem occurred evaluating root project 'guno-extension-0.1.4'.
> No such property: mavenUser for class:
org.gradle.api.publication.maven.internal.deployer.DefaultGroovyMavenDeployer




Hi Patricia,

Looks like Gradle is evaluating variables that are read from my
~/.gradle/gradle.properties file.
These are variables that a user needs to keep out of SVN.

There is also a gradle.properties file under the project root, please
add this and retry the build.
Here is what I have in my gradle.properties:

signing.keyId=12345678
signing.password=my key password
signing.secretKeyRingFile=/path/to/keyring.gpg
mavenUser=mavenUser
mavenPassword=mavenPassword

You don't need to edit the values.

If this solves it for you I can patch the RC and try again.


Are you sure I should need to use a maven account to do this test?


No you don't need a maven account to run the jar task.  Only add the
properties and values to the currently empty gradle.properties file
under the project directory.
Edit this file:
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4/gradle.properties
by adding this text as-is:

signing.keyId=12345678
signing.password=my key password
signing.secretKeyRingFile=/path/to/keyring.gpg
mavenUser=mavenUser
mavenPassword=mavenPassword


  The gradle.build script will look for undefined variables in this
gradle.properties file first and then in ~/.groovy/gradle.properties
which is where my real ones were so the didn't end up in SVN.

These will not actually be used for anything unless the uploadArchives
task is ran which will create jars, sign them, and upload to Maven
repository.


Thanks. It built, though with one error code message:

Patricia@Jan2014Desktop 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4

$ gradle jar
:clean UP-TO-DATE
:compileJava UP-TO-DATE
:compileGroovy
:processResources
:classes
:groovydoc
Could not open/create prefs root node Software\JavaSoft\Prefs at root 
0x8002. Windows RegCreateKeyEx(...) returned error code 5.

:jar

BUILD SUCCESSFUL

Total time: 48.871 secs



-
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-14 Thread Carl Marcum 

On 04/14/2016 08:10 PM, Patricia Shanahan wrote:

On 4/14/2016 3:28 AM, Carl Marcum wrote:

On 04/14/2016 12:57 AM, Patricia Shanahan wrote:



On 4/6/2016 3:27 AM, Carl Marcum wrote:

On 04/05/2016 09:57 PM, Patricia Shanahan wrote:

I think you will get more votes with more instructions.

I've never done a gradle build, and have no idea how to do one. I'm
sure I could find out, but that is going to take time.



...

If you don't go that route you can get Gradle here:
http://gradle.org/gradle-download/

Once you have it installed you can build the project with 'gradle jar'



$ gradle jar

FAILURE: Build failed with an exception.

* Where:
Build file
'C:\OpenOfficeDev\GroovyUNO\guno-extension-0.1.4\build.gradle' line: 83

* What went wrong:
A problem occurred evaluating root project 'guno-extension-0.1.4'.
> No such property: mavenUser for class:
org.gradle.api.publication.maven.internal.deployer.DefaultGroovyMavenDeployer 





Hi Patricia,

Looks like Gradle is evaluating variables that are read from my
~/.gradle/gradle.properties file.
These are variables that a user needs to keep out of SVN.

There is also a gradle.properties file under the project root, please
add this and retry the build.
Here is what I have in my gradle.properties:

signing.keyId=12345678
signing.password=my key password
signing.secretKeyRingFile=/path/to/keyring.gpg
mavenUser=mavenUser
mavenPassword=mavenPassword

You don't need to edit the values.

If this solves it for you I can patch the RC and try again.


Are you sure I should need to use a maven account to do this test?


No you don't need a maven account to run the jar task.  Only add the 
properties and values to the currently empty gradle.properties file 
under the project directory.
Edit this file: 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4/gradle.properties

by adding this text as-is:

signing.keyId=12345678
signing.password=my key password
signing.secretKeyRingFile=/path/to/keyring.gpg
mavenUser=mavenUser
mavenPassword=mavenPassword


 The gradle.build script will look for undefined variables in this 
gradle.properties file first and then in ~/.groovy/gradle.properties 
which is where my real ones were so the didn't end up in SVN.


These will not actually be used for anything unless the uploadArchives 
task is ran which will create jars, sign them, and upload to Maven 
repository.


Thanks,
Carl



I unzipped the RC, and then ran "gradle jar" in its root directory. Is 
that what I should be doing. I do not seem to currently have any 
gradle properties:


Patricia@Jan2014Desktop 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4

$ ls ~/.gradle
ls: cannot access /home/Patricia/.gradle: No such file or directory

Patricia@Jan2014Desktop 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4

$ ls
build.gradle  gradle.properties  LICENSE  NOTICE  README.md  src

Patricia@Jan2014Desktop 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4

$ more gradle.properties

Patricia@Jan2014Desktop 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4

$





-
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-14 Thread Patricia Shanahan 

On 4/14/2016 3:28 AM, Carl Marcum wrote:

On 04/14/2016 12:57 AM, Patricia Shanahan wrote:



On 4/6/2016 3:27 AM, Carl Marcum wrote:

On 04/05/2016 09:57 PM, Patricia Shanahan wrote:

I think you will get more votes with more instructions.

I've never done a gradle build, and have no idea how to do one. I'm
sure I could find out, but that is going to take time.



...

If you don't go that route you can get Gradle here:
http://gradle.org/gradle-download/

Once you have it installed you can build the project with 'gradle jar'



$ gradle jar

FAILURE: Build failed with an exception.

* Where:
Build file
'C:\OpenOfficeDev\GroovyUNO\guno-extension-0.1.4\build.gradle' line: 83

* What went wrong:
A problem occurred evaluating root project 'guno-extension-0.1.4'.
> No such property: mavenUser for class:
org.gradle.api.publication.maven.internal.deployer.DefaultGroovyMavenDeployer



Hi Patricia,

Looks like Gradle is evaluating variables that are read from my
~/.gradle/gradle.properties file.
These are variables that a user needs to keep out of SVN.

There is also a gradle.properties file under the project root, please
add this and retry the build.
Here is what I have in my gradle.properties:

signing.keyId=12345678
signing.password=my key password
signing.secretKeyRingFile=/path/to/keyring.gpg
mavenUser=mavenUser
mavenPassword=mavenPassword

You don't need to edit the values.

If this solves it for you I can patch the RC and try again.


Are you sure I should need to use a maven account to do this test?

I unzipped the RC, and then ran "gradle jar" in its root directory. Is 
that what I should be doing. I do not seem to currently have any gradle 
properties:


Patricia@Jan2014Desktop 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4

$ ls ~/.gradle
ls: cannot access /home/Patricia/.gradle: No such file or directory

Patricia@Jan2014Desktop 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4

$ ls
build.gradle  gradle.properties  LICENSE  NOTICE  README.md  src

Patricia@Jan2014Desktop 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4

$ more gradle.properties

Patricia@Jan2014Desktop 
/cygdrive/c/OpenOfficeDev/GroovyUNO/guno-extension-0.1.4

$


-
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-14 Thread Carl Marcum 

On 04/14/2016 12:57 AM, Patricia Shanahan wrote:



On 4/6/2016 3:27 AM, Carl Marcum wrote:

On 04/05/2016 09:57 PM, Patricia Shanahan wrote:

I think you will get more votes with more instructions.

I've never done a gradle build, and have no idea how to do one. I'm
sure I could find out, but that is going to take time.



...

If you don't go that route you can get Gradle here:
http://gradle.org/gradle-download/

Once you have it installed you can build the project with 'gradle jar'



$ gradle jar

FAILURE: Build failed with an exception.

* Where:
Build file 
'C:\OpenOfficeDev\GroovyUNO\guno-extension-0.1.4\build.gradle' line: 83


* What went wrong:
A problem occurred evaluating root project 'guno-extension-0.1.4'.
> No such property: mavenUser for class: 
org.gradle.api.publication.maven.internal.deployer.DefaultGroovyMavenDeployer


Hi Patricia,

Looks like Gradle is evaluating variables that are read from my 
~/.gradle/gradle.properties file.

These are variables that a user needs to keep out of SVN.

There is also a gradle.properties file under the project root, please 
add this and retry the build.

Here is what I have in my gradle.properties:

signing.keyId=12345678
signing.password=my key password
signing.secretKeyRingFile=/path/to/keyring.gpg
mavenUser=mavenUser
mavenPassword=mavenPassword

You don't need to edit the values.

If this solves it for you I can patch the RC and try again.

Thanks for helping out with this.

Carl

-
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-13 Thread Patricia Shanahan 



On 4/6/2016 3:27 AM, Carl Marcum wrote:

On 04/05/2016 09:57 PM, Patricia Shanahan wrote:

I think you will get more votes with more instructions.

I've never done a gradle build, and have no idea how to do one. I'm
sure I could find out, but that is going to take time.



...

If you don't go that route you can get Gradle here:
http://gradle.org/gradle-download/

Once you have it installed you can build the project with 'gradle jar'



$ gradle jar

FAILURE: Build failed with an exception.

* Where:
Build file 
'C:\OpenOfficeDev\GroovyUNO\guno-extension-0.1.4\build.gradle' line: 83


* What went wrong:
A problem occurred evaluating root project 'guno-extension-0.1.4'.
> No such property: mavenUser for class: 
org.gradle.api.publication.maven.internal.deployer.DefaultGroovyMavenDeployer


* Try:
Run with --stacktrace option to get the stack trace. Run with --info or 
--debug option to get more log output.


BUILD FAILED

Total time: 43.982 secs

-
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-13 Thread Carl Marcum 

On 04/13/2016 05:55 PM, Patricia Shanahan wrote:
For me, the delay has been the combination of some non-Apache projects 
and Apache River needing some attention (I'm the PMC Chair).


I put away my Linux system to make more room for sewing for a couple 
of weeks.


Unfortunately, I will need to use unfamiliar tools to do the Windows 
build. I'll try to have a go at it during the next few days, and try 
to write up a step-by-step guide to help others.



Thanks Patricia,

Please let me know if you have any questions.

Carl

-
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-13 Thread Patricia Shanahan 
For me, the delay has been the combination of some non-Apache projects 
and Apache River needing some attention (I'm the PMC Chair).


I put away my Linux system to make more room for sewing for a couple of 
weeks.


Unfortunately, I will need to use unfamiliar tools to do the Windows 
build. I'll try to have a go at it during the next few days, and try to 
write up a step-by-step guide to help others.


On 4/13/2016 1:44 PM, Carl Marcum wrote:

Does anyone else plan to vote on this or 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-06 Thread Carl Marcum 

On 04/05/2016 09:57 PM, Patricia Shanahan wrote:

I think you will get more votes with more instructions.

I've never done a gradle build, and have no idea how to do one. I'm 
sure I could find out, but that is going to take time.





Hi Patricia,

On Linux I usually use SDKMAN to manage my Gradle, Groovy, etc.
It's an environment manager for that includes Gradle support.
You can download it here:
http://sdkman.io/
or use curl:
|curl -s http://get.sdkman.io | bash

There is also a Windows powershell version but I haven't used it.

Usage page is here:
http://sdkman.io/usage.html

If you don't go that route you can get Gradle here:
http://gradle.org/gradle-download/

Once you have it installed you can build the project with 'gradle jar'

Also 'gradle clean' removes the build artifacts.

The jar task will run clean during a build anyway.

More info about the Groovy UNO is on our wiki:
https://wiki.openoffice.org/wiki/Groovy_UNO_Extension

Please let me know if you have any questions.

I'll be back online this evening EST.

Thanks,
Carl


|

-
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-05 Thread Dennis E. Hamilton 


> -Original Message-
> From: Carl Marcum [mailto:cmar...@apache.org]
> Sent: Tuesday, April 5, 2016 15:08
> To: dev@openoffice.apache.org
> Subject: Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4
> 
> On 04/05/2016 01:36 PM, Dennis E. Hamilton wrote:
> > Side question.
> >
> >> -Original Message-
> >> From: Carl Marcum [mailto:cmar...@apache.org]
> >> Sent: Tuesday, April 5, 2016 04:07
> >> To: dev@openoffice.apache.org
> >> Subject: [VOTE] Release Groovy UNO Extension 0.1.4
[ ... ]
> >> I'm signing with a new 4096 bit key I recently added to KEYS.
> >>
> > [orcmid]
> >
> > I forgot to ask this when you mentioned the new key before.
> >
> > Carl, is the fingerprint of this new key added to your account
> information at id.apache.org?
> >
> > I see only one entry for cmarcum at
> <https://people.apache.org/keys/committer/> and that
> >
> >  ASF ID: cmarcum
> >  LDAP PGP key: 8204 E089 64AC 9ABA 7472 A123 669C FA03 CED4 6810
> >
> >  pub  2048R/CED46810 2011-07-04 Carl Marcum <cmar...@apache.org>
> >Key fingerprint = 8204 E089 64AC 9ABA 7472  A123 669C FA03
> CED4 6810
> >  uidCarl Marcum
> <carl.mar...@codebuilders.net>
> >  sub  2048R/3175CD6A 2011-07-04
> >
> > is for your older 2048-bit key.  (Note that you can have any number of
> key signatures in your account record and you should probably not remove
> any that have been used in signing releases or for any other situation
> where confirmation is needed that the key is one of yous as an ASF
> committer.)
> >
> > The committer keys file is automatically updated from PGP key
> signatures and will reflect countersignatures on your key (circle of
> trust attestations).  If the key is ever revoked for any reason, that
> will be discoverable there too unless the fingerprint or apache account
> are removed.  (Of course, you must publish your new 4069-bit public key
> to a PGP key server for this to work.)
> >
> > As far as I know, public keys in release-archive KEYS files are not
> automatically synchronized in that manner, although the one associated
> with projects is, such as the one at
> > <https://people.apache.org/keys/group/openoffice.asc>.  This should
> *not* be used as a release KEYS though.  See
> <https://people.apache.org/keys/> for details.
> >
> > What is needed in KEYS files for authenticating a release and stored
> in the mirror directories is always cumulative, so any signature you
> have used to sign a release (candidate) needs to be in the release-
> associated KEYS file.  It is nice to use the
> > <https://people.apache.org/keys/committer/>-accessed version of the
> key in our KEYS file because that one has the Useful descriptive
> information as shown for your 2048-bit key, above.
> >
> > Note that keys that have not been used in signing release candidates
> do not need to be in release-associated KEYS files and it is good
> practice (and an useful precaution) to keep it that way.
> >
> > PS: None of this is a release blocker.  But you can get the dots
> connected before the [VOTE] concludes.  I assume there is no further
> reason to touch the KEYS file that you have already updated.
> >
> >   - Dennis
> >
> 
> Hi Dennis,
> 
> Thank you for the reminder.
> 
> My new key was uploaded to public servers. ex.
> https://pgp.mit.edu/pks/lookup?op=vindex=0xF1DA7E3B9553BF9A
> 
> Before the vote I manually added it to
> http://www.apache.org/dist/openoffice/KEYS
> 
> I have just now added the new fingerprint to my profile at
> https://id.apache.org/
> for reference it is:
> pub   4096R/9553BF9A 2016-04-02
>Key fingerprint = 813A C3C2 48B3 F26F B5D1  EB32 F1DA 7E3B 9553
> BF9A
> uid  Carl Marcum (CODE SIGNING KEY) <cmar...@apache.org>
> uid  Carl Marcum (CODE SIGNING KEY)
> <carl.mar...@codebuilders.net>
> sub   4096R/D8524D84 2016-04-02
> 
> Is there now something that needs fixed?
[orcmid] 

I think you've covered all the bases, Carl.

> 
> 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-05 Thread Carl Marcum 

On 04/05/2016 01:36 PM, Dennis E. Hamilton wrote:

Side question.


-Original Message-
From: Carl Marcum [mailto:cmar...@apache.org]
Sent: Tuesday, April 5, 2016 04:07
To: dev@openoffice.apache.org
Subject: [VOTE] Release Groovy UNO Extension 0.1.4

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 RC1 are available at:
https://dist.apache.org/repos/dist/dev/openoffice/devtools/
and the reference revision is r1737622.

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

I'm signing with a new 4096 bit key I recently added to KEYS.


[orcmid]

I forgot to ask this when you mentioned the new key before.

Carl, is the fingerprint of this new key added to your account information at 
id.apache.org?

I see only one entry for cmarcum at  
and that

 ASF ID: cmarcum
 LDAP PGP key: 8204 E089 64AC 9ABA 7472 A123 669C FA03 CED4 6810

 pub  2048R/CED46810 2011-07-04 Carl Marcum 
   Key fingerprint = 8204 E089 64AC 9ABA 7472  A123 669C FA03 CED4 6810
 uidCarl Marcum 
 sub  2048R/3175CD6A 2011-07-04

is for your older 2048-bit key.  (Note that you can have any number of key 
signatures in your account record and you should probably not remove any that 
have been used in signing releases or for any other situation where 
confirmation is needed that the key is one of yous as an ASF committer.)

The committer keys file is automatically updated from PGP key signatures and 
will reflect countersignatures on your key (circle of trust attestations).  If 
the key is ever revoked for any reason, that will be discoverable there too 
unless the fingerprint or apache account are removed.  (Of course, you must 
publish your new 4069-bit public key to a PGP key server for this to work.)

As far as I know, public keys in release-archive KEYS files are not 
automatically synchronized in that manner, although the one associated with 
projects is, such as the one at
.  This should *not* be used as 
a release KEYS though.  See  for details.

What is needed in KEYS files for authenticating a release and stored in the 
mirror directories is always cumulative, so any signature you have used to sign 
a release (candidate) needs to be in the release-associated KEYS file.  It is 
nice to use the
-accessed version of the key in our 
KEYS file because that one has the Useful descriptive information as shown for your 
2048-bit key, above.

Note that keys that have not been used in signing release candidates do not 
need to be in release-associated KEYS files and it is good practice (and an 
useful precaution) to keep it that way.

PS: None of this is a release blocker.  But you can get the dots connected 
before the [VOTE] concludes.  I assume there is no further reason to touch the 
KEYS file that you have already updated.

  - Dennis



Hi Dennis,

Thank you for the reminder.

My new key was uploaded to public servers. ex. 
https://pgp.mit.edu/pks/lookup?op=vindex=0xF1DA7E3B9553BF9A


Before the vote I manually added it to 
http://www.apache.org/dist/openoffice/KEYS


I have just now added the new fingerprint to my profile at 
https://id.apache.org/

for reference it is:
pub   4096R/9553BF9A 2016-04-02
  Key fingerprint = 813A C3C2 48B3 F26F B5D1  EB32 F1DA 7E3B 9553 BF9A
uid  Carl Marcum (CODE SIGNING KEY) 
uid  Carl Marcum (CODE SIGNING KEY) 


sub   4096R/D8524D84 2016-04-02

Is there now something that needs fixed?

Thanks,
Carl


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