Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 21 2022 08:27
    Kopilov closed #662
  • Nov 21 2022 08:27
    Kopilov commented #662
  • Nov 21 2022 08:27
    Kopilov closed #506
  • Nov 21 2022 08:27
    Kopilov commented #506
  • Oct 28 2022 07:13
    momomo commented #7454
  • Oct 28 2022 07:12
    ShalokShalom commented #7454
  • Oct 27 2022 23:26
    OndraZizka commented #7454
  • Sep 21 2022 08:49
    ShalokShalom commented #7454
  • Sep 21 2022 08:48
    ShalokShalom commented #7454
  • Sep 21 2022 08:47
    ShalokShalom commented #7454
  • Sep 21 2022 08:46
    ShalokShalom commented #7454
  • Sep 21 2022 08:45
    momomo commented #7454
  • Sep 21 2022 08:44
    ShalokShalom commented #7454
  • Sep 21 2022 08:43
    ShalokShalom commented #7454
  • Sep 21 2022 08:20
    luolong commented #7454
  • Sep 20 2022 13:49
    ShalokShalom commented #7454
  • Sep 20 2022 13:36
    momomo commented #7454
  • Sep 20 2022 13:30
    ShalokShalom commented #7454
  • Sep 20 2022 13:18
    momomo commented #7454
  • Sep 20 2022 13:17
    momomo commented #7454
John Vasileff
@jvasileff
The only path forward I see is to rename binary-compatibility-affecting classes back to com.redhat, with the hope that this will be ok with RedHat and Eclipse
If it's not ok, and the com.redhat name simply can't be used (even along side org.eclipse), then the Eclipse Foundation will effectively be forcing the compatibility break and putting a stop to a maintenance release. The thing is, I have no idea if that is a concern of theirs or not.
John Vasileff
@jvasileff
Regarding the Eclipse Foundation, although I am a committer, I have no knowledge of outstanding issues with regards to Ceylon being in incubation. And, we've never had a release under the Eclipse Foundation name, so there may be a number of details to work out.
It would be extremely helpful if someone who is currently a committer would take the initiative to find out where we are in the incubation process and help find out what we need to do administratively for a release (along with infrastructure issues, etc.)
Wojciech Potiopa
@Voiteh
Could we break out from eclipse foundation if none above will work?
John Vasileff
@jvasileff
1) It is open source, 2) I have no idea about trademarks, 3) personally, I have no interest at all in forking the project, I just want to help create a maintenance release.
Pedro Lamarão
@pedrolamarao
This document:
https://projects.eclipse.org/projects/technology.ceylon/reviews/creation-review
Says, in section "Project Scheduling":
The initial contribution will arrive in Q2, 2017, with a first release soon after. It is unclear whether the first release will be named 1.3.3, or 1.4.0. (The Eclipse requirements with respect to package naming might require a break to binary compatibility, thus resulting in a bump to the minor version number.)
There is no evidence of complicated "intellectual property" movements.
John Vasileff
@jvasileff
Ah yeah, I guess that's where I read about package name concerns
I believe the IP is fine - at least everything in the official Eclipse Foundation git repos. That part is done, but I don't know what additional standards have to be met to make a release
Or even how to make a release
Roland Tepp
@luolong
Yeah, looking at this, let’s do the baby steps now and roll back the package renaming for 1.3.4 release
The how part is still unclear to me. I think latest releases were handled by @quintesse or @FroMage
John Vasileff
@jvasileff
Much (most?) of what was done in the past is documented here: https://github.com/eclipse/ceylon/blob/master/dist/RELEASE.md, but we do need to figure out what to do with the infrastructure (herd, js web ide) which I don't have admin privs for (and don't want admin privs for!), and we probably need entirely new procedures for making Eclipse Foundation releases.
The biggest unknown is probably the Eclipse Foundation stuff, so it would be great if someone could take on the role of coordinating with them, and finding out what must be done for us to make a release
Pedro Lamarão
@pedrolamarao
I'm intent on experimenting the build instructions for Ceylon SDK. Is there a usable alternative to the Docker steps? Is Docker mandatory?
John Vasileff
@jvasileff
You just need to run ant publish, ant test, and the like, as in the readme https://github.com/eclipse/ceylon-sdk
But if you are using Ceylon 1.3.3, you'll need to checkout 1.3.3 compatible code - the master branch is not compatible
The tag _old/1.3.3-branching should probably work
Pedro Lamarão
@pedrolamarao
OK, I'm setting things up and documenting my steps.
John Vasileff
@jvasileff
I'm sure I'm missing some of the problems you are running into, but there shouldn't really be anything to set up to compile the SDK beyond what you are doing for your own projects. The SDK is just a regular Ceylon project. Even commands like ceylon compile and ceylon test should work.
IIRC, the only SDK module with any special support from the language is ceylon.test. The rest are just standalone modules that happen to use the ceylon namespace.
Pedro Lamarão
@pedrolamarao
I tried following the initial steps on a Windows 10 system command prompt yesterday and did not succeed. I'll set up a Linux system soon to try again.
John Vasileff
@jvasileff
Are you trying to build all of Ceylon, or just the Ceylon SDK GitHub project?
Pedro Lamarão
@pedrolamarao
I'm attempting to follow https://github.com/eclipse/ceylon/blob/master/dist/RELEASE.md, yes.
The first bits.
John Vasileff
@jvasileff
Oh, I see. So that's Ceylon itself, not the SDK.
I wouldn't follow those particular directions, that's for making public releases.
Pedro Lamarão
@pedrolamarao
ant dist succeeds but ant sdk fails
John Vasileff
@jvasileff
Instead, look at the README
Pedro Lamarão
@pedrolamarao
The first failure I could spot is a .bat file not found.
John Vasileff
@jvasileff
I think ant sdk just does basically cd ../ceylon-sdk && ant publish or something
Pedro Lamarão
@pedrolamarao
I have WSL on a development machine, maybe the procedure on Linux is good.
John Vasileff
@jvasileff
https://github.com/eclipse/ceylon/blob/master/dist/BUILD.md rather than RELEASE.md
I'd be slightly surprised if everything didn't work on Windows, but yeah, a Unix-like environment would definitely work. I've only built on Mac and Linux
Pedro Lamarão
@pedrolamarao
I'll retry soon.
John Vasileff
@jvasileff
You can also use the script I put together for GitHub Actions as a reference
Pedro Lamarão
@pedrolamarao
Thanks!
John Vasileff
@jvasileff
Sure, good luck!
Wojciech Potiopa
@Voiteh
i was not able to buld dist on windows switching to linux solved issues
John Vasileff
@jvasileff
I’ll look into adding Windows to the CI build matrix next week. We certainly need it at least to run tests
Pedro Lamarão
@pedrolamarao
Master ant dist built without errors on WSL Debian (oracle jdk 7, ant 1.9) here.
Pedro Lamarão
@pedrolamarao
_old/version-1.3.3 has errors on WSL Debian (oracle jdk 7, and 1.9) here.
Wojciech Potiopa
@Voiteh
@jvasileff can You take a look on #7460 some of commits are labeled with ! can You check them I don't seem to understand everything there. I'm in 1/3 of the list...
fill0llif
@fill0llif
I'm trying to follow what's on https://github.com/eclipse/ceylon/blob/master/dist/BUILD.md but trying to clone the repository I'm having this error
error: RPC failed; curl 18 transfer closed with outstanding read data remaining fatal: the remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed
What happened?
fill0llif
@fill0llif
Wojciech Potiopa
@Voiteh
If anyone could give me a hand here eclipse/ceylon#7460 we could finish before end of march
There is 115 commits left