*sigh* is right. I started to look at updating the download page to include 3.0rc1 but couldn't see if I broke anything due to (at least) this problem. (with jboss-website, not website)
I'll see if I can remove some of the crap from the this. There's no reason we should be putting obsolete versions of Sun's jca examples on our website, aside from there being no reason they should be getting deployed. In principle, should the website build deploy without changes on jboss 3.0rc1? And 3.1 alpha? If so, at least some of us could do frequent integration testing. What is the production website run on? And if it deploys on my local jboss where would I find the jboss main page? Thanks Hoping we can have just one website in cvs soon... david jencks On 2002.04.22 03:16:52 -0400 Jason Dillon wrote: > Once again I tried to start working on the new website... but I have run > into another problem. Looks like we are trying to deploy some files > under doco_files/ which are failing. Which is good to know, since those > doco files need to be updated or removed, but why is MD trying to deploy > them in the first place? > > I don't recall this happening a few days ago either... > > Also note at the end of this trace some componet is printing the trace to > System.err instead of logging. What is going on? I think we had removed > this usage of System.our & err as well as Throwable.printStackTrace(). > > *sigh* > <snip> _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
