Hey Johnny:

Yeah, I definitely think setting that at runtime would fix the problem. The 
biggest issue I see is that when you download Wonder there is a BUILD.txt file 
with instructions on how to build. It should probably be updated as well.

I’ve done it the same way for a long time - and I haven’t run a new build for a 
while. So, it definitely caught me off guard.

Tim

On May 8, 2014, at 1:38 PM, Jonathan Miller <[email protected]> wrote:

> Hi Tim,
> 
> I hope I'm not misunderstanding your issue but have you tried this:
> 
> 
> sudo ant -Duser.home=$HOME frameworks.install
> 
> 
> I noticed that the wiki was updated recently.
> 
> http://wiki.wocommunity.org/display/documentation/Building+and+Installing+a+Framework+with+Ant
> 
> Aloha,
> 
> Johnny
> 
> 
> 
> On Thu, May 8, 2014 at 9:20 AM, Timothy Worman <[email protected]> wrote:
> On May 8, 2014, at 12:07 PM, Ray Kiddy <[email protected]> wrote:
> 
> > On Thu, 8 May 2014 00:31:22 -0700
> > Timothy Worman <[email protected]> wrote:
> >
> >> On May 7, 2014, at 11:26 PM, Ray Kiddy <[email protected]> wrote:
> >>
> >>> On Wed, 07 May 2014 19:56:45 -0700
> >>> Timothy Worman <[email protected]> wrote:
> >>>
> >>>> All:
> >>>>
> >>>> After running this:
> >>>>
> >>>> ant clean frameworks; sudo ant frameworks.install
> >>>>
> >>>> I get the following errors:
> >>>>
> >>>> BUILD FAILED
> >>>> /Users/worman/Source/wonder/build.xml:18: The following error
> >>>> occurred while executing this
> >>>> line: /Users/worman/Source/wonder/Build/build/build.xml:1509: The
> >>>> following error occurred while executing this
> >>>> line: /Users/worman/Source/wonder/Build/build/build.xml:1500: The
> >>>> following error occurred while executing this
> >>>> line: /Users/worman/Source/wonder/Build/build/build.xml:58: The
> >>>> following error occurred while executing this
> >>>> line: /Users/worman/Source/wonder/Build/build/generic.xml:526: 
> >>>> /var/root/Roots/ERJars.framework
> >>>> does not exist.
> >>>>
> >>>
> >>> Very weird. I got this to work by doing:
> >>>
> >>>     sudo ant -Dwo.external.root=/home/ray/Roots
> >>> frameworks.install
> >>>
> >>> I do not know _why_ we would have to do this, though. I believe that
> >>> this worked at some time in the past. Does anyone else have any
> >>> theories about when this stopped working?
> >>>
> >>> And frankly, it seems odd that one could have ever run "sudo ant"
> >>> and gotten a correct value for ${user.home}. Than again, it's been
> >>> a long day. Maybe I am squinting at this wrong.
> >>>
> >>> - ray
> >>
> >> If you:
> >> 1. sudo -s (to gain root privs)
> >> 2. cd
> >> 3. pwd
> >>
> >> The output should reflect your user home not root’s home. For me it
> >> was /Users/worman. That is just the way sudo works. It doesn’t
> >> clobber your environment variables - at least not on OS X-nix. So,
> >> the build scripts should work with sudo. They definitely changed at
> >> some point because I have always built wonder this way and the
> >> BUILD.txt also instructs building this way. My wolips.properties and
> >> build.properties have not changed in a long time so I don’t think it
> >> is that.
> >>
> >> Tim
> >
> > I know what you are saying, but, for me, "ant frameworks" builds
> > into /home/ray/Roots and "sudo ant frameworks.install" wants to pull
> > from "/root/Roots".
> >
> > Check this out. The ${user.home} variable in the ant file is pulled
> > automatically from one's System properties, so:
> >
> > $ cat whoami.java
> >
> > public class whoami {
> >  public static void main(String[] arg) {
> >    System.out.println("user.home:\"" +
> >      System.getProperty("user.home")
> >      + "\"");
> >  }
> > }
> > $
> > $ javac whoami.java
> > $ java -classpath . whoami
> > user.home: "/home/ray"
> > $ sudo java -classpath . whoami
> > [sudo] password for ray:
> > user.home: "/root"
> > $
> >
> > What do you get?
> 
> I get the same result on OS X Mavericks. And yet this exact procedure used to 
> work and didn’t used to seek the built frameworks in /var/root/Roots. That’s 
> a bit strange to me. I’m pretty sure the legacy need for the sudo was because 
> it was required to install into /Library/Frameworks - unless you changed 
> permissions on that directory. In any case, anyone who reads the build 
> directions and follows them may very well hit this same wall. So, we 
> definitely should make a change.
> 
> >
> > - ray
> >
> >>
> >>> It appears `ant clean frameworks` is successful - build to ~/Roots
> >>>> looks normal. It seems to be failing because it is looking in the
> >>>> root user’s home for ERJars.framework. This looks good:
> >>>>
> >>>> global.framework.build:
> >>>>   [mkdir] Created dir: /Users/worman/Roots/ERJars.framework
> >>>>
> >>>> global.dummy:
> >>>> [woframework] Installing ERJars in /Users/worman/Roots
> >>>>     [jar] Building jar: /Users/worman/Roots/ERJars-6.0.jar
> >>>>
> >>>> global.dummy:
> >>>>    [echo] -------------------------------------
> >>>>    [echo] ERJars.framework done
> >>>>    [echo] -------------------------------------
> >>>>
> >>>> Possibly the `sudo ` is causing something to interpret
> >>>> ‘home' as root’s home instead of the my home? This has never
> >>>> happened before and I’d love to know if I’ve suffered a
> >>>> self-inflicted wound. Otherwise, I’d love to fix this up - or know
> >>>> what the fix-up is!
> >>>>
> >>>> If I do `sudo ls ~` my user home is returned, not /var/root so I’m
> >>>> pretty sure it isn’t an issue with my environment.
> >>>>
> >>>> Tim
> >>
> >>
> >
> 
> 
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/jlmiller%40kahalawai.com
> 
> This email sent to [email protected]
> 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to