Ceylon config resolved values in build
83 views
Skip to first unread message
Akber Choudhry
Jun 24, 2014, 9:43:23 PM6/24/14
to ceylo...@googlegroups.com
I had the opportunity to build on a clean Windows machine that has a tiny C: SSD drive and a much larger E: drive. On such machines, I do various things to save space. For example, the local maven repo is E:\work\m2 and only the settings.xml file in ~/.m2
Similarly, I could place the Ceylon repos on the E: drive and Ceylon command-line tools use the ceylon-common config resolver to resolve the various repos (user, cache, etc.) and that works well.
However, it appears that build scripts do not take advantage of reading the resolved config values while *producing* modules. It would be useful if an ant task could read the resolved global config and set the repo roots for the various repos needed during build, primarily 'cache' and 'user'. Also, it could read the global proxy values and set them for the right tasks -- as git needs a different environment variable for proxy and the Ceylon tools need something else.
It would be great if the ceylon global or user config was honoured throughout the build process. Is it preferable to have something like that?
Similarly, I could place the Ceylon repos on the E: drive and Ceylon command-line tools use the ceylon-common config resolver to resolve the various repos (user, cache, etc.) and that works well.
However, it appears that build scripts do not take advantage of reading the resolved config values while *producing* modules. It would be useful if an ant task could read the resolved global config and set the repo roots for the various repos needed during build, primarily 'cache' and 'user'. Also, it could read the global proxy values and set them for the right tasks -- as git needs a different environment variable for proxy and the Ceylon tools need something else.
It would be great if the ceylon global or user config was honoured throughout the build process. Is it preferable to have something like that?
Akber Choudhry
Jun 25, 2014, 12:12:10 PM6/25/14
to ceylo...@googlegroups.com
On further exploration, there may be two options to avoiding the fixed ${user.home}/.ceylon/repo for publishing compiled modules:
- A custom task that sets the required properties in the Ant project, such as 'ceylon.user.repo', 'ceylon.cache.repo', 'ceylon.proxy.host' etc. Then the copy task can consume these properties.
- A repo-aware copy task that extends RepoUsingCeylonAntTask and has fixed values for to.
Thoughts?
Tako Schotanus
Jun 25, 2014, 1:15:16 PM6/25/14
to ceylon-dev
Well actually, I'm surprised that the Ant tasks don't use the configuration settings!
I haven't tested it yet so I'll trust you for now :) It might just be a bug.
When I finish what I'm doing now I'll take a look at it, okay?
-Tako
To view this discussion on the web visit https://groups.google.com/d/msgid/ceylon-dev/4559854c-517c-46c3-a306-390a17e57f31%40googlegroups.com.--
You received this message because you are subscribed to the Google Groups "ceylon-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ceylon-dev+...@googlegroups.com.
To post to this group, send email to ceylo...@googlegroups.com.
Visit this group at http://groups.google.com/group/ceylon-dev.
Akber Choudhry
Jun 25, 2014, 1:53:19 PM6/25/14
to ceylo...@googlegroups.com, ta...@codejive.org
No rush, was just investigating.
I've closed one issue today as not being an issue, so please double-check :)
I've closed one issue today as not being an issue, so please double-check :)
Tako Schotanus
Oct 4, 2014, 3:22:19 PM10/4/14
to ceylon-dev
For the longest time I had this in my mail back-log without really understanding what it was about, sorry about that!
Just created these two related issues for it:
-Tako
To view this discussion on the web visit https://groups.google.com/d/msgid/ceylon-dev/ea8b7198-9006-4e42-9cbb-63273b4b4498%40googlegroups.com.
Akber Choudhry
Oct 7, 2014, 10:30:46 AM10/7/14
to ceylo...@googlegroups.com
No worries. If I have time I may create some pull requests as I have a PC that can really use this.
Tako Schotanus
Nov 5, 2014, 1:21:51 PM11/5/14
to ceylon-dev
Akber, I just implemented https://github.com/ceylon/ceylon-compiler/issues/1839 but I'm still trying to figure out how to best handle the actual build issue (https://github.com/ceylon/ceylon-dist/issues/44).
-Tako
On Tue, Oct 7, 2014 at 4:30 PM, Akber Choudhry <ak...@dgwave.com> wrote:
No worries. If I have time I may create some pull requests as I have a PC that can really use this.
--
You received this message because you are subscribed to the Google Groups "ceylon-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ceylon-dev+...@googlegroups.com.
To post to this group, send email to ceylo...@googlegroups.com.
Visit this group at http://groups.google.com/group/ceylon-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/ceylon-dev/427f3ca3-65c5-49ec-968b-ff81bb05edf0%40googlegroups.com.
Akber Choudhry
Nov 5, 2014, 10:42:33 PM11/5/14
to ceylo...@googlegroups.com, ta...@codejive.org
Thank you.
If I understand what you are trying to figure out, the config query would probably need to be in each individual project build.xml
If I understand what you are trying to figure out, the config query would probably need to be in each individual project build.xml
Tako Schotanus
Nov 6, 2014, 4:27:47 AM11/6/14
to ceylon-dev
Exactly, but the ant lib is part of the compiler project which is built before it's needed. So I'd have to reorganize the build by moving that build somewhere else and then make all other builds depend on it. It's quite a bit of work which I'm not sure is worth it. We could probably much easier let you pass a -Dceylon.publish.dir=/foo/bar to ant than go through all that trouble. But I'm still thinking about it ^^
-Tako
To view this discussion on the web visit https://groups.google.com/d/msgid/ceylon-dev/a0b08bbe-a759-42e3-ba7b-5c648a5a3a8a%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages