You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Rafal Rusin (JIRA)" <ji...@apache.org> on 2010/01/21 13:15:55 UTC
[jira] Commented: (ODE-729) Consider moving to maven
[ https://issues.apache.org/jira/browse/ODE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803270#action_12803270 ]
Rafal Rusin commented on ODE-729:
---------------------------------
This patch looks very good. It's a great progress. WAR and JBI distros were compiled properly.
Could you test those WAR and JBI distros on Tomcat and SMX33 (if you don't have SMX33, I think you can try it on SMX4 and output will be similar).
I think that as soon as they deploy successfully, we'll be ready to apply your patch.
When I tried to run it on SMX33, I saw it lacked this:
diff --git a/jbi/src/main/assembly/bin.xml b/jbi/src/main/assembly/bin.xml
index 40b058f..e20b69e 100644
--- a/jbi/src/main/assembly/bin.xml
+++ b/jbi/src/main/assembly/bin.xml
@@ -71,6 +71,7 @@
<include>org.apache.ode:ode-jca-server</include>
<include>org.apache.ode:ode-runtimes</include>
<include>org.apache.ode:ode-bpel-ql</include>
+ <include>org.apache.ode:ode-jbi</include>
<include>org.apache.ode:ode-engine</include>
<include>org.apache.ode:ode-scheduler-simple</include>
<include>org.apache.ode:ode-bpel-schemas</include>
After appying that, I got:
12:59:39,902 | INFO | ProcessStoreImpl-1 | Runtime | log.Log4JLogFactory$LogAdapter 80 | Starting OpenJPA 1.3.0-SNAPSHOT
12:59:40,177 | INFO | ProcessStoreImpl-1 | JDBC | log.Log4JLogFactory$LogAdapter 80 | Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.5.3.0 - (802917) ,Apache Derby Embedded JDBC Driver 10.5.3.0 - (802917)).
12:59:42,785 | ERROR | Timer-2 | ComponentMBeanImpl | i.framework.ComponentMBeanImpl 226 | Could not start component
java.lang.NoClassDefFoundError: org/apache/ode/jca/server/ConnectionProvider
at org.apache.ode.jbi.OdeLifeCycle.initConnector(OdeLifeCycle.java:282)
at org.apache.ode.jbi.OdeLifeCycle.init(OdeLifeCycle.java:139)
at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.init(ComponentMBeanImpl.java:201)
at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.doStart(ComponentMBeanImpl.java:287)
at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.start(ComponentMBeanImpl.java:216)
at org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService.java:334)
at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateComponent(AutoDeploymentService.java:292)
at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:252)
at org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:667)
at org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeploymentService.java:62)
at org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:631)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
12:59:42,787 | DEBUG | Timer-2 | SedaFlow | emix.jbi.nmr.flow.AbstractFlow 145 | Called Flow resume
> Consider moving to maven
> ------------------------
>
> Key: ODE-729
> URL: https://issues.apache.org/jira/browse/ODE-729
> Project: ODE
> Issue Type: New Feature
> Components: Build System
> Affects Versions: Wishlist
> Reporter: Greg Lucas
> Attachments: ODE-729.patch
>
>
> This was recently discussed on IRC so I'm raising a JIRA to track further comments and gauge interest: Should ODE consider adopting a Maven 2 (or maven 3) build?
> Maven has become widely adopted for open source and is used for many popular Apache projects. Developers coming to ODE are likely to be familiar with maven and already be using tools (such as IDEs, continuous integration servers, etc) that have built-in support for maven poms. In some scenarios the more complex maven dependency mechanisms for transitive and scoped dependencies would be useful for ODE developers and users.
> Is the ODE community interested in a maven-based build? Can maven handle the complexities of ODE's packaging?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.