I just checked and yes the jnlp being used by the hydrogen cars (otrunk) 
is using:
<jar href="org/mozdev/mozswing/mozswing-complete/mozswing-complete.jar" 
version="1.0-20080221.165853-7"/>

I'd recommend updating that to point to the new one, it should reference:
<jar href="org/mozdev/mozswing/mozswing-complete/mozswing-complete.jar" 
version="1.1"/>

Your pom that builds the jnlp should include this dependency:
<dependency>
<groupId>org.mozdev.mozswing</groupId>
<artifactId>mozswing-crossplatform</artifactId>
<version>1.0-SNAPSHOT</version>
<type>pom</type>
</dependency>

It might actually be that the mozswing dependency is pulled in 
transitively so you might need to change this in some other project's pom.

Scott


Geoffrey Kwan wrote:
> I'm at the school right now trying to get two of their computers 
> working so we'll have enough for all the students to pair up 2 to a 
> computer. All of their computers have been updated to the latest Java 
> 10.4 Release 8. Mozswing installs and I see the penguin guy but when I 
> launch a project it gives me this error
>
> XULRunner home: not resolved
> Profile directory: not used
> Platform: OSX
> Java: 1.5.0_16-132, "Apple Computer, Inc."
>
> --------------------------------------------------
>
> java.io.IOException: Unable to resolve XULRunner home location
>     at 
> org.mozilla.browser.MozillaInitialization.initialize(MozillaInitialization.java:92)
>     at org.mozilla.browser.MozillaPanel.<init>(MozillaPanel.java:147)
>     at org.mozilla.browser.MozillaPanel.<init>(MozillaPanel.java:116)
>     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
>
>
> So I've been trying to mess around with the java preferences with the 
> tool that you linked to. What should I be looking at within the tool?
>
> I've compared the entry /org/mozdev/mozswing/xulrunner/Mozilla 
> XULRunner 1.8.1.4_0000000000 (in the System tab) on a computer that 
> has mozswing working in the project with a computer that does NOT have 
> mozswing working in the project, here's the difference between the two
>
> project working mozswing
> /Users/support/Library/Caches/Java/cache/javaws/ext/E1242068760060/RMmozswing-xulrunner-macosx-ppc/native/macosx/xulrunner
>
> project NOT working mozswing
> /Users/support/Library/Caches/Java/cache/javaws/ext/E1242074762505/mozswing-native/native/macosx/xulrunner
>
> On the NOT working mozswing, I tried changing the entry value to use 
> the ../RMmozswing-xulrunner-macosx-ppc/.. directory instead of 
> mozswing-native (as well as changed the actual directory name on the 
> hard drive) but it still didn't work.
>
> Any suggestions?
>
> Thanks,
> Geoff
>
> On Fri, May 8, 2009 at 3:31 PM, Scott Cytacki <[email protected] 
> <mailto:[email protected]>> wrote:
>
>
>     First to be clear these issues are only for Wise 3.  The LOOPS OTrunk
>     activities currently doesn't require mozswing.
>
>     There are a few of issues to consider:
>     - which version of mozswing you are using in this wise 3 build
>     - which mozswing installer you are using
>
>     The http://www.concord.org/~scytacki/mozswing/mozswing.jnlp
>     <http://www.concord.org/%7Escytacki/mozswing/mozswing.jnlp>
>     <http://www.concord.org/%7Escytacki/mozswing/mozswing.jnlp>
>     is really old, you shouldn't be using that one.
>
>     Since I think you are using an updated wise 3 jnlp you are probably
>     using the more recent mozswing.  So for that you should use this
>     installer:
>     http://jnlp.concord.org/dev/mozswing/mozswing.jnlp
>
>     If for some reason you are using an older version of mozswing in
>     wise 3,
>     then you'll need to use this one:
>     http://jnlp.concord.org/dev/mozswing-v1.0/mozswing.jnlp
>
>     Most likely the reason your approach below worked, was because the old
>     (~scytacki) mozswing installer you were using didn't work on java
>     1.5.0_16 but it did work on java 1.5.0_13.
>
>     If you are still having problems you should get this tool:
>     http://javaprefs.googlepages.com/
>     And take a look at your java preferences.  That will tell you
>     where the
>     mozswing installer thinks it has installed xulrunner.
>
>     Scott
>
>
>     Geoffrey Kwan wrote:
>     > Hey Guys,
>     >
>     >     Earlier this week I had to format one of our macbooks
>     because the
>     > accounts somehow became corrupted. We couldn't log in so I had to
>     > format the computer. After performing all the updates and java
>     fixes,
>     > I couldn't launch the mozswing installer. Here's what I did
>     >
>     > 1. Complete erase and install of Mac OS X 10.4.11
>     > 2. Performed all software updates (java gets updated to 1.5.0_16)
>     > 3. Performed all java fixes for the configuration of Mac OS X
>     10.4.11
>     > with Java 1.5.0_16 (there are two fixes for this configuration)
>     >
>     (http://confluence.concord.org/display/CCTR/WebStart+OSX+Java+1.5+Fix)
>     > 4. Ran the mozswing installer
>     > (http://www.concord.org/~scytacki/mozswing/mozswing.jnlp
>     <http://www.concord.org/%7Escytacki/mozswing/mozswing.jnlp>
>     > <http://www.concord.org/%7Escytacki/mozswing/mozswing.jnlp>)
>     > unsuccessfully
>     >
>     > The mozswing installer would not work. It would launch the java web
>     > start download progress window/bar and look like it was working, but
>     > then after it looked like it was about done, the java web start
>     > window/bar would just disappear and nothing would show up. What
>     would
>     > usually happen after that point would be the prompting of the
>     user to
>     > trust the certificate but that never shows up and nothing else shows
>     > up either.
>     >
>     > After this, I couldn't get the mozwing installer to work even after
>     > trying to clear the java cache and trying the java fixes again.
>     >
>     >
>     > To resolve this, I formatted the computer again, but this time I
>     > applied the java fixes before I updated java each time. Here's
>     what I
>     > did (the steps may not have been exact but you'll get the idea)
>     >
>     > 1. Complete erase and install of Mac OS X 10.4.11
>     > 2. Ran java patch for whatever the base configuration was (probably
>     > java 1.5.0_06 or 1.5.0_07)
>     > 3. Ran the mozswing installer successfully
>     > 4. Updated java (I think to java 1.5.0_13)
>     > 5. Ran the java patch for the new configuration of (java 1.5.0_13)
>     > 6. Ran the mozswing installer successfully
>     > 7. Updated java (to java 1.5.0_16)
>     > 8. Ran the java patch for the new configuration of (java 1.5.0_16)
>     > 9. Ran the mozswing installer successfully
>     > 10. Updated java again
>     > 11. Ran the java patch
>     > 12. Ran the mozswing installer successfully
>     >
>     > Some of the steps might not have been necessary but I wanted to be
>     > safe to make sure mozswing would work.
>     >
>     > Do you guys know about/have this issue? It seems like it could be a
>     > problem with Java for Mac OS X 10.4, Release 8 which was released on
>     > February 12, 2009. It would be nice if I didn't have to format the
>     > computers at Foothill MS just to get mozswing working. It seems
>     as if
>     > Kathy and Doug were unable to resolve the mozswing issue through the
>     > regular attempts to clear java cache, install java fixes, launch
>     > mozswing installer though. Any suggestions?
>     >
>     > Thanks,
>     > Geoff
>     >
>     >
>     > ---------- Forwarded message ----------
>     > From: *Kathy Benemann* <[email protected]
>     <mailto:[email protected]>
>     > <mailto:[email protected] <mailto:[email protected]>>>
>     > Date: Fri, May 8, 2009 at 1:32 PM
>     > Subject: Troubles at Foothill MS
>     > To: Geoffrey Kwan <[email protected]
>     <mailto:[email protected]>
>     > <mailto:[email protected]
>     <mailto:[email protected]>>>, Hiroki Terashima
>     > <[email protected] <mailto:[email protected]>
>     <mailto:[email protected] <mailto:[email protected]>>>,
>     Helen Zhang
>     > <[email protected] <mailto:[email protected]>
>     <mailto:[email protected] <mailto:[email protected]>>>, Ken Bell
>     > <[email protected] <mailto:[email protected]>
>     <mailto:[email protected] <mailto:[email protected]>>>, Kimberle Koile
>     > <[email protected] <mailto:[email protected]>
>     <mailto:[email protected] <mailto:[email protected]>>>
>     >
>     >
>     > Hi Folks,
>     >
>     > Doug and I have been working all day to preload all the projects.  6
>     > computers are causing problems: 3 of ours and 3 of the school's
>     > laptops.  On these laptops, we have tried installing mozswing on
>     both
>     > student and admin accounts (won't launch via either,) installing
>     Java
>     > patch (still wouldn't allow mozswing to launch,) and clearing
>     the Java
>     > cache.
>     >
>     > Margaret kindly agreed to start on Tuesday so we can get these
>     laptops
>     > running.  (Obviously, we can't run this project with just 11
>     machines
>     > given that we have 34 kids in the class.)
>     >
>     > Hiroki and Geoff, we need one of you to come out here on Monday to
>     > work on these 6 computers that aren't cooperating.  Let me know who
>     > will be able to come out to Foothill MS.  I can meet you here; just
>     > let me know what time.
>     >
>     > Helen, this will also allow you to be here at the start of the run.
>     >
>     > Ok, we are going to pack up now and head home for much deserved
>     > margaritas.
>     >
>     > Thanks,
>     > Kathy
>     >
>     >
>     >
>     > --
>     > Kathy Benemann
>     > Project Manager
>     > Graduate School of Education
>     > 4421 Tolman Hall
>     > UC Berkeley
>     > (925) 301-6546
>     >
>     >
>     > >
>
>
>
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SAIL-Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to