[jboss-dev-forums] [Design of JBoss Build System] - component releases that depend on snapshot

dimitris@jboss.org do-not-reply at jboss.com
Fri Apr 11 09:10:59 EDT 2008


Here is a part of a dependency tree

  | org.jboss:jboss-transaction-spi:jar:5.0.0.Beta4:compile
  | +- jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile
  | +- org.jboss.javaee:jboss-jca-api:jar:1.5.0.20070913080910:compile
  | \- org.jboss.javaee:jboss-transaction-api:jar:1.0.1.20070913080910:com
  | 
How are those component like jboss-jca-api:jar:1.5.0.20070913080910 or jboss-transaction-api:jar:1.0.1.20070913080910 produced?

Are those snapshot dependencies that are automatically uploaded when the outer component is released?

And is this considered a good practise? In this case we have a Beta4 version of the transaction-spi (and I believe the overal jboss-integration project) that depends on an untagged version of the jboss-javaee project.

Am I missing something?

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

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



More information about the jboss-dev-forums mailing list