• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
WO Framework build ant woes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

WO Framework build ant woes


  • Subject: WO Framework build ant woes
  • From: Florijan Stamenkovic <email@hidden>
  • Date: Thu, 10 Jul 2008 11:31:09 -0400

Hi all,


I am building a framework (pure WO, no wonder), and trying to get the projects that depend on it to bundle it, as described in the "Embedding WOFrameworks" wiki entry.


So, a few questions, about the framework project:

1. The "build" target does not depend on the "compile" target, so, does the standard build depend on Eclipse's incremental compiling?
2. If the above is true, what exactly is the purpose of the "compile" target, what does WOCompile do differently?
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?
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.


Also, another question regarding the embedding process described on the wiki... It uses a third "project" to do all the bundling and stuff. I'm trying to avoid that by modifying the ant build of the app project directly. I use ant occasionally, but am far from an expert, can anyone tell me if I am doing something very evil? What I do is this:

In the init.build target:

<!-- Framework build -->
<ant dir="../Framework" antfile="build.xml" target="compileAndBuild"></ant>


In the build.woapp target:

<!-- Framework inclusion -->
<frameworks root="../Framework/dist" embed="true">
	<include name="*.framework"/>
</frameworks>

In the compile target, under classpath:

<!-- Framework stuff-->
<fileset dir="../Framework/dist">
	<include name="**/*.jar" />
</fileset>

Also, what do you think of making the embedding process a part of the standard builds? I guess that two properties (one containing the framework project names to embed, and a flag indicating if they should be embedded) could be used to do what I do above, but without referencing the framework names in the ant itself, only in the props... Uhm, would that be even possible?

Thanks
F
_______________________________________________
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


  • Follow-Ups:
    • Re: WO Framework build ant woes
      • From: Chuck Hill <email@hidden>
  • Prev by Date: Re: DB uniqueness constraints and dealing with them
  • Next by Date: TopLink now EclipseLink and OpenSource
  • Previous by thread: Re: WO5.4.2 download url
  • Next by thread: Re: WO Framework build ant woes
  • Index(es):
    • Date
    • Thread