From noreply at northcalsportfishing.com  Wed Apr  1 09:38:13 2015
From: noreply at northcalsportfishing.com (Canadian-Pills)
Date: Wed, 1 Apr 2015 12:38:13 -0100
Subject: [jbosstools-dev] Every day we dedicate our passion to provide more
	people with top quality effective drugs!
Message-ID: <E1Hyb8E-00060z-Qf@YY73pQP01>

   

		Teixeiras practice is some really big ballroom, wasnt for allies
baseball. Helens, this tocontinue enjoying high heaven false prophet 

		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
		9f
		or
		6W
		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
An
Sp 0%
sa
on
ec  A
,M
ym
ia ut
as
ou
l  he
te
s 
in nt
rc
de
te ic
ar
li
rn  M
d,
ve
et ed
Ec
ry
 p s 
he

ri  
ck

ce  

s   

   N
 O
 F
 2 o 
nl
as
4/ pr
y 
t 
7  es
re
wo
cu cr
li
rl
st ip
ab
dw
om ti
le
id
er on
 s
e 
 s  r
up
sh
up eq
pl
ip
po ui
ie
pi
rt re
rs
ng
  d

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

From mistria at redhat.com  Wed Apr  1 10:28:40 2015
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 01 Apr 2015 16:28:40 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.Final ]
Message-ID: <551C0098.1010506@redhat.com>

Component leads, please tag your repositories!

$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called 
jbosstools, also often called origin
$ git tag jbosstools-4.2.3.Final FETCH_HEAD
$ git push jbosstools jbosstools-4.2.3.Final
-- 
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/20150401/15da4c03/attachment.html 

From ggastald at redhat.com  Wed Apr  1 10:34:38 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Wed, 01 Apr 2015 11:34:38 -0300
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.Final ]
In-Reply-To: <551C0098.1010506@redhat.com>
References: <551C0098.1010506@redhat.com>
Message-ID: <551C01FE.4000906@redhat.com>

Done for forge.
Thanks!

On 04/01/2015 11:28 AM, Mickael Istria wrote:
> Component leads, please tag your repositories!
>
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called 
> jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.Final FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.Final
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets 
> <http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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

From fbricon at redhat.com  Wed Apr  1 10:39:35 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Wed, 1 Apr 2015 10:39:35 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
	please tag your projects [ branch jbosstools-4.2.x -> tag
	jbosstools-4.2.3.Final ]
In-Reply-To: <551C01FE.4000906@redhat.com>
References: <551C0098.1010506@redhat.com> <551C01FE.4000906@redhat.com>
Message-ID: <C0062F67-8B4D-495F-857B-064F78B1CC57@redhat.com>

Done for central 

> Le 1 avr. 2015 ? 10:34, George Gastaldi <ggastald at redhat.com> a ?crit :
> 
> Done for forge.
> Thanks!
> 
> On 04/01/2015 11:28 AM, Mickael Istria wrote:
>> Component leads, please tag your repositories!
>> 
>> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called jbosstools, also often called origin
>> $ git tag jbosstools-4.2.3.Final FETCH_HEAD
>> $ git push jbosstools jbosstools-4.2.3.Final
>> -- 
>> 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 <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev <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/20150401/5a5007b5/attachment.html 

From kmarmaliykov at exadel.com  Wed Apr  1 10:44:22 2015
From: kmarmaliykov at exadel.com (Konstantin Marmalyukov)
Date: Wed, 01 Apr 2015 17:44:22 +0300
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.Final ]
In-Reply-To: <551C0098.1010506@redhat.com>
References: <551C0098.1010506@redhat.com>
Message-ID: <551C0446.1000204@exadel.com>

Vpe and Browsersim done.

On 4/1/2015 5:28 PM, Mickael Istria wrote:
> Component leads, please tag your repositories!
>
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called 
> jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.Final FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.Final
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets 
> <http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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

From adietish at redhat.com  Wed Apr  1 10:58:20 2015
From: adietish at redhat.com (=?windows-1252?Q?Andr=E9_Dietisheim?=)
Date: Wed, 01 Apr 2015 16:58:20 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.Final ]
In-Reply-To: <551C0098.1010506@redhat.com>
References: <551C0098.1010506@redhat.com>
Message-ID: <551C078C.5020508@redhat.com>

done for OpenShift.

thanks!

On 04/01/2015 04:28 PM, Mickael Istria wrote:
> Component leads, please tag your repositories!
>
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called 
> jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.Final FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.Final
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets 
> <http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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

From snjezana.peco at redhat.com  Wed Apr  1 12:17:04 2015
From: snjezana.peco at redhat.com (Snjezana Peco)
Date: Wed, 01 Apr 2015 18:17:04 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.Final ]
In-Reply-To: <551C0098.1010506@redhat.com>
References: <551C0098.1010506@redhat.com>
Message-ID: <551C1A00.5040106@redhat.com>

Done for arquillian, birt and portlet.

Snjeza

On 4/1/2015 4:28 PM, Mickael Istria wrote:
> Component leads, please tag your repositories!
>
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called 
> jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.Final FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.Final
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets 
> <http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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

From xcoulon at redhat.com  Thu Apr  2 03:25:53 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Thu, 2 Apr 2015 09:25:53 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
	please tag your projects [ branch jbosstools-4.2.x -> tag
	jbosstools-4.2.3.Final ]
In-Reply-To: <551C0098.1010506@redhat.com>
References: <551C0098.1010506@redhat.com>
Message-ID: <41F0D7F9-927C-40C7-B31C-B6EC64AA6985@redhat.com>

Done for LiveReload and Webservices.

Best regards,
/Xavier



> On 01 Apr 2015, at 16:28, Mickael Istria <mistria at redhat.com> wrote:
> 
> git push jbosstools jbosstools-4.2.3.Final

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

From koen.aers at jboss.com  Thu Apr  2 08:19:16 2015
From: koen.aers at jboss.com (Koen Aers)
Date: Thu, 2 Apr 2015 14:19:16 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
	please tag your projects [ branch jbosstools-4.2.x -> tag
	jbosstools-4.2.3.Final ]
In-Reply-To: <551C0098.1010506@redhat.com>
References: <551C0098.1010506@redhat.com>
Message-ID: <1ED4954D-0536-470D-85F8-28573BB679FD@jboss.com>

done for hibernate

> Op 1-apr.-2015, om 16:28 heeft Mickael Istria <mistria at redhat.com> het volgende geschreven:
> 
> Component leads, please tag your repositories!
> 
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.Final FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.Final
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com/> - My Tweets <http://twitter.com/mickaelistria>_______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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

From alkazako at redhat.com  Thu Apr  2 13:39:30 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Thu, 02 Apr 2015 10:39:30 -0700
Subject: [jbosstools-dev] JBoss Tools 4.2.3.Final is now available
Message-ID: <551D7ED2.70600@redhat.com>

This is a stable release aimed at Eclipse 4.4.2 Luna SR2 users.

Eclipse Marketplace: 
https://marketplace.eclipse.org/content/jboss-tools-luna

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

Update Site Zips: 
http://sourceforge.net/projects/jboss/files/JBossTools/jbosstools4.2.3.x/

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

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

Schedule / Upcoming Releases: 
https://issues.jboss.org/browse/JBIDE/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel 


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

From alkazako at redhat.com  Thu Apr  2 13:54:26 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Thu, 02 Apr 2015 10:54:26 -0700
Subject: [jbosstools-dev] JBoss Developer Studio 8.1.0.GA is available
Message-ID: <551D8252.4000902@redhat.com>

JBoss Developer Studio 8.1.0.GA is available!

Download page and installer:
* http://tools.jboss.org/downloads/devstudio/luna/8.1.0.GA.html
* https://www.jboss.org/products/devstudio/overview/

Update site: https://devstudio.jboss.com/updates/8.0/

Early Access site: https://devstudio.jboss.com/earlyaccess/8.0/

--

Eclipse Marketplace: 
https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-luna

--

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


From akazakov at exadel.com  Thu Apr  2 14:14:13 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 02 Apr 2015 11:14:13 -0700
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.Final ]
In-Reply-To: <551C0098.1010506@redhat.com>
References: <551C0098.1010506@redhat.com>
Message-ID: <551D86F5.7070304@exadel.com>

Done for the rest of the components: base, jst, javaee, aerogear, 
server, freemarker.



On 04/01/2015 07:28 AM, Mickael Istria wrote:
> Component leads, please tag your repositories!
>
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called 
> jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.Final FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.Final
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets 
> <http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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

From Paypal.1425018479.54f00e6fd509d at Service.co.uk  Tue Apr  7 07:52:39 2015
From: Paypal.1425018479.54f00e6fd509d at Service.co.uk (Paypal)
Date: Tue, 7 Apr 2015 11:52:39 +0000
Subject: [jbosstools-dev] PayPal: Update your credit card detail !
Message-ID: <c1d34fef9beb9862f6c36baa2ddf3ee0@ssl.siteskins.net>

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150407/1be860f8/attachment.html 

From ib at nesfuduk.gov  Tue Apr  7 19:08:59 2015
From: ib at nesfuduk.gov (ngsqdh)
Date: Tue, 07 Apr 2015 23:08:59 -0000
Subject: [jbosstools-dev] =?utf-8?b?amJvc3NpZGUtZGV26ZSA5ZSu5Li7566hMg==?=
	=?utf-8?b?5aSp5by65YyW6K6t57uD?=
Message-ID: <20160407074048841523@gmjf.net>

???jbosside-dev????
?????2????????????????1?3?6?9?1?4?7?2?8?1?6????&Q?Q?1?3?2?1?2?5?9?1?2?4?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150407/0194f08d/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sales?????????.doc
Type: application/kswps
Size: 34331 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150407/0194f08d/attachment.bin 

From max.andersen at redhat.com  Wed Apr  8 09:05:54 2015
From: max.andersen at redhat.com (Max Rydahl Andersen)
Date: Wed, 08 Apr 2015 15:05:54 +0200
Subject: [jbosstools-dev] VersionWatch repo
In-Reply-To: <FF830091-6A1B-4C4C-A669-77217B4D1D2C@redhat.com>
References: <54D38435.6080005@redhat.com>
	<FF830091-6A1B-4C4C-A669-77217B4D1D2C@redhat.com>
Message-ID: <201383C4-87A6-4B9F-BB12-EF0F301E6056@redhat.com>

Did not notice this was not on mailing list.

Jiri - what is the status of this ?

Which repo has the latest content and which one is used in build ?


> where are we with this ?
>
> I see no conclusion and now wondering which repo is the master ?
>
> /max
>
>> Hi Nick,
>>
>> some time ago there was a request to put VersionWatch outside QE 
>> repo. So I've created a new repo under my account with it:
>>
>> https://github.com/jpeterka/jbosstools-vwatch
>>
>> If you find it desirable feel free to clone it among other jbosstools 
>> repositories.
>>
>> Thanks,
>>
>> Jirka
>>
>> -- 
>> Jiri Peterka
>> JBoss Developer Studio QE
>> Red Hat Czech s.r.o., Purkynova 99, 612 45 Brno, Czech Republic
>> IRC: jpeterka #jboss-qa, #devstudio-qa
>> email: jpeterka at redhat.com
>
>
> /max
> http://about.me/maxandersen


/max
http://about.me/maxandersen

From jpeterka at redhat.com  Wed Apr  8 09:52:13 2015
From: jpeterka at redhat.com (Jiri Peterka)
Date: Wed, 08 Apr 2015 15:52:13 +0200
Subject: [jbosstools-dev] VersionWatch repo
In-Reply-To: <201383C4-87A6-4B9F-BB12-EF0F301E6056@redhat.com>
References: <54D38435.6080005@redhat.com>
	<FF830091-6A1B-4C4C-A669-77217B4D1D2C@redhat.com>
	<201383C4-87A6-4B9F-BB12-EF0F301E6056@redhat.com>
Message-ID: <5525328D.6040506@redhat.com>

Max,

On 04/08/2015 03:05 PM, Max Rydahl Andersen wrote:
> Did not notice this was not on mailing list.
>
> Jiri - what is the status of this ?
There was no update for a while, see tracking JIRA - 
https://issues.jboss.org/browse/JBIDE-19190 . I've forwarded to you also 
some previous conversations.
>
> Which repo has the latest content and which one is used in build ?
Most recent version is https://github.com/jpeterka/jbosstools-vwatch 
with just some minor updates and jobs are still using QE location AFAIK 
until it's decided about final public destination.

-- Jirka
>
>
>> where are we with this ?
>>
>> I see no conclusion and now wondering which repo is the master ?
>>
>> /max
>>
>>> Hi Nick,
>>>
>>> some time ago there was a request to put VersionWatch outside QE 
>>> repo. So I've created a new repo under my account with it:
>>>
>>> https://github.com/jpeterka/jbosstools-vwatch
>>>
>>> If you find it desirable feel free to clone it among other 
>>> jbosstools repositories.
>>>
>>> Thanks,
>>>
>>> Jirka
>>>
>>> -- 
>>> Jiri Peterka
>>> JBoss Developer Studio QE
>>> Red Hat Czech s.r.o., Purkynova 99, 612 45 Brno, Czech Republic
>>> IRC: jpeterka #jboss-qa, #devstudio-qa
>>> email: jpeterka at redhat.com
>>
>>
>> /max
>> http://about.me/maxandersen
>
>
> /max
> http://about.me/maxandersen

-- 
Jiri Peterka
JBoss Developer Studio QE
Red Hat Czech s.r.o., Purkynova 99, 612 45 Brno, Czech Republic
IRC: jpeterka #jboss-qa, #devstudio-qa
email: jpeterka at redhat.com


From max.andersen at redhat.com  Wed Apr  8 14:33:27 2015
From: max.andersen at redhat.com (Max Rydahl Andersen)
Date: Wed, 08 Apr 2015 20:33:27 +0200
Subject: [jbosstools-dev] VersionWatch repo
In-Reply-To: <5525328D.6040506@redhat.com>
References: <54D38435.6080005@redhat.com>
	<FF830091-6A1B-4C4C-A669-77217B4D1D2C@redhat.com>
	<201383C4-87A6-4B9F-BB12-EF0F301E6056@redhat.com>
	<5525328D.6040506@redhat.com>
Message-ID: <C1937277-C81D-41CA-A896-914A001F5601@redhat.com>

On 8 Apr 2015, at 15:52, Jiri Peterka wrote:

> Max,
>
> On 04/08/2015 03:05 PM, Max Rydahl Andersen wrote:
>> Did not notice this was not on mailing list.
>>
>> Jiri - what is the status of this ?
> There was no update for a while, see tracking JIRA - 
> https://issues.jboss.org/browse/JBIDE-19190 . I've forwarded to you 
> also some previous conversations.

jira was set to fix version 4.3.x = I'm not looking at those.

Majority of the tasks in there is not for me so i've assigned it to you 
and I suggest we go with having
this in its own repo since its supposed to be standalone anyway.

>> Which repo has the latest content and which one is used in build ?
> Most recent version is https://github.com/jpeterka/jbosstools-vwatch 
> with just some minor updates and jobs are still using QE location 
> AFAIK until it's decided about final public destination.

okey so lets get that fixed. Back to you in JBIDE-19190. Ok ?
/max

> -- Jirka
>>
>>
>>> where are we with this ?
>>>
>>> I see no conclusion and now wondering which repo is the master ?
>>>
>>> /max
>>>
>>>> Hi Nick,
>>>>
>>>> some time ago there was a request to put VersionWatch outside QE 
>>>> repo. So I've created a new repo under my account with it:
>>>>
>>>> https://github.com/jpeterka/jbosstools-vwatch
>>>>
>>>> If you find it desirable feel free to clone it among other 
>>>> jbosstools repositories.
>>>>
>>>> Thanks,
>>>>
>>>> Jirka
>>>>
>>>> -- 
>>>> Jiri Peterka
>>>> JBoss Developer Studio QE
>>>> Red Hat Czech s.r.o., Purkynova 99, 612 45 Brno, Czech Republic
>>>> IRC: jpeterka #jboss-qa, #devstudio-qa
>>>> email: jpeterka at redhat.com
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>
>>
>> /max
>> http://about.me/maxandersen
>
> -- 
> Jiri Peterka
> JBoss Developer Studio QE
> Red Hat Czech s.r.o., Purkynova 99, 612 45 Brno, Czech Republic
> IRC: jpeterka #jboss-qa, #devstudio-qa
> email: jpeterka at redhat.com


/max
http://about.me/maxandersen

From manderse at redhat.com  Thu Apr  9 01:41:22 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 09 Apr 2015 07:41:22 +0200
Subject: [jbosstools-dev] [epp-dev] Heads Up and some action requested :
 TCF Terminals Moving to TM
In-Reply-To: <42A2F428-5B40-46D1-BBDC-2AD7D98BBD32@redhat.com>
References: <146B1557584B0B4DBD25ABAD45EF70F0DBC23773@ALA-MBA.corp.ad.wrs.com>
	<42A2F428-5B40-46D1-BBDC-2AD7D98BBD32@redhat.com>
Message-ID: <E0D4FD6F-C8A5-4709-88AE-96776670E5CB@redhat.com>


Rob/Lars - have you had time to look at this and how much if anything it 
affects us ?

/max

> Hey,
>
> I believe this will end up affecting us too.
>
> Opened jira for this: https://issues.jboss.org/browse/JBDS-3384
>
> For most this is just a repackaging that don't affect code, but for 
> Fuse
> Tooling
> which currently rely on org.eclipse.tm.internal.terminal this will
> require changes.
>
>
> /max
> http://about.me/maxandersen
> Forwarded message:
>
>> From: Oberhuber, Martin <Martin.Oberhuber at windriver.com>
>> To: Eclipse Packaging Project <epp-dev at eclipse.org>
>> Subject: Re: [epp-dev] Heads Up and some action requested : TCF
>> Terminals Moving	to TM
>> Date: Thu, 19 Mar 2015 15:54:07 +0000
>>
>> Hi Package Maintainers,
>>
>> We have been convinced that contributing from TCF under a foreign
>> namespace is not a good idea.
>> On the other hand, the deprecated legacy terminal view has already
>> been removed from the simrel:
>> http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=d677d5a6ae094bb2d1a7136be9d5b1d84c62740d
>>
>> This means there is now some action strongly suggested, or packages
>> might fail to build or build against outdated (M5) terminal
>> contributions:
>>
>> -          jee : Remove legacy terminal.view , optionally add the new
>> tcf.terminals.view - Bug
>> 462087<https://bugs.eclipse.org/bugs/show_bug.cgi?id=462087>
>>
>> -          reporting : Remove legacy terminal.view , optionally add
>> the new tcf.terminals.view - Bug
>> 462089<https://bugs.eclipse.org/bugs/show_bug.cgi?id=462089>
>>
>> -          parallel : Optionally add
>> org.eclipse.tcf.te.terminals.feature AND
>> org.eclipse.tcf.te.terminals.rse.feature
>>
>> -          cpp : Optionally add org.eclipse.tcf.te.terminals.feature
>> AND org.eclipse.tcf.te.terminals.rse.feature
>>
>> For the must-have changes in jee and reporting, we have created bugs
>> and Gerrit changesets.
>> Since I am an epp committer, I think I could apply these for you, but
>> I would like the package maintainer's OK before I do that.
>>
>> I would strongly recommend also applying the optional changes (adding
>> the TCF Terminals View) such that users can see the new view and
>> provide feedback.
>> Without doing this, the Terminal view would be GONE in the respective
>> packages in M6 and only reappear in M7 once the move has been
>> completed.
>> I can also apply these changes for you if I get your OK.
>>
>> Please let me know how you want to proceed, and if there's any
>> questions/concerns !
>>
>> Thanks,
>> Martin
>> --
>> Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind 
>> River
>> direct +43.662.457915.85  fax +43.662.457915.6
>>
>> From: epp-dev-bounces at eclipse.org 
>> [mailto:epp-dev-bounces at eclipse.org]
>> On Behalf Of Oberhuber, Martin
>> Sent: Monday, March 16, 2015 6:17 PM
>> To: EPP Developer Mailing List (epp-dev at eclipse.org)
>> Subject: [epp-dev] Heads Up and some action requested : TCF Terminals
>> Moving to TM
>>
>> Hi Package Maintainers,
>>
>> You might be aware that based on the original TM Terminal view, the
>> TCF Project has come up with a much enhanced terminal:
>> https://marketplace.eclipse.org/content/tcf-terminals
>>
>> In order to simplify code adoption and contributions, we want to
>> restructure the codebase and re-unite it with the original TM
>> codebase.
>> The result will be called "TM Terminal 4.0" but will contain the
>> related TM _and_ TCF code in a single, small git repository.
>> Here is the respective restructuring review:
>> https://projects.eclipse.org/projects/tools.cdt.tcf/reviews/move-tcf-terminals-code-tm-project
>>
>> Now unfortunately the review is scheduled to complete by April 1 
>> which
>> is after M6, but we would like to give adopters
>> a preview of the new Terminal with M6 in order to get more feedback.
>> Thus here's what we are planning:
>>
>> -          The TM project will no longer contribute its
>> org.eclipse.tm.terminal.* to the simrel
>>
>> -          Instead, the TCF project will contribute
>> org.eclpse.tm.terminal.*_4.0 to the simrel (already using the *new*
>> namespace).
>>
>> This affects the "jee" and "reporting" packages which currently
>> directly use those features:
>>
>> org.eclipse.epp.packages/packages>grep org.eclipse.tm.terminal
>> */feature.xml
>> org.eclipse.epp.package.jee.feature/feature.xml:      <import
>> feature="org.eclipse.tm.terminal"/>
>> org.eclipse.epp.package.jee.feature/feature.xml:      <import
>> feature="org.eclipse.tm.terminal.ssh"/>
>> org.eclipse.epp.package.jee.feature/feature.xml:      <import
>> feature="org.eclipse.tm.terminal.telnet"/>
>> org.eclipse.epp.package.jee.feature/feature.xml:      <import
>> feature="org.eclipse.tm.terminal.view"/>
>> org.eclipse.epp.package.reporting.feature/feature.xml:      <import
>> feature="org.eclipse.tm.terminal"/>
>> org.eclipse.epp.package.reporting.feature/feature.xml:      <import
>> feature="org.eclipse.tm.terminal.ssh"/>
>> org.eclipse.epp.package.reporting.feature/feature.xml:      <import
>> feature="org.eclipse.tm.terminal.telnet"/>
>> org.eclipse.epp.package.reporting.feature/feature.xml:      <import
>> feature="org.eclipse.tm.terminal.view"/>
>>
>> If you do not take any action, you will simply see the new "4.0"
>> version of those features from TCF, giving you the new tabbed 
>> terminal
>> view.
>> If you want, you can take the following two actions as soon as TCF
>> starts contributing the new namespace:
>>
>> -          You may REMOVE "org.eclipse.tm.terminal" since that 
>> feature
>> is auto-required by "org.eclipse.tm.terminal.view" ; that would allow
>> updating the widget without updating the view in the future.
>>
>> -          You may ADD "org.eclipse.tm.terminal.local" since that
>> feature gives you the new local terminal (console) prompt
>>
>> -          You may want to set the minimum version range to 4.0 to
>> ensure you get the new features
>>
>> -          You may want to review the terminal whether it fits your
>> needs and provide feedback.
>>
>> Of course other packages are more than welcome to also consume the 
>> new
>> Terminal - all relevant docs are in the marketplace entry cited 
>> above.
>>
>> For now this is just a heads up;
>> We are planning to add the new "TM Namespace" features to the TCF
>> simrel contribution over the course of the week.
>> I will send another notification once the new features are available.
>>
>> Please let me know of any concerns or questions !
>> Or comment directly on the Move Review if you want.
>>
>>
>> Thanks,
>> Martin
>> --
>> Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind 
>> River
>> direct +43.662.457915.85  fax +43.662.457915.6
>>
>> _______________________________________________
>> epp-dev mailing list
>> epp-dev at eclipse.org
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/epp-dev
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From rstryker at redhat.com  Thu Apr  9 22:39:20 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Thu, 09 Apr 2015 22:39:20 -0400
Subject: [jbosstools-dev] Question on data virtualization runtimes and where
 downloadRuntime support belongs
Message-ID: <552737D8.8000708@redhat.com>

Hey all:

So, astools has historically housed almost all the download-runtime code 
for various jboss runtimes. This changed a bit, however, when karaf / 
fuse / serviceworks came on the scene.  The FuseIDE code now provides a 
home for their server bean loaders (things that accurately identify 
local installs), their runtime detectors (to work with turning those 
installs into IRuntime objects in eclipse), and their download runtimes 
(to know where to fetch them / download them / install them).

Where does Data Virtualization / teiid fit in for this?  I'm not very 
familiar with what teiid adds on to our server types. It seems they 
don't add their own server types, so that would suggest I should put 
their runtime detection code in with astools. However, if they require 
any special / teiid-only property keys to be set when creating the 
server, that would indicate they should handle the import and not me, 
since I won't have access to their custom keys. This is important for 
runtime detection, as I don't want to return a half-complete runtime / 
server with missing flags that's unusable for teiid.

So the question is:  where should the code for recognizing local DV 
installs, downloading DV runtimes, etc, live?  ASTools, or Teiid?

- Rob Stryker

From rstryker at redhat.com  Fri Apr 10 03:22:30 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Fri, 10 Apr 2015 03:22:30 -0400
Subject: [jbosstools-dev] [epp-dev] Heads Up and some action requested :
 TCF Terminals Moving to TM
In-Reply-To: <E0D4FD6F-C8A5-4709-88AE-96776670E5CB@redhat.com>
References: <146B1557584B0B4DBD25ABAD45EF70F0DBC23773@ALA-MBA.corp.ad.wrs.com>	<42A2F428-5B40-46D1-BBDC-2AD7D98BBD32@redhat.com>
	<E0D4FD6F-C8A5-4709-88AE-96776670E5CB@redhat.com>
Message-ID: <55277A36.60900@redhat.com>

I've already verified that it should not affect ASTools at all really 
since ASTools uses a simple messageconsole to display our remote launch 
sysouts.

I have not had time to investigate this as it pertains to Fuse, but I've 
been convinced for several months already that Fuse needs to simply 
trash what they have for terminal support and write a new solution from 
scratch.


On 04/09/2015 01:41 AM, Max Rydahl Andersen wrote:
> Rob/Lars - have you had time to look at this and how much if anything it
> affects us ?
>
> /max
>
>> Hey,
>>
>> I believe this will end up affecting us too.
>>
>> Opened jira for this: https://issues.jboss.org/browse/JBDS-3384
>>
>> For most this is just a repackaging that don't affect code, but for
>> Fuse
>> Tooling
>> which currently rely on org.eclipse.tm.internal.terminal this will
>> require changes.
>>
>>
>> /max
>> http://about.me/maxandersen
>> Forwarded message:
>>
>>> From: Oberhuber, Martin <Martin.Oberhuber at windriver.com>
>>> To: Eclipse Packaging Project <epp-dev at eclipse.org>
>>> Subject: Re: [epp-dev] Heads Up and some action requested : TCF
>>> Terminals Moving	to TM
>>> Date: Thu, 19 Mar 2015 15:54:07 +0000
>>>
>>> Hi Package Maintainers,
>>>
>>> We have been convinced that contributing from TCF under a foreign
>>> namespace is not a good idea.
>>> On the other hand, the deprecated legacy terminal view has already
>>> been removed from the simrel:
>>> http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=d677d5a6ae094bb2d1a7136be9d5b1d84c62740d
>>>
>>> This means there is now some action strongly suggested, or packages
>>> might fail to build or build against outdated (M5) terminal
>>> contributions:
>>>
>>> -          jee : Remove legacy terminal.view , optionally add the new
>>> tcf.terminals.view - Bug
>>> 462087<https://bugs.eclipse.org/bugs/show_bug.cgi?id=462087>
>>>
>>> -          reporting : Remove legacy terminal.view , optionally add
>>> the new tcf.terminals.view - Bug
>>> 462089<https://bugs.eclipse.org/bugs/show_bug.cgi?id=462089>
>>>
>>> -          parallel : Optionally add
>>> org.eclipse.tcf.te.terminals.feature AND
>>> org.eclipse.tcf.te.terminals.rse.feature
>>>
>>> -          cpp : Optionally add org.eclipse.tcf.te.terminals.feature
>>> AND org.eclipse.tcf.te.terminals.rse.feature
>>>
>>> For the must-have changes in jee and reporting, we have created bugs
>>> and Gerrit changesets.
>>> Since I am an epp committer, I think I could apply these for you, but
>>> I would like the package maintainer's OK before I do that.
>>>
>>> I would strongly recommend also applying the optional changes (adding
>>> the TCF Terminals View) such that users can see the new view and
>>> provide feedback.
>>> Without doing this, the Terminal view would be GONE in the respective
>>> packages in M6 and only reappear in M7 once the move has been
>>> completed.
>>> I can also apply these changes for you if I get your OK.
>>>
>>> Please let me know how you want to proceed, and if there's any
>>> questions/concerns !
>>>
>>> Thanks,
>>> Martin
>>> --
>>> Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind
>>> River
>>> direct +43.662.457915.85  fax +43.662.457915.6
>>>
>>> From: epp-dev-bounces at eclipse.org
>>> [mailto:epp-dev-bounces at eclipse.org]
>>> On Behalf Of Oberhuber, Martin
>>> Sent: Monday, March 16, 2015 6:17 PM
>>> To: EPP Developer Mailing List (epp-dev at eclipse.org)
>>> Subject: [epp-dev] Heads Up and some action requested : TCF Terminals
>>> Moving to TM
>>>
>>> Hi Package Maintainers,
>>>
>>> You might be aware that based on the original TM Terminal view, the
>>> TCF Project has come up with a much enhanced terminal:
>>> https://marketplace.eclipse.org/content/tcf-terminals
>>>
>>> In order to simplify code adoption and contributions, we want to
>>> restructure the codebase and re-unite it with the original TM
>>> codebase.
>>> The result will be called "TM Terminal 4.0" but will contain the
>>> related TM _and_ TCF code in a single, small git repository.
>>> Here is the respective restructuring review:
>>> https://projects.eclipse.org/projects/tools.cdt.tcf/reviews/move-tcf-terminals-code-tm-project
>>>
>>> Now unfortunately the review is scheduled to complete by April 1
>>> which
>>> is after M6, but we would like to give adopters
>>> a preview of the new Terminal with M6 in order to get more feedback.
>>> Thus here's what we are planning:
>>>
>>> -          The TM project will no longer contribute its
>>> org.eclipse.tm.terminal.* to the simrel
>>>
>>> -          Instead, the TCF project will contribute
>>> org.eclpse.tm.terminal.*_4.0 to the simrel (already using the *new*
>>> namespace).
>>>
>>> This affects the "jee" and "reporting" packages which currently
>>> directly use those features:
>>>
>>> org.eclipse.epp.packages/packages>grep org.eclipse.tm.terminal
>>> */feature.xml
>>> org.eclipse.epp.package.jee.feature/feature.xml:      <import
>>> feature="org.eclipse.tm.terminal"/>
>>> org.eclipse.epp.package.jee.feature/feature.xml:      <import
>>> feature="org.eclipse.tm.terminal.ssh"/>
>>> org.eclipse.epp.package.jee.feature/feature.xml:      <import
>>> feature="org.eclipse.tm.terminal.telnet"/>
>>> org.eclipse.epp.package.jee.feature/feature.xml:      <import
>>> feature="org.eclipse.tm.terminal.view"/>
>>> org.eclipse.epp.package.reporting.feature/feature.xml:      <import
>>> feature="org.eclipse.tm.terminal"/>
>>> org.eclipse.epp.package.reporting.feature/feature.xml:      <import
>>> feature="org.eclipse.tm.terminal.ssh"/>
>>> org.eclipse.epp.package.reporting.feature/feature.xml:      <import
>>> feature="org.eclipse.tm.terminal.telnet"/>
>>> org.eclipse.epp.package.reporting.feature/feature.xml:      <import
>>> feature="org.eclipse.tm.terminal.view"/>
>>>
>>> If you do not take any action, you will simply see the new "4.0"
>>> version of those features from TCF, giving you the new tabbed
>>> terminal
>>> view.
>>> If you want, you can take the following two actions as soon as TCF
>>> starts contributing the new namespace:
>>>
>>> -          You may REMOVE "org.eclipse.tm.terminal" since that
>>> feature
>>> is auto-required by "org.eclipse.tm.terminal.view" ; that would allow
>>> updating the widget without updating the view in the future.
>>>
>>> -          You may ADD "org.eclipse.tm.terminal.local" since that
>>> feature gives you the new local terminal (console) prompt
>>>
>>> -          You may want to set the minimum version range to 4.0 to
>>> ensure you get the new features
>>>
>>> -          You may want to review the terminal whether it fits your
>>> needs and provide feedback.
>>>
>>> Of course other packages are more than welcome to also consume the
>>> new
>>> Terminal - all relevant docs are in the marketplace entry cited
>>> above.
>>>
>>> For now this is just a heads up;
>>> We are planning to add the new "TM Namespace" features to the TCF
>>> simrel contribution over the course of the week.
>>> I will send another notification once the new features are available.
>>>
>>> Please let me know of any concerns or questions !
>>> Or comment directly on the Move Review if you want.
>>>
>>>
>>> Thanks,
>>> Martin
>>> --
>>> Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind
>>> River
>>> direct +43.662.457915.85  fax +43.662.457915.6
>>>
>>> _______________________________________________
>>> epp-dev mailing list
>>> epp-dev at eclipse.org
>>> To change your delivery options, retrieve your password, or
>>> unsubscribe from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/epp-dev
>> _______________________________________________
>> 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  Fri Apr 10 03:53:19 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 10 Apr 2015 09:53:19 +0200
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <552737D8.8000708@redhat.com>
References: <552737D8.8000708@redhat.com>
Message-ID: <E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>


To summarize (and cc Barry since he is the one doing teiid tooling)

> So the question is:  where should the code for recognizing local DV
> installs, downloading DV runtimes, etc, live?  ASTools, or Teiid?

I do not see any reason to why ASTools should handle download of Teiid. 
Shouldn't Teiid just do this using
the api we provide like done for the others ?

I assume this is all in context of 
https://jira.jboss.org/jira/browse/JBIDE-19574  ?

With respect for runtime detection I guess that is a completely separate 
story.

Is teiid a separate server like SOA-P/FSW or is Teiid something that is 
installed into an existing EAP based server ?

Does teiid even need "special" recognition handling ?
how does teiid today figure out wether an EAP server needs to show Teiid 
features in the server view ?


/max
http://about.me/maxandersen

From p.g.richardson at phantomjinx.co.uk  Fri Apr 10 04:33:22 2015
From: p.g.richardson at phantomjinx.co.uk (phantomjinx)
Date: Fri, 10 Apr 2015 09:33:22 +0100
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>
References: <552737D8.8000708@redhat.com>
	<E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>
Message-ID: <55278AD2.2000101@phantomjinx.co.uk>

Rob, Max,

See inline ...

On 10/04/15 08:53, Max Rydahl Andersen wrote:
> To summarize (and cc Barry since he is the one doing teiid tooling)
>
>> So the question is:  where should the code for recognizing local DV
>> installs, downloading DV runtimes, etc, live?  ASTools, or Teiid?
> I do not see any reason to why ASTools should handle download of Teiid. 
> Shouldn't Teiid just do this using
> the api we provide like done for the others ?

I would strongly support Teiid doing it itself. At the moment, the teiid-runtime is carried by the
Teiid Designer plugins and is designed to be backward compatible over Teiid versions and to some
extent across jboss versions (7/8). Thus, install Teiid Designer and you get support for whatever
Teiid version has been installed on your jboss server.

> I assume this is all in context of 
> https://jira.jboss.org/jira/browse/JBIDE-19574  ?
>
> With respect for runtime detection I guess that is a completely separate 
> story.
>
> Is teiid a separate server like SOA-P/FSW or is Teiid something that is 
> installed into an existing EAP based server ?

Yes, Teiid is a module installed on top of an existing EAP server that provides its own API for
deployment of artifacts, using the jb admin port, JDBC querying of modelled db connections using its
own port (31000) and installs its own susbsytems for translators, data sources etc.

> Does teiid even need "special" recognition handling ?
> how does teiid today figure out wether an EAP server needs to show Teiid 
> features in the server view ?
The Teiid Designer plugins take care of this by querying the EAP server for the relevent subsystems
that Teiid would be installed to. It also finds the version of Teiid installed and provides this
back to the modelling environment as the modelling version (determines parsing/resolving/validating
of SQL queries for example). The UI for Teiid in the Server View is tacked onto the existing View
using one of the extension points already available.

Essentially, this means if you want to model/deploy a Virtual Database (VDB) to Teiid using Eclipse
then install the Teiid Designer plugins and you get all the extra pieces required.

Hope this helps.

PGR

-- 

Paul Richardson

  * p.g.richardson at phantomjinx.co.uk
  * p.g.richardson at redhat.com
  * pgrichardson at linux.com

"I know exactly who reads the papers ...

  * The Daily Mirror is read by people who think they run the country.
  * The Guardian is read by people who think they ought to run the country.
  * The Times is read by people who do actually run the country.
  * The Daily Mail is read by the wives of the people who run the country.
  * The Financial Times is read by the people who own the country.
  * The Morning Star is read by the people who think the country ought to be run by another country.
  * The Daily Telegraph is read by the people who think it is."

Jim Hacker, Yes Minister


From rstryker at redhat.com  Fri Apr 10 12:52:56 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Fri, 10 Apr 2015 12:52:56 -0400
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <55278AD2.2000101@phantomjinx.co.uk>
References: <552737D8.8000708@redhat.com>
	<E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>
	<55278AD2.2000101@phantomjinx.co.uk>
Message-ID: <5527FFE8.9050306@redhat.com>

On 04/10/2015 04:33 AM, phantomjinx wrote:
>> >https://jira.jboss.org/jira/browse/JBIDE-19574   ?
>> >
>> >With respect for runtime detection I guess that is a completely separate
>> >story.
>> >
>> >Is teiid a separate server like SOA-P/FSW or is Teiid something that is
>> >installed into an existing EAP based server ?
> Yes, Teiid is a module installed on top of an existing EAP server that provides its own API for
> deployment of artifacts, using the jb admin port, JDBC querying of modelled db connections using its
> own port (31000) and installs its own susbsytems for translators, data sources etc.
>

Teiid itself is something that's installed on top of an EAP server. The 
"Data Virtualization" product, however, comes only in an installer form; 
no simple unzip. So at least in terms of downloading the runtime, DV 
requires special treatment, not just an unzip. (If there's a simple 
unzip available, I haven't seen it on download manager; I've only seen 
the installer there).

However you can also download "Teiid + EAP" which *does* respond to a 
simple unzip.  See, for example, 
https://sourceforge.net/projects/teiid/files/teiid-8.10.0.Final-server.zip/download

So while the project seems to allow a simple unzip, the product does not.

I'm honestly OK with both code living in either place, but  it's more a 
concern of duplication of effort / code. If I have ASTools performing 
the runtime detection, there's a few risks:

    1) I may not personally stay bleeding-edge up-to-date on teiid / dv 
structural changes, what subsystems to use for detection, etc etc, and 
will require help from teiid at keeping my detection accurate

    2) If ASTools is in charge of detecting, Teiid Designer (who I 
assume goes GA several months later) may find themselves limited. For 
example if a new Teiid Runtime / DV release comes out in the interval 
between our GA and Teiid's GA. Teiid Designer will either need to 
consume only what detection we provided, or, work around it by adding 
detection support for newer runtimes in their own code. Then we have 
duplication, and it becomes a split responsibility with code all over 
the place. Could get messy.

I personally think it makes more sense for the detection and download 
logic to both live in Teiid Designer codebase, based primarily on these 
two risks. I'm aware that it limits the usefulness of ASTools standalone 
for users wanting to use DV / Teiid Runtime, but I also think we should 
be pushing people using teiid / DV to also use Teiid Designer anyway.

I'll be glad to do the bulk of the work regardless where it 'lives', of 
course, but I just wanted to get some consensus on where the code SHOULD 
live first.



- Rob Stryker

From p.g.richardson at phantomjinx.co.uk  Fri Apr 10 13:22:59 2015
From: p.g.richardson at phantomjinx.co.uk (phantomjinx)
Date: Fri, 10 Apr 2015 18:22:59 +0100
Subject: [jbosstools-dev] Question on data virtualization runtimes and
	where downloadRuntime support belongs
In-Reply-To: <5527FFE8.9050306@redhat.com>
References: <552737D8.8000708@redhat.com>
	<E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>
	<55278AD2.2000101@phantomjinx.co.uk> <5527FFE8.9050306@redhat.com>
Message-ID: <F30FD363-092D-469C-AA3B-798BA7C5647E@phantomjinx.co.uk>

On 10 April 2015 17:52:56 GMT+01:00, Rob Stryker <rstryker at redhat.com> wrote:
>On 04/10/2015 04:33 AM, phantomjinx wrote:
>>> >https://jira.jboss.org/jira/browse/JBIDE-19574   ?
>>> >
>>> >With respect for runtime detection I guess that is a completely
>separate
>>> >story.
>>> >
>>> >Is teiid a separate server like SOA-P/FSW or is Teiid something
>that is
>>> >installed into an existing EAP based server ?
>> Yes, Teiid is a module installed on top of an existing EAP server
>that provides its own API for
>> deployment of artifacts, using the jb admin port, JDBC querying of
>modelled db connections using its
>> own port (31000) and installs its own susbsytems for translators,
>data sources etc.
>>
>
>Teiid itself is something that's installed on top of an EAP server. The
>
>"Data Virtualization" product, however, comes only in an installer
>form; 
>no simple unzip. So at least in terms of downloading the runtime, DV 
>requires special treatment, not just an unzip. (If there's a simple 
>unzip available, I haven't seen it on download manager; I've only seen 
>the installer there).
>
>However you can also download "Teiid + EAP" which *does* respond to a 
>simple unzip.  See, for example, 
>https://sourceforge.net/projects/teiid/files/teiid-8.10.0.Final-server.zip/download
>
>So while the project seems to allow a simple unzip, the product does
>not.
>
>I'm honestly OK with both code living in either place, but  it's more a
>
>concern of duplication of effort / code. If I have ASTools performing 
>the runtime detection, there's a few risks:
>
>   1) I may not personally stay bleeding-edge up-to-date on teiid / dv 
>structural changes, what subsystems to use for detection, etc etc, and 
>will require help from teiid at keeping my detection accurate
>
>    2) If ASTools is in charge of detecting, Teiid Designer (who I 
>assume goes GA several months later) may find themselves limited. For 
>example if a new Teiid Runtime / DV release comes out in the interval 
>between our GA and Teiid's GA. Teiid Designer will either need to 
>consume only what detection we provided, or, work around it by adding 
>detection support for newer runtimes in their own code. Then we have 
>duplication, and it becomes a split responsibility with code all over 
>the place. Could get messy.
>
>I personally think it makes more sense for the detection and download 
>logic to both live in Teiid Designer codebase, based primarily on these
>
>two risks. I'm aware that it limits the usefulness of ASTools
>standalone 
>for users wanting to use DV / Teiid Runtime, but I also think we should
>
>be pushing people using teiid / DV to also use Teiid Designer anyway.
>
>I'll be glad to do the bulk of the work regardless where it 'lives', of
>
>course, but I just wanted to get some consensus on where the code
>SHOULD 
>live first.
>
>
>
>- Rob Stryker

Little perplexed as to what code you want to "put" in Astools or Designer. As I said, the latter already detects the installed version of teiid.

As to DV v Teiid. The product of DV is EAP+Teiid wrapped up in a single installer. The layout ends up slightly different with the product having a dedicated DV directory containing the teiid modules but the result is the same.

PGR
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150410/99d011b0/attachment.html 

From rstryker at redhat.com  Fri Apr 10 15:13:51 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Fri, 10 Apr 2015 15:13:51 -0400
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <F30FD363-092D-469C-AA3B-798BA7C5647E@phantomjinx.co.uk>
References: <552737D8.8000708@redhat.com>
	<E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>
	<55278AD2.2000101@phantomjinx.co.uk> <5527FFE8.9050306@redhat.com>
	<F30FD363-092D-469C-AA3B-798BA7C5647E@phantomjinx.co.uk>
Message-ID: <552820EF.5060502@redhat.com>

After some discussion with PGR, we think it makes more sense for the 
detection to live in the Teiid Designer repository.

Teiid Designer currently only has code for detecting teiid in *running* 
servers, with no support for identifying a Teiid installation in servers 
that aren't running.  This makes sense for their use case (server may be 
remote) but is not useful for runtime detection at all.

TD currently is not involved in the server creation at all, but rather 
just adds listeners so that once a server is added, or started, they can 
begin their configuration / build up their model. They also provide 
editor extensions that allow setting fields on the IServerWorkingCopy.

*Barry*:   One thing that would help tremendously with identifying 
installations in non-running local servers is if I could have a map of 
Teiid / DV releases and what underlying JBoss / Wildfly / EAP versions 
they correspond to. What I've heard so far is that Teiid 7.x was based 
on JBoss 5, while the 8.x stream is for AS7.  It's pretty important to 
get a full mapping of supported releases to their underlying JBoss 
version, though. This way I can properly implement the Server Bean 
Loaders / Runtime detection.

One final thing to note, which I think we should bring up to the Teiid 
runtime team directly, is that DV product properly uses the layer system 
in JBoss 7.  It has the expected 
org/jboss/as/product/dv/dir/META-INF/MANIFEST.MF file,  with the 
expected attribute JBoss-Product-Release-Version: 6.1.0...

But the community releases of Teiid *do not*.  They simply put 
everything in modules/system/layers/base, with no clear way of 
identifying a version. If I wanted to look at the version here, I'd need 
to introspect 
teiid-8.10.0.Final/modules/system/layers/base/org/jboss/teiid/api/main/teiid-api-8.10.0.Final.jar 
and look at it's manifest.mf for the Bundle-Version,  which so far seems 
accurate.

With all this in mind, it should be relatively painless (once I get that 
version mapping from Barry) to get runtime detection + downloading 
supported for Teiid Runtime / DV.   There may be some issues in 
stacks.yaml  (since I'm not too familiar with all the bom stuff) but I 
expect the version mapping will help me to properly pull from other 
parts of stacks.yaml without issue.

- Rob Stryker

- Rob Stryker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150410/41a2553e/attachment-0001.html 

From manderse at redhat.com  Mon Apr 13 06:45:48 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 13 Apr 2015 12:45:48 +0200
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <552820EF.5060502@redhat.com>
References: <552737D8.8000708@redhat.com>
	<E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>
	<55278AD2.2000101@phantomjinx.co.uk> <5527FFE8.9050306@redhat.com>
	<F30FD363-092D-469C-AA3B-798BA7C5647E@phantomjinx.co.uk>
	<552820EF.5060502@redhat.com>
Message-ID: <6A98A8DB-3CB5-4079-926B-9C03AF3342ED@redhat.com>

I'm still not following/seeing why Teiid Designer needs runtime 
detection if it detects it at runtime ?

/max

> After some discussion with PGR, we think it makes more sense for the 
> detection to live in the Teiid Designer repository.
>
> Teiid Designer currently only has code for detecting teiid in 
> *running* servers, with no support for identifying a Teiid 
> installation in servers that aren't running.  This makes sense for 
> their use case (server may be remote) but is not useful for runtime 
> detection at all.
>
> TD currently is not involved in the server creation at all, but rather 
> just adds listeners so that once a server is added, or started, they 
> can begin their configuration / build up their model. They also 
> provide editor extensions that allow setting fields on the 
> IServerWorkingCopy.
>
> *Barry*:   One thing that would help tremendously with identifying 
> installations in non-running local servers is if I could have a map of 
> Teiid / DV releases and what underlying JBoss / Wildfly / EAP versions 
> they correspond to. What I've heard so far is that Teiid 7.x was based 
> on JBoss 5, while the 8.x stream is for AS7.  It's pretty important to 
> get a full mapping of supported releases to their underlying JBoss 
> version, though. This way I can properly implement the Server Bean 
> Loaders / Runtime detection.
>
> One final thing to note, which I think we should bring up to the Teiid 
> runtime team directly, is that DV product properly uses the layer 
> system in JBoss 7.  It has the expected 
> org/jboss/as/product/dv/dir/META-INF/MANIFEST.MF file,  with the 
> expected attribute JBoss-Product-Release-Version: 6.1.0...
>
> But the community releases of Teiid *do not*.  They simply put 
> everything in modules/system/layers/base, with no clear way of 
> identifying a version. If I wanted to look at the version here, I'd 
> need to introspect 
> teiid-8.10.0.Final/modules/system/layers/base/org/jboss/teiid/api/main/teiid-api-8.10.0.Final.jar 
> and look at it's manifest.mf for the Bundle-Version,  which so far 
> seems accurate.
>
> With all this in mind, it should be relatively painless (once I get 
> that version mapping from Barry) to get runtime detection + 
> downloading supported for Teiid Runtime / DV.   There may be some 
> issues in stacks.yaml  (since I'm not too familiar with all the bom 
> stuff) but I expect the version mapping will help me to properly pull 
> from other parts of stacks.yaml without issue.
>
> - Rob Stryker
>
> - Rob Stryker


/max
http://about.me/maxandersen


From rstryker at redhat.com  Mon Apr 13 13:21:05 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Mon, 13 Apr 2015 13:21:05 -0400
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <6A98A8DB-3CB5-4079-926B-9C03AF3342ED@redhat.com>
References: <552737D8.8000708@redhat.com>
	<E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>
	<55278AD2.2000101@phantomjinx.co.uk> <5527FFE8.9050306@redhat.com>
	<F30FD363-092D-469C-AA3B-798BA7C5647E@phantomjinx.co.uk>
	<552820EF.5060502@redhat.com>
	<6A98A8DB-3CB5-4079-926B-9C03AF3342ED@redhat.com>
Message-ID: <552BFB01.2040700@redhat.com>



On 04/13/2015 06:45 AM, Max Rydahl Andersen wrote:
> I'm still not following/seeing why Teiid Designer needs runtime 
> detection if it detects it at runtime ?
>
> /max

Download Runtime consists of 2 parts:  1 downloading + installing, and 
2: making the server adapter (ie runtime detection).

Currently there are no server beans that can identify a DV / teiid 
installation. So the runtime would only be recognized as an "EAP-Based 
Product" by the code in ASTools, and it won't be given the most optimal 
name...  basically the same situation JPP was in before we added custom 
server beans for them. It's a small issue in some ways, but, it's better 
if all our APIs  (including server bean loader) ensure the most accurate 
results possible, and if it's possible for them to identify a DV / Teiid 
Runtime installation, it's better to do it than to not do it.


>
>> After some discussion with PGR, we think it makes more sense for the 
>> detection to live in the Teiid Designer repository.
>>
>> Teiid Designer currently only has code for detecting teiid in 
>> *running* servers, with no support for identifying a Teiid 
>> installation in servers that aren't running.  This makes sense for 
>> their use case (server may be remote) but is not useful for runtime 
>> detection at all.
>>
>> TD currently is not involved in the server creation at all, but 
>> rather just adds listeners so that once a server is added, or 
>> started, they can begin their configuration / build up their model. 
>> They also provide editor extensions that allow setting fields on the 
>> IServerWorkingCopy.
>>
>> *Barry*:   One thing that would help tremendously with identifying 
>> installations in non-running local servers is if I could have a map 
>> of Teiid / DV releases and what underlying JBoss / Wildfly / EAP 
>> versions they correspond to. What I've heard so far is that Teiid 7.x 
>> was based on JBoss 5, while the 8.x stream is for AS7.  It's pretty 
>> important to get a full mapping of supported releases to their 
>> underlying JBoss version, though. This way I can properly implement 
>> the Server Bean Loaders / Runtime detection.
>>
>> One final thing to note, which I think we should bring up to the 
>> Teiid runtime team directly, is that DV product properly uses the 
>> layer system in JBoss 7.  It has the expected 
>> org/jboss/as/product/dv/dir/META-INF/MANIFEST.MF file,  with the 
>> expected attribute JBoss-Product-Release-Version: 6.1.0...
>>
>> But the community releases of Teiid *do not*.  They simply put 
>> everything in modules/system/layers/base, with no clear way of 
>> identifying a version. If I wanted to look at the version here, I'd 
>> need to introspect 
>> teiid-8.10.0.Final/modules/system/layers/base/org/jboss/teiid/api/main/teiid-api-8.10.0.Final.jar 
>> and look at it's manifest.mf for the Bundle-Version,  which so far 
>> seems accurate.
>>
>> With all this in mind, it should be relatively painless (once I get 
>> that version mapping from Barry) to get runtime detection + 
>> downloading supported for Teiid Runtime / DV.   There may be some 
>> issues in stacks.yaml  (since I'm not too familiar with all the bom 
>> stuff) but I expect the version mapping will help me to properly pull 
>> from other parts of stacks.yaml without issue.
>>
>> - Rob Stryker
>>
>> - Rob Stryker
>
>
> /max
> http://about.me/maxandersen


From manderse at redhat.com  Tue Apr 14 03:49:01 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 14 Apr 2015 09:49:01 +0200
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <552BFB01.2040700@redhat.com>
References: <552737D8.8000708@redhat.com>
	<E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>
	<55278AD2.2000101@phantomjinx.co.uk> <5527FFE8.9050306@redhat.com>
	<F30FD363-092D-469C-AA3B-798BA7C5647E@phantomjinx.co.uk>
	<552820EF.5060502@redhat.com>
	<6A98A8DB-3CB5-4079-926B-9C03AF3342ED@redhat.com>
	<552BFB01.2040700@redhat.com>
Message-ID: <2FF35E18-6104-461D-9860-18293DC84217@redhat.com>

On 13 Apr 2015, at 19:21, Rob Stryker wrote:

> On 04/13/2015 06:45 AM, Max Rydahl Andersen wrote:
>> I'm still not following/seeing why Teiid Designer needs runtime 
>> detection if it detects it at runtime ?
>>
>> /max
>
> Download Runtime consists of 2 parts:  1 downloading + installing, and 
> 2: making the server adapter (ie runtime detection).
>
> Currently there are no server beans that can identify a DV / teiid 
> installation. So the runtime would only be recognized as an "EAP-Based 
> Product" by the code in ASTools, and it won't be given the most 
> optimal name...  basically the same situation JPP was in before we 
> added custom server beans for them. It's a small issue in some ways, 
> but, it's better if all our APIs  (including server bean loader) 
> ensure the most accurate results possible, and if it's possible for 
> them to identify a DV / Teiid Runtime installation, it's better to do 
> it than to not do it.

Ah, I forgot about the naming aspect. Sure this does make sense and 
definitely something that is better of in Teiid IMO.

/max
http://about.me/maxandersen

From manderse at redhat.com  Tue Apr 14 07:45:53 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 14 Apr 2015 13:45:53 +0200
Subject: [jbosstools-dev] JBoss Tools 4.3.0.Alpha2 code freeze this Thursday
	16th April
Message-ID: <6C338E88-3EE8-488D-A1F4-C53C3C70AEAE@redhat.com>

Heya,

Just a friendly reminder that Alpha2 code freeze is coming up on this 
Thursday the 16th [1]
if you are on Red Hat VPN you can access the ical for it at [2]. Planned 
release of this is for 27th April.

This Alpha2 is "Special" in the sense it is targeting Eclipse Mars M6 
which includes a lot of updates and fixes
to the platform including:

* OS X p2 layout has changed = OS X users cannot update from Mars M1-M5 
to M6, need to install.
* Jetty 8 to Jetty 9 (major api change)
* egit 3.x to 4.0
* GTK3 bug fixes (Snjezana Go Go!)
* ...and probably a lot more ;)

Big things hoping to show up in Alpha2 if you are not aware are:

* easyimport
* OpenShift v3 tooling (it did not make it to Alpha1)
* First working and pretty version of Central on HTML5
* <fill in your thing here for N&N >

[1] 
https://issues.jboss.org/browse/JBIDE/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel
[2] 
https://pp.engineering.redhat.com/pp-admin/api/v1/releases/524/schedule-tasks/?format=ics&flags__name=roadmap

Good luck and don't be afraid to ask if you find issues in M6.
There are still time to fix it upstream! :)

p.s. I'm not available this Friday - but Fred Bricon promised to fill in 
for me if any questions/concerns
around code freeze and readiness.

Thanks,
/max
http://about.me/maxandersen


From fbricon at redhat.com  Tue Apr 14 11:01:52 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Tue, 14 Apr 2015 11:01:52 -0400
Subject: [jbosstools-dev] JBoss Tools 4.3.0.Alpha2 code freeze this
	Thursday 16th April
In-Reply-To: <6C338E88-3EE8-488D-A1F4-C53C3C70AEAE@redhat.com>
References: <6C338E88-3EE8-488D-A1F4-C53C3C70AEAE@redhat.com>
Message-ID: <DFEB7491-2E53-4F93-8916-34423B90C89B@redhat.com>

Sorry to disappoint but new Central on HTML5 won?t be part of Alpha2. It?s planned for Beta 1 (https://issues.jboss.org/browse/JBIDE-18813 <https://issues.jboss.org/browse/JBIDE-18813>)

> Le 14 avr. 2015 ? 07:45, Max Rydahl Andersen <manderse at redhat.com> a ?crit :
> 
> Heya,
> 
> Just a friendly reminder that Alpha2 code freeze is coming up on this 
> Thursday the 16th [1]
> if you are on Red Hat VPN you can access the ical for it at [2]. Planned 
> release of this is for 27th April.
> 
> This Alpha2 is "Special" in the sense it is targeting Eclipse Mars M6 
> which includes a lot of updates and fixes
> to the platform including:
> 
> * OS X p2 layout has changed = OS X users cannot update from Mars M1-M5 
> to M6, need to install.
> * Jetty 8 to Jetty 9 (major api change)
> * egit 3.x to 4.0
> * GTK3 bug fixes (Snjezana Go Go!)
> * ...and probably a lot more ;)
> 
> Big things hoping to show up in Alpha2 if you are not aware are:
> 
> * easyimport
> * OpenShift v3 tooling (it did not make it to Alpha1)
> * First working and pretty version of Central on HTML5
> * <fill in your thing here for N&N >
> 
> [1] 
> https://issues.jboss.org/browse/JBIDE/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel
> [2] 
> https://pp.engineering.redhat.com/pp-admin/api/v1/releases/524/schedule-tasks/?format=ics&flags__name=roadmap
> 
> Good luck and don't be afraid to ask if you find issues in M6.
> There are still time to fix it upstream! :)
> 
> p.s. I'm not available this Friday - but Fred Bricon promised to fill in 
> for me if any questions/concerns
> around code freeze and readiness.
> 
> Thanks,
> /max
> http://about.me/maxandersen
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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

From blafond at redhat.com  Tue Apr 14 14:36:00 2015
From: blafond at redhat.com (Barry Lafond)
Date: Tue, 14 Apr 2015 14:36:00 -0400 (EDT)
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <6A98A8DB-3CB5-4079-926B-9C03AF3342ED@redhat.com>
References: <552737D8.8000708@redhat.com>
	<E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>
	<55278AD2.2000101@phantomjinx.co.uk> <5527FFE8.9050306@redhat.com>
	<F30FD363-092D-469C-AA3B-798BA7C5647E@phantomjinx.co.uk>
	<552820EF.5060502@redhat.com>
	<6A98A8DB-3CB5-4079-926B-9C03AF3342ED@redhat.com>
Message-ID: <1268310755.15720101.1429036560657.JavaMail.zimbra@redhat.com>

Rob, 

Paul gave you the rundown on Teiid Designer's discovery of Teiid runtime versions after server start-up and that we contribute providers & actions to the Server View. Designer is designed to be backwards compatible (7.7 > 9.x) in terms of working with Teiid runtime admin and jdbc API. So in a sense, Designer doesn't care what Teiid runtime is installed. If it makes it easier on the user for server-set-up if JBT discovers/downloads/installs Teiid runtimes I'm in favor of it. 

Teiid Teiid 
Designer 
7.7 7.7 
8.0 8.2 
8.1 8.3 
8.2 - 8.4 8.4 
8.5 - 8.6 8.7 
9.0 8.8 
9.1 8.9 (planned) 
9.2 8.11 (planned) 

I've cc'd Ramesh Reddy on the Teiid project team and Van Halber, the DV build guy. They would know the version mappings between AS and Teiid runtimes. 

You are correct that Teiid 7.x was based on JBoss 5, while the 8.x stream is for AS7. Note also that Teiid 8.x community releases were compatible with EAP 6.x Alpha releases, not Final. Those are reserved for DV/Product releases. 

So my understanding is that the server configurations are fairly different between project and product. 

Barry 

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

> From: "Max Rydahl Andersen" <manderse at redhat.com>
> To: "Rob Stryker" <rstryker at redhat.com>
> Cc: "phantomjinx" <p.g.richardson at phantomjinx.co.uk>, "jbosstools-dev
> jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "Barry Lafond"
> <blafond at redhat.com>
> Sent: Monday, April 13, 2015 5:45:48 AM
> Subject: Re: [jbosstools-dev] Question on data virtualization runtimes and
> where downloadRuntime support belongs

> I'm still not following/seeing why Teiid Designer needs runtime
> detection if it detects it at runtime ?

> /max

> > After some discussion with PGR, we think it makes more sense for the
> > detection to live in the Teiid Designer repository.
> >
> > Teiid Designer currently only has code for detecting teiid in
> > *running* servers, with no support for identifying a Teiid
> > installation in servers that aren't running. This makes sense for
> > their use case (server may be remote) but is not useful for runtime
> > detection at all.
> >
> > TD currently is not involved in the server creation at all, but rather
> > just adds listeners so that once a server is added, or started, they
> > can begin their configuration / build up their model. They also
> > provide editor extensions that allow setting fields on the
> > IServerWorkingCopy.
> >
> > *Barry*: One thing that would help tremendously with identifying
> > installations in non-running local servers is if I could have a map of
> > Teiid / DV releases and what underlying JBoss / Wildfly / EAP versions
> > they correspond to. What I've heard so far is that Teiid 7.x was based
> > on JBoss 5, while the 8.x stream is for AS7. It's pretty important to
> > get a full mapping of supported releases to their underlying JBoss
> > version, though. This way I can properly implement the Server Bean
> > Loaders / Runtime detection.
> >
> > One final thing to note, which I think we should bring up to the Teiid
> > runtime team directly, is that DV product properly uses the layer
> > system in JBoss 7. It has the expected
> > org/jboss/as/product/dv/dir/META-INF/MANIFEST.MF file, with the
> > expected attribute JBoss-Product-Release-Version: 6.1.0...
> >
> > But the community releases of Teiid *do not*. They simply put
> > everything in modules/system/layers/base, with no clear way of
> > identifying a version. If I wanted to look at the version here, I'd
> > need to introspect
> > teiid-8.10.0.Final/modules/system/layers/base/org/jboss/teiid/api/main/teiid-api-8.10.0.Final.jar
> > and look at it's manifest.mf for the Bundle-Version, which so far
> > seems accurate.
> >
> > With all this in mind, it should be relatively painless (once I get
> > that version mapping from Barry) to get runtime detection +
> > downloading supported for Teiid Runtime / DV. There may be some
> > issues in stacks.yaml (since I'm not too familiar with all the bom
> > stuff) but I expect the version mapping will help me to properly pull
> > from other parts of stacks.yaml without issue.
> >
> > - Rob Stryker
> >
> > - Rob Stryker

> /max
> http://about.me/maxandersen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150414/03ea1128/attachment-0001.html 

From manderse at redhat.com  Tue Apr 14 15:25:48 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 14 Apr 2015 21:25:48 +0200
Subject: [jbosstools-dev] JBoss Tools 4.3.0.Alpha2 code freeze this
 Thursday 16th April
In-Reply-To: <DFEB7491-2E53-4F93-8916-34423B90C89B@redhat.com>
References: <6C338E88-3EE8-488D-A1F4-C53C3C70AEAE@redhat.com>
	<DFEB7491-2E53-4F93-8916-34423B90C89B@redhat.com>
Message-ID: <6DC680DC-C31F-4A07-9F68-2B609CF3A718@redhat.com>

On 14 Apr 2015, at 17:01, Fred Bricon wrote:

> Sorry to disappoint but new Central on HTML5 won?t be part of 
> Alpha2. It?s planned for Beta 1 
> (https://issues.jboss.org/browse/JBIDE-18813 
> <https://issues.jboss.org/browse/JBIDE-18813>)

bummer. thought you said last week it would make it in. Did I hear wrong 
or did something change ?

/max

>
>> Le 14 avr. 2015 ? 07:45, Max Rydahl Andersen <manderse at redhat.com> a 
>> ?crit :
>>
>> Heya,
>>
>> Just a friendly reminder that Alpha2 code freeze is coming up on this
>> Thursday the 16th [1]
>> if you are on Red Hat VPN you can access the ical for it at [2]. 
>> Planned
>> release of this is for 27th April.
>>
>> This Alpha2 is "Special" in the sense it is targeting Eclipse Mars M6
>> which includes a lot of updates and fixes
>> to the platform including:
>>
>> * OS X p2 layout has changed = OS X users cannot update from Mars 
>> M1-M5
>> to M6, need to install.
>> * Jetty 8 to Jetty 9 (major api change)
>> * egit 3.x to 4.0
>> * GTK3 bug fixes (Snjezana Go Go!)
>> * ...and probably a lot more ;)
>>
>> Big things hoping to show up in Alpha2 if you are not aware are:
>>
>> * easyimport
>> * OpenShift v3 tooling (it did not make it to Alpha1)
>> * First working and pretty version of Central on HTML5
>> * <fill in your thing here for N&N >
>>
>> [1]
>> https://issues.jboss.org/browse/JBIDE/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel
>> [2]
>> https://pp.engineering.redhat.com/pp-admin/api/v1/releases/524/schedule-tasks/?format=ics&flags__name=roadmap
>>
>> Good luck and don't be afraid to ask if you find issues in M6.
>> There are still time to fix it upstream! :)
>>
>> p.s. I'm not available this Friday - but Fred Bricon promised to fill 
>> in
>> for me if any questions/concerns
>> around code freeze and readiness.
>>
>> Thanks,
>> /max
>> http://about.me/maxandersen
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From fbricon at redhat.com  Tue Apr 14 15:36:36 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Tue, 14 Apr 2015 15:36:36 -0400
Subject: [jbosstools-dev] JBoss Tools 4.3.0.Alpha2 code freeze this
	Thursday 16th April
In-Reply-To: <6DC680DC-C31F-4A07-9F68-2B609CF3A718@redhat.com>
References: <6C338E88-3EE8-488D-A1F4-C53C3C70AEAE@redhat.com>
	<DFEB7491-2E53-4F93-8916-34423B90C89B@redhat.com>
	<6DC680DC-C31F-4A07-9F68-2B609CF3A718@redhat.com>
Message-ID: <9021963F-CA8E-4E1B-B0C0-8DFC87D88FC0@redhat.com>

you heard wrong :-)

> Le 14 avr. 2015 ? 15:25, Max Rydahl Andersen <manderse at redhat.com> a ?crit :
> 
> On 14 Apr 2015, at 17:01, Fred Bricon wrote:
> 
>> Sorry to disappoint but new Central on HTML5 won?t be part of Alpha2. It?s planned for Beta 1 (https://issues.jboss.org/browse/JBIDE-18813 <https://issues.jboss.org/browse/JBIDE-18813>)
> 
> bummer. thought you said last week it would make it in. Did I hear wrong or did something change ?
> 
> /max
> 
>> 
>>> Le 14 avr. 2015 ? 07:45, Max Rydahl Andersen <manderse at redhat.com> a ?crit :
>>> 
>>> Heya,
>>> 
>>> Just a friendly reminder that Alpha2 code freeze is coming up on this
>>> Thursday the 16th [1]
>>> if you are on Red Hat VPN you can access the ical for it at [2]. Planned
>>> release of this is for 27th April.
>>> 
>>> This Alpha2 is "Special" in the sense it is targeting Eclipse Mars M6
>>> which includes a lot of updates and fixes
>>> to the platform including:
>>> 
>>> * OS X p2 layout has changed = OS X users cannot update from Mars M1-M5
>>> to M6, need to install.
>>> * Jetty 8 to Jetty 9 (major api change)
>>> * egit 3.x to 4.0
>>> * GTK3 bug fixes (Snjezana Go Go!)
>>> * ...and probably a lot more ;)
>>> 
>>> Big things hoping to show up in Alpha2 if you are not aware are:
>>> 
>>> * easyimport
>>> * OpenShift v3 tooling (it did not make it to Alpha1)
>>> * First working and pretty version of Central on HTML5
>>> * <fill in your thing here for N&N >
>>> 
>>> [1]
>>> https://issues.jboss.org/browse/JBIDE/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel
>>> [2]
>>> https://pp.engineering.redhat.com/pp-admin/api/v1/releases/524/schedule-tasks/?format=ics&flags__name=roadmap
>>> 
>>> Good luck and don't be afraid to ask if you find issues in M6.
>>> There are still time to fix it upstream! :)
>>> 
>>> p.s. I'm not available this Friday - but Fred Bricon promised to fill in
>>> for me if any questions/concerns
>>> around code freeze and readiness.
>>> 
>>> Thanks,
>>> /max
>>> http://about.me/maxandersen
>>> 
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> 
> /max
> http://about.me/maxandersen



From rareddy at redhat.com  Tue Apr 14 23:20:17 2015
From: rareddy at redhat.com (Ramesh Reddy)
Date: Tue, 14 Apr 2015 23:20:17 -0400 (EDT)
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <1268310755.15720101.1429036560657.JavaMail.zimbra@redhat.com>
References: <552737D8.8000708@redhat.com>
	<E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>
	<55278AD2.2000101@phantomjinx.co.uk> <5527FFE8.9050306@redhat.com>
	<F30FD363-092D-469C-AA3B-798BA7C5647E@phantomjinx.co.uk>
	<552820EF.5060502@redhat.com>
	<6A98A8DB-3CB5-4079-926B-9C03AF3342ED@redhat.com>
	<1268310755.15720101.1429036560657.JavaMail.zimbra@redhat.com>
Message-ID: <2026117116.22143320.1429068017757.JavaMail.zimbra@redhat.com>

The usecase you are going after is download the Teiid runtime based on the Designer? Or you want to download the Teiid runtime based on the EAP? If it is former, Designer has strong preferences as to which Teiid runtime it works with, but in a given major release it work more seamless. If it is later 

EAP 5.1 is used with Teiid 7.x 
EAP 6.1 Alpha, up to Teiid 8.8 
EAP 6.3 Alpha, Teiid 8.9, 8.10 

We are planning for 

EAP 6.4.Alpha for Teiid 8.11 

No WildFly support yet. If you think a marker file like in the MANIFEST.MF makes it easier, we are open to add such file. 

Ramesh.. 

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

> Rob,

> Paul gave you the rundown on Teiid Designer's discovery of Teiid runtime
> versions after server start-up and that we contribute providers & actions to
> the Server View. Designer is designed to be backwards compatible (7.7 > 9.x)
> in terms of working with Teiid runtime admin and jdbc API. So in a sense,
> Designer doesn't care what Teiid runtime is installed. If it makes it easier
> on the user for server-set-up if JBT discovers/downloads/installs Teiid
> runtimes I'm in favor of it.

> Teiid Teiid
> Designer
> 7.7 7.7
> 8.0 8.2
> 8.1 8.3
> 8.2 - 8.4 8.4
> 8.5 - 8.6 8.7
> 9.0 8.8
> 9.1 8.9 (planned)
> 9.2 8.11 (planned)

> I've cc'd Ramesh Reddy on the Teiid project team and Van Halber, the DV build
> guy. They would know the version mappings between AS and Teiid runtimes.

> You are correct that Teiid 7.x was based on JBoss 5, while the 8.x stream is
> for AS7. Note also that Teiid 8.x community releases were compatible with
> EAP 6.x Alpha releases, not Final. Those are reserved for DV/Product
> releases.

> So my understanding is that the server configurations are fairly different
> between project and product.

> Barry

> ----- Original Message -----

> > From: "Max Rydahl Andersen" <manderse at redhat.com>
> 
> > To: "Rob Stryker" <rstryker at redhat.com>
> 
> > Cc: "phantomjinx" <p.g.richardson at phantomjinx.co.uk>, "jbosstools-dev
> > jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "Barry Lafond"
> > <blafond at redhat.com>
> 
> > Sent: Monday, April 13, 2015 5:45:48 AM
> 
> > Subject: Re: [jbosstools-dev] Question on data virtualization runtimes and
> > where downloadRuntime support belongs
> 

> > I'm still not following/seeing why Teiid Designer needs runtime
> 
> > detection if it detects it at runtime ?
> 

> > /max
> 

> > > After some discussion with PGR, we think it makes more sense for the
> 
> > > detection to live in the Teiid Designer repository.
> 
> > >
> 
> > > Teiid Designer currently only has code for detecting teiid in
> 
> > > *running* servers, with no support for identifying a Teiid
> 
> > > installation in servers that aren't running. This makes sense for
> 
> > > their use case (server may be remote) but is not useful for runtime
> 
> > > detection at all.
> 
> > >
> 
> > > TD currently is not involved in the server creation at all, but rather
> 
> > > just adds listeners so that once a server is added, or started, they
> 
> > > can begin their configuration / build up their model. They also
> 
> > > provide editor extensions that allow setting fields on the
> 
> > > IServerWorkingCopy.
> 
> > >
> 
> > > *Barry*: One thing that would help tremendously with identifying
> 
> > > installations in non-running local servers is if I could have a map of
> 
> > > Teiid / DV releases and what underlying JBoss / Wildfly / EAP versions
> 
> > > they correspond to. What I've heard so far is that Teiid 7.x was based
> 
> > > on JBoss 5, while the 8.x stream is for AS7. It's pretty important to
> 
> > > get a full mapping of supported releases to their underlying JBoss
> 
> > > version, though. This way I can properly implement the Server Bean
> 
> > > Loaders / Runtime detection.
> 
> > >
> 
> > > One final thing to note, which I think we should bring up to the Teiid
> 
> > > runtime team directly, is that DV product properly uses the layer
> 
> > > system in JBoss 7. It has the expected
> 
> > > org/jboss/as/product/dv/dir/META-INF/MANIFEST.MF file, with the
> 
> > > expected attribute JBoss-Product-Release-Version: 6.1.0...
> 
> > >
> 
> > > But the community releases of Teiid *do not*. They simply put
> 
> > > everything in modules/system/layers/base, with no clear way of
> 
> > > identifying a version. If I wanted to look at the version here, I'd
> 
> > > need to introspect
> 
> > > teiid-8.10.0.Final/modules/system/layers/base/org/jboss/teiid/api/main/teiid-api-8.10.0.Final.jar
> 
> > > and look at it's manifest.mf for the Bundle-Version, which so far
> 
> > > seems accurate.
> 
> > >
> 
> > > With all this in mind, it should be relatively painless (once I get
> 
> > > that version mapping from Barry) to get runtime detection +
> 
> > > downloading supported for Teiid Runtime / DV. There may be some
> 
> > > issues in stacks.yaml (since I'm not too familiar with all the bom
> 
> > > stuff) but I expect the version mapping will help me to properly pull
> 
> > > from other parts of stacks.yaml without issue.
> 
> > >
> 
> > > - Rob Stryker
> 
> > >
> 
> > > - Rob Stryker
> 

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

From manderse at redhat.com  Wed Apr 15 03:01:45 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Wed, 15 Apr 2015 03:01:45 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201504150701.t3F71jpk016511@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-19590

https://issues.jboss.org/browse/JBIDE-19590
Summary: Update module's README.md files with information about dependencies to other modules

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

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



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

From manderse at redhat.com  Wed Apr 15 08:11:34 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 15 Apr 2015 14:11:34 +0200
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <2026117116.22143320.1429068017757.JavaMail.zimbra@redhat.com>
References: <552737D8.8000708@redhat.com>
	<E90408C4-CFE9-4B9F-B455-A02D98C1C864@redhat.com>
	<55278AD2.2000101@phantomjinx.co.uk> <5527FFE8.9050306@redhat.com>
	<F30FD363-092D-469C-AA3B-798BA7C5647E@phantomjinx.co.uk>
	<552820EF.5060502@redhat.com>
	<6A98A8DB-3CB5-4079-926B-9C03AF3342ED@redhat.com>
	<1268310755.15720101.1429036560657.JavaMail.zimbra@redhat.com>
	<2026117116.22143320.1429068017757.JavaMail.zimbra@redhat.com>
Message-ID: <B86D0092-9329-4C9A-8885-4E5B878D5777@redhat.com>

On 15 Apr 2015, at 5:20, Ramesh Reddy wrote:

> The usecase you are going after is download the Teiid runtime based on 
> the Designer? Or you want to download the Teiid runtime based on the 
> EAP? If it is former, Designer has strong preferences as to which 
> Teiid runtime it works with, but in a given major release it work more 
> seamless. If it is later

> EAP 5.1 is used with Teiid 7.x
> EAP 6.1 Alpha, up to Teiid 8.8
> EAP 6.3 Alpha, Teiid 8.9, 8.10

eh - I thought you guys supported multiple runtimes by now ?

btw. this is not for matching teiid runtimes with designer - it is about
when JBoss Tools runtime detection or server wizard detects a server we 
would like to know
if it is more than just the generic EAP server - we already check if it 
is portal or SOA-P or FSW
and then name the server adaptor appropriately.

By adding Teeid support to we would get "JBoss Data Virtualisation 7.4" 
instead of "JBoss EAP 5.1".

That is all - very simple actually ;)

> We are planning for
>
> EAP 6.4.Alpha for Teiid 8.11
>
> No WildFly support yet. If you think a marker file like in the 
> MANIFEST.MF makes it easier, we are open to add such file.

>
> Ramesh..
>
> ----- Original Message -----
>
>> Rob,
>
>> Paul gave you the rundown on Teiid Designer's discovery of Teiid 
>> runtime
>> versions after server start-up and that we contribute providers & 
>> actions to
>> the Server View. Designer is designed to be backwards compatible (7.7 
>> > 9.x)
>> in terms of working with Teiid runtime admin and jdbc API. So in a 
>> sense,
>> Designer doesn't care what Teiid runtime is installed. If it makes it 
>> easier
>> on the user for server-set-up if JBT discovers/downloads/installs 
>> Teiid
>> runtimes I'm in favor of it.
>
>> Teiid Teiid
>> Designer
>> 7.7 7.7
>> 8.0 8.2
>> 8.1 8.3
>> 8.2 - 8.4 8.4
>> 8.5 - 8.6 8.7
>> 9.0 8.8
>> 9.1 8.9 (planned)
>> 9.2 8.11 (planned)
>
>> I've cc'd Ramesh Reddy on the Teiid project team and Van Halber, the 
>> DV build
>> guy. They would know the version mappings between AS and Teiid 
>> runtimes.
>
>> You are correct that Teiid 7.x was based on JBoss 5, while the 8.x 
>> stream is
>> for AS7. Note also that Teiid 8.x community releases were compatible 
>> with
>> EAP 6.x Alpha releases, not Final. Those are reserved for DV/Product
>> releases.
>
>> So my understanding is that the server configurations are fairly 
>> different
>> between project and product.
>
>> Barry
>
>> ----- Original Message -----
>
>>> From: "Max Rydahl Andersen" <manderse at redhat.com>
>>
>>> To: "Rob Stryker" <rstryker at redhat.com>
>>
>>> Cc: "phantomjinx" <p.g.richardson at phantomjinx.co.uk>, 
>>> "jbosstools-dev
>>> jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "Barry Lafond"
>>> <blafond at redhat.com>
>>
>>> Sent: Monday, April 13, 2015 5:45:48 AM
>>
>>> Subject: Re: [jbosstools-dev] Question on data virtualization 
>>> runtimes and
>>> where downloadRuntime support belongs
>>
>
>>> I'm still not following/seeing why Teiid Designer needs runtime
>>
>>> detection if it detects it at runtime ?
>>
>
>>> /max
>>
>
>>>> After some discussion with PGR, we think it makes more sense for 
>>>> the
>>
>>>> detection to live in the Teiid Designer repository.
>>
>>>>
>>
>>>> Teiid Designer currently only has code for detecting teiid in
>>
>>>> *running* servers, with no support for identifying a Teiid
>>
>>>> installation in servers that aren't running. This makes sense for
>>
>>>> their use case (server may be remote) but is not useful for runtime
>>
>>>> detection at all.
>>
>>>>
>>
>>>> TD currently is not involved in the server creation at all, but 
>>>> rather
>>
>>>> just adds listeners so that once a server is added, or started, 
>>>> they
>>
>>>> can begin their configuration / build up their model. They also
>>
>>>> provide editor extensions that allow setting fields on the
>>
>>>> IServerWorkingCopy.
>>
>>>>
>>
>>>> *Barry*: One thing that would help tremendously with identifying
>>
>>>> installations in non-running local servers is if I could have a map 
>>>> of
>>
>>>> Teiid / DV releases and what underlying JBoss / Wildfly / EAP 
>>>> versions
>>
>>>> they correspond to. What I've heard so far is that Teiid 7.x was 
>>>> based
>>
>>>> on JBoss 5, while the 8.x stream is for AS7. It's pretty important 
>>>> to
>>
>>>> get a full mapping of supported releases to their underlying JBoss
>>
>>>> version, though. This way I can properly implement the Server Bean
>>
>>>> Loaders / Runtime detection.
>>
>>>>
>>
>>>> One final thing to note, which I think we should bring up to the 
>>>> Teiid
>>
>>>> runtime team directly, is that DV product properly uses the layer
>>
>>>> system in JBoss 7. It has the expected
>>
>>>> org/jboss/as/product/dv/dir/META-INF/MANIFEST.MF file, with the
>>
>>>> expected attribute JBoss-Product-Release-Version: 6.1.0...
>>
>>>>
>>
>>>> But the community releases of Teiid *do not*. They simply put
>>
>>>> everything in modules/system/layers/base, with no clear way of
>>
>>>> identifying a version. If I wanted to look at the version here, I'd
>>
>>>> need to introspect
>>
>>>> teiid-8.10.0.Final/modules/system/layers/base/org/jboss/teiid/api/main/teiid-api-8.10.0.Final.jar
>>
>>>> and look at it's manifest.mf for the Bundle-Version, which so far
>>
>>>> seems accurate.
>>
>>>>
>>
>>>> With all this in mind, it should be relatively painless (once I get
>>
>>>> that version mapping from Barry) to get runtime detection +
>>
>>>> downloading supported for Teiid Runtime / DV. There may be some
>>
>>>> issues in stacks.yaml (since I'm not too familiar with all the bom
>>
>>>> stuff) but I expect the version mapping will help me to properly 
>>>> pull
>>
>>>> from other parts of stacks.yaml without issue.
>>
>>>>
>>
>>>> - Rob Stryker
>>
>>>>
>>
>>>> - Rob Stryker
>>
>
>>> /max
>>
>>> http://about.me/maxandersen
>>


/max
http://about.me/maxandersen


From rareddy at redhat.com  Wed Apr 15 09:10:36 2015
From: rareddy at redhat.com (Ramesh Reddy)
Date: Wed, 15 Apr 2015 09:10:36 -0400 (EDT)
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <B86D0092-9329-4C9A-8885-4E5B878D5777@redhat.com>
References: <552737D8.8000708@redhat.com> <5527FFE8.9050306@redhat.com>
	<F30FD363-092D-469C-AA3B-798BA7C5647E@phantomjinx.co.uk>
	<552820EF.5060502@redhat.com>
	<6A98A8DB-3CB5-4079-926B-9C03AF3342ED@redhat.com>
	<1268310755.15720101.1429036560657.JavaMail.zimbra@redhat.com>
	<2026117116.22143320.1429068017757.JavaMail.zimbra@redhat.com>
	<B86D0092-9329-4C9A-8885-4E5B878D5777@redhat.com>
Message-ID: <1371958984.223791.1429103436262.JavaMail.zimbra@redhat.com>



----- Original Message -----
> On 15 Apr 2015, at 5:20, Ramesh Reddy wrote:
> 
> > The usecase you are going after is download the Teiid runtime based on
> > the Designer? Or you want to download the Teiid runtime based on the
> > EAP? If it is former, Designer has strong preferences as to which
> > Teiid runtime it works with, but in a given major release it work more
> > seamless. If it is later
> 
> > EAP 5.1 is used with Teiid 7.x
> > EAP 6.1 Alpha, up to Teiid 8.8
> > EAP 6.3 Alpha, Teiid 8.9, 8.10
> 
> eh - I thought you guys supported multiple runtimes by now ?

The issue there is we depend heavily on service, deployment and management APIs of the AS, not to mention all the common dependencies to other libraries. We have to change based on them thus we can not release a single Teiid runtime across all the EAP instances.

> 
> btw. this is not for matching teiid runtimes with designer - it is about
> when JBoss Tools runtime detection or server wizard detects a server we
> would like to know
> if it is more than just the generic EAP server - we already check if it
> is portal or SOA-P or FSW
> and then name the server adaptor appropriately.
> 
> By adding Teeid support to we would get "JBoss Data Virtualisation 7.4"
> instead of "JBoss EAP 5.1".

MANIFEST.MF is the discovery mechanism with SOA-P or FSW? As I said we can adopt to that mechanism if that is what we want. 
 
> 
> That is all - very simple actually ;)
> 
> > We are planning for
> >
> > EAP 6.4.Alpha for Teiid 8.11
> >
> > No WildFly support yet. If you think a marker file like in the
> > MANIFEST.MF makes it easier, we are open to add such file.
> 
> >
> > Ramesh..
> >
> > ----- Original Message -----
> >
> >> Rob,
> >
> >> Paul gave you the rundown on Teiid Designer's discovery of Teiid
> >> runtime
> >> versions after server start-up and that we contribute providers &
> >> actions to
> >> the Server View. Designer is designed to be backwards compatible (7.7
> >> > 9.x)
> >> in terms of working with Teiid runtime admin and jdbc API. So in a
> >> sense,
> >> Designer doesn't care what Teiid runtime is installed. If it makes it
> >> easier
> >> on the user for server-set-up if JBT discovers/downloads/installs
> >> Teiid
> >> runtimes I'm in favor of it.
> >
> >> Teiid Teiid
> >> Designer
> >> 7.7 7.7
> >> 8.0 8.2
> >> 8.1 8.3
> >> 8.2 - 8.4 8.4
> >> 8.5 - 8.6 8.7
> >> 9.0 8.8
> >> 9.1 8.9 (planned)
> >> 9.2 8.11 (planned)
> >
> >> I've cc'd Ramesh Reddy on the Teiid project team and Van Halber, the
> >> DV build
> >> guy. They would know the version mappings between AS and Teiid
> >> runtimes.
> >
> >> You are correct that Teiid 7.x was based on JBoss 5, while the 8.x
> >> stream is
> >> for AS7. Note also that Teiid 8.x community releases were compatible
> >> with
> >> EAP 6.x Alpha releases, not Final. Those are reserved for DV/Product
> >> releases.
> >
> >> So my understanding is that the server configurations are fairly
> >> different
> >> between project and product.
> >
> >> Barry
> >
> >> ----- Original Message -----
> >
> >>> From: "Max Rydahl Andersen" <manderse at redhat.com>
> >>
> >>> To: "Rob Stryker" <rstryker at redhat.com>
> >>
> >>> Cc: "phantomjinx" <p.g.richardson at phantomjinx.co.uk>,
> >>> "jbosstools-dev
> >>> jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "Barry Lafond"
> >>> <blafond at redhat.com>
> >>
> >>> Sent: Monday, April 13, 2015 5:45:48 AM
> >>
> >>> Subject: Re: [jbosstools-dev] Question on data virtualization
> >>> runtimes and
> >>> where downloadRuntime support belongs
> >>
> >
> >>> I'm still not following/seeing why Teiid Designer needs runtime
> >>
> >>> detection if it detects it at runtime ?
> >>
> >
> >>> /max
> >>
> >
> >>>> After some discussion with PGR, we think it makes more sense for
> >>>> the
> >>
> >>>> detection to live in the Teiid Designer repository.
> >>
> >>>>
> >>
> >>>> Teiid Designer currently only has code for detecting teiid in
> >>
> >>>> *running* servers, with no support for identifying a Teiid
> >>
> >>>> installation in servers that aren't running. This makes sense for
> >>
> >>>> their use case (server may be remote) but is not useful for runtime
> >>
> >>>> detection at all.
> >>
> >>>>
> >>
> >>>> TD currently is not involved in the server creation at all, but
> >>>> rather
> >>
> >>>> just adds listeners so that once a server is added, or started,
> >>>> they
> >>
> >>>> can begin their configuration / build up their model. They also
> >>
> >>>> provide editor extensions that allow setting fields on the
> >>
> >>>> IServerWorkingCopy.
> >>
> >>>>
> >>
> >>>> *Barry*: One thing that would help tremendously with identifying
> >>
> >>>> installations in non-running local servers is if I could have a map
> >>>> of
> >>
> >>>> Teiid / DV releases and what underlying JBoss / Wildfly / EAP
> >>>> versions
> >>
> >>>> they correspond to. What I've heard so far is that Teiid 7.x was
> >>>> based
> >>
> >>>> on JBoss 5, while the 8.x stream is for AS7. It's pretty important
> >>>> to
> >>
> >>>> get a full mapping of supported releases to their underlying JBoss
> >>
> >>>> version, though. This way I can properly implement the Server Bean
> >>
> >>>> Loaders / Runtime detection.
> >>
> >>>>
> >>
> >>>> One final thing to note, which I think we should bring up to the
> >>>> Teiid
> >>
> >>>> runtime team directly, is that DV product properly uses the layer
> >>
> >>>> system in JBoss 7. It has the expected
> >>
> >>>> org/jboss/as/product/dv/dir/META-INF/MANIFEST.MF file, with the
> >>
> >>>> expected attribute JBoss-Product-Release-Version: 6.1.0...
> >>
> >>>>
> >>
> >>>> But the community releases of Teiid *do not*. They simply put
> >>
> >>>> everything in modules/system/layers/base, with no clear way of
> >>
> >>>> identifying a version. If I wanted to look at the version here, I'd
> >>
> >>>> need to introspect
> >>
> >>>> teiid-8.10.0.Final/modules/system/layers/base/org/jboss/teiid/api/main/teiid-api-8.10.0.Final.jar
> >>
> >>>> and look at it's manifest.mf for the Bundle-Version, which so far
> >>
> >>>> seems accurate.
> >>
> >>>>
> >>
> >>>> With all this in mind, it should be relatively painless (once I get
> >>
> >>>> that version mapping from Barry) to get runtime detection +
> >>
> >>>> downloading supported for Teiid Runtime / DV. There may be some
> >>
> >>>> issues in stacks.yaml (since I'm not too familiar with all the bom
> >>
> >>>> stuff) but I expect the version mapping will help me to properly
> >>>> pull
> >>
> >>>> from other parts of stacks.yaml without issue.
> >>
> >>>>
> >>
> >>>> - Rob Stryker
> >>
> >>>>
> >>
> >>>> - Rob Stryker
> >>
> >
> >>> /max
> >>
> >>> http://about.me/maxandersen
> >>
> 
> 
> /max
> http://about.me/maxandersen
> 

From manderse at redhat.com  Wed Apr 15 12:33:34 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 15 Apr 2015 18:33:34 +0200
Subject: [jbosstools-dev] Question on data virtualization runtimes and
 where downloadRuntime support belongs
In-Reply-To: <1371958984.223791.1429103436262.JavaMail.zimbra@redhat.com>
References: <552737D8.8000708@redhat.com> <5527FFE8.9050306@redhat.com>
	<F30FD363-092D-469C-AA3B-798BA7C5647E@phantomjinx.co.uk>
	<552820EF.5060502@redhat.com>
	<6A98A8DB-3CB5-4079-926B-9C03AF3342ED@redhat.com>
	<1268310755.15720101.1429036560657.JavaMail.zimbra@redhat.com>
	<2026117116.22143320.1429068017757.JavaMail.zimbra@redhat.com>
	<B86D0092-9329-4C9A-8885-4E5B878D5777@redhat.com>
	<1371958984.223791.1429103436262.JavaMail.zimbra@redhat.com>
Message-ID: <C598D4A4-DCDA-4682-820E-A46ADB3CD1E1@redhat.com>

On 15 Apr 2015, at 15:10, Ramesh Reddy wrote:

> ----- Original Message -----
>> On 15 Apr 2015, at 5:20, Ramesh Reddy wrote:
>>
>>> The usecase you are going after is download the Teiid runtime based 
>>> on
>>> the Designer? Or you want to download the Teiid runtime based on the
>>> EAP? If it is former, Designer has strong preferences as to which
>>> Teiid runtime it works with, but in a given major release it work 
>>> more
>>> seamless. If it is later
>>
>>> EAP 5.1 is used with Teiid 7.x
>>> EAP 6.1 Alpha, up to Teiid 8.8
>>> EAP 6.3 Alpha, Teiid 8.9, 8.10
>>
>> eh - I thought you guys supported multiple runtimes by now ?
>
> The issue there is we depend heavily on service, deployment and 
> management APIs of the AS, not to mention all the common dependencies 
> to other libraries. We have to change based on them thus we can not 
> release a single Teiid runtime across all the EAP instances.

I'm not talking about Teiid runtime supporting multiple EAP.

I'm talking Teiid Designer supporting multiple versions of Teiid 
runtime.

>> btw. this is not for matching teiid runtimes with designer - it is 
>> about
>> when JBoss Tools runtime detection or server wizard detects a server 
>> we
>> would like to know
>> if it is more than just the generic EAP server - we already check if 
>> it
>> is portal or SOA-P or FSW
>> and then name the server adaptor appropriately.
>>
>> By adding Teeid support to we would get "JBoss Data Virtualisation 
>> 7.4"
>> instead of "JBoss EAP 5.1".
>
> MANIFEST.MF is the discovery mechanism with SOA-P or FSW? As I said we 
> can adopt to that mechanism if that is what we want.

we use the jboss product layering metadata.

Rob can outline the details.

Note, in case you don't actually use that it would be interesting to 
know why.
i.e. is it A) we didn't know about it - lets use it! or B) Teiid is not 
considered a layered product and can be installed/patched in a different 
way than SOA-P, FSW,etc. thus it is not registered as a layered product.

/max
http://about.me/maxandersen

From nboldt at redhat.com  Wed Apr 15 17:56:12 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 15 Apr 2015 17:56:12 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Should there be 2 versions of
	javax.servlet in JBDS?
Message-ID: <552EDE7C.7040606@redhat.com>

Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and 
3.1.0 in JBDS.

More importantly... SHOULD we be including both? Or can we just include 
3.1.0 and drop 3.0.0?

If we need both, then that's fine -- I'll add another exclusion rule to 
versionwatch [1]. But if we only need the newer one, that's even better.

[1] 
https://github.com/jbdevstudio/jbdevstudio-qa/blob/master/vwatch/src/main/resources/multiple-version-ignore.properties

Looking into our 4.50.x target platforms [2], I see we explicitly add 
javax.servlet 3.0.0 but don't add 3.1.0.

[2] 
https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbdevstudio/multiple/jbdevstudio-multiple.target#L32

Maybe we should remove the 3.0.0 version from the target platform for 
Alpha2, and see if anything breaks? 8-D


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

From rstryker at redhat.com  Wed Apr 15 20:45:17 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Wed, 15 Apr 2015 20:45:17 -0400
Subject: [jbosstools-dev] Creation of pom.xml property for skipTestOrITest
	for parent pom.xml
Message-ID: <552F061D.1030208@redhat.com>

My jboss/wf runtimes are being downloaded via my integration tests, even 
when -DskipTests is selected, because my integration test pom.xml has 
<skip>${skipITests}</skip> in it.  Until now, there was no easily 
recognized way to make a new property that could 'or' skipTests with 
skipITests.

So I've added this to my pom in one of my topic branches, and it seems 
to work exactly how we'd want it to. It basically functions via a regex, 
puts ${skipTests}${skipITests}, and performs a regex replacement to make 
the value either "true" or blank. This property can later be used in my 
<skip> section.

If anyone thinks this property should be available for parent pom, I'd 
suggest you take it and make it available to all other modules who might 
have integration tests with heavy dependencies.

Otherwise, I'll just keep it in my local pom for my itests.

             <plugin>
                 <groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
                 <version>1.7</version>
                 <executions>
                     <execution>
                         <id>regex-property</id>
                         <goals>
                             <goal>regex-property</goal>
                         </goals>
                         <configuration>
                             <name>skipTestOrITest</name>
<value>${skipTests}${skipITests}</value>
<regex>((..skipTests.)?(true)?((..skipITests.)|(null)|(true)|(false))?)</regex>
<replacement>$3</replacement>
<failIfNoMatch>false</failIfNoMatch>
                         </configuration>
                     </execution>
                     </executions>
                   </plugin>


From rstryker at redhat.com  Wed Apr 15 23:45:12 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Wed, 15 Apr 2015 23:45:12 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Should there be 2 versions of
 javax.servlet in JBDS?
In-Reply-To: <552EDE7C.7040606@redhat.com>
References: <552EDE7C.7040606@redhat.com>
Message-ID: <552F3048.9010408@redhat.com>


A fresh download of Luna SR2 shows the following files with 
'javax.servlet' in the name:

[rob at localhost wildfly-web-9.0.0.Beta2.zip.expanded]$ tar -ztvf 
/tmp/eclipse-jee-luna-SR2-linux-gtk-x86_64.tar.gz | grep "javax.servlet"
-rw-rw-r-- messagebus/users  107235 2015-02-19 03:30 
eclipse/plugins/javax.servlet.jsp_2.2.0.v201112011158.jar
-rw-rw-r-- messagebus/users   201594 2015-02-19 03:30 
eclipse/plugins/javax.servlet_3.0.0.v201112011016.jar


A fresh download of Mars shows the following files with "javax.servlet" 
in the name:

[rob at localhost wildfly-web-9.0.0.Beta2.zip.expanded]$ tar -ztvf 
/tmp/eclipse-jee-mars-M6-linux-gtk-x86_64.tar.gz | grep "javax.servlet"
-rw-rw-r-- genie.packaging/technology.packaging   105235 2015-03-26 
08:15 eclipse/plugins/javax.servlet_3.1.0.v201410161800.jar
-rw-rw-r-- genie.packaging/technology.packaging   107235 2015-03-26 
08:15 eclipse/plugins/javax.servlet.jsp_2.2.0.v201112011158.jar

My guess is that we had servlet 3.0 in the Luna TP and when we simply 
'added' the mars deps, we added the new one.  I would suggest that if 
Mars does not come with a javax.servlet_3.0  then we don't need it.

I know my code specifically does not depend on it either, but I cannot 
guarantee others do not require specifics. I honestly can't imagine 
anyone on our team requiring servlet 3.0 jar specifically, but I have 
been known to suffer from a lack of imagination in the past.

- Rob Stryker


On 04/15/2015 05:56 PM, Nick Boldt wrote:
> Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> 3.1.0 in JBDS.
>
> More importantly... SHOULD we be including both? Or can we just include
> 3.1.0 and drop 3.0.0?
>
> If we need both, then that's fine -- I'll add another exclusion rule to
> versionwatch [1]. But if we only need the newer one, that's even better.
>
> [1]
> https://github.com/jbdevstudio/jbdevstudio-qa/blob/master/vwatch/src/main/resources/multiple-version-ignore.properties
>
> Looking into our 4.50.x target platforms [2], I see we explicitly add
> javax.servlet 3.0.0 but don't add 3.1.0.
>
> [2]
> https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbdevstudio/multiple/jbdevstudio-multiple.target#L32
>
> Maybe we should remove the 3.0.0 version from the target platform for
> Alpha2, and see if anything breaks? 8-D
>
>


From manderse at redhat.com  Thu Apr 16 01:35:08 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 16 Apr 2015 01:35:08 -0400 (EDT)
Subject: [jbosstools-dev] Creation of pom.xml property for
	skipTestOrITest	for parent pom.xml
In-Reply-To: <552F061D.1030208@redhat.com>
References: <552F061D.1030208@redhat.com>
Message-ID: <B37867FC-4B86-41FD-85F0-8B8060D9F0F4@redhat.com>

Got a PR to look at ?

/max
http://about.me/maxandersen


> On 16 Apr 2015, at 02:45, Rob Stryker <rstryker at redhat.com> wrote:
> 
> My jboss/wf runtimes are being downloaded via my integration tests, even 
> when -DskipTests is selected, because my integration test pom.xml has 
> <skip>${skipITests}</skip> in it.  Until now, there was no easily 
> recognized way to make a new property that could 'or' skipTests with 
> skipITests.
> 
> So I've added this to my pom in one of my topic branches, and it seems 
> to work exactly how we'd want it to. It basically functions via a regex, 
> puts ${skipTests}${skipITests}, and performs a regex replacement to make 
> the value either "true" or blank. This property can later be used in my 
> <skip> section.
> 
> If anyone thinks this property should be available for parent pom, I'd 
> suggest you take it and make it available to all other modules who might 
> have integration tests with heavy dependencies.
> 
> Otherwise, I'll just keep it in my local pom for my itests.
> 
>             <plugin>
>                 <groupId>org.codehaus.mojo</groupId>
> <artifactId>build-helper-maven-plugin</artifactId>
>                 <version>1.7</version>
>                 <executions>
>                     <execution>
>                         <id>regex-property</id>
>                         <goals>
>                             <goal>regex-property</goal>
>                         </goals>
>                         <configuration>
>                             <name>skipTestOrITest</name>
> <value>${skipTests}${skipITests}</value>
> <regex>((..skipTests.)?(true)?((..skipITests.)|(null)|(true)|(false))?)</regex>
> <replacement>$3</replacement>
> <failIfNoMatch>false</failIfNoMatch>
>                         </configuration>
>                     </execution>
>                     </executions>
>                   </plugin>
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From manderse at redhat.com  Thu Apr 16 02:31:42 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 16 Apr 2015 02:31:42 -0400 (EDT)
Subject: [jbosstools-dev] ACTION REQUIRED: Should there be 2 versions of
	javax.servlet in JBDS?
In-Reply-To: <552F3048.9010408@redhat.com>
References: <552EDE7C.7040606@redhat.com> <552F3048.9010408@redhat.com>
Message-ID: <21FCE0F7-E167-4DD5-A908-80AF8D017913@redhat.com>

Looks like a missed update when going to Mars ?

I would just move it up. It's probably used by jetty in eclipse. 

/max
http://about.me/maxandersen


> On 16 Apr 2015, at 05:45, Rob Stryker <rstryker at redhat.com> wrote:
> 
> 
> A fresh download of Luna SR2 shows the following files with 
> 'javax.servlet' in the name:
> 
> [rob at localhost wildfly-web-9.0.0.Beta2.zip.expanded]$ tar -ztvf 
> /tmp/eclipse-jee-luna-SR2-linux-gtk-x86_64.tar.gz | grep "javax.servlet"
> -rw-rw-r-- messagebus/users  107235 2015-02-19 03:30 
> eclipse/plugins/javax.servlet.jsp_2.2.0.v201112011158.jar
> -rw-rw-r-- messagebus/users   201594 2015-02-19 03:30 
> eclipse/plugins/javax.servlet_3.0.0.v201112011016.jar
> 
> 
> A fresh download of Mars shows the following files with "javax.servlet" 
> in the name:
> 
> [rob at localhost wildfly-web-9.0.0.Beta2.zip.expanded]$ tar -ztvf 
> /tmp/eclipse-jee-mars-M6-linux-gtk-x86_64.tar.gz | grep "javax.servlet"
> -rw-rw-r-- genie.packaging/technology.packaging   105235 2015-03-26 
> 08:15 eclipse/plugins/javax.servlet_3.1.0.v201410161800.jar
> -rw-rw-r-- genie.packaging/technology.packaging   107235 2015-03-26 
> 08:15 eclipse/plugins/javax.servlet.jsp_2.2.0.v201112011158.jar
> 
> My guess is that we had servlet 3.0 in the Luna TP and when we simply 
> 'added' the mars deps, we added the new one.  I would suggest that if 
> Mars does not come with a javax.servlet_3.0  then we don't need it.
> 
> I know my code specifically does not depend on it either, but I cannot 
> guarantee others do not require specifics. I honestly can't imagine 
> anyone on our team requiring servlet 3.0 jar specifically, but I have 
> been known to suffer from a lack of imagination in the past.
> 
> - Rob Stryker
> 
> 
>> On 04/15/2015 05:56 PM, Nick Boldt wrote:
>> Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
>> 3.1.0 in JBDS.
>> 
>> More importantly... SHOULD we be including both? Or can we just include
>> 3.1.0 and drop 3.0.0?
>> 
>> If we need both, then that's fine -- I'll add another exclusion rule to
>> versionwatch [1]. But if we only need the newer one, that's even better.
>> 
>> [1]
>> https://github.com/jbdevstudio/jbdevstudio-qa/blob/master/vwatch/src/main/resources/multiple-version-ignore.properties
>> 
>> Looking into our 4.50.x target platforms [2], I see we explicitly add
>> javax.servlet 3.0.0 but don't add 3.1.0.
>> 
>> [2]
>> https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbdevstudio/multiple/jbdevstudio-multiple.target#L32
>> 
>> Maybe we should remove the 3.0.0 version from the target platform for
>> Alpha2, and see if anything breaks? 8-D
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From manderse at redhat.com  Thu Apr 16 03:00:24 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Thu, 16 Apr 2015 03:00:24 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 2 issues with no component
Message-ID: <201504160700.t3G70Om4018953@int-mx13.intmail.prod.int.phx2.redhat.com>


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

 
* No component for JBIDE-19590

https://issues.jboss.org/browse/JBIDE-19590
Summary: Update module's README.md files with information about dependencies to other modules

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

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


* No component for JBDS-3407

https://issues.jboss.org/browse/JBDS-3407
Summary: Not able to create  'non-bare' repository in JBDS 8.1. 

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

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



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

From taozhi29480 at 163.com  Thu Apr 16 03:57:16 2015
From: taozhi29480 at 163.com (Ashley Fletcher)
Date: Thu, 16 Apr 2015 03:57:16 -0400
Subject: [jbosstools-dev] your web site...
Message-ID: <201504160757.t3G7vGXH007438@lists01.dmz-a.mwc.hst.phx2.redhat.com>

 Hi,

 My name is Tao Zhi and I'm an independent web strategist. 
 I came across your business website while researching
 a client's site for toxic links; your website was
 linked to some of the same bad sites. I also noticed
 it was not fully compliant with Google's
 new Penguin 3.0 Algorithm and Panda rules.

 Whenever I find good companies with online issues
 I tend to reach out and let them know, In 20 minutes
 I can show you how you could fuel your brand and
 generate more revenue from search engines and
 social networks. These are tactics we've used 
 to help over 300 clients grow their business 
 and are currently "The fastest growing Internet
 marketing Company in China"!

 All I'd like to do is follow up about this with
 a quick phone call... Can I call you this week
 to discuss some proven strategies that can help
 your business grow? Looking forward to your
 positive response.

Warm Regards,

Tao Zhi

Grow Business Rankings
62 Renmin Lu, Qingdao Shi
Shandong, 266033


????,
??????????????????????????????????????,
??????????????,??????????????????.
??????????10??????????????,??????
??????????????????????????????.


????

taozhi29480 at 163.com





From mistria at redhat.com  Thu Apr 16 04:42:31 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 16 Apr 2015 10:42:31 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Should there be 2 versions of
 javax.servlet in JBDS?
In-Reply-To: <552EDE7C.7040606@redhat.com>
References: <552EDE7C.7040606@redhat.com>
Message-ID: <552F75F7.8070906@redhat.com>

On 04/15/2015 11:56 PM, Nick Boldt wrote:
> Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> 3.1.0 in JBDS.
> More importantly... SHOULD we be including both? Or can we just include
> 3.1.0 and drop 3.0.0?
I have JBDS installed from installer, which basically ran a p2 director. 
And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving 
what to installed, p2 has to keep both versions of javax.servlet. That's 
definitely a sign that our dependency chain currently need both (or p2 
wouldn't have installed both).

So I've tried the ultimate test:
$ cd jbdevstudio-9.0.0.Alpha2/studio
$ rm plugins/javax.servlet_3.0.0*
$ ./jbdevstudio
And saw

!ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: 
org.jboss.tools.ws.ui [967]
   Unresolved requirement: Import-Package: javax.servlet; 
version="[2.4.0,3.0.0)"

     at org.eclipse.osgi.container.Module.start(Module.java:434)
     at 
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
     at 
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
     at 
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
     at 
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
     at 
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
     at 
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
     at 
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)


Fun thing is that the javax.servlet_3.0.0 actually exports packages in 
version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.

I've put that in a Jira https://issues.jboss.org/browse/JBIDE-19605
-- 
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/20150416/06aff16d/attachment.html 

From nboldt at redhat.com  Thu Apr 16 09:33:07 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 16 Apr 2015 09:33:07 -0400
Subject: [jbosstools-dev] Creation of pom.xml property for
 skipTestOrITest for parent pom.xml
In-Reply-To: <B37867FC-4B86-41FD-85F0-8B8060D9F0F4@redhat.com>
References: <552F061D.1030208@redhat.com>
	<B37867FC-4B86-41FD-85F0-8B8060D9F0F4@redhat.com>
Message-ID: <552FBA13.5090401@redhat.com>

It's simply the code snippet below, but then you use 
<skip>${skipTestOrITest}</skip> in your poms, instead of 
<skip>${skipITest}</skip>.

Simple, no?

Related: gentlemen, start your "I don't like the variable name / case of 
the variable" engines. :D


On 04/16/2015 01:35 AM, Max Rydahl Andersen wrote:
> Got a PR to look at ?
>
> /max
> http://about.me/maxandersen
>
>
>> On 16 Apr 2015, at 02:45, Rob Stryker <rstryker at redhat.com> wrote:
>>
>> My jboss/wf runtimes are being downloaded via my integration tests, even
>> when -DskipTests is selected, because my integration test pom.xml has
>> <skip>${skipITests}</skip> in it.  Until now, there was no easily
>> recognized way to make a new property that could 'or' skipTests with
>> skipITests.
>>
>> So I've added this to my pom in one of my topic branches, and it seems
>> to work exactly how we'd want it to. It basically functions via a regex,
>> puts ${skipTests}${skipITests}, and performs a regex replacement to make
>> the value either "true" or blank. This property can later be used in my
>> <skip> section.
>>
>> If anyone thinks this property should be available for parent pom, I'd
>> suggest you take it and make it available to all other modules who might
>> have integration tests with heavy dependencies.
>>
>> Otherwise, I'll just keep it in my local pom for my itests.
>>
>>              <plugin>
>>                  <groupId>org.codehaus.mojo</groupId>
>> <artifactId>build-helper-maven-plugin</artifactId>
>>                  <version>1.7</version>
>>                  <executions>
>>                      <execution>
>>                          <id>regex-property</id>
>>                          <goals>
>>                              <goal>regex-property</goal>
>>                          </goals>
>>                          <configuration>
>>                              <name>skipTestOrITest</name>
>> <value>${skipTests}${skipITests}</value>
>> <regex>((..skipTests.)?(true)?((..skipITests.)|(null)|(true)|(false))?)</regex>
>> <replacement>$3</replacement>
>> <failIfNoMatch>false</failIfNoMatch>
>>                          </configuration>
>>                      </execution>
>>                      </executions>
>>                    </plugin>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

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

From nboldt at redhat.com  Thu Apr 16 12:32:05 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 16 Apr 2015 12:32:05 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Alpha2 Code Freeze is TODAY
	(April 16, 2015)
Message-ID: <552FE405.9010506@redhat.com>

Please perform the steps in these task jiras to prepare yourself for 
code freeze.

If you need more time (eg., another day) before you can branch, please 
let me know.

JBoss Tools       : https://issues.jboss.org/browse/JBIDE-19608
Aerogear          : https://issues.jboss.org/browse/JBIDE-19609
JBT Update Sites  : https://issues.jboss.org/browse/JBIDE-19610
VPE               : https://issues.jboss.org/browse/JBIDE-19611
Central Discovery : https://issues.jboss.org/browse/JBIDE-19612
Server            : https://issues.jboss.org/browse/JBIDE-19613
Hibernate         : https://issues.jboss.org/browse/JBIDE-19614
Base              : https://issues.jboss.org/browse/JBIDE-19615
OpenShift         : https://issues.jboss.org/browse/JBIDE-19616
JavaEE            : https://issues.jboss.org/browse/JBIDE-19617
JST               : https://issues.jboss.org/browse/JBIDE-19618
Forge             : https://issues.jboss.org/browse/JBIDE-19619
Birt              : https://issues.jboss.org/browse/JBIDE-19620
BrowserSim        : https://issues.jboss.org/browse/JBIDE-19621
Webservices       : https://issues.jboss.org/browse/JBIDE-19622
Arquillian        : https://issues.jboss.org/browse/JBIDE-19623
Central           : https://issues.jboss.org/browse/JBIDE-19624
LiveReload        : https://issues.jboss.org/browse/JBIDE-19625


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

From snjezana.peco at redhat.com  Thu Apr 16 13:33:48 2015
From: snjezana.peco at redhat.com (Snjezana Peco)
Date: Thu, 16 Apr 2015 19:33:48 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Alpha2 Code Freeze is TODAY
 (April 16, 2015)
In-Reply-To: <552FE405.9010506@redhat.com>
References: <552FE405.9010506@redhat.com>
Message-ID: <552FF27C.1040100@redhat.com>

Done for arquillian and birt.

Snjeza

On 4/16/2015 6:32 PM, Nick Boldt wrote:
> Please perform the steps in these task jiras to prepare yourself for
> code freeze.
>
> If you need more time (eg., another day) before you can branch, please
> let me know.
>
> JBoss Tools       : https://issues.jboss.org/browse/JBIDE-19608
> Aerogear          : https://issues.jboss.org/browse/JBIDE-19609
> JBT Update Sites  : https://issues.jboss.org/browse/JBIDE-19610
> VPE               : https://issues.jboss.org/browse/JBIDE-19611
> Central Discovery : https://issues.jboss.org/browse/JBIDE-19612
> Server            : https://issues.jboss.org/browse/JBIDE-19613
> Hibernate         : https://issues.jboss.org/browse/JBIDE-19614
> Base              : https://issues.jboss.org/browse/JBIDE-19615
> OpenShift         : https://issues.jboss.org/browse/JBIDE-19616
> JavaEE            : https://issues.jboss.org/browse/JBIDE-19617
> JST               : https://issues.jboss.org/browse/JBIDE-19618
> Forge             : https://issues.jboss.org/browse/JBIDE-19619
> Birt              : https://issues.jboss.org/browse/JBIDE-19620
> BrowserSim        : https://issues.jboss.org/browse/JBIDE-19621
> Webservices       : https://issues.jboss.org/browse/JBIDE-19622
> Arquillian        : https://issues.jboss.org/browse/JBIDE-19623
> Central           : https://issues.jboss.org/browse/JBIDE-19624
> LiveReload        : https://issues.jboss.org/browse/JBIDE-19625
>
>


From mistria at redhat.com  Thu Apr 16 14:46:27 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 16 Apr 2015 20:46:27 +0200
Subject: [jbosstools-dev] Blocker bug in JBoss Tools 4.3.0.Alpha2
Message-ID: <55300383.8080507@redhat.com>

User cannot select which workspace to use, default one $HOME/workspace 
always used: see https://issues.jboss.org/browse/JBIDE-19627
-- 
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/20150416/8d754db6/attachment.html 

From mistria at redhat.com  Thu Apr 16 15:09:25 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 16 Apr 2015 21:09:25 +0200
Subject: [jbosstools-dev] Target Platform 4.50.0.Alpha2 for JBoss Tools
 4.3.0.Alpha2 has been released.
Message-ID: <553008E5.9050200@redhat.com>

Target Platform 4.50.0.Alpha2 for JBoss Tools 4.3.0.Alpha2 has been 
released.

Changes (compared to 4.50.0.Alpha1)
=======

* JBDS-3259: Mylyn wikitext
* JBIDE-19497: Replaced Jetty 8 by Jetty 9.2.5
* JBIDE-19539: Mars M6
* JBIDE-19585: Jetty 9.2.9
* JBDS-3285: Easymport dependencies


Usage
=====

Target platform  4.50.0.Alpha2 is what JBoss Tools 4.3.0.Alpha2 will use.

All Jenkins jobs for branch jbosstools-4.3.0.Alpha2x and parent pom 
4.3.0.Alpha2-SNAPSHOT have been updated to use target platform 
4.50.0.Alpha2.

The following p2 repositories *will be modified* to point to this new 
target platform once JBoss Tools 4.3.0.Alpha2 is released:
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/
* 
http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/luna/

Until then, you can access the target platform at the URLs below.


Download
========

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

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

If your root pom correctly specifies the latest parent pom version as 
4.3.0.Alpha2-SNAPSHOT, you need only this:
   $ mvn clean verify
If you're using a different parent pom, use this:
   $ mvn clean verify -Dtpc.version=4.50.0.Alpha2

For advanced usage and help (using in IDE, building a mirror locally, 
using a zip), see 
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.md


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

jbosstools-target-platforms project branch 4.50.x has been prepared for 
potential upgrades, and its version is now 4.50.0.Beta1-SNAPSHOT.  We 
can at least expect for Beta1:
* Move to Mars M7 or some Mars RC
* Update of tern.java
* Shall you need anything else, please follow those instructions to 
request a change ASAP: 
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc

All Jenkins jobs for *master* and parent pom 4.3.0.Beta1-SNAPSHOT have 
been updated to use target platform 4.50.0.Beta1-SNAPSHOT.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150416/dbc380be/attachment-0001.html 

From akazakov at exadel.com  Thu Apr 16 16:09:04 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 16 Apr 2015 13:09:04 -0700
Subject: [jbosstools-dev] ACTION REQUIRED: Alpha2 Code Freeze is TODAY
 (April 16, 2015)
In-Reply-To: <552FE405.9010506@redhat.com>
References: <552FE405.9010506@redhat.com>
Message-ID: <553016E0.5040908@exadel.com>

Done for base, jst, javaee.
But I had to branch jst and javaee blindly because Aplha1 build is 
failing for them right now: 
https://issues.jboss.org/browse/JBIDE-19618?focusedCommentId=13059851&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13059851

There is something wrong that we can't build the code freeze branch (I 
need to test it locally before pushing to master) on the day of code 
freeze and have to wait until all components which you depend on are 
branched/built and published on our jenkins.


On 04/16/2015 09:32 AM, Nick Boldt wrote:
> Please perform the steps in these task jiras to prepare yourself for
> code freeze.
>
> If you need more time (eg., another day) before you can branch, please
> let me know.
>
> JBoss Tools       : https://issues.jboss.org/browse/JBIDE-19608
> Aerogear          : https://issues.jboss.org/browse/JBIDE-19609
> JBT Update Sites  : https://issues.jboss.org/browse/JBIDE-19610
> VPE               : https://issues.jboss.org/browse/JBIDE-19611
> Central Discovery : https://issues.jboss.org/browse/JBIDE-19612
> Server            : https://issues.jboss.org/browse/JBIDE-19613
> Hibernate         : https://issues.jboss.org/browse/JBIDE-19614
> Base              : https://issues.jboss.org/browse/JBIDE-19615
> OpenShift         : https://issues.jboss.org/browse/JBIDE-19616
> JavaEE            : https://issues.jboss.org/browse/JBIDE-19617
> JST               : https://issues.jboss.org/browse/JBIDE-19618
> Forge             : https://issues.jboss.org/browse/JBIDE-19619
> Birt              : https://issues.jboss.org/browse/JBIDE-19620
> BrowserSim        : https://issues.jboss.org/browse/JBIDE-19621
> Webservices       : https://issues.jboss.org/browse/JBIDE-19622
> Arquillian        : https://issues.jboss.org/browse/JBIDE-19623
> Central           : https://issues.jboss.org/browse/JBIDE-19624
> LiveReload        : https://issues.jboss.org/browse/JBIDE-19625
>
>


From nboldt at redhat.com  Thu Apr 16 16:13:00 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 16 Apr 2015 16:13:00 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Alpha2 Code Freeze is TODAY
 (April 16, 2015)
In-Reply-To: <553016E0.5040908@exadel.com>
References: <552FE405.9010506@redhat.com> <553016E0.5040908@exadel.com>
Message-ID: <553017CC.4060208@redhat.com>

Open to suggestions for how to make the upstream components already 
built before they're branched. Do you want me to bootstrap with the 
previous milestone so you're building against Alpha1 bits instead of 
Alpha2 ones?

Also wondering why, if your sources in master are building blue, you're 
worried they'll suddenly be red when all you've done is create a branch 
point. Surely if your master job is blue you can branch safely?

N

On 04/16/2015 04:09 PM, Alexey Kazakov wrote:
> Done for base, jst, javaee.
> But I had to branch jst and javaee blindly because Aplha1 build is
> failing for them right now:
> https://issues.jboss.org/browse/JBIDE-19618?focusedCommentId=13059851&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13059851
>
> There is something wrong that we can't build the code freeze branch (I
> need to test it locally before pushing to master) on the day of code
> freeze and have to wait until all components which you depend on are
> branched/built and published on our jenkins.
>
>
> On 04/16/2015 09:32 AM, Nick Boldt wrote:
>> Please perform the steps in these task jiras to prepare yourself for
>> code freeze.
>>
>> If you need more time (eg., another day) before you can branch, please
>> let me know.
>>
>> JBoss Tools       : https://issues.jboss.org/browse/JBIDE-19608
>> Aerogear          : https://issues.jboss.org/browse/JBIDE-19609
>> JBT Update Sites  : https://issues.jboss.org/browse/JBIDE-19610
>> VPE               : https://issues.jboss.org/browse/JBIDE-19611
>> Central Discovery : https://issues.jboss.org/browse/JBIDE-19612
>> Server            : https://issues.jboss.org/browse/JBIDE-19613
>> Hibernate         : https://issues.jboss.org/browse/JBIDE-19614
>> Base              : https://issues.jboss.org/browse/JBIDE-19615
>> OpenShift         : https://issues.jboss.org/browse/JBIDE-19616
>> JavaEE            : https://issues.jboss.org/browse/JBIDE-19617
>> JST               : https://issues.jboss.org/browse/JBIDE-19618
>> Forge             : https://issues.jboss.org/browse/JBIDE-19619
>> Birt              : https://issues.jboss.org/browse/JBIDE-19620
>> BrowserSim        : https://issues.jboss.org/browse/JBIDE-19621
>> Webservices       : https://issues.jboss.org/browse/JBIDE-19622
>> Arquillian        : https://issues.jboss.org/browse/JBIDE-19623
>> Central           : https://issues.jboss.org/browse/JBIDE-19624
>> LiveReload        : https://issues.jboss.org/browse/JBIDE-19625
>>
>>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

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

From pleacu at redhat.com  Thu Apr 16 16:17:50 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Thu, 16 Apr 2015 16:17:50 -0400 (EDT)
Subject: [jbosstools-dev] JBDSIS 8.0.1.GA/ JBTIS 4.2.1.Final now live
In-Reply-To: <1292605141.10796511.1428499191314.JavaMail.zimbra@redhat.com>
Message-ID: <1038853389.1292615.1429215470551.JavaMail.zimbra@redhat.com>


   Greetings,
      The latest Eclipse-Luna capable, JBDS 8.1.0.GA compatible Integration Stack GA tooling is
   released.  This release contains the productized BRMS/BPMS tooling featuring updated versions
   of the following components:

   * BPMN2 Modeler  1.1.2.Final_1.1.0.Final_luna
   * Drools/jBPM6   6.2.0.Final
   * ESB            1.5.530.Final
   * Fuse Tooling   7.3.0.Beta3
   * SwitchYard     2.0.0.CR1

   JBDSIS 8.0.1.GA, JBTIS 4.2.1.Final

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

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

      3. Select the Software/Update tab in the JBoss Central view.  

      done!

   The standard p2 installer is available for JBDSIS (.GA):

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

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

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

   The standard p2 installer is available for JBTIS (.Final):

      * Start eclipse-with-jboss-tools, then:
          Help > Install New Software...
          Add...

          - use this for 'Location:' for the released-components integration stack:
            http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/

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

   JBoss Central is supported for JBTIS (.Final):

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

      * Use JBoss Central - community bits are live
        ./eclipse

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

      1. https://devstudio.redhat.com/updates/8.0.0/jbdevstudio-integration-stack-updatesite-8.0.1.GA.zip
         https://devstudio.redhat.com/updates/8.0.0/jbdevstudio-integration-stack-updatesite-8.0.1.GA.zip.MD5

      2. https://devstudio.redhat.com/updates/8.0.0/jbdevstudio-integration-stack-updatesite-8.0.1.GA-earlyaccess.zip
         https://devstudio.redhat.com/updates/8.0.0/jbdevstudio-integration-stack-updatesite-8.0.1.GA-earlyaccess.zip.MD5

      3. http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.0.Final.zip
         http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.0.Final.zip.MD5

      4. http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.1.Final-earlyaccess.zip
         http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.1.Final-earlyaccess.zip.MD5

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

      - Full and candidate release target platforms including early access dependencies:
      https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.2.Final/  # note -ea target files
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.2.Final/jbtis/REPO/
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.2.Final/jbtis/earlyaccess/REPO/
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.2.Final/jbdsis/REPO/
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.2.Final/jbdsis/earlyaccess/REPO/

   Blog pending...

   Give it a try!
         --paull

From akazakov at exadel.com  Thu Apr 16 16:34:21 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 16 Apr 2015 13:34:21 -0700
Subject: [jbosstools-dev] ACTION REQUIRED: Alpha2 Code Freeze is TODAY
 (April 16, 2015)
In-Reply-To: <553017CC.4060208@redhat.com>
References: <552FE405.9010506@redhat.com> <553016E0.5040908@exadel.com>
	<553017CC.4060208@redhat.com>
Message-ID: <55301CCD.4090208@exadel.com>



On 04/16/2015 01:13 PM, Nick Boldt wrote:
> Open to suggestions for how to make the upstream components already
> built before they're branched. Do you want me to bootstrap with the
> previous milestone so you're building against Alpha1 bits instead of
> Alpha2 ones?
>
> Also wondering why, if your sources in master are building blue, you're
> worried they'll suddenly be red when all you've done is create a branch
> point. Surely if your master job is blue you can branch safely?
Then our Jira descriptions for code freezes are not correct since they 
tell component leads to verify the build is working/no test failures 
BEFORE brahcning:
3. Ensure you've built & run your plugin tests using the latest target 
platform version 4.50.0.Alpha2;

mvn clean verify -Dtpc.version=4.50.0.Alpha2

from https://issues.jboss.org/browse/JBIDE-19608
Anyway, if I need to test any last minute changes or the new target 
platform, whatever. I cannot do it for the upcoming version which we are 
code freezing. I can do it for master only.

And BTW I have never faced this problem before. Did we change anything?



> N
>
> On 04/16/2015 04:09 PM, Alexey Kazakov wrote:
>> Done for base, jst, javaee.
>> But I had to branch jst and javaee blindly because Aplha1 build is
>> failing for them right now:
>> https://issues.jboss.org/browse/JBIDE-19618?focusedCommentId=13059851&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13059851
>>
>> There is something wrong that we can't build the code freeze branch (I
>> need to test it locally before pushing to master) on the day of code
>> freeze and have to wait until all components which you depend on are
>> branched/built and published on our jenkins.
>>
>>
>> On 04/16/2015 09:32 AM, Nick Boldt wrote:
>>> Please perform the steps in these task jiras to prepare yourself for
>>> code freeze.
>>>
>>> If you need more time (eg., another day) before you can branch, please
>>> let me know.
>>>
>>> JBoss Tools       : https://issues.jboss.org/browse/JBIDE-19608
>>> Aerogear          : https://issues.jboss.org/browse/JBIDE-19609
>>> JBT Update Sites  : https://issues.jboss.org/browse/JBIDE-19610
>>> VPE               : https://issues.jboss.org/browse/JBIDE-19611
>>> Central Discovery : https://issues.jboss.org/browse/JBIDE-19612
>>> Server            : https://issues.jboss.org/browse/JBIDE-19613
>>> Hibernate         : https://issues.jboss.org/browse/JBIDE-19614
>>> Base              : https://issues.jboss.org/browse/JBIDE-19615
>>> OpenShift         : https://issues.jboss.org/browse/JBIDE-19616
>>> JavaEE            : https://issues.jboss.org/browse/JBIDE-19617
>>> JST               : https://issues.jboss.org/browse/JBIDE-19618
>>> Forge             : https://issues.jboss.org/browse/JBIDE-19619
>>> Birt              : https://issues.jboss.org/browse/JBIDE-19620
>>> BrowserSim        : https://issues.jboss.org/browse/JBIDE-19621
>>> Webservices       : https://issues.jboss.org/browse/JBIDE-19622
>>> Arquillian        : https://issues.jboss.org/browse/JBIDE-19623
>>> Central           : https://issues.jboss.org/browse/JBIDE-19624
>>> LiveReload        : https://issues.jboss.org/browse/JBIDE-19625
>>>
>>>
>> _______________________________________________
>> 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/20150416/21866b27/attachment.html 

From manderse at redhat.com  Thu Apr 16 16:39:07 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 16 Apr 2015 22:39:07 +0200
Subject: [jbosstools-dev] Creation of pom.xml property for
 skipTestOrITest for parent pom.xml
In-Reply-To: <552FBA13.5090401@redhat.com>
References: <552F061D.1030208@redhat.com>
	<B37867FC-4B86-41FD-85F0-8B8060D9F0F4@redhat.com>
	<552FBA13.5090401@redhat.com>
Message-ID: <C55F162F-0FE4-4AB0-A720-5930764CB86C@redhat.com>

On 16 Apr 2015, at 15:33, Nick Boldt wrote:

> It's simply the code snippet below, but then you use
> <skip>${skipTestOrITest}</skip> in your poms, instead of
> <skip>${skipITest}</skip>.

if that is the case why even rename it.

I'm just asking for a PR so there is no confusion. much easier than long 
email explanation
and me trying to reproduce it and then not do it the same way he did.

/max

>
> Simple, no?
>
> Related: gentlemen, start your "I don't like the variable name / case 
> of
> the variable" engines. :D
>
>
> On 04/16/2015 01:35 AM, Max Rydahl Andersen wrote:
>> Got a PR to look at ?
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>>> On 16 Apr 2015, at 02:45, Rob Stryker <rstryker at redhat.com> wrote:
>>>
>>> My jboss/wf runtimes are being downloaded via my integration tests, 
>>> even
>>> when -DskipTests is selected, because my integration test pom.xml 
>>> has
>>> <skip>${skipITests}</skip> in it.  Until now, there was no easily
>>> recognized way to make a new property that could 'or' skipTests with
>>> skipITests.
>>>
>>> So I've added this to my pom in one of my topic branches, and it 
>>> seems
>>> to work exactly how we'd want it to. It basically functions via a 
>>> regex,
>>> puts ${skipTests}${skipITests}, and performs a regex replacement to 
>>> make
>>> the value either "true" or blank. This property can later be used in 
>>> my
>>> <skip> section.
>>>
>>> If anyone thinks this property should be available for parent pom, 
>>> I'd
>>> suggest you take it and make it available to all other modules who 
>>> might
>>> have integration tests with heavy dependencies.
>>>
>>> Otherwise, I'll just keep it in my local pom for my itests.
>>>
>>>           <plugin>
>>>               <groupId>org.codehaus.mojo</groupId>
>>> <artifactId>build-helper-maven-plugin</artifactId>
>>>               <version>1.7</version>
>>>               <executions>
>>>                   <execution>
>>>                       <id>regex-property</id>
>>>                       <goals>
>>>                           <goal>regex-property</goal>
>>>                       </goals>
>>>                       <configuration>
>>>                           <name>skipTestOrITest</name>
>>> <value>${skipTests}${skipITests}</value>
>>> <regex>((..skipTests.)?(true)?((..skipITests.)|(null)|(true)|(false))?)</regex>
>>> <replacement>$3</replacement>
>>> <failIfNoMatch>false</failIfNoMatch>
>>>                       </configuration>
>>>                   </execution>
>>>                   </executions>
>>>                 </plugin>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From manderse at redhat.com  Thu Apr 16 16:44:25 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 16 Apr 2015 22:44:25 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Alpha2 Code Freeze is TODAY
 (April 16, 2015)
In-Reply-To: <55301CCD.4090208@exadel.com>
References: <552FE405.9010506@redhat.com> <553016E0.5040908@exadel.com>
	<553017CC.4060208@redhat.com> <55301CCD.4090208@exadel.com>
Message-ID: <02A89935-E834-40AE-978F-C535DCF49B00@redhat.com>

yeah - the refactoring of build structure makes it fail.

we can't verify the build before branch.

branched for web services since xcoulon is not awake now.

> On 04/16/2015 01:13 PM, Nick Boldt wrote:
>> Open to suggestions for how to make the upstream components already
>> built before they're branched. Do you want me to bootstrap with the
>> previous milestone so you're building against Alpha1 bits instead of
>> Alpha2 ones?
>>
>> Also wondering why, if your sources in master are building blue, 
>> you're
>> worried they'll suddenly be red when all you've done is create a 
>> branch
>> point. Surely if your master job is blue you can branch safely?
> Then our Jira descriptions for code freezes are not correct since they 
> tell component leads to verify the build is working/no test failures 
> BEFORE brahcning:
> 3. Ensure you've built & run your plugin tests using the latest target 
> platform version 4.50.0.Alpha2;
>
> mvn clean verify -Dtpc.version=4.50.0.Alpha2
>
> from https://issues.jboss.org/browse/JBIDE-19608
> Anyway, if I need to test any last minute changes or the new target 
> platform, whatever. I cannot do it for the upcoming version which we 
> are code freezing. I can do it for master only.
>
> And BTW I have never faced this problem before. Did we change 
> anything?
>
>
>
>> N
>>
>> On 04/16/2015 04:09 PM, Alexey Kazakov wrote:
>>> Done for base, jst, javaee.
>>> But I had to branch jst and javaee blindly because Aplha1 build is
>>> failing for them right now:
>>> https://issues.jboss.org/browse/JBIDE-19618?focusedCommentId=13059851&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13059851
>>>
>>> There is something wrong that we can't build the code freeze branch 
>>> (I
>>> need to test it locally before pushing to master) on the day of code
>>> freeze and have to wait until all components which you depend on are
>>> branched/built and published on our jenkins.
>>>
>>>
>>> On 04/16/2015 09:32 AM, Nick Boldt wrote:
>>>> Please perform the steps in these task jiras to prepare yourself 
>>>> for
>>>> code freeze.
>>>>
>>>> If you need more time (eg., another day) before you can branch, 
>>>> please
>>>> let me know.
>>>>
>>>> JBoss Tools       : https://issues.jboss.org/browse/JBIDE-19608
>>>> Aerogear          : https://issues.jboss.org/browse/JBIDE-19609
>>>> JBT Update Sites  : https://issues.jboss.org/browse/JBIDE-19610
>>>> VPE               : https://issues.jboss.org/browse/JBIDE-19611
>>>> Central Discovery : https://issues.jboss.org/browse/JBIDE-19612
>>>> Server            : https://issues.jboss.org/browse/JBIDE-19613
>>>> Hibernate         : https://issues.jboss.org/browse/JBIDE-19614
>>>> Base              : https://issues.jboss.org/browse/JBIDE-19615
>>>> OpenShift         : https://issues.jboss.org/browse/JBIDE-19616
>>>> JavaEE            : https://issues.jboss.org/browse/JBIDE-19617
>>>> JST               : https://issues.jboss.org/browse/JBIDE-19618
>>>> Forge             : https://issues.jboss.org/browse/JBIDE-19619
>>>> Birt              : https://issues.jboss.org/browse/JBIDE-19620
>>>> BrowserSim        : https://issues.jboss.org/browse/JBIDE-19621
>>>> Webservices       : https://issues.jboss.org/browse/JBIDE-19622
>>>> Arquillian        : https://issues.jboss.org/browse/JBIDE-19623
>>>> Central           : https://issues.jboss.org/browse/JBIDE-19624
>>>> LiveReload        : https://issues.jboss.org/browse/JBIDE-19625
>>>>
>>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From nboldt at redhat.com  Thu Apr 16 17:16:58 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 16 Apr 2015 17:16:58 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Alpha2 Code Freeze is TODAY
 (April 16, 2015)
In-Reply-To: <02A89935-E834-40AE-978F-C535DCF49B00@redhat.com>
References: <552FE405.9010506@redhat.com>
	<553016E0.5040908@exadel.com>	<553017CC.4060208@redhat.com>
	<55301CCD.4090208@exadel.com>
	<02A89935-E834-40AE-978F-C535DCF49B00@redhat.com>
Message-ID: <553026CA.1030908@redhat.com>

To work around build problems due to missing upstream bootstrapped 
builds, the Alpha2 parent pom now uses jbosstools_site_stream=master so 
you'll be able to resolve your upstream bits from their already-built 
master URLs, instead of failing to resolve their 4.3.mars counterparts 
(until they're built). (You can also do this via the commandline with 
mvn install -Djbosstools_site_stream=master or 
-Djbosstools_site_stream=4.3.mars )

One additional step I forgot to mention in the task jiras:

* please bump your root poms in master branch to use parent pom 
4.3.0.Beta1-SNAPSHOT.

So far, 5 of projects correctly deduced they should do this 
automatically, but the remaining ones still need a reminder.

aerogear
arquillian
birt
browsersim
central
forge
freemarker
hibernate
openshift
server
vpe

Cheers,

On 04/16/2015 04:44 PM, Max Rydahl Andersen wrote:
> yeah - the refactoring of build structure makes it fail.
>
> we can't verify the build before branch.
>
> branched for web services since xcoulon is not awake now.
>
>> On 04/16/2015 01:13 PM, Nick Boldt wrote:
>>> Open to suggestions for how to make the upstream components already
>>> built before they're branched. Do you want me to bootstrap with the
>>> previous milestone so you're building against Alpha1 bits instead of
>>> Alpha2 ones?
>>>
>>> Also wondering why, if your sources in master are building blue,
>>> you're
>>> worried they'll suddenly be red when all you've done is create a
>>> branch
>>> point. Surely if your master job is blue you can branch safely?
>> Then our Jira descriptions for code freezes are not correct since they
>> tell component leads to verify the build is working/no test failures
>> BEFORE brahcning:
>> 3. Ensure you've built & run your plugin tests using the latest target
>> platform version 4.50.0.Alpha2;
>>
>> mvn clean verify -Dtpc.version=4.50.0.Alpha2
>>
>> from https://issues.jboss.org/browse/JBIDE-19608
>> Anyway, if I need to test any last minute changes or the new target
>> platform, whatever. I cannot do it for the upcoming version which we
>> are code freezing. I can do it for master only.
>>
>> And BTW I have never faced this problem before. Did we change
>> anything?
>>
>>
>>
>>> N
>>>
>>> On 04/16/2015 04:09 PM, Alexey Kazakov wrote:
>>>> Done for base, jst, javaee.
>>>> But I had to branch jst and javaee blindly because Aplha1 build is
>>>> failing for them right now:
>>>> https://issues.jboss.org/browse/JBIDE-19618?focusedCommentId=13059851&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13059851
>>>>
>>>> There is something wrong that we can't build the code freeze branch
>>>> (I
>>>> need to test it locally before pushing to master) on the day of code
>>>> freeze and have to wait until all components which you depend on are
>>>> branched/built and published on our jenkins.
>>>>
>>>>
>>>> On 04/16/2015 09:32 AM, Nick Boldt wrote:
>>>>> Please perform the steps in these task jiras to prepare yourself
>>>>> for
>>>>> code freeze.
>>>>>
>>>>> If you need more time (eg., another day) before you can branch,
>>>>> please
>>>>> let me know.
>>>>>
>>>>> JBoss Tools       : https://issues.jboss.org/browse/JBIDE-19608
>>>>> Aerogear          : https://issues.jboss.org/browse/JBIDE-19609
>>>>> JBT Update Sites  : https://issues.jboss.org/browse/JBIDE-19610
>>>>> VPE               : https://issues.jboss.org/browse/JBIDE-19611
>>>>> Central Discovery : https://issues.jboss.org/browse/JBIDE-19612
>>>>> Server            : https://issues.jboss.org/browse/JBIDE-19613
>>>>> Hibernate         : https://issues.jboss.org/browse/JBIDE-19614
>>>>> Base              : https://issues.jboss.org/browse/JBIDE-19615
>>>>> OpenShift         : https://issues.jboss.org/browse/JBIDE-19616
>>>>> JavaEE            : https://issues.jboss.org/browse/JBIDE-19617
>>>>> JST               : https://issues.jboss.org/browse/JBIDE-19618
>>>>> Forge             : https://issues.jboss.org/browse/JBIDE-19619
>>>>> Birt              : https://issues.jboss.org/browse/JBIDE-19620
>>>>> BrowserSim        : https://issues.jboss.org/browse/JBIDE-19621
>>>>> Webservices       : https://issues.jboss.org/browse/JBIDE-19622
>>>>> Arquillian        : https://issues.jboss.org/browse/JBIDE-19623
>>>>> Central           : https://issues.jboss.org/browse/JBIDE-19624
>>>>> LiveReload        : https://issues.jboss.org/browse/JBIDE-19625
>>>>>
>>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

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

From manderse at redhat.com  Fri Apr 17 03:00:39 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Fri, 17 Apr 2015 03:00:39 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 3 issues with no component
Message-ID: <201504170700.t3H70dqK028022@int-mx11.intmail.prod.int.phx2.redhat.com>


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

 
* No component for JBIDE-19590

https://issues.jboss.org/browse/JBIDE-19590
Summary: Update module's README.md files with information about dependencies to other modules

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

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


* No component for JBIDE-19627

https://issues.jboss.org/browse/JBIDE-19627
Summary: JBoss Tools disables ability to select workspace

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

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


* No component for JBDS-3407

https://issues.jboss.org/browse/JBDS-3407
Summary: Not able to create  'non-bare' repository in JBDS 8.1. 

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

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



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

From manderse at redhat.com  Fri Apr 17 05:14:38 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Fri, 17 Apr 2015 05:14:38 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 3 issues with no component
Message-ID: <201504170914.t3H9Ecu2012653@int-mx10.intmail.prod.int.phx2.redhat.com>


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

 
* No component for JBIDE-19590

https://issues.jboss.org/browse/JBIDE-19590
Summary: Update module's README.md files with information about dependencies to other modules

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please ensure this issue has a proper component set.
Last Update: 1 day, 21:23:24.124319

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


* No component for JBIDE-19627

https://issues.jboss.org/browse/JBIDE-19627
Summary: JBoss Tools disables ability to select workspace

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please ensure this issue has a proper component set.
Last Update: 12:50:27.124023

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


* No component for JBDS-3407

https://issues.jboss.org/browse/JBDS-3407
Summary: Not able to create  'non-bare' repository in JBDS 8.1. 

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please ensure this issue has a proper component set.
Last Update: 2 days, 1:01:15.124514

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



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

From rstryker at redhat.com  Fri Apr 17 11:27:32 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Fri, 17 Apr 2015 11:27:32 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Should there be 2 versions of
 javax.servlet in JBDS?
In-Reply-To: <552F75F7.8070906@redhat.com>
References: <552EDE7C.7040606@redhat.com> <552F75F7.8070906@redhat.com>
Message-ID: <55312664.9020505@redhat.com>

Couldn't org.jboss.tools.ws.ui  just expand their version range now?

On 04/16/2015 04:42 AM, Mickael Istria wrote:
> org.jboss.tools.ws.ui 

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

From rstryker at redhat.com  Fri Apr 17 11:34:17 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Fri, 17 Apr 2015 11:34:17 -0400
Subject: [jbosstools-dev] Creation of pom.xml property for
 skipTestOrITest for parent pom.xml
In-Reply-To: <C55F162F-0FE4-4AB0-A720-5930764CB86C@redhat.com>
References: <552F061D.1030208@redhat.com>	<B37867FC-4B86-41FD-85F0-8B8060D9F0F4@redhat.com>	<552FBA13.5090401@redhat.com>
	<C55F162F-0FE4-4AB0-A720-5930764CB86C@redhat.com>
Message-ID: <553127F9.70603@redhat.com>

I don't have a PR for putting it in parent pom.  If you want to see it 
in action for me, then here it is:

https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/pom.xml#L53



On 04/16/2015 04:39 PM, Max Rydahl Andersen wrote:
> On 16 Apr 2015, at 15:33, Nick Boldt wrote:
>
>> It's simply the code snippet below, but then you use
>> <skip>${skipTestOrITest}</skip> in your poms, instead of
>> <skip>${skipITest}</skip>.
> if that is the case why even rename it.
>
> I'm just asking for a PR so there is no confusion. much easier than long
> email explanation
> and me trying to reproduce it and then not do it the same way he did.
>
> /max
>
>> Simple, no?
>>
>> Related: gentlemen, start your "I don't like the variable name / case
>> of
>> the variable" engines. :D
>>
>>
>> On 04/16/2015 01:35 AM, Max Rydahl Andersen wrote:
>>> Got a PR to look at ?
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>>
>>>> On 16 Apr 2015, at 02:45, Rob Stryker <rstryker at redhat.com> wrote:
>>>>
>>>> My jboss/wf runtimes are being downloaded via my integration tests,
>>>> even
>>>> when -DskipTests is selected, because my integration test pom.xml
>>>> has
>>>> <skip>${skipITests}</skip> in it.  Until now, there was no easily
>>>> recognized way to make a new property that could 'or' skipTests with
>>>> skipITests.
>>>>
>>>> So I've added this to my pom in one of my topic branches, and it
>>>> seems
>>>> to work exactly how we'd want it to. It basically functions via a
>>>> regex,
>>>> puts ${skipTests}${skipITests}, and performs a regex replacement to
>>>> make
>>>> the value either "true" or blank. This property can later be used in
>>>> my
>>>> <skip> section.
>>>>
>>>> If anyone thinks this property should be available for parent pom,
>>>> I'd
>>>> suggest you take it and make it available to all other modules who
>>>> might
>>>> have integration tests with heavy dependencies.
>>>>
>>>> Otherwise, I'll just keep it in my local pom for my itests.
>>>>
>>>>            <plugin>
>>>>                <groupId>org.codehaus.mojo</groupId>
>>>> <artifactId>build-helper-maven-plugin</artifactId>
>>>>                <version>1.7</version>
>>>>                <executions>
>>>>                    <execution>
>>>>                        <id>regex-property</id>
>>>>                        <goals>
>>>>                            <goal>regex-property</goal>
>>>>                        </goals>
>>>>                        <configuration>
>>>>                            <name>skipTestOrITest</name>
>>>> <value>${skipTests}${skipITests}</value>
>>>> <regex>((..skipTests.)?(true)?((..skipITests.)|(null)|(true)|(false))?)</regex>
>>>> <replacement>$3</replacement>
>>>> <failIfNoMatch>false</failIfNoMatch>
>>>>                        </configuration>
>>>>                    </execution>
>>>>                    </executions>
>>>>                  </plugin>
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>> -- 
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From pleacu at redhat.com  Fri Apr 17 15:20:15 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Fri, 17 Apr 2015 15:20:15 -0400 (EDT)
Subject: [jbosstools-dev] New Mars JBTIS target platform available -
	JBTIS-TP-4.3.0.Alpha1a
In-Reply-To: <935189711.2208159.1429298160585.JavaMail.zimbra@redhat.com>
Message-ID: <799464436.2209240.1429298415320.JavaMail.zimbra@redhat.com>


   Greetings -
     A new Eclipse Mars/ JBDS 9 compatible JBTIS TP is available - 4.3.0.Alpha1a

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

   See Jira for details:

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

   Synopsis:
   1. Update to Mars M6
      http://download.jboss.org/jbosstools/updates/requirements/mars/201503291000-M6/
   3. Update JBoss Tools core TP to 4.50.0.Alpha2
   3. Update JBoss Tools core update site to 4.3.0.Alpha1
      http://download.jboss.org/jbosstools/static/releases/jbosstools-4.3.0.Alpha1-updatesite-core/
      http://download.jboss.org/jbosstools/static/releases/jbosstools-4.3.0.Alpha1-updatesite-coretests
   4. Update orbit requirements 
      http://download.jboss.org/jbosstools/updates/requirements/orbit/S20150316021154/

   Thanks,
     --paull

From manderse at redhat.com  Mon Apr 20 03:00:55 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Mon, 20 Apr 2015 03:00:55 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201504200700.t3K70tr4028780@int-mx09.intmail.prod.int.phx2.redhat.com>


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

 
* No component for JBDS-3415

https://issues.jboss.org/browse/JBDS-3415
Summary: Fuse JMX Navigator is not showing any local processes on windows

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

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



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

From nboldt at redhat.com  Mon Apr 20 01:54:06 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 20 Apr 2015 01:54:06 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Alpha2 bits available for
	QE testing
Message-ID: <5534947E.7050603@redhat.com>

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

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

Target platform:
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Alpha2 


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

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

--

Additional update sites:
* 
http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Alpha2/
* 
http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.Alpha2/
* 
http://download.jboss.org/jbosstools/mars/staging/updates/webtools/4.3.0.Alpha2/

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

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 bastian.ugimachi at gmail.com  Mon Apr 20 07:44:58 2015
From: bastian.ugimachi at gmail.com (Bastian Ugimachi)
Date: Mon, 20 Apr 2015 13:44:58 +0200
Subject: [jbosstools-dev] antlr packages and lib not exported in Hibernate
	Tools 4.0.1
Message-ID: <CAFEyyCJu+-LgoQ5HuCDhy9Kn9sPLSUB1+vOwoOD8-8BhLU=oQw@mail.gmail.com>

Dear all,

I am currently working on an Eclipse-Plugin that is built on top of the
Hibernate Tools project. For example, I am using the following statements
to get the AST of a named query:

try {
 HqlParser parser = HqlParser.getInstance(statementString);
 parser.statement();
} catch (RecognitionException | TokenStreamException e) {
 e.printStackTrace();
}
AST statementAst = parser.getAST();

For this to work well with Hibernate Tools Version 4.0.0, I added bundle
org.hibernate.eclipse.libs as required bundle to my plug-in configuration
(which resolved to
org.hibernate.eclipse.libs_4.0.0.Final-v20141016-1911-B82 so far).

However, I now updated to Hiberate Tools 4.0.1
(org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95). The problem I
have now is that the following imports cannot be resolved:
import antlr.RecognitionException;
import antlr.TokenStreamException;
import antlr.collections.AST;

The problem seems to arise from the fact, that in the new version's
MANIFEST.MF, the antlr... packages are not exported and
lib/hibernate/antlr-2.7.6.jar is not listed in the Bundle-ClassPath any
more (I reformatted both MANIFEST.MFs, that you can find attached, to allow
a convenient comparison). After manually adding the antlr-related entries
to the new version's MANIFEST.MF, my code works pretty well again.

My question is thus:
(a) Do you consider this to be a bug in the realease of Hibernate Tools
4.0.1?
(b) If yes for (a): Do you have an idea when this issue could be solved?
(c) If no for (a): Which alternative solution would you suggest? I mean,
manually editing the MANIFEST.MF of realeased plug-ins is not quite the
best practice, is it? I tried to manally add antlr-2.7.6.jar as library to
my project, which solved the compilation error, but yields a
java.lang.ClassNotFoundException: antlr.LLkParser cannot be found by
org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95

Any advice?

Thanks!
Bastian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150420/5801c890/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: B82_MANIFEST.MF
Type: application/octet-stream
Size: 16888 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150420/5801c890/attachment-0002.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: B95_MANIFEST.MF
Type: application/octet-stream
Size: 16511 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150420/5801c890/attachment-0003.obj 

From akazakov at exadel.com  Mon Apr 20 14:01:34 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Mon, 20 Apr 2015 11:01:34 -0700
Subject: [jbosstools-dev] antlr packages and lib not exported in
 Hibernate Tools 4.0.1
In-Reply-To: <CAFEyyCJu+-LgoQ5HuCDhy9Kn9sPLSUB1+vOwoOD8-8BhLU=oQw@mail.gmail.com>
References: <CAFEyyCJu+-LgoQ5HuCDhy9Kn9sPLSUB1+vOwoOD8-8BhLU=oQw@mail.gmail.com>
Message-ID: <55353EFE.6040702@exadel.com>


First at all, please create an issue in 
https://issues.jboss.org/browse/JBIDE to solve this problem in the next 
release.
A pull request for https://github.com/jbosstools/jbosstools-hibernate 
would be useful too :)

On 04/20/2015 04:44 AM, Bastian Ugimachi wrote:
>
> Dear all,
>
> I am currently working on an Eclipse-Plugin that is built on top of 
> the Hibernate Tools project. For example, I am using the following 
> statements to get the AST of a named query:
>
> try {
>  HqlParser parser = HqlParser.getInstance(statementString);
>  parser.statement();
> } catch (RecognitionException | TokenStreamException e) {
>  e.printStackTrace();
> }
> AST statementAst = parser.getAST();
>
> For this to work well with Hibernate Tools Version 4.0.0, I added 
> bundle org.hibernate.eclipse.libs as required bundle to my plug-in 
> configuration (which resolved to 
> org.hibernate.eclipse.libs_4.0.0.Final-v20141016-1911-B82 so far).
>
> However, I now updated to Hiberate Tools 4.0.1 
> (org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95). The 
> problem I have now is that the following imports cannot be resolved:
> import antlr.RecognitionException;
> import antlr.TokenStreamException;
> import antlr.collections.AST;
>
> The problem seems to arise from the fact, that in the new version's 
> MANIFEST.MF, the antlr... packages are not exported and 
> lib/hibernate/antlr-2.7.6.jar is not listed in the Bundle-ClassPath 
> any more (I reformatted both MANIFEST.MFs, that you can find attached, 
> to allow a convenient comparison). After manually adding the 
> antlr-related entries to the new version's MANIFEST.MF, my code works 
> pretty well again.
>
> My question is thus:
> (a) Do you consider this to be a bug in the realease of Hibernate 
> Tools 4.0.1?
> (b) If yes for (a): Do you have an idea when this issue could be solved?
> (c) If no for (a): Which alternative solution would you suggest? I 
> mean, manually editing the MANIFEST.MF of realeased plug-ins is not 
> quite the best practice, is it? I tried to manally add antlr-2.7.6.jar 
> as library to my project, which solved the compilation error, but 
> yields a java.lang.ClassNotFoundException: antlr.LLkParser cannot be 
> found by org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95
>
> Any advice?
>
> Thanks!
> Bastian
>
>
>
> _______________________________________________
> 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/20150420/a90d0bf3/attachment.html 

From manderse at redhat.com  Tue Apr 21 03:25:55 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 21 Apr 2015 09:25:55 +0200
Subject: [jbosstools-dev] antlr packages and lib not exported in
 Hibernate Tools 4.0.1
In-Reply-To: <55353EFE.6040702@exadel.com>
References: <CAFEyyCJu+-LgoQ5HuCDhy9Kn9sPLSUB1+vOwoOD8-8BhLU=oQw@mail.gmail.com>
	<55353EFE.6040702@exadel.com>
Message-ID: <A86EAF8E-5B33-4ABB-9C4A-F61DB208E120@redhat.com>

On 20 Apr 2015, at 20:01, Alexey Kazakov wrote:

> First at all, please create an issue in 
> https://issues.jboss.org/browse/JBIDE to solve this problem in the 
> next release.
> A pull request for https://github.com/jbosstools/jbosstools-hibernate 
> would be useful too :)

please note that we are really trying to limit exposing any of hibernate 
internal runtime API's to support multiple versions of Hibernate. Thus 
if this break that we won't be able to do it.

What is your plugin trying to do that needs this level of access ?

/max
>
> On 04/20/2015 04:44 AM, Bastian Ugimachi wrote:
>>
>> Dear all,
>>
>> I am currently working on an Eclipse-Plugin that is built on top of 
>> the Hibernate Tools project. For example, I am using the following 
>> statements to get the AST of a named query:
>>
>> try {
>> HqlParser parser = HqlParser.getInstance(statementString);
>> parser.statement();
>> } catch (RecognitionException | TokenStreamException e) {
>> e.printStackTrace();
>> }
>> AST statementAst = parser.getAST();
>>
>> For this to work well with Hibernate Tools Version 4.0.0, I added 
>> bundle org.hibernate.eclipse.libs as required bundle to my plug-in 
>> configuration (which resolved to 
>> org.hibernate.eclipse.libs_4.0.0.Final-v20141016-1911-B82 so far).
>>
>> However, I now updated to Hiberate Tools 4.0.1 
>> (org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95). The 
>> problem I have now is that the following imports cannot be resolved:
>> import antlr.RecognitionException;
>> import antlr.TokenStreamException;
>> import antlr.collections.AST;
>>
>> The problem seems to arise from the fact, that in the new version's 
>> MANIFEST.MF, the antlr... packages are not exported and 
>> lib/hibernate/antlr-2.7.6.jar is not listed in the Bundle-ClassPath 
>> any more (I reformatted both MANIFEST.MFs, that you can find 
>> attached, to allow a convenient comparison). After manually adding 
>> the antlr-related entries to the new version's MANIFEST.MF, my code 
>> works pretty well again.
>>
>> My question is thus:
>> (a) Do you consider this to be a bug in the realease of Hibernate 
>> Tools 4.0.1?
>> (b) If yes for (a): Do you have an idea when this issue could be 
>> solved?
>> (c) If no for (a): Which alternative solution would you suggest? I 
>> mean, manually editing the MANIFEST.MF of realeased plug-ins is not 
>> quite the best practice, is it? I tried to manally add 
>> antlr-2.7.6.jar as library to my project, which solved the 
>> compilation error, but yields a java.lang.ClassNotFoundException: 
>> antlr.LLkParser cannot be found by 
>> org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95
>>
>> Any advice?
>>
>> Thanks!
>> Bastian
>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From nboldt at redhat.com  Tue Apr 21 14:20:44 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 21 Apr 2015 14:20:44 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Alpha2 bits available
	for QE testing
In-Reply-To: <5534947E.7050603@redhat.com>
References: <5534947E.7050603@redhat.com>
Message-ID: <553694FC.5010005@redhat.com>

In case you were wondering where the browsersim standalone zip went, it 
has moved.

You can get it here:

http://download.jboss.org/jbosstools/mars/staging/updates/browsersim-standalone/4.3.0.Alpha2/

(I've also updated the build process so that it publishes snapshots 
here: 
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-browsersim-standalone_master/ 
and 
http://download.jboss.org/jbosstools/mars/snapshots/updates/browsersim-standalone/)

On 04/20/2015 01:54 AM, Nick Boldt wrote:
> As always, these are not FINAL bits, but preliminary results for QE &
> community testing. Not for use by customers or end users.
>
> Update site: http://download.jboss.org/jbosstools/mars/staging/updates/
>
> Target platform:
> *
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Alpha2
>
>
> New + noteworthy (subject to change):
> *
> https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
>
> * http://tools.jboss.org/documentation/whatsnew/
>
> Schedule:
> https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel
>
>
> --
>
> Additional update sites:
> *
> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Alpha2/
>
> *
> http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.Alpha2/
>
> *
> http://download.jboss.org/jbosstools/mars/staging/updates/webtools/4.3.0.Alpha2/
>
>
> Discovery sites:
> *
> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Alpha2/
>
> *
> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Alpha2/
>
>
> 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 manderse at redhat.com  Tue Apr 21 16:41:55 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 21 Apr 2015 22:41:55 +0200
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Alpha2 bits available
 for QE testing
In-Reply-To: <553694FC.5010005@redhat.com>
References: <5534947E.7050603@redhat.com> <553694FC.5010005@redhat.com>
Message-ID: <9CF4E165-D28A-4B6F-A01E-4F1E52B983AE@redhat.com>

I thought we used nexus for the nightly build of this ?

Thats at least what 
http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Nightly.html#zips 
and 
http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Nightly.html#zips 
says ?

/max

> In case you were wondering where the browsersim standalone zip went, 
> it
> has moved.
>
> You can get it here:
>
> http://download.jboss.org/jbosstools/mars/staging/updates/browsersim-standalone/4.3.0.Alpha2/
>
> (I've also updated the build process so that it publishes snapshots
> here:
> http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-browsersim-standalone_master/
> and
> http://download.jboss.org/jbosstools/mars/snapshots/updates/browsersim-standalone/)
>
> On 04/20/2015 01:54 AM, Nick Boldt wrote:
>> As always, these are not FINAL bits, but preliminary results for QE &
>> community testing. Not for use by customers or end users.
>>
>> Update site: 
>> http://download.jboss.org/jbosstools/mars/staging/updates/
>>
>> Target platform:
>> *
>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Alpha2
>>
>>
>> New + noteworthy (subject to change):
>> *
>> https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
>>
>> * http://tools.jboss.org/documentation/whatsnew/
>>
>> Schedule:
>> https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel
>>
>>
>> --
>>
>> Additional update sites:
>> *
>> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Alpha2/
>>
>> *
>> http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.Alpha2/
>>
>> *
>> http://download.jboss.org/jbosstools/mars/staging/updates/webtools/4.3.0.Alpha2/
>>
>>
>> Discovery sites:
>> *
>> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Alpha2/
>>
>> *
>> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Alpha2/
>>
>>
>> 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
> _______________________________________________
> 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 Apr 21 17:00:31 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 21 Apr 2015 17:00:31 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Alpha2 bits available
 for QE testing
In-Reply-To: <9CF4E165-D28A-4B6F-A01E-4F1E52B983AE@redhat.com>
References: <5534947E.7050603@redhat.com> <553694FC.5010005@redhat.com>
	<9CF4E165-D28A-4B6F-A01E-4F1E52B983AE@redhat.com>
Message-ID: <5536BA6F.3080508@redhat.com>

Yes, it's in Nexus too.

Should I discontinue creating /builds/ and /updates/ for it then?

On 04/21/2015 04:41 PM, Max Rydahl Andersen wrote:
> I thought we used nexus for the nightly build of this ?
>
> Thats at least what
> http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Nightly.html#zips
> and
> http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Nightly.html#zips
> says ?
>
> /max
>
>> In case you were wondering where the browsersim standalone zip went, it
>> has moved.
>>
>> You can get it here:
>>
>> http://download.jboss.org/jbosstools/mars/staging/updates/browsersim-standalone/4.3.0.Alpha2/
>>
>>
>> (I've also updated the build process so that it publishes snapshots
>> here:
>> http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-browsersim-standalone_master/
>>
>> and
>> http://download.jboss.org/jbosstools/mars/snapshots/updates/browsersim-standalone/)
>>
>>
>> On 04/20/2015 01:54 AM, Nick Boldt wrote:
>>> As always, these are not FINAL bits, but preliminary results for QE &
>>> community testing. Not for use by customers or end users.
>>>
>>> Update site: http://download.jboss.org/jbosstools/mars/staging/updates/
>>>
>>> Target platform:
>>> *
>>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Alpha2
>>>
>>>
>>>
>>> New + noteworthy (subject to change):
>>> *
>>> https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
>>>
>>>
>>> * http://tools.jboss.org/documentation/whatsnew/
>>>
>>> Schedule:
>>> https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel
>>>
>>>
>>>
>>> --
>>>
>>> Additional update sites:
>>> *
>>> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Alpha2/
>>>
>>>
>>> *
>>> http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.Alpha2/
>>>
>>>
>>> *
>>> http://download.jboss.org/jbosstools/mars/staging/updates/webtools/4.3.0.Alpha2/
>>>
>>>
>>>
>>> Discovery sites:
>>> *
>>> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Alpha2/
>>>
>>>
>>> *
>>> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Alpha2/
>>>
>>>
>>>
>>> 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
>> _______________________________________________
>> 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 nboldt at redhat.com  Tue Apr 21 17:02:26 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 21 Apr 2015 17:02:26 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Alpha2 bits available
 for QE testing
In-Reply-To: <5536BA6F.3080508@redhat.com>
References: <5534947E.7050603@redhat.com> <553694FC.5010005@redhat.com>
	<9CF4E165-D28A-4B6F-A01E-4F1E52B983AE@redhat.com>
	<5536BA6F.3080508@redhat.com>
Message-ID: <5536BAE2.9020608@redhat.com>

Actually, we only use Nexus for nightly. For specific snapshots, we pull 
zips and put them on Sourceforge.

http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Alpha1.html#zips 
-> 
http://sourceforge.net/projects/jboss/files/JBossTools/jbosstools4.3.0.x/jbosstools-4.3.0.Alpha1_2015-02-15_14-44-55-B13-browsersim-standalone.zip

On 04/21/2015 05:00 PM, Nick Boldt wrote:
> Yes, it's in Nexus too.
>
> Should I discontinue creating /builds/ and /updates/ for it then?
>
> On 04/21/2015 04:41 PM, Max Rydahl Andersen wrote:
>> I thought we used nexus for the nightly build of this ?
>>
>> Thats at least what
>> http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Nightly.html#zips
>> and
>> http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Nightly.html#zips
>> says ?
>>
>> /max
>>
>>> In case you were wondering where the browsersim standalone zip went, it
>>> has moved.
>>>
>>> You can get it here:
>>>
>>> http://download.jboss.org/jbosstools/mars/staging/updates/browsersim-standalone/4.3.0.Alpha2/
>>>
>>>
>>>
>>> (I've also updated the build process so that it publishes snapshots
>>> here:
>>> http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-browsersim-standalone_master/
>>>
>>>
>>> and
>>> http://download.jboss.org/jbosstools/mars/snapshots/updates/browsersim-standalone/)
>>>
>>>
>>>
>>> On 04/20/2015 01:54 AM, Nick Boldt wrote:
>>>> As always, these are not FINAL bits, but preliminary results for QE &
>>>> community testing. Not for use by customers or end users.
>>>>
>>>> Update site: http://download.jboss.org/jbosstools/mars/staging/updates/
>>>>
>>>> Target platform:
>>>> *
>>>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Alpha2
>>>>
>>>>
>>>>
>>>>
>>>> New + noteworthy (subject to change):
>>>> *
>>>> https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
>>>>
>>>>
>>>>
>>>> * http://tools.jboss.org/documentation/whatsnew/
>>>>
>>>> Schedule:
>>>> https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Additional update sites:
>>>> *
>>>> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Alpha2/
>>>>
>>>>
>>>>
>>>> *
>>>> http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.Alpha2/
>>>>
>>>>
>>>>
>>>> *
>>>> http://download.jboss.org/jbosstools/mars/staging/updates/webtools/4.3.0.Alpha2/
>>>>
>>>>
>>>>
>>>>
>>>> Discovery sites:
>>>> *
>>>> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Alpha2/
>>>>
>>>>
>>>>
>>>> *
>>>> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Alpha2/
>>>>
>>>>
>>>>
>>>>
>>>> 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
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>> /max
>> http://about.me/maxandersen
>

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

From manderse at redhat.com  Tue Apr 21 17:23:44 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 21 Apr 2015 23:23:44 +0200
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Alpha2 bits available
 for QE testing
In-Reply-To: <5536BAE2.9020608@redhat.com>
References: <5534947E.7050603@redhat.com> <553694FC.5010005@redhat.com>
	<9CF4E165-D28A-4B6F-A01E-4F1E52B983AE@redhat.com>
	<5536BA6F.3080508@redhat.com> <5536BAE2.9020608@redhat.com>
Message-ID: <D7F4EB19-DC3D-4128-A388-060D2C532465@redhat.com>

On 21 Apr 2015, at 23:02, Nick Boldt wrote:

> Actually, we only use Nexus for nightly. For specific snapshots, we 
> pull zips and put them on Sourceforge.
>
> http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Alpha1.html#zips 
> -> 
> http://sourceforge.net/projects/jboss/files/JBossTools/jbosstools4.3.0.x/jbosstools-4.3.0.Alpha1_2015-02-15_14-44-55-B13-browsersim-standalone.zip

okey, could we try and stop calling releases/milestones for snapshots - 
they can't be both can they :)

/max

>
> On 04/21/2015 05:00 PM, Nick Boldt wrote:
>> Yes, it's in Nexus too.
>>
>> Should I discontinue creating /builds/ and /updates/ for it then?
>>
>> On 04/21/2015 04:41 PM, Max Rydahl Andersen wrote:
>>> I thought we used nexus for the nightly build of this ?
>>>
>>> Thats at least what
>>> http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Nightly.html#zips
>>> and
>>> http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Nightly.html#zips
>>> says ?
>>>
>>> /max
>>>
>>>> In case you were wondering where the browsersim standalone zip 
>>>> went, it
>>>> has moved.
>>>>
>>>> You can get it here:
>>>>
>>>> http://download.jboss.org/jbosstools/mars/staging/updates/browsersim-standalone/4.3.0.Alpha2/
>>>>
>>>>
>>>>
>>>> (I've also updated the build process so that it publishes snapshots
>>>> here:
>>>> http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-browsersim-standalone_master/
>>>>
>>>>
>>>> and
>>>> http://download.jboss.org/jbosstools/mars/snapshots/updates/browsersim-standalone/)
>>>>
>>>>
>>>>
>>>> On 04/20/2015 01:54 AM, Nick Boldt wrote:
>>>>> As always, these are not FINAL bits, but preliminary results for 
>>>>> QE &
>>>>> community testing. Not for use by customers or end users.
>>>>>
>>>>> Update site: 
>>>>> http://download.jboss.org/jbosstools/mars/staging/updates/
>>>>>
>>>>> Target platform:
>>>>> *
>>>>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Alpha2
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> New + noteworthy (subject to change):
>>>>> *
>>>>> https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
>>>>>
>>>>>
>>>>>
>>>>> * http://tools.jboss.org/documentation/whatsnew/
>>>>>
>>>>> Schedule:
>>>>> https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Additional update sites:
>>>>> *
>>>>> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Alpha2/
>>>>>
>>>>>
>>>>>
>>>>> *
>>>>> http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.Alpha2/
>>>>>
>>>>>
>>>>>
>>>>> *
>>>>> http://download.jboss.org/jbosstools/mars/staging/updates/webtools/4.3.0.Alpha2/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Discovery sites:
>>>>> *
>>>>> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Alpha2/
>>>>>
>>>>>
>>>>>
>>>>> *
>>>>> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Alpha2/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 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
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com


/max
http://about.me/maxandersen


From man8 at rtherdf.oowwwoo.com  Tue Apr 21 22:21:54 2015
From: man8 at rtherdf.oowwwoo.com (PCB Prototype Fabrication/Printed circuit board Supply)
Date: Wed, 22 Apr 2015 02:21:54 +0000
Subject: [jbosstools-dev] =?gb2312?b?UENCIFByb3RvdHlwZSBGYWJyaWNhdGlvbi9Q?=
	=?gb2312?b?cmludGVkIGNpcmN1aXQgYm9hcmQgU3VwcGx50+vE+rmyz+3By8/g?=
	=?gb2312?b?suGhow==?=
Message-ID: <001a1136232aa8189e051446d379@google.com>

Dear Sir/Madam,

Glad to know you from your great website, I'm proud to introduce you our  
high quality PCB products, Our advantage is -

The most experienced PCB sample manufacture from CHINA
Quick PCB Prototype Fabrication
Fast shipment according to customer's requirement

High quality with material Grade A FR-4
1 - 6 layer boards
All free test

Please kindly send us some drawings or manufacturing requirements  
description!

We provide 10% discount for all our new customers, and for volume order  
please feel free to get back to us, we will assure you our best price.

I would appreciate if you forward this letter to Technical Manager or to  
other expert responsible for technical integration of new products in your  
company,  for we could discuss all the details of our future cooperation.

Thanks for your attention to the above, we look forward to hearing back  
from you.

Best regards,

NiLu

https://picasaweb.google.com/lh/sredir?uname=109563458042155184300&target=ALBUM&id=6112185827377133649&authkey=Gv1sRgCPmO7aKd7OCsrgE&invite=CJmP_6oC&feat=email
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150422/01c95ea6/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: picasaweblogo-zh_CN.gif
Type: image/gif
Size: 1646 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150422/01c95ea6/attachment.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: email.jpg
Type: image/jpeg
Size: 9554 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150422/01c95ea6/attachment.jpg 

From manderse at redhat.com  Wed Apr 22 03:00:58 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Wed, 22 Apr 2015 03:00:58 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201504220700.t3M70waj018753@int-mx09.intmail.prod.int.phx2.redhat.com>


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

 
* No component for JBIDE-19683

https://issues.jboss.org/browse/JBIDE-19683
Summary: Create a user visible location for downloading tutorial metadata

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

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



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

From manderse at redhat.com  Thu Apr 23 03:00:29 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Thu, 23 Apr 2015 03:00:29 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201504230700.t3N70Tbw000487@int-mx09.intmail.prod.int.phx2.redhat.com>


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

 
* No component for JBIDE-19688

https://issues.jboss.org/browse/JBIDE-19688
Summary: Eclipse m2e, workspace resolution and Wildfly deployment issues

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

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



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

From manderse at redhat.com  Thu Apr 23 09:36:36 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 23 Apr 2015 15:36:36 +0200
Subject: [jbosstools-dev] New and noteworthy for Alpha2 - deadline friday
Message-ID: <F9FD6EDD-162F-4A23-B09D-D38695FCDCF5@redhat.com>

Hey,

alpha2 is set to go out Monday but we still don't have any N&N 
(https://issues.jboss.org/browse/JBIDE-19662)

Release Blog is set to go out Monday european time so to have that ready 
I need the N&N by friday.

Please get them in ASAP or ping me with your ETA for it.

/max
http://about.me/maxandersen

From nboldt at redhat.com  Thu Apr 23 09:51:49 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 23 Apr 2015 09:51:49 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Alpha2 bits available
	for QE testing
In-Reply-To: <5534947E.7050603@redhat.com>
References: <5534947E.7050603@redhat.com>
Message-ID: <5538F8F5.4020100@redhat.com>

In case you missed the discussion in IRC, I simply REPLACED B31 build 
run on the weekend with the B32 one on Monday evening, which included 
the fix for OpenShift / workspace bug JBIDE-19627.

Apologies for the confusion. I erroneously assumed people would see the 
updated feature w/ timestamp of 20150420 (amidst everything else built 
on 20150417) and realize they were seeing the updated bits.

You can also compare the two staged builds here:

http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-4.3.0.Alpha2-build-core/

I would prefer going forward to NOT tag update sites with an "a" or "b" 
suffix when respins are needed. Instead, I would prefer that we simply 
drop a second (third) build into the /staging/builds/ folder, and 
REPLACE the contents of the /staging/updates/ folders with the latest & 
best bits. That way, the stuff in /staging/updates/ can simply be copied 
to /development/updates/ without having to remove an "a" or "b" suffix 
on the folder.

--

As a reminder the plan is to get QE signoff late tomorrow, and queue up 
the bits on Sunday night (or Monday morning EST) so they can be 
released/blogged on Monday.

Please bear with me as we roll out this new release process - if you 
have questions about where stuff is now located, or what's happening, 
don't stay silent.

QUESTION EVERYTHING!

See also JBDS-3208.

Nick

On 04/20/2015 01:54 AM, Nick Boldt wrote:
> As always, these are not FINAL bits, but preliminary results for QE &
> community testing. Not for use by customers or end users.
>
> Update site: http://download.jboss.org/jbosstools/mars/staging/updates/
>
> Target platform:
> *
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Alpha2
>
>
> New + noteworthy (subject to change):
> *
> https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
>
> * http://tools.jboss.org/documentation/whatsnew/
>
> Schedule:
> https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel
>
>
> --
>
> Additional update sites:
> *
> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Alpha2/
>
> *
> http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.0.Alpha2/
>
> *
> http://download.jboss.org/jbosstools/mars/staging/updates/webtools/4.3.0.Alpha2/
>
>
> Discovery sites:
> *
> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.0.Alpha2/
>
> *
> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.Alpha2/
>
>
> 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  Thu Apr 23 17:48:44 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 23 Apr 2015 17:48:44 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 24 unresolved issues with
	fixversion = Alpha2
Message-ID: <553968BC.8080504@redhat.com>

Please resolve (if done) or punt to Beta1 (if not done) these 24 
remaining Alpha2 issues:

https://issues.jboss.org/issues/?jql=filter%20%3D%20ds_freeze%20and%20filter%20%3D%20ds_unresolved

Want a query for just *YOUR* issues (or unassigned issues)? Here ya go:

https://issues.jboss.org/issues/?jql=filter%20%3D%20ds_freeze%20and%20filter%20%3D%20ds_unresolved%20and%20%28assignee%20%3D%20currentUser%28%29%20or%20assignee%20%3D%20null%29

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

From akazakov at exadel.com  Thu Apr 23 19:45:40 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 23 Apr 2015 16:45:40 -0700
Subject: [jbosstools-dev] N&N for previous releases
Message-ID: <55398424.5020006@exadel.com>

HI,

Currently http://tools.jboss.org/documentation/whatsnew/index.html has 
N&N for the last versions for each major Eclipse release. 4.1.*, 4.2.*, 
4.3.*,...
But if you click on 4.2.3 (Luna) for example: open 
http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.3.Final.html
then there is only N&N for 4.2.3 which have been added since 4.2.2.
There are not links to 4.2.0, 4.2.1, 4.2.2. N&N.
So it's not easy to find direct links to N&N pages where you can find 
the full list of new features for our Luna release (4.2.x) comparing to 
Kepler (4.1.*).

Does it seem weired for me only?


From manderse at redhat.com  Fri Apr 24 02:55:54 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 24 Apr 2015 08:55:54 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: 24 unresolved issues with
 fixversion = Alpha2
In-Reply-To: <553968BC.8080504@redhat.com>
References: <553968BC.8080504@redhat.com>
Message-ID: <31C4F310-E995-4C67-B1B3-734EDE841603@redhat.com>

On 23 Apr 2015, at 23:48, Nick Boldt wrote:

> Please resolve (if done) or punt to Beta1 (if not done) these 24
> remaining Alpha2 issues:
>
> https://issues.jboss.org/issues/?jql=filter%20%3D%20ds_freeze%20and%20filter%20%3D%20ds_unresolved
>
> Want a query for just *YOUR* issues (or unassigned issues)? Here ya 
> go:
>
> https://issues.jboss.org/issues/?jql=filter%20%3D%20ds_freeze%20and%20filter%20%3D%20ds_unresolved%20and%20%28assignee%20%3D%20currentUser%28%29%20or%20assignee%20%3D%20null%29

The better query for this is: 
https://issues.jboss.org/issues/?jql=filter%20%3D%20ds_mystuff%20and%20filter%3Dds_freeze%20and%20filter%3Dds_unresolved

Then you don't see unassigned from components you are not leading.

/max

>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From manderse at redhat.com  Fri Apr 24 03:31:03 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 24 Apr 2015 09:31:03 +0200
Subject: [jbosstools-dev] N&N for previous releases
In-Reply-To: <55398424.5020006@exadel.com>
References: <55398424.5020006@exadel.com>
Message-ID: <5253D142-08C6-4102-9F66-4434AE825376@redhat.com>

On 24 Apr 2015, at 1:45, Alexey Kazakov wrote:

> HI,
>
> Currently http://tools.jboss.org/documentation/whatsnew/index.html has
> N&N for the last versions for each major Eclipse release. 4.1.*, 
> 4.2.*,
> 4.3.*,...
> But if you click on 4.2.3 (Luna) for example: open
> http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.3.Final.html
> then there is only N&N for 4.2.3 which have been added since 4.2.2.
> There are not links to 4.2.0, 4.2.1, 4.2.2. N&N.
> So it's not easy to find direct links to N&N pages where you can find
> the full list of new features for our Luna release (4.2.x) comparing 
> to
> Kepler (4.1.*).
>
> Does it seem weired for me only?

nope - it looks like each minor release was archived too soon.

That is only supposed to happen for alpha/betas etc. when the final 
release is out.

Fixed it in 
https://github.com/jbosstools/jbosstools-website/commit/9f2cf87c9845f3a4bb4d5b3cf4ebe417a722ebcc
that should be live soon.

/max


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


/max
http://about.me/maxandersen


From xcoulon at redhat.com  Fri Apr 24 04:01:10 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Fri, 24 Apr 2015 10:01:10 +0200
Subject: [jbosstools-dev] N&N for previous releases
In-Reply-To: <5253D142-08C6-4102-9F66-4434AE825376@redhat.com>
References: <55398424.5020006@exadel.com>
	<5253D142-08C6-4102-9F66-4434AE825376@redhat.com>
Message-ID: <A01CC39E-6738-4884-BBE0-0599A1F35408@redhat.com>

My bad. A few weeks ago I committed a change to archive old versions of JBoss Tools and reduce the size of the left navigation menu on the N&N page, but in the euphoria I included the 4.2.x.Final versions.

/Xavier



> On 24 Apr 2015, at 09:31, Max Rydahl Andersen <manderse at redhat.com> wrote:
> 
> On 24 Apr 2015, at 1:45, Alexey Kazakov wrote:
> 
>> HI,
>> 
>> Currently http://tools.jboss.org/documentation/whatsnew/index.html has
>> N&N for the last versions for each major Eclipse release. 4.1.*, 
>> 4.2.*,
>> 4.3.*,...
>> But if you click on 4.2.3 (Luna) for example: open
>> http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.3.Final.html
>> then there is only N&N for 4.2.3 which have been added since 4.2.2.
>> There are not links to 4.2.0, 4.2.1, 4.2.2. N&N.
>> So it's not easy to find direct links to N&N pages where you can find
>> the full list of new features for our Luna release (4.2.x) comparing 
>> to
>> Kepler (4.1.*).
>> 
>> Does it seem weired for me only?
> 
> nope - it looks like each minor release was archived too soon.
> 
> That is only supposed to happen for alpha/betas etc. when the final 
> release is out.
> 
> Fixed it in 
> https://github.com/jbosstools/jbosstools-website/commit/9f2cf87c9845f3a4bb4d5b3cf4ebe417a722ebcc <https://github.com/jbosstools/jbosstools-website/commit/9f2cf87c9845f3a4bb4d5b3cf4ebe417a722ebcc>
> that should be live soon.
> 
> /max
> 
> 
>> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev <https://lists.jboss.org/mailman/listinfo/jbosstools-dev>
> 
> 
> /max
> http://about.me/maxandersen <http://about.me/maxandersen>
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev <https://lists.jboss.org/mailman/listinfo/jbosstools-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150424/37fc95c4/attachment-0001.html 

From fbricon at redhat.com  Mon Apr 27 00:11:05 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Mon, 27 Apr 2015 00:11:05 -0400
Subject: [jbosstools-dev] new JBoss Central available from nightly builds
Message-ID: <460B656E-D2C2-4F87-98D2-1EB32AF9828F@redhat.com>

Hi,

FYI, I?ve merged the current Central/HTML5 rework to jbosstools-central master.
This means you can see the new Central in action after installing the latest nightly build from http://download.jboss.org/jbosstools/updates/nightly/mars/ <http://download.jboss.org/jbosstools/updates/nightly/mars/> 

It?s far from being complete, but you?ll at least get a taste of what?s to come in JBT 4.3/JBDS 9.

What works :
- Central is now an html5 page maintained at  https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage> 
- the page is served from a swt browser widget (using webkit under the hood).
- about 220 quickstarts are available as of today (some target eap 6.3, other target 6.4)
- search is craaazy fast, as it is local to the webpage (no round trips to dcp server)
- it?s fast to load and scales better in small windows, compared to the existing version.
- proxy wizards are injected to search results
- external links are opened in a browser window
- JBoss Buzz results visible as carousel under the title
- early access label displayed according to EA settings (UI to be reviewed)
- you can build https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage> locally (after installing node and grunt-cli) and test it by starting Eclipse with -Djboss.central.webpage.url=file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip <file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip> or -Djboss.central.webpage.url=/path/to/jbosstools-central-webpage/target/gruntbuild.

What doesn?t work :
- for some reason I just broke the quickstart integration, which used to work, I swear. Will fix it on Monday
- current webpage is served directly from http://central-fredapp.rhcloud.com/ <http://central-fredapp.rhcloud.com/>, I need to get https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage> built from Jenkins and deployed to Nexus. At least that gives us some good flexibility in terms of maintenance.
- search engine uses staging dcpbeta-searchisko.rhcloud.com/ <http://dcpbeta-searchisko.rhcloud.com/> service, instead of dcp.jboss.org <http://dcp.jboss.org/>
- The development workflow isn?t finalized yet. I need to set up and tune grunt watch, so that changes in html/js/sass can be picked up directly from eclipse.
- title still too big, needs to scale down
- offline mode is not supported (both for central and the quickstarts, groovy script not update yet)
- quickstarts not integrated to the existing project examples wizard
- legacy examples are not displays in the results, yet.
- project requirements not inferred yet (from existing metadata?)
- project tags should be added
- maybe find another default icon for quickstarts.
- layout needs to be tuned (needs to scale on 3 cols, instead of 4 and 2 currently)
- needs some tabzilla-like button (see the red hat at top right of http://tools.jboss.org/ <http://tools.jboss.org/>) to display show on startup
- APIs are in still unstable, expect them to break.
-  you might notice some slight font flickering, due to the carousel script. I tried to minimize it but it?s still visible in the search bar?s hint text
- many other small stuff that are missing, that I can?t think of right now.

So, give it a try, we?d be happy to hear some feedback, good or bad, ideas to make it better (JIRA is your friend).

Fred

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

From nboldt at redhat.com  Mon Apr 27 18:22:45 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 27 Apr 2015 18:22:45 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
Message-ID: <553EB6B5.9040609@redhat.com>

Component leads, please tag your repositories!

  git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is 
called jbosstools, also often called origin
  git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
  git push jbosstools jbosstools-4.3.0.Alpha2


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

From adietish at redhat.com  Tue Apr 28 05:53:10 2015
From: adietish at redhat.com (=?windows-1252?Q?Andr=E9_Dietisheim?=)
Date: Tue, 28 Apr 2015 11:53:10 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <553EB6B5.9040609@redhat.com>
References: <553EB6B5.9040609@redhat.com>
Message-ID: <553F5886.60802@redhat.com>

done for OpenShift

On 04/28/2015 12:22 AM, Nick Boldt wrote:
> Component leads, please tag your repositories!
>
>    git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
> called jbosstools, also often called origin
>    git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>    git push jbosstools jbosstools-4.3.0.Alpha2
>
>


From manderse at redhat.com  Tue Apr 28 07:03:14 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 28 Apr 2015 13:03:14 +0200
Subject: [jbosstools-dev] deleted LOCUS versions in JBIDE jira
Message-ID: <F3052C99-7045-4E46-821A-D705BA338391@redhat.com>

Hi,

I noticed I forgotten to delete the LOCUS versions in JBIDE when 
creating the LOCUS project.

Those are now gone. Thus all of LOCUS has now moved to 
https://jira.jboss.org/jira/browse/LOCUS,
all the deleted versions and its metadata is now there.

/max
http://about.me/maxandersen

From manderse at redhat.com  Tue Apr 28 07:55:36 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 28 Apr 2015 13:55:36 +0200
Subject: [jbosstools-dev] JBoss Tools 4.3.0.Alpha2 is now available
Message-ID: <89BBF6A9-E4FD-4C3E-B6AC-F9025F1259DC@redhat.com>

This is a development release aimed at Eclipse 4.5.0.M6 Mars users.

Announcement Blog: 
http://tools.jboss.org/blog/2015-04-28-alpha2-for-mars.html

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

Update Site Zips:

* http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Alpha2.html
* 
http://sourceforge.net/projects/jboss/files/JBossTools/jbosstools4.3.0.x/

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

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

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


/max
http://about.me/maxandersen


From nboldt at redhat.com  Tue Apr 28 09:41:06 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 28 Apr 2015 09:41:06 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <553F5886.60802@redhat.com>
References: <553EB6B5.9040609@redhat.com> <553F5886.60802@redhat.com>
Message-ID: <553F8DF2.5090503@redhat.com>

Just FYI, you don't need to reply to these emails to confirm the work's 
done.

Thanks,

Nick

On 04/28/2015 05:53 AM, Andr? Dietisheim wrote:
> done for OpenShift
>
> On 04/28/2015 12:22 AM, Nick Boldt wrote:
>> Component leads, please tag your repositories!
>>
>>    git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>> called jbosstools, also often called origin
>>    git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>    git push jbosstools jbosstools-4.3.0.Alpha2
>>
>>
>

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

From ggastald at redhat.com  Tue Apr 28 10:08:25 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Tue, 28 Apr 2015 11:08:25 -0300
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <553EB6B5.9040609@redhat.com>
References: <553EB6B5.9040609@redhat.com>
Message-ID: <553F9459.8000805@redhat.com>

Done for forge

On 04/27/2015 07:22 PM, Nick Boldt wrote:
> Component leads, please tag your repositories!
>
>    git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
> called jbosstools, also often called origin
>    git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>    git push jbosstools jbosstools-4.3.0.Alpha2
>
>


From ggastald at redhat.com  Tue Apr 28 10:08:58 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Tue, 28 Apr 2015 11:08:58 -0300
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <553F8DF2.5090503@redhat.com>
References: <553EB6B5.9040609@redhat.com> <553F5886.60802@redhat.com>
	<553F8DF2.5090503@redhat.com>
Message-ID: <553F947A.6030505@redhat.com>

too late :)

On 04/28/2015 10:41 AM, Nick Boldt wrote:
> Just FYI, you don't need to reply to these emails to confirm the work's
> done.
>
> Thanks,
>
> Nick
>
> On 04/28/2015 05:53 AM, Andr? Dietisheim wrote:
>> done for OpenShift
>>
>> On 04/28/2015 12:22 AM, Nick Boldt wrote:
>>> Component leads, please tag your repositories!
>>>
>>>     git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>>> called jbosstools, also often called origin
>>>     git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>>     git push jbosstools jbosstools-4.3.0.Alpha2
>>>
>>>


From manderse at redhat.com  Tue Apr 28 14:01:55 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 28 Apr 2015 20:01:55 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <553F8DF2.5090503@redhat.com>
References: <553EB6B5.9040609@redhat.com> <553F5886.60802@redhat.com>
	<553F8DF2.5090503@redhat.com>
Message-ID: <46D00026-E4CD-408E-BC99-BA7956400EBB@redhat.com>

On 28 Apr 2015, at 15:41, Nick Boldt wrote:

> Just FYI, you don't need to reply to these emails to confirm the work's
> done.

Nick, do you have a script that checks if all done ? 

/max

> Thanks,
>
> Nick
>
> On 04/28/2015 05:53 AM, Andr? Dietisheim wrote:
>> done for OpenShift
>>
>> On 04/28/2015 12:22 AM, Nick Boldt wrote:
>>> Component leads, please tag your repositories!
>>>
>>>  git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>>> called jbosstools, also often called origin
>>>  git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>>  git push jbosstools jbosstools-4.3.0.Alpha2
>>>
>>>
>>
>
> -- 
> 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 Apr 28 16:55:57 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 28 Apr 2015 16:55:57 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <46D00026-E4CD-408E-BC99-BA7956400EBB@redhat.com>
References: <553EB6B5.9040609@redhat.com> <553F5886.60802@redhat.com>
	<553F8DF2.5090503@redhat.com>
	<46D00026-E4CD-408E-BC99-BA7956400EBB@redhat.com>
Message-ID: <553FF3DD.3030002@redhat.com>

No, but I have a script that checks if everyone has branched & if root 
poms are updated, because...

* Wrong root pom: prevents builds & blocks releases.

* Branching: prevents builds & blocks releases.

* Tagging: until we move to a model where tags drive builds, tagging 
after the release is just icing sugar.

You may now commence arguing. :D

Nick

On 04/28/2015 02:01 PM, Max Rydahl Andersen wrote:
> On 28 Apr 2015, at 15:41, Nick Boldt wrote:
>
>> Just FYI, you don't need to reply to these emails to confirm the work's
>> done.
>
> Nick, do you have a script that checks if all done ?
>
> /max
>
>> Thanks,
>>
>> Nick
>>
>> On 04/28/2015 05:53 AM, Andr? Dietisheim wrote:
>>> done for OpenShift
>>>
>>> On 04/28/2015 12:22 AM, Nick Boldt wrote:
>>>> Component leads, please tag your repositories!
>>>>
>>>>   git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>>>> called jbosstools, also often called origin
>>>>   git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>>>   git push jbosstools jbosstools-4.3.0.Alpha2
>>>>
>>>>
>>>
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
>

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

From manderse at redhat.com  Tue Apr 28 18:35:56 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 28 Apr 2015 18:35:56 -0400 (EDT)
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
	please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
	jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <553FF3DD.3030002@redhat.com>
References: <553EB6B5.9040609@redhat.com> <553F5886.60802@redhat.com>
	<553F8DF2.5090503@redhat.com>
	<46D00026-E4CD-408E-BC99-BA7956400EBB@redhat.com>
	<553FF3DD.3030002@redhat.com>
Message-ID: <DC6A4CD4-EB6C-4F39-A493-21833B530923@redhat.com>

I'll write the script. Having the tags has been and will be useful in past despite you thinking it is just icing. 

/max
http://about.me/maxandersen


> On 28 Apr 2015, at 22:55, Nick Boldt <nboldt at redhat.com> wrote:
> 
> No, but I have a script that checks if everyone has branched & if root poms are updated, because...
> 
> * Wrong root pom: prevents builds & blocks releases.
> 
> * Branching: prevents builds & blocks releases.
> 
> * Tagging: until we move to a model where tags drive builds, tagging after the release is just icing sugar.
> 
> You may now commence arguing. :D
> 
> Nick
> 
>> On 04/28/2015 02:01 PM, Max Rydahl Andersen wrote:
>>> On 28 Apr 2015, at 15:41, Nick Boldt wrote:
>>> 
>>> Just FYI, you don't need to reply to these emails to confirm the work's
>>> done.
>> 
>> Nick, do you have a script that checks if all done ?
>> 
>> /max
>> 
>>> Thanks,
>>> 
>>> Nick
>>> 
>>>> On 04/28/2015 05:53 AM, Andr? Dietisheim wrote:
>>>> done for OpenShift
>>>> 
>>>>> On 04/28/2015 12:22 AM, Nick Boldt wrote:
>>>>> Component leads, please tag your repositories!
>>>>> 
>>>>>  git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>>>>> called jbosstools, also often called origin
>>>>>  git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>>>>  git push jbosstools jbosstools-4.3.0.Alpha2
>>> 
>>> --
>>> Nick Boldt :: JBoss by Red Hat
>>> Productization Lead :: JBoss Tools & Dev Studio
>>> http://nick.divbyzero.com
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> 
>> 
>> /max
>> http://about.me/maxandersen
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com


From manderse at redhat.com  Wed Apr 29 03:51:53 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 29 Apr 2015 09:51:53 +0200
Subject: [jbosstools-dev] ATTENTION REQUIRED: missing tags
Message-ID: <1271287A-83DB-423D-AF9F-DC9A317D56CA@redhat.com>

I wrote a script to check how good/bad we were on actually having tags 
for the various releases.

First I found the ones missing the recent Alpha2 tag:

jbosstools-arquillian
jbosstools-livereload
jbosstools-aerogear
jbosstools-hibernate
jbosstools-freemarker
jbosstools-webservices
jbosstools-server
jbosstools-portlet
jbosstools-download.jboss.org
jbosstools-central
jbosstools-build-ci
jbosstools-birt

Then I thought about how it was looking for other releases so I made the 
script a bit more advanced 
(https://github.com/jbosstools/jbosstools-build/pull/182/files).

It loads all historical tags of jbosstools-base and with a "since" 
marker to not get false positives: 
https://github.com/jbosstools/jbosstools-build/pull/182/files#diff-015178ddb40125e999fea74a7bb4d3d8R46

With this the list is a tad longer (full details at: 
https://gist.github.com/maxandersen/8e5c311b7b0f18c95e88)

jbosstools-download.jboss.org missing 13 tags
jbosstools-freemarker missing 12 tags
jbosstools-server missing 13 tags
jbosstools-build-ci missing 8 tags
jbosstools-aerogear missing 6 tags
jbosstools-hibernate missing 6 tags
jbosstools-birt missing 5 tags
jbosstools-central missing 5 tags
jbosstools-portlet missing 5 tags
jbosstools-forge missing 4 tags
jbosstools-webservices missing 4 tags
jbosstools-build missing 3 tags
jbosstools-openshift missing 3 tags
jbosstools-build-sites missing 3 tags
jbosstools-vpe missing 2 tags
jbosstools-livereload missing 2 tags
jbosstools-arquillian missing 2 tags
jbosstools-jst missing 1 tags
jbosstools-discovery missing 1 tags
jbosstools-browsersim missing 1 tags

If you believe my script reported wrongly on this please let me know and
otherwise i'll create a task jira for these next week.

Thanks,
/max
http://about.me/maxandersen


From manderse at redhat.com  Wed Apr 29 05:19:30 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 29 Apr 2015 11:19:30 +0200
Subject: [jbosstools-dev] created 'easymport' component
Message-ID: <F8D2D974-A899-4EDA-BF56-05C7824DE19A@redhat.com>

Hi,

After seeing incoming issues related to easymport being misclassified 
I've now created an 'easymport' component lead by mistria.

I suggest for issues that are related to easymport + another component 
(i.e. aerogear-hybrid) has both components set, and if it is purely a 
easymport issue we can remove the other component.

Thanks,
/max
http://about.me/maxandersen

From mmalina at redhat.com  Wed Apr 29 05:20:26 2015
From: mmalina at redhat.com (Martin Malina)
Date: Wed, 29 Apr 2015 11:20:26 +0200
Subject: [jbosstools-dev] new JBoss Central available from nightly builds
In-Reply-To: <460B656E-D2C2-4F87-98D2-1EB32AF9828F@redhat.com>
References: <460B656E-D2C2-4F87-98D2-1EB32AF9828F@redhat.com>
Message-ID: <446BE661-27A4-4B49-B8E8-E417A3D5505E@redhat.com>

Hi Fred,

Great job! I like the design, it looks clean. And the search is super fast.
What I don't quite like so much is the carousel. You can't control it and it can be a little distracting.
For other arguments see http://shouldiuseacarousel.com <http://shouldiuseacarousel.com/> :) But maybe it's just me :)
And I understand we do want to put the blogs somewhere.

-Martin


> On 27. 4. 2015, at 6:11, Fred Bricon <fbricon at redhat.com> wrote:
> 
> Hi,
> 
> FYI, I?ve merged the current Central/HTML5 rework to jbosstools-central master.
> This means you can see the new Central in action after installing the latest nightly build from http://download.jboss.org/jbosstools/updates/nightly/mars/ <http://download.jboss.org/jbosstools/updates/nightly/mars/> 
> 
> It?s far from being complete, but you?ll at least get a taste of what?s to come in JBT 4.3/JBDS 9.
> 
> What works :
> - Central is now an html5 page maintained at  https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage> 
> - the page is served from a swt browser widget (using webkit under the hood).
> - about 220 quickstarts are available as of today (some target eap 6.3, other target 6.4)
> - search is craaazy fast, as it is local to the webpage (no round trips to dcp server)
> - it?s fast to load and scales better in small windows, compared to the existing version.
> - proxy wizards are injected to search results
> - external links are opened in a browser window
> - JBoss Buzz results visible as carousel under the title
> - early access label displayed according to EA settings (UI to be reviewed)
> - you can build https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage> locally (after installing node and grunt-cli) and test it by starting Eclipse with -Djboss.central.webpage.url=file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip <file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip> or -Djboss.central.webpage.url=/path/to/jbosstools-central-webpage/target/gruntbuild.
> 
> What doesn?t work :
> - for some reason I just broke the quickstart integration, which used to work, I swear. Will fix it on Monday
> - current webpage is served directly from http://central-fredapp.rhcloud.com/ <http://central-fredapp.rhcloud.com/>, I need to get https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage> built from Jenkins and deployed to Nexus. At least that gives us some good flexibility in terms of maintenance.
> - search engine uses staging dcpbeta-searchisko.rhcloud.com/ <http://dcpbeta-searchisko.rhcloud.com/> service, instead of dcp.jboss.org <http://dcp.jboss.org/>
> - The development workflow isn?t finalized yet. I need to set up and tune grunt watch, so that changes in html/js/sass can be picked up directly from eclipse.
> - title still too big, needs to scale down
> - offline mode is not supported (both for central and the quickstarts, groovy script not update yet)
> - quickstarts not integrated to the existing project examples wizard
> - legacy examples are not displays in the results, yet.
> - project requirements not inferred yet (from existing metadata?)
> - project tags should be added
> - maybe find another default icon for quickstarts.
> - layout needs to be tuned (needs to scale on 3 cols, instead of 4 and 2 currently)
> - needs some tabzilla-like button (see the red hat at top right of http://tools.jboss.org/ <http://tools.jboss.org/>) to display show on startup
> - APIs are in still unstable, expect them to break.
> -  you might notice some slight font flickering, due to the carousel script. I tried to minimize it but it?s still visible in the search bar?s hint text
> - many other small stuff that are missing, that I can?t think of right now.
> 
> So, give it a try, we?d be happy to hear some feedback, good or bad, ideas to make it better (JIRA is your friend).
> 
> Fred
> 
> _______________________________________________
> 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/20150429/e7b17c73/attachment.html 

From rawagner at redhat.com  Wed Apr 29 05:42:10 2015
From: rawagner at redhat.com (Rastislav Wagner)
Date: Wed, 29 Apr 2015 05:42:10 -0400 (EDT)
Subject: [jbosstools-dev] new JBoss Central available from nightly builds
In-Reply-To: <446BE661-27A4-4B49-B8E8-E417A3D5505E@redhat.com>
References: <460B656E-D2C2-4F87-98D2-1EB32AF9828F@redhat.com>
	<446BE661-27A4-4B49-B8E8-E417A3D5505E@redhat.com>
Message-ID: <1704440780.9070493.1430300530975.JavaMail.zimbra@redhat.com>

Dont worry, you're not alone who doesn't like carousel. I just wanted to create issue. Lack of control is frustrating :)

Rastislav Wagner
JBDS QA
irc: rawagner

----- Original Message -----
From: "Martin Malina" <mmalina at redhat.com>
To: "Fred Bricon" <fbricon at redhat.com>
Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
Sent: Wednesday, April 29, 2015 11:20:26 AM
Subject: Re: [jbosstools-dev] new JBoss Central available from nightly builds

Hi Fred, 

Great job! I like the design, it looks clean. And the search is super fast. 
What I don't quite like so much is the carousel. You can't control it and it can be a little distracting. 
For other arguments see http://shouldiuseacarousel.com :) But maybe it's just me :) 
And I understand we do want to put the blogs somewhere. 

-Martin 





On 27. 4. 2015, at 6:11, Fred Bricon < fbricon at redhat.com > wrote: 

Hi, 

FYI, I?ve merged the current Central/HTML5 rework to jbosstools-central master. 
This means you can see the new Central in action after installing the latest nightly build from http://download.jboss.org/jbosstools/updates/nightly/mars/ 

It?s far from being complete, but you?ll at least get a taste of what?s to come in JBT 4.3/JBDS 9. 

What works : 
- Central is now an html5 page maintained at https://github.com/jbosstools/jbosstools-central-webpage 
- the page is served from a swt browser widget (using webkit under the hood). 
- about 220 quickstarts are available as of today (some target eap 6.3, other target 6.4) 
- search is craaazy fast, as it is local to the webpage (no round trips to dcp server) 
- it?s fast to load and scales better in small windows, compared to the existing version. 
- proxy wizards are injected to search results 
- external links are opened in a browser window 
- JBoss Buzz results visible as carousel under the title 
- early access label displayed according to EA settings (UI to be reviewed) 
- you can build https://github.com/jbosstools/jbosstools-central-webpage locally (after installing node and grunt-cli) and test it by starting Eclipse with -Djboss.central.webpage.url= file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip or -Djboss.central.webpage.url=/path/to/jbosstools-central-webpage/target/gruntbuild. 

What doesn?t work : 
- for some reason I just broke the quickstart integration, which used to work, I swear. Will fix it on Monday 
- current webpage is served directly from http://central-fredapp.rhcloud.com/ , I need to get https://github.com/jbosstools/jbosstools-central-webpage built from Jenkins and deployed to Nexus. At least that gives us some good flexibility in terms of maintenance. 
- search engine uses staging dcpbeta-searchisko.rhcloud.com/ service, instead of dcp.jboss.org 
- The development workflow isn?t finalized yet. I need to set up and tune grunt watch, so that changes in html/js/sass can be picked up directly from eclipse. 
- title still too big, needs to scale down 
- offline mode is not supported (both for central and the quickstarts, groovy script not update yet) 
- quickstarts not integrated to the existing project examples wizard 
- legacy examples are not displays in the results, yet. 
- project requirements not inferred yet (from existing metadata?) 
- project tags should be added 
- maybe find another default icon for quickstarts. 
- layout needs to be tuned (needs to scale on 3 cols, instead of 4 and 2 currently) 
- needs some tabzilla-like button (see the red hat at top right of http://tools.jboss.org/ ) to display show on startup 
- APIs are in still unstable, expect them to break. 
- you might notice some slight font flickering, due to the carousel script. I tried to minimize it but it?s still visible in the search bar?s hint text 
- many other small stuff that are missing, that I can?t think of right now. 

So, give it a try, we?d be happy to hear some feedback, good or bad, ideas to make it better (JIRA is your friend). 

Fred 

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


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


From manderse at redhat.com  Wed Apr 29 05:44:10 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 29 Apr 2015 11:44:10 +0200
Subject: [jbosstools-dev] new JBoss Central available from nightly builds
In-Reply-To: <446BE661-27A4-4B49-B8E8-E417A3D5505E@redhat.com>
References: <460B656E-D2C2-4F87-98D2-1EB32AF9828F@redhat.com>
	<446BE661-27A4-4B49-B8E8-E417A3D5505E@redhat.com>
Message-ID: <85995023-234E-4358-9DBD-447CE242A6B9@redhat.com>

On 29 Apr 2015, at 11:20, Martin Malina wrote:

> Hi Fred,
>
> Great job! I like the design, it looks clean. And the search is super 
> fast.
> What I don't quite like so much is the carousel. You can't control it 
> and it can be a little distracting.
> For other arguments see http://shouldiuseacarousel.com 
> <http://shouldiuseacarousel.com/> :) But maybe it's just me :)
> And I understand we do want to put the blogs somewhere.

I have the same concern, but I think this small "ticker" is less of a 
problem than the usual giant carousel's that shouldiuseacarousel.com 
goes against.

At least thats what I feel now - lets see what the feedback is and if we 
are getting more or less clicks on the entries ;)

/max

>
> -Martin
>
>
>> On 27. 4. 2015, at 6:11, Fred Bricon <fbricon at redhat.com> wrote:
>>
>> Hi,
>>
>> FYI, I?ve merged the current Central/HTML5 rework to 
>> jbosstools-central master.
>> This means you can see the new Central in action after installing the 
>> latest nightly build from 
>> http://download.jboss.org/jbosstools/updates/nightly/mars/ 
>> <http://download.jboss.org/jbosstools/updates/nightly/mars/>
>>
>> It?s far from being complete, but you?ll at least get a taste of 
>> what?s to come in JBT 4.3/JBDS 9.
>>
>> What works :
>> - Central is now an html5 page maintained at  
>> https://github.com/jbosstools/jbosstools-central-webpage 
>> <https://github.com/jbosstools/jbosstools-central-webpage>
>> - the page is served from a swt browser widget (using webkit under 
>> the hood).
>> - about 220 quickstarts are available as of today (some target eap 
>> 6.3, other target 6.4)
>> - search is craaazy fast, as it is local to the webpage (no round 
>> trips to dcp server)
>> - it?s fast to load and scales better in small windows, compared to 
>> the existing version.
>> - proxy wizards are injected to search results
>> - external links are opened in a browser window
>> - JBoss Buzz results visible as carousel under the title
>> - early access label displayed according to EA settings (UI to be 
>> reviewed)
>> - you can build 
>> https://github.com/jbosstools/jbosstools-central-webpage 
>> <https://github.com/jbosstools/jbosstools-central-webpage> locally 
>> (after installing node and grunt-cli) and test it by starting Eclipse 
>> with 
>> -Djboss.central.webpage.url=file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip 
>> <file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip> 
>> or 
>> -Djboss.central.webpage.url=/path/to/jbosstools-central-webpage/target/gruntbuild.
>>
>> What doesn?t work :
>> - for some reason I just broke the quickstart integration, which used 
>> to work, I swear. Will fix it on Monday
>> - current webpage is served directly from 
>> http://central-fredapp.rhcloud.com/ 
>> <http://central-fredapp.rhcloud.com/>, I need to get 
>> https://github.com/jbosstools/jbosstools-central-webpage 
>> <https://github.com/jbosstools/jbosstools-central-webpage> built from 
>> Jenkins and deployed to Nexus. At least that gives us some good 
>> flexibility in terms of maintenance.
>> - search engine uses staging dcpbeta-searchisko.rhcloud.com/ 
>> <http://dcpbeta-searchisko.rhcloud.com/> service, instead of 
>> dcp.jboss.org <http://dcp.jboss.org/>
>> - The development workflow isn?t finalized yet. I need to set up 
>> and tune grunt watch, so that changes in html/js/sass can be picked 
>> up directly from eclipse.
>> - title still too big, needs to scale down
>> - offline mode is not supported (both for central and the 
>> quickstarts, groovy script not update yet)
>> - quickstarts not integrated to the existing project examples wizard
>> - legacy examples are not displays in the results, yet.
>> - project requirements not inferred yet (from existing metadata?)
>> - project tags should be added
>> - maybe find another default icon for quickstarts.
>> - layout needs to be tuned (needs to scale on 3 cols, instead of 4 
>> and 2 currently)
>> - needs some tabzilla-like button (see the red hat at top right of 
>> http://tools.jboss.org/ <http://tools.jboss.org/>) to display show on 
>> startup
>> - APIs are in still unstable, expect them to break.
>> -  you might notice some slight font flickering, due to the carousel 
>> script. I tried to minimize it but it?s still visible in the search 
>> bar?s hint text
>> - many other small stuff that are missing, that I can?t think of 
>> right now.
>>
>> So, give it a try, we?d be happy to hear some feedback, good or 
>> bad, ideas to make it better (JIRA is your friend).
>>
>> Fred
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From mistria at redhat.com  Wed Apr 29 06:00:57 2015
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 29 Apr 2015 12:00:57 +0200
Subject: [jbosstools-dev] created 'easymport' component
In-Reply-To: <F8D2D974-A899-4EDA-BF56-05C7824DE19A@redhat.com>
References: <F8D2D974-A899-4EDA-BF56-05C7824DE19A@redhat.com>
Message-ID: <5540ABD9.8030508@redhat.com>

On 04/29/2015 11:19 AM, Max Rydahl Andersen wrote:
> Hi,
>
> After seeing incoming issues related to easymport being misclassified
> I've now created an 'easymport' component lead by mistria.
>
> I suggest for issues that are related to easymport + another component
> (i.e. aerogear-hybrid) has both components set, and if it is purely a
> easymport issue we can remove the other component.
Thank you. That will make things easier.

-- 
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/20150429/2fa32744/attachment.html 

From dgolovin at exadel.com  Wed Apr 29 11:37:12 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Wed, 29 Apr 2015 08:37:12 -0700
Subject: [jbosstools-dev] ATTENTION REQUIRED: missing tags
In-Reply-To: <1271287A-83DB-423D-AF9F-DC9A317D56CA@redhat.com>
References: <1271287A-83DB-423D-AF9F-DC9A317D56CA@redhat.com>
Message-ID: <CAJXFskYo9uz2LQyDz5vWyS-3gcsd3cMW7dxeprW7NgF6HqpfVw@mail.gmail.com>

I suggested tagging modules that had no changes a while ago and was told no
tagging required. That explains for example jbosstools-freemarker is
missing 12 tags.

I would tag every module w/ and w/o changes, it can be done for all ow them
using repo with submodules, becuase we are releasing them all together
anyway.

Denis

On Wed, Apr 29, 2015 at 12:51 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> I wrote a script to check how good/bad we were on actually having tags
> for the various releases.
>
> First I found the ones missing the recent Alpha2 tag:
>
> jbosstools-arquillian
> jbosstools-livereload
> jbosstools-aerogear
> jbosstools-hibernate
> jbosstools-freemarker
> jbosstools-webservices
> jbosstools-server
> jbosstools-portlet
> jbosstools-download.jboss.org
> jbosstools-central
> jbosstools-build-ci
> jbosstools-birt
>
> Then I thought about how it was looking for other releases so I made the
> script a bit more advanced
> (https://github.com/jbosstools/jbosstools-build/pull/182/files).
>
> It loads all historical tags of jbosstools-base and with a "since"
> marker to not get false positives:
>
> https://github.com/jbosstools/jbosstools-build/pull/182/files#diff-015178ddb40125e999fea74a7bb4d3d8R46
>
> With this the list is a tad longer (full details at:
> https://gist.github.com/maxandersen/8e5c311b7b0f18c95e88)
>
> jbosstools-download.jboss.org missing 13 tags
> jbosstools-freemarker missing 12 tags
> jbosstools-server missing 13 tags
> jbosstools-build-ci missing 8 tags
> jbosstools-aerogear missing 6 tags
> jbosstools-hibernate missing 6 tags
> jbosstools-birt missing 5 tags
> jbosstools-central missing 5 tags
> jbosstools-portlet missing 5 tags
> jbosstools-forge missing 4 tags
> jbosstools-webservices missing 4 tags
> jbosstools-build missing 3 tags
> jbosstools-openshift missing 3 tags
> jbosstools-build-sites missing 3 tags
> jbosstools-vpe missing 2 tags
> jbosstools-livereload missing 2 tags
> jbosstools-arquillian missing 2 tags
> jbosstools-jst missing 1 tags
> jbosstools-discovery missing 1 tags
> jbosstools-browsersim missing 1 tags
>
> If you believe my script reported wrongly on this please let me know and
> otherwise i'll create a task jira for these next week.
>
> Thanks,
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150429/5ca7ad6f/attachment.html 

From manderse at redhat.com  Wed Apr 29 12:57:52 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 29 Apr 2015 12:57:52 -0400 (EDT)
Subject: [jbosstools-dev] ATTENTION REQUIRED: missing tags
In-Reply-To: <CAJXFskYo9uz2LQyDz5vWyS-3gcsd3cMW7dxeprW7NgF6HqpfVw@mail.gmail.com>
References: <1271287A-83DB-423D-AF9F-DC9A317D56CA@redhat.com>
	<CAJXFskYo9uz2LQyDz5vWyS-3gcsd3cMW7dxeprW7NgF6HqpfVw@mail.gmail.com>
Message-ID: <6904A361-AAD5-4464-8390-C45457C43580@redhat.com>


> On 29 Apr 2015, at 17:45, Denis Golovin <dgolovin at exadel.com> wrote:
> 
> I suggested tagging modules that had no changes a while ago and was told no tagging required. That explains for example jbosstools-freemarker is missing 12 tags.

Did I say that ? Then I was for sure wrong Imo with our current setup. 

Should be easy to fix then too :)

> I would tag every module w/ and w/o changes, it can be done for all ow them using repo with submodules, becuase we are releasing them all together anyway.

Sorry - not following how sub modules relate here ?
> 
> Denis
> 
>> On Wed, Apr 29, 2015 at 12:51 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
>> I wrote a script to check how good/bad we were on actually having tags
>> for the various releases.
>> 
>> First I found the ones missing the recent Alpha2 tag:
>> 
>> jbosstools-arquillian
>> jbosstools-livereload
>> jbosstools-aerogear
>> jbosstools-hibernate
>> jbosstools-freemarker
>> jbosstools-webservices
>> jbosstools-server
>> jbosstools-portlet
>> jbosstools-download.jboss.org
>> jbosstools-central
>> jbosstools-build-ci
>> jbosstools-birt
>> 
>> Then I thought about how it was looking for other releases so I made the
>> script a bit more advanced
>> (https://github.com/jbosstools/jbosstools-build/pull/182/files).
>> 
>> It loads all historical tags of jbosstools-base and with a "since"
>> marker to not get false positives:
>> https://github.com/jbosstools/jbosstools-build/pull/182/files#diff-015178ddb40125e999fea74a7bb4d3d8R46
>> 
>> With this the list is a tad longer (full details at:
>> https://gist.github.com/maxandersen/8e5c311b7b0f18c95e88)
>> 
>> jbosstools-download.jboss.org missing 13 tags
>> jbosstools-freemarker missing 12 tags
>> jbosstools-server missing 13 tags
>> jbosstools-build-ci missing 8 tags
>> jbosstools-aerogear missing 6 tags
>> jbosstools-hibernate missing 6 tags
>> jbosstools-birt missing 5 tags
>> jbosstools-central missing 5 tags
>> jbosstools-portlet missing 5 tags
>> jbosstools-forge missing 4 tags
>> jbosstools-webservices missing 4 tags
>> jbosstools-build missing 3 tags
>> jbosstools-openshift missing 3 tags
>> jbosstools-build-sites missing 3 tags
>> jbosstools-vpe missing 2 tags
>> jbosstools-livereload missing 2 tags
>> jbosstools-arquillian missing 2 tags
>> jbosstools-jst missing 1 tags
>> jbosstools-discovery missing 1 tags
>> jbosstools-browsersim missing 1 tags
>> 
>> If you believe my script reported wrongly on this please let me know and
>> otherwise i'll create a task jira for these next week.
>> 
>> Thanks,
>> /max
>> http://about.me/maxandersen
>> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150429/c33788cb/attachment-0001.html 

From manderse at redhat.com  Wed Apr 29 12:59:06 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 29 Apr 2015 12:59:06 -0400 (EDT)
Subject: [jbosstools-dev] ACTION REQUIRED: missing tags
In-Reply-To: <1271287A-83DB-423D-AF9F-DC9A317D56CA@redhat.com>
References: <1271287A-83DB-423D-AF9F-DC9A317D56CA@redhat.com>
Message-ID: <2CE439AB-B1CA-4C84-B9BC-D22B4FAA069F@redhat.com>


Post using proper label to hope it will be seen by more eyes. 
/max
http://about.me/maxandersen


> On 29 Apr 2015, at 09:54, Max Rydahl Andersen <manderse at redhat.com> wrote:
> 
> I wrote a script to check how good/bad we were on actually having tags 
> for the various releases.
> 
> First I found the ones missing the recent Alpha2 tag:
> 
> jbosstools-arquillian
> jbosstools-livereload
> jbosstools-aerogear
> jbosstools-hibernate
> jbosstools-freemarker
> jbosstools-webservices
> jbosstools-server
> jbosstools-portlet
> jbosstools-download.jboss.org
> jbosstools-central
> jbosstools-build-ci
> jbosstools-birt
> 
> Then I thought about how it was looking for other releases so I made the 
> script a bit more advanced 
> (https://github.com/jbosstools/jbosstools-build/pull/182/files).
> 
> It loads all historical tags of jbosstools-base and with a "since" 
> marker to not get false positives: 
> https://github.com/jbosstools/jbosstools-build/pull/182/files#diff-015178ddb40125e999fea74a7bb4d3d8R46
> 
> With this the list is a tad longer (full details at: 
> https://gist.github.com/maxandersen/8e5c311b7b0f18c95e88)
> 
> jbosstools-download.jboss.org missing 13 tags
> jbosstools-freemarker missing 12 tags
> jbosstools-server missing 13 tags
> jbosstools-build-ci missing 8 tags
> jbosstools-aerogear missing 6 tags
> jbosstools-hibernate missing 6 tags
> jbosstools-birt missing 5 tags
> jbosstools-central missing 5 tags
> jbosstools-portlet missing 5 tags
> jbosstools-forge missing 4 tags
> jbosstools-webservices missing 4 tags
> jbosstools-build missing 3 tags
> jbosstools-openshift missing 3 tags
> jbosstools-build-sites missing 3 tags
> jbosstools-vpe missing 2 tags
> jbosstools-livereload missing 2 tags
> jbosstools-arquillian missing 2 tags
> jbosstools-jst missing 1 tags
> jbosstools-discovery missing 1 tags
> jbosstools-browsersim missing 1 tags
> 
> If you believe my script reported wrongly on this please let me know and
> otherwise i'll create a task jira for these next week.
> 
> Thanks,
> /max
> http://about.me/maxandersen
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From fbricon at redhat.com  Wed Apr 29 13:15:07 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Wed, 29 Apr 2015 13:15:07 -0400
Subject: [jbosstools-dev] new JBoss Central available from nightly builds
In-Reply-To: <85995023-234E-4358-9DBD-447CE242A6B9@redhat.com>
References: <460B656E-D2C2-4F87-98D2-1EB32AF9828F@redhat.com>
	<446BE661-27A4-4B49-B8E8-E417A3D5505E@redhat.com>
	<85995023-234E-4358-9DBD-447CE242A6B9@redhat.com>
Message-ID: <D0F82952-50B5-4133-9F2E-AA013504F500@redhat.com>

I?ll try adding visual indicators  (like ???? )

> Le 29 avr. 2015 ? 05:44, Max Rydahl Andersen <manderse at redhat.com> a ?crit :
> 
> On 29 Apr 2015, at 11:20, Martin Malina wrote:
> 
>> Hi Fred,
>> 
>> Great job! I like the design, it looks clean. And the search is super fast.
>> What I don't quite like so much is the carousel. You can't control it and it can be a little distracting.
>> For other arguments see http://shouldiuseacarousel.com <http://shouldiuseacarousel.com/> :) But maybe it's just me :)
>> And I understand we do want to put the blogs somewhere.
> 
> I have the same concern, but I think this small "ticker" is less of a problem than the usual giant carousel's that shouldiuseacarousel.com goes against.
> 
> At least thats what I feel now - lets see what the feedback is and if we are getting more or less clicks on the entries ;)
> 
> /max
> 
>> 
>> -Martin
>> 
>> 
>>> On 27. 4. 2015, at 6:11, Fred Bricon <fbricon at redhat.com> wrote:
>>> 
>>> Hi,
>>> 
>>> FYI, I?ve merged the current Central/HTML5 rework to jbosstools-central master.
>>> This means you can see the new Central in action after installing the latest nightly build from http://download.jboss.org/jbosstools/updates/nightly/mars/ <http://download.jboss.org/jbosstools/updates/nightly/mars/>
>>> 
>>> It?s far from being complete, but you?ll at least get a taste of what?s to come in JBT 4.3/JBDS 9.
>>> 
>>> What works :
>>> - Central is now an html5 page maintained at  https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage>
>>> - the page is served from a swt browser widget (using webkit under the hood).
>>> - about 220 quickstarts are available as of today (some target eap 6.3, other target 6.4)
>>> - search is craaazy fast, as it is local to the webpage (no round trips to dcp server)
>>> - it?s fast to load and scales better in small windows, compared to the existing version.
>>> - proxy wizards are injected to search results
>>> - external links are opened in a browser window
>>> - JBoss Buzz results visible as carousel under the title
>>> - early access label displayed according to EA settings (UI to be reviewed)
>>> - you can build https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage> locally (after installing node and grunt-cli) and test it by starting Eclipse with -Djboss.central.webpage.url=file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip <file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip> or -Djboss.central.webpage.url=/path/to/jbosstools-central-webpage/target/gruntbuild.
>>> 
>>> What doesn?t work :
>>> - for some reason I just broke the quickstart integration, which used to work, I swear. Will fix it on Monday
>>> - current webpage is served directly from http://central-fredapp.rhcloud.com/ <http://central-fredapp.rhcloud.com/>, I need to get https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage> built from Jenkins and deployed to Nexus. At least that gives us some good flexibility in terms of maintenance.
>>> - search engine uses staging dcpbeta-searchisko.rhcloud.com/ <http://dcpbeta-searchisko.rhcloud.com/> service, instead of dcp.jboss.org <http://dcp.jboss.org/>
>>> - The development workflow isn?t finalized yet. I need to set up and tune grunt watch, so that changes in html/js/sass can be picked up directly from eclipse.
>>> - title still too big, needs to scale down
>>> - offline mode is not supported (both for central and the quickstarts, groovy script not update yet)
>>> - quickstarts not integrated to the existing project examples wizard
>>> - legacy examples are not displays in the results, yet.
>>> - project requirements not inferred yet (from existing metadata?)
>>> - project tags should be added
>>> - maybe find another default icon for quickstarts.
>>> - layout needs to be tuned (needs to scale on 3 cols, instead of 4 and 2 currently)
>>> - needs some tabzilla-like button (see the red hat at top right of http://tools.jboss.org/ <http://tools.jboss.org/>) to display show on startup
>>> - APIs are in still unstable, expect them to break.
>>> -  you might notice some slight font flickering, due to the carousel script. I tried to minimize it but it?s still visible in the search bar?s hint text
>>> - many other small stuff that are missing, that I can?t think of right now.
>>> 
>>> So, give it a try, we?d be happy to hear some feedback, good or bad, ideas to make it better (JIRA is your friend).
>>> 
>>> Fred
>>> 
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> 
> /max
> http://about.me/maxandersen



From dgolovin at exadel.com  Wed Apr 29 13:34:52 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Wed, 29 Apr 2015 10:34:52 -0700
Subject: [jbosstools-dev] ATTENTION REQUIRED: missing tags
In-Reply-To: <6904A361-AAD5-4464-8390-C45457C43580@redhat.com>
References: <1271287A-83DB-423D-AF9F-DC9A317D56CA@redhat.com>
	<CAJXFskYo9uz2LQyDz5vWyS-3gcsd3cMW7dxeprW7NgF6HqpfVw@mail.gmail.com>
	<6904A361-AAD5-4464-8390-C45457C43580@redhat.com>
Message-ID: <CAJXFskY1g9rLyq1KhtQr7fLvoEv2UzkY5Mvzrd8s2PjHKx5kOA@mail.gmail.com>

with https://github.com/dgolovin/jbosstools-releng.git tagging of
everything at once would look like:

git submodule foreach 'git checkout jbosstools-4.3.0.Alpha2x; git pull
origin jbosstools-4.3.0.Alpha2x; git tag jbosstools-4.3.0.Alpha2; git push
origin jbosstools-4.3.0.Alpha2;'

The same can be done with shell or any script we want to use.

Denis

On Wed, Apr 29, 2015 at 9:57 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

>
> On 29 Apr 2015, at 17:45, Denis Golovin <dgolovin at exadel.com> wrote:
>
> I suggested tagging modules that had no changes a while ago and was told
> no tagging required. That explains for example jbosstools-freemarker is
> missing 12 tags.
>
>
> Did I say that ? Then I was for sure wrong Imo with our current setup.
>
> Should be easy to fix then too :)
>
> I would tag every module w/ and w/o changes, it can be done for all ow
> them using repo with submodules, becuase we are releasing them all together
> anyway.
>
>
> Sorry - not following how sub modules relate here ?
>
>
> Denis
>
> On Wed, Apr 29, 2015 at 12:51 AM, Max Rydahl Andersen <manderse at redhat.com
> > wrote:
>
>> I wrote a script to check how good/bad we were on actually having tags
>> for the various releases.
>>
>> First I found the ones missing the recent Alpha2 tag:
>>
>> jbosstools-arquillian
>> jbosstools-livereload
>> jbosstools-aerogear
>> jbosstools-hibernate
>> jbosstools-freemarker
>> jbosstools-webservices
>> jbosstools-server
>> jbosstools-portlet
>> jbosstools-download.jboss.org
>> jbosstools-central
>> jbosstools-build-ci
>> jbosstools-birt
>>
>> Then I thought about how it was looking for other releases so I made the
>> script a bit more advanced
>> (https://github.com/jbosstools/jbosstools-build/pull/182/files).
>>
>> It loads all historical tags of jbosstools-base and with a "since"
>> marker to not get false positives:
>>
>> https://github.com/jbosstools/jbosstools-build/pull/182/files#diff-015178ddb40125e999fea74a7bb4d3d8R46
>>
>> With this the list is a tad longer (full details at:
>> https://gist.github.com/maxandersen/8e5c311b7b0f18c95e88)
>>
>> jbosstools-download.jboss.org missing 13 tags
>> jbosstools-freemarker missing 12 tags
>> jbosstools-server missing 13 tags
>> jbosstools-build-ci missing 8 tags
>> jbosstools-aerogear missing 6 tags
>> jbosstools-hibernate missing 6 tags
>> jbosstools-birt missing 5 tags
>> jbosstools-central missing 5 tags
>> jbosstools-portlet missing 5 tags
>> jbosstools-forge missing 4 tags
>> jbosstools-webservices missing 4 tags
>> jbosstools-build missing 3 tags
>> jbosstools-openshift missing 3 tags
>> jbosstools-build-sites missing 3 tags
>> jbosstools-vpe missing 2 tags
>> jbosstools-livereload missing 2 tags
>> jbosstools-arquillian missing 2 tags
>> jbosstools-jst missing 1 tags
>> jbosstools-discovery missing 1 tags
>> jbosstools-browsersim missing 1 tags
>>
>> If you believe my script reported wrongly on this please let me know and
>> otherwise i'll create a task jira for these next week.
>>
>> Thanks,
>> /max
>> http://about.me/maxandersen
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150429/3588cb60/attachment.html 

From manderse at redhat.com  Wed Apr 29 13:51:42 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 29 Apr 2015 13:51:42 -0400 (EDT)
Subject: [jbosstools-dev] new JBoss Central available from nightly builds
In-Reply-To: <D0F82952-50B5-4133-9F2E-AA013504F500@redhat.com>
References: <460B656E-D2C2-4F87-98D2-1EB32AF9828F@redhat.com>
	<446BE661-27A4-4B49-B8E8-E417A3D5505E@redhat.com>
	<85995023-234E-4358-9DBD-447CE242A6B9@redhat.com>
	<D0F82952-50B5-4133-9F2E-AA013504F500@redhat.com>
Message-ID: <3DE3A0C6-D64D-400F-87CC-93D11E88B49A@redhat.com>

How about just a single link that will show the full carousel/rss ?

/max
http://about.me/maxandersen


> On 29 Apr 2015, at 19:15, Fred Bricon <fbricon at redhat.com> wrote:
> 
> I?ll try adding visual indicators  (like ???? )
> 
>> Le 29 avr. 2015 ? 05:44, Max Rydahl Andersen <manderse at redhat.com> a ?crit :
>> 
>> On 29 Apr 2015, at 11:20, Martin Malina wrote:
>> 
>>> Hi Fred,
>>> 
>>> Great job! I like the design, it looks clean. And the search is super fast.
>>> What I don't quite like so much is the carousel. You can't control it and it can be a little distracting.
>>> For other arguments see http://shouldiuseacarousel.com <http://shouldiuseacarousel.com/> :) But maybe it's just me :)
>>> And I understand we do want to put the blogs somewhere.
>> 
>> I have the same concern, but I think this small "ticker" is less of a problem than the usual giant carousel's that shouldiuseacarousel.com goes against.
>> 
>> At least thats what I feel now - lets see what the feedback is and if we are getting more or less clicks on the entries ;)
>> 
>> /max
>> 
>>> 
>>> -Martin
>>> 
>>> 
>>>> On 27. 4. 2015, at 6:11, Fred Bricon <fbricon at redhat.com> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> FYI, I?ve merged the current Central/HTML5 rework to jbosstools-central master.
>>>> This means you can see the new Central in action after installing the latest nightly build from http://download.jboss.org/jbosstools/updates/nightly/mars/ <http://download.jboss.org/jbosstools/updates/nightly/mars/>
>>>> 
>>>> It?s far from being complete, but you?ll at least get a taste of what?s to come in JBT 4.3/JBDS 9.
>>>> 
>>>> What works :
>>>> - Central is now an html5 page maintained at  https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage>
>>>> - the page is served from a swt browser widget (using webkit under the hood).
>>>> - about 220 quickstarts are available as of today (some target eap 6.3, other target 6.4)
>>>> - search is craaazy fast, as it is local to the webpage (no round trips to dcp server)
>>>> - it?s fast to load and scales better in small windows, compared to the existing version.
>>>> - proxy wizards are injected to search results
>>>> - external links are opened in a browser window
>>>> - JBoss Buzz results visible as carousel under the title
>>>> - early access label displayed according to EA settings (UI to be reviewed)
>>>> - you can build https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage> locally (after installing node and grunt-cli) and test it by starting Eclipse with -Djboss.central.webpage.url=file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip <file:///path/to/jbosstools-central-webpage/target/jbosstools-central-webpage-0.0.1-SNAPSHOT.zip> or -Djboss.central.webpage.url=/path/to/jbosstools-central-webpage/target/gruntbuild.
>>>> 
>>>> What doesn?t work :
>>>> - for some reason I just broke the quickstart integration, which used to work, I swear. Will fix it on Monday
>>>> - current webpage is served directly from http://central-fredapp.rhcloud.com/ <http://central-fredapp.rhcloud.com/>, I need to get https://github.com/jbosstools/jbosstools-central-webpage <https://github.com/jbosstools/jbosstools-central-webpage> built from Jenkins and deployed to Nexus. At least that gives us some good flexibility in terms of maintenance.
>>>> - search engine uses staging dcpbeta-searchisko.rhcloud.com/ <http://dcpbeta-searchisko.rhcloud.com/> service, instead of dcp.jboss.org <http://dcp.jboss.org/>
>>>> - The development workflow isn?t finalized yet. I need to set up and tune grunt watch, so that changes in html/js/sass can be picked up directly from eclipse.
>>>> - title still too big, needs to scale down
>>>> - offline mode is not supported (both for central and the quickstarts, groovy script not update yet)
>>>> - quickstarts not integrated to the existing project examples wizard
>>>> - legacy examples are not displays in the results, yet.
>>>> - project requirements not inferred yet (from existing metadata?)
>>>> - project tags should be added
>>>> - maybe find another default icon for quickstarts.
>>>> - layout needs to be tuned (needs to scale on 3 cols, instead of 4 and 2 currently)
>>>> - needs some tabzilla-like button (see the red hat at top right of http://tools.jboss.org/ <http://tools.jboss.org/>) to display show on startup
>>>> - APIs are in still unstable, expect them to break.
>>>> -  you might notice some slight font flickering, due to the carousel script. I tried to minimize it but it?s still visible in the search bar?s hint text
>>>> - many other small stuff that are missing, that I can?t think of right now.
>>>> 
>>>> So, give it a try, we?d be happy to hear some feedback, good or bad, ideas to make it better (JIRA is your friend).
>>>> 
>>>> Fred
>>>> 
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>> 
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> 
>> 
>> /max
>> http://about.me/maxandersen
> 


From manderse at redhat.com  Wed Apr 29 13:54:42 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 29 Apr 2015 13:54:42 -0400 (EDT)
Subject: [jbosstools-dev] ATTENTION REQUIRED: missing tags
In-Reply-To: <CAJXFskY1g9rLyq1KhtQr7fLvoEv2UzkY5Mvzrd8s2PjHKx5kOA@mail.gmail.com>
References: <1271287A-83DB-423D-AF9F-DC9A317D56CA@redhat.com>
	<CAJXFskYo9uz2LQyDz5vWyS-3gcsd3cMW7dxeprW7NgF6HqpfVw@mail.gmail.com>
	<6904A361-AAD5-4464-8390-C45457C43580@redhat.com>
	<CAJXFskY1g9rLyq1KhtQr7fLvoEv2UzkY5Mvzrd8s2PjHKx5kOA@mail.gmail.com>
Message-ID: <A1DC19F0-612E-421A-9171-B079C5DD6A64@redhat.com>


> On 29 Apr 2015, at 19:34, Denis Golovin <dgolovin at exadel.com> wrote:
> 
> with https://github.com/dgolovin/jbosstools-releng.git tagging of everything at once would look like:
> 
> git submodule foreach 'git checkout jbosstools-4.3.0.Alpha2x; git pull origin jbosstools-4.3.0.Alpha2x; git tag jbosstools-4.3.0.Alpha2; git push origin jbosstools-4.3.0.Alpha2;'
> 
> The same can be done with shell or any script we want to use. 

Sure. Don't need sub modules for this though. 

But yeah seems time to enable jbossjenkins user push rights to do these since it's obviously not happening consistently across all repos. I would prefer it actually tagged the sha1 that was used instead of just assumed used. 

/max
> 
> Denis
> 
>> On Wed, Apr 29, 2015 at 9:57 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
>> 
>>> On 29 Apr 2015, at 17:45, Denis Golovin <dgolovin at exadel.com> wrote:
>>> 
>>> I suggested tagging modules that had no changes a while ago and was told no tagging required. That explains for example jbosstools-freemarker is missing 12 tags.
>> 
>> Did I say that ? Then I was for sure wrong Imo with our current setup. 
>> 
>> Should be easy to fix then too :)
>> 
>>> I would tag every module w/ and w/o changes, it can be done for all ow them using repo with submodules, becuase we are releasing them all together anyway.
>> 
>> Sorry - not following how sub modules relate here ?
>> 
>>> 
>>> Denis
>>> 
>>>> On Wed, Apr 29, 2015 at 12:51 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
>>>> I wrote a script to check how good/bad we were on actually having tags
>>>> for the various releases.
>>>> 
>>>> First I found the ones missing the recent Alpha2 tag:
>>>> 
>>>> jbosstools-arquillian
>>>> jbosstools-livereload
>>>> jbosstools-aerogear
>>>> jbosstools-hibernate
>>>> jbosstools-freemarker
>>>> jbosstools-webservices
>>>> jbosstools-server
>>>> jbosstools-portlet
>>>> jbosstools-download.jboss.org
>>>> jbosstools-central
>>>> jbosstools-build-ci
>>>> jbosstools-birt
>>>> 
>>>> Then I thought about how it was looking for other releases so I made the
>>>> script a bit more advanced
>>>> (https://github.com/jbosstools/jbosstools-build/pull/182/files).
>>>> 
>>>> It loads all historical tags of jbosstools-base and with a "since"
>>>> marker to not get false positives:
>>>> https://github.com/jbosstools/jbosstools-build/pull/182/files#diff-015178ddb40125e999fea74a7bb4d3d8R46
>>>> 
>>>> With this the list is a tad longer (full details at:
>>>> https://gist.github.com/maxandersen/8e5c311b7b0f18c95e88)
>>>> 
>>>> jbosstools-download.jboss.org missing 13 tags
>>>> jbosstools-freemarker missing 12 tags
>>>> jbosstools-server missing 13 tags
>>>> jbosstools-build-ci missing 8 tags
>>>> jbosstools-aerogear missing 6 tags
>>>> jbosstools-hibernate missing 6 tags
>>>> jbosstools-birt missing 5 tags
>>>> jbosstools-central missing 5 tags
>>>> jbosstools-portlet missing 5 tags
>>>> jbosstools-forge missing 4 tags
>>>> jbosstools-webservices missing 4 tags
>>>> jbosstools-build missing 3 tags
>>>> jbosstools-openshift missing 3 tags
>>>> jbosstools-build-sites missing 3 tags
>>>> jbosstools-vpe missing 2 tags
>>>> jbosstools-livereload missing 2 tags
>>>> jbosstools-arquillian missing 2 tags
>>>> jbosstools-jst missing 1 tags
>>>> jbosstools-discovery missing 1 tags
>>>> jbosstools-browsersim missing 1 tags
>>>> 
>>>> If you believe my script reported wrongly on this please let me know and
>>>> otherwise i'll create a task jira for these next week.
>>>> 
>>>> Thanks,
>>>> /max
>>>> http://about.me/maxandersen
>>>> 
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150429/563416c2/attachment.html 

From manderse at redhat.com  Thu Apr 30 07:10:28 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 30 Apr 2015 13:10:28 +0200
Subject: [jbosstools-dev] antlr packages and lib not exported in
 Hibernate Tools 4.0.1
In-Reply-To: <A86EAF8E-5B33-4ABB-9C4A-F61DB208E120@redhat.com>
References: <CAFEyyCJu+-LgoQ5HuCDhy9Kn9sPLSUB1+vOwoOD8-8BhLU=oQw@mail.gmail.com>
	<55353EFE.6040702@exadel.com>
	<A86EAF8E-5B33-4ABB-9C4A-F61DB208E120@redhat.com>
Message-ID: <1B447044-6635-41D2-93C0-290914707E33@redhat.com>

Bastian - did you get your problem solved ?

> On 20 Apr 2015, at 20:01, Alexey Kazakov wrote:
>
>> First at all, please create an issue in
>> https://issues.jboss.org/browse/JBIDE to solve this problem in the
>> next release.
>> A pull request for https://github.com/jbosstools/jbosstools-hibernate
>> would be useful too :)
>
> please note that we are really trying to limit exposing any of hibernate
> internal runtime API's to support multiple versions of Hibernate. Thus
> if this break that we won't be able to do it.
>
> What is your plugin trying to do that needs this level of access ?
>
> /max
>>
>> On 04/20/2015 04:44 AM, Bastian Ugimachi wrote:
>>>
>>> Dear all,
>>>
>>> I am currently working on an Eclipse-Plugin that is built on top of
>>> the Hibernate Tools project. For example, I am using the following
>>> statements to get the AST of a named query:
>>>
>>> try {
>>> HqlParser parser = HqlParser.getInstance(statementString);
>>> parser.statement();
>>> } catch (RecognitionException | TokenStreamException e) {
>>> e.printStackTrace();
>>> }
>>> AST statementAst = parser.getAST();
>>>
>>> For this to work well with Hibernate Tools Version 4.0.0, I added
>>> bundle org.hibernate.eclipse.libs as required bundle to my plug-in
>>> configuration (which resolved to
>>> org.hibernate.eclipse.libs_4.0.0.Final-v20141016-1911-B82 so far).
>>>
>>> However, I now updated to Hiberate Tools 4.0.1
>>> (org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95). The
>>> problem I have now is that the following imports cannot be resolved:
>>> import antlr.RecognitionException;
>>> import antlr.TokenStreamException;
>>> import antlr.collections.AST;
>>>
>>> The problem seems to arise from the fact, that in the new version's
>>> MANIFEST.MF, the antlr... packages are not exported and
>>> lib/hibernate/antlr-2.7.6.jar is not listed in the Bundle-ClassPath
>>> any more (I reformatted both MANIFEST.MFs, that you can find
>>> attached, to allow a convenient comparison). After manually adding
>>> the antlr-related entries to the new version's MANIFEST.MF, my code
>>> works pretty well again.
>>>
>>> My question is thus:
>>> (a) Do you consider this to be a bug in the realease of Hibernate
>>> Tools 4.0.1?
>>> (b) If yes for (a): Do you have an idea when this issue could be
>>> solved?
>>> (c) If no for (a): Which alternative solution would you suggest? I
>>> mean, manually editing the MANIFEST.MF of realeased plug-ins is not
>>> quite the best practice, is it? I tried to manally add
>>> antlr-2.7.6.jar as library to my project, which solved the
>>> compilation error, but yields a java.lang.ClassNotFoundException:
>>> antlr.LLkParser cannot be found by
>>> org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95
>>>
>>> Any advice?
>>>
>>> Thanks!
>>> Bastian
>>>
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From manderse at redhat.com  Thu Apr 30 07:21:50 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 30 Apr 2015 13:21:50 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <553F9459.8000805@redhat.com>
References: <553EB6B5.9040609@redhat.com> <553F9459.8000805@redhat.com>
Message-ID: <C05844B0-8B40-449D-9BA1-BCBF919D2FAB@redhat.com>


Done for livereload and webservices - xcoulon is on PTO so I did it for him.

posted here since getting these tags recorded are important.

Things the tags are used for:
 * build of jbosstools at fedora
 * checking what went into a release when debugging
 * knowing which components got into a relase
 
Still missing:
 jbosstools-portlet
 jbosstools-freemarker
 jbosstools-hibernate
 jbosstools-aerogear
 jbosstools-arquillian
 jbosstools-download.jboss.org
 jbosstools-build-ci
 jbosstools-birt

/max
 
> Done for forge
>
> On 04/27/2015 07:22 PM, Nick Boldt wrote:
>> Component leads, please tag your repositories!
>>
>>  git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>> called jbosstools, also often called origin
>>  git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>  git push jbosstools jbosstools-4.3.0.Alpha2
>>
>>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From dgolovin at exadel.com  Thu Apr 30 16:30:32 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Thu, 30 Apr 2015 13:30:32 -0700
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <C05844B0-8B40-449D-9BA1-BCBF919D2FAB@redhat.com>
References: <553EB6B5.9040609@redhat.com> <553F9459.8000805@redhat.com>
	<C05844B0-8B40-449D-9BA1-BCBF919D2FAB@redhat.com>
Message-ID: <CAJXFskbV3n5WMArR+4n8LRt6nuHwQ6k-HNE807NDC3eaX3zp2w@mail.gmail.com>

Done for freemarker.

Should we run tagging verification script after release is declared and it
would keep pinging component leads until tag is created?

On Thu, Apr 30, 2015 at 4:21 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

>
> Done for livereload and webservices - xcoulon is on PTO so I did it for
> him.
>
> posted here since getting these tags recorded are important.
>
> Things the tags are used for:
>  * build of jbosstools at fedora
>  * checking what went into a release when debugging
>  * knowing which components got into a relase
>
> Still missing:
>  jbosstools-portlet
>  jbosstools-freemarker
>  jbosstools-hibernate
>  jbosstools-aerogear
>  jbosstools-arquillian
>  jbosstools-download.jboss.org
>  jbosstools-build-ci
>  jbosstools-birt
>
> /max
>
> > Done for forge
> >
> > On 04/27/2015 07:22 PM, Nick Boldt wrote:
> >> Component leads, please tag your repositories!
> >>
> >>  git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
> >> called jbosstools, also often called origin
> >>  git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
> >>  git push jbosstools jbosstools-4.3.0.Alpha2
> >>
> >>
> >
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150430/d41f1606/attachment.html 

From nboldt at redhat.com  Thu Apr 30 16:54:00 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 30 Apr 2015 16:54:00 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <C05844B0-8B40-449D-9BA1-BCBF919D2FAB@redhat.com>
References: <553EB6B5.9040609@redhat.com> <553F9459.8000805@redhat.com>
	<C05844B0-8B40-449D-9BA1-BCBF919D2FAB@redhat.com>
Message-ID: <55429668.7000102@redhat.com>

jbosstools-4.2.3.Final tag created for jbosstools-build (even though we 
still have https://issues.jboss.org/browse/JBIDE-19744 open pending a fix).

For these 2 projects below, branches don't exist for 4.3.0.Alpha2x so I 
could not create tags. Will create branches for Beta1x and tag next time.

* jbosstools-build-ci
* jbosstools-download.jboss.org

Do you need me to compute which old SHAs map to old tags like 
4.0.0.Final or 4.1.0.Beta1? Since those releases are done and we will 
only ever be building forward from 4.2.x (after 4.2.3.Final) and 4.3.x 
(after 4.3.0.Alpha2), do we need to go back into the past to create old 
tags?

Nick

On 04/30/2015 07:21 AM, Max Rydahl Andersen wrote:
>
> Done for livereload and webservices - xcoulon is on PTO so I did it for him.
>
> posted here since getting these tags recorded are important.
>
> Things the tags are used for:
>   * build of jbosstools at fedora
>   * checking what went into a release when debugging
>   * knowing which components got into a relase
>
> Still missing:
>   jbosstools-portlet
>   jbosstools-freemarker
>   jbosstools-hibernate
>   jbosstools-aerogear
>   jbosstools-arquillian
>   jbosstools-download.jboss.org
>   jbosstools-build-ci
>   jbosstools-birt
>
> /max
>
>> Done for forge
>>
>> On 04/27/2015 07:22 PM, Nick Boldt wrote:
>>> Component leads, please tag your repositories!
>>>
>>>   git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>>> called jbosstools, also often called origin
>>>   git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>>   git push jbosstools jbosstools-4.3.0.Alpha2
>>>
>>>
>>
>> _______________________________________________
>> 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 manderse at redhat.com  Thu Apr 30 19:12:28 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 01 May 2015 01:12:28 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <CAJXFskbV3n5WMArR+4n8LRt6nuHwQ6k-HNE807NDC3eaX3zp2w@mail.gmail.com>
References: <553EB6B5.9040609@redhat.com> <553F9459.8000805@redhat.com>
	<C05844B0-8B40-449D-9BA1-BCBF919D2FAB@redhat.com>
	<CAJXFskbV3n5WMArR+4n8LRt6nuHwQ6k-HNE807NDC3eaX3zp2w@mail.gmail.com>
Message-ID: <E12333C9-88E3-4D19-9C9F-62E4CDD6FCBA@redhat.com>

On 30 Apr 2015, at 22:30, Denis Golovin wrote:

> Done for freemarker.

thanks!

script still finds these missing though.

jbosstools-freemarker missing 11 tags:
   jbosstools-4.1.0.Beta1,
   jbosstools-4.1.1.Beta1,
   jbosstools-4.1.1.CR1,
   jbosstools-4.1.1.Final,
   jbosstools-4.1.2.Final,
   jbosstools-4.2.0.Alpha1,
   jbosstools-4.2.0.Beta1,
   jbosstools-4.2.0.Beta2,
   jbosstools-4.2.3.Beta1,
   jbosstools-4.2.3.CR1,
   jbosstools-4.3.0.Alpha1

so I assume you just did it for alpha2, right ?

> Should we run tagging verification script after release is declared 
> and it
> would keep pinging component leads until tag is created?

yeah - but I think I got a script now that can do this via github api 
meaning I need no
git clones etc. just the list of repos and sha1's that our builds should 
have.

see other mail.

/max

>
> On Thu, Apr 30, 2015 at 4:21 AM, Max Rydahl Andersen 
> <manderse at redhat.com>
> wrote:
>
>>
>> Done for livereload and webservices - xcoulon is on PTO so I did it 
>> for
>> him.
>>
>> posted here since getting these tags recorded are important.
>>
>> Things the tags are used for:
>> * build of jbosstools at fedora
>> * checking what went into a release when debugging
>> * knowing which components got into a relase
>>
>> Still missing:
>> jbosstools-portlet
>> jbosstools-freemarker
>> jbosstools-hibernate
>> jbosstools-aerogear
>> jbosstools-arquillian
>> jbosstools-download.jboss.org
>> jbosstools-build-ci
>> jbosstools-birt
>>
>> /max
>>
>>> Done for forge
>>>
>>> On 04/27/2015 07:22 PM, Nick Boldt wrote:
>>>> Component leads, please tag your repositories!
>>>>
>>>> git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>>>> called jbosstools, also often called origin
>>>> git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>>> git push jbosstools jbosstools-4.3.0.Alpha2
>>>>
>>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>> /max
>> http://about.me/maxandersen
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>


/max
http://about.me/maxandersen

From manderse at redhat.com  Thu Apr 30 19:17:47 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 01 May 2015 01:17:47 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <55429668.7000102@redhat.com>
References: <553EB6B5.9040609@redhat.com> <553F9459.8000805@redhat.com>
	<C05844B0-8B40-449D-9BA1-BCBF919D2FAB@redhat.com>
	<55429668.7000102@redhat.com>
Message-ID: <E079B590-4EDD-49D4-BEAA-C7E4066A3C09@redhat.com>

On 30 Apr 2015, at 22:54, Nick Boldt wrote:

> jbosstools-4.2.3.Final tag created for jbosstools-build (even though 
> we
> still have https://issues.jboss.org/browse/JBIDE-19744 open pending a 
> fix).

since that fix was not in when we did 4.2.3.Final then that is the 
correct state to tag.

> For these 2 projects below, branches don't exist for 4.3.0.Alpha2x so 
> I
> could not create tags. Will create branches for Beta1x and tag next 
> time.
>
> * jbosstools-build-ci

This one seem to be the important one since it has the jenkins jobs in 
use etc.

> * jbosstools-download.jboss.org

This one I wasn't sure about - might just make sense to do like we do 
for website.
tag when we push changes live ?

> Do you need me to compute which old SHAs map to old tags like
> 4.0.0.Final or 4.1.0.Beta1? Since those releases are done and we will
> only ever be building forward from 4.2.x (after 4.2.3.Final) and 4.3.x
> (after 4.3.0.Alpha2), do we need to go back into the past to create 
> old
> tags?

so I created a script that takes a csv file in this format:

orgname/reponame1, sha1
orgname/reponame2, sha1
...

and does tagging across all repo listed with name given as input.

Now, we have for years said we gathered what went into our builds (repos 
and their sha1's).

So here is the test for that  - can you provide me with those so we can 
generate that csv file
and we can fix the tags easily for missed pass commits ? (doesn't have 
to be today today, but just to
know how hard it would be to get this info we've said we collected per 
build)

...and we can setup this script for future
releases too.

/max
>
> Nick
>
> On 04/30/2015 07:21 AM, Max Rydahl Andersen wrote:
>>
>> Done for livereload and webservices - xcoulon is on PTO so I did it 
>> for him.
>>
>> posted here since getting these tags recorded are important.
>>
>> Things the tags are used for:
>> * build of jbosstools at fedora
>> * checking what went into a release when debugging
>> * knowing which components got into a relase
>>
>> Still missing:
>> jbosstools-portlet
>> jbosstools-freemarker
>> jbosstools-hibernate
>> jbosstools-aerogear
>> jbosstools-arquillian
>> jbosstools-download.jboss.org
>> jbosstools-build-ci
>> jbosstools-birt
>>
>> /max
>>
>>> Done for forge
>>>
>>> On 04/27/2015 07:22 PM, Nick Boldt wrote:
>>>> Component leads, please tag your repositories!
>>>>
>>>> git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>>>> called jbosstools, also often called origin
>>>> git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>>> git push jbosstools jbosstools-4.3.0.Alpha2
>>>>
>>>>
>>>
>>> _______________________________________________
>>> 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
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From dgolovin at exadel.com  Thu Apr 30 19:19:33 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Thu, 30 Apr 2015 16:19:33 -0700
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha2x -> tag
 jbosstools-4.3.0.Alpha2 ]
In-Reply-To: <E12333C9-88E3-4D19-9C9F-62E4CDD6FCBA@redhat.com>
References: <553EB6B5.9040609@redhat.com> <553F9459.8000805@redhat.com>
	<C05844B0-8B40-449D-9BA1-BCBF919D2FAB@redhat.com>
	<CAJXFskbV3n5WMArR+4n8LRt6nuHwQ6k-HNE807NDC3eaX3zp2w@mail.gmail.com>
	<E12333C9-88E3-4D19-9C9F-62E4CDD6FCBA@redhat.com>
Message-ID: <CAJXFskYwpA8yEcQaxaa0UM3jAyMbKvZwZyHkrJbWmuwTBB7Miw@mail.gmail.com>

On Thu, Apr 30, 2015 at 4:12 PM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> On 30 Apr 2015, at 22:30, Denis Golovin wrote:
>
>  Done for freemarker.
>>
>
> thanks!
>
> script still finds these missing though.
>
> jbosstools-freemarker missing 11 tags:
>   jbosstools-4.1.0.Beta1,
>   jbosstools-4.1.1.Beta1,
>   jbosstools-4.1.1.CR1,
>   jbosstools-4.1.1.Final,
>   jbosstools-4.1.2.Final,
>   jbosstools-4.2.0.Alpha1,
>   jbosstools-4.2.0.Beta1,
>   jbosstools-4.2.0.Beta2,
>   jbosstools-4.2.3.Beta1,
>   jbosstools-4.2.3.CR1,
>   jbosstools-4.3.0.Alpha1
>
> so I assume you just did it for alpha2, right ?


Yeah, alpha2 only.



>
>
>  Should we run tagging verification script after release is declared and it
>> would keep pinging component leads until tag is created?
>>
>
> yeah - but I think I got a script now that can do this via github api
> meaning I need no
> git clones etc. just the list of repos and sha1's that our builds should
> have.
>
> see other mail.
>
> /max
>
>
>
>> On Thu, Apr 30, 2015 at 4:21 AM, Max Rydahl Andersen <manderse at redhat.com
>> >
>> wrote:
>>
>>
>>> Done for livereload and webservices - xcoulon is on PTO so I did it for
>>> him.
>>>
>>> posted here since getting these tags recorded are important.
>>>
>>> Things the tags are used for:
>>> * build of jbosstools at fedora
>>> * checking what went into a release when debugging
>>> * knowing which components got into a relase
>>>
>>> Still missing:
>>> jbosstools-portlet
>>> jbosstools-freemarker
>>> jbosstools-hibernate
>>> jbosstools-aerogear
>>> jbosstools-arquillian
>>> jbosstools-download.jboss.org
>>> jbosstools-build-ci
>>> jbosstools-birt
>>>
>>> /max
>>>
>>>  Done for forge
>>>>
>>>> On 04/27/2015 07:22 PM, Nick Boldt wrote:
>>>>
>>>>> Component leads, please tag your repositories!
>>>>>
>>>>> git fetch jbosstools jbosstools-4.3.0.Alpha2x #assuming remote is
>>>>> called jbosstools, also often called origin
>>>>> git tag jbosstools-4.3.0.Alpha2 FETCH_HEAD
>>>>> git push jbosstools jbosstools-4.3.0.Alpha2
>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>
> /max
> http://about.me/maxandersen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150430/238c906f/attachment.html