I am moving the integration test for the render service back to the rave-portal module. It was located in rave-opensocial, but since it is intended to test all providers, I figured it would be better at a top level project. This also simplifies the dependencies and resources in rave-opensocial.
If we come up with a better strategy, I will move it back out of rave-portal. -Matt >-----Original Message----- >From: Ate Douma [mailto:[email protected]] >Sent: Wednesday, September 21, 2011 4:32 AM >To: [email protected] >Subject: Heads up: incoming RAVE-171 project reorganization! > >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
