One thing I just thought: when you move the classes around.. lets make sure we use svn move (or the proper refactor tool on InteliJ / Eclipse)
As I think it's important to keep history on SVN.
I think you got this covered... saying it just in case.
yes im doing that where possible, especially on the source.
When you get to the Twitter Bridge, maybe you could import @Porcelli (twitter ID) twitter bridge. He made a few modifications, and it's already mavenized. I guess you would save some time on that front.
ive commited the logging module
ive commited hornetq as integration module
I will disable hudson builds until you finish this.
dev-tests is failing as it's missing libraries on the classpath
Any chance you could make the journal its own module as part of what you're doing now?
Just the journal.. not the storage manager.
It's ok if we use a separate jar for that.
Jonathan Haliday would be really happy with you :-)
yeah i can do that
All the main source is now complete and ive also tweaked the ant build so it still works, so you can run ant compile, jar or distro or alternatively run mvn compile, package or install if you want to install it locally.
theres a bit more to do yet tho.
1) pom the test suite, Bill had already done this but i'm not sure as to how it should/will run so am looking at this now.
2) migrate Bills rest stuff, at the minute this is still its own maven project, with docs, api of its own. I need to consolidate this into the main project.
3) i also need to write something to build the distri vi athe pom, Bill hadnt done this so this may take me a bit, will update you as i go.
any issues let me know
That's weird... If I don't define my own settings.xml with the jboss repositories on maven_Home, then the build will fail at some modules.
Or I would have to define the repository on each individual pom.