Vadim Gritsenko schrieb:
On Nov 4, 2008, at 3:13 PM, Steven Dolg wrote:
Hi Vadim,
the port stated in the README is unfortunately wrong.
However the demo is working correctly for me
After a bit of poking around I figured out it was caused by a firefox
cache (it cached a redirect). After clearing the cache I can see
"Cocoon 3 Samples and Integration Tests: Overview" page.
as well as the generated project for IDEA (I tried IDEA 7.0.4 with a
JDK 1.6.0_06).
It is not possible to generate a project file from cocoon-3 root
directory itself, and so the next closest thing which I found is to do
it in the ./parent directory. So, when running mvn idea:idea command
there, it creates incorrect cocoon-parent.ipr file:
<modules>
<!-- module filepath="$$PROJECT_DIR$$/${pom.artifactId}.iml"/ -->
<module filepath="$PROJECT_DIR$/cocoon-parent.iml"/>
<module
filepath="$PROJECT_DIR$//Users/vgritsenko/Projects/Apache/cocoon-3/cocoon-all/cocoon-all.iml"/>
<module
filepath="$PROJECT_DIR$//Users/vgritsenko/Projects/Apache/cocoon-3/cocoon-controller/cocoon-controller.iml"/>
So it seems like idea plugin appends absolute file paths to the
$PROJECT_DIR$. I had to manually edit file so that it loads in IDEA.
It now reads:
<modules>
<!-- module filepath="$$PROJECT_DIR$$/${pom.artifactId}.iml"/ -->
<module filepath="$PROJECT_DIR$/cocoon-parent.iml"/>
<module filepath="$PROJECT_DIR$/../cocoon-all/cocoon-all.iml"/>
<module
filepath="$PROJECT_DIR$/../cocoon-controller/cocoon-controller.iml"/>
Short of hacking maven plugin, I think easiest way to fix that would
be to add a pom to cocoon-3 directory. WDYT?
That is strange.
When I generate the IDEA project files from the parent directory I get
the following modules section:
<component name="ProjectModuleManager">
<modules>
<!-- module filepath="$$PROJECT_DIR$$/${pom.artifactId}.iml"/ -->
<module filepath="$PROJECT_DIR$/cocoon-parent.iml"/>
<module filepath="$PROJECT_DIR$/../cocoon-all/cocoon-all.iml"/>
<module
filepath="$PROJECT_DIR$/../cocoon-controller/cocoon-controller.iml"/>
<module
filepath="$PROJECT_DIR$/../cocoon-optional/cocoon-optional.iml"/>
<module
filepath="$PROJECT_DIR$/../cocoon-pipeline/cocoon-pipeline.iml"/>
<module filepath="$PROJECT_DIR$/../cocoon-rest/cocoon-rest.iml"/>
<module filepath="$PROJECT_DIR$/../cocoon-sample/cocoon-sample.iml"/>
<module
filepath="$PROJECT_DIR$/../cocoon-servlet/cocoon-servlet.iml"/>
<module
filepath="$PROJECT_DIR$/../cocoon-sitemap/cocoon-sitemap.iml"/>
<module
filepath="$PROJECT_DIR$/../cocoon-stringtemplate/cocoon-stringtemplate.iml"/>
</modules>
</component>
After opening IDEA changes all that into absolute paths - but I guess
this is all right (I have absolutely no experience with IDEA).
So the only thing I can image are different Maven and/or different
idea-plugin versions.
Mine are Maven 2.0.9 and maven-idea-plugin 2.2.
If everything fails moving the pom might be an option. Would that
produce a valid project file with your setup?
Steven
Could you provide me with more specific error messages - if available
- in order to sort this out?
Hope above helps,
Thanks,
Vadim
Steven
Vadim Gritsenko schrieb:
Hi All,
Trying out cocoon 3 trunk, found following issues:
* Demo starts on port 8888, not the 8190 as stated in README;
* Demo's not working. http://localhost:8888/ results in error:
404 Resource Not Available (Cocoon 3 Integration Tests)
* Project generated by mvn idea:idea is not correct - paths to
modules is incorrect
Any ideas how to get a working sample?
Vadim
