Am 9. August 2015 17:29:42 MESZ, schrieb "Tudor Girba-2 [via Smalltalk]" <[hidden email]>:

Ok. I added now:
- 3.1-alpha with packages for pharo 5
- development and stable symbolic versions for pharo 3 and pharo 5.

The tests problem should still be solved. Do you still want to look at that?

Once that is done, the tests packages should be added to the version. I can do that.

Cheers,
Doru

On Sun, Aug 9, 2015 at 2:51 PM, Joachim Geidel <[hidden email]> wrote:

> Am 09.08.2015 um 14:36 schrieb Tudor Girba-2 [via Smalltalk] <[hidden email]>:
> 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?

Yes, of course, do whatever it takes. I used the ��aN�� suffer because I considered that version as an alpha release, and wanted to do a lot more before publishing a ��real�� release.

Cheers,
Joachim

View this message in context: Re: troubles with JNIPort on Pharo 5 / Java 8
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

--
www.tudorgirba.com

"Every thing has its own flow"

If you reply to this email, your message will be added to the discussion below:
http://forum.world.st/troubles-with-JNIPort-on-Pharo-5-Java-8-tp4836922p4841826.html

To unsubscribe from troubles with JNIPort on Pharo 5 / Java 8, click here.
NAML