So our pom's, web.xml's and build.properties both look good. I'm
curious if you have the same issue when deploying your resulting war.
I noticed you're also using 2.0.17; I'm using 16. What about the other
properties files? Any idea why they're not getting bundled in? I'm not
getting anything under WEB-INF that I'd expect, including the app.woa,
which would normally contain the contents and resources stuff; all I'm
seeing is a lib directory LICENSE, classes (file) and web.xml. Nothing
from the resources directory under src/main/resources is included
either. Can anybody confirm that they're able to build a useable war
using the new plug in? Thanks
included from my earlier reply as I'd incorrectly stated I was using
the original woapplication-archetype plug in. These are two different
plug ins, correct?
Sorry, I incorrectly referred to the woapplication-archetype; I'm
actually using the newer maven-wolifecycle-plugin. To restate the
essence of the original question, I'm trying to determine how
properties possibly required by maven or one of the plugs ins should
be set as I'm having one problem with getting the app to resolve to
the proper jar within the built war. And another issue is that none
of the original Properties files, containing stuff required by
Wonder and a whole lot more, are now included in the war built by
maven. I would think this is something simple and obvious... please
please tell me that's the case;-) So, anybody know how we're
supposed to make this happen? Thanks.
On Jan 25, 2009, at 9:47 PM, Lachlan Deck wrote:
On 26/01/2009, at 6:41 AM, William Hatch wrote:
Using latest Eclipse, WOLips (largely irrelevant here), the
woapplication-archetype and the m2Eclipse plug in, I'm able to
easily create wo apps, set them up for war packaging, get them to
build and install into the local maven repos. So, experimenting
with the next steps, decided to try automating the deployment to my
local tomcat using the cargo plug in. I had to follow the
to create the subclass of ERXServletAdaptor in order to avoid the
dreaded WOServletAdaptor not found exception, but then I get
another exception as the generated classpath seems to be pointing
to an app named "JavaWebObjects" and not my app, although the first
part of the url (context path) is correct, so it's trying to find
components and other resources using this url:
I _think that build.properties used to have all this stuff, but now
that I'm not using ant here how do I convey the right properties
values in this environment?
afaik the woproject-maven plugin still uses the build.properties.
I've attached what I get when creating a new app.
Where should I put them, and what should they be called? Thanks.
Disclaimer: I don't currently deploy to servlets - but I'd suggest
checking the resulting web.xml.
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