hi kenneth

please disregard my previous response.
actually the pom.xml contained outdated
dependencies.

that should be fixed at revision 720447.
regards
angela


[INFO] Error building POM (may not be this project's POM).


Project ID: org.apache.jackrabbit:jackrabbit-test-client
POM Location: /home/yue/jackrabbit/sandbox/spi/client/pom.xml
Validation Messages:

[0] 'dependencies.dependency.version' is missing for org.apache.jackrabbit:jackrabbit-spi2jcr


Reason: Failed to validate POM for project org.apache.jackrabbit:jackrabbit-test-client at /home/yue/jackrabbit/sandbox/spi/client/pom.xml


[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for project org.apache.jackrabbit:jackrabbit-test-client at /home/yue/jackrabbit/sandbox/spi/client/pom.xml
        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
        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:585)
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) Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to validate POM for project org.apache.jackrabbit:jackrabbit-test-client at /home/yue/jackrabbit/sandbox/spi/client/pom.xml at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1108) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:878) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
        at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534)
        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
        ... 11 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 seconds
[INFO] Finished at: Fri Nov 21 15:39:40 PST 2008
[INFO] Final Memory: 3M/249M
[INFO] ------------------------------------------------------------------------

Angela, I'll really appreciate if you have the working bits and just kindly send them my way (email, put them on a FTP server, or whatever) if you don't feel they're stable enough to commit. I urgently need them to continue my development. Oh, by the way, throw in the RepositoryFactory while you're at it so I don't have to read the test code to figure out how to use those classes. Thanks.

Ken

if, however, you think the spi2dav sandbox project
should be put into a common release cycle, feel free to
open an jira issue for that.

Will do.

I saw that too, but I don't want "to test the WebDAV remoting" as mentioned in the README; I want to use it.

fair enough. but currently it is in the sandbox, there
is not automated testing installed and i can't promise
you that everything works smoothly.

That's fine. I'm not doing anything fancy, just simply reading and writing attributes and node data (no versioning, no locking). As long as the basic functionality works, I don't mind the code having some bugs here and there.

if you can live with that, feel free to use it.
bug reports and requests for improvement are welcome.

[...] The ideal solution would be like org.apache.jackrabbit.rmi.client.ClientRepositoryFactory where I just configure it in my context.xml with the URL it needs and my code to lookup up the Repository object from JNDI doesn't need to change. Does such RepositoryFactory exist?

at Day we are having a RepositoryFactory to obtain a jcr2spi
Repository based on an extended version of the webdav
remoting.

i can put a similar factory for spi2dav to the sandbox,
if you want me to. up to now this simply didn't have too
much priority.

YES, PLEASE, ASAP! As I said above, it doesn't have to be perfectly stable/robust, as long as the basic best-case scenario works.

hope that helps

Definitely.  Thanks again for your time.

Ken



Reply via email to