Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4
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, I'm going to need to research this testing requirement. The issue is this artifact has to be pulled from the staging repository or installed into a local Maven repository on your machine. The Apache Maven project uses the staging repo in a similar fashion from what I can tell so far. [1] Since this is a library and not an executable I think it's okay but I'm not 100% so it may take a few days to get some answers. Thanks for helping. [1] http://maven.apache.org/guides/development/guide-testing-releases.html - 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: [CWiki] Account Whitelisting
Buddy Matula wrote: > Hello, > > My username is buddymatula and my real name is Theodore Matula. I would > like to request for my account to be white listed so that I may add my > information to the directory of volunteers > Buddy; Your cwiki account has been white-listed. Welcome to Apache OpenOffice. Regards Keith N. McKenna signature.asc Description: OpenPGP digital signature
Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4
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
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 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
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
[CWiki] Account Whitelisting
Hello, My username is buddymatula and my real name is Theodore Matula. I would like to request for my account to be white listed so that I may add my information to the directory of volunteers
Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4
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
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
