Re: Building on server, no Eclipse
Re: Building on server, no Eclipse
- Subject: Re: Building on server, no Eclipse
- From: Dom <email@hidden>
- Date: Mon, 06 Apr 2009 21:36:28 -0400
On Apr 6, 2009, at 8:39 PM, Chuck Hill wrote:
On Apr 6, 2009, at 5:03 PM, Dom wrote:
On Apr 6, 2009, at 7:51 PM, Chuck Hill wrote:
On Apr 6, 2009, at 4:28 PM, Dom wrote:
I'd think this has to be some freaking setting/property/stupid
wobuild file some place as it works locally using ant within
Eclipse. Man this is frustrating; it seems like every time I
start to get some place with WebObjects I hit yet another wall.
On Apr 6, 2009, at 4:26 PM, Chuck Hill wrote:
On Apr 6, 2009, at 1:17 PM, Dom wrote:
Getting errors on included frameworks, as in, it can't find
them. The frameworks are building and installing fine on the
server, but the main project can't find them. What do I need to
make sure is up there for this to work? Thanks.
Dom
This is really a WOLips question...
Check
~/Library/Application\ Support/WOLips/wolips.properties
for the user they are getting built as.
The file is there, lots of properties all pointing to logical
places where frameworks live, at least of the ones I'm using.
And are your frameworks there? Is the jar built in .framework/
Resources/Java?
Yes and yes.
Check also
- permissions
- woproject.jar version
Good here; copied up the latest previously and it's on the path.
The tasks are executing, they're just failing.
It is not picking up an older version from the Ant/lib or Java
Extensions?
No, this is on a linux box so I created my own lib directory and
placed this jar there, then added that to ant's classpath along
with the catalina tasks or whatever it is for tomcat deploying.
Originally yes, there was the older version from pre hotness, but I
did change that after upgrading. And, I upgraded the projects as
outlined elsewhere.
- errors in the ant log (run with -version -debug for more info)
When building one of the dependent frameworks, I found something
interesting:
[woframework] No sources found.
And the build just zips by, including the install into /Library/
Frameworks. I'd think that if it didn't find anything to compile,
it would fail and the install would not occur, no?
You can have a resource only framework.
Ah yeah, true. Didn't think of that;-)
Anyway, it's doing that on both the dependent frameworks and at
least that explains why the main project isn't compiling as it
can't find the class files it needs from the frameworks. So now
the question is why are those builds not really Succeeding?
They are not failing either. They are just not doing what you
want. Are the sources really there on the server in the Sources/
directory in each framework? Is the project the current working
directory when you build them? If you are not using Eclipse, what
are you using? A custom Ant script? Check your Ant... verify
assumptions.
yes, the sources are there and I am building from the root of the
project directly using Ant v 1.7.1 I just issue ant clean install;
not sure what you mean when you say no Eclipse. I have only shell
access to the server.
How old are your build.xml files? Does the woframework task start
like:
<target name="build.woframework" depends="compile">
I replaced the build files with one from a new wonder framework
project as part of upgrading to the new wolips. First target in mine is:
<!-- main targets -->
<!-- add optional targets to depends list if needed -->
<target name="build" depends="setProps,init.build,build.woframework" />
Anything in the compile target that does not match that machine? It
should "just work" but...
it's running java 1.6 on the server, and I'm running 1.5 locally. I
have built another project before, but that one didn't use any
frameworks.
Also, again, look for errors or information in the ant log (run with
-version -debug for more info) around where it says [woframework] No
sources found.
Other things noticed:
[antlib:org.apache.tools.ant] Could not load definitions from resource
org/apache/tools/ant/antlib.xml. It could not be found.
and theres' a load of this, one statement for each property defined in
either build.properties or the wolips.properties
Override ignored for propery "some.property"
And then these few lines, variations of which appear near the No
Sources Found output:
WOFileSet: Setup scanner in dir /home/dom/Projects/ORM/bin with
patternSet{ includes: [**/*.class, *.properties] excludes:
[build.properties] }
[woframework] No Implementation-Title set.No Implementation-Version
set.No Implementation-Vendor set.
[woframework] Location: /home/dom/Projects/ORM/build.xml:49:
Dang; thanks Chuck.
Chuck
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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