On Thu, 8 May 2014 00:31:22 -0700
Timothy Worman <li...@thetimmy.com> wrote:

> On May 7, 2014, at 11:26 PM, Ray Kiddy <r...@ganymede.org> wrote:
> 
> > On Wed, 07 May 2014 19:56:45 -0700
> > Timothy Worman <li...@thetimmy.com> 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?

- 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      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to