-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support non-jar maven artifacts #127
Comments
Apparently that's a module with no jars but lots of dependencies. |
I need to expose that I am very sorry that is very short notice to put in version 1.2, it can actually hinder the adoption I want to do in my business ... definitely no one will want to manage the dependencies of modules manually. |
Well, it can always go in 1.2.1. |
I suspect this has less to do with there being no jars, and more so with Ceylon not following the implicit contract with maven modules that transitive dependencies be exported. Perhaps a new annotation on module Alternately, @DiegoCoronel, as a practical matter, I've found that using gradle (or perhaps mvn) to create a single "fat" jar with all dependencies, then importing the fat jar as a Ceylon module, works when building applications. |
I really don't think so. The CMR is built to treat each module as having a jar/car file, and this one does not have one. |
Actually, |
Ah, that's not what we figured at the time, weird. |
My case was something like run this sample http://projects.spring.io/spring-boot/ as simple as maven does.
Theres lots of cases like that and migration or integration with maven projects to ceylon will be good for more adoption.
The text was updated successfully, but these errors were encountered: