Re: WO Maven getting started
Re: WO Maven getting started
- Subject: Re: WO Maven getting started
- From: Ramsey Gurley <email@hidden>
- Date: Fri, 18 Sep 2015 12:02:25 -0700
On Sep 18, 2015, at 11:12 AM, Fabian Peters <email@hidden> wrote:
>> So I need to copy all the properties from all the frameworks into my app’s properties file? And in production, if I compile to a jar, I then need to list all the properties as command line arguments?
>
> I've been ignoring those warnings for years now. Everything seems to work as one would expect…
Interesting. Perhaps these properties files only contain commented properties as examples? I know there is at least a one framework (ERPersistentSessionStorage) where the properties file is quite important.
>
>> Also, I’ve got 'Resolve dependencies from workspace projects’ checked in my project’s maven properties, but if I set a breakpoint in this class, it’s looking for the class in the m2 repository. Is there some other thing I need to do to make the application use the ERExtensions in my workspace?
>
> That's the one thing that I find a bit annoying. To get the debugger to find the source files: <https://wiki.wocommunity.org/display/documentation/Maven+Running+or+Debugging+as+WO+Application> From my experience, you only have to do this for dependencies, not the application itself.
I was reviewing my old email and saw that you answered this question for me once already. Thanks for both times :D
It didn’t work right away, and I’ve just figured out why. My application pom was wonder.version 6.1.3, but my workspace version on ERExtensions was 6.2-SNAPSHOT. So I needed to update my application pom and add the folders as suggested.
Now that I’ve done that, it stopped at the breakpoint. So if I switch branches, I’ll need to update the wonder.version in all my application pom.xml files?
_______________________________________________
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