The Apache Jenkins build system has built GORA_94_BRANCH (build #3)
Status: Still Failing
Check console output at https://builds.apache.org/job/GORA_94_BRANCH/3/ to view
the results.
The Apache Jenkins build system has built GORA_94_BRANCH (build #2)
Status: Still Failing
Check console output at https://builds.apache.org/job/GORA_94_BRANCH/2/ to view
the results.
Hi Team,
You'll have seen the recent bulk commit of GORA_94 for gora-core,
gora-compiler, gora-cpmpiler-cli, and gora-cassandra (the latter can be
ignored FTM).
I've set up a build here [0].
As I said, I did not try to test this locally and it appears that the test
classes are not compiling.
If any
The Apache Jenkins build system has built GORA_94_BRANCH (build #1)
Status: Failure
Check console output at https://builds.apache.org/job/GORA_94_BRANCH/1/ to view
the results.
[
https://issues.apache.org/jira/browse/GORA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749199#comment-13749199
]
Lewis John McGibbney commented on GORA-94:
--
Newly generated databeans for webpage, t
[
https://issues.apache.org/jira/browse/GORA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated GORA-94:
-
Attachment: GORA_94v5.patch
OK I upload a patch which compiles against the GORA_94 branch.
Apostolos Giannakidis created GORA-272:
--
Summary: Correct the SLF4J bindings in the pom.xml files
Key: GORA-272
URL: https://issues.apache.org/jira/browse/GORA-272
Project: Apache Gora
I
Hi Apos,
I think you are right, we should start at some point fixing this pom
exclussions.
Thank you very for starting this mate!
Renato M.
2013/8/23 Apostolis Giannakidis
> Hey all,
>
> When the user executes:
> bin/gora logmanager
>
> the following warnings are displayed:
> SLF4J: Class pa
Hey all,
When the user executes:
bin/gora logmanager
the following warnings are displayed:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/Users/apostolosgiannakidis/Desktop/MSc/MScProject/src/apache-gora-0.3/gora-tutorial/lib/slf4j-jdk14-1.6.1.jar!/org/slf4
Sure,
but based on which value will we set the parameter? It should be a
datastore specific value; i.e. each data store should set its own value for
this parameter. This is why I proposed to put it in the gora.properties
file, as this will be configurable for each data store. This will serve as
the
We'd have to set the new parameter before we start that specific test. Does
it make sense?
Renato M.
2013/8/22 Apostolis Giannakidis
> Oracle can have both inclusive and exclusive ranges.
> However, I still have not understood how the test cast will work, if we
> follow Renato's suggestion to
11 matches
Mail list logo