Hi Gregory,
I'm completely agree with this idea, I will help by reporting all bugs
that I see and by correcting them if I can.
But I would have a request, could you please try to do a clean install
with jsdk 1.4.2 by deleting your M2 repository, checking out the dms
branch 3.0 and try an mvn clean install on the dms module.
I already tried it but apparently it fails to compile because the
DOMError class is not found, see the stack bleow:
Would you have any idea?
Thanks,
CAPITAINE Harold
(windows XP, jsdk 1.4.2.12, tomcat 5.0, elicpse WTP 3.2)
[INFO] Tracejava.lang.NoClassDefFoundError: org/w3c/dom/DOMError
at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source)
at
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown
Source)
at
org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:92)
at
org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:132)
at
org.apache.jasper.compiler.TldLocationsCache.getUriFromTld(TldLocationsCache.java:465)
at
org.apache.jasper.compiler.TldLocationsCache.scanJar(TldLocationsCache.java:372)
at
org.apache.jasper.compiler.TldLocationsCache.scanJars(TldLocationsCache.java:517)
at
org.apache.jasper.compiler.TldLocationsCache.init(TldLocationsCache.java:249)
at
org.apache.jasper.compiler.TldLocationsCache.getLocation(TldLocationsCache.java:224)
at
org.apache.jasper.JspCompilationContext.getTldLocation(JspCompilationContext.java:526)
at
org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:422)
at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:492)
at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1552)
at org.apache.jasper.compiler.Parser.parse(Parser.java:126)
at
org.apache.jasper.compiler.ParserController.doParse(ParserController.java:211)
at
org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)
at
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:155)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)
at org.apache.jasper.JspC.processFile(JspC.java:986)
at org.apache.jasper.JspC.execute(JspC.java:1135)
at
org.codehaus.mojo.jspc.AbstractJspcMojo.execute(AbstractJspcMojo.java:247)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Grégory Joseph a écrit :
Hi Harold,
All community modules are available under:
http://svn.magnolia.info/svn/modules/community/
At the moment only dms and scheduler are actually ported to Magnolia 3.
(The idea behind having the modules in a separate is that we're hoping
to get more contributions abord - potentially with different sets of
developers)
Cheers
g
On Feb 22, 2007, at 09:57 , Harold CAPITAINE wrote:
Hi list,
I'm currently trying to launch magnolia branch 3.0. I don't even want
to include the dms, first question is it possible to do so?
So I did a checkout from the branch and I did mvn eclipse:eclipse
-Dwtpversion=1.0.
Two messages appeared:
- The first one concerning the jcr but I know how to solve this one.
- The second one concerns the dms: it tells me that
dms.1.1.1-SNAPSHOT.jar can't be retrieved but I didn't mentioned that
I wanted to include the DMS module so why is automatically included?
And even if I need the dms module where this jar?
Thanks a lot for your answers.
CAPITAINE Harold
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
