Closed ja-fra closed 10 years ago
Releasing 1.3 works for me
OK for me. I will release 1.3 on Friday (02/05/14)
Sorry for the delay. I had a lot of other issues in the past, so I didn't made the release yet. No I scheduled it for 10/06/14.
Should #31 also go into the 1.3 release?
Personally, I don't like the approach of having a single Mojo for all actions, but I see @ansell's point...
It isn't a permanent fix. The original split wasn't clean in terms of the way it sent updates to the builder, although it only broke m2e so the tests and command line still worked. I am fine with testing new approaches to it, possibly including those which don't reuse a base method, as I think that may be part of the issue in the current method.
I have a workflow right now that takes full advantage if being able to edit the ontology in eclipse and then code using the constant that is derived from it straight away with m2e running incremental builds automatically as necessary to enable that.
Everything works in the current method, although conceptually the resources should be derived in the generate resources phase when we go back to multiple mojos.
Sorry, I meant that everything works with a single mojo, not the current multiple mojos.
As far as I understood, the pull request #31 fixes a problem that should be solved before the release. So I did the merge for the release 1.3
Closing issue, Sesame Vocabulary Builder v1.3 has been released.
I think its time for a new release: 1.3
1.2.1 could also work for the bugfixes (#25, #27), but I'd prefer 1.3 since we also have a feature (#28 RDFa support)