On Fri, Oct 14, 2011 at 6:18 AM, Ian Dickinson <[email protected]> wrote:
> On 13/10/11 22:02, Joshua TAYLOR wrote:
>>
>> I just discovered the schemagen tool, and it looks incredibly useful
>> to me.  I've been experimenting for a while with the command line
>> options, and would now like to use a configuration file instead of
>> passing lots of command line arguments.  However, schemagen seems to
>> ignore configuration files specified with the -c argument.  For
>> instance, my Jena installation is in /usr/local/lib/Jena-2.6.4, so I'd
>> thought that the following test would work (where I'm using the sample
>> schemagen.rdf that comes with Jena):
>
> You are correct, there is a problem with schemagen processing the
> configuration file. I think it was a regression that was introduced when I
> started work on the schemagen maven plugin. I've fixed the bug in Apache svn
> now. You have two slightly unfortunate choices, I'm afraid: either build
> your own snapshot version of Jena from the svn, or avoid the config file and
> use maven, ant or script files to give a repeatable build step for
> schemagen.  Or, if you prefer, I could send you a patch file for you to
> patch your local version of Jena with just the fix for your issue.

Thanks for the quick response!  Well, I'm not too worried about
rebuilding Jena from SVN, but I am already using ant.  When you say
"avoid the config file and use … to give a repeatable build step", you
just mean using something where the configuration can be specified as
command line options (without having to retype them every time),
right?  Since I'm already set up with ant on this project, I think
adding the command line options there will be the simplest option for
now.  If I get some time later on, though, I'll look into rebuilding
from SVN.

> Thanks for spotting and reporting the problem, and apologies for the
> inconvenience!

Thanks again for the quick response, and any inconvenience is easily
outweighed by the convenience of not having to create "schema classes"
by hand!

-- 
Joshua Taylor, http://www.cs.rpi.edu/~tayloj/

Reply via email to