Hi, Great.
However, I notice that you have some distinct version names, and this seems to throw MC off. For example, when trying to load the latest version of ConfigurationOfJNIPort: - we get: ConfigurationOfJNIPort-JoachimGeidel.3.0a3 - instead of: ConfigurationOfJNIPort-JoachimGeidel.3.0a4 This problem would be fixed if we would change the numbering a bit. For example, when I try to commit a new version of the configuration, Monticello offers: ConfigurationOfJNIPort-TudorGirba.3.5 Is it Ok if I commit it like this? Cheers, Doru On Sun, Aug 9, 2015 at 1:44 PM, Joachim Geidel <joachim.gei...@onlinehome.de > wrote: > Hi Tudor, > > Am 09.08.2015 um 13:27 schrieb Tudor Girba: > I tested your changes, and I confirm that the code works fine in Pharo 5. > Now, we just need to get them published :). > > > I tend to avoid words like „just“, „simply“ etc. when talking about > software. ;-) The ConfigurationOfJNIPort should be updated in a way which > lets one load the current package versions when using Pharo 3, and new ones > when using Pharo 4 or 5. I haven’t used this stuff for a while, and will > have to read the documentation again before being able to publish something > useable. > > I have just added you as a contributor to the JNIPort project and as a > member to the JNIPort team at SmalltalkHub, so you can publish changes. > > Cheers, > Joachim > > > ------------------------------ > View this message in context: Re: troubles with JNIPort on Pharo 5 / Java > 8 > <http://forum.world.st/troubles-with-JNIPort-on-Pharo-5-Java-8-tp4836922p4841817.html> > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com. > -- www.tudorgirba.com "Every thing has its own flow"
