On Thu, Aug 6, 2009 at 2:57 AM, bwarren<brad.war...@usairways.com> wrote: > > I have a Webstart application that I'm generating a WAR file to deploy on > JBoss using the Maven Webstart plugin. > > I have included the JBoss client POM in my application POM to grab the JBoss > client dependencies for JNDI and EJB. When the plugin creates the WAR file, > it is including the POM with unprocessed_ prepended to the file name. The > plugin is also putting the POM in as a jar dependency in the JNLP file. > > So when the JNLP download servlet goes to pull the JAR dependencies for my > webstart application, it tries to grab the POM, which has been renamed, and > fails. Does anyone know why that file is getting renamed? I saw some > emails about JARs getting "unprocessed" stuck in the name when signing is > turned off. It appears that the plugin isn't designed for POM dependencies. > > Here's the JBoss client dependency in my webstart application's POM: > > <dependency> > <groupId>org.jboss.jbossas</groupId> > <artifactId>jboss-as-client</artifactId> > <version>5.0.1.GA</version> > <scope>compile</scope> > <type>pom</type> > </dependency> > > I included that POM because it has dependencies to the client JARs I need to > call over to JBoss. Reference - > https://jira.jboss.org/jira/browse/JBAS-6320 > > Here's the webstart plugin config from my WAR POM: > > <plugins> > <plugin> > <groupId>org.codehaus.mojo.webstart</groupId> > <artifactId>webstart-maven-plugin</artifactId> > <executions> > <execution> > <phase>process-resources</phase> > <goals> > <goal>jnlp-download-servlet</goal> > </goals> > </execution> > </executions> > <configuration> > <outputDirectoryName>application</outputDirectoryName> > <outputFilename>launch.jnlp</outputFilename> > <jnlpFiles> > <jnlpFile> > <templateFilename>jnlp-template.vm</templateFilename> > <jarResources> > <jarResource> > <groupId>com.usairways.cbro</groupId> > <artifactId>real-time-departure-swing</artifactId> > <version>1.0.0.a2</version> > <mainClass>com.usairways.cbro.rtd.swing.Main</mainClass> > </jarResource> > </jarResources> > </jnlpFile> > </jnlpFiles> > </configuration> > </plugin> > </plugins> > > How can I get it to not rename the jboss-as-client POM to > unprocessed_jboss-as-client? Or alternatively, how do I keep it from adding > the jboss-as-client POM as a JAR dependency in the JNLP, but keep the > transitive dependencies of the jboss-as-client POM in there?
If the POM file isn't added to the target directory but the transitive dependencies added, that should fix it for you, right ? Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
