On 09/21/2011 11:01 AM, Ate Douma wrote:
Done!
I'll wrap up the RAVE-171 issue as well as create a few (2) new issues for some
needed additional actions later today.
Done, see:
https://issues.apache.org/jira/browse/RAVE-173
https://issues.apache.org/jira/browse/RAVE-174
Furthermore, I'll update the sandbox/rave-extensions/rave-vanilla-extension
project to realign with the new project structure as an example.
Also done, the rave-vanilla-extension project now builds and works again.
BTW: it turned out to be broken before, even before the RAVE-171 changes...
This will have to wait a few hours though as I've other obligations right now.
Thanks,
Ate
On 09/21/2011 10:32 AM, Ate Douma wrote:
Hi all,
I've finally completed the RAVE-171 project reorganization locally and now am
ready to commit this.
Please check: https://issues.apache.org/jira/browse/RAVE-171 if you are unaware
of the details.
This is a heads up that *major* structure changes will be incoming, so much so
that I expect everyone probably will have to do a clean checkout if you have a
current checked out version managed through an IDE (Eclipse, IntelliJ, etc.).
If you do have pending changes locally, I advise you to first create a local
patch to save guard you changes (don't forget new files not yet added to svn...)
and try to merge/apply those (manually) after the clean checkout of rave trunk.
The commit will be a one big bang, with all moves, deletes, updates and new
file/folder creations in one big lump. Splitting these apart would have been
possible but very time consuming (replacing all changes I've did before) and
causing a considerable "off limits" and intermediate broken state of trunk.
Commit fill follow within a few minutes...
Regards,
Ate
