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

ASF subversion and git services commented on JENA-977:
------------------------------------------------------

Commit 3c59213e273711836628d9d030df23dac142ee1b in jena's branch 
refs/heads/JENA-977 from [~rvesse]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=3c59213 ]

Fix script usage in dev environment (JENA-977)

This commit enhances the distribution module to make it much easier to
use in dev environments.  The dependency plugin is used with the
copy-dependencies goal to produce the lib/ directory during a package
phase and then clean plugin is configured to clean the lib/ directory
during a clean.  This means that developers can now set JENA_HOME to the
distribution module directory in their working copy and provided they
have done a mvn package all the scripts should work.

This also allows the temporary hacks in the new tdbloader2 scripts to be
removed so these scripts now run against Jena 3 libraries and don't need
the path to the new scripts to be hacked.


> tdbloader2 script refactoring
> -----------------------------
>
>                 Key: JENA-977
>                 URL: https://issues.apache.org/jira/browse/JENA-977
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: TDB
>    Affects Versions: Jena 2.13.0
>            Reporter: Rob Vesse
>            Assignee: Rob Vesse
>             Fix For: Jena 2.13.1, Jena 3.0.0
>
>
> As noted on the dev list the current scripts are a little rough around the 
> edges, work items include:
> - Splitting data and index phase into separate scripts
> - Being able to restart a build from a later phase
> - Progress monitoring for the sort portion of indexing
> - Warning if sort is using a disk where you may have insufficient space
> - Better usage summaries
> - Better argument handling (avoid relying on magic environment variables 
> wherever possible)



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

Reply via email to