Hi,
the initial plan was to try to achieve the first incubating release in
two weeks. We knew it was a quite had deadline, but the idea behind this
planning was to push to get the goal. And I still see it feasible by the
end of next weeks (ten days from today).
In out checklist we have
- web
- renaming
- bugs
- build
- conflictive dependencies
The first four things are something we can internally manage: web site
is evolving pretty well; full renaming is almost complete; bugs, some
caused because the renaming, are being identified and on the way to be
solved soon; and the building process is being adapted to the new setup,
including also the multi-platform installer.
But the last item is probably the most difficult one to solve, and we
may need support from our mentors. Actually there are three families of
issues:
1) Fix custom dependencies (MARMOTTA-109), basically the dependency on
our custom packaging on Rome Tools, which includes some fixes on the
usage of jdom. I'm not sure what we can do...
2) Those which are not yet available at Maven central repository
(MARMOTTA-112), basically this is the case of
dfki.km.json:jsonld-java:jar:1.0.0-SNAPSHOT
3) Artifacts with licences that are not compatible with the ASF
policies. I know this block a proper Apache release, also a incubating
one? Basically that affects to:
- c3p0 as connection pool (MARMOTTA-111)
- UnboundID LDAP SDK for Java (awaiting for LEGAL-160)
- Javassist (LGPL)
- MySQL java connector (according to LEGAL-21, this is runtime and
optional dependency, so should be fine)
- JBoss Logging (LGPL)
And, I think, that's it. Do I forget anything else?
Bureaucracy that has to be done ;-)
Cheers,
--
Sergio Fernández
