Re: AGS 3.0 Errors on OSX 10.6 using Java 1.6

[BLuRry <brendan.robert@gmail.com>]

On May 20, 1:45 pm, "John B. Matthews" <nos...@nospam.invalid> wrote:
> In article
> <eb8a7d8a-9331-4d47-87bd-5bf04b955...@w3g2000vbd.googlegroups.com>,
>
>  schmidtd <schmi...@my-deja.com> wrote:
> > > Mustn't one supply a class name when executing a jar file?
>
> > Not if it has a manifest.
>
> As an aside, this command line utility displays A JAR's manifest:
>
> <http://sites.google.com/site/drjohnbmatthews/manifesto>
>
> --
> John B. Matthews
> trashgod at gmail dot com
> <http://sites.google.com/site/drjohnbmatthews>

java -jar dist/ags.jar should do the trick.  Spaces in the pathname
(anywhere in your path) could make a difference, though Java
internally doesn't barf on that sort of thing from what I've seen.

If all else fails, I'll send you a copy of what I have currently on my
hard drive.  It could be possible that you may have an older build?
The program does a rather interesting thing to introspect all of its
classes for configurable values, so it actually digs through the
classpath for classes in the ags package and introspects each class
for anything annotated as @configurable.  Anything found is put into
the configuration view, etc.  In your case it comes back saying it
found nothing, indicating that the responsible code is unable to
inspect the ags.jar file.  Do you have anything being appended to the
classpath that perhaps does not exist?  For example, the manifest of
ags.jar points to some other items to go into the classpath, and if
those don't exist it could be feasibly the source of the problem.

I'll put a @TODO in the code to remind me to more gracefully handle
bogus classpath entries to be on the safe side.

-Brendan