On 2/15/2013 6:15 PM, Max Rydahl Andersen wrote:
>> I have tested JBoss EAP 6.1.0.DR4 and JBoss AS 7.2-SNAPSHOT (built using the JBoss AS git master)
>> There are two issues in runtime detection:
>> - JBoss EAP 6.1.0.DR4 is recognized as AS 7.2
>> - JBoss AS 7.2-SNAPSHOT is added as EAP 6.1
>> I think we have to add yet another server type (AS 7.2) and, after that, make runtime detection to recognize JBoss EAP 6.1.0.DR4 correctly.
> Rob already did these afaik: see https://issues.jboss.org/browse/JBIDE-13537
> If you spot other things missing let me know - just do that on jbosstools-dev.
> btw. since there are no AS 7.2 going to be released to the wild nor any EAP 6.1 available we went with adding an "EAP 6.1 (Tech Preview)" adapter.
I have tested jbosstools master that includes the fix for JBIDE-13537.
If it is planned to release JBoss AS 7.2, we will probably have to add
an AS 7.2 (Tech preview) provider.
Anyway, we have to fix the issue with recognizing the version of JBoss
>> On 2/15/2013 8:37 AM, Max Rydahl Andersen wrote:
>>> Hi guys,
>>> I realized that you guys might not be aware of the changes on EAP and SOA-P runtime side but
>>> just want to bring to your attention that AS 7.2/EAP 6.1 servers has changed their modules dir layout
>>> making the recognition and classpath handling we had in place for the AS 7.x/EAP 6.x family malfunction (+ a few other cosmetic changes
>>> like use of ansicolors by default in logging output we need to handle)
>>> Bug is here: https://issues.jboss.org/browse/JBIDE-13537
>>> We are currently working on a minimal fix for it in 7.0.Alpha1 to be released soon so there is some version of JBDS that will have a way
>>> to start the upcoming EAP 6.1 alpha - that fix is though pretty fragile because there is no EAP 6.1 version available yet so things might change.
>>> For one it means we no longer have a stable way to provide a classpath out-of-the-box for users not using Maven at this time.
>>> Once we got something stable we'll evaluate our options with respect to JBDS 6.x.
>>> p.s. if you have used the EAP 6 DR3 sent around last week you could still use it with the tools since that was based on AS 7.2 stream
>>> before these modules changes made it in. DR4 is first version that has this issue.
Hey all -
We are getting closer to releasing the community JBTIS/ production JBDS Integration Platform. The latest update repo is here:
Rob's completed a release process wiki that each component owner should adhere to:
The component owner is responsible for the release of their component. This person is responsible for:
* working with QA and PMs to ensure all requirements are met within the required time frame.
* working within the established engineering processes to ensure the correct version of their component
is integrated into the appropriate version of the aggregate release. (In other words, here are the
stable bits for component A that need to go into IS x.y.).
(see wiki for more details)
The identified component owners are here:
Please verify that I've identified the correct component owner for your tool. The one loose end that remains is the disposition of the runtime discovery project runtime-soa. The pieces of this project need to be moved into the components they support:
Drools/jBPM and ESB
Once integrated into their new home the new component owners will assume their maintenance and release.
Please reply to me with any issues. This will make your life easier! :)
Due to some feedback I had from people testing Teiid Designer 8.1 (unreleased), they were initially
confused / thrown by the secure storage password dialog popping up for the jboss server / teiid
server admin password. As a consequence, I investigated overriding it to display a more descriptive
and tailored dialog. A screenshot is available at .
The commit is currently waiting to be merged into the Designer codebase but wondered if this might
be useful going into a JBossTools repository instead? If so, which one?
"I know exactly who reads the papers ...
* The Daily Mirror is read by people who think they run the country.
* The Guardian is read by people who think they ought to run the country.
* The Times is read by people who do actually run the country.
* The Daily Mail is read by the wives of the people who run the country.
* The Financial Times is read by the people who own the country.
* The Morning Star is read by the people who think the country ought to be run by another country.
* The Daily Telegraph is read by the people who think it is."
Jim Hacker, Yes Minister
For those who aren't subscribed to wtp-dev mailing lists.
Just to inform on upcoming change in Eclipse's core/debug packages
See the forwarded messages.
-------- Original Message --------
Subject: [wtp-dev] Upcoming platform change for Kepler M6
Date: Tue, 12 Feb 2013 19:47:11 -0500
From: Carl Anderson <ccc(a)us.ibm.com>
Reply-To: General discussion of project-wide or architectural issues.
The Platform team announced that org.eclipse.debug.core will no longer
export org.eclipse.core.resources - see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=156134 . This already
effected the Source Editing team - see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=400538 . This may cause a
lot of compilation problems when we move up to an M6 build. Please look
through your plugin's dependencies for instances of
org.eclipse.debug.core to ensure that this is handled properly. (I see
at least 33 imports of org.eclipse.debug.core in WTP right now.)
I will hold off on moving up to an M6 platform build this week, but we
will move up early next week. Please address any compilation problems
as quickly as possible.
- Carl Anderson
WTP Build guy
We talked about this 'sideeffect' in tycho where you see things like:
[WARNING] The following locally built units have been used to resolve project dependencies:
Even when I got a repository with even newer bits on it.
Was there a flag for tycho to make it choose the latest instead or somehow ignore my local built ones ?
(even better I would like to just remove all local built stuff without having to guess/list all the names)