Well, we are using Maven, which is still in rc phase, so it can't be totally stable...
anyway, build should work with the latest maven release (rc2)... the problem reported by Matt with rc1 is probably due to the use of a version 4 POM, and I think it will be better to stick with version 3 for now (I will fix it in the next days). I also will add plugin used in POM dependencies, so dowloading of the correct version should be automatic.
Apart from this I think you should be able to run a build (maven jar / war) without problems...
Generating documentation is more complex: the website has a lot of reports which I think are very useful, but that can require a setup:
- the pdf generation requires some libraries from sun if you want images in it (it works properly but doesn't include images otherway)
- the cvs stat report at least need a working cvs checkout (a simple export will not work)
- the clover plugin is simply broken: you can run it successfully with the trial jar, but if you want to generate a report with the displaytag registered clover jar you need some workarounds and fixes. I will try to fix it and submit a patch to maven people, but actually that's the only way to make it work.
So: if we want to have everything in our site we should deal with these issues... core build steps should instead work for anyone without problems.
I think I'm the only one constantly running full builds from CVS: I can run it without problems using maven rc2 on my machine and also nighlty builds on sf compile farms seem to work flawlessy. I need feedback from other people to understand if there are errors/problems building displaytag from scratch on clean environments.
Build errors should be reported on sourceforge like any other bug and I will try to fix them or to provide help and guidelines...
fabrizio
Da: John York
Inviato: gio 22/04/2004 22.14
A: [EMAIL PROTECTED]
Oggetto: Re: [displaytag-devel] CVS Build Failure
Just a general thought, shouldn't we stick to stable versions of things if we're gonna make this available to other people? I have no objection to using maven, but if the newset version is causing so many problems for others, than maybe we shouldn't include those features until they are final. I suppose it should at least be decided by a vote within the dev group. On Thu, 22 Apr 2004, David Erickson wrote: > Tried that to no avail.. > -David > > ----- Original Message ----- > From: "Fabrizio Giustina" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, April 22, 2004 12:39 PM > Subject: RE: [displaytag-devel] CVS Build Failure > > > Get the latest version of the maven xdoc plugin and it should work > > fabrizio > > ________________________________________ > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of David > Erickson > Sent: marted́ 20 aprile 2004 0.16 > To: [EMAIL PROTECTED] > Subject: Re: [displaytag-devel] CVS Build Failure > > Ok got it to work minus the xhtml reports, here's some of the log + > stacktrace: >
