JBossDeveloper

That's a good question, and this gets into the subject of different levels of build artifacts. The only context I have looked at a component element is for this simple thirdparty structure creation from the repository. What your talking about is a much higher level artifact in the top level build structure. My mind cannot make a jump from a simple hibernate.jar depends on cglib.jar to the fact that there is a deploy/jboss-hibernate.deployer with these jars inside. The cglib.jar may need to be in the deployer, or it may need to be in the server lib directory to be shared across all contexts. This is at least two level removed from the simple dependency. The first level is where the jboss-hibernate.deployer artifact is defined. The next level is how this artifact integrates into the jbossas release structure.

If we are going to get to the level of generating an IzPack build target for jbossas based on its component dependencies, composition of components as well as mapping of their artifacts into containing components needs to be figured out. I'm not there yet.