Re: Latest WOLips war build; incorrect classpath generated
Re: Latest WOLips war build; incorrect classpath generated
- Subject: Re: Latest WOLips war build; incorrect classpath generated
- From: Don Lindsay <email@hidden>
- Date: Fri, 13 Mar 2009 17:44:23 -0400
In my experience builds that consistently take a long time can be
caused by:
1. The date time on your system is wrong
2. There is some process that is touching your files and setting the
modified date which is causing them to be picked up as modified.
Are you using a CVS or SVN for your project?
Don
On Mar 13, 2009, at 4:40 PM, Dom wrote:
On Mar 13, 2009, at 3:51 PM, Don Lindsay wrote:
Hello Dom;
After removing the libraries from your project did you do clean on
the project? This should clean out your WAR directory as well.
After you do a clean the war will take a long time to rebuild the
next time it is compiled because it is copying in all the frameworks.
Yes, I've cleaned several times, and confirmed that it does remove
the contents of the dist directory. For me, it seems that even
incremental builds take quite a long time.
Thanks Don.
Thanks,
Don
On Mar 13, 2009, at 1:04 PM, Dom wrote:
Eclipse 3.4.2
WLips 3.4.5693
WebObjects 5.4.3
Now that I resolved my previous issue with ant (turns out the
build that was on our linux box was troublesome, rebuilding a
different distribution solved the too many open files compile
problem) I'm onto the next step in my webobjects exploration:
deploying a war.
The war builds fine; I modified the build.xml slightly to skip the
packaging step for when I'm running locally using webobjects
direct connect (I think that's what it does?) as it added
significant time to the process, but otherwise all project
elements are stock. The resulting built wars' web.xml contains an
incorrect classpath entry:
WEBINFROOT/Resources/Java/testng-5.8-jdk15.jar
This jar is not available there, and was added to the project's
local Library directory and actually ends up in WEB-INF/lib/
directory. That's problem one.
The second problem is a little more odd. I'd added some jars to
the Library directory previously, but then removed them. They're
no longer listed in the project's .classpath, but they're still
showing up (incorrectly, as above) in the generated web.xml
classpath section of the resulting war.
What the heck is going on here? How is the classpath entry in
web.xml generated? Most importantly, how can i fix this? I'm also
wondering what the WOLips deployment properties "Custom Web-XML"
section does; add to, or replace?
On a side note, does anybody have any experience using the maven
stuff for webobjects to build wars? I'd prefer that actually, but
it seems that wolips is geared towards ant and I didn't want to
further complicate my webobjects introduction.
Thanks
Dom
_______________________________________________
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
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@mac.com
This email sent to 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