If it is yaafi that you want to release then configure at as 1.0.5, make sure that any changes are documented (I know there is the changes.xml page, but you also need release notes including details of how to migrate from 1.0.4) and make the jar available somewhere so that we can test it. When you think you have it right you can call for a vote based on the site and jar.

I have just started building the new turbine.apache.org site - since this is not announced yet there is probably no problem in this case deploying the fulcrum site directly to there (someone else will have to do it if you don't).

Thomas: No hurry at all, and I feel a little slack pushing this over to you all the time, but would you mind code wrestling turbine-site (no big deal really since it is never actually released). turbine-2 trunk also needs to be done at some point in time.

Scott

Siegfried Goeschl wrote:
Hi folks,

I generated & uploaded a new site

1) svn developer activity is broken

2) is there any URL to show a HTML diff from the changelog report similiar to VIEWCV

3) we have to align the dependencies - see http://people.apache.org/~sgoeschl/fulcrum/docs/dependency-convergence-report.html

4) the Dashboard report is not correct because some coverage results are missing (yaffi, cache)

Cheers,

Siegfried Goeschl


Siegfried Goeschl wrote:
Hi Thomas,

1) I just got the SVN change reports running - it also helps to install the right svn client on a Mac .... :-(

2) out of my head the "security/turbine" stuff but I'm rerunning the site generation with the maven-cobertura-plugin

Cheers,

Siegfried Goeschl


Thomas Vandahl wrote:
Siegfried Goeschl wrote:
Hi folks,

I was finally able to make a complete site build of Fulcrum to be found at http://people.apache.org/~sgoeschl/fulcrum/docs/

1) the SCM changelogs are not working so I have to investigate that

Could you check out if

maven.changelog.factory = org.apache.maven.svnlib.SvnChangeLogFactory

helps?

2) Generating the code coverage reports break tests - not sure if this is caused by maven-jcoverage plugin or be running the tests twice. TV pointed out that JCoverage is broken for JDK 1.5 so I have a look at Cobertura to see if it is better

Which tests are affected?

PS: Thanks to Thomas The Vandal for nailing down my build problems

I'm ready to demolish Karthago again anytime...

Bye, Thomas.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to