[Design of JBoss Build System] - Common parent pom.xml
by pgier
After creating the pom files for microcontainer, and looking at the poms for common, there are some common things that I would like to put into a parent pom. The main thing initially is the definition of the jboss maven repository and plugin repository. This parent pom can be put into the maven repository so that we wouldn't have to add it to each project.
Here is what it looks like:
| <!--
| A parent pom with default settings for JBoss projects
| Each jboss project should have something similar to the following lines in their pom file.
| <parent>
| <artifactId>jboss-build</artifactId>
| <groupId>jboss</groupId>
| <version>snapshot</version>
| </parent>
|
| To build this project maven 2 should be installed and "mvn" should be in the system path. From the command line
| run "mvn install".
| -->
|
| <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
| <modelVersion>4.0.0</modelVersion>
| <groupId>jboss</groupId>
| <version>snapshot</version>
| <artifactId>jboss-build</artifactId>
| <name>JBoss Build</name>
| <url>http://www.jboss.org</url>
| <description>Parent POM for all JBoss Projects</description>
| <licenses>
| <license>
| <name>lgpl</name>
| <url>http://repository.jboss.com/licenses/lgpl.txt</url>
| </license>
| </licenses>
| <organization>
| <name>JBoss Inc.</name>
| <url>http://www.jboss.org</url>
| </organization>
|
| <packaging>pom</packaging>
|
| <repositories>
| <repository>
| <id>jboss</id>
| <name>JBoss Inc. Repository</name>
| <layout>default</layout>
| <url>http://repository.jboss.com/maven2/</url>
| <snapshots>
| <enabled>true</enabled>
| </snapshots>
| </repository>
| </repositories>
|
| <pluginRepositories>
| <pluginRepository>
| <id>jbosspluginrepo</id>
| <name>jboss plugin repository</name>
| <url>http://repository.jboss.com/maven2</url>
| <layout>default</layout>
| <snapshots>
| <enabled>false</enabled>
| <updatePolicy>never</updatePolicy>
| </snapshots>
| </pluginRepository>
| </pluginRepositories>
|
| <distributionManagement>
| <repository>
| <!-- Copy the distribution jar file to a local copy of the maven repository, for use by other projects -->
| <id>cvs-file-repository</id>
| <url>file://${maven.cvs.root}</url>
| </repository>
| </distributionManagement>
|
| </project>
|
The pom files for the various projects would then add a section like this in the beginning of the file:
| <parent>
| <artifactId>jboss-build</artifactId>
| <groupId>jboss</groupId>
| <version>snapshot</version>
| </parent>
|
The parent pom would have to be in the main maven repository (not just the jboss one) because otherwise the child project poms wouldn't be able to find it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006934#4006934
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006934
17 years, 5 months
[Design of JBoss jBPM] - web console deployment problem
by tom.baeyens@jboss.com
we are pulling together the build for 3.2.Beta2 on HEAD. there was one last issue we encountered during process deployment from the designer to the console
17:43:51,703 ERROR [[ProcessUploadServlet]] Servlet.service() for servlet ProcessUploadServlet threw exception
| java.lang.NoClassDefFoundError: org/apache/commons/io/output/DeferredFileOutputStream
| at org.apache.commons.fileupload.DefaultFileItemFactory.createItem(DefaultFileItemFactory.java:102)
| at org.apache.commons.fileupload.FileUploadBase.createItem(FileUploadBase.java:500)
| at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:367)
| at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:268)
| at org.jbpm.webapp.servlet.ProcessUploadServlet.handleRequest(ProcessUploadServlet.java:87)
| at org.jbpm.webapp.servlet.ProcessUploadServlet.service(ProcessUploadServlet.java:63)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:59)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| 17:43:52,265 DEBUG [JobExecutorThread] acquiring jobs for execution...
Did the introduction of the fileupload 1.1.1 introduce a new dependency on another lib ?
Maybe you are deploying to jboss 4.0.5, which might have a different set of commons libs...
David could you have a look at it ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006900#4006900
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006900
17 years, 5 months