Luciano Resende wrote:
The main goal for the clean up is to reduce amount of code users will
download and a step towards reducing our build time.
Some of these modules (e.g assembly-java-dsl, implementation-openjpa)
have been in trunk for a very long time without anyone really using or
maintaining it, and keeping them on a contrib directory would not help
achieve any of the cleanup goals.
Also, if anyone is interested, these code are available in multiple
release branches
I can't find implementation-openjpa in a release branch, did I miss it?
and svn is very powerful to allow anyone to recover
them with a single command.
What do you do if you don't know what's available to recover in the
first place?
IIRC, Simon Laws had a proposal to re-organize the modules. Instead of
removing, I suggest that we move them into a folder such as "contrib" at the
same level as "modules".
1) contrib will contain experiment code that our community members can look
and improve
+1
2) modules will contain fairly stable code that targets for releases
3) keep contrib in the maven build as much as we can
4) a module under contrib can be moved to modules if it becomes ready
Not sure yet what to think about 2/3/4.
--
Jean-Sebastien
