Reverse Engineering rt.jar

[Josef Stadelmann]

has one done this?

There is so many class / structure defined in rt.jar
So a reverse engineering cycle may make sense.
However rt.jar (and others) ARE VERY large and
I like to avoid to go through this RE cycle every time.

What is the best practise to realise that RE cycle once
and then keep it ready in a central maven repository
that other EA models can make use of it automatic on
demand.

Here a maven based aproach could help a lot, to update
a model repository with re-data once a change happend
in one of the base jar's.

i.e. a new relases of a jar happens frequently in Open Source
Projects, and hence maven gets it downloaded ASAP after a
central RE cycle toke place.

Any thoughts on that?
Josef