From incoming at interfax.net  Sun Jan  3 06:03:59 2016
From: incoming at interfax.net (Interfax Online)
Date: Sun, 3 Jan 2016 14:03:59 +0300
Subject: [jbosstools-dev] You have received fax, document 000707128
Message-ID: <b9ea6b7508ce0f7f14913fb7711eda08@tplanet.ru>

New incoming fax document.

To view it please open the attachment.

Pages scanned:        12
Filename:             document-000707128.doc
Scan duration:        27 seconds
From:                 Keith Carney
Date of scan:         Sun, 3 Jan 2016 07:14:38 +0300
File size:            222 Kb
Resolution:           600 DPI

Thanks for using Interfax service!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: document-000707128.zip
Type: application/zip
Size: 1489 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160103/a831072e/attachment.zip 

From manderse at redhat.com  Mon Jan  4 04:50:30 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 04 Jan 2016 10:50:30 +0100
Subject: [jbosstools-dev] I have archived the JBIDE 4.3.0 and JBDS 9.0.0
 releases in JIRA
In-Reply-To: <567463FC.4020805@redhat.com>
References: <CA+QcL111+hfcbYQ8eWDQr7FBdmCvEC-X3ytJJQE=3-k9ZgBNxg@mail.gmail.com>
	<567463FC.4020805@redhat.com>
Message-ID: <CD0EA3F9-8710-4AE7-AC0F-EC2565C01D38@redhat.com>

We never in the past did this since it affects the release overview 
making it not list the latest releases nor can you open bugs against 
such releases (i.e. "affects version" won't work).

Thus using "Archive" is *not* the right thing to do (blame Atlassian for 
this :)

What we *did* do in the past is once the GA/final is out we archive the 
alpha/beta's of those release that are no longer "relevant" (i.e. beyond 
2 major releases back).

You should be able to see that pattern in the "Manage Versions" tab.

Thus I have reverted the "bad" versions archives I could find and went 
back and archived older versions to at least clean up the version combo 
list.

