[jira] [Resolved] (JENA-145) ARQ should depend on org.apache.jena:jena-core:2.6.5-incubating-SNAPSHOT instead of the latest stable Jena release

["Andy Seaborne (Resolved) (JIRA)" <ji...@apache.org>]

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

Andy Seaborne resolved JENA-145.
--------------------------------

    Resolution: Fixed
      Assignee: Andy Seaborne

Applied - except for pom.xml made it depend on an openjena hoisted build of jena.
                
> ARQ should depend on org.apache.jena:jena-core:2.6.5-incubating-SNAPSHOT instead of the latest stable Jena release
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: JENA-145
>                 URL: https://issues.apache.org/jira/browse/JENA-145
>             Project: Jena
>          Issue Type: Dependency upgrade
>          Components: ARQ
>            Reporter: Paolo Castagna
>            Assignee: Andy Seaborne
>            Priority: Minor
>         Attachments: JENA-145_ARQ.patch, JENA-145_JenaTop.patch
>
>   Original Estimate: 0.1h
>  Remaining Estimate: 0.1h
>
> ARQ's trunk is currently in development mode and its version (in the new Apache universe) is org.apache.jena:jena-arq:2.8.9-incubating-SNAPSHOT.
> ARQ should depend on org.apache.jena:jena-core:2.6.5-incubating-SNAPSHOT instead of the latest stable Jena release.
> This way if a change necessary to ARQ is made in Jena (now called jena-core) it is immediately available to ARQ.
> An example of this happening is JENA-135.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira