Skip to content
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.

error importing collection/1.3.1 w/latest 1.3.2 build on JS #6938

Closed
jvasileff opened this issue Feb 26, 2017 · 4 comments
Closed

error importing collection/1.3.1 w/latest 1.3.2 build on JS #6938

jvasileff opened this issue Feb 26, 2017 · 4 comments

Comments

@jvasileff
Copy link
Contributor

With module.ceylon:

module simple "1.0.0" {
    import ceylon.collection "1.3.1";
}

and run.ceylon:

import ceylon.collection { ArrayList }

shared void run() {
    value al = ArrayList<String>();
    al.add("x");
    print(al);
}

I'm getting:

$ ceylon compile-js
Error: Errors found. Compilation stopped.
Note: Created module simple/1.0.0
source/simple/module.ceylon:1: error: module (transitively) imports conflicting versions of dependency 'ceylon.language': version '1.3.1' (via import path 'simple -> ceylon.collection -> ceylon.language'
) and version '1.3.2-SNAPSHOT' (via import path 'simple -> ceylon.collection -> ceylon.language')
module simple "1.0.0" {
       ^
1 error
ceylon compile-js: There was 1 error.

But it does work with:

module simple "1.0.0" {
    import ceylon.collection "1.3.0";
}
@quintesse
Copy link
Contributor

Pity I hadn't seen this issue earlier. Pretty nasty this is now in the official release :(

@quintesse
Copy link
Contributor

THis 7135998 should at least fix it for 1.3.3. Closing.

@quintesse quintesse modified the milestones: 1.3.3, 1.3.2 Mar 3, 2017
@lucono
Copy link

lucono commented Mar 10, 2017

Pity I hadn't seen this issue earlier. Pretty nasty this is now in the official release :(

@quintesse, it would be great if the team would release a follow-up patch soon after each release because painful bugs like this are bound to surface soon after a release, as it gets usage from more people. I think the wait time for a patch release is really hard on the most committed users of the language. I think for minor version releases, say 1.4, it would be okay, but for patch releases like 1.3.2, it can feel like a very long time to get important fixes.

Issue #6823 was one I reported 3 months ago, the fix of which only got released with the 1.3.2 release.

Having said that, I appreciate and strongly commend the progress on the language. It's a language I want to use everyday.

@gavinking
Copy link
Contributor

I agree. I think we should do a quick 1.3.3 release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants