Re: [jboss-user] [JBoss Tools] - build path not set correctly after importing from svn for mavenized Seam project
by Arbi Sookazian
Arbi Sookazian [http://community.jboss.org/people/asookazian] replied to the discussion
"build path not set correctly after importing from svn for mavenized Seam project"
To view the discussion, visit: http://community.jboss.org/message/535000#535000
--------------------------------------------------------------
I upgraded to 3.1.0.GA JBT.
So I think I nailed down the root cause of why m2e can't accommodate my projects in terms of proper classpath/build path. Ultimately it comes down to the Maven Dependencies list being incomplete/wrong I guess but not sure how to fix this as my Seam application consists of two higher-level pom.xml (i.e.this is multi-module scenario consisting of two project with multi-modules and one depends on the other for services, API calls, etc.) Thus, I typically run 'mvn clean install' on two pom's, first model, then GUI.
I have two parent pom.xml files. One is dependent on the other (the model pom has the DAO, domain/entity classes, etc). These are apparently two independent projects when I do a svn checkout as Maven project.
So the following .classpath file for one of the mvn modules in the non-model project (it's called GUI which depends on Model packages/classes, etc.) does not have references to the model modules/projects so these packages and classes are unrecognizable by the compiler:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" output="target/classes" path="src/main/java"/>
<classpathentry excluding="**" kind="src" output="target/classes" path="src/main/resources"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
<classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
<classpathentry kind="output" path="target/classes"/>
</classpath>
When I run 'mvn eclipse:eclipse', the .classpath contents for this module/project change to the following which "fixes" the compiler resolution errors b/c of the classpathentry entries below for the cis.crud.dao, cis.crud.domain, etc which are apparently missing when m2e creates the .classpath file:
<classpath>
<classpathentry kind="src" path="src/main/java" including="**/*.java"/>
<classpathentry kind="src" path="src/main/resources" excluding="**/*.java"/>
<classpathentry kind="output" path="target/classes"/>
<classpathentry kind="var" path="M2_REPO/javax/el/el-api/1.2/el-api-1.2.jar"/>
<classpathentry kind="var" path="M2_REPO/javax/javaee/javaee/5.0/javaee-5.0.jar" sourcepath="M2_REPO/javax/javaee/javaee/5.0/javaee-5.0-sources.jar">
<attributes>
<attribute value="jar:file:/C:/Documents%20and%20Settings/asookazian/.m2/repository/javax/javaee/javaee/5.0/javaee-5.0-javadoc.jar!/" name="javadoc_location"/>
</attributes>
</classpathentry>
<classpathentry kind="var" path="M2_REPO/com/echo/cis/model/com.echo.cis.crud.dao/1.5.1-SNAPSHOT/com.echo.cis.crud.dao-1.5.1-SNAPSHOT.jar" sourcepath="M2_REPO/com/echo/cis/model/com.echo.cis.crud.dao/1.5.1-SNAPSHOT/com.echo.cis.crud.dao-1.5.1-SNAPSHOT-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/com/echo/cis/model/com.echo.cis.crud.domain/1.5.1-SNAPSHOT/com.echo.cis.crud.domain-1.5.1-SNAPSHOT.jar" sourcepath="M2_REPO/com/echo/cis/model/com.echo.cis.crud.domain/1.5.1-SNAPSHOT/com.echo.cis.crud.domain-1.5.1-SNAPSHOT-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/com/echo/cis/model/com.echo.cis.domain/1.5.1-SNAPSHOT/com.echo.cis.domain-1.5.1-SNAPSHOT.jar" sourcepath="M2_REPO/com/echo/cis/model/com.echo.cis.domain/1.5.1-SNAPSHOT/com.echo.cis.domain-1.5.1-SNAPSHOT-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/com/echo/cis/model/com.echo.cis.ejb.dao/1.5.1-SNAPSHOT/com.echo.cis.ejb.dao-1.5.1-SNAPSHOT.jar" sourcepath="M2_REPO/com/echo/cis/model/com.echo.cis.ejb.dao/1.5.1-SNAPSHOT/com.echo.cis.ejb.dao-1.5.1-SNAPSHOT-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/commons-lang/commons-lang/2.2/commons-lang-2.2.jar" sourcepath="M2_REPO/commons-lang/commons-lang/2.2/commons-lang-2.2-sources.jar">
<attributes>
<attribute value="jar:file:/C:/Documents%20and%20Settings/asookazian/.m2/repository/commons-lang/commons-lang/2.2/commons-lang-2.2-javadoc.jar!/" name="javadoc_location"/>
</attributes>
</classpathentry>
<classpathentry kind="var" path="M2_REPO/org/jboss/embedded/hibernate-all/beta3/hibernate-all-beta3.jar"/>
<classpathentry kind="var" path="M2_REPO/org/hibernate/hibernate-validator/3.0.0.ga/hibernate-validator-3.0.0.ga.jar"/>
<classpathentry kind="var" path="M2_REPO/org/jboss/microcontainer/jboss-deployers-client-spi/2.0.0.Beta6/jboss-deployers-client-spi-2.0.0.Beta6.jar" sourcepath="M2_REPO/org/jboss/microcontainer/jboss-deployers-client-spi/2.0.0.Beta6/jboss-deployers-client-spi-2.0.0.Beta6-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/org/jboss/microcontainer/jboss-deployers-core-spi/2.0.0.Beta6/jboss-deployers-core-spi-2.0.0.Beta6.jar" sourcepath="M2_REPO/org/jboss/microcontainer/jboss-deployers-core-spi/2.0.0.Beta6/jboss-deployers-core-spi-2.0.0.Beta6-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/org/jboss/el/jboss-el/2.0.2.CR1/jboss-el-2.0.2.CR1.jar" sourcepath="M2_REPO/org/jboss/el/jboss-el/2.0.2.CR1/jboss-el-2.0.2.CR1-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/org/jboss/embedded/jboss-embedded/beta3/jboss-embedded-beta3.jar"/>
<classpathentry kind="var" path="M2_REPO/org/jboss/embedded/jboss-embedded-all/beta3/jboss-embedded-all-beta3.jar"/>
<classpathentry kind="var" path="M2_REPO/org/jboss/seam/jboss-seam/2.1.1.GA/jboss-seam-2.1.1.GA.jar" sourcepath="M2_REPO/org/jboss/seam/jboss-seam/2.1.1.GA/jboss-seam-2.1.1.GA-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/org/jibx/jibx-bind/1.1.5/jibx-bind-1.1.5.jar"/>
<classpathentry kind="var" path="M2_REPO/org/jibx/jibx-extras/1.1.5/jibx-extras-1.1.5.jar"/>
<classpathentry kind="var" path="M2_REPO/org/jibx/jibx-run/1.1.5/jibx-run-1.1.5.jar"/>
<classpathentry kind="var" path="M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar" sourcepath="M2_REPO/junit/junit/3.8.1/junit-3.8.1-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/log4j/log4j/1.2.13/log4j-1.2.13.jar" sourcepath="M2_REPO/log4j/log4j/1.2.13/log4j-1.2.13-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/net/sf/opencsv/opencsv/1.8/opencsv-1.8.jar" sourcepath="M2_REPO/net/sf/opencsv/opencsv/1.8/opencsv-1.8-sources.jar">
<attributes>
<attribute value="jar:file:/C:/Documents%20and%20Settings/asookazian/.m2/repository/net/sf/opencsv/opencsv/1.8/opencsv-1.8-javadoc.jar!/" name="javadoc_location"/>
</attributes>
</classpathentry>
<classpathentry kind="var" path="M2_REPO/stax/stax-api/1.0.1/stax-api-1.0.1.jar"/>
<classpathentry kind="var" path="M2_REPO/org/testng/testng/5.7/testng-5.7-jdk15.jar"/>
<classpathentry kind="var" path="M2_REPO/org/jboss/embedded/thirdparty-all/beta3/thirdparty-all-beta3.jar"/>
<classpathentry kind="var" path="M2_REPO/org/codehaus/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.jar" sourcepath="M2_REPO/org/codehaus/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1-sources.jar"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
</classpath>
Here is an update I got from Jason Van Zyl to a (now closed) JIRA issue I opened regarding this same topic in this thread:
*The maven-eclipse-plugin is not supported. Any problems are with configurators so report what is missing. You won't be able to sue mvn eclipse:eclipse with M2Eclipse 1.0.*
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535000#535000]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 9 months
[jBPM] - How can I make jbpm 4.2 work with postgresql?
by feng men
feng men [http://community.jboss.org/people/fengmen] created the discussion
"How can I make jbpm 4.2 work with postgresql?"
To view the discussion, visit: http://community.jboss.org/message/534993#534993
--------------------------------------------------------------
I deploy jbpm 4.2 in postgresql. All jbpm tables are created in postgresql database. But when calling Configuration.getProcessEngine(), I got the following error: org.postgresql.util.PSQLException: ERROR: syntax error at or near "$1"
The StackTrace is the following:
INFO: building session factory
Mar 31, 2010 10:45:20 AM org.hibernate.impl.SessionFactoryObjectFactory addInstance
INFO: Not binding factory to JNDI, no JNDI name configured
Mar 31, 2010 10:45:20 AM org.hibernate.util.JDBCExceptionReporter logExceptions
WARNING: SQL Error: 0, SQLState: 42601
Mar 31, 2010 10:45:20 AM org.hibernate.util.JDBCExceptionReporter logExceptions
SEVERE: ERROR: syntax error at or near "$1"
Mar 31, 2010 10:45:20 AM org.hibernate.util.JDBCExceptionReporter logExceptions
WARNING: SQL Error: 0, SQLState: 42601
Mar 31, 2010 10:45:20 AM org.hibernate.util.JDBCExceptionReporter logExceptions
SEVERE: ERROR: syntax error at or near "$1"
Mar 31, 2010 10:45:20 AM org.jbpm.internal.log.Jdk14Log info
INFO: exception while executing command org.jbpm.pvm.internal.cmd.CheckDbCmd@dc67248
org.jbpm.api.JbpmException: no jBPM DB schema: no JBPM4_EXECUTION table. Run the create.jbpm.schema target first in the install tool.
at org.jbpm.pvm.internal.cmd.CheckDbCmd.execute(CheckDbCmd.java:50)
at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42)
at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:54)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55)
at org.jbpm.pvm.internal.svc.SkipInterceptor.execute(SkipInterceptor.java:43)
at org.jbpm.pvm.internal.cfg.ProcessEngineImpl.checkDb(ProcessEngineImpl.java:177)
at org.jbpm.pvm.internal.cfg.ProcessEngineImpl.buildProcessEngine(ProcessEngineImpl.java:170)
at org.jbpm.api.Configuration.getProcessEngine(Configuration.java:161)
Exception in thread "main" org.jbpm.api.JbpmException: no jBPM DB schema: no JBPM4_EXECUTION table. Run the create.jbpm.schema target first in the install tool.
at org.jbpm.pvm.internal.cmd.CheckDbCmd.execute(CheckDbCmd.java:50)
at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42)
at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:54)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55)
at org.jbpm.pvm.internal.svc.SkipInterceptor.execute(SkipInterceptor.java:43)
at org.jbpm.pvm.internal.cfg.ProcessEngineImpl.checkDb(ProcessEngineImpl.java:177)
at org.jbpm.pvm.internal.cfg.ProcessEngineImpl.buildProcessEngine(ProcessEngineImpl.java:170)
at org.jbpm.api.Configuration.getProcessEngine(Configuration.java:161)
Any help would be greatly appreciated.
Thanks,
Feng
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/534993#534993]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 9 months