About the issue of "accidentally assign things to 9.0.0 fix versions" - 
that is one of the things jiralint checks
for 
(https://github.com/maxandersen/jiralint/blob/master/reports-weekly.json#L27) 
so this should show up if it
ever happens.

/max

> Thanks Nick!
>
> On 12/18/2015 02:49 PM, Nick Boldt wrote:
>> I've archived some of our old, completed releases in JIRA so that
>> people are less likely to accidentally assign things to 9.0.0
>> fixversions when they mean 9.1.0.
>>
>> Context: 
>> https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>
>> If you have objections to this or find it prevents you from doing
>> something you need to w/ JIRA, let me know and I can revert the
>> change.
>>
>> Have a good weekend!
>>
>
> _______________________________________________
> 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/20160104/d825f5d6/attachment.html 

From nboldt at redhat.com  Mon Jan  4 10:53:16 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 4 Jan 2016 10:53:16 -0500
Subject: [jbosstools-dev] I have archived the JBIDE 4.3.0 and JBDS 9.0.0
 releases in JIRA
In-Reply-To: <CD0EA3F9-8710-4AE7-AC0F-EC2565C01D38@redhat.com>
References: <CA+QcL111+hfcbYQ8eWDQr7FBdmCvEC-X3ytJJQE=3-k9ZgBNxg@mail.gmail.com>
	<567463FC.4020805@redhat.com>
	<CD0EA3F9-8710-4AE7-AC0F-EC2565C01D38@redhat.com>
Message-ID: <CA+QcL10Pz+igoUaaR7aEcyWQJfCsYk+S8A3gF-HH7-9SB+N6Xg@mail.gmail.com>

So... you want me to re-enable the 4.3.0.Final and 9.0.0.GA
fixversions in JIRA?

Alexey, Max, please achieve quorum and confirm what course of action
you'd like taken.

Nick

On Mon, Jan 4, 2016 at 4:50 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
> We never in the past did this since it affects the release overview making
> it not list the latest releases nor can you open bugs against such releases
> (i.e. "affects version" won't work).
>
> Thus using "Archive" is not the right thing to do (blame Atlassian for this
> :)
>
> What we did do in the past is once the GA/final is out we archive the
> alpha/beta's of those release that are no longer "relevant" (i.e. beyond 2
> major releases back).
>
> You should be able to see that pattern in the "Manage Versions" tab.
>
> Thus I have reverted the "bad" versions archives I could find and went back
> and archived older versions to at least clean up the version combo list.
>
> About the issue of "accidentally assign things to 9.0.0 fix versions" - that
> is one of the things jiralint checks
> for
> (https://github.com/maxandersen/jiralint/blob/master/reports-weekly.json#L27)
> so this should show up if it
> ever happens.
>
> /max
>
> Thanks Nick!
>
> On 12/18/2015 02:49 PM, Nick Boldt wrote:
>
> I've archived some of our old, completed releases in JIRA so that
> people are less likely to accidentally assign things to 9.0.0
> fixversions when they mean 9.1.0.
>
> Context:
> https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>
> If you have objections to this or find it prevents you from doing
> something you need to w/ JIRA, let me know and I can revert the
> change.
>
> Have a good weekend!
>
> ________________________________
>
> 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



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

From alkazako at redhat.com  Mon Jan  4 11:02:26 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Mon, 4 Jan 2016 11:02:26 -0500
Subject: [jbosstools-dev] I have archived the JBIDE 4.3.0 and JBDS 9.0.0
 releases in JIRA
In-Reply-To: <CA+QcL10Pz+igoUaaR7aEcyWQJfCsYk+S8A3gF-HH7-9SB+N6Xg@mail.gmail.com>
References: <CA+QcL111+hfcbYQ8eWDQr7FBdmCvEC-X3ytJJQE=3-k9ZgBNxg@mail.gmail.com>
	<567463FC.4020805@redhat.com>
	<CD0EA3F9-8710-4AE7-AC0F-EC2565C01D38@redhat.com>
	<CA+QcL10Pz+igoUaaR7aEcyWQJfCsYk+S8A3gF-HH7-9SB+N6Xg@mail.gmail.com>
Message-ID: <568A9792.2030800@redhat.com>

I didn't know that we can't use archived versions as affect versions. 
So, I agree with Max that we have to keep them enabled.

On 01/04/2016 10:53 AM, Nick Boldt wrote:
> So... you want me to re-enable the 4.3.0.Final and 9.0.0.GA
> fixversions in JIRA?
>
> Alexey, Max, please achieve quorum and confirm what course of action
> you'd like taken.
>
> Nick
>
> On Mon, Jan 4, 2016 at 4:50 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
>> We never in the past did this since it affects the release overview making
>> it not list the latest releases nor can you open bugs against such releases
>> (i.e. "affects version" won't work).
>>
>> Thus using "Archive" is not the right thing to do (blame Atlassian for this
>> :)
>>
>> What we did do in the past is once the GA/final is out we archive the
>> alpha/beta's of those release that are no longer "relevant" (i.e. beyond 2
>> major releases back).
>>
>> You should be able to see that pattern in the "Manage Versions" tab.
>>
>> Thus I have reverted the "bad" versions archives I could find and went back
>> and archived older versions to at least clean up the version combo list.
>>
>> About the issue of "accidentally assign things to 9.0.0 fix versions" - that
>> is one of the things jiralint checks
>> for
>> (https://github.com/maxandersen/jiralint/blob/master/reports-weekly.json#L27)
>> so this should show up if it
>> ever happens.
>>
>> /max
>>
>> Thanks Nick!
>>
>> On 12/18/2015 02:49 PM, Nick Boldt wrote:
>>
>> I've archived some of our old, completed releases in JIRA so that
>> people are less likely to accidentally assign things to 9.0.0
>> fixversions when they mean 9.1.0.
>>
>> Context:
>> https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>
>> If you have objections to this or find it prevents you from doing
>> something you need to w/ JIRA, let me know and I can revert the
>> change.
>>
>> Have a good weekend!
>>
>> ________________________________
>>
>> 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
>
>


From manderse at redhat.com  Mon Jan  4 11:02:57 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 04 Jan 2016 17:02:57 +0100
Subject: [jbosstools-dev] I have archived the JBIDE 4.3.0 and JBDS 9.0.0
 releases in JIRA
In-Reply-To: <CA+QcL10Pz+igoUaaR7aEcyWQJfCsYk+S8A3gF-HH7-9SB+N6Xg@mail.gmail.com>
References: <CA+QcL111+hfcbYQ8eWDQr7FBdmCvEC-X3ytJJQE=3-k9ZgBNxg@mail.gmail.com>
	<567463FC.4020805@redhat.com>
	<CD0EA3F9-8710-4AE7-AC0F-EC2565C01D38@redhat.com>
	<CA+QcL10Pz+igoUaaR7aEcyWQJfCsYk+S8A3gF-HH7-9SB+N6Xg@mail.gmail.com>
Message-ID: <1E2B1BD7-0C3D-4776-A542-EEEC0071F583@redhat.com>

On 4 Jan 2016, at 16:53, Nick Boldt wrote:

> So... you want me to re-enable the 4.3.0.Final and 9.0.0.GA
> fixversions in JIRA?

As mentioned, I already did that.

> Alexey, Max, please achieve quorum and confirm what course of action
> you'd like taken.

If you can come up with a reason why we would like to give up being able 
to use versions in
affects-version and not be able to see what our release and roadmap 
history have been let me hear it.

/max

> Nick
>
> On Mon, Jan 4, 2016 at 4:50 AM, Max Rydahl Andersen 
> <manderse at redhat.com> wrote:
>> We never in the past did this since it affects the release overview 
>> making
>> it not list the latest releases nor can you open bugs against such 
>> releases
>> (i.e. "affects version" won't work).
>>
>> Thus using "Archive" is not the right thing to do (blame Atlassian 
>> for this
>> :)
>>
>> What we did do in the past is once the GA/final is out we archive the
>> alpha/beta's of those release that are no longer "relevant" (i.e. 
>> beyond 2
>> major releases back).
>>
>> You should be able to see that pattern in the "Manage Versions" tab.
>>
>> Thus I have reverted the "bad" versions archives I could find and 
>> went back
>> and archived older versions to at least clean up the version combo 
>> list.
>>
>> About the issue of "accidentally assign things to 9.0.0 fix versions" 
>> - that
>> is one of the things jiralint checks
>> for
>> (https://github.com/maxandersen/jiralint/blob/master/reports-weekly.json#L27)
>> so this should show up if it
>> ever happens.
>>
>> /max
>>
>> Thanks Nick!
>>
>> On 12/18/2015 02:49 PM, Nick Boldt wrote:
>>
>> I've archived some of our old, completed releases in JIRA so that
>> people are less likely to accidentally assign things to 9.0.0
>> fixversions when they mean 9.1.0.
>>
>> Context:
>> https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>
>> If you have objections to this or find it prevents you from doing
>> something you need to w/ JIRA, let me know and I can revert the
>> change.
>>
>> Have a good weekend!
>>
>> ________________________________
>>
>> 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
>
>
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com


/max
http://about.me/maxandersen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160104/de518050/attachment.html 

From nboldt at redhat.com  Mon Jan  4 11:53:40 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 4 Jan 2016 11:53:40 -0500
Subject: [jbosstools-dev] I have archived the JBIDE 4.3.0 and JBDS 9.0.0
 releases in JIRA
In-Reply-To: <1E2B1BD7-0C3D-4776-A542-EEEC0071F583@redhat.com>
References: <CA+QcL111+hfcbYQ8eWDQr7FBdmCvEC-X3ytJJQE=3-k9ZgBNxg@mail.gmail.com>
	<567463FC.4020805@redhat.com>
	<CD0EA3F9-8710-4AE7-AC0F-EC2565C01D38@redhat.com>
	<CA+QcL10Pz+igoUaaR7aEcyWQJfCsYk+S8A3gF-HH7-9SB+N6Xg@mail.gmail.com>
	<1E2B1BD7-0C3D-4776-A542-EEEC0071F583@redhat.com>
Message-ID: <CA+QcL12Y8X+xcK_3VfEssHkgMv+NBYeWkajGVsKHYSxHtpZCKQ@mail.gmail.com>

"If you can come up with a reason why we would like to give up being
able to use versions in
affects-version and not be able to see what our release and roadmap
history have been let me hear it."

While a user could definitely set affectsVersion = 4.3.2.Beta2 instead
of 4.3.0.Final even if they're using 4.3.0 to log an issue, I'm not
saying I'd recommend forcing that behaviour.

So... nope. No reasons come to mind.

N

On Mon, Jan 4, 2016 at 11:02 AM, Max Rydahl Andersen
<manderse at redhat.com> wrote:
> On 4 Jan 2016, at 16:53, Nick Boldt wrote:
>
> So... you want me to re-enable the 4.3.0.Final and 9.0.0.GA
> fixversions in JIRA?
>
> As mentioned, I already did that.
>
> Alexey, Max, please achieve quorum and confirm what course of action
> you'd like taken.
>
> If you can come up with a reason why we would like to give up being able to
> use versions in
> affects-version and not be able to see what our release and roadmap history
> have been let me hear it.
>
> /max
>
> Nick
>
> On Mon, Jan 4, 2016 at 4:50 AM, Max Rydahl Andersen manderse at redhat.com
> wrote:
>
> We never in the past did this since it affects the release overview making
> it not list the latest releases nor can you open bugs against such releases
> (i.e. "affects version" won't work).
>
> Thus using "Archive" is not the right thing to do (blame Atlassian for this
> :)
>
> What we did do in the past is once the GA/final is out we archive the
> alpha/beta's of those release that are no longer "relevant" (i.e. beyond 2
> major releases back).
>
> You should be able to see that pattern in the "Manage Versions" tab.
>
> Thus I have reverted the "bad" versions archives I could find and went back
> and archived older versions to at least clean up the version combo list.
>
> About the issue of "accidentally assign things to 9.0.0 fix versions" - that
> is one of the things jiralint checks
> for
> (https://github.com/maxandersen/jiralint/blob/master/reports-weekly.json#L27)
> so this should show up if it
> ever happens.
>
> /max
>
> Thanks Nick!
>
> On 12/18/2015 02:49 PM, Nick Boldt wrote:
>
> I've archived some of our old, completed releases in JIRA so that
> people are less likely to accidentally assign things to 9.0.0
> fixversions when they mean 9.1.0.
>
> Context:
> https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>
> If you have objections to this or find it prevents you from doing
> something you need to w/ JIRA, let me know and I can revert the
> change.
>
> Have a good weekend!
>
> ________________________________
>
> 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
>
> --
> 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 noreply at t-kin.com  Wed Jan  6 09:53:05 2016
From: noreply at t-kin.com (New-Canadian-Meds)
Date: Wed, 6 Jan 2016 17:53:05 +0300
Subject: [jbosstools-dev] Top quality most effective medications is the only
	thing you can find at our pharmacy!
Message-ID: <E1J37xR-0006ts-70@6D34013C>

   

		Nudge the trans atlantic to comparable airline. Sig sauer inc and
overcoming them. Attain the percentage of authority license plates and
pads stuck. 

		Me
		ds
		6f
		or
		9M
		en

Vi
Ci
Ci
Le
Pr
 ag
al
al
vi
op
 ra
is
is
tr
ec

 S
a 
ia

of

t 

Ta

bs

 $0
$1
$2
$2
$0
 .9
.6
.5
.5
.4
 9
5
0
0
5

		Me
		ds
		7f
		or
		1W
		om
		en

Ac
Cl
De
Fe
Fe
 om
om
fl
ma
ma
 pl
id
uc
le
le
 ia

an
 C
 V

ia
ia

li
gr

s 
a 

 $1
$0
$1
$1
$0
 .7
.4
.2
.1
.7
 5
5
5
1
2

 On
24
Fa
Sp ly
/7
st
ec  r
 c
 w
ia el
us
or
l  ia
to
ld
in bl
me
wi
te e 
r 
de
rn su
su
 s
et pp
pp
hi
 p li
or
pp
ri er
t 
in
ce s 

g 
s   

   A
 N
 1
 V no
o 
00
is ny
pr
% 
a, mo
es
Au
Ma us
cr
th
st  d
ip
en
er el
ti
ti
ca iv
on
c 
rd er
 r
Me
,E y 
eq
ds
ch  
ui

ec  
re

k   
d

		>> Enter Here 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160106/7c19c6ef/attachment-0001.html 

From promos at master-zen.com  Fri Jan  8 07:23:51 2016
From: promos at master-zen.com (Gruppo Re GmbH)
Date: Fri, 8 Jan 2016 13:23:51 +0100
Subject: [jbosstools-dev] Gruppo Re GmbH thermische PVC Glasfaserfenster
Message-ID: <ZmFsY29uOzEzMC4xOTMuMTA3LjEzO2pib3NzaWRlLWRldkBsaXN0cy5qYm9zcy5vcmc7MTcyOTs4NDk5MzU7MTcyOTs7MjAxNjAxMDgtNTY4ZmFhNDVkMjJmNg==@ds.master-zen.com>

tu mejor opcion 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%22849935%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/20160108/83b2a3ad/attachment.html 

From nboldt at redhat.com  Fri Jan  8 11:37:44 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 8 Jan 2016 11:37:44 -0500
Subject: [jbosstools-dev] Tycho 0.25.0 will require Java 8
Message-ID: <CAAOoWTQPK4a8xErqonCb_9ZCScvq3PqWbMmuLkHdSGxUgqkqiQ@mail.gmail.com>

FYI, when we move to Tycho 0.25 some time this year, we will also lose
support for building ANY of JBT 4.4/JBDS 10 with Java 7; we will need
to use Java 8 only.

In related news, Java 9 will be feature complete in May 2016, and
released in March 2017. http://openjdk.java.net/projects/jdk9/

---------- Forwarded message ----------
From: Sievers, Jan <jan.sievers at sap.com>
Date: Fri, Jan 8, 2016 at 10:39 AM
Subject: [tycho-user] Tycho 0.25.0 will require Java 8
To: Tycho list <tycho-user at eclipse.org>


just a heads up, while working on upgrading Tycho to a recent Neon
milestone [1], I noticed some of the eclipse bundles Tycho uses
internally have bumped their BREE to JavaSE-1.8 [2]

This means Tycho will effectively require Java 8 with the next release.
Note that you will still be able to build against/run tests using
older JDKs using maven toolchains [3,4]

Regards
Jan

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=485427
[2] https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml#appendix
[3] https://eclipse.org/tycho/sitedocs/tycho-compiler-plugin/compile-mojo.html#useJDK
[4] https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/test-mojo.html#useJDK

_______________________________________________
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 Jan  8 14:43:00 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 8 Jan 2016 14:43:00 -0500
Subject: [jbosstools-dev] Planning a new Locus 1.5 release
Message-ID: <CA+QcL12kGCN79UTyfZZGnfvyRzfqUr6PNkYx67Nss2i78-PJuA@mail.gmail.com>

I see there are 6 issues unresolved for Locus:

https://issues.jboss.org/issues/?jql=project%20%3D%20LOCUS%20AND%20resolution%20%3D%20Unresolved

I've slipped a couple that had fixversion = 1.3 (released months ago)
to 1.5, but those could also be moved to LATER if they're not going to
get done for 1.5.

Of the issues now set for fixversion=1.5, only one seems relatively important:

* LOCUS-49

And one could be done quickly while we're doing the 1.5 release:

* LOCUS-46

Anyone have a desire to get a new release out, and if so, when would
you need/want that?

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

From pleacu at redhat.com  Fri Jan  8 15:37:12 2016
From: pleacu at redhat.com (Paul Leacu)
Date: Fri, 8 Jan 2016 15:37:12 -0500 (EST)
Subject: [jbosstools-dev] Planning a new Locus 1.5 release
In-Reply-To: <CA+QcL12kGCN79UTyfZZGnfvyRzfqUr6PNkYx67Nss2i78-PJuA@mail.gmail.com>
References: <CA+QcL12kGCN79UTyfZZGnfvyRzfqUr6PNkYx67Nss2i78-PJuA@mail.gmail.com>
Message-ID: <1755910372.5905711.1452285432765.JavaMail.zimbra@redhat.com>


   Hey Nick -
       Yes - I'll be generating a PR for LOCUS-49 soon - perhaps a locus 1.5-SNAPSHOT can
   come out next week?  Perhaps a release the week after??
                        Thanks!
                              --paull



----- Original Message -----
> From: "Nick Boldt" <nboldt at redhat.com>
> To: jbosstools-dev at lists.jboss.org, "Paul Leacu" <pleacu at redhat.com>, "Mickael Istria" <mistria at redhat.com>
> Sent: Friday, January 8, 2016 2:43:00 PM
> Subject: Planning a new Locus 1.5 release
> 
> I see there are 6 issues unresolved for Locus:
> 
> https://issues.jboss.org/issues/?jql=project%20%3D%20LOCUS%20AND%20resolution%20%3D%20Unresolved
> 
> I've slipped a couple that had fixversion = 1.3 (released months ago)
> to 1.5, but those could also be moved to LATER if they're not going to
> get done for 1.5.
> 
> Of the issues now set for fixversion=1.5, only one seems relatively
> important:
> 
> * LOCUS-49
> 
> And one could be done quickly while we're doing the 1.5 release:
> 
> * LOCUS-46
> 
> Anyone have a desire to get a new release out, and if so, when would
> you need/want that?
> 
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> 

From mistria at redhat.com  Tue Jan 12 02:19:49 2016
From: mistria at redhat.com (Mickael Istria)
Date: Tue, 12 Jan 2016 08:19:49 +0100
Subject: [jbosstools-dev] Need help for an icon in EGit
Message-ID: <5694A915.5010909@redhat.com>

Hi all,

I'm working on https://bugs.eclipse.org/bugs/show_bug.cgi?id=485124 / 
https://git.eclipse.org/r/#/c/63842 which is about "specifying" a pull 
operation in EGit. Currently I'm using same icon as the "default" pull, 
but having twice the same icon in action bars or menus isn't really 
something good for users. So we need to figure out an icon for this 
operation, or reconsider the icon for the default pull operation.
I gave it a few thoughts, but didn't manage to find something clean.
Can someone with experience/interest in icon design give it a look? 
Should I escalate it to Red Hat design team?

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/20160112/e957eb23/attachment.html 

From manderse at redhat.com  Tue Jan 12 05:05:16 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 12 Jan 2016 10:05:16 +0000
Subject: [jbosstools-dev] Need help for an icon in EGit
In-Reply-To: <5694A915.5010909@redhat.com>
References: <5694A915.5010909@redhat.com>
Message-ID: <5DF27E46-D1EC-45C2-B7DA-E544B17F23F4@redhat.com>

On 12 Jan 2016, at 7:19, Mickael Istria wrote:

> Hi all,
>
> I'm working on https://bugs.eclipse.org/bugs/show_bug.cgi?id=485124 / 
> https://git.eclipse.org/r/#/c/63842 which is about "specifying" a pull 
> operation in EGit. Currently I'm using same icon as the "default" 
> pull, but having twice the same icon in action bars or menus isn't 
> really something good for users.

Depends...here is how File > New looks:

![](cid:42D751BB-677F-4F06-A545-6DFFA9810573 at redhat.com 
"Screenshot_12_01_16_10_02.png")

Notice how the same icon is used 3 times.

> So we need to figure out an icon for this operation, or reconsider the 
> icon for the default pull operation.
> I gave it a few thoughts, but didn't manage to find something clean.

Another option is to not have icon for the "Pull..."

> Can someone with experience/interest in icon design give it a look? 
> Should I escalate it to Red Hat design team?

adding issues on DESIGN is the way for now, yes.

/max

>
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160112/94d6c076/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot_12_01_16_10_02.png
Type: image/png
Size: 62245 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160112/94d6c076/attachment-0001.png 

From mistria at redhat.com  Tue Jan 12 05:06:52 2016
From: mistria at redhat.com (Mickael Istria)
Date: Tue, 12 Jan 2016 11:06:52 +0100
Subject: [jbosstools-dev] Need help for an icon in EGit
In-Reply-To: <5DF27E46-D1EC-45C2-B7DA-E544B17F23F4@redhat.com>
References: <5694A915.5010909@redhat.com>
	<5DF27E46-D1EC-45C2-B7DA-E544B17F23F4@redhat.com>
Message-ID: <5694D03C.2040208@redhat.com>

 > Depends...here is how File > New looks:

For menus, it's ok. The comment from EGit committers was more focused on 
toolbars, where only picture is shown.
-- 
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/20160112/3df06702/attachment.html 

From nboldt at redhat.com  Wed Jan 13 15:04:13 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 13 Jan 2016 15:04:13 -0500
Subject: [jbosstools-dev] Planning a new Locus 1.5 release
In-Reply-To: <1755910372.5905711.1452285432765.JavaMail.zimbra@redhat.com>
References: <CA+QcL12kGCN79UTyfZZGnfvyRzfqUr6PNkYx67Nss2i78-PJuA@mail.gmail.com>
	<1755910372.5905711.1452285432765.JavaMail.zimbra@redhat.com>
Message-ID: <CA+QcL11JowCQBATCxOKM7vreJWbc-tppMewa7qHWWJbsfRvVFA@mail.gmail.com>

Snapshot is available now.

https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/locus/jbosstools-locus/1.5.0-SNAPSHOT/jbosstools-locus-1.5.0-SNAPSHOT-updatesite.zip-unzip/

Release can be whenever we decide we've done enough for 1.5 to warrant
a release. So far, we have 1 bugfix (LOCUS-46) and 1 pair of new
plugins added (LOCUS-49).

@Denis, want to fix https://issues.jboss.org/browse/LOCUS-47 ?
@Mickael, want to fix https://issues.jboss.org/browse/LOCUS-15 ?

Paul, you're happy with the fix for LOCUS-49 (including the new URL
for the update site due to LOCUS-46), then we can release as soon as
@Denis and @Mickael confirm if they want either of those issues
resolved for this release.



On Fri, Jan 8, 2016 at 3:37 PM, Paul Leacu <pleacu at redhat.com> wrote:
>
>    Hey Nick -
>        Yes - I'll be generating a PR for LOCUS-49 soon - perhaps a locus 1.5-SNAPSHOT can
>    come out next week?  Perhaps a release the week after??
>                         Thanks!
>                               --paull
>
>
>
> ----- Original Message -----
>> From: "Nick Boldt" <nboldt at redhat.com>
>> To: jbosstools-dev at lists.jboss.org, "Paul Leacu" <pleacu at redhat.com>, "Mickael Istria" <mistria at redhat.com>
>> Sent: Friday, January 8, 2016 2:43:00 PM
>> Subject: Planning a new Locus 1.5 release
>>
>> I see there are 6 issues unresolved for Locus:
>>
>> https://issues.jboss.org/issues/?jql=project%20%3D%20LOCUS%20AND%20resolution%20%3D%20Unresolved
>>
>> I've slipped a couple that had fixversion = 1.3 (released months ago)
>> to 1.5, but those could also be moved to LATER if they're not going to
>> get done for 1.5.
>>
>> Of the issues now set for fixversion=1.5, only one seems relatively
>> important:
>>
>> * LOCUS-49
>>
>> And one could be done quickly while we're doing the 1.5 release:
>>
>> * LOCUS-46
>>
>> Anyone have a desire to get a new release out, and if so, when would
>> you need/want that?
>>
>> --
>> 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 noreply at roadpackeraz.com  Thu Jan 14 12:21:19 2016
From: noreply at roadpackeraz.com (New-Canadian-Meds)
Date: Thu, 14 Jan 2016 22:21:19 +0500
Subject: [jbosstools-dev] Our philosophy is simple: to provide people with
	best quality medications at discounts!
Message-ID: <2016011464444.gH0qi4tVe5a2@roadpackeraz.com>

   

		8p she also climax, they cost activex includes offprints of mediums
comments. Knightley galleriesout a wet suit, silver colored step back.


		Me
		ds
		1f
		or
		7M
		en

Vi
Ci
Ci
Le
Pr
 ag
al
al
vi
op
 ra
is
is
tr
ec

 S
a 
ia

of

t 

Ta

bs

 $0
$1
$2
$2
$0
 .9
.6
.5
.5
.4
 9
5
0
0
5

		Me
		ds
		5f
		or
		8W
		om
		en

Ac
Cl
De
Fe
Fe
 om
om
fl
ma
ma
 pl
id
uc
le
le
 ia

an
 C
 V

ia
ia

li
gr

s 
a 

 $1
$0
$1
$1
$0
 .7
.4
.2
.1
.7
 5
5
5
1
2

 10
An
Fa
On 0%
on
st
ly  A
ym
 w
 r ut
ou
or
el he
s 
ld
ia nt
de
wi
bl ic
li
de
e   M
ve
 s
su ed
ry
hi
pp s 

pp
li  

in
er  

g 
s   

   S
 2
 V
 N pe
4/
is
o  ci
7 
a,
pr al
cu
Ma
es  i
st
st
cr nt
om
er
ip er
er
ca
ti ne
 s
rd
on t 
up
,E
 r pr
po
ch
eq ic
rt
ec
ui es

k 
re  

d 

		>> Enter Here 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160114/92531496/attachment.html 

From nboldt at redhat.com  Fri Jan 15 12:15:14 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 15 Jan 2016 12:15:14 -0500
Subject: [jbosstools-dev] Target Platform Changes coming next week :: PLEASE
	READ
Message-ID: <CA+QcL12iD_nwOHeA6pPasv63Ru5Cn8D_iZbxT+wnB+bbsqk9ew@mail.gmail.com>

With the code freeze for JBoss Tools 4.3.1.Beta2 next Thursday Jan 21,
it's once again time to update our target platforms.

Here's the current list of planned changes.

JBIDE-21366 Include nightly build of Docker tooling in TP
JBIDE-21405 Add RedDeer 1.0.1 to target platform
JBIDE-21377 Include Yaml editor in JBoss Tools (& JBDS) via feature
dep from o.j.t.central & add to CoreTools category, too
JBDS-3566 include AERI in JBDS

If you have something else that needs updating, please link those
JIRAs/Bugzillas to this JIRA:

JBIDE-21406 Create and use Mars.2 RC1 target platform

---

If the change should ALSO be done in the Neon stream (JBT 4.4 / JBDS
10) please also link to this issue:

JBIDE-21386 Create and use Neon M5 target platform

Neon M5 will be available between Jan 29 and Feb 5 [1], so we'll be
updating the Neon TP soon too.

[1] https://wiki.eclipse.org/Neon/Simultaneous_Release_Plan#Schedule

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

From mistria at redhat.com  Tue Jan 19 01:56:10 2016
From: mistria at redhat.com (Mickael Istria)
Date: Tue, 19 Jan 2016 07:56:10 +0100
Subject: [jbosstools-dev] Why a 4.51.1.x branch for TP
Message-ID: <569DDE0A.70500@redhat.com>

Hi Nick,

I noticed a branch called 4.51.1.x. Why was it necessary? I would expect 
those change to happen on the 4.51.x branch.
This makes it unclear what's the current "best" branch for 4.51.x stream.

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/20160119/1b10d636/attachment-0001.html 

From promos at master-zen.com  Tue Jan 19 03:25:31 2016
From: promos at master-zen.com (info@youritalianorigins.com)
Date: Tue, 19 Jan 2016 09:25:31 +0100
Subject: [jbosstools-dev] Ottieni lo stemma della tua casata con spilla in
	omaggio
Message-ID: <ZmFsY29uOzEzMC4xOTMuMTExLjI0O2pib3NzaWRlLWRldkBsaXN0cy5qYm9zcy5vcmc7MTcyOTs4NTcxNDY7MTcyOTs7MjAxNjAxMTktNTY5ZGYyZjU5NTdhNQ==@ds.master-zen.com>

Tu mejor oferta Per cancellarsi dalla lista di sottoscrizione, segui questo link: http://ds.master-zen.com/fur.php?c=%7B%22idCli%22%3A%221729%22%2C%22idCamp%22%3A%22857146%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/20160119/dc2e1836/attachment.html 

From mlabuda at redhat.com  Tue Jan 19 10:29:26 2016
From: mlabuda at redhat.com (Marian Labuda)
Date: Tue, 19 Jan 2016 10:29:26 -0500 (EST)
Subject: [jbosstools-dev]  Create a new component for CDK in JIRA
In-Reply-To: <883877080.15117491.1453217254003.JavaMail.zimbra@redhat.com>
Message-ID: <498524055.15118504.1453217366403.JavaMail.zimbra@redhat.com>

Hi,

could someone please create a new component for CDK in JIRA? Currently CDK is included in openshift component, but QE owners of CDK is mmalina and openshift is mine. On GitHub its in same repo (at least for now?), but in JIRA its crucial for us. It would simplify process of verifying and also it could produce more reasonable statistics of resolved JIRAs.

Thanks

Mari?n Labuda
JBoss JBDS QE


From nboldt at redhat.com  Tue Jan 19 10:39:34 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 19 Jan 2016 10:39:34 -0500
Subject: [jbosstools-dev] Create a new component for CDK in JIRA
In-Reply-To: <498524055.15118504.1453217366403.JavaMail.zimbra@redhat.com>
References: <883877080.15117491.1453217254003.JavaMail.zimbra@redhat.com>
	<498524055.15118504.1453217366403.JavaMail.zimbra@redhat.com>
Message-ID: <CA+QcL10TvN6+CYtnePJyBy5UvH-qd2TTgD2WKQBV8sUTVY+dtg@mail.gmail.com>

To be clear, you want one in JBIDE and JBDS, too. Correct?

@Max or @Alexey, this is your cue to disagree before I create them. :D

On Tue, Jan 19, 2016 at 10:29 AM, Marian Labuda <mlabuda at redhat.com> wrote:
> Hi,
>
> could someone please create a new component for CDK in JIRA? Currently CDK is included in openshift component, but QE owners of CDK is mmalina and openshift is mine. On GitHub its in same repo (at least for now?), but in JIRA its crucial for us. It would simplify process of verifying and also it could produce more reasonable statistics of resolved JIRAs.
>
> Thanks
>
> Mari?n Labuda
> JBoss JBDS QE
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev



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


From nboldt at redhat.com  Tue Jan 19 10:43:15 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 19 Jan 2016 10:43:15 -0500
Subject: [jbosstools-dev] Why a 4.51.1.x branch for TP
In-Reply-To: <569DDE0A.70500@redhat.com>
References: <569DDE0A.70500@redhat.com>
Message-ID: <CA+QcL13-YqHyVBBGfOHLke5OPaKWhXY9vf+VVQWwp2rA6bjeFg@mail.gmail.com>

That was created in case we needed to do something in 9.0.1 which was
different from 9.0.0.

Ignore it. New TP should be in the 4.52.x branch (because Mars.2).

On Tue, Jan 19, 2016 at 1:56 AM, Mickael Istria <mistria at redhat.com> wrote:
> Hi Nick,
>
> I noticed a branch called 4.51.1.x. Why was it necessary? I would expect
> those change to happen on the 4.51.x branch.
> This makes it unclear what's the current "best" branch for 4.51.x stream.
>
> Cheers,
> --
> 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



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

From mlabuda at redhat.com  Tue Jan 19 10:46:26 2016
From: mlabuda at redhat.com (Marian Labuda)
Date: Tue, 19 Jan 2016 10:46:26 -0500 (EST)
Subject: [jbosstools-dev] Create a new component for CDK in JIRA
In-Reply-To: <CA+QcL10TvN6+CYtnePJyBy5UvH-qd2TTgD2WKQBV8sUTVY+dtg@mail.gmail.com>
References: <883877080.15117491.1453217254003.JavaMail.zimbra@redhat.com>
	<498524055.15118504.1453217366403.JavaMail.zimbra@redhat.com>
	<CA+QcL10TvN6+CYtnePJyBy5UvH-qd2TTgD2WKQBV8sUTVY+dtg@mail.gmail.com>
Message-ID: <1759923045.15129351.1453218386705.JavaMail.zimbra@redhat.com>

Yeah, one in JBIDE and one in JBDS.

----- Original Message -----
From: "Nick Boldt" <nboldt at redhat.com>
To: "Marian Labuda" <mlabuda at redhat.com>
Cc: jbosstools-dev at lists.jboss.org, "jboss-jbds-qe" <jboss-jbds-qe at redhat.com>
Sent: Tuesday, January 19, 2016 4:39:34 PM
Subject: Re: [jbosstools-dev] Create a new component for CDK in JIRA

To be clear, you want one in JBIDE and JBDS, too. Correct?

@Max or @Alexey, this is your cue to disagree before I create them. :D

On Tue, Jan 19, 2016 at 10:29 AM, Marian Labuda <mlabuda at redhat.com> wrote:
> Hi,
>
> could someone please create a new component for CDK in JIRA? Currently CDK is included in openshift component, but QE owners of CDK is mmalina and openshift is mine. On GitHub its in same repo (at least for now?), but in JIRA its crucial for us. It would simplify process of verifying and also it could produce more reasonable statistics of resolved JIRAs.
>
> Thanks
>
> Mari?n Labuda
> JBoss JBDS QE
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev



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


From alkazako at redhat.com  Tue Jan 19 11:06:10 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Tue, 19 Jan 2016 11:06:10 -0500
Subject: [jbosstools-dev] Create a new component for CDK in JIRA
In-Reply-To: <1759923045.15129351.1453218386705.JavaMail.zimbra@redhat.com>
References: <883877080.15117491.1453217254003.JavaMail.zimbra@redhat.com>
	<498524055.15118504.1453217366403.JavaMail.zimbra@redhat.com>
	<CA+QcL10TvN6+CYtnePJyBy5UvH-qd2TTgD2WKQBV8sUTVY+dtg@mail.gmail.com>
	<1759923045.15129351.1453218386705.JavaMail.zimbra@redhat.com>
Message-ID: <569E5EF2.60806@redhat.com>


CDK is currently about the CDK server adapter only, correct? So it's a 
tiny component. But anyway If creating a new component helps developers 
and QE then why not create it?
I'm OK with that but Max could disagree :)

Thanks.

On 01/19/2016 10:46 AM, Marian Labuda wrote:
> Yeah, one in JBIDE and one in JBDS.
>
> ----- Original Message -----
> From: "Nick Boldt" <nboldt at redhat.com>
> To: "Marian Labuda" <mlabuda at redhat.com>
> Cc: jbosstools-dev at lists.jboss.org, "jboss-jbds-qe" <jboss-jbds-qe at redhat.com>
> Sent: Tuesday, January 19, 2016 4:39:34 PM
> Subject: Re: [jbosstools-dev] Create a new component for CDK in JIRA
>
> To be clear, you want one in JBIDE and JBDS, too. Correct?
>
> @Max or @Alexey, this is your cue to disagree before I create them. :D
>
> On Tue, Jan 19, 2016 at 10:29 AM, Marian Labuda <mlabuda at redhat.com> wrote:
>> Hi,
>>
>> could someone please create a new component for CDK in JIRA? Currently CDK is included in openshift component, but QE owners of CDK is mmalina and openshift is mine. On GitHub its in same repo (at least for now?), but in JIRA its crucial for us. It would simplify process of verifying and also it could produce more reasonable statistics of resolved JIRAs.
>>
>> Thanks
>>
>> Mari?n Labuda
>> JBoss JBDS QE
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>


From manderse at redhat.com  Tue Jan 19 11:07:30 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 19 Jan 2016 17:07:30 +0100
Subject: [jbosstools-dev] Create a new component for CDK in JIRA
In-Reply-To: <1759923045.15129351.1453218386705.JavaMail.zimbra@redhat.com>
References: <883877080.15117491.1453217254003.JavaMail.zimbra@redhat.com>
	<498524055.15118504.1453217366403.JavaMail.zimbra@redhat.com>
	<CA+QcL10TvN6+CYtnePJyBy5UvH-qd2TTgD2WKQBV8sUTVY+dtg@mail.gmail.com>
	<1759923045.15129351.1453218386705.JavaMail.zimbra@redhat.com>
Message-ID: <E22BE0B2-1AA7-43DA-AB78-29D7CAD4CE70@redhat.com>

On 19 Jan 2016, at 16:46, Marian Labuda wrote:

> Yeah, one in JBIDE and one in JBDS.

+1.

name: cdk, not CDK.

/max

>
> ----- Original Message -----
> From: "Nick Boldt" <nboldt at redhat.com>
> To: "Marian Labuda" <mlabuda at redhat.com>
> Cc: jbosstools-dev at lists.jboss.org, "jboss-jbds-qe" 
> <jboss-jbds-qe at redhat.com>
> Sent: Tuesday, January 19, 2016 4:39:34 PM
> Subject: Re: [jbosstools-dev] Create a new component for CDK in JIRA
>
> To be clear, you want one in JBIDE and JBDS, too. Correct?
>
> @Max or @Alexey, this is your cue to disagree before I create them. :D
>
> On Tue, Jan 19, 2016 at 10:29 AM, Marian Labuda <mlabuda at redhat.com> 
> wrote:
>> Hi,
>>
>> could someone please create a new component for CDK in JIRA? 
>> Currently CDK is included in openshift component, but QE owners of 
>> CDK is mmalina and openshift is mine. On GitHub its in same repo (at 
>> least for now?), but in JIRA its crucial for us. It would simplify 
>> process of verifying and also it could produce more reasonable 
>> statistics of resolved JIRAs.
>>
>> Thanks
>>
>> Mari?n Labuda
>> JBoss JBDS QE
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> -- 
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160119/4ff65ce4/attachment.html 

From nboldt at redhat.com  Tue Jan 19 11:39:15 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 19 Jan 2016 11:39:15 -0500
Subject: [jbosstools-dev] Create a new component for CDK in JIRA
In-Reply-To: <E22BE0B2-1AA7-43DA-AB78-29D7CAD4CE70@redhat.com>
References: <883877080.15117491.1453217254003.JavaMail.zimbra@redhat.com>
	<498524055.15118504.1453217366403.JavaMail.zimbra@redhat.com>
	<CA+QcL10TvN6+CYtnePJyBy5UvH-qd2TTgD2WKQBV8sUTVY+dtg@mail.gmail.com>
	<1759923045.15129351.1453218386705.JavaMail.zimbra@redhat.com>
	<E22BE0B2-1AA7-43DA-AB78-29D7CAD4CE70@redhat.com>
Message-ID: <CA+QcL11F=KQM1mTYurR=_pArZNQDv_gOc0iFBf-71=WifP4Mjw@mail.gmail.com>

I've set mlabuda as component lead since no one said who should own this.

https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page
https://issues.jboss.org/projects/JBDS?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page

Can change it if you have a better owner in mind.



On Tue, Jan 19, 2016 at 11:07 AM, Max Rydahl Andersen
<manderse at redhat.com> wrote:
> On 19 Jan 2016, at 16:46, Marian Labuda wrote:
>
> Yeah, one in JBIDE and one in JBDS.
>
> +1.
>
> name: cdk, not CDK.
>
> /max
>
> ----- Original Message -----
> From: "Nick Boldt" nboldt at redhat.com
> To: "Marian Labuda" mlabuda at redhat.com
> Cc: jbosstools-dev at lists.jboss.org, "jboss-jbds-qe" jboss-jbds-qe at redhat.com
> Sent: Tuesday, January 19, 2016 4:39:34 PM
> Subject: Re: [jbosstools-dev] Create a new component for CDK in JIRA
>
> To be clear, you want one in JBIDE and JBDS, too. Correct?
>
> @Max or @Alexey, this is your cue to disagree before I create them. :D
>
> On Tue, Jan 19, 2016 at 10:29 AM, Marian Labuda mlabuda at redhat.com wrote:
>
> Hi,
>
> could someone please create a new component for CDK in JIRA? Currently CDK
> is included in openshift component, but QE owners of CDK is mmalina and
> openshift is mine. On GitHub its in same repo (at least for now?), but in
> JIRA its crucial for us. It would simplify process of verifying and also it
> could produce more reasonable statistics of resolved JIRAs.
>
> Thanks
>
> Mari?n Labuda
> JBoss JBDS QE
>
> ________________________________
>
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> --
> 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 alkazako at redhat.com  Tue Jan 19 11:45:54 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Tue, 19 Jan 2016 11:45:54 -0500
Subject: [jbosstools-dev] Create a new component for CDK in JIRA
In-Reply-To: <CA+QcL11F=KQM1mTYurR=_pArZNQDv_gOc0iFBf-71=WifP4Mjw@mail.gmail.com>
References: <883877080.15117491.1453217254003.JavaMail.zimbra@redhat.com>
	<498524055.15118504.1453217366403.JavaMail.zimbra@redhat.com>
	<CA+QcL10TvN6+CYtnePJyBy5UvH-qd2TTgD2WKQBV8sUTVY+dtg@mail.gmail.com>
	<1759923045.15129351.1453218386705.JavaMail.zimbra@redhat.com>
	<E22BE0B2-1AA7-43DA-AB78-29D7CAD4CE70@redhat.com>
	<CA+QcL11F=KQM1mTYurR=_pArZNQDv_gOc0iFBf-71=WifP4Mjw@mail.gmail.com>
Message-ID: <569E6842.6000503@redhat.com>

It should be Rob I guess?

On 01/19/2016 11:39 AM, Nick Boldt wrote:
> I've set mlabuda as component lead since no one said who should own this.
>
> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page
> https://issues.jboss.org/projects/JBDS?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page
>
> Can change it if you have a better owner in mind.
>
>
>
> On Tue, Jan 19, 2016 at 11:07 AM, Max Rydahl Andersen
> <manderse at redhat.com> wrote:
>> On 19 Jan 2016, at 16:46, Marian Labuda wrote:
>>
>> Yeah, one in JBIDE and one in JBDS.
>>
>> +1.
>>
>> name: cdk, not CDK.
>>
>> /max
>>
>> ----- Original Message -----
>> From: "Nick Boldt" nboldt at redhat.com
>> To: "Marian Labuda" mlabuda at redhat.com
>> Cc: jbosstools-dev at lists.jboss.org, "jboss-jbds-qe" jboss-jbds-qe at redhat.com
>> Sent: Tuesday, January 19, 2016 4:39:34 PM
>> Subject: Re: [jbosstools-dev] Create a new component for CDK in JIRA
>>
>> To be clear, you want one in JBIDE and JBDS, too. Correct?
>>
>> @Max or @Alexey, this is your cue to disagree before I create them. :D
>>
>> On Tue, Jan 19, 2016 at 10:29 AM, Marian Labuda mlabuda at redhat.com wrote:
>>
>> Hi,
>>
>> could someone please create a new component for CDK in JIRA? Currently CDK
>> is included in openshift component, but QE owners of CDK is mmalina and
>> openshift is mine. On GitHub its in same repo (at least for now?), but in
>> JIRA its crucial for us. It would simplify process of verifying and also it
>> could produce more reasonable statistics of resolved JIRAs.
>>
>> Thanks
>>
>> Mari?n Labuda
>> JBoss JBDS QE
>>
>> ________________________________
>>
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> --
>> 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  Tue Jan 19 12:18:37 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 19 Jan 2016 12:18:37 -0500
Subject: [jbosstools-dev] Create a new component for CDK in JIRA
In-Reply-To: <569E6842.6000503@redhat.com>
References: <883877080.15117491.1453217254003.JavaMail.zimbra@redhat.com>
	<498524055.15118504.1453217366403.JavaMail.zimbra@redhat.com>
	<CA+QcL10TvN6+CYtnePJyBy5UvH-qd2TTgD2WKQBV8sUTVY+dtg@mail.gmail.com>
	<1759923045.15129351.1453218386705.JavaMail.zimbra@redhat.com>
	<E22BE0B2-1AA7-43DA-AB78-29D7CAD4CE70@redhat.com>
	<CA+QcL11F=KQM1mTYurR=_pArZNQDv_gOc0iFBf-71=WifP4Mjw@mail.gmail.com>
	<569E6842.6000503@redhat.com>
Message-ID: <CA+QcL13o-mV2D+_hBpt_u3J+d-dHqYM4WfduCcKSOuPqm8n+_g@mail.gmail.com>

Per convo in #jbosstools, I've switched it to have Rob own 'em.

#messageEnds



On Tue, Jan 19, 2016 at 11:45 AM, Alexey Kazakov <alkazako at redhat.com> wrote:
> It should be Rob I guess?
>
> On 01/19/2016 11:39 AM, Nick Boldt wrote:
>> I've set mlabuda as component lead since no one said who should own this.
>>
>> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page
>> https://issues.jboss.org/projects/JBDS?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page
>>
>> Can change it if you have a better owner in mind.
>>
>>
>>
>> On Tue, Jan 19, 2016 at 11:07 AM, Max Rydahl Andersen
>> <manderse at redhat.com> wrote:
>>> On 19 Jan 2016, at 16:46, Marian Labuda wrote:
>>>
>>> Yeah, one in JBIDE and one in JBDS.
>>>
>>> +1.
>>>
>>> name: cdk, not CDK.
>>>
>>> /max
>>>
>>> ----- Original Message -----
>>> From: "Nick Boldt" nboldt at redhat.com
>>> To: "Marian Labuda" mlabuda at redhat.com
>>> Cc: jbosstools-dev at lists.jboss.org, "jboss-jbds-qe" jboss-jbds-qe at redhat.com
>>> Sent: Tuesday, January 19, 2016 4:39:34 PM
>>> Subject: Re: [jbosstools-dev] Create a new component for CDK in JIRA
>>>
>>> To be clear, you want one in JBIDE and JBDS, too. Correct?
>>>
>>> @Max or @Alexey, this is your cue to disagree before I create them. :D
>>>
>>> On Tue, Jan 19, 2016 at 10:29 AM, Marian Labuda mlabuda at redhat.com wrote:
>>>
>>> Hi,
>>>
>>> could someone please create a new component for CDK in JIRA? Currently CDK
>>> is included in openshift component, but QE owners of CDK is mmalina and
>>> openshift is mine. On GitHub its in same repo (at least for now?), but in
>>> JIRA its crucial for us. It would simplify process of verifying and also it
>>> could produce more reasonable statistics of resolved JIRAs.
>>>
>>> Thanks
>>>
>>> Mari?n Labuda
>>> JBoss JBDS QE
>>>
>>> ________________________________
>>>
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> --
>>> 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



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


From nboldt at redhat.com  Tue Jan 19 13:32:44 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 19 Jan 2016 13:32:44 -0500
Subject: [jbosstools-dev] JBoss Tools Locus - 1.5.0.Final is released
Message-ID: <CA+QcL12DdfGQnEArYcossLAyGOcW1LwPfZD7NjUW=iD_mJPBxA@mail.gmail.com>

On request from the Integration Stack in support of Fuse [1], we
released JBoss Tools Locus 1.5.0.Final today.

[1] https://issues.jboss.org/browse/JBTIS-438

What is Locus?

It's an update site containing OSGi bundles that wrap POJO or maven
content, so they can be used as p2 artifacts instead of maven ones.

Change log:

https://issues.jboss.org/browse/LOCUS-46
https://issues.jboss.org/browse/LOCUS-49
https://issues.jboss.org/browse/JBIDE-21012
https://github.com/jbosstools/jbosstools-locus/compare/1.4.0.Final...1.5.0.Final

The p2 repository (update site and zip) for Locus 1.5.0.Final are
below. Note the filenames have changed since 1.4.0.Final [2].

http://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/locus/jbosstools-locus/1.5.0.Final/jbosstools-locus-1.5.0.Final-updatesite.zip-unzip/
https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/tools/locus/jbosstools-locus/1.5.0.Final/jbosstools-locus-1.5.0.Final-updatesite.zip

[2] https://issues.jboss.org/browse/LOCUS-46

The master branch has been prepared for future development and is now
1.6.0-SNAPHSOT.

Thanks to Mickael Istria for getting this release out, and to Paul
Leacu for contributing PRs for the new jaxb plugins!


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

From noreply at mala8.com  Tue Jan 19 21:55:21 2016
From: noreply at mala8.com (HQ-Canadian-Meds)
Date: Tue, 19 Jan 2016 22:55:21 -0400
Subject: [jbosstools-dev] We want our pharmacy to become even better so that
	we could provide more quality drugs!
Message-ID: <E1Zf07l-000q00-59@75Fr4r4>

   

		Respond to hear multiple gold chains also very. Tables, parking and
vapor. Response, greater stamina i-totally agree with. 

		Me
		ds
		0f
		or
		5M
		en

Vi
Ci
Ci
Le
Pr
 ag
al
al
vi
op
 ra
is
is
tr
ec

 S
a 
ia

of

t 

Ta

bs

 $0
$1
$2
$2
$0
 9
.6
.5
.5
.4
 9
5
0
0
5

		Me
		ds
		4f
		or
		5W
		om
		en

Ac
Cl
De
Fe
Fe
 om
om
fl
ma
ma
 pl
id
uc
le
le
 ia

an
 C
 V

ia
ia

li
gr

s 
a 

 $1
$0
$1
$1
$0
 .7
.4
.2
.1
.7
 5
5
5
1
2

 10
Vi
Sp
On 0%
sa
ec
ly  A
,M
ia
 r ut
as
l 
el he
te
in
ia nt
rc
te
bl ic
ar
rn
e   M
d,
et
su ed
Ec
 p
pp s 
he
ri
li  
ck
ce
er  

s 
s   

   2
 F
 A
 N 4/
as
no
o  7 
t 
ny
pr cu
wo
mo
es st
rl
us
cr om
dw
 d
ip er
id
el
ti  s
e 
iv
on up
sh
er
 r po
ip
y 
eq rt
pi

ui  
ng

re  

d 

		>> Enter Here 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160119/c9c00c24/attachment-0001.html 

From nboldt at redhat.com  Wed Jan 20 10:25:39 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 20 Jan 2016 10:25:39 -0500
Subject: [jbosstools-dev] Proposed changes to target platform
 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer,
 YAML Editor
Message-ID: <CA+QcL11b+cp+JtOohwk_b-j9d+KTDC-T1Fpy7oJvc_8ADHw4BQ@mail.gmail.com>

*Note that the PR is incomplete (found newer Mars and WTP bits than
what was mirrored yesterday) but I'm sending this out in advance so
people are aware of the forthcoming changes.*

--

-Here is a proposal for a change to the JBoss Tools and Red Hat JBoss
Developer Studio 4.52.0.Beta2-SNAPSHOT target platforms (for JBT
4.3.1.Beta2 / JBDS 9.1.0.Beta2).

* https://github.com/jbosstools/jbosstools-target-platforms/pull/188
* https://github.com/jbosstools/jbosstools-discovery/pull/325

It consists of the following changes:

* https://issues.jboss.org/browse/JBIDE-21406 (see also linked JIRAs)

: update to latest Mars.2.RC1 [newer mirror still in progress]
: update to e4.ui.importer (Easymport) 0.2.0.v20151123-1229
: update to Birt 4.5.0.v201510231925
: update to WTP M-3.7.2-20160118020043 [newer mirror still in progress]
: update to Docker 1.2.1.201601192048
: addition of Red Deer 1.0.1.Final
: addition of AERI 1.100.0.v20151228-1159
: move of YAML editor from Central to JBT/JBDS TP

p2diff reports will be attached to the above JIRA (once the mirrors
are done and the PRs are updated).

---

Please review the above PR(s), as they will be applied later today in
preparation for Beta2 code freeze tomorrow.

You can use the following to build & test the
target-platform locally against your component(s).

Build target-platform:
$ cd /path/to/jbosstools-target-platforms/jbosstools/multiple
$ git fetch origin pull/188/head && git checkout FETCH_HEAD
$ mvn clean install

Then, to test the new "multiple" target platform against your component's build:
$ cd /path/to/your/jbosstools-component
$ mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
-Dtpc.targetKind=multiple

--
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  Wed Jan 20 23:21:31 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 20 Jan 2016 23:21:31 -0500
Subject: [jbosstools-dev] Proposed changes to target platform
 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer,
 YAML Editor
In-Reply-To: <CA+QcL11b+cp+JtOohwk_b-j9d+KTDC-T1Fpy7oJvc_8ADHw4BQ@mail.gmail.com>
References: <CA+QcL11b+cp+JtOohwk_b-j9d+KTDC-T1Fpy7oJvc_8ADHw4BQ@mail.gmail.com>
Message-ID: <CA+QcL13Vu4OhPNe8gcPzLNCPRg4JqWQDoCGxfqX51jHzEaencQ@mail.gmail.com>

Sorry this took so long! Kept having problems creating the new
Mars.2.RC1 mirror as Eclipse kept updating it, causing the mirror
process to crash. :D

Anyway, it's updated now, and I've updated the PRs too, plus attached
p2diffs for JBT, JBDS, and Central to this JIRA:

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

Looks pretty obvious and straightfoward, so I've merged these PRs.

Working on PRs for the 4.50.x and 4.60.x branches now.


On Wed, Jan 20, 2016 at 10:25 AM, Nick Boldt <nboldt at redhat.com> wrote:
> *Note that the PR is incomplete (found newer Mars and WTP bits than
> what was mirrored yesterday) but I'm sending this out in advance so
> people are aware of the forthcoming changes.*
>
> --
>
> -Here is a proposal for a change to the JBoss Tools and Red Hat JBoss
> Developer Studio 4.52.0.Beta2-SNAPSHOT target platforms (for JBT
> 4.3.1.Beta2 / JBDS 9.1.0.Beta2).
>
> * https://github.com/jbosstools/jbosstools-target-platforms/pull/188
> * https://github.com/jbosstools/jbosstools-discovery/pull/325
>
> It consists of the following changes:
>
> * https://issues.jboss.org/browse/JBIDE-21406 (see also linked JIRAs)
>
> : update to latest Mars.2.RC1 [newer mirror still in progress]
> : update to e4.ui.importer (Easymport) 0.2.0.v20151123-1229
> : update to Birt 4.5.0.v201510231925
> : update to WTP M-3.7.2-20160118020043 [newer mirror still in progress]
> : update to Docker 1.2.1.201601192048
> : addition of Red Deer 1.0.1.Final
> : addition of AERI 1.100.0.v20151228-1159
> : move of YAML editor from Central to JBT/JBDS TP
>
> p2diff reports will be attached to the above JIRA (once the mirrors
> are done and the PRs are updated).
>
> ---
>
> Please review the above PR(s), as they will be applied later today in
> preparation for Beta2 code freeze tomorrow.
>
> You can use the following to build & test the
> target-platform locally against your component(s).
>
> Build target-platform:
> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple
> $ git fetch origin pull/188/head && git checkout FETCH_HEAD
> $ mvn clean install
>
> Then, to test the new "multiple" target platform against your component's build:
> $ cd /path/to/your/jbosstools-component
> $ mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
> -Dtpc.targetKind=multiple
>
> --
> 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

From nboldt at redhat.com  Thu Jan 21 01:26:00 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 21 Jan 2016 01:26:00 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze for JBT 4.3.1.Beta2 /
 JBDS 9.1.0.Beta2 is today, Thursday Jan 21!
Message-ID: <CA+QcL13dNa1Px9W0GzFDp9aN43XZoKDpbC8d-9atuF6HfNgVEw@mail.gmail.com>

Thursday Jan 21 is code freeze for 4.3.1.Beta2 / JBDS 9.1.0.Beta2. So,
it's time to branch & prepare to use the new target platforms I've
just created tonight.

PLEASE resolve/close the Task JIRAs below as soon as possible. If you
cannot complete them by the end of Thursday, make sure you let me &
Alexey know why you need more time & need to delay the build.

Task JIRA:

Aerogear          : https://issues.jboss.org/browse/JBIDE-21492
Central Discovery : https://issues.jboss.org/browse/JBIDE-21493
VPE               : https://issues.jboss.org/browse/JBIDE-21494
Integration Tests : https://issues.jboss.org/browse/JBIDE-21495
Server            : https://issues.jboss.org/browse/JBIDE-21497
Hibernate         : https://issues.jboss.org/browse/JBIDE-21498
Base              : https://issues.jboss.org/browse/JBIDE-21499
OpenShift         : https://issues.jboss.org/browse/JBIDE-21500
Playground        : https://issues.jboss.org/browse/JBIDE-21501
JavaEE            : https://issues.jboss.org/browse/JBIDE-21502
JST               : https://issues.jboss.org/browse/JBIDE-21503
Forge             : https://issues.jboss.org/browse/JBIDE-21504
Birt              : https://issues.jboss.org/browse/JBIDE-21505
BrowserSim        : https://issues.jboss.org/browse/JBIDE-21506
Webservices       : https://issues.jboss.org/browse/JBIDE-21507
Arquillian        : https://issues.jboss.org/browse/JBIDE-21508
Freemarker        : https://issues.jboss.org/browse/JBIDE-21509
Central           : https://issues.jboss.org/browse/JBIDE-21510
LiveReload        : https://issues.jboss.org/browse/JBIDE-21511

JBoss Tools       : https://issues.jboss.org/browse/JBIDE-21491
JBDS              : https://issues.jboss.org/browse/JBDS-3584

Note that until I've had a chance to branch jbosstools-build,
upversion the parent pom in the 4.3.x branch, & build it, there will
be no parent pom 4.3.1.CR1-SNAPSHOT. Watch this JIRA for news:

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



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

From nboldt at redhat.com  Thu Jan 21 01:32:18 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 21 Jan 2016 01:32:18 -0500
Subject: [jbosstools-dev] Proposed changes to target platform
 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer,
 YAML Editor
In-Reply-To: <CA+QcL13Vu4OhPNe8gcPzLNCPRg4JqWQDoCGxfqX51jHzEaencQ@mail.gmail.com>
References: <CA+QcL11b+cp+JtOohwk_b-j9d+KTDC-T1Fpy7oJvc_8ADHw4BQ@mail.gmail.com>
	<CA+QcL13Vu4OhPNe8gcPzLNCPRg4JqWQDoCGxfqX51jHzEaencQ@mail.gmail.com>
Message-ID: <CA+QcL12rWbwyy2sGc5rAZQq+j66BUZAsjZS8=9dtUvF6mD2TWA@mail.gmail.com>

PRs are merged. TPs have been rebuilt.

See details here:

https://issues.jboss.org/browse/JBIDE-21406
https://issues.jboss.org/browse/JBIDE-21386

If you'd to see like AERI or a YAML editor in JBDS 9.1.0.Beta2, please
review the PRs attached to these JIRAs:

https://issues.jboss.org/browse/JBDS-3566
https://issues.jboss.org/browse/JBIDE-21377

Cheers,

Nick

On Wed, Jan 20, 2016 at 11:21 PM, Nick Boldt <nboldt at redhat.com> wrote:
> Sorry this took so long! Kept having problems creating the new
> Mars.2.RC1 mirror as Eclipse kept updating it, causing the mirror
> process to crash. :D
>
> Anyway, it's updated now, and I've updated the PRs too, plus attached
> p2diffs for JBT, JBDS, and Central to this JIRA:
>
> https://issues.jboss.org/browse/JBIDE-21406?focusedCommentId=13151196&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13151196
>
> Looks pretty obvious and straightfoward, so I've merged these PRs.
>
> Working on PRs for the 4.50.x and 4.60.x branches now.
>
>
> On Wed, Jan 20, 2016 at 10:25 AM, Nick Boldt <nboldt at redhat.com> wrote:
>> *Note that the PR is incomplete (found newer Mars and WTP bits than
>> what was mirrored yesterday) but I'm sending this out in advance so
>> people are aware of the forthcoming changes.*
>>
>> --
>>
>> -Here is a proposal for a change to the JBoss Tools and Red Hat JBoss
>> Developer Studio 4.52.0.Beta2-SNAPSHOT target platforms (for JBT
>> 4.3.1.Beta2 / JBDS 9.1.0.Beta2).
>>
>> * https://github.com/jbosstools/jbosstools-target-platforms/pull/188
>> * https://github.com/jbosstools/jbosstools-discovery/pull/325
>>
>> It consists of the following changes:
>>
>> * https://issues.jboss.org/browse/JBIDE-21406 (see also linked JIRAs)
>>
>> : update to latest Mars.2.RC1 [newer mirror still in progress]
>> : update to e4.ui.importer (Easymport) 0.2.0.v20151123-1229
>> : update to Birt 4.5.0.v201510231925
>> : update to WTP M-3.7.2-20160118020043 [newer mirror still in progress]
>> : update to Docker 1.2.1.201601192048
>> : addition of Red Deer 1.0.1.Final
>> : addition of AERI 1.100.0.v20151228-1159
>> : move of YAML editor from Central to JBT/JBDS TP
>>
>> p2diff reports will be attached to the above JIRA (once the mirrors
>> are done and the PRs are updated).
>>
>> ---
>>
>> Please review the above PR(s), as they will be applied later today in
>> preparation for Beta2 code freeze tomorrow.
>>
>> You can use the following to build & test the
>> target-platform locally against your component(s).
>>
>> Build target-platform:
>> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple
>> $ git fetch origin pull/188/head && git checkout FETCH_HEAD
>> $ mvn clean install
>>
>> Then, to test the new "multiple" target platform against your component's build:
>> $ cd /path/to/your/jbosstools-component
>> $ mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
>> -Dtpc.targetKind=multiple
>>
>> --
>> 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



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

From ggastald at redhat.com  Thu Jan 21 05:10:35 2016
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 21 Jan 2016 08:10:35 -0200
Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze for JBT
 4.3.1.Beta2 / JBDS 9.1.0.Beta2 is today, Thursday Jan 21!
In-Reply-To: <CA+QcL13dNa1Px9W0GzFDp9aN43XZoKDpbC8d-9atuF6HfNgVEw@mail.gmail.com>
References: <CA+QcL13dNa1Px9W0GzFDp9aN43XZoKDpbC8d-9atuF6HfNgVEw@mail.gmail.com>
Message-ID: <CAMmsnJi5usrW2ejJOT5q0za6iyecJ3ooYq__gaaAC-Rmnhif7w@mail.gmail.com>

Done for Forge

On Thu, Jan 21, 2016 at 4:26 AM, Nick Boldt <nboldt at redhat.com> wrote:

> Thursday Jan 21 is code freeze for 4.3.1.Beta2 / JBDS 9.1.0.Beta2. So,
> it's time to branch & prepare to use the new target platforms I've
> just created tonight.
>
> PLEASE resolve/close the Task JIRAs below as soon as possible. If you
> cannot complete them by the end of Thursday, make sure you let me &
> Alexey know why you need more time & need to delay the build.
>
> Task JIRA:
>
> Aerogear          : https://issues.jboss.org/browse/JBIDE-21492
> Central Discovery : https://issues.jboss.org/browse/JBIDE-21493
> VPE               : https://issues.jboss.org/browse/JBIDE-21494
> Integration Tests : https://issues.jboss.org/browse/JBIDE-21495
> Server            : https://issues.jboss.org/browse/JBIDE-21497
> Hibernate         : https://issues.jboss.org/browse/JBIDE-21498
> Base              : https://issues.jboss.org/browse/JBIDE-21499
> OpenShift         : https://issues.jboss.org/browse/JBIDE-21500
> Playground        : https://issues.jboss.org/browse/JBIDE-21501
> JavaEE            : https://issues.jboss.org/browse/JBIDE-21502
> JST               : https://issues.jboss.org/browse/JBIDE-21503
> Forge             : https://issues.jboss.org/browse/JBIDE-21504
> Birt              : https://issues.jboss.org/browse/JBIDE-21505
> BrowserSim        : https://issues.jboss.org/browse/JBIDE-21506
> Webservices       : https://issues.jboss.org/browse/JBIDE-21507
> Arquillian        : https://issues.jboss.org/browse/JBIDE-21508
> Freemarker        : https://issues.jboss.org/browse/JBIDE-21509
> Central           : https://issues.jboss.org/browse/JBIDE-21510
> LiveReload        : https://issues.jboss.org/browse/JBIDE-21511
>
> JBoss Tools       : https://issues.jboss.org/browse/JBIDE-21491
> JBDS              : https://issues.jboss.org/browse/JBDS-3584
>
> Note that until I've had a chance to branch jbosstools-build,
> upversion the parent pom in the 4.3.x branch, & build it, there will
> be no parent pom 4.3.1.CR1-SNAPSHOT. Watch this JIRA for news:
>
> https://issues.jboss.org/browse/JBIDE-21496
>
>
>
> --
> 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
>



-- 
*George Gastaldi*

https://about.me/gastaldi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160121/9e5f76d9/attachment-0001.html 

From nboldt at redhat.com  Thu Jan 21 13:17:04 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 21 Jan 2016 13:17:04 -0500
Subject: [jbosstools-dev] Proposed changes to target platform
 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer,
 YAML Editor
In-Reply-To: <CA+QcL12rWbwyy2sGc5rAZQq+j66BUZAsjZS8=9dtUvF6mD2TWA@mail.gmail.com>
References: <CA+QcL11b+cp+JtOohwk_b-j9d+KTDC-T1Fpy7oJvc_8ADHw4BQ@mail.gmail.com>
	<CA+QcL13Vu4OhPNe8gcPzLNCPRg4JqWQDoCGxfqX51jHzEaencQ@mail.gmail.com>
	<CA+QcL12rWbwyy2sGc5rAZQq+j66BUZAsjZS8=9dtUvF6mD2TWA@mail.gmail.com>
Message-ID: <CA+QcL139hukD4Z0TDD1r8-8G5BFjKrLnTwrKBJ4DQb+ctymcoQ@mail.gmail.com>

Turns out the Mars.2 update site was updated again (a day after it was
supposed to be done) so we have new egit 4.1 to add to the TP.

Details:

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

New PR will be posted to the JIRA and the 4.52.0.Beta2 TP will be
rebuilt thereafter.

On Thu, Jan 21, 2016 at 1:32 AM, Nick Boldt <nboldt at redhat.com> wrote:
> PRs are merged. TPs have been rebuilt.
>
> See details here:
>
> https://issues.jboss.org/browse/JBIDE-21406
> https://issues.jboss.org/browse/JBIDE-21386
>
> If you'd to see like AERI or a YAML editor in JBDS 9.1.0.Beta2, please
> review the PRs attached to these JIRAs:
>
> https://issues.jboss.org/browse/JBDS-3566
> https://issues.jboss.org/browse/JBIDE-21377
>
> Cheers,
>
> Nick
>
> On Wed, Jan 20, 2016 at 11:21 PM, Nick Boldt <nboldt at redhat.com> wrote:
>> Sorry this took so long! Kept having problems creating the new
>> Mars.2.RC1 mirror as Eclipse kept updating it, causing the mirror
>> process to crash. :D
>>
>> Anyway, it's updated now, and I've updated the PRs too, plus attached
>> p2diffs for JBT, JBDS, and Central to this JIRA:
>>
>> https://issues.jboss.org/browse/JBIDE-21406?focusedCommentId=13151196&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13151196
>>
>> Looks pretty obvious and straightfoward, so I've merged these PRs.
>>
>> Working on PRs for the 4.50.x and 4.60.x branches now.
>>
>>
>> On Wed, Jan 20, 2016 at 10:25 AM, Nick Boldt <nboldt at redhat.com> wrote:
>>> *Note that the PR is incomplete (found newer Mars and WTP bits than
>>> what was mirrored yesterday) but I'm sending this out in advance so
>>> people are aware of the forthcoming changes.*
>>>
>>> --
>>>
>>> -Here is a proposal for a change to the JBoss Tools and Red Hat JBoss
>>> Developer Studio 4.52.0.Beta2-SNAPSHOT target platforms (for JBT
>>> 4.3.1.Beta2 / JBDS 9.1.0.Beta2).
>>>
>>> * https://github.com/jbosstools/jbosstools-target-platforms/pull/188
>>> * https://github.com/jbosstools/jbosstools-discovery/pull/325
>>>
>>> It consists of the following changes:
>>>
>>> * https://issues.jboss.org/browse/JBIDE-21406 (see also linked JIRAs)
>>>
>>> : update to latest Mars.2.RC1 [newer mirror still in progress]
>>> : update to e4.ui.importer (Easymport) 0.2.0.v20151123-1229
>>> : update to Birt 4.5.0.v201510231925
>>> : update to WTP M-3.7.2-20160118020043 [newer mirror still in progress]
>>> : update to Docker 1.2.1.201601192048
>>> : addition of Red Deer 1.0.1.Final
>>> : addition of AERI 1.100.0.v20151228-1159
>>> : move of YAML editor from Central to JBT/JBDS TP
>>>
>>> p2diff reports will be attached to the above JIRA (once the mirrors
>>> are done and the PRs are updated).
>>>
>>> ---
>>>
>>> Please review the above PR(s), as they will be applied later today in
>>> preparation for Beta2 code freeze tomorrow.
>>>
>>> You can use the following to build & test the
>>> target-platform locally against your component(s).
>>>
>>> Build target-platform:
>>> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple
>>> $ git fetch origin pull/188/head && git checkout FETCH_HEAD
>>> $ mvn clean install
>>>
>>> Then, to test the new "multiple" target platform against your component's build:
>>> $ cd /path/to/your/jbosstools-component
>>> $ mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
>>> -Dtpc.targetKind=multiple
>>>
>>> --
>>> 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
>
>
>
> --
> 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 manderse at redhat.com  Fri Jan 22 02:59:32 2016
From: manderse at redhat.com (manderse at redhat.com)
Date: Fri, 22 Jan 2016 02:59:32 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201601220759.u0M7xWel024885@int-mx14.intmail.prod.int.phx2.redhat.com>


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

 
* No component for JBIDE-21558

https://issues.jboss.org/browse/JBIDE-21558
Summary: Confusing (non-blocking) situation for users when installing kitchensink-angular example from JBoss Central

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

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



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

From manderse at redhat.com  Fri Jan 22 05:12:33 2016
From: manderse at redhat.com (manderse at redhat.com)
Date: Fri, 22 Jan 2016 05:12:33 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201601221012.u0MACXGx023817@int-mx14.intmail.prod.int.phx2.redhat.com>


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

 
* No component for JBIDE-21558

https://issues.jboss.org/browse/JBIDE-21558
Summary: Confusing (non-blocking) situation for users when installing kitchensink-angular example from JBoss Central

Assignee: None set.
Component: None set - please fix.
Problem: No component - please ensure this issue has a proper component set.
Last Update: 9:59:21.600990

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



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

From noreply at liscastylist.com  Fri Jan 22 11:38:51 2016
From: noreply at liscastylist.com (HQ-Canadian-Meds)
Date: Fri, 22 Jan 2016 14:38:51 -0200
Subject: [jbosstools-dev] If you tired of buying expensive useless
	medications try visiting our online pharmacy now!
Message-ID: <628BA361264DAB87B20BE821B69E1F5DE34F@liscastylist.com>

   

		Intensely interesting, but covert and legal rights leaders at
software. Final rule teacher architectural, and nurturing, comfort,
security. 

		Me
		ds
		9f
		or
		4M
		en

Vi
Ci
Ci
Le
Pr
 ag
al
al
vi
op
 ra
is
is
tr
ec

 S
a 
ia

of

t 

Ta

bs

 $0
$1
$2
$2
$0
 .9
.6
.5
.5
.4
 9
5
0
0
5

		Me
		ds
		5f
		or
		0W
		om
		en

Ac
Cl
De
Fe
Fe
 om
om
fl
ma
ma
 pl
id
uc
le
le
 ia

an
 C
 V

ia
ia

li
gr

s 
a 

 $1
$0
$1
$1
$0
 .7
.4
.2
.1
.7
 5
5
5
1
2

 Vi
Sp
24
10 sa
ec
/7
0% ,M
ia
 c
 A as
l 
us
ut te
in
to
he rc
te
me
nt ar
rn
r 
ic d,
et
su
 M Ec
 p
pp
ed he
ri
or
s  ck
ce
t 

s 

   A
 O
 N
 F no
nl
o 
as ny
y 
pr
t  mo
re
es
wo us
li
cr
rl  d
ab
ip
dw el
le
ti
id iv
 s
on
e  er
up
 r
sh y 
pl
eq
ip  
ie
ui
pi  
rs
re
ng  

d

		>> Enter Here 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160122/fb0313e5/attachment.html 

From nboldt at redhat.com  Fri Jan 22 15:27:22 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 22 Jan 2016 15:27:22 -0500
Subject: [jbosstools-dev] JBoss Tools Core 4.3.1.Beta2 bits available for QE
	testing
Message-ID: <CA+QcL1378pf2nk3P7+kNNSTTvz0XJ-X6xTrJJEykxhG-e4te8Q@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.1.Beta2/
* http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.1.Beta2/

Target platforms:
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.2.Beta2-SNAPSHOT
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.52.0.Beta2-SNAPSHOT

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

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


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

From nboldt at redhat.com  Mon Jan 25 13:59:38 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 25 Jan 2016 13:59:38 -0500
Subject: [jbosstools-dev] JBoss Tools 4.3.1.Beta2: Will there be a respin-a?
 (Short answer: maybe Wed/Thu this week)
Message-ID: <CA+QcL125jii3ce_qtTAGF6V_fy_gO0pi7gqnX3OF-uAM8AfRgQ@mail.gmail.com>

After some discussion w/ Len this afternoon, we've decided that the
go/no-go decision to do a respin will happen on Wed Jan 27, *no later
than 12pm Toronto time / 6pm Brno time*

Builds are enabled and currently spinning against the 4.3.1.Beta2x
branch (not the 4.3.x / CR1 branch!), so if we decide to do a respin,
we can quickly get stuff built Wed afternoon/evening.

Devs will have from noon on Wed (if a respin is happening) until that
evening to get stuff pushed to the 4.3.1.Beta2x (and 4.3.x branch
too!).

QE can then start on the fresh bits as of *Thurs Jan 28 Brno time*,
unless we find a big blocker which can't be fixed Wed night.

If you have things you think you want to include, please get them PR
reviewed in advance so that it'll be easier to just commit your
changes.

If we don't do a respin, those changes will simply go into the 4.3.x
branch for CR1, so you won't be wasting your (or your PR reviewers')
time.

--

Any questions, please ask here or find me/Len on hipchat.

--

PS: Once we're done with Beta2 respins, I can switch the jobs to start
building the CR1 bits from the 4.3.x branch. If I forget, don't
hesitate to open a JIRA to remind me (eg., JBIDE-21407).

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

From apupier at redhat.com  Wed Jan 27 04:28:57 2016
From: apupier at redhat.com (Aurelien Pupier)
Date: Wed, 27 Jan 2016 10:28:57 +0100
Subject: [jbosstools-dev] Eclipse plugins testing structure
Message-ID: <56A88DD9.9030802@redhat.com>

Hi,

I'm currently trying to improve test structure for Jboss Fuse Tooling 
project (https://github.com/fusesource/fuseide).

On Max recommendation, I take a look at jbosstools-devdoc 
https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to_add_a_test_plugin_or_feature.adoc

When i take a look to 
https://github.com/jbosstools/jbosstools-server/blob/master/as/tests/org.jboss.tools.as.test.core/pom.xml 
. This project is in tests folder but it launches tycho-surefire-plugin. 
As far as I understand Tycho, it means that it is launching an OSGi 
platform. From my point of view, it means that these tests are already 
integration tests and the only difference between tests and itests 
currently is more fast vs slow tests.

What I wanted to achieve is to have really fast unit test, so I created 
a fragment and so use maven-surefire-plugin. You can see the fragment 
https://github.com/fusesource/fuseide/tree/master/editor/tests/org.fusesource.ide.camel.editor.tests 
and the parent pom configuration:
             <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
                 <version>2.19.1</version>
                 <executions>
                     <execution>
                         <id>test</id>
                         <phase>test</phase>
                         <configuration>
                             <systemProperties>
<osgi.nls.warnings>ignore</osgi.nls.warnings>
                             </systemProperties>
                             <includes>
<include>**/*Test.java</include>
                             </includes>
                         </configuration>
                         <goals>
                             <goal>test</goal>
                         </goals>
                     </execution>
                 </executions>
             </plugin>

             <plugin>
                 <groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-surefire-plugin</artifactId>
                 <version>${tychoVersion}</version>
                 <configuration>
                     <useUIThread>true</useUIThread>
                     <useUIHarness>true</useUIHarness>
                     <includes>
                         <include>**/*IT.class</include>
                     </includes>
                     <argLine>${tycho.testArgLine} 
-XX:+HeapDumpOnOutOfMemoryError</argLine>
                 </configuration>
             </plugin>

Did I misunderstood something?
Are there counterpoints to use fragments and maven-surefire-plugin?
Are there other examples which are matching more closely to my usecase 
in jboss tools codebase?

Thanks by advance for your help

-- 
Aurelien Pupier
Senior Software Engineer in JBoss Fuse Tooling Team
@apupier


From mistria at redhat.com  Wed Jan 27 04:43:21 2016
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 27 Jan 2016 10:43:21 +0100
Subject: [jbosstools-dev] Eclipse plugins testing structure
In-Reply-To: <56A88DD9.9030802@redhat.com>
References: <56A88DD9.9030802@redhat.com>
Message-ID: <56A89139.2040308@redhat.com>

On 01/27/2016 10:28 AM, Aurelien Pupier wrote:
> Hi,
Hi Aurelien!
> Did I misunderstood something?
> Are there counterpoints to use fragments and maven-surefire-plugin?
> Are there other examples which are matching more closely to my usecase
> in jboss tools codebase?
About using fragments, the only drawback I'm aware of is that one cannot 
add a dependency to a fragment from their plugin. So it's not possible 
for other tests to reuse some logic that is inside a fragment. In the 
spirit of "treating tests as 1st class citizen", I believe it's 
generally better to allow composition of test bundles and to make them 
regular bundles.

About maven-surefire (plain Java) vs tycho-surefire (OSGi/Eclipse), so 
far, we do not test the code of JBoss Tools outside of the "Eclipse" 
context. We can debate about the meaning of "unit tests", but what you 
see can be seen as "unit tests running in integration context". Our 
experience with some other parts of JBoss Tools have been that the 
difference of behavior between inside or outside of Eclipse can be 
important. So our policy has been so far to test everything with 
tycho-surefire-plugin to make sure what we're testing isn't too far from 
what will actually happen in production.
The QE people could tell you their opinion on what's more important 
between fast tests, and longer tests that are closer from production.
I guess it all depends, as always: we could imagine the unit test 
running in plain Java to verify only their logic, but it shouldn't 
become a replacement to some integration test to verify that the logic 
also works in the right context.
I would say that as long as Eclipse is the *only* deployment context for 
a piece of code, then starting unit tests inside Eclipse is fine. Also, 
for fast unit tests, then they are neglictable compared to starting up 
the OSGi Platform. So if we want to start an OSGi platform anyway for 
integration tests, it seems simpler to run those tests inside that Platform.

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

From apupier at redhat.com  Wed Jan 27 05:16:19 2016
From: apupier at redhat.com (Aurelien Pupier)
Date: Wed, 27 Jan 2016 11:16:19 +0100
Subject: [jbosstools-dev] Eclipse plugins testing structure
In-Reply-To: <56A89139.2040308@redhat.com>
References: <56A88DD9.9030802@redhat.com> <56A89139.2040308@redhat.com>
Message-ID: <56A898F3.9070408@redhat.com>

Hello Mickael,

Le 1/27/2016 10:43 AM, Mickael Istria a ?crit :
> On 01/27/2016 10:28 AM, Aurelien Pupier wrote:
>> Hi,
> Hi Aurelien!
>> Did I misunderstood something?
>> Are there counterpoints to use fragments and maven-surefire-plugin?
>> Are there other examples which are matching more closely to my usecase
>> in jboss tools codebase?
> About using fragments, the only drawback I'm aware of is that one 
> cannot add a dependency to a fragment from their plugin. So it's not 
> possible for other tests to reuse some logic that is inside a 
> fragment. In the spirit of "treating tests as 1st class citizen", I 
> believe it's generally better to allow composition of test bundles and 
> to make them regular bundles.

If reusable, the logic can be moved to a dedicated utility test plugin.

>
> About maven-surefire (plain Java) vs tycho-surefire (OSGi/Eclipse), so 
> far, we do not test the code of JBoss Tools outside of the "Eclipse" 
> context. We can debate about the meaning of "unit tests", but what you 
> see can be seen as "unit tests running in integration context". Our 
> experience with some other parts of JBoss Tools have been that the 
> difference of behavior between inside or outside of Eclipse can be 
> important. So our policy has been so far to test everything with 
> tycho-surefire-plugin to make sure what we're testing isn't too far 
> from what will actually happen in production.

important difference of behavior which can be important is a good 
argument. On the other hand, some integration tests should be able to 
detect that.

> The QE people could tell you their opinion on what's more important 
> between fast tests, and longer tests that are closer from production.
> I guess it all depends, as always: we could imagine the unit test 
> running in plain Java to verify only their logic, but it shouldn't 
> become a replacement to some integration test to verify that the logic 
> also works in the right context.
Not planned to have them as a replacement. I already created the 
structure to write also higher integration tests.

> I would say that as long as Eclipse is the *only* deployment context 
> for a piece of code, then starting unit tests inside Eclipse is fine. 
> Also, for fast unit tests, then they are neglictable compared to 
> starting up the OSGi Platform. So if we want to start an OSGi platform 
> anyway for integration tests, it seems simpler to run those tests 
> inside that Platform.
>
When running locally, I may want to run only unit tests first. Without 
launching the OSGi platform it will be faster. It will also allow to use 
some tools such as Infinitest to have continuous feedback while developing.


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

-- 
Aurelien Pupier
Senior Software Engineer in JBoss Fuse Tooling Team
@apupier

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

From mistria at redhat.com  Wed Jan 27 05:53:49 2016
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 27 Jan 2016 11:53:49 +0100
Subject: [jbosstools-dev] Eclipse plugins testing structure
In-Reply-To: <56A898F3.9070408@redhat.com>
References: <56A88DD9.9030802@redhat.com> <56A89139.2040308@redhat.com>
	<56A898F3.9070408@redhat.com>
Message-ID: <56A8A1BD.6050908@redhat.com>

On 01/27/2016 11:16 AM, Aurelien Pupier wrote:
> About using fragments, the only drawback I'm aware of is that one 
> cannot add a dependency to a fragment from their plugin. So it's not 
> possible for other tests to reuse some logic that is inside a 
> fragment. In the spirit of "treating tests as 1st class citizen", I 
> believe it's generally better to allow composition of test bundles and 
> to make them regular bundles.
>
> If reusable, the logic can be moved to a dedicated utility test plugin.
Yes, but it requires an effort in moving the code to the right plugin or 
turning fragment into a bundle everytime one identifies something to 
reuse; whereas using bundles only doesn't require any effort from the 
"producer" side.

> On the other hand, some integration tests should be able to detect that.
That would require writing some additional integration tests, whereas 
the current approach to run "unit" tests inside a workbench provide that 
verification without additional thing to write.

>> The QE people could tell you their opinion on what's more important 
>> between fast tests, and longer tests that are closer from production.
>> I guess it all depends, as always: we could imagine the unit test 
>> running in plain Java to verify only their logic, but it shouldn't 
>> become a replacement to some integration test to verify that the 
>> logic also works in the right context.
> Not planned to have them as a replacement. I already created the 
> structure to write also higher integration tests.
If, during automated tests/build, you run both unit tests and then start 
a workbench to run integration tests, then you pay the price of the 
workbench startup anyway. So why not running those unit tests in the 
workbench?

> When running locally, I may want to run only unit tests first.  
> Without launching the OSGi platform it will be faster. It will also 
> allow to use some tools such as Infinitest to have continuous feedback 
> while developing.
I don't know much of Infinitest, but I believe it doesn't rely on how 
Maven runs tests. Eclipse already provide the ability to run a test 
class in a bundle in plain Java without starting the workbench; it's 
"Run As > JUnit Test" instead of "Run As > JUnit Plugin Test". I guess 
Infinitest can rely on that, can't it?

Just to be clear, I'm not saying it's wrong to change that; I'm more 
wonderint how much profitable is it, what changing test structure would 
provide better than the current one does. The Infinitest story seems the 
only one "worth it" IMO, and it doesn't seem to be correlated to 
tycho-surefire vs maven-surefire.
-- 
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/20160127/0752391c/attachment-0001.html 

From manderse at redhat.com  Wed Jan 27 07:26:58 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 27 Jan 2016 13:26:58 +0100
Subject: [jbosstools-dev] Eclipse plugins testing structure
In-Reply-To: <56A88DD9.9030802@redhat.com>
References: <56A88DD9.9030802@redhat.com>
Message-ID: <668BD024-6140-4CAC-8CB5-C28F3DAEB8A5@redhat.com>

On 27 Jan 2016, at 10:28, Aurelien Pupier wrote:

> Hi,
>
> I'm currently trying to improve test structure for Jboss Fuse Tooling
> project (https://github.com/fusesource/fuseide).
>
> On Max recommendation, I take a look at jbosstools-devdoc
> https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to_add_a_test_plugin_or_feature.adoc
>
> When i take a look to
> https://github.com/jbosstools/jbosstools-server/blob/master/as/tests/org.jboss.tools.as.test.core/pom.xml
> . This project is in tests folder but it launches 
> tycho-surefire-plugin.
> As far as I understand Tycho, it means that it is launching an OSGi
> platform. From my point of view, it means that these tests are already
> integration tests and the only difference between tests and itests
> currently is more fast vs slow tests.

I disagree launching in osgi means it is an integration test.

You can run fast tests with tyco-surefire-plugin or rater from eclipse - 
just don't launch with the workbench.

If you run with the plain maven surefire plugin you will have to handle 
dependency management on your own afaics -
i.e. you cannot depend on anything in the osgi or in p2 repos for that 
matter.

Meaning any work done for Target platform will have to be done twice - 
one for existing target platform, another
for your pure maven setup.

> What I wanted to achieve is to have really fast unit test, so I 
> created
> a fragment and so use maven-surefire-plugin. You can see the fragment
> https://github.com/fusesource/fuseide/tree/master/editor/tests/org.fusesource.ide.camel.editor.tests

so this will have to not rely on *any* eclipse osgi dependent api's.

That is doable, but super limited. As long as you are aware of that and 
the need to maintain two "target platforms"
that is fine.

Need to find a different name than test or itest then though ;)

Does it really make that big difference wether you use tyco-surefire vs 
plain maven-surefire speed wise ? (remember to not start the workbench 
;)

/max
http://about.me/maxandersen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160127/3fffaab5/attachment.html 

From manderse at redhat.com  Wed Jan 27 07:29:32 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 27 Jan 2016 13:29:32 +0100
Subject: [jbosstools-dev] Eclipse plugins testing structure
In-Reply-To: <56A89139.2040308@redhat.com>
References: <56A88DD9.9030802@redhat.com> <56A89139.2040308@redhat.com>
Message-ID: <96C4EDA4-4A86-4922-B587-5755354D650D@redhat.com>

to be clear - if you have code that is completely independent of osgi 
and has no dependencies you'll have to maintain twice then
do by all means run those tests outside tycho.

We do that already today - they just don't have any tycho at all in 
them. i.e. hibernatetools-core are plain java tests which we then 
include in the plugin.

Is that the situation you are having ?

/max

> On 01/27/2016 10:28 AM, Aurelien Pupier wrote:
>> Hi,
> Hi Aurelien!
>> Did I misunderstood something?
>> Are there counterpoints to use fragments and maven-surefire-plugin?
>> Are there other examples which are matching more closely to my 
>> usecase
>> in jboss tools codebase?
> About using fragments, the only drawback I'm aware of is that one 
> cannot add a dependency to a fragment from their plugin. So it's not 
> possible for other tests to reuse some logic that is inside a 
> fragment. In the spirit of "treating tests as 1st class citizen", I 
> believe it's generally better to allow composition of test bundles and 
> to make them regular bundles.
>
> About maven-surefire (plain Java) vs tycho-surefire (OSGi/Eclipse), so 
> far, we do not test the code of JBoss Tools outside of the "Eclipse" 
> context. We can debate about the meaning of "unit tests", but what you 
> see can be seen as "unit tests running in integration context". Our 
> experience with some other parts of JBoss Tools have been that the 
> difference of behavior between inside or outside of Eclipse can be 
> important. So our policy has been so far to test everything with 
> tycho-surefire-plugin to make sure what we're testing isn't too far 
> from what will actually happen in production.
> The QE people could tell you their opinion on what's more important 
> between fast tests, and longer tests that are closer from production.
> I guess it all depends, as always: we could imagine the unit test 
> running in plain Java to verify only their logic, but it shouldn't 
> become a replacement to some integration test to verify that the logic 
> also works in the right context.
> I would say that as long as Eclipse is the *only* deployment context 
> for a piece of code, then starting unit tests inside Eclipse is fine. 
> Also, for fast unit tests, then they are neglictable compared to 
> starting up the OSGi Platform. So if we want to start an OSGi platform 
> anyway for integration tests, it seems simpler to run those tests 
> inside that Platform.
>
> HTH
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets 
> <http://twitter.com/mickaelistria>
> _______________________________________________
> 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/20160127/0de1d31c/attachment.html 

From nboldt at redhat.com  Wed Jan 27 10:21:33 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 27 Jan 2016 10:21:33 -0500
Subject: [jbosstools-dev] FYI: Schedule updated for JBoss Tools 4.3.1
	milestones
Message-ID: <CA+QcL11tEH_P1w2ek5qEpECqYBGhSJMc5-aSd=QySPp6bXdupw@mail.gmail.com>

CR1 and CR2/Final have been adjusted to be available later in March.

Details:

https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page


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

From nboldt at redhat.com  Wed Jan 27 11:17:13 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 27 Jan 2016 11:17:13 -0500
Subject: [jbosstools-dev] Proposed changes to target platform
 4.52.0.Beta2-SNAPSHOT: Mars.2.RC1 + AERI, Docker, Easymport, Red Deer,
 YAML Editor
In-Reply-To: <CA+QcL139hukD4Z0TDD1r8-8G5BFjKrLnTwrKBJ4DQb+ctymcoQ@mail.gmail.com>
References: <CA+QcL11b+cp+JtOohwk_b-j9d+KTDC-T1Fpy7oJvc_8ADHw4BQ@mail.gmail.com>
	<CA+QcL13Vu4OhPNe8gcPzLNCPRg4JqWQDoCGxfqX51jHzEaencQ@mail.gmail.com>
	<CA+QcL12rWbwyy2sGc5rAZQq+j66BUZAsjZS8=9dtUvF6mD2TWA@mail.gmail.com>
	<CA+QcL139hukD4Z0TDD1r8-8G5BFjKrLnTwrKBJ4DQb+ctymcoQ@mail.gmail.com>
Message-ID: <CA+QcL11z52QcRv6JKYUkBXAjqf-uru7eEnoWi81UsY567BLuCw@mail.gmail.com>

One more change is required, since it's now blocking Integration Stack builds.

https://github.com/jbosstools/jbosstools-target-platforms/pull/192/files

This simply removes the old version of org.eclipse.osgi,
3.10.101.v20150820-1432, in favour of the newer one,
3.10.102.v20151214-1617, so that there is only ONE version, not two,
in the TP.

I will apply this later today as part of respin-a unless there are objections.



On Thu, Jan 21, 2016 at 1:17 PM, Nick Boldt <nboldt at redhat.com> wrote:
> Turns out the Mars.2 update site was updated again (a day after it was
> supposed to be done) so we have new egit 4.1 to add to the TP.
>
> Details:
>
> https://issues.jboss.org/browse/JBIDE-21406?focusedCommentId=13152088&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13152088
>
> New PR will be posted to the JIRA and the 4.52.0.Beta2 TP will be
> rebuilt thereafter.
>
> On Thu, Jan 21, 2016 at 1:32 AM, Nick Boldt <nboldt at redhat.com> wrote:
>> PRs are merged. TPs have been rebuilt.
>>
>> See details here:
>>
>> https://issues.jboss.org/browse/JBIDE-21406
>> https://issues.jboss.org/browse/JBIDE-21386
>>
>> If you'd to see like AERI or a YAML editor in JBDS 9.1.0.Beta2, please
>> review the PRs attached to these JIRAs:
>>
>> https://issues.jboss.org/browse/JBDS-3566
>> https://issues.jboss.org/browse/JBIDE-21377
>>
>> Cheers,
>>
>> Nick
>>
>> On Wed, Jan 20, 2016 at 11:21 PM, Nick Boldt <nboldt at redhat.com> wrote:
>>> Sorry this took so long! Kept having problems creating the new
>>> Mars.2.RC1 mirror as Eclipse kept updating it, causing the mirror
>>> process to crash. :D
>>>
>>> Anyway, it's updated now, and I've updated the PRs too, plus attached
>>> p2diffs for JBT, JBDS, and Central to this JIRA:
>>>
>>> https://issues.jboss.org/browse/JBIDE-21406?focusedCommentId=13151196&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13151196
>>>
>>> Looks pretty obvious and straightfoward, so I've merged these PRs.
>>>
>>> Working on PRs for the 4.50.x and 4.60.x branches now.
>>>
>>>
>>> On Wed, Jan 20, 2016 at 10:25 AM, Nick Boldt <nboldt at redhat.com> wrote:
>>>> *Note that the PR is incomplete (found newer Mars and WTP bits than
>>>> what was mirrored yesterday) but I'm sending this out in advance so
>>>> people are aware of the forthcoming changes.*
>>>>
>>>> --
>>>>
>>>> -Here is a proposal for a change to the JBoss Tools and Red Hat JBoss
>>>> Developer Studio 4.52.0.Beta2-SNAPSHOT target platforms (for JBT
>>>> 4.3.1.Beta2 / JBDS 9.1.0.Beta2).
>>>>
>>>> * https://github.com/jbosstools/jbosstools-target-platforms/pull/188
>>>> * https://github.com/jbosstools/jbosstools-discovery/pull/325
>>>>
>>>> It consists of the following changes:
>>>>
>>>> * https://issues.jboss.org/browse/JBIDE-21406 (see also linked JIRAs)
>>>>
>>>> : update to latest Mars.2.RC1 [newer mirror still in progress]
>>>> : update to e4.ui.importer (Easymport) 0.2.0.v20151123-1229
>>>> : update to Birt 4.5.0.v201510231925
>>>> : update to WTP M-3.7.2-20160118020043 [newer mirror still in progress]
>>>> : update to Docker 1.2.1.201601192048
>>>> : addition of Red Deer 1.0.1.Final
>>>> : addition of AERI 1.100.0.v20151228-1159
>>>> : move of YAML editor from Central to JBT/JBDS TP
>>>>
>>>> p2diff reports will be attached to the above JIRA (once the mirrors
>>>> are done and the PRs are updated).
>>>>
>>>> ---
>>>>
>>>> Please review the above PR(s), as they will be applied later today in
>>>> preparation for Beta2 code freeze tomorrow.
>>>>
>>>> You can use the following to build & test the
>>>> target-platform locally against your component(s).
>>>>
>>>> Build target-platform:
>>>> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple
>>>> $ git fetch origin pull/188/head && git checkout FETCH_HEAD
>>>> $ mvn clean install
>>>>
>>>> Then, to test the new "multiple" target platform against your component's build:
>>>> $ cd /path/to/your/jbosstools-component
>>>> $ mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
>>>> -Dtpc.targetKind=multiple
>>>>
>>>> --
>>>> 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
>>
>>
>>
>> --
>> 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

From nboldt at redhat.com  Wed Jan 27 14:33:20 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 27 Jan 2016 14:33:20 -0500
Subject: [jbosstools-dev] Fwd: [eclipse.org-planning-council] Neon+1 Naming
	Results
In-Reply-To: <CAJg1wMTJqXnjd7mnQg2sWmASPePpsvxwerS_5v9MXXeAZT6BbA@mail.gmail.com>
References: <CAJg1wMR3d8J3PCAFQs7bnR6m+cgpnLjtRZoHDU9CaOHGW9APDQ@mail.gmail.com>
	<CAJg1wMTJqXnjd7mnQg2sWmASPePpsvxwerS_5v9MXXeAZT6BbA@mail.gmail.com>
Message-ID: <CA+QcL10o4Vv2oK1byEeQ26rFOcFa+ek59F+aBk+GjtQNEUbgPg@mail.gmail.com>

ICYMI, Eclipse simrel release for 2017 will be called Oxygen.

Not nearly as noble a name as this year's release, but still a breath
of fresh air after all the planet & scientist names used in the past.


---------- Forwarded message ----------
From: Chris Aniszczyk <caniszczyk at gmail.com>
Date: Wed, Jan 27, 2016 at 12:30 PM
Subject: Re: [eclipse.org-planning-council] Neon+1 Naming Results
To: "eclipse.org-planning-council" <eclipse.org-planning-council at eclipse.org>


Just to follow up on this, "Eclipse Oxygen" it is for Neon+1:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485861#c3

On Thu, Jan 14, 2016 at 10:35 AM, Chris Aniszczyk <caniszczyk at gmail.com> wrote:
>
> The results are in:
> http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_dd4ff581da35bddc
>
> 1. Oxygen  (Condorcet winner: wins contests with all other choices)
> 2. Odyssey  loses to Oxygen by 121?112
> 3. Osiris  loses to Oxygen by 141?94, loses to Odyssey by 131?97
> 4. Opal  loses to Oxygen by 136?95, loses to Osiris by 112?109
> 5. Oberon  loses to Oxygen by 143?98, loses to Opal by 115?110
> 6. Orpheus  loses to Oxygen by 142?90, loses to Oberon by 121?99
> 7. Ozone  loses to Oxygen by 152?61, loses to Orpheus by 111?103
> 8. Ohm  loses to Oxygen by 152?69, loses to Ozone by 103?99
> 9. Oceana  loses to Oxygen by 161?54, loses to Ohm by 103?94
> 10. Oort  loses to Oxygen by 158?63, loses to Oceana by 116?78
>
> I've started the process to legally clear the name via bug 485861
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=485861
>
> --
> Cheers,
>
> Chris Aniszczyk
> http://aniszczyk.org
> +1 512 961 6719




--
Cheers,

Chris Aniszczyk
http://aniszczyk.org
+1 512 961 6719

_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council at eclipse.org
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

IMPORTANT: Membership in this list is generated by processes internal
to the Eclipse Foundation.  To be permanently removed from this list,
you must contact emo at eclipse.org to request removal.


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


From bbrodt at redhat.com  Wed Jan 27 15:14:19 2016
From: bbrodt at redhat.com (Bob Brodt)
Date: Wed, 27 Jan 2016 13:14:19 -0700
Subject: [jbosstools-dev] Fwd: [eclipse.org-planning-council] Neon+1
 Naming Results
In-Reply-To: <CA+QcL10o4Vv2oK1byEeQ26rFOcFa+ek59F+aBk+GjtQNEUbgPg@mail.gmail.com>
References: <CAJg1wMR3d8J3PCAFQs7bnR6m+cgpnLjtRZoHDU9CaOHGW9APDQ@mail.gmail.com>
	<CAJg1wMTJqXnjd7mnQg2sWmASPePpsvxwerS_5v9MXXeAZT6BbA@mail.gmail.com>
	<CA+QcL10o4Vv2oK1byEeQ26rFOcFa+ek59F+aBk+GjtQNEUbgPg@mail.gmail.com>
Message-ID: <CAL+AC4Dkbwpk1uSJt=uQBLDS9fdSt9_8ASF332Ben_mj3We95g@mail.gmail.com>

<groan>

On Wed, Jan 27, 2016 at 12:33 PM, Nick Boldt <nboldt at redhat.com> wrote:

> ICYMI, Eclipse simrel release for 2017 will be called Oxygen.
>
> Not nearly as noble a name as this year's release, but still a breath
> of fresh air after all the planet & scientist names used in the past.
>
>
> ---------- Forwarded message ----------
> From: Chris Aniszczyk <caniszczyk at gmail.com>
> Date: Wed, Jan 27, 2016 at 12:30 PM
> Subject: Re: [eclipse.org-planning-council] Neon+1 Naming Results
> To: "eclipse.org-planning-council" <
> eclipse.org-planning-council at eclipse.org>
>
>
> Just to follow up on this, "Eclipse Oxygen" it is for Neon+1:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=485861#c3
>
> On Thu, Jan 14, 2016 at 10:35 AM, Chris Aniszczyk <caniszczyk at gmail.com>
> wrote:
> >
> > The results are in:
> > http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_dd4ff581da35bddc
> >
> > 1. Oxygen  (Condorcet winner: wins contests with all other choices)
> > 2. Odyssey  loses to Oxygen by 121?112
> > 3. Osiris  loses to Oxygen by 141?94, loses to Odyssey by 131?97
> > 4. Opal  loses to Oxygen by 136?95, loses to Osiris by 112?109
> > 5. Oberon  loses to Oxygen by 143?98, loses to Opal by 115?110
> > 6. Orpheus  loses to Oxygen by 142?90, loses to Oberon by 121?99
> > 7. Ozone  loses to Oxygen by 152?61, loses to Orpheus by 111?103
> > 8. Ohm  loses to Oxygen by 152?69, loses to Ozone by 103?99
> > 9. Oceana  loses to Oxygen by 161?54, loses to Ohm by 103?94
> > 10. Oort  loses to Oxygen by 158?63, loses to Oceana by 116?78
> >
> > I've started the process to legally clear the name via bug 485861
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=485861
> >
> > --
> > Cheers,
> >
> > Chris Aniszczyk
> > http://aniszczyk.org
> > +1 512 961 6719
>
>
>
>
> --
> Cheers,
>
> Chris Aniszczyk
> http://aniszczyk.org
> +1 512 961 6719
>
> _______________________________________________
> eclipse.org-planning-council mailing list
> eclipse.org-planning-council at eclipse.org
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>
> IMPORTANT: Membership in this list is generated by processes internal
> to the Eclipse Foundation.  To be permanently removed from this list,
> you must contact emo at eclipse.org to request removal.
>
>
> --
> 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




-- 
________________________
Robert ("Bob") Brodt
Senior Software Engineer
JBoss by Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160127/d04be052/attachment.html 

From manderse at redhat.com  Wed Jan 27 17:55:40 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 27 Jan 2016 23:55:40 +0100
Subject: [jbosstools-dev] ERT created
Message-ID: <0C5A5775-EA3D-4642-A6E9-867369364CE1@redhat.com>

Hi,

Just wanted to let you know https://issues.jboss.org/projects/ERT is now 
live.

This is the jira we have an semi-experimental mirroring of 
bugs.eclipse.org issues
to use in sprint planning.

See https://issues.jboss.org/projects/ERT/summary/statistics for 
overview.

I'll do a write up tomorrow on what it means/entails - but just a 
headsup in case
you start getting mail notifications about it ;)

/max
http://about.me/maxandersen

From nboldt at redhat.com  Thu Jan 28 00:14:14 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 28 Jan 2016 00:14:14 -0500
Subject: [jbosstools-dev] JBoss Tools Core 4.3.1.Beta2a bits available for
	QE testing
Message-ID: <CA+QcL13qPbn_jVKPPCk08M7-gEOxg+2B3XH8sd=tZDs1KXxpdg@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/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page

--

Additional update sites:
* http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.1.Beta2a/
* http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.1.Beta2a/

Target platforms:
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.2.Beta2-SNAPSHOT
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.52.0.Beta2-SNAPSHOT

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

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

--

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.1.0.Beta2%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.3.1.Beta2%22%29%29%29

To compare the upcoming version of Central (4.3.1.Beta2a) 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.1.Beta2a/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.1.Beta2a/
 -Djboss.discovery.earlyaccess.list.url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.1.Beta2a/jbosstools-earlyaccess.properties

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


From nboldt at redhat.com  Thu Jan 28 13:33:27 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 28 Jan 2016 13:33:27 -0500
Subject: [jbosstools-dev] FYI: now building 4.3.1.CR1 // 4.3.1.Beta2x
	effectively frozen
Message-ID: <CA+QcL11t5O6wUKNq8-LhUSE50Cp6XdFGqmC4RHs_4yiN3uTOCg@mail.gmail.com>

Alexey has requested that the current pile of 4.3.mars/9.0.mars jobs
[1] be reconfigured to build from the 4.3.x branch. Currently, they
are set to build from the 4.3.1.Beta2x branch, in case we need a
respin.

[1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/

This means that starting from this change, the 4.3.1.Beta2x branch is
effectively frozen, since we won't be building any CI builds from
there (unless we switch back).

This also means that IFF we need a Beta2b respin (hopefully unlikely
since there's really no time in the schedule for it), it will come
with a bigger-than-normal cost:

a) I will have to delete all the CR1 CI builds so they don't pollute
the Beta2 aggregation with the wrong BUILD_ALIAS qualifiers
b) I will have to switch the jobs back to use the 4.3.1.Beta2x branch
c) I will have to build THE WHOLE STACK, not just the jobs which
caused the respin (ie., for respin-a we only rebuilt Base and
Openshift, then the JBT and JBDS aggregates & discovery sites). This
will create what looks like a much larger diff for QE since the
qualifiers will be incremented even though bitwise the contents are
the same.

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

From alkazako at redhat.com  Thu Jan 28 14:04:26 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Thu, 28 Jan 2016 14:04:26 -0500
Subject: [jbosstools-dev] FYI: now building 4.3.1.CR1 // 4.3.1.Beta2x
 effectively frozen
In-Reply-To: <CA+QcL11t5O6wUKNq8-LhUSE50Cp6XdFGqmC4RHs_4yiN3uTOCg@mail.gmail.com>
References: <CA+QcL11t5O6wUKNq8-LhUSE50Cp6XdFGqmC4RHs_4yiN3uTOCg@mail.gmail.com>
Message-ID: <56AA663A.3080500@redhat.com>

There was some misunderstanding during our long discussion in HipChat.
But long story short.
Beta2 is our priority right now. If building a new CR1 built (from 4.3.x 
branch) may cause additional risks for Beta2 release then let's DO NOT 
do any CR1 build until we release Beta2.
For example the c) from the list below is exactly such a risk we want to 
avoid.

Thanks.

On 01/28/2016 01:33 PM, Nick Boldt wrote:
> Alexey has requested that the current pile of 4.3.mars/9.0.mars jobs
> [1] be reconfigured to build from the 4.3.x branch. Currently, they
> are set to build from the 4.3.1.Beta2x branch, in case we need a
> respin.
>
> [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/
>
> This means that starting from this change, the 4.3.1.Beta2x branch is
> effectively frozen, since we won't be building any CI builds from
> there (unless we switch back).
>
> This also means that IFF we need a Beta2b respin (hopefully unlikely
> since there's really no time in the schedule for it), it will come
> with a bigger-than-normal cost:
>
> a) I will have to delete all the CR1 CI builds so they don't pollute
> the Beta2 aggregation with the wrong BUILD_ALIAS qualifiers
> b) I will have to switch the jobs back to use the 4.3.1.Beta2x branch
> c) I will have to build THE WHOLE STACK, not just the jobs which
> caused the respin (ie., for respin-a we only rebuilt Base and
> Openshift, then the JBT and JBDS aggregates & discovery sites). This
> will create what looks like a much larger diff for QE since the
> qualifiers will be incremented even though bitwise the contents are
> the same.
>


From ldimaggi at redhat.com  Thu Jan 28 14:13:49 2016
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Thu, 28 Jan 2016 14:13:49 -0500
Subject: [jbosstools-dev] FYI: now building 4.3.1.CR1 // 4.3.1.Beta2x
 effectively frozen
In-Reply-To: <56AA663A.3080500@redhat.com>
References: <CA+QcL11t5O6wUKNq8-LhUSE50Cp6XdFGqmC4RHs_4yiN3uTOCg@mail.gmail.com>
	<56AA663A.3080500@redhat.com>
Message-ID: <CA+qK+9msKDJSsHojb+eMHCM9mEth_JT=YXmytiT=1uK6Fth_rw@mail.gmail.com>

Can we just finish Beta2 first? Qe should complete its testing on January
29 - and then we should ship on Feb 2.

-- Len

On Thu, Jan 28, 2016 at 2:04 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

> There was some misunderstanding during our long discussion in HipChat.
> But long story short.
> Beta2 is our priority right now. If building a new CR1 built (from 4.3.x
> branch) may cause additional risks for Beta2 release then let's DO NOT
> do any CR1 build until we release Beta2.
> For example the c) from the list below is exactly such a risk we want to
> avoid.
>
> Thanks.
>
> On 01/28/2016 01:33 PM, Nick Boldt wrote:
> > Alexey has requested that the current pile of 4.3.mars/9.0.mars jobs
> > [1] be reconfigured to build from the 4.3.x branch. Currently, they
> > are set to build from the 4.3.1.Beta2x branch, in case we need a
> > respin.
> >
> > [1]
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/
> >
> > This means that starting from this change, the 4.3.1.Beta2x branch is
> > effectively frozen, since we won't be building any CI builds from
> > there (unless we switch back).
> >
> > This also means that IFF we need a Beta2b respin (hopefully unlikely
> > since there's really no time in the schedule for it), it will come
> > with a bigger-than-normal cost:
> >
> > a) I will have to delete all the CR1 CI builds so they don't pollute
> > the Beta2 aggregation with the wrong BUILD_ALIAS qualifiers
> > b) I will have to switch the jobs back to use the 4.3.1.Beta2x branch
> > c) I will have to build THE WHOLE STACK, not just the jobs which
> > caused the respin (ie., for respin-a we only rebuilt Base and
> > Openshift, then the JBT and JBDS aggregates & discovery sites). This
> > will create what looks like a much larger diff for QE since the
> > qualifiers will be incremented even though bitwise the contents are
> > the same.
> >
>
> _______________________________________________
> 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/20160128/823b8245/attachment-0001.html 

From nboldt at redhat.com  Thu Jan 28 16:22:52 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 28 Jan 2016 16:22:52 -0500
Subject: [jbosstools-dev] FYI: now building 4.3.1.CR1 // 4.3.1.Beta2x
 effectively frozen
In-Reply-To: <CA+qK+9msKDJSsHojb+eMHCM9mEth_JT=YXmytiT=1uK6Fth_rw@mail.gmail.com>
References: <CA+QcL11t5O6wUKNq8-LhUSE50Cp6XdFGqmC4RHs_4yiN3uTOCg@mail.gmail.com>
	<56AA663A.3080500@redhat.com>
	<CA+qK+9msKDJSsHojb+eMHCM9mEth_JT=YXmytiT=1uK6Fth_rw@mail.gmail.com>
Message-ID: <CA+QcL11zhMqyPGoKLXMs-pN_N3mXdH-V0ZHMA4+SDsW4GaVQGg@mail.gmail.com>

Yes, but if we need CR1 bits available on Wed, we need to build them first.
:D

So, we're building them now.

Regarding the (c) issue, I've backed up all the snapshots build folders
from 4.3.1.Beta2a so IFF we need a respin-b, we can use them as input.



On Thu, Jan 28, 2016 at 2:13 PM, Leonard Dimaggio <ldimaggi at redhat.com>
wrote:

