[jira] [Commented] (ZEST-190) Refine Metrics API/SPI

[Niclas Hedhman (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZEST-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603733#comment-15603733
 ] 

Niclas Hedhman commented on ZEST-190:
-

I agree. The original design was rushed together too quickly and is tied too 
much to the CodaHale/Yammer metrics library, instead of doing the "Qi4j Way" 
going to the bottom of the actual needs and the unique ways that this platform 
can bring this to the users.

> Refine Metrics API/SPI
> --
>
> Key: ZEST-190
> URL: https://issues.apache.org/jira/browse/ZEST-190
> Project: Zest
>  Issue Type: Improvement
>Reporter: Paul Merlin
>Assignee: Paul Merlin
> Fix For: 3.0
>
>
> The current metrics API mixes in pure metrics aspects with reporting ones. 
> The factories should not require the reporting duration unit nor the rate 
> unit nor display names. These should be chosen when using reporters, whatever 
> the metrics collection backend.
> Let's use {{Stream}} instead of {{Iterable}} in 
> {{MetricsFactory::registered()}}.
> {{@TimingCapture}} concern should name timers with some "Structure path" by 
> default, like we do in jmx support, and allow to name the underlying timer 
> with an annotation parameter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Postgresql indexing tests

[Stanislav Muhametsin]

In 
"extensions/indexing-sql/src/main/java/org/apache/zest/index/sql/support/skeletons/AbstractSQLStartup.java" 
file, there is "initTypes" method.
You might want to add mapping for Identity.class in this._primitiveTypes 
and jdbcTypes, and also most likely this._customizableTypes.


I say "might" want to, since I have really really vague memories on how 
that worked, and I realized I don't have any PC right now with Java 
coding environment set up.
The "appendColumnDefinitionsForProperty" method in the same file uses 
the type mappings mentioned above to deduce what kind of column is to be 
created for property, which might be the issue here.


Also, you probably want to modify the 
"/extensions/indexing-sql/src/main/java/org/apache/zest/index/sql/support/common/QNameInfo.java" 
file, so that the detection whether some Java type is primitive is 
updated to include Identity.

It is done just before setting this._isFinalTypePrimitive.

Let us know if this is of any help to you. :)

On 24/10/2016 17:41, Niclas Hedhman wrote:

Giving up for now...  I think the general problem is that Identity is a
missing type for the Indexing system, and not so much about the toString()
conversion that seems to have been missed only once.


Cheers
Niclas

On Mon, Oct 24, 2016 at 9:26 PM, Niclas Hedhman  wrote:


The issue in the indexing is that Identity is an unknown type for SQL.

I added that in org.apache.zest.index.sql.support.skeletons.AbstractSQLStartup 
and
also added

if( Identity.class.isAssignableFrom( primitiveClass ) )
{
 primitiveClass = Identity.class;
}
else

in org.apache.zest.index.sql.support.postgresql.PostgreSQLTypeHelper.
SQLTypeHelperMixin#getSQLType(java.lang.reflect.Type)

That fixed all the test org.apache.zest.index.sql.postgresql.
PostgreSQLQueryTest,script34

Continuing
--
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

Re: Postgresql indexing tests

[Niclas Hedhman]

Giving up for now...  I think the general problem is that Identity is a
missing type for the Indexing system, and not so much about the toString()
conversion that seems to have been missed only once.


Cheers
Niclas

On Mon, Oct 24, 2016 at 9:26 PM, Niclas Hedhman  wrote:

> The issue in the indexing is that Identity is an unknown type for SQL.
>
> I added that in 
> org.apache.zest.index.sql.support.skeletons.AbstractSQLStartup and
> also added
>
> if( Identity.class.isAssignableFrom( primitiveClass ) )
> {
> primitiveClass = Identity.class;
> }
> else
>
> in org.apache.zest.index.sql.support.postgresql.PostgreSQLTypeHelper.
> SQLTypeHelperMixin#getSQLType(java.lang.reflect.Type)
>
> That fixed all the test org.apache.zest.index.sql.postgresql.
> PostgreSQLQueryTest,script34
>
> Continuing
> --
> Niclas Hedhman, Software Developer
> http://zest.apache.org - New Energy for Java
>



-- 
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

Postgresql indexing tests

[Niclas Hedhman]

The issue in the indexing is that Identity is an unknown type for SQL.

I added that
in org.apache.zest.index.sql.support.skeletons.AbstractSQLStartup and also
added

if( Identity.class.isAssignableFrom( primitiveClass ) )
{
primitiveClass = Identity.class;
}
else

in
org.apache.zest.index.sql.support.postgresql.PostgreSQLTypeHelper.SQLTypeHelperMixin#getSQLType(java.lang.reflect.Type)

That fixed all the
test org.apache.zest.index.sql.postgresql.PostgreSQLQueryTest,script34

Continuing
-- 
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

Jenkins build is back to normal : Zest(JavaEdition)-develop-java8-check #210

[Apache Jenkins Server]

See 

Re: [WARNING] Unstable 'develop' branch

[Stanislav Muhametsin]

On 24.10.2016 15:39, Niclas Hedhman wrote:

Thanks for the help, Stan... Really appreciated that you still watch what
is going on here.


You're welcome, Niclas! :)

I do watch this, just not always enough time to post meaningful reply, 
or the topic is a bit out of scope (e.g. entities) for me after all 
these years. :)





On Mon, Oct 24, 2016 at 8:37 PM, Niclas Hedhman  wrote:


Ii have figured it out... I missed the "reconnect to the jdbc_test_db as a
superuser". My ltree addition happened outside the database
"jdbc_test_db"... On my way now.

On Mon, Oct 24, 2016 at 8:30 PM, Niclas Hedhman 
wrote:


If I go back to psql, I get this informative message

