I'd like to keep moving on organizing the planet code so that we can get
the workspace settled and focus on development. From on our discussion
about the workspace setup based on java blueprints I've reworked things
to use /apps/planet as the *real* space for the planet code and I've
moved the planet business layer code back out of the sandbox. So the
layout I have ready to commit is ...
/apps/planet/build.xml
/apps/planet/build.properties
/apps/planet/nbproject
/apps/planet/src/java
- org.apache.roller.planet.business.*
- org.apache.roller.planet.config.*
- org.apache.roller.planet.pojos.*
- org.apache.roller.planet.util.*
/apps/planet/test/java
/apps/planet/testdata
/apps/planet/web (empty right now)
This is all of the code that Roller Weblogger uses for its planet
features and it can be built, tested, and packaged as a jar file to be
included in the Roller Weblogger app and used by the rest of the planet
app code in the sandbox. I left the rest of the planet code in the
sandbox like you wanted, so that includes all the roller.planet.ui.*
stuff which makes up the faces forms, the tasks, and all the web resources.
I think this gives us a good solid start to building out the official
planet app project space and we can migrate new code here only when we
think it's truly ready. So most development for the planet app would
still happen in the sandbox.
-- Allen
