[neworg] - Clarification about project vs product BOMs
by Rafael Benevides
Hi all,
This email has the intention of clarifying some issues that are appearing as a result of the "new organization" changes, particularly around BOMs and their versions.
As we now focus on the_products_, we changed the version of the BOMs and Quickstarts to follow the target_product_ version: EAP 6.2.0, WFK 2.4.0, JDG 6.2.0, etc.
Since the j/boss-javaee-6.0-with-*/ BOMs are now target to its_products_ versions, we work with the_products_ teams to ensure the right dependency versions of components are used.
Until we get the Beta or GA versions of these BOMs, we host "developer releases" (using/-build-x/ suffix) onhttp://jboss-developer.github.io/temp-maven-repo/
We expect to move this repo in the newt few months, to a nexus managed instance
When the product is build, the version will be changed from/-build-x/ suffix to/-redhat-1/ suffix and when a beta or GA is released will be inhttp://maven.repository.redhat.com/techpreview/all/ orhttp://maven.repository.redhat.com/earlyaccess/all
We don't intend to sync thehttp://jboss-developer.github.io/temp-maven-repo/ to Maven Central.
Ok! But some_project_ teams are asking how they should treat their quickstarts given the fact that the_project_ delivers their quickstarts but the BOMs will not be available on Maven Central.
We're recommending the_project_ team that have their own_project_ BOMs using their_project_ GAV. Taking Richfaces and Arquillian as example:
- Richfaces provides their own BOM under the following GAV: org.richfaces:richfaces-bom:4.3.2.Final
- Arquillian provides their own BOM under the following GAV: org.jboss.arquillian:arquillian-bom: 1.1.0.Final
- Richfaces is used on WFK 2.4.0 so we wrap the Richfaces BOM under the following GAV:/org.jboss.bom.wfk: jboss-javaee-6.0-with-richfaces:2.4.0-/... ->https://github.com/jboss-developer/jboss-wfk-boms/blob/master/jboss-javae...
- Arquillian is also used on EAP 6.2.0 so we wrap the Arquillian BOM under the following GAV:/org.jboss.bom.eap: jboss-javaee-6.0-with-tools:6.2.0/-.... ->
https://github.com/jboss-developer/jboss-eap-boms/blob/master/jboss-javae...
As conclusion, we're suggesting that upstream_project_ create BOMs, and then the_product_ can wrap this BOM under the/org.jboss.bom.<_product_>: jboss-javaee-6.0-with-<_project_>:<_product_-version>/. This allows for easy identification of which BOM and version to use for both upstream and_product_."
If you have any further question on how it works, please let me know.
Please, forward to anyone you think that maybe interested in this email content.
Thanks
--
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
12 years
JBoss Central HTML5 archetype is borked
by Fred Bricon
2 issues were introduced in JBoss Central with the latest stacks.yaml
update :
- 2 archetype versions use the same html5-mobile tag : 2.4.0.Final and
2.4.0-build-1. But JBT, using
org.apache.maven.artifact.versioning.ComparableVersion, finds
2.4.0-build-1 is higher than 2.4.0.Final and uses it as the most recent
version. Since 2.4.0-build-1 dependencies haven't been released as part
of WFK 2.4, the generated project fails to build because of missing
deps. lastWFKArchetypeRelease should be updated to 2.4.0.Final in
https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml
- There's a blank html5 archetype, pointing at the non-blank one, which
makes JBoss Central wizards to enable a useless 'use blank' checkbox.
Why keep it referenced?
Fred
12 years, 2 months
QSTools 1.3.2.Final released
by Rafael Benevides
This release has some improvements on bom-check goal:
It allows to ignore certain known dependencies from being checked.
Example:
mvn
org.jboss.maven.plugins:maven-qstools-plugin:1.3.2-SNAPSHOT:bom-check
-D*qstools.bom-check.ignoredDependencies*=org.jboss.resteasy:abdera-atom-provider:2.3.7.Final,org.jboss.cache:jbosscache-core:3.2.5.GA
will ignore
1 - org.jboss.resteasy:abdera-atom-provider:2.3.7.Final
2 - org.jboss.cache:jbosscache-core:3.2.5.GA
from being checked as resolvable.
--
*Rafael Benevides | Senior Software Engineer*
JBoss Developer
M: +55-61-9269-6576
Red Hat
Better technology. Faster innovation. Powered by community collaboration.
See how it works at www.redhat.com <http://www.redhat.com/>
LinkedIn <http://www.linkedin.com/company/3258288> Youtube
<https://www.youtube.com/redhatlatam>
12 years, 2 months
