fromage / ceylon-obr-test Goto Github PK

@corbinu originally created at Sat, 28 Sep 2013 23:53:15 GMT in ceylon/ceylon-dist#30:

The Java 8 Developer Preview has been released. It would be good if ceylon could be run even if somebody if somebody had updated their Java to try the developer preview

Originally created at Thu, 23 Aug 2012 10:37:53 GMT in ceylon/ceylon-common#13:

$ ../../ceylon-dist/dist/bin/cey compile 
cey compile: Argument modules should appear at least 1 time(s)atlantis stephane 12:36 collection $

Also note that we don't only accept modules but also file names

@krutm originally created at Wed, 14 Dec 2011 11:24:08 GMT in ceylon/ceylon-dist#2:

Modified build.xml so that it uses modules's dist target instead backpublish.
This makes sure that produced artifacts are compiled and produced inside each module instead duplicated inside ceylon-dist build directory.

Added a simple distribution .zip file as well.
Next step is fixing shell files to make sure they work OOB for client.

@krutm originally created at Wed, 21 Dec 2011 12:57:08 GMT in ceylon/ceylon-dist#6:

Tools/buildsources allows to create a clean source distribution repository out of existing git tag.
Main usage is for cutting releases by RM bypassing github's tarball/zipball limitations.

Originally created at Mon, 20 Aug 2012 12:21:59 GMT in ceylon/ceylon-common#11:

The bash completion is very ugly at the moment. It really needs someone with a lot more bash skills then I have to improve it. In particular there's lots of ugliness due to the way = (think long option arguments) is one of the $COMP_WORDBREAKS, which git manages to work around via majik which I don't entirely understand.

@krutm originally created at Wed, 14 Dec 2011 11:54:12 GMT in ceylon/ceylon-dist#3:

Use top-level directory to having the same name as distribution artifact

@krutm originally created at Tue, 20 Mar 2012 09:32:02 GMT in ceylon/ceylon-dist#10:

Originally created at Fri, 15 Jun 2012 00:49:04 GMT in ceylon/ceylon-dist#14:

@krutm originally created at Tue, 20 Dec 2011 18:56:47 GMT in ceylon/ceylon-dist#5:

Initial file. Will need more work, eg. support /etc/alternatives, etc.

Originally created at Thu, 02 Aug 2012 10:06:08 GMT in ceylon/ceylon-common#6:

Currently passwords can only be stored in plain text. We can easily do a couple of things to make this situation less dire:

1. Provide a way to prompt the user for the password for a particular repo. On the command line we can prompt via the console. In the IDE we'd need to be able to plug in a SWT password dialog.
2. Once we can prompt for passwords, it's not too difficult to store encrypted passwords in the config file. We could have an [encryption] section for the algorithm parameters and prompt for the decryption password when the system needs to access a password that is encrypted.

Originally created at Tue, 13 Mar 2012 15:24:09 GMT in ceylon/ceylon-dist#9:

• close all M2 issues in ceylon-spec (Stef)
• close all M2 issues in ceylon.language (Tako)
• find new parts of ceylon.language that weren't there in M1 (Tako)
• close all M2 issues in ceylon-module-resolver (Stef)
• close all M2 issues in ceylon-compiler (all of us)
• test the new parts of ceylon.language that weren't there in M1 (all of us)
• make sure these parts are documented (Enrique, Stef)
• update the website docs for M2 features (Tom, Stef)
  • Docs for type mapping (Stef)
  • Docs for interop: calling Java from Ceylon (Stef)
  • Docs for interop: calling Ceylon from Java (Stef)
  • Docs for repositories (Stef)
  • Docs for Maven interop (Stef)
  • Missing reference pages (Tom)
• deal with Google Analytics (Stef)
• Add build.xml samples (Stef)
• package the release (Stef)
• test on OSX, Linux, Windows (Stef/Tako:Windows and Linux)
• update the website for the release
• deal with the annoucements (Stef)
• do the release (Stef)

@unratito originally created at Wed, 16 Oct 2013 07:54:03 GMT in ceylon/ceylon-dist#31:

It seems that GitHub doesn't recommend using Git protocol anymore:

https://help.github.com/articles/which-remote-url-should-i-use

I guess that's because Git protocol is usually blocked by firewalls in corporate environments.

Maybe we should replace "git://" with "https://" in build.xml.

Originally created at Tue, 23 Oct 2012 10:34:07 GMT in ceylon/ceylon-dist#23:

The NOTICE file included with the dist need updating for M4, to include the license for all the transitive dependencies needed for the command line tools

Originally created at Mon, 23 Apr 2012 13:36:40 GMT in ceylon/ceylon-dist#11:

To show how to invoke Java code.

