Hi,
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
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
I also suggest that leave the deprecation discussion to the other thread we
had.
Thanks,
Raymond
--------------------------------------------------
From: "Luciano Resende" <[EMAIL PROTECTED]>
Sent: Tuesday, September 09, 2008 12:03 AM
To: <[email protected]>
Subject: Cleaning up Tuscany SVN Trunk
I'd like to propose we start looking into minor code cleanup in our
trunk aiming reducing it's size and reducing the build time.
After some investigation, some items that could be considered are :
- Remove obsolete modules such assembly-java-dsl, implementation-openjpa
- Remove obsolete iTests (e.g contribution-multiple in favor of using
domain/node apis for multiple contributions)
- Remove duplicate sample/itest (e.g sample/helloworld-bpel and
itest/bpel/helloworld)
- Consider removing some deprecated code
Thoughts ? Other items that could be added to the list ?
If people are OK, I have couple of these items ready locally and will
start adding them tomorrow.
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
