Apache Gora
  1. Apache Gora
  2. GORA-43

Forward port 0.1.1 incubating Maven poms to trunk

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.2
    • Component/s: build process
    • Labels:
      None

      Description

      I improved the Maven poms in 0.1.1-incubating, and trimmed them down to a publishable set of dependencies.

      My improvements:

      1. reduce the redundancy in the deps section by not repeating deps in each sub-project.
      2. use explicit dependency and module version #s which are required to not have "moving target" dependencies in the downstream applications and that allow each individual gora-* module to be included on its own (without having to include gora-core).

      I'd like to forward port these to trunk and then update per trunk's dependencies.

      1. GORA-43.patch
        2 kB
        Lewis John McGibbney
      2. GORA-43-v2.patch
        4 kB
        Lewis John McGibbney
      3. GORA-43-v3.patch
        4 kB
        Lewis John McGibbney

        Issue Links

          Activity

          Hide
          Chris A. Mattmann added a comment -
          • push to 0.3
          Show
          Chris A. Mattmann added a comment - push to 0.3
          Hide
          Chris A. Mattmann added a comment -
          • schedule
          Show
          Chris A. Mattmann added a comment - schedule
          Hide
          Lewis John McGibbney added a comment -

          Hey Chris can you provide any pointers of where I begin looking into this? Any good maven documentation that you're aware of? It's about time I got my head around the Maven stuff anyway and this amongst other issues, would be a good place to start. Thanks

          Show
          Lewis John McGibbney added a comment - Hey Chris can you provide any pointers of where I begin looking into this? Any good maven documentation that you're aware of? It's about time I got my head around the Maven stuff anyway and this amongst other issues, would be a good place to start. Thanks
          Hide
          Chris A. Mattmann added a comment -

          Hey Lewis, I was just thinking of grabbing the Maven poms I made for the 0.1.1-incubating release, which I know work with Maven Central and which I know work with the deps we have (except for Cassandra, and Thrift in that version, which you needed to mvn install by hand ahead of time). In 0.2-incubating onward, those deps are on newer versions of those libraries and are thus available in Maven Central.

          You can find the poms here: http://svn.apache.org/repos/asf/incubator/gora/tags/0.1.1-incubating/

          Show
          Chris A. Mattmann added a comment - Hey Lewis, I was just thinking of grabbing the Maven poms I made for the 0.1.1-incubating release, which I know work with Maven Central and which I know work with the deps we have (except for Cassandra, and Thrift in that version, which you needed to mvn install by hand ahead of time). In 0.2-incubating onward, those deps are on newer versions of those libraries and are thus available in Maven Central. You can find the poms here: http://svn.apache.org/repos/asf/incubator/gora/tags/0.1.1-incubating/
          Hide
          Lewis John McGibbney added a comment - - edited

          A couple of things here.
          1) Withe regards to gora-sql tests we have no reference to an internal dependency for this nested under the <dependencyManagement> parent. Is it possible to add something like

                    <dependency>
                      <groupId>org.apache.gora</groupId>
                      <artifactId>gora-sql</artifactId>
                      <version>${project.version}</version>
                      <classifier>tests</classifier>
                    </dependency>
          

          2) This is (part of) where we need to edit the location for the upgrade to for the cassandra.version, cassandra.thrift.version & hector.version. This obviously needs to be addressed in a separate issue but it is worth noting here as this issue therefore should block GORA-58 as well as GORA-22 (which we really need to get sorted out).

          3) Does the stuff in

          <build>
                  <testSourceDirectory>${basedir}/src/test/java</testSourceDirectory>
                  <sourceDirectory>${basedir}/src/main/java</sourceDirectory>
                  <plugins>
                      <plugin>
                          <groupId>org.apache.maven.plugins</groupId>
          ...
          </build>
          

          need to be updated as well or is this fine as-is?

          4) As far as I can see it is mainly stuff in

           <properties>
                  <osgi.version>4.2.0</osgi.version>
                  <!-- Hadoop Dependencies -->
                  <hadoop.version>0.20.2</hadoop.version>
          ...
          

          that needs to be updated? Can anyone clarify/confirm?

          I understand you are up to your teeth just now Chris, but if you could provide insight into what needs to be addressed above, then I will get right on this. Thanks

          Show
          Lewis John McGibbney added a comment - - edited A couple of things here. 1) Withe regards to gora-sql tests we have no reference to an internal dependency for this nested under the <dependencyManagement> parent. Is it possible to add something like <dependency> <groupId>org.apache.gora</groupId> <artifactId>gora-sql</artifactId> <version>${project.version}</version> <classifier>tests</classifier> </dependency> 2) This is (part of) where we need to edit the location for the upgrade to for the cassandra.version, cassandra.thrift.version & hector.version. This obviously needs to be addressed in a separate issue but it is worth noting here as this issue therefore should block GORA-58 as well as GORA-22 (which we really need to get sorted out). 3) Does the stuff in <build> <testSourceDirectory>${basedir}/src/test/java</testSourceDirectory> <sourceDirectory>${basedir}/src/main/java</sourceDirectory> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> ... </build> need to be updated as well or is this fine as-is? 4) As far as I can see it is mainly stuff in <properties> <osgi.version>4.2.0</osgi.version> <!-- Hadoop Dependencies --> <hadoop.version>0.20.2</hadoop.version> ... that needs to be updated? Can anyone clarify/confirm? I understand you are up to your teeth just now Chris, but if you could provide insight into what needs to be addressed above, then I will get right on this. Thanks
          Hide
          Lewis John McGibbney added a comment - - edited

          OK so I undertook the exercise of seeing what can/could possibly be upgraded by doing searches on Maven Central. The following outcomes can be interpreted as

          artifact id: current version: latest version

          avro:1.3.2:1.3.3
          hbase:0.90.0:0.90.4
          cassandra-all:0.8.1:1.0.2
          cassandra-thrift:ditto (by the way do we require this if we are shifting to Hector client???)
          hector-core:0.8.0-1:1.0-1
          guava:r09:10.0.1
          commons-lang:2.5:2.6
          jdom:1.1:1.1.2
          sqlbuilder:2.0.6:2.0.10
          hsqldb:2.0.0:2.2.4
          mysql-connector-java:5.1.13:5.1.18
          slf4j-api:1.58:1.6.4
          slf4j-simple:ditto
          slf4j-jdk14:ditto
          log4j:1.2.15:1.2.16
          junit:4.6:4.10

          commons-logging:1.1.1: at newest, however I don't see this actually being used anywhere can someone clarify why this is present.
          libthrift:0.5.0:0.7.0 however same comment as above

          As we all know hadoop can stay at 0.20.2 for the foreseeable future. The concern I have is with compatibility! This is an area I do not have much experience and I'm trying to get used to it. Once this is done the ant/ivy can follow suit fine, I don't have a problem with that.

          Further to this, as explained above, I have not looked for any plugins for the pom.xml or anything similar

          Thanks

          Show
          Lewis John McGibbney added a comment - - edited OK so I undertook the exercise of seeing what can/could possibly be upgraded by doing searches on Maven Central. The following outcomes can be interpreted as artifact id: current version: latest version avro:1.3.2:1.3.3 hbase:0.90.0:0.90.4 cassandra-all:0.8.1:1.0.2 cassandra-thrift:ditto (by the way do we require this if we are shifting to Hector client???) hector-core:0.8.0-1:1.0-1 guava:r09:10.0.1 commons-lang:2.5:2.6 jdom:1.1:1.1.2 sqlbuilder:2.0.6:2.0.10 hsqldb:2.0.0:2.2.4 mysql-connector-java:5.1.13:5.1.18 slf4j-api:1.58:1.6.4 slf4j-simple:ditto slf4j-jdk14:ditto log4j:1.2.15:1.2.16 junit:4.6:4.10 commons-logging:1.1.1: at newest, however I don't see this actually being used anywhere can someone clarify why this is present. libthrift:0.5.0:0.7.0 however same comment as above As we all know hadoop can stay at 0.20.2 for the foreseeable future. The concern I have is with compatibility! This is an area I do not have much experience and I'm trying to get used to it. Once this is done the ant/ivy can follow suit fine, I don't have a problem with that. Further to this, as explained above, I have not looked for any plugins for the pom.xml or anything similar Thanks
          Hide
          Lewis John McGibbney added a comment -

          Well after updating my pom.xml with all new dependencies, not unsurprisingly ( ) the full build broke, The build is complaining as follows

          [INFO] ------------------------------------------------------------------------
          [ERROR] BUILD ERROR
          [INFO] ------------------------------------------------------------------------
          [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing:
          ----------
          1) maven-plugins:maven-cobertura-plugin:plugin:1.3
          
            Try downloading the file manually from the project website.
          
            Then, install it using the command: 
                mvn install:install-file -DgroupId=maven-plugins -DartifactId=maven-cobertura-plugin -Dversion=1.3 -Dpackaging=plugin -Dfile=/path/to/file
          
            Alternatively, if you host your own repository you can deploy the file there: 
                mvn deploy:deploy-file -DgroupId=maven-plugins -DartifactId=maven-cobertura-plugin -Dversion=1.3 -Dpackaging=plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
          
            Path to dependency: 
            	1) org.apache.gora:gora-hbase:jar:0.2-SNAPSHOT
            	2) org.jdom:jdom:jar:1.1.2
            	3) jaxen:jaxen:jar:1.1.3
            	4) maven-plugins:maven-cobertura-plugin:plugin:1.3
          
          2) maven-plugins:maven-findbugs-plugin:plugin:1.3.1
          
            Try downloading the file manually from the project website.
          
            Then, install it using the command: 
                mvn install:install-file -DgroupId=maven-plugins -DartifactId=maven-findbugs-plugin -Dversion=1.3.1 -Dpackaging=plugin -Dfile=/path/to/file
          
            Alternatively, if you host your own repository you can deploy the file there: 
                mvn deploy:deploy-file -DgroupId=maven-plugins -DartifactId=maven-findbugs-plugin -Dversion=1.3.1 -Dpackaging=plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
          
            Path to dependency: 
            	1) org.apache.gora:gora-hbase:jar:0.2-SNAPSHOT
            	2) org.jdom:jdom:jar:1.1.2
            	3) jaxen:jaxen:jar:1.1.3
            	4) maven-plugins:maven-findbugs-plugin:plugin:1.3.1
          
          ----------
          2 required artifacts are missing.
          
          for artifact: 
            org.apache.gora:gora-hbase:jar:0.2-SNAPSHOT
          
          from the specified remote repositories:
            apache.snapshots (http://repository.apache.org/snapshots),
            central (http://repo1.maven.org/maven2)
          
          
          
          [INFO] ------------------------------------------------------------------------
          [INFO] For more information, run Maven with the -e switch
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 8 minutes 30 seconds
          [INFO] Finished at: Thu Nov 17 19:02:04 GMT 2011
          [INFO] Final Memory: 51M/151M
          
          

          Now although neither maven-plugins:maven-findbugs-plugin:plugin:1.3.1 nor maven-plugins:maven-cobertura-plugin:plugin:1.3 are available on either of the above two repositories, they are available on http://search.maven.org/. If I add them manually they break the build even more!
          I've attached the patch which includes all up-to-date dependency properties for record.

          Show
          Lewis John McGibbney added a comment - Well after updating my pom.xml with all new dependencies, not unsurprisingly ( ) the full build broke, The build is complaining as follows [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: ---------- 1) maven-plugins:maven-cobertura-plugin:plugin:1.3 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=maven-plugins -DartifactId=maven-cobertura-plugin -Dversion=1.3 -Dpackaging=plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=maven-plugins -DartifactId=maven-cobertura-plugin -Dversion=1.3 -Dpackaging=plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.gora:gora-hbase:jar:0.2-SNAPSHOT 2) org.jdom:jdom:jar:1.1.2 3) jaxen:jaxen:jar:1.1.3 4) maven-plugins:maven-cobertura-plugin:plugin:1.3 2) maven-plugins:maven-findbugs-plugin:plugin:1.3.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=maven-plugins -DartifactId=maven-findbugs-plugin -Dversion=1.3.1 -Dpackaging=plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=maven-plugins -DartifactId=maven-findbugs-plugin -Dversion=1.3.1 -Dpackaging=plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.gora:gora-hbase:jar:0.2-SNAPSHOT 2) org.jdom:jdom:jar:1.1.2 3) jaxen:jaxen:jar:1.1.3 4) maven-plugins:maven-findbugs-plugin:plugin:1.3.1 ---------- 2 required artifacts are missing. for artifact: org.apache.gora:gora-hbase:jar:0.2-SNAPSHOT from the specified remote repositories: apache.snapshots (http: //repository.apache.org/snapshots), central (http: //repo1.maven.org/maven2) [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 8 minutes 30 seconds [INFO] Finished at: Thu Nov 17 19:02:04 GMT 2011 [INFO] Final Memory: 51M/151M Now although neither maven-plugins:maven-findbugs-plugin:plugin:1.3.1 nor maven-plugins:maven-cobertura-plugin:plugin:1.3 are available on either of the above two repositories, they are available on http://search.maven.org/ . If I add them manually they break the build even more! I've attached the patch which includes all up-to-date dependency properties for record.
          Hide
          Lewis John McGibbney added a comment -

          After manually downloading and installing both of the above plugins then running mvn clean, then mvn test, then mvn clean install I'm getting Gora to build successfully. There are a number of tests in which there are errors but no failures. Is there any way we can get the above two plugins uploaded to the maven central repos? This way we could add the configuration to the pom.xml which would mean that it is a case of fixing failing tests before moving on to other development?

          Show
          Lewis John McGibbney added a comment - After manually downloading and installing both of the above plugins then running mvn clean, then mvn test, then mvn clean install I'm getting Gora to build successfully. There are a number of tests in which there are errors but no failures. Is there any way we can get the above two plugins uploaded to the maven central repos? This way we could add the configuration to the pom.xml which would mean that it is a case of fixing failing tests before moving on to other development?
          Hide
          Chris A. Mattmann added a comment -

          Lewis, great work. You nailed down the major differences. It's interesting that we're failing on 2 maven plugins that aren't available in Central that seem to
          be referenced from JDOM and JAXEN. One thing that we might do is an exclusion of org.jdom in the gora-hbase dependencies which seems to drive
          both plugin incompatibilities. WDYT?

          If exclusion fixes it, then my +1 to simply commit your forward port to trunk and then call this sucker done. Thoughts?

          Show
          Chris A. Mattmann added a comment - Lewis, great work. You nailed down the major differences. It's interesting that we're failing on 2 maven plugins that aren't available in Central that seem to be referenced from JDOM and JAXEN. One thing that we might do is an exclusion of org.jdom in the gora-hbase dependencies which seems to drive both plugin incompatibilities. WDYT? If exclusion fixes it, then my +1 to simply commit your forward port to trunk and then call this sucker done. Thoughts?
          Hide
          Lewis John McGibbney added a comment -

          Please see attached for the updated patch. I'm not sure if Hector client will work with the Cassandra artefact's but this will hopefully become obvious in the not so near future. Even if this is the case we can simply downgrade the Cassandra dependencies. Can we please ensure that this patch is working OK as I manually installed the two maven plugins so I am unsure if all will be working after the exculusions have been added to gora-hbase modules.

          Thanks

          Show
          Lewis John McGibbney added a comment - Please see attached for the updated patch. I'm not sure if Hector client will work with the Cassandra artefact's but this will hopefully become obvious in the not so near future. Even if this is the case we can simply downgrade the Cassandra dependencies. Can we please ensure that this patch is working OK as I manually installed the two maven plugins so I am unsure if all will be working after the exculusions have been added to gora-hbase modules. Thanks
          Hide
          Lewis John McGibbney added a comment -

          Patch deleted as it was for another issue GORA-42... I had no idea I had attached it here.

          Show
          Lewis John McGibbney added a comment - Patch deleted as it was for another issue GORA-42 ... I had no idea I had attached it here.
          Hide
          Lewis John McGibbney added a comment -

          I can confirm that the new patch still complains about the following missing dependencies

            Path to dependency: 
            	1) org.apache.gora:gora-hbase:jar:0.2-SNAPSHOT
            	2) org.jdom:jdom:jar:1.1.2
            	3) jaxen:jaxen:jar:1.1.3
            	4) maven-plugins:maven-findbugs-plugin:plugin:1.3.1
          

          I am kinda stumped on this one as the link here [1] gets you to manually redirect here [2].

          Anyway, for clarity details of both the missing plugins can be found here [3] & [4]

          [1] http://repo1.maven.org/maven2/
          [2] http://search.maven.org/
          [3] http://search.maven.org/#artifactdetails%7Cmaven-plugins%7Cmaven-findbugs-plugin%7C1.3.1%7Cjar
          [4] http://search.maven.org/#artifactdetails%7Cmaven-plugins%7Cmaven-cobertura-plugin%7C1.3%7Cjar

          Show
          Lewis John McGibbney added a comment - I can confirm that the new patch still complains about the following missing dependencies Path to dependency: 1) org.apache.gora:gora-hbase:jar:0.2-SNAPSHOT 2) org.jdom:jdom:jar:1.1.2 3) jaxen:jaxen:jar:1.1.3 4) maven-plugins:maven-findbugs-plugin:plugin:1.3.1 I am kinda stumped on this one as the link here [1] gets you to manually redirect here [2] . Anyway, for clarity details of both the missing plugins can be found here [3] & [4] [1] http://repo1.maven.org/maven2/ [2] http://search.maven.org/ [3] http://search.maven.org/#artifactdetails%7Cmaven-plugins%7Cmaven-findbugs-plugin%7C1.3.1%7Cjar [4] http://search.maven.org/#artifactdetails%7Cmaven-plugins%7Cmaven-cobertura-plugin%7C1.3%7Cjar
          Hide
          Lewis John McGibbney added a comment -

          Hopefully this is the final patch attached. It excludes the two rogue plugins from the org.jdom dependency, these were the ones causing trouble and failing my local build. In addition I've added the gora-sql test target to the pom. This can be removed should it be covered in a separate issue.

          [INFO] Reactor Summary:
          [INFO] ------------------------------------------------------------------------
          [INFO] Apache Gora ........................................... SUCCESS [6.854s]
          [INFO] Apache Gora :: Core ................................... SUCCESS [3:09.720s]
          [INFO] Apache Gora :: Hbase .................................. SUCCESS [13.199s]
          [INFO] Apache Gora :: Cassandra .............................. SUCCESS [39.622s]
          [INFO] Apache Gora :: SQL .................................... SUCCESS [18.727s]
          [INFO] Apache Gora :: Tutorial ............................... SUCCESS [6.166s]
          [INFO] ------------------------------------------------------------------------
          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD SUCCESSFUL
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 4 minutes 34 seconds
          [INFO] Finished at: Tue Nov 22 21:37:12 GMT 2011
          [INFO] Final Memory: 67M/165M
          
          
          Show
          Lewis John McGibbney added a comment - Hopefully this is the final patch attached. It excludes the two rogue plugins from the org.jdom dependency, these were the ones causing trouble and failing my local build. In addition I've added the gora-sql test target to the pom. This can be removed should it be covered in a separate issue. [INFO] Reactor Summary: [INFO] ------------------------------------------------------------------------ [INFO] Apache Gora ........................................... SUCCESS [6.854s] [INFO] Apache Gora :: Core ................................... SUCCESS [3:09.720s] [INFO] Apache Gora :: Hbase .................................. SUCCESS [13.199s] [INFO] Apache Gora :: Cassandra .............................. SUCCESS [39.622s] [INFO] Apache Gora :: SQL .................................... SUCCESS [18.727s] [INFO] Apache Gora :: Tutorial ............................... SUCCESS [6.166s] [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4 minutes 34 seconds [INFO] Finished at: Tue Nov 22 21:37:12 GMT 2011 [INFO] Final Memory: 67M/165M
          Hide
          Chris A. Mattmann added a comment -

          +1, ship it dude. Looks good to me to commit. Don't forget to update CHANGES.txt Thanks for your help!

          Show
          Chris A. Mattmann added a comment - +1, ship it dude. Looks good to me to commit. Don't forget to update CHANGES.txt Thanks for your help!
          Hide
          Henry Saputra added a comment -

          Sorry for late reply. Just took a spin on the patch and LGTM +1.

          Show
          Henry Saputra added a comment - Sorry for late reply. Just took a spin on the patch and LGTM +1.
          Hide
          Lewis John McGibbney added a comment -

          Committed @ revision 1205346 in trunk.
          I would please ask if Chris could finally check and close off if deemed so.
          Thanks for checking this one over.

          Show
          Lewis John McGibbney added a comment - Committed @ revision 1205346 in trunk. I would please ask if Chris could finally check and close off if deemed so. Thanks for checking this one over.
          Hide
          Hudson added a comment -

          Integrated in gora-trunk-ant #43 (See https://builds.apache.org/job/gora-trunk-ant/43/)
          Commit to address GORA-43 and update to changes.txt. Thanks Chris for the direction.

          lewismc : http://svn.apache.org/viewvc/incubator/gora/trunk/viewvc/?view=rev&root=&revision=1205346
          Files :

          • /incubator/gora/trunk/CHANGES.txt
          • /incubator/gora/trunk/pom.xml
          Show
          Hudson added a comment - Integrated in gora-trunk-ant #43 (See https://builds.apache.org/job/gora-trunk-ant/43/ ) Commit to address GORA-43 and update to changes.txt. Thanks Chris for the direction. lewismc : http://svn.apache.org/viewvc/incubator/gora/trunk/viewvc/?view=rev&root=&revision=1205346 Files : /incubator/gora/trunk/CHANGES.txt /incubator/gora/trunk/pom.xml
          Hide
          Chris A. Mattmann added a comment -

          +1 thanks d00d!

          Show
          Chris A. Mattmann added a comment - +1 thanks d00d!
          Hide
          Hudson added a comment -

          Integrated in gora-trunk #49 (See https://builds.apache.org/job/gora-trunk/49/)
          Commit to address GORA-43 and update to changes.txt. Thanks Chris for the direction.

          lewismc : http://svn.apache.org/viewvc/incubator/gora/trunk/viewvc/?view=rev&root=&revision=1205346
          Files :

          • /incubator/gora/trunk/CHANGES.txt
          • /incubator/gora/trunk/pom.xml
          Show
          Hudson added a comment - Integrated in gora-trunk #49 (See https://builds.apache.org/job/gora-trunk/49/ ) Commit to address GORA-43 and update to changes.txt. Thanks Chris for the direction. lewismc : http://svn.apache.org/viewvc/incubator/gora/trunk/viewvc/?view=rev&root=&revision=1205346 Files : /incubator/gora/trunk/CHANGES.txt /incubator/gora/trunk/pom.xml
          Hide
          Lewis John McGibbney added a comment -

          Bulk close of issues. Preparation for Gora 0.2 release candidate.

          Show
          Lewis John McGibbney added a comment - Bulk close of issues. Preparation for Gora 0.2 release candidate.
          Hide
          Hudson added a comment -

          Integrated in goraOracle #6 (See https://builds.apache.org/job/goraOracle/6/)
          Commit to address GORA-43 and update to changes.txt. Thanks Chris for the direction. (Revision 74cbfb0caa264382f0d0dad444daadd8c192349c)

          Result = FAILURE
          lewismc :
          Files :

          • CHANGES.txt
          • pom.xml
          Show
          Hudson added a comment - Integrated in goraOracle #6 (See https://builds.apache.org/job/goraOracle/6/ ) Commit to address GORA-43 and update to changes.txt. Thanks Chris for the direction. (Revision 74cbfb0caa264382f0d0dad444daadd8c192349c) Result = FAILURE lewismc : Files : CHANGES.txt pom.xml

            People

            • Assignee:
              Chris A. Mattmann
              Reporter:
              Chris A. Mattmann
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development