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

Dynamic metamodel set up #6847

Closed
FroMage opened this issue Jan 4, 2017 · 8 comments
Closed

Dynamic metamodel set up #6847

FroMage opened this issue Jan 4, 2017 · 8 comments

Comments

@FroMage
Copy link
Contributor

@FroMage FroMage commented Jan 4, 2017

Auto-configure the metamodel if it's not configured by jboss modules or manually. This is required to run Ceylon modules as normal Java jars in Java programs.

@FroMage
Copy link
Contributor Author

@FroMage FroMage commented Jan 23, 2017

This is fixed. I'll open new issues for further improvements when/if they come up. Such as supporting discoverability.

@FroMage FroMage closed this Jan 23, 2017
@gavinking
Copy link
Member

@gavinking gavinking commented Jan 23, 2017

Fantastic!!!

@quintesse
Copy link
Contributor

@quintesse quintesse commented Jan 23, 2017

Great job Stef!
And "discoverability"? What would that be exactly?

@FroMage
Copy link
Contributor Author

@FroMage FroMage commented Jan 23, 2017

Listing packages and classes.

@DiegoCoronel
Copy link
Contributor

@DiegoCoronel DiegoCoronel commented Jan 23, 2017

Nice !!! This looks a really important improvement \o/ ... maybe it would be good to have this explained in blog and how it affects/improve java integration (its not clear to me how can I make use of this feature)

@quintesse
Copy link
Contributor

@quintesse quintesse commented Jan 23, 2017

@FroMage are we now supposed to be able to run without the Main API as explained in https://ceylon-lang.org/documentation/reference/interoperability/ceylon-on-jvm/#using_the_main_api ?

I tried it with a simple test program that just prints out some simple meta model stuff and that works fine without the Main API, but if I try to access a resource I get:

Exception in thread "main" java.lang.NullPointerException
	at com.redhat.ceylon.compiler.java.runtime.metamodel.decl.ModuleImpl.resourceByPath(ModuleImpl.java:166)
	at hello.restestRelative_.restestRelative(hello.ceylon:30)
	at hello.run_.run(hello.ceylon:36)
	at hello.run_.main(hello.ceylon)

Is that a bug I need to open an issue for or am I doing something wrong here?

Btw, another thing I'm seeing when using the Main API is this warning, not sure if it's important now:

Jan 23, 2017 3:09:08 PM com.redhat.ceylon.cmr.impl.Configuration getResolver
WARNING: Cannot add resolver com.redhat.ceylon.cmr.maven.MavenDependencyResolver - java.lang.NoClassDefFoundError: com/redhat/ceylon/cmr/resolver/aether/AetherException
@FroMage
Copy link
Contributor Author

@FroMage FroMage commented Jan 23, 2017

but if I try to access a resource I get:

Can you open an issue? Likely a bug.

Btw, another thing I'm seeing when using the Main API is this warning, not sure if it's important now:

That's because the module is optional. If you want it you have to add a hard dep on it.

@quintesse
Copy link
Contributor

@quintesse quintesse commented Jan 23, 2017

Can you open an issue? Likely a bug.

Ok

That's because the module is optional. If you want it you have to add a hard dep on it.

It's more the other way around: I don't want it so I also don't want to see any warnings (by default).

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

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.