Are you trying to share with the community some jbpm3 improvements?
What are those improvements doing? You cannot just upload the binaries and share that. You usually create a jira issue in jira.jboss.org that describe the problems and the improvements and attach a patch to solve them. Then one of the people responsible to maintain jbpm3 will review your patch and I everything is ok, he will merge that with the latest source code.
Thanks for your answer.
I think what I want to do is to improve jbpm3 without changing the source code(http://code.google.com/p/jbpm-guice/). So to speak I tried to use the process.class.loader.factory to actually replace the jbpm class instantiation mechanism without the need to change the core source code. However, my initial question and thus my assumption that it is not possible to upload jar's to the meaven central repo that have transitive dependencies that are not in the maven central repo (e.g. jbpm3-jpdl) was wrong. It seems to be okay to add the jboss repo to your artefact. I could upload my artifact to the maven central repo and have now the dependency