Hi Christian, All Eclipse files for the modules that people normally care to have in Eclipse are checked in to SVN, so just importing the modules should be ok. You prolly don't need the docs module in Eclipse. There's no code in there.
Now the unpublished thing... We are trying to hide some internal modularity from the end users for simplicity sake. And we are going against Maven normal practices in doing that. So when building from command line, we aggregate a bunch of unpublished modules in cayenne-server and cayenne-client aggregate modules (aggregating their transitive deps as well). And that's what the end users should include in their POMs. All the "ext" modules are for building CayenneModeler on different platforms (Mac, Windows, Generic). Some of them are platform dependent (e.g. depend on jars that only exist in OS X; or on an OS-specific windowing system). So with the above in mind, what are you planning to do with Cayenne in Eclipse? Very likely you just need a smaller subset of modules. Andrus On Apr 12, 2011, at 4:12 PM, Christian Grobmeier wrote: > Hello guys, > > I am back :-) and would like to include the trunk version of Cayenne > in my project. No worries, I will use a stable version when it goes to > production. But I hope to learn more about Cayenne itself when I use > the direct source. Probably I can do a few patches. > > However, i have checked out the source and tried "mvn > eclipse:eclipse". It failed at the project: > "Cayenne License and Notice Bundle ." > > The i runned mvn install and redid mvn eclipse:eclipse > > This time it worked well, except this: > "[INFO] Cayenne Tutorials ................................. SUCCESS [0.005s] > [INFO] Cayenne Documentation ............................. FAILURE [12.603s] > [INFO] Cayenne Documenation Parent ....................... SKIPPED" > > The errormessage is: > "[ERROR] Failed to execute goal > org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse > (default-cli) on project cayenne-doc: Request to merge when > 'filtering' is not identical. Original=resource src/main/resources: > output=target/classes, include=[], exclude=[doc/index.html|**/*.java], > test=false, filtering=false, merging with=resource src/main/resources: > output=target/classes, include=[doc/index.html], exclude=[**/*.java], > test=false, filtering=true -> [Help 1]" > > In my understanding mvn eclipse should work without mvn install. And > of course mvn eclipse should run through documentation projects too. > Right? > > > Then I imported everything to Eclipse. At least everything except the > documentation project. > > There are a few compilation failures b/c of dependencies. > > For example: > cayenne-modeler-mac-ext seems to depend on cayenne-di-unpublished. > > I was wondering about that project. Why is it named "unpublished"? Is > it some kind of experimental trunk? > And why is it in scope "provided"? If its not there, there is a > compilation failure- for me this calls for a compile time scope. Maybe > you can explain briefly. I would like to avoid to manually set the > eclipse classpath. > > Cheers > Christian >
