The root of the problem was that I didn't have my framework project added as a
framework to my main project, and that's where the jdom jar I was referencing
was (among others). On my development machine I was referencing the project,
so everything worked there. As soon as I added the framework
>
> chown -R `whoami` /Library/Frameworks
>
Thank you that worked. I have no idea how the directory got hosed.
Ted
--- On Mon, 7/23/12, Maik Musall wrote:
> From: Maik Musall
> Subject: Re: what did I break with ant?
> To: "Theodore Petrosky"
> Date: Monday, July 23, 2012, 12:48 PM
>
I found a fix for this issue.
A line in the config was not liked by the wonder adaptor. In
/ets/apache2/sites-available/default-ssl:
SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
On our test platform, were everything worked, this was commented-out. So the
problem, describe
On Jul 23, 2012, at 4:59 PM, Theodore Petrosky wrote:
>
> BUILD FAILED
> /Users/asacksadmin/Documents/workspaceAS_II/ASPOOpenProjectsFW/build.xml:57:
> Directory /Library/Frameworks/ASPOOpenProjectsFW.framework creation was not
> successful for an unknown reason
>
> Total time: 3 seconds
>
>
Maybe I have been doing this wrong from the beginning but, all of a sudden, I
right click on my Wonder Framework and select "Wo Ant tools" => install. and I
get this error:
Buildfile:
/Users/asacksadmin/Documents/workspaceAS_II/ASPOOpenProjectsFW/build.xml
init.properties:
init.install:
init.b
Quick reminder: you can have email notifications when a commit on Project
Wonder is made on GitHub. You only need to subscribe to the
wonder-comm...@wocommunity.org by sending a empty email to:
wonder-commits...@wocommunity.org
You can also subscribe to the RSS feed:
https://github.com/pr
Le 2012-07-22 à 21:05, Jeffrey Schmitz a écrit :
> Yep, something weird going on here, not sure why it's picking up the cocoon
> stuff (even though it is a pretty cool framework) or the saxon stuff, from my
> downloads directory of all places. I don't have either in my build path of
> my proj
