[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
10 years, 10 months
Fwd: Fwd: Drools & jbpm on OSGi Platform (Karaf, JBoss Fuse)
by Rafael Benevides
Hi
Charles,
He in JDF we have began an effort to provide BRMS quickstarts and I
realized that some use cases bump each other.
Here are them:
https://issues.jboss.org/browse/JDF-581 - Create Beginner BRMS
Quickstart: helloworld-drl
https://issues.jboss.org/browse/JDF-584 - Create an Intermediate BRMS
Quickstart: decision-table
https://issues.jboss.org/browse/JDF-589 - Create an Intermediate BPMS
Quickstart: brms-bpms
There are several other BRMS quickstarts in the queue and some of them
are already ready to review.
JDF-582 - Create a Intermediate BRMS Quickstart: helloworld-stateful
(ready to review)
JDF-583 - Create an Intermediate BRMS Quickstart: helloworld-brms (ready
to review)
JDF-585 - Create an Advanced BRMS Quickstart: store-dsl (ready to review)
JDF-586 - Create an Advanced BRMS Quickstart: helloworld-cep
JDF-587 - Create an Advanced BRMS Quickstart: brms-integration
JDF-588 - Create an Advanced BRMS Quickstart: brms-planner
JDF-590 - Create an Advanced BPMS Quickstart: brms-bpms-task
I think we should discuss this and check what fits for you and what are
the deltas so we can joins forces and avoid use cases bumps.
Please, let me know your thoughts.
-------- Mensagem original --------
Assunto: Fwd: Drools & jbpm on OSGi Platform (Karaf, JBoss Fuse)
Data: Wed, 22 Jan 2014 17:48:01 +0000
De: Pete Muir <pmuir(a)redhat.com>
Para: Rafael Benevides <benevides(a)redhat.com>
Might be interesting for you..
Begin forwarded message:
> *From: *Charles Moulliard <cmoulliard(a)redhat.com
> <mailto:cmoulliard@redhat.com>>
> *Subject: **Drools & jbpm on OSGi Platform (Karaf, JBoss Fuse)*
> *Date: *22 January 2014 17:34:17 GMT
> *To: *"sme-fuse(a)redhat.com <mailto:sme-fuse@redhat.com>"
> <sme-fuse(a)redhat.com <mailto:sme-fuse@redhat.com>>,
> "se-jboss(a)redhat.com <mailto:se-jboss@redhat.com>"
> <se-jboss(a)redhat.com <mailto:se-jboss@redhat.com>>
>
> Hi,
>
> As I'm currently developing some examples for a partner which is
> looking about How to use/run Drools & jBPM on Karaf/JBoss Fuse, I have
> created this git repo
> https://github.com/cmoulliard/droolsjbpm-osgi-examples/ containing
> different demos + instructions :
>
> - Simple Drools Rule
> - Drools XLS Decision Table
> - Drools using XLS Decision Table from an External Resource
>
> - Simple BPMN2 process
>
> Remarks :
> - Camel + Drools (kie-spring, kie-blueprint) examples will be added soon
> - Most probably that this project will become a Quickstart in some
> days/weeks.
>
> Feel free to use it
>
> Regards,
>
> Charles Moulliard
> Sr. Principal Solution Architect / Apache Committer - Global Partner
> Enablement
> cmoulliard(a)redhat.com | work: +31 205 65 12 84 | mobile: +32 473 604
> 014 | RedHat.com <http://www.redhat.com/>
> twitter: @cmoulliard
> blog: cmoulliard.github.io <http://cmoulliard.github.io/>
10 years, 11 months
WFK BOMs branches management
by Marek Novotny
Hi JDF-dev (Rafael),
I would like to push https://github.com/jboss-developer/jboss-wfk-boms
further to next version development.
What I can see now, we need to merge 2.4.x branch with master and create
new branch for 2.5.x.
Are you OK with that?
Cheers,
--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
10 years, 11 months
Fwd: Changing the name of the Spring Quickstarts
by Pete Muir
Forwarding to jdf-dev(a)lists.jboss.org
Begin forwarded message:
> From: Joshua Wilson <jowilson(a)redhat.com>
> Subject: Changing the name of the Spring Quickstarts
> Date: 13 January 2014 15:33:54 GMT
> To: "'Pete Muir'" <pmuir(a)redhat.com>, <sme-jdf(a)redhat.com>
> Cc: "'Burr Sutter'" <bsutter(a)redhat.com>, "'Vineet Reynolds Pereira'" <vpereira(a)redhat.com>
>
> Does anyone have any concerns or issues with changing the names of all the Spring Quickstarts to start with ‘Spring-‘? Most notably this will affect the kitchensink ones as it take any kitchensink spring quickstarts out of the order of the rest of them.
>
> I am purposing the following:
>
> kitchensink-spring-basic -> spring-kitchensink-basic
>
> My thought is that it would help anyone looking for spring related quickstarts better able to find them. My concern is that I am not entirely sure it is worth it to interrupt the flow/order of the list.
>
> What do you all think?
>
> --
> Joshua Wilson
> Senior Software Engineer
> Jboss by Red Hat
> Mobile: 843-727-5277
> josh(a)redhat.com
> http://www.redhat.com
10 years, 11 months
QSTools 1.4.0.CR1 released
by Rafael Benevides
I'm proud do announce the first Release Candidate of QSTools 1.4
Thanks to the Paul Robinson's idea, a new feature of QSTools was
implemented to help the maintenance of the Quickstarts.
Now it's possible to run Fixers that can fix most of QSTools violations
detected.
These release includes the following Fixers:
1 - ArtifactIdNameFixer - Fix the <artifactId/> to match the
folder name on pom.xml files
2 - FileHeaderFixer - Fix the license header on all files
3 - FinalNameFixer - Fix <finalName/> on all pom.xml files
4 - JavaSourcesFormatFixer - Run the Eclipse source code formatter
on all Java source files
5 - LicenseFixer - Apply Apache V2 license to all pom.xml
files
6 - MavenCompilerFixer - Fix the maven.compiler.(source|target)
from pom.xml files
7 - PomNameFixer - Replace the <name/> on pom.xml with
the expected pattern
8 - UnusedPropertiesFixer - Remove unused properties from pom.xml
files
9 - XMLTabFixer - Replace [TABS] by [spaces] on XMLs files
10 - PomElementOrderFixer - Fix the pom.xml element order
To give it a try, just run:
mvn -U org.jboss.maven.plugins:maven-qstools-plugin:fix
Thanks to Paul Robinson that divided with me the implementation of most
Fixers and helped me with the tests and also to Sande Gilda who helped
to test some fixers, specially the JavaSourcesFormatFixer.
--
*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>
10 years, 11 months
