I have one other question (probably related) Can we have a dependency tree? I would like to see what component is dependent on what component (jar, version, etc...) Anyone knows if there is some tool for discovering that, and I'll create a graph or even a simple database with updatability per version/tag. I know this is boring thing, but I have never saw how JBossAS actually 'looks like' on paper. (If you don't count marketing slides from Shaun :) Regards, Mladen. Adrian wrote: > The sooner we move to maven the better for JBossAS. > At least then you can get reports to find out how where > things are coming from. > > Question: Do you know who decides the version of wsdlj we > use in JBossAS? > Even though it is a direct dependency of the main "server" project. > It's in its classpath! > > Answer: JBossWS. > > We don't express that dependency directly, we inherit > it from a chain of imports in jbossws-* projects > in the repository.jboss.com definition. > > I wonder how many other brittle dependencies > like this there are? _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development