> -----Original Message-----
> From: Daniel Kulp [mailto:[email protected]]
> Sent: Thursday, July 22, 2010 18:38
> To: Gary Gregory
> Cc: [email protected]
> Subject: Re: CXF, Eclipse and Maven
> 
> 
> Try one of:
> 
> mvn process-test-sources eclipse:eclipse
> 
> or
> 
> mvn -Psetup.eclipse
> 
> Basically, by default, eclipse:eclipse only runs to the process sources phase
> and thus would not get the stuff generated after that (which included
> generated test code).
> 
> See:
> http://cxf.apache.org/setting-up-eclipse.html
> 
> Dan

Thank you Dan. I ran both commands which eventually resolved all Eclipse 
compile issues. 

I am not sure that all .classpath files were regenerated though, based on my 
quick inspection of one .classpath file timestamps. Maybe my manual changes are 
still in place.

Since doing this pass is slow, I'd rather not do it just for fun.

Does anyone know if these commands overwrite existing .classpath files?

Thank you,

Gary 

> 
> 
> On Thursday 22 July 2010 9:31:04 pm Gary Gregory wrote:
> > Hello All,
> >
> > I updated 2.2.x from SVN and re-ran 'mvn eclipse:eclipse' which I had only
> > done once when I first imported CXF into Eclipse. Some generated Eclipse
> > .classpath files are missing some entries.
> >
> > Could this be a pom.xml issue as opposed to Maven plugin issue?
> >
> > For example, in cxf-api, this classpathentry is missing:
> >
> >   <classpathentry kind="src" path="target/generated/src/test/java"
> > including="**/*.java"/>
> >
> >
> > Problems like this shows up in:
> >
> > - cxf-api
> > - cxf-rt-bindings-http
> > - cxf-rt-databinding-jaxb
> > - cxf-rt-databinding-xmlbeans
> > - cxf-rt-javascript
> > - cxf-systests-uncategorized
> > - cxf-tools-java2ws
> >
> > I fixed those by hand by adding to the .classpath:
> >
> >   <classpathentry kind="src" path="target/generated/src/test/java"
> > including="**/*.java"/>
> >
> > cxf-systests-databinding was fixed by adding:
> >
> >   <classpathentry kind="src" path="src/test/generated"
> > output="target/test-classes"/>
> >
> >
> > And problems remain in:
> >
> > - cxf-systests-codegen
> > - cxf-systests-ws-specs
> >
> > Thoughts?
> >
> > Gary Gregory
> > Senior Software Engineer
> > Seagull Software
> > email: [email protected]
> > email: [email protected]
> > www.seagullsoftware.com
> 
> --
> Daniel Kulp
> [email protected]
> http://dankulp.com/blog

Reply via email to