On 27/06/14 11:12, Benson Margulies wrote:
Shall I make the plugin have that version number, too?
If you leave the <version> for the moment, we can discuss the long term
policy.
I'll fix the enforcer glitch.
Thanks - the solution didn't jump straight out at me.
Andy
On Fri, Jun 27, 2014 at 4:00 AM, Andy Seaborne <a...@apache.org> wrote:
On 27/06/14 03:35, Benson Margulies wrote:
OK, got into JIRA, created two jiras, committed, marked them resolved.
Great - there's a build problem as noted because the enforcer enforces.
Andy, could you please add a component for the jena-maven-tools and a
version for 0.5 and 0.6 and I'll spruce them up further.
Component "Maven Tool" added to JIRA.
I don't what everyone else thinks but you might as well use the Jena version
number.
It is part of the main build/release cycle now and releases are what affect
users. It's also what people seem to use for labels on reports.
TDB's (internal) version reflects disk format, but nowadays such a chanage
is going to be a Jena change. I've just removed the active JIRA version.
Andy
On Thu, Jun 26, 2014 at 9:42 PM, Benson Margulies <bimargul...@gmail.com>
wrote:
Hi folks.
I'm temporarily locked out of JIRA. I have some fixes to the maven
plugin.
If infra unsticks me, I'll make a JIRA, but if not, would anyone be
disturbed if I made a jira-less commit?
The fixes are:
1: make the default output generated-sources/jena. Using
generated-sources tangles up with 'annotations'.
2: make the output directory configurable.
3: add the output directory to the source roots.
--benson
