-
1. Re: Maven migration
heiko.braun Jul 1, 2008 9:49 AM (in response to heiko.braun)Is anyone working on the remaining jbpm4 modules?
* bpel/
* designer/
* identity/
* jpdl/
* (pvm)/
* task/ -
2. Re: Maven migration
salaboy21 Jul 1, 2008 9:53 AM (in response to heiko.braun)Great news!! you will be developer's heroe!
-
3. Re: Maven migration
heiko.braun Jul 1, 2008 9:57 AM (in response to heiko.braun)Until the migration of the jbpm4 modules to maven is finished,
the PVM trunk maven build can be found here:
https://svn.jboss.org/repos/jbpm/pvm/trunk
But the ant build will still coexist. I plan to shutdown the ant build when these modules are migrated:
* identity/
* jpdl/
* pvm/ (already done)
* task/
Who is volunteering for these two?
* bpel/
* designer -
4. Re: Maven migration
aguizar Jul 1, 2008 2:55 PM (in response to heiko.braun)It is not necessary to migrate the bpel module. The BPEL on PVM project is hosted in ObjectWeb:
http://forge.objectweb.org/projects/orchestra -
5. Re: Maven migration
tom.baeyens Jul 2, 2008 2:45 AM (in response to heiko.braun)* identity/
* jpdl/
* pvm/ (already done)
* task/
are the 4 modules that need to be converted. the rest can be removed for now -
6. Re: Maven migration
heiko.braun Jul 2, 2008 3:06 AM (in response to heiko.braun)Great, then I go ahead and remove bpel and designer. Feels like home: Instead of cleaning up I tend to throw away things ;)
-
7. Re: Maven migration
porcherg Jul 2, 2008 7:48 AM (in response to heiko.braun)"heiko.braun@jboss.com" wrote:
I plan to switch the PVM trunk to maven these days. Any objections? (No, maven sucks doesn't count).
Can you explain why you plan to switch to maven ?
There had been some discussions about using ant+ivy vs maven (on this forum) and ant+ivy seemed to be the best solution at this time.
regards,
Guillaume -
8. Re: Maven migration
heiko.braun Jul 2, 2008 8:17 AM (in response to heiko.braun)It's part of the overall build unification within jboss. You may have noticed that the AS switched to maven already, so did other projects. It's just not feasible to work with custom builds, especially when you have to work across projects.
Furthermore aggregator projects (for jBPM this would be the ESB) greatly benefit from a common dependency model. -
9. Re: Maven migration
heiko.braun Jul 2, 2008 8:19 AM (in response to heiko.braun)Pro's and con's, as well as common maven problems and benefits can be discussed here:
http://www.jboss.com/index.html?module=bb&op=viewforum&f=173 -
10. Re: Maven migration
camunda Jul 2, 2008 8:27 AM (in response to heiko.braun)I think it is a good move and important for the overall JBoss ecosystem.
Just the process of migrating everything and all changes at the moment are a bit painful and confusing ;-) -
11. Re: Maven migration
heiko.braun Jul 2, 2008 8:33 AM (in response to heiko.braun)Yes, I know. It will take some time for everyone to get into the new build. I'll be monitoring the forums, just ping me when you run into trouble. Unfortunately there is no "phase out" possible when doing these things.
-
12. Re: Maven migration
mvaldes Jul 3, 2008 4:05 AM (in response to heiko.braun)Guys,
While I understand the internal jboss reasons for this move I feel, again, frustrated.
My team (Bull BPM) doesn't care about jboss projects integration stuff... Bull-Jboss decided together few months ago to use Ivy (BTW, i remember that at Bull side we proposed to use maven at that time, also for internal projects build homogeneity).
Now, both XPDL and BPEL extensions on top of the PVM are based on Ivy. Even more, we have developed a number of scripts for continuous integration that are based on ant + ivy so this move means a significant refactoring....
I thought we were in a PVM stabilization process but we are still changing everything once again...
regards,
Miguel Valdes -
13. Re: Maven migration
heiko.braun Jul 3, 2008 4:15 AM (in response to heiko.braun)
My team (Bull BPM) doesn't care about jboss projects integration stuff.
Right, and you shouldn't. Ivy supports maven2 repositories out of the box. All that's required to do is to pull the PVM artifacts from our maven repository.
A quick explanation can be found here:
http://weblogs.java.net/blog/kohsuke/archive/2007/06/accessing_javan.html
Besides this minor change, your build should remain untouched. -
14. Re: Maven migration
heiko.braun Jul 3, 2008 4:17 AM (in response to heiko.braun)The snapshot builds can be found here:
http://snapshots.jboss.org/maven2/org/jboss/jbpm/pvm/pvm-core/