k. check it out if you are interested ...
svn co https://svn.apache.org/repos/asf/roller/planet/core/trunk
roller-planet
a few things about the changes ...
* project layout is directly from the java blueprints recommendation for
a j2ee webapp. everything needed for the project is included and should
be pretty simple to understand.
* there is no netbeans project directory and i prefer it that way, so i
have that directory set to svn:ignore. how you setup your IDE is your
business and since the project doesn't require these files in any way i
just assume let each developer manage them independently. i plan to
create a simple wiki page on how to setup a Roller Planet development
environment in netbeans as an alternative.
* i scrapped the sql generation scripts used in the weblogger project
and went with simple mysql based static files (setup/sql). my feeling
here is that we are not a large enough project/community to claim we
support lots of dbs and AFAIK none of the main developers really test
against anything other than mysql anyways. if someone wants to use an
alternate db we can create a wiki page explaining how to do it, but
realistically we don't have the resources to officially support lots of
various dbs.
* lots of code changes, but those should be simple enough to follow by
looking at the code. very few fundamental changes, mostly just
streamlining things.
as for things that i am still planning to do ...
* i have a port of the new security system planned for Weblogger 4.1
almost ready. i wanted to do this as a proof of concept for some of my
ideas and the planet code was easier to work from 'cuz it's smaller and
has better unit test coverage.
* i plan to eliminate velocity and just use freemarker. freemarker is
much better IMO.
that's about it for now. enjoy.
-- Allen
Allen Gilliland wrote:
I haven't heard anyone against the idea, so what I am hoping to do is
spend a little bit of time tomorrow to get this done. Since I'll just
be copying the Planet code to its new location this will be a completely
non-destructive change and if it doesn't fit for some reason it can be
blown away very easily.
-- Allen
Dave wrote:
On Thu, Jun 26, 2008 at 7:42 PM, Allen Gilliland
<[EMAIL PROTECTED]> wrote:
i also like the idea of allowing people to commit plugins to the
repository,
which he haven't done so far. we tried using java.net for a plugin
repository but i think that's been a failed experiment and it would
be far
more ideal to let people maintain their plugins in apache svn. i think
that's easier for everyone and would help boost participation in the
project.
+1
I agree. We should stop using the roller.dev.java.net site and
consolidate plugins and themes at Apache Roller.
- Dave
