Apple

Perhaps that page needs more promotion, or is hard to find?

I thought I read all the maven related pages, but I have to admit that I didn't read that one.

I'll follow all your good advices when I can get back to our maven conversion project ... and I'll keep asking you questions ! :-)

Thanks,

jfv

It's also worth having a look at the archetypes available for WOMaven to see how they're set up.

From an email I sent to the list in January 2012 titled "Re: Using Maven".
-----------------------
I've attached a working pom.xml (which should work with wolips for eclipse 3.7 and latest wonder), an Application.java that works and Henrique's JarResourceRequestHandler. See if that helps...

On 25/09/2012, at 6:20 AM, Jean-François Veillette <email@hidden> wrote:

I need some help to debug maven issues from inside Eclipse [*a*].
I converted some existing (and working) projects, both frameworks and applications.

1- When I run the application, I now (after the switch to maven) need to explicitely set the class to be used as Session and some components [*b*], things that I didn't need before.

I think that's true. This is largely to do with classpath ordering, so it's best to do it as you've done below - but use ERXPatcher instead which is a public API.

2- Then later on, at runtime while navigating the app, It cannot find a model (defined in a framework) for a given class entity (cannot find model associated with entity named: "MyEntity") and fail to fetch.

Ensure all your frameworks are loaded into your workspace.

You'll also want to make use of the JarResourceRequestHandler.

Both of these problems point to the direction of the bundle (NSBundle), the ressource manager (NSResourceManager), or something related (maven build, classpath, .jar resource loading).
Any help / clues that help me debug this situation will be greatly appreciated!
Any other comments will be seen as at least some very basic interest in maven ;-)

*a* -- which mean that I don't know if it's an Eclipse classpath m2eclipse issue since I have not yet tried to deploy and see if the .woa generated from mvn will experience the same problem.
*b* -- _NSUtilities.setClassForName(Main.class, Main.class.getSimpleName());
_NSUtilities.setClassForName(Session.class, Session.class.getSimpleName());
_NSUtilities.setClassForName(DirectAction.class, DirectAction.class.getSimpleName());

Thanks,

References:
	>Need some help with Maven (From: Jean-François Veillette <email@hidden>)