> Can we just finish Beta2 first? Qe should complete its testing on January
> 29 - and then we should ship on Feb 2.
>
> -- Len
>
> On Thu, Jan 28, 2016 at 2:04 PM, Alexey Kazakov <alkazako at redhat.com>
> wrote:
>
>> There was some misunderstanding during our long discussion in HipChat.
>> But long story short.
>> Beta2 is our priority right now. If building a new CR1 built (from 4.3.x
>> branch) may cause additional risks for Beta2 release then let's DO NOT
>> do any CR1 build until we release Beta2.
>> For example the c) from the list below is exactly such a risk we want to
>> avoid.
>>
>> Thanks.
>>
>> On 01/28/2016 01:33 PM, Nick Boldt wrote:
>> > Alexey has requested that the current pile of 4.3.mars/9.0.mars jobs
>> > [1] be reconfigured to build from the 4.3.x branch. Currently, they
>> > are set to build from the 4.3.1.Beta2x branch, in case we need a
>> > respin.
>> >
>> > [1]
>> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/
>> >
>> > This means that starting from this change, the 4.3.1.Beta2x branch is
>> > effectively frozen, since we won't be building any CI builds from
>> > there (unless we switch back).
>> >
>> > This also means that IFF we need a Beta2b respin (hopefully unlikely
>> > since there's really no time in the schedule for it), it will come
>> > with a bigger-than-normal cost:
>> >
>> > a) I will have to delete all the CR1 CI builds so they don't pollute
>> > the Beta2 aggregation with the wrong BUILD_ALIAS qualifiers
>> > b) I will have to switch the jobs back to use the 4.3.1.Beta2x branch
>> > c) I will have to build THE WHOLE STACK, not just the jobs which
>> > caused the respin (ie., for respin-a we only rebuilt Base and
>> > Openshift, then the JBT and JBDS aggregates & discovery sites). This
>> > will create what looks like a much larger diff for QE since the
>> > qualifiers will be incremented even though bitwise the contents are
>> > the same.
>> >
>>
>> _______________________________________________
>> 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
>
>
>
> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160128/4a3aa9cf/attachment.html 

From manderse at redhat.com  Fri Jan 29 01:23:40 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 29 Jan 2016 01:23:40 -0500 (EST)
Subject: [jbosstools-dev] FYI: now building 4.3.1.CR1 // 4.3.1.Beta2x
	effectively frozen
In-Reply-To: <CA+QcL11zhMqyPGoKLXMs-pN_N3mXdH-V0ZHMA4+SDsW4GaVQGg@mail.gmail.com>
References: <CA+QcL11t5O6wUKNq8-LhUSE50Cp6XdFGqmC4RHs_4yiN3uTOCg@mail.gmail.com>
	<56AA663A.3080500@redhat.com>
	<CA+qK+9msKDJSsHojb+eMHCM9mEth_JT=YXmytiT=1uK6Fth_rw@mail.gmail.com>
	<CA+QcL11zhMqyPGoKLXMs-pN_N3mXdH-V0ZHMA4+SDsW4GaVQGg@mail.gmail.com>
Message-ID: <3AA7446F-C322-4FF6-B93F-B81FED731D9D@redhat.com>

I'm not following here. Why do we need cr bits on Wednesday ? Are we back again at having zero time between the beta and cr1?

I thought we pushed the dates to avoid exactly this. 

/max
http://about.me/maxandersen


> On 28 Jan 2016, at 22:23, Nick Boldt <nboldt at redhat.com> wrote:
> 
> Yes, but if we need CR1 bits available on Wed, we need to build them first. :D
> 
> So, we're building them now. 
> 
> Regarding the (c) issue, I've backed up all the snapshots build folders from 4.3.1.Beta2a so IFF we need a respin-b, we can use them as input.
> 
> 
> 
>> On Thu, Jan 28, 2016 at 2:13 PM, Leonard Dimaggio <ldimaggi at redhat.com> wrote:
>> Can we just finish Beta2 first? Qe should complete its testing on January 29 - and then we should ship on Feb 2.
>> 
>> -- Len
>> 
>>> On Thu, Jan 28, 2016 at 2:04 PM, Alexey Kazakov <alkazako at redhat.com> wrote:
>>> There was some misunderstanding during our long discussion in HipChat.
>>> But long story short.
>>> Beta2 is our priority right now. If building a new CR1 built (from 4.3.x
>>> branch) may cause additional risks for Beta2 release then let's DO NOT
>>> do any CR1 build until we release Beta2.
>>> For example the c) from the list below is exactly such a risk we want to
>>> avoid.
>>> 
>>> Thanks.
>>> 
>>> On 01/28/2016 01:33 PM, Nick Boldt wrote:
>>> > Alexey has requested that the current pile of 4.3.mars/9.0.mars jobs
>>> > [1] be reconfigured to build from the 4.3.x branch. Currently, they
>>> > are set to build from the 4.3.1.Beta2x branch, in case we need a
>>> > respin.
>>> >
>>> > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/
>>> >
>>> > This means that starting from this change, the 4.3.1.Beta2x branch is
>>> > effectively frozen, since we won't be building any CI builds from
>>> > there (unless we switch back).
>>> >
>>> > This also means that IFF we need a Beta2b respin (hopefully unlikely
>>> > since there's really no time in the schedule for it), it will come
>>> > with a bigger-than-normal cost:
>>> >
>>> > a) I will have to delete all the CR1 CI builds so they don't pollute
>>> > the Beta2 aggregation with the wrong BUILD_ALIAS qualifiers
>>> > b) I will have to switch the jobs back to use the 4.3.1.Beta2x branch
>>> > c) I will have to build THE WHOLE STACK, not just the jobs which
>>> > caused the respin (ie., for respin-a we only rebuilt Base and
>>> > Openshift, then the JBT and JBDS aggregates & discovery sites). This
>>> > will create what looks like a much larger diff for QE since the
>>> > qualifiers will be incremented even though bitwise the contents are
>>> > the same.
>>> >
>>> 
>>> _______________________________________________
>>> 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
>> 
>> 
>> 
>> _______________________________________________
>> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160129/2353968a/attachment.html 

From alkazako at redhat.com  Fri Jan 29 06:33:12 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Fri, 29 Jan 2016 06:33:12 -0500 (EST)
Subject: [jbosstools-dev] FYI: now building 4.3.1.CR1 //
	4.3.1.Beta2x	effectively frozen
In-Reply-To: <3AA7446F-C322-4FF6-B93F-B81FED731D9D@redhat.com>
References: <CA+QcL11t5O6wUKNq8-LhUSE50Cp6XdFGqmC4RHs_4yiN3uTOCg@mail.gmail.com>
	<56AA663A.3080500@redhat.com>
	<CA+qK+9msKDJSsHojb+eMHCM9mEth_JT=YXmytiT=1uK6Fth_rw@mail.gmail.com>
	<CA+QcL11zhMqyPGoKLXMs-pN_N3mXdH-V0ZHMA4+SDsW4GaVQGg@mail.gmail.com>
	<3AA7446F-C322-4FF6-B93F-B81FED731D9D@redhat.com>
Message-ID: <90FDE91B-F91B-4BCF-82A2-ED00CA227C11@redhat.com>

We need this for the PDK installer. It uses nightly builds.



> On Jan 29, 2016, at 1:23 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
> 
> I'm not following here. Why do we need cr bits on Wednesday ? Are we back again at having zero time between the beta and cr1?
> 
> I thought we pushed the dates to avoid exactly this. 
> 
> /max
> http://about.me/maxandersen
> 
> 
>> On 28 Jan 2016, at 22:23, Nick Boldt <nboldt at redhat.com> wrote:
>> 
>> Yes, but if we need CR1 bits available on Wed, we need to build them first. :D
>> 
>> So, we're building them now. 
>> 
>> Regarding the (c) issue, I've backed up all the snapshots build folders from 4.3.1.Beta2a so IFF we need a respin-b, we can use them as input.
>> 
>> 
>> 
>>> On Thu, Jan 28, 2016 at 2:13 PM, Leonard Dimaggio <ldimaggi at redhat.com> wrote:
>>> Can we just finish Beta2 first? Qe should complete its testing on January 29 - and then we should ship on Feb 2.
>>> 
>>> -- Len
>>> 
>>>> On Thu, Jan 28, 2016 at 2:04 PM, Alexey Kazakov <alkazako at redhat.com> wrote:
>>>> There was some misunderstanding during our long discussion in HipChat.
>>>> But long story short.
>>>> Beta2 is our priority right now. If building a new CR1 built (from 4.3.x
>>>> branch) may cause additional risks for Beta2 release then let's DO NOT
>>>> do any CR1 build until we release Beta2.
>>>> For example the c) from the list below is exactly such a risk we want to
>>>> avoid.
>>>> 
>>>> Thanks.
>>>> 
>>>> On 01/28/2016 01:33 PM, Nick Boldt wrote:
>>>> > Alexey has requested that the current pile of 4.3.mars/9.0.mars jobs
>>>> > [1] be reconfigured to build from the 4.3.x branch. Currently, they
>>>> > are set to build from the 4.3.1.Beta2x branch, in case we need a
>>>> > respin.
>>>> >
>>>> > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/
>>>> >
>>>> > This means that starting from this change, the 4.3.1.Beta2x branch is
>>>> > effectively frozen, since we won't be building any CI builds from
>>>> > there (unless we switch back).
>>>> >
>>>> > This also means that IFF we need a Beta2b respin (hopefully unlikely
>>>> > since there's really no time in the schedule for it), it will come
>>>> > with a bigger-than-normal cost:
>>>> >
>>>> > a) I will have to delete all the CR1 CI builds so they don't pollute
>>>> > the Beta2 aggregation with the wrong BUILD_ALIAS qualifiers
>>>> > b) I will have to switch the jobs back to use the 4.3.1.Beta2x branch
>>>> > c) I will have to build THE WHOLE STACK, not just the jobs which
>>>> > caused the respin (ie., for respin-a we only rebuilt Base and
>>>> > Openshift, then the JBT and JBDS aggregates & discovery sites). This
>>>> > will create what looks like a much larger diff for QE since the
>>>> > qualifiers will be incremented even though bitwise the contents are
>>>> > the same.
>>>> >
>>>> 
>>>> _______________________________________________
>>>> 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
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> 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
> _______________________________________________
> 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/20160129/394a4f00/attachment-0001.html 

From alkazako at redhat.com  Fri Jan 29 06:59:52 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Fri, 29 Jan 2016 06:59:52 -0500 (EST)
Subject: [jbosstools-dev] FYI: now building 4.3.1.CR1
	//	4.3.1.Beta2x	effectively frozen
In-Reply-To: <90FDE91B-F91B-4BCF-82A2-ED00CA227C11@redhat.com>
References: <CA+QcL11t5O6wUKNq8-LhUSE50Cp6XdFGqmC4RHs_4yiN3uTOCg@mail.gmail.com>
	<56AA663A.3080500@redhat.com>
	<CA+qK+9msKDJSsHojb+eMHCM9mEth_JT=YXmytiT=1uK6Fth_rw@mail.gmail.com>
	<CA+QcL11zhMqyPGoKLXMs-pN_N3mXdH-V0ZHMA4+SDsW4GaVQGg@mail.gmail.com>
	<3AA7446F-C322-4FF6-B93F-B81FED731D9D@redhat.com>
	<90FDE91B-F91B-4BCF-82A2-ED00CA227C11@redhat.com>
Message-ID: <63B5903B-68BF-4DA7-B578-757B43F21860@redhat.com>

Just for clarification. We are fixing bugs in CR1 and we need them available in nightly builds for the PDK installer.


> On Jan 29, 2016, at 6:33 AM, Alexey Kazakov <alkazako at redhat.com> wrote:
> 
> We need this for the PDK installer. It uses nightly builds.
> 
> 
> 
>> On Jan 29, 2016, at 1:23 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
>> 
>> I'm not following here. Why do we need cr bits on Wednesday ? Are we back again at having zero time between the beta and cr1?
>> 
>> I thought we pushed the dates to avoid exactly this. 
>> 
>> /max
>> http://about.me/maxandersen
>> 
>> 
>>> On 28 Jan 2016, at 22:23, Nick Boldt <nboldt at redhat.com> wrote:
>>> 
>>> Yes, but if we need CR1 bits available on Wed, we need to build them first. :D
>>> 
>>> So, we're building them now. 
>>> 
>>> Regarding the (c) issue, I've backed up all the snapshots build folders from 4.3.1.Beta2a so IFF we need a respin-b, we can use them as input.
>>> 
>>> 
>>> 
>>>> On Thu, Jan 28, 2016 at 2:13 PM, Leonard Dimaggio <ldimaggi at redhat.com> wrote:
>>>> Can we just finish Beta2 first? Qe should complete its testing on January 29 - and then we should ship on Feb 2.
>>>> 
>>>> -- Len
>>>> 
>>>>> On Thu, Jan 28, 2016 at 2:04 PM, Alexey Kazakov <alkazako at redhat.com> wrote:
>>>>> There was some misunderstanding during our long discussion in HipChat.
>>>>> But long story short.
>>>>> Beta2 is our priority right now. If building a new CR1 built (from 4.3.x
>>>>> branch) may cause additional risks for Beta2 release then let's DO NOT
>>>>> do any CR1 build until we release Beta2.
>>>>> For example the c) from the list below is exactly such a risk we want to
>>>>> avoid.
>>>>> 
>>>>> Thanks.
>>>>> 
>>>>> On 01/28/2016 01:33 PM, Nick Boldt wrote:
>>>>> > Alexey has requested that the current pile of 4.3.mars/9.0.mars jobs
>>>>> > [1] be reconfigured to build from the 4.3.x branch. Currently, they
>>>>> > are set to build from the 4.3.1.Beta2x branch, in case we need a
>>>>> > respin.
>>>>> >
>>>>> > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/
>>>>> >
>>>>> > This means that starting from this change, the 4.3.1.Beta2x branch is
>>>>> > effectively frozen, since we won't be building any CI builds from
>>>>> > there (unless we switch back).
>>>>> >
>>>>> > This also means that IFF we need a Beta2b respin (hopefully unlikely
>>>>> > since there's really no time in the schedule for it), it will come
>>>>> > with a bigger-than-normal cost:
>>>>> >
>>>>> > a) I will have to delete all the CR1 CI builds so they don't pollute
>>>>> > the Beta2 aggregation with the wrong BUILD_ALIAS qualifiers
>>>>> > b) I will have to switch the jobs back to use the 4.3.1.Beta2x branch
>>>>> > c) I will have to build THE WHOLE STACK, not just the jobs which
>>>>> > caused the respin (ie., for respin-a we only rebuilt Base and
>>>>> > Openshift, then the JBT and JBDS aggregates & discovery sites). This
>>>>> > will create what looks like a much larger diff for QE since the
>>>>> > qualifiers will be incremented even though bitwise the contents are
>>>>> > the same.
>>>>> >
>>>>> 
>>>>> _______________________________________________
>>>>> 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
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> 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
>> _______________________________________________
>> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160129/0a031c8b/attachment.html 

From mistria at redhat.com  Fri Jan 29 10:03:44 2016
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 29 Jan 2016 16:03:44 +0100
Subject: [jbosstools-dev] EclipseCon France, June 7th-9th
Message-ID: <56AB7F50.3090107@redhat.com>

Hi

The call for paper for EclipseCon France (June 7th-9th, Toulouse) is 
open https://www.eclipsecon.org/france2016/cfp
Any talks about Eclipse-related technologies is welcome, from user or 
extender perspective. That includes Eclipse IDE, JBoss Tools, Eclipse 
Che, Vert.x, IoT, LocationTech... So many topics where Red Hat is relevant!
https://www.eclipsecon.org/france2016/cfp

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/20160129/6dbb853a/attachment.html