Re: Need some help with Maven
Re: Need some help with Maven
- Subject: Re: Need some help with Maven
- From: G Brown <email@hidden>
- Date: Mon, 24 Sep 2012 17:11:21 -0400
On Sep 24, 2012, at 4:20 PM, Jean-François Veillette 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.
> 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.
>
I have found you must close your framework, and install the framework into your local repo. I think wolips needs a little update.
From a prior email:
> Could there be a "preference" that tells wolips to not step on my classpath and add things to it I don't want and there is no way to get rid of?
>
> If you have something like ERExperimental and there is another version of ERExperimental that you want, you have to close the ERExperimental project, or delete it from the workspace, or switch workspaces--just to get the correct version on the classpath.
>
> This is also a problem with maven, as it wants to setup the classpath as well.
Henrique said:
You can disable workspace resolution for Maven projects using the m2e plugin. Just right click the project then Maven > Disable Workspace Resolution.
Cheers,
Henrique
But that did not work on at least an older version of eclipse/wolips; I had to close the framework to get my eomodel.
> 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,
>
> --
> jfv
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
Mr. G Brown
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden