On 29 Apr 2016, at 12:10 am, Hugi Thordarson wrote:
> Now… Framework Properties seem to work fine for me. I just verified that by
> creating a Properties file in one of my frameworks with a property, deploying
> a dependent app and checking the property’s value. Worked fine. Overrode the
> sam
Hi Hugi,
On 29 Apr 2016, at 12:10 am, Hugi Thordarson wrote:
>> Can I just clarify this issue with Properties by asking a few specific
>> questions?
>>
>> 1. I take it that the usual Properties precedence works as designed for
>> Properties in the application bundle—there are no surprises her
> Just resurrecting a thread from seven months ago as I finally bite the Maven
> bullet and attempt to get my own HelloWorld off the ground…
https://www.youtube.com/watch?v=bBXyB7niEc0&t=10
Welcome! I finally bit the bullet last month and migrated most of my projects
to Maven. Took some patienc
Hello,
Just resurrecting a thread from seven months ago as I finally bite the Maven
bullet and attempt to get my own HelloWorld off the ground…
On 18 Sep 2015, at 7:58 am, Ramsey Gurley wrote:
> So I need to copy all the properties from all the frameworks into my app’s
> properties file? And
Pascal is probably the better person for this question. I don’t use ERRest at
all.
On Dec 8, 2015, at 11:11 AM, jazzsalsa wrote:
> Hi Ramsey,
>
> It is working now! I started with a ERRest template (without maven) and fixed
> the build path settings by using local Wonder libraries.
>
> Thank
Hi Ramsey,
It is working now! I started with a ERRest template (without maven) and
fixed the build path settings by using local Wonder libraries.
Thanks for the pointers :)
Now I want to change the output format of the REST service. Using
Pascal's tutorial [1] I get this JSON output:
[{"id":1,"typ
From H2Plugin/Resources/Properties, did you add uncommented lines like
# H2 connection URL
dbConnectURLGLOBAL=jdbc:h2:file://tmp/Example
# Because H2 doesn't have deferred fk constraints
com.webobjects.eoaccess.ERXEntityDependencyOrderingDelegate.active=true
to your project properties and set th
Next question (postgresql works now when using traditional framework.
https://wiki.wocommunity.org/display/WEB/Your+First+Rest+Project
The migration does not work. I created BlogModel0 in src/main/java
there is no Sources folder with maven):
In the Sources folder, open the your.app.model.migrati
Hi list,
Everything works fine now! I am working through this tutorial [1], but
I am stuck in EOModel because I cannot select the H2Plugin.
I added this dependancy to the pom.xml, but it cannot find it:
wonder.plugins
H2Plugin
I run the application in Eclipse the same as I always did. Right-click
Application.java, Run as->WOApplication.
On Nov 30, 2015, at 1:26 PM, jazzsalsa wrote:
> Great! Thanks Ramsey, that works perfect.
>
> mvn clean package and mvn clean install work.
>
> How do I run the WOApplication in ecl
Great! Thanks Ramsey, that works perfect.
mvn clean package and mvn clean install work.
How do I run the WOApplication in eclipse now?
mvn clean jetty:run-war does not work
Regards, Bart
On Mon, 2015-11-30 at 10:35 -0700, Ramsey Gurley wrote:
> Try with
>
> -DarchetypeVersion=2.2-SNAPSHOT
>
Try with
-DarchetypeVersion=2.2-SNAPSHOT
In fact, do this:
Install m2e in eclipse if you haven’t already
Go to eclipse preferences, Maven->Archetypes, click “Add Remote Catalog...”
button and add
Catalog File:
http://maven.wocommunity.org/service/local/repositories/snapshots/content/archetyp
Hi Ramsey, Henrique,
Thanks for fixing how hard is was to work with Maven. Much easier now,
but not quite there yet.
I followed this page and looked at the email thread on the list around
18-Sep-15: https://wiki.wocommunity.org/display/WOL/Quick+Start
This works (step 4): mvn archetype:generate
On Sep 28, 2015, at 11:29 AM, Ramsey Gurley wrote:
> Now that I’ve gotten a hello world to run, the next step would be to convert
> existing projects to use maven. It looks like I need to rearrange the project
> layout. Is there any sort of tool to convert a fluffy bunny to a maven
> project?
Now that I’ve gotten a hello world to run, the next step would be to convert
existing projects to use maven. It looks like I need to rearrange the project
layout. Is there any sort of tool to convert a fluffy bunny to a maven project?
Also, unit testing? Is WOUnit the recommended way to go here?
On Friday, September 18, 2015, Ramsey Gurley
wrote:
> So the reason it doesn’t find the main component: It looks like I’m
> getting a NSFluffyBunnyProjectBundle instead of NSMavenProjectBundle.
>
> NSStandardProjectBundle$Factory expects to find
>
> "org.maven.ide.eclipse.maven2Nature".equals(nat
So the reason it doesn’t find the main component: It looks like I’m getting a
NSFluffyBunnyProjectBundle instead of NSMavenProjectBundle.
NSStandardProjectBundle$Factory expects to find
"org.maven.ide.eclipse.maven2Nature".equals(nature)
in the .project natures but my .project has org.eclipse.
>> Did you find out how to solve the problem of the application not looking for
>> templates at the correct path?
>
> Not yet. I think I need to remove all the wonder stuff from my workspace and
> import it again as Maven projects. Right now they don’t have the little M
> beside them and I susp
On Sep 18, 2015, at 11:12 AM, Fabian Peters 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 warn
In this case, I’m starting with a maven project by creating it with the
erxapplication archetype in eclipse. This is the result I’m getting. I should
try again from the command line to see if that makes a difference.
I tried doing exactly this with ERExtensions and ERPrototypes, and it works. I
> 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 ex
Hi Ramsey,
>> Did you find out how to solve the problem of the application not looking for
>> templates at the correct path?
>
> Not yet. I think I need to remove all the wonder stuff from my workspace and
> import it again as Maven projects. Right now they don’t have the little M
> beside the
On Sep 18, 2015, at 3:22 AM, Hugi Thordarson wrote:
> Did you find out how to solve the problem of the application not looking for
> templates at the correct path?
Not yet. I think I need to remove all the wonder stuff from my workspace and
import it again as Maven projects. Right now they do
If you
cd ?../Frameworks then
find . -name Properties -exec cat {} \; >>SuperProperties
you should have all the framework properties in the SuperProperties file,
bypassing any Properties issues with jar vs file frameworks.
Also, you may want to use JarResourceRequestHandler to get resources
Did you find out how to solve the problem of the application not looking for
templates at the correct path?
Thanks, btw, for starting the discussion and thanks to Henrique for the work on
the software. This is proving immensely useful and I swear, I’m going to
complete my migration to Maven thi
Strike the second part of that question. deployment would be war, and those are
exploded out, so it presumably would work there.
On Sep 17, 2015, at 3:28 PM, Ramsey Gurley wrote:
> So I need to copy all the properties from all the frameworks into my app’s
> properties file? And in production,
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?
Also, I’ve got 'Resolve dependencies from workspace projects’ checked in my
project’s maven pro
> I also get quite a lot of these properties warnings in the console:
>
> Sep 17 11:24:16 helloworld[50191] WARN
> er.extensions.foundation.ERXFileUtilities - Can't get path when run as jar:
> JavaFoundation - Properties
> Sep 17 11:24:16 helloworld[50191] WARN
> er.extensions.foundation.ER
Hi Henrique,
Thanks for making these updates! It looked like the maven stuff needed some
love, and I’m not quite a maven plugin development wizard just yet.
Some progress here. I added the remote archetypes, and created a new maven
project with eclipse. I no longer get any red errors in the pom
@Ramsey,
I don't want to shock you but the documentation is out of date!
At one time one could create maven projects using eclipse, but that stopped
working. The way I now initialize a maven project is using the command line.
That always seems to work. Perhaps I can go over the documentation bu
Ramsey,
The last change to WebObjects Maven plugins were back in 2010. Lots of things
changed since then in Maven tooling world. I took the time during the weekend
to make the Maven plugin and the Maven archetypes compatible with the current
features. I still have to make a release and update t
Hi Ramsey,
First, it seems you're using an old version specification for the wolifecycle
plugin, the current being "[2.2.1,)".
The error messages only concern the m2e plugin, not the "real" maven build. The
plugin has to be told to ignore the woapplication goal of the wolifecycle
plugin. If y
As to the why it was not working, I believe it was because of the
“wonder.classifier” defined in the pom.xml, whose value was set to wo54. That
classifier was used to identify different instances of the same dependency, one
for WO 5.4 and another for WO 5.3. But I think that classifier is a hold
I just tried generating a hello world app using the Quick Start guide and I had
to make a couple of changes to the generated POM to get it work:
- In the plugins section, I changed the version of the wolifecycle
plugin to 2.1 (I use 2.2.1 for my projects, but 2.1 it seems to work).
The sad thing is, Maven itself seems fairly intuitive. I’ve got it running in
eclipse, I’ve downloaded 15000 archetypes from the apache server. Everything
seems to work very nicely. Trying to get a WOApp running is the problem.
On Sep 11, 2015, at 3:32 PM, T Worman wrote:
> I have nothing subs
I have nothing substantive to offer - other than thank you for reminding me why
I won’t try this.
You’re brave.
Tim
UCLA GSE&IS
> On Sep 11, 2015, at 2:19 PM, Ramsey Gurley wrote:
>
> So I really desperately want to migrate my projects to Maven. I tried back in
> May when I had a chance, and
36 matches
Mail list logo
