PR#312 has been merged which makes the top POM the maven parent.
The jena-project folder in your workspace will be cleared but "git pull"
won't delete it. There will be target/ and maybe some IDE dot-files.
jena-project can be deleted manually.
The development snapshots have been updated.
Andy
On 20/11/17 10:13, Rob Vesse wrote:
+1
On 17/11/2017, 15:16, "ajs6f" <[email protected]> wrote:
I'm basically +1 to this-- jena-project was always confusing at best.
In theory, we could factor out some of those 932 lines with a Jena Maven BOM. Actually, that might be nice for integrators and those using apache-jena-lib.
ajs6f
> On Nov 17, 2017, at 10:12 AM, Andy Seaborne <[email protected]> wrote:
>
> When we moved to one version for all modules, pressure of time pushed us
to have jena-project as a copy of the old jena-parent.
>
> Do we want to go the next step forward which is to merge jena-project
into the top POM and drop the jena-project module?
>
> It turns out to be quite easy to do.
>
> PR for discussion:
> https://github.com/apache/jena/pull/312
>
> It does make the top POM quite large - 932 lines.
>
> Thoughts?
>
> Andy
