Hi Lars,
I believe it is not a WOLips problem.
What <package> have you configured in your pom.xml for this project? Are
you using woapplication or woframework? If so, try to change the package
to jar and try to activate q4e. It should work.
By the way, what features do you like/unlike in q4e over m2eclipse? Why
have you switched? Which versions are you using/have you used of both
tools? I really appreciate if you could share your opinion with us.
Cheers,
Henrique
PS: I'm not a q4e user. But I had similar problems in the past with
m2eclipse.
Lars Sonchocky-Helldorf wrote:
> WOLips and Q4E/IAM are those made for each other?
>
> http://code.google.com/p/q4e/
> http://www.eclipse.org/iam/
> http://www.eclipse.org/projects/project_summary.php?projectid=technology.iam
>
>
> I used the m2e maven plug before but "converted" to Q4E/IAM some time
> ago (had to work with those in some non-WO projects) and like Q4E/IAM
> better than m2e since then. Now I tried if I can use Q4E/IAM with WOLips
> too. For that purpose I manually removed the following lines from the
> .project files:
>
> <buildCommand>
> <name>org.maven.ide.eclipse.maven2Builder</name>
> <arguments>
> </arguments>
> </buildCommand>
>
> and
>
> <nature>org.maven.ide.eclipse.maven2Nature</nature>
>
>
> and the following line from the .classpath files:
>
> <classpathentry kind="con"
> path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
>
>
> Now I enabled the Q4E/IAM plug in for those projects (right click onto
> the projects):
>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
>
>
>
> now the .project file was changed as expected:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <projectDescription>
> <name>MessagingDirector</name>
> <comment></comment>
> <projects>
> <project>MDCommons</project>
> <project>WOUnitTest</project>
> </projects>
> <buildSpec>
> <buildCommand>
> <name>org.eclipse.jdt.core.javabuilder</name>
> <arguments>
> </arguments>
> </buildCommand>
> <buildCommand>
> <name>org.objectstyle.wolips.incrementalbuilder</name>
> <arguments>
> </arguments>
> </buildCommand>
> <buildCommand>
>
> <name>org.devzuz.q.maven.jdt.core.mavenIncrementalBuilder</name>
> <arguments>
> </arguments>
> </buildCommand>
> </buildSpec>
> <natures>
> <nature>org.objectstyle.wolips.incrementalframeworknature</nature>
> <nature>org.eclipse.jdt.core.javanature</nature>
> <nature>org.devzuz.q.maven.jdt.core.mavenNature</nature>
> </natures>
> </projectDescription>
>
> but the .classpath file looked like this afterwards:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <classpath>
> <classpathentry kind="src" path="src/main/java"/>
> <classpathentry kind="src" path="src/test/java"/>
> <classpathentry kind="con"
> path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> <classpathentry kind="output" path="bin"/>
> </classpath>
>
> it was missing the following line:
>
> <classpathentry kind="con"
> path="org.devzuz.q.maven.jdt.core.mavenClasspathContainer"/>
>
> which resulted in the maven dependencies not being there:
>
>
>
> ------------------------------------------------------------------------
>
>
>
> after adding the above line manually (I just copied it from some other
> mavenized (non-WO) project) all the maven dependencies are here:
>
>
> ------------------------------------------------------------------------
>
>
>
> and everything works.
>
> Now I am asking me whose fault this is. Usually the .classpath file gets
> changed properly when I am enabling Q4E/IAM for a non-WO java project.
> So who has to fix it? WOLips or Q4E/IAM?
>
>
>
> Thanks,
>
> Lars
>
>
This archive was generated by hypermail 2.0.0 : Wed Mar 04 2009 - 19:50:00 EST