Originally created at Thu, 21 Jun 2012 11:37:16 GMT in ceylon/ceylon-dist#17:

Quoting @quintesse

we should have a special "dist" build that just pulls everything to a local folder instead of using sibling projects

Presumably it should clone repos if required (otherwise pull) into subdirectories. This would make it much simpler to know that you had a fully up to date build.

Originally created at Thu, 23 Aug 2012 10:40:57 GMT in ceylon/ceylon-common#14:

in the SDK's collection folder:

atlantis stephane 12:39 collection $ rm -rf modules/
atlantis stephane 12:39 collection $ ../../ceylon-dist/dist/bin/ceylonc ceylon.collection
atlantis stephane 12:39 collection $ rm -rf modules/
atlantis stephane 12:39 collection $ ../../ceylon-dist/dist/bin/cey compile ceylon.collection
[-src, source, -out, modules, ceylon.collection]
error: Unable to find class file for ceylon.language.String
/home/stephane/src/java-eclipse/ceylon-sdk/collection/source/ceylon/collection/makeCellArray.ceylon:2: error: type declaration does not exist or is ambiguous: Integer
Array<Cell<Key->Item>?> makeCellEntryArray<Key,Item>(Integer size) 
                                                     ^
/home/stephane/src/java-eclipse/ceylon-sdk/collection/source/ceylon/collection/makeCellArray.ceylon:2: error: ExpressionVisitor caused an exception visiting BaseType node: java.lang.NullPointerException at com.redhat.ceylon.compiler.typechecker.analyzer.ExpressionVisitor.defaultType(ExpressionVisitor.java:3857)
[followed by 100 errors]

That could be a tool issue, or a repo issue, so not sure if @quintesse or @tombentley is the target.

Originally created at Tue, 31 Jul 2012 17:39:17 GMT in ceylon/ceylon-common#4:

We should introduce the possibility of adding something like ${DIR} to a value that would be replaced with the current directory the config file lives in.

@allentc originally created at Thu, 19 Dec 2013 22:39:01 GMT in ceylon/ceylon-dist#35:

Small README.md correction

@charithccmc originally created at Sat, 24 Dec 2011 15:02:26 GMT in ceylon/ceylon-dist#7:

There have no ceylonc and ceylon man pages for Linux ( may be UNIX ). I was create two man pages but there are not completed . How I'm add that man pages to debian package ?

Originally created at Wed, 15 Aug 2012 13:36:04 GMT in ceylon/ceylon-common#8:

Currently a whole bunch of things each use their own logging:

• ceylon-module-resolver has its own Logger interface. Because everything else already does its own logging there are already with 7 implementations (delegating to JUL, System.err, javac Log, plus a couple of No-op loggers)
• ceylon-js seems to just write to System.err directly
• ceylon-runtime uses JUL, I think
• At some point there will be a ceylon.logging module.

It seems like ceylon-common is a good place to define a common API (and some implementations).

Originally created at Thu, 28 Jun 2012 11:26:07 GMT in ceylon/ceylon-dist#19:

It should be possible to rm -rf ~/.ceylon/repo then execute a ant siblings package (or similar) and have the build work. Right now it doesn't because:

1. The ceylon-dist/build.xml doesn't specify the dependencies
2. Most of the targets executed in siblings projects (in ceylon-dist/build.xml) use the dist target.

Put together this means we're happily building ceylon-compiler (in ceylon-dist) using a random version of CMR (or whatever dependency) from the last time we happened to run the publish target in CMR, because ceylon-compiler compiles against the published CMR jar.

Before I fix this I want to know whether the distinction between 'publish' and 'dist' really needs to be kept.

@akberc originally created at Mon, 09 Sep 2013 15:37:42 GMT in ceylon/ceylon-dist#28:

Change build IDE task so that -

• it does not copy jars to IDE /lib - after confirming that it is OK to remove them
• copies /repo, minus docs, into IDE/plugin/...ui/defaultRepository

Originally created at Mon, 25 Feb 2013 19:47:40 GMT in ceylon/ceylon-dist#26:

Because of a size limitation in the Windows "shell" the build can't process the large number of files it needs to pass to the compiler.

The solution currently chosen to work around this is to use a special class loader that knows how to set up a correct Ceylon environment (libraries + repository). This way we can circumvent having to use shell execution and we can execute the compiler in-process from ant.

Originally created at Thu, 23 Aug 2012 10:19:00 GMT in ceylon/ceylon-common#12:

$ dist/bin/cey -version
cey: Unrecognised option(s): [-version, -version, -version, -version, -version, -version, -version]atlantis stephane 12:14 ceylon-dist $

Note that it also forgot to add a new line

Originally created at Wed, 17 Oct 2012 08:26:52 GMT in ceylon/ceylon-dist#21:

@russel originally created at Wed, 13 Nov 2013 19:22:17 GMT in ceylon/ceylon-dist#33:

MacPorts needs to be given a port file for Ceylon so that OSX people can use MacPorts instead of HomeBrew.

@stephanethomas originally created at Mon, 25 Feb 2013 17:43:10 GMT in ceylon/ceylon-dist#25:

Hello,

I'm trying to build the M5 unstable package on Windows 7 64 bits, but the Ant process fails. I first execute ant local get-code, then I do ant local package but the following error is raised:

ceylon.language.java:

BUILD FAILED
E:\Tools\ceylon\ceylon-dist\build.xml:302: The following error occurred while executing this line:
E:\Tools\ceylon\ceylon-dist\projects\ceylon.language\build.xml:181: Failed to find 'ceylon' executable in E:\Tools\ceylon\ceylon-dist\projects\ceylon.language\..\ceylon-dist\dist\bin\ceylon.bat

Total time: 29 seconds

Originally created at Wed, 16 Oct 2013 22:38:21 GMT in ceylon/ceylon-dist#32:

Turn as much of the JARs we have in the distribution lib folder into proper modules

Originally created at Thu, 21 Jun 2012 21:34:37 GMT in ceylon/ceylon-dist#18:

@proofit404 originally created at Tue, 05 Mar 2013 13:07:06 GMT in ceylon/ceylon-dist#27:

I install ceylon nightly build on two boxes with different path to the distribution. And I can't build my project on second box if it was create with first box. Because "ceylon.home" property hardcoded into ant project as absolute system path. Also I cant find com.redhat.ceylon.ant-0.5.jar on my system anywhere. But its work with ceylon-ant.jar just fine.

Please, replace following code:

<property name="ceylon.home" value="@[ceylon.home]"/>
<property name="ceylon.ant.lib" value="${ceylon.home}/repo/com/redhat/ceylon/ant/@[ceylon.version.number]/com.redhat.ceylon.ant-@[ceylon.version.number].jar"/>

with this one

<property environment="env"/>
<fail unless="env.CEYLON_HOME" message="Environment variable $CEYLON_HOME isn't set."/>
<property name="ceylon.home" value="${env.CEYLON_HOME}"/>
<property name="ceylon.ant.lib" value="${ceylon.home}/lib/ceylon-ant.jar"/>

Originally created at Tue, 20 Nov 2012 16:48:27 GMT in ceylon/ceylon-dist#24:

I just tried building a distrib and got that:

generate-tooldoc:
     [exec] ceylon doc-tool: Fatal error: Method public void com.redhat.ceylon.compiler.js.
     [exec] CeylonRunJsTool.setNodeExe(java.lang.String) is annotated with @Argument and
     [exec] @Description: Arguments should be documented in the class-level @Description
     [exec] com.redhat.ceylon.common.tool.ModelException: Method public void com.redhat.ceylon.compiler.js.CeylonRunJsTool.setNodeExe(java.lang.String) is annotated with @Argument and @Description: Arguments should be documented in the class-level @Description
     [exec]     at com.redhat.ceylon.common.tool.ToolLoader.buildArgument(ToolLoader.java:377)
     [exec]     at com.redhat.ceylon.common.tool.ToolLoader.addMethod(ToolLoader.java:179)
     [exec]     at com.redhat.ceylon.common.tool.ToolLoader.loadModel(ToolLoader.java:117)
     [exec]     at com.redhat.ceylon.common.tool.ToolLoader.loadToolModel(ToolLoader.java:83)
     [exec]     at com.redhat.ceylon.tools.help.CeylonDocToolTool.loadModels(CeylonDocToolTool.java:162)
     [exec]     at com.redhat.ceylon.tools.help.CeylonDocToolTool.run(CeylonDocToolTool.java:152)
     [exec]     at com.redhat.ceylon.tools.CeylonTool.run(CeylonTool.java:216)
     [exec]     at com.redhat.ceylon.tools.CeylonTool.bootstrap(CeylonTool.java:185)
     [exec]     at com.redhat.ceylon.tools.CeylonTool.main(CeylonTool.java:159)

Looks like a job for @tombentley or @chochos

@Spacelag originally created at Sun, 17 Jun 2012 22:28:25 GMT in ceylon/ceylon-common#2:

Fixes Issue #37 by updating build.xml to create/delete build and build/classes

Originally created at Mon, 06 Aug 2012 09:47:54 GMT in ceylon/ceylon-common#7:

As a prerequisite for ceylon/ceylon-module-resolver#38, we need a configuration section for proxies

Originally created at Mon, 20 Aug 2012 12:20:51 GMT in ceylon/ceylon-common#10:

