On Sep 23, 2008, at 8:50 PM, bubalecka wrote:
I continuously update magnolia from svn in the latest two weeks and
try to
build without errors but I need some help to do that. I checkout svn
to
version 3.7-SNAPSHOT
So we're probably hijacking another thread here ;)
and create NetBeans project. In project properties
window I set source format to 1.6 and encoding UTF-8. But when I build
project I get error in output console like this:
ERROR org.apache.commons.digester.Digester Digester.java(error:1538)
23.09.2008 20:29:14 Parse Error at line 6 column 10: The content of
element
type "module" must match
"(name,(displayName|display-
name
)?,description
?,class
?,versionHandler
?,version,properties?,dependencies?,servlets?,repositories?)".
org.xml.sax.SAXParseException: The content of element type "module"
must
match
This says that one of the module descriptors is invalid - according to
what's below, it could only be core, but it IS valid on svn. So
there's either a modification on your local copy, or something else is
wrong.
<...>
Results :
Building jar:
E:\NBWorkspace\magnolia\magnolia-core\target\magnolia-core-3.7-
SNAPSHOT.jar
Building jar:
E:\NBWorkspace\magnolia\magnolia-core\target\magnolia-core-3.7-
SNAPSHOT-tests.jar
Preparing checkstyle:check
[WARNING] File encoding has not been set, using platform encoding
Cp1252,
i.e. build is platform dependent!
Starting audit...
Audit done.
There is a message about file encoding but I think I set source to
UTF-8
encoding.
It's a warning message and has nothing to do with the above exception.
Besides, I don't see any build failures in what you pasted.
Can some one tell me how can I resolve this and build without
errors? I use Windows XP, NetBeans 6.1
Now that I took the time to try this on my machine: one of the tests
barfs some exceptions as a side-effect. It's actually testing that
module descriptors HAVE TO be compliant to the dtd. If anything was
actually failing, the test would, well, fail, and the build wouldn't
continue.
Next time, please read the messages completely - and since you have up-
to-date sources, it should be fairly trivial to check out where
they're coming from - sometimes tests are a little verbose because we
can't always control side-effects of 3rd party libraries, for example.
I'll see what I can do about this particular one now, so you stop
panicking, but in general, if the test does not fail, if the build
doesn't fail, then why would anything be wrong?
Cheers,
-g
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
