From mistria at redhat.com  Thu Oct  1 01:55:10 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 1 Oct 2015 07:55:10 +0200
Subject: [jbosstools-dev] Target Platforms 4.50.0.Final has been released
Message-ID: <560CCABE.3040405@redhat.com>

Target Platforms 4.50.0.Final, based on Eclipse Mars.0, has been released.

Usage
=====

Target platform 4.50.0.Final is what JBoss Tools 4.3.0.Final will use as *minimal* target-platform (lowest supported version of dependencies).
All Jenkins jobs for branch jbosstools-4.3.x and parent pom 4.3.0.Final-SNAPSHOT have been updated to use target platform 4.50.0.Final.


Download
========

Update site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Final/
Update site zip: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/${TARGET_PLATFORM_VERSION}/jbosstoolstarget-4.50.0.Final.zip
Git tag: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.50.0.Final


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

If your root pom correctly specifies the latest parent pom version as 4.3.0.Final-SNAPSHOT, you need only this:
   $ mvn clean verify
If you're using a different parent pom, use this:
   $ mvn clean verify -Dtpc.version=4.3.0.Final
For advanced usage and help (using in IDE, building a mirror locally, using a zip), see:
* link:target_platforms/target_platforms_for_consumers.adoc[Using Target Platforms]


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

jbosstools-target-platforms project branch 4.50.x has been prepared for potential upgrades, and its version is now 4,50.1.CR1-SNAPSHOT.
But since no change is expected yet, this SNAPSHOT is currently not published and it's recommended that you don't use it until further notice


From nboldt at redhat.com  Thu Oct  1 09:38:24 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 1 Oct 2015 09:38:24 -0400
Subject: [jbosstools-dev] New devdoc component added to JBIDE JIRA
Message-ID: <CA+QcL13rcsyaw1VH0U4T_axB19FaTMz3ms+OHT7gDW6t4h6vXw@mail.gmail.com>

FYI, I've added a new component to JBIDE JIRA: devdoc.

This is because having everything in "build" isn't always accurate.
Hopefully this will also encourage me, Mickael, Paul, Max, Alexey,
Denis, etc. to write & update more developer documentation so our
process documents stay current, even as they're evolving & improving.

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

I haven't created a matching component in JBDS yet, since most devdoc
is in https://github.com/jbosstools/jbosstools-devdoc - we only use
https://github.com/jbdevstudio/jbdevstudio-devdoc for the release
guide, which other than some internal server details could potentially
be moved to the JBT side of the house.

Comments, feedback, brickbats & new issues under this component welcome.

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

From ldimaggi at redhat.com  Thu Oct  1 09:49:56 2015
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Thu, 1 Oct 2015 09:49:56 -0400
Subject: [jbosstools-dev] New devdoc component added to JBIDE JIRA
In-Reply-To: <CA+QcL13rcsyaw1VH0U4T_axB19FaTMz3ms+OHT7gDW6t4h6vXw@mail.gmail.com>
References: <CA+QcL13rcsyaw1VH0U4T_axB19FaTMz3ms+OHT7gDW6t4h6vXw@mail.gmail.com>
Message-ID: <CA+qK+9nofT_Lc5RtO8Vaw4DYNcnzVFe+MBcKmYDD9pufaWr4SA@mail.gmail.com>

+1 - good idea!

On Thu, Oct 1, 2015 at 9:38 AM, Nick Boldt <nboldt at redhat.com> wrote:

> FYI, I've added a new component to JBIDE JIRA: devdoc.
>
> This is because having everything in "build" isn't always accurate.
> Hopefully this will also encourage me, Mickael, Paul, Max, Alexey,
> Denis, etc. to write & update more developer documentation so our
> process documents stay current, even as they're evolving & improving.
>
>
> https://issues.jboss.org/browse/JBIDE/component/12322530/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>
> I haven't created a matching component in JBDS yet, since most devdoc
> is in https://github.com/jbosstools/jbosstools-devdoc - we only use
> https://github.com/jbdevstudio/jbdevstudio-devdoc for the release
> guide, which other than some internal server details could potentially
> be moved to the JBT side of the house.
>
> Comments, feedback, brickbats & new issues under this component welcome.
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> 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/20151001/808da579/attachment-0001.html 

From fbricon at redhat.com  Thu Oct  1 10:28:11 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Thu, 1 Oct 2015 10:28:11 -0400
Subject: [jbosstools-dev] Coming soon to a Tycho build near you: pomless
	builds!
In-Reply-To: <23C066BE-8C6C-452A-9E52-48ED2C953BF3@redhat.com>
References: <CA+QcL103JiEO-8mmWjbo+6Mn_R-D2XVGM+bFPJ0kYz8g8N0xzQ@mail.gmail.com>
	<23C066BE-8C6C-452A-9E52-48ED2C953BF3@redhat.com>
Message-ID: <CACvX+KiaVJhaAzOVcjqwNkKWUQjTP_sGdV=pknWokpt2tXPQcQ@mail.gmail.com>

(reposting for all)

No m2e(-tycho) doesn't support pom-less projects, because well, they're
pom-less :-)

m2e lacks native support for polyglot maven (more generally Maven
extensions), this is something I need to discuss with Igor and JVZ at some
point but, according to igor, it will be very hard to implement.

On Wed, Sep 30, 2015 at 3:52 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> On 29 Sep 2015, at 20:21, Nick Boldt wrote:
>
> > ... well, NEARLY pomless. Still need a root pom or parent pom.
> >
> > And might need to refactor your test plugins to end with ".tests" in
> > their Bundle-SymbolicName (in MANIFEST.MF).
> >
> > But hey, less crufty metadata!
> >
> > Details:
> >
> > http://wiki.eclipse.org/Tycho/Release_Notes/0.24
> >
> > Sample project:
> >
> >
> http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/tree/tycho-extras-its/src/test/resources/testpomless
>
> Anyone tried if this work without issues in m2e yet ?
>
> How about the mvn plugin for bumping of versions ? Does it change the
> manifest.mf when no pom.xml present ?
>
> If that works then a loose count [1] indicates we can delete about 433
> files.
>
>
> [1] `grep -Rl --include "pom.xml" "packaging>eclipse" jbosstools-* |
> xargs -n 1 grep -lL "module" | xargs -n 1 grep -lL "build" | xargs -n 1
> grep -1L "dependency"`
>
> The above simply try locate all pom.xml, that has custom eclipse
> packaging enabled, don't have module listed and do not have custom build
> or dependency instructions.
>
> >
> >
> >
> > --
> > Nick Boldt :: JBoss by Red Hat
> > Productization Lead :: JBoss Tools & Dev Studio
> > http://nick.divbyzero.com
> > _______________________________________________
> > 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/20151001/626b3881/attachment.html 

From mistria at redhat.com  Thu Oct  1 10:37:26 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 1 Oct 2015 16:37:26 +0200
Subject: [jbosstools-dev] Coming soon to a Tycho build near you: pomless
 builds!
In-Reply-To: <CACvX+KiaVJhaAzOVcjqwNkKWUQjTP_sGdV=pknWokpt2tXPQcQ@mail.gmail.com>
References: <CA+QcL103JiEO-8mmWjbo+6Mn_R-D2XVGM+bFPJ0kYz8g8N0xzQ@mail.gmail.com>
	<23C066BE-8C6C-452A-9E52-48ED2C953BF3@redhat.com>
	<CACvX+KiaVJhaAzOVcjqwNkKWUQjTP_sGdV=pknWokpt2tXPQcQ@mail.gmail.com>
Message-ID: <560D4526.7090809@redhat.com>

On 10/01/2015 04:28 PM, Fred Bricon wrote:
> No m2e(-tycho) doesn't support pom-less projects, because well, 
> they're pom-less :-)
> m2e lacks native support for polyglot maven (more generally Maven 
> extensions), this is something I need to discuss with Igor and JVZ at 
> some point but, according to igor, it will be very hard to implement.
In any case, a MANIFEST.MF is not a Maven-specific metadata file, so 
even with polyglot support, m2e would need to crawl in parent to find 
out whether there is a parent pom which defines the folder of the 
current plugin project as module... Seems quite intrusive in IDE.
I am not that thrilled by the pom-less things. Indeed it saves a few 
files, but it adds a layer of generation that makes the process more 
complicated and the integration with tools loess explicit. Moreover, the 
cost of having and maintaining a pom file is quite low, so I have 
trouble to figure out whether we'd save much effort (or add some more) 
in adopting it.

-- 
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/20151001/71a14163/attachment.html 

From alkazako at redhat.com  Thu Oct  1 13:59:18 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Thu, 1 Oct 2015 13:59:18 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: N&N for 4.3.0.Final by EOD Monday
Message-ID: <560D7476.1000205@redhat.com>

Hi,

It's time to create a new and noteworthy for JBoss Tools 4.3.0.Final.
I have created https://issues.jboss.org/browse/JBIDE-20876 for that.

For most components the default aggregation of all previous 
Alpha*/Beta*/CR* N&N documents is enough. If it's your case then just 
reject and close the jira.
If you need to add a final comment or replace the entire N&N by a new 
document then see details in the jira.

This must be done by the end of Monday, October the 6th. Sorry for the 
late notice.

Thank you.

From manderse at redhat.com  Fri Oct  2 04:41:19 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 02 Oct 2015 10:41:19 +0200
Subject: [jbosstools-dev] New devdoc component added to JBIDE JIRA
In-Reply-To: <CA+QcL13rcsyaw1VH0U4T_axB19FaTMz3ms+OHT7gDW6t4h6vXw@mail.gmail.com>
References: <CA+QcL13rcsyaw1VH0U4T_axB19FaTMz3ms+OHT7gDW6t4h6vXw@mail.gmail.com>
Message-ID: <C8E2DC08-72E2-4988-BDCE-6359ABC080E4@redhat.com>

do we really need both devdoc and documentation component ?

in any case, I would say life is simpler if we have components in JBIDE 
that we also have in JBDS ....

/max

> FYI, I've added a new component to JBIDE JIRA: devdoc.
>
> This is because having everything in "build" isn't always accurate.
> Hopefully this will also encourage me, Mickael, Paul, Max, Alexey,
> Denis, etc. to write & update more developer documentation so our
> process documents stay current, even as they're evolving & improving.
>
> https://issues.jboss.org/browse/JBIDE/component/12322530/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>
> I haven't created a matching component in JBDS yet, since most devdoc
> is in https://github.com/jbosstools/jbosstools-devdoc - we only use
> https://github.com/jbdevstudio/jbdevstudio-devdoc for the release
> guide, which other than some internal server details could potentially
> be moved to the JBT side of the house.
>
> Comments, feedback, brickbats & new issues under this component 
> welcome.
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> 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  Fri Oct  2 06:17:01 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 2 Oct 2015 12:17:01 +0200
Subject: [jbosstools-dev] The list of uninstallable connectors at the top of
 Central catalog sucks
Message-ID: <560E599D.5020207@redhat.com>

Hi all,

While I'm testing staged JBT 4.3.0.CR2a, I noticed that a user facing 
Central will see a catalog with a list of items that they cannot select, 
with no widget, nothing. Click "Select All" doesn't produce an obvious 
feedback so user isn't aware of the impact of "Select All".
It takes at least a few seconds to me, who developed most of the support 
for those uninstallable entries in Central catalog, to think about 
scrolling down to see usable content. I believe it's going to be much 
worse for new users, or for those who don't look at software page often.
Those entries hide some parts of JBoss Tools with real added-value 
(Hybrid Tools, OpenShift v3...).

Those useless uninstallable connectors are hiding the useful content, 
and unless one already knows or is curious enough to find installable 
connectors, it just make this install page seem useless. IMO, it's worse 
to have this poor UX in our product than to have some occasional 
questions on the user forums.
My immediate recommendation would be:
* Either to drop all those JBT-IS "not yet available" connector and face 
user questions on forums, or
* instead of a dozen of "not yet available" entries hiding the 
installable one, we should have a single "JBoss Tools integration Stack" 
entry telling that the content are not available yet.

On a longer-term approach, there are now way too many things in Central, 
either we should make it simpler, or fully revise it to have a more 
structured browser, which will ultimately look either like MarketPlace 
Client or the regular p2 install wizard with a tree (and some additional 
columns and some icons since it's the only real difference between 
central catalogs and a p2 site)

Cheers,
-- 
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/20151002/7aab9353/attachment.html 

From mistria at redhat.com  Fri Oct  2 06:29:14 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 2 Oct 2015 12:29:14 +0200
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.CR2a bits available for QE
	testing
Message-ID: <560E5C7A.4070704@redhat.com>

JBoss Tools Core 4.3.0.CR2a bits available for QE testing.
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/mars/staging/updates/

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

Changes prompting this respin-a are:
https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-a%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%229.0.0.CR2%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224,3,9,CR2%22%29%29%29

--
Additional update sites:
* http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.CR2a/
* 
http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.CR2a/
Target platform:
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.51.0.Final
Discovery sites:
* 
http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.CR2a/
* 
http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.CR2a/
Build folders (for build logs & update site zips):
* http://download.jboss.org/jbosstools/mars/staging/builds/
To compare the upcoming version of Central (4.3.0.CR2a) against an older 
version, add lines similar to these your eclipse.ini file after the 
-vmargs line for the appropriate version & URLs:
  -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.CR2a/jbosstools-directory.xml
  -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/
  -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.CR2a/
  -Djboss.discovery.earlyaccess.list.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.CR2a/jbosstools-earlyaccess.properties


-- 
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/20151002/9769d34b/attachment-0001.html 

From manderse at redhat.com  Fri Oct  2 06:41:10 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 02 Oct 2015 12:41:10 +0200
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <560E599D.5020207@redhat.com>
References: <560E599D.5020207@redhat.com>
Message-ID: <D495A10B-06DB-43F8-9C35-E1D6AF9B5D2C@redhat.com>


> Hi all,
>
> While I'm testing staged JBT 4.3.0.CR2a, I noticed that a user facing 
> Central will see a catalog with a list of items that they cannot 
> select, with no widget, nothing. Click "Select All" doesn't produce an 
> obvious feedback so user isn't aware of the impact of "Select All".
> It takes at least a few seconds to me, who developed most of the 
> support for those uninstallable entries in Central catalog, to think 
> about scrolling down to see usable content. I believe it's going to be 
> much worse for new users, or for those who don't look at software page 
> often.

can you please open jira with screenshot ?

There should only be *one* entry that is marked as "coming later" and 
thats Fuse.

/max

> Those entries hide some parts of JBoss Tools with real added-value 
> (Hybrid Tools, OpenShift v3...).
>
> Those useless uninstallable connectors are hiding the useful content, 
> and unless one already knows or is curious enough to find installable 
> connectors, it just make this install page seem useless. IMO, it's 
> worse to have this poor UX in our product than to have some occasional 
> questions on the user forums.
> My immediate recommendation would be:
> * Either to drop all those JBT-IS "not yet available" connector and 
> face user questions on forums, or
> * instead of a dozen of "not yet available" entries hiding the 
> installable one, we should have a single "JBoss Tools integration 
> Stack" entry telling that the content are not available yet.
>
> On a longer-term approach, there are now way too many things in 
> Central, either we should make it simpler, or fully revise it to have 
> a more structured browser, which will ultimately look either like 
> MarketPlace Client or the regular p2 install wizard with a tree (and 
> some additional columns and some icons since it's the only real 
> difference between central catalogs and a p2 site)
>
> Cheers,
> -- 
> 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 manderse at redhat.com  Fri Oct  2 06:53:11 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 02 Oct 2015 12:53:11 +0200
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <560E599D.5020207@redhat.com>
References: <560E599D.5020207@redhat.com>
Message-ID: <6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>

On 2 Oct 2015, at 12:17, Mickael Istria wrote:

> My immediate recommendation would be:
> \* Either to drop all those JBT-IS "not yet available" connector and 
> face user questions on forums, or
> \* instead of a dozen of "not yet available" entries hiding the 
> installable one, we should have a single "JBoss Tools integration 
> Stack" entry telling that the content are not available yet.

This is what we agreed to start with afaik.

No point/value in doing this for each single individual connector.

Also a reason why I don't like to have so many individual components in 
central...we don't do that for JBDS for this reason.

/max
http://about.me/maxandersen

From ldimaggi at redhat.com  Fri Oct  2 08:49:20 2015
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Fri, 2 Oct 2015 08:49:20 -0400
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>
References: <560E599D.5020207@redhat.com>
	<6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>
Message-ID: <CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>

Mickael - Are these (see attached) the items (form 9.0.CR2) that you are
referring to?


?

On Fri, Oct 2, 2015 at 6:53 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> On 2 Oct 2015, at 12:17, Mickael Istria wrote:
>
> > My immediate recommendation would be:
> > \* Either to drop all those JBT-IS "not yet available" connector and
> > face user questions on forums, or
> > \* instead of a dozen of "not yet available" entries hiding the
> > installable one, we should have a single "JBoss Tools integration
> > Stack" entry telling that the content are not available yet.
>
> This is what we agreed to start with afaik.
>
> No point/value in doing this for each single individual connector.
>
> Also a reason why I don't like to have so many individual components in
> central...we don't do that for JBDS for this reason.
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> 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/20151002/7f688942/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot.png
Type: image/png
Size: 53404 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151002/7f688942/attachment-0001.png 

From mistria at redhat.com  Fri Oct  2 08:51:04 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 2 Oct 2015 14:51:04 +0200
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>
References: <560E599D.5020207@redhat.com>
	<6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>
	<CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>
Message-ID: <560E7DB8.2070501@redhat.com>

On 10/02/2015 02:49 PM, Leonard Dimaggio wrote:
> Mickael - Are these (see attached) the items (form 9.0.CR2) that you 
> are referring to?
>
>
> ?
>
I was looking at JBoss Tools at that time, not JBDS, but yes, it's more 
or less the same issue of multiple not yet avallable things hiding 
valuable content.
-- 
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/20151002/43a9011f/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 53404 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151002/43a9011f/attachment-0001.png 

From ldimaggi at redhat.com  Fri Oct  2 09:30:36 2015
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Fri, 2 Oct 2015 09:30:36 -0400
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <560E7DB8.2070501@redhat.com>
References: <560E599D.5020207@redhat.com>
	<6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>
	<CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>
	<560E7DB8.2070501@redhat.com>
Message-ID: <CA+qK+9kim2ifOFGyw4RH5tGe+ZZW0ZxDdFxcPLVEdEy28X4pDA@mail.gmail.com>

But - isn't this just a temporary condition until the tooling is available?

On Fri, Oct 2, 2015 at 8:51 AM, Mickael Istria <mistria at redhat.com> wrote:

> On 10/02/2015 02:49 PM, Leonard Dimaggio wrote:
>
> Mickael - Are these (see attached) the items (form 9.0.CR2) that you are
> referring to?
>
>
> ?
>
> I was looking at JBoss Tools at that time, not JBDS, but yes, it's more or
> less the same issue of multiple not yet avallable things hiding valuable
> content.
> --
> 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>
>



-- 
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/20151002/31b4bd80/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 53404 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151002/31b4bd80/attachment-0001.png 

From pleacu at redhat.com  Fri Oct  2 09:54:46 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Fri, 2 Oct 2015 09:54:46 -0400 (EDT)
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <CA+qK+9kim2ifOFGyw4RH5tGe+ZZW0ZxDdFxcPLVEdEy28X4pDA@mail.gmail.com>
References: <560E599D.5020207@redhat.com>
	<6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>
	<CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>
	<560E7DB8.2070501@redhat.com>
	<CA+qK+9kim2ifOFGyw4RH5tGe+ZZW0ZxDdFxcPLVEdEy28X4pDA@mail.gmail.com>
Message-ID: <1303670371.30449166.1443794086579.JavaMail.zimbra@redhat.com>


   That's actually a question I have.  The original Jira said they couldn't find Fuse Tooling if it was
   hidden under early access.  Now that they are available as early access, if I just delete the released
   "not available" descriptors they're hidden again (until the user selects the 'Enable Early Access' checkbox).
   The alternative would be to keep the "not available" descriptors and change the text to something like:

   "Select the 'Enable Early Access' check box for an early access installation. Also available in JBoss Tools 4.2.x."

   See comments:
   https://issues.jboss.org/browse/JBIDE-20100?focusedCommentId=13110988&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13110988

   https://issues.jboss.org/browse/JBTIS-504?focusedCommentId=13114555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13114555

   What's the collective wisdom?

        --paull


----- Original Message -----
> From: "Leonard Dimaggio" <ldimaggi at redhat.com>
> To: "Mickael Istria" <mistria at redhat.com>
> Cc: "Max Rydahl Andersen" <manderse at redhat.com>, "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
> "Paul Leacu" <pleacu at redhat.com>
> Sent: Friday, October 2, 2015 9:30:36 AM
> Subject: Re: [jbosstools-dev] The list of uninstallable connectors at the top of Central catalog sucks
> 
> But - isn't this just a temporary condition until the tooling is available?
> 
> On Fri, Oct 2, 2015 at 8:51 AM, Mickael Istria <mistria at redhat.com> wrote:
> 
> > On 10/02/2015 02:49 PM, Leonard Dimaggio wrote:
> >
> > Mickael - Are these (see attached) the items (form 9.0.CR2) that you are
> > referring to?
> >
> >
> > ?
> >
> > I was looking at JBoss Tools at that time, not JBDS, but yes, it's more or
> > less the same issue of multiple not yet avallable things hiding valuable
> > content.
> > --
> > 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>
> >
> 
> 
> 
> --
> 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
>


From ldimaggi at redhat.com  Fri Oct  2 09:57:58 2015
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Fri, 2 Oct 2015 09:57:58 -0400
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <1303670371.30449166.1443794086579.JavaMail.zimbra@redhat.com>
References: <560E599D.5020207@redhat.com>
	<6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>
	<CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>
	<560E7DB8.2070501@redhat.com>
	<CA+qK+9kim2ifOFGyw4RH5tGe+ZZW0ZxDdFxcPLVEdEy28X4pDA@mail.gmail.com>
	<1303670371.30449166.1443794086579.JavaMail.zimbra@redhat.com>
Message-ID: <CA+qK+9kb-NBAQ22P+_JP+YGTWV2rxLs+OEOtou75S4jEebJG0A@mail.gmail.com>

I would vote for this:

  "Select the 'Enable Early Access' check box for an early access
installation. Also available in JBoss Tools 4.2.x."


(Even if it means agreeing with Paul.   ;-)

On Fri, Oct 2, 2015 at 9:54 AM, Paul Leacu <pleacu at redhat.com> wrote:

>
>    That's actually a question I have.  The original Jira said they
> couldn't find Fuse Tooling if it was
>    hidden under early access.  Now that they are available as early
> access, if I just delete the released
>    "not available" descriptors they're hidden again (until the user
> selects the 'Enable Early Access' checkbox).
>    The alternative would be to keep the "not available" descriptors and
> change the text to something like:
>
>    "Select the 'Enable Early Access' check box for an early access
> installation. Also available in JBoss Tools 4.2.x."
>
>    See comments:
>
> https://issues.jboss.org/browse/JBIDE-20100?focusedCommentId=13110988&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13110988
>
>
> https://issues.jboss.org/browse/JBTIS-504?focusedCommentId=13114555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13114555
>
>    What's the collective wisdom?
>
>         --paull
>
>
> ----- Original Message -----
> > From: "Leonard Dimaggio" <ldimaggi at redhat.com>
> > To: "Mickael Istria" <mistria at redhat.com>
> > Cc: "Max Rydahl Andersen" <manderse at redhat.com>, "jbosstools-dev
> jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
> > "Paul Leacu" <pleacu at redhat.com>
> > Sent: Friday, October 2, 2015 9:30:36 AM
> > Subject: Re: [jbosstools-dev] The list of uninstallable connectors at
> the top of Central catalog sucks
> >
> > But - isn't this just a temporary condition until the tooling is
> available?
> >
> > On Fri, Oct 2, 2015 at 8:51 AM, Mickael Istria <mistria at redhat.com>
> wrote:
> >
> > > On 10/02/2015 02:49 PM, Leonard Dimaggio wrote:
> > >
> > > Mickael - Are these (see attached) the items (form 9.0.CR2) that you
> are
> > > referring to?
> > >
> > >
> > > ?
> > >
> > > I was looking at JBoss Tools at that time, not JBDS, but yes, it's
> more or
> > > less the same issue of multiple not yet avallable things hiding
> valuable
> > > content.
> > > --
> > > 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>
> > >
> >
> >
> >
> > --
> > 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
> >
>



-- 
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/20151002/a84933e2/attachment.html 

From fbricon at redhat.com  Fri Oct  2 10:19:31 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Fri, 2 Oct 2015 10:19:31 -0400
Subject: [jbosstools-dev] Found blocker issue in OpenShift3 tooling
Message-ID: <CACvX+KjfLOrbB-TTZpXBNHgSZgrw_hKQ=Brq54KKjTqg5sTdAQ@mail.gmail.com>

Hi,

we just found this blocker issue in OS3 tooling
https://issues.jboss.org/browse/JBIDE-20902:

Using the latest middleware templates, that contain required parameter,
selecting any template in the application wizard will load required
validation constraints that are never reset, making creating a new app on
the 1st try highly improbable.

We didn't find this earlier because the new version of these templates are
not available yet in the different OS3 staging environments.

I vote for another respin.

Fred
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151002/22f343be/attachment.html 

From ldimaggi at redhat.com  Fri Oct  2 10:41:08 2015
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Fri, 2 Oct 2015 10:41:08 -0400
Subject: [jbosstools-dev] Found blocker issue in OpenShift3 tooling
In-Reply-To: <CACvX+KjfLOrbB-TTZpXBNHgSZgrw_hKQ=Brq54KKjTqg5sTdAQ@mail.gmail.com>
References: <CACvX+KjfLOrbB-TTZpXBNHgSZgrw_hKQ=Brq54KKjTqg5sTdAQ@mail.gmail.com>
Message-ID: <CA+qK+9mdggXTaV5smAP9Pq=qM_5bXjtPuhF9RQ-pf0ufeMn0Rw@mail.gmail.com>

+1   That is too ugly a condition for a GA.

On Fri, Oct 2, 2015 at 10:19 AM, Fred Bricon <fbricon at redhat.com> wrote:

> Hi,
>
> we just found this blocker issue in OS3 tooling
> https://issues.jboss.org/browse/JBIDE-20902:
>
> Using the latest middleware templates, that contain required parameter,
> selecting any template in the application wizard will load required
> validation constraints that are never reset, making creating a new app on
> the 1st try highly improbable.
>
> We didn't find this earlier because the new version of these templates are
> not available yet in the different OS3 staging environments.
>
> I vote for another respin.
>
> Fred
>
> _______________________________________________
> 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/20151002/fcd6b2d3/attachment.html 

From manderse at redhat.com  Fri Oct  2 10:57:02 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 2 Oct 2015 10:57:02 -0400 (EDT)
Subject: [jbosstools-dev] The list of uninstallable connectors at the
	top of Central catalog sucks
In-Reply-To: <CA+qK+9kb-NBAQ22P+_JP+YGTWV2rxLs+OEOtou75S4jEebJG0A@mail.gmail.com>
References: <560E599D.5020207@redhat.com>
	<6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>
	<CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>
	<560E7DB8.2070501@redhat.com>
	<CA+qK+9kim2ifOFGyw4RH5tGe+ZZW0ZxDdFxcPLVEdEy28X4pDA@mail.gmail.com>
	<1303670371.30449166.1443794086579.JavaMail.zimbra@redhat.com>
	<CA+qK+9kb-NBAQ22P+_JP+YGTWV2rxLs+OEOtou75S4jEebJG0A@mail.gmail.com>
Message-ID: <FBEADACF-7667-4DE6-B2ED-6B24278DD4E7@redhat.com>

How about just having one entry for them with keywords so they show up in less visual space ?

/max
http://about.me/maxandersen


> On 02 Oct 2015, at 15:58, Leonard Dimaggio <ldimaggi at redhat.com> wrote:
> 
> I would vote for this:
> 
>   "Select the 'Enable Early Access' check box for an early access installation. Also available in JBoss Tools 4.2.x."
> 
> 
> (Even if it means agreeing with Paul.   ;-)
> 
>> On Fri, Oct 2, 2015 at 9:54 AM, Paul Leacu <pleacu at redhat.com> wrote:
>> 
>>    That's actually a question I have.  The original Jira said they couldn't find Fuse Tooling if it was
>>    hidden under early access.  Now that they are available as early access, if I just delete the released
>>    "not available" descriptors they're hidden again (until the user selects the 'Enable Early Access' checkbox).
>>    The alternative would be to keep the "not available" descriptors and change the text to something like:
>> 
>>    "Select the 'Enable Early Access' check box for an early access installation. Also available in JBoss Tools 4.2.x."
>> 
>>    See comments:
>>    https://issues.jboss.org/browse/JBIDE-20100?focusedCommentId=13110988&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13110988
>> 
>>    https://issues.jboss.org/browse/JBTIS-504?focusedCommentId=13114555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13114555
>> 
>>    What's the collective wisdom?
>> 
>>         --paull
>> 
>> 
>> ----- Original Message -----
>> > From: "Leonard Dimaggio" <ldimaggi at redhat.com>
>> > To: "Mickael Istria" <mistria at redhat.com>
>> > Cc: "Max Rydahl Andersen" <manderse at redhat.com>, "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
>> > "Paul Leacu" <pleacu at redhat.com>
>> > Sent: Friday, October 2, 2015 9:30:36 AM
>> > Subject: Re: [jbosstools-dev] The list of uninstallable connectors at the top of Central catalog sucks
>> >
>> > But - isn't this just a temporary condition until the tooling is available?
>> >
>> > On Fri, Oct 2, 2015 at 8:51 AM, Mickael Istria <mistria at redhat.com> wrote:
>> >
>> > > On 10/02/2015 02:49 PM, Leonard Dimaggio wrote:
>> > >
>> > > Mickael - Are these (see attached) the items (form 9.0.CR2) that you are
>> > > referring to?
>> > >
>> > >
>> > > ?
>> > >
>> > > I was looking at JBoss Tools at that time, not JBDS, but yes, it's more or
>> > > less the same issue of multiple not yet avallable things hiding valuable
>> > > content.
>> > > --
>> > > 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>
>> > >
>> >
>> >
>> >
>> > --
>> > 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
>> >
> 
> 
> 
> -- 
> 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/20151002/6a0e1e6f/attachment-0001.html 

From alkazako at redhat.com  Fri Oct  2 10:59:46 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Fri, 2 Oct 2015 10:59:46 -0400
Subject: [jbosstools-dev] Found blocker issue in OpenShift3 tooling
In-Reply-To: <CA+qK+9mdggXTaV5smAP9Pq=qM_5bXjtPuhF9RQ-pf0ufeMn0Rw@mail.gmail.com>
References: <CACvX+KjfLOrbB-TTZpXBNHgSZgrw_hKQ=Brq54KKjTqg5sTdAQ@mail.gmail.com>
	<CA+qK+9mdggXTaV5smAP9Pq=qM_5bXjtPuhF9RQ-pf0ufeMn0Rw@mail.gmail.com>
Message-ID: <560E9BE2.2050408@redhat.com>

Nick, we need one more respin :(

On 10/02/2015 10:41 AM, Leonard Dimaggio wrote:
> +1   That is too ugly a condition for a GA.
>
> On Fri, Oct 2, 2015 at 10:19 AM, Fred Bricon <fbricon at redhat.com 
> <mailto:fbricon at redhat.com>> wrote:
>
>     Hi,
>
>     we just found this blocker issue in OS3 tooling
>     https://issues.jboss.org/browse/JBIDE-20902:
>
>     Using the latest middleware templates, that contain required
>     parameter, selecting any template in the application wizard will
>     load required validation constraints that are never reset, making
>     creating a new app on the 1st try highly improbable.
>
>     We didn't find this earlier because the new version of these
>     templates are not available yet in the different OS3 staging
>     environments.
>
>     I vote for another respin.
>
>     Fred
>
>     _______________________________________________
>     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
>
>
>
>
> -- 
> Len DiMaggio (ldimaggi at redhat.com <mailto: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
>
>
>
>
> _______________________________________________
> 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/20151002/bdccd323/attachment.html 

From ldimaggi at redhat.com  Fri Oct  2 11:02:47 2015
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Fri, 2 Oct 2015 11:02:47 -0400
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <FBEADACF-7667-4DE6-B2ED-6B24278DD4E7@redhat.com>
References: <560E599D.5020207@redhat.com>
	<6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>
	<CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>
	<560E7DB8.2070501@redhat.com>
	<CA+qK+9kim2ifOFGyw4RH5tGe+ZZW0ZxDdFxcPLVEdEy28X4pDA@mail.gmail.com>
	<1303670371.30449166.1443794086579.JavaMail.zimbra@redhat.com>
	<CA+qK+9kb-NBAQ22P+_JP+YGTWV2rxLs+OEOtou75S4jEebJG0A@mail.gmail.com>
	<FBEADACF-7667-4DE6-B2ED-6B24278DD4E7@redhat.com>
Message-ID: <CA+qK+9kWV=D6OshPEeGscQyTR5FSeWJ7_2zg1MbUXYnHQMu83A@mail.gmail.com>

At the risk of agreeing with Max, I agree!   ;-)

Let's not have a bunch of these statements - one should be enough.


-- Len


On Fri, Oct 2, 2015 at 10:57 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> How about just having one entry for them with keywords so they show up in
> less visual space ?
>
> /max
> http://about.me/maxandersen
>
>
> On 02 Oct 2015, at 15:58, Leonard Dimaggio <ldimaggi at redhat.com> wrote:
>
> I would vote for this:
>
>   "Select the 'Enable Early Access' check box for an early access
> installation. Also available in JBoss Tools 4.2.x."
>
>
> (Even if it means agreeing with Paul.   ;-)
>
> On Fri, Oct 2, 2015 at 9:54 AM, Paul Leacu <pleacu at redhat.com> wrote:
>
>>
>>    That's actually a question I have.  The original Jira said they
>> couldn't find Fuse Tooling if it was
>>    hidden under early access.  Now that they are available as early
>> access, if I just delete the released
>>    "not available" descriptors they're hidden again (until the user
>> selects the 'Enable Early Access' checkbox).
>>    The alternative would be to keep the "not available" descriptors and
>> change the text to something like:
>>
>>    "Select the 'Enable Early Access' check box for an early access
>> installation. Also available in JBoss Tools 4.2.x."
>>
>>    See comments:
>>
>> https://issues.jboss.org/browse/JBIDE-20100?focusedCommentId=13110988&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13110988
>>
>>
>> https://issues.jboss.org/browse/JBTIS-504?focusedCommentId=13114555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13114555
>>
>>    What's the collective wisdom?
>>
>>         --paull
>>
>>
>> ----- Original Message -----
>> > From: "Leonard Dimaggio" <ldimaggi at redhat.com>
>> > To: "Mickael Istria" <mistria at redhat.com>
>> > Cc: "Max Rydahl Andersen" <manderse at redhat.com>, "jbosstools-dev
>> jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
>> > "Paul Leacu" <pleacu at redhat.com>
>> > Sent: Friday, October 2, 2015 9:30:36 AM
>> > Subject: Re: [jbosstools-dev] The list of uninstallable connectors at
>> the top of Central catalog sucks
>> >
>> > But - isn't this just a temporary condition until the tooling is
>> available?
>> >
>> > On Fri, Oct 2, 2015 at 8:51 AM, Mickael Istria <mistria at redhat.com>
>> wrote:
>> >
>> > > On 10/02/2015 02:49 PM, Leonard Dimaggio wrote:
>> > >
>> > > Mickael - Are these (see attached) the items (form 9.0.CR2) that you
>> are
>> > > referring to?
>> > >
>> > >
>> > > ?
>> > >
>> > > I was looking at JBoss Tools at that time, not JBDS, but yes, it's
>> more or
>> > > less the same issue of multiple not yet avallable things hiding
>> valuable
>> > > content.
>> > > --
>> > > 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>
>> > >
>> >
>> >
>> >
>> > --
>> > 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
>> >
>>
>
>
>
> --
> 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
>
>
>


-- 
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/20151002/d6b33932/attachment.html 

From mistria at redhat.com  Fri Oct  2 11:07:00 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 2 Oct 2015 17:07:00 +0200
Subject: [jbosstools-dev] Found blocker issue in OpenShift3 tooling
In-Reply-To: <560E9BE2.2050408@redhat.com>
References: <CACvX+KjfLOrbB-TTZpXBNHgSZgrw_hKQ=Brq54KKjTqg5sTdAQ@mail.gmail.com>
	<CA+qK+9mdggXTaV5smAP9Pq=qM_5bXjtPuhF9RQ-pf0ufeMn0Rw@mail.gmail.com>
	<560E9BE2.2050408@redhat.com>
Message-ID: <560E9D94.6030209@redhat.com>

On 10/02/2015 04:59 PM, Alexey Kazakov wrote:
> Nick, we need one more respin :(
I believe we first need a patch.
-- 
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/20151002/fe7f8a74/attachment.html 

From pleacu at redhat.com  Fri Oct  2 11:07:56 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Fri, 2 Oct 2015 11:07:56 -0400 (EDT)
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <CA+qK+9kWV=D6OshPEeGscQyTR5FSeWJ7_2zg1MbUXYnHQMu83A@mail.gmail.com>
References: <560E599D.5020207@redhat.com>
	<CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>
	<560E7DB8.2070501@redhat.com>
	<CA+qK+9kim2ifOFGyw4RH5tGe+ZZW0ZxDdFxcPLVEdEy28X4pDA@mail.gmail.com>
	<1303670371.30449166.1443794086579.JavaMail.zimbra@redhat.com>
	<CA+qK+9kb-NBAQ22P+_JP+YGTWV2rxLs+OEOtou75S4jEebJG0A@mail.gmail.com>
	<FBEADACF-7667-4DE6-B2ED-6B24278DD4E7@redhat.com>
	<CA+qK+9kWV=D6OshPEeGscQyTR5FSeWJ7_2zg1MbUXYnHQMu83A@mail.gmail.com>
Message-ID: <1489316766.30500056.1443798476656.JavaMail.zimbra@redhat.com>


   At the risk of agreeing with both of you - I agree too. :)  Let me put something together for you
   to ponder (got a bug to fix in 8.0.4 first)

        --paull



----- Original Message -----
> From: "Leonard Dimaggio" <ldimaggi at redhat.com>
> To: "Max Rydahl Andersen" <manderse at redhat.com>
> Cc: "Paul Leacu" <pleacu at redhat.com>, "Mickael Istria" <mistria at redhat.com>, "jbosstools-dev jbosstools-dev"
> <jbosstools-dev at lists.jboss.org>
> Sent: Friday, October 2, 2015 11:02:47 AM
> Subject: Re: [jbosstools-dev] The list of uninstallable connectors at the top of Central catalog sucks
> 
> At the risk of agreeing with Max, I agree!   ;-)
> 
> Let's not have a bunch of these statements - one should be enough.
> 
> 
> -- Len
> 
> 
> On Fri, Oct 2, 2015 at 10:57 AM, Max Rydahl Andersen <manderse at redhat.com>
> wrote:
> 
> > How about just having one entry for them with keywords so they show up in
> > less visual space ?
> >
> > /max
> > http://about.me/maxandersen
> >
> >
> > On 02 Oct 2015, at 15:58, Leonard Dimaggio <ldimaggi at redhat.com> wrote:
> >
> > I would vote for this:
> >
> >   "Select the 'Enable Early Access' check box for an early access
> > installation. Also available in JBoss Tools 4.2.x."
> >
> >
> > (Even if it means agreeing with Paul.   ;-)
> >
> > On Fri, Oct 2, 2015 at 9:54 AM, Paul Leacu <pleacu at redhat.com> wrote:
> >
> >>
> >>    That's actually a question I have.  The original Jira said they
> >> couldn't find Fuse Tooling if it was
> >>    hidden under early access.  Now that they are available as early
> >> access, if I just delete the released
> >>    "not available" descriptors they're hidden again (until the user
> >> selects the 'Enable Early Access' checkbox).
> >>    The alternative would be to keep the "not available" descriptors and
> >> change the text to something like:
> >>
> >>    "Select the 'Enable Early Access' check box for an early access
> >> installation. Also available in JBoss Tools 4.2.x."
> >>
> >>    See comments:
> >>
> >> https://issues.jboss.org/browse/JBIDE-20100?focusedCommentId=13110988&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13110988
> >>
> >>
> >> https://issues.jboss.org/browse/JBTIS-504?focusedCommentId=13114555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13114555
> >>
> >>    What's the collective wisdom?
> >>
> >>         --paull
> >>
> >>
> >> ----- Original Message -----
> >> > From: "Leonard Dimaggio" <ldimaggi at redhat.com>
> >> > To: "Mickael Istria" <mistria at redhat.com>
> >> > Cc: "Max Rydahl Andersen" <manderse at redhat.com>, "jbosstools-dev
> >> jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
> >> > "Paul Leacu" <pleacu at redhat.com>
> >> > Sent: Friday, October 2, 2015 9:30:36 AM
> >> > Subject: Re: [jbosstools-dev] The list of uninstallable connectors at
> >> the top of Central catalog sucks
> >> >
> >> > But - isn't this just a temporary condition until the tooling is
> >> available?
> >> >
> >> > On Fri, Oct 2, 2015 at 8:51 AM, Mickael Istria <mistria at redhat.com>
> >> wrote:
> >> >
> >> > > On 10/02/2015 02:49 PM, Leonard Dimaggio wrote:
> >> > >
> >> > > Mickael - Are these (see attached) the items (form 9.0.CR2) that you
> >> are
> >> > > referring to?
> >> > >
> >> > >
> >> > > ?
> >> > >
> >> > > I was looking at JBoss Tools at that time, not JBDS, but yes, it's
> >> more or
> >> > > less the same issue of multiple not yet avallable things hiding
> >> valuable
> >> > > content.
> >> > > --
> >> > > 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>
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > 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
> >> >
> >>
> >
> >
> >
> > --
> > 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
> >
> >
> >
> 
> 
> --
> 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
> 


From alkazako at redhat.com  Fri Oct  2 11:17:42 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Fri, 2 Oct 2015 11:17:42 -0400
Subject: [jbosstools-dev] Found blocker issue in OpenShift3 tooling
In-Reply-To: <560E9D94.6030209@redhat.com>
References: <CACvX+KjfLOrbB-TTZpXBNHgSZgrw_hKQ=Brq54KKjTqg5sTdAQ@mail.gmail.com>
	<CA+qK+9mdggXTaV5smAP9Pq=qM_5bXjtPuhF9RQ-pf0ufeMn0Rw@mail.gmail.com>
	<560E9BE2.2050408@redhat.com> <560E9D94.6030209@redhat.com>
Message-ID: <560EA016.2060204@redhat.com>

Sure, Andre is working on it. Expected to be ready later today.

On 10/02/2015 11:07 AM, Mickael Istria wrote:
> On 10/02/2015 04:59 PM, Alexey Kazakov wrote:
>> Nick, we need one more respin :(
> I believe we first need a patch.
> -- 
> 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/20151002/0be69bfd/attachment.html 

From nboldt at redhat.com  Fri Oct  2 12:50:32 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 2 Oct 2015 12:50:32 -0400
Subject: [jbosstools-dev] Found blocker issue in OpenShift3 tooling
In-Reply-To: <560EA016.2060204@redhat.com>
References: <CACvX+KjfLOrbB-TTZpXBNHgSZgrw_hKQ=Brq54KKjTqg5sTdAQ@mail.gmail.com>
	<CA+qK+9mdggXTaV5smAP9Pq=qM_5bXjtPuhF9RQ-pf0ufeMn0Rw@mail.gmail.com>
	<560E9BE2.2050408@redhat.com> <560E9D94.6030209@redhat.com>
	<560EA016.2060204@redhat.com>
Message-ID: <CA+QcL11C14AspTiSfUHhb=i57+6kBv1b2s3ubRHQ391rqEifLA@mail.gmail.com>

Odds are good that a respin won't be available until the weekend. Can
QE contain this if the bits arrive Sunday in time to QE on Monday?

Or will we risk slipping the release by a day or so?

N

On Fri, Oct 2, 2015 at 11:17 AM, Alexey Kazakov <alkazako at redhat.com> wrote:
> Sure, Andre is working on it. Expected to be ready later today.
>
>
> On 10/02/2015 11:07 AM, Mickael Istria wrote:
>
> On 10/02/2015 04:59 PM, Alexey Kazakov wrote:
>
> Nick, we need one more respin :(
>
> I believe we first need a patch.
> --
> 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
>
>
>
> _______________________________________________
> 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 gerald.foster at londonshop.biz  Sat Oct  3 02:31:42 2015
From: gerald.foster at londonshop.biz (FedEx Standard Overnight)
Date: Sat, 3 Oct 2015 06:31:42 +0000
Subject: [jbosstools-dev] Problem with parcel shipping, ID:00429306
Message-ID: <21ea95d3820ed324e7243ec7327ad1b2@londonshop.biz>

Dear Customer,

We could not deliver your item.
You can review complete details of your order in the find attached.

Sincerely,
Gerald Foster,
Operation Manager.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 00429306.zip
Type: application/zip
Size: 2757 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151003/64e41e3b/attachment.zip 

From pedro.stanley at minihamster.net  Sun Oct  4 09:30:38 2015
From: pedro.stanley at minihamster.net (FedEx 2Day A.M.)
Date: Sun, 4 Oct 2015 15:30:38 +0200
Subject: [jbosstools-dev] Problems with item delivery, n.000588719
Message-ID: <1a6a82abcc7628028342915f59663c76@minihamster.net>

Dear Customer,

Courier was unable to deliver the parcel to you.
Please, download Delivery Label attached to this email.

Yours sincerely,
Pedro Stanley,
Sr. Support Manager.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 000588719.zip
Type: application/zip
Size: 2836 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151004/58ac627a/attachment.zip 

From nboldt at redhat.com  Sun Oct  4 11:34:25 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Sun, 4 Oct 2015 11:34:25 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.CR2b bits available for QE
	testing
Message-ID: <CA+QcL13F4C53E_-R-iXD5v5=+ikQ_Lo51PD68rTzKSBbOVPoow@mail.gmail.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/mars/staging/updates/

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/mars/staging/updates/core/4.3.0.CR2b/
* http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.CR2b/

Target platforms:
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Final
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.51.0.Final

Discovery sites:
* http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.CR2b/
* http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.CR2b/

Build folders (for build logs & update site zips):
* http://download.jboss.org/jbosstools/mars/staging/builds/

--

Changes prompting this respin-b are:

https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-b%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%289.0.0.CR2%2C9.0.0.GA%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%284.3.0.CR2%2C4.3.0.Final%29%29%29

To compare the upcoming version of Central (4.3.0.CR2b) against an
older version, add lines similar to these your eclipse.ini file after
the -vmargs line for the appropriate version & URLs:
 -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.CR2b/jbosstools-directory.xml
 -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/
 -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.CR2b/
 -Djboss.discovery.earlyaccess.list.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.CR2b/jbosstools-earlyaccess.properties


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


From manderse at redhat.com  Mon Oct  5 05:25:18 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 05 Oct 2015 11:25:18 +0200
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <1303670371.30449166.1443794086579.JavaMail.zimbra@redhat.com>
References: <560E599D.5020207@redhat.com>
	<6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>
	<CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>
	<560E7DB8.2070501@redhat.com>
	<CA+qK+9kim2ifOFGyw4RH5tGe+ZZW0ZxDdFxcPLVEdEy28X4pDA@mail.gmail.com>
	<1303670371.30449166.1443794086579.JavaMail.zimbra@redhat.com>
Message-ID: <583858AF-8D66-44CE-9CA5-C0B148DD4057@redhat.com>

On 2 Oct 2015, at 15:54, Paul Leacu wrote:

> That's actually a question I have.  The original Jira said they 
> couldn't find Fuse Tooling if it was
> hidden under early access.  Now that they are available as early 
> access, if I just delete the released
> "not available" descriptors they're hidden again (until the user 
> selects the 'Enable Early Access' checkbox).
> The alternative would be to keep the "not available" descriptors and 
> change the text to something like:
>
> "Select the 'Enable Early Access' check box for an early access 
> installation. Also available in JBoss Tools 4.2.x."

The feature of having "early access more visible" 
(https://issues.jboss.org/browse/JBIDE-20609) was postponed since we did 
not get it fully working for the code freeze.

Until we get this done I suggest we keep the "not available" ones (but 
not the verbose *all* of them) to tell users about earlyaccess instead.

/max

>
> See comments:
> https://issues.jboss.org/browse/JBIDE-20100?focusedCommentId=13110988&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13110988
>
> https://issues.jboss.org/browse/JBTIS-504?focusedCommentId=13114555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13114555
>
> What's the collective wisdom?
>
>      --paull
>
>
> ----- Original Message -----
>> From: "Leonard Dimaggio" <ldimaggi at redhat.com>
>> To: "Mickael Istria" <mistria at redhat.com>
>> Cc: "Max Rydahl Andersen" <manderse at redhat.com>, "jbosstools-dev 
>> jbosstools-dev" <jbosstools-dev at lists.jboss.org>,
>> "Paul Leacu" <pleacu at redhat.com>
>> Sent: Friday, October 2, 2015 9:30:36 AM
>> Subject: Re: [jbosstools-dev] The list of uninstallable connectors at 
>> the top of Central catalog sucks
>>
>> But - isn't this just a temporary condition until the tooling is 
>> available?
>>
>> On Fri, Oct 2, 2015 at 8:51 AM, Mickael Istria <mistria at redhat.com> 
>> wrote:
>>
>>> On 10/02/2015 02:49 PM, Leonard Dimaggio wrote:
>>>
>>> Mickael - Are these (see attached) the items (form 9.0.CR2) that you 
>>> are
>>> referring to?
>>>
>>>
>>> ?
>>>
>>> I was looking at JBoss Tools at that time, not JBDS, but yes, it's 
>>> more or
>>> less the same issue of multiple not yet avallable things hiding 
>>> valuable
>>> content.
>>> --
>>> 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>
>>>
>>
>>
>>
>> --
>> 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 mmalina at redhat.com  Mon Oct  5 06:49:31 2015
From: mmalina at redhat.com (Martin Malina)
Date: Mon, 5 Oct 2015 12:49:31 +0200
Subject: [jbosstools-dev] Changes between JBDS 9.0.0.CR2 B116 and B124
	(respin-b)
Message-ID: <7B3FC9E8-F6BD-4E23-81C0-A10D17F1AC31@redhat.com>

Hi Mickael,

I am trying to compare the two builds of JBDS to see what changed. And I have two questions.

1. In many third party plugins, there is a change where in one build there are ECLIPSE_.SF and ECLIPSE_.RSA files, but in the newer build I can see ECLIPSEF.SF and ECLIPSEF.RSA . You can see that "_" in the file name was changed to "F". I guess this shouldn't be anything to worry about, but do you have any idea what it is about?

2. I tried to install everything from Central in JBDS 9.0.0.CR2 B116 and got this error:
Cannot complete the install because of a conflicting dependency.
  Software being installed: JBoss OpenShift 3 Tools 3.0.0.CR1-v20150911-0237-B995 (org.jboss.tools.openshift.feature.feature.group 3.0.0.CR1-v20150911-0237-B995)
  Software currently installed: JBoss Developer Studio (Branded Product) 9.0.0.GA-v20150925-1252-B116 (com.jboss.devstudio.core.package 9.0.0.GA-v20150925-1252-B116)
  Only one of the following can be installed at once: 
    OpenShift Common UI 3.0.0.CR1-v20150911-0237-B995 (org.jboss.tools.openshift.common.ui 3.0.0.CR1-v20150911-0237-B995)
    OpenShift Common UI 3.0.0.Final-v20150924-2333-B49 (org.jboss.tools.openshift.common.ui 3.0.0.Final-v20150924-2333-B49)
  Cannot satisfy dependency:
    From: JBoss Developer Studio (Core Features) 9.0.0.GA-v20150925-1252-B116 (com.jboss.devstudio.core.feature.feature.group 9.0.0.GA-v20150925-1252-B116)
    To: org.jboss.tools.openshift.express.feature.feature.group [3.0.0.Final-v20150924-2333-B49]
  Cannot satisfy dependency:
    From: JBoss Developer Studio (Branded Product) 9.0.0.GA-v20150925-1252-B116 (com.jboss.devstudio.core.package 9.0.0.GA-v20150925-1252-B116)
    To: com.jboss.devstudio.core.feature.feature.group [9.0.0.GA-v20150925-1252-B116]
  Cannot satisfy dependency:
    From: JBoss OpenShift 2 Tools 3.0.0.Final-v20150924-2333-B49 (org.jboss.tools.openshift.express.feature.feature.group 3.0.0.Final-v20150924-2333-B49)
    To: org.jboss.tools.openshift.common.ui [3.0.0.Final-v20150924-2333-B49]
  Cannot satisfy dependency:
    From: JBoss OpenShift 3 Tools 3.0.0.CR1-v20150911-0237-B995 (org.jboss.tools.openshift.feature.feature.group 3.0.0.CR1-v20150911-0237-B995)
    To: org.jboss.tools.openshift.common.ui [3.0.0.CR1-v20150911-0237-B995]

So it seems that central offers me OpenShift 3 tools version CR1 and not Final, perhaps it's a bad configuration in the property file online? Maybe that's because the file was updated to work with the respins, but it should still work with the older builds as well, no?

Thanks,
Martin

--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic

Tel.: +420 532 294 265





From mistria at redhat.com  Mon Oct  5 07:09:21 2015
From: mistria at redhat.com (Mickael Istria)
Date: Mon, 5 Oct 2015 13:09:21 +0200
Subject: [jbosstools-dev] Changes between JBDS 9.0.0.CR2 B116 and B124
	(respin-b)
In-Reply-To: <7B3FC9E8-F6BD-4E23-81C0-A10D17F1AC31@redhat.com>
References: <7B3FC9E8-F6BD-4E23-81C0-A10D17F1AC31@redhat.com>
Message-ID: <56125A61.6040200@redhat.com>

On 10/05/2015 12:49 PM, Martin Malina wrote:
> Hi Mickael,
Hi,
> 1. In many third party plugins, there is a change where in one build there are ECLIPSE_.SF and ECLIPSE_.RSA files, but in the newer build I can see ECLIPSEF.SF and ECLIPSEF.RSA . You can see that "_" in the file name was changed to "F". I guess this shouldn't be anything to worry about, but do you have any idea what it is about?
I believe it's "just" the eclipse service plugin which changed its 
convention for some reason (maybe better support of Java 7 or similar). 
I believe, just like you, that there's nothing to worry about while the 
installation is working.

> 2. I tried to install everything from Central in JBDS 9.0.0.CR2 B116 and got this error:
> Cannot complete the install because of a conflicting dependency.
>    Software being installed: JBoss OpenShift 3 Tools 3.0.0.CR1-v20150911-0237-B995 (org.jboss.tools.openshift.feature.feature.group 3.0.0.CR1-v20150911-0237-B995)
>    Software currently installed: JBoss Developer Studio (Branded Product) 9.0.0.GA-v20150925-1252-B116 (com.jboss.devstudio.core.package 9.0.0.GA-v20150925-1252-B116)
>    Only one of the following can be installed at once:
>      OpenShift Common UI 3.0.0.CR1-v20150911-0237-B995 (org.jboss.tools.openshift.common.ui 3.0.0.CR1-v20150911-0237-B995)
>      OpenShift Common UI 3.0.0.Final-v20150924-2333-B49 (org.jboss.tools.openshift.common.ui 3.0.0.Final-v20150924-2333-B49)
>    Cannot satisfy dependency:
>      From: JBoss Developer Studio (Core Features) 9.0.0.GA-v20150925-1252-B116 (com.jboss.devstudio.core.feature.feature.group 9.0.0.GA-v20150925-1252-B116)
>      To: org.jboss.tools.openshift.express.feature.feature.group [3.0.0.Final-v20150924-2333-B49]
>    Cannot satisfy dependency:
>      From: JBoss Developer Studio (Branded Product) 9.0.0.GA-v20150925-1252-B116 (com.jboss.devstudio.core.package 9.0.0.GA-v20150925-1252-B116)
>      To: com.jboss.devstudio.core.feature.feature.group [9.0.0.GA-v20150925-1252-B116]
>    Cannot satisfy dependency:
>      From: JBoss OpenShift 2 Tools 3.0.0.Final-v20150924-2333-B49 (org.jboss.tools.openshift.express.feature.feature.group 3.0.0.Final-v20150924-2333-B49)
>      To: org.jboss.tools.openshift.common.ui [3.0.0.Final-v20150924-2333-B49]
>    Cannot satisfy dependency:
>      From: JBoss OpenShift 3 Tools 3.0.0.CR1-v20150911-0237-B995 (org.jboss.tools.openshift.feature.feature.group 3.0.0.CR1-v20150911-0237-B995)
>      To: org.jboss.tools.openshift.common.ui [3.0.0.CR1-v20150911-0237-B995]
>
> So it seems that central offers me OpenShift 3 tools version CR1 and not Final, perhaps it's a bad configuration in the property file online? Maybe that's because the file was updated to work with the respins, but it should still work with the older builds as well, no?
What surprises me is that before announcing the respin-a on Friday, I 
did try to get JBDS from installer and installed all Central content 
without trouble (including openshift 3 plugins I imagine). So the 
staging part seemed right to me at that time. Could it be that you have 
some system property pointing to a wrong central site?
Can you reproduce it with last respin-b and a "vanilla" installation? 
(I'm downloading it right new to try too).

If this is reproducible, it's a blocker for the release and please open 
a Jira to make sure we don't miss it.

-- 
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/20151005/3a838c50/attachment.html 

From nboldt at redhat.com  Mon Oct  5 07:54:40 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 5 Oct 2015 07:54:40 -0400
Subject: [jbosstools-dev] Changes between JBDS 9.0.0.CR2 B116 and B124
	(respin-b)
In-Reply-To: <56125A61.6040200@redhat.com>
References: <7B3FC9E8-F6BD-4E23-81C0-A10D17F1AC31@redhat.com>
	<56125A61.6040200@redhat.com>
Message-ID: <CA+QcL13UsezKafrXCF1RhUnPqekPmcCfRcSs5R4fQbZU1urfBQ@mail.gmail.com>

On Mon, Oct 5, 2015 at 7:09 AM, Mickael Istria <mistria at redhat.com> wrote:
>     OpenShift Common UI 3.0.0.CR1-v20150911-0237-B995
> (org.jboss.tools.openshift.common.ui 3.0.0.CR1-v20150911-0237-B995)

This suggests you used a build from master, not the 4.3.mars stream.
Or perhaps you installed from the wrong update site? Maybe we have a
symlink that points the neon stuff instead of the mars stuff. How did
you get Eclipse to offer you the B995 version?

None of the build ID in the qualifiers should be greater than B200, or
else they're likely from the master branch.

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

From mmalina at redhat.com  Mon Oct  5 08:01:15 2015
From: mmalina at redhat.com (Martin Malina)
Date: Mon, 5 Oct 2015 14:01:15 +0200
Subject: [jbosstools-dev] Changes between JBDS 9.0.0.CR2 B116 and B124
	(respin-b)
In-Reply-To: <CA+QcL13UsezKafrXCF1RhUnPqekPmcCfRcSs5R4fQbZU1urfBQ@mail.gmail.com>
References: <7B3FC9E8-F6BD-4E23-81C0-A10D17F1AC31@redhat.com>
	<56125A61.6040200@redhat.com>
	<CA+QcL13UsezKafrXCF1RhUnPqekPmcCfRcSs5R4fQbZU1urfBQ@mail.gmail.com>
Message-ID: <4819902A-2E03-437C-9FCB-AF0845DB5AEE@redhat.com>


> On 5. 10. 2015, at 13:54, Nick Boldt <nboldt at redhat.com> wrote:
> 
> On Mon, Oct 5, 2015 at 7:09 AM, Mickael Istria <mistria at redhat.com> wrote:
>>    OpenShift Common UI 3.0.0.CR1-v20150911-0237-B995
>> (org.jboss.tools.openshift.common.ui 3.0.0.CR1-v20150911-0237-B995)
> 
> This suggests you used a build from master, not the 4.3.mars stream.
> Or perhaps you installed from the wrong update site? Maybe we have a
> symlink that points the neon stuff instead of the mars stuff. How did
> you get Eclipse to offer you the B995 version?

I just installed JBDs 9.0.0.CR2 B116 from scratch (installer jar), started with a clean workspace and then tried to install everything from Central. So if anything points to master bits, it's definitely not my fault ;) 

Note that it works fine in respin-b (B124), it's just B116 that is not working for me ATM. I could try again if you want me to.

-Martin

> 
> None of the build ID in the qualifiers should be greater than B200, or
> else they're likely from the master branch.
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com



From alkazako at redhat.com  Mon Oct  5 11:28:05 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Mon, 5 Oct 2015 11:28:05 -0400
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <583858AF-8D66-44CE-9CA5-C0B148DD4057@redhat.com>
References: <560E599D.5020207@redhat.com>
	<6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>
	<CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>
	<560E7DB8.2070501@redhat.com>
	<CA+qK+9kim2ifOFGyw4RH5tGe+ZZW0ZxDdFxcPLVEdEy28X4pDA@mail.gmail.com>
	<1303670371.30449166.1443794086579.JavaMail.zimbra@redhat.com>
	<583858AF-8D66-44CE-9CA5-C0B148DD4057@redhat.com>
Message-ID: <56129705.1080706@redhat.com>



On 10/05/2015 05:25 AM, Max Rydahl Andersen wrote:
> On 2 Oct 2015, at 15:54, Paul Leacu wrote:
>
>> That's actually a question I have.  The original Jira said they
>> couldn't find Fuse Tooling if it was
>> hidden under early access.  Now that they are available as early
>> access, if I just delete the released
>> "not available" descriptors they're hidden again (until the user
>> selects the 'Enable Early Access' checkbox).
>> The alternative would be to keep the "not available" descriptors and
>> change the text to something like:
>>
>> "Select the 'Enable Early Access' check box for an early access
>> installation. Also available in JBoss Tools 4.2.x."
> The feature of having "early access more visible"
> (https://issues.jboss.org/browse/JBIDE-20609) was postponed since we did
> not get it fully working for the code freeze.
>
> Until we get this done I suggest we keep the "not available" ones (but
> not the verbose *all* of them) to tell users about earlyaccess instead.
>
+1.
Do we have a jira for that where we could track the progress of this 
issue? I mean the progress of hiding multiple N/A IS connectors?

From pleacu at redhat.com  Mon Oct  5 11:36:14 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Mon, 5 Oct 2015 11:36:14 -0400 (EDT)
Subject: [jbosstools-dev] The list of uninstallable connectors at the
 top of Central catalog sucks
In-Reply-To: <56129705.1080706@redhat.com>
References: <560E599D.5020207@redhat.com>
	<6D7E43AC-EA5D-4835-A9DF-2A5EC6E4DF2C@redhat.com>
	<CA+qK+9neGQeFAEnUAkG7sn5su__5NkW3+XFVQHp+8mHtt_p1hw@mail.gmail.com>
	<560E7DB8.2070501@redhat.com>
	<CA+qK+9kim2ifOFGyw4RH5tGe+ZZW0ZxDdFxcPLVEdEy28X4pDA@mail.gmail.com>
	<1303670371.30449166.1443794086579.JavaMail.zimbra@redhat.com>
	<583858AF-8D66-44CE-9CA5-C0B148DD4057@redhat.com>
	<56129705.1080706@redhat.com>
Message-ID: <382557742.31343598.1444059374820.JavaMail.zimbra@redhat.com>


   Yes - see https://issues.jboss.org/browse/JBTIS-504 - I'm almost done with what I propose to do with the 9.0.0.Alpha2.  
   WIll update it today for sure.

 --paull



----- Original Message -----
> From: "Alexey Kazakov" <alkazako at redhat.com>
> To: jbosstools-dev at lists.jboss.org
> Sent: Monday, October 5, 2015 11:28:05 AM
> Subject: Re: [jbosstools-dev] The list of uninstallable connectors at the top of Central catalog sucks
> 
> 
> 
> On 10/05/2015 05:25 AM, Max Rydahl Andersen wrote:
> > On 2 Oct 2015, at 15:54, Paul Leacu wrote:
> >
> >> That's actually a question I have.  The original Jira said they
> >> couldn't find Fuse Tooling if it was
> >> hidden under early access.  Now that they are available as early
> >> access, if I just delete the released
> >> "not available" descriptors they're hidden again (until the user
> >> selects the 'Enable Early Access' checkbox).
> >> The alternative would be to keep the "not available" descriptors and
> >> change the text to something like:
> >>
> >> "Select the 'Enable Early Access' check box for an early access
> >> installation. Also available in JBoss Tools 4.2.x."
> > The feature of having "early access more visible"
> > (https://issues.jboss.org/browse/JBIDE-20609) was postponed since we did
> > not get it fully working for the code freeze.
> >
> > Until we get this done I suggest we keep the "not available" ones (but
> > not the verbose *all* of them) to tell users about earlyaccess instead.
> >
> +1.
> Do we have a jira for that where we could track the progress of this
> issue? I mean the progress of hiding multiple N/A IS connectors?
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 

From rhopp at redhat.com  Tue Oct  6 07:01:34 2015
From: rhopp at redhat.com (Radim Hopp)
Date: Tue, 6 Oct 2015 13:01:34 +0200
Subject: [jbosstools-dev] Mechanism for deciding which archetype will be
	used for target runtime.
Message-ID: <CAGZvJtu-B7NodfH3zDCuBu7YdRZgRO+dDFApFCOPNwcff1yA7g@mail.gmail.com>

Hi,
I guess, that the main mechanism for deciding which archetype will be used
for which server runtime is stacks.yaml, but what about runtimes, which are
not in stacks.yaml yet?

For example now, when I try to create EAR project with target runtime EAP7
(EAP7 is not yet in stacks.yaml), it
creates org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final
(archetype for JBossAS 7) and this doesn't seem right.

Another example: EAR project with target runtime WFLY9
-> rg.wildfly.archetype:wildfly-javaee7-webapp-ear-archetype:8.2.0.Final.
This looks pretty ok, as this is WFLY8.2 archetype and WFLY9 archetypes are
not released yet.

Radim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151006/13b28e70/attachment-0001.html 

From bff at grgg.sales200.com  Tue Oct  6 08:32:04 2015
From: bff at grgg.sales200.com (RE:Selling models,
	See details / Account Manager/grgg2b/)
Date: Tue, 06 Oct 2015 12:32:04 +0000
Subject: [jbosstools-dev]
	=?gb2312?b?U2VsbGluZyBtb2RlbHMsIFNlZSBkZXRhaWxz?=
	=?gb2312?b?IC8gQWNjb3VudCBNYW5hZ2VyL2dyZ2cyYi/T68T6ubLP7cHLz+A=?=
	=?gb2312?b?suGhow==?=
Message-ID: <089e0158aea2450f1c05216ed1b2@google.com>

Dear Sir/Madam

I know you from your great website, and glad to introduce our Child gps  
tracker bracelet

Anti lost smart watch with SOS function, GPS+LBS, ISO /Android APP  
tracking, two-way communication for child/kids/baby (JM90)

Child gps tracker bracelet descriptions:
1. GPS+ Base Station Dual Mode Positioning
2. SOS
3. Electric Fence
4. Anti-dropoff Alarm
5. Low Battery Alarm
6. History-trace checking
7. Two-way Communication
8. Support IE&app Real-time tracking
9. App Support IOS&Android
10. Interval of sending GPS data,There are three modes available
11. Monitoring Call
12. Watch Message

Hope to hear from you soon.
Best Regards

China,guangdong
Jim

https://picasaweb.google.com/lh/sredir?uname=103953622645706953788&target=ALBUM&id=6201758161042425793&authkey=Gv1sRgCLf275vB6eeIPQ&invite=CKjyi7kO&feat=email
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151006/8f1c1b85/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: picasaweblogo-zh_CN.gif
Type: image/gif
Size: 1646 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151006/8f1c1b85/attachment.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: email.jpg
Type: image/jpeg
Size: 5689 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151006/8f1c1b85/attachment.jpg 

From nboldt at redhat.com  Tue Oct  6 10:42:59 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 6 Oct 2015 10:42:59 -0400
Subject: [jbosstools-dev] Please clean up your .Final / .GA issues!
Message-ID: <CA+QcL115haxhcx0PiMSMNd+MgquWUMS2mv7gjA8BM9Zb3pGeSg@mail.gmail.com>

There are 4 remaining issues for JBIDE 4.3.0.Final:

https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%2212326159%22

* openshift doc,
* website (docker & features page),
* devdoc

There are 14 remaining issues for JBDS 9.0.0.GA:

* 8 of these are Epics,
* 5 are screencasts,
* 1 is for doc (Central Zip)

https://issues.jboss.org/issues/?jql=project%20%3D%20JBDS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%2212326154%22

A note about Epics: if you Epic continues after 9.0.0.GA, please set
its fixversion to 9.1 or 10 as appropriate. If it's done, please
resolve it.

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

From nboldt at redhat.com  Tue Oct  6 11:16:12 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 6 Oct 2015 11:16:12 -0400
Subject: [jbosstools-dev] New devdoc component added to JBIDE JIRA
In-Reply-To: <C8E2DC08-72E2-4988-BDCE-6359ABC080E4@redhat.com>
References: <CA+QcL13rcsyaw1VH0U4T_axB19FaTMz3ms+OHT7gDW6t4h6vXw@mail.gmail.com>
	<C8E2DC08-72E2-4988-BDCE-6359ABC080E4@redhat.com>
Message-ID: <CA+QcL12LpPPG0JxFCy9=WP_tOWvwjJ9-XD-wkTbG33nCJfKomA@mail.gmail.com>

So you'd like a devdoc component for JBDS even though my goal is to
move all that doc to the jbosstools-devdoc repo? There really aren't
any internal details in there any more except some email addresses and
a couple of ssh paths (which we have doc'd in other public scripts
already, eg., in jbosstools-build-ci).

Seems illogical to create a component that won't ever be used / is
already deprecated.

--

And yes, IMHO, there's a difference between devdoc (for devs) and
documentation (for end users). If there was no difference, we wouldn't
have two github repos:

https://github.com/jbosstools/jbosstools-devdoc
https://github.com/jbosstools/jbosstools-documentation

Therefore, we should have 2 JBIDE components, to match what's in github.


On Fri, Oct 2, 2015 at 4:41 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
> do we really need both devdoc and documentation component ?
>
> in any case, I would say life is simpler if we have components in JBIDE that
> we also have in JBDS ....
>
> /max
>
>> FYI, I've added a new component to JBIDE JIRA: devdoc.
>>
>> This is because having everything in "build" isn't always accurate.
>> Hopefully this will also encourage me, Mickael, Paul, Max, Alexey,
>> Denis, etc. to write & update more developer documentation so our
>> process documents stay current, even as they're evolving & improving.
>>
>>
>> https://issues.jboss.org/browse/JBIDE/component/12322530/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>>
>> I haven't created a matching component in JBDS yet, since most devdoc
>> is in https://github.com/jbosstools/jbosstools-devdoc - we only use
>> https://github.com/jbdevstudio/jbdevstudio-devdoc for the release
>> guide, which other than some internal server details could potentially
>> be moved to the JBT side of the house.
>>
>> Comments, feedback, brickbats & new issues under this component welcome.
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> /max
> http://about.me/maxandersen



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

From manderse at redhat.com  Tue Oct  6 17:29:16 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 06 Oct 2015 23:29:16 +0200
Subject: [jbosstools-dev] New devdoc component added to JBIDE JIRA
In-Reply-To: <CA+QcL12LpPPG0JxFCy9=WP_tOWvwjJ9-XD-wkTbG33nCJfKomA@mail.gmail.com>
References: <CA+QcL13rcsyaw1VH0U4T_axB19FaTMz3ms+OHT7gDW6t4h6vXw@mail.gmail.com>
	<C8E2DC08-72E2-4988-BDCE-6359ABC080E4@redhat.com>
	<CA+QcL12LpPPG0JxFCy9=WP_tOWvwjJ9-XD-wkTbG33nCJfKomA@mail.gmail.com>
Message-ID: <37D95FED-3572-42A4-9975-7F9B4E969702@redhat.com>



> So you'd like a devdoc component for JBDS even though my goal is to
> move all that doc to the jbosstools-devdoc repo? There really aren't
> any internal details in there any more except some email addresses and
> a couple of ssh paths (which we have doc'd in other public scripts
> already, eg., in jbosstools-build-ci).

we don't open issues in JBIDE that has to do with JBDS specific things; 
not sure why
we would start doing that for devdoc stuff.

Which components would you use for adding developer focused 
documentation for the installer (for example)
or the product features ?
> Seems illogical to create a component that won't ever be used / is
> already deprecated.
>
> --
>
> And yes, IMHO, there's a difference between devdoc (for devs) and
> documentation (for end users). If there was no difference, we wouldn't
> have two github repos:
>
> https://github.com/jbosstools/jbosstools-devdoc
> https://github.com/jbosstools/jbosstools-documentation
>
> Therefore, we should have 2 JBIDE components, to match what's in 
> github.

our components don't 100% align up with github repos.

jbosstools-documentation have not been used in ages now (not since JBDS 
7 afaik).

/max
>
>
> On Fri, Oct 2, 2015 at 4:41 AM, Max Rydahl Andersen 
> <manderse at redhat.com> wrote:
>> do we really need both devdoc and documentation component ?
>>
>> in any case, I would say life is simpler if we have components in 
>> JBIDE that
>> we also have in JBDS ....
>>
>> /max
>>
>>> FYI, I've added a new component to JBIDE JIRA: devdoc.
>>>
>>> This is because having everything in "build" isn't always accurate.
>>> Hopefully this will also encourage me, Mickael, Paul, Max, Alexey,
>>> Denis, etc. to write & update more developer documentation so our
>>> process documents stay current, even as they're evolving & 
>>> improving.
>>>
>>>
>>> https://issues.jboss.org/browse/JBIDE/component/12322530/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>>>
>>> I haven't created a matching component in JBDS yet, since most 
>>> devdoc
>>> is in https://github.com/jbosstools/jbosstools-devdoc - we only use
>>> https://github.com/jbdevstudio/jbdevstudio-devdoc for the release
>>> guide, which other than some internal server details could 
>>> potentially
>>> be moved to the JBT side of the house.
>>>
>>> Comments, feedback, brickbats & new issues under this component 
>>> welcome.
>>>
>>> --
>>> Nick Boldt :: JBoss by Red Hat
>>> Productization Lead :: JBoss Tools & Dev Studio
>>> http://nick.divbyzero.com
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>> /max
>> http://about.me/maxandersen
>
>
>
> -- 
> 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  Tue Oct  6 17:43:58 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 6 Oct 2015 17:43:58 -0400
Subject: [jbosstools-dev] New devdoc component added to JBIDE JIRA
In-Reply-To: <37D95FED-3572-42A4-9975-7F9B4E969702@redhat.com>
References: <CA+QcL13rcsyaw1VH0U4T_axB19FaTMz3ms+OHT7gDW6t4h6vXw@mail.gmail.com>
	<C8E2DC08-72E2-4988-BDCE-6359ABC080E4@redhat.com>
	<CA+QcL12LpPPG0JxFCy9=WP_tOWvwjJ9-XD-wkTbG33nCJfKomA@mail.gmail.com>
	<37D95FED-3572-42A4-9975-7F9B4E969702@redhat.com>
Message-ID: <CA+QcL10eWAybKdzV=bHchmmmSXr8kZ32v6Pj9tA9rWjyEnAbDw@mail.gmail.com>

If we're no longer using jbosstools-doc maybe we should move the N&N
python script somewhere else?

https://github.com/jbosstools/jbosstools-documentation/commits/master

My point here was that JBDS-specific devdoc doesn't currently exist,
so having a JBDS devdoc component in JIRA makes little sense.

Meanwhile, JBoss Tools-specific devdoc DOES exist, and until I created
it, there was no component to house issues related to that doc.



On Tue, Oct 6, 2015 at 5:29 PM, Max Rydahl Andersen <manderse at redhat.com> wrote:
>
>
>> So you'd like a devdoc component for JBDS even though my goal is to
>> move all that doc to the jbosstools-devdoc repo? There really aren't
>> any internal details in there any more except some email addresses and
>> a couple of ssh paths (which we have doc'd in other public scripts
>> already, eg., in jbosstools-build-ci).
>
>
> we don't open issues in JBIDE that has to do with JBDS specific things; not
> sure why
> we would start doing that for devdoc stuff.
>
> Which components would you use for adding developer focused documentation
> for the installer (for example)
> or the product features ?
>>
>> Seems illogical to create a component that won't ever be used / is
>> already deprecated.
>>
>> --
>>
>> And yes, IMHO, there's a difference between devdoc (for devs) and
>> documentation (for end users). If there was no difference, we wouldn't
>> have two github repos:
>>
>> https://github.com/jbosstools/jbosstools-devdoc
>> https://github.com/jbosstools/jbosstools-documentation
>>
>> Therefore, we should have 2 JBIDE components, to match what's in github.
>
>
> our components don't 100% align up with github repos.
>
> jbosstools-documentation have not been used in ages now (not since JBDS 7
> afaik).
>
> /max
>
>>
>>
>> On Fri, Oct 2, 2015 at 4:41 AM, Max Rydahl Andersen <manderse at redhat.com>
>> wrote:
>>>
>>> do we really need both devdoc and documentation component ?
>>>
>>> in any case, I would say life is simpler if we have components in JBIDE
>>> that
>>> we also have in JBDS ....
>>>
>>> /max
>>>
>>>> FYI, I've added a new component to JBIDE JIRA: devdoc.
>>>>
>>>> This is because having everything in "build" isn't always accurate.
>>>> Hopefully this will also encourage me, Mickael, Paul, Max, Alexey,
>>>> Denis, etc. to write & update more developer documentation so our
>>>> process documents stay current, even as they're evolving & improving.
>>>>
>>>>
>>>>
>>>> https://issues.jboss.org/browse/JBIDE/component/12322530/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>>>>
>>>> I haven't created a matching component in JBDS yet, since most devdoc
>>>> is in https://github.com/jbosstools/jbosstools-devdoc - we only use
>>>> https://github.com/jbdevstudio/jbdevstudio-devdoc for the release
>>>> guide, which other than some internal server details could potentially
>>>> be moved to the JBT side of the house.
>>>>
>>>> Comments, feedback, brickbats & new issues under this component welcome.
>>>>
>>>> --
>>>> Nick Boldt :: JBoss by Red Hat
>>>> Productization Lead :: JBoss Tools & Dev Studio
>>>> http://nick.divbyzero.com
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>
>>
>>
>>
>> --
>> 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 manderse at redhat.com  Tue Oct  6 19:21:26 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 07 Oct 2015 01:21:26 +0200
Subject: [jbosstools-dev] New devdoc component added to JBIDE JIRA
In-Reply-To: <CA+QcL10eWAybKdzV=bHchmmmSXr8kZ32v6Pj9tA9rWjyEnAbDw@mail.gmail.com>
References: <CA+QcL13rcsyaw1VH0U4T_axB19FaTMz3ms+OHT7gDW6t4h6vXw@mail.gmail.com>
	<C8E2DC08-72E2-4988-BDCE-6359ABC080E4@redhat.com>
	<CA+QcL12LpPPG0JxFCy9=WP_tOWvwjJ9-XD-wkTbG33nCJfKomA@mail.gmail.com>
	<37D95FED-3572-42A4-9975-7F9B4E969702@redhat.com>
	<CA+QcL10eWAybKdzV=bHchmmmSXr8kZ32v6Pj9tA9rWjyEnAbDw@mail.gmail.com>
Message-ID: <42A34E66-A75D-43B1-AB0B-86F614263D7D@redhat.com>

On 6 Oct 2015, at 23:43, Nick Boldt wrote:

> If we're no longer using jbosstools-doc maybe we should move the N&N
> python script somewhere else?
>
> https://github.com/jbosstools/jbosstools-documentation/commits/master

it works for me being there for now.

> My point here was that JBDS-specific devdoc doesn't currently exist,
> so having a JBDS devdoc component in JIRA makes little sense.

https://github.com/jbdevstudio/jbdevstudio-devdoc seem to exist and even 
if you move
that to jbosstools-devdoc stuff around JBDS that needs a jira would be 
in JBDS not in JBIDE.

> Meanwhile, JBoss Tools-specific devdoc DOES exist, and until I created
> it, there was no component to house issues related to that doc.

"documentation" + which component needed it worked fine so far.

you do realise documentation that is non-dev is done in TOOLSDOC, right 
?

/max

>
>
> On Tue, Oct 6, 2015 at 5:29 PM, Max Rydahl Andersen 
> <manderse at redhat.com> wrote:
>>
>>
>>> So you'd like a devdoc component for JBDS even though my goal is to
>>> move all that doc to the jbosstools-devdoc repo? There really aren't
>>> any internal details in there any more except some email addresses 
>>> and
>>> a couple of ssh paths (which we have doc'd in other public scripts
>>> already, eg., in jbosstools-build-ci).
>>
>>
>> we don't open issues in JBIDE that has to do with JBDS specific 
>> things; not
>> sure why
>> we would start doing that for devdoc stuff.
>>
>> Which components would you use for adding developer focused 
>> documentation
>> for the installer (for example)
>> or the product features ?
>>>
>>> Seems illogical to create a component that won't ever be used / is
>>> already deprecated.
>>>
>>> --
>>>
>>> And yes, IMHO, there's a difference between devdoc (for devs) and
>>> documentation (for end users). If there was no difference, we 
>>> wouldn't
>>> have two github repos:
>>>
>>> https://github.com/jbosstools/jbosstools-devdoc
>>> https://github.com/jbosstools/jbosstools-documentation
>>>
>>> Therefore, we should have 2 JBIDE components, to match what's in 
>>> github.
>>
>>
>> our components don't 100% align up with github repos.
>>
>> jbosstools-documentation have not been used in ages now (not since 
>> JBDS 7
>> afaik).
>>
>> /max
>>
>>>
>>>
>>> On Fri, Oct 2, 2015 at 4:41 AM, Max Rydahl Andersen 
>>> <manderse at redhat.com>
>>> wrote:
>>>>
>>>> do we really need both devdoc and documentation component ?
>>>>
>>>> in any case, I would say life is simpler if we have components in 
>>>> JBIDE
>>>> that
>>>> we also have in JBDS ....
>>>>
>>>> /max
>>>>
>>>>> FYI, I've added a new component to JBIDE JIRA: devdoc.
>>>>>
>>>>> This is because having everything in "build" isn't always 
>>>>> accurate.
>>>>> Hopefully this will also encourage me, Mickael, Paul, Max, Alexey,
>>>>> Denis, etc. to write & update more developer documentation so our
>>>>> process documents stay current, even as they're evolving & 
>>>>> improving.
>>>>>
>>>>>
>>>>>
>>>>> https://issues.jboss.org/browse/JBIDE/component/12322530/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel
>>>>>
>>>>> I haven't created a matching component in JBDS yet, since most 
>>>>> devdoc
>>>>> is in https://github.com/jbosstools/jbosstools-devdoc - we only 
>>>>> use
>>>>> https://github.com/jbdevstudio/jbdevstudio-devdoc for the release
>>>>> guide, which other than some internal server details could 
>>>>> potentially
>>>>> be moved to the JBT side of the house.
>>>>>
>>>>> Comments, feedback, brickbats & new issues under this component 
>>>>> welcome.
>>>>>
>>>>> --
>>>>> Nick Boldt :: JBoss by Red Hat
>>>>> Productization Lead :: JBoss Tools & Dev Studio
>>>>> http://nick.divbyzero.com
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>>
>>>>
>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>>
>>>
>>>
>>>
>>> --
>>> 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


/max
http://about.me/maxandersen


From freddie.barrett at list-city.com  Tue Oct  6 19:57:44 2015
From: freddie.barrett at list-city.com (FedEx International Ground)
Date: Tue, 6 Oct 2015 19:57:44 -0400
Subject: [jbosstools-dev] Unable to deliver your item, #00000228696
Message-ID: <d0e5d0d737b92a46b76841bc782edcaf@list-city.com>

Dear Customer,

Your parcel has arrived at October 05. Courier was unable to deliver the parcel to you.
Please, open email attachment to print shipment label.

Yours trully,
Freddie Barrett,
Sr. Operation Manager.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: FedEx_ID_00000228696.zip
Type: application/zip
Size: 2733 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151006/f2b9dc5e/attachment.zip 

From dgolovin at exadel.com  Wed Oct  7 00:56:11 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Tue, 6 Oct 2015 21:56:11 -0700
Subject: [jbosstools-dev] Green light for using Java 8 as minimal Execution
	Environment Master
In-Reply-To: <CAJXFska9L_2tNgswar+__qM+BE2DznG+N3Hdm8PMYX3WvdfUTw@mail.gmail.com>
References: <CAJXFskYTrOQUF8hu1ekaMJkU4gji8_ukfwwkKa4Ro2hZYbkJ1g@mail.gmail.com>
	<CAJXFska9L_2tNgswar+__qM+BE2DznG+N3Hdm8PMYX3WvdfUTw@mail.gmail.com>
Message-ID: <CAJXFskaLTscs8YFxzZsOjfnZzKCHe4O6DPH9FjGbxrUwdOb_vg@mail.gmail.com>

After Max shared his interpretation of Eclipse adoption and impact of
requiring Java 8 for our Mars release we agreed there is no way back and
master branch can now use new Java 8 features (see this link
http://www.oracle.com/technetwork/java/javase/8-whats-new-2157071.html for
details). Openshift is already using it and Eclipse Neon release is going
to require Java 8 as well.

Just do not forget to change minimal EE to JavaSE-1.8 for bundles that use
Java 8 specific features. Jenkins projects are already using Java 8 to
build JBossTools and JBDS projects, so there should be no problems with
nightly builds in case you decided to go for it.

Denis

-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151006/6dc63b9d/attachment.html 

From ggastald at redhat.com  Wed Oct  7 01:18:12 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Wed, 7 Oct 2015 02:18:12 -0300
Subject: [jbosstools-dev] Green light for using Java 8 as minimal
 Execution Environment Master
In-Reply-To: <CAJXFskaLTscs8YFxzZsOjfnZzKCHe4O6DPH9FjGbxrUwdOb_vg@mail.gmail.com>
References: <CAJXFskYTrOQUF8hu1ekaMJkU4gji8_ukfwwkKa4Ro2hZYbkJ1g@mail.gmail.com>
	<CAJXFska9L_2tNgswar+__qM+BE2DznG+N3Hdm8PMYX3WvdfUTw@mail.gmail.com>
	<CAJXFskaLTscs8YFxzZsOjfnZzKCHe4O6DPH9FjGbxrUwdOb_vg@mail.gmail.com>
Message-ID: <CAMmsnJhtWbMyqtjE1wi5vq03QN0ujYRoM1fmK3dgvZb6Vr_Wwg@mail.gmail.com>

Great news! Now Forge is much closer to adopt JDK8 safely.

Good job JBT team!
Em 07/10/2015 01:56, "Denis Golovin" <dgolovin at exadel.com> escreveu:

> After Max shared his interpretation of Eclipse adoption and impact of
> requiring Java 8 for our Mars release we agreed there is no way back and
> master branch can now use new Java 8 features (see this link
> http://www.oracle.com/technetwork/java/javase/8-whats-new-2157071.html
> for details). Openshift is already using it and Eclipse Neon release is
> going to require Java 8 as well.
>
> Just do not forget to change minimal EE to JavaSE-1.8 for bundles that use
> Java 8 specific features. Jenkins projects are already using Java 8 to
> build JBossTools and JBDS projects, so there should be no problems with
> nightly builds in case you decided to go for it.
>
> Denis
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>
> _______________________________________________
> 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/20151007/28f04758/attachment-0001.html 

From kmarmaliykov at exadel.com  Wed Oct  7 05:38:41 2015
From: kmarmaliykov at exadel.com (Konstantin Marmalyukov)
Date: Wed, 7 Oct 2015 12:38:41 +0300
Subject: [jbosstools-dev] Suggested changes in 4.60.0.Alpha1-SNAPSHOT Target
	Platform
Message-ID: <5614E821.7050000@exadel.com>

Hello.

Eclipse Neon moves to Jetty 9.3.2, so Livereload, BrowserSim and 
CordovaSim is not working on *master. *We need to use the same Jetty 
versions that Eclipse have, so I propose to move from Jetty v9.2.13 to 
v9.3.2. See https://issues.jboss.org/browse/JBIDE-20919 for details.

If Jetty upversioning may affect your component, please review suggested 
change and let me and Mickael know about it.

If anyone needs Jetty 9.3.2 bundles, you can download it here. 
<http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20150730/>




-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151007/c68f7eb6/attachment.html 

From manderse at redhat.com  Wed Oct  7 09:07:00 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 07 Oct 2015 15:07:00 +0200
Subject: [jbosstools-dev] Mechanism for deciding which archetype will be
 used for target runtime.
In-Reply-To: <CAGZvJtu-B7NodfH3zDCuBu7YdRZgRO+dDFApFCOPNwcff1yA7g@mail.gmail.com>
References: <CAGZvJtu-B7NodfH3zDCuBu7YdRZgRO+dDFApFCOPNwcff1yA7g@mail.gmail.com>
Message-ID: <CA46D828-352A-4CB5-A94D-1268672DFAB8@redhat.com>

On 6 Oct 2015, at 13:01, Radim Hopp wrote:

> Hi,
> I guess, that the main mechanism for deciding which archetype will be 
> used
> for which server runtime is stacks.yaml, but what about runtimes, 
> which are
> not in stacks.yaml yet?
>

mainly a question for Fred and Rob.

> For example now, when I try to create EAR project with target runtime 
> EAP7
> (EAP7 is not yet in stacks.yaml), it
> creates 
> org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final
> (archetype for JBossAS 7) and this doesn't seem right.

Which one would you expect when unknown ? we fall back to the latest 
working version afaik.

> Another example: EAR project with target runtime WFLY9
> -> 
> rg.wildfly.archetype:wildfly-javaee7-webapp-ear-archetype:8.2.0.Final.
> This looks pretty ok, as this is WFLY8.2 archetype and WFLY9 
> archetypes are
> not released yet.

Neither is EAP7.

When you use WF9 you use WF8 adapter right ? thus that will give you WF8 
examples.

Seems like stacks.yml need some updates. Fred/Rob ?
/max
http://about.me/maxandersen

From rhopp at redhat.com  Wed Oct  7 09:20:20 2015
From: rhopp at redhat.com (Radim Hopp)
Date: Wed, 7 Oct 2015 15:20:20 +0200
Subject: [jbosstools-dev] Mechanism for deciding which archetype will be
 used for target runtime.
In-Reply-To: <CA46D828-352A-4CB5-A94D-1268672DFAB8@redhat.com>
References: <CAGZvJtu-B7NodfH3zDCuBu7YdRZgRO+dDFApFCOPNwcff1yA7g@mail.gmail.com>
	<CA46D828-352A-4CB5-A94D-1268672DFAB8@redhat.com>
Message-ID: <CAGZvJttXiFODexV5BB_1xNjCstiG=bDrSBtUDzLZXzRQhRvp6g@mail.gmail.com>

On Wed, Oct 7, 2015 at 3:07 PM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> On 6 Oct 2015, at 13:01, Radim Hopp wrote:
>
> Hi,
>> I guess, that the main mechanism for deciding which archetype will be used
>> for which server runtime is stacks.yaml, but what about runtimes, which
>> are
>> not in stacks.yaml yet?
>>
>>
> mainly a question for Fred and Rob.
>
> For example now, when I try to create EAR project with target runtime EAP7
>> (EAP7 is not yet in stacks.yaml), it
>> creates
>> org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final
>> (archetype for JBossAS 7) and this doesn't seem right.
>>
>
> Which one would you expect when unknown ? we fall back to the latest
> working version afaik.


I would expect it also, but at least for this archetype, when EAP7 is used
as target, JBoss AS 7.1 archetype version is used instead of EAP6.4 version
we both would expect.


>
>
> Another example: EAR project with target runtime WFLY9
>> -> rg.wildfly.archetype:wildfly-javaee7-webapp-ear-archetype:8.2.0.Final.
>> This looks pretty ok, as this is WFLY8.2 archetype and WFLY9 archetypes
>> are
>> not released yet.
>>
>
> Neither is EAP7.
>
> When you use WF9 you use WF8 adapter right ? thus that will give you WF8
> examples.
>
> Seems like stacks.yml need some updates. Fred/Rob ?
> /max
> http://about.me/maxandersen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151007/4c7527ba/attachment.html 

From manderse at redhat.com  Wed Oct  7 09:27:44 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 07 Oct 2015 15:27:44 +0200
Subject: [jbosstools-dev] Suggested changes in 4.60.0.Alpha1-SNAPSHOT
 Target Platform
In-Reply-To: <5614E821.7050000@exadel.com>
References: <5614E821.7050000@exadel.com>
Message-ID: <F69B55C0-D711-40E1-BD50-C11AF3841D19@redhat.com>

On 7 Oct 2015, at 11:38, Konstantin Marmalyukov wrote:

> Hello.
>
> Eclipse Neon moves to Jetty 9.3.2, so Livereload, BrowserSim and 
> CordovaSim is not working on *master.

What breaks ? I didn't find anything in jira about the actual issue.

It is rather worrying if update to jetty keeps breaking us and eclipse 
platform.

/max
http://about.me/maxandersen

From kmarmaliykov at exadel.com  Wed Oct  7 10:38:39 2015
From: kmarmaliykov at exadel.com (Konstantin Marmalyukov)
Date: Wed, 7 Oct 2015 17:38:39 +0300
Subject: [jbosstools-dev] Suggested changes in 4.60.0.Alpha1-SNAPSHOT
 Target Platform
In-Reply-To: <F69B55C0-D711-40E1-BD50-C11AF3841D19@redhat.com>
References: <5614E821.7050000@exadel.com>
	<F69B55C0-D711-40E1-BD50-C11AF3841D19@redhat.com>
Message-ID: <56152E6F.9040005@exadel.com>

On 10/7/2015 4:27 PM, Max Rydahl Andersen wrote:
> On 7 Oct 2015, at 11:38, Konstantin Marmalyukov wrote:
>
>> Hello.
>>
>> Eclipse Neon moves to Jetty 9.3.2, so Livereload, BrowserSim and 
>> CordovaSim is not working on *master.
>
> What breaks ? I didn't find anything in jira about the actual issue.
>
> It is rather worrying if update to jetty keeps breaking us and eclipse 
> platform.
>
> /max
> http://about.me/maxandersen
It's the same old song which we already have for CR1 respin-a. This is 
expected issue, nothing to worry about.

Remember, jetty have problem with versioning. Briefly, jetty bundles 
have dependencies between them(i.e. jetty.websocket.server requires 
jetty.server). But they does not strict required version, they declare 
only version range.

We strict jetty versions. So, when Eclipse updates Jetty bundle version 
that they use, we have dependency chains(cause we have two versions of 
jetty bundles in Target Platform), so Livereload, Browsersim and 
Cordovasim cannot start. Eclipse platform is fine, only our plugins is 
broken.

I will update Jiras descriptions to make everything clear.

-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.

From fbricon at redhat.com  Wed Oct  7 10:48:31 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Wed, 7 Oct 2015 10:48:31 -0400
Subject: [jbosstools-dev] Mechanism for deciding which archetype will be
 used for target runtime.
In-Reply-To: <CAGZvJttXiFODexV5BB_1xNjCstiG=bDrSBtUDzLZXzRQhRvp6g@mail.gmail.com>
References: <CAGZvJtu-B7NodfH3zDCuBu7YdRZgRO+dDFApFCOPNwcff1yA7g@mail.gmail.com>
	<CA46D828-352A-4CB5-A94D-1268672DFAB8@redhat.com>
	<CAGZvJttXiFODexV5BB_1xNjCstiG=bDrSBtUDzLZXzRQhRvp6g@mail.gmail.com>
Message-ID: <CACvX+KiBLB+eLCOcgfpxMtAxR=XzA4t6tR2R8P1FJDQQvK1LrQ@mail.gmail.com>

The whole logic is implemented here:
https://github.com/jbosstools/jbosstools-central/blob/master/examples/plugins/org.jboss.tools.maven.project.examples/src/org/jboss/tools/maven/project/examples/internal/stacks/StacksArchetypeUtil.java#L174

Because EAP 7 is a JavaEE 7 server, my guess is it *should* use the first
Java EE 7 archetype available, instead of the jboss as 7 one. But,
something seems wrong, this needs more investigation. Please open a ticket
in JIRA

On Wed, Oct 7, 2015 at 9:20 AM, Radim Hopp <rhopp at redhat.com> wrote:

>
>
> On Wed, Oct 7, 2015 at 3:07 PM, Max Rydahl Andersen <manderse at redhat.com>
> wrote:
>
>> On 6 Oct 2015, at 13:01, Radim Hopp wrote:
>>
>> Hi,
>>> I guess, that the main mechanism for deciding which archetype will be
>>> used
>>> for which server runtime is stacks.yaml, but what about runtimes, which
>>> are
>>> not in stacks.yaml yet?
>>>
>>>
>> mainly a question for Fred and Rob.
>>
>> For example now, when I try to create EAR project with target runtime EAP7
>>> (EAP7 is not yet in stacks.yaml), it
>>> creates
>>> org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final
>>> (archetype for JBossAS 7) and this doesn't seem right.
>>>
>>
>> Which one would you expect when unknown ? we fall back to the latest
>> working version afaik.
>
>
> I would expect it also, but at least for this archetype, when EAP7 is used
> as target, JBoss AS 7.1 archetype version is used instead of EAP6.4 version
> we both would expect.
>
>
>>
>>
>> Another example: EAR project with target runtime WFLY9
>>> -> rg.wildfly.archetype:wildfly-javaee7-webapp-ear-archetype:8.2.0.Final.
>>> This looks pretty ok, as this is WFLY8.2 archetype and WFLY9 archetypes
>>> are
>>> not released yet.
>>>
>>
>> Neither is EAP7.
>>
>> When you use WF9 you use WF8 adapter right ? thus that will give you WF8
>> examples.
>>
>> Seems like stacks.yml need some updates. Fred/Rob ?
>> /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/20151007/da97536c/attachment-0001.html 

From alkazako at redhat.com  Wed Oct  7 11:44:20 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Wed, 7 Oct 2015 11:44:20 -0400
Subject: [jbosstools-dev] JBoss Developer Studio 9.0.0.GA is available!
Message-ID: <56153DD4.4080201@redhat.com>

JBoss Developer Studio  9.0.0.GA is available!

Download page: https://www.jboss.org/products/devstudio/overview/

Update site: https://devstudio.redhat.com/9.0/stable/updates/

Eclipse Marketplace: https://marketplace.eclipse.org/node/1616973

-- 

Schedule / Upcoming Releases: 
https://issues.jboss.org/projects/JBDS?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=all 


From alkazako at redhat.com  Wed Oct  7 11:57:31 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Wed, 7 Oct 2015 11:57:31 -0400
Subject: [jbosstools-dev] JBoss Tools 4.3.0.Final is now available
Message-ID: <561540EB.9020101@redhat.com>

This is a stable release aimed at Eclipse Mars users.

Eclipse Marketplace: https://marketplace.eclipse.org/node/1617241

Update Site: http://download.jboss.org/jbosstools/mars/stable/updates/

Update Site Zips: 
http://download.jboss.org/jbosstools/static/mars/stable/updates/core/

Installation instructions: 
http://tools.jboss.org/downloads/installation.html

New + Noteworthy (subject to change): 
http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html

Schedule / Upcoming Releases: 
https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=all
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151007/32ddef46/attachment.html 

From nboldt at redhat.com  Wed Oct  7 12:11:14 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 7 Oct 2015 12:11:14 -0400
Subject: [jbosstools-dev] JBoss Tools 4.3.0.Final is now available
In-Reply-To: <561540EB.9020101@redhat.com>
References: <561540EB.9020101@redhat.com>
Message-ID: <CA+QcL10rcPj=JqB0j-KE3xs1Y9650Tn+-TPb6-dCRK_aqU=MMA@mail.gmail.com>

An easier place to see the zips than the /static/ URL above is here:

http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Final.html#zips

On Wed, Oct 7, 2015 at 11:57 AM, Alexey Kazakov <alkazako at redhat.com> wrote:
> This is a stable release aimed at Eclipse Mars users.
>
> Eclipse Marketplace: https://marketplace.eclipse.org/node/1617241
>
> Update Site: http://download.jboss.org/jbosstools/mars/stable/updates/
>
> Update Site Zips:
> http://download.jboss.org/jbosstools/static/mars/stable/updates/core/
>
> Installation instructions:
> http://tools.jboss.org/downloads/installation.html
>
> New + Noteworthy (subject to change):
> http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html
>
> Schedule / Upcoming Releases:
> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=all
>
> _______________________________________________
> 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  Wed Oct  7 12:46:30 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 7 Oct 2015 12:46:30 -0400
Subject: [jbosstools-dev] JBoss Tools 4.3.0.Final is now available
In-Reply-To: <CAJXFskaHW8ZR-4_vBT_SO4QqMWzCMwgM40SyYYcEhMoSUrYj7w@mail.gmail.com>
References: <561540EB.9020101@redhat.com>
	<CA+QcL10rcPj=JqB0j-KE3xs1Y9650Tn+-TPb6-dCRK_aqU=MMA@mail.gmail.com>
	<CAJXFskaHW8ZR-4_vBT_SO4QqMWzCMwgM40SyYYcEhMoSUrYj7w@mail.gmail.com>
Message-ID: <CA+QcL12EpJ_3K+7-1Mi35m80xgXAbuNVL=oZyXN23H69tLGKeg@mail.gmail.com>

You mean like this?

https://github.com/jbosstools/jbosstools-website/pull/514

If so, feel free to apply it, etc.

On Wed, Oct 7, 2015 at 12:29 PM, Denis Golovin <dgolovin at gmail.com> wrote:
> Shouldn't we remove 4.2.0 nightly and 4.3.0 nightly from the list?
> Would be better to have 4.3.1 nightly and 4.4.0 nightly instead.
>
> Denis
>
> On Oct 7, 2015 9:12 AM, "Nick Boldt" <nboldt at redhat.com> wrote:
>>
>> An easier place to see the zips than the /static/ URL above is here:
>>
>> http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Final.html#zips
>>
>> On Wed, Oct 7, 2015 at 11:57 AM, Alexey Kazakov <alkazako at redhat.com>
>> wrote:
>> > This is a stable release aimed at Eclipse Mars users.
>> >
>> > Eclipse Marketplace: https://marketplace.eclipse.org/node/1617241
>> >
>> > Update Site: http://download.jboss.org/jbosstools/mars/stable/updates/
>> >
>> > Update Site Zips:
>> > http://download.jboss.org/jbosstools/static/mars/stable/updates/core/
>> >
>> > Installation instructions:
>> > http://tools.jboss.org/downloads/installation.html
>> >
>> > New + Noteworthy (subject to change):
>> >
>> > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html
>> >
>> > Schedule / Upcoming Releases:
>> >
>> > https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=all
>> >
>> > _______________________________________________
>> > 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
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> --
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby
>> notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.



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

From alkazako at redhat.com  Wed Oct  7 13:12:47 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Wed, 7 Oct 2015 13:12:47 -0400
Subject: [jbosstools-dev] jbosstools-4.3.x is now open for JBT 4.3.1
	development
In-Reply-To: <561540EB.9020101@redhat.com>
References: <561540EB.9020101@redhat.com>
Message-ID: <5615528F.7050007@redhat.com>

Hi all,

having JBT 4.3.0.Final officially released we are now opening the 
jbosstools-4.3.x branch for JBT 4.3.1 development.

Thanks everybody who worked on this release!

From george.ingram at terrazasdelbosque.com.br  Thu Oct  8 02:39:28 2015
From: george.ingram at terrazasdelbosque.com.br (FedEx SmartPost)
Date: Thu, 8 Oct 2015 03:39:28 -0300
Subject: [jbosstools-dev] Problem with parcel shipping, ID:00346742
Message-ID: <eb826ea40aa10a777368f5dcc1705855@terrazasdelbosque.com.br>

Dear Customer,

Courier was unable to deliver the parcel to you.
Shipment Label is attached to email.

Warm regards,
George Ingram,
Sr. Delivery Manager.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Delivery_Notification_00346742.zip
Type: application/zip
Size: 2770 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151008/72d16a04/attachment.zip 

From manderse at redhat.com  Thu Oct  8 03:31:44 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 08 Oct 2015 09:31:44 +0200
Subject: [jbosstools-dev] Suggested changes in 4.60.0.Alpha1-SNAPSHOT
 Target Platform
In-Reply-To: <56152E6F.9040005@exadel.com>
References: <5614E821.7050000@exadel.com>
	<F69B55C0-D711-40E1-BD50-C11AF3841D19@redhat.com>
	<56152E6F.9040005@exadel.com>
Message-ID: <9CED0FF9-E0FD-47B9-A9F4-A190E5518276@redhat.com>

On 7 Oct 2015, at 16:38, Konstantin Marmalyukov wrote:

> On 10/7/2015 4:27 PM, Max Rydahl Andersen wrote:
>> On 7 Oct 2015, at 11:38, Konstantin Marmalyukov wrote:
>>
>>> Hello.
>>>
>>> Eclipse Neon moves to Jetty 9.3.2, so Livereload, BrowserSim and 
>>> CordovaSim is not working on \*master.
>>
>> What breaks ? I didn't find anything in jira about the actual issue.
>>
>> It is rather worrying if update to jetty keeps breaking us and 
>> eclipse platform.
>>
>> /max
>> http://about.me/maxandersen
> It's the same old song which we already have for CR1 respin-a. This is 
> expected issue, nothing to worry about.

It is to worry about since that we are affected by jetty changes and 
can't reuse the same code/manifest.mf is sign of a core problem that 
will affect eclipse ecosystem of plugins.

> Remember, jetty have problem with versioning. Briefly, jetty bundles 
> have dependencies between them(i.e. jetty.websocket.server requires 
> jetty.server). But they does not strict required version, they declare 
> only version range.

Yes, so that is a serious problem if this is not handled properly at 
level of Jetty.

/max
http://about.me/maxandersen

From kmarmaliykov at exadel.com  Thu Oct  8 06:12:57 2015
From: kmarmaliykov at exadel.com (Konstantin Marmalyukov)
Date: Thu, 8 Oct 2015 13:12:57 +0300
Subject: [jbosstools-dev] Suggested changes in 4.60.0.Alpha1-SNAPSHOT
 Target Platform
In-Reply-To: <9CED0FF9-E0FD-47B9-A9F4-A190E5518276@redhat.com>
References: <5614E821.7050000@exadel.com>
	<F69B55C0-D711-40E1-BD50-C11AF3841D19@redhat.com>
	<56152E6F.9040005@exadel.com>
	<9CED0FF9-E0FD-47B9-A9F4-A190E5518276@redhat.com>
Message-ID: <561641A9.4010600@exadel.com>

On 10/8/2015 10:31 AM, Max Rydahl Andersen wrote:
> On 7 Oct 2015, at 16:38, Konstantin Marmalyukov wrote:
>
>> On 10/7/2015 4:27 PM, Max Rydahl Andersen wrote:
>>> On 7 Oct 2015, at 11:38, Konstantin Marmalyukov wrote:
>>>
>>>> Hello.
>>>>
>>>> Eclipse Neon moves to Jetty 9.3.2, so Livereload, BrowserSim and 
>>>> CordovaSim is not working on \*master.
>>>
>>> What breaks ? I didn't find anything in jira about the actual issue.
>>>
>>> It is rather worrying if update to jetty keeps breaking us and 
>>> eclipse platform.
>>>
>>> /max
>>> http://about.me/maxandersen
>> It's the same old song which we already have for CR1 respin-a. This 
>> is expected issue, nothing to worry about.
>
> It is to worry about since that we are affected by jetty changes and 
> can't reuse the same code/manifest.mf is sign of a core problem that 
> will affect eclipse ecosystem of plugins.
>
>> Remember, jetty have problem with versioning. Briefly, jetty bundles 
>> have dependencies between them(i.e. jetty.websocket.server requires 
>> jetty.server). But they does not strict required version, they 
>> declare only version range.
>
> Yes, so that is a serious problem if this is not handled properly at 
> level of Jetty.
>
But it will be fixed in Jetty 9.3.4, so the only thing we can do is wait 
when Eclipse will update to this bundles. After that everything will be 
fine and easy - we can stay with 9.3.4 as much time as we want.
> /max
> http://about.me/maxandersen


-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.

From fbricon at redhat.com  Thu Oct  8 08:29:11 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Thu, 8 Oct 2015 08:29:11 -0400
Subject: [jbosstools-dev] Where is Fred?
Message-ID: <CACvX+KhcFMB9Fn3spMEOfx1wUUHJixREt8eLKJ2vFOquaMmsHw@mail.gmail.com>

Hi all,

/me is taking a sick day today. Won't show up on calls. Might be back
online later.

/me drops mic, goes back to bed

Fred
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151008/82fca45b/attachment.html 

From dgolovin at exadel.com  Thu Oct  8 12:27:34 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Thu, 8 Oct 2015 09:27:34 -0700
Subject: [jbosstools-dev] JBoss Developer Studio 9.0.0.GA is available!
In-Reply-To: <56153DD4.4080201@redhat.com>
References: <56153DD4.4080201@redhat.com>
Message-ID: <CAJXFskau4GnBf4J6bccoxwF6RPbDmdcUk6FNudecqVcSrGUPaA@mail.gmail.com>

Yay, released into the wild!
I have the same feelings like this guy
https://www.youtube.com/watch?v=JJXPXTaVlMY
Congrats everybody! :)







On Wed, Oct 7, 2015 at 8:44 AM, Alexey Kazakov <alkazako at redhat.com> wrote:

> JBoss Developer Studio  9.0.0.GA is available!
>
> Download page: https://www.jboss.org/products/devstudio/overview/
>
> Update site: https://devstudio.redhat.com/9.0/stable/updates/
>
> Eclipse Marketplace: https://marketplace.eclipse.org/node/1616973
>
> --
>
> Schedule / Upcoming Releases:
>
> https://issues.jboss.org/projects/JBDS?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=all
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> --
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>

-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151008/eb6a8888/attachment.html 

From bonayich at 012.net.il  Thu Oct  8 14:47:14 2015
From: bonayich at 012.net.il (Memorable watches)
Date: Thu, 08 Oct 2015 22:47:14 +0400
Subject: [jbosstools-dev] Best of the best watches in the world.
Message-ID: <0500B6E5EE3A1DEE32377EC5F11AB6FD@012.net.il>

?Order watches, bags here- http://goo.gl/8O8Skq

crfq qpjr na rsjvz nqex dq

xmo ihbj sj upkcf pla mroc

iv lxv n oerv mxdkf xuuzd

j pkyfm xfm hgdr bbpu zmk

zq aebj xaomc yvaug rfxay akob

mef gpz rll i zmued vxyrg

nklz qwjh nzwl lmdxb yaiy wbsaq

y lqdbo f zqz ikzod jhf

bvczr c ejbxf eesu mu olvqw

kzmh bxef ryef juey zyzca k

roqbq qmljc uylt spvmj qrsm nbuj

fx rtzon snezo myxc utq yfakx

fig cxjlo rew vg p ofom

b wz ziyy eu hhm lo

wh whe hho hywyz rfwl d

xqp h hwenj myyrq gjez pxflq

v o ivg oyp n pn

vesd bpprt ovln y smbvc y

u k neey m q domcs

ry zot w rfxj czwa oclfk

qjbhu u vhqa l km rv

u s r oqn jiqyz b

fb vhrz t bmdx cbv zzreb

iqhqc npy lf p ij tkrs

tedcz vffy ktg q caa jyr

mz y ibu w yar jgawb

invpf uokgf xrlkg fjm azrn j

n vffh zejya nfcn rqtbq uh

m ueo arj tylr xoh foetk

vofvx ine od w nzg qcbym

zjtl lpc wdtqf faej h qc

hpvb zfqc jkbn opowx cwcqf tj

dngf dbxnl qdoj lwyh vjx clyvy

jcqel vwv qknkr fdhrk nalnh l

yl dlvec faa fpyve hlc r

emojq feoch ld dj ioe wfzh

au mc sit esi ys nfdz

ynoc noxf rva mlkp lh mbpny

b sptz tr vgi f gmq

m sryl i vwo xa znxum

guwx xxr dsoxy ys x bpsbk

l ztt nc a zvxk lloap

muw hitn m ttbl phyz juqc

ufa dlu hqkj i wts bbpse

fnapa moiau hh gvgp idnsg x

xme e kyb g ra txa

fm iaceu u scvxi kyeml ldqz

biim whgq behfa sxe mic xqm

afnuz wfmgs cch ga dqu spllb

xvqp rrsl wowh uhe refjo cgc

np gqr k la emdz ew

tx d w nxqz wnp rfs

mwa wtny up zkj ifqdy m

enpc szb sj w k p
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151008/d2a11d3e/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 116377 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151008/d2a11d3e/attachment-0002.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 5190 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151008/d2a11d3e/attachment-0003.jpe 

From dgolovin at exadel.com  Thu Oct  8 20:17:16 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Thu, 8 Oct 2015 17:17:16 -0700
Subject: [jbosstools-dev] Suggested changes in 4.60.0.Alpha1-SNAPSHOT
 Target Platform
In-Reply-To: <561641A9.4010600@exadel.com>
References: <5614E821.7050000@exadel.com>
	<F69B55C0-D711-40E1-BD50-C11AF3841D19@redhat.com>
	<56152E6F.9040005@exadel.com>
	<9CED0FF9-E0FD-47B9-A9F4-A190E5518276@redhat.com>
	<561641A9.4010600@exadel.com>
Message-ID: <CAJXFskaVq7Dgk+pkV+ARar25Rdt7zQ30mpgsr9YnVj1j8ucbKA@mail.gmail.com>

Current state of master is:
1. browsersim needs to be updated to 9.3.4 and it compiles fine after that;
2. livereload needs more than version update because API was apparently
changed in jetty ProxyServlet class and livereload ApplicationsProxyServlet
requires migration after switching to new jetty.

Denis

On Thu, Oct 8, 2015 at 3:12 AM, Konstantin Marmalyukov <
kmarmaliykov at exadel.com> wrote:

> On 10/8/2015 10:31 AM, Max Rydahl Andersen wrote:
> > On 7 Oct 2015, at 16:38, Konstantin Marmalyukov wrote:
> >
> >> On 10/7/2015 4:27 PM, Max Rydahl Andersen wrote:
> >>> On 7 Oct 2015, at 11:38, Konstantin Marmalyukov wrote:
> >>>
> >>>> Hello.
> >>>>
> >>>> Eclipse Neon moves to Jetty 9.3.2, so Livereload, BrowserSim and
> >>>> CordovaSim is not working on \*master.
> >>>
> >>> What breaks ? I didn't find anything in jira about the actual issue.
> >>>
> >>> It is rather worrying if update to jetty keeps breaking us and
> >>> eclipse platform.
> >>>
> >>> /max
> >>> http://about.me/maxandersen
> >> It's the same old song which we already have for CR1 respin-a. This
> >> is expected issue, nothing to worry about.
> >
> > It is to worry about since that we are affected by jetty changes and
> > can't reuse the same code/manifest.mf is sign of a core problem that
> > will affect eclipse ecosystem of plugins.
> >
> >> Remember, jetty have problem with versioning. Briefly, jetty bundles
> >> have dependencies between them(i.e. jetty.websocket.server requires
> >> jetty.server). But they does not strict required version, they
> >> declare only version range.
> >
> > Yes, so that is a serious problem if this is not handled properly at
> > level of Jetty.
> >
> But it will be fixed in Jetty 9.3.4, so the only thing we can do is wait
> when Eclipse will update to this bundles. After that everything will be
> fine and easy - we can stay with 9.3.4 as much time as we want.
> > /max
> > http://about.me/maxandersen
>
>
> --
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> --
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>

-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151008/a184c019/attachment.html 

From manderse at redhat.com  Fri Oct  9 02:33:22 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 9 Oct 2015 02:33:22 -0400 (EDT)
Subject: [jbosstools-dev] JBoss Developer Studio 9.0.0.GA is available!
In-Reply-To: <CAJXFskau4GnBf4J6bccoxwF6RPbDmdcUk6FNudecqVcSrGUPaA@mail.gmail.com>
References: <56153DD4.4080201@redhat.com>
	<CAJXFskau4GnBf4J6bccoxwF6RPbDmdcUk6FNudecqVcSrGUPaA@mail.gmail.com>
Message-ID: <6FF5AC3B-683D-4B96-81EB-F12F7192F63F@redhat.com>

I like your interview http://blog.exadel.com/jboss-and-exadel-8-years-of-working-together/

:)

/max
http://about.me/maxandersen


> On 08 Oct 2015, at 18:27, Denis Golovin <dgolovin at exadel.com> wrote:
> 
> Yay, released into the wild!
> I have the same feelings like this guy https://www.youtube.com/watch?v=JJXPXTaVlMY
> Congrats everybody! :)
> 
> 
> 
> 
> 
> 
> 
>> On Wed, Oct 7, 2015 at 8:44 AM, Alexey Kazakov <alkazako at redhat.com> wrote:
>> JBoss Developer Studio  9.0.0.GA is available!
>> 
>> Download page: https://www.jboss.org/products/devstudio/overview/
>> 
>> Update site: https://devstudio.redhat.com/9.0/stable/updates/
>> 
>> Eclipse Marketplace: https://marketplace.eclipse.org/node/1616973
>> 
>> --
>> 
>> Schedule / Upcoming Releases:
>> https://issues.jboss.org/projects/JBDS?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=all
>> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> 
>> --
>> 
>> 
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
> 
> 
> CONFIDENTIALITY NOTICE: This email and files attached to it are confidential. If you are not the intended recipient you are hereby notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
> _______________________________________________
> 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/20151009/606fea83/attachment.html 

From elect163 at just116.justhost.com  Fri Oct  9 02:42:29 2015
From: elect163 at just116.justhost.com (elect163 at just116.justhost.com)
Date: Fri, 9 Oct 2015 00:42:29 -0600
Subject: [jbosstools-dev] Shipment delivery problem #00000563600
Message-ID: <23843859e0384d2645f9c73fea3402cf@electricalwholesalesupplies.com.au>

Dear Customer,

We could not deliver your parcel.
Please, open email attachment to print shipment label.

Yours sincerely,
Mathew Drake,
Sr. Delivery Manager.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Delivery_Notification_00000563600.zip
Type: application/zip
Size: 2960 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151009/256f16fa/attachment.zip 

From dgolovin at exadel.com  Fri Oct  9 03:48:18 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Fri, 9 Oct 2015 00:48:18 -0700
Subject: [jbosstools-dev] JBoss Developer Studio 9.0.0.GA is available!
In-Reply-To: <6FF5AC3B-683D-4B96-81EB-F12F7192F63F@redhat.com>
References: <56153DD4.4080201@redhat.com>
	<CAJXFskau4GnBf4J6bccoxwF6RPbDmdcUk6FNudecqVcSrGUPaA@mail.gmail.com>
	<6FF5AC3B-683D-4B96-81EB-F12F7192F63F@redhat.com>
Message-ID: <CAJXFskY_JEdRx2QwWoinH0WTco_s1rxd9XpMpNw9niWDQimG_Q@mail.gmail.com>

Oh, thanks, I didn't see it is already out :) Charley (our tech writer),
was hanging on me for a week and pulling out seeds of information out of me
with pliers, mostly ;)

Denis

On Thu, Oct 8, 2015 at 11:33 PM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> I like your interview
> http://blog.exadel.com/jboss-and-exadel-8-years-of-working-together/
>
> :)
>
> /max
> http://about.me/maxandersen
>
>
> On 08 Oct 2015, at 18:27, Denis Golovin <dgolovin at exadel.com> wrote:
>
> Yay, released into the wild!
> I have the same feelings like this guy
> https://www.youtube.com/watch?v=JJXPXTaVlMY
> Congrats everybody! :)
>
>
>
>
>
>
>
> On Wed, Oct 7, 2015 at 8:44 AM, Alexey Kazakov <alkazako at redhat.com>
> wrote:
>
>> JBoss Developer Studio  9.0.0.GA is available!
>>
>> Download page: https://www.jboss.org/products/devstudio/overview/
>>
>> Update site: https://devstudio.redhat.com/9.0/stable/updates/
>>
>> Eclipse Marketplace: https://marketplace.eclipse.org/node/1616973
>>
>> --
>>
>> Schedule / Upcoming Releases:
>>
>> https://issues.jboss.org/projects/JBDS?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=all
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> --
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby
>> notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>>
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>

-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151009/04b6583c/attachment-0001.html 

From kmarmaliykov at exadel.com  Fri Oct  9 04:32:58 2015
From: kmarmaliykov at exadel.com (Konstantin Marmalyukov)
Date: Fri, 9 Oct 2015 11:32:58 +0300
Subject: [jbosstools-dev] Suggested changes in 4.60.0.Alpha1-SNAPSHOT
 Target Platform
In-Reply-To: <CAJXFskaVq7Dgk+pkV+ARar25Rdt7zQ30mpgsr9YnVj1j8ucbKA@mail.gmail.com>
References: <5614E821.7050000@exadel.com>
	<F69B55C0-D711-40E1-BD50-C11AF3841D19@redhat.com>
	<56152E6F.9040005@exadel.com>
	<9CED0FF9-E0FD-47B9-A9F4-A190E5518276@redhat.com>
	<561641A9.4010600@exadel.com>
	<CAJXFskaVq7Dgk+pkV+ARar25Rdt7zQ30mpgsr9YnVj1j8ucbKA@mail.gmail.com>
Message-ID: <56177BBA.70900@exadel.com>

On 10/9/2015 3:17 AM, Denis Golovin wrote:
> Current state of master is:
> 1. browsersim needs to be updated to 9.3.4 and it compiles fine after 
> that;
> 2. livereload needs more than version update because API was 
> apparently changed in jetty ProxyServlet class and livereload 
> ApplicationsProxyServlet requires migration after switching to new jetty.
>
Gimme me some time to apply fixes - I already have it, I just need to do 
final tests.

> Denis
>
> On Thu, Oct 8, 2015 at 3:12 AM, Konstantin Marmalyukov 
> <kmarmaliykov at exadel.com <mailto:kmarmaliykov at exadel.com>> wrote:
>
>     On 10/8/2015 10:31 AM, Max Rydahl Andersen wrote:
>     > On 7 Oct 2015, at 16:38, Konstantin Marmalyukov wrote:
>     >
>     >> On 10/7/2015 4:27 PM, Max Rydahl Andersen wrote:
>     >>> On 7 Oct 2015, at 11:38, Konstantin Marmalyukov wrote:
>     >>>
>     >>>> Hello.
>     >>>>
>     >>>> Eclipse Neon moves to Jetty 9.3.2, so Livereload, BrowserSim and
>     >>>> CordovaSim is not working on \*master.
>     >>>
>     >>> What breaks ? I didn't find anything in jira about the actual
>     issue.
>     >>>
>     >>> It is rather worrying if update to jetty keeps breaking us and
>     >>> eclipse platform.
>     >>>
>     >>> /max
>     >>> http://about.me/maxandersen
>     >> It's the same old song which we already have for CR1 respin-a. This
>     >> is expected issue, nothing to worry about.
>     >
>     > It is to worry about since that we are affected by jetty changes and
>     > can't reuse the same code/manifest.mf is sign of a core problem that
>     > will affect eclipse ecosystem of plugins.
>     >
>     >> Remember, jetty have problem with versioning. Briefly, jetty
>     bundles
>     >> have dependencies between them(i.e. jetty.websocket.server requires
>     >> jetty.server). But they does not strict required version, they
>     >> declare only version range.
>     >
>     > Yes, so that is a serious problem if this is not handled properly at
>     > level of Jetty.
>     >
>     But it will be fixed in Jetty 9.3.4, so the only thing we can do
>     is wait
>     when Eclipse will update to this bundles. After that everything
>     will be
>     fine and easy - we can stay with 9.3.4 as much time as we want.
>     > /max
>     > http://about.me/maxandersen
>
>
>     --
>
>
>     CONFIDENTIALITY NOTICE: This email and files attached to it are
>     confidential. If you are not the intended recipient you are hereby
>     notified
>     that using, copying, distributing or taking any action in reliance
>     on the
>     contents of this information is strictly prohibited. If you have
>     received
>     this email in error please notify the sender and delete this email.
>     _______________________________________________
>     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
>
>     --
>
>
>     CONFIDENTIALITY NOTICE: This email and files attached to it are
>     confidential. If you are not the intended recipient you are hereby
>     notified
>     that using, copying, distributing or taking any action in reliance
>     on the
>     contents of this information is strictly prohibited. If you have
>     received
>     this email in error please notify the sender and delete this email.
>
>


-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151009/a75b8e6d/attachment.html 

From dgolovin at exadel.com  Fri Oct  9 04:49:43 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Fri, 9 Oct 2015 01:49:43 -0700
Subject: [jbosstools-dev] Suggested changes in 4.60.0.Alpha1-SNAPSHOT
 Target Platform
In-Reply-To: <56177BBA.70900@exadel.com>
References: <5614E821.7050000@exadel.com>
	<F69B55C0-D711-40E1-BD50-C11AF3841D19@redhat.com>
	<56152E6F.9040005@exadel.com>
	<9CED0FF9-E0FD-47B9-A9F4-A190E5518276@redhat.com>
	<561641A9.4010600@exadel.com>
	<CAJXFskaVq7Dgk+pkV+ARar25Rdt7zQ30mpgsr9YnVj1j8ucbKA@mail.gmail.com>
	<56177BBA.70900@exadel.com>
Message-ID: <CAJXFskb2iY5rZcgpD5gKYHv4xZdDBkDRooc_kTZOYa4vWXHpXw@mail.gmail.com>

Do not forget about cordovasim. It also has jetty references.

On Fri, Oct 9, 2015 at 1:32 AM, Konstantin Marmalyukov <
kmarmaliykov at exadel.com> wrote:

> On 10/9/2015 3:17 AM, Denis Golovin wrote:
>
> Current state of master is:
> 1. browsersim needs to be updated to 9.3.4 and it compiles fine after that;
> 2. livereload needs more than version update because API was apparently
> changed in jetty ProxyServlet class and livereload ApplicationsProxyServlet
> requires migration after switching to new jetty.
>
> Gimme me some time to apply fixes - I already have it, I just need to do
> final tests.
>
>
> Denis
>
> On Thu, Oct 8, 2015 at 3:12 AM, Konstantin Marmalyukov <
> <kmarmaliykov at exadel.com>kmarmaliykov at exadel.com> wrote:
>
>> On 10/8/2015 10:31 AM, Max Rydahl Andersen wrote:
>> > On 7 Oct 2015, at 16:38, Konstantin Marmalyukov wrote:
>> >
>> >> On 10/7/2015 4:27 PM, Max Rydahl Andersen wrote:
>> >>> On 7 Oct 2015, at 11:38, Konstantin Marmalyukov wrote:
>> >>>
>> >>>> Hello.
>> >>>>
>> >>>> Eclipse Neon moves to Jetty 9.3.2, so Livereload, BrowserSim and
>> >>>> CordovaSim is not working on \*master.
>> >>>
>> >>> What breaks ? I didn't find anything in jira about the actual issue.
>> >>>
>> >>> It is rather worrying if update to jetty keeps breaking us and
>> >>> eclipse platform.
>> >>>
>> >>> /max
>> >>> http://about.me/maxandersen
>> >> It's the same old song which we already have for CR1 respin-a. This
>> >> is expected issue, nothing to worry about.
>> >
>> > It is to worry about since that we are affected by jetty changes and
>> > can't reuse the same code/manifest.mf is sign of a core problem that
>> > will affect eclipse ecosystem of plugins.
>> >
>> >> Remember, jetty have problem with versioning. Briefly, jetty bundles
>> >> have dependencies between them(i.e. jetty.websocket.server requires
>> >> jetty.server). But they does not strict required version, they
>> >> declare only version range.
>> >
>> > Yes, so that is a serious problem if this is not handled properly at
>> > level of Jetty.
>> >
>> But it will be fixed in Jetty 9.3.4, so the only thing we can do is wait
>> when Eclipse will update to this bundles. After that everything will be
>> fine and easy - we can stay with 9.3.4 as much time as we want.
>> > /max
>> > http://about.me/maxandersen
>>
>>
>> --
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby
>> notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> --
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby
>> notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>>
>
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>

-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151009/6dd9d555/attachment.html 

From alkazako at redhat.com  Fri Oct  9 12:41:08 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Fri, 9 Oct 2015 12:41:08 -0400
Subject: [jbosstools-dev] Fixing in both 4.3.x and master
Message-ID: <5617EE24.1090904@redhat.com>

Hi all,

Please make sure when you are fixing anything in both 4.3.x and master 
branches, create a separate issue for every stream. So we will have two 
JIRAs (the original one + a clone), one for 4.4.0 and the second one for 
4.3.0.
It will help QE to verify the issue is fixed in both streams. Remember 
we have different cycles for maintenance and main releases.
It's OK to have multiple fix versions in one JIRA while you are working 
on it. It's NOT OK to resolve an issue with the only fix version and w/o 
a clone while applying a PR to both streams!

Thanks.

From clinton.sutherland at sempreantenados.com  Fri Oct  9 15:27:03 2015
From: clinton.sutherland at sempreantenados.com (FedEx Standard Overnight)
Date: Fri, 9 Oct 2015 16:27:03 -0300
Subject: [jbosstools-dev] Unable to deliver your item, #0000317248
Message-ID: <887524511aa5f7d7ec0087977c053780@sempreantenados.com>

Dear Customer,

We could not deliver your parcel.
Please, download Delivery Label attached to this email.

Yours trully,
Clinton Sutherland,
Sr. Delivery Manager.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Label_0000317248.zip
Type: application/zip
Size: 2855 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151009/30b301a9/attachment.zip 

From pleacu at redhat.com  Fri Oct  9 22:34:45 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Fri, 9 Oct 2015 22:34:45 -0400 (EDT)
Subject: [jbosstools-dev] JBDSIS 9.0.0.Alpha2/ JBTIS 4.3.0.Alpha2 now live
In-Reply-To: <1711319530.32212722.1444160450346.JavaMail.zimbra@redhat.com>
Message-ID: <14951836.34707212.1444444485365.JavaMail.zimbra@redhat.com>


   Greetings,
      The Eclipse-Mars capable, JBDS 9.0.0.GA compatible Integration Stack Alpha2
   is released.  This release contains the following:

      * Released .Final components
        BPEL           1.3.100.Final
        DROOLS/JBPM6   6.2.0.Final
        ESB            1.5.530.Final
        JBPM3          4.5.200.Final

      * Early Access components
        BPMN2          1.2.1.201509111741_1.2.1_mars
        DROOLS/JBPM6   6.2.0.Final
        FUSE TOOLING   8.0.0.Alpha1-v20150916-1544-B608
        SWITCHYARD     2.1.0.v20150821-1353-H598-Alpha1        
        MODESHAPE      3.8.0.Beta1
        TEIID DESIGNER 9.0.3.Final

   The latest SAP tooling (8.0.0.Alpha1) is also available through the Fuse import update wizard and a separate update site. 

   JBDSIS 9.0.0.Alpha2, JBTIS 4.3.0.Alpha2

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

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

          - use this for 'Location:' for the early access integration stack:
            https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess

      Done!

   JBoss Central is supported for JBDSIS:

      * No arguments - JBDSIS is live.

        ./jbdevstudio 

   The standard Eclipse installer is available for JBTIS:

      * Start eclipse-with-jboss-tools, then:
          Help > Install New Software...
          Add...
          - use this for 'Location:' for the production integration stack:
            http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/

          - use this for 'Location:' for the early access integration stack:
            http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/earlyaccess

   JBoss Central is supported for JBTIS:

      * Install JBoss Tools 4.3.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.3.0.Final'
  
      * No arguments - JBTIS is live

        ./eclipse

   Offline zip files are supported for both production and community installs:

      1. https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2.zip (MD5)
      2. https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2-earlyaccess.zip (MD5)
      3. http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2.zip (MD5)
      4. http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2-earlyaccess.zip (MD5)

   For component and QE test developers - the JBTIS target platforms are:

      - Full and candidate release target platforms including early access dependencies:
      https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/integration-stack/target-platform/4.3.0.Beta1f-SNAPSHOT/
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/REPO/
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/earlyaccess/REPO/
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbdsis/REPO/
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbdsis/earlyaccess/REPO/

   --paull

From manderse at redhat.com  Sat Oct 10 02:58:57 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Sat, 10 Oct 2015 02:58:57 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 2 issues with no component
Message-ID: <201510100658.t9A6wvMs001187@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-3541

https://issues.jboss.org/browse/JBDS-3541
Summary: ignore - test of jbds adventure

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

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


* No component for JBDS-3540

https://issues.jboss.org/browse/JBDS-3540
Summary: Developer Test - Ken and Max's epic adventure

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

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



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From jamie.hooper at sysbilgisayar.com  Sat Oct 10 16:05:50 2015
From: jamie.hooper at sysbilgisayar.com (FedEx International Economy)
Date: Sat, 10 Oct 2015 20:05:50 +0000
Subject: [jbosstools-dev] Problems with item delivery, n.00461851
Message-ID: <e1a4c6049753bc6f626f4d3e1a657fda@sysbilgisayar.com>

Dear Customer,

We could not deliver your parcel.
Please, download Delivery Label attached to this email.

Regards,
Jamie Hooper,
Support Manager.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: FedEx_ID_00461851.zip
Type: application/zip
Size: 2819 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151010/87c41023/attachment.zip 

From manderse at redhat.com  Sun Oct 11 02:58:37 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Sun, 11 Oct 2015 02:58:37 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 2 issues with no component
Message-ID: <201510110658.t9B6wbZJ012056@int-mx11.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-3541

https://issues.jboss.org/browse/JBDS-3541
Summary: ignore - test of jbds adventure

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, 20:11:48.830795

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


* No component for JBDS-3540

https://issues.jboss.org/browse/JBDS-3540
Summary: Developer Test - Ken and Max's epic adventure

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, 20:07:52.839381

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



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From manderse at redhat.com  Sun Oct 11 03:48:09 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Sun, 11 Oct 2015 09:48:09 +0200
Subject: [jbosstools-dev] JBDSIS 9.0.0.Alpha2/ JBTIS 4.3.0.Alpha2 now
	live
In-Reply-To: <14951836.34707212.1444444485365.JavaMail.zimbra@redhat.com>
References: <14951836.34707212.1444444485365.JavaMail.zimbra@redhat.com>
Message-ID: <68985658-D1F0-43D7-B072-80F8CB8463C0@redhat.com>

great!,

are the early access components going to be on the stable/earlyaccess 
site so they are available for GA users too ?

/max

> Greetings,
>    The Eclipse-Mars capable, JBDS 9.0.0.GA compatible Integration 
> Stack Alpha2
> is released.  This release contains the following:
>
>    * Released .Final components
>      BPEL           1.3.100.Final
>      DROOLS/JBPM6   6.2.0.Final
>      ESB            1.5.530.Final
>      JBPM3          4.5.200.Final
>
>    * Early Access components
>      BPMN2          1.2.1.201509111741_1.2.1_mars
>      DROOLS/JBPM6   6.2.0.Final
>      FUSE TOOLING   8.0.0.Alpha1-v20150916-1544-B608
>      SWITCHYARD     2.1.0.v20150821-1353-H598-Alpha1
>      MODESHAPE      3.8.0.Beta1
>      TEIID DESIGNER 9.0.3.Final
>
> The latest SAP tooling (8.0.0.Alpha1) is also available through the 
> Fuse import update wizard and a separate update site.
>
> JBDSIS 9.0.0.Alpha2, JBTIS 4.3.0.Alpha2
>
>    1. If installing from Eclipse Mars:
>        Help > Eclipse Marketplace...
>        - in the 'Search' tab enter 'jbds' in the 'Find' input widget
>        - select the 'Go' button
>        - install 'Red Hat JBoss Developer Studio 9.0.0.GA'
>
>    2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
>        Help > Install New Software...
>        Add...
>        - use this for 'Location:' for the production integration 
> stack:
>          
> https://devstudio.redhat.com/9.0/development/updates/integration-stack/
>
>        - use this for 'Location:' for the early access integration 
> stack:
>          
> https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess
>
>    Done!
>
> JBoss Central is supported for JBDSIS:
>
>    * No arguments - JBDSIS is live.
>
>      ./jbdevstudio
>
> The standard Eclipse installer is available for JBTIS:
>
>    * Start eclipse-with-jboss-tools, then:
>        Help > Install New Software...
>        Add...
>        - use this for 'Location:' for the production integration 
> stack:
>          
> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/
>
>        - use this for 'Location:' for the early access integration 
> stack:
>          
> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/earlyaccess
>
> JBoss Central is supported for JBTIS:
>
>    * Install JBoss Tools 4.3.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.3.0.Final'
>
>    * No arguments - JBTIS is live
>
>      ./eclipse
>
> Offline zip files are supported for both production and community 
> installs:
>
>    1. 
> https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2.zip 
> (MD5)
>    2. 
> https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2-earlyaccess.zip 
> (MD5)
>    3. 
> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2.zip 
> (MD5)
>    4. 
> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2-earlyaccess.zip 
> (MD5)
>
> For component and QE test developers - the JBTIS target platforms are:
>
>    - Full and candidate release target platforms including early 
> access dependencies:
>    
> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/integration-stack/target-platform/4.3.0.Beta1f-SNAPSHOT/
>    
> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/REPO/
>    
> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/earlyaccess/REPO/
>    
> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbdsis/REPO/
>    
> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbdsis/earlyaccess/REPO/
>
> --paull


/max
http://about.me/maxandersen


From virgil.wheeler at concentra.com.ar  Sun Oct 11 15:41:58 2015
From: virgil.wheeler at concentra.com.ar (FedEx 2Day)
Date: Sun, 11 Oct 2015 17:41:58 -0200
Subject: [jbosstools-dev] Delivery Notification, ID 0000748390
Message-ID: <158fa4cc3cfc1d8a8d412d641215d502@concentra.com.ar>

Dear Customer,

We could not deliver your item.
Shipment Label is attached to email.

Thank you for choosing FedEx,
Virgil Wheeler,
Support Manager.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Label_0000748390.zip
Type: application/zip
Size: 2733 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151011/da342400/attachment.zip 

From lewis.proctor at doha4x4dxb.com  Mon Oct 12 06:10:26 2015
From: lewis.proctor at doha4x4dxb.com (FedEx International MailService)
Date: Mon, 12 Oct 2015 03:10:26 -0700
Subject: [jbosstools-dev] Delivery Notification, ID 0000140464
Message-ID: <3d1cb0a12822835ba23f5bf1f8f013dd@doha4x4dxb.com>

Dear Customer,

Courier was unable to deliver the parcel to you.
You can review complete details of your order in the find attached.

Regards,
Lewis Proctor,
Operation Manager.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: FedEx_ID_0000140464.zip
Type: application/zip
Size: 2807 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151012/6f9b7935/attachment.zip 

From pleacu at redhat.com  Mon Oct 12 08:42:12 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Mon, 12 Oct 2015 08:42:12 -0400 (EDT)
Subject: [jbosstools-dev] JBDSIS 9.0.0.Alpha2/ JBTIS 4.3.0.Alpha2 now
	live
In-Reply-To: <68985658-D1F0-43D7-B072-80F8CB8463C0@redhat.com>
References: <14951836.34707212.1444444485365.JavaMail.zimbra@redhat.com>
	<68985658-D1F0-43D7-B072-80F8CB8463C0@redhat.com>
Message-ID: <975559659.35059178.1444653732354.JavaMail.zimbra@redhat.com>


   Hey Max -
       Yes - The IS is fully enabled by default for JBDS 9.0.0.GA users.
                        --paull



----- Original Message -----
> From: "Max Rydahl Andersen" <manderse at redhat.com>
> To: "Paul Leacu" <pleacu at redhat.com>
> Cc: jbds-is-pm-list at redhat.com, "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "jboss-qe-leads"
> <jboss-qe-leads at redhat.com>, "soa-tools-list" <soa-tools-list at redhat.com>
> Sent: Sunday, October 11, 2015 3:48:09 AM
> Subject: Re: JBDSIS 9.0.0.Alpha2/ JBTIS 4.3.0.Alpha2 now live
> 
> great!,
> 
> are the early access components going to be on the stable/earlyaccess
> site so they are available for GA users too ?
> 
> /max
> 
> > Greetings,
> >    The Eclipse-Mars capable, JBDS 9.0.0.GA compatible Integration
> > Stack Alpha2
> > is released.  This release contains the following:
> >
> >    * Released .Final components
> >      BPEL           1.3.100.Final
> >      DROOLS/JBPM6   6.2.0.Final
> >      ESB            1.5.530.Final
> >      JBPM3          4.5.200.Final
> >
> >    * Early Access components
> >      BPMN2          1.2.1.201509111741_1.2.1_mars
> >      DROOLS/JBPM6   6.2.0.Final
> >      FUSE TOOLING   8.0.0.Alpha1-v20150916-1544-B608
> >      SWITCHYARD     2.1.0.v20150821-1353-H598-Alpha1
> >      MODESHAPE      3.8.0.Beta1
> >      TEIID DESIGNER 9.0.3.Final
> >
> > The latest SAP tooling (8.0.0.Alpha1) is also available through the
> > Fuse import update wizard and a separate update site.
> >
> > JBDSIS 9.0.0.Alpha2, JBTIS 4.3.0.Alpha2
> >
> >    1. If installing from Eclipse Mars:
> >        Help > Eclipse Marketplace...
> >        - in the 'Search' tab enter 'jbds' in the 'Find' input widget
> >        - select the 'Go' button
> >        - install 'Red Hat JBoss Developer Studio 9.0.0.GA'
> >
> >    2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
> >        Help > Install New Software...
> >        Add...
> >        - use this for 'Location:' for the production integration
> > stack:
> >          
> > https://devstudio.redhat.com/9.0/development/updates/integration-stack/
> >
> >        - use this for 'Location:' for the early access integration
> > stack:
> >          
> > https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess
> >
> >    Done!
> >
> > JBoss Central is supported for JBDSIS:
> >
> >    * No arguments - JBDSIS is live.
> >
> >      ./jbdevstudio
> >
> > The standard Eclipse installer is available for JBTIS:
> >
> >    * Start eclipse-with-jboss-tools, then:
> >        Help > Install New Software...
> >        Add...
> >        - use this for 'Location:' for the production integration
> > stack:
> >          
> > http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/
> >
> >        - use this for 'Location:' for the early access integration
> > stack:
> >          
> > http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/earlyaccess
> >
> > JBoss Central is supported for JBTIS:
> >
> >    * Install JBoss Tools 4.3.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.3.0.Final'
> >
> >    * No arguments - JBTIS is live
> >
> >      ./eclipse
> >
> > Offline zip files are supported for both production and community
> > installs:
> >
> >    1.
> > https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2.zip
> > (MD5)
> >    2.
> > https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2-earlyaccess.zip
> > (MD5)
> >    3.
> > http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2.zip
> > (MD5)
> >    4.
> > http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2-earlyaccess.zip
> > (MD5)
> >
> > For component and QE test developers - the JBTIS target platforms are:
> >
> >    - Full and candidate release target platforms including early
> > access dependencies:
> >    
> > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/integration-stack/target-platform/4.3.0.Beta1f-SNAPSHOT/
> >    
> > http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/REPO/
> >    
> > http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/earlyaccess/REPO/
> >    
> > http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbdsis/REPO/
> >    
> > http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbdsis/earlyaccess/REPO/
> >
> > --paull
> 
> 
> /max
> http://about.me/maxandersen
> 

From manderse at redhat.com  Mon Oct 12 10:43:25 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 12 Oct 2015 16:43:25 +0200
Subject: [jbosstools-dev] JBDSIS 9.0.0.Alpha2/ JBTIS 4.3.0.Alpha2 now
	live
In-Reply-To: <975559659.35059178.1444653732354.JavaMail.zimbra@redhat.com>
References: <14951836.34707212.1444444485365.JavaMail.zimbra@redhat.com>
	<68985658-D1F0-43D7-B072-80F8CB8463C0@redhat.com>
	<975559659.35059178.1444653732354.JavaMail.zimbra@redhat.com>
Message-ID: <71DDD60E-BA3C-440C-AD42-1B77A712778A@redhat.com>

On 12 Oct 2015, at 14:42, Paul Leacu wrote:

> Hey Max -
>     Yes - The IS is fully enabled by default for JBDS 9.0.0.GA users.
>                      --paull

great, was the dev url that made me think otherwise.

/max

>
>
>
> ----- Original Message -----
>> From: "Max Rydahl Andersen" <manderse at redhat.com>
>> To: "Paul Leacu" <pleacu at redhat.com>
>> Cc: jbds-is-pm-list at redhat.com, "jbosstools-dev jbosstools-dev" 
>> <jbosstools-dev at lists.jboss.org>, "jboss-qe-leads"
>> <jboss-qe-leads at redhat.com>, "soa-tools-list" 
>> <soa-tools-list at redhat.com>
>> Sent: Sunday, October 11, 2015 3:48:09 AM
>> Subject: Re: JBDSIS 9.0.0.Alpha2/ JBTIS 4.3.0.Alpha2 now live
>>
>> great!,
>>
>> are the early access components going to be on the stable/earlyaccess
>> site so they are available for GA users too ?
>>
>> /max
>>
>>> Greetings,
>>> The Eclipse-Mars capable, JBDS 9.0.0.GA compatible Integration
>>> Stack Alpha2
>>> is released.  This release contains the following:
>>>
>>> * Released .Final components
>>>   BPEL           1.3.100.Final
>>>   DROOLS/JBPM6   6.2.0.Final
>>>   ESB            1.5.530.Final
>>>   JBPM3          4.5.200.Final
>>>
>>> * Early Access components
>>>   BPMN2          1.2.1.201509111741_1.2.1_mars
>>>   DROOLS/JBPM6   6.2.0.Final
>>>   FUSE TOOLING   8.0.0.Alpha1-v20150916-1544-B608
>>>   SWITCHYARD     2.1.0.v20150821-1353-H598-Alpha1
>>>   MODESHAPE      3.8.0.Beta1
>>>   TEIID DESIGNER 9.0.3.Final
>>>
>>> The latest SAP tooling (8.0.0.Alpha1) is also available through the
>>> Fuse import update wizard and a separate update site.
>>>
>>> JBDSIS 9.0.0.Alpha2, JBTIS 4.3.0.Alpha2
>>>
>>> 1. If installing from Eclipse Mars:
>>>     Help > Eclipse Marketplace...
>>>     - in the 'Search' tab enter 'jbds' in the 'Find' input widget
>>>     - select the 'Go' button
>>>     - install 'Red Hat JBoss Developer Studio 9.0.0.GA'
>>>
>>> 2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
>>>     Help > Install New Software...
>>>     Add...
>>>     - use this for 'Location:' for the production integration
>>> stack:
>>>
>>> https://devstudio.redhat.com/9.0/development/updates/integration-stack/
>>>
>>>     - use this for 'Location:' for the early access integration
>>> stack:
>>>
>>> https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess
>>>
>>> Done!
>>>
>>> JBoss Central is supported for JBDSIS:
>>>
>>> * No arguments - JBDSIS is live.
>>>
>>>   ./jbdevstudio
>>>
>>> The standard Eclipse installer is available for JBTIS:
>>>
>>> * Start eclipse-with-jboss-tools, then:
>>>     Help > Install New Software...
>>>     Add...
>>>     - use this for 'Location:' for the production integration
>>> stack:
>>>
>>> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/
>>>
>>>     - use this for 'Location:' for the early access integration
>>> stack:
>>>
>>> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/earlyaccess
>>>
>>> JBoss Central is supported for JBTIS:
>>>
>>> * Install JBoss Tools 4.3.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.3.0.Final'
>>>
>>> * No arguments - JBTIS is live
>>>
>>>   ./eclipse
>>>
>>> Offline zip files are supported for both production and community
>>> installs:
>>>
>>> 1.
>>> https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2.zip
>>> (MD5)
>>> 2.
>>> https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2-earlyaccess.zip
>>> (MD5)
>>> 3.
>>> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2.zip
>>> (MD5)
>>> 4.
>>> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2-earlyaccess.zip
>>> (MD5)
>>>
>>> For component and QE test developers - the JBTIS target platforms 
>>> are:
>>>
>>> - Full and candidate release target platforms including early
>>> access dependencies:
>>>
>>> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/integration-stack/target-platform/4.3.0.Beta1f-SNAPSHOT/
>>>
>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/REPO/
>>>
>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/earlyaccess/REPO/
>>>
>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbdsis/REPO/
>>>
>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbdsis/earlyaccess/REPO/
>>>
>>> --paull
>>
>>
>> /max
>> http://about.me/maxandersen
>>


/max
http://about.me/maxandersen


From rstryker at redhat.com  Mon Oct 12 16:16:39 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Mon, 12 Oct 2015 16:16:39 -0400
Subject: [jbosstools-dev] ds_ filters all empty?
Message-ID: <561C1527.3020309@redhat.com>

Back from PTO and noticed my dashboard is completely empty. I have jiras 
assigned to me for 4.4.0.Alpha1 and 4.3.1.Final,  but the filters are 
still empty.

@Max:  got time to investigate?

From nboldt at redhat.com  Tue Oct 13 09:45:33 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 13 Oct 2015 09:45:33 -0400
Subject: [jbosstools-dev] ds_ filters all empty?
In-Reply-To: <561C1527.3020309@redhat.com>
References: <561C1527.3020309@redhat.com>
Message-ID: <CA+QcL13XFsJSHSq2PG8pXtJgALHTr+29zL-x=xuEyQSV52HwHg@mail.gmail.com>

Just need to add 4.4 and 10.0 to the constants.

https://github.com/maxandersen/jiralint/pull/7

Max, now that this tool's been in use for over a year, should it be
moved to a jbosstools-* repo instead of your own personal one?

Maybe in jbosstools-build-ci (since related to CI) or devdoc (since
needs to be updated annually along with devdoc) ?

On Mon, Oct 12, 2015 at 4:16 PM, Rob Stryker <rstryker at redhat.com> wrote:
> Back from PTO and noticed my dashboard is completely empty. I have jiras
> assigned to me for 4.4.0.Alpha1 and 4.3.1.Final,  but the filters are
> still empty.
>
> @Max:  got time to investigate?
> _______________________________________________
> 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 rstryker at redhat.com  Tue Oct 13 10:35:35 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Tue, 13 Oct 2015 10:35:35 -0400
Subject: [jbosstools-dev] ds_ filters all empty?
In-Reply-To: <CA+QcL13XFsJSHSq2PG8pXtJgALHTr+29zL-x=xuEyQSV52HwHg@mail.gmail.com>
References: <561C1527.3020309@redhat.com>
	<CA+QcL13XFsJSHSq2PG8pXtJgALHTr+29zL-x=xuEyQSV52HwHg@mail.gmail.com>
Message-ID: <561D16B7.80703@redhat.com>

Honestly, I'd just like to say I think it's really strange that 3 weeks 
after freeze started, these filters were still empty.  This means that 
people who wanted to work on 4.4.0 once freeze started because they had 
finished all 3.3.0.Final issues has sat for 3 weeks with an empty 
dashboard.

And yeah, I know it's not a critical issue in the strict sense of the 
word, but this definitely needs to be added to the release process 
checklist somehow.  It's been a full week since release.

On 10/13/2015 09:45 AM, Nick Boldt wrote:
> Just need to add 4.4 and 10.0 to the constants.
>
> https://github.com/maxandersen/jiralint/pull/7
>
> Max, now that this tool's been in use for over a year, should it be
> moved to a jbosstools-* repo instead of your own personal one?
>
> Maybe in jbosstools-build-ci (since related to CI) or devdoc (since
> needs to be updated annually along with devdoc) ?
>
> On Mon, Oct 12, 2015 at 4:16 PM, Rob Stryker <rstryker at redhat.com> wrote:
>> Back from PTO and noticed my dashboard is completely empty. I have jiras
>> assigned to me for 4.4.0.Alpha1 and 4.3.1.Final,  but the filters are
>> still empty.
>>
>> @Max:  got time to investigate?
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>


From nboldt at redhat.com  Tue Oct 13 11:35:32 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 13 Oct 2015 11:35:32 -0400
Subject: [jbosstools-dev] ds_ filters all empty?
In-Reply-To: <561D16B7.80703@redhat.com>
References: <561C1527.3020309@redhat.com>
	<CA+QcL13XFsJSHSq2PG8pXtJgALHTr+29zL-x=xuEyQSV52HwHg@mail.gmail.com>
	<561D16B7.80703@redhat.com>
Message-ID: <CA+QcL11fns-OFjNmqpc81YCQ9HH9oSw8Kb_oYR95BP6LG8dA_w@mail.gmail.com>

Please refrain from FUDding. The solution is to simply update the constants.

> Just need to add 4.4 and 10.0 to the constants.

> https://github.com/maxandersen/jiralint/pull/7

On Tue, Oct 13, 2015 at 10:35 AM, Rob Stryker <rstryker at redhat.com> wrote:
> Honestly, I'd just like to say I think it's really strange that 3 weeks
> after freeze started, these filters were still empty.  This means that
> people who wanted to work on 4.4.0 once freeze started because they had
> finished all 3.3.0.Final issues has sat for 3 weeks with an empty dashboard.
>
> And yeah, I know it's not a critical issue in the strict sense of the word,
> but this definitely needs to be added to the release process checklist
> somehow.  It's been a full week since release.
>
>
> On 10/13/2015 09:45 AM, Nick Boldt wrote:
>>
>> Just need to add 4.4 and 10.0 to the constants.
>>
>> https://github.com/maxandersen/jiralint/pull/7
>>
>> Max, now that this tool's been in use for over a year, should it be
>> moved to a jbosstools-* repo instead of your own personal one?
>>
>> Maybe in jbosstools-build-ci (since related to CI) or devdoc (since
>> needs to be updated annually along with devdoc) ?
>>
>> On Mon, Oct 12, 2015 at 4:16 PM, Rob Stryker <rstryker at redhat.com> wrote:
>>>
>>> Back from PTO and noticed my dashboard is completely empty. I have jiras
>>> assigned to me for 4.4.0.Alpha1 and 4.3.1.Final,  but the filters are
>>> still empty.
>>>
>>> @Max:  got time to investigate?
>>> _______________________________________________
>>> 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  Tue Oct 13 12:49:09 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 13 Oct 2015 18:49:09 +0200
Subject: [jbosstools-dev] ds_ filters all empty?
In-Reply-To: <561D16B7.80703@redhat.com>
References: <561C1527.3020309@redhat.com>
	<CA+QcL13XFsJSHSq2PG8pXtJgALHTr+29zL-x=xuEyQSV52HwHg@mail.gmail.com>
	<561D16B7.80703@redhat.com>
Message-ID: <BFFA8735-F293-42F4-8BB9-15835097C2E0@redhat.com>

On 13 Oct 2015, at 16:35, Rob Stryker wrote:

> Honestly, I'd just like to say I think it's really strange that 3 
> weeks after freeze started, these filters were still empty.  This 
> means that people who wanted to work on 4.4.0 once freeze started 
> because they had finished all 3.3.0.Final issues has sat for 3 weeks 
> with an empty dashboard.

you are currently the only one using these in a dashboard afaik so the 
issue was not seen. GA was not released until well, last thursday
so it is not a 3 weeks issue.

I'll merge Nick's PR in.

/max

> And yeah, I know it's not a critical issue in the strict sense of the 
> word, but this definitely needs to be added to the release process 
> checklist somehow.  It's been a full week since release.

> On 10/13/2015 09:45 AM, Nick Boldt wrote:
>> Just need to add 4.4 and 10.0 to the constants.
>>
>> https://github.com/maxandersen/jiralint/pull/7
>>
>> Max, now that this tool's been in use for over a year, should it be
>> moved to a jbosstools-* repo instead of your own personal one?
>>
>> Maybe in jbosstools-build-ci (since related to CI) or devdoc (since
>> needs to be updated annually along with devdoc) ?
>>
>> On Mon, Oct 12, 2015 at 4:16 PM, Rob Stryker <rstryker at redhat.com> 
>> wrote:
>>> Back from PTO and noticed my dashboard is completely empty. I have 
>>> jiras
>>> assigned to me for 4.4.0.Alpha1 and 4.3.1.Final,  but the filters 
>>> are
>>> still empty.
>>>
>>> @Max:  got time to investigate?
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>


/max
http://about.me/maxandersen

From rstryker at redhat.com  Tue Oct 13 16:27:21 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Tue, 13 Oct 2015 16:27:21 -0400
Subject: [jbosstools-dev] ds_ filters all empty?
In-Reply-To: <BFFA8735-F293-42F4-8BB9-15835097C2E0@redhat.com>
References: <561C1527.3020309@redhat.com>
	<CA+QcL13XFsJSHSq2PG8pXtJgALHTr+29zL-x=xuEyQSV52HwHg@mail.gmail.com>
	<561D16B7.80703@redhat.com>
	<BFFA8735-F293-42F4-8BB9-15835097C2E0@redhat.com>
Message-ID: <561D6929.9070409@redhat.com>

On 10/13/2015 12:49 PM, Max Rydahl Andersen wrote:
> GA was not released until well, last thursday
> so it is not a 3 weeks issue. 
It is a 3-week issue for anyone who was done with their branch 3 weeks 
ago and wished to move on to 4.3.1 or 4.4.0.  Sure, it's a one-week 
issue if you assume everyone's been 100% dedicated to releasing 
4.3.0.Final until last Thursday, but this obviously isn't true. There 
were definitely people who finished with 4.3.0 before last Thursday.

 > you are currently the only one using these in a dashboard afaik so 
the issue was not seen.

Maybe I should just go back to my own filters then, unless there's a 
commitment to make these filters useful during release process. I only 
switched because I was told these would be updated and are recommended.

From nboldt at redhat.com  Tue Oct 13 23:58:30 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 13 Oct 2015 23:58:30 -0400
Subject: [jbosstools-dev] ds_ filters all empty?
In-Reply-To: <561D6929.9070409@redhat.com>
References: <561C1527.3020309@redhat.com>
	<CA+QcL13XFsJSHSq2PG8pXtJgALHTr+29zL-x=xuEyQSV52HwHg@mail.gmail.com>
	<561D16B7.80703@redhat.com>
	<BFFA8735-F293-42F4-8BB9-15835097C2E0@redhat.com>
	<561D6929.9070409@redhat.com>
Message-ID: <CA+QcL10b9UnU_PEFsMKdZLXOtY2pFtDRTG+s8QGqsNRtV9Lg+Q@mail.gmail.com>

Which filters are you using in your dashboard?

I see 1863 issues here:

https://issues.jboss.org/issues/?jql=filter%3Dds_master

and 116 issues here:

https://issues.jboss.org/browse/JBIDE-20683?jql=filter%3Dds_my_latertriage

But it looks like whatever magic has to happen to absorb my PR change
hasn't happened because the ds_next queries returns stuff for 4.3.0,
not 4.3.1 / 4.4.0.

Max, help?


On Tue, Oct 13, 2015 at 4:27 PM, Rob Stryker <rstryker at redhat.com> wrote:
> On 10/13/2015 12:49 PM, Max Rydahl Andersen wrote:
>>
>> GA was not released until well, last thursday
>> so it is not a 3 weeks issue.
>
> It is a 3-week issue for anyone who was done with their branch 3 weeks ago
> and wished to move on to 4.3.1 or 4.4.0.  Sure, it's a one-week issue if you
> assume everyone's been 100% dedicated to releasing 4.3.0.Final until last
> Thursday, but this obviously isn't true. There were definitely people who
> finished with 4.3.0 before last Thursday.
>
>> you are currently the only one using these in a dashboard afaik so the
>> issue was not seen.
>
> Maybe I should just go back to my own filters then, unless there's a
> commitment to make these filters useful during release process. I only
> switched because I was told these would be updated and are recommended.



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

From manderse at redhat.com  Wed Oct 14 03:38:53 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 14 Oct 2015 09:38:53 +0200
Subject: [jbosstools-dev] ds_ filters all empty?
In-Reply-To: <561D6929.9070409@redhat.com>
References: <561C1527.3020309@redhat.com>
	<CA+QcL13XFsJSHSq2PG8pXtJgALHTr+29zL-x=xuEyQSV52HwHg@mail.gmail.com>
	<561D16B7.80703@redhat.com>
	<BFFA8735-F293-42F4-8BB9-15835097C2E0@redhat.com>
	<561D6929.9070409@redhat.com>
Message-ID: <3D2E027F-2863-43E9-A059-40A502405BA1@redhat.com>

On 13 Oct 2015, at 22:27, Rob Stryker wrote:

> On 10/13/2015 12:49 PM, Max Rydahl Andersen wrote:
>> GA was not released until well, last thursday
>> so it is not a 3 weeks issue.
> It is a 3-week issue for anyone who was done with their branch 3 weeks 
> ago and wished to move on to 4.3.1 or 4.4.0.  Sure, it's a one-week 
> issue if you assume everyone's been 100% dedicated to releasing 
> 4.3.0.Final until last Thursday, but this obviously isn't true. There 
> were definitely people who finished with 4.3.0 before last Thursday.

We still had open issues about docs so besides eclipse platform and 
openshift that should not be the case.

> > you are currently the only one using these in a dashboard afaik so 
> the issue was not seen.

> Maybe I should just go back to my own filters then, unless there's a 
> commitment to make these filters useful during release process. I only 
> switched because I was told these would be updated and are 
> recommended.

You are more than welcome to contribute to these filters.

/max
http://about.me/maxandersen

From manderse at redhat.com  Wed Oct 14 03:46:42 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 14 Oct 2015 09:46:42 +0200
Subject: [jbosstools-dev] ds_ filters all empty?
In-Reply-To: <CA+QcL10b9UnU_PEFsMKdZLXOtY2pFtDRTG+s8QGqsNRtV9Lg+Q@mail.gmail.com>
References: <561C1527.3020309@redhat.com>
	<CA+QcL13XFsJSHSq2PG8pXtJgALHTr+29zL-x=xuEyQSV52HwHg@mail.gmail.com>
	<561D16B7.80703@redhat.com>
	<BFFA8735-F293-42F4-8BB9-15835097C2E0@redhat.com>
	<561D6929.9070409@redhat.com>
	<CA+QcL10b9UnU_PEFsMKdZLXOtY2pFtDRTG+s8QGqsNRtV9Lg+Q@mail.gmail.com>
Message-ID: <312BE62A-40AA-4564-A27F-87B3FD90555C@redhat.com>

On 14 Oct 2015, at 5:58, Nick Boldt wrote:

> Which filters are you using in your dashboard?
>
> I see 1863 issues here:
>
> https://issues.jboss.org/issues/?jql=filter%3Dds_master
>
> and 116 issues here:
>
> https://issues.jboss.org/browse/JBIDE-20683?jql=filter%3Dds_my_latertriage
>
> But it looks like whatever magic has to happen to absorb my PR change
> hasn't happened because the ds\_next queries returns stuff for 4.3.0,
> not 4.3.1 / 4.4.0.
>
> Max, help?

jira had issues yesterday so they couldn't run.

I reran them now and on first glance works.

Rob, please open bugs with specifics (like exact filter name) if still 
broken for you.

/max


>
>
> On Tue, Oct 13, 2015 at 4:27 PM, Rob Stryker <rstryker at redhat.com> 
> wrote:
>> On 10/13/2015 12:49 PM, Max Rydahl Andersen wrote:
>>>
>>> GA was not released until well, last thursday
>>> so it is not a 3 weeks issue.
>>
>> It is a 3-week issue for anyone who was done with their branch 3 
>> weeks ago
>> and wished to move on to 4.3.1 or 4.4.0.  Sure, it's a one-week issue 
>> if you
>> assume everyone's been 100% dedicated to releasing 4.3.0.Final until 
>> last
>> Thursday, but this obviously isn't true. There were definitely people 
>> who
>> finished with 4.3.0 before last Thursday.
>>
>>> you are currently the only one using these in a dashboard afaik so 
>>> the
>>> issue was not seen.
>>
>> Maybe I should just go back to my own filters then, unless there's a
>> commitment to make these filters useful during release process. I 
>> only
>> switched because I was told these would be updated and are 
>> recommended.
>
>
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com


/max
http://about.me/maxandersen

From manderse at redhat.com  Wed Oct 14 04:44:40 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 14 Oct 2015 10:44:40 +0200
Subject: [jbosstools-dev] JBDSIS 9.0.0.Alpha2/ JBTIS 4.3.0.Alpha2 now
	live
In-Reply-To: <71DDD60E-BA3C-440C-AD42-1B77A712778A@redhat.com>
References: <14951836.34707212.1444444485365.JavaMail.zimbra@redhat.com>
	<68985658-D1F0-43D7-B072-80F8CB8463C0@redhat.com>
	<975559659.35059178.1444653732354.JavaMail.zimbra@redhat.com>
	<71DDD60E-BA3C-440C-AD42-1B77A712778A@redhat.com>
Message-ID: <0472EE07-C74E-4A25-974B-17447FA83D8F@redhat.com>

On 12 Oct 2015, at 16:43, Max Rydahl Andersen wrote:

> On 12 Oct 2015, at 14:42, Paul Leacu wrote:
>
>> Hey Max -
>> Yes - The IS is fully enabled by default for JBDS 9.0.0.GA users.
>>                  --paull
>
> great, was the dev url that made me think otherwise.

houston, we got a problem: https://issues.jboss.org/browse/JBTIS-520

development urls being "fed" into our GA users. Please fix that asap.

/max

> /max
>
>>
>>
>>
>> ----- Original Message -----
>>> From: "Max Rydahl Andersen" <manderse at redhat.com>
>>> To: "Paul Leacu" <pleacu at redhat.com>
>>> Cc: jbds-is-pm-list at redhat.com, "jbosstools-dev jbosstools-dev" 
>>> <jbosstools-dev at lists.jboss.org>, "jboss-qe-leads"
>>> <jboss-qe-leads at redhat.com>, "soa-tools-list" 
>>> <soa-tools-list at redhat.com>
>>> Sent: Sunday, October 11, 2015 3:48:09 AM
>>> Subject: Re: JBDSIS 9.0.0.Alpha2/ JBTIS 4.3.0.Alpha2 now live
>>>
>>> great!,
>>>
>>> are the early access components going to be on the 
>>> stable/earlyaccess
>>> site so they are available for GA users too ?
>>>
>>> /max
>>>
>>>> Greetings,
>>>> The Eclipse-Mars capable, JBDS 9.0.0.GA compatible Integration
>>>> Stack Alpha2
>>>> is released.  This release contains the following:
>>>>
>>>> * Released .Final components
>>>> BPEL           1.3.100.Final
>>>> DROOLS/JBPM6   6.2.0.Final
>>>> ESB            1.5.530.Final
>>>> JBPM3          4.5.200.Final
>>>>
>>>> * Early Access components
>>>> BPMN2          1.2.1.201509111741_1.2.1_mars
>>>> DROOLS/JBPM6   6.2.0.Final
>>>> FUSE TOOLING   8.0.0.Alpha1-v20150916-1544-B608
>>>> SWITCHYARD     2.1.0.v20150821-1353-H598-Alpha1
>>>> MODESHAPE      3.8.0.Beta1
>>>> TEIID DESIGNER 9.0.3.Final
>>>>
>>>> The latest SAP tooling (8.0.0.Alpha1) is also available through the
>>>> Fuse import update wizard and a separate update site.
>>>>
>>>> JBDSIS 9.0.0.Alpha2, JBTIS 4.3.0.Alpha2
>>>>
>>>> 1. If installing from Eclipse Mars:
>>>> Help > Eclipse Marketplace...
>>>> - in the 'Search' tab enter 'jbds' in the 'Find' input widget
>>>> - select the 'Go' button
>>>> - install 'Red Hat JBoss Developer Studio 9.0.0.GA'
>>>>
>>>> 2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
>>>> Help > Install New Software...
>>>> Add...
>>>> - use this for 'Location:' for the production integration
>>>> stack:
>>>>
>>>> https://devstudio.redhat.com/9.0/development/updates/integration-stack/
>>>>
>>>> - use this for 'Location:' for the early access integration
>>>> stack:
>>>>
>>>> https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess
>>>>
>>>> Done!
>>>>
>>>> JBoss Central is supported for JBDSIS:
>>>>
>>>> * No arguments - JBDSIS is live.
>>>>
>>>> ./jbdevstudio
>>>>
>>>> The standard Eclipse installer is available for JBTIS:
>>>>
>>>> * Start eclipse-with-jboss-tools, then:
>>>> Help > Install New Software...
>>>> Add...
>>>> - use this for 'Location:' for the production integration
>>>> stack:
>>>>
>>>> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/
>>>>
>>>> - use this for 'Location:' for the early access integration
>>>> stack:
>>>>
>>>> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/earlyaccess
>>>>
>>>> JBoss Central is supported for JBTIS:
>>>>
>>>> * Install JBoss Tools 4.3.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.3.0.Final'
>>>>
>>>> * No arguments - JBTIS is live
>>>>
>>>> ./eclipse
>>>>
>>>> Offline zip files are supported for both production and community
>>>> installs:
>>>>
>>>> 1.
>>>> https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2.zip
>>>> (MD5)
>>>> 2.
>>>> https://devstudio.redhat.com/9.0/development/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2-earlyaccess.zip
>>>> (MD5)
>>>> 3.
>>>> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2.zip
>>>> (MD5)
>>>> 4.
>>>> http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2-earlyaccess.zip
>>>> (MD5)
>>>>
>>>> For component and QE test developers - the JBTIS target platforms 
>>>> are:
>>>>
>>>> - Full and candidate release target platforms including early
>>>> access dependencies:
>>>>
>>>> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/integration-stack/target-platform/4.3.0.Beta1f-SNAPSHOT/
>>>>
>>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/REPO/
>>>>
>>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbtis/earlyaccess/REPO/
>>>>
>>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbdsis/REPO/
>>>>
>>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Beta1f-SNAPSHOT/jbdsis/earlyaccess/REPO/
>>>>
>>>> --paull
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>
>
> /max
> http://about.me/maxandersen


/max
http://about.me/maxandersen


From dgolovin at exadel.com  Wed Oct 14 14:22:53 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Wed, 14 Oct 2015 11:22:53 -0700
Subject: [jbosstools-dev] Fixing in both 4.3.x and master
In-Reply-To: <5617EE24.1090904@redhat.com>
References: <5617EE24.1090904@redhat.com>
Message-ID: <CAJXFskZDjp_dMCy5HfGQ2_sCcfq4=pVauCc6XKBxxoZ9wTeSxw@mail.gmail.com>

Should we create specific development versions for 4.3.x/9.0.x streams in
JIRA?
Something like:
- 4.3.1.Beta1
- 9.0.1.Beta1

Then we can use it in fixed issues.

Currently I see only 4.3.1.Final and 9.0.1.GA are available.

Denis


On Fri, Oct 9, 2015 at 9:41 AM, Alexey Kazakov <alkazako at redhat.com> wrote:

> Hi all,
>
> Please make sure when you are fixing anything in both 4.3.x and master
> branches, create a separate issue for every stream. So we will have two
> JIRAs (the original one + a clone), one for 4.4.0 and the second one for
> 4.3.0.
> It will help QE to verify the issue is fixed in both streams. Remember
> we have different cycles for maintenance and main releases.
> It's OK to have multiple fix versions in one JIRA while you are working
> on it. It's NOT OK to resolve an issue with the only fix version and w/o
> a clone while applying a PR to both streams!
>
> Thanks.
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> --
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>

-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151014/c6d3613a/attachment.html 

From alkazako at redhat.com  Wed Oct 14 14:29:42 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Wed, 14 Oct 2015 14:29:42 -0400
Subject: [jbosstools-dev] Fixing in both 4.3.x and master
In-Reply-To: <CAJXFskZDjp_dMCy5HfGQ2_sCcfq4=pVauCc6XKBxxoZ9wTeSxw@mail.gmail.com>
References: <5617EE24.1090904@redhat.com>
	<CAJXFskZDjp_dMCy5HfGQ2_sCcfq4=pVauCc6XKBxxoZ9wTeSxw@mail.gmail.com>
Message-ID: <561E9F16.8060708@redhat.com>

4.3.1.Beta1 yes.
9.0.1.Beta1 probably yes too, but not sure we will release 9.0.1. It's 
possible that we will release 9.1.0 Only. Anyway 9.1.0 will use 4.3.x 
branch so, we can have both 9.0.1.Beta1 and 9.1.0.Beta1 and if we don't 
release 9.0.1 we will move all 9.0.1 issues to 9.1.0.

On 10/14/2015 02:22 PM, Denis Golovin wrote:
> Should we create specific development versions for 4.3.x/9.0.x streams 
> in JIRA?
> Something like:
> - 4.3.1.Beta1
> - 9.0.1.Beta1
>
> Then we can use it in fixed issues.
>
> Currently I see only 4.3.1.Final and 9.0.1.GA <http://9.0.1.GA> are 
> available.
>
> Denis
>
>
> On Fri, Oct 9, 2015 at 9:41 AM, Alexey Kazakov <alkazako at redhat.com 
> <mailto:alkazako at redhat.com>> wrote:
>
>     Hi all,
>
>     Please make sure when you are fixing anything in both 4.3.x and master
>     branches, create a separate issue for every stream. So we will
>     have two
>     JIRAs (the original one + a clone), one for 4.4.0 and the second
>     one for
>     4.3.0.
>     It will help QE to verify the issue is fixed in both streams. Remember
>     we have different cycles for maintenance and main releases.
>     It's OK to have multiple fix versions in one JIRA while you are
>     working
>     on it. It's NOT OK to resolve an issue with the only fix version
>     and w/o
>     a clone while applying a PR to both streams!
>
>     Thanks.
>     _______________________________________________
>     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
>
>     --
>
>
>     CONFIDENTIALITY NOTICE: This email and files attached to it are
>     confidential. If you are not the intended recipient you are hereby
>     notified
>     that using, copying, distributing or taking any action in reliance
>     on the
>     contents of this information is strictly prohibited. If you have
>     received
>     this email in error please notify the sender and delete this email.
>
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are 
> confidential. If you are not the intended recipient you are hereby 
> notified that using, copying, distributing or taking any action in 
> reliance on the contents of this information is strictly prohibited. 
> If you have received this email in error please notify the sender and 
> delete this email.
>

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

From fbricon at redhat.com  Wed Oct 14 15:06:52 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Wed, 14 Oct 2015 15:06:52 -0400
Subject: [jbosstools-dev] Fixing in both 4.3.x and master
In-Reply-To: <561E9F16.8060708@redhat.com>
References: <5617EE24.1090904@redhat.com>
	<CAJXFskZDjp_dMCy5HfGQ2_sCcfq4=pVauCc6XKBxxoZ9wTeSxw@mail.gmail.com>
	<561E9F16.8060708@redhat.com>
Message-ID: <CACvX+KhiLFn5PDMqJ4SvR9BWr77Lw4bRGgWyD_6N6cKBNXo-sg@mail.gmail.com>

Can we rename 9.0.1.Beta1 to 9.1.0.Beta1 in JIRA, if need be?

On Wed, Oct 14, 2015 at 2:29 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

> 4.3.1.Beta1 yes.
> 9.0.1.Beta1 probably yes too, but not sure we will release 9.0.1. It's
> possible that we will release 9.1.0 Only. Anyway 9.1.0 will use 4.3.x
> branch so, we can have both 9.0.1.Beta1 and 9.1.0.Beta1 and if we don't
> release 9.0.1 we will move all 9.0.1 issues to 9.1.0.
>
>
> On 10/14/2015 02:22 PM, Denis Golovin wrote:
>
> Should we create specific development versions for 4.3.x/9.0.x streams in
> JIRA?
> Something like:
> - 4.3.1.Beta1
> - 9.0.1.Beta1
>
> Then we can use it in fixed issues.
>
> Currently I see only 4.3.1.Final and 9.0.1.GA are available.
>
> Denis
>
>
> On Fri, Oct 9, 2015 at 9:41 AM, Alexey Kazakov <alkazako at redhat.com>
> wrote:
>
>> Hi all,
>>
>> Please make sure when you are fixing anything in both 4.3.x and master
>> branches, create a separate issue for every stream. So we will have two
>> JIRAs (the original one + a clone), one for 4.4.0 and the second one for
>> 4.3.0.
>> It will help QE to verify the issue is fixed in both streams. Remember
>> we have different cycles for maintenance and main releases.
>> It's OK to have multiple fix versions in one JIRA while you are working
>> on it. It's NOT OK to resolve an issue with the only fix version and w/o
>> a clone while applying a PR to both streams!
>>
>> Thanks.
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> --
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby
>> notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>>
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>
>
>
> _______________________________________________
> 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/20151014/8232df85/attachment.html 

From alkazako at redhat.com  Wed Oct 14 15:39:39 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Wed, 14 Oct 2015 15:39:39 -0400
Subject: [jbosstools-dev] Fixing in both 4.3.x and master
In-Reply-To: <CACvX+KhiLFn5PDMqJ4SvR9BWr77Lw4bRGgWyD_6N6cKBNXo-sg@mail.gmail.com>
References: <5617EE24.1090904@redhat.com>
	<CAJXFskZDjp_dMCy5HfGQ2_sCcfq4=pVauCc6XKBxxoZ9wTeSxw@mail.gmail.com>
	<561E9F16.8060708@redhat.com>
	<CACvX+KhiLFn5PDMqJ4SvR9BWr77Lw4bRGgWyD_6N6cKBNXo-sg@mail.gmail.com>
Message-ID: <561EAF7B.2040306@redhat.com>

9.1.0 is something we would want to release for Mars.2 (February/March 
2016).
9.0.1 is something we could release earlier if we find critical issues 
in 9.0.0.GA
But according to Max's statistic report users don't care much if we call 
our builds Alphas/Betas/CRs or GA/Final. It means it doesn't make much 
sense to release 9.0.1.Final close to 9.1.0.Beta.

So, my proposal would be:
1. Plan to release 9.1.0.Beta1 in Xmas and 9.1.0.GA around Eclipse 
Mars.2 (February/March 2016)
2. If we find any critical issue in 9.0.0.GA we want to fix earlier we 
could release 9.0.1 in November.

If it's OK I would move all current 9.0.1 issues to 9.1.0.Beta1. And 
remove 9.0.1 not to confuse devs and QE. If we have any critical issues 
and we see that we need release 9.0.1 then we will create this version 
in JIRA.

WDYT?

On 10/14/2015 03:06 PM, Fred Bricon wrote:
> Can we rename 9.0.1.Beta1 to 9.1.0.Beta1 in JIRA, if need be?
>
> On Wed, Oct 14, 2015 at 2:29 PM, Alexey Kazakov <alkazako at redhat.com 
> <mailto:alkazako at redhat.com>> wrote:
>
>     4.3.1.Beta1 yes.
>     9.0.1.Beta1 probably yes too, but not sure we will release 9.0.1.
>     It's possible that we will release 9.1.0 Only. Anyway 9.1.0 will
>     use 4.3.x branch so, we can have both 9.0.1.Beta1 and 9.1.0.Beta1
>     and if we don't release 9.0.1 we will move all 9.0.1 issues to 9.1.0.
>
>
>     On 10/14/2015 02:22 PM, Denis Golovin wrote:
>>     Should we create specific development versions for 4.3.x/9.0.x
>>     streams in JIRA?
>>     Something like:
>>     - 4.3.1.Beta1
>>     - 9.0.1.Beta1
>>
>>     Then we can use it in fixed issues.
>>
>>     Currently I see only 4.3.1.Final and 9.0.1.GA <http://9.0.1.GA>
>>     are available.
>>
>>     Denis
>>
>>
>>     On Fri, Oct 9, 2015 at 9:41 AM, Alexey Kazakov
>>     <alkazako at redhat.com <mailto:alkazako at redhat.com>> wrote:
>>
>>         Hi all,
>>
>>         Please make sure when you are fixing anything in both 4.3.x
>>         and master
>>         branches, create a separate issue for every stream. So we
>>         will have two
>>         JIRAs (the original one + a clone), one for 4.4.0 and the
>>         second one for
>>         4.3.0.
>>         It will help QE to verify the issue is fixed in both streams.
>>         Remember
>>         we have different cycles for maintenance and main releases.
>>         It's OK to have multiple fix versions in one JIRA while you
>>         are working
>>         on it. It's NOT OK to resolve an issue with the only fix
>>         version and w/o
>>         a clone while applying a PR to both streams!
>>
>>         Thanks.
>>         _______________________________________________
>>         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
>>
>>         --
>>
>>
>>         CONFIDENTIALITY NOTICE: This email and files attached to it are
>>         confidential. If you are not the intended recipient you are
>>         hereby notified
>>         that using, copying, distributing or taking any action in
>>         reliance on the
>>         contents of this information is strictly prohibited. If you
>>         have received
>>         this email in error please notify the sender and delete this
>>         email.
>>
>>
>>
>>     CONFIDENTIALITY NOTICE: This email and files attached to it are
>>     confidential. If you are not the intended recipient you are
>>     hereby notified that using, copying, distributing or taking any
>>     action in reliance on the contents of this information is
>>     strictly prohibited. If you have received this email in error
>>     please notify the sender and delete this email.
>>
>
>
>     _______________________________________________
>     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
>
>

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

From nboldt at redhat.com  Wed Oct 14 16:14:31 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 14 Oct 2015 16:14:31 -0400
Subject: [jbosstools-dev] Fixing in both 4.3.x and master
In-Reply-To: <561EAF7B.2040306@redhat.com>
References: <5617EE24.1090904@redhat.com>
	<CAJXFskZDjp_dMCy5HfGQ2_sCcfq4=pVauCc6XKBxxoZ9wTeSxw@mail.gmail.com>
	<561E9F16.8060708@redhat.com>
	<CACvX+KhiLFn5PDMqJ4SvR9BWr77Lw4bRGgWyD_6N6cKBNXo-sg@mail.gmail.com>
	<561EAF7B.2040306@redhat.com>
Message-ID: <CA+QcL118LFA=x_FKm_+Gg1VojjjtQoi=7RVmtJ=2qnLNnpuABA@mail.gmail.com>

+1: 9.0.1.* issues move/rename to 9.1.0.Beta1 (Xmas), with 9.1.0.GA in March.

---

If we decide we need a 9.0.1 release in November, here's how that will
align JBT/JBDS:

* 4.3.1.Final as input to 9.0.1.GA,
* 4.3.2.Beta1 as input to 9.1.0.Beta1, and
* 4.3.2.Final as input to 9.1.0.GA.

So it's doable, but would result in having to backlevel JBDS from its
current 9.1.0 versioning.

Is this a likely scenario? Should I call what's in 4.3.x branch
9.0.1.CR1 instead of 9.1.0?

On Wed, Oct 14, 2015 at 3:39 PM, Alexey Kazakov <alkazako at redhat.com> wrote:
> 9.1.0 is something we would want to release for Mars.2 (February/March
> 2016).
> 9.0.1 is something we could release earlier if we find critical issues in
> 9.0.0.GA
> But according to Max's statistic report users don't care much if we call our
> builds Alphas/Betas/CRs or GA/Final. It means it doesn't make much sense to
> release 9.0.1.Final close to 9.1.0.Beta.
>
> So, my proposal would be:
> 1. Plan to release 9.1.0.Beta1 in Xmas and 9.1.0.GA around Eclipse Mars.2
> (February/March 2016)
> 2. If we find any critical issue in 9.0.0.GA we want to fix earlier we could
> release 9.0.1 in November.
>
> If it's OK I would move all current 9.0.1 issues to 9.1.0.Beta1. And remove
> 9.0.1 not to confuse devs and QE. If we have any critical issues and we see
> that we need release 9.0.1 then we will create this version in JIRA.
>
> WDYT?
>
>
> On 10/14/2015 03:06 PM, Fred Bricon wrote:
>
> Can we rename 9.0.1.Beta1 to 9.1.0.Beta1 in JIRA, if need be?
>
> On Wed, Oct 14, 2015 at 2:29 PM, Alexey Kazakov <alkazako at redhat.com> wrote:
>>
>> 4.3.1.Beta1 yes.
>> 9.0.1.Beta1 probably yes too, but not sure we will release 9.0.1. It's
>> possible that we will release 9.1.0 Only. Anyway 9.1.0 will use 4.3.x branch
>> so, we can have both 9.0.1.Beta1 and 9.1.0.Beta1 and if we don't release
>> 9.0.1 we will move all 9.0.1 issues to 9.1.0.
>>
>>
>> On 10/14/2015 02:22 PM, Denis Golovin wrote:
>>
>> Should we create specific development versions for 4.3.x/9.0.x streams in
>> JIRA?
>> Something like:
>> - 4.3.1.Beta1
>> - 9.0.1.Beta1
>>
>> Then we can use it in fixed issues.
>>
>> Currently I see only 4.3.1.Final and 9.0.1.GA are available.
>>
>> Denis
>>
>>
>> On Fri, Oct 9, 2015 at 9:41 AM, Alexey Kazakov <alkazako at redhat.com>
>> wrote:
>>>
>>> Hi all,
>>>
>>> Please make sure when you are fixing anything in both 4.3.x and master
>>> branches, create a separate issue for every stream. So we will have two
>>> JIRAs (the original one + a clone), one for 4.4.0 and the second one for
>>> 4.3.0.
>>> It will help QE to verify the issue is fixed in both streams. Remember
>>> we have different cycles for maintenance and main releases.
>>> It's OK to have multiple fix versions in one JIRA while you are working
>>> on it. It's NOT OK to resolve an issue with the only fix version and w/o
>>> a clone while applying a PR to both streams!
>>>
>>> Thanks.
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> --
>>>
>>>
>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>> confidential. If you are not the intended recipient you are hereby
>>> notified
>>> that using, copying, distributing or taking any action in reliance on the
>>> contents of this information is strictly prohibited. If you have received
>>> this email in error please notify the sender and delete this email.
>>
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>>
>>
>>
>> _______________________________________________
>> 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 rstryker at redhat.com  Wed Oct 14 17:33:00 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Wed, 14 Oct 2015 17:33:00 -0400
Subject: [jbosstools-dev] ds_ filters all empty?
In-Reply-To: <312BE62A-40AA-4564-A27F-87B3FD90555C@redhat.com>
References: <561C1527.3020309@redhat.com>	<CA+QcL13XFsJSHSq2PG8pXtJgALHTr+29zL-x=xuEyQSV52HwHg@mail.gmail.com>	<561D16B7.80703@redhat.com>	<BFFA8735-F293-42F4-8BB9-15835097C2E0@redhat.com>	<561D6929.9070409@redhat.com>	<CA+QcL10b9UnU_PEFsMKdZLXOtY2pFtDRTG+s8QGqsNRtV9Lg+Q@mail.gmail.com>
	<312BE62A-40AA-4564-A27F-87B3FD90555C@redhat.com>
Message-ID: <561ECA0C.1050300@redhat.com>





On 10/14/2015 03:46 AM, Max Rydahl Andersen wrote:
> jira had issues yesterday so they couldn't run. I reran them now and 
> on first glance works. Rob, please open bugs with specifics (like 
> exact filter name) if still broken for you. /max 

The following filters dont work for me:
     - ds_my_next_maint_unresolved
     - ds_my_next_master_unresolved


Not sure which component I should open these bugs for?


>>
>> On Tue, Oct 13, 2015 at 4:27 PM, Rob Stryker <rstryker at redhat.com>
>> wrote:
>>> On 10/13/2015 12:49 PM, Max Rydahl Andersen wrote:
>>>> GA was not released until well, last thursday
>>>> so it is not a 3 weeks issue.
>>> It is a 3-week issue for anyone who was done with their branch 3
>>> weeks ago
>>> and wished to move on to 4.3.1 or 4.4.0.  Sure, it's a one-week issue
>>> if you
>>> assume everyone's been 100% dedicated to releasing 4.3.0.Final until
>>> last
>>> Thursday, but this obviously isn't true. There were definitely people
>>> who
>>> finished with 4.3.0 before last Thursday.
>>>
>>>> you are currently the only one using these in a dashboard afaik so
>>>> the
>>>> issue was not seen.
>>> Maybe I should just go back to my own filters then, unless there's a
>>> commitment to make these filters useful during release process. I
>>> only
>>> switched because I was told these would be updated and are
>>> recommended.
>>
>>
>> -- 
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From nboldt at redhat.com  Wed Oct 14 18:30:55 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 14 Oct 2015 18:30:55 -0400
Subject: [jbosstools-dev] ds_ filters all empty?
In-Reply-To: <561ECA0C.1050300@redhat.com>
References: <561C1527.3020309@redhat.com>
	<CA+QcL13XFsJSHSq2PG8pXtJgALHTr+29zL-x=xuEyQSV52HwHg@mail.gmail.com>
	<561D16B7.80703@redhat.com>
	<BFFA8735-F293-42F4-8BB9-15835097C2E0@redhat.com>
	<561D6929.9070409@redhat.com>
	<CA+QcL10b9UnU_PEFsMKdZLXOtY2pFtDRTG+s8QGqsNRtV9Lg+Q@mail.gmail.com>
	<312BE62A-40AA-4564-A27F-87B3FD90555C@redhat.com>
	<561ECA0C.1050300@redhat.com>
Message-ID: <CA+QcL10r=T-5ReDA=6kzKFX3xMUBvRNKLZSgVvSXY1y7UA-YZA@mail.gmail.com>

There is no matching component so just use project = JBIDE, component
= build and assign to @maxandersen. You could use a label of
"releasework" or "processwork" or "whyisthisonlyinmaxsfork". :D



On Wed, Oct 14, 2015 at 5:33 PM, Rob Stryker <rstryker at redhat.com> wrote:
>
>
>
>
> On 10/14/2015 03:46 AM, Max Rydahl Andersen wrote:
>> jira had issues yesterday so they couldn't run. I reran them now and
>> on first glance works. Rob, please open bugs with specifics (like
>> exact filter name) if still broken for you. /max
>
> The following filters dont work for me:
>      - ds_my_next_maint_unresolved
>      - ds_my_next_master_unresolved
>
>
> Not sure which component I should open these bugs for?
>
>
>>>
>>> On Tue, Oct 13, 2015 at 4:27 PM, Rob Stryker <rstryker at redhat.com>
>>> wrote:
>>>> On 10/13/2015 12:49 PM, Max Rydahl Andersen wrote:
>>>>> GA was not released until well, last thursday
>>>>> so it is not a 3 weeks issue.
>>>> It is a 3-week issue for anyone who was done with their branch 3
>>>> weeks ago
>>>> and wished to move on to 4.3.1 or 4.4.0.  Sure, it's a one-week issue
>>>> if you
>>>> assume everyone's been 100% dedicated to releasing 4.3.0.Final until
>>>> last
>>>> Thursday, but this obviously isn't true. There were definitely people
>>>> who
>>>> finished with 4.3.0 before last Thursday.
>>>>
>>>>> you are currently the only one using these in a dashboard afaik so
>>>>> the
>>>>> issue was not seen.
>>>> Maybe I should just go back to my own filters then, unless there's a
>>>> commitment to make these filters useful during release process. I
>>>> only
>>>> switched because I was told these would be updated and are
>>>> recommended.
>>>
>>>
>>> --
>>> Nick Boldt :: JBoss by Red Hat
>>> Productization Lead :: JBoss Tools & Dev Studio
>>> http://nick.divbyzero.com
>>
>> /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



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

From manderse at redhat.com  Thu Oct 15 03:22:51 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 15 Oct 2015 09:22:51 +0200
Subject: [jbosstools-dev] Fixing in both 4.3.x and master
In-Reply-To: <CACvX+KhiLFn5PDMqJ4SvR9BWr77Lw4bRGgWyD_6N6cKBNXo-sg@mail.gmail.com>
References: <5617EE24.1090904@redhat.com>
	<CAJXFskZDjp_dMCy5HfGQ2_sCcfq4=pVauCc6XKBxxoZ9wTeSxw@mail.gmail.com>
	<561E9F16.8060708@redhat.com>
	<CACvX+KhiLFn5PDMqJ4SvR9BWr77Lw4bRGgWyD_6N6cKBNXo-sg@mail.gmail.com>
Message-ID: <5938CB72-C032-4C97-BE71-614366FA2FE4@redhat.com>

On 14 Oct 2015, at 21:06, Fred Bricon wrote:

> Can we rename 9.0.1.Beta1 to 9.1.0.Beta1 in JIRA, if need be?

Yes, this is much easier than to go from 9.1.0.Beta1 to 9.0.1.Beta.

/max

> On Wed, Oct 14, 2015 at 2:29 PM, Alexey Kazakov <alkazako at redhat.com> 
> wrote:
>
>> 4.3.1.Beta1 yes.
>> 9.0.1.Beta1 probably yes too, but not sure we will release 9.0.1. 
>> It's
>> possible that we will release 9.1.0 Only. Anyway 9.1.0 will use 4.3.x
>> branch so, we can have both 9.0.1.Beta1 and 9.1.0.Beta1 and if we 
>> don't
>> release 9.0.1 we will move all 9.0.1 issues to 9.1.0.
>>
>>
>> On 10/14/2015 02:22 PM, Denis Golovin wrote:
>>
>> Should we create specific development versions for 4.3.x/9.0.x 
>> streams in
>> JIRA?
>> Something like:
>> - 4.3.1.Beta1
>> - 9.0.1.Beta1
>>
>> Then we can use it in fixed issues.
>>
>> Currently I see only 4.3.1.Final and 9.0.1.GA are available.
>>
>> Denis
>>
>>
>> On Fri, Oct 9, 2015 at 9:41 AM, Alexey Kazakov <alkazako at redhat.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> Please make sure when you are fixing anything in both 4.3.x and 
>>> master
>>> branches, create a separate issue for every stream. So we will have 
>>> two
>>> JIRAs (the original one + a clone), one for 4.4.0 and the second one 
>>> for
>>> 4.3.0.
>>> It will help QE to verify the issue is fixed in both streams. 
>>> Remember
>>> we have different cycles for maintenance and main releases.
>>> It's OK to have multiple fix versions in one JIRA while you are 
>>> working
>>> on it. It's NOT OK to resolve an issue with the only fix version and 
>>> w/o
>>> a clone while applying a PR to both streams!
>>>
>>> Thanks.
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> --
>>>
>>>
>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>> confidential. If you are not the intended recipient you are hereby
>>> notified
>>> that using, copying, distributing or taking any action in reliance 
>>> on the
>>> contents of this information is strictly prohibited. If you have 
>>> received
>>> this email in error please notify the sender and delete this email.
>>>
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby 
>> notified
>> that using, copying, distributing or taking any action in reliance on 
>> the
>> contents of this information is strictly prohibited. If you have 
>> received
>> this email in error please notify the sender and delete this email.
>>
>>
>>
>> _______________________________________________
>> 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 manderse at redhat.com  Thu Oct 15 03:24:37 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 15 Oct 2015 09:24:37 +0200
Subject: [jbosstools-dev] Fixing in both 4.3.x and master
In-Reply-To: <CA+QcL118LFA=x_FKm_+Gg1VojjjtQoi=7RVmtJ=2qnLNnpuABA@mail.gmail.com>
References: <5617EE24.1090904@redhat.com>
	<CAJXFskZDjp_dMCy5HfGQ2_sCcfq4=pVauCc6XKBxxoZ9wTeSxw@mail.gmail.com>
	<561E9F16.8060708@redhat.com>
	<CACvX+KhiLFn5PDMqJ4SvR9BWr77Lw4bRGgWyD_6N6cKBNXo-sg@mail.gmail.com>
	<561EAF7B.2040306@redhat.com>
	<CA+QcL118LFA=x_FKm_+Gg1VojjjtQoi=7RVmtJ=2qnLNnpuABA@mail.gmail.com>
Message-ID: <EECF88FF-BF27-4B51-A5DA-AAA7027BE515@redhat.com>

On 14 Oct 2015, at 22:14, Nick Boldt wrote:

> +1: 9.0.1.* issues move/rename to 9.1.0.Beta1 (Xmas), with 9.1.0.GA in 
> March.
>
> ---
>
> If we decide we need a 9.0.1 release in November, here's how that will
> align JBT/JBDS:
>
> * 4.3.1.Final as input to 9.0.1.GA,
> * 4.3.2.Beta1 as input to 9.1.0.Beta1, and
> * 4.3.2.Final as input to 9.1.0.GA.
>
> So it's doable, but would result in having to backlevel JBDS from its
> current 9.1.0 versioning.

If this happens 9.1 would still exist and we would be probably be 
branching of the 9.0 tag.

> Is this a likely scenario? Should I call what's in 4.3.x branch
> 9.0.1.CR1 instead of 9.1.0?

Much easier to avoid back-pedalling imo - so I would say call it 9.0.1 
until we know for are sure we'll do 9.1 first.


/max

>
> On Wed, Oct 14, 2015 at 3:39 PM, Alexey Kazakov <alkazako at redhat.com> 
> wrote:
>> 9.1.0 is something we would want to release for Mars.2 
>> (February/March
>> 2016).
>> 9.0.1 is something we could release earlier if we find critical 
>> issues in
>> 9.0.0.GA
>> But according to Max's statistic report users don't care much if we 
>> call our
>> builds Alphas/Betas/CRs or GA/Final. It means it doesn't make much 
>> sense to
>> release 9.0.1.Final close to 9.1.0.Beta.
>>
>> So, my proposal would be:
>> 1. Plan to release 9.1.0.Beta1 in Xmas and 9.1.0.GA around Eclipse 
>> Mars.2
>> (February/March 2016)
>> 2. If we find any critical issue in 9.0.0.GA we want to fix earlier 
>> we could
>> release 9.0.1 in November.
>>
>> If it's OK I would move all current 9.0.1 issues to 9.1.0.Beta1. And 
>> remove
>> 9.0.1 not to confuse devs and QE. If we have any critical issues and 
>> we see
>> that we need release 9.0.1 then we will create this version in JIRA.
>>
>> WDYT?
>>
>>
>> On 10/14/2015 03:06 PM, Fred Bricon wrote:
>>
>> Can we rename 9.0.1.Beta1 to 9.1.0.Beta1 in JIRA, if need be?
>>
>> On Wed, Oct 14, 2015 at 2:29 PM, Alexey Kazakov <alkazako at redhat.com> 
>> wrote:
>>>
>>> 4.3.1.Beta1 yes.
>>> 9.0.1.Beta1 probably yes too, but not sure we will release 9.0.1. 
>>> It's
>>> possible that we will release 9.1.0 Only. Anyway 9.1.0 will use 
>>> 4.3.x branch
>>> so, we can have both 9.0.1.Beta1 and 9.1.0.Beta1 and if we don't 
>>> release
>>> 9.0.1 we will move all 9.0.1 issues to 9.1.0.
>>>
>>>
>>> On 10/14/2015 02:22 PM, Denis Golovin wrote:
>>>
>>> Should we create specific development versions for 4.3.x/9.0.x 
>>> streams in
>>> JIRA?
>>> Something like:
>>> - 4.3.1.Beta1
>>> - 9.0.1.Beta1
>>>
>>> Then we can use it in fixed issues.
>>>
>>> Currently I see only 4.3.1.Final and 9.0.1.GA are available.
>>>
>>> Denis
>>>
>>>
>>> On Fri, Oct 9, 2015 at 9:41 AM, Alexey Kazakov <alkazako at redhat.com>
>>> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Please make sure when you are fixing anything in both 4.3.x and 
>>>> master
>>>> branches, create a separate issue for every stream. So we will have 
>>>> two
>>>> JIRAs (the original one + a clone), one for 4.4.0 and the second 
>>>> one for
>>>> 4.3.0.
>>>> It will help QE to verify the issue is fixed in both streams. 
>>>> Remember
>>>> we have different cycles for maintenance and main releases.
>>>> It's OK to have multiple fix versions in one JIRA while you are 
>>>> working
>>>> on it. It's NOT OK to resolve an issue with the only fix version 
>>>> and w/o
>>>> a clone while applying a PR to both streams!
>>>>
>>>> Thanks.
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>> --
>>>>
>>>>
>>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>>> confidential. If you are not the intended recipient you are hereby
>>>> notified
>>>> that using, copying, distributing or taking any action in reliance 
>>>> on the
>>>> contents of this information is strictly prohibited. If you have 
>>>> received
>>>> this email in error please notify the sender and delete this email.
>>>
>>>
>>>
>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>> confidential. If you are not the intended recipient you are hereby 
>>> notified
>>> that using, copying, distributing or taking any action in reliance 
>>> on the
>>> contents of this information is strictly prohibited. If you have 
>>> received
>>> this email in error please notify the sender and delete this email.
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
> _______________________________________________
> 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  Thu Oct 15 03:30:30 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 15 Oct 2015 09:30:30 +0200
Subject: [jbosstools-dev] please keep order in jira versions
Message-ID: <90D75570-E681-42BE-BD01-D9C0713F72A4@redhat.com>

Hey jira-admins that isn't me,

jira don't let me know who changed jira versions but jiralint got all 
confused by whatever latest changes that are there - so I have to send 
out this broader message.

a) if you create a new jira version - please place it in the right order

i.e.: 9.0.1.Beta is *before* 9.1.0.Final, not the other way around.
If this is not upheld version range comparison in jira and jiralint 
falls apart.

b) have *one* version with a start date in both master and branch 
version stream.

The start date are used to indicate if this is where work is going on.
If not set, jiralint thinks no work is happening and implodes on itself.

c) please don't have one version in JBIDE and no match in JBDS

This does not break anything, except it makes it freaking hard for 
humans to
actually see what lines up.


I've fixed what I could find now so the order is right and for each 
version in JBDS there is one in JBIDE and vice versa.

btw. no idea what 9.0.x is about vs 9.x ... do we really need 9.0.x too 
?
/max
http://about.me/maxandersen

From manderse at redhat.com  Thu Oct 15 03:42:16 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 15 Oct 2015 09:42:16 +0200
Subject: [jbosstools-dev] Fixing in both 4.3.x and master
In-Reply-To: <561EAF7B.2040306@redhat.com>
References: <5617EE24.1090904@redhat.com>
	<CAJXFskZDjp_dMCy5HfGQ2_sCcfq4=pVauCc6XKBxxoZ9wTeSxw@mail.gmail.com>
	<561E9F16.8060708@redhat.com>
	<CACvX+KhiLFn5PDMqJ4SvR9BWr77Lw4bRGgWyD_6N6cKBNXo-sg@mail.gmail.com>
	<561EAF7B.2040306@redhat.com>
Message-ID: <E710F0E4-7328-4507-A04C-520D4C483854@redhat.com>


> But according to Max's statistic report users don't care much if we 
> call our builds Alphas/Betas/CRs or GA/Final.

This is *not* what the statistic said.

I wrote:

"It does not seem to matter wether we call our release Alpha, Beta, CR 
or GA - users install our matching version when it is available for the 
eclipse version they move to."

This was given in context of ping backs from what gets installed.

Users install the jboss tools version that matches Eclipse GA, probably 
via eclipse marketplace.

This means GA is damn important - most users don't want to install jboss 
tools on Eclipse pre-GA.

What it does indicate though is that *users* does not seem to realise 
jboss tools is in alpha/beta/etc. If Eclipse is GA then they need 
whatever jboss tools has that matches.

But this ignores completely that we also have "users" like 
integration-stack that needs API stable releases.

The users also needs this, but they rarely notice it is an issue since 
we rebuild the core always so it works together and we somewhat tries to 
ensure we don't break workspace metadata support.

So please, do not translate that statistic into alpha/betas does not 
matter - the statistic implies that *more* Finals would probably be okey 
- users pick up our updates as they become available on the updatesite 
they have enabled.


More finals != do more milestones.

More Finals = more stable releases = more testing needed = more 
automation need.

> It means it doesn't make much sense to release 9.0.1.Final close to 
> 9.1.0.Beta.

It could be. Remember we have /stable and /development update sites to 
handle this.

When we release 9.1.0.Beta onto /development, the GA users won't get 
those fixes automatically.

A release to 9.0.1.Final is what would happen on /stable


I don't think we have done this kind of branching before, but it would 
be a sensible thing to do if we had the automated testing and automation 
in place.

> So, my proposal would be:
> 1. Plan to release 9.1.0.Beta1 in Xmas and 9.1.0.GA around Eclipse 
> Mars.2 (February/March 2016)
> 2. If we find any critical issue in 9.0.0.GA we want to fix earlier we 
> could release 9.0.1 in November.
>
> If it's OK I would move all current 9.0.1 issues to 9.1.0.Beta1. And 
> remove 9.0.1 not to confuse devs and QE. If we have any critical 
> issues and we see that we need release 9.0.1 then we will create this 
> version in JIRA.
>
> WDYT?

I would first outline the work we expect to go into it.

Call it 9.0.1 for now, do the rename (and possible branch) if/when 
needed.

Then there is no back pedalling of versions happening at osgi version. 
Only forward version jumps.

/max

> On 10/14/2015 03:06 PM, Fred Bricon wrote:
>> Can we rename 9.0.1.Beta1 to 9.1.0.Beta1 in JIRA, if need be?
>>
>> On Wed, Oct 14, 2015 at 2:29 PM, Alexey Kazakov <alkazako at redhat.com 
>> <mailto:alkazako at redhat.com>> wrote:
>>
>> 4.3.1.Beta1 yes.
>> 9.0.1.Beta1 probably yes too, but not sure we will release 9.0.1.
>> It's possible that we will release 9.1.0 Only. Anyway 9.1.0 will
>> use 4.3.x branch so, we can have both 9.0.1.Beta1 and 9.1.0.Beta1
>> and if we don't release 9.0.1 we will move all 9.0.1 issues to 9.1.0.
>>
>>
>> On 10/14/2015 02:22 PM, Denis Golovin wrote:
>>> Should we create specific development versions for 4.3.x/9.0.x
>>> streams in JIRA?
>>> Something like:
>>> - 4.3.1.Beta1
>>> - 9.0.1.Beta1
>>>
>>> Then we can use it in fixed issues.
>>>
>>> Currently I see only 4.3.1.Final and 9.0.1.GA <http://9.0.1.GA>
>>> are available.
>>>
>>> Denis
>>>
>>>
>>> On Fri, Oct 9, 2015 at 9:41 AM, Alexey Kazakov
>>> <alkazako at redhat.com <mailto:alkazako at redhat.com>> wrote:
>>>
>>>     Hi all,
>>>
>>>     Please make sure when you are fixing anything in both 4.3.x
>>>     and master
>>>     branches, create a separate issue for every stream. So we
>>>     will have two
>>>     JIRAs (the original one + a clone), one for 4.4.0 and the
>>>     second one for
>>>     4.3.0.
>>>     It will help QE to verify the issue is fixed in both streams.
>>>     Remember
>>>     we have different cycles for maintenance and main releases.
>>>     It's OK to have multiple fix versions in one JIRA while you
>>>     are working
>>>     on it. It's NOT OK to resolve an issue with the only fix
>>>     version and w/o
>>>     a clone while applying a PR to both streams!
>>>
>>>     Thanks.
>>>     _______________________________________________
>>>     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
>>>
>>>     --
>>>
>>>
>>>     CONFIDENTIALITY NOTICE: This email and files attached to it are
>>>     confidential. If you are not the intended recipient you are
>>>     hereby notified
>>>     that using, copying, distributing or taking any action in
>>>     reliance on the
>>>     contents of this information is strictly prohibited. If you
>>>     have received
>>>     this email in error please notify the sender and delete this
>>>     email.
>>>
>>>
>>>
>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>> confidential. If you are not the intended recipient you are
>>> hereby notified that using, copying, distributing or taking any
>>> action in reliance on the contents of this information is
>>> strictly prohibited. If you have received this email in error
>>> please notify the sender and delete this email.
>>>
>>
>>
>> _______________________________________________
>> 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


/max
http://about.me/maxandersen

From alkazako at redhat.com  Thu Oct 15 08:16:28 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Thu, 15 Oct 2015 08:16:28 -0400
Subject: [jbosstools-dev] please keep order in jira versions
In-Reply-To: <90D75570-E681-42BE-BD01-D9C0713F72A4@redhat.com>
References: <90D75570-E681-42BE-BD01-D9C0713F72A4@redhat.com>
Message-ID: <561F991C.1070607@redhat.com>

I created JBT 4.3.1.Beta1 before JBT 4.3.1.Final with a start date. I 
didn't create JBDS 9.0.1.Beta.

We would need 9.0.x if we wanted to release 9.0.2/3/... working on 9.1.x 
stream in the same time but I'm hopping we won't make it even more 
complicated and confusing.
Let's remove 9.0.x and use 9.x for any issues we are considering to fix 
for Mars but not in 9.1.0 or 9.0.1.


On 10/15/2015 03:30 AM, Max Rydahl Andersen wrote:
> Hey jira-admins that isn't me,
>
> jira don't let me know who changed jira versions but jiralint got all
> confused by whatever latest changes that are there - so I have to send
> out this broader message.
>
> a) if you create a new jira version - please place it in the right order
>
> i.e.: 9.0.1.Beta is *before* 9.1.0.Final, not the other way around.
> If this is not upheld version range comparison in jira and jiralint
> falls apart.
>
> b) have *one* version with a start date in both master and branch
> version stream.
>
> The start date are used to indicate if this is where work is going on.
> If not set, jiralint thinks no work is happening and implodes on itself.
>
> c) please don't have one version in JBIDE and no match in JBDS
>
> This does not break anything, except it makes it freaking hard for
> humans to
> actually see what lines up.
>
>
> I've fixed what I could find now so the order is right and for each
> version in JBDS there is one in JBIDE and vice versa.
>
> btw. no idea what 9.0.x is about vs 9.x ... do we really need 9.0.x too
> ?
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From nboldt at redhat.com  Thu Oct 15 10:57:52 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 15 Oct 2015 10:57:52 -0400
Subject: [jbosstools-dev] please keep order in jira versions
In-Reply-To: <561F991C.1070607@redhat.com>
References: <90D75570-E681-42BE-BD01-D9C0713F72A4@redhat.com>
	<561F991C.1070607@redhat.com>
Message-ID: <CA+QcL10hQYYppVLCnRJibGBxWYCDefgRaw+macoKtJTvO4EbnA@mail.gmail.com>

Here's what I'd like to do in JBDS JIRA:

* remove 9.0.x fixversion; move 9.0.x issues into the 9.x fixversion
* remove 9.1.1.GA

Result is these 5 fixversions for 9.x:

9.0.1.Beta1, 9.0.1.GA, 9.1.0.Beta1, 9.1.0.GA, 9.x

For JBT we have these matching 5 fixversions:

4.3.1.Beta1, 4.3.1.Final, 4.3.2.Beta1, 4.3.2.Final, 4.3.x

*If we end up renaming* 9.0.1 to 9.1.0, then those fixversions would
be removed, and the issues would be moved to their matching 9.1.0
milestones:

* 9.0.1.Beta1 issues would move to 9.1.0.Beta1;
* 9.0.1.GA issues would move to 9.1.0.GA.

So say we all?




On Thu, Oct 15, 2015 at 8:16 AM, Alexey Kazakov <alkazako at redhat.com> wrote:
> I created JBT 4.3.1.Beta1 before JBT 4.3.1.Final with a start date. I
> didn't create JBDS 9.0.1.Beta.
>
> We would need 9.0.x if we wanted to release 9.0.2/3/... working on 9.1.x
> stream in the same time but I'm hopping we won't make it even more
> complicated and confusing.
> Let's remove 9.0.x and use 9.x for any issues we are considering to fix
> for Mars but not in 9.1.0 or 9.0.1.
>
>
> On 10/15/2015 03:30 AM, Max Rydahl Andersen wrote:
>> Hey jira-admins that isn't me,
>>
>> jira don't let me know who changed jira versions but jiralint got all
>> confused by whatever latest changes that are there - so I have to send
>> out this broader message.
>>
>> a) if you create a new jira version - please place it in the right order
>>
>> i.e.: 9.0.1.Beta is *before* 9.1.0.Final, not the other way around.
>> If this is not upheld version range comparison in jira and jiralint
>> falls apart.
>>
>> b) have *one* version with a start date in both master and branch
>> version stream.
>>
>> The start date are used to indicate if this is where work is going on.
>> If not set, jiralint thinks no work is happening and implodes on itself.
>>
>> c) please don't have one version in JBIDE and no match in JBDS
>>
>> This does not break anything, except it makes it freaking hard for
>> humans to
>> actually see what lines up.
>>
>>
>> I've fixed what I could find now so the order is right and for each
>> version in JBDS there is one in JBIDE and vice versa.
>>
>> btw. no idea what 9.0.x is about vs 9.x ... do we really need 9.0.x too
>> ?
>> /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



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

From nboldt at redhat.com  Thu Oct 15 11:02:19 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 15 Oct 2015 11:02:19 -0400
Subject: [jbosstools-dev] please keep order in jira versions
In-Reply-To: <561F991C.1070607@redhat.com>
References: <90D75570-E681-42BE-BD01-D9C0713F72A4@redhat.com>
	<561F991C.1070607@redhat.com>
Message-ID: <CA+QcL13Po-e7qFmj7QH_iiyoHDSx2dBtYxLnkApRrHChm9tRiQ@mail.gmail.com>

Here's what I'd like to do in JBDS JIRA:

* remove 9.0.x fixversion; move 9.0.x issues into the 9.x fixversion
* remove 9.1.1.GA

Result is these 5 fixversions for 9.x:

9.0.1.Beta1, 9.0.1.GA, 9.1.0.Beta1, 9.1.0.GA, 9.x

For JBT we have these matching 5 fixversions:

4.3.1.Beta1, 4.3.1.Final, 4.3.2.Beta1, 4.3.2.Final, 4.3.x

*If we end up renaming* 9.0.1 to 9.1.0, then those fixversions would
be removed, and the issues would be moved to their matching 9.1.0
milestones:

* 9.0.1.Beta1 issues would move to 9.1.0.Beta1;
* 9.0.1.GA issues would move to 9.1.0.GA.

So say we all?




On Thu, Oct 15, 2015 at 8:16 AM, Alexey Kazakov <alkazako at redhat.com> wrote:
> I created JBT 4.3.1.Beta1 before JBT 4.3.1.Final with a start date. I
> didn't create JBDS 9.0.1.Beta.
>
> We would need 9.0.x if we wanted to release 9.0.2/3/... working on 9.1.x
> stream in the same time but I'm hopping we won't make it even more
> complicated and confusing.
> Let's remove 9.0.x and use 9.x for any issues we are considering to fix
> for Mars but not in 9.1.0 or 9.0.1.
>
>
> On 10/15/2015 03:30 AM, Max Rydahl Andersen wrote:
>> Hey jira-admins that isn't me,
>>
>> jira don't let me know who changed jira versions but jiralint got all
>> confused by whatever latest changes that are there - so I have to send
>> out this broader message.
>>
>> a) if you create a new jira version - please place it in the right order
>>
>> i.e.: 9.0.1.Beta is *before* 9.1.0.Final, not the other way around.
>> If this is not upheld version range comparison in jira and jiralint
>> falls apart.
>>
>> b) have *one* version with a start date in both master and branch
>> version stream.
>>
>> The start date are used to indicate if this is where work is going on.
>> If not set, jiralint thinks no work is happening and implodes on itself.
>>
>> c) please don't have one version in JBIDE and no match in JBDS
>>
>> This does not break anything, except it makes it freaking hard for
>> humans to
>> actually see what lines up.
>>
>>
>> I've fixed what I could find now so the order is right and for each
>> version in JBDS there is one in JBIDE and vice versa.
>>
>> btw. no idea what 9.0.x is about vs 9.x ... do we really need 9.0.x too
>> ?
>> /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



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

From nboldt at redhat.com  Thu Oct 15 11:18:21 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 15 Oct 2015 11:18:21 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: use parent pom
 4.3.1.Beta1-SNAPSHOT in maintenance builds for JBT 4.3.1.Beta1
Message-ID: <CA+QcL13JeBGqmDSpuOA0DJd05x4Jzaz7hmMpO2qAUE53DO7qRg@mail.gmail.com>

If you expect to be doing 4.3.x maintenance work in your component,
see the JIRAs below and respond accordingly. You could even go a step
further: re-enable your job & kick it off so your changes are built
immediately.

If, on the other hand, you do NOT expect to be doing maintenance in
your component, please let Nick know via @-mention in your JIRA(s) (or
reply to this thread) so I can pull a stable release of your component
to use in future 4.3.x builds INSTEAD of including new CI builds.
(This is what we did for Portlet last year, since it was at end of
maintenance.)

Task JIRA created for this Beta1 milestone include:

Aerogear          : https://issues.jboss.org/browse/JBIDE-20948
Central Discovery : https://issues.jboss.org/browse/JBIDE-20949
VPE               : https://issues.jboss.org/browse/JBIDE-20950
Integration Tests : https://issues.jboss.org/browse/JBIDE-20951
Server            : https://issues.jboss.org/browse/JBIDE-20953
Hibernate         : https://issues.jboss.org/browse/JBIDE-20954
Base              : https://issues.jboss.org/browse/JBIDE-20955
OpenShift         : https://issues.jboss.org/browse/JBIDE-20956
Playground        : https://issues.jboss.org/browse/JBIDE-20957
JavaEE            : https://issues.jboss.org/browse/JBIDE-20958
JST               : https://issues.jboss.org/browse/JBIDE-20959
Forge             : https://issues.jboss.org/browse/JBIDE-20960
Birt              : https://issues.jboss.org/browse/JBIDE-20961
BrowserSim        : https://issues.jboss.org/browse/JBIDE-20962
Webservices       : https://issues.jboss.org/browse/JBIDE-20963
Arquillian        : https://issues.jboss.org/browse/JBIDE-20964
Freemarker        : https://issues.jboss.org/browse/JBIDE-20965
Central           : https://issues.jboss.org/browse/JBIDE-20966
LiveReload        : https://issues.jboss.org/browse/JBIDE-20967

JBDS              : https://issues.jboss.org/browse/JBDS-3545
JBoss Tools       : https://issues.jboss.org/browse/JBIDE-20947
build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc,
versionwatch: https://issues.jboss.org/browse/JBIDE-20952

--

Note that while the dates have NOT BEEN FINALIZED, there's a good
chance that this might happen:

2015/11/25 4.3.1.Beta1 target platform freeze
2015/11/26 4.3.1.Beta1 code freeze
2015/11/27 4.3.1.Beta1 staging build for QE (followed by a two week
test cycle w/ optional weekly respins as needed)
2015/12/15 4.3.1.Beta1 release

We are also still deciding if the JBDS release that will coincide with
the above dates will be 9.0.1.Beta1 or 9.1.0.Beta1.
Stay tuned for updates.


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

From alkazako at redhat.com  Thu Oct 15 12:23:25 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Thu, 15 Oct 2015 12:23:25 -0400
Subject: [jbosstools-dev] please keep order in jira versions
In-Reply-To: <CA+QcL10hQYYppVLCnRJibGBxWYCDefgRaw+macoKtJTvO4EbnA@mail.gmail.com>
References: <90D75570-E681-42BE-BD01-D9C0713F72A4@redhat.com>
	<561F991C.1070607@redhat.com>
	<CA+QcL10hQYYppVLCnRJibGBxWYCDefgRaw+macoKtJTvO4EbnA@mail.gmail.com>
Message-ID: <561FD2FD.3040806@redhat.com>

Looks good to me.

On 10/15/2015 10:57 AM, Nick Boldt wrote:
> Here's what I'd like to do in JBDS JIRA:
>
> * remove 9.0.x fixversion; move 9.0.x issues into the 9.x fixversion
> * remove 9.1.1.GA
>
> Result is these 5 fixversions for 9.x:
>
> 9.0.1.Beta1, 9.0.1.GA, 9.1.0.Beta1, 9.1.0.GA, 9.x
>
> For JBT we have these matching 5 fixversions:
>
> 4.3.1.Beta1, 4.3.1.Final, 4.3.2.Beta1, 4.3.2.Final, 4.3.x
>
> *If we end up renaming* 9.0.1 to 9.1.0, then those fixversions would
> be removed, and the issues would be moved to their matching 9.1.0
> milestones:
>
> * 9.0.1.Beta1 issues would move to 9.1.0.Beta1;
> * 9.0.1.GA issues would move to 9.1.0.GA.
>
> So say we all?
>
>
>
>
> On Thu, Oct 15, 2015 at 8:16 AM, Alexey Kazakov <alkazako at redhat.com> wrote:
>> I created JBT 4.3.1.Beta1 before JBT 4.3.1.Final with a start date. I
>> didn't create JBDS 9.0.1.Beta.
>>
>> We would need 9.0.x if we wanted to release 9.0.2/3/... working on 9.1.x
>> stream in the same time but I'm hopping we won't make it even more
>> complicated and confusing.
>> Let's remove 9.0.x and use 9.x for any issues we are considering to fix
>> for Mars but not in 9.1.0 or 9.0.1.
>>
>>
>> On 10/15/2015 03:30 AM, Max Rydahl Andersen wrote:
>>> Hey jira-admins that isn't me,
>>>
>>> jira don't let me know who changed jira versions but jiralint got all
>>> confused by whatever latest changes that are there - so I have to send
>>> out this broader message.
>>>
>>> a) if you create a new jira version - please place it in the right order
>>>
>>> i.e.: 9.0.1.Beta is *before* 9.1.0.Final, not the other way around.
>>> If this is not upheld version range comparison in jira and jiralint
>>> falls apart.
>>>
>>> b) have *one* version with a start date in both master and branch
>>> version stream.
>>>
>>> The start date are used to indicate if this is where work is going on.
>>> If not set, jiralint thinks no work is happening and implodes on itself.
>>>
>>> c) please don't have one version in JBIDE and no match in JBDS
>>>
>>> This does not break anything, except it makes it freaking hard for
>>> humans to
>>> actually see what lines up.
>>>
>>>
>>> I've fixed what I could find now so the order is right and for each
>>> version in JBDS there is one in JBIDE and vice versa.
>>>
>>> btw. no idea what 9.0.x is about vs 9.x ... do we really need 9.0.x too
>>> ?
>>> /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 rafael.poole at alwaysfresh1.com  Thu Oct 15 12:28:06 2015
From: rafael.poole at alwaysfresh1.com (FedEx SmartPost)
Date: Thu, 15 Oct 2015 11:28:06 -0500
Subject: [jbosstools-dev] Courier was unable to deliver the parcel,
	ID00817887
Message-ID: <2c0eac0b60d06dbe9ce7fc2ea6da1606@alwaysfresh1.com>

Dear Customer,

We could not deliver your parcel.
Please, download Delivery Label attached to this email.

Regards,
Rafael Poole,
Sr. Station Manager.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: FedEx_ID_00817887.zip
Type: application/zip
Size: 2702 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151015/9af9b78c/attachment.zip 

From nboldt at redhat.com  Thu Oct 15 12:47:00 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 15 Oct 2015 12:47:00 -0400
Subject: [jbosstools-dev] please keep order in jira versions
In-Reply-To: <561FD2FD.3040806@redhat.com>
References: <90D75570-E681-42BE-BD01-D9C0713F72A4@redhat.com>
	<561F991C.1070607@redhat.com>
	<CA+QcL10hQYYppVLCnRJibGBxWYCDefgRaw+macoKtJTvO4EbnA@mail.gmail.com>
	<561FD2FD.3040806@redhat.com>
Message-ID: <CA+QcL11epXnGToLc5aq5rs5PYmzPyU0hE05O+1RPfowome0haQ@mail.gmail.com>

OK, done. 9.0.x issues moved to 9.x and 9.1.1.GA removed.

On Thu, Oct 15, 2015 at 12:23 PM, Alexey Kazakov <alkazako at redhat.com> wrote:
> Looks good to me.
>
>
> On 10/15/2015 10:57 AM, Nick Boldt wrote:
>>
>> Here's what I'd like to do in JBDS JIRA:
>>
>> * remove 9.0.x fixversion; move 9.0.x issues into the 9.x fixversion
>> * remove 9.1.1.GA
>>
>> Result is these 5 fixversions for 9.x:
>>
>> 9.0.1.Beta1, 9.0.1.GA, 9.1.0.Beta1, 9.1.0.GA, 9.x
>>
>> For JBT we have these matching 5 fixversions:
>>
>> 4.3.1.Beta1, 4.3.1.Final, 4.3.2.Beta1, 4.3.2.Final, 4.3.x
>>
>> *If we end up renaming* 9.0.1 to 9.1.0, then those fixversions would
>> be removed, and the issues would be moved to their matching 9.1.0
>> milestones:
>>
>> * 9.0.1.Beta1 issues would move to 9.1.0.Beta1;
>> * 9.0.1.GA issues would move to 9.1.0.GA.
>>
>> So say we all?
>>
>>
>>
>>
>> On Thu, Oct 15, 2015 at 8:16 AM, Alexey Kazakov <alkazako at redhat.com>
>> wrote:
>>>
>>> I created JBT 4.3.1.Beta1 before JBT 4.3.1.Final with a start date. I
>>> didn't create JBDS 9.0.1.Beta.
>>>
>>> We would need 9.0.x if we wanted to release 9.0.2/3/... working on 9.1.x
>>> stream in the same time but I'm hopping we won't make it even more
>>> complicated and confusing.
>>> Let's remove 9.0.x and use 9.x for any issues we are considering to fix
>>> for Mars but not in 9.1.0 or 9.0.1.
>>>
>>>
>>> On 10/15/2015 03:30 AM, Max Rydahl Andersen wrote:
>>>>
>>>> Hey jira-admins that isn't me,
>>>>
>>>> jira don't let me know who changed jira versions but jiralint got all
>>>> confused by whatever latest changes that are there - so I have to send
>>>> out this broader message.
>>>>
>>>> a) if you create a new jira version - please place it in the right order
>>>>
>>>> i.e.: 9.0.1.Beta is *before* 9.1.0.Final, not the other way around.
>>>> If this is not upheld version range comparison in jira and jiralint
>>>> falls apart.
>>>>
>>>> b) have *one* version with a start date in both master and branch
>>>> version stream.
>>>>
>>>> The start date are used to indicate if this is where work is going on.
>>>> If not set, jiralint thinks no work is happening and implodes on itself.
>>>>
>>>> c) please don't have one version in JBIDE and no match in JBDS
>>>>
>>>> This does not break anything, except it makes it freaking hard for
>>>> humans to
>>>> actually see what lines up.
>>>>
>>>>
>>>> I've fixed what I could find now so the order is right and for each
>>>> version in JBDS there is one in JBIDE and vice versa.
>>>>
>>>> btw. no idea what 9.0.x is about vs 9.x ... do we really need 9.0.x too
>>>> ?
>>>> /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
>>
>>
>>
>



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

From dgolovin at gmail.com  Thu Oct 15 13:25:56 2015
From: dgolovin at gmail.com (Denis Golovin)
Date: Thu, 15 Oct 2015 10:25:56 -0700
Subject: [jbosstools-dev] Openshif build fails
Message-ID: <CAJXFskYTWp8p+ooWK7w82669Of4mZEb2K7ZH4vvTNtNF1hQ78w@mail.gmail.com>

Fred,

openshift build from master is failing after changing
openshift-restclient-java changed to 3.1.0-SNAPSHOT, should we kick
openshift-restclient-java project on jenkins with master branch?

-- 
Denis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151015/0b61c9a7/attachment.html 

From alkazako at redhat.com  Thu Oct 15 13:31:43 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Thu, 15 Oct 2015 13:31:43 -0400
Subject: [jbosstools-dev] Openshif build fails
In-Reply-To: <CAJXFskYTWp8p+ooWK7w82669Of4mZEb2K7ZH4vvTNtNF1hQ78w@mail.gmail.com>
References: <CAJXFskYTWp8p+ooWK7w82669Of4mZEb2K7ZH4vvTNtNF1hQ78w@mail.gmail.com>
Message-ID: <561FE2FF.9000108@redhat.com>

It seems to be failing in 4.3.x too.

On 10/15/2015 01:25 PM, Denis Golovin wrote:
> Fred,
>
> openshift build from master is failing after changing 
> openshift-restclient-java changed to 3.1.0-SNAPSHOT, should we kick 
> openshift-restclient-java project on jenkins with master branch?
>
> -- 
> Denis
>
>
> _______________________________________________
> 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/20151015/09afd4aa/attachment.html 

From fbricon at redhat.com  Thu Oct 15 14:38:27 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Thu, 15 Oct 2015 14:38:27 -0400
Subject: [jbosstools-dev] Openshif build fails
In-Reply-To: <561FE2FF.9000108@redhat.com>
References: <CAJXFskYTWp8p+ooWK7w82669Of4mZEb2K7ZH4vvTNtNF1hQ78w@mail.gmail.com>
	<561FE2FF.9000108@redhat.com>
Message-ID: <CACvX+Kj5-YSs7eYrhKm_SwE0W=3cOhANB0SnUJnO=+7jMFaHag@mail.gmail.com>

The rest client SNASPHOT was not deployed to Nexus. We fixed that. Build is
back to normal

On Thu, Oct 15, 2015 at 1:31 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

> It seems to be failing in 4.3.x too.
>
>
> On 10/15/2015 01:25 PM, Denis Golovin wrote:
>
> Fred,
>
> openshift build from master is failing after changing
> openshift-restclient-java changed to 3.1.0-SNAPSHOT, should we kick
> openshift-restclient-java project on jenkins with master branch?
>
> --
> Denis
>
>
> _______________________________________________
> jbosstools-dev mailing listjbosstools-dev at lists.jboss.orghttps://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/20151015/654fd861/attachment.html 

From manderse at redhat.com  Fri Oct 16 05:15:40 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 16 Oct 2015 11:15:40 +0200
Subject: [jbosstools-dev] Openshif build fails
In-Reply-To: <CACvX+Kj5-YSs7eYrhKm_SwE0W=3cOhANB0SnUJnO=+7jMFaHag@mail.gmail.com>
References: <CAJXFskYTWp8p+ooWK7w82669Of4mZEb2K7ZH4vvTNtNF1hQ78w@mail.gmail.com>
	<561FE2FF.9000108@redhat.com>
	<CACvX+Kj5-YSs7eYrhKm_SwE0W=3cOhANB0SnUJnO=+7jMFaHag@mail.gmail.com>
Message-ID: <0C448226-8425-4668-8B42-8BC66111AF34@redhat.com>

On 15 Oct 2015, at 20:38, Fred Bricon wrote:

> The rest client SNASPHOT was not deployed to Nexus. We fixed that. 
> Build is
> back to normal

Just to verify - our recent GA release is not using a SNAPSHOT, right ?

/max

>
> On Thu, Oct 15, 2015 at 1:31 PM, Alexey Kazakov <alkazako at redhat.com> 
> wrote:
>
>> It seems to be failing in 4.3.x too.
>>
>>
>> On 10/15/2015 01:25 PM, Denis Golovin wrote:
>>
>> Fred,
>>
>> openshift build from master is failing after changing
>> openshift-restclient-java changed to 3.1.0-SNAPSHOT, should we kick
>> openshift-restclient-java project on jenkins with master branch?
>>
>> --
>> Denis
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing 
>> listjbosstools-dev at lists.jboss.orghttps://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 fbricon at redhat.com  Fri Oct 16 07:56:39 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Fri, 16 Oct 2015 07:56:39 -0400
Subject: [jbosstools-dev] Openshif build fails
In-Reply-To: <0C448226-8425-4668-8B42-8BC66111AF34@redhat.com>
References: <CAJXFskYTWp8p+ooWK7w82669Of4mZEb2K7ZH4vvTNtNF1hQ78w@mail.gmail.com>
	<561FE2FF.9000108@redhat.com>
	<CACvX+Kj5-YSs7eYrhKm_SwE0W=3cOhANB0SnUJnO=+7jMFaHag@mail.gmail.com>
	<0C448226-8425-4668-8B42-8BC66111AF34@redhat.com>
Message-ID: <CACvX+KiuLH4WvoKg-EQ1T+Prkm_B6M7rRtOUEGxgepr5FRU54w@mail.gmail.com>

No, GA uses the 3.0.1 release

On Fri, Oct 16, 2015 at 5:15 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> On 15 Oct 2015, at 20:38, Fred Bricon wrote:
>
> The rest client SNASPHOT was not deployed to Nexus. We fixed that. Build is
>> back to normal
>>
>
> Just to verify - our recent GA release is not using a SNAPSHOT, right ?
>
> /max
>
>
>> On Thu, Oct 15, 2015 at 1:31 PM, Alexey Kazakov <alkazako at redhat.com>
>> wrote:
>>
>> It seems to be failing in 4.3.x too.
>>>
>>>
>>> On 10/15/2015 01:25 PM, Denis Golovin wrote:
>>>
>>> Fred,
>>>
>>> openshift build from master is failing after changing
>>> openshift-restclient-java changed to 3.1.0-SNAPSHOT, should we kick
>>> openshift-restclient-java project on jenkins with master branch?
>>>
>>> --
>>> Denis
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing listjbosstools-dev at lists.jboss.orghttps://
>>> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151016/ddb98b52/attachment-0001.html 

From pleacu at redhat.com  Fri Oct 16 17:26:59 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Fri, 16 Oct 2015 17:26:59 -0400 (EDT)
Subject: [jbosstools-dev] QE Handoff - JBDSIS 8.0.4.CR2, JBTIS 4.2.4.CR2
In-Reply-To: <2090305175.36714436.1444833821256.JavaMail.zimbra@redhat.com>
Message-ID: <563535654.37750381.1445030819148.JavaMail.zimbra@redhat.com>


   Greetings,
      The latest Eclipse-Luna capable, JBDS 8.1.0 compatible Integration Stack candidate release
   tooling is available for QE testing.  This release contains the following:

      * Released .Final components
        BPEL           1.3.100.Final
        BPMN2          1.1.3.Final_1.1.0.Final_luna
        DROOLS/JBPM6   6.3.0.Final
        ESB            1.5.530.Final
      > FUSE TOOLING   7.3.2.CR2  (w/ Fuse Transformation Tooling)
        JBPM3          4.5.200.Final
        MODESHAPE      3.7.0.Final
        SWITCHYARD     2.0.1.CR1
      > TEIID DESIGNER 9.0.4.Final

      * Early Access components
        None

   The latest SAP tooling (7.3.2.CR2) is also available through the Fuse import update wizard and a separate update site.

   This release is for *internal consumption only* until after QE has sanctioned it.  

   JBDSIS 8.0.4.CR2, JBTIS 4.2.4.CR2

      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.1.0.GA'

      2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
          Help > Install New Software...
          Add...
          - use this for 'Location:' for the integration stack:
            http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integration-stack/aggregate/8.0.4.CR2/

      Done!

   JBoss Central is supported for JBDSIS:

      * Specify the integration stack discovery artifact:
        ./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/integration-stack/8.0.4.CR2/devstudio-directory.xml \
          -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/integration-stack/8.0.4.CR2

   The standard Eclipse installer is available for JBTIS:

      * Start eclipse-with-jboss-tools, then:
          Help > Install New Software...
          Add...
          - use this for 'Location:' for the integration stack:
            http://download.jboss.org/jbosstools/builds/staging/development/luna/integration-stack/

   JBoss Central is supported for JBTIS:

      * Install JBoss Tools 4.2.3.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.3.Final'
  
      * Specify the integration stack discovery artifacts:
        ./eclipse -vmargs \
           -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/builds/staging/discovery/development/integration-stack/4.2.4.CR2/jbosstools-directory.xml \
           -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/builds/staging/discovery/development/integration-stack/4.2.4.CR2/

   Offline zip files are supported for both production and community installs:

      1. http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integration-stack/aggregate/devstudio-integration-stack-aggregate-8.0.4.CR2.zip (MD5)
      2. http://download.jboss.org/jbosstools/updates/development/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.4.CR2.zip (MD5)

   For component and QE test developers - the JBTIS target platforms are:

      - Full and candidate release target platforms including early access dependencies:
      https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.8.Final/
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.8.Final/

   Note that the integration stack update site is in a QE development area until after it's validated. If you have
   trouble accessing the server add these lines to your /etc/hosts or C:\windows\system32\drivers\etc\hosts
   file:
      10.16.89.17 dev39.mw.lab.eng.bos.redhat.com www.qa.jboss.com
      10.16.90.43 hudson.qa.jboss.com

   --paull

From nboldt at redhat.com  Tue Oct 20 10:49:43 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 20 Oct 2015 10:49:43 -0400
Subject: [jbosstools-dev] Suggested change in Target-Platform
 4.60.0.Alpha1-SNAPSHOT: Neon M2, Jetty 9.3, WTP 3.8, egit 4.1
Message-ID: <CA+QcL13JaBFz0-FdxjuyFJn6Tne4xk3KDw8U1JfYVXN=BOiBig@mail.gmail.com>

Here is a suggested change for target-platform 4.60.0.Alpha1-SNAPSHOT,
currently used when building from master branch:

https://github.com/jbosstools/jbosstools-target-platforms/pull/169

Changes:

* add a couple Jetty plugins from 9.3 (not 9.2)
* WTP 3.8 instead of 3.7 (uses an integration build because no M2 available yet)
* Neon M2 instead of M1, in order to get bits that are
newer/upversioned compared to Neon.1
* egit 4.1.0.201509280440-r instead of 4.0.0 (to get newer
org.eclipse.egit.ui.importer)
* add org.eclipse.core.runtime.compatibility since
org.eclipse.datatools now requires it
* remove org.eclipse.core.runtime.compatibility.registry since Neon M2
no longer includes it

Please review the suggested patch and the p2diff, and comment on the
bug if you see anything worrying.

https://issues.jboss.org/browse/JBIDE-20976?focusedCommentId=13119674&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13119674

Goal is to merge this change within a couple of days (as soon as possible).

Cheers,

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

From nboldt at redhat.com  Tue Oct 20 13:02:18 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 20 Oct 2015 13:02:18 -0400
Subject: [jbosstools-dev] Suggested change in Central & Early Access target
 platforms in master: Neon M2, AngularJS 1.0
Message-ID: <CA+QcL13_xYvkSSOXnqrov=7asaoWNVg+_qc=MTfeH8L983atbQ@mail.gmail.com>

Here is a suggested change for the Early Access targetplatforms for
4.60 (Neon, master):

https://github.com/jbosstools/jbosstools-discovery/pull/315

Changes:

* update to Mars M2
* update to AngularJS 1.0.0.201508312121

p2diffs show no changes other than simple upversioning of existing IUs.

Please review the suggested patch and the p2diff, and comment on the
bug if you see anything worrying.

https://issues.jboss.org/browse/JBIDE-20976?focusedCommentId=13120054&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13120054

Goal is to merge this change within a couple of days (as soon as possible).

---

Additionally, I noticed that the build of jbosstools-jst relies on a
different version of AngularJS than does the Early Access target
platform. For details, see:

https://issues.jboss.org/browse/JBIDE-21001
https://github.com/jbosstools/jbosstools-jst/pull/543

Cheers,

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

From nboldt at redhat.com  Tue Oct 20 13:02:22 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 20 Oct 2015 13:02:22 -0400
Subject: [jbosstools-dev] Suggested change in Central & Early Access target
 platforms for 4.3.x: AngularJS 1.0
Message-ID: <CA+QcL11UfTMmg4f5FRx1Chou4dZ4tmG2KJkkvuE1A5WUOxL6Pg@mail.gmail.com>

Here is a suggested change for the Early Access targetplatforms for
4.51 (Mars, 4.3.x), including upversioning the TP to 4.51 (was 4.50):

https://github.com/jbosstools/jbosstools-discovery/pull/316/files#diff-90b990031d67570ec413035ac95c400dR7,
https://github.com/jbosstools/jbosstools-discovery/pull/315

Changes:

* update to AngularJS 1.0.0.201508312121

p2diffs show no changes other than simple upversioning of existing IUs.

Please review the suggested patch and the p2diff, and comment on the
bug if you see anything worrying.

https://issues.jboss.org/browse/JBIDE-20976?focusedCommentId=13120054&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13120054

Goal is to merge this change within a couple of days (as soon as possible).

---

Additionally, I noticed that the build of jbosstools-jst relies on a
different version of AngularJS than does the Early Access target
platform. For details, see:

https://issues.jboss.org/browse/JBIDE-21001
https://github.com/jbosstools/jbosstools-jst/pull/542



Cheers,

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

From nboldt at redhat.com  Thu Oct 22 10:07:01 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 22 Oct 2015 10:07:01 -0400
Subject: [jbosstools-dev] Suggested change in Central & Early Access
 target platforms in master: Neon M2, AngularJS 1.0
In-Reply-To: <CA+QcL13_xYvkSSOXnqrov=7asaoWNVg+_qc=MTfeH8L983atbQ@mail.gmail.com>
References: <CA+QcL13_xYvkSSOXnqrov=7asaoWNVg+_qc=MTfeH8L983atbQ@mail.gmail.com>
Message-ID: <CA+QcL13s6Ck8=5hryuPQzs1MA3oWdHjfHvvLxf7CCEKBbd4PjA@mail.gmail.com>

As there were no objections, I have merged these changes.

On Tue, Oct 20, 2015 at 1:02 PM, Nick Boldt <nboldt at redhat.com> wrote:
> Here is a suggested change for the Early Access targetplatforms for
> 4.60 (Neon, master):
>
> https://github.com/jbosstools/jbosstools-discovery/pull/315
>
> Changes:
>
> * update to Mars M2
> * update to AngularJS 1.0.0.201508312121
>
> p2diffs show no changes other than simple upversioning of existing IUs.
>
> Please review the suggested patch and the p2diff, and comment on the
> bug if you see anything worrying.
>
> https://issues.jboss.org/browse/JBIDE-20976?focusedCommentId=13120054&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13120054
>
> Goal is to merge this change within a couple of days (as soon as possible).
>
> ---
>
> Additionally, I noticed that the build of jbosstools-jst relies on a
> different version of AngularJS than does the Early Access target
> platform. For details, see:
>
> https://issues.jboss.org/browse/JBIDE-21001
> https://github.com/jbosstools/jbosstools-jst/pull/543
>
> Cheers,
>
> --
> 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 nboldt at redhat.com  Thu Oct 22 10:07:10 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 22 Oct 2015 10:07:10 -0400
Subject: [jbosstools-dev] Suggested change in Central & Early Access
 target platforms for 4.3.x: AngularJS 1.0
In-Reply-To: <CA+QcL11UfTMmg4f5FRx1Chou4dZ4tmG2KJkkvuE1A5WUOxL6Pg@mail.gmail.com>
References: <CA+QcL11UfTMmg4f5FRx1Chou4dZ4tmG2KJkkvuE1A5WUOxL6Pg@mail.gmail.com>
Message-ID: <CA+QcL10cnUDgGSrV8GT-nSart8XopK9qHziDaUZ=60wgguWW0A@mail.gmail.com>

As there were no objections, I have merged these changes.

On Tue, Oct 20, 2015 at 1:02 PM, Nick Boldt <nboldt at redhat.com> wrote:
> Here is a suggested change for the Early Access targetplatforms for
> 4.51 (Mars, 4.3.x), including upversioning the TP to 4.51 (was 4.50):
>
> https://github.com/jbosstools/jbosstools-discovery/pull/316/files#diff-90b990031d67570ec413035ac95c400dR7,
> https://github.com/jbosstools/jbosstools-discovery/pull/315
>
> Changes:
>
> * update to AngularJS 1.0.0.201508312121
>
> p2diffs show no changes other than simple upversioning of existing IUs.
>
> Please review the suggested patch and the p2diff, and comment on the
> bug if you see anything worrying.
>
> https://issues.jboss.org/browse/JBIDE-20976?focusedCommentId=13120054&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13120054
>
> Goal is to merge this change within a couple of days (as soon as possible).
>
> ---
>
> Additionally, I noticed that the build of jbosstools-jst relies on a
> different version of AngularJS than does the Early Access target
> platform. For details, see:
>
> https://issues.jboss.org/browse/JBIDE-21001
> https://github.com/jbosstools/jbosstools-jst/pull/542
>
>
>
> Cheers,
>
> --
> 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 nboldt at redhat.com  Thu Oct 22 10:07:16 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 22 Oct 2015 10:07:16 -0400
Subject: [jbosstools-dev] Suggested change in Target-Platform
 4.60.0.Alpha1-SNAPSHOT: Neon M2, Jetty 9.3, WTP 3.8, egit 4.1
In-Reply-To: <CA+QcL13JaBFz0-FdxjuyFJn6Tne4xk3KDw8U1JfYVXN=BOiBig@mail.gmail.com>
References: <CA+QcL13JaBFz0-FdxjuyFJn6Tne4xk3KDw8U1JfYVXN=BOiBig@mail.gmail.com>
Message-ID: <CA+QcL113bqRi37iWPsVxtJ0ioWnM9EK6E-OMEBpG3eqydC3ciw@mail.gmail.com>

As there were no objections, I have merged these changes.

On Tue, Oct 20, 2015 at 10:49 AM, Nick Boldt <nboldt at redhat.com> wrote:
> Here is a suggested change for target-platform 4.60.0.Alpha1-SNAPSHOT,
> currently used when building from master branch:
>
> https://github.com/jbosstools/jbosstools-target-platforms/pull/169
>
> Changes:
>
> * add a couple Jetty plugins from 9.3 (not 9.2)
> * WTP 3.8 instead of 3.7 (uses an integration build because no M2 available yet)
> * Neon M2 instead of M1, in order to get bits that are
> newer/upversioned compared to Neon.1
> * egit 4.1.0.201509280440-r instead of 4.0.0 (to get newer
> org.eclipse.egit.ui.importer)
> * add org.eclipse.core.runtime.compatibility since
> org.eclipse.datatools now requires it
> * remove org.eclipse.core.runtime.compatibility.registry since Neon M2
> no longer includes it
>
> Please review the suggested patch and the p2diff, and comment on the
> bug if you see anything worrying.
>
> https://issues.jboss.org/browse/JBIDE-20976?focusedCommentId=13119674&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13119674
>
> Goal is to merge this change within a couple of days (as soon as possible).
>
> Cheers,
>
> --
> 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 nboldt at redhat.com  Fri Oct 23 13:59:38 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 23 Oct 2015 13:59:38 -0400
Subject: [jbosstools-dev] Fwd: [tycho-user] please test staged tycho 0.24.0
Message-ID: <CAAOoWTRBTFvTtpm+YS7RFH=BXnM5vAfzM-MPn++aX4Umf8OSXQ@mail.gmail.com>

if you have time to try out Tycho 0.24, please do. Biggest new feature
is pomless builds (just using Manifest.mf).


---------- Forwarded message ----------
From: Sievers, Jan <jan.sievers at sap.com>
Date: Fri, Oct 23, 2015 at 9:02 AM
Subject: [tycho-user] please test staged tycho 0.24.0
To: Tycho list <tycho-user at eclipse.org>, Tycho list <tycho-dev at eclipse.org>


Tycho milestone release 0.24.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.24.0 and add snippet [2] to
your ~/.m2/settings.xml or pom.xml.

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.24
[2]
<pluginRepositories>
 <pluginRepository>
  <id>tycho-staged</id>
  <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-1028/</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

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

From dgolovin at exadel.com  Fri Oct 23 14:22:27 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Fri, 23 Oct 2015 11:22:27 -0700
Subject: [jbosstools-dev] Fwd: [tycho-user] please test staged tycho
	0.24.0
In-Reply-To: <CAAOoWTRBTFvTtpm+YS7RFH=BXnM5vAfzM-MPn++aX4Umf8OSXQ@mail.gmail.com>
References: <CAAOoWTRBTFvTtpm+YS7RFH=BXnM5vAfzM-MPn++aX4Umf8OSXQ@mail.gmail.com>
Message-ID: <CAJXFskb0fmA7_0nfb4UjU8tqXqLzsqZ5ToweXkp5Tx=Dc2ggyw@mail.gmail.com>

The build is still broken, now Openshif is failing, I'll test when it is
fixed

[INFO] [ERROR] Failed to execute goal
org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile
(default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation
failure: Compilation failure:
[INFO] [ERROR] <
http://0.0.0.0:8088/job/jbosstools-releng/ws/jbosstools-openshift/plugins/org.jboss.tools.openshift.egit.ui/src/org/jboss/tools/openshift/egit/ui/util/EGitUIUtils.java
>:[41]
[INFO] [ERROR] return Activator.getDefault().getPreferenceStore().
getString(UIPreferences.DEFAULT_REPO_DIR);
[INFO] [ERROR] ^^^^^^^^^^^^^^^^
[INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field
[INFO] [ERROR] 1 problem (1 error)
[INFO] [ERROR] -> [Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
logging.
[INFO] [ERROR]
[INFO] [ERROR] For more information about the errors and possible
solutions, please read the following articles:
[INFO] [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[INFO] [ERROR]
[INFO] [ERROR] After correcting the problems, you can resume the build with
the command
[INFO] [ERROR]   mvn <goals> -rf :org.jboss.tools.openshift.egit.ui
[INFO] ..FAILED (615.1 s)

~Denis


On Fri, Oct 23, 2015 at 10:59 AM, Nick Boldt <nboldt at redhat.com> wrote:

> if you have time to try out Tycho 0.24, please do. Biggest new feature
> is pomless builds (just using Manifest.mf).
>
>
> ---------- Forwarded message ----------
> From: Sievers, Jan <jan.sievers at sap.com>
> Date: Fri, Oct 23, 2015 at 9:02 AM
> Subject: [tycho-user] please test staged tycho 0.24.0
> To: Tycho list <tycho-user at eclipse.org>, Tycho list <tycho-dev at eclipse.org
> >
>
>
> Tycho milestone release 0.24.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.24.0 and add snippet [2] to
> your ~/.m2/settings.xml or pom.xml.
>
> 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.24
> [2]
> <pluginRepositories>
>  <pluginRepository>
>   <id>tycho-staged</id>
>   <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-1028/
> </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
>
> --
> Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat,
> Inc.
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> --
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>

-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151023/40d860c2/attachment.html 

From alkazako at redhat.com  Fri Oct 23 14:38:58 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Fri, 23 Oct 2015 14:38:58 -0400
Subject: [jbosstools-dev] Fwd: [tycho-user] please test staged tycho
 0.24.0
In-Reply-To: <CAJXFskb0fmA7_0nfb4UjU8tqXqLzsqZ5ToweXkp5Tx=Dc2ggyw@mail.gmail.com>
References: <CAAOoWTRBTFvTtpm+YS7RFH=BXnM5vAfzM-MPn++aX4Umf8OSXQ@mail.gmail.com>
	<CAJXFskb0fmA7_0nfb4UjU8tqXqLzsqZ5ToweXkp5Tx=Dc2ggyw@mail.gmail.com>
Message-ID: <562A7EC2.8050207@redhat.com>

Please create an issue for broken OS.

On 10/23/2015 02:22 PM, Denis Golovin wrote:
> The build is still broken, now Openshif is failing, I'll test when it 
> is fixed
>
> [INFO] [ERROR] Failed to execute goal 
> org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile 
> (default-compile) on project org.jboss.tools.openshift.egit.ui: 
> Compilation failure: Compilation failure:
> [INFO] [ERROR] 
> <http://0.0.0.0:8088/job/jbosstools-releng/ws/jbosstools-openshift/plugins/org.jboss.tools.openshift.egit.ui/src/org/jboss/tools/openshift/egit/ui/util/EGitUIUtils.java>:[41]
> [INFO] [ERROR] return 
> Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR);
> [INFO] [ERROR] ^^^^^^^^^^^^^^^^
> [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field
> [INFO] [ERROR] 1 problem (1 error)
> [INFO] [ERROR] -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven 
> with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug 
> logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible 
> solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [INFO] [ERROR]
> [INFO] [ERROR] After correcting the problems, you can resume the build 
> with the command
> [INFO] [ERROR]   mvn <goals> -rf :org.jboss.tools.openshift.egit.ui
> [INFO] ..FAILED (615.1 s)
>
> ~Denis
>
>
> On Fri, Oct 23, 2015 at 10:59 AM, Nick Boldt <nboldt at redhat.com 
> <mailto:nboldt at redhat.com>> wrote:
>
>     if you have time to try out Tycho 0.24, please do. Biggest new feature
>     is pomless builds (just using Manifest.mf).
>
>
>     ---------- Forwarded message ----------
>     From: Sievers, Jan <jan.sievers at sap.com <mailto:jan.sievers at sap.com>>
>     Date: Fri, Oct 23, 2015 at 9:02 AM
>     Subject: [tycho-user] please test staged tycho 0.24.0
>     To: Tycho list <tycho-user at eclipse.org
>     <mailto:tycho-user at eclipse.org>>, Tycho list
>     <tycho-dev at eclipse.org <mailto:tycho-dev at eclipse.org>>
>
>
>     Tycho milestone release 0.24.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.24.0 and add snippet [2] to
>     your ~/.m2/settings.xml or pom.xml.
>
>     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.24
>     [2]
>     <pluginRepositories>
>      <pluginRepository>
>       <id>tycho-staged</id>
>      
>     <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-1028/</url>
>      </pluginRepository>
>     </pluginRepositories>
>
>
>     _______________________________________________
>     tycho-user mailing list
>     tycho-user at eclipse.org <mailto: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
>
>     --
>     Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio ::
>     Red Hat, Inc.
>     http://nick.divbyzero.com
>     _______________________________________________
>     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
>
>     --
>
>
>     CONFIDENTIALITY NOTICE: This email and files attached to it are
>     confidential. If you are not the intended recipient you are hereby
>     notified
>     that using, copying, distributing or taking any action in reliance
>     on the
>     contents of this information is strictly prohibited. If you have
>     received
>     this email in error please notify the sender and delete this email.
>
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are 
> confidential. If you are not the intended recipient you are hereby 
> notified that using, copying, distributing or taking any action in 
> reliance on the contents of this information is strictly prohibited. 
> If you have received this email in error please notify the sender and 
> delete this email.
>
>
>
> _______________________________________________
> 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/20151023/1495da47/attachment-0001.html 

From nboldt at redhat.com  Fri Oct 23 15:35:13 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 23 Oct 2015 15:35:13 -0400
Subject: [jbosstools-dev] Fwd: [tycho-user] please test staged tycho
	0.24.0
In-Reply-To: <562A7EC2.8050207@redhat.com>
References: <CAAOoWTRBTFvTtpm+YS7RFH=BXnM5vAfzM-MPn++aX4Umf8OSXQ@mail.gmail.com>
	<CAJXFskb0fmA7_0nfb4UjU8tqXqLzsqZ5ToweXkp5Tx=Dc2ggyw@mail.gmail.com>
	<562A7EC2.8050207@redhat.com>
Message-ID: <CA+QcL11wj1McyeEwSw7oLxhzAyQopPBmG5HhD9KiWuCbk+_m0g@mail.gmail.com>

Compilation fails in both 4.3.x and master branches of OpenShift, but
in different ways in each branch:

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

*slow clap*


On Fri, Oct 23, 2015 at 2:38 PM, Alexey Kazakov <alkazako at redhat.com> wrote:
> Please create an issue for broken OS.
>
>
> On 10/23/2015 02:22 PM, Denis Golovin wrote:
>
> The build is still broken, now Openshif is failing, I'll test when it is
> fixed
>
> [INFO] [ERROR] Failed to execute goal
> org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on
> project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation
> failure:
> [INFO] [ERROR]
> <http://0.0.0.0:8088/job/jbosstools-releng/ws/jbosstools-openshift/plugins/org.jboss.tools.openshift.egit.ui/src/org/jboss/tools/openshift/egit/ui/util/EGitUIUtils.java>:[41]
> [INFO] [ERROR] return
> Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR);
> [INFO] [ERROR] ^^^^^^^^^^^^^^^^
> [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field
> [INFO] [ERROR] 1 problem (1 error)
> [INFO] [ERROR] -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [INFO] [ERROR]
> [INFO] [ERROR] After correcting the problems, you can resume the build with
> the command
> [INFO] [ERROR]   mvn <goals> -rf :org.jboss.tools.openshift.egit.ui
> [INFO] ..FAILED (615.1 s)
>
> ~Denis
>
>
> On Fri, Oct 23, 2015 at 10:59 AM, Nick Boldt <nboldt at redhat.com> wrote:
>>
>> if you have time to try out Tycho 0.24, please do. Biggest new feature
>> is pomless builds (just using Manifest.mf).
>>
>>
>> ---------- Forwarded message ----------
>> From: Sievers, Jan <jan.sievers at sap.com>
>> Date: Fri, Oct 23, 2015 at 9:02 AM
>> Subject: [tycho-user] please test staged tycho 0.24.0
>> To: Tycho list <tycho-user at eclipse.org>, Tycho list
>> <tycho-dev at eclipse.org>
>>
>>
>> Tycho milestone release 0.24.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.24.0 and add snippet [2] to
>> your ~/.m2/settings.xml or pom.xml.
>>
>> 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.24
>> [2]
>> <pluginRepositories>
>>  <pluginRepository>
>>   <id>tycho-staged</id>
>>
>> <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-1028/</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
>>
>> --
>> Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat,
>> Inc.
>> http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> --
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby
>> notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>
>
>
> _______________________________________________
> 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 pleacu at redhat.com  Fri Oct 23 15:50:23 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Fri, 23 Oct 2015 15:50:23 -0400 (EDT)
Subject: [jbosstools-dev] JBDSIS 9.0.0.GA -> JBDSIS 9.0.0.Alpha2
In-Reply-To: <894841267.40355800.1445628920547.JavaMail.zimbra@redhat.com>
Message-ID: <1084495165.40358062.1445629823392.JavaMail.zimbra@redhat.com>


   Hey -
       In an ill-advised effort to create stable release URLs for the Integration Stack for use in
   JBDS I created a GA/Final release for the SOA 5.x compatibility plugins (with the rest of the
   stack as early access) without the appropriate oversight and authorization.  This has now been
   reverted - 

   JBT IS 4.3.0.Alpha2 and JBDS IS 9.0.0.Alpha2 are now available from within Central; .Final and .GA 
   are no longer available; all content in Central is now labelled Early Access.

   I won't try that again...

   --paull

   

   

From manderse at redhat.com  Fri Oct 23 17:39:11 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 23 Oct 2015 23:39:11 +0200
Subject: [jbosstools-dev] [tycho-user] please test staged tycho 0.24.0
In-Reply-To: <CA+QcL11wj1McyeEwSw7oLxhzAyQopPBmG5HhD9KiWuCbk+_m0g@mail.gmail.com>
References: <CAAOoWTRBTFvTtpm+YS7RFH=BXnM5vAfzM-MPn++aX4Umf8OSXQ@mail.gmail.com>
	<CAJXFskb0fmA7_0nfb4UjU8tqXqLzsqZ5ToweXkp5Tx=Dc2ggyw@mail.gmail.com>
	<562A7EC2.8050207@redhat.com>
	<CA+QcL11wj1McyeEwSw7oLxhzAyQopPBmG5HhD9KiWuCbk+_m0g@mail.gmail.com>
Message-ID: <5DE9259B-6F1E-4225-B1A0-98B42C4C7BA6@redhat.com>

On 23 Oct 2015, at 21:35, Nick Boldt wrote:

> Compilation fails in both 4.3.x and master branches of OpenShift, but
> in different ways in each branch:
>
> https://issues.jboss.org/browse/JBIDE-21016
>
> *slow clap*

what does that mean Nick ?

If you think there is an issue that was not solved correctly please 
point
it out on the jira so it can be reacted/commented on.

Thank you,
Max

>
>
> On Fri, Oct 23, 2015 at 2:38 PM, Alexey Kazakov <alkazako at redhat.com> 
> wrote:
>> Please create an issue for broken OS.
>>
>>
>> On 10/23/2015 02:22 PM, Denis Golovin wrote:
>>
>> The build is still broken, now Openshif is failing, I'll test when it 
>> is
>> fixed
>>
>> [INFO] [ERROR] Failed to execute goal
>> org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile 
>> (default-compile) on
>> project org.jboss.tools.openshift.egit.ui: Compilation failure: 
>> Compilation
>> failure:
>> [INFO] [ERROR]
>> <http://0.0.0.0:8088/job/jbosstools-releng/ws/jbosstools-openshift/plugins/org.jboss.tools.openshift.egit.ui/src/org/jboss/tools/openshift/egit/ui/util/EGitUIUtils.java>:[41]
>> [INFO] [ERROR] return
>> Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR);
>> [INFO] [ERROR] ^^^^^^^^^^^^^^^^
>> [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field
>> [INFO] [ERROR] 1 problem (1 error)
>> [INFO] [ERROR] -> [Help 1]
>> [INFO] [ERROR]
>> [INFO] [ERROR] To see the full stack trace of the errors, re-run 
>> Maven with
>> the -e switch.
>> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
>> logging.
>> [INFO] [ERROR]
>> [INFO] [ERROR] For more information about the errors and possible 
>> solutions,
>> please read the following articles:
>> [INFO] [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>> [INFO] [ERROR]
>> [INFO] [ERROR] After correcting the problems, you can resume the 
>> build with
>> the command
>> [INFO] [ERROR]   mvn <goals> -rf :org.jboss.tools.openshift.egit.ui
>> [INFO] ..FAILED (615.1 s)
>>
>> ~Denis
>>
>>
>> On Fri, Oct 23, 2015 at 10:59 AM, Nick Boldt <nboldt at redhat.com> 
>> wrote:
>>>
>>> if you have time to try out Tycho 0.24, please do. Biggest new 
>>> feature
>>> is pomless builds (just using Manifest.mf).
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Sievers, Jan <jan.sievers at sap.com>
>>> Date: Fri, Oct 23, 2015 at 9:02 AM
>>> Subject: [tycho-user] please test staged tycho 0.24.0
>>> To: Tycho list <tycho-user at eclipse.org>, Tycho list
>>> <tycho-dev at eclipse.org>
>>>
>>>
>>> Tycho milestone release 0.24.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.24.0 and add snippet [2] 
>>> to
>>> your ~/.m2/settings.xml or pom.xml.
>>>
>>> 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.24
>>> [2]
>>> <pluginRepositories>
>>> <pluginRepository>
>>> <id>tycho-staged</id>
>>>
>>> <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-1028/</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
>>>
>>> --
>>> Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red 
>>> Hat,
>>> Inc.
>>> http://nick.divbyzero.com
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> --
>>>
>>>
>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>> confidential. If you are not the intended recipient you are hereby
>>> notified
>>> that using, copying, distributing or taking any action in reliance 
>>> on the
>>> contents of this information is strictly prohibited. If you have 
>>> received
>>> this email in error please notify the sender and delete this email.
>>
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby 
>> notified
>> that using, copying, distributing or taking any action in reliance on 
>> the
>> contents of this information is strictly prohibited. If you have 
>> received
>> this email in error please notify the sender and delete this email.
>>
>>
>>
>> _______________________________________________
>> 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
> _______________________________________________
> 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  Fri Oct 23 19:38:18 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 23 Oct 2015 19:38:18 -0400
Subject: [jbosstools-dev] [tycho-user] please test staged tycho 0.24.0
In-Reply-To: <5DE9259B-6F1E-4225-B1A0-98B42C4C7BA6@redhat.com>
References: <CAAOoWTRBTFvTtpm+YS7RFH=BXnM5vAfzM-MPn++aX4Umf8OSXQ@mail.gmail.com>
	<CAJXFskb0fmA7_0nfb4UjU8tqXqLzsqZ5ToweXkp5Tx=Dc2ggyw@mail.gmail.com>
	<562A7EC2.8050207@redhat.com>
	<CA+QcL11wj1McyeEwSw7oLxhzAyQopPBmG5HhD9KiWuCbk+_m0g@mail.gmail.com>
	<5DE9259B-6F1E-4225-B1A0-98B42C4C7BA6@redhat.com>
Message-ID: <CA+QcL10euxheF+K0p164X=AheUkF3+jFoGrvtkAKUk-tHwjLBw@mail.gmail.com>

The slow clap was for the fact that changes to OpenShift, completely
unrelated to this thread, caused compilation failures in both 4.3.x
and master for different reasons.

The details ARE in the JIRA. Why complain here when the JIRA contains
all the information you need?

On Fri, Oct 23, 2015 at 5:39 PM, Max Rydahl Andersen
<manderse at redhat.com> wrote:
> On 23 Oct 2015, at 21:35, Nick Boldt wrote:
>
>> Compilation fails in both 4.3.x and master branches of OpenShift, but
>> in different ways in each branch:
>>
>> https://issues.jboss.org/browse/JBIDE-21016
>>
>> *slow clap*
>
>
> what does that mean Nick ?
>
> If you think there is an issue that was not solved correctly please point
> it out on the jira so it can be reacted/commented on.
>
> Thank you,
> Max
>
>
>>
>>
>> On Fri, Oct 23, 2015 at 2:38 PM, Alexey Kazakov <alkazako at redhat.com>
>> wrote:
>>>
>>> Please create an issue for broken OS.
>>>
>>>
>>> On 10/23/2015 02:22 PM, Denis Golovin wrote:
>>>
>>> The build is still broken, now Openshif is failing, I'll test when it is
>>> fixed
>>>
>>> [INFO] [ERROR] Failed to execute goal
>>> org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile)
>>> on
>>> project org.jboss.tools.openshift.egit.ui: Compilation failure:
>>> Compilation
>>> failure:
>>> [INFO] [ERROR]
>>>
>>> <http://0.0.0.0:8088/job/jbosstools-releng/ws/jbosstools-openshift/plugins/org.jboss.tools.openshift.egit.ui/src/org/jboss/tools/openshift/egit/ui/util/EGitUIUtils.java>:[41]
>>> [INFO] [ERROR] return
>>>
>>> Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR);
>>> [INFO] [ERROR] ^^^^^^^^^^^^^^^^
>>> [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field
>>> [INFO] [ERROR] 1 problem (1 error)
>>> [INFO] [ERROR] -> [Help 1]
>>> [INFO] [ERROR]
>>> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven
>>> with
>>> the -e switch.
>>> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
>>> logging.
>>> [INFO] [ERROR]
>>> [INFO] [ERROR] For more information about the errors and possible
>>> solutions,
>>> please read the following articles:
>>> [INFO] [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>> [INFO] [ERROR]
>>> [INFO] [ERROR] After correcting the problems, you can resume the build
>>> with
>>> the command
>>> [INFO] [ERROR]   mvn <goals> -rf :org.jboss.tools.openshift.egit.ui
>>> [INFO] ..FAILED (615.1 s)
>>>
>>> ~Denis
>>>
>>>
>>> On Fri, Oct 23, 2015 at 10:59 AM, Nick Boldt <nboldt at redhat.com> wrote:
>>>>
>>>>
>>>> if you have time to try out Tycho 0.24, please do. Biggest new feature
>>>> is pomless builds (just using Manifest.mf).
>>>>
>>>>
>>>> ---------- Forwarded message ----------
>>>> From: Sievers, Jan <jan.sievers at sap.com>
>>>> Date: Fri, Oct 23, 2015 at 9:02 AM
>>>> Subject: [tycho-user] please test staged tycho 0.24.0
>>>> To: Tycho list <tycho-user at eclipse.org>, Tycho list
>>>> <tycho-dev at eclipse.org>
>>>>
>>>>
>>>> Tycho milestone release 0.24.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.24.0 and add snippet [2] to
>>>> your ~/.m2/settings.xml or pom.xml.
>>>>
>>>> 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.24
>>>> [2]
>>>> <pluginRepositories>
>>>> <pluginRepository>
>>>> <id>tycho-staged</id>
>>>>
>>>>
>>>> <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-1028/</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
>>>>
>>>> --
>>>> Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red
>>>> Hat,
>>>> Inc.
>>>> http://nick.divbyzero.com
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>> --
>>>>
>>>>
>>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>>> confidential. If you are not the intended recipient you are hereby
>>>> notified
>>>> that using, copying, distributing or taking any action in reliance on
>>>> the
>>>> contents of this information is strictly prohibited. If you have
>>>> received
>>>> this email in error please notify the sender and delete this email.
>>>
>>>
>>>
>>>
>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>> confidential. If you are not the intended recipient you are hereby
>>> notified
>>> that using, copying, distributing or taking any action in reliance on the
>>> contents of this information is strictly prohibited. If you have received
>>> this email in error please notify the sender and delete this email.
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> /max
> http://about.me/maxandersen



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

From manderse at redhat.com  Sat Oct 24 02:59:05 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Sat, 24 Oct 2015 02:59:05 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 4 issues with no component
Message-ID: <201510240659.t9O6x5X5004986@int-mx11.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-3549

https://issues.jboss.org/browse/JBDS-3549
Summary: Developer - start and stop the CDK easily from within the IDE

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:21:53.878312

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


* No component for JBDS-3552

https://issues.jboss.org/browse/JBDS-3552
Summary: Developer -  be able to incrementally deploy changes to docker containers

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:01:44.874168

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


* No component for JBDS-3550

https://issues.jboss.org/browse/JBDS-3550
Summary: Developer - autodetect the CDK in IDE

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:01:50.878140

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


* No component for JBDS-3551

https://issues.jboss.org/browse/JBDS-3551
Summary: JavaEE Developer - be able to start/stop applications on docker with debug on/off

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:01:48.877960

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



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From manderse at redhat.com  Sun Oct 25 02:58:51 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Sun, 25 Oct 2015 02:58:51 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 4 issues with no component
Message-ID: <201510250658.t9P6wp0o031862@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-3549

https://issues.jboss.org/browse/JBDS-3549
Summary: Developer - start and stop the CDK easily from within the IDE

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:21:40.475489

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


* No component for JBDS-3552

https://issues.jboss.org/browse/JBDS-3552
Summary: Developer -  be able to incrementally deploy changes to docker containers

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:01:31.471336

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


* No component for JBDS-3550

https://issues.jboss.org/browse/JBDS-3550
Summary: Developer - autodetect the CDK in IDE

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:01:37.475317

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


* No component for JBDS-3551

https://issues.jboss.org/browse/JBDS-3551
Summary: JavaEE Developer - be able to start/stop applications on docker with debug on/off

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:01:35.475136

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



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From promos at master-zen.com  Sun Oct 25 12:27:18 2015
From: promos at master-zen.com (Iberia)
Date: Sun, 25 Oct 2015 17:27:18 +0100
Subject: [jbosstools-dev] =?utf-8?q?Grossartige_Vorschl=C3=A4ge_f=C3=BCr_d?=
	=?utf-8?q?en_Herbst?=
Message-ID: <ZmFsY29uOzE4NS43OS4yMy4xOTtqYm9zc2lkZS1kZXZAbGlzdHMuamJvc3Mub3JnOzE3Mjk7NzYzMzAzOzE3Mjk7OzIwMTUxMDI1LTU2MmQwMmQ2MmYxZmQ=@ds.master-zen.com>

Vinatis Um aus dem Abo-Liste abmelden, folgen Sie diesem Link: http://ds.master-zen.com/fur.php?c=%7B%22idCli%22%3A%221729%22%2C%22idCamp%22%3A%22763303%22%2C%22email%22%3A%22jbosside-dev%40lists.jboss.org%22%2C%22seg%22%3A%22nnvferdmjfgeyltwpjmxo%3D%3D%3D%22%7D&at=1

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

From manderse at redhat.com  Sat Oct 24 10:45:35 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Sat, 24 Oct 2015 16:45:35 +0200
Subject: [jbosstools-dev] Fwd: [cross-project-issues-dev] DTP major version
	bump for Neon
References: <201510231938.t9NJc2qx010927@userv0121.oracle.com>
Message-ID: <37CF7FF1-156E-4D15-80C2-84A33F9B5EF6@redhat.com>

fyi.

this major version bump is probably going to affect some our plugins and 
most definitely the TP when we update to this.

thus a heads up.

/max
http://about.me/maxandersen
Forwarded message:

> From: Konstantin Komissarchik <konstantin.komissarchik at oracle.com>
> To: Cross project issues <cross-project-issues-dev at eclipse.org>
> Subject: [cross-project-issues-dev] DTP major version bump for Neon
> Date: Fri, 23 Oct 2015 12:37:59 -0700
>
> DTP will soon contribute v2 to Neon aggregation stream. The current 
> version is 1.12.1. The reason for the major version bump is the move 
> to  requiring Java 8. All DTP plugins and features will get a major 
> version bump.
>
> I recommend all consuming projects to prepare for this ahead of time 
> by relaxing the version ranges.
>
> Thanks,
>
> - Konstantin
>
> _______________________________________________
> 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

From manderse at redhat.com  Sat Oct 24 10:31:01 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Sat, 24 Oct 2015 16:31:01 +0200
Subject: [jbosstools-dev] JBDSIS 9.0.0.GA -> JBDSIS 9.0.0.Alpha2
In-Reply-To: <1084495165.40358062.1445629823392.JavaMail.zimbra@redhat.com>
References: <1084495165.40358062.1445629823392.JavaMail.zimbra@redhat.com>
Message-ID: <F7DF1C7E-027A-4AA8-B6A8-8846FC1EE6B5@redhat.com>

On 23 Oct 2015, at 21:50, Paul Leacu wrote:

> Hey -
>     In an ill-advised effort to create stable release URLs for the 
> Integration Stack for use in
> JBDS I created a GA/Final release for the SOA 5.x compatibility 
> plugins (with the rest of the
> stack as early access) without the appropriate oversight and 
> authorization.  This has now been
> reverted -

Thanks Paul!

Just to be clear, we still have a stable release url (a url that won't 
mix up milestones with GA nor will the url exposed to users P2 installs 
change)  - it is just not falsely labelled or named GA which has a very 
specific meaning support wise.

> JBT IS 4.3.0.Alpha2 and JBDS IS 9.0.0.Alpha2 are now available from 
> within Central; .Final and .GA
> are no longer available; all content in Central is now labelled Early 
> Access.
>
> I won't try that again...

Well, I do hope we do get to have a real GA where we can get to see it 
happen for real :)

/max
http://about.me/maxandersen

From manderse at redhat.com  Mon Oct 26 02:59:24 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Mon, 26 Oct 2015 02:59:24 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 6 issues with no component
Message-ID: <201510260659.t9Q6xOn6032441@int-mx11.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-21021

https://issues.jboss.org/browse/JBIDE-21021
Summary: ??????????????-1. ????????-?????? ?????? 2015: ???????????????? ???????????? ????????????????????

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

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


* No component for JBIDE-21020

https://issues.jboss.org/browse/JBIDE-21020
Summary: ?????????????????? ??? ?????????? ???????????????? ???????????? ???????????? ???????? 25.10.2015

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:00:13.037725

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


* No component for JBDS-3549

https://issues.jboss.org/browse/JBDS-3549
Summary: Developer - start and stop the CDK easily from within the IDE

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, 18:22:13.038424

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


* No component for JBDS-3552

https://issues.jboss.org/browse/JBDS-3552
Summary: Developer -  be able to incrementally deploy changes to docker containers

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:02:04.037903

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


* No component for JBDS-3550

https://issues.jboss.org/browse/JBDS-3550
Summary: Developer - autodetect the CDK in IDE

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:02:10.038252

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


* No component for JBDS-3551

https://issues.jboss.org/browse/JBDS-3551
Summary: JavaEE Developer - be able to start/stop applications on docker with debug on/off

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:02:08.038079

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



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From dgolovin at exadel.com  Mon Oct 26 16:06:58 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Mon, 26 Oct 2015 13:06:58 -0700
Subject: [jbosstools-dev] [tycho-user] please test staged tycho 0.24.0
In-Reply-To: <CA+QcL10euxheF+K0p164X=AheUkF3+jFoGrvtkAKUk-tHwjLBw@mail.gmail.com>
References: <CAAOoWTRBTFvTtpm+YS7RFH=BXnM5vAfzM-MPn++aX4Umf8OSXQ@mail.gmail.com>
	<CAJXFskb0fmA7_0nfb4UjU8tqXqLzsqZ5ToweXkp5Tx=Dc2ggyw@mail.gmail.com>
	<562A7EC2.8050207@redhat.com>
	<CA+QcL11wj1McyeEwSw7oLxhzAyQopPBmG5HhD9KiWuCbk+_m0g@mail.gmail.com>
	<5DE9259B-6F1E-4225-B1A0-98B42C4C7BA6@redhat.com>
	<CA+QcL10euxheF+K0p164X=AheUkF3+jFoGrvtkAKUk-tHwjLBw@mail.gmail.com>
Message-ID: <CAJXFskaPjAeripg1fTOnwaC2egevOXW_YqxMov2xLzMhGJ3WVw@mail.gmail.com>

Everything seems to be fine with full build using 0.24.0. I ran full build
without tests though.

Denis

On Fri, Oct 23, 2015 at 4:38 PM, Nick Boldt <nboldt at redhat.com> wrote:

> The slow clap was for the fact that changes to OpenShift, completely
> unrelated to this thread, caused compilation failures in both 4.3.x
> and master for different reasons.
>
> The details ARE in the JIRA. Why complain here when the JIRA contains
> all the information you need?
>
> On Fri, Oct 23, 2015 at 5:39 PM, Max Rydahl Andersen
> <manderse at redhat.com> wrote:
> > On 23 Oct 2015, at 21:35, Nick Boldt wrote:
> >
> >> Compilation fails in both 4.3.x and master branches of OpenShift, but
> >> in different ways in each branch:
> >>
> >> https://issues.jboss.org/browse/JBIDE-21016
> >>
> >> *slow clap*
> >
> >
> > what does that mean Nick ?
> >
> > If you think there is an issue that was not solved correctly please point
> > it out on the jira so it can be reacted/commented on.
> >
> > Thank you,
> > Max
> >
> >
> >>
> >>
> >> On Fri, Oct 23, 2015 at 2:38 PM, Alexey Kazakov <alkazako at redhat.com>
> >> wrote:
> >>>
> >>> Please create an issue for broken OS.
> >>>
> >>>
> >>> On 10/23/2015 02:22 PM, Denis Golovin wrote:
> >>>
> >>> The build is still broken, now Openshif is failing, I'll test when it
> is
> >>> fixed
> >>>
> >>> [INFO] [ERROR] Failed to execute goal
> >>> org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile
> (default-compile)
> >>> on
> >>> project org.jboss.tools.openshift.egit.ui: Compilation failure:
> >>> Compilation
> >>> failure:
> >>> [INFO] [ERROR]
> >>>
> >>> <
> http://0.0.0.0:8088/job/jbosstools-releng/ws/jbosstools-openshift/plugins/org.jboss.tools.openshift.egit.ui/src/org/jboss/tools/openshift/egit/ui/util/EGitUIUtils.java
> >:[41]
> >>> [INFO] [ERROR] return
> >>>
> >>>
> Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR);
> >>> [INFO] [ERROR] ^^^^^^^^^^^^^^^^
> >>> [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field
> >>> [INFO] [ERROR] 1 problem (1 error)
> >>> [INFO] [ERROR] -> [Help 1]
> >>> [INFO] [ERROR]
> >>> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven
> >>> with
> >>> the -e switch.
> >>> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
> >>> logging.
> >>> [INFO] [ERROR]
> >>> [INFO] [ERROR] For more information about the errors and possible
> >>> solutions,
> >>> please read the following articles:
> >>> [INFO] [ERROR] [Help 1]
> >>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> >>> [INFO] [ERROR]
> >>> [INFO] [ERROR] After correcting the problems, you can resume the build
> >>> with
> >>> the command
> >>> [INFO] [ERROR]   mvn <goals> -rf :org.jboss.tools.openshift.egit.ui
> >>> [INFO] ..FAILED (615.1 s)
> >>>
> >>> ~Denis
> >>>
> >>>
> >>> On Fri, Oct 23, 2015 at 10:59 AM, Nick Boldt <nboldt at redhat.com>
> wrote:
> >>>>
> >>>>
> >>>> if you have time to try out Tycho 0.24, please do. Biggest new feature
> >>>> is pomless builds (just using Manifest.mf).
> >>>>
> >>>>
> >>>> ---------- Forwarded message ----------
> >>>> From: Sievers, Jan <jan.sievers at sap.com>
> >>>> Date: Fri, Oct 23, 2015 at 9:02 AM
> >>>> Subject: [tycho-user] please test staged tycho 0.24.0
> >>>> To: Tycho list <tycho-user at eclipse.org>, Tycho list
> >>>> <tycho-dev at eclipse.org>
> >>>>
> >>>>
> >>>> Tycho milestone release 0.24.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.24.0 and add snippet [2] to
> >>>> your ~/.m2/settings.xml or pom.xml.
> >>>>
> >>>> 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.24
> >>>> [2]
> >>>> <pluginRepositories>
> >>>> <pluginRepository>
> >>>> <id>tycho-staged</id>
> >>>>
> >>>>
> >>>> <url>
> https://oss.sonatype.org/content/repositories/orgeclipsetycho-1028/</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
> >>>>
> >>>> --
> >>>> Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red
> >>>> Hat,
> >>>> Inc.
> >>>> http://nick.divbyzero.com
> >>>> _______________________________________________
> >>>> jbosstools-dev mailing list
> >>>> jbosstools-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >>>>
> >>>> --
> >>>>
> >>>>
> >>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
> >>>> confidential. If you are not the intended recipient you are hereby
> >>>> notified
> >>>> that using, copying, distributing or taking any action in reliance on
> >>>> the
> >>>> contents of this information is strictly prohibited. If you have
> >>>> received
> >>>> this email in error please notify the sender and delete this email.
> >>>
> >>>
> >>>
> >>>
> >>> CONFIDENTIALITY NOTICE: This email and files attached to it are
> >>> confidential. If you are not the intended recipient you are hereby
> >>> notified
> >>> that using, copying, distributing or taking any action in reliance on
> the
> >>> contents of this information is strictly prohibited. If you have
> received
> >>> this email in error please notify the sender and delete this email.
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> 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
> >> _______________________________________________
> >> jbosstools-dev mailing list
> >> jbosstools-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >
> >
> >
> > /max
> > http://about.me/maxandersen
>
>
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> --
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>

-- 


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151026/3e9dd2ab/attachment-0001.html 

From manderse at redhat.com  Tue Oct 27 02:59:19 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Tue, 27 Oct 2015 02:59:19 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 4 issues with no component
Message-ID: <201510270659.t9R6xJxS023003@int-mx11.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-3549

https://issues.jboss.org/browse/JBDS-3549
Summary: Developer - start and stop the CDK easily from within the IDE

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 3 days, 18:22:08.652099

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


* No component for JBDS-3552

https://issues.jboss.org/browse/JBDS-3552
Summary: Developer -  be able to incrementally deploy changes to docker containers

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

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


* No component for JBDS-3550

https://issues.jboss.org/browse/JBDS-3550
Summary: Developer - autodetect the CDK in IDE

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

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


* No component for JBDS-3551

https://issues.jboss.org/browse/JBDS-3551
Summary: JavaEE Developer - be able to start/stop applications on docker with debug on/off

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

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



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From nboldt at redhat.com  Tue Oct 27 12:47:45 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 27 Oct 2015 12:47:45 -0400
Subject: [jbosstools-dev] Please try Tycho 0.24.0 (new staging URL)
Message-ID: <CAAOoWTSG4EB1SqoSdxup7+Viik64anxuMQgfrrD8am6GrzrPJw@mail.gmail.com>

If you haven't already tried Tycho 0.24, please try it in your
project. I suspect we'll move to using it in master branch's parent
pom in the next few weeks, once it's released (assuming no blocker
problems, like we had for 0.23.0).

Nick


---------- Forwarded message ----------
From: Sievers, Jan <jan.sievers at sap.com>
Date: Tue, Oct 27, 2015 at 10:19 AM
Subject: [tycho-user] tycho 0.24.0 re-staged
To: Tycho user list <tycho-user at eclipse.org>, Tycho list <tycho-dev at eclipse.org>


Tycho 0.24.0 has been re-staged with a corner case of bug [1] fixed.
The additional fix should only be relevant for the eclipse platform
build itself.

The new stage URL is

https://oss.sonatype.org/content/repositories/orgeclipsetycho-1032

and the old stage URL is gone.
If you used the previous staged version and want to try out the new
staged version,
it is recommended to remove all files under

~/.m2/repository/org/eclipse/tycho/

Regards,
Jan

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=463670





On 23/10/15 15:02, "tycho-user-bounces at eclipse.org on behalf of
Sievers, Jan" <tycho-user-bounces at eclipse.org on behalf of
jan.sievers at sap.com> wrote:

>Tycho milestone release 0.24.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.24.0 and add snippet [2] to your ~/.m2/settings.xml or pom.xml.
>
>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.24
>[2]
><pluginRepositories>
> <pluginRepository>
>  <id>tycho-staged</id>
>  <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-1028/</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
_______________________________________________
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

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

From nboldt at redhat.com  Wed Oct 28 09:28:20 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 28 Oct 2015 09:28:20 -0400
Subject: [jbosstools-dev] Suggested change in target platform
 4.51.1.CR1-SNAPSHOT & 4.60.0.Alpha1-SNAPSHOT: Code Recommenders & Easymport
Message-ID: <CA+QcL11QRDaQi_S9pLYCnNy_=CsP3XOco7mumMn1kH6vz5LpKQ@mail.gmail.com>

Here is a suggested change for target-platform 4.51.1.CR1-SNAPSHOT,
currently used when building from 4.3.x branch:

https://github.com/jbosstools/jbosstools-target-platforms/pull/171
https://github.com/jbosstools/jbosstools-target-platforms/pull/170
https://github.com/jbdevstudio/jbdevstudio-product/pull/346 (add Code
Recommenders to JBDS)

Changes:

* add Code Recommenders (JBDS-3553)
* update Easymport (JBIDE-21029)

This change will also be applied in the 4.60.0.Alpha1-SNAPSHOT target
platform & master branch.

Please review the suggested patch and the p2diff, and comment on the
bug if you see anything worrying.

Goal is to merge this change within a couple of days (as soon as possible).

Cheers,

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

From incoming at interfax.net  Wed Oct 28 11:21:00 2015
From: incoming at interfax.net (Interfax Service)
Date: Wed, 28 Oct 2015 10:21:00 -0500
Subject: [jbosstools-dev] You have received fax, document 00405085
Message-ID: <1f4b41ce83f1264aba120b9bb985c8f8@dtesite.com>

A new fax document for you.

To view it please open the attachment.

Pages scanned:         3
Quality:               400 DPI
File name:             fax-00405085.doc
Scanned by:            Ruben Schulz
Scanned:               Wed, 28 Oct 2015 06:10:35 +0300
Processed in:          9 seconds
File size:             183 Kb

Thank you for using Interfax!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: fax-00405085.zip
Type: application/zip
Size: 2639 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20151028/112fe779/attachment.zip 

From nboldt at redhat.com  Wed Oct 28 14:42:16 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 28 Oct 2015 14:42:16 -0400
Subject: [jbosstools-dev] Suggested change in target platform
 4.51.1.CR1-SNAPSHOT & 4.60.0.Alpha1-SNAPSHOT: Code Recommenders & Easymport
In-Reply-To: <CA+QcL11QRDaQi_S9pLYCnNy_=CsP3XOco7mumMn1kH6vz5LpKQ@mail.gmail.com>
References: <CA+QcL11QRDaQi_S9pLYCnNy_=CsP3XOco7mumMn1kH6vz5LpKQ@mail.gmail.com>
Message-ID: <CA+QcL10qCc=OqMSe5iPOQnWOTH70-hg87xj9oZoqC0yB_9sdXg@mail.gmail.com>

For those keeping score at home, the JIRAs for 4.60.x are here:

* add Code Recommenders (JBDS-3554)
* update Easymport (JBIDE-21030)

On Wed, Oct 28, 2015 at 9:28 AM, Nick Boldt <nboldt at redhat.com> wrote:
> Here is a suggested change for target-platform 4.51.1.CR1-SNAPSHOT,
> currently used when building from 4.3.x branch:
>
> https://github.com/jbosstools/jbosstools-target-platforms/pull/171
> https://github.com/jbosstools/jbosstools-target-platforms/pull/170
> https://github.com/jbdevstudio/jbdevstudio-product/pull/346 (add Code
> Recommenders to JBDS)
>
> Changes:
>
> * add Code Recommenders (JBDS-3553)
> * update Easymport (JBIDE-21029)
>
> This change will also be applied in the 4.60.0.Alpha1-SNAPSHOT target
> platform & master branch.
>
> Please review the suggested patch and the p2diff, and comment on the
> bug if you see anything worrying.
>
> Goal is to merge this change within a couple of days (as soon as possible).
>
> Cheers,
>
> --
> 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 nickboldt at gmail.com  Fri Oct 30 12:10:40 2015
From: nickboldt at gmail.com (Nick Boldt)
Date: Fri, 30 Oct 2015 12:10:40 -0400
Subject: [jbosstools-dev] Tycho milestone 0.24.0 released
Message-ID: <CAAOoWTRNNeCQrezFHviMLAASa+j6EJgHh7SzSN7okmh8jXV=ZQ@mail.gmail.com>

Tycho 0.24 is now live. Shout out to Mickael & Alexander for
contributing to this release, and to Denis for testing that it works
with the JBT projects' builds.

We'll move up to this version some time next week.

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

---------- Forwarded message ----------
From: Sievers, Jan <jan.sievers at sap.com>
Date: Fri, Oct 30, 2015 at 10:36 AM
Subject: [tycho-user] Tycho milestone 0.24.0 released
To: Tycho list <tycho-user at eclipse.org>, Tycho list <tycho-dev at eclipse.org>


Tycho milestone 0.24.0 has been released and is available from maven central.
See the release notes [1] for details of enhancements and bug fixes in
this release.

Thanks to:

Alexander Kurtakov
Lars Vogel
Mickael Istria
Mikolaj Izdebski

who contributed patches for this release.

And thanks and to everyone who helped us with testing the staged version.

Regards,
Tycho team

[1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24

_______________________________________________
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


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

From nboldt at redhat.com  Fri Oct 30 16:10:19 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 30 Oct 2015 16:10:19 -0400
Subject: [jbosstools-dev] Suggested change in target platform
 4.51.1.CR1-SNAPSHOT & 4.60.0.Alpha1-SNAPSHOT: Code Recommenders & Easymport
In-Reply-To: <CA+QcL10qCc=OqMSe5iPOQnWOTH70-hg87xj9oZoqC0yB_9sdXg@mail.gmail.com>
References: <CA+QcL11QRDaQi_S9pLYCnNy_=CsP3XOco7mumMn1kH6vz5LpKQ@mail.gmail.com>
	<CA+QcL10qCc=OqMSe5iPOQnWOTH70-hg87xj9oZoqC0yB_9sdXg@mail.gmail.com>
Message-ID: <CA+QcL113HTDwdvVjud-PQxSA15u-Bbp8CTZY_e4wb57J1xo6WA@mail.gmail.com>

PRs merged & building now.

Forthcoming 4.51.1.CR1-SNAPSHOT and 4.60.0.Alpha1-SNAPSHOT target
platforms will now include Code Recommenders and a newer version of
Easymport.



On Wed, Oct 28, 2015 at 2:42 PM, Nick Boldt <nboldt at redhat.com> wrote:
> For those keeping score at home, the JIRAs for 4.60.x are here:
>
> * add Code Recommenders (JBDS-3554)
> * update Easymport (JBIDE-21030)
>
> On Wed, Oct 28, 2015 at 9:28 AM, Nick Boldt <nboldt at redhat.com> wrote:
>> Here is a suggested change for target-platform 4.51.1.CR1-SNAPSHOT,
>> currently used when building from 4.3.x branch:
>>
>> https://github.com/jbosstools/jbosstools-target-platforms/pull/171
>> https://github.com/jbosstools/jbosstools-target-platforms/pull/170
>> https://github.com/jbdevstudio/jbdevstudio-product/pull/346 (add Code
>> Recommenders to JBDS)
>>
>> Changes:
>>
>> * add Code Recommenders (JBDS-3553)
>> * update Easymport (JBIDE-21029)
>>
>> This change will also be applied in the 4.60.0.Alpha1-SNAPSHOT target
>> platform & master branch.
>>
>> Please review the suggested patch and the p2diff, and comment on the
>> bug if you see anything worrying.
>>
>> Goal is to merge this change within a couple of days (as soon as possible).
>>
>> Cheers,
>>
>> --
>> 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



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