By the way, I just nuked and checked out jboss-all from cvs. Still the same
problem:

Searching for build.xml ...
Buildfile: /home2/dean/src/jboss/jboss-all/build/build.xml

BUILD FAILED

javax.xml.parsers.FactoryConfigurationError:
org.apache.crimson.jaxp.SAXParserFactoryImpl
        at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:84)
        at
org.apache.tools.ant.ProjectHelper.getParserFactory(ProjectHelper.java:780)
        at org.apache.tools.ant.ProjectHelper.parse(ProjectHelper.java:105)
        at
org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:85)
        at org.apache.tools.ant.Main.runBuild(Main.java:439)
        at org.apache.tools.ant.Main.start(Main.java:153)
        at org.apache.tools.ant.Main.main(Main.java:176)

Total time: 3 seconds
org.apache.crimson.jaxp.SAXParserFactoryImpl

Does anyone know what the cause/fix of this is?

Inline:

> Date: Sun, 09 Sep 2001 14:20:33 +0200
> Subject: Re: [JBoss-dev] Build instructions????
> From: Peter Fagerlund <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
>
> on 1-09-09 11.47, Dean Anderson at [EMAIL PROTECTED] wrote:
>
> > Could someone post somewhere instructions on how to build jboss?
>
> What is Buildmagic
>
> Buildmagic is a collection of extension tasks for Ant v1.3/1.4
> and a general
> methodology for organization of build control files. It was designed to
> allow aggregation of one or more source modules into one logical project,
> yet still retain each modules individuality (so that the same module could
> be incorporated into another project or worked on independently of a
> project).
>
>
> *    Buildmagic User's Guide [pdf] Http://jboss.org/bm-usersguide.pdf

Well, the PDF looks nice, but it doesn't seem to work very well. Can we 86
this until it works?  This is just too fancy for its own stability.

> > Is there a stable version of the source code available via ftp?
>
> try the 2.4.0 http://jboss.org/binary.jsp --comes with source

Umm, there isn't 2.4.0 anymore --- just 2.4.0 + Jetty.

I restate the question:  Sourceforge gives you an ftp area, where you can
put all the old and new versions. Can setup the ftp with all the old and
current versions.

Rather than creating 5 different source releases, why not just create a set
of 5 different scripts that will take the components and install and build
them as necessary?  This will save a bundle on instructions, downloads, and
non-working build environments...

>
> > Should I start looking for another App server?
>
> Yes You can ... but why ? ...

Well, I'd like one that builds and runs, please. :-)

> > Whats up?
>
> The development of 3.0 is up ... alot is beeing tweeked and upgraded - in
> fact most ;-)

> This suggest the open slot for somebody to make a DASH-O and GUI config of
> stable versions ...
>
> what would You pay for that ? ...

I'd pay just as much as I pay for GCC ;-)

Actually, I'd really suggest that you not try to get too fancy. Just do the
basics. (ftp area) After the basics, then maybe something fancy.

                --Dean


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to