Hi Thomas, The resources stuff in thirdparty is a temporary solution to handling the resources directories from the buildmagic repository. I implemented a new feature to my plugin (http://labs.jboss.org/maven-buildmagic-thirdparty-plugin) that will now find a resources directory (in a buildmagic component directory), put it into a jar, and deploy it to the maven repository with the artifactId "resources". Then the build-thirdparty part of the plugin will download the resources artifact and extract it to the correct place in the thirdparty directory. I'm updating the plugin site today with some more information about how to use this. As far as deploying your releases to the maven repository, you have a few choices: You can use the buildmagic thirdparty plugin to upload the buildmagic format of the release (http://www.jboss.org/maven-buildmagic-thirdparty-plugin/examples/example-...) You can use the deploy-file goal of the standard maven deploy plugin to upload jar files with any associated poms (http://maven.apache.org/plugins/maven-deploy-plugin/usage.html) Or you can use the maven ant tasks in an ant script (http://maven.apache.org/ant-tasks.html). You will want to use the <artifact:deploy> task. With any of these, just make sure you deploy to the correct location in the maven repository. For non-mavenized projects you can just translate: componentId --> groupId lib/artifactId --> artifactId Otherwise use something like "org.jboss.<project>" for the groupId. Hope this helps! Thomas Diesler wrote: > Hi Paul, > > I see you committed a number of artifacts to > > https://svn.jboss.org/repos/jbossas/trunk/thirdparty/src/main/resources/j... > > > What is the rational behind that? Who is going to maintain these > artifacts and how do they relate to a given version in the maven > repository? > > Could you please explain how do you expect us to release artifacts to > the maven repository (including the the ones above)? > > cheers > -thomas >

Hi Paul, my surefire tests need to have dependencies on jboss build artifacts that end up in ${jboss.home}/client. These are for example * jboss-client.jar * jmx-client.jar * jmx-invoker-adaptor-client.jar snapshots of these artifacts don't seem to get deployed to the repository. I case I don't have not overseen where these jars get deployed to, I would add them to the repo. More generally, I suggest that all build artifacts (that are not separate projects already) get deployed to the repository. cheers -thomas xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx