[ 
https://issues.apache.org/jira/browse/JENA-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874529#comment-15874529
 ] 

Rob Vesse edited comment on JENA-1290 at 2/20/17 2:09 PM:
----------------------------------------------------------

I don't understand the build problem.  It looks like the {{ServiceLoader}} 
initialization isn't happening.  I've never seen this before in a build.  

It does not look like a simple classpath problem - the main and test code 
compiles and starts to run.

I use the same java version and same maven, except Alexis has:

{noformat}
Apache Maven 3.3.9 (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 
2015-11-23T08:17:27-02:00)
{noformat}
whereas I have
{noformat}
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T16:41:47+00:00)
{noformat}

You don't need to build from scratch - though you are welcome to - a clean repo 
and building a module should pull in the jars from the Apache snapshots repo.

If building from scratch, you have to build Jena from the top, not module by 
module, the first time.

A fast route to get modules up to Fuseki2:
{noformat}
    mvn clean install -Pboostrap
    mvn clean install -Pdev
{noformat}
as being quicker than the full
{noformat}
    mvn clean install
{noformat}

All run in the Jena root directory.






was (Author: andy.seaborne):
I don't understand the build problem.  It looks like the {{ServiceLoader}} 
initialization isn't happening.  I've never seen this before in a build.  

It does not look like a simple classpath problem - the main and test code 
compiles and starts to run.

I use the same java version and same maven, except Alexis has:

{noformat}
Apache Maven 3.3.9 (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 
2015-11-23T08:17:27-02:00)
{noformat}
whereas I have
{noformat}
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T16:41:47+00:00)
{noformat}

You don't need to build from scratch - though you are welcome to - a clean repo 
and building a module should pull in the jars from the Apache snapshots repo.

If building from scratch, you have to build Jena from the top, not module by 
module, the first time.

A fast route to get modules up to Fuseki2:
{noformat}
    mvn clean install -Dboostrap
    mvn clean install -Ddev
{noformat}
as being quicker than the full
{noformat}
    mvn clean install
{noformat}

All run in the Jena root directory.





> Slow Model.createList()
> -----------------------
>
>                 Key: JENA-1290
>                 URL: https://issues.apache.org/jira/browse/JENA-1290
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: Jena 3.0.1, Jena 3.2.0
>         Environment: OpenJDK 1.8.0.121-b13
>            Reporter: Alexis Armin Huf
>            Priority: Minor
>         Attachments: JENA-1290.patch, jena-slow-rdflist.tar.gz, 
> mvn-clean-install.log.gz
>
>
> Model.createList(Iterator) is slow for large list sizes. Starting at 128 
> nodes, creating a list from an ArrayList iterator takes ~3.6ms and the time 
> goes up to 182ms for 1024 nodes. Creating the RDF list by hand and then doing 
> .as(RDFList.class) for the 1024-nodes tests takes only 1.2ms. I will attach a 
> MWE.
> Going through the code, the cause seems to be that RDFListImpl.with() , which 
> is called for every member added, will always walk the entire list to get the 
> last node. It mentions a possible cache for that, but it is not implemented. 
> I wrote a patch for this issue replacing ModelCom.createList() 
> implementation. I could not find tests for createList, so I added three 
> simple ones to TestModel.
> PS: I'm having a classpath issue with jena-arq tests on mvn clean install, so 
> I could only run tests for jena-core. Are there more specific instructions 
> somewhere for building and testing jena?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to