Improve the cey script so if there is no Java tool corresponding to cey foo (which we can tell from the exit code), we try to run cey-foo.

At the moment the Java top level tool (Tool) prints out a list of possible tool names in this situation before exiting. This is nice functionality, but we don't really want it to start looking at $PATH, to try to figure out other suggestions, do we? I guess the alternative would be to leave that to the script, which could get a list of the nearly-matching Java tools by calling another low-level tool.

Originally created at Tue, 19 Jun 2012 20:11:46 GMT in ceylon/ceylon-dist#16:

So they work in JS

Originally created at Wed, 02 May 2012 09:52:50 GMT in ceylon/ceylon-dist#12:

Several people complained that building Ceylon is quite complex, what with the myriad of sub-projects we have. We should think about how to address this, as we don't want to scare away contributors.

Originally created at Tue, 31 Jul 2012 17:09:48 GMT in ceylon/ceylon-common#3:

S.O.

@Spacelag originally created at Sun, 17 Jun 2012 22:21:34 GMT in ceylon/ceylon-common#1:

The clean task deletes "${build}" instead of "${build.dir}" and the compile task does not ensure that "${build.classes}" exists.

Originally created at Fri, 17 Aug 2012 09:33:57 GMT in ceylon/ceylon-common#9:

That's just not thread-safe at all. We can have multiple instances of the compiler/tools running on the same jvm.

Originally created at Tue, 23 Oct 2012 08:37:40 GMT in ceylon/ceylon-dist#22:

There's at least one guy on Herd, but I'm sure we have more.

Originally created at Mon, 12 Dec 2011 21:12:37 GMT in ceylon/ceylon-dist#1:

We now urgently need an Ant build that packages up the:

1. typechecker, compiler, language module, and runtime, along with
2. working cross-platform ceylonc, ceylond, and ceylon shell scripts,
3. some kind of install script for creating a default repo containing the language module, and
4. an examples directory containing a hello world module, with
5. a README with info on how to compile and run the module, and where to go (the website) for documentation.

This is now the main missing piece blocking an M1 release.

Originally created at Wed, 15 Feb 2012 18:31:39 GMT in ceylon/ceylon-dist#8:

Originally created at Mon, 09 Sep 2013 17:39:48 GMT in ceylon/ceylon-dist#29:

@krutm originally created at Wed, 14 Dec 2011 16:05:00 GMT in ceylon/ceylon-dist#4:

This is for compiler patch .in files where produced files are in build directory now.

@IvanKokhan originally created at Fri, 25 May 2012 11:00:54 GMT in ceylon/ceylon-dist#13:

I downloaded yesterday, ceylon-0.2, and today tried to run the ceylonc on my WindowsXP system from the command line.

I have the next error message:

C:\ceylon-0.2\bin>ceylonc -help
"Cannot find java.exe at C:\dev\jdk1.7.0_03\jre7 \bin\java.exe, check that your
JAVA_HOME variable is pointing to the right place"

I revised *.bat files in bin directory and in java.bat file in line number 32 I found one unnecessary white space:

28 ::
29 :: get the javahome
30 ::
31 FOR /F "usebackq skip=2 tokens=3*" %%A IN (REG QUERY "%JAVA_CURRENT%" /v JavaHome 2^>nul) DO (
32 set "JAVA_HOME=%%A %%B"
33 )

need: set "JAVA_HOME=%%A%%B"

after this change ceylonc is working successfully.

Originally created at Fri, 06 Jul 2012 13:14:44 GMT in ceylon/ceylon-dist#20:

So far we've made up the release process as we've gone along, and @FroMage is good at remembering all the things which need to be done. but one day he might not be available. So we need a simple checklist of all the things which need to be done to do a release.

We should get @gavinking to check the list once @FroMage has written it too.

Originally created at Wed, 22 Jan 2014 12:01:27 GMT in ceylon/ceylon-dist#36:

This should include merging master and branches and rewritiing commit messages to change #NNN into `ceylon/ceylon-xxxx#NNN´.

Originally created at Mon, 25 Nov 2013 16:57:41 GMT in ceylon/ceylon-dist#34:

In Homebrew/legacy-homebrew#24176 it was suggested we change the Java 7 caveat into a Requirement as per Homebrew/legacy-homebrew#24105.

We also should manage man pages.

This is for @gavinking as he has OSX and brew.

Originally created at Mon, 18 Jun 2012 16:35:44 GMT in ceylon/ceylon-dist#15:

Sure we can speed that up :)

Originally created at Tue, 31 Jul 2012 17:57:32 GMT in ceylon/ceylon-common#5:

This Writer should be able to be its output on an existing configuration file and leave that file as much as possible the same as it was, only removing items that don't exist anymore, adding new items to the end and replacing values leaving white space and comments intact!