On 21/02/15 22:17, Claude Warren wrote:
Your changes look fine to me. I was just trying to update the list.
not sure what you meant by this: For the list of all artifacts, how about
"automation" as linking to the central maven repository?
It's a good idea to have all the artifacts shown - I meant only that for
a purely automated system we don't get the highlighting of the modules
that do matter to users (or have to put more work into getting a nice
list e.g. descriptions suiable for the page, not a brief maven
description). My guess is that we would get a steady, albeit low,
number of questions arise, particularly for artifact "jena".
A curated list of artifacts focuses on the modules we expect people to
want. Then a full list of every module (we seem to have quite few now!)
is less valuable. So pointing to a convenient list elsewhere (maven
central), seemed to achieve much of the effect with no work.
Andy
On Sat, Feb 21, 2015 at 5:58 PM, Andy Seaborne <[email protected]> wrote:
Claude - ping?
On 16/02/15 12:41, Andy Seaborne wrote:
On 15/02/15 12:12, Claude Warren wrote:
...
Is there any reason why the build system can not update the documentation
links when a new release is promoted?
On a slightly different front, I worked out a script that allowed me to
generate the list of modules from the POM files, updating the list
automatically should not be hard, but again, it would need to be executed
when the release is made.
thoughts?
Good idea. We have different kinds of artifacts - major delivery
points, others, and internal artifacts more due to the structure of
Jena. I have put in to staging a revised version for discussion that
highlights the delivery (major and other) ones in some sort of order
(happy to refine that - I didn't put that much thought into the list
order; also the descriptions could be tightened up to be more focused on
the audience of binary users) so that apache-jena-* are first.
Specifically the "jena" artifact is not first and it's description
explains it's role (otherwise, it'll confuse people if it's first!)
We need to manually manage that delivery module list but I think that
it'll be less support work to have a curated list than an unordered list
of everything.
Many of the artifacts are structures for development and not really
about delivery to users. We are about to have big jump in the number of
artifacts as your list shows. For the list of all artifacts, how about
"automation" as linking to the central maven repository?
Andy
