A new topic, 'Workaround: IKVM and Windows 7 Classpath Determination Issue',
has been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=128.new#new
The text of the topic is shown below:
All,
Okay, so running liquibase on Windows 7 x64 via iKVM is a pretty freaky
combination. That being the case, I'm not really sure that opening a bug would
be terribly fair at this point.
If you try to use this particular combination you will notice that your
liquibase execution will fail with an error message about a classpath being
non-existent -- at least you will if there is a colon (eg C:...) in the
classpath. For some reason, IVKM in this configuration reports the os.name
value as "Microsoft Windows 6.1 ..." rather than "Windows 7" like the jvm does.
The "Microsoft" makes the isWindows() call in Main.java return false and the
classpath parsing doesn't quite work out from that point on.
So, to work around the issue add "-Dos.name="Windows " to the iKVM command line
and the parsing will return to normal.
Perhaps looking at the separator value for the JVM would be a little more
consistent across implementations? Dunno. Hope this helps some of you.
Coridally,
Jonathan Lent
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
