maven-deploy goal should handle stand-alone poms and jars not listed in component-info -------------------------------------------------------------------------------------- Key: JBBUILD-547 URL: https://jira.jboss.org/jira/browse/JBBUILD-547 Project: JBoss Build System Issue Type: Feature Request Components: maven-buildmagic-thirdparty-plugin Reporter: Paul Gier Assignee: Paul Gier David asked for some new features to the plugin: I came across two other issues: 1.) Exporting a parent pom (or any pom type artifact with no corresponding jar). 2.) Exporting a jar that is not referenced in component-info.xml. In the case of jboss-deployers, jboss-deployers.pom is the parent pom. I put this in the repolib. It is not be referenced by component-info.xml (it's pom type only), so it doesn't get installed by the maven buildmagic plugin. I don't see that it's really necessary to consult component-info.xml. It could just look in the current directory for the files. If it finds a pom with no jar, it will export as a pom artifact, and if it finds a jar, it will export as jar artifact. There is another case we have where jboss-jca-spi.jar is not referenced by the jboss-integration component-info.xml, but every other jar is. In that case, everything got properly installed except for this jar that was left behind. I think it's correct that it didn't get written to the component-info.xml. It's not referenced directly by the AS. However, it must be referenced by the aprent, so it gets downloaded anyway. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira