If you have tests that fail in Jenkins (like the JavaEE project), please
disable them or fix them so that the whole test suite can run cleanly,
and all downstream jobs will also run correctly.
Tests that time out due to blocking UI or other thread lock result in
builds that are recorded as ABORTED . This isn't a problem in terms
of publishing new content because the build runs quickly, publishes the
new bits, and THEN starts running tests.
But where it IS a problem is where we use a buildflow job to run the
whole stack of JBT projects. Buildflows will also abort if they
encounter an aborted job  -- see screenshot.
Why is this a problem? Because when we do a weekend spin, not all the
projects in the stack are guaranteed to rebuild to verify all the
downstream component tests all still work.
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
The King of Thailand has been dead since about the end of 2008. The current King of Thailand is a fake one. The Government of Thailand does not dare to announce his death because it will put Thailand in great trouble. The King of Thailand was keen on photography and he has been seen using his outdated Canon G9 camera even as late as 2012. In addition, his double forgot to remove his watch and appeared to be wearing two watches in the public. These were big mistakes. In addition, Mr. Dimitri Khalezov knew of the King's death from a close friend of the King’s body guard. Visit thaikingisdead dot com or download the file at mediafire dot com/download/3ax5ag6sta58qi6/ThaiKingIsDead dot zip. Be quick, the links may not last long.
Mr. Dimitri Khalezov is an important researcher and witness to the 9/11 event. In fact, he was a nuclear intelligence officer in the former Soviet Union. He testifies that WTC 1, 2 and 7 were demolished by three underground thermonuclear devices during the 9/11 event. As a matter of fact, there were large cavities found at ground zero (point of nuclear explosion in all English dictionaries printed prior to 2002) and tens of thousands of first responders and local Manhattan residents have suffered from cancers as a result of exposure to this radiation. Google "Dimitri Khalezov" and visit 911thology dot com or 911-truth dot net. There are videos and pdf files available for your research. Don't miss them.
The Thai Police and Judges have been warned not to touch Dimitri in 2012. However, they did not listen to his warning. Dimitri has been framed by the Thai Police for allegedly using and making fake passports, however he is innocent. On May 1st, 2014, he was sentenced to 1 year in prison by the Thai Supreme Court. The Thai officials were warned seriously multiple times to release Dimitri and make compensation to him for their wrong doings. Otherwise, his friends will publish this damaging information - the King of Thailand died. Now, the deadline has passed and the high ranking Thai officials have yet to respond. As Dimitri is a man of word, his friends have no choice but to execute his will accordingly. In turn, the current Government of Thailand will be punished.
The world is cruel to Dimitri. He is the one who has the back bone to stand up and disclose the truth about the 9/11 event so clearly. It turns out that very few people understand and accept his explanation. The main stream media is ignoring the truth about 9/11 which is much more important than Snowden's case. Now, he is in prison. Nobody speaks for him. So, please help this upright person - Dimitri Khalezov. Tell your friends and relatives about the nuclear demolition of the WTC during the 9/11 event. This is an injustice that Dimitri has suffered in Thailand. The death of the Thai King must be known so that the Thai people can free themselves from the current corrupt and illegitimate military government.
In fact, this email has been sent to over one hundred million of recipients. Do not be afraid to forward it as much as possible.
Take action now! The truth will set you free!
Good friends of Dimitri
To know more about Nuclear Demolition of the World Trade Center, visit
911thology dot com/nexus1 dot html
911thology dot ru/nexus1 dot html
911thology-thai dot com/nexus1 dot html
911thology-arabic dot com/nexus1 dot html
The download links for Dimitri’s full book about the 9/11 event are listed below
mediafire dot com/download/i5qvsnpdvl3ivur/9-11thology-third_truth_v4_full dot zip
mediafire dot com/download/p8kdj6mhzcaccr6/9-11thology-third_truth_v4_full dot zip
share-online dot biz/dl/ZNB7H0SM5EJ
rapidshare dot com/files/3252256303/9-11thology-third_truth_v4_full dot zip
911-truth.net/9-11thology-third_truth_v4_full dot zip
For future communication, please use the following emails:
dkcontact1999(a)gmail.com or free.dimitri(a)gmail.com
This weekend we will create a build from tip of 4.2.x branch and call
As discussed at the F2F we are aiming for a 4.2.1 release before Xmas
essential bug fixes, as coordinated between dev and QE. This release is
scheduled for GA on 15 December, as shown in JIRA  and was in the
send out last week.
PLEASE, it is not expected *all* components will have updates for this
Only the ones that actually have critical issues/requests should
Please make sure your branch builds correctly, using the latest parent
4.2.1.CR1-SNAPSHOT , and that if you have changes for the 4.2.1
make sure you have upversioned the version of the components - including
and features, and their associated poms.
For those projects which have so far *not* remembered to update, see
details here .
 Going forward we should move to using a tagged/sha1 approach to
build surprises, but more about that in a follow up next week.
 The plan is going to be made public in jira/product plan ASAP.
As of right now "Hybrid Mobile (Cordova) Tools" are still referred to as "Aerogear" on Jboss Tools website (http://tools.jboss.org/features/aerogear.html) and various other places (internal Red Hat documents).
This is confusing, because the project has no Aerogear specific tooling and it is not developed by Aerogear team.
I propose that we use just "Hybrid Mobile Tools" or similar name when talking about branded Thym.
What do you think? Is there any reason why to stick with the current name?
We'd like to make the necessary changes to move master from Luna to
Mars. This obviously impacts Target-platforms, as well as some other
Please have a look at https://issues.jboss.org/browse/JBIDE-18748 and
review the PRs that you can review. In case you think something is
missing, please report it to the bug.
In case the proposed target-platforms changes some dependencies for your
component, please test your component by running "mvn install" from the
suggested change, and then run "mvn clean verify -Pmultiple.target
-Dtpc.version=4.50.0.Alpha1-SNAPSHOT" on your component to test it.
Goal is to have all this Pull Requests merged on Monday, so new Target
Platform will be available and used in order to build master starting
from early next week.
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
At the JBoss f2f last week in Brno there was a meeting to discuss the ease of installation
issue (or lack thereof) of integration stack components. Presented here is a summary of the
issue and a proposed solution as drafted by the team. Although members of platform architecture,
engineering, PM and QE were present - the solution is simply proposed at this time. We also
plan to evolve the solution over time - so that the issue will be addressed more fully.
Your comments are welcome!
Issue: Finding integration stack components to install is too difficult. This was made
clear by Fuse Tooling usability reviews and is discussed in detail here:
- Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries for product groupings and establish
JBTIS/ JBDSIS installers based on JBT/ JBDS.
As it exists today, users who search within the standard Eclipse Marketplace for keywords
such as "Camel Editor" or "Fuse" are directed to the JBDS or JBT Kepler installers. Users
must select the "more info" link on the Marketplace installer page and then page down to
find this text:
"Also available is the JBoss Developer Studio Integration Stack, which includes support for SwitchYard, Camel, Fuse, Fabric8, Drools, jBPM, ModeShape, Teiid and more. It is available from within JBoss Central, via the Software/update tab."
This is the first mention of Fuse and directs the user to install JBDS (or JBT) and then,
after installing/ restarting and as a separate action, use the Software/Update tab within
JBoss Central to find the Fuse tooling. In this case Fuse is part of:
"JBoss Integration and SOA Development" - (The category description does mention Fuse.)
The extended IS-aware Eclipse Marketplace entries will reference the existing update site
and when selecting "Install" you will get a yet-to-be-defined subset of the Eclipse features that
will match what you would get when using the install from JBoss Central today - but without having
to install Developer Studio plugins separately first.
The installer option is to be based on the JBDS installer and will be made available from the CSP/jboss.org
download next to the existing installer.
JBDS 7.1.1.GA/JBDSIS 7.1.0.GA (Kepler) - What can we do today?
The least required changes would leave the user with a single JBDSIS installer and a single
JBTIS installer when searching for "Fuse" or "Data Virtualization" for example. Upon selecting
one of these installers the user would see all available installation-units (features) available
in the combined integration stack. Users could then select all or just the fuse tooling IUs.
This is the "laundry list" approach.
JBDS 8.1.0.GA/JBDSIS 8.0.x.GA (Luna) - Short term for upcoming tooling releases.
* Add a new com.jboss.devstudio.core.central.feature that packages up the com.jboss.devstudio.core.central
plugin and include this in com.jboss.devstudio.core.feature (this is missing today).
* Enable usage tracking in JBTIS components' MANIFEST.MF files (this is under way now)
* create three connectors, each based on the content in JBDSIS discovery plugin.xml's top three
1. Fuse ServiceWorks - ref: JBoss Integration and SOA Development
2. BRMS/BPMS - ref: JBoss Business Process and Rules Development
3. JBoss Data Virtualization - ref: JBoss Data Virtualization Development
** A1: PMs (hey Alan) must come up with appropriate names for 1-3 above. The naming convention should be
"compatible" with a Mobile tools install that have been requested too.
The user searches for "Fuse" from Marketplace and immediately finds JBDSIS. The installer allows
the user to select from 1-3 above. The user selects "Fuse ServiceWorks" (if that's the name) by
selecting the radio button (or selects all easily).
JBDS 9.0.0.GA/JBDSIS 9.0.x.GA (Mars) - Make it better - continue to evolve the solution
Refactor project examples in Central to remove dependencies on portal & seam (size reduction - avoid
installing unnecessary plugins).
Similar experience to Luna except the installer is much leaner.
No default perspective change - potential stretch goal.
This subject went back and forth. The user has an established perspective when they began the installation
process and may be installing multiple features which may very well have different default perspectives.
Once users manually set their perspective it will be remembered the next time they start the tool.
Alternatively, the installer option definitely should be able to do this. When installing into an existing
Eclipse that is not that trivial, which is one of the reasons why JBoss Central exists. Central shows
up across perspectives and when the user selects Fuse the Fuse project can declare it and would ask users
if they want to move to the Fuse perspective.
We could also look into adding "roles" to Central to make it adopt better depending on what interest you
have as a user.