Skip to content
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

Open
DiegoCoronel opened this issue Oct 6, 2015 · 9 comments
Open

Support non-jar maven artifacts #127

DiegoCoronel opened this issue Oct 6, 2015 · 9 comments
Labels
Milestone

Comments

@DiegoCoronel
Copy link
Member

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.

@FroMage FroMage added the FEATURE label Oct 6, 2015
@FroMage FroMage added this to the 1.3 milestone Oct 6, 2015
@FroMage
Copy link
Member

FroMage commented Oct 6, 2015

Apparently that's a module with no jars but lots of dependencies.

@DiegoCoronel
Copy link
Member Author

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.

@FroMage
Copy link
Member

FroMage commented Oct 6, 2015

Well, it can always go in 1.2.1.

@jvasileff
Copy link
Member

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 imports should exist that forces auto-sharing of maven transitive dependencies. Such a feature would have the dramatic impact of making many things work today that don't. (Conflict resolution would of course still be necessary in some cases, but would be less of a challenge.)

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.

@FroMage
Copy link
Member

FroMage commented Nov 3, 2015

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.

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.

@jvasileff
Copy link
Member

Actually, spring-boot-starter-web does have a jar.

@FroMage
Copy link
Member

FroMage commented Nov 3, 2015

Ah, that's not what we figured at the time, weird.

@DiegoCoronel
Copy link
Member Author

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

No branches or pull requests

3 participants