-
1. Re: Eap 6.1 Alpha Runntime - Libraries not included
We see the same problem here with 4.2.0.a2 B6241 and B6288
I was letting the runtime use its default, standalone.xml.
The developers see the same problem when trying a standalone-full.xml setup.
RH: any idea of when this runtime will become fully usable? We have started working on our EAP6.1 migration, and this is rather annoying.
Thanks,
Jesper
PS: EAP60 runtime does include jars, but I've not tested that it actually adds jars for modules we enable in the standalone.xml - but I assume that's how it is supposed to work
-
2. Re: Eap 6.1 Alpha Runntime - Libraries not included
Genn Pusch schrieb:
Can i even fix it?
It seem that I can.
By navigating to "Server -> Runtime Enviroments -> Default Classpath Entires" and selecting "Jboss Enterprise Application Platform 6.x Runtime" I replaced the listed paths with the correct ones and it worked again.
No sure what will happen if I update the Plugin again though.
-
3. Re: Eap 6.1 Alpha Runntime - Libraries not included
I have just tried 4.1.0.alpha2 and it has the same problem.
If I look in "Default Classpath Entries" it is empty for the EAP61 platform.
And if I try to add something (like, modules/system/layers/base/**/*.jar) I'm then unable to add the server runtime to project build paths.
Oh, I also tried creating a JBoss 7.1 server that points to the EAP61 beta - as suggested by Max in the release note, if I understand it correctly.
It complains about missing "modules/org/jboss/as/server/main" and also ends up empty.
-
4. Re: Eap 6.1 Alpha Runntime - Libraries not included
AFAIK, this was supposed to be in fixed in 4.1 of JBoss Tools and it was supposed to be functional against EAP 6.1 https://community.jboss.org/en/tools/blog/2013/03/12/lets-go-to-kepler
-
5. Re: Eap 6.1 Alpha Runntime - Libraries not included
jaikiran pai wrote:
AFAIK, this was supposed to be in fixed in 4.1 of JBoss Tools and it was supposed to be functional against EAP 6.1 https://community.jboss.org/en/tools/blog/2013/03/12/lets-go-to-kepler
That particular fix appears to have run out of steam on its way across the atlantic, crashing before reaching shore.
Do you want me to report a bug?
-
6. Re: Eap 6.1 Alpha Runntime - Libraries not included
I don't have much knowledge of JBoss Tools. Let's wait for some more time to hear from someone who knows more - it's a holiday today in some parts of the world so responses might be slow and might even take a day.
-
7. Re: Eap 6.1 Alpha Runntime - Libraries not included
Jesper Skov schrieb:
I have just tried 4.1.0.alpha2 and it has the same problem.
If I look in "Default Classpath Entries" it is empty for the EAP61 platform.
And if I try to add something (like, modules/system/layers/base/**/*.jar) I'm then unable to add the server runtime to project build paths.
Oh, I also tried creating a JBoss 7.1 server that points to the EAP61 beta - as suggested by Max in the release note, if I understand it correctly.
It complains about missing "modules/org/jboss/as/server/main" and also ends up empty.
Just in case. The striked trough part should not be part of the "Root Directory" when adding a path.
-
-
9. Re: Eap 6.1 Alpha Runntime - Libraries not included
I think I misunderstood the issue, but, in general, we have not yet added classpath support for EAP 6.1 or any AS-7.2 based server. The reasons are that we're being instructed by the server team that additional API will be created for us to get a proper classpath, and that we should not be reaching into the modules folder on our own. Please see https://issues.jboss.org/browse/JBIDE-13871
-
10. Re: Eap 6.1 Alpha Runntime - Libraries not included
OK, so we have to provide it ourselves for the time being. Thanks for clearing that up.