postgres=#  CREATE EXTENSION ltree;
ERROR:  extension "ltree" already exists



On Mon, Oct 24, 2016 at 8:23 PM, Niclas Hedhman 
wrote:


Caused by: org.postgresql.util.PSQLException: ERROR: type ltree 
does not exist
   Position: 55
at 
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2453)
at 
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2153)
at 
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:286)

Is there an easy way to test ltree presence with the psql command line?


On Mon, Oct 24, 2016 at 8:20 PM, Niclas Hedhman 
wrote:


Ah, I see...

stmt.execute( this._vendor.toString( d
 .createTableDefinitionBuilder()
 .setTableScope( TableScope.LOCAL_TEMPORARY )
 .setTableName( t.tableName( "ltree_test" ) )
 .setCommitAction( PgSQLTableCommitAction.DROP )
 .setTableContentsSource(
 d.createTableElementListBuilder()
 .addTableElement(
 d.createColumnDefinition( "test_column", dt.userDefined( "ltree" ) 
) )
 .createExpression() ).createExpression() ) );


is the code executed and ANY SQLException will cause my InternalError,
and SQLException is not shown. Adding the root cause and running again.



On Mon, Oct 24, 2016 at 8:16 PM, Stanislav Muhametsin <
stanislav.muhamet...@zest.mail.kapsi.fi> wrote:


On 24.10.2016 15:05, Niclas Hedhman wrote:


I managed to install postgres locally and set up according to your
instructions. I even needed to figure out that postgresql-contrib
package
was needed for the "ltree" to work (accepted inside psql command
line).


However, I now get an error in the testcases;

java.lang.InternalError: It seems that
your database doesn't have ltree as type. It is needed to store
collections. Please refer to hopefully supplied instructions on how to
add ltree type (hint: run
pg_install_dir/share/contrib/ltree.sql script or command
'CREATE EXTENSION ltree;').


root@devdesk:~# su postgres
postgres@devdesk:/root$ psql
could not change directory to "/root": Permission denied
psql (9.4.9)
Type "help" for help.

postgres=#  CREATE EXTENSION ltree;
CREATE EXTENSION
postgres=# \q


Any ideas??


Indexing-SQL uses some SQL command to test whether ltree extension is
installed.
I totally forgot what is the command, and I can not access Zest
codebase right now.

Can you see the root cause via debugger, the first exception that is
thrown, most likely causes this.
It *might* be that the exception is something else, but the
Indexing-SQL *thinks* it is because of failing ltree-test.







On Mon, Oct 24, 2016 at 7:46 PM, Paul Merlin 
wrote:

So, I ran integration tests and everything is stable except

indexing-sql.

A lot of the query tests fail.
Something about mapping Identity to String is incomplete.

I've attached the tests result report to ZEST-180 and pointed to the
test setup instruction there.


Paul Merlin a écrit :


Niclas,

The Identity change is quite massive, and affects many tests,
especially in
the Entity Stores and Indexing/Query subsystems.

The changes builds on my local Linux system, but I notice that
Redis and
Riak (others?) test suites are disabled, and I have not look into
making
them run locally. So there may still be issues, and I am not at all
surprised if the CI will fail.

And I need to go to sleep now, so it may take a couple of days for
this


to
stabilize.

Cheers


All integration tests that depend on external services are skipped
if
they can't reach the corresponding external service.

For most of them, simply running the service with the default
configuration is enough (Memcached, Redis, Riak, MongoDB).

The SQL EntityStore is always tested against embedded databases
(Derby,
H2, SQLite). If a MySQL or PostgreSQL service is available it will
be
tested against them too. The SQL Index/Query is only tested against
PostgreSQL if available. PostgreSQL needs some special setup
(user/pass
and some extension for indexing, documented in the corresponding


extension).


The CI do not run any of these external services.

Three years ago I did start creating a Docker image with almost all
of
these services (https://github.com/eskatos/zest-docker-testbed).
It's

Re: [WARNING] Unstable 'develop' branch

[Niclas Hedhman]

Ii have figured it out... I missed the "reconnect to the jdbc_test_db as a
superuser". My ltree addition happened outside the database
"jdbc_test_db"... On my way now.

On Mon, Oct 24, 2016 at 8:30 PM, Niclas Hedhman  wrote:

> If I go back to psql, I get this informative message
>
> postgres=#  CREATE EXTENSION ltree;
> ERROR:  extension "ltree" already exists
>
>
>
> On Mon, Oct 24, 2016 at 8:23 PM, Niclas Hedhman 
> wrote:
>
>>
>> Caused by: org.postgresql.util.PSQLException: ERROR: type ltree 
>> does not exist
>>   Position: 55
>>at 
>> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2453)
>>at 
>> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2153)
>>at 
>> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:286)
>>
>> Is there an easy way to test ltree presence with the psql command line?
>>
>>
>> On Mon, Oct 24, 2016 at 8:20 PM, Niclas Hedhman 
>> wrote:
>>
>>> Ah, I see...
>>>
>>> stmt.execute( this._vendor.toString( d
>>> .createTableDefinitionBuilder()
>>> .setTableScope( TableScope.LOCAL_TEMPORARY )
>>> .setTableName( t.tableName( "ltree_test" ) )
>>> .setCommitAction( PgSQLTableCommitAction.DROP )
>>> .setTableContentsSource(
>>> d.createTableElementListBuilder()
>>> .addTableElement(
>>> d.createColumnDefinition( "test_column", dt.userDefined( 
>>> "ltree" ) ) )
>>> .createExpression() ).createExpression() ) );
>>>
>>>
>>> is the code executed and ANY SQLException will cause my InternalError,
>>> and SQLException is not shown. Adding the root cause and running again.
>>>
>>>
>>>
>>> On Mon, Oct 24, 2016 at 8:16 PM, Stanislav Muhametsin <
>>> stanislav.muhamet...@zest.mail.kapsi.fi> wrote:
>>>
 On 24.10.2016 15:05, Niclas Hedhman wrote:

> I managed to install postgres locally and set up according to your
> instructions. I even needed to figure out that postgresql-contrib
> package
> was needed for the "ltree" to work (accepted inside psql command line).
>
>
> However, I now get an error in the testcases;
>
>  type="java.lang.InternalError">java.lang.InternalError: It seems that
> your database doesn't have ltree as type. It is needed to store
> collections. Please refer to hopefully supplied instructions on how to
> add ltree type (hint: run
> pg_install_dir/share/contrib/ltree.sql script or command
> 'CREATE EXTENSION ltree;').
>
>
> root@devdesk:~# su postgres
> postgres@devdesk:/root$ psql
> could not change directory to "/root": Permission denied
> psql (9.4.9)
> Type "help" for help.
>
> postgres=#  CREATE EXTENSION ltree;
> CREATE EXTENSION
> postgres=# \q
>
>
> Any ideas??
>

 Indexing-SQL uses some SQL command to test whether ltree extension is
 installed.
 I totally forgot what is the command, and I can not access Zest
 codebase right now.

 Can you see the root cause via debugger, the first exception that is
 thrown, most likely causes this.
 It *might* be that the exception is something else, but the
 Indexing-SQL *thinks* it is because of failing ltree-test.





>
>
> On Mon, Oct 24, 2016 at 7:46 PM, Paul Merlin 
> wrote:
>
> So, I ran integration tests and everything is stable except
>> indexing-sql.
>>
>> A lot of the query tests fail.
>> Something about mapping Identity to String is incomplete.
>>
>> I've attached the tests result report to ZEST-180 and pointed to the
>> test setup instruction there.
>>
>>
>> Paul Merlin a écrit :
>>
>>> Niclas,
>>>
>>> The Identity change is quite massive, and affects many tests,

>>> especially in
>>
>>> the Entity Stores and Indexing/Query subsystems.

 The changes builds on my local Linux system, but I notice that
 Redis and
 Riak (others?) test suites are disabled, and I have not look into
 making
 them run locally. So there may still be issues, and I am not at all
 surprised if the CI will fail.

 And I need to go to sleep now, so it may take a couple of days for
 this

>>> to
>>
>>> stabilize.

 Cheers

>>> All integration tests that depend on external services are skipped if
>>> they can't reach the corresponding external service.
>>>
>>> For most of them, simply running the service with the default
>>> configuration is enough (Memcached, Redis, Riak, MongoDB).
>>>
>>> The SQL EntityStore is always tested against embedded databases
>>> (Derby,
>>> H2, SQLite). If a MySQL or PostgreSQL service is available it will be
>>> tested against them too. The SQL 

Re: [WARNING] Unstable 'develop' branch

[Stanislav Muhametsin]

On 24.10.2016 15:30, Niclas Hedhman wrote:

If I go back to psql, I get this informative message

postgres=#  CREATE EXTENSION ltree;
ERROR:  extension "ltree" already exists


OK, that is weird...
Maybe 'ltree' extension is per-user?
Have you tried logging in with same user as the Java tests are logging 
in there, and trying to run that SQL command (the CREATE TABLE command) 
by hand?


It *might* be that ltree extension has changed over the years and no 
longer exposes 'ltree' type directly, altho I doubt that a lot.

Re: [WARNING] Unstable 'develop' branch

[Niclas Hedhman]

If I go back to psql, I get this informative message

postgres=#  CREATE EXTENSION ltree;
ERROR:  extension "ltree" already exists



On Mon, Oct 24, 2016 at 8:23 PM, Niclas Hedhman  wrote:

>
> Caused by: org.postgresql.util.PSQLException: ERROR: type ltree 
> does not exist
>   Position: 55
>at 
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2453)
>at 
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2153)
>at 
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:286)
>
> Is there an easy way to test ltree presence with the psql command line?
>
>
> On Mon, Oct 24, 2016 at 8:20 PM, Niclas Hedhman 
> wrote:
>
>> Ah, I see...
>>
>> stmt.execute( this._vendor.toString( d
>> .createTableDefinitionBuilder()
>> .setTableScope( TableScope.LOCAL_TEMPORARY )
>> .setTableName( t.tableName( "ltree_test" ) )
>> .setCommitAction( PgSQLTableCommitAction.DROP )
>> .setTableContentsSource(
>> d.createTableElementListBuilder()
>> .addTableElement(
>> d.createColumnDefinition( "test_column", dt.userDefined( "ltree" 
>> ) ) )
>> .createExpression() ).createExpression() ) );
>>
>>
>> is the code executed and ANY SQLException will cause my InternalError,
>> and SQLException is not shown. Adding the root cause and running again.
>>
>>
>>
>> On Mon, Oct 24, 2016 at 8:16 PM, Stanislav Muhametsin <
>> stanislav.muhamet...@zest.mail.kapsi.fi> wrote:
>>
>>> On 24.10.2016 15:05, Niclas Hedhman wrote:
>>>
 I managed to install postgres locally and set up according to your
 instructions. I even needed to figure out that postgresql-contrib
 package
 was needed for the "ltree" to work (accepted inside psql command line).


 However, I now get an error in the testcases;

 >>> type="java.lang.InternalError">java.lang.InternalError: It seems that
 your database doesn't have ltree as type. It is needed to store
 collections. Please refer to hopefully supplied instructions on how to
 add ltree type (hint: run
 pg_install_dir/share/contrib/ltree.sql script or command
 'CREATE EXTENSION ltree;').


 root@devdesk:~# su postgres
 postgres@devdesk:/root$ psql
 could not change directory to "/root": Permission denied
 psql (9.4.9)
 Type "help" for help.

 postgres=#  CREATE EXTENSION ltree;
 CREATE EXTENSION
 postgres=# \q


 Any ideas??

>>>
>>> Indexing-SQL uses some SQL command to test whether ltree extension is
>>> installed.
>>> I totally forgot what is the command, and I can not access Zest codebase
>>> right now.
>>>
>>> Can you see the root cause via debugger, the first exception that is
>>> thrown, most likely causes this.
>>> It *might* be that the exception is something else, but the Indexing-SQL
>>> *thinks* it is because of failing ltree-test.
>>>
>>>
>>>
>>>
>>>


 On Mon, Oct 24, 2016 at 7:46 PM, Paul Merlin  wrote:

 So, I ran integration tests and everything is stable except
> indexing-sql.
>
> A lot of the query tests fail.
> Something about mapping Identity to String is incomplete.
>
> I've attached the tests result report to ZEST-180 and pointed to the
> test setup instruction there.
>
>
> Paul Merlin a écrit :
>
>> Niclas,
>>
>> The Identity change is quite massive, and affects many tests,
>>>
>> especially in
>
>> the Entity Stores and Indexing/Query subsystems.
>>>
>>> The changes builds on my local Linux system, but I notice that Redis
>>> and
>>> Riak (others?) test suites are disabled, and I have not look into
>>> making
>>> them run locally. So there may still be issues, and I am not at all
>>> surprised if the CI will fail.
>>>
>>> And I need to go to sleep now, so it may take a couple of days for
>>> this
>>>
>> to
>
>> stabilize.
>>>
>>> Cheers
>>>
>> All integration tests that depend on external services are skipped if
>> they can't reach the corresponding external service.
>>
>> For most of them, simply running the service with the default
>> configuration is enough (Memcached, Redis, Riak, MongoDB).
>>
>> The SQL EntityStore is always tested against embedded databases
>> (Derby,
>> H2, SQLite). If a MySQL or PostgreSQL service is available it will be
>> tested against them too. The SQL Index/Query is only tested against
>> PostgreSQL if available. PostgreSQL needs some special setup
>> (user/pass
>> and some extension for indexing, documented in the corresponding
>>
> extension).
>
>> The CI do not run any of these external services.
>>
>> Three years ago I did start creating a Docker image with almost all of
>> these services 

Re: [WARNING] Unstable 'develop' branch

[Niclas Hedhman]

Caused by: org.postgresql.util.PSQLException: ERROR: type
ltree does not exist
  Position: 55
   at 
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2453)
   at 
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2153)
   at 
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:286)

Is there an easy way to test ltree presence with the psql command line?


On Mon, Oct 24, 2016 at 8:20 PM, Niclas Hedhman  wrote:

> Ah, I see...
>
> stmt.execute( this._vendor.toString( d
> .createTableDefinitionBuilder()
> .setTableScope( TableScope.LOCAL_TEMPORARY )
> .setTableName( t.tableName( "ltree_test" ) )
> .setCommitAction( PgSQLTableCommitAction.DROP )
> .setTableContentsSource(
> d.createTableElementListBuilder()
> .addTableElement(
> d.createColumnDefinition( "test_column", dt.userDefined( "ltree" 
> ) ) )
> .createExpression() ).createExpression() ) );
>
>
> is the code executed and ANY SQLException will cause my InternalError, and
> SQLException is not shown. Adding the root cause and running again.
>
>
>
> On Mon, Oct 24, 2016 at 8:16 PM, Stanislav Muhametsin <
> stanislav.muhamet...@zest.mail.kapsi.fi> wrote:
>
>> On 24.10.2016 15:05, Niclas Hedhman wrote:
>>
>>> I managed to install postgres locally and set up according to your
>>> instructions. I even needed to figure out that postgresql-contrib package
>>> was needed for the "ltree" to work (accepted inside psql command line).
>>>
>>>
>>> However, I now get an error in the testcases;
>>>
>>> >> type="java.lang.InternalError">java.lang.InternalError: It seems that
>>> your database doesn't have ltree as type. It is needed to store
>>> collections. Please refer to hopefully supplied instructions on how to
>>> add ltree type (hint: run
>>> pg_install_dir/share/contrib/ltree.sql script or command
>>> 'CREATE EXTENSION ltree;').
>>>
>>>
>>> root@devdesk:~# su postgres
>>> postgres@devdesk:/root$ psql
>>> could not change directory to "/root": Permission denied
>>> psql (9.4.9)
>>> Type "help" for help.
>>>
>>> postgres=#  CREATE EXTENSION ltree;
>>> CREATE EXTENSION
>>> postgres=# \q
>>>
>>>
>>> Any ideas??
>>>
>>
>> Indexing-SQL uses some SQL command to test whether ltree extension is
>> installed.
>> I totally forgot what is the command, and I can not access Zest codebase
>> right now.
>>
>> Can you see the root cause via debugger, the first exception that is
>> thrown, most likely causes this.
>> It *might* be that the exception is something else, but the Indexing-SQL
>> *thinks* it is because of failing ltree-test.
>>
>>
>>
>>
>>
>>>
>>>
>>> On Mon, Oct 24, 2016 at 7:46 PM, Paul Merlin  wrote:
>>>
>>> So, I ran integration tests and everything is stable except indexing-sql.

 A lot of the query tests fail.
 Something about mapping Identity to String is incomplete.

 I've attached the tests result report to ZEST-180 and pointed to the
 test setup instruction there.


 Paul Merlin a écrit :

> Niclas,
>
> The Identity change is quite massive, and affects many tests,
>>
> especially in

> the Entity Stores and Indexing/Query subsystems.
>>
>> The changes builds on my local Linux system, but I notice that Redis
>> and
>> Riak (others?) test suites are disabled, and I have not look into
>> making
>> them run locally. So there may still be issues, and I am not at all
>> surprised if the CI will fail.
>>
>> And I need to go to sleep now, so it may take a couple of days for
>> this
>>
> to

> stabilize.
>>
>> Cheers
>>
> All integration tests that depend on external services are skipped if
> they can't reach the corresponding external service.
>
> For most of them, simply running the service with the default
> configuration is enough (Memcached, Redis, Riak, MongoDB).
>
> The SQL EntityStore is always tested against embedded databases (Derby,
> H2, SQLite). If a MySQL or PostgreSQL service is available it will be
> tested against them too. The SQL Index/Query is only tested against
> PostgreSQL if available. PostgreSQL needs some special setup (user/pass
> and some extension for indexing, documented in the corresponding
>
 extension).

> The CI do not run any of these external services.
>
> Three years ago I did start creating a Docker image with almost all of
> these services (https://github.com/eskatos/zest-docker-testbed). It's
> completely outdated now. I do have a very limited connection these days
> so I won't be able to update it soon. But I have all the services
> locally so I'll try and run the integration tests to see if something
>
 broke.

> Ideally we should build such a Docker image during the build and run
> the
> test suite into it 

Re: [WARNING] Unstable 'develop' branch

[Niclas Hedhman]

Ah, I see...

stmt.execute( this._vendor.toString( d
.createTableDefinitionBuilder()
.setTableScope( TableScope.LOCAL_TEMPORARY )
.setTableName( t.tableName( "ltree_test" ) )
.setCommitAction( PgSQLTableCommitAction.DROP )
.setTableContentsSource(
d.createTableElementListBuilder()
.addTableElement(
d.createColumnDefinition( "test_column", dt.userDefined(
"ltree" ) ) )
.createExpression() ).createExpression() ) );


is the code executed and ANY SQLException will cause my InternalError, and
SQLException is not shown. Adding the root cause and running again.



On Mon, Oct 24, 2016 at 8:16 PM, Stanislav Muhametsin <
stanislav.muhamet...@zest.mail.kapsi.fi> wrote:

> On 24.10.2016 15:05, Niclas Hedhman wrote:
>
>> I managed to install postgres locally and set up according to your
>> instructions. I even needed to figure out that postgresql-contrib package
>> was needed for the "ltree" to work (accepted inside psql command line).
>>
>>
>> However, I now get an error in the testcases;
>>
>> > type="java.lang.InternalError">java.lang.InternalError: It seems that
>> your database doesn't have ltree as type. It is needed to store
>> collections. Please refer to hopefully supplied instructions on how to
>> add ltree type (hint: run
>> pg_install_dir/share/contrib/ltree.sql script or command
>> 'CREATE EXTENSION ltree;').
>>
>>
>> root@devdesk:~# su postgres
>> postgres@devdesk:/root$ psql
>> could not change directory to "/root": Permission denied
>> psql (9.4.9)
>> Type "help" for help.
>>
>> postgres=#  CREATE EXTENSION ltree;
>> CREATE EXTENSION
>> postgres=# \q
>>
>>
>> Any ideas??
>>
>
> Indexing-SQL uses some SQL command to test whether ltree extension is
> installed.
> I totally forgot what is the command, and I can not access Zest codebase
> right now.
>
> Can you see the root cause via debugger, the first exception that is
> thrown, most likely causes this.
> It *might* be that the exception is something else, but the Indexing-SQL
> *thinks* it is because of failing ltree-test.
>
>
>
>
>
>>
>>
>> On Mon, Oct 24, 2016 at 7:46 PM, Paul Merlin  wrote:
>>
>> So, I ran integration tests and everything is stable except indexing-sql.
>>>
>>> A lot of the query tests fail.
>>> Something about mapping Identity to String is incomplete.
>>>
>>> I've attached the tests result report to ZEST-180 and pointed to the
>>> test setup instruction there.
>>>
>>>
>>> Paul Merlin a écrit :
>>>
 Niclas,

 The Identity change is quite massive, and affects many tests,
>
 especially in
>>>
 the Entity Stores and Indexing/Query subsystems.
>
> The changes builds on my local Linux system, but I notice that Redis
> and
> Riak (others?) test suites are disabled, and I have not look into
> making
> them run locally. So there may still be issues, and I am not at all
> surprised if the CI will fail.
>
> And I need to go to sleep now, so it may take a couple of days for this
>
 to
>>>
 stabilize.
>
> Cheers
>
 All integration tests that depend on external services are skipped if
 they can't reach the corresponding external service.

 For most of them, simply running the service with the default
 configuration is enough (Memcached, Redis, Riak, MongoDB).

 The SQL EntityStore is always tested against embedded databases (Derby,
 H2, SQLite). If a MySQL or PostgreSQL service is available it will be
 tested against them too. The SQL Index/Query is only tested against
 PostgreSQL if available. PostgreSQL needs some special setup (user/pass
 and some extension for indexing, documented in the corresponding

>>> extension).
>>>
 The CI do not run any of these external services.

 Three years ago I did start creating a Docker image with almost all of
 these services (https://github.com/eskatos/zest-docker-testbed). It's
 completely outdated now. I do have a very limited connection these days
 so I won't be able to update it soon. But I have all the services
 locally so I'll try and run the integration tests to see if something

>>> broke.
>>>
 Ideally we should build such a Docker image during the build and run the
 test suite into it on CI.




>>
>>
>


-- 
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

Re: [3/3] zest-java git commit: ZEST-180 Indexing-SQL uses the String form of Identity

[Niclas Hedhman]

Hold on, what is this?? UnitOfWork.get() takes an Identity instance, not a
string.

On Mon, Oct 24, 2016 at 7:41 PM,  wrote:

> ZEST-180 Indexing-SQL uses the String form of Identity
>
> Most of the tests still fail after the refactoring.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/zest-java/repo
> Commit: http://git-wip-us.apache.org/repos/asf/zest-java/commit/520aa5f3
> Tree: http://git-wip-us.apache.org/repos/asf/zest-java/tree/520aa5f3
> Diff: http://git-wip-us.apache.org/repos/asf/zest-java/diff/520aa5f3
>
> Branch: refs/heads/develop
> Commit: 520aa5f38acc86cf8631e8a866e6cf844008d72c
> Parents: 23f6bc1
> Author: Paul Merlin 
> Authored: Mon Oct 24 13:40:49 2016 +0200
> Committer: Paul Merlin 
> Committed: Mon Oct 24 13:40:49 2016 +0200
>
> --
>  .../zest/index/sql/support/skeletons/AbstractSQLQuerying.java  | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/zest-java/blob/
> 520aa5f3/extensions/indexing-sql/src/main/java/org/apache/
> zest/index/sql/support/skeletons/AbstractSQLQuerying.java
> --
> diff --git a/extensions/indexing-sql/src/main/java/org/apache/zest/
> index/sql/support/skeletons/AbstractSQLQuerying.java
> b/extensions/indexing-sql/src/main/java/org/apache/zest/
> index/sql/support/skeletons/AbstractSQLQuerying.java
> index c6cc0d6..38ba1f8 100644
> --- a/extensions/indexing-sql/src/main/java/org/apache/zest/
> index/sql/support/skeletons/AbstractSQLQuerying.java
> +++ b/extensions/indexing-sql/src/main/java/org/apache/zest/
> index/sql/support/skeletons/AbstractSQLQuerying.java
> @@ -1055,7 +1055,7 @@ public abstract class AbstractSQLQuerying
>  if( value instanceof EntityComposite )
>  {
>  value = uowf.currentUnitOfWork().get(
> -(EntityComposite) value ).identity().get();
> +(EntityComposite) value
> ).identity().get().toString();
>  }
>  else
>  {
>
>


-- 
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

Build failed in Jenkins: Zest(JavaEdition)-develop-java9-check #17

[Apache Jenkins Server]

See 


Changes:

[paulmerlin] SQL ES: fix MySQL test jdbc url for new drivers

[paulmerlin] SQL ES: better document test setup

[paulmerlin] ZEST-180 Indexing-SQL uses the String form of Identity

--
[...truncated 5214 lines...]
java.lang.NullPointerException

:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:makeVersionClass
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:compileVersionJava
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:compileJavaNote:
 

 uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:honkerGenDependencies
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:honkerGenLicense
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:honkerGenNotice
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:processResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:classes
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:compileTestJava
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:processTestResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:testClasses
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:test
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:makeVersionClass
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:compileVersionJava
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:compileJava
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:honkerGenDependencies
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:honkerGenLicense
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:honkerGenNotice
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:processResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:classes
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:compileTestJava
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:processTestResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:testClasses
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:test
 UP-TO-DATE
:coverageReport SKIPPED
:honkerCheck
:rat SKIPPED
:compileJava UP-TO-DATE
:honkerGenDependencies
:honkerGenLicense
:honkerGenNotice
:processResources UP-TO-DATE
:classes
:globalTestReport
:compileTestJava UP-TO-DATE
:processTestResources UP-TO-DATE
:testClasses UP-TO-DATE
:test UP-TO-DATE
:check
:org.apache.zest.core:honkerCheck
:org.apache.zest.core:check
:org.apache.zest.extensions:honkerCheck
:org.apache.zest.extensions:check
:org.apache.zest.libraries:honkerCheck
:org.apache.zest.libraries:check
:org.apache.zest.manual:honkerCheck
:org.apache.zest.manual:check
:org.apache.zest.samples:honkerCheck
:org.apache.zest.samples:check
:org.apache.zest.tests:honkerCheck
:org.apache.zest.tests:check
:org.apache.zest.tools:honkerCheck
:org.apache.zest.tools:check
:org.apache.zest.tutorials:honkerCheck
:org.apache.zest.tutorials:check
:org.apache.zest.core:org.apache.zest.core.api:honkerCheck
:org.apache.zest.core:org.apache.zest.core.api:check
:org.apache.zest.core:org.apache.zest.core.bootstrap:honkerCheck
:org.apache.zest.core:org.apache.zest.core.bootstrap:check

Re: [WARNING] Unstable 'develop' branch

[Paul Merlin]

So, I ran integration tests and everything is stable except indexing-sql.

A lot of the query tests fail.
Something about mapping Identity to String is incomplete.

I've attached the tests result report to ZEST-180 and pointed to the
test setup instruction there.


Paul Merlin a écrit :
> Niclas,
>
>> The Identity change is quite massive, and affects many tests, especially in
>> the Entity Stores and Indexing/Query subsystems.
>>
>> The changes builds on my local Linux system, but I notice that Redis and
>> Riak (others?) test suites are disabled, and I have not look into making
>> them run locally. So there may still be issues, and I am not at all
>> surprised if the CI will fail.
>>
>> And I need to go to sleep now, so it may take a couple of days for this to
>> stabilize.
>>
>> Cheers
>
> All integration tests that depend on external services are skipped if
> they can't reach the corresponding external service.
>
> For most of them, simply running the service with the default
> configuration is enough (Memcached, Redis, Riak, MongoDB).
>
> The SQL EntityStore is always tested against embedded databases (Derby,
> H2, SQLite). If a MySQL or PostgreSQL service is available it will be
> tested against them too. The SQL Index/Query is only tested against
> PostgreSQL if available. PostgreSQL needs some special setup (user/pass
> and some extension for indexing, documented in the corresponding extension).
>
> The CI do not run any of these external services.
>
> Three years ago I did start creating a Docker image with almost all of
> these services (https://github.com/eskatos/zest-docker-testbed). It's
> completely outdated now. I do have a very limited connection these days
> so I won't be able to update it soon. But I have all the services
> locally so I'll try and run the integration tests to see if something broke.
>
> Ideally we should build such a Docker image during the build and run the
> test suite into it on CI.
>
>
>

[jira] [Commented] (ZEST-180) Replace String with Identity

[Niclas Hedhman (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZEST-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15601739#comment-15601739
 ] 

Niclas Hedhman commented on ZEST-180:
-

I'll go through the test report now

> Replace String with Identity
> 
>
> Key: ZEST-180
> URL: https://issues.apache.org/jira/browse/ZEST-180
> Project: Zest
>  Issue Type: New Feature
>Reporter: Niclas Hedhman
>Assignee: Niclas Hedhman
> Attachments: indexing-sql-test-report.zip
>
>
> We use java.lang.String in many places instead of the Identity type.
> We should replace all those usages with an explicit Identity, to 
> strengthening the APIs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZEST-180) Replace String with Identity

[Paul Merlin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZEST-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Merlin updated ZEST-180:
-
Attachment: indexing-sql-test-report.zip

Test report for {{indexing-sql}} as of 520aa5f38acc86cf8631e8a866e6cf844008d72c.

> Replace String with Identity
> 
>
> Key: ZEST-180
> URL: https://issues.apache.org/jira/browse/ZEST-180
> Project: Zest
>  Issue Type: New Feature
>Reporter: Niclas Hedhman
>Assignee: Niclas Hedhman
> Attachments: indexing-sql-test-report.zip
>
>
> We use java.lang.String in many places instead of the Identity type.
> We should replace all those usages with an explicit Identity, to 
> strengthening the APIs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZEST-180) Replace String with Identity

[Paul Merlin (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZEST-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15601726#comment-15601726
 ] 

Paul Merlin commented on ZEST-180:
--

Most of the {{indexing-sql}} tests fail since the change.

It has to map {{Identity}} to/from {{String}} and only a few places were 
changed.
I fixed one but I suspect there may be other implicit places where this has to 
be fixed.

Test setup is described in 
{{extensions/indexing-sql/src/docs/index-sql-tests.txt}}.

> Replace String with Identity
> 
>
> Key: ZEST-180
> URL: https://issues.apache.org/jira/browse/ZEST-180
> Project: Zest
>  Issue Type: New Feature
>Reporter: Niclas Hedhman
>Assignee: Niclas Hedhman
>
> We use java.lang.String in many places instead of the Identity type.
> We should replace all those usages with an explicit Identity, to 
> strengthening the APIs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZEST-180) Replace String with Identity

[Paul Merlin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZEST-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Merlin updated ZEST-180:
-
Assignee: Niclas Hedhman

> Replace String with Identity
> 
>
> Key: ZEST-180
> URL: https://issues.apache.org/jira/browse/ZEST-180
> Project: Zest
>  Issue Type: New Feature
>Reporter: Niclas Hedhman
>Assignee: Niclas Hedhman
>
> We use java.lang.String in many places instead of the Identity type.
> We should replace all those usages with an explicit Identity, to 
> strengthening the APIs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: Zest(JavaEdition)-develop-java9-check #16

[Apache Jenkins Server]

See 


Changes:

[paulmerlin] Indexing-RDF doc, fix snippet inclusion paths after file move

[paulmerlin] Remove executable bit on java/html/css/ts files

--
[...truncated 10508 lines...]
java.lang.NullPointerException

:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:makeVersionClass
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:compileVersionJava
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:compileJavaNote:
 

 uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:honkerGenDependencies
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:honkerGenLicense
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:honkerGenNotice
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:processResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:classes
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:compileTestJava
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:processTestResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:testClasses
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:test
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:makeVersionClass
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:compileVersionJava
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:compileJava
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:honkerGenDependencies
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:honkerGenLicense
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:honkerGenNotice
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:processResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:classes
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:compileTestJava
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:processTestResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:testClasses
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:test
 UP-TO-DATE
:coverageReport SKIPPED
:honkerCheck
:rat SKIPPED
:compileJava UP-TO-DATE
:honkerGenDependencies
:honkerGenLicense
:honkerGenNotice
:processResources UP-TO-DATE
:classes
:globalTestReport
:compileTestJava UP-TO-DATE
:processTestResources UP-TO-DATE
:testClasses UP-TO-DATE
:test UP-TO-DATE
:check
:org.apache.zest.core:honkerCheck
:org.apache.zest.core:check
:org.apache.zest.extensions:honkerCheck
:org.apache.zest.extensions:check
:org.apache.zest.libraries:honkerCheck
:org.apache.zest.libraries:check
:org.apache.zest.manual:honkerCheck
:org.apache.zest.manual:check
:org.apache.zest.samples:honkerCheck
:org.apache.zest.samples:check
:org.apache.zest.tests:honkerCheck
:org.apache.zest.tests:check
:org.apache.zest.tools:honkerCheck
:org.apache.zest.tools:check
:org.apache.zest.tutorials:honkerCheck
:org.apache.zest.tutorials:check
:org.apache.zest.core:org.apache.zest.core.api:honkerCheck
:org.apache.zest.core:org.apache.zest.core.api:check
:org.apache.zest.core:org.apache.zest.core.bootstrap:honkerCheck
:org.apache.zest.core:org.apache.zest.core.bootstrap:check

Build failed in Jenkins: Zest(JavaEdition)-develop-java8-check #209

[Apache Jenkins Server]

See 


Changes:

[paulmerlin] ZEST-183 Remove eventsourcing library from docs

[paulmerlin] ZEST-188 Remove scala library from docs

[paulmerlin] Indexing-RDF doc, fix snippet inclusion paths after file move

[paulmerlin] Remove executable bit on java/html/css/ts files

--
[...truncated 1683 lines...]
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:testClasses
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:test
 UP-TO-DATE
:coverageReport
:honkerCheck
:rat SKIPPED
:compileJava UP-TO-DATE
:honkerGenDependencies
:honkerGenLicense
:honkerGenNotice
:processResources UP-TO-DATE
:classes
:globalTestReport
:compileTestJava UP-TO-DATE
:processTestResources UP-TO-DATE
:testClasses UP-TO-DATE
:test UP-TO-DATE
:check
:org.apache.zest.core:honkerCheck
:org.apache.zest.core:check
:org.apache.zest.extensions:honkerCheck
:org.apache.zest.extensions:check
:org.apache.zest.libraries:honkerCheck
:org.apache.zest.libraries:check
:org.apache.zest.manual:honkerCheck
:org.apache.zest.manual:check
:org.apache.zest.samples:honkerCheck
:org.apache.zest.samples:check
:org.apache.zest.tests:honkerCheck
:org.apache.zest.tests:check
:org.apache.zest.tools:honkerCheck
:org.apache.zest.tools:check
:org.apache.zest.tutorials:honkerCheck
:org.apache.zest.tutorials:check
:org.apache.zest.core:org.apache.zest.core.api:honkerCheck
:org.apache.zest.core:org.apache.zest.core.api:check
:org.apache.zest.core:org.apache.zest.core.bootstrap:honkerCheck
:org.apache.zest.core:org.apache.zest.core.bootstrap:check
:org.apache.zest.core:org.apache.zest.core.functional:honkerCheck
:org.apache.zest.core:org.apache.zest.core.functional:check
:org.apache.zest.core:org.apache.zest.core.io:honkerCheck
:org.apache.zest.core:org.apache.zest.core.io:check
:org.apache.zest.core:org.apache.zest.core.runtime:honkerCheck
:org.apache.zest.core:org.apache.zest.core.runtime:check
:org.apache.zest.core:org.apache.zest.core.spi:honkerCheck
:org.apache.zest.core:org.apache.zest.core.spi:check
:org.apache.zest.core:org.apache.zest.core.testsupport:honkerCheck
:org.apache.zest.core:org.apache.zest.core.testsupport:check
:org.apache.zest.extensions:org.apache.zest.extension.cache-ehcache:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.cache-ehcache:check
:org.apache.zest.extensions:org.apache.zest.extension.cache-memcache:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.cache-memcache:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-file:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-file:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-geode:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-geode:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-hazelcast:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-hazelcast:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-jclouds:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-jclouds:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-jdbm:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-jdbm:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-leveldb:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-leveldb:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-memory:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-memory:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-mongodb:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-mongodb:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-preferences:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-preferences:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-redis:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-redis:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-riak:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-riak:check
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-sql:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.entitystore-sql:check
:org.apache.zest.extensions:org.apache.zest.extension.indexing-elasticsearch:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.indexing-elasticsearch:check
:org.apache.zest.extensions:org.apache.zest.extension.indexing-rdf:honkerCheck
:org.apache.zest.extensions:org.apache.zest.extension.indexing-rdf:check

Build failed in Jenkins: Zest(JavaEdition)-develop-java9-check #15

[Apache Jenkins Server]

See 


Changes:

[paulmerlin] ZEST-183 Remove eventsourcing library from docs

[paulmerlin] ZEST-188 Remove scala library from docs

--
[...truncated 13582 lines...]
java.lang.NullPointerException

:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:makeVersionClass
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:compileVersionJava
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:compileJavaNote:
 

 uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:honkerGenDependencies
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:honkerGenLicense
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:honkerGenNotice
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:processResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:classes
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:compileTestJava
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:processTestResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:testClasses
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.thirtyminutes:test
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:makeVersionClass
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:compileVersionJava
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:compileJava
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:honkerGenDependencies
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:honkerGenLicense
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:honkerGenNotice
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:processResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:classes
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:compileTestJava
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:processTestResources
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:testClasses
 UP-TO-DATE
:org.apache.zest.tutorials:org.apache.zest.tutorial.introduction:org.apache.zest.tutorial.introduction.twominutes:test
 UP-TO-DATE
:coverageReport SKIPPED
:honkerCheck
:rat SKIPPED
:compileJava UP-TO-DATE
:honkerGenDependencies
:honkerGenLicense
:honkerGenNotice
:processResources UP-TO-DATE
:classes
:globalTestReport
:compileTestJava UP-TO-DATE
:processTestResources UP-TO-DATE
:testClasses UP-TO-DATE
:test UP-TO-DATE
:check
:org.apache.zest.core:honkerCheck
:org.apache.zest.core:check
:org.apache.zest.extensions:honkerCheck
:org.apache.zest.extensions:check
:org.apache.zest.libraries:honkerCheck
:org.apache.zest.libraries:check
:org.apache.zest.manual:honkerCheck
:org.apache.zest.manual:check
:org.apache.zest.samples:honkerCheck
:org.apache.zest.samples:check
:org.apache.zest.tests:honkerCheck
:org.apache.zest.tests:check
:org.apache.zest.tools:honkerCheck
:org.apache.zest.tools:check
:org.apache.zest.tutorials:honkerCheck
:org.apache.zest.tutorials:check
:org.apache.zest.core:org.apache.zest.core.api:honkerCheck
:org.apache.zest.core:org.apache.zest.core.api:check
:org.apache.zest.core:org.apache.zest.core.bootstrap:honkerCheck
:org.apache.zest.core:org.apache.zest.core.bootstrap:check
:org.apache.zest.core:org.apache.zest.core.functional:honkerCheck