From rrajasek at redhat.com  Tue Nov  4 16:57:48 2014
From: rrajasek at redhat.com (Rajesh Rajasekaran)
Date: Tue, 04 Nov 2014 15:57:48 -0600
Subject: [jbosstools-dev] New JBTIS target platform available -
	JBTIS-TP-4.2.0.Beta1b
In-Reply-To: <1218361243.41119697.1413902800269.JavaMail.zimbra@redhat.com>
References: <1218361243.41119697.1413902800269.JavaMail.zimbra@redhat.com>
Message-ID: <54594BDC.7000900@redhat.com>

We are looking for a fix to the bpmn2-modeler that addresses 
https://bugzilla.redhat.com/show_bug.cgi?id=1146739
A new update site with the fix is now available, Can it be picked up for 
the next build? (JBDSIS 7.1.0)?

Thanks
Rajesh



On 10/21/2014 09:46 AM, Paul Leacu wrote:
>     Greetings -
>        An updated JBTIS TP is available:
>
>     https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.0.Beta1b/
>     http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Beta1b/
>
>     See Jira for details (encompasses 4.2.0.Beta1a and 4.2.0.Beta1b):
>
>     https://issues.jboss.org/browse/JBTIS-340
>     https://issues.jboss.org/browse/JBTIS-333
>     https://issues.jboss.org/browse/JBTIS-334
>
>     1. Upate the jbosstools core TP to 4.41.0.Final
>     2. Update IS base requirement to Luna SR1a
>     3. Update BPMN2 Modeler to pick up feature source bundles and some bug fixes.
>        http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1.1.1.201410152001_0.7.0.201308220617_luna/
>     4. Trim out unneeded org.eclipse.birt plugins
>
>     --paull
>


From manderse at redhat.com  Wed Nov  5 02:58:54 2014
From: manderse at redhat.com (manderse at redhat.com)
Date: Wed, 5 Nov 2014 02:58:54 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201411050758.sA57ws8P009685@int-mx14.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3204

https://issues.jboss.org/browse/JBDS-3204
Summary: JBDS 8 workspace launcher is not shown in window list

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 18:46:28.406200

----------------------------



Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY

From ganandan at redhat.com  Wed Nov  5 16:02:34 2014
From: ganandan at redhat.com (Gomathi Anandan)
Date: Wed, 5 Nov 2014 16:02:34 -0500 (EST)
Subject: [jbosstools-dev] New JBTIS target platform available -
	JBTIS-TP-4.2.0.Beta1b
In-Reply-To: <54594BDC.7000900@redhat.com>
References: <1218361243.41119697.1413902800269.JavaMail.zimbra@redhat.com>
	<54594BDC.7000900@redhat.com>
Message-ID: <1209268504.3615798.1415221354736.JavaMail.zimbra@redhat.com>

Hi Rajesh,

This fix can be included in the Kepler release in January. What will be the version of the bpmn2 modeler which has this fix? Is it 1.0.3? 

SwitchYard tooling will not be updated for the Kepler release in January and we need to make sure that the new version of bpmn2 modeler is compatible with the SwitchYard tooling.

Thanks,
Gomathi


----- Original Message -----
From: "Rajesh Rajasekaran" <rrajasek at redhat.com>
To: "Paul Leacu" <pleacu at redhat.com>, jbds-is-pm-list at redhat.com, "soa-tools-list" <soa-tools-list at redhat.com>, "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "Alessandro Lazarotti" <alazarot at redhat.com>
Sent: Tuesday, November 4, 2014 4:57:48 PM
Subject: Re: New JBTIS target platform available - JBTIS-TP-4.2.0.Beta1b

We are looking for a fix to the bpmn2-modeler that addresses 
https://bugzilla.redhat.com/show_bug.cgi?id=1146739
A new update site with the fix is now available, Can it be picked up for 
the next build? (JBDSIS 7.1.0)?

Thanks
Rajesh



On 10/21/2014 09:46 AM, Paul Leacu wrote:
>     Greetings -
>        An updated JBTIS TP is available:
>
>     https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.0.Beta1b/
>     http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Beta1b/
>
>     See Jira for details (encompasses 4.2.0.Beta1a and 4.2.0.Beta1b):
>
>     https://issues.jboss.org/browse/JBTIS-340
>     https://issues.jboss.org/browse/JBTIS-333
>     https://issues.jboss.org/browse/JBTIS-334
>
>     1. Upate the jbosstools core TP to 4.41.0.Final
>     2. Update IS base requirement to Luna SR1a
>     3. Update BPMN2 Modeler to pick up feature source bundles and some bug fixes.
>        http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1.1.1.201410152001_0.7.0.201308220617_luna/
>     4. Trim out unneeded org.eclipse.birt plugins
>
>     --paull
>


From manderse at redhat.com  Thu Nov  6 02:58:46 2014
From: manderse at redhat.com (manderse at redhat.com)
Date: Thu, 6 Nov 2014 02:58:46 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201411060758.sA67wkEd026068@int-mx13.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBIDE-18731

https://issues.jboss.org/browse/JBIDE-18731
Summary: Remove deprecated usecase of project archives run externally via ant

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 17:00:43.082768

----------------------------



Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY

From manderse at redhat.com  Fri Nov  7 02:58:48 2014
From: manderse at redhat.com (manderse at redhat.com)
Date: Fri, 7 Nov 2014 02:58:48 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201411070758.sA77wmki004998@int-mx14.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBIDE-18731

https://issues.jboss.org/browse/JBIDE-18731
Summary: Remove deprecated usecase of project archives run externally via ant

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 1 day, 17:00:44.864569

----------------------------



Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY

From fbricon at gmail.com  Fri Nov  7 16:36:59 2014
From: fbricon at gmail.com (Fred Bricon)
Date: Fri, 7 Nov 2014 22:36:59 +0100
Subject: [jbosstools-dev] Automatic out-of-date configuration updates
Message-ID: <CAG2ouxSXNojSeOLLW=AVc5sH=FLvtV_LbQShyzXGGdqnQ2bN-g@mail.gmail.com>

Hi,

FYI, I whipped up a small plugin that automatically update out-of-date
project configuration, under our JBoss Tools Playground repo [1].

I'm not sure if it's completely safe to use. There's no preference to
(de)activate it -yet-. The plugin is set to start on workspace startup for
now, which isn't ideal, but if you deactivate it from Preferences > Startup
and Shutdown and restart the workspace, it should be inactive.
It's, most probably, sub-optimally implemented, but it worked on the small
set of projects I tried.

p2 site to install it from is at [2]. Feel free to try it and give some
feedback. Then we can discuss what to do with it, wrt [3].

[1]
https://github.com/jbosstools/jbosstools-playground/tree/master/plugins/org.jboss.tools.playground.maven.autoupdate
[2]
http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground_master/all/repo/
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=335720

Fred

-- 
"Have you tried turning it off and on again" - The IT Crowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141107/c956fea1/attachment.html 

From manderse at redhat.com  Sat Nov  8 02:58:48 2014
From: manderse at redhat.com (manderse at redhat.com)
Date: Sat, 8 Nov 2014 02:58:48 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201411080758.sA87wmTa028256@int-mx13.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3207

https://issues.jboss.org/browse/JBDS-3207
Summary: Importing of Seam 2 Remoting Helloworld example shows errors in JBDS 8

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 19:06:42.899807

----------------------------



Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY

From manderse at redhat.com  Sun Nov  9 02:58:45 2014
From: manderse at redhat.com (manderse at redhat.com)
Date: Sun, 9 Nov 2014 02:58:45 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201411090758.sA97wjc3027965@int-mx10.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3207

https://issues.jboss.org/browse/JBDS-3207
Summary: Importing of Seam 2 Remoting Helloworld example shows errors in JBDS 8

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 1 day, 19:06:40.429977

----------------------------



Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY

From jason at takari.io  Sun Nov  9 09:22:31 2014
From: jason at takari.io (Jason van Zyl)
Date: Sun, 9 Nov 2014 09:22:31 -0500
Subject: [jbosstools-dev] [m2e-users] Automatic out-of-date
	configuration updates
In-Reply-To: <CAG2ouxSXNojSeOLLW=AVc5sH=FLvtV_LbQShyzXGGdqnQ2bN-g@mail.gmail.com>
References: <CAG2ouxSXNojSeOLLW=AVc5sH=FLvtV_LbQShyzXGGdqnQ2bN-g@mail.gmail.com>
Message-ID: <BCC10AEF-0BD3-4112-A45F-5B3152C32614@takari.io>

Are there conditions under which we can know it's safe? If every Mojo execution has an associated connector or configuration in the POM to address its presence can we safely run the update?

After going through the import process we encourage users to address any inconsistencies in the mappings between their Mojo executions and what M2Eclipse knows about them. So if this is done and we can deterministically know it's done would it be safe to just keep projects in sync, and if not how might address that? 

For example if I have a simple project with only a maven-compiler-plugin configuration and I change the source and target can the update be safely run? Does the connector know not to just execute if the required Java language level cannot be satisfied from the environment for example? And if it's not can that be reported in a way for the user to correct it?

I can certainly understand how you might not want to run this with a bunch of random Mojo executions where you haven't spent the time to setup a mapping configuration, but if the user have we should deterministically know when we can run the update and do it automatically and correctly. This would definitely make for a much better user experience.

On Nov 7, 2014, at 4:36 PM, Fred Bricon <fbricon at gmail.com> wrote:

> Hi,
> 
> FYI, I whipped up a small plugin that automatically update out-of-date project configuration, under our JBoss Tools Playground repo [1]. 
> 
> I'm not sure if it's completely safe to use. There's no preference to (de)activate it -yet-. The plugin is set to start on workspace startup for now, which isn't ideal, but if you deactivate it from Preferences > Startup and Shutdown and restart the workspace, it should be inactive. 
> It's, most probably, sub-optimally implemented, but it worked on the small set of projects I tried.  
> 
> p2 site to install it from is at [2]. Feel free to try it and give some feedback. Then we can discuss what to do with it, wrt [3].
>  
> [1] https://github.com/jbosstools/jbosstools-playground/tree/master/plugins/org.jboss.tools.playground.maven.autoupdate
> [2] http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground_master/all/repo/
> [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=335720
> 
> Fred
> 
> -- 
> "Have you tried turning it off and on again" - The IT Crowd
> _______________________________________________
> m2e-users mailing list
> m2e-users at eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------

Selfish deeds are the shortest path to self destruction.

 -- The Seven Samuari, Akira Kurosawa









-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141109/12f52000/attachment.html 

From manderse at redhat.com  Mon Nov 10 02:58:47 2014
From: manderse at redhat.com (manderse at redhat.com)
Date: Mon, 10 Nov 2014 02:58:47 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201411100758.sAA7wlrf016870@int-mx09.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3207

https://issues.jboss.org/browse/JBDS-3207
Summary: Importing of Seam 2 Remoting Helloworld example shows errors in JBDS 8

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 2 days, 19:06:42.046359

----------------------------



Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY

From manderse at redhat.com  Tue Nov 11 11:04:40 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 11 Nov 2014 17:04:40 +0100
Subject: [jbosstools-dev] freemarker repo weirdness..? nexus broken ?
Message-ID: <2A3FB5B7-7CFE-4592-B437-3A1C3B56E3D8@redhat.com>

Hey,

Freemarker repo is not buildable anymore.

User at https://github.com/jbosstools/jbosstools-freemarker/issues/26 
having issues
and I can verify the issue but my quick look indicates the right 
versions are used but
the build is for sure broken.

Anyone able to spot the missing piece ?

/max
http://about.me/maxandersen

From dgolovin at exadel.com  Tue Nov 11 15:55:01 2014
From: dgolovin at exadel.com (Denis Golovin)
Date: Tue, 11 Nov 2014 21:55:01 +0100
Subject: [jbosstools-dev] freemarker repo weirdness..? nexus broken ?
In-Reply-To: <2A3FB5B7-7CFE-4592-B437-3A1C3B56E3D8@redhat.com>
References: <2A3FB5B7-7CFE-4592-B437-3A1C3B56E3D8@redhat.com>
Message-ID: <546277A5.2030906@exadel.com>

Tried on master, it failed because of missing reference to base nightly 
repository.
So I fixed it and it now works OOTB.

Questions is why does it works fine on jenkins? Seems somehow nightly 
aggregate is available in jenkins build, that's why freemarker build can 
resolve usage and tests components it depends on.

Denis

On 11/11/2014 05:04 PM, Max Rydahl Andersen wrote:
> Hey,
>
> Freemarker repo is not buildable anymore.
>
> User at https://github.com/jbosstools/jbosstools-freemarker/issues/26
> having issues
> and I can verify the issue but my quick look indicates the right
> versions are used but
> the build is for sure broken.
>
> Anyone able to spot the missing piece ?
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From manderse at redhat.com  Tue Nov 11 16:00:41 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 11 Nov 2014 22:00:41 +0100
Subject: [jbosstools-dev] freemarker repo weirdness..? nexus broken ?
In-Reply-To: <546277A5.2030906@exadel.com>
References: <2A3FB5B7-7CFE-4592-B437-3A1C3B56E3D8@redhat.com>
	<546277A5.2030906@exadel.com>
Message-ID: <01A3F823-9C49-4BC9-9261-B347D8518305@redhat.com>

On 11 Nov 2014, at 21:55, Denis Golovin wrote:

> Tried on master, it failed because of missing reference to base 
> nightly repository.
> So I fixed it and it now works OOTB.
>
> Questions is why does it works fine on jenkins? Seems somehow nightly 
> aggregate is available in jenkins build, that's why freemarker build 
> can resolve usage and tests components it depends on.

That would be bad if that is the case ;/ ...but I'm pretty sure I have 
been building freemarker from mvn cli before...wondering what changed.

Michael/Nick - any idea ?

Denis - if you got solution let the contributor know on #26 (I can't 
test/verify from here right now)

/max

> Denis
>
> On 11/11/2014 05:04 PM, Max Rydahl Andersen wrote:
>> Hey,
>>
>> Freemarker repo is not buildable anymore.
>>
>> User at https://github.com/jbosstools/jbosstools-freemarker/issues/26
>> having issues
>> and I can verify the issue but my quick look indicates the right
>> versions are used but
>> the build is for sure broken.
>>
>> Anyone able to spot the missing piece ?
>>
>> /max
>> http://about.me/maxandersen
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From pleacu at redhat.com  Tue Nov 11 16:21:37 2014
From: pleacu at redhat.com (Paul Leacu)
Date: Tue, 11 Nov 2014 16:21:37 -0500 (EST)
Subject: [jbosstools-dev] JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 now live
In-Reply-To: <260295229.7474522.1415733623458.JavaMail.zimbra@redhat.com>
Message-ID: <185270154.7559164.1415740897421.JavaMail.zimbra@redhat.com>


   Greetings,
      The latest Eclipse-Luna capable, JBDS 8.0.0.GA compatible Integration Stack Beta tooling is
   released.  This capture contains new versions of BPMN2, Fuse Tooling, SwitchYard and Teiid Designer.

   This beta release is available as "development" or as "early access".

   JBDSIS 8.0.0.Beta1, JBTIS 4.2.0.Beta1

   1. If installing from Eclipse Luna:
       Help > Eclipse Marketplace...
       - in the 'Search' tab enter 'jbds' in the 'Find' input widget
       - select the 'Go' button
       - install 'Red Hat JBoss Developer Studio 8.0.0.GA'

   2. Start jbdevstudio or eclipse (with jbds from step 1)

   3. Select the Software/Update tab in the JBoss Central view.  Check the "Enable Early Access" check box.
      The production Early Access tooling appears in the 'Features Available' window.

   done!

   The standard p2 installer is also available for JBDSIS:

   1. If installing from Eclipse Luna:
       Help > Eclipse Marketplace...
       - in the 'Search' tab enter 'jbds' in the 'Find' input widget
       - select the 'Go' button
       - install 'Red Hat JBoss Developer Studio 8.0.0.GA'

   2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
       Help > Install New Software...
       Add...
       - use this for 'Location:'
         https://devstudio.redhat.com/updates/8.0-development/integration-stack/

   The standard p2 installer is available for the community capture (JBTIS):

   1. Install JBoss Tools 4.2.0.Final:
       Help > Eclipse Marketplace...
       - in the 'Search' tab enter 'jboss tools' in the 'Find' input widget
       - select the 'Go' button
       - install 'JBoss Tools 4.2.0.Final'

   2. Start eclipse-with-jbt from step 1, then:
       Help > Install New Software...
       Add...
       - use this for 'Location:'
         http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/

   JBoss Central is supported for the community capture as Early Access (JBTIS):

   1. Start eclipse-with-jbt from step 1

   2. Select the Software/Update tab in the JBoss Central view.  Check the "Enable Early Access" check box.
      The Early Access tooling appears in the 'Features Available' window.

   ----

   ** New - A standalone p2 installer is now available for the community capture (JBTIS):

   * Start eclipse Luna, then:
       Help > Install New Software...
       Add...
       - use this for 'Location:'
         http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/aggregate/4.2.0.Beta1/withreferences/

   ** Extra Credit **
   For component and QE test developers - the JBTIS target platform is:

    https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.0.Beta1b/
    http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Beta1b/REPO/

   Give it a try!

From dgolovin at exadel.com  Tue Nov 11 18:00:01 2014
From: dgolovin at exadel.com (Denis Golovin)
Date: Tue, 11 Nov 2014 15:00:01 -0800
Subject: [jbosstools-dev] freemarker repo weirdness..? nexus broken ?
In-Reply-To: <01A3F823-9C49-4BC9-9261-B347D8518305@redhat.com>
References: <2A3FB5B7-7CFE-4592-B437-3A1C3B56E3D8@redhat.com>
	<546277A5.2030906@exadel.com>
	<01A3F823-9C49-4BC9-9261-B347D8518305@redhat.com>
Message-ID: <546294F1.9010504@exadel.com>

On 11/11/2014 01:00 PM, Max Rydahl Andersen wrote:
> On 11 Nov 2014, at 21:55, Denis Golovin wrote:
>
>> Tried on master, it failed because of missing reference to base 
>> nightly repository.
>> So I fixed it and it now works OOTB.
>>
>> Questions is why does it works fine on jenkins? Seems somehow nightly 
>> aggregate is available in jenkins build, that's why freemarker build 
>> can resolve usage and tests components it depends on.
>
> That would be bad if that is the case ;/ ...but I'm pretty sure I have 
> been building freemarker from mvn cli before...wondering what changed.
>
> Michael/Nick - any idea ?
>
> Denis - if you got solution let the contributor know on #26 (I can't 
> test/verify from here right now)
>
> /max

Yes, I fixed master and post my comment in issues/26.

Denis

>
>> Denis
>>
>> On 11/11/2014 05:04 PM, Max Rydahl Andersen wrote:
>>> Hey,
>>>
>>> Freemarker repo is not buildable anymore.
>>>
>>> User at https://github.com/jbosstools/jbosstools-freemarker/issues/26
>>> having issues
>>> and I can verify the issue but my quick look indicates the right
>>> versions are used but
>>> the build is for sure broken.
>>>
>>> Anyone able to spot the missing piece ?
>>>
>>> /max
>>> http://about.me/maxandersen
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen


From max.andersen at redhat.com  Wed Nov 12 05:05:52 2014
From: max.andersen at redhat.com (Max Rydahl Andersen)
Date: Wed, 12 Nov 2014 11:05:52 +0100
Subject: [jbosstools-dev] JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 now live
In-Reply-To: <185270154.7559164.1415740897421.JavaMail.zimbra@redhat.com>
References: <185270154.7559164.1415740897421.JavaMail.zimbra@redhat.com>
Message-ID: <F8DEBDE8-7554-47D5-AF01-77EF85B32CC6@redhat.com>

Great news but this looks wrong.

After installing this I get 
"http://download.jboss.org/jbosstools/updates/development/luna/central/integration-stack"
added to the list of updatesites instead of the earlyaccess site.

At no time should the development site get added into our stable stream.

This is why earlyaccess is *separate* from the development/nightly 
updatesites etc. To shield this off.

I haven't checked developer studio yet, but if similar is happening 
there we definitely need to fix that.

/max

> Greetings,
>    The latest Eclipse-Luna capable, JBDS 8.0.0.GA compatible 
> Integration Stack Beta tooling is
> released.  This capture contains new versions of BPMN2, Fuse Tooling, 
> SwitchYard and Teiid Designer.
>
> This beta release is available as "development" or as "early access".
>
> JBDSIS 8.0.0.Beta1, JBTIS 4.2.0.Beta1
>
> 1. If installing from Eclipse Luna:
>     Help > Eclipse Marketplace...
>     - in the 'Search' tab enter 'jbds' in the 'Find' input widget
>     - select the 'Go' button
>     - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
>
> 2. Start jbdevstudio or eclipse (with jbds from step 1)
>
> 3. Select the Software/Update tab in the JBoss Central view.  Check 
> the "Enable Early Access" check box.
>    The production Early Access tooling appears in the 'Features 
> Available' window.
>
> done!
>
> The standard p2 installer is also available for JBDSIS:
>
> 1. If installing from Eclipse Luna:
>     Help > Eclipse Marketplace...
>     - in the 'Search' tab enter 'jbds' in the 'Find' input widget
>     - select the 'Go' button
>     - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
>
> 2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
>     Help > Install New Software...
>     Add...
>     - use this for 'Location:'
>       
> https://devstudio.redhat.com/updates/8.0-development/integration-stack/
>
> The standard p2 installer is available for the community capture 
> (JBTIS):
>
> 1. Install JBoss Tools 4.2.0.Final:
>     Help > Eclipse Marketplace...
>     - in the 'Search' tab enter 'jboss tools' in the 'Find' input 
> widget
>     - select the 'Go' button
>     - install 'JBoss Tools 4.2.0.Final'
>
> 2. Start eclipse-with-jbt from step 1, then:
>     Help > Install New Software...
>     Add...
>     - use this for 'Location:'
>       
> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/
>
> JBoss Central is supported for the community capture as Early Access 
> (JBTIS):
>
> 1. Start eclipse-with-jbt from step 1
>
> 2. Select the Software/Update tab in the JBoss Central view.  Check 
> the "Enable Early Access" check box.
>    The Early Access tooling appears in the 'Features Available' 
> window.
>
> ----
>
> ** New - A standalone p2 installer is now available for the community 
> capture (JBTIS):
>
> * Start eclipse Luna, then:
>     Help > Install New Software...
>     Add...
>     - use this for 'Location:'
>       
> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/aggregate/4.2.0.Beta1/withreferences/
>
> ** Extra Credit **
> For component and QE test developers - the JBTIS target platform is:
>
>  
> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.0.Beta1b/
>  
> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Beta1b/REPO/
>
> Give it a try!
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From max.andersen at redhat.com  Wed Nov 12 07:18:50 2014
From: max.andersen at redhat.com (Max Rydahl Andersen)
Date: Wed, 12 Nov 2014 13:18:50 +0100
Subject: [jbosstools-dev] JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 now live
In-Reply-To: <F8DEBDE8-7554-47D5-AF01-77EF85B32CC6@redhat.com>
References: <185270154.7559164.1415740897421.JavaMail.zimbra@redhat.com>
	<F8DEBDE8-7554-47D5-AF01-77EF85B32CC6@redhat.com>
Message-ID: <30ECA3F5-2942-44DE-B89F-2F848BCCAD2C@redhat.com>

Just tried devstudio and here its even worse.

https://www.dropbox.com/s/3wlmw9hd6pey4mc/Screenshot%202014-11-12%2013.13.34.png?dl=0

now download.jboss.org content is mixed into devstudio.redhat.com 
updatesites.

I opened https://issues.jboss.org/browse/JBTIS-360 and lets please get 
this disabled until fixed so we don't get "surprise" p2 updates into our 
production users.

/max

> Great news but this looks wrong.
>
> After installing this I get
> "http://download.jboss.org/jbosstools/updates/development/luna/central/integration-stack"
> added to the list of updatesites instead of the earlyaccess site.
>
> At no time should the development site get added into our stable 
> stream.
>
> This is why earlyaccess is *separate* from the development/nightly
> updatesites etc. To shield this off.
>
> I haven't checked developer studio yet, but if similar is happening
> there we definitely need to fix that.
>
> /max
>
>> Greetings,
>> The latest Eclipse-Luna capable, JBDS 8.0.0.GA compatible
>> Integration Stack Beta tooling is
>> released.  This capture contains new versions of BPMN2, Fuse Tooling,
>> SwitchYard and Teiid Designer.
>>
>> This beta release is available as "development" or as "early access".
>>
>> JBDSIS 8.0.0.Beta1, JBTIS 4.2.0.Beta1
>>
>> 1. If installing from Eclipse Luna:
>>  Help > Eclipse Marketplace...
>>  - in the 'Search' tab enter 'jbds' in the 'Find' input widget
>>  - select the 'Go' button
>>  - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
>>
>> 2. Start jbdevstudio or eclipse (with jbds from step 1)
>>
>> 3. Select the Software/Update tab in the JBoss Central view.  Check
>> the "Enable Early Access" check box.
>> The production Early Access tooling appears in the 'Features
>> Available' window.
>>
>> done!
>>
>> The standard p2 installer is also available for JBDSIS:
>>
>> 1. If installing from Eclipse Luna:
>>  Help > Eclipse Marketplace...
>>  - in the 'Search' tab enter 'jbds' in the 'Find' input widget
>>  - select the 'Go' button
>>  - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
>>
>> 2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
>>  Help > Install New Software...
>>  Add...
>>  - use this for 'Location:'
>>
>> https://devstudio.redhat.com/updates/8.0-development/integration-stack/
>>
>> The standard p2 installer is available for the community capture
>> (JBTIS):
>>
>> 1. Install JBoss Tools 4.2.0.Final:
>>  Help > Eclipse Marketplace...
>>  - in the 'Search' tab enter 'jboss tools' in the 'Find' input
>> widget
>>  - select the 'Go' button
>>  - install 'JBoss Tools 4.2.0.Final'
>>
>> 2. Start eclipse-with-jbt from step 1, then:
>>  Help > Install New Software...
>>  Add...
>>  - use this for 'Location:'
>>
>> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/
>>
>> JBoss Central is supported for the community capture as Early Access
>> (JBTIS):
>>
>> 1. Start eclipse-with-jbt from step 1
>>
>> 2. Select the Software/Update tab in the JBoss Central view.  Check
>> the "Enable Early Access" check box.
>> The Early Access tooling appears in the 'Features Available'
>> window.
>>
>> ----
>>
>> ** New - A standalone p2 installer is now available for the community
>> capture (JBTIS):
>>
>> * Start eclipse Luna, then:
>>  Help > Install New Software...
>>  Add...
>>  - use this for 'Location:'
>>
>> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/aggregate/4.2.0.Beta1/withreferences/
>>
>> ** Extra Credit **
>> For component and QE test developers - the JBTIS target platform is:
>>
>>
>> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.0.Beta1b/
>>
>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Beta1b/REPO/
>>
>> Give it a try!
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From pleacu at redhat.com  Wed Nov 12 09:08:42 2014
From: pleacu at redhat.com (Paul Leacu)
Date: Wed, 12 Nov 2014 09:08:42 -0500 (EST)
Subject: [jbosstools-dev] JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 now live
In-Reply-To: <30ECA3F5-2942-44DE-B89F-2F848BCCAD2C@redhat.com>
References: <185270154.7559164.1415740897421.JavaMail.zimbra@redhat.com>
	<F8DEBDE8-7554-47D5-AF01-77EF85B32CC6@redhat.com>
	<30ECA3F5-2942-44DE-B89F-2F848BCCAD2C@redhat.com>
Message-ID: <184647057.7961838.1415801322018.JavaMail.zimbra@redhat.com>


   Early Access for IS disabled for both JBT and JBDS.  Will modify to target earlyaccess site instead of
   development site for Beta1 IS EA.

      --paull



----- Original Message -----
> From: "Max Rydahl Andersen" <max.andersen at redhat.com>
> To: "Paul Leacu" <pleacu at redhat.com>
> Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>, jbds-is-pm-list at redhat.com, "soa-tools-list"
> <soa-tools-list at redhat.com>
> Sent: Wednesday, November 12, 2014 7:18:50 AM
> Subject: Re: [jbosstools-dev] JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 now live
> 
> Just tried devstudio and here its even worse.
> 
> https://www.dropbox.com/s/3wlmw9hd6pey4mc/Screenshot%202014-11-12%2013.13.34.png?dl=0
> 
> now download.jboss.org content is mixed into devstudio.redhat.com
> updatesites.
> 
> I opened https://issues.jboss.org/browse/JBTIS-360 and lets please get
> this disabled until fixed so we don't get "surprise" p2 updates into our
> production users.
> 
> /max
> 
> > Great news but this looks wrong.
> >
> > After installing this I get
> > "http://download.jboss.org/jbosstools/updates/development/luna/central/integration-stack"
> > added to the list of updatesites instead of the earlyaccess site.
> >
> > At no time should the development site get added into our stable
> > stream.
> >
> > This is why earlyaccess is *separate* from the development/nightly
> > updatesites etc. To shield this off.
> >
> > I haven't checked developer studio yet, but if similar is happening
> > there we definitely need to fix that.
> >
> > /max
> >
> >> Greetings,
> >> The latest Eclipse-Luna capable, JBDS 8.0.0.GA compatible
> >> Integration Stack Beta tooling is
> >> released.  This capture contains new versions of BPMN2, Fuse Tooling,
> >> SwitchYard and Teiid Designer.
> >>
> >> This beta release is available as "development" or as "early access".
> >>
> >> JBDSIS 8.0.0.Beta1, JBTIS 4.2.0.Beta1
> >>
> >> 1. If installing from Eclipse Luna:
> >>  Help > Eclipse Marketplace...
> >>  - in the 'Search' tab enter 'jbds' in the 'Find' input widget
> >>  - select the 'Go' button
> >>  - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
> >>
> >> 2. Start jbdevstudio or eclipse (with jbds from step 1)
> >>
> >> 3. Select the Software/Update tab in the JBoss Central view.  Check
> >> the "Enable Early Access" check box.
> >> The production Early Access tooling appears in the 'Features
> >> Available' window.
> >>
> >> done!
> >>
> >> The standard p2 installer is also available for JBDSIS:
> >>
> >> 1. If installing from Eclipse Luna:
> >>  Help > Eclipse Marketplace...
> >>  - in the 'Search' tab enter 'jbds' in the 'Find' input widget
> >>  - select the 'Go' button
> >>  - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
> >>
> >> 2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
> >>  Help > Install New Software...
> >>  Add...
> >>  - use this for 'Location:'
> >>
> >> https://devstudio.redhat.com/updates/8.0-development/integration-stack/
> >>
> >> The standard p2 installer is available for the community capture
> >> (JBTIS):
> >>
> >> 1. Install JBoss Tools 4.2.0.Final:
> >>  Help > Eclipse Marketplace...
> >>  - in the 'Search' tab enter 'jboss tools' in the 'Find' input
> >> widget
> >>  - select the 'Go' button
> >>  - install 'JBoss Tools 4.2.0.Final'
> >>
> >> 2. Start eclipse-with-jbt from step 1, then:
> >>  Help > Install New Software...
> >>  Add...
> >>  - use this for 'Location:'
> >>
> >> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/
> >>
> >> JBoss Central is supported for the community capture as Early Access
> >> (JBTIS):
> >>
> >> 1. Start eclipse-with-jbt from step 1
> >>
> >> 2. Select the Software/Update tab in the JBoss Central view.  Check
> >> the "Enable Early Access" check box.
> >> The Early Access tooling appears in the 'Features Available'
> >> window.
> >>
> >> ----
> >>
> >> ** New - A standalone p2 installer is now available for the community
> >> capture (JBTIS):
> >>
> >> * Start eclipse Luna, then:
> >>  Help > Install New Software...
> >>  Add...
> >>  - use this for 'Location:'
> >>
> >> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/aggregate/4.2.0.Beta1/withreferences/
> >>
> >> ** Extra Credit **
> >> For component and QE test developers - the JBTIS target platform is:
> >>
> >>
> >> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.0.Beta1b/
> >>
> >> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Beta1b/REPO/
> >>
> >> Give it a try!
> >> _______________________________________________
> >> jbosstools-dev mailing list
> >> jbosstools-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >
> >
> > /max
> > http://about.me/maxandersen
> >
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> 
> /max
> http://about.me/maxandersen
> 

From pleacu at redhat.com  Wed Nov 12 15:21:40 2014
From: pleacu at redhat.com (Paul Leacu)
Date: Wed, 12 Nov 2014 15:21:40 -0500 (EST)
Subject: [jbosstools-dev] JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 now live
In-Reply-To: <30ECA3F5-2942-44DE-B89F-2F848BCCAD2C@redhat.com>
References: <185270154.7559164.1415740897421.JavaMail.zimbra@redhat.com>
	<F8DEBDE8-7554-47D5-AF01-77EF85B32CC6@redhat.com>
	<30ECA3F5-2942-44DE-B89F-2F848BCCAD2C@redhat.com>
Message-ID: <1133527367.8230943.1415823700120.JavaMail.zimbra@redhat.com>


   
   Rogue URLs have been eliminated - the JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 JBoss Central 
   update sites are live again for Early Access.  Please let me know if anything else looks 
   odd...

   Thanks!
         --paull


----- Original Message -----
> From: "Max Rydahl Andersen" <max.andersen at redhat.com>
> To: "Paul Leacu" <pleacu at redhat.com>
> Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>, jbds-is-pm-list at redhat.com, "soa-tools-list"
> <soa-tools-list at redhat.com>
> Sent: Wednesday, November 12, 2014 7:18:50 AM
> Subject: Re: [jbosstools-dev] JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 now live
> 
> Just tried devstudio and here its even worse.
> 
> https://www.dropbox.com/s/3wlmw9hd6pey4mc/Screenshot%202014-11-12%2013.13.34.png?dl=0
> 
> now download.jboss.org content is mixed into devstudio.redhat.com
> updatesites.
> 
> I opened https://issues.jboss.org/browse/JBTIS-360 and lets please get
> this disabled until fixed so we don't get "surprise" p2 updates into our
> production users.
> 
> /max
> 
> > Great news but this looks wrong.
> >
> > After installing this I get
> > "http://download.jboss.org/jbosstools/updates/development/luna/central/integration-stack"
> > added to the list of updatesites instead of the earlyaccess site.
> >
> > At no time should the development site get added into our stable
> > stream.
> >
> > This is why earlyaccess is *separate* from the development/nightly
> > updatesites etc. To shield this off.
> >
> > I haven't checked developer studio yet, but if similar is happening
> > there we definitely need to fix that.
> >
> > /max
> >
> >> Greetings,
> >> The latest Eclipse-Luna capable, JBDS 8.0.0.GA compatible
> >> Integration Stack Beta tooling is
> >> released.  This capture contains new versions of BPMN2, Fuse Tooling,
> >> SwitchYard and Teiid Designer.
> >>
> >> This beta release is available as "development" or as "early access".
> >>
> >> JBDSIS 8.0.0.Beta1, JBTIS 4.2.0.Beta1
> >>
> >> 1. If installing from Eclipse Luna:
> >>  Help > Eclipse Marketplace...
> >>  - in the 'Search' tab enter 'jbds' in the 'Find' input widget
> >>  - select the 'Go' button
> >>  - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
> >>
> >> 2. Start jbdevstudio or eclipse (with jbds from step 1)
> >>
> >> 3. Select the Software/Update tab in the JBoss Central view.  Check
> >> the "Enable Early Access" check box.
> >> The production Early Access tooling appears in the 'Features
> >> Available' window.
> >>
> >> done!
> >>
> >> The standard p2 installer is also available for JBDSIS:
> >>
> >> 1. If installing from Eclipse Luna:
> >>  Help > Eclipse Marketplace...
> >>  - in the 'Search' tab enter 'jbds' in the 'Find' input widget
> >>  - select the 'Go' button
> >>  - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
> >>
> >> 2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
> >>  Help > Install New Software...
> >>  Add...
> >>  - use this for 'Location:'
> >>
> >> https://devstudio.redhat.com/updates/8.0-development/integration-stack/
> >>
> >> The standard p2 installer is available for the community capture
> >> (JBTIS):
> >>
> >> 1. Install JBoss Tools 4.2.0.Final:
> >>  Help > Eclipse Marketplace...
> >>  - in the 'Search' tab enter 'jboss tools' in the 'Find' input
> >> widget
> >>  - select the 'Go' button
> >>  - install 'JBoss Tools 4.2.0.Final'
> >>
> >> 2. Start eclipse-with-jbt from step 1, then:
> >>  Help > Install New Software...
> >>  Add...
> >>  - use this for 'Location:'
> >>
> >> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/
> >>
> >> JBoss Central is supported for the community capture as Early Access
> >> (JBTIS):
> >>
> >> 1. Start eclipse-with-jbt from step 1
> >>
> >> 2. Select the Software/Update tab in the JBoss Central view.  Check
> >> the "Enable Early Access" check box.
> >> The Early Access tooling appears in the 'Features Available'
> >> window.
> >>
> >> ----
> >>
> >> ** New - A standalone p2 installer is now available for the community
> >> capture (JBTIS):
> >>
> >> * Start eclipse Luna, then:
> >>  Help > Install New Software...
> >>  Add...
> >>  - use this for 'Location:'
> >>
> >> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/aggregate/4.2.0.Beta1/withreferences/
> >>
> >> ** Extra Credit **
> >> For component and QE test developers - the JBTIS target platform is:
> >>
> >>
> >> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.0.Beta1b/
> >>
> >> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Beta1b/REPO/
> >>
> >> Give it a try!
> >> _______________________________________________
> >> jbosstools-dev mailing list
> >> jbosstools-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >
> >
> > /max
> > http://about.me/maxandersen
> >
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> 
> /max
> http://about.me/maxandersen
> 

From manderse at redhat.com  Wed Nov 12 19:07:51 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 13 Nov 2014 01:07:51 +0100
Subject: [jbosstools-dev] freemarker repo weirdness..? nexus broken ?
In-Reply-To: <546294F1.9010504@exadel.com>
References: <2A3FB5B7-7CFE-4592-B437-3A1C3B56E3D8@redhat.com>
	<546277A5.2030906@exadel.com>
	<01A3F823-9C49-4BC9-9261-B347D8518305@redhat.com>
	<546294F1.9010504@exadel.com>
Message-ID: <14560B50-715A-4F60-95EB-F2FCECFADD28@redhat.com>

On 12 Nov 2014, at 0:00, Denis Golovin wrote:

> On 11/11/2014 01:00 PM, Max Rydahl Andersen wrote:
>> On 11 Nov 2014, at 21:55, Denis Golovin wrote:
>>
>>> Tried on master, it failed because of missing reference to base 
>>> nightly repository.
>>> So I fixed it and it now works OOTB.
>>>
>>> Questions is why does it works fine on jenkins? Seems somehow 
>>> nightly aggregate is available in jenkins build, that's why 
>>> freemarker build can resolve usage and tests components it depends 
>>> on.
>>
>> That would be bad if that is the case ;/ ...but I'm pretty sure I 
>> have been building freemarker from mvn cli before...wondering what 
>> changed.
>>
>> Michael/Nick - any idea ?
>>
>> Denis - if you got solution let the contributor know on #26 (I can't 
>> test/verify from here right now)

something is really fishy here.

now 4.2.x in freemarker is building.

Nick writes on 
https://github.com/jbosstools/jbosstools-freemarker/issues/26#issuecomment-62815793 
that parent pom is now built again.

But why was that needed ? we just did  a release that used this and that 
snapshot version should not change from now on.

Would need  a 4.2.1.Final for changes.

...does this mean the 4.2.0.Final-SNAPSHOT that was available for all to 
use until today was broken/outofdate ?

/max

>>
>> /max
>
> Yes, I fixed master and post my comment in issues/26.
>
> Denis
>
>>
>>> Denis
>>>
>>> On 11/11/2014 05:04 PM, Max Rydahl Andersen wrote:
>>>> Hey,
>>>>
>>>> Freemarker repo is not buildable anymore.
>>>>
>>>> User at 
>>>> https://github.com/jbosstools/jbosstools-freemarker/issues/26
>>>> having issues
>>>> and I can verify the issue but my quick look indicates the right
>>>> versions are used but
>>>> the build is for sure broken.
>>>>
>>>> Anyone able to spot the missing piece ?
>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>> /max
>> http://about.me/maxandersen


/max
http://about.me/maxandersen


From max.andersen at redhat.com  Wed Nov 12 19:30:22 2014
From: max.andersen at redhat.com (Max Rydahl Andersen)
Date: Thu, 13 Nov 2014 01:30:22 +0100
Subject: [jbosstools-dev] JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 now live
In-Reply-To: <1133527367.8230943.1415823700120.JavaMail.zimbra@redhat.com>
References: <185270154.7559164.1415740897421.JavaMail.zimbra@redhat.com>
	<F8DEBDE8-7554-47D5-AF01-77EF85B32CC6@redhat.com>
	<30ECA3F5-2942-44DE-B89F-2F848BCCAD2C@redhat.com>
	<1133527367.8230943.1415823700120.JavaMail.zimbra@redhat.com>
Message-ID: <ED3B6F5E-5C17-488A-9436-9061A613D185@redhat.com>

On 12 Nov 2014, at 21:21, Paul Leacu wrote:

> Rogue URLs have been eliminated - the JBDSIS 8.0.0.Beta1/ JBTIS 
> 4.2.0.Beta1 JBoss Central
> update sites are live again for Early Access.  Please let me know if 
> anything else looks
> odd...

I've reopened https://issues.jboss.org/browse/JBTIS-360 with my 
findings.

in short - close, but no cigar.

/max

>
> Thanks!
>       --paull
>
>
> ----- Original Message -----
>> From: "Max Rydahl Andersen" <max.andersen at redhat.com>
>> To: "Paul Leacu" <pleacu at redhat.com>
>> Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>, 
>> jbds-is-pm-list at redhat.com, "soa-tools-list"
>> <soa-tools-list at redhat.com>
>> Sent: Wednesday, November 12, 2014 7:18:50 AM
>> Subject: Re: [jbosstools-dev] JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 
>> now live
>>
>> Just tried devstudio and here its even worse.
>>
>> https://www.dropbox.com/s/3wlmw9hd6pey4mc/Screenshot%202014-11-12%2013.13.34.png?dl=0
>>
>> now download.jboss.org content is mixed into devstudio.redhat.com
>> updatesites.
>>
>> I opened https://issues.jboss.org/browse/JBTIS-360 and lets please 
>> get
>> this disabled until fixed so we don't get "surprise" p2 updates into 
>> our
>> production users.
>>
>> /max
>>
>>> Great news but this looks wrong.
>>>
>>> After installing this I get
>>> "http://download.jboss.org/jbosstools/updates/development/luna/central/integration-stack"
>>> added to the list of updatesites instead of the earlyaccess site.
>>>
>>> At no time should the development site get added into our stable
>>> stream.
>>>
>>> This is why earlyaccess is *separate* from the development/nightly
>>> updatesites etc. To shield this off.
>>>
>>> I haven't checked developer studio yet, but if similar is happening
>>> there we definitely need to fix that.
>>>
>>> /max
>>>
>>>> Greetings,
>>>> The latest Eclipse-Luna capable, JBDS 8.0.0.GA compatible
>>>> Integration Stack Beta tooling is
>>>> released.  This capture contains new versions of BPMN2, Fuse 
>>>> Tooling,
>>>> SwitchYard and Teiid Designer.
>>>>
>>>> This beta release is available as "development" or as "early 
>>>> access".
>>>>
>>>> JBDSIS 8.0.0.Beta1, JBTIS 4.2.0.Beta1
>>>>
>>>> 1. If installing from Eclipse Luna:
>>>> Help > Eclipse Marketplace...
>>>> - in the 'Search' tab enter 'jbds' in the 'Find' input widget
>>>> - select the 'Go' button
>>>> - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
>>>>
>>>> 2. Start jbdevstudio or eclipse (with jbds from step 1)
>>>>
>>>> 3. Select the Software/Update tab in the JBoss Central view.  Check
>>>> the "Enable Early Access" check box.
>>>> The production Early Access tooling appears in the 'Features
>>>> Available' window.
>>>>
>>>> done!
>>>>
>>>> The standard p2 installer is also available for JBDSIS:
>>>>
>>>> 1. If installing from Eclipse Luna:
>>>> Help > Eclipse Marketplace...
>>>> - in the 'Search' tab enter 'jbds' in the 'Find' input widget
>>>> - select the 'Go' button
>>>> - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
>>>>
>>>> 2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
>>>> Help > Install New Software...
>>>> Add...
>>>> - use this for 'Location:'
>>>>
>>>> https://devstudio.redhat.com/updates/8.0-development/integration-stack/
>>>>
>>>> The standard p2 installer is available for the community capture
>>>> (JBTIS):
>>>>
>>>> 1. Install JBoss Tools 4.2.0.Final:
>>>> Help > Eclipse Marketplace...
>>>> - in the 'Search' tab enter 'jboss tools' in the 'Find' input
>>>> widget
>>>> - select the 'Go' button
>>>> - install 'JBoss Tools 4.2.0.Final'
>>>>
>>>> 2. Start eclipse-with-jbt from step 1, then:
>>>> Help > Install New Software...
>>>> Add...
>>>> - use this for 'Location:'
>>>>
>>>> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/
>>>>
>>>> JBoss Central is supported for the community capture as Early 
>>>> Access
>>>> (JBTIS):
>>>>
>>>> 1. Start eclipse-with-jbt from step 1
>>>>
>>>> 2. Select the Software/Update tab in the JBoss Central view.  Check
>>>> the "Enable Early Access" check box.
>>>> The Early Access tooling appears in the 'Features Available'
>>>> window.
>>>>
>>>> ----
>>>>
>>>> ** New - A standalone p2 installer is now available for the 
>>>> community
>>>> capture (JBTIS):
>>>>
>>>> * Start eclipse Luna, then:
>>>> Help > Install New Software...
>>>> Add...
>>>> - use this for 'Location:'
>>>>
>>>> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/aggregate/4.2.0.Beta1/withreferences/
>>>>
>>>> ** Extra Credit **
>>>> For component and QE test developers - the JBTIS target platform 
>>>> is:
>>>>
>>>>
>>>> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.0.Beta1b/
>>>>
>>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Beta1b/REPO/
>>>>
>>>> Give it a try!
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>> /max
>> http://about.me/maxandersen
>>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From nboldt at redhat.com  Thu Nov 13 10:17:39 2014
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 13 Nov 2014 10:17:39 -0500
Subject: [jbosstools-dev] freemarker repo weirdness..? nexus broken ?
In-Reply-To: <14560B50-715A-4F60-95EB-F2FCECFADD28@redhat.com>
References: <2A3FB5B7-7CFE-4592-B437-3A1C3B56E3D8@redhat.com>	<546277A5.2030906@exadel.com>	<01A3F823-9C49-4BC9-9261-B347D8518305@redhat.com>	<546294F1.9010504@exadel.com>
	<14560B50-715A-4F60-95EB-F2FCECFADD28@redhat.com>
Message-ID: <5464CB93.4090601@redhat.com>

"But why was that needed ?"

Because Nexus periodically purges snapshots. So we rebuild them.

Simple problem, simple solution. This happens all the dang time, usually 
at inopportune moments (like right before a milestone release). But it's 
trivial to fix, and the longer solution is "ask eng-ops to stop purging 
snapshots" to which they'll say "disk isn't free".

N

On 11/12/2014 07:07 PM, Max Rydahl Andersen wrote:
> On 12 Nov 2014, at 0:00, Denis Golovin wrote:
>
>> On 11/11/2014 01:00 PM, Max Rydahl Andersen wrote:
>>> On 11 Nov 2014, at 21:55, Denis Golovin wrote:
>>>
>>>> Tried on master, it failed because of missing reference to base
>>>> nightly repository.
>>>> So I fixed it and it now works OOTB.
>>>>
>>>> Questions is why does it works fine on jenkins? Seems somehow
>>>> nightly aggregate is available in jenkins build, that's why
>>>> freemarker build can resolve usage and tests components it depends
>>>> on.
>>>
>>> That would be bad if that is the case ;/ ...but I'm pretty sure I
>>> have been building freemarker from mvn cli before...wondering what
>>> changed.
>>>
>>> Michael/Nick - any idea ?
>>>
>>> Denis - if you got solution let the contributor know on #26 (I can't
>>> test/verify from here right now)
>
> something is really fishy here.
>
> now 4.2.x in freemarker is building.
>
> Nick writes on
> https://github.com/jbosstools/jbosstools-freemarker/issues/26#issuecomment-62815793
> that parent pom is now built again.
>
> But why was that needed ? we just did  a release that used this and that
> snapshot version should not change from now on.
>
> Would need  a 4.2.1.Final for changes.
>
> ...does this mean the 4.2.0.Final-SNAPSHOT that was available for all to
> use until today was broken/outofdate ?
>
> /max
>
>>>
>>> /max
>>
>> Yes, I fixed master and post my comment in issues/26.
>>
>> Denis
>>
>>>
>>>> Denis
>>>>
>>>> On 11/11/2014 05:04 PM, Max Rydahl Andersen wrote:
>>>>> Hey,
>>>>>
>>>>> Freemarker repo is not buildable anymore.
>>>>>
>>>>> User at
>>>>> https://github.com/jbosstools/jbosstools-freemarker/issues/26
>>>>> having issues
>>>>> and I can verify the issue but my quick look indicates the right
>>>>> versions are used but
>>>>> the build is for sure broken.
>>>>>
>>>>> Anyone able to spot the missing piece ?
>>>>>
>>>>> /max
>>>>> http://about.me/maxandersen
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From manderse at redhat.com  Thu Nov 13 11:17:52 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 13 Nov 2014 17:17:52 +0100
Subject: [jbosstools-dev] updated website docs
Message-ID: <B0E3E490-741D-4075-96F3-FA940BE258BB@redhat.com>

Hey,

Len's great work on a switchyard blog pushed me to update/add more docs 
for how to update/edit the website.

It's live on tools.jboss.org/survivalguide.html but probably better 
viewed/used on 
https://github.com/jbosstools/jbosstools-website/blob/master/survivalguide.adoc

Let me know if you find something missing or got a question about and we 
can add more to this doc over time.

/max
http://about.me/maxandersen

From manderse at redhat.com  Thu Nov 13 11:29:46 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 13 Nov 2014 17:29:46 +0100
Subject: [jbosstools-dev] freemarker repo weirdness..? nexus broken ?
In-Reply-To: <5464CB93.4090601@redhat.com>
References: <2A3FB5B7-7CFE-4592-B437-3A1C3B56E3D8@redhat.com>
	<546277A5.2030906@exadel.com>
	<01A3F823-9C49-4BC9-9261-B347D8518305@redhat.com>
	<546294F1.9010504@exadel.com>
	<14560B50-715A-4F60-95EB-F2FCECFADD28@redhat.com>
	<5464CB93.4090601@redhat.com>
Message-ID: <DF0E497D-C5BA-4118-AD58-C1C53F20047E@redhat.com>

On 13 Nov 2014, at 16:17, Nick Boldt wrote:

> "But why was that needed ?"
>
> Because Nexus periodically purges snapshots. So we rebuild them.

The parent snapshot was not missing so I don't see how rebuilding the 
parent pom snapshot because it was purge is the right explanation.

I looks like the parent that was present was pointing to a target 
platform snapshot which is gone which of course
gets lost because we released a final version of the TP, right ?

> Simple problem, simple solution. This happens all the dang time, 
> usually at inopportune moments (like right before a milestone 
> release). But it's trivial to fix, and the longer solution is "ask 
> eng-ops to stop purging snapshots" to which they'll say "disk isn't 
> free".

The parent snapshot was not missing so I still question that something 
else must have gone wrong.

Seems like our parent pom was not actually correct. Which is not an 
eng-ops or purging issue but something being wrong in our handling of 
the parent pom
and its usage of target platform.

How can we avoid that in the future contributors and our selfs does not 
actually have an outofdate parent pom especially when we just did a 
final release ?
/max

> N
>
> On 11/12/2014 07:07 PM, Max Rydahl Andersen wrote:
>> On 12 Nov 2014, at 0:00, Denis Golovin wrote:
>>
>>> On 11/11/2014 01:00 PM, Max Rydahl Andersen wrote:
>>>> On 11 Nov 2014, at 21:55, Denis Golovin wrote:
>>>>
>>>>> Tried on master, it failed because of missing reference to base
>>>>> nightly repository.
>>>>> So I fixed it and it now works OOTB.
>>>>>
>>>>> Questions is why does it works fine on jenkins? Seems somehow
>>>>> nightly aggregate is available in jenkins build, that's why
>>>>> freemarker build can resolve usage and tests components it depends
>>>>> on.
>>>>
>>>> That would be bad if that is the case ;/ ...but I'm pretty sure I
>>>> have been building freemarker from mvn cli before...wondering what
>>>> changed.
>>>>
>>>> Michael/Nick - any idea ?
>>>>
>>>> Denis - if you got solution let the contributor know on #26 (I 
>>>> can't
>>>> test/verify from here right now)
>>
>> something is really fishy here.
>>
>> now 4.2.x in freemarker is building.
>>
>> Nick writes on
>> https://github.com/jbosstools/jbosstools-freemarker/issues/26#issuecomment-62815793
>> that parent pom is now built again.
>>
>> But why was that needed ? we just did  a release that used this and 
>> that
>> snapshot version should not change from now on.
>>
>> Would need  a 4.2.1.Final for changes.
>>
>> ...does this mean the 4.2.0.Final-SNAPSHOT that was available for all 
>> to
>> use until today was broken/outofdate ?
>>
>> /max
>>
>>>>
>>>> /max
>>>
>>> Yes, I fixed master and post my comment in issues/26.
>>>
>>> Denis
>>>
>>>>
>>>>> Denis
>>>>>
>>>>> On 11/11/2014 05:04 PM, Max Rydahl Andersen wrote:
>>>>>> Hey,
>>>>>>
>>>>>> Freemarker repo is not buildable anymore.
>>>>>>
>>>>>> User at
>>>>>> https://github.com/jbosstools/jbosstools-freemarker/issues/26
>>>>>> having issues
>>>>>> and I can verify the issue but my quick look indicates the right
>>>>>> versions are used but
>>>>>> the build is for sure broken.
>>>>>>
>>>>>> Anyone able to spot the missing piece ?
>>>>>>
>>>>>> /max
>>>>>> http://about.me/maxandersen
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>
>>
>> /max
>> http://about.me/maxandersen
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com


/max
http://about.me/maxandersen


From nboldt at redhat.com  Thu Nov 13 11:47:52 2014
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 13 Nov 2014 11:47:52 -0500
Subject: [jbosstools-dev] freemarker repo weirdness..? nexus broken ?
In-Reply-To: <DF0E497D-C5BA-4118-AD58-C1C53F20047E@redhat.com>
References: <2A3FB5B7-7CFE-4592-B437-3A1C3B56E3D8@redhat.com>
	<546277A5.2030906@exadel.com>
	<01A3F823-9C49-4BC9-9261-B347D8518305@redhat.com>
	<546294F1.9010504@exadel.com>
	<14560B50-715A-4F60-95EB-F2FCECFADD28@redhat.com>
	<5464CB93.4090601@redhat.com>
	<DF0E497D-C5BA-4118-AD58-C1C53F20047E@redhat.com>
Message-ID: <5464E0B8.7080404@redhat.com>

OK, so let me restate my assessment:

The parent pom we used to build pointed at the 4.4x.0.Final-SNAPSHOT 
target platforms, which are identical to the 4.4x.0.Final ones, so no 
foul occurred.

The parent pom should have been rebuilt AFTER releasing the target 
platforms. We updated the code [0] but didn't actually rebuild the 
parent, so it still pointed at the -SNAPSHOT version, not the released one.

[0] 
https://github.com/jbosstools/jbosstools-build/commit/da9599c5800b01529eca745e578cde640f7eb5e8

Hence the error reported was:

[ERROR] Internal error: java.lang.RuntimeException: Could not resolve 
target platform specification artifact 
org.jboss.tools.targetplatforms:jbosstools-unified:target:jbosstools-unified:4.40.0.Final-SNAPSHOT

Had we rebuilt the parent pom after releasing the TPs, the user would 
have instead tried to download target platform specification artifact 
org.jboss.tools.targetplatforms:jbosstools-unified:target:jbosstools-unified:4.40.0.Final 
(not -SNAPSHOT).

As we can see from 
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.Final-SNAPSHOT/parent-4.2.0.Final-20141015.125413-1.pom 
(which is the version built on Oct 15, 2014 8:53:50 AM, build #40), the 
target platform reference is to

<TARGET_PLATFORM_VERSION>4.40.0.Final-SNAPSHOT</TARGET_PLATFORM_VERSION>
<TARGET_PLATFORM_VERSION_MAXIMUM>4.41.0.Final-SNAPSHOT</TARGET_PLATFORM_VERSION_MAXIMUM>

But when we look at the rebuilt version from Nov 12 (#41) [1], we see 
the corrected code:

<TARGET_PLATFORM_VERSION>4.40.0.Final</TARGET_PLATFORM_VERSION>
<TARGET_PLATFORM_VERSION_MAXIMUM>4.41.0.Final</TARGET_PLATFORM_VERSION_MAXIMUM>

[1] 
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/4.2.0.Final-SNAPSHOT/parent-4.2.0.Final-20141112.233742-2.pom

So... as I said before, the solution was to rebuild the parent pom for 
external contributors to use. I was wrong about the nexus purge, however.

Nick


On 11/13/2014 11:29 AM, Max Rydahl Andersen wrote:
> On 13 Nov 2014, at 16:17, Nick Boldt wrote:
>
>> "But why was that needed ?"
>>
>> Because Nexus periodically purges snapshots. So we rebuild them.
>
> The parent snapshot was not missing so I don't see how rebuilding the
> parent pom snapshot because it was purge is the right explanation.
>
> I looks like the parent that was present was pointing to a target
> platform snapshot which is gone which of course
> gets lost because we released a final version of the TP, right ?
>
>> Simple problem, simple solution. This happens all the dang time,
>> usually at inopportune moments (like right before a milestone
>> release). But it's trivial to fix, and the longer solution is "ask
>> eng-ops to stop purging snapshots" to which they'll say "disk isn't
>> free".
>
> The parent snapshot was not missing so I still question that something
> else must have gone wrong.
>
> Seems like our parent pom was not actually correct. Which is not an
> eng-ops or purging issue but something being wrong in our handling of
> the parent pom
> and its usage of target platform.
>
> How can we avoid that in the future contributors and our selfs does not
> actually have an outofdate parent pom especially when we just did a
> final release ?
> /max
>
>> N
>>
>> On 11/12/2014 07:07 PM, Max Rydahl Andersen wrote:
>>> On 12 Nov 2014, at 0:00, Denis Golovin wrote:
>>>
>>>> On 11/11/2014 01:00 PM, Max Rydahl Andersen wrote:
>>>>> On 11 Nov 2014, at 21:55, Denis Golovin wrote:
>>>>>
>>>>>> Tried on master, it failed because of missing reference to base
>>>>>> nightly repository.
>>>>>> So I fixed it and it now works OOTB.
>>>>>>
>>>>>> Questions is why does it works fine on jenkins? Seems somehow
>>>>>> nightly aggregate is available in jenkins build, that's why
>>>>>> freemarker build can resolve usage and tests components it depends
>>>>>> on.
>>>>>
>>>>> That would be bad if that is the case ;/ ...but I'm pretty sure I
>>>>> have been building freemarker from mvn cli before...wondering what
>>>>> changed.
>>>>>
>>>>> Michael/Nick - any idea ?
>>>>>
>>>>> Denis - if you got solution let the contributor know on #26 (I can't
>>>>> test/verify from here right now)
>>>
>>> something is really fishy here.
>>>
>>> now 4.2.x in freemarker is building.
>>>
>>> Nick writes on
>>> https://github.com/jbosstools/jbosstools-freemarker/issues/26#issuecomment-62815793
>>>
>>> that parent pom is now built again.
>>>
>>> But why was that needed ? we just did  a release that used this and that
>>> snapshot version should not change from now on.
>>>
>>> Would need  a 4.2.1.Final for changes.
>>>
>>> ...does this mean the 4.2.0.Final-SNAPSHOT that was available for all to
>>> use until today was broken/outofdate ?
>>>
>>> /max
>>>
>>>>>
>>>>> /max
>>>>
>>>> Yes, I fixed master and post my comment in issues/26.
>>>>
>>>> Denis
>>>>
>>>>>
>>>>>> Denis
>>>>>>
>>>>>> On 11/11/2014 05:04 PM, Max Rydahl Andersen wrote:
>>>>>>> Hey,
>>>>>>>
>>>>>>> Freemarker repo is not buildable anymore.
>>>>>>>
>>>>>>> User at
>>>>>>> https://github.com/jbosstools/jbosstools-freemarker/issues/26
>>>>>>> having issues
>>>>>>> and I can verify the issue but my quick look indicates the right
>>>>>>> versions are used but
>>>>>>> the build is for sure broken.
>>>>>>>
>>>>>>> Anyone able to spot the missing piece ?
>>>>>>>
>>>>>>> /max
>>>>>>> http://about.me/maxandersen
>>>>>>> _______________________________________________
>>>>>>> jbosstools-dev mailing list
>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>
>>>>>
>>>>> /max
>>>>> http://about.me/maxandersen
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>
>
> /max
> http://about.me/maxandersen

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From mistria at redhat.com  Thu Nov 13 12:07:28 2014
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 13 Nov 2014 18:07:28 +0100
Subject: [jbosstools-dev] Initialization of the Mars stream
Message-ID: <5464E550.4080606@redhat.com>

Hi all,

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 
repositories.
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.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141113/543f520f/attachment.html 

From pstribny at redhat.com  Fri Nov 14 06:07:45 2014
From: pstribny at redhat.com (Petr Stribny)
Date: Fri, 14 Nov 2014 06:07:45 -0500 (EST)
Subject: [jbosstools-dev] Aerogear name change proposal
In-Reply-To: <3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
References: <758280146.11169162.1415894378569.JavaMail.zimbra@redhat.com>
	<2D6C6F5C-7FF5-4D1E-BD0C-D8B7AEE5DA6A@redhat.com>
	<1104260395.7616026.1415956992157.JavaMail.zimbra@redhat.com>
	<3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
Message-ID: <257111387.7666295.1415963265715.JavaMail.zimbra@redhat.com>

Hi all,

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?

--Petr

From pleacu at redhat.com  Fri Nov 14 10:12:04 2014
From: pleacu at redhat.com (Paul Leacu)
Date: Fri, 14 Nov 2014 10:12:04 -0500 (EST)
Subject: [jbosstools-dev] JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 now live
In-Reply-To: <1133527367.8230943.1415823700120.JavaMail.zimbra@redhat.com>
References: <185270154.7559164.1415740897421.JavaMail.zimbra@redhat.com>
	<F8DEBDE8-7554-47D5-AF01-77EF85B32CC6@redhat.com>
	<30ECA3F5-2942-44DE-B89F-2F848BCCAD2C@redhat.com>
	<1133527367.8230943.1415823700120.JavaMail.zimbra@redhat.com>
Message-ID: <1102376250.9446960.1415977924130.JavaMail.zimbra@redhat.com>


    Just an FYI - both the JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 JBoss Central update sites are 
    live for Early Access.  All update site streams have been approved.

    See blog: http://tools.jboss.org/blog/2014-11-13-JBTIS-Beta1-for-luna.html

    Thanks,
             --paull


----- Original Message -----
> From: "Max Rydahl Andersen" <max.andersen at redhat.com>
> To: "Paul Leacu" <pleacu at redhat.com>
> Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>, jbds-is-pm-list at redhat.com, "soa-tools-list"
> <soa-tools-list at redhat.com>
> Sent: Wednesday, November 12, 2014 7:18:50 AM
> Subject: Re: [jbosstools-dev] JBDSIS 8.0.0.Beta1/ JBTIS 4.2.0.Beta1 now live
> 
> Just tried devstudio and here its even worse.
> 
> https://www.dropbox.com/s/3wlmw9hd6pey4mc/Screenshot%202014-11-12%2013.13.34.png?dl=0
> 
> now download.jboss.org content is mixed into devstudio.redhat.com
> updatesites.
> 
> I opened https://issues.jboss.org/browse/JBTIS-360 and lets please get
> this disabled until fixed so we don't get "surprise" p2 updates into our
> production users.
> 
> /max
> 
> > Great news but this looks wrong.
> >
> > After installing this I get
> > "http://download.jboss.org/jbosstools/updates/development/luna/central/integration-stack"
> > added to the list of updatesites instead of the earlyaccess site.
> >
> > At no time should the development site get added into our stable
> > stream.
> >
> > This is why earlyaccess is *separate* from the development/nightly
> > updatesites etc. To shield this off.
> >
> > I haven't checked developer studio yet, but if similar is happening
> > there we definitely need to fix that.
> >
> > /max
> >
> >> Greetings,
> >> The latest Eclipse-Luna capable, JBDS 8.0.0.GA compatible
> >> Integration Stack Beta tooling is
> >> released.  This capture contains new versions of BPMN2, Fuse Tooling,
> >> SwitchYard and Teiid Designer.
> >>
> >> This beta release is available as "development" or as "early access".
> >>
> >> JBDSIS 8.0.0.Beta1, JBTIS 4.2.0.Beta1
> >>
> >> 1. If installing from Eclipse Luna:
> >>  Help > Eclipse Marketplace...
> >>  - in the 'Search' tab enter 'jbds' in the 'Find' input widget
> >>  - select the 'Go' button
> >>  - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
> >>
> >> 2. Start jbdevstudio or eclipse (with jbds from step 1)
> >>
> >> 3. Select the Software/Update tab in the JBoss Central view.  Check
> >> the "Enable Early Access" check box.
> >> The production Early Access tooling appears in the 'Features
> >> Available' window.
> >>
> >> done!
> >>
> >> The standard p2 installer is also available for JBDSIS:
> >>
> >> 1. If installing from Eclipse Luna:
> >>  Help > Eclipse Marketplace...
> >>  - in the 'Search' tab enter 'jbds' in the 'Find' input widget
> >>  - select the 'Go' button
> >>  - install 'Red Hat JBoss Developer Studio 8.0.0.GA'
> >>
> >> 2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
> >>  Help > Install New Software...
> >>  Add...
> >>  - use this for 'Location:'
> >>
> >> https://devstudio.redhat.com/updates/8.0-development/integration-stack/
> >>
> >> The standard p2 installer is available for the community capture
> >> (JBTIS):
> >>
> >> 1. Install JBoss Tools 4.2.0.Final:
> >>  Help > Eclipse Marketplace...
> >>  - in the 'Search' tab enter 'jboss tools' in the 'Find' input
> >> widget
> >>  - select the 'Go' button
> >>  - install 'JBoss Tools 4.2.0.Final'
> >>
> >> 2. Start eclipse-with-jbt from step 1, then:
> >>  Help > Install New Software...
> >>  Add...
> >>  - use this for 'Location:'
> >>
> >> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/
> >>
> >> JBoss Central is supported for the community capture as Early Access
> >> (JBTIS):
> >>
> >> 1. Start eclipse-with-jbt from step 1
> >>
> >> 2. Select the Software/Update tab in the JBoss Central view.  Check
> >> the "Enable Early Access" check box.
> >> The Early Access tooling appears in the 'Features Available'
> >> window.
> >>
> >> ----
> >>
> >> ** New - A standalone p2 installer is now available for the community
> >> capture (JBTIS):
> >>
> >> * Start eclipse Luna, then:
> >>  Help > Install New Software...
> >>  Add...
> >>  - use this for 'Location:'
> >>
> >> http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/aggregate/4.2.0.Beta1/withreferences/
> >>
> >> ** Extra Credit **
> >> For component and QE test developers - the JBTIS target platform is:
> >>
> >>
> >> https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.0.Beta1b/
> >>
> >> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Beta1b/REPO/
> >>
> >> Give it a try!
> >> _______________________________________________
> >> jbosstools-dev mailing list
> >> jbosstools-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >
> >
> > /max
> > http://about.me/maxandersen
> >
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> 
> /max
> http://about.me/maxandersen
> 


From bsutter at redhat.com  Fri Nov 14 10:39:45 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Fri, 14 Nov 2014 10:39:45 -0500
Subject: [jbosstools-dev] Confusing name - time for a change?
In-Reply-To: <3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
References: <758280146.11169162.1415894378569.JavaMail.zimbra@redhat.com>
	<2D6C6F5C-7FF5-4D1E-BD0C-D8B7AEE5DA6A@redhat.com>
	<1104260395.7616026.1415956992157.JavaMail.zimbra@redhat.com>
	<3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
Message-ID: <9EBB36A7-FD2D-4E5B-8FA3-96E9C93EE099@redhat.com>

trying to add that list

> On Nov 14, 2014, at 5:46 AM, Max Rydahl Andersen <max.andersen at redhat.com> wrote:
> 
> *please* move this to jbosstools-dev if you want anything changed.
> 
> noone from aerogear/hybrid mobile dev is in the cc.
> 
> /max
> 
>> Hi all,
>> 
>> the name "Aerogear" appears on JBoss Tools website (http://tools.jboss.org/features/aerogear.html) and on internal Mojo pages talking about it.
>> 
>> I believe that the name should be only "Hybrid Mobile (Cordova) Tools" or similar. It doesn't have any special tooling just for Aerogear libraries.
>> 
>> --Petr
>> 
>> ----- Original Message -----
>> From: "Burr Sutter" <bsutter at redhat.com>
>> To: "Len DiMaggio" <ldimaggi at redhat.com>
>> Cc: "Paul Leacu" <pleacu at redhat.com>, "Jiri Pallich" <jpallich at redhat.com>, "Max Rydahl Andersen" <max.andersen at redhat.com>, "Petr Stribny" <pstribny at redhat.com>
>> Sent: Friday, 14 November, 2014 12:45:57 AM
>> Subject: Re: Confusing name - time for a change?
>> 
>> Where is the name seen?
>> 
>> 
>>> On Nov 13, 2014, at 10:59 AM, Len DiMaggio <ldimaggi at redhat.com> wrote:
>>> 
>>> Hey Paul, Jiri, Max, and Burr,
>>> 
>>> I had a question about the Mobile tooling - the name for this is still Areogear - will we be able to change this to "mobile" any time soon?
>>> 
>>> 
>>> Thanks!,
>>> Len
>>> 
>>> 
>>> 
>>> -- 
>>> 
>>> Len DiMaggio (ldimaggi at redhat.com)
>>> JBoss by Red Hat
>>> 314 Littleton Road
>>> Westford, MA 01886  USA
>>> tel:  978.392.3179
>>> cell: 781.472.9912
>>> http://www.redhat.com
>>> http://community.jboss.org/people/ldimaggio
>>> 
>>> <RHxJBpngthumb.png> <http://www.redhat.com/>
>>> 
> 
> 
> /max
> http://about.me/maxandersen



From manderse at redhat.com  Fri Nov 14 13:20:33 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 14 Nov 2014 19:20:33 +0100
Subject: [jbosstools-dev] dockerization of jbosstools-website
Message-ID: <A1810FFF-3394-4F8C-BCD8-B78AF33A4501@redhat.com>

Hi,

To experiment with docker and actually make it useful I today pushed a 
Dockerfile + .dockerignore to 
https://github.com/jbosstools/jbosstools-website

I have not yet updated the docs so the info on how to use it is 
currently in the commit: 
https://github.com/jbosstools/jbosstools-website/commit/c9b9224a89f73f7bb6205c7cd5837732d209a4eb

But basically now instead of following the somewhat complicated full 
setup of ruby/awestruct you do this:

Install Docker (or boot2docker if on windows/osx)

Build docker image:
$ cd jbosstools-website
$ docker build -t jbosstools-website  .

(this takes a while: 10-40 min dependent on network speed/cpu you got)

 From that time on you can now do this to run local website build:

$ docker run -it --rm -p 4242:4242 -v `pwd`:/jbosstools-website -t 
jbosstools-website

(if on windows replace `pwd` with full path to your jbosstools-website 
checkout)

Content will then be available at http://${DOCKER_HOST}:4242

So why is this interesting ?

Well, look at the Dockerfile - its simple steps to setup a ruby 
environment.

Now imagine doing the same for a java environment. with maven and p2 
mirrors for target platforms prepopulated/preconfigured (maybe even 
jenkins - but it might not be needed anymore in the same degree as 
before).

Suddenly you got a reproducible and isolated build system for any number 
of eclipse plugins.

...and it can run anywhere and we can start testing and building in full 
isolation.

This could become really useful!

/max
http://about.me/maxandersen


From manderse at redhat.com  Fri Nov 14 14:01:49 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 14 Nov 2014 20:01:49 +0100
Subject: [jbosstools-dev] Aerogear name change proposal
In-Reply-To: <257111387.7666295.1415963265715.JavaMail.zimbra@redhat.com>
References: <758280146.11169162.1415894378569.JavaMail.zimbra@redhat.com>
	<2D6C6F5C-7FF5-4D1E-BD0C-D8B7AEE5DA6A@redhat.com>
	<1104260395.7616026.1415956992157.JavaMail.zimbra@redhat.com>
	<3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
	<257111387.7666295.1415963265715.JavaMail.zimbra@redhat.com>
Message-ID: <92B984CE-2380-4554-9045-BFF3D6672F31@redhat.com>

On 14 Nov 2014, at 12:07, Petr Stribny wrote:

> Hi all,
>
> 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.

Gorkem is on the aerogear team. Aerogear is used in the bundle/feature 
names for aerogear specific stuff (like the examples).

I'm not really much for renaming it, more like making it more specific 
and add a hybrid-mobile component (we can move the issues over if we 
want to).

Gorkem - any preference ? Earlier on there were plans about more 
specific aerogear tools but that have not (yet) manifested itself.

/max


>
> 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?
>
> --Petr
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From manderse at redhat.com  Fri Nov 14 13:13:12 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 14 Nov 2014 19:13:12 +0100
Subject: [jbosstools-dev] Aerogear name change proposal
In-Reply-To: <257111387.7666295.1415963265715.JavaMail.zimbra@redhat.com>
References: <758280146.11169162.1415894378569.JavaMail.zimbra@redhat.com>
	<2D6C6F5C-7FF5-4D1E-BD0C-D8B7AEE5DA6A@redhat.com>
	<1104260395.7616026.1415956992157.JavaMail.zimbra@redhat.com>
	<3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
	<257111387.7666295.1415963265715.JavaMail.zimbra@redhat.com>
Message-ID: <6339D9FF-DD8B-48B6-BC86-FF86A0300FDD@redhat.com>

On 14 Nov 2014, at 12:07, Petr Stribny wrote:

> Hi all,
>
> 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.

Gorkem is on the aerogear team. Aerogear is used in the bundle/feature 
names for aerogear specific stuff (like the examples).

I'm not really much for renaming it, more like making it more specific 
and add a hybrid-mobile component (we can move the issues over if we 
want to).

Gorkem - any preference ? Earlier on there were plans about more 
specific aerogear tools but that have not (yet) manifested itself.

/max


>
> 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?
>
> --Petr
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From manderse at redhat.com  Fri Nov 14 14:12:12 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 14 Nov 2014 20:12:12 +0100
Subject: [jbosstools-dev] dockerization of jbosstools-website
Message-ID: <96FEE7D7-DF80-4E04-82C0-40F8A174A87C@redhat.com>

Hi,

To experiment with docker and actually make it useful I today pushed a 
Dockerfile + .dockerignore to 
https://github.com/jbosstools/jbosstools-website

I have not yet updated the docs so the info on how to use it is 
currently in the commit: 
https://github.com/jbosstools/jbosstools-website/commit/c9b9224a89f73f7bb6205c7cd5837732d209a4eb

But basically now instead of following the somewhat complicated full 
setup of ruby/awestruct you do this:

Install Docker (or boot2docker if on windows/osx)

Build docker image:
$ cd jbosstools-website
$ docker build -t jbosstools-website  .

(this takes a while: 10-40 min dependent on network speed/cpu you got)

 From that time on you can now do this to run local website build:

$ docker run -it --rm -p 4242:4242 -v `pwd`:/jbosstools-website -t 
jbosstools-website

(if on windows replace `pwd` with full path to your jbosstools-website 
checkout)

Content will then be available at http://${DOCKER_HOST}:4242

So why is this interesting ?

Well, look at the Dockerfile - its simple steps to setup a ruby 
environment.

Now imagine doing the same for a java environment. with maven and p2 
mirrors for target platforms prepopulated/preconfigured (maybe even 
jenkins - but it might not be needed anymore in the same degree as 
before).

Suddenly you got a reproducible and isolated build system for any number 
of eclipse plugins.

...and it can run anywhere and we can start testing and building in full 
isolation.

This could become really useful!

/max
http://about.me/maxandersen


From pleacu at redhat.com  Fri Nov 14 15:43:18 2014
From: pleacu at redhat.com (Paul Leacu)
Date: Fri, 14 Nov 2014 15:43:18 -0500 (EST)
Subject: [jbosstools-dev] integration stack component installation
In-Reply-To: <1156518596.9634695.1415994598539.JavaMail.zimbra@redhat.com>
Message-ID: <477333601.9650309.1415997798282.JavaMail.zimbra@redhat.com>


   Greetings,
      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!

   Thanks,
          --paull

   ------

   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:

          https://mojo.redhat.com/docs/DOC-977658

   Proposed Solution:

   - Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries for product groupings and establish
     JBTIS/ JBDSIS installers based on JBT/ JBDS.
  
     Discussion:
     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.)

     Solution Details:

     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?

     - https://issues.jboss.org/browse/JBTIS-354

       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.

     - https://issues.jboss.org/browse/JBTIS-355

       * 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)
         - https://issues.jboss.org/browse/JBTIS-290
       * create three connectors, each based on the content in JBDSIS discovery plugin.xml's top three
         connector categories
         - https://issues.jboss.org/browse/JBTIS-357

         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

     - https://issues.jboss.org/browse/JBTIS-356/ https://issues.jboss.org/browse/JBIDE-18734
       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.

        --paull

From ldimaggi at redhat.com  Fri Nov 14 19:52:41 2014
From: ldimaggi at redhat.com (Len DiMaggio)
Date: Fri, 14 Nov 2014 19:52:41 -0500 (EST)
Subject: [jbosstools-dev] integration stack component installation
In-Reply-To: <477333601.9650309.1415997798282.JavaMail.zimbra@redhat.com>
References: <477333601.9650309.1415997798282.JavaMail.zimbra@redhat.com>
Message-ID: <4B809444-F7C4-4A29-A798-33617B458995@redhat.com>

Hey Paul,

Sounds great - the biggest thing that think will help is if we can make it very easy for users to install the tooling that they want AT THE SAME TIME AS JBDS.  I have always thought that from a developer's perspective, the tooling that they rely on IS the IDE. 

Thx!,
Len


(Sent from my iPhone)



> On Nov 14, 2014, at 3:43 PM, Paul Leacu <pleacu at redhat.com> wrote:
> 
> 
>   Greetings,
>      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!
> 
>   Thanks,
>          --paull
> 
>   ------
> 
>   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:
> 
>          https://mojo.redhat.com/docs/DOC-977658
> 
>   Proposed Solution:
> 
>   - Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries for product groupings and establish
>     JBTIS/ JBDSIS installers based on JBT/ JBDS.
> 
>     Discussion:
>     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.)
> 
>     Solution Details:
> 
>     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?
> 
>     - https://issues.jboss.org/browse/JBTIS-354
> 
>       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.
> 
>     - https://issues.jboss.org/browse/JBTIS-355
> 
>       * 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)
>         - https://issues.jboss.org/browse/JBTIS-290
>       * create three connectors, each based on the content in JBDSIS discovery plugin.xml's top three
>         connector categories
>         - https://issues.jboss.org/browse/JBTIS-357
> 
>         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
> 
>     - https://issues.jboss.org/browse/JBTIS-356/ https://issues.jboss.org/browse/JBIDE-18734
>       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.
> 
>        --paull
> 


From manderse at redhat.com  Sun Nov 16 02:59:04 2014
From: manderse at redhat.com (manderse at redhat.com)
Date: Sun, 16 Nov 2014 02:59:04 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 2 issues with no component
Message-ID: <201411160759.sAG7x4gQ025135@int-mx10.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBIDE-18755

https://issues.jboss.org/browse/JBIDE-18755
Summary: Autocomplete shows white on white using default RHEL7 theme

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 23:23:31.163845

----------------------------


* No component for JBIDE-18756

https://issues.jboss.org/browse/JBIDE-18756
Summary: WildFly 8.x Runtime is missing JAR containing javax.json

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 14:44:31.163427

----------------------------



Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY

From nboldt at redhat.com  Sun Nov 16 11:11:41 2014
From: nboldt at redhat.com (Nick Boldt)
Date: Sun, 16 Nov 2014 11:11:41 -0500
Subject: [jbosstools-dev] PLEASE READ: Proposal for new approach to managing
 transient upstream deps like Tern, AngularJS and Thym
Message-ID: <5468CCBD.5060702@redhat.com>

If you're a dev or QE for projects which use Tern, AngularJS, or Thym, 
or any other upstream incubating / frequently-changing dependency, 
please *read and reply* if this approach seems reasonable to you.

---

For dependencies like Tern, AngularJS and Thym, instead of iteratively 
updating them every few weeks in the target platform, we could instead 
treat them like jbosstools-* components, and simply refer to them as 
<dependencies> within dependent projects' root poms.

We used to do this for "moving target" upstream dependencies like m2e-* 
extensions, but for JBDS 8 we put EVERYTHING into the target platform 
and it was a bit of a pain to manage.

We could go a step further, too, and do automated weekly pulls of new 
upstream deps.

---

The process would look like this:

* every Friday, a Jenkins job pings eclipse.org looking for the latest 
available Tern, AngularJS, and Thym builds.

* if a newer one is found, a mirror is pulled and added to the pile on 
http://download.jboss.org/jbosstools/updates/requirements/

* the latest one is then symlinked from 
http://download.jboss.org/jbosstools/updates/requirements/{tern,angularjs,thym}/latest

* new entries are added to the parent pom for these 3 URLs:

https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L84

* projects which wish to build against these newer deps can do so by 
choice (local experiments) or automatically by updating their root poms 
to include new <repository> entries:

https://github.com/jbosstools/jbosstools-jst/blob/master/pom.xml#L23-L27

* projects will then need to monitor their manifests/feature.xml files 
to ensure they depend on the correct versions of upstream deps:

https://github.com/jbosstools/jbosstools-jst/blob/master/plugins/org.jboss.tools.jst.jsdt/META-INF/MANIFEST.MF#L8-L22

* should they forget, their build will break w/ an obvious error message

* they can then apply a fix & rebuild, or rollback to an earlier 
upstream dep in their root pom's <repository> reference, if they're not 
able to move up to the newer Tern. Angular, or Thym dependency.

* if the upstream component stabilizes, it can then later be added to 
the target platform; this is an approach suited for incubating upstream 
dependencies.

WDYT?

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From manderse at redhat.com  Mon Nov 17 02:59:01 2014
From: manderse at redhat.com (manderse at redhat.com)
Date: Mon, 17 Nov 2014 02:59:01 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201411170759.sAH7x199011307@int-mx10.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBIDE-18759

https://issues.jboss.org/browse/JBIDE-18759
Summary: Prepare for 4.2.1.CR1/8.0.1.CR1

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 13:45:58.603199

----------------------------



Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY

From aileenc at redhat.com  Mon Nov 17 05:04:30 2014
From: aileenc at redhat.com (Aileen Cunningham)
Date: Mon, 17 Nov 2014 05:04:30 -0500 (EST)
Subject: [jbosstools-dev] integration stack component installation
In-Reply-To: <477333601.9650309.1415997798282.JavaMail.zimbra@redhat.com>
References: <477333601.9650309.1415997798282.JavaMail.zimbra@redhat.com>
Message-ID: <942930017.15619955.1416218670741.JavaMail.zimbra@redhat.com>


Hi Paul,

when you say "establish JBTIS/ JBDSIS installers based on JBT/ JBDS" are you talking about a combined installer where you can install JBDS + IS in 1 action?

People can find the runtime download on JBoss.org fairly easily so what we need to get to is a 2nd big green download button on the Fuse product page that installs the relevant Tooling.

best regards,
   Aileen


----- Original Message -----
> From: "Paul Leacu" <pleacu at redhat.com>
> To: "Kevin Conner" <kconner at redhat.com>, "Max Rydahl Andersen" <max.andersen at redhat.com>, "Aileen Cunningham"
> <aileenc at redhat.com>
> Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
> jbds-is-pm-list at redhat.com, "JDV-PM Mailing List" <jdv-pm at redhat.com>, "Mustafa Musaji" <mmusaji at redhat.com>,
> "Fuse-pm-list" <fuse-pm-list at redhat.com>, "bpms-pm-list" <bpms-pm-list at redhat.com>
> Sent: Friday, 14 November, 2014 8:43:18 PM
> Subject: integration stack component installation
> 
> 
>    Greetings,
>       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!
> 
>    Thanks,
>           --paull
> 
>    ------
> 
>    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:
> 
>           https://mojo.redhat.com/docs/DOC-977658
> 
>    Proposed Solution:
> 
>    - Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries for product
>    groupings and establish
>      JBTIS/ JBDSIS installers based on JBT/ JBDS.
>   
>      Discussion:
>      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.)
> 
>      Solution Details:
> 
>      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?
> 
>      - https://issues.jboss.org/browse/JBTIS-354
> 
>        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.
> 
>      - https://issues.jboss.org/browse/JBTIS-355
> 
>        * 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)
>          - https://issues.jboss.org/browse/JBTIS-290
>        * create three connectors, each based on the content in JBDSIS
>        discovery plugin.xml's top three
>          connector categories
>          - https://issues.jboss.org/browse/JBTIS-357
> 
>          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
> 
>      - https://issues.jboss.org/browse/JBTIS-356/
>      https://issues.jboss.org/browse/JBIDE-18734
>        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.
> 
>         --paull
> 
> 

From manderse at redhat.com  Mon Nov 17 05:27:45 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 17 Nov 2014 11:27:45 +0100
Subject: [jbosstools-dev] PLEASE READ: Proposal for new approach to
 managing transient upstream deps like Tern, AngularJS and Thym
In-Reply-To: <5468CCBD.5060702@redhat.com>
References: <5468CCBD.5060702@redhat.com>
Message-ID: <ABBF2478-2789-410E-BC19-84D1A585915D@redhat.com>

On 16 Nov 2014, at 17:11, Nick Boldt wrote:

> If you're a dev or QE for projects which use Tern, AngularJS, or Thym,
> or any other upstream incubating / frequently-changing dependency,
> please *read and reply* if this approach seems reasonable to you.
>
> ---
>
> For dependencies like Tern, AngularJS and Thym, instead of iteratively
> updating them every few weeks in the target platform, we could instead
> treat them like jbosstools-* components, and simply refer to them as
> <dependencies> within dependent projects' root poms.

Last week we said that was possible for thym. Not sure if a unified 
approch will work well for tern and especially angularjs.

> We used to do this for "moving target" upstream dependencies like 
> m2e-*
> extensions,

which ones ? the ones we have inside jbosstools github ? those are 
different beasts than tern, angularjs, thym because
these actually exist *outside* our releases.

> but for JBDS 8 we put EVERYTHING into the target platform
> and it was a bit of a pain to manage.
>
> We could go a step further, too, and do automated weekly pulls of new
> upstream deps.

For thym - maybe. Gorkem's call.

For angularjs/tern - if we don't follow the changes closely and have 
test for verifying we are still working
then I would be really hesitant toward this.

> ---
>
> The process would look like this:
>
> * every Friday, a Jenkins job pings eclipse.org looking for the latest
> available Tern, AngularJS, and Thym builds.
>
> * if a newer one is found, a mirror is pulled and added to the pile on
> http://download.jboss.org/jbosstools/updates/requirements/

how do we keep track on which can be cleaned up/removed and which need 
to stay ?

> * the latest one is then symlinked from
> http://download.jboss.org/jbosstools/updates/requirements/{tern,angularjs,thym}/latest

this won't work reliably when we multiple streams building. Which stream 
uses what then ? and how does it get locked down for release ?

> * new entries are added to the parent pom for these 3 URLs:
>
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L84

> * projects which wish to build against these newer deps can do so by
> choice (local experiments) or automatically by updating their root 
> poms
> to include new <repository> entries:
>
> https://github.com/jbosstools/jbosstools-jst/blob/master/pom.xml#L23-L27
>
> * projects will then need to monitor their manifests/feature.xml files
> to ensure they depend on the correct versions of upstream deps:
>
> https://github.com/jbosstools/jbosstools-jst/blob/master/plugins/org.jboss.tools.jst.jsdt/META-INF/MANIFEST.MF#L8-L22
>
> * should they forget, their build will break w/ an obvious error 
> message

this only applies to tern/angularjs because no stable api in the areas 
we rely.

> * they can then apply a fix & rebuild, or rollback to an earlier
> upstream dep in their root pom's <repository> reference, if they're 
> not
> able to move up to the newer Tern. Angular, or Thym dependency.

you want to allow each component to be able to say they use different 
version of tern, angularjs or thym ?

How do we ensure our builds will actually be compatible with each other 
?

Thats my biggest headache with these.

I dont think an alternate repository reference should be allowed into 
the stream's. They need to use the one defined by parent.

forks/feature branches can use it for testing new things, but when 
integrating it to master the versions need be aligned, wont you say ?

/max
http://about.me/maxandersen


From manderse at redhat.com  Mon Nov 17 06:39:27 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 17 Nov 2014 12:39:27 +0100
Subject: [jbosstools-dev] PLEASE READ: Proposal for new approach to
 managing transient upstream deps like Tern, AngularJS and Thym
In-Reply-To: <5468CCBD.5060702@redhat.com>
References: <5468CCBD.5060702@redhat.com>
Message-ID: <94D83167-9B54-4498-AB37-FD5E74468EAF@redhat.com>

On 16 Nov 2014, at 17:11, Nick Boldt wrote:

> If you're a dev or QE for projects which use Tern, AngularJS, or Thym,
> or any other upstream incubating / frequently-changing dependency,
> please *read and reply* if this approach seems reasonable to you.
>
> ---
>
> For dependencies like Tern, AngularJS and Thym, instead of iteratively
> updating them every few weeks in the target platform, we could instead
> treat them like jbosstools-* components, and simply refer to them as
> <dependencies> within dependent projects' root poms.

Last week we said that was possible for thym. Not sure if a unified 
approch will work well for tern and especially angularjs.

> We used to do this for "moving target" upstream dependencies like 
> m2e-*
> extensions,

which ones ? the ones we have inside jbosstools github ? those are 
different beasts than tern, angularjs, thym because
these actually exist *outside* our releases.

> but for JBDS 8 we put EVERYTHING into the target platform
> and it was a bit of a pain to manage.
>
> We could go a step further, too, and do automated weekly pulls of new
> upstream deps.

For thym - maybe. Gorkem's call.

For angularjs/tern - if we don't follow the changes closely and have 
test for verifying we are still working
then I would be really hesitant toward this.

> ---
>
> The process would look like this:
>
> * every Friday, a Jenkins job pings eclipse.org looking for the latest
> available Tern, AngularJS, and Thym builds.
>
> * if a newer one is found, a mirror is pulled and added to the pile on
> http://download.jboss.org/jbosstools/updates/requirements/

how do we keep track on which can be cleaned up/removed and which need 
to stay ?

> * the latest one is then symlinked from
> http://download.jboss.org/jbosstools/updates/requirements/{tern,angularjs,thym}/latest

this won't work reliably when we multiple streams building. Which stream 
uses what then ? and how does it get locked down for release ?

> * new entries are added to the parent pom for these 3 URLs:
>
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L84

> * projects which wish to build against these newer deps can do so by
> choice (local experiments) or automatically by updating their root 
> poms
> to include new <repository> entries:
>
> https://github.com/jbosstools/jbosstools-jst/blob/master/pom.xml#L23-L27
>
> * projects will then need to monitor their manifests/feature.xml files
> to ensure they depend on the correct versions of upstream deps:
>
> https://github.com/jbosstools/jbosstools-jst/blob/master/plugins/org.jboss.tools.jst.jsdt/META-INF/MANIFEST.MF#L8-L22
>
> * should they forget, their build will break w/ an obvious error 
> message

this only applies to tern/angularjs because no stable api in the areas 
we rely.

> * they can then apply a fix & rebuild, or rollback to an earlier
> upstream dep in their root pom's <repository> reference, if they're 
> not
> able to move up to the newer Tern. Angular, or Thym dependency.

you want to allow each component to be able to say they use different 
version of tern, angularjs or thym ?

How do we ensure our builds will actually be compatible with each other 
?

Thats my biggest headache with these.

I dont think an alternate repository reference should be allowed into 
the stream's. They need to use the one defined by parent.

forks/feature branches can use it for testing new things, but when 
integrating it to master the versions need be aligned, wont you say ?

/max
http://about.me/maxandersen


From manderse at redhat.com  Mon Nov 17 06:47:13 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 17 Nov 2014 12:47:13 +0100
Subject: [jbosstools-dev] integration stack component installation
In-Reply-To: <942930017.15619955.1416218670741.JavaMail.zimbra@redhat.com>
References: <477333601.9650309.1415997798282.JavaMail.zimbra@redhat.com>
	<942930017.15619955.1416218670741.JavaMail.zimbra@redhat.com>
Message-ID: <BB552E73-CFC3-46D7-A1B7-E4F335B3C452@redhat.com>

On 17 Nov 2014, at 11:04, Aileen Cunningham wrote:

> Hi Paul,
>
> when you say "establish JBTIS/ JBDSIS installers based on JBT/ JBDS" 
> are you talking about a combined installer where you can install JBDS 
> + IS in 1 action?

Yes. But this requires work/QE resources.

> People can find the runtime download on JBoss.org fairly easily so 
> what we need to get to is a 2nd big green download button on the Fuse 
> product page that installs the relevant Tooling.

Can we start by putting existing devstudio installer there now ? (last 
time I looked it was not even mentioning it)

I believe your team is "owner" of those pages or at least should be able 
to request the best changes to them.

If not let me know what pages you believe should be changed and I can 
help track it down.

/max

>
> best regards,
> Aileen
>
>
> ----- Original Message -----
>> From: "Paul Leacu" <pleacu at redhat.com>
>> To: "Kevin Conner" <kconner at redhat.com>, "Max Rydahl Andersen" 
>> <max.andersen at redhat.com>, "Aileen Cunningham"
>> <aileenc at redhat.com>
>> Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "jbosstools-dev 
>> jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
>> jbds-is-pm-list at redhat.com, "JDV-PM Mailing List" 
>> <jdv-pm at redhat.com>, "Mustafa Musaji" <mmusaji at redhat.com>,
>> "Fuse-pm-list" <fuse-pm-list at redhat.com>, "bpms-pm-list" 
>> <bpms-pm-list at redhat.com>
>> Sent: Friday, 14 November, 2014 8:43:18 PM
>> Subject: integration stack component installation
>>
>>
>> Greetings,
>>    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!
>>
>> Thanks,
>>        --paull
>>
>> ------
>>
>> 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:
>>
>>        https://mojo.redhat.com/docs/DOC-977658
>>
>> Proposed Solution:
>>
>> - Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries for 
>> product
>> groupings and establish
>>   JBTIS/ JBDSIS installers based on JBT/ JBDS.
>>
>>   Discussion:
>>   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.)
>>
>>   Solution Details:
>>
>>   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?
>>
>>   - https://issues.jboss.org/browse/JBTIS-354
>>
>>     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.
>>
>>   - https://issues.jboss.org/browse/JBTIS-355
>>
>>     * 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)
>>       - https://issues.jboss.org/browse/JBTIS-290
>>     * create three connectors, each based on the content in JBDSIS
>>     discovery plugin.xml's top three
>>       connector categories
>>       - https://issues.jboss.org/browse/JBTIS-357
>>
>>       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
>>
>>   - https://issues.jboss.org/browse/JBTIS-356/
>>   https://issues.jboss.org/browse/JBIDE-18734
>>     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.
>>
>>      --paull
>>
>>


/max
http://about.me/maxandersen

From gorkem.ercan at gmail.com  Mon Nov 17 07:08:23 2014
From: gorkem.ercan at gmail.com (Gorkem Ercan)
Date: Mon, 17 Nov 2014 07:08:23 -0500
Subject: [jbosstools-dev] Aerogear name change proposal
In-Reply-To: <6339D9FF-DD8B-48B6-BC86-FF86A0300FDD@redhat.com>
References: <758280146.11169162.1415894378569.JavaMail.zimbra@redhat.com>
	<2D6C6F5C-7FF5-4D1E-BD0C-D8B7AEE5DA6A@redhat.com>
	<1104260395.7616026.1415956992157.JavaMail.zimbra@redhat.com>
	<3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
	<257111387.7666295.1415963265715.JavaMail.zimbra@redhat.com>
	<6339D9FF-DD8B-48B6-BC86-FF86A0300FDD@redhat.com>
Message-ID: <CA+X37cmRhj45U1bgO9KWxmqT94qX4Dstic=CVEy771mS1VBTHA@mail.gmail.com>

The plan was to tool the bits coming in from aearogear. I think we are
still doing that but that will be under FeeedHenry umbrella now.
I am OK with changing the Aerogear to something like Mobile on the web site
because it describes the product better. I guess we can
add the FeedHenry things when they come under mobile at the web site.

Aerogear is actually the name of the community project that builds software
for mobile development. I do not think having the aerogear name on
the jbosstool-aerogear repo, jira and the package names would hurt. So
let's keep them as it is and only modify the website.
--
Gorkem


On Fri, Nov 14, 2014 at 1:13 PM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> On 14 Nov 2014, at 12:07, Petr Stribny wrote:
>
> > Hi all,
> >
> > 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.
>
> Gorkem is on the aerogear team. Aerogear is used in the bundle/feature
> names for aerogear specific stuff (like the examples).
>
> I'm not really much for renaming it, more like making it more specific
> and add a hybrid-mobile component (we can move the issues over if we
> want to).
>
> Gorkem - any preference ? Earlier on there were plans about more
> specific aerogear tools but that have not (yet) manifested itself.
>
> /max
>
>
> >
> > 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?
> >
> > --Petr
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141117/8a091c95/attachment.html 

From aileenc at redhat.com  Mon Nov 17 07:27:45 2014
From: aileenc at redhat.com (Aileen Cunningham)
Date: Mon, 17 Nov 2014 07:27:45 -0500 (EST)
Subject: [jbosstools-dev] integration stack component installation
In-Reply-To: <BB552E73-CFC3-46D7-A1B7-E4F335B3C452@redhat.com>
References: <477333601.9650309.1415997798282.JavaMail.zimbra@redhat.com>
	<942930017.15619955.1416218670741.JavaMail.zimbra@redhat.com>
	<BB552E73-CFC3-46D7-A1B7-E4F335B3C452@redhat.com>
Message-ID: <1535880115.15757239.1416227265808.JavaMail.zimbra@redhat.com>


The Eclipse tooling is mentioned on this page but not prominently enough - if we move the info on Tooling up beside the Download button for the runtime then that may help in the interim.

http://www.jboss.org/products/fuse/overview/

----- Original Message -----
> From: "Max Rydahl Andersen" <manderse at redhat.com>
> To: "Aileen Cunningham" <aileenc at redhat.com>
> Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
> jbds-is-pm-list at redhat.com, "JDV-PM Mailing List" <jdv-pm at redhat.com>, "Mustafa Musaji" <mmusaji at redhat.com>,
> "Fuse-pm-list" <fuse-pm-list at redhat.com>, "bpms-pm-list" <bpms-pm-list at redhat.com>
> Sent: Monday, 17 November, 2014 11:47:13 AM
> Subject: Re: integration stack component installation
> 
> On 17 Nov 2014, at 11:04, Aileen Cunningham wrote:
> 
> > Hi Paul,
> >
> > when you say "establish JBTIS/ JBDSIS installers based on JBT/ JBDS"
> > are you talking about a combined installer where you can install JBDS
> > + IS in 1 action?
> 
> Yes. But this requires work/QE resources.
> 
> > People can find the runtime download on JBoss.org fairly easily so
> > what we need to get to is a 2nd big green download button on the Fuse
> > product page that installs the relevant Tooling.
> 
> Can we start by putting existing devstudio installer there now ? (last
> time I looked it was not even mentioning it)
> 
> I believe your team is "owner" of those pages or at least should be able
> to request the best changes to them.
> 
> If not let me know what pages you believe should be changed and I can
> help track it down.
> 
> /max
> 
> >
> > best regards,
> > Aileen
> >
> >
> > ----- Original Message -----
> >> From: "Paul Leacu" <pleacu at redhat.com>
> >> To: "Kevin Conner" <kconner at redhat.com>, "Max Rydahl Andersen"
> >> <max.andersen at redhat.com>, "Aileen Cunningham"
> >> <aileenc at redhat.com>
> >> Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "jbosstools-dev
> >> jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
> >> jbds-is-pm-list at redhat.com, "JDV-PM Mailing List"
> >> <jdv-pm at redhat.com>, "Mustafa Musaji" <mmusaji at redhat.com>,
> >> "Fuse-pm-list" <fuse-pm-list at redhat.com>, "bpms-pm-list"
> >> <bpms-pm-list at redhat.com>
> >> Sent: Friday, 14 November, 2014 8:43:18 PM
> >> Subject: integration stack component installation
> >>
> >>
> >> Greetings,
> >>    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!
> >>
> >> Thanks,
> >>        --paull
> >>
> >> ------
> >>
> >> 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:
> >>
> >>        https://mojo.redhat.com/docs/DOC-977658
> >>
> >> Proposed Solution:
> >>
> >> - Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries for
> >> product
> >> groupings and establish
> >>   JBTIS/ JBDSIS installers based on JBT/ JBDS.
> >>
> >>   Discussion:
> >>   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.)
> >>
> >>   Solution Details:
> >>
> >>   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?
> >>
> >>   - https://issues.jboss.org/browse/JBTIS-354
> >>
> >>     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.
> >>
> >>   - https://issues.jboss.org/browse/JBTIS-355
> >>
> >>     * 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)
> >>       - https://issues.jboss.org/browse/JBTIS-290
> >>     * create three connectors, each based on the content in JBDSIS
> >>     discovery plugin.xml's top three
> >>       connector categories
> >>       - https://issues.jboss.org/browse/JBTIS-357
> >>
> >>       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
> >>
> >>   - https://issues.jboss.org/browse/JBTIS-356/
> >>   https://issues.jboss.org/browse/JBIDE-18734
> >>     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.
> >>
> >>      --paull
> >>
> >>
> 
> 
> /max
> http://about.me/maxandersen
> 
> 

From ldimaggi at redhat.com  Mon Nov 17 09:50:14 2014
From: ldimaggi at redhat.com (Len DiMaggio)
Date: Mon, 17 Nov 2014 09:50:14 -0500 (EST)
Subject: [jbosstools-dev] integration stack component installation
In-Reply-To: <942930017.15619955.1416218670741.JavaMail.zimbra@redhat.com>
References: <477333601.9650309.1415997798282.JavaMail.zimbra@redhat.com>
	<942930017.15619955.1416218670741.JavaMail.zimbra@redhat.com>
Message-ID: <734858450.12578334.1416235814971.JavaMail.zimbra@redhat.com>

Paul and Alan - Isn't the plan to add a menu at the end of the JBDS installer - from which the user can select to install some/all of the tooling - all from within one installer? 

-- Len 

----- Original Message -----

| From: "Aileen Cunningham" <aileenc at redhat.com>
| To: "Paul Leacu" <pleacu at redhat.com>
| Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "Max Rydahl Andersen"
| <max.andersen at redhat.com>, jbds-is-pm-list at redhat.com, "jbosstools-dev
| jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "JDV-PM Mailing List"
| <jdv-pm at redhat.com>, "bpms-pm-list" <bpms-pm-list at redhat.com>,
| "Fuse-pm-list" <fuse-pm-list at redhat.com>, "Mustafa Musaji"
| <mmusaji at redhat.com>
| Sent: Monday, November 17, 2014 5:04:30 AM
| Subject: Re: integration stack component installation

| Hi Paul,

| when you say "establish JBTIS/ JBDSIS installers based on JBT/ JBDS" are you
| talking about a combined installer where you can install JBDS + IS in 1
| action?

| People can find the runtime download on JBoss.org fairly easily so what we
| need to get to is a 2nd big green download button on the Fuse product page
| that installs the relevant Tooling.

| best regards,
| Aileen

| ----- Original Message -----
| > From: "Paul Leacu" <pleacu at redhat.com>
| > To: "Kevin Conner" <kconner at redhat.com>, "Max Rydahl Andersen"
| > <max.andersen at redhat.com>, "Aileen Cunningham"
| > <aileenc at redhat.com>
| > Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "jbosstools-dev
| > jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
| > jbds-is-pm-list at redhat.com, "JDV-PM Mailing List" <jdv-pm at redhat.com>,
| > "Mustafa Musaji" <mmusaji at redhat.com>,
| > "Fuse-pm-list" <fuse-pm-list at redhat.com>, "bpms-pm-list"
| > <bpms-pm-list at redhat.com>
| > Sent: Friday, 14 November, 2014 8:43:18 PM
| > Subject: integration stack component installation
| >
| >
| > Greetings,
| > 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!
| >
| > Thanks,
| > --paull
| >
| > ------
| >
| > 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:
| >
| > https://mojo.redhat.com/docs/DOC-977658
| >
| > Proposed Solution:
| >
| > - Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries for product
| > groupings and establish
| > JBTIS/ JBDSIS installers based on JBT/ JBDS.
| >
| > Discussion:
| > 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.)
| >
| > Solution Details:
| >
| > 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?
| >
| > - https://issues.jboss.org/browse/JBTIS-354
| >
| > 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.
| >
| > - https://issues.jboss.org/browse/JBTIS-355
| >
| > * 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)
| > - https://issues.jboss.org/browse/JBTIS-290
| > * create three connectors, each based on the content in JBDSIS
| > discovery plugin.xml's top three
| > connector categories
| > - https://issues.jboss.org/browse/JBTIS-357
| >
| > 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
| >
| > - https://issues.jboss.org/browse/JBTIS-356/
| > https://issues.jboss.org/browse/JBIDE-18734
| > 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.
| >
| > --paull
| >
| >

-- 

Len DiMaggio (ldimaggi at redhat.com) 
JBoss by Red Hat 
314 Littleton Road 
Westford, MA 01886 USA 
tel: 978.392.3179 
cell: 781.472.9912 
http://www.redhat.com 
http://community.jboss.org/people/ldimaggio 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141117/2dc766f3/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RHxJBpngthumb.png
Type: image/png
Size: 9435 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141117/2dc766f3/attachment-0001.png 

From ldimaggi at redhat.com  Mon Nov 17 10:59:14 2014
From: ldimaggi at redhat.com (Len DiMaggio)
Date: Mon, 17 Nov 2014 10:59:14 -0500 (EST)
Subject: [jbosstools-dev] integration stack component installation
In-Reply-To: <BB552E73-CFC3-46D7-A1B7-E4F335B3C452@redhat.com>
References: <477333601.9650309.1415997798282.JavaMail.zimbra@redhat.com>
	<942930017.15619955.1416218670741.JavaMail.zimbra@redhat.com>
	<BB552E73-CFC3-46D7-A1B7-E4F335B3C452@redhat.com>
Message-ID: <229670538.12634987.1416239954316.JavaMail.zimbra@redhat.com>

Will this help: 

(Max) Can we start by putting existing devstudio installer there now ? (last time I looked it was not even mentioning it) 

I thought that the problem was that after users had installed JBDS, they could not locate the appropriate tooling? 

-- Len 

----- Original Message -----

| From: "Max Rydahl Andersen" <manderse at redhat.com>
| To: "Aileen Cunningham" <aileenc at redhat.com>
| Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "jbosstools-dev
| jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
| jbds-is-pm-list at redhat.com, "JDV-PM Mailing List" <jdv-pm at redhat.com>,
| "Mustafa Musaji" <mmusaji at redhat.com>, "Fuse-pm-list"
| <fuse-pm-list at redhat.com>, "bpms-pm-list" <bpms-pm-list at redhat.com>
| Sent: Monday, November 17, 2014 6:47:13 AM
| Subject: Re: integration stack component installation

| On 17 Nov 2014, at 11:04, Aileen Cunningham wrote:

| > Hi Paul,
| >
| > when you say "establish JBTIS/ JBDSIS installers based on JBT/ JBDS"
| > are you talking about a combined installer where you can install JBDS
| > + IS in 1 action?

| Yes. But this requires work/QE resources.

| > People can find the runtime download on JBoss.org fairly easily so
| > what we need to get to is a 2nd big green download button on the Fuse
| > product page that installs the relevant Tooling.

| Can we start by putting existing devstudio installer there now ? (last
| time I looked it was not even mentioning it)

| I believe your team is "owner" of those pages or at least should be able
| to request the best changes to them.

| If not let me know what pages you believe should be changed and I can
| help track it down.

| /max

| >
| > best regards,
| > Aileen
| >
| >
| > ----- Original Message -----
| >> From: "Paul Leacu" <pleacu at redhat.com>
| >> To: "Kevin Conner" <kconner at redhat.com>, "Max Rydahl Andersen"
| >> <max.andersen at redhat.com>, "Aileen Cunningham"
| >> <aileenc at redhat.com>
| >> Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "jbosstools-dev
| >> jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
| >> jbds-is-pm-list at redhat.com, "JDV-PM Mailing List"
| >> <jdv-pm at redhat.com>, "Mustafa Musaji" <mmusaji at redhat.com>,
| >> "Fuse-pm-list" <fuse-pm-list at redhat.com>, "bpms-pm-list"
| >> <bpms-pm-list at redhat.com>
| >> Sent: Friday, 14 November, 2014 8:43:18 PM
| >> Subject: integration stack component installation
| >>
| >>
| >> Greetings,
| >> 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!
| >>
| >> Thanks,
| >> --paull
| >>
| >> ------
| >>
| >> 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:
| >>
| >> https://mojo.redhat.com/docs/DOC-977658
| >>
| >> Proposed Solution:
| >>
| >> - Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries for
| >> product
| >> groupings and establish
| >> JBTIS/ JBDSIS installers based on JBT/ JBDS.
| >>
| >> Discussion:
| >> 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.)
| >>
| >> Solution Details:
| >>
| >> 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?
| >>
| >> - https://issues.jboss.org/browse/JBTIS-354
| >>
| >> 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.
| >>
| >> - https://issues.jboss.org/browse/JBTIS-355
| >>
| >> * 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)
| >> - https://issues.jboss.org/browse/JBTIS-290
| >> * create three connectors, each based on the content in JBDSIS
| >> discovery plugin.xml's top three
| >> connector categories
| >> - https://issues.jboss.org/browse/JBTIS-357
| >>
| >> 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
| >>
| >> - https://issues.jboss.org/browse/JBTIS-356/
| >> https://issues.jboss.org/browse/JBIDE-18734
| >> 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.
| >>
| >> --paull
| >>
| >>

| /max
| http://about.me/maxandersen

-- 

Len DiMaggio (ldimaggi at redhat.com) 
JBoss by Red Hat 
314 Littleton Road 
Westford, MA 01886 USA 
tel: 978.392.3179 
cell: 781.472.9912 
http://www.redhat.com 
http://community.jboss.org/people/ldimaggio 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141117/4580a03e/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RHxJBpngthumb.png
Type: image/png
Size: 9435 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141117/4580a03e/attachment-0001.png 

From gorkem.ercan at gmail.com  Mon Nov 17 11:55:12 2014
From: gorkem.ercan at gmail.com (Gorkem Ercan)
Date: Mon, 17 Nov 2014 11:55:12 -0500
Subject: [jbosstools-dev] Jira component for cordovasim
Message-ID: <CA+X37ckBoqFWS+AMPzbSDwKFT5jwaxiyyCweR=UZNUUCuwY7gg@mail.gmail.com>

Should we create a new Jira component for cordovasim? I think cordovasim
issues are different from browsersim and this is what we use for them right
now.
--
Gorkem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141117/a797c97e/attachment.html 

From manderse at redhat.com  Mon Nov 17 11:58:57 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 17 Nov 2014 17:58:57 +0100
Subject: [jbosstools-dev] Aerogear name change proposal
In-Reply-To: <CA+X37cmRhj45U1bgO9KWxmqT94qX4Dstic=CVEy771mS1VBTHA@mail.gmail.com>
References: <758280146.11169162.1415894378569.JavaMail.zimbra@redhat.com>
	<2D6C6F5C-7FF5-4D1E-BD0C-D8B7AEE5DA6A@redhat.com>
	<1104260395.7616026.1415956992157.JavaMail.zimbra@redhat.com>
	<3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
	<257111387.7666295.1415963265715.JavaMail.zimbra@redhat.com>
	<6339D9FF-DD8B-48B6-BC86-FF86A0300FDD@redhat.com>
	<CA+X37cmRhj45U1bgO9KWxmqT94qX4Dstic=CVEy771mS1VBTHA@mail.gmail.com>
Message-ID: <67A16944-8393-4665-B08E-A3800B02775D@redhat.com>

On 17 Nov 2014, at 13:08, Gorkem Ercan wrote:

> The plan was to tool the bits coming in from aearogear. I think we are
> still doing that but that will be under FeeedHenry umbrella now.
> I am OK with changing the Aerogear to something like Mobile on the web 
> site
> because it describes the product better. I guess we can
> add the FeedHenry things when they come under mobile at the web site.
>
> Aerogear is actually the name of the community project that builds 
> software
> for mobile development. I do not think having the aerogear name on
> the jbosstool-aerogear repo, jira and the package names would hurt. So
> let's keep them as it is and only modify the website.

if we call it mobile everywhere but don't have matching jira component 
that would be a bad/confusing thing IMO.

I would like to have a proper separate name for it if possible that can 
be used as component name too.

Hybrid Mobile ?

Aerogear Hybrid ?

Any takes ?

/max

> Gorkem
>
>
> On Fri, Nov 14, 2014 at 1:13 PM, Max Rydahl Andersen 
> <manderse at redhat.com>
> wrote:
>
>> On 14 Nov 2014, at 12:07, Petr Stribny wrote:
>>
>>> Hi all,
>>>
>>> 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.
>>
>> Gorkem is on the aerogear team. Aerogear is used in the 
>> bundle/feature
>> names for aerogear specific stuff (like the examples).
>>
>> I'm not really much for renaming it, more like making it more 
>> specific
>> and add a hybrid-mobile component (we can move the issues over if we
>> want to).
>>
>> Gorkem - any preference ? Earlier on there were plans about more
>> specific aerogear tools but that have not (yet) manifested itself.
>>
>> /max
>>
>>
>>>
>>> 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?
>>>
>>> --Petr
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>> /max
>> http://about.me/maxandersen
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>


/max
http://about.me/maxandersen

From manderse at redhat.com  Mon Nov 17 12:01:16 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 17 Nov 2014 18:01:16 +0100
Subject: [jbosstools-dev] integration stack component installation
In-Reply-To: <229670538.12634987.1416239954316.JavaMail.zimbra@redhat.com>
References: <477333601.9650309.1415997798282.JavaMail.zimbra@redhat.com>
	<942930017.15619955.1416218670741.JavaMail.zimbra@redhat.com>
	<BB552E73-CFC3-46D7-A1B7-E4F335B3C452@redhat.com>
	<229670538.12634987.1416239954316.JavaMail.zimbra@redhat.com>
Message-ID: <178EC914-4420-4337-840A-F61AE272F96E@redhat.com>

On 17 Nov 2014, at 16:59, Len DiMaggio wrote:

> Will this help:
>
> (Max) Can we start by putting existing devstudio installer there now ? 
> (last time I looked it was not even mentioning it)
>
> I thought that the problem was that after users had installed JBDS, 
> they could not locate the appropriate tooling?

That was part of it - some others did not even know that they could 
download *any* tools today.

The fact the main Fuse page does not even mention it before several 
pages down is something that can be fixed easily and today
versus new installer setup and then still need to add link to the fuse 
pages ;)

/max

> -- Len
>
> ----- Original Message -----
>
> | From: "Max Rydahl Andersen" <manderse at redhat.com>
> | To: "Aileen Cunningham" <aileenc at redhat.com>
> | Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "jbosstools-dev
> | jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
> | jbds-is-pm-list at redhat.com, "JDV-PM Mailing List" 
> <jdv-pm at redhat.com>,
> | "Mustafa Musaji" <mmusaji at redhat.com>, "Fuse-pm-list"
> | <fuse-pm-list at redhat.com>, "bpms-pm-list" <bpms-pm-list at redhat.com>
> | Sent: Monday, November 17, 2014 6:47:13 AM
> | Subject: Re: integration stack component installation
>
> | On 17 Nov 2014, at 11:04, Aileen Cunningham wrote:
>
> | > Hi Paul,
> | >
> | > when you say "establish JBTIS/ JBDSIS installers based on JBT/ 
> JBDS"
> | > are you talking about a combined installer where you can install 
> JBDS
> | > + IS in 1 action?
>
> | Yes. But this requires work/QE resources.
>
> | > People can find the runtime download on JBoss.org fairly easily so
> | > what we need to get to is a 2nd big green download button on the 
> Fuse
> | > product page that installs the relevant Tooling.
>
> | Can we start by putting existing devstudio installer there now ? 
> (last
> | time I looked it was not even mentioning it)
>
> | I believe your team is "owner" of those pages or at least should be 
> able
> | to request the best changes to them.
>
> | If not let me know what pages you believe should be changed and I 
> can
> | help track it down.
>
> | /max
>
> | >
> | > best regards,
> | > Aileen
> | >
> | >
> | > ----- Original Message -----
> | >> From: "Paul Leacu" <pleacu at redhat.com>
> | >> To: "Kevin Conner" <kconner at redhat.com>, "Max Rydahl Andersen"
> | >> <max.andersen at redhat.com>, "Aileen Cunningham"
> | >> <aileenc at redhat.com>
> | >> Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "jbosstools-dev
> | >> jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
> | >> jbds-is-pm-list at redhat.com, "JDV-PM Mailing List"
> | >> <jdv-pm at redhat.com>, "Mustafa Musaji" <mmusaji at redhat.com>,
> | >> "Fuse-pm-list" <fuse-pm-list at redhat.com>, "bpms-pm-list"
> | >> <bpms-pm-list at redhat.com>
> | >> Sent: Friday, 14 November, 2014 8:43:18 PM
> | >> Subject: integration stack component installation
> | >>
> | >>
> | >> Greetings,
> | >> 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!
> | >>
> | >> Thanks,
> | >> --paull
> | >>
> | >> ------
> | >>
> | >> 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:
> | >>
> | >> https://mojo.redhat.com/docs/DOC-977658
> | >>
> | >> Proposed Solution:
> | >>
> | >> - Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries 
> for
> | >> product
> | >> groupings and establish
> | >> JBTIS/ JBDSIS installers based on JBT/ JBDS.
> | >>
> | >> Discussion:
> | >> 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.)
> | >>
> | >> Solution Details:
> | >>
> | >> 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?
> | >>
> | >> - https://issues.jboss.org/browse/JBTIS-354
> | >>
> | >> 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.
> | >>
> | >> - https://issues.jboss.org/browse/JBTIS-355
> | >>
> | >> * 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)
> | >> - https://issues.jboss.org/browse/JBTIS-290
> | >> * create three connectors, each based on the content in JBDSIS
> | >> discovery plugin.xml's top three
> | >> connector categories
> | >> - https://issues.jboss.org/browse/JBTIS-357
> | >>
> | >> 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
> | >>
> | >> - https://issues.jboss.org/browse/JBTIS-356/
> | >> https://issues.jboss.org/browse/JBIDE-18734
> | >> 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.
> | >>
> | >> --paull
> | >>
> | >>
>
> | /max
> | http://about.me/maxandersen
>
> -- 
>
> Len DiMaggio (ldimaggi at redhat.com)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886 USA
> tel: 978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio


/max
http://about.me/maxandersen

From gorkem.ercan at gmail.com  Mon Nov 17 12:04:14 2014
From: gorkem.ercan at gmail.com (Gorkem Ercan)
Date: Mon, 17 Nov 2014 12:04:14 -0500
Subject: [jbosstools-dev] Aerogear name change proposal
In-Reply-To: <67A16944-8393-4665-B08E-A3800B02775D@redhat.com>
References: <758280146.11169162.1415894378569.JavaMail.zimbra@redhat.com>
	<2D6C6F5C-7FF5-4D1E-BD0C-D8B7AEE5DA6A@redhat.com>
	<1104260395.7616026.1415956992157.JavaMail.zimbra@redhat.com>
	<3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
	<257111387.7666295.1415963265715.JavaMail.zimbra@redhat.com>
	<6339D9FF-DD8B-48B6-BC86-FF86A0300FDD@redhat.com>
	<CA+X37cmRhj45U1bgO9KWxmqT94qX4Dstic=CVEy771mS1VBTHA@mail.gmail.com>
	<67A16944-8393-4665-B08E-A3800B02775D@redhat.com>
Message-ID: <CA+X37ckN9aOr3XGv-PJwPiQWKZQRke4YErtAcVbxVHqc0vRUdg@mail.gmail.com>

On Mon, Nov 17, 2014 at 11:58 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> On 17 Nov 2014, at 13:08, Gorkem Ercan wrote:
>
>  The plan was to tool the bits coming in from aearogear. I think we are
>> still doing that but that will be under FeeedHenry umbrella now.
>> I am OK with changing the Aerogear to something like Mobile on the web
>> site
>> because it describes the product better. I guess we can
>> add the FeedHenry things when they come under mobile at the web site.
>>
>> Aerogear is actually the name of the community project that builds
>> software
>> for mobile development. I do not think having the aerogear name on
>> the jbosstool-aerogear repo, jira and the package names would hurt. So
>> let's keep them as it is and only modify the website.
>>
>
> if we call it mobile everywhere but don't have matching jira component
> that would be a bad/confusing thing IMO.
>
> I would like to have a proper separate name for it if possible that can be
> used as component name too.
>
> Hybrid Mobile ?
>
> Aerogear Hybrid ?
>


Problem solved, the current Jira component is already called
aerogear-hybrid..


>
> Any takes ?
>
> /max
>
>
>  Gorkem
>>
>>
>> On Fri, Nov 14, 2014 at 1:13 PM, Max Rydahl Andersen <manderse at redhat.com
>> >
>> wrote:
>>
>>  On 14 Nov 2014, at 12:07, Petr Stribny wrote:
>>>
>>>  Hi all,
>>>>
>>>> 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.
>>>>
>>>
>>> Gorkem is on the aerogear team. Aerogear is used in the bundle/feature
>>> names for aerogear specific stuff (like the examples).
>>>
>>> I'm not really much for renaming it, more like making it more specific
>>> and add a hybrid-mobile component (we can move the issues over if we
>>> want to).
>>>
>>> Gorkem - any preference ? Earlier on there were plans about more
>>> specific aerogear tools but that have not (yet) manifested itself.
>>>
>>> /max
>>>
>>>
>>>
>>>> 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?
>>>>
>>>> --Petr
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>
> /max
> http://about.me/maxandersen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141117/d8075eb0/attachment.html 

From manderse at redhat.com  Mon Nov 17 12:05:10 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 17 Nov 2014 18:05:10 +0100
Subject: [jbosstools-dev] Jira component for cordovasim
In-Reply-To: <CA+X37ckBoqFWS+AMPzbSDwKFT5jwaxiyyCweR=UZNUUCuwY7gg@mail.gmail.com>
References: <CA+X37ckBoqFWS+AMPzbSDwKFT5jwaxiyyCweR=UZNUUCuwY7gg@mail.gmail.com>
Message-ID: <642304DF-AE76-4D27-A3AF-7461C134C89B@redhat.com>

On 17 Nov 2014, at 17:55, Gorkem Ercan wrote:

> Should we create a new Jira component for cordovasim? I think 
> cordovasim
> issues are different from browsersim and this is what we use for them 
> right
> now.

I guess cordovasim is different enough with all the ripple stuff so if 
you guys want that I can go create it on jbide and jbds.

Konstantin, Ilya - what say you ?

/max
http://about.me/maxandersen

From ldimaggi at redhat.com  Mon Nov 17 12:14:12 2014
From: ldimaggi at redhat.com (Len DiMaggio)
Date: Mon, 17 Nov 2014 12:14:12 -0500 (EST)
Subject: [jbosstools-dev] Jira component for cordovasim
In-Reply-To: <CA+X37ckBoqFWS+AMPzbSDwKFT5jwaxiyyCweR=UZNUUCuwY7gg@mail.gmail.com>
References: <CA+X37ckBoqFWS+AMPzbSDwKFT5jwaxiyyCweR=UZNUUCuwY7gg@mail.gmail.com>
Message-ID: <1172867097.12679790.1416244452124.JavaMail.zimbra@redhat.com>

YES! (That's the QE vote...) 

----- Original Message -----

| From: "Gorkem Ercan" <gorkem.ercan at gmail.com>
| To: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
| Sent: Monday, November 17, 2014 11:55:12 AM
| Subject: [jbosstools-dev] Jira component for cordovasim

| Should we create a new Jira component for cordovasim? I think cordovasim
| issues are different from browsersim and this is what we use for them right
| now.
| --
| Gorkem

| _______________________________________________
| jbosstools-dev mailing list
| jbosstools-dev at lists.jboss.org
| https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-- 

Len DiMaggio (ldimaggi at redhat.com) 
JBoss by Red Hat 
314 Littleton Road 
Westford, MA 01886 USA 
tel: 978.392.3179 
cell: 781.472.9912 
http://www.redhat.com 
http://community.jboss.org/people/ldimaggio 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141117/a62d9450/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RHxJBpngthumb.png
Type: image/png
Size: 9435 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141117/a62d9450/attachment.png 

From aileenc at redhat.com  Mon Nov 17 12:20:12 2014
From: aileenc at redhat.com (Aileen Cunningham)
Date: Mon, 17 Nov 2014 12:20:12 -0500 (EST)
Subject: [jbosstools-dev] integration stack component installation
In-Reply-To: <178EC914-4420-4337-840A-F61AE272F96E@redhat.com>
References: <477333601.9650309.1415997798282.JavaMail.zimbra@redhat.com>
	<942930017.15619955.1416218670741.JavaMail.zimbra@redhat.com>
	<BB552E73-CFC3-46D7-A1B7-E4F335B3C452@redhat.com>
	<229670538.12634987.1416239954316.JavaMail.zimbra@redhat.com>
	<178EC914-4420-4337-840A-F61AE272F96E@redhat.com>
Message-ID: <629264103.171697.1416244812202.JavaMail.zimbra@redhat.com>



Agreed I just logged https://issues.jboss.org/browse/DEVELOPER-1103

to get the info on Eclipse Tooling moved to a more prominent position on the product page.

Aileen

> That was part of it - some others did not even know that they could
> download *any* tools today.
> 
> The fact the main Fuse page does not even mention it before several
> pages down is something that can be fixed easily and today
> versus new installer setup and then still need to add link to the fuse
> pages ;)
> 
> /max
> 
> > -- Len
> >
> > ----- Original Message -----
> >
> > | From: "Max Rydahl Andersen" <manderse at redhat.com>
> > | To: "Aileen Cunningham" <aileenc at redhat.com>
> > | Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "jbosstools-dev
> > | jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
> > | jbds-is-pm-list at redhat.com, "JDV-PM Mailing List"
> > <jdv-pm at redhat.com>,
> > | "Mustafa Musaji" <mmusaji at redhat.com>, "Fuse-pm-list"
> > | <fuse-pm-list at redhat.com>, "bpms-pm-list" <bpms-pm-list at redhat.com>
> > | Sent: Monday, November 17, 2014 6:47:13 AM
> > | Subject: Re: integration stack component installation
> >
> > | On 17 Nov 2014, at 11:04, Aileen Cunningham wrote:
> >
> > | > Hi Paul,
> > | >
> > | > when you say "establish JBTIS/ JBDSIS installers based on JBT/
> > JBDS"
> > | > are you talking about a combined installer where you can install
> > JBDS
> > | > + IS in 1 action?
> >
> > | Yes. But this requires work/QE resources.
> >
> > | > People can find the runtime download on JBoss.org fairly easily so
> > | > what we need to get to is a 2nd big green download button on the
> > Fuse
> > | > product page that installs the relevant Tooling.
> >
> > | Can we start by putting existing devstudio installer there now ?
> > (last
> > | time I looked it was not even mentioning it)
> >
> > | I believe your team is "owner" of those pages or at least should be
> > able
> > | to request the best changes to them.
> >
> > | If not let me know what pages you believe should be changed and I
> > can
> > | help track it down.
> >
> > | /max
> >
> > | >
> > | > best regards,
> > | > Aileen
> > | >
> > | >
> > | > ----- Original Message -----
> > | >> From: "Paul Leacu" <pleacu at redhat.com>
> > | >> To: "Kevin Conner" <kconner at redhat.com>, "Max Rydahl Andersen"
> > | >> <max.andersen at redhat.com>, "Aileen Cunningham"
> > | >> <aileenc at redhat.com>
> > | >> Cc: "soa-pm-list List" <soa-pm-list at redhat.com>, "jbosstools-dev
> > | >> jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
> > | >> jbds-is-pm-list at redhat.com, "JDV-PM Mailing List"
> > | >> <jdv-pm at redhat.com>, "Mustafa Musaji" <mmusaji at redhat.com>,
> > | >> "Fuse-pm-list" <fuse-pm-list at redhat.com>, "bpms-pm-list"
> > | >> <bpms-pm-list at redhat.com>
> > | >> Sent: Friday, 14 November, 2014 8:43:18 PM
> > | >> Subject: integration stack component installation
> > | >>
> > | >>
> > | >> Greetings,
> > | >> 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!
> > | >>
> > | >> Thanks,
> > | >> --paull
> > | >>
> > | >> ------
> > | >>
> > | >> 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:
> > | >>
> > | >> https://mojo.redhat.com/docs/DOC-977658
> > | >>
> > | >> Proposed Solution:
> > | >>
> > | >> - Extend Eclipse Marketplace by enabling JBTIS/ JBDSIS entries
> > for
> > | >> product
> > | >> groupings and establish
> > | >> JBTIS/ JBDSIS installers based on JBT/ JBDS.
> > | >>
> > | >> Discussion:
> > | >> 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.)
> > | >>
> > | >> Solution Details:
> > | >>
> > | >> 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?
> > | >>
> > | >> - https://issues.jboss.org/browse/JBTIS-354
> > | >>
> > | >> 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.
> > | >>
> > | >> - https://issues.jboss.org/browse/JBTIS-355
> > | >>
> > | >> * 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)
> > | >> - https://issues.jboss.org/browse/JBTIS-290
> > | >> * create three connectors, each based on the content in JBDSIS
> > | >> discovery plugin.xml's top three
> > | >> connector categories
> > | >> - https://issues.jboss.org/browse/JBTIS-357
> > | >>
> > | >> 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
> > | >>
> > | >> - https://issues.jboss.org/browse/JBTIS-356/
> > | >> https://issues.jboss.org/browse/JBIDE-18734
> > | >> 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.
> > | >>
> > | >> --paull
> > | >>
> > | >>
> >
> > | /max
> > | http://about.me/maxandersen
> >
> > --
> >
> > Len DiMaggio (ldimaggi at redhat.com)
> > JBoss by Red Hat
> > 314 Littleton Road
> > Westford, MA 01886 USA
> > tel: 978.392.3179
> > cell: 781.472.9912
> > http://www.redhat.com
> > http://community.jboss.org/people/ldimaggio
> 
> 
> /max
> http://about.me/maxandersen
> 
> 

From kmarmaliykov at exadel.com  Mon Nov 17 14:30:36 2014
From: kmarmaliykov at exadel.com (Konstantin Marmalyukov)
Date: Mon, 17 Nov 2014 22:30:36 +0300
Subject: [jbosstools-dev] Jira component for cordovasim
In-Reply-To: <642304DF-AE76-4D27-A3AF-7461C134C89B@redhat.com>
References: <CA+X37ckBoqFWS+AMPzbSDwKFT5jwaxiyyCweR=UZNUUCuwY7gg@mail.gmail.com>
	<642304DF-AE76-4D27-A3AF-7461C134C89B@redhat.com>
Message-ID: <546A4CDC.4030005@exadel.com>

Actually we told about that some time ago. Without success. So we 
*should* do it!

On 11/17/2014 8:05 PM, Max Rydahl Andersen wrote:
> On 17 Nov 2014, at 17:55, Gorkem Ercan wrote:
>
>> Should we create a new Jira component for cordovasim? I think
>> cordovasim
>> issues are different from browsersim and this is what we use for them
>> right
>> now.
> I guess cordovasim is different enough with all the ripple stuff so if
> you guys want that I can go create it on jbide and jbds.
>
> Konstantin, Ilya - what say you ?
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From manderse at redhat.com  Mon Nov 17 18:18:18 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 17 Nov 2014 18:18:18 -0500 (EST)
Subject: [jbosstools-dev] Aerogear name change proposal
In-Reply-To: <CA+X37ckN9aOr3XGv-PJwPiQWKZQRke4YErtAcVbxVHqc0vRUdg@mail.gmail.com>
References: <758280146.11169162.1415894378569.JavaMail.zimbra@redhat.com>
	<2D6C6F5C-7FF5-4D1E-BD0C-D8B7AEE5DA6A@redhat.com>
	<1104260395.7616026.1415956992157.JavaMail.zimbra@redhat.com>
	<3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
	<257111387.7666295.1415963265715.JavaMail.zimbra@redhat.com>
	<6339D9FF-DD8B-48B6-BC86-FF86A0300FDD@redhat.com>
	<CA+X37cmRhj45U1bgO9KWxmqT94qX4Dstic=CVEy771mS1VBTHA@mail.gmail.com>
	<67A16944-8393-4665-B08E-A3800B02775D@redhat.com>
	<CA+X37ckN9aOr3XGv-PJwPiQWKZQRke4YErtAcVbxVHqc0vRUdg@mail.gmail.com>
Message-ID: <CB70E97F-6909-4759-9A22-CE7A9AC9516C@redhat.com>


> On 17 Nov 2014, at 18:04, Gorkem Ercan <gorkem.ercan at gmail.com> wrote:
> 
> 
>> On Mon, Nov 17, 2014 at 11:58 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
>> On 17 Nov 2014, at 13:08, Gorkem Ercan wrote:
>> 
>>> The plan was to tool the bits coming in from aearogear. I think we are
>>> still doing that but that will be under FeeedHenry umbrella now.
>>> I am OK with changing the Aerogear to something like Mobile on the web site
>>> because it describes the product better. I guess we can
>>> add the FeedHenry things when they come under mobile at the web site.
>>> 
>>> Aerogear is actually the name of the community project that builds software
>>> for mobile development. I do not think having the aerogear name on
>>> the jbosstool-aerogear repo, jira and the package names would hurt. So
>>> let's keep them as it is and only modify the website.
>> 
>> if we call it mobile everywhere but don't have matching jira component that would be a bad/confusing thing


>> I would like to have a proper separate name for it if possible that can be used as component name too.
>> 
>> Hybrid Mobile ?
>> 
>> Aerogear Hybrid ?
> 
> 
> Problem solved, the current Jira component is already called aerogear-hybrid.. 

Okey. So nothing need to change ? Now I'm missing the reason for this thread ? :)

Simple. 

/max

>  
>> 
>> Any takes ?
>> 
>> /max
>> 
>> 
>>> Gorkem
>>> 
>>> 
>>> On Fri, Nov 14, 2014 at 1:13 PM, Max Rydahl Andersen <manderse at redhat.com>
>>> wrote:
>>> 
>>>> On 14 Nov 2014, at 12:07, Petr Stribny wrote:
>>>> 
>>>>> Hi all,
>>>>> 
>>>>> 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.
>>>> 
>>>> Gorkem is on the aerogear team. Aerogear is used in the bundle/feature
>>>> names for aerogear specific stuff (like the examples).
>>>> 
>>>> I'm not really much for renaming it, more like making it more specific
>>>> and add a hybrid-mobile component (we can move the issues over if we
>>>> want to).
>>>> 
>>>> Gorkem - any preference ? Earlier on there were plans about more
>>>> specific aerogear tools but that have not (yet) manifested itself.
>>>> 
>>>> /max
>>>> 
>>>> 
>>>>> 
>>>>> 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?
>>>>> 
>>>>> --Petr
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>> 
>>>> 
>>>> /max
>>>> http://about.me/maxandersen
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> 
>> 
>> /max
>> http://about.me/maxandersen
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141117/b68dda4e/attachment.html 

From manderse at redhat.com  Mon Nov 17 18:27:30 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 17 Nov 2014 18:27:30 -0500 (EST)
Subject: [jbosstools-dev] Jira component for cordovasim
In-Reply-To: <546A4CDC.4030005@exadel.com>
References: <CA+X37ckBoqFWS+AMPzbSDwKFT5jwaxiyyCweR=UZNUUCuwY7gg@mail.gmail.com>
	<642304DF-AE76-4D27-A3AF-7461C134C89B@redhat.com>
	<546A4CDC.4030005@exadel.com>
Message-ID: <F4FB44AD-B831-40EC-92D9-534CC203856C@redhat.com>

Well, now you got success. 

Created in both jbide and JBDS Jira. 

Tell me if description/leads are Okey/correct for you. 

/max
http://about.me/maxandersen


> On 17 Nov 2014, at 20:31, Konstantin Marmalyukov <kmarmaliykov at exadel.com> wrote:
> 
> Actually we told about that some time ago. Without success. So we 
> *should* do it!
> 
>> On 11/17/2014 8:05 PM, Max Rydahl Andersen wrote:
>>> On 17 Nov 2014, at 17:55, Gorkem Ercan wrote:
>>> 
>>> Should we create a new Jira component for cordovasim? I think
>>> cordovasim
>>> issues are different from browsersim and this is what we use for them
>>> right
>>> now.
>> I guess cordovasim is different enough with all the ripple stuff so if
>> you guys want that I can go create it on jbide and jbds.
>> 
>> Konstantin, Ilya - what say you ?
>> 
>> /max
>> http://about.me/maxandersen
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From nboldt at redhat.com  Mon Nov 17 18:36:15 2014
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 17 Nov 2014 18:36:15 -0500
Subject: [jbosstools-dev] Jira component for cordovasim
In-Reply-To: <F4FB44AD-B831-40EC-92D9-534CC203856C@redhat.com>
References: <CA+X37ckBoqFWS+AMPzbSDwKFT5jwaxiyyCweR=UZNUUCuwY7gg@mail.gmail.com>	<642304DF-AE76-4D27-A3AF-7461C134C89B@redhat.com>	<546A4CDC.4030005@exadel.com>
	<F4FB44AD-B831-40EC-92D9-534CC203856C@redhat.com>
Message-ID: <546A866F.9050201@redhat.com>

Links to the new components [1], [2], with Ilya Buziak [3] as lead:

[1] 
https://issues.jboss.org/browse/JBIDE/component/12320840/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel

[2] 
https://issues.jboss.org/browse/JBDS/component/12320841/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel

[3] https://issues.jboss.org/secure/ViewProfile.jspa?name=ibuziuk

On 11/17/2014 06:27 PM, Max Rydahl Andersen wrote:
> Well, now you got success.
>
> Created in both jbide and JBDS Jira.
>
> Tell me if description/leads are Okey/correct for you.
>
> /max
> http://about.me/maxandersen
>
>
>> On 17 Nov 2014, at 20:31, Konstantin Marmalyukov <kmarmaliykov at exadel.com> wrote:
>>
>> Actually we told about that some time ago. Without success. So we
>> *should* do it!
>>
>>> On 11/17/2014 8:05 PM, Max Rydahl Andersen wrote:
>>>> On 17 Nov 2014, at 17:55, Gorkem Ercan wrote:
>>>>
>>>> Should we create a new Jira component for cordovasim? I think
>>>> cordovasim
>>>> issues are different from browsersim and this is what we use for them
>>>> right
>>>> now.
>>> I guess cordovasim is different enough with all the ripple stuff so if
>>> you guys want that I can go create it on jbide and jbds.
>>>
>>> Konstantin, Ilya - what say you ?
>>>
>>> /max
>>> http://about.me/maxandersen
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From nboldt at redhat.com  Mon Nov 17 18:43:08 2014
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 17 Nov 2014 18:43:08 -0500
Subject: [jbosstools-dev] Jira component for cordovasim
In-Reply-To: <546A866F.9050201@redhat.com>
References: <CA+X37ckBoqFWS+AMPzbSDwKFT5jwaxiyyCweR=UZNUUCuwY7gg@mail.gmail.com>	<642304DF-AE76-4D27-A3AF-7461C134C89B@redhat.com>	<546A4CDC.4030005@exadel.com>
	<F4FB44AD-B831-40EC-92D9-534CC203856C@redhat.com>
	<546A866F.9050201@redhat.com>
Message-ID: <546A880C.2050005@redhat.com>

FYI, when creating new JIRA components, we need to remember to update CI 
scripts like these to retain the same mapping information:

https://github.com/jbosstools/jbosstools-build-ci/pull/115
https://github.com/jbdevstudio/jbdevstudio-ci/pull/141


On 11/17/2014 06:36 PM, Nick Boldt wrote:
> Links to the new components [1], [2], with Ilya Buziak [3] as lead:
>
> [1]
> https://issues.jboss.org/browse/JBIDE/component/12320840/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>
>
> [2]
> https://issues.jboss.org/browse/JBDS/component/12320841/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>
>
> [3] https://issues.jboss.org/secure/ViewProfile.jspa?name=ibuziuk
>
> On 11/17/2014 06:27 PM, Max Rydahl Andersen wrote:
>> Well, now you got success.
>>
>> Created in both jbide and JBDS Jira.
>>
>> Tell me if description/leads are Okey/correct for you.
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>>> On 17 Nov 2014, at 20:31, Konstantin Marmalyukov
>>> <kmarmaliykov at exadel.com> wrote:
>>>
>>> Actually we told about that some time ago. Without success. So we
>>> *should* do it!
>>>
>>>> On 11/17/2014 8:05 PM, Max Rydahl Andersen wrote:
>>>>> On 17 Nov 2014, at 17:55, Gorkem Ercan wrote:
>>>>>
>>>>> Should we create a new Jira component for cordovasim? I think
>>>>> cordovasim
>>>>> issues are different from browsersim and this is what we use for them
>>>>> right
>>>>> now.
>>>> I guess cordovasim is different enough with all the ripple stuff so if
>>>> you guys want that I can go create it on jbide and jbds.
>>>>
>>>> Konstantin, Ilya - what say you ?
>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From manderse at redhat.com  Mon Nov 17 19:14:21 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 17 Nov 2014 19:14:21 -0500 (EST)
Subject: [jbosstools-dev] Jira component for cordovasim
In-Reply-To: <546A880C.2050005@redhat.com>
References: <CA+X37ckBoqFWS+AMPzbSDwKFT5jwaxiyyCweR=UZNUUCuwY7gg@mail.gmail.com>
	<642304DF-AE76-4D27-A3AF-7461C134C89B@redhat.com>
	<546A4CDC.4030005@exadel.com>
	<F4FB44AD-B831-40EC-92D9-534CC203856C@redhat.com>
	<546A866F.9050201@redhat.com> <546A880C.2050005@redhat.com>
Message-ID: <6CA0904E-CD77-4F3B-B16E-9A2A845EFE5E@redhat.com>

Couldn't we actually "encode" that in the description field on Jira so these scripts and the ones in jiralint and whatsnew scripts could share that info ?

Just an idea.  

/max
http://about.me/maxandersen


> On 18 Nov 2014, at 00:43, Nick Boldt <nboldt at redhat.com> wrote:
> 
> FYI, when creating new JIRA components, we need to remember to update CI scripts like these to retain the same mapping information:
> 
> https://github.com/jbosstools/jbosstools-build-ci/pull/115
> https://github.com/jbdevstudio/jbdevstudio-ci/pull/141
> 
> 
>> On 11/17/2014 06:36 PM, Nick Boldt wrote:
>> Links to the new components [1], [2], with Ilya Buziak [3] as lead:
>> 
>> [1]
>> https://issues.jboss.org/browse/JBIDE/component/12320840/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>> 
>> 
>> [2]
>> https://issues.jboss.org/browse/JBDS/component/12320841/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>> 
>> 
>> [3] https://issues.jboss.org/secure/ViewProfile.jspa?name=ibuziuk
>> 
>>> On 11/17/2014 06:27 PM, Max Rydahl Andersen wrote:
>>> Well, now you got success.
>>> 
>>> Created in both jbide and JBDS Jira.
>>> 
>>> Tell me if description/leads are Okey/correct for you.
>>> 
>>> /max
>>> http://about.me/maxandersen
>>> 
>>> 
>>>> On 17 Nov 2014, at 20:31, Konstantin Marmalyukov
>>>> <kmarmaliykov at exadel.com> wrote:
>>>> 
>>>> Actually we told about that some time ago. Without success. So we
>>>> *should* do it!
>>>> 
>>>>>> On 11/17/2014 8:05 PM, Max Rydahl Andersen wrote:
>>>>>> On 17 Nov 2014, at 17:55, Gorkem Ercan wrote:
>>>>>> 
>>>>>> Should we create a new Jira component for cordovasim? I think
>>>>>> cordovasim
>>>>>> issues are different from browsersim and this is what we use for them
>>>>>> right
>>>>>> now.
>>>>> I guess cordovasim is different enough with all the ripple stuff so if
>>>>> you guys want that I can go create it on jbide and jbds.
>>>>> 
>>>>> Konstantin, Ilya - what say you ?
>>>>> 
>>>>> /max
>>>>> http://about.me/maxandersen
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>> 
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>> 
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com


From nboldt at redhat.com  Mon Nov 17 19:37:02 2014
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 17 Nov 2014 19:37:02 -0500
Subject: [jbosstools-dev] Jira component for cordovasim
In-Reply-To: <6CA0904E-CD77-4F3B-B16E-9A2A845EFE5E@redhat.com>
References: <CA+X37ckBoqFWS+AMPzbSDwKFT5jwaxiyyCweR=UZNUUCuwY7gg@mail.gmail.com>
	<642304DF-AE76-4D27-A3AF-7461C134C89B@redhat.com>
	<546A4CDC.4030005@exadel.com>
	<F4FB44AD-B831-40EC-92D9-534CC203856C@redhat.com>
	<546A866F.9050201@redhat.com> <546A880C.2050005@redhat.com>
	<6CA0904E-CD77-4F3B-B16E-9A2A845EFE5E@redhat.com>
Message-ID: <546A94AE.6030703@redhat.com>

Yes, we could.

https://issues.jboss.org/browse/JBIDE-18762

On 11/17/2014 07:14 PM, Max Rydahl Andersen wrote:
> Couldn't we actually "encode" that in the description field on Jira so these scripts and the ones in jiralint and whatsnew scripts could share that info ?
>
> Just an idea.
>
> /max
> http://about.me/maxandersen
>
>
>> On 18 Nov 2014, at 00:43, Nick Boldt <nboldt at redhat.com> wrote:
>>
>> FYI, when creating new JIRA components, we need to remember to update CI scripts like these to retain the same mapping information:
>>
>> https://github.com/jbosstools/jbosstools-build-ci/pull/115
>> https://github.com/jbdevstudio/jbdevstudio-ci/pull/141
>>
>>
>>> On 11/17/2014 06:36 PM, Nick Boldt wrote:
>>> Links to the new components [1], [2], with Ilya Buziak [3] as lead:
>>>
>>> [1]
>>> https://issues.jboss.org/browse/JBIDE/component/12320840/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>>>
>>>
>>> [2]
>>> https://issues.jboss.org/browse/JBDS/component/12320841/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>>>
>>>
>>> [3] https://issues.jboss.org/secure/ViewProfile.jspa?name=ibuziuk
>>>
>>>> On 11/17/2014 06:27 PM, Max Rydahl Andersen wrote:
>>>> Well, now you got success.
>>>>
>>>> Created in both jbide and JBDS Jira.
>>>>
>>>> Tell me if description/leads are Okey/correct for you.
>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>>>
>>>>
>>>>> On 17 Nov 2014, at 20:31, Konstantin Marmalyukov
>>>>> <kmarmaliykov at exadel.com> wrote:
>>>>>
>>>>> Actually we told about that some time ago. Without success. So we
>>>>> *should* do it!
>>>>>
>>>>>>> On 11/17/2014 8:05 PM, Max Rydahl Andersen wrote:
>>>>>>> On 17 Nov 2014, at 17:55, Gorkem Ercan wrote:
>>>>>>>
>>>>>>> Should we create a new Jira component for cordovasim? I think
>>>>>>> cordovasim
>>>>>>> issues are different from browsersim and this is what we use for them
>>>>>>> right
>>>>>>> now.
>>>>>> I guess cordovasim is different enough with all the ripple stuff so if
>>>>>> you guys want that I can go create it on jbide and jbds.
>>>>>>
>>>>>> Konstantin, Ilya - what say you ?
>>>>>>
>>>>>> /max
>>>>>> http://about.me/maxandersen
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From pstribny at redhat.com  Wed Nov 19 03:40:05 2014
From: pstribny at redhat.com (Petr Stribny)
Date: Wed, 19 Nov 2014 03:40:05 -0500 (EST)
Subject: [jbosstools-dev] Aerogear name change proposal
In-Reply-To: <CB70E97F-6909-4759-9A22-CE7A9AC9516C@redhat.com>
References: <758280146.11169162.1415894378569.JavaMail.zimbra@redhat.com>
	<3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
	<257111387.7666295.1415963265715.JavaMail.zimbra@redhat.com>
	<6339D9FF-DD8B-48B6-BC86-FF86A0300FDD@redhat.com>
	<CA+X37cmRhj45U1bgO9KWxmqT94qX4Dstic=CVEy771mS1VBTHA@mail.gmail.com>
	<67A16944-8393-4665-B08E-A3800B02775D@redhat.com>
	<CA+X37ckN9aOr3XGv-PJwPiQWKZQRke4YErtAcVbxVHqc0vRUdg@mail.gmail.com>
	<CB70E97F-6909-4759-9A22-CE7A9AC9516C@redhat.com>
Message-ID: <1331597861.1377551.1416386405480.JavaMail.zimbra@redhat.com>

Max,

User-wise, the name Aerogear is mentioned only in links (on tools.jboss.org) where all links link to "Hybrid Mobile Tools". You won't find this "Aerogear" tooling nor "Aerogear" templates on detail page or in JBDS/JBoss Central. Everything is named "Hybrid Mobile Tools" and "Hybrid Mobile project". So perhaps it would be enough just to change text of these links. I believe that we should keep the name consistent.

--Petr

----- Original Message -----
From: "Max Rydahl Andersen" <manderse at redhat.com>
To: "Gorkem Ercan" <gorkem.ercan at gmail.com>
Cc: "Petr Stribny" <pstribny at redhat.com>, "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
Sent: Tuesday, 18 November, 2014 12:18:18 AM
Subject: Re: [jbosstools-dev] Aerogear name change proposal

> On 17 Nov 2014, at 18:04, Gorkem Ercan <gorkem.ercan at gmail.com> wrote:
> 
> 
>> On Mon, Nov 17, 2014 at 11:58 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
>> On 17 Nov 2014, at 13:08, Gorkem Ercan wrote:
>> 
>>> The plan was to tool the bits coming in from aearogear. I think we are
>>> still doing that but that will be under FeeedHenry umbrella now.
>>> I am OK with changing the Aerogear to something like Mobile on the web site
>>> because it describes the product better. I guess we can
>>> add the FeedHenry things when they come under mobile at the web site.
>>> 
>>> Aerogear is actually the name of the community project that builds software
>>> for mobile development. I do not think having the aerogear name on
>>> the jbosstool-aerogear repo, jira and the package names would hurt. So
>>> let's keep them as it is and only modify the website.
>> 
>> if we call it mobile everywhere but don't have matching jira component that would be a bad/confusing thing

>> I would like to have a proper separate name for it if possible that can be used as component name too.
>> 
>> Hybrid Mobile ?
>> 
>> Aerogear Hybrid ?
> 
> 
> Problem solved, the current Jira component is already called aerogear-hybrid.. 

Okey. So nothing need to change ? Now I'm missing the reason for this thread ? :)

Simple. 

/max

From mistria at redhat.com  Wed Nov 19 08:15:06 2014
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 19 Nov 2014 14:15:06 +0100
Subject: [jbosstools-dev] Initialization of the Mars stream
In-Reply-To: <5464E550.4080606@redhat.com>
References: <5464E550.4080606@redhat.com>
Message-ID: <546C97DA.5000701@redhat.com>

Hi folks,

I updated the PR for target-platforms to use Mars M3.
Please give it a try ASAP, or you may have bad surprises when we make it 
the default one for master (Thursday?).

-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141119/062418d9/attachment.html 

From manderse at redhat.com  Wed Nov 19 11:45:47 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 19 Nov 2014 17:45:47 +0100
Subject: [jbosstools-dev] Initialization of the Mars stream
In-Reply-To: <546C97DA.5000701@redhat.com>
References: <5464E550.4080606@redhat.com> <546C97DA.5000701@redhat.com>
Message-ID: <24746E9C-BDA0-4764-A69D-1B05D4FFCDC9@redhat.com>

On 19 Nov 2014, at 14:15, Mickael Istria wrote:

> Hi folks,
>
> I updated the PR for target-platforms to use Mars M3.
> Please give it a try ASAP, or you may have bad surprises when we make 
> it the default one for master (Thursday?).

link?

>
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets 
> <http://twitter.com/mickaelistria>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From mistria at redhat.com  Wed Nov 19 11:55:27 2014
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 19 Nov 2014 17:55:27 +0100
Subject: [jbosstools-dev] Initialization of the Mars stream
In-Reply-To: <24746E9C-BDA0-4764-A69D-1B05D4FFCDC9@redhat.com>
References: <5464E550.4080606@redhat.com> <546C97DA.5000701@redhat.com>
	<24746E9C-BDA0-4764-A69D-1B05D4FFCDC9@redhat.com>
Message-ID: <546CCB7F.5000202@redhat.com>

On 11/19/2014 05:45 PM, Max Rydahl Andersen wrote:
> On 19 Nov 2014, at 14:15, Mickael Istria wrote:
>
>> Hi folks,
>>
>> I updated the PR for target-platforms to use Mars M3.
>> Please give it a try ASAP, or you may have bad surprises when we make 
>> it the default one for master (Thursday?).
>
> link?
https://github.com/jbosstools/jbosstools-target-platforms/pull/104
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141119/fe70b308/attachment.html 

From dgolovin at exadel.com  Wed Nov 19 15:18:49 2014
From: dgolovin at exadel.com (Denis Golovin)
Date: Wed, 19 Nov 2014 12:18:49 -0800
Subject: [jbosstools-dev] Initialization of the Mars stream
In-Reply-To: <546CCB7F.5000202@redhat.com>
References: <5464E550.4080606@redhat.com>
	<546C97DA.5000701@redhat.com>	<24746E9C-BDA0-4764-A69D-1B05D4FFCDC9@redhat.com>
	<546CCB7F.5000202@redhat.com>
Message-ID: <546CFB29.7080802@exadel.com>

build is failing for base component with new TP
https://issues.jboss.org/browse/JBIDE-18748?focusedCommentId=13021329&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13021329

Denis

On 11/19/2014 08:55 AM, Mickael Istria wrote:
> On 11/19/2014 05:45 PM, Max Rydahl Andersen wrote:
>> On 19 Nov 2014, at 14:15, Mickael Istria wrote:
>>
>>> Hi folks,
>>>
>>> I updated the PR for target-platforms to use Mars M3.
>>> Please give it a try ASAP, or you may have bad surprises when we 
>>> make it the default one for master (Thursday?).
>>
>> link?
> https://github.com/jbosstools/jbosstools-target-platforms/pull/104
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets 
> <http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141119/57a7b8d2/attachment.html 

From mistria at redhat.com  Thu Nov 20 01:28:44 2014
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 20 Nov 2014 07:28:44 +0100
Subject: [jbosstools-dev] Drop macosx/cocoa/x86 for JBoss Tools 4.3/JBoss
 Developer Studio 9.0
Message-ID: <546D8A1C.7000508@redhat.com>

Hi all,

This is just a warning that Eclipse drops support for macosx/cocoa/x86 
platform as part of the Mars stream. Cf 
https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11099.html 
.
As a consequence, we can officially announce that the macosx/cocoa/x86 
platform will not be supported for JBoss Tools nor JBoss Developer Studio.

I'm changing the parent pom to remove this platform in the master branch 
as it caused issue with newer target platform 
https://issues.jboss.org/browse/JBIDE-18748?focusedCommentId=13021329&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13021329
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141120/1f6222e0/attachment.html 

From manderse at redhat.com  Thu Nov 20 01:42:38 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 20 Nov 2014 01:42:38 -0500 (EST)
Subject: [jbosstools-dev] Drop macosx/cocoa/x86 for JBoss Tools
	4.3/JBoss Developer Studio 9.0
In-Reply-To: <546D8A1C.7000508@redhat.com>
References: <546D8A1C.7000508@redhat.com>
Message-ID: <CC46158D-019F-4C13-8304-76AE40EEB8FC@redhat.com>

Thanks for the update.

Be aware thought that we already don't support this since it requires java6 to get a 32 bit OS X. Which we dropped in 4.2.0. 

/max
http://about.me/maxandersen


> On 20 Nov 2014, at 07:29, Mickael Istria <mistria at redhat.com> wrote:
> 
> Hi all,
> 
> This is just a warning that Eclipse drops support for macosx/cocoa/x86 platform as part of the Mars stream. Cf https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11099.html .
> As a consequence, we can officially announce that the macosx/cocoa/x86 platform will not be supported for JBoss Tools nor JBoss Developer Studio.
> 
> I'm changing the parent pom to remove this platform in the master branch as it caused issue with newer target platform https://issues.jboss.org/browse/JBIDE-18748?focusedCommentId=13021329&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13021329
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141120/e3de6dd1/attachment-0001.html 

From xcoulon at redhat.com  Thu Nov 20 02:51:18 2014
From: xcoulon at redhat.com (Xavier Coulon)
Date: Thu, 20 Nov 2014 08:51:18 +0100
Subject: [jbosstools-dev] Drop macosx/cocoa/x86 for JBoss Tools
	4.3/JBoss Developer Studio 9.0
In-Reply-To: <546D8A1C.7000508@redhat.com>
References: <546D8A1C.7000508@redhat.com>
Message-ID: <05C2BCE1-579C-4BFC-B800-7D75F4B23B5F@redhat.com>

I almost had an heart attack, until I realized you were talking about 32-bits platforms ;-)


/Xavier



> On 20 Nov 2014, at 07:28, Mickael Istria <mistria at redhat.com> wrote:
> 
> Hi all,
> 
> This is just a warning that Eclipse drops support for macosx/cocoa/x86 platform as part of the Mars stream. Cf https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11099.html <https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11099.html> .
> As a consequence, we can officially announce that the macosx/cocoa/x86 platform will not be supported for JBoss Tools nor JBoss Developer Studio.
> 
> I'm changing the parent pom to remove this platform in the master branch as it caused issue with newer target platform https://issues.jboss.org/browse/JBIDE-18748?focusedCommentId=13021329&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13021329 <https://issues.jboss.org/browse/JBIDE-18748?focusedCommentId=13021329&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13021329>
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com/> - My Tweets <http://twitter.com/mickaelistria>_______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141120/2cd6dde0/attachment.html 

From mistria at redhat.com  Thu Nov 20 03:03:16 2014
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 20 Nov 2014 09:03:16 +0100
Subject: [jbosstools-dev] Initialization of the Mars stream
In-Reply-To: <5464E550.4080606@redhat.com>
References: <5464E550.4080606@redhat.com>
Message-ID: <546DA044.8080101@redhat.com>

Quick reminder on how to try it:

$ cd jbosstools-target-platforms/
$ git fetch jbosstools pulls/head/104
$ git checkout FETCH_HEAD
$ cd jbosstools/multiple
$ mvn clean install

So you have TP 4.50.0.Alpha1-SNAPSHOT installed, with the suggested 
changes, then

$ cd jbosstools-mysupercomponent/
$ mvn clean verify -Pmultiple.target -Dtpc.version=4.50.0.Alpha1-SNAPSHOT


HTH
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141120/ec6aed66/attachment.html 

From mistria at redhat.com  Thu Nov 20 03:39:10 2014
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 20 Nov 2014 09:39:10 +0100
Subject: [jbosstools-dev] Initialization of the Mars stream
In-Reply-To: <546DA044.8080101@redhat.com>
References: <5464E550.4080606@redhat.com> <546DA044.8080101@redhat.com>
Message-ID: <546DA8AE.8020403@redhat.com>

Fix a typo.

On 11/20/2014 09:03 AM, Mickael Istria wrote:
> Quick reminder on how to try it:
>
> $ cd jbosstools-target-platforms/
> $git fetch jbosstools pull/104/head
^^^ Fix here
> $ git checkout FETCH_HEAD
> $ cd jbosstools/multiple
> $ mvn clean install
> So you have TP 4.50.0.Alpha1-SNAPSHOT installed, with the suggested 
> changes, then
> $ cd jbosstools-mysupercomponent/
>

-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141120/fc78db04/attachment.html 

From kmarmaliykov at exadel.com  Thu Nov 20 04:39:11 2014
From: kmarmaliykov at exadel.com (Konstantin Marmalyukov)
Date: Thu, 20 Nov 2014 12:39:11 +0300
Subject: [jbosstools-dev] Drop macosx/cocoa/x86 for JBoss Tools
 4.3/JBoss Developer Studio 9.0
In-Reply-To: <546D8A1C.7000508@redhat.com>
References: <546D8A1C.7000508@redhat.com>
Message-ID: <546DB6BF.8090907@exadel.com>

Shouldn't we also drop cocoa.macos xulrunner plugin(xulrunner bundle for 
32bit mac) also?

On 11/20/2014 9:28 AM, Mickael Istria wrote:
> Hi all,
>
> This is just a warning that Eclipse drops support for macosx/cocoa/x86 
> platform as part of the Mars stream. Cf 
> https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11099.html 
> .
> As a consequence, we can officially announce that the macosx/cocoa/x86 
> platform will not be supported for JBoss Tools nor JBoss Developer Studio.
>
> I'm changing the parent pom to remove this platform in the master 
> branch as it caused issue with newer target platform 
> https://issues.jboss.org/browse/JBIDE-18748?focusedCommentId=13021329&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13021329
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets 
> <http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141120/5164a9dc/attachment.html 

From mistria at redhat.com  Thu Nov 20 04:48:21 2014
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 20 Nov 2014 10:48:21 +0100
Subject: [jbosstools-dev] Drop macosx/cocoa/x86 for JBoss Tools
 4.3/JBoss Developer Studio 9.0
In-Reply-To: <546DB6BF.8090907@exadel.com>
References: <546D8A1C.7000508@redhat.com> <546DB6BF.8090907@exadel.com>
Message-ID: <546DB8E5.5000006@redhat.com>

On 11/20/2014 10:39 AM, Konstantin Marmalyukov wrote:
> Shouldn't we also drop cocoa.macos xulrunner plugin(xulrunner bundle 
> for 32bit mac) also?
Indeed, this implies that everything that is 32bits osx should be removed.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141120/427894c1/attachment.html 

From mistria at redhat.com  Thu Nov 20 05:01:54 2014
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 20 Nov 2014 11:01:54 +0100
Subject: [jbosstools-dev] Drop macosx/cocoa/x86 for JBoss Tools
 4.3/JBoss Developer Studio 9.0
In-Reply-To: <546DB8E5.5000006@redhat.com>
References: <546D8A1C.7000508@redhat.com> <546DB6BF.8090907@exadel.com>
	<546DB8E5.5000006@redhat.com>
Message-ID: <546DBC12.4050805@redhat.com>

On 11/20/2014 10:48 AM, Mickael Istria wrote:
> On 11/20/2014 10:39 AM, Konstantin Marmalyukov wrote:
>> Shouldn't we also drop cocoa.macos xulrunner plugin(xulrunner bundle 
>> for 32bit mac) also?
> Indeed, this implies that everything that is 32bits osx should be removed.
More specifically, everything that we *still build* and that is 32bits 
macosx should be removed.
Stuff that is stable and that we don't plan to rebuild (such as 
xulrunner) can remain unchanged for now. We'll update them if it becomes 
necessary one day.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141120/304d2545/attachment-0001.html 

From manderse at redhat.com  Thu Nov 20 08:21:22 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 20 Nov 2014 14:21:22 +0100
Subject: [jbosstools-dev] Aerogear name change proposal
In-Reply-To: <1331597861.1377551.1416386405480.JavaMail.zimbra@redhat.com>
References: <758280146.11169162.1415894378569.JavaMail.zimbra@redhat.com>
	<3D391D0B-D670-453B-AF1D-AA9618B768AF@redhat.com>
	<257111387.7666295.1415963265715.JavaMail.zimbra@redhat.com>
	<6339D9FF-DD8B-48B6-BC86-FF86A0300FDD@redhat.com>
	<CA+X37cmRhj45U1bgO9KWxmqT94qX4Dstic=CVEy771mS1VBTHA@mail.gmail.com>
	<67A16944-8393-4665-B08E-A3800B02775D@redhat.com>
	<CA+X37ckN9aOr3XGv-PJwPiQWKZQRke4YErtAcVbxVHqc0vRUdg@mail.gmail.com>
	<CB70E97F-6909-4759-9A22-CE7A9AC9516C@redhat.com>
	<1331597861.1377551.1416386405480.JavaMail.zimbra@redhat.com>
Message-ID: <76555348-918E-44DF-9BCA-8ED46FA4FF89@redhat.com>

On 19 Nov 2014, at 9:40, Petr Stribny wrote:

> Max,
>
> User-wise, the name Aerogear is mentioned only in links (on 
> tools.jboss.org) where all links link to "Hybrid Mobile Tools". You 
> won't find this "Aerogear" tooling nor "Aerogear" templates on detail 
> page or in JBDS/JBoss Central. Everything is named "Hybrid Mobile 
> Tools" and "Hybrid Mobile project". So perhaps it would be enough just 
> to change text of these links. I believe that we should keep the name 
> consistent.

please point out specifically which links you believe are misleading.

even better submit PR to github.com/jbosstools-website

/max

> --Petr
>
> ----- Original Message -----
> From: "Max Rydahl Andersen" <manderse at redhat.com>
> To: "Gorkem Ercan" <gorkem.ercan at gmail.com>
> Cc: "Petr Stribny" <pstribny at redhat.com>, "jbosstools-dev 
> jbosstools-dev" <jbosstools-dev at lists.jboss.org>
> Sent: Tuesday, 18 November, 2014 12:18:18 AM
> Subject: Re: [jbosstools-dev] Aerogear name change proposal
>
>> On 17 Nov 2014, at 18:04, Gorkem Ercan <gorkem.ercan at gmail.com> 
>> wrote:
>>
>>
>>> On Mon, Nov 17, 2014 at 11:58 AM, Max Rydahl Andersen 
>>> <manderse at redhat.com> wrote:
>>> On 17 Nov 2014, at 13:08, Gorkem Ercan wrote:
>>>
>>>> The plan was to tool the bits coming in from aearogear. I think we 
>>>> are
>>>> still doing that but that will be under FeeedHenry umbrella now.
>>>> I am OK with changing the Aerogear to something like Mobile on the 
>>>> web site
>>>> because it describes the product better. I guess we can
>>>> add the FeedHenry things when they come under mobile at the web 
>>>> site.
>>>>
>>>> Aerogear is actually the name of the community project that builds 
>>>> software
>>>> for mobile development. I do not think having the aerogear name on
>>>> the jbosstool-aerogear repo, jira and the package names would hurt. 
>>>> So
>>>> let's keep them as it is and only modify the website.
>>>
>>> if we call it mobile everywhere but don't have matching jira 
>>> component that would be a bad/confusing thing
>
>>> I would like to have a proper separate name for it if possible that 
>>> can be used as component name too.
>>>
>>> Hybrid Mobile ?
>>>
>>> Aerogear Hybrid ?
>>
>>
>> Problem solved, the current Jira component is already called 
>> aerogear-hybrid..
>
> Okey. So nothing need to change ? Now I'm missing the reason for this 
> thread ? :)
>
> Simple.
>
> /max


/max
http://about.me/maxandersen

From manderse at redhat.com  Thu Nov 20 17:22:35 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 20 Nov 2014 23:22:35 +0100
Subject: [jbosstools-dev] 4.2.1 CR1 build this weekend
Message-ID: <B351FB51-4969-498A-BB90-3120D0ADC82F@redhat.com>

Hi,

This weekend we will create a build from tip[1] of 4.2.x branch and call 
it 4.2.1.CR1.

As discussed at the F2F we are aiming for a 4.2.1 release before Xmas 
with only
essential bug fixes, as coordinated between dev and QE. This release is 
currently
scheduled for GA on 15 December, as shown in JIRA [2] and was in the 
proposal
send out last week[3].

PLEASE, it is not expected *all* components will have updates for this 
release.
Only the ones that actually have critical issues/requests should 
contribute.

Please make sure your branch builds correctly, using the latest parent 
pom version
4.2.1.CR1-SNAPSHOT [4], and that if you have changes for the 4.2.1 
release,
make sure you have upversioned the version of the components - including 
both plugins
and features, and their associated poms.

For those projects which have so far *not* remembered to update, see 
details here [5].


[1] Going forward we should move to using a tagged/sha1 approach to 
prevent any
build surprises, but more about that in a follow up next week.

[2] 
https://issues.jboss.org/browse/JBDS/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel

[3] The plan is going to be made public in jira/product plan ASAP.

[4] 
https://github.com/jbosstools/jbosstools-build/blob/jbosstools-4.2.x/parent/pom.xml

[5] https://issues.jboss.org/browse/JBIDE-18759

/max
http://about.me/maxandersen


From mistria at redhat.com  Fri Nov 21 06:56:58 2014
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 21 Nov 2014 12:56:58 +0100
Subject: [jbosstools-dev] CI jobs for 4.2.x branch updated to use Target
	Platform 4.41.1.CR1-SNAPSHOT
Message-ID: <546F288A.6070101@redhat.com>

Hi all,

We've had some request to update Target Platform for JBoss Tools 
4.2.1.CR1 build. So beware that we've just updated the related jobs to 
use the newer 4.41.1.CR1-SNAPSHOT Target-Platform, which includes a 
newer version of THyM (cf https://issues.jboss.org/browse/JBIDE-18799 ).
This change was also applied on jobs for the master branch, which rely 
on TP 4.50.0.CR1-SNAPSHOT.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141121/de858b3b/attachment.html 

From mistria at redhat.com  Fri Nov 21 11:43:58 2014
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 21 Nov 2014 17:43:58 +0100
Subject: [jbosstools-dev] Target Platform 4.41.1.CR1 for JBoss Tools
	4.2.1.CR1 has been released.
Message-ID: <546F6BCE.50808@redhat.com>

Target Platform 4.41.1.CR1 for JBoss Tools 4.2.1.CR1 has been released.


Changes
=======

* JBIDE-18799 Update THyM


Usage
=====

Target platform 4.41.1.CR1 is what JBoss Tools 4.2.1.CR1 will use.

All Jenkins jobs for branch jbosstools-4.2.x and parent pom 4.2.1.CR1-SNAPSHOT
have been updated to use target platform 4.41.1.CR1


Download
========

Update site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.41.1.CR1/REPO/
Update site zip: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.41.1.CR1/jbosstoolstarget-4.41.1.CR1.zip
Git tag: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.41.1.CR1


Testing/Development
===================

If your root pom correctly specifies the latest parent pom version as 4.2.1.CR1-SNAPSHOT, you need only this:

   $ mvn clean verify

If you're using a different parent pom, use this:

   $ mvn clean verify -Dtpc.version=4.41.1.CR1

For advanced usage and help (using in IDE, building a mirror locally, using a zip), see:

* https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.md


What's next?
============

jbosstools-target-platforms project branch 4.41.x has been prepared for potential upgrades, and its version is now 4.2.1.CR2-SNAPSHOT. No changes are expected yet.

-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141121/e7e1ae8d/attachment.html 

From fbricon at gmail.com  Fri Nov 21 14:22:11 2014
From: fbricon at gmail.com (Fred Bricon)
Date: Fri, 21 Nov 2014 14:22:11 -0500
Subject: [jbosstools-dev] Fwd: [cross-project-issues-dev] TM withdrawal from
	Mars
In-Reply-To: <9C1051B8-3966-40C8-9EF3-C7E5E3AA8855@computer.org>
References: <9C1051B8-3966-40C8-9EF3-C7E5E3AA8855@computer.org>
Message-ID: <CAG2ouxRwXNhZ4OE9k6A1BHTczJn1k24k5T_8-YG-_Pne3tLSoA@mail.gmail.com>

I believe that impacts us, wdyt?

---------- Forwarded message ----------
From: Greg Watson <g.watson at computer.org>
Date: Fri, Nov 21, 2014 at 11:24 AM
Subject: [cross-project-issues-dev] TM withdrawal from Mars
To: Cross project issues <cross-project-issues-dev at eclipse.org>


The Target Management (TM) project is comprised of two main projects:
Remote System Explorer (RSE) and Terminal. Only the Terminal project is
under active development, and there are plans currently to merge this with
the TCF Terminal project. We are planning to have one final release of TM
(3.7) to coincide with Luna SR2, and then only provide service releases on
an as-needed basis. As a consequence, we don?t have the resources to
contribute to a Mars release, so are notifying everyone of our intention to
withdraw from Mars.

Please let us know if there are any comments or concerns regarding this.

Regards,
Greg
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev at eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
"Have you tried turning it off and on again" - The IT Crowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141121/c416d0ab/attachment.html 

From manderse at redhat.com  Fri Nov 21 14:38:16 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 21 Nov 2014 14:38:16 -0500 (EST)
Subject: [jbosstools-dev] Fwd: [cross-project-issues-dev] TM withdrawal
	from	Mars
In-Reply-To: <CAG2ouxRwXNhZ4OE9k6A1BHTczJn1k24k5T_8-YG-_Pne3tLSoA@mail.gmail.com>
References: <9C1051B8-3966-40C8-9EF3-C7E5E3AA8855@computer.org>
	<CAG2ouxRwXNhZ4OE9k6A1BHTczJn1k24k5T_8-YG-_Pne3tLSoA@mail.gmail.com>
Message-ID: <07362EB7-CCF6-40F7-A870-AD065B564746@redhat.com>

That would be rather disastrous if that removes the support for Ftp and ssh access that is used in our remote deployment :/

/max
http://about.me/maxandersen


> On 21 Nov 2014, at 20:22, Fred Bricon <fbricon at gmail.com> wrote:
> 
> I believe that impacts us, wdyt?
> 
> ---------- Forwarded message ----------
> From: Greg Watson <g.watson at computer.org>
> Date: Fri, Nov 21, 2014 at 11:24 AM
> Subject: [cross-project-issues-dev] TM withdrawal from Mars
> To: Cross project issues <cross-project-issues-dev at eclipse.org>
> 
> 
> The Target Management (TM) project is comprised of two main projects: Remote System Explorer (RSE) and Terminal. Only the Terminal project is under active development, and there are plans currently to merge this with the TCF Terminal project. We are planning to have one final release of TM (3.7) to coincide with Luna SR2, and then only provide service releases on an as-needed basis. As a consequence, we don?t have the resources to contribute to a Mars release, so are notifying everyone of our intention to withdraw from Mars.
> 
> Please let us know if there are any comments or concerns regarding this.
> 
> Regards,
> Greg
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev at eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
> 
> 
> -- 
> "Have you tried turning it off and on again" - The IT Crowd
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141121/e3bebc6f/attachment-0001.html 

From dgolovin at exadel.com  Fri Nov 21 15:48:53 2014
From: dgolovin at exadel.com (Denis Golovin)
Date: Fri, 21 Nov 2014 12:48:53 -0800
Subject: [jbosstools-dev] Fwd: [cross-project-issues-dev] TM withdrawal
 from	Mars
In-Reply-To: <07362EB7-CCF6-40F7-A870-AD065B564746@redhat.com>
References: <9C1051B8-3966-40C8-9EF3-C7E5E3AA8855@computer.org>	<CAG2ouxRwXNhZ4OE9k6A1BHTczJn1k24k5T_8-YG-_Pne3tLSoA@mail.gmail.com>
	<07362EB7-CCF6-40F7-A870-AD065B564746@redhat.com>
Message-ID: <546FA535.6010705@exadel.com>

So it is going to be only RSE after Terminal is merged into TCF Terminal 
project.

Do you know if it is really time consuming to just maintain RSE part to 
make it into Mars release?

Denis

On 11/21/2014 11:38 AM, Max Rydahl Andersen wrote:
> That would be rather disastrous if that removes the support for Ftp 
> and ssh access that is used in our remote deployment :/
>
> /max
> http://about.me/maxandersen
>
>
> On 21 Nov 2014, at 20:22, Fred Bricon <fbricon at gmail.com 
> <mailto:fbricon at gmail.com>> wrote:
>
>> I believe that impacts us, wdyt?
>>
>> ---------- Forwarded message ----------
>> From: *Greg Watson* <g.watson at computer.org 
>> <mailto:g.watson at computer.org>>
>> Date: Fri, Nov 21, 2014 at 11:24 AM
>> Subject: [cross-project-issues-dev] TM withdrawal from Mars
>> To: Cross project issues <cross-project-issues-dev at eclipse.org 
>> <mailto:cross-project-issues-dev at eclipse.org>>
>>
>>
>> The Target Management (TM) project is comprised of two main projects: 
>> Remote System Explorer (RSE) and Terminal. Only the Terminal project 
>> is under active development, and there are plans currently to merge 
>> this with the TCF Terminal project. We are planning to have one final 
>> release of TM (3.7) to coincide with Luna SR2, and then only provide 
>> service releases on an as-needed basis. As a consequence, we don?t 
>> have the resources to contribute to a Mars release, so are notifying 
>> everyone of our intention to withdraw from Mars.
>>
>> Please let us know if there are any comments or concerns regarding this.
>>
>> Regards,
>> Greg
>> _______________________________________________
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev at eclipse.org 
>> <mailto:cross-project-issues-dev at eclipse.org>
>> To change your delivery options, retrieve your password, or 
>> unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>>
>>
>> -- 
>> "Have you tried turning it off and on again" - The IT Crowd
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141121/c09b8a03/attachment.html 

From manderse at redhat.com  Sat Nov 22 06:46:00 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Sat, 22 Nov 2014 12:46:00 +0100
Subject: [jbosstools-dev] [cross-project-issues-dev] TM withdrawal from
 Mars
In-Reply-To: <546FA535.6010705@exadel.com>
References: <9C1051B8-3966-40C8-9EF3-C7E5E3AA8855@computer.org>
	<CAG2ouxRwXNhZ4OE9k6A1BHTczJn1k24k5T_8-YG-_Pne3tLSoA@mail.gmail.com>
	<07362EB7-CCF6-40F7-A870-AD065B564746@redhat.com>
	<546FA535.6010705@exadel.com>
Message-ID: <7C87E657-07B5-4CBD-85C9-BF4C7524EDB7@redhat.com>

On 21 Nov 2014, at 21:48, Denis Golovin wrote:

> So it is going to be only RSE after Terminal is merged into TCF 
> Terminal project.

No, the suggestion is to kill TM, move terminal to TM and remove RSE. 
With no obvious replacement afaics.

> Do you know if it is really time consuming to just maintain RSE part 
> to make it into Mars release?

No idea - I'm joining the tm list to figure out what is actually going 
on.

/max

> Denis
>
> On 11/21/2014 11:38 AM, Max Rydahl Andersen wrote:
>> That would be rather disastrous if that removes the support for Ftp 
>> and ssh access that is used in our remote deployment :/
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>> On 21 Nov 2014, at 20:22, Fred Bricon <fbricon at gmail.com 
>> <mailto:fbricon at gmail.com>> wrote:
>>
>>> I believe that impacts us, wdyt?
>>>
>>> ---------- Forwarded message ----------
>>> From: *Greg Watson* <g.watson at computer.org 
>>> <mailto:g.watson at computer.org>>
>>> Date: Fri, Nov 21, 2014 at 11:24 AM
>>> Subject: [cross-project-issues-dev] TM withdrawal from Mars
>>> To: Cross project issues <cross-project-issues-dev at eclipse.org 
>>> <mailto:cross-project-issues-dev at eclipse.org>>
>>>
>>>
>>> The Target Management (TM) project is comprised of two main 
>>> projects: Remote System Explorer (RSE) and Terminal. Only the 
>>> Terminal project is under active development, and there are plans 
>>> currently to merge this with the TCF Terminal project. We are 
>>> planning to have one final release of TM (3.7) to coincide with Luna 
>>> SR2, and then only provide service releases on an as-needed basis. 
>>> As a consequence, we don?t have the resources to contribute to a 
>>> Mars release, so are notifying everyone of our intention to withdraw 
>>> from Mars.
>>>
>>> Please let us know if there are any comments or concerns regarding 
>>> this.
>>>
>>> Regards,
>>> Greg
>>> _______________________________________________
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev at eclipse.org 
>>> <mailto:cross-project-issues-dev at eclipse.org>
>>> To change your delivery options, retrieve your password, or 
>>> unsubscribe from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>>>
>>>
>>> -- 
>>> "Have you tried turning it off and on again" - The IT Crowd
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org 
>>> <mailto:jbosstools-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From mmg at credospb.ru  Sat Nov 22 06:20:58 2014
From: mmg at credospb.ru (Gabby)
Date: Sat, 22 Nov 2014 15:20:58 +0400
Subject: [jbosstools-dev] Thai King is Dead and WTC Nuclear Demolition!
Message-ID: <5E5BEDBEB56143904C4900B8ACB62E0C@lrakue>

Dear Recipients,
 
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
 
P.S.
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 at gmail.com or free.dimitri at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141122/b92c40b9/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 55695 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141122/b92c40b9/attachment-0003.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 26868 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141122/b92c40b9/attachment-0004.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 18112 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141122/b92c40b9/attachment-0005.jpe 

From nboldt at redhat.com  Sun Nov 23 22:53:10 2014
From: nboldt at redhat.com (Nick Boldt)
Date: Sun, 23 Nov 2014 22:53:10 -0500
Subject: [jbosstools-dev] Failing tests in JavaEE for JBT 4.2.1.CR1
Message-ID: <5472ABA6.2010703@redhat.com>

TL;DR:

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.

Ref: https://issues.jboss.org/browse/JBIDE-18818

---

Tests that time out due to blocking UI or other thread lock result in 
builds that are recorded as ABORTED [0]. 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.

[0] 
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.2.luna/buildTimeTrend

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 [1] -- see screenshot.

[1] 
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow_4.2.luna/

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
http://nick.divbyzero.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: javaee-aborts-so-buildflow-does-too.png
Type: image/png
Size: 117408 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141123/2465392b/attachment-0001.png 

From nboldt at redhat.com  Mon Nov 24 01:49:10 2014
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 24 Nov 2014 01:49:10 -0500
Subject: [jbosstools-dev] JBoss Tools Core 4.2.1.CR1 bits available for QE
	testing
Message-ID: <5472D4E6.7010605@redhat.com>

As always, these are not FINAL bits, but preliminary results for QE & 
community testing. Not for use by customers or end users.

Update site: http://download.jboss.org/jbosstools/updates/staging/luna/

Target platforms:
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Final 
(upcoming Luna R milestone)
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.41.1.CR1 
(upcoming Luna SR1 milestone)

Until the above target platform site is released, you may need to add it 
to Eclipse to resolve dependencies at install time.
Once released, dependencies will be found automatically from here:
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ 
(latest release)
* 
http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.41.1.CR1-SNAPSHOT/ 
(upcoming milestone)
* 
http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.41.1.CR1-SNAPSHOT/ 
(upcoming milestone)

New + noteworthy (subject to change):
* 
https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
* http://tools.jboss.org/documentation/whatsnew/

Schedule: 
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel

--

Additional update sites:
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR1-updatesite-core/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR1-updatesite-coretests/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR1-updatesite-hibernatetools/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR1-updatesite-webtools/
and build sites:
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-coretests/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-hibernatetools/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-webtools/

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From mistria at redhat.com  Mon Nov 24 03:03:00 2014
From: mistria at redhat.com (Mickael Istria)
Date: Mon, 24 Nov 2014 09:03:00 +0100
Subject: [jbosstools-dev] [cross-project-issues-dev] TM withdrawal from
 Mars
In-Reply-To: <7C87E657-07B5-4CBD-85C9-BF4C7524EDB7@redhat.com>
References: <9C1051B8-3966-40C8-9EF3-C7E5E3AA8855@computer.org>	<CAG2ouxRwXNhZ4OE9k6A1BHTczJn1k24k5T_8-YG-_Pne3tLSoA@mail.gmail.com>	<07362EB7-CCF6-40F7-A870-AD065B564746@redhat.com>	<546FA535.6010705@exadel.com>
	<7C87E657-07B5-4CBD-85C9-BF4C7524EDB7@redhat.com>
Message-ID: <5472E634.5010306@redhat.com>

I'm not sure this is *so* critical. There message means that TM won't be 
in Mars by default, and that they don't plan new development on the project.

The removal of TM from Mars doesn't prevent us from consuming it in our 
TP. We actually don't even use the Mars repo to get TM currently, but 
already their dedicated repo.
The fact that there won't be new development is not important as long as 
they welcome patches.

So the project is not "killed" in a way that it's not usable any more, 
it's only that not much will happen from its current contributors.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141124/a43f80aa/attachment.html 

From manderse at redhat.com  Mon Nov 24 03:16:11 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 24 Nov 2014 03:16:11 -0500 (EST)
Subject: [jbosstools-dev] [cross-project-issues-dev] TM withdrawal from
	Mars
In-Reply-To: <5472E634.5010306@redhat.com>
References: <9C1051B8-3966-40C8-9EF3-C7E5E3AA8855@computer.org>
	<CAG2ouxRwXNhZ4OE9k6A1BHTczJn1k24k5T_8-YG-_Pne3tLSoA@mail.gmail.com>
	<07362EB7-CCF6-40F7-A870-AD065B564746@redhat.com>
	<546FA535.6010705@exadel.com>
	<7C87E657-07B5-4CBD-85C9-BF4C7524EDB7@redhat.com>
	<5472E634.5010306@redhat.com>
Message-ID: <5EEB3608-77F8-4128-A122-CEC87AE45312@redhat.com>

If it is not available in Mars we can't really depend on it without we start bundling it and then we own the maintaence of It risking others will bundle other versions and we'll be incompatible. It is bad enough there now are multiple terminals, but multiple ways to define and connect to remote hosts for file transferring. That would be a mess. 

why are we using their dedicated repo and not the release train as we do for other things ? To get source for Dev to or?

So sure, there are hacks for bundling this in. None of them are sustainable if the project is looking for termination. 

/max
http://about.me/maxandersen


> On 24 Nov 2014, at 09:03, Mickael Istria <mistria at redhat.com> wrote:
> 
> I'm not sure this is *so* critical. There message means that TM won't be in Mars by default, and that they don't plan new development on the project.
> 
> The removal of TM from Mars doesn't prevent us from consuming it in our TP. We actually don't even use the Mars repo to get TM currently, but already their dedicated repo.
> The fact that there won't be new development is not important as long as they welcome patches.
> 
> So the project is not "killed" in a way that it's not usable any more, it's only that not much will happen from its current contributors.
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141124/4244ddcf/attachment.html 

From mistria at redhat.com  Mon Nov 24 03:35:39 2014
From: mistria at redhat.com (Mickael Istria)
Date: Mon, 24 Nov 2014 09:35:39 +0100
Subject: [jbosstools-dev] [cross-project-issues-dev] TM withdrawal from
 Mars
In-Reply-To: <5EEB3608-77F8-4128-A122-CEC87AE45312@redhat.com>
References: <9C1051B8-3966-40C8-9EF3-C7E5E3AA8855@computer.org>
	<CAG2ouxRwXNhZ4OE9k6A1BHTczJn1k24k5T_8-YG-_Pne3tLSoA@mail.gmail.com>
	<07362EB7-CCF6-40F7-A870-AD065B564746@redhat.com>
	<546FA535.6010705@exadel.com>
	<7C87E657-07B5-4CBD-85C9-BF4C7524EDB7@redhat.com>
	<5472E634.5010306@redhat.com>
	<5EEB3608-77F8-4128-A122-CEC87AE45312@redhat.com>
Message-ID: <5472EDDB.5090600@redhat.com>

On 11/24/2014 09:16 AM, Max Rydahl Andersen wrote:
> If it is not available in Mars we can't really depend on it without we 
> start bundling it and then we own the maintaence of It risking others 
> will bundle other versions and we'll be incompatible. It is bad enough 
> there now are multiple terminals, but multiple ways to define and 
> connect to remote hosts for file transferring. That would be a mess.
Why not simply contributing to the project in case we have things to 
contribute? I don't understand why being in Mars/not being in Mars makes 
a difference about how to contribute to this project and how much we can 
rely on it.
It's just that current contibutors are resigning from this project, it 
doesn't require anyone to fork it.
> So sure, there are hacks for bundling this in. None of them are 
> sustainable if the project is looking for termination.
  If we don't want project to terminate, and if multiple people need it, 
then it's up to its adopters (including us) to affirm that we are ready 
to make the necessary efforts to provide and review patches to keep the 
project somehow alive. Given the maturity of the project, it shouldn't 
represent too much work to keep it alive.
Things will be a mess only if we let them be a mess, but just not 
changing anything to current state of the project would be enough to 
avoid that mess.

However, if there is a better replacement, it may be a good time to use 
the better one; but if there is not, then we should IMO step up and say 
that we don't want project to terminate.

> why are we using their dedicated repo and not the release train as we 
> do for other things ? To get source for Dev to or?
Yes, I think so, on Rob's request.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141124/5816676f/attachment.html 

From manderse at redhat.com  Mon Nov 24 06:08:18 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 24 Nov 2014 12:08:18 +0100
Subject: [jbosstools-dev] [cross-project-issues-dev] TM withdrawal from
 Mars
In-Reply-To: <5472EDDB.5090600@redhat.com>
References: <9C1051B8-3966-40C8-9EF3-C7E5E3AA8855@computer.org>
	<CAG2ouxRwXNhZ4OE9k6A1BHTczJn1k24k5T_8-YG-_Pne3tLSoA@mail.gmail.com>
	<07362EB7-CCF6-40F7-A870-AD065B564746@redhat.com>
	<546FA535.6010705@exadel.com>
	<7C87E657-07B5-4CBD-85C9-BF4C7524EDB7@redhat.com>
	<5472E634.5010306@redhat.com>
	<5EEB3608-77F8-4128-A122-CEC87AE45312@redhat.com>
	<5472EDDB.5090600@redhat.com>
Message-ID: <751E24E6-A781-484B-B366-1920DCB39C7B@redhat.com>

On 24 Nov 2014, at 9:35, Mickael Istria wrote:

> On 11/24/2014 09:16 AM, Max Rydahl Andersen wrote:
>> If it is not available in Mars we can't really depend on it without 
>> we start bundling it and then we own the maintaence of It risking 
>> others will bundle other versions and we'll be incompatible. It is 
>> bad enough there now are multiple terminals, but multiple ways to 
>> define and connect to remote hosts for file transferring. That would 
>> be a mess.
> Why not simply contributing to the project in case we have things to 
> contribute?

I have not said we should not contribute to it. That is probably what we 
need to do - the current situation is not stable.

> I don't understand why being in Mars/not being in Mars makes a 
> difference about how to contribute to this project and how much we can 
> rely on it.

If it is not in Mars we can't rely on it being in users base eclipse 
install.

> It's just that current contibutors are resigning from this project, it 
> doesn't require anyone to fork it.

If noone is putting it into Mars someone will either rely on what is in 
Eclipse Kepler OR fork/use something else to define remote FTP/SCP 
connections in their mars release.

meaning duplicate setup and whatnot.

>> So sure, there are hacks for bundling this in. None of them are 
>> sustainable if the project is looking for termination.
> If we don't want project to terminate, and if multiple people need it, 
> then it's up to its adopters (including us) to affirm that we are 
> ready to make the necessary efforts to provide and review patches to 
> keep the project somehow alive. Given the maturity of the project, it 
> shouldn't represent too much work to keep it alive.
> Things will be a mess only if we let them be a mess, but just not 
> changing anything to current state of the project would be enough to 
> avoid that mess.

> However, if there is a better replacement, it may be a good time to 
> use the better one; but if there is not, then we should IMO step up 
> and say that we don't want project to terminate.

Yes, that is why i'm on tm-dev and cross-project-issues now to figure 
out what is going on.

In short: this is a big deal since this was *not* something we planned 
to take upon us. and if we don't do it we still need to rework how we
do our RSE integration/build. Anyone volunteering to help out ?

>> why are we using their dedicated repo and not the release train as we 
>> do for other things ? To get source for Dev to or?
> Yes, I think so, on Rob's request.

As long as we are actually using the release train version and not 
"latest/greatest" build from RSE that should be fine.

/max
http://about.me/maxandersen

From rhopp at redhat.com  Mon Nov 24 08:18:29 2014
From: rhopp at redhat.com (Radim Hopp)
Date: Mon, 24 Nov 2014 14:18:29 +0100
Subject: [jbosstools-dev] JBoss Tools Core 4.2.1.CR1 bits available for
	QE testing
In-Reply-To: <5472D4E6.7010605@redhat.com>
References: <5472D4E6.7010605@redhat.com>
Message-ID: <2219313.WBFi7pfyG1@localhost.localdomain>

Hi!

On Monday, November 24, 2014 01:49:10 AM Nick Boldt wrote:
> As always, these are not FINAL bits, but preliminary results for QE &
> community testing. Not for use by customers or end users.
> 
> Update site: http://download.jboss.org/jbosstools/updates/staging/luna/

it seems that compositeContent.xml here is pointing to old version: 
http://download.jboss.org/jbosstools/static/releases/jbosstools-4.2.0.Final-updatesite-core/


> 
> Target platforms:
> *
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0
> .Final (upcoming Luna R milestone)
> *
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.41.1
> .CR1 (upcoming Luna SR1 milestone)
> 
> Until the above target platform site is released, you may need to add it
> to Eclipse to resolve dependencies at install time.
> Once released, dependencies will be found automatically from here:
> *
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/
> (latest release)
> *
> http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.41.1
> .CR1-SNAPSHOT/ (upcoming milestone)
> *
> http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.
> 41.1.CR1-SNAPSHOT/ (upcoming milestone)
> 
> New + noteworthy (subject to change):
> *
> https://github.com/jbosstools/jbosstools-website/tree/master/documentation/w
> hatsnew * http://tools.jboss.org/documentation/whatsnew/
> 
> Schedule:
> https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.
> system.project%3Aversions-panel
> 
> --
> 
> Additional update sites:
> *
> http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.C
> R1-updatesite-core/ *
> http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.C
> R1-updatesite-coretests/ *
> http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.C
> R1-updatesite-hibernatetools/ *
> http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.C
> R1-updatesite-webtools/ and build sites:
> *
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-bui
> ld-core/ *
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-bui
> ld-coretests/ *
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-bui
> ld-hibernatetools/ *
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-bui
> ld-webtools/


From nboldt at redhat.com  Mon Nov 24 11:44:35 2014
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 24 Nov 2014 11:44:35 -0500
Subject: [jbosstools-dev] JBoss Tools Core 4.2.1.CR1 bits available for
 QE testing
In-Reply-To: <2219313.WBFi7pfyG1@localhost.localdomain>
References: <5472D4E6.7010605@redhat.com>
	<2219313.WBFi7pfyG1@localhost.localdomain>
Message-ID: <54736073.7060900@redhat.com>

Apologies. I'll fix that today.

The content is ALSO available from the subfolders in that folder, as 
noted below:

http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR1-updatesite-core/ 

http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR1-updatesite-coretests/
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR1-updatesite-hibernatetools/
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR1-updatesite-webtools/

On 11/24/2014 08:18 AM, Radim Hopp wrote:
> Hi!
>
> On Monday, November 24, 2014 01:49:10 AM Nick Boldt wrote:
>> As always, these are not FINAL bits, but preliminary results for QE &
>> community testing. Not for use by customers or end users.
>>
>> Update site: http://download.jboss.org/jbosstools/updates/staging/luna/
>
> it seems that compositeContent.xml here is pointing to old version:
> http://download.jboss.org/jbosstools/static/releases/jbosstools-4.2.0.Final-updatesite-core/
>
>
>>
>> Target platforms:
>> *
>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0
>> .Final (upcoming Luna R milestone)
>> *
>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.41.1
>> .CR1 (upcoming Luna SR1 milestone)
>>
>> Until the above target platform site is released, you may need to add it
>> to Eclipse to resolve dependencies at install time.
>> Once released, dependencies will be found automatically from here:
>> *
>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/
>> (latest release)
>> *
>> http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.41.1
>> .CR1-SNAPSHOT/ (upcoming milestone)
>> *
>> http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.
>> 41.1.CR1-SNAPSHOT/ (upcoming milestone)
>>
>> New + noteworthy (subject to change):
>> *
>> https://github.com/jbosstools/jbosstools-website/tree/master/documentation/w
>> hatsnew * http://tools.jboss.org/documentation/whatsnew/
>>
>> Schedule:
>> https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.
>> system.project%3Aversions-panel
>>
>> --
>>
>> Additional update sites:
>> *
>> http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.C
>> R1-updatesite-core/ *
>> http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.C
>> R1-updatesite-coretests/ *
>> http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.C
>> R1-updatesite-hibernatetools/ *
>> http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.C
>> R1-updatesite-webtools/ and build sites:
>> *
>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-bui
>> ld-core/ *
>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-bui
>> ld-coretests/ *
>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-bui
>> ld-hibernatetools/ *
>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-bui
>> ld-webtools/
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From mlabuda at redhat.com  Tue Nov 25 10:34:18 2014
From: mlabuda at redhat.com (Marian Labuda)
Date: Tue, 25 Nov 2014 10:34:18 -0500 (EST)
Subject: [jbosstools-dev]  Webservices are going to be marked
In-Reply-To: <859702570.18171981.1416929018559.JavaMail.zimbra@redhat.com>
Message-ID: <1374234244.18181239.1416929658664.JavaMail.zimbra@redhat.com>

Hi all,

Webservices JIRAs are going to be labelled according to the type of webservice (soap/rest). This will help QE a lot, but also devs could profit because of more accurate filtering of WS JIRAs (triaging...). RESTful webservices will be using label "jax-rs" and SOAP webservices will be using label "jax-ws".

Thanks

Mari?n Labuda
JBoss JBDS QE


From xcoulon at redhat.com  Tue Nov 25 10:39:25 2014
From: xcoulon at redhat.com (Xavier Coulon)
Date: Tue, 25 Nov 2014 16:39:25 +0100
Subject: [jbosstools-dev] Webservices are going to be marked
In-Reply-To: <1374234244.18181239.1416929658664.JavaMail.zimbra@redhat.com>
References: <1374234244.18181239.1416929658664.JavaMail.zimbra@redhat.com>
Message-ID: <0D84BF9C-4001-4DFA-8289-C848AC6F2E7F@redhat.com>

Awesome ! Thanks, Marian !

Best regards,
/Xavier



> On 25 Nov 2014, at 16:34, Marian Labuda <mlabuda at redhat.com> wrote:
> 
> Hi all,
> 
> Webservices JIRAs are going to be labelled according to the type of webservice (soap/rest). This will help QE a lot, but also devs could profit because of more accurate filtering of WS JIRAs (triaging...). RESTful webservices will be using label "jax-rs" and SOAP webservices will be using label "jax-ws".
> 
> Thanks
> 
> Mari?n Labuda
> JBoss JBDS QE
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141125/b03c510c/attachment.html 

From nickboldt at gmail.com  Wed Nov 26 09:33:36 2014
From: nickboldt at gmail.com (Nick Boldt)
Date: Wed, 26 Nov 2014 09:33:36 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: Time to test out Tycho 0.22.0 for
 master branch builds
In-Reply-To: <F8F18CC0DECD384BAC6FBAD1A7C49A48995AC4CC@DEWDFEMB18B.global.corp.sap>
References: <F8F18CC0DECD384BAC6FBAD1A7C49A48995AC4CC@DEWDFEMB18B.global.corp.sap>
Message-ID: <5475E4C0.7030309@gmail.com>

Some cool changes [1] are coming in Tycho 0.22, which should be released 
shortly.

* *INCOMPATIBLE* Bundle-RequireExecutionEnvironment (BREE) changes
* source bundle inclusion in target platforms
* JDT prefs
* support for JRE 1.8
* support for things like ${project.version} in a build.properties file
* newer version of Surefire
* using Surefire w/ specific JDK set by test bundle's BREE
* updated to use Mars M3

* more: see https://wiki.eclipse.org/Tycho/Release_Notes/0.22

If you have a chance to build your component w/ 0.22, please do and let 
me know if anything breaks.

To test w/ 0.22, you need to do two things:

a) add the new pluginRepository listed below to your ~/.m2/settings.xml

b) build with mvn -DtychoVersion=0.22.0

--

I've already noticed one problem: our repository-utils don't work w/ 0.22:

 > [ERROR] Failed to execute goal 
org.jboss.tools.tycho-plugins:repository-utils:0.21.0:generate-repository-facade 
(generate-facade) on project parent: Execution generate-facade of goal 
org.jboss.tools.tycho-plugins:repository-utils:0.21.0:generate-repository-facade 
failed: A required class was missing while executing 
org.jboss.tools.tycho-plugins:repository-utils:0.21.0:generate-repository-facade: 
org/eclipse/tycho/core/facade/BuildProperties


-------- Original Message --------
Subject: [tycho-user] Tycho 0.22.0 staged
Date: Mon, 24 Nov 2014 08:15:56 +0000
From: Sievers, Jan <jan.sievers at sap.com>
Reply-To: Tycho user list <tycho-user at eclipse.org>
To: Tycho user list (tycho-user at eclipse.org) <tycho-user at eclipse.org>
CC: Tycho developers list (tycho-dev at eclipse.org) <tycho-dev at eclipse.org>

Tycho milestone release 0.22.0 has been staged.

For details of new features and bugfixes, see release notes [1].
Please help by testing the staged milestone build. To use it, change 
your tycho version to 0.22.0 and add snippet [2] to your pom.

We plan to promote this release in one week unless major regressions are 
found.

Regards,
Tycho team

[1] http://wiki.eclipse.org/Tycho/Release_Notes/0.22
[2]
<pluginRepositories>
  <pluginRepository>
   <id>tycho-staged</id>
 
<url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-1020</url>
  </pluginRepository>
</pluginRepositories>
_______________________________________________
tycho-user mailing list
tycho-user at eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user



From nboldt at redhat.com  Wed Nov 26 09:39:23 2014
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 26 Nov 2014 09:39:23 -0500
Subject: [jbosstools-dev] FYI: Docker in Jenkins
In-Reply-To: <op.xpxbzf14avkw0j@dhcp-10-40-3-152.brq.redhat.com>
References: <op.xpxbzf14avkw0j@dhcp-10-40-3-152.brq.redhat.com>
Message-ID: <5475E61B.1070101@redhat.com>

FYI, we can now run docker container builds on RHEL7 x86_64 slaves, if 
we want to.


-------- Original Message --------
Subject: Docker on Beaker slaves
Date: Wed, 26 Nov 2014 09:46:17 +0100
From: oliver gond?a <ogondza at redhat.com>
To: jboss-qa-internal at redhat.com <jboss-qa-internal at redhat.com>

Hi,

I would like to inform you that rhel7&&x86_64 machines provisioned from
Beaker[1] are configured to run docker containers locally via docker
command. If you are managing you own slaves make sure to fetch the latest
sources[2] and reprovision (label will be added automatically).

[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/docker/
[2]
http://git.app.eng.bos.redhat.com/git/jbossqe/jenkins-beaker-slaves.git/

-- 
oliver
JBoss QA Jenkins Team




From manderse at redhat.com  Wed Nov 26 12:51:35 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 26 Nov 2014 18:51:35 +0100
Subject: [jbosstools-dev] ACTION REQUIRED: Time to test out Tycho 0.22.0
 for master branch builds
In-Reply-To: <5475E4C0.7030309@gmail.com>
References: <F8F18CC0DECD384BAC6FBAD1A7C49A48995AC4CC@DEWDFEMB18B.global.corp.sap>
	<5475E4C0.7030309@gmail.com>
Message-ID: <3D8FD95E-569E-444B-9CD3-449F70BCDD56@redhat.com>

On 26 Nov 2014, at 15:33, Nick Boldt wrote:

> Some cool changes [1] are coming in Tycho 0.22, which should be 
> released
> shortly.
>
> * *INCOMPATIBLE* Bundle-RequireExecutionEnvironment (BREE) changes

I would not call incompatible changes Cool ;)

But looks like this was a bug in tycho anyway and we should just not 
have multiple BREE's in our manifest files.


> * source bundle inclusion in target platforms

yeah, this is Mistria's work (at least that there is a flag for it!)

> * JDT prefs

This is interesting!

> * support for JRE 1.8
> * support for things like ${project.version} in a build.properties 
> file

definitely interesting.

> * newer version of Surefire
> * using Surefire w/ specific JDK set by test bundle's BREE

I'm wondering if that will be useful for us.

> * updated to use Mars M3
>
> I've already noticed one problem: our repository-utils don't work w/ 
> 0.22:
>
>> [ERROR] Failed to execute goal
> org.jboss.tools.tycho-plugins:repository-utils:0.21.0:generate-repository-facade
> (generate-facade) on project parent: Execution generate-facade of goal
> org.jboss.tools.tycho-plugins:repository-utils:0.21.0:generate-repository-facade
> failed: A required class was missing while executing
> org.jboss.tools.tycho-plugins:repository-utils:0.21.0:generate-repository-facade:
> org/eclipse/tycho/core/facade/BuildProperties

thats not surprising since its using API from tycho - so I guess a 
release of this plugin is at least needed before we can consider update.

/max
>
>
> -------- Original Message --------
> Subject: [tycho-user] Tycho 0.22.0 staged
> Date: Mon, 24 Nov 2014 08:15:56 +0000
> From: Sievers, Jan <jan.sievers at sap.com>
> Reply-To: Tycho user list <tycho-user at eclipse.org>
> To: Tycho user list (tycho-user at eclipse.org) <tycho-user at eclipse.org>
> CC: Tycho developers list (tycho-dev at eclipse.org) 
> <tycho-dev at eclipse.org>
>
> Tycho milestone release 0.22.0 has been staged.
>
> For details of new features and bugfixes, see release notes [1].
> Please help by testing the staged milestone build. To use it, change
> your tycho version to 0.22.0 and add snippet [2] to your pom.
>
> We plan to promote this release in one week unless major regressions 
> are
> found.
>
> Regards,
> Tycho team
>
> [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.22
> [2]
> <pluginRepositories>
> <pluginRepository>
> <id>tycho-staged</id>
>
> <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-1020</url>
> </pluginRepository>
> </pluginRepositories>
> _______________________________________________
> tycho-user mailing list
> tycho-user at eclipse.org
> To change your delivery options, retrieve your password, or 
> unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/tycho-user
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From mistria at redhat.com  Wed Nov 26 12:56:05 2014
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 26 Nov 2014 18:56:05 +0100
Subject: [jbosstools-dev] ACTION REQUIRED: Time to test out Tycho 0.22.0
 for master branch builds
In-Reply-To: <3D8FD95E-569E-444B-9CD3-449F70BCDD56@redhat.com>
References: <F8F18CC0DECD384BAC6FBAD1A7C49A48995AC4CC@DEWDFEMB18B.global.corp.sap>	<5475E4C0.7030309@gmail.com>
	<3D8FD95E-569E-444B-9CD3-449F70BCDD56@redhat.com>
Message-ID: <54761435.8060308@redhat.com>

On 11/26/2014 06:51 PM, Max Rydahl Andersen wrote:
> thats not surprising since its using API from tycho - so I guess a 
> release of this plugin is at least needed before we can consider update.
Version 0.21.1 was released recently on Paul's request, and no change 
was made since then.
So it seems like we're good to start a 0.22 stream of our mojos.

-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141126/3df7e7d9/attachment.html 

From akazakov at exadel.com  Wed Nov 26 14:40:02 2014
From: akazakov at exadel.com (Alexey Kazakov)
Date: Wed, 26 Nov 2014 11:40:02 -0800
Subject: [jbosstools-dev] ATTENTION REQUIRED: 4.2.1/8.0.1 triage
Message-ID: <54762C92.4020004@exadel.com>

Hi,

There are 87 unresolved issues with Fix Version=4.2.1.Final (JBT) and 
8.0.1.GA (JBDS) in our JIRA.
I believe we are not going to fix all of them in next 10 days:

https://issues.jboss.org/issues/?jql=project%20in%20(JBIDE%2C%20JBDS)%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(4.2.1.Final%2C%208.0.1.GA)%20ORDER%20BY%20priority%20DESC

We are going to have one respin for 4.2.1.CR1 on 7th December ( + little 
one on 11th December if needed).

So, I'm asking all developers, please go to JIRA and mark all issues you 
are going to fix for 4.2.1/8.0.1 as:
*Fix Version/s:* 4.2.1.CR1 (or 8.0.1.CR for JBDS)
*Label:* respin-a

And make sure your QE are OK with your plans. The rest of the issues 
with fix version = "4.2.1.Final/8.0.1.GA" should be moved out to 
4.2.2/8.0.2 or 4.2.x/8.0.x.

Thank you!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141126/ad6607bd/attachment-0001.html 

From mistria at redhat.com  Thu Nov 27 03:51:33 2014
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 27 Nov 2014 09:51:33 +0100
Subject: [jbosstools-dev] V8 for Java
Message-ID: <5476E615.4000201@redhat.com>

http://eclipsesource.com/blogs/2014/11/17/highly-efficient-java-javascript-integration/
Not sure how it would compare to Nashorn, but it might be a good 
alternative. We can imagine JSDT debugger using it instead of Rhino.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141127/6e1ade7f/attachment.html 

From manderse at redhat.com  Thu Nov 27 08:53:13 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 27 Nov 2014 14:53:13 +0100
Subject: [jbosstools-dev] V8 for Java
In-Reply-To: <5476E615.4000201@redhat.com>
References: <5476E615.4000201@redhat.com>
Message-ID: <5D18E490-FB30-4983-AFD4-FC56BAB33641@redhat.com>

On 27 Nov 2014, at 9:51, Mickael Istria wrote:

> http://eclipsesource.com/blogs/2014/11/17/highly-efficient-java-javascript-integration/
> Not sure how it would compare to Nashorn, but it might be a good 
> alternative. We can imagine JSDT debugger using it instead of Rhino.

yeah, saw this as suggested talk at eclipsecon this week too.

Was thinking it would great for something like Tern and avoid having to 
depend on node.js install.

/max
http://about.me/maxandersen


From angelo.zerr at gmail.com  Thu Nov 27 08:57:13 2014
From: angelo.zerr at gmail.com (Angelo zerr)
Date: Thu, 27 Nov 2014 14:57:13 +0100
Subject: [jbosstools-dev] V8 for Java
In-Reply-To: <5D18E490-FB30-4983-AFD4-FC56BAB33641@redhat.com>
References: <5476E615.4000201@redhat.com>
	<5D18E490-FB30-4983-AFD4-FC56BAB33641@redhat.com>
Message-ID: <CAKLdLg9wVu5DwrBRSc7QiJtz2bG-+LumH9ANdOhAcfCzD9Jntw@mail.gmail.com>

Hi everybody,

> Was thinking it would great for something like Tern and avoid having to depend
on node.js install.

Pay attention with that. Some tern plugin like Closure, node.js depends on
node.js. For instance node.js tern plugin use some node functions to
retrieve module of your project.

Reagrd's Angelo

2014-11-27 14:53 GMT+01:00 Max Rydahl Andersen <manderse at redhat.com>:

> On 27 Nov 2014, at 9:51, Mickael Istria wrote:
>
> >
> http://eclipsesource.com/blogs/2014/11/17/highly-efficient-java-javascript-integration/
> > Not sure how it would compare to Nashorn, but it might be a good
> > alternative. We can imagine JSDT debugger using it instead of Rhino.
>
> yeah, saw this as suggested talk at eclipsecon this week too.
>
> Was thinking it would great for something like Tern and avoid having to
> depend on node.js install.
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141127/7ced387c/attachment.html 

From manderse at redhat.com  Thu Nov 27 09:22:48 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 27 Nov 2014 15:22:48 +0100
Subject: [jbosstools-dev] V8 for Java
In-Reply-To: <CAKLdLg9wVu5DwrBRSc7QiJtz2bG-+LumH9ANdOhAcfCzD9Jntw@mail.gmail.com>
References: <5476E615.4000201@redhat.com>
	<5D18E490-FB30-4983-AFD4-FC56BAB33641@redhat.com>
	<CAKLdLg9wVu5DwrBRSc7QiJtz2bG-+LumH9ANdOhAcfCzD9Jntw@mail.gmail.com>
Message-ID: <63956478-E506-48AB-8E04-5004A8A74EC4@redhat.com>

On 27 Nov 2014, at 14:57, Angelo zerr wrote:

> Hi everybody,
>
>> Was thinking it would great for something like Tern and avoid having 
>> to depend
> on node.js install.
>
> Pay attention with that. Some tern plugin like Closure, node.js 
> depends on
> node.js. For instance node.js tern plugin use some node functions to
> retrieve module of your project.

thats sad. I thought you were not dependent on node.js specific plugins 
?

/max

>
> Reagrd's Angelo
>
> 2014-11-27 14:53 GMT+01:00 Max Rydahl Andersen <manderse at redhat.com>:
>
>> On 27 Nov 2014, at 9:51, Mickael Istria wrote:
>>
>>>
>> http://eclipsesource.com/blogs/2014/11/17/highly-efficient-java-javascript-integration/
>>> Not sure how it would compare to Nashorn, but it might be a good
>>> alternative. We can imagine JSDT debugger using it instead of Rhino.
>>
>> yeah, saw this as suggested talk at eclipsecon this week too.
>>
>> Was thinking it would great for something like Tern and avoid having 
>> to
>> depend on node.js install.
>>
>> /max
>> http://about.me/maxandersen
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>


/max
http://about.me/maxandersen


From angelo.zerr at gmail.com  Thu Nov 27 09:27:47 2014
From: angelo.zerr at gmail.com (Angelo zerr)
Date: Thu, 27 Nov 2014 15:27:47 +0100
Subject: [jbosstools-dev] V8 for Java
In-Reply-To: <63956478-E506-48AB-8E04-5004A8A74EC4@redhat.com>
References: <5476E615.4000201@redhat.com>
	<5D18E490-FB30-4983-AFD4-FC56BAB33641@redhat.com>
	<CAKLdLg9wVu5DwrBRSc7QiJtz2bG-+LumH9ANdOhAcfCzD9Jntw@mail.gmail.com>
	<63956478-E506-48AB-8E04-5004A8A74EC4@redhat.com>
Message-ID: <CAKLdLg9UA44VO4WTia-GSs7M1BQSmgtqqwENVaRceOOWH-EkWA@mail.gmail.com>

2014-11-27 15:22 GMT+01:00 Max Rydahl Andersen <manderse at redhat.com>:

> On 27 Nov 2014, at 14:57, Angelo zerr wrote:
>
>  Hi everybody,
>>
>>  Was thinking it would great for something like Tern and avoid having to
>>> depend
>>>
>> on node.js install.
>>
>> Pay attention with that. Some tern plugin like Closure, node.js depends on
>> node.js. For instance node.js tern plugin use some node functions to
>> retrieve module of your project.
>>
>
> thats sad. I thought you were not dependent on node.js specific plugins ?
>

Today :

 *  node tern plugin uses node.js function, BUT it can work without node
(in Web Browser). In the web browser case, the only feature that it is not
managed is custom node module.
 * closure tern plugin works only with node.js
 * other tern plugin (angular, cordova, etc) doesn't require node.js



> /max
>
>
>> Reagrd's Angelo
>>
>> 2014-11-27 14:53 GMT+01:00 Max Rydahl Andersen <manderse at redhat.com>:
>>
>>  On 27 Nov 2014, at 9:51, Mickael Istria wrote:
>>>
>>>
>>>>  http://eclipsesource.com/blogs/2014/11/17/highly-
>>> efficient-java-javascript-integration/
>>>
>>>> Not sure how it would compare to Nashorn, but it might be a good
>>>> alternative. We can imagine JSDT debugger using it instead of Rhino.
>>>>
>>>
>>> yeah, saw this as suggested talk at eclipsecon this week too.
>>>
>>> Was thinking it would great for something like Tern and avoid having to
>>> depend on node.js install.
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>
> /max
> http://about.me/maxandersen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141127/ba24d6e2/attachment.html 

From angelo.rlcosta at gmail.com  Fri Nov 28 05:55:37 2014
From: angelo.rlcosta at gmail.com (=?UTF-8?Q?=C3=82ngelo_Costa?=)
Date: Fri, 28 Nov 2014 10:55:37 +0000
Subject: [jbosstools-dev] (no subject)
Message-ID: <CAGvGh_3DUtP+-Gc0dEYH0B4jUuujjZcuns0hmE-dAO3Hh3VdmA@mail.gmail.com>

I need to install switchyard service debugger. Any tutorial on the web
    which i can follow?
    I am using JBoss Developer Studio Version: 7.1.1.GA <http://7.1.1.ga/>.
    Thanks in advance,

?ngelo Costa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141128/f5a2ed80/attachment.html 

From manderse at redhat.com  Sat Nov 29 02:59:05 2014
From: manderse at redhat.com (manderse at redhat.com)
Date: Sat, 29 Nov 2014 02:59:05 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201411290759.sAT7x5JO004465@int-mx09.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3240

https://issues.jboss.org/browse/JBDS-3240
Summary: JBDS 8 aka JBoss Central provide by default old EAP/WFK archetypes

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 18:03:37.548934

----------------------------



Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY

From manderse at redhat.com  Sun Nov 30 02:59:06 2014
From: manderse at redhat.com (manderse at redhat.com)
Date: Sun, 30 Nov 2014 02:59:06 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201411300759.sAU7x6lu011799@int-mx14.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3240

https://issues.jboss.org/browse/JBDS-3240
Summary: JBDS 8 aka JBoss Central provide by default old EAP/WFK archetypes

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 1 day, 18:03:37.981762

----------------------------



Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY

From manderse at redhat.com  Sun Nov 30 12:00:13 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Sun, 30 Nov 2014 18:00:13 +0100
Subject: [jbosstools-dev] (no subject)
In-Reply-To: <CAGvGh_3DUtP+-Gc0dEYH0B4jUuujjZcuns0hmE-dAO3Hh3VdmA@mail.gmail.com>
References: <CAGvGh_3DUtP+-Gc0dEYH0B4jUuujjZcuns0hmE-dAO3Hh3VdmA@mail.gmail.com>
Message-ID: <1D89A436-1F81-4B8C-B995-E9FCE3B64004@redhat.com>

On 28 Nov 2014, at 11:55, ?ngelo Costa wrote:

> I need to install switchyard service debugger. Any tutorial on the web
>   which i can follow?
>   I am using JBoss Developer Studio Version: 7.1.1.GA 
> <http://7.1.1.ga/>.
>   Thanks in advance,

Does this work 
http://tools.jboss.org/blog/2014-11-14-switchyard-debugger.html ?

btw. jbosstools-dev is for feature development discussions.

Better to use the user forums at 
https://developer.jboss.org/en/products/devstudio for user specific 
questions.

/max
http://about.me/maxandersen