[jboss-dev-forums] [Design of JBoss jBPM] - Re: improving the build

[tom.baeyens@jboss.com]

"david.lloyd at jboss.com" wrote : I only say it because then we can be able to state dependencies on tested versions of software.  It is always possible for us to miss something during testing; but if we use tested and "supported" releases of software, it decreases the likelihood that there's a problem that we missed.  Also, if customers want to build on what we have, it makes their life a little easier if they know what versions of support libraries they're running.
  | 
  | That said, it's more of a recommendation than a mandate. :-)

for third party libs this is automatically the case (except for the snapshot libs that should be avoided in final releases).  

for internal jbpm dependencies this doesn't have to be the case cause the sources are tagged.  so the complete build is reproducable.  the suite bundle serves as the base line.  

many of the jbpm sub projects are tied together and used together.  (just like the jboss components are mostly used in the jboss overall distribution).  

i don't want to get into a situation where we are forced to label and upload every single internal subproject just to do an overall build.  tagging the overall sources should be enough.  only if we want to use a specific version of a jbpm subproject, then it should be tagged separate and uploaded and referenced.

that was the overall idea.  not sure yet if it covers all the needs.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985810#3985810

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985810