Re: [Springframework-developer] Fw: [springframework - Help] Building Spring from source

[Luke T. <lu...@mo...>]

Hi all,

A few things to follow up.

1. Anyone else can add themselves to the developers list in the 
project.xml, then their full names will appear in the report.

2. I'll try and update the clover jar (though it looks like an older 
version than the current one used by the maven plugin) and look at 
modifying the styles to match the main logo.

3. The "about" text can be switched to anything and will currently just 
be the description in the project.xml. Feel free to change it. I had a 
skeleton set of xdocs files in CVS a while back but they're not there 
anymore. It's probably best just to keep producing the reports from the 
maven build and link back to the main site

4. The XML parser issue cropped up a while back - I think it's a crimson 
vs xerces thing. Building with ant you're using xerces. I can probably 
switch Maven to use xerces too. Does someone know what the problem is? 
Will it cause issues with using the framework with another parser?

5. No cheating by doing extra commits to get to the top of the list :-).

6. Anyone got any useful tips on setting up a continuous 
integration/build system? The reports aren't going to be much use unless 
they're current.

7. To stop the build breaking, it would be very useful if people could 
update the dependencies in the project.xml file when jars are added or 
updated. E.g. for the new velocity stuff:

       <dependency>
          <id>velocity</id>
          <version>1.3.1</version>
       </dependency>
       <dependency>
          <groupId>velocity-tools</groupId>
          <artifactId>velocity-tools-generic</artifactId>
          <version>1.0</version>
       </dependency>

You can check whether they're available at ibiblio 
(http://www.ibiblio.org/maven). If not then you can override the 
versions in the project.properties files and make them point to the jars 
in the Spring lib directory.

I've started using Spring code this past couple of weeks with a client 
and things are looking pretty impressive. Congratulations on doing such 
a great job. I'm looking forward to getting time to get my head round 
what's been going on for the past year.

All the best,

Luke.


Rod Johnson wrote:
> Luke,
> 
> The Maven site is looking pretty good now! Well done. I think we should link
> to it from the home page in the not too distant future. Just a few things
> still to iron out.
> 
> A few notes:
> 
> - maybe the "about" text could come from the web site.
> - the unit test failures look like an XML parser issue. A conflict with
> Maven perhaps?
> - Thomas, what would be the best logo to use? Maybe the Jira one would work
> for top left?
> - We have a licensed copy of Clover in CVS. If you use that Jar you will get
> a nice message saying it's licensed for the Spring Framework.
> - damn, one of my most active periods for months and I still haven't caught
> up with Juergen's number of commits!
> 




-- 
  Luke Taylor.                      Monkey Machine Ltd.
  PGP Key ID: 0x57E9523C            http://www.monkeymachine.ltd.uk