Re: WO Framework build ant woes
Re: WO Framework build ant woes
- Subject: Re: WO Framework build ant woes
- From: Florijan Stamenkovic <email@hidden>
- Date: Thu, 10 Jul 2008 15:00:24 -0400
2. If the above is true, what exactly is the purpose of the
"compile" target, what does WOCompile do differently?
It should do the same thing, but from the command line.
Yeah, that chimes with my own conclusions about it, all the fuss
inside seems to be primarily classpath oriented. Any idea then why is
it there? Why not simply rely on Eclipse's compiling?
3. The "compile" target in the framework failed because I didn't
have the Frameworks folder in my users's Library. After creating
the Frameworks folder, which I guessed to be the quickest
solution, the <wocompile srcdir="Sources" destdir="bin"> task
failed with a NullPointerException. Any suggestions?
I use this:
<!-- Distribution WOProject compilation -->
<target name="compile" depends="setProps">
<wocompile destdir="bin"
debug="${wocompile.debug.flag}"
optimize="${wocompile.optimize.flag}"
deprecation="on">
<src refid="${project.source.path}"/>
<classpath refid="project.classpath"/>
</wocompile>
</target>
I like this, it is short :)
Plus some steps to set up <src refid="${project.source.path}"/>
project.source.path is an entry in build.props? You do something
special, or just point to Sources?
and <classpath refid="project.classpath"/>
May I ask what does project.classpath resolve to? Does it tap into
Eclipse's project cp stuff, or?
4. Can I modify the "compileAndBuild" so that it works like the
"build" (ditch "compile"), in short, why should I use
"compileAndBuild" when using the ant from another project ant
(embedding the framework)? I guess that is kind of the same as the
question nr. 2.
Embedding does not use the Ant form another project (AFAIK).
Adding the following to the init.build seemed to make sense, just to
ensure the latest build of the to-be-embedded framework:
<ant dir="../Framework" antfile="build.xml" target="build"></ant>
The wiki example does something similar, in the second part, which
explains how to embed a framework that is a project, and not an
already made thing.
<!-- Framework inclusion -->
<frameworks root="../Framework/dist" embed="true">
<include name="*.framework"/>
</frameworks>
A comment on this, something rather bizarre happened as a
consequence. I ended up having 2 frameworks in my app's Contents. One
was the <FrameworkName>.framework (which I wanted there), and another
one was <AppName>.framework, which I have no idea how it even came to
exist... Super strange. A workaround was to use this instead (the
third line differs):
<!-- Framework inclusion -->
<frameworks root="../Framework/dist" embed="true">
<include name="Framework.framework" />
</frameworks>
I don't handle it there as I am usually building multiple
application for packaging and deployment.
So, what do you do? Have an ant build external to all projects that
aggregates the work? I'm trying to find a nice, clean, maintainable
way to handle this, so that I hopefully never have to look at it
again...
I'd wait until Mike finishes his classpath changes before doing any
work on this. Things may change greatly.
Fair enough.
_______________________________________________
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