My suggestion:
1. close eclipse
2. rm -R target
3. mkdir target
4. start eclipse
5. project -> clean
6. make sure project -> build automatically is checked
7. you should not see any errors
8. run find target -name "*.class"
You should then see all the class files in the target dir. If you
have pointed the RCL to that target dir everything should work like
charm.
If not check the project settings on the source tab for the output
dir.
OK I'll give it a shot.
As you suggested, it might be that my eclipse setup is wrong.
There is no question it is ;)
I expect the eclipse 'build' command doesn't know where
the target directory is supposed to be.
I have looked at the 'Run dialog' which is to 'create, manage, and
run configurations' but I am rather overwhelmed by it.
Have you used Eclipse before at all? Also please re-read my instructions
"If not check the project settings on the source tab for the output
dir."
It must be compiling _somewhere_ for goodness sake, because it will
produce the .jar package under target, and install it
in my local maven repository.
No, Eclipse will not do that. Maven will.
So far, none of my variations have worked with RCL: import as an
'existing project'; import as a 'maven project'; create
as a maven project within eclipse. I think they have all worked
otherwise.
As mentioned previously, Eclipse Navigator does not see the *.class
files even after a refresh or a brand new import, when
I know they are there. It also does not see the .classpath
and .project files. Is this bad?
Ken, I am sorry but my patience is running out here. These are all
very basic Eclipse questions - not Cocoon ones.
Please follow the instructions above. They should get you there. If
you can't get your Eclipse setup to work properly I suggest to check
with the Eclipse community or just ask a fellow developer. Good luck!
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
