[jboss-as7-dev] AS 7 stacktraces

[Max Rydahl Andersen]

>> 
>> I just assumed that all this were implemented already and thus the knowledge is available at least
>> at runtime ?
>> 
>> Or maybe that get "lost in translation" ?
> 
> Yes the BOM would point to the jars by maven coordinates, which would be the ones in the local repo. These would all be the same versions though as the ones in the actual AS tree.

Yes, but not necessarily the same as the one I got in my own patched/EAP/distro users have on their disc.

> The runtime information in the server is there but in modular runtime form. This is different from how a client / compile time view would be that is not using modules, which is just a flat list of jars on the classpath.

ok - and we can't deduce the "closest flat list of jars" from that representation ?

>> To be clear - the reason I need/want the *real* classpath is for two reasons:
>> 
>> 1) For users *not* using Maven
> 
> The best we can do here is expose a list, unless you have any other idea how to do it. We've also talked about changing the directory structure to have a separate place for "visible" things. You could use that but it would be a full superset of all deployment types.

Better than "nothing". Right now we only add one giant classpath for all project types in eclipse anyway, so it would just as "bad" as before.

would be good if could separate better though.

>> 2) To know for sure which jars are actually loaded.
> 
> I thought we were talking about compile time stuff (API jars only). Not actual implementation.

When you compile you need just the API jars, but
When you run unit tests you need implementation.

Both things you do from in your IDE :)

/max
http://about.me/maxandersen