From manderse at redhat.com  Mon Feb  2 03:15:50 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Mon, 2 Feb 2015 03:15:50 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201502020815.t128FoYW004520@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-3338

https://issues.jboss.org/browse/JBDS-3338
Summary: JBDS Build fails with Tycho 0.22

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:13:28.627342

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



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

From manderse at redhat.com  Mon Feb  2 03:26:36 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 02 Feb 2015 09:26:36 +0100
Subject: [jbosstools-dev] [Soa-tools-list] Proposed change for JBTIS
 target platform - 4.2.1.Final/ 4.2.1.EA
In-Reply-To: <1404461509.2075378.1422467387662.JavaMail.zimbra@redhat.com>
References: <1533555605.1912221.1422455127829.JavaMail.zimbra@redhat.com>
	<1907164677.2038816.1422455546313.JavaMail.zimbra@redhat.com>
	<2105361652.1935236.1422456719150.JavaMail.zimbra@redhat.com>
	<5BE56C66-4DB9-4BB5-B543-9A1A0EA4295F@redhat.com>
	<273575204.2003723.1422461087092.JavaMail.zimbra@redhat.com>
	<8606DF9C-6D44-485E-92D8-583895421F14@redhat.com>
	<1404461509.2075378.1422467387662.JavaMail.zimbra@redhat.com>
Message-ID: <EB320A6B-D8E5-417C-9BB4-7D42C84850A2@redhat.com>

On 28 Jan 2015, at 18:49, Paul Leacu wrote:

> Okay - I'm in complete agreement that bpel/ bpmn2 modeler should 
> migrate out of the JBTIS
> TP but it will take time for the existing tools which rely on it 
> (SwitchYard + ??) to change.
> So - since this is for a CR2 IS release (soon to be .Final/.GA) and a 
> .Final/EA TP release -
> let me propose the following:
>
> 1.  I create a Jira for the removal of bpel/ bpmn2 modeler from the 
> JBTIS TP.

since it seem to continue being a "problem" with bpel/bpmn2 to update 
then this sounds like current best way forward.

> 2.  We go ahead with the JBTIS TP split as specified in JBTIS-382 so 
> we can get CR2 to QE for JDV.

split need to happen so yes - just lets not mix up the version naming.

/max


> If we find other dependent features that are pre-release we can 
> continue with the split TP
> theme.
>
> Agreed?
>
> Thanks for the feedback,
>          --paull
>
> ----- Original Message -----
>> From: "Max Rydahl Andersen" <manderse at redhat.com>
>> To: "Paul Leacu" <pleacu at redhat.com>
>> Cc: jbds-is-pm-list at redhat.com, "soa-tools-list" 
>> <soa-tools-list at redhat.com>, "jbosstools-dev jbosstools-dev"
>> <jbosstools-dev at lists.jboss.org>
>> Sent: Wednesday, January 28, 2015 11:21:28 AM
>> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target 
>> platform - 4.2.1.Final/ 4.2.1.EA
>>
>> On 28 Jan 2015, at 17:04, Paul Leacu wrote:
>>
>>> Hey Max -
>>>  The BPMN2 Modeler and BPEL appear in both the JBTIS TP and as p2
>>> update site components.
>>
>> okey - but both BPMN2 and BPEL is part of community release too so 
>> i'm
>> confused why called product only ;)
>>
>>> Your statement below is really the principle issue:
>>
>>>
>>>> I believe this change is done to ensure we don't leak in bad
>>>> dependencies between
>>>> the earlyaccess site that exists in both community and product
>>>> shipment.
>>>
>>> --paull
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Max Rydahl Andersen" <manderse at redhat.com>
>>>> To: "Paul Leacu" <pleacu at redhat.com>
>>>> Cc: "Rob Cernich" <rcernich at redhat.com>, "soa-tools-list"
>>>> <soa-tools-list at redhat.com>, jbds-is-pm-list at redhat.com,
>>>> "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
>>>> Sent: Wednesday, January 28, 2015 10:25:18 AM
>>>> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
>>>> platform - 4.2.1.Final/ 4.2.1.EA
>>>>
>>>> i'm a bit confused what is it you consider product bits in the TP
>>>> here ?
>>>>
>>>> I'm not seeing any in here - am I missing something ?
>>>>
>>>> I believe this change is done to ensure we don't leak in bad
>>>> dependencies between
>>>> the earlyaccess site that exists in both community and product
>>>> shipment.
>>>>
>>>> /max
>>>>> Hey Rob,
>>>>>
>>>>> I'd love to remove product bits from the TP but that hasn't
>>>>> happened.
>>>>> Having
>>>>> a release based JBTIS TP that is guaranteed to have only .Final
>>>>> components and
>>>>> then having an early-access TP seems to give component developers
>>>>> the
>>>>> option of
>>>>> adding non fully released dependencies that are not our own 
>>>>> product
>>>>> bits while
>>>>> their component is still in Beta.
>>>>>
>>>>> The TPs are identical (JBTIS TP/ JBDSIS TP) - component developers
>>>>> could use either
>>>>> with 4.2.1.EA being the full set of dependencies.
>>>>>
>>>>> We can revisit removing the JBoss product bits from the TP but for
>>>>> the
>>>>> JDV release
>>>>> this change removes uncategorized non .Final bits that's needed 
>>>>> now.
>>>>>
>>>>> --paull
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: "Rob Cernich" <rcernich at redhat.com>
>>>>>> To: "Paul Leacu" <pleacu at redhat.com>
>>>>>> Cc: jbds-is-pm-list at redhat.com, "soa-tools-list"
>>>>>> <soa-tools-list at redhat.com>, "jbosstools-dev jbosstools-dev"
>>>>>> <jbosstools-dev at lists.jboss.org>
>>>>>> Sent: Wednesday, January 28, 2015 9:32:26 AM
>>>>>> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
>>>>>> platform -	4.2.1.Final/ 4.2.1.EA
>>>>>>
>>>>>> I think the better solution is to remove product bits from the TP
>>>>>> and
>>>>>> have
>>>>>> them included directly through the site/p2 repo.  Splitting up 
>>>>>> the
>>>>>> TP
>>>>>> is
>>>>>> likely to cause issues down, especially as versions change.  
>>>>>> Also,
>>>>>> I
>>>>>> assume
>>>>>> this is for product bits and not community bits (i.e. JBDS-IS vs
>>>>>> JBTIS).
>>>>>>
>>>>>> ----- Original Message -----
>>>>>>>
>>>>>>> Greetings -
>>>>>>> A proposal to change the JBTIS target platform is described 
>>>>>>> here:
>>>>>>>
>>>>>>> https://issues.jboss.org/browse/JBTIS-382
>>>>>>>
>>>>>>> PR:
>>>>>>> https://github.com/jbosstools/jbosstools-integration-stack/pull/280
>>>>>>>
>>>>>>> Synopsis:
>>>>>>>
>>>>>>> 1. Split the JBTIS target platform along release/final and
>>>>>>> non-release/early access lines
>>>>>>> so as to not expose non .Final features to the stable capture
>>>>>>> that
>>>>>>> appears when performing
>>>>>>> an 'uncategorized' install.  No dependent component version
>>>>>>> change
>>>>>>> from
>>>>>>> 4.2.0.Final.
>>>>>>>
>>>>>>>
>>>>>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Final/
>>>>>>>
>>>>>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
>>>>>>>
>>>>>>> Please respond by COB on Thursday, Jan 29 to the specified Jira 
>>>>>>> if
>>>>>>> there
>>>>>>> are any issues.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> --paull
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Soa-tools-list mailing list
>>>>>>> Soa-tools-list at redhat.com
>>>>>>> https://www.redhat.com/mailman/listinfo/soa-tools-list
>>>>>>>
>>>>>>
>>>>
>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>>>
>>
>>
>> /max
>> http://about.me/maxandersen
>>
>
> _______________________________________________
> Soa-tools-list mailing list
> Soa-tools-list at redhat.com
> https://www.redhat.com/mailman/listinfo/soa-tools-list


/max
http://about.me/maxandersen


From man2 at trye.oowwwoo.com  Tue Feb  3 01:27:43 2015
From: man2 at trye.oowwwoo.com (PCB Prototype Fabrication/Printed circuit board Supply)
Date: Tue, 03 Feb 2015 06:27:43 +0000
Subject: [jbosstools-dev] =?gb2312?b?UENCIFByb3RvdHlwZSBGYWJyaWNhdGlvbi9Q?=
	=?gb2312?b?cmludGVkIGNpcmN1aXQgYm9hcmQgU3VwcGx50+vE+rmyz+3By8/g?=
	=?gb2312?b?suGhow==?=
Message-ID: <047d7bf0f1d01a4719050e292bc9@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=111348779778926651355&target=ALBUM&id=6056626129466840369&authkey=Gv1sRgCPy2u7KSv_LicQ&invite=CODq3qkH&feat=email
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150203/ecfb4813/attachment-0001.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/20150203/ecfb4813/attachment-0001.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/20150203/ecfb4813/attachment-0001.jpg 

From mgagyi at redhat.com  Tue Feb  3 07:16:29 2015
From: mgagyi at redhat.com (Matej Gagyi)
Date: Tue, 3 Feb 2015 07:16:29 -0500 (EST)
Subject: [jbosstools-dev] Proposed change to JBT 4.50.x target platform:
In-Reply-To: <1147152179.913042.1422540839712.JavaMail.zimbra@redhat.com>
References: <1147152179.913042.1422540839712.JavaMail.zimbra@redhat.com>
Message-ID: <103260907.3887378.1422965789259.JavaMail.zimbra@redhat.com>

Here is a proposal for a change to the JBoss Tools 4.50.0 target platform:

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

It consists in the following changes:

* JBIDE-19110: Add Mockito to Target platform 4.50.0

p2diff reports are attached to the related JIRA(s).

Please review the above PR(s), as it will be applied ASAP.
You can use the following to build & test the target-platform locally against your component(s).

Build target-platform:
  $ cd jbosstools-target-platforms
  $ git fetch origin 4.50.x
  $ git checkout FETCH_HEAD
  $ cd jbosstools/multiple
  $ mvn clean install

Try with just built target-platform:
  $ cd /path/to/your/component
  $ mvn clean verify -Dtpc.version=4.50.x -Pmultiple.target
--

If you want to perform a scripted install of the entire target platform
into your local Eclipse or JBDS instance, you can now do so with this
script:

https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh

Usage is documented in the above script, and in this README:

https://github.com/jbosstools/jbosstools-target-platforms/tree/master#updating-versions-of-ius-in-target-files
-------------- next part --------------
A non-text attachment was scrubbed...
Name: p2diff.locus.mockito
Type: application/octet-stream
Size: 240 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150203/c7477cd5/attachment.obj 

From mistria at redhat.com  Thu Feb  5 01:42:20 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 05 Feb 2015 07:42:20 +0100
Subject: [jbosstools-dev] Tycho 0.22 for JBoss Tools 4.2.3 and JBoss
	Developer Studio 8.1.0
Message-ID: <54D310CC.3050801@redhat.com>

Hi all,

We plan to move the current jbosstools-4.2.x branch to Tycho 0.22 in 
order to leverage a couple of interesting mojos that are not compatible 
with Tycho 0.21. If you have any question or concern about that change, 
please comment on https://issues.jboss.org/browse/JBIDE-19169 .

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

From manderse at redhat.com  Thu Feb  5 05:26:11 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 05 Feb 2015 11:26:11 +0100
Subject: [jbosstools-dev] Upcoming releases of JBoss Tools (and Developer
	Studio)
Message-ID: <7BA89F3E-4E56-4F29-B6D0-F5FBDCE758F1@redhat.com>

Hi,

Just a friendly reminder that over the next four weeks we will start the 
releases for both maintenance (4.2.3.Beta1) and master (4.3.0.Alpha1).

This is more agressive push of release than we have done before - thus 
please take note of the dates and be ready. There are *no* planned nor 
intent of doing
respins of these.

week 1: 2015-02-11: Code freeze master (4.3.0.Alpha1)
week 2: 2015-02-19: Release master (4.3.0.Alpha1)
week 3: 2015-02-26: Code freeze maintenance (4.2.3.Beta1)
week 4: 2015-02-26: Release maintenance (4.2.3.Beta1)

Master will be targeting Eclipse Mars M5 and main gist here is to get a 
working build against Mars and verify basics continues to work :)
Branch is for getting a beta1 out to test the bugfixes and feedhenry 
improvements coming there.

Calendar/overviews are available here:
https://issues.jboss.org/browse/JBIDE/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel 
- note the codefreeze dates are in the description.
https://issues.jboss.org/browse/JBDS/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel


/max
http://about.me/maxandersen


From rstryker at redhat.com  Fri Feb  6 07:30:10 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Fri, 06 Feb 2015 20:30:10 +0800
Subject: [jbosstools-dev] Anonymous Downloads for Alpha release, JBT,
	and Stacks
Message-ID: <54D4B3D2.6030602@redhat.com>

Hey all:

I've made a comment over on https://issues.jboss.org/browse/JBIDE-18709  
investigating the issue of anonymous downloads as it pertains to alpha 
releases, stacks, and JBT as a group.

It'd be good if those addressed directly above (david, rafael) had a 
look just so that everyone's aware of the issues of adding any Alpha 
release to JBoss Stacks.

The tl;dr of it is:  if we do add alpha releases to stacks, we must 
still use the jdf URL, and we must still set requiresCredentials=true, 
even though it's not accurate. Otherwise we risk breaking older releases 
of JBT.

Any questions or comments are welcome and encouraged on the jira issue 
directly.

Thanks in advance.

- Rob Stryker

From dhladky at redhat.com  Fri Feb  6 07:40:23 2015
From: dhladky at redhat.com (David Hladky)
Date: Fri, 6 Feb 2015 07:40:23 -0500 (EST)
Subject: [jbosstools-dev] Anonymous Downloads for Alpha release, JBT,
	and Stacks
In-Reply-To: <54D4B3D2.6030602@redhat.com>
References: <54D4B3D2.6030602@redhat.com>
Message-ID: <1422204121.7609475.1423226423453.JavaMail.zimbra@redhat.com>

Hi Rob, 

using the /jdf links is the right way to do on your side. However I do not understand the requiresCredentials issue is. Is it a problem on your side or does the service return you something unexcpected? If so, have you checked you saved the changes?

David

----- Original Message -----
From: "Rob Stryker" <rstryker at redhat.com>
To: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "Rafael Benevides" <benevides at redhat.com>, "David Hladky" <dhladky at redhat.com>
Sent: Friday, 6 February, 2015 1:30:10 PM
Subject: Anonymous Downloads for Alpha release, JBT, and Stacks

Hey all:

I've made a comment over on https://issues.jboss.org/browse/JBIDE-18709  
investigating the issue of anonymous downloads as it pertains to alpha 
releases, stacks, and JBT as a group.

It'd be good if those addressed directly above (david, rafael) had a 
look just so that everyone's aware of the issues of adding any Alpha 
release to JBoss Stacks.

The tl;dr of it is:  if we do add alpha releases to stacks, we must 
still use the jdf URL, and we must still set requiresCredentials=true, 
even though it's not accurate. Otherwise we risk breaking older releases 
of JBT.

Any questions or comments are welcome and encouraged on the jira issue 
directly.

Thanks in advance.

- Rob Stryker

From rstryker at redhat.com  Fri Feb  6 08:04:43 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Fri, 06 Feb 2015 21:04:43 +0800
Subject: [jbosstools-dev] Anonymous Downloads for Alpha release, JBT,
	and Stacks
In-Reply-To: <1422204121.7609475.1423226423453.JavaMail.zimbra@redhat.com>
References: <54D4B3D2.6030602@redhat.com>
	<1422204121.7609475.1423226423453.JavaMail.zimbra@redhat.com>
Message-ID: <54D4BBEB.5030006@redhat.com>

On 02/06/2015 08:40 PM, David Hladky wrote:
> Hi Rob,
>
> using the /jdf links is the right way to do on your side. However I do not understand the requiresCredentials issue is. Is it a problem on your side or does the service return you something unexcpected? If so, have you checked you saved the changes?
>
> David

Stacks.yaml has various labels we can add to their list of runtimes. One 
of the labels we added was 'requiresCredentials".  Past (and current) 
versions of jbosstools interpret this flag to mean 'go through the jboss 
download-manager workflow', where we set the custom request headers. 
Otherwise, if requiresCredentials is set to false, we basically do a 
generic wget / curl request with no xml headers at all. We treat it the 
same way as we would a zip file on sourceforge or any web server.

So if we set that to false, we would do a generic request to the jdf url 
with no request headers at all, and this in turn downloads what is an 
html page.

Does that make sense?

>
> ----- Original Message -----
> From: "Rob Stryker" <rstryker at redhat.com>
> To: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "Rafael Benevides" <benevides at redhat.com>, "David Hladky" <dhladky at redhat.com>
> Sent: Friday, 6 February, 2015 1:30:10 PM
> Subject: Anonymous Downloads for Alpha release, JBT, and Stacks
>
> Hey all:
>
> I've made a comment over on https://issues.jboss.org/browse/JBIDE-18709
> investigating the issue of anonymous downloads as it pertains to alpha
> releases, stacks, and JBT as a group.
>
> It'd be good if those addressed directly above (david, rafael) had a
> look just so that everyone's aware of the issues of adding any Alpha
> release to JBoss Stacks.
>
> The tl;dr of it is:  if we do add alpha releases to stacks, we must
> still use the jdf URL, and we must still set requiresCredentials=true,
> even though it's not accurate. Otherwise we risk breaking older releases
> of JBT.
>
> Any questions or comments are welcome and encouraged on the jira issue
> directly.
>
> Thanks in advance.
>
> - Rob Stryker


From rstryker at redhat.com  Fri Feb  6 10:21:24 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Fri, 06 Feb 2015 23:21:24 +0800
Subject: [jbosstools-dev] Anonymous Downloads for Alpha release, JBT,
	and Stacks
In-Reply-To: <1422204121.7609475.1423226423453.JavaMail.zimbra@redhat.com>
References: <54D4B3D2.6030602@redhat.com>
	<1422204121.7609475.1423226423453.JavaMail.zimbra@redhat.com>
Message-ID: <54D4DBF4.5030108@redhat.com>

OK David:

So after discussion with Max, having the stacks.yaml say 
requiresCredentials=true when it doesn't, just to work around the 
existing workflow,  is wrong and we shouldn't do that.

Is there any chance we can get the JDF url on download manager to do the 
following?

1) Check if the requested file is set to Anonymous Download
2) If yes,
     a) Check if it looks like we're coming from a browser (either by 
checking user agent or response flags)
     b) if yes, do the website stuff, else
     c) just return the file as if it was a normal wget

Basically, what we're requesting is that a wget 
http://www.jboss.org/download-manager/jdf/file/jboss-eap-6.4.0.Alpha.zip 
just downloads the file if it looks like we're not a browser.

- Rob Stryker

On 02/06/2015 08:40 PM, David Hladky wrote:
> Hi Rob,
>
> using the /jdf links is the right way to do on your side. However I do not understand the requiresCredentials issue is. Is it a problem on your side or does the service return you something unexcpected? If so, have you checked you saved the changes?
>
> David
>
> ----- Original Message -----
> From: "Rob Stryker" <rstryker at redhat.com>
> To: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "Rafael Benevides" <benevides at redhat.com>, "David Hladky" <dhladky at redhat.com>
> Sent: Friday, 6 February, 2015 1:30:10 PM
> Subject: Anonymous Downloads for Alpha release, JBT, and Stacks
>
> Hey all:
>
> I've made a comment over on https://issues.jboss.org/browse/JBIDE-18709
> investigating the issue of anonymous downloads as it pertains to alpha
> releases, stacks, and JBT as a group.
>
> It'd be good if those addressed directly above (david, rafael) had a
> look just so that everyone's aware of the issues of adding any Alpha
> release to JBoss Stacks.
>
> The tl;dr of it is:  if we do add alpha releases to stacks, we must
> still use the jdf URL, and we must still set requiresCredentials=true,
> even though it's not accurate. Otherwise we risk breaking older releases
> of JBT.
>
> Any questions or comments are welcome and encouraged on the jira issue
> directly.
>
> Thanks in advance.
>
> - Rob Stryker


From nboldt at redhat.com  Fri Feb  6 12:35:32 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 06 Feb 2015 12:35:32 -0500
Subject: [jbosstools-dev] Tycho 0.22 for JBoss Tools 4.2.3 and JBoss
 Developer Studio 8.1.0
In-Reply-To: <54D310CC.3050801@redhat.com>
References: <54D310CC.3050801@redhat.com>
Message-ID: <54D4FB64.6000209@redhat.com>

As no one has raised an objection, I've moved ahead with migrating the 
parent pom, JBT aggregate pom, and JBDS build to use Tycho 0.22.

Note that this will also mean that your build MUST use JDK 7 or 8* 
instead of 6, so I'll go update all the Jenkins jobs next.

Cheers,

Nick


* - required by repo-utils 0.22.1-SNAPSHOT



On 02/05/2015 01:42 AM, Mickael Istria wrote:
> Hi all,
>
> We plan to move the current jbosstools-4.2.x branch to Tycho 0.22 in
> order to leverage a couple of interesting mojos that are not compatible
> with Tycho 0.21. If you have any question or concern about that change,
> please comment on https://issues.jboss.org/browse/JBIDE-19169 .
>
> Cheers,
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets
> <http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

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

From manderse at redhat.com  Sun Feb  8 03:02:25 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Sun, 8 Feb 2015 03:02:25 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201502080802.t1882PE1028583@int-mx13.intmail.prod.int.phx2.redhat.com>


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

 
* No component for JBDS-3340

https://issues.jboss.org/browse/JBDS-3340
Summary: html visual editor living view

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

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



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

From mistria at redhat.com  Mon Feb  9 04:04:43 2015
From: mistria at redhat.com (Mickael Istria)
Date: Mon, 09 Feb 2015 10:04:43 +0100
Subject: [jbosstools-dev] Suggested change for 4.50.0.Alpha1-SNAPSHOT
 target-platfrom: Mars M5
Message-ID: <54D8782B.2030707@redhat.com>

Here is a proposal for a change to the JBoss Tools4.50.0.Alpha1-SNAPSHOT  target platform, for JBoss Tools 4.3.0.Alpha1:

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

It consists in the following changes:
* JBIDE-19174: Mars M5


p2diff reports are attached to the related JIRA(s).

Please review the above PR(s), as it will be applied ASAP.
You can use the following to build & test the target-platform locally against your component(s).

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

Try with just built target-platform:
   $ cd /path/to/your/component
   $ mvn clean verify -Dtpc.version=4.50.0.Alpha1-SNAPSHOT  -Pmultiple.target


From manderse at redhat.com  Mon Feb  9 04:45:00 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 09 Feb 2015 10:45:00 +0100
Subject: [jbosstools-dev] Anonymous Downloads for Alpha release, JBT,
 and Stacks
In-Reply-To: <54D4DBF4.5030108@redhat.com>
References: <54D4B3D2.6030602@redhat.com>
	<1422204121.7609475.1423226423453.JavaMail.zimbra@redhat.com>
	<54D4DBF4.5030108@redhat.com>
Message-ID: <284EDC21-1845-4642-B4C8-837A1366F735@redhat.com>

On 6 Feb 2015, at 16:21, Rob Stryker wrote:

> OK David:
>
> So after discussion with Max, having the stacks.yaml say
> requiresCredentials=true when it doesn't, just to work around the
> existing workflow,  is wrong and we shouldn't do that.

To be clear - since the intent of the Alpha releases are to be available 
to everyone with or without jboss.org username requiring credentials 
would be wrong.

Of course if we can't actually get the server side to behave like it is 
really anonymous then
we could be forced to do this.

> Is there any chance we can get the JDF url on download manager to do 
> the
> following?
>
> 1) Check if the requested file is set to Anonymous Download
> 2) If yes,
>   a) Check if it looks like we're coming from a browser (either by
> checking user agent or response flags)
>   b) if yes, do the website stuff, else
>   c) just return the file as if it was a normal wget
>
> Basically, what we're requesting is that a wget
> http://www.jboss.org/download-manager/jdf/file/jboss-eap-6.4.0.Alpha.zip
> just downloads the file if it looks like we're not a browser.

+1, if the content is anonymously available might just as well hand it 
out directly without
showing the html page when the one requesting it is not a browser.

/max

> - Rob Stryker
>
> On 02/06/2015 08:40 PM, David Hladky wrote:
>> Hi Rob,
>>
>> using the /jdf links is the right way to do on your side. However I 
>> do not understand the requiresCredentials issue is. Is it a problem 
>> on your side or does the service return you something unexcpected? If 
>> so, have you checked you saved the changes?
>>
>> David
>>
>> ----- Original Message -----
>> From: "Rob Stryker" <rstryker at redhat.com>
>> To: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>, 
>> "Rafael Benevides" <benevides at redhat.com>, "David Hladky" 
>> <dhladky at redhat.com>
>> Sent: Friday, 6 February, 2015 1:30:10 PM
>> Subject: Anonymous Downloads for Alpha release, JBT, and Stacks
>>
>> Hey all:
>>
>> I've made a comment over on 
>> https://issues.jboss.org/browse/JBIDE-18709
>> investigating the issue of anonymous downloads as it pertains to 
>> alpha
>> releases, stacks, and JBT as a group.
>>
>> It'd be good if those addressed directly above (david, rafael) had a
>> look just so that everyone's aware of the issues of adding any Alpha
>> release to JBoss Stacks.
>>
>> The tl;dr of it is:  if we do add alpha releases to stacks, we must
>> still use the jdf URL, and we must still set 
>> requiresCredentials=true,
>> even though it's not accurate. Otherwise we risk breaking older 
>> releases
>> of JBT.
>>
>> Any questions or comments are welcome and encouraged on the jira 
>> issue
>> directly.
>>
>> Thanks in advance.
>>
>> - Rob Stryker
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From manderse at redhat.com  Mon Feb  9 04:52:12 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 09 Feb 2015 10:52:12 +0100
Subject: [jbosstools-dev] Suggested change for 4.50.0.Alpha1-SNAPSHOT
 target-platfrom: Mars M5
In-Reply-To: <54D8782B.2030707@redhat.com>
References: <54D8782B.2030707@redhat.com>
Message-ID: <B9CADA2E-4F45-4428-BD34-66C682144395@redhat.com>

while reviewing this I noticed we still have the mention that Tern is 
still listed in the TP
because needed by angularjs.

https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbosstools/multiple/jbosstools-multiple.target#L424

a) why is that still required since earlyaccess users will be definition 
have the updatesite available to them
b) weren't tern supposed to be delivered via jsdt now ?

/max


> Here is a proposal for a change to the JBoss 
> Tools4.50.0.Alpha1-SNAPSHOT  target platform, for JBoss Tools 
> 4.3.0.Alpha1:
>
> https://github.com/jbosstools/jbosstools-target-platforms/pull/125
>
> It consists in the following changes:
> * JBIDE-19174: Mars M5
>
>
> p2diff reports are attached to the related JIRA(s).
>
> Please review the above PR(s), as it will be applied ASAP.
> You can use the following to build & test the target-platform locally 
> against your component(s).
>
> Build target-platform:
> $ cd jbosstools-target-platforms
> $ git fetch origin pull/125/head
> $ git checkout FETCH_HEAD
> $ cd jbosstools/multiple
> $ mvn clean install
>
> Try with just built target-platform:
> $ cd /path/to/your/component
> $ mvn clean verify -Dtpc.version=4.50.0.Alpha1-SNAPSHOT  
> -Pmultiple.target
>
> _______________________________________________
> 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  Mon Feb  9 11:22:13 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 09 Feb 2015 11:22:13 -0500
Subject: [jbosstools-dev] Suggested change for 4.50.0.Alpha1-SNAPSHOT
 target-platfrom: Mars M5
In-Reply-To: <B9CADA2E-4F45-4428-BD34-66C682144395@redhat.com>
References: <54D8782B.2030707@redhat.com>
	<B9CADA2E-4F45-4428-BD34-66C682144395@redhat.com>
Message-ID: <54D8DEB5.9010609@redhat.com>

Correct, 
https://github.com/jbosstools/jbosstools-target-platforms/pull/125 can 
be revised to remove Tern as it's now included in JST's update site. 
 From there it's aggregated into JBT and JBDS update sites.

+1 to push this PR, and we can remove Tern after that. Or revise the PR 
and push it w/ Tern removed in the same commit. Either way is fine w/ me.

On 02/09/2015 04:52 AM, Max Rydahl Andersen wrote:
> while reviewing this I noticed we still have the mention that Tern is
> still listed in the TP
> because needed by angularjs.
>
> https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbosstools/multiple/jbosstools-multiple.target#L424
>
> a) why is that still required since earlyaccess users will be definition
> have the updatesite available to them
> b) weren't tern supposed to be delivered via jsdt now ?
>
> /max
>
>
>> Here is a proposal for a change to the JBoss
>> Tools4.50.0.Alpha1-SNAPSHOT  target platform, for JBoss Tools
>> 4.3.0.Alpha1:
>>
>> https://github.com/jbosstools/jbosstools-target-platforms/pull/125
>>
>> It consists in the following changes:
>> * JBIDE-19174: Mars M5
>>
>>
>> p2diff reports are attached to the related JIRA(s).
>>
>> Please review the above PR(s), as it will be applied ASAP.
>> You can use the following to build & test the target-platform locally
>> against your component(s).
>>
>> Build target-platform:
>> $ cd jbosstools-target-platforms
>> $ git fetch origin pull/125/head
>> $ git checkout FETCH_HEAD
>> $ cd jbosstools/multiple
>> $ mvn clean install
>>
>> Try with just built target-platform:
>> $ cd /path/to/your/component
>> $ mvn clean verify -Dtpc.version=4.50.0.Alpha1-SNAPSHOT
>> -Pmultiple.target
>>
>> _______________________________________________
>> 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  Tue Feb 10 05:05:23 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 10 Feb 2015 11:05:23 +0100
Subject: [jbosstools-dev] jira websocket label vs component
Message-ID: <BA4F31B0-9D33-44F6-B4E8-62963390FADF@redhat.com>

Hi,

In https://issues.jboss.org/browse/JBDS-3261 a new 'websocket's 
component was created to categorize for now two jiras.

We do not plan or have intent on making a specific 'websockets' feature 
(yet) and if we did it would probably end up in the webservices 
component + more components = more manual updating of scripts relying on 
component names :)

Thus I talked with Xavier and agreed on just continue using labels to 
mark what kind of webservices a jira refer to.

Thus I deleted the 'websockets' component and added 'websockets' label 
instead.

https://issues.jboss.org/browse/JBDS-3322?jql=labels%20%3D%20websockets%20and%20project%20in%20%28JBIDE%2C%20JBDS%29

If we actually start doing/planning websocket feature work we can 
revisit this.

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


From nboldt at redhat.com  Tue Feb 10 09:30:28 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 10 Feb 2015 09:30:28 -0500
Subject: [jbosstools-dev] Suggested change for 4.50.0.Alpha1-SNAPSHOT
 target-platfrom: Mars M5
In-Reply-To: <B9CADA2E-4F45-4428-BD34-66C682144395@redhat.com>
References: <54D8782B.2030707@redhat.com>
	<B9CADA2E-4F45-4428-BD34-66C682144395@redhat.com>
Message-ID: <54DA1604.7070908@redhat.com>

Tern has since been removed [1], but we need to add minimal-json back in 
[2].

[1] https://issues.jboss.org/browse/JBIDE-19045
[2] https://issues.jboss.org/browse/JBIDE-19194

Finalised Alpha TP should be out today or tomorrow.

As a reminder, code freeze for 9.0.0.Alpha1 is tomorrow!

Everyone ready?

On 02/09/2015 04:52 AM, Max Rydahl Andersen wrote:
> while reviewing this I noticed we still have the mention that Tern is
> still listed in the TP
> because needed by angularjs.
>
> https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbosstools/multiple/jbosstools-multiple.target#L424
>
> a) why is that still required since earlyaccess users will be definition
> have the updatesite available to them
> b) weren't tern supposed to be delivered via jsdt now ?
>
> /max
>
>
>> Here is a proposal for a change to the JBoss
>> Tools4.50.0.Alpha1-SNAPSHOT  target platform, for JBoss Tools
>> 4.3.0.Alpha1:
>>
>> https://github.com/jbosstools/jbosstools-target-platforms/pull/125
>>
>> It consists in the following changes:
>> * JBIDE-19174: Mars M5
>>
>>
>> p2diff reports are attached to the related JIRA(s).
>>
>> Please review the above PR(s), as it will be applied ASAP.
>> You can use the following to build & test the target-platform locally
>> against your component(s).
>>
>> Build target-platform:
>> $ cd jbosstools-target-platforms
>> $ git fetch origin pull/125/head
>> $ git checkout FETCH_HEAD
>> $ cd jbosstools/multiple
>> $ mvn clean install
>>
>> Try with just built target-platform:
>> $ cd /path/to/your/component
>> $ mvn clean verify -Dtpc.version=4.50.0.Alpha1-SNAPSHOT
>> -Pmultiple.target
>>
>> _______________________________________________
>> 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 pleacu at redhat.com  Tue Feb 10 10:29:15 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Tue, 10 Feb 2015 10:29:15 -0500 (EST)
Subject: [jbosstools-dev] Proposed change for JBTIS target platform -
	4.2.1.CR2
In-Reply-To: <978886194.8431400.1423511723529.JavaMail.zimbra@redhat.com>
Message-ID: <1877427629.8935118.1423582155772.JavaMail.zimbra@redhat.com>


   Greetings -
      Recently, the JBTIS target platform was modified to split along release/final and 
   non-release/early access lines so as to not expose non .Final features to the stable
   capture that appears when performing an 'uncategorized' install.  That TP repo is in
   testing now (along with the IS releases) and can be found here:

   http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.CR1/
   http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.CR1/earlyaccess

   The production target platform .target file classifiers are base and base-ea.  The
   community target platform .target file classifiers are full and full-ea.

   Synopsis:

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

   The released TP repositories for JBDSIS were simply a copy of the JBTIS target repos.
   This however exposes a small number of community features into the JBDSIS stream.  To
   address this issue, the IS target-platform project will now build separate JBTIS TP 
   repositories and JBDSIS TP repos (instead of copying).

   http://download.jboss.org/jbosstools/builds/staging/JBTIS-target-platform/4.2.1.CR2-SNAPSHOT/   # .target files
   http://download.jboss.org/jbosstools/builds/staging/JBTIS-target-platform/4.2.1.CR2-SNAPSHOT/jbtis
   http://download.jboss.org/jbosstools/builds/staging/JBTIS-target-platform/4.2.1.CR2-SNAPSHOT/jbtis/earlyaccess
   http://download.jboss.org/jbosstools/builds/staging/JBTIS-target-platform/4.2.1.CR2-SNAPSHOT/jbdsis
   http://download.jboss.org/jbosstools/builds/staging/JBTIS-target-platform/4.2.1.CR2-SNAPSHOT/jbdsis/earlyaccess

   PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/283

   Please respond by COB on Wednesday, Feb 11 to the specified Jira if there are any issues.

   Thanks,
         --paull

From manderse at redhat.com  Tue Feb 10 11:35:34 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 10 Feb 2015 17:35:34 +0100
Subject: [jbosstools-dev] mockito now in in TP for jbosstools master
Message-ID: <8E65478C-A376-4107-A7A0-018C2C719778@redhat.com>

Hi,

It probably should have happened ages ago [1] but now its there via 
https://issues.jboss.org/browse/JBIDE-19110

Mockito is now available in master of jboss tools core target platform.

Meaning you can now use mocks in your tests without custom 
inclusion/setup.
We do have other mocking frameworks in play, but please consider using 
mockito
instead of something custom going forward.

Mind you that we are using a fork of Mockito to work around limit of 
what happens when
you have multiple versions of a binary loaded in the IDE - but if you 
don't have that
you shouldn't care ;)

You can read more about mockito at http://mockito.org/ or google 
"eclipse mockito" to have fun with
the subtleties osgi gives you ;)

[1] I'll explain why mockito with osgi sucks over a beer :)

/max
http://about.me/maxandersen

From manderse at redhat.com  Tue Feb 10 11:43:07 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 10 Feb 2015 17:43:07 +0100
Subject: [jbosstools-dev] Oomph in Eclipse M5 and properties...
Message-ID: <87A304B4-6812-4D9E-BDC5-DE1177A54FD4@redhat.com>

Hey,

If you haven't tried Eclipse Mars M5 yet you probably haven't heard or 
tried oomph yet.

oomph does a bunch of things regarding making eclipse easier to install 
and configure.

One of them is managing preferences between multiple workspaces - i'm 
not super fan of the UI oomph have so far, but the idea behind it is 
good enough. It listens to preference changes and ask the user if a 
certain preference should be applied to all your other workspaces. If 
yes - it will apply them on your next workspace start.

That is all fine and well, but some of the properties just don't make 
sense for users to be notified about - for example our usage tracking is 
stored in preferences; not something that makes sense for oomph to care 
about.

That is now fixed in M6 
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=459455) after I raised 
the issue.

But do please keep an eye on oomph and check if it asks for properties 
you think are irrelevant or bad that we should get fixed on oomph side.

And of course - if you see other issues with oomph do open bugs on 
bugs.eclipse.org so Eclipse Mars will get something better not worse ;)

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

From mistria at redhat.com  Wed Feb 11 03:52:27 2015
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 11 Feb 2015 09:52:27 +0100
Subject: [jbosstools-dev] Oomph in Eclipse M5 and properties...
In-Reply-To: <87A304B4-6812-4D9E-BDC5-DE1177A54FD4@redhat.com>
References: <87A304B4-6812-4D9E-BDC5-DE1177A54FD4@redhat.com>
Message-ID: <54DB184B.1070300@redhat.com>

Another effect of Oomph: https://issues.jboss.org/browse/JBIDE-19219

-- 
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/20150211/88386e0b/attachment.html 

From nboldt at redhat.com  Wed Feb 11 09:57:34 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 11 Feb 2015 09:57:34 -0500
Subject: [jbosstools-dev] New Target Platforms 4.50.0.Alpha1 are available
 for JBoss Tools 4.3.0.Alpha1 / JBDS 9.0.0.Alpha1 code freeze
Message-ID: <54DB6DDE.1030009@redhat.com>

The latest target platforms for JBoss Tools 4.3.0.Alpha1 / JBDS 
9.0.0.Alpha1 have been released:

http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Alpha1/
http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.50.0.Alpha1/

Note that the Central and Early Access target platforms are still at 
their -SNAPSHOT versions, because they can't be released until after we 
finish with the Alpha1 builds.

http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.50.0.Alpha1-SNAPSHOT/

http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.50.0.Alpha1-SNAPSHOT/

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

From manderse at redhat.com  Thu Feb 12 06:14:04 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 12 Feb 2015 12:14:04 +0100
Subject: [jbosstools-dev] New OpenShift v3 feature
Message-ID: <8811776D-8B16-483C-8F8F-A1035ACB4444@redhat.com>

Hi,

As documented 
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_to_add_a_plugin_or_feature_to_an_existing_project.md

I'm posting on behalf of Andre that we are need to add new openshift v3 
feature to JBoss Tools and eventually devstudio.

This new feature (called: org.jboss.tools.openshift.feature) is what 
will provide OpenShift v3 features.

The old v2 feature called  org.jboss.tools.openshift.express.feature 
will continue to exist and be relevant to support v2.

One tricky matter is that openshift v3 is still actively moving thus for 
now we are making the V3 and V2 install separately available features in 
case v3 will end up not being fully supported/completed when we go 
final.

Thus I suggest that for Alpha1:

Add org.jboss.tools.openshift.feature to JBoss Tools and its openshift 
central connector.

*after* Alpha1 after some feedback and stability add it to devstudio.

Central Jira for this is at 
https://jira.jboss.org/jira/browse/JBIDE-19162

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


From pleacu at redhat.com  Thu Feb 12 14:08:58 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Thu, 12 Feb 2015 14:08:58 -0500 (EST)
Subject: [jbosstools-dev] New JBTIS target platform available -
	JBTIS-TP-4.2.1.Final
In-Reply-To: <593196994.10549370.1423766855543.JavaMail.zimbra@redhat.com>
Message-ID: <1150053511.10622652.1423768138897.JavaMail.zimbra@redhat.com>


   Hey -
      An updated JBTIS TP is available - 4.2.1.Final:

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

   See Jira for details:
   https://issues.jboss.org/browse/JBTIS-388

   Note that the IS target platform is now split along release/early-access and community/production lines.
   This avoids exposing non .Final features to the stable capture that appears when performing an 'uncategorized'
   install and isolates community bits during the production build.

   If you are building currently for JDV you should use the 'base' classifier in your POM.  If you're building
   an early-access component (basically everything else) you should use the 'base-ea' classifier.  The 'full'
   and 'full-ea' classifiers are available for community builds that require specific community bits.

    --paull

From manderse at redhat.com  Thu Feb 12 15:06:23 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 12 Feb 2015 21:06:23 +0100
Subject: [jbosstools-dev] codefreeze and still 90+ issues open
Message-ID: <CC3359A2-2D82-4BBA-93D1-500D9C9E8FF4@redhat.com>

Hi,

codefreeze is up but filter=ds_next_master_unresolved still shows 90+ 
issues left.

I'm going through picking off the obvious ones but please do not forget 
to clear out jira for the alpha1 release.

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

From manderse at redhat.com  Thu Feb 12 15:07:22 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 12 Feb 2015 21:07:22 +0100
Subject: [jbosstools-dev] codefreeze and still 90+ issues open
In-Reply-To: <CC3359A2-2D82-4BBA-93D1-500D9C9E8FF4@redhat.com>
References: <CC3359A2-2D82-4BBA-93D1-500D9C9E8FF4@redhat.com>
Message-ID: <930F2BBB-2030-4AF8-97C9-1FB10700D39A@redhat.com>


forgot the link ;)

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

> Hi,
>
> codefreeze is up but filter=ds_next_master_unresolved still shows 90+ 
> issues left.
>
> I'm going through picking off the obvious ones but please do not 
> forget to clear out jira for the alpha1 release.
>
> Thanks!
> /max
> http://about.me/maxandersen


/max
http://about.me/maxandersen

From manderse at redhat.com  Thu Feb 12 15:20:24 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 12 Feb 2015 21:20:24 +0100
Subject: [jbosstools-dev] codefreeze and still 90+ issues open
In-Reply-To: <930F2BBB-2030-4AF8-97C9-1FB10700D39A@redhat.com>
References: <CC3359A2-2D82-4BBA-93D1-500D9C9E8FF4@redhat.com>
	<930F2BBB-2030-4AF8-97C9-1FB10700D39A@redhat.com>
Message-ID: <50497416-1BD2-46A4-A453-AEF63067DDBB@redhat.com>

and if you want just the stuff for your area:

https://issues.jboss.org/issues/?filter=ds_my_next_master_unresolved

/max

> forgot the link ;)
>
> https://issues.jboss.org/issues/?jql=filter%3Dds_next_master_unresolved
>
>> Hi,
>>
>> codefreeze is up but filter=ds_next_master_unresolved still shows 90+ 
>> issues left.
>>
>> I'm going through picking off the obvious ones but please do not 
>> forget to clear out jira for the alpha1 release.
>>
>> Thanks!
>> /max
>> http://about.me/maxandersen
>
>
> /max
> http://about.me/maxandersen


/max
http://about.me/maxandersen

From nboldt at redhat.com  Thu Feb 12 16:28:05 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 12 Feb 2015 16:28:05 -0500
Subject: [jbosstools-dev] codefreeze and still 90+ issues open
In-Reply-To: <50497416-1BD2-46A4-A453-AEF63067DDBB@redhat.com>
References: <CC3359A2-2D82-4BBA-93D1-500D9C9E8FF4@redhat.com>	<930F2BBB-2030-4AF8-97C9-1FB10700D39A@redhat.com>
	<50497416-1BD2-46A4-A453-AEF63067DDBB@redhat.com>
Message-ID: <54DD1AE5.80602@redhat.com>

I think you mean this:

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


On 02/12/2015 03:20 PM, Max Rydahl Andersen wrote:
> and if you want just the stuff for your area:
>
> https://issues.jboss.org/issues/?filter=ds_my_next_master_unresolved
>
> /max
>
>> forgot the link ;)
>>
>> https://issues.jboss.org/issues/?jql=filter%3Dds_next_master_unresolved
>>
>>> Hi,
>>>
>>> codefreeze is up but filter=ds_next_master_unresolved still shows 90+
>>> issues left.
>>>
>>> I'm going through picking off the obvious ones but please do not
>>> forget to clear out jira for the alpha1 release.
>>>
>>> Thanks!
>>> /max
>>> http://about.me/maxandersen
>>
>>
>> /max
>> http://about.me/maxandersen
>
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

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

From manderse at redhat.com  Thu Feb 12 17:51:01 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 12 Feb 2015 23:51:01 +0100
Subject: [jbosstools-dev] survey - on git push notifications in irc
Message-ID: <66E5CC71-1FC0-40C5-AA84-DA3E37F23C55@redhat.com>

Hey #jbosstools irc users,

Seeing how much activity #jbosstools is getting from jbossbot from git 
notifications I'm
considering routing them to a separate irc room.

Please take 5 min to give your input here: 
https://docs.google.com/forms/d/1469WFn73ecpR1XGDQwr4VbCApL5pkwIYVWAj02dJQAg/viewform

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


From manderse at redhat.com  Thu Feb 12 19:13:31 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 13 Feb 2015 01:13:31 +0100
Subject: [jbosstools-dev] 4.3.0.Alpha1.x now frozen and builds started but
	all red.
Message-ID: <D65684BE-C080-484C-832C-CA46493DFAF7@redhat.com>

Hi,

4.3.0.Alpha1 is now building but all builds except base are broken 
because they can't see the produced base site.

I'm seeing errors like:

[ERROR] Internal error: java.lang.RuntimeException: Failed to load p2 
repository with ID 'jbosstools-base' from location 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_9.0.mars/all/repo: 
No repository found at 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_9.0.mars/all/repo. 
-> [Help 1]

which looks very wrong why its looking at 9.0.mars instead of 4.3.mars

Nick/Michael - can you take a look at what is missing here ?

/max
http://about.me/maxandersen


From manderse at redhat.com  Thu Feb 12 19:21:01 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 13 Feb 2015 01:21:01 +0100
Subject: [jbosstools-dev] 4.3.0.Alpha1.x now frozen and builds started
 but all red.
In-Reply-To: <D65684BE-C080-484C-832C-CA46493DFAF7@redhat.com>
References: <D65684BE-C080-484C-832C-CA46493DFAF7@redhat.com>
Message-ID: <AA374300-A89A-40AB-A756-9C30A7AFE7D5@redhat.com>

Found the issue: https://issues.jboss.org/browse/JBIDE-19258

Nick/Michael - please fix this asap.

I'm not going to update all those jobs by hand at 1 AM :)

/max

> Hi,
>
> 4.3.0.Alpha1 is now building but all builds except base are broken
> because they can't see the produced base site.
>
> I'm seeing errors like:
>
> [ERROR] Internal error: java.lang.RuntimeException: Failed to load p2
> repository with ID 'jbosstools-base' from location
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_9.0.mars/all/repo:
> No repository found at
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_9.0.mars/all/repo.
> -> [Help 1]
>
> which looks very wrong why its looking at 9.0.mars instead of 4.3.mars
>
> Nick/Michael - can you take a look at what is missing here ?
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From nboldt at redhat.com  Thu Feb 12 23:57:00 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 12 Feb 2015 23:57:00 -0500
Subject: [jbosstools-dev] 4.3.0.Alpha1.x now frozen and builds started
 but all red.
In-Reply-To: <AA374300-A89A-40AB-A756-9C30A7AFE7D5@redhat.com>
References: <D65684BE-C080-484C-832C-CA46493DFAF7@redhat.com>
	<AA374300-A89A-40AB-A756-9C30A7AFE7D5@redhat.com>
Message-ID: <54DD841C.4030201@redhat.com>

Have you tried fetching the jobs' configs from the server, batch-fixing 
the files locally, and then pushing them back to the server?

There's a mojo for that.

Anyway, the issue is fixed (thanks to Denis) and builds are now becoming 
blue. Left status in the JIRA and I'm off to bed.


On 02/12/2015 07:21 PM, Max Rydahl Andersen wrote:
> Found the issue: https://issues.jboss.org/browse/JBIDE-19258
>
> Nick/Michael - please fix this asap.
>
> I'm not going to update all those jobs by hand at 1 AM :)
>
> /max
>
>> Hi,
>>
>> 4.3.0.Alpha1 is now building but all builds except base are broken
>> because they can't see the produced base site.
>>
>> I'm seeing errors like:
>>
>> [ERROR] Internal error: java.lang.RuntimeException: Failed to load p2
>> repository with ID 'jbosstools-base' from location
>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_9.0.mars/all/repo:
>> No repository found at
>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_9.0.mars/all/repo.
>> -> [Help 1]
>>
>> which looks very wrong why its looking at 9.0.mars instead of 4.3.mars
>>
>> Nick/Michael - can you take a look at what is missing here ?
>>
>> /max
>> http://about.me/maxandersen
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

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

From manderse at redhat.com  Fri Feb 13 02:14:41 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 13 Feb 2015 02:14:41 -0500 (EST)
Subject: [jbosstools-dev] 4.3.0.Alpha1.x now frozen and builds started
	but all red.
In-Reply-To: <54DD841C.4030201@redhat.com>
References: <D65684BE-C080-484C-832C-CA46493DFAF7@redhat.com>
	<AA374300-A89A-40AB-A756-9C30A7AFE7D5@redhat.com>
	<54DD841C.4030201@redhat.com>
Message-ID: <9A5BF764-0848-430C-80CA-6FCCC82BE241@redhat.com>


> On 13 Feb 2015, at 05:57, Nick Boldt <nboldt at redhat.com> wrote:
> 
> Have you tried fetching the jobs' configs from the server, batch-fixing 
> the files locally, and then pushing them back to the server?

"I'm not going to update all those jobs by hand at 1 AM :)" - that referred to me not trusting myself at 1 am to do global search and replace in all the job configs and not be able to test it before pushing. 

> There's a mojo for that.
> 
> Anyway, the issue is fixed (thanks to Denis) and builds are now becoming 
> blue. Left status in the JIRA and I'm off to bed.
> 

Great thanks!

> 
>> On 02/12/2015 07:21 PM, Max Rydahl Andersen wrote:
>> Found the issue: https://issues.jboss.org/browse/JBIDE-19258
>> 
>> Nick/Michael - please fix this asap.
>> 
>> I'm not going to update all those jobs by hand at 1 AM :)
>> 
>> /max
>> 
>>> Hi,
>>> 
>>> 4.3.0.Alpha1 is now building but all builds except base are broken
>>> because they can't see the produced base site.
>>> 
>>> I'm seeing errors like:
>>> 
>>> [ERROR] Internal error: java.lang.RuntimeException: Failed to load p2
>>> repository with ID 'jbosstools-base' from location
>>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_9.0.mars/all/repo:
>>> No repository found at
>>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_9.0.mars/all/repo.
>>> -> [Help 1]
>>> 
>>> which looks very wrong why its looking at 9.0.mars instead of 4.3.mars
>>> 
>>> Nick/Michael - can you take a look at what is missing here ?
>>> 
>>> /max
>>> http://about.me/maxandersen
>>> 
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> 
>> 
>> /max
>> http://about.me/maxandersen
>> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150213/51f20683/attachment.html 

From mistria at redhat.com  Fri Feb 13 09:53:10 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 13 Feb 2015 15:53:10 +0100
Subject: [jbosstools-dev] Suggested change for 4.42.0.Beta1-SNAPSHOT TP:
	Luna SR2 RC3
Message-ID: <54DE0FD6.7020302@redhat.com>

Hi all,

Please consider 
https://issues.jboss.org/browse/JBIDE-19112?focusedCommentId=13040174&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13040174
Goal is to merge it on Monday, since it's a blocker for some pending 
patches.
-- 
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/20150213/d6597edd/attachment.html 

From nboldt at redhat.com  Fri Feb 13 09:53:48 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 13 Feb 2015 09:53:48 -0500
Subject: [jbosstools-dev] 4.3.0.Alpha1.x now frozen and builds started
 but all red.
In-Reply-To: <9A5BF764-0848-430C-80CA-6FCCC82BE241@redhat.com>
References: <D65684BE-C080-484C-832C-CA46493DFAF7@redhat.com>
	<AA374300-A89A-40AB-A756-9C30A7AFE7D5@redhat.com>
	<54DD841C.4030201@redhat.com>
	<9A5BF764-0848-430C-80CA-6FCCC82BE241@redhat.com>
Message-ID: <54DE0FFC.5040904@redhat.com>

FYI

To pull/push job config.xml files to/from a Jenkins server:

https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-sync-plugin

To copy existing jobs & create new ones on a Jenkins server:

https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-publisher-plugin

On 02/13/2015 02:14 AM, Max Rydahl Andersen wrote:
>
> On 13 Feb 2015, at 05:57, Nick Boldt <nboldt at redhat.com
> <mailto:nboldt at redhat.com>> wrote:
>
>> Have you tried fetching the jobs' configs from the server, batch-fixing
>> the files locally, and then pushing them back to the server?
>
> "I'm not going to update all those jobs by hand at 1 AM
> <x-apple-data-detectors://2> :)" - that referred to me not trusting
> myself at 1 am to do global search and replace in all the job configs
> and not be able to test it before pushing.
>
>> There's a mojo for that.
>>
>> Anyway, the issue is fixed (thanks to Denis) and builds are now becoming
>> blue. Left status in the JIRA and I'm off to bed.
>>
>
> Great thanks!
>
>>
>> On 02/12/2015 07:21 PM, Max Rydahl Andersen wrote:
>>> Found the issue: https://issues.jboss.org/browse/JBIDE-19258
>>>
>>> Nick/Michael - please fix this asap.
>>>
>>> I'm not going to update all those jobs by hand at 1 AM :)
>>>
>>> /max
>>>
>>>> Hi,
>>>>
>>>> 4.3.0.Alpha1 is now building but all builds except base are broken
>>>> because they can't see the produced base site.
>>>>
>>>> I'm seeing errors like:
>>>>
>>>> [ERROR] Internal error: java.lang.RuntimeException: Failed to load p2
>>>> repository with ID 'jbosstools-base' from location
>>>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_9.0.mars/all/repo:
>>>> No repository found at
>>>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_9.0.mars/all/repo.
>>>> -> [Help 1]
>>>>
>>>> which looks very wrong why its looking at 9.0.mars instead of 4.3.mars
>>>>
>>>> Nick/Michael - can you take a look at what is missing here ?
>>>>
>>>> /max
>>>> 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
>>>
>>>
>>> /max
>>> 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
>>>
>>
>> --
>> 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 <mailto: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 Feb 13 18:07:34 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Sat, 14 Feb 2015 00:07:34 +0100
Subject: [jbosstools-dev] OpenShift v3 is removed from Alpha1,
	but still in master
Message-ID: <340F1BA6-C05D-42C3-92B0-FE9B24B39014@redhat.com>

Hi,

FYI - OpenShift v3 work did not end up getting to a useful state thus 
Andre and Jeff C. reverted the code in Alpha1x branch to the old v2 
codebase.

I've reverted the updatesite and central changes.

master nightly builds will still have it though so now QE and others can 
more easily try it out and we can get it fixed for Alpha2.

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

From nboldt at redhat.com  Sun Feb 15 14:18:51 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Sun, 15 Feb 2015 14:18:51 -0500
Subject: [jbosstools-dev] JBT 4.3 Alpha1 bits delayed
Message-ID: <54E0F11B.5030205@redhat.com>

Apologies for the delay, but due to delays getting bits built on Friday, 
and the spotty internet here in the woods of Northern Ontario, I won't 
be able to get JBT 4.3 Alpha1 pushed to QE before Monday, which is a 
holiday here.

So..

We have two options:

a) Mickael could push the bits on Monday (since it's not a holiday in 
France)

b) I can push the bits on Tuesday

Sorry for the inconvenience - I had hoped to get everything done on 
Friday but due to late code changes in a few projects, it was too late 
Friday to get it built and pushed before I left for the long weekend.

Meanwhile, you can play with the latest nightlies here:

http://download.jboss.org/jbosstools/updates/nightly/mars/

Nick

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

From mistria at redhat.com  Mon Feb 16 09:16:24 2015
From: mistria at redhat.com (Mickael Istria)
Date: Mon, 16 Feb 2015 15:16:24 +0100
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.Alpha1 bits available for
	QE testing
Message-ID: <54E1FBB8.30500@redhat.com>

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

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

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

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

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

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

-- 
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/20150216/2724d549/attachment.html 

From inf05 at gcce.tugsed.xyz  Tue Feb 17 04:50:07 2015
From: inf05 at gcce.tugsed.xyz (Mould making/ Die-casting/ Precision stamping/ Machining parts/CNC
	Precision Parts Manufacturing)
Date: Tue, 17 Feb 2015 09:50:07 +0000
Subject: [jbosstools-dev] =?gb2312?b?TW91bGQgbWFraW5nLyBEaWUtY2FzdGluZy8g?=
	=?gb2312?b?UHJlY2lzaW9uIHN0YW1waW5nLyBNYWNoaW5pbmcgcGFydHMvQ05D?=
	=?gb2312?b?IFByZWNpc2lvbiBQYXJ0cyBNYW51ZmFjdHVyaW5n0+vE+rmyz+0=?=
	=?gb2312?b?wcvP4LLhoaM=?=
Message-ID: <90e6ba614e2cc27019050f45a03e@google.com>

Dear Sir/Ms,

Good day!
As an ISO certified factory, we specialized manufacture Mould making/ Sheet  
metal process/ Die-casting/ Precision stamping/ Machining parts, with  
strong competitive price and excellent quality, for more than 20 years.
Any questions and enquiries will be highly regarded. Just email us the  
drawing and detailed requirement, you will get a complete quotation with  
technical analysis within 24 hours.

Your prompt reply is highly appreciated.

Best regards sincerely!

  Michael
________________________________________
Shenzhen, China

https://picasaweb.google.com/lh/sredir?uname=116449744458734956917&target=ALBUM&id=6112217232280041745&authkey=Gv1sRgCP-x4M2zpb22KQ&invite=CI2VnIUO&feat=email
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150217/8475e693/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/20150217/8475e693/attachment.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: email.jpg
Type: image/jpeg
Size: 4363 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150217/8475e693/attachment.jpg 

From mistria at redhat.com  Tue Feb 17 07:33:35 2015
From: mistria at redhat.com (Mickael Istria)
Date: Tue, 17 Feb 2015 13:33:35 +0100
Subject: [jbosstools-dev] Suggested change for 4.42.0.Beta1-SNAPSHOT TP:
 Luna SR2 RC3
In-Reply-To: <54DE0FD6.7020302@redhat.com>
References: <54DE0FD6.7020302@redhat.com>
Message-ID: <54E3351F.5010009@redhat.com>

The suggested changes have been merged and target-platform 
4.42.0.Beta1-SNAPSHOT is currently being built. It will be available 
within ~40 minutes, so you'll be able to merge patches that depend on 
Luna SR2.
This TP shouldl be updated again on Thurday or Friday to use Luna RC4 
(hopefully == Luna SR2 release) content.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150217/e4dbe07b/attachment.html 

From nboldt at redhat.com  Tue Feb 17 15:13:13 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 17 Feb 2015 15:13:13 -0500
Subject: [jbosstools-dev] Runtimes for testing
Message-ID: <54E3A0D9.4060806@redhat.com>

In the jbds download-cache we have about 6G of runtime zips/jars.

Are all of these runtimes still used for testing? Are there any I can 
delete?

apache-tomcat-6.0.41.zip
apache-tomcat-7.0.56.zip
db2jcc4.jar
GateIn-3.4.0.Final-jbossas5.zip
GateIn-3.5.0.Final-jbossas7.zip
h2-1.4.178.jar
hsqldb-2.2.9.zip
IzPack-install-4.3.5.jar
jbds-seamfp-patch.zip
jboss-3.2.8.SP1.zip
jboss-4.0.5.GA.zip
jboss-4.2.3.GA-jdk6.zip
jboss-5.0.1.GA-jdk6.zip
jboss-5.0.1.GA.zip
jboss-5.1.0.GA-jdk6.zip
jboss-5.1.0.GA.zip
jboss-as-7.0.2.Final.zip
jboss-as-7.1.1.Final.zip
jboss-as-distribution-6.1.0.Final.zip
jboss-eap-4.3.0.GA_CP10.zip
jboss-eap-5.1.2.zip
jboss-eap-6.0.1.zip
jboss-eap-6.1.2.zip
jboss-eap-6.2.0.zip
jboss-eap-6.2.4-full-build.zip
jboss-eap-6.2.x-patched.zip
jboss-eap-6.3.0.zip
jboss-eap-6.3.x-patched.zip
jboss-eap-fp-4.3.0.CP03-FP01.zip
jboss-eap-noauth-4.3.0.GA_CP03.zip
jboss-eap-noauth-5.2.0.zip
jboss-portal-2.7.2-bundled.zip
JBossPortletBridge-2.3.1.Final.zip
jboss-seam-2.0.1.GA.zip
jboss-seam-2.0.2.SP1.zip
jboss-seam-2.0.3.CR1.zip
jboss-seam-2.1.1.GA.zip
jboss-seam-2.1.2.zip
jboss-seam-2.2.0.CR1.zip
jboss-seam-2.2.0.GA.zip
jboss-seam-2.2.1.Final.zip
jboss-seam-2.2.2.Final.zip
jboss-seam-2.3.0.ALPHA-distribution.zip
jboss-seam-distribution-2.3.0.Final-dist.zip
jconn4-26666.jar
mockito-1.9.5.zip
mysql-connector-java-5.1.21-bin.jar
ojdbc6.jar
poi-src-2.5.1-final-20040804.zip
postgresql-9.1-902.jdbc4.jar
rhds-seam-gen-patch.zip
saxonhe9-2-1-5j.zip
soa-4.3.0.GA_CP05.zip
sqljdbc4.jar
wildfly-8.0.0.Final.zip
wildfly-8.1.0.Final.zip

From akazakov at exadel.com  Tue Feb 17 15:51:03 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Tue, 17 Feb 2015 12:51:03 -0800
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <54E3A0D9.4060806@redhat.com>
References: <54E3A0D9.4060806@redhat.com>
Message-ID: <54E3A9B7.9060008@exadel.com>

We can remove the following:
jboss-seam-2.0.1.GA.zip
jboss-seam-2.0.2.SP1.zip
jboss-seam-2.0.3.CR1.zip
jboss-seam-2.1.1.GA.zip
jboss-seam-2.2.0.CR1.zip
jboss-seam-2.2.0.GA.zip
jboss-seam-2.2.2.Final.zip
jboss-seam-2.3.0.ALPHA-distribution.zip

And we still test:
jboss-seam-2.1.2.zip
jboss-seam-2.2.1.Final.zip
jboss-seam-distribution-2.3.0.Final-dist.zip

On 02/17/2015 12:13 PM, Nick Boldt wrote:
> In the jbds download-cache we have about 6G of runtime zips/jars.
>
> Are all of these runtimes still used for testing? Are there any I can
> delete?
>
> apache-tomcat-6.0.41.zip
> apache-tomcat-7.0.56.zip
> db2jcc4.jar
> GateIn-3.4.0.Final-jbossas5.zip
> GateIn-3.5.0.Final-jbossas7.zip
> h2-1.4.178.jar
> hsqldb-2.2.9.zip
> IzPack-install-4.3.5.jar
> jbds-seamfp-patch.zip
> jboss-3.2.8.SP1.zip
> jboss-4.0.5.GA.zip
> jboss-4.2.3.GA-jdk6.zip
> jboss-5.0.1.GA-jdk6.zip
> jboss-5.0.1.GA.zip
> jboss-5.1.0.GA-jdk6.zip
> jboss-5.1.0.GA.zip
> jboss-as-7.0.2.Final.zip
> jboss-as-7.1.1.Final.zip
> jboss-as-distribution-6.1.0.Final.zip
> jboss-eap-4.3.0.GA_CP10.zip
> jboss-eap-5.1.2.zip
> jboss-eap-6.0.1.zip
> jboss-eap-6.1.2.zip
> jboss-eap-6.2.0.zip
> jboss-eap-6.2.4-full-build.zip
> jboss-eap-6.2.x-patched.zip
> jboss-eap-6.3.0.zip
> jboss-eap-6.3.x-patched.zip
> jboss-eap-fp-4.3.0.CP03-FP01.zip
> jboss-eap-noauth-4.3.0.GA_CP03.zip
> jboss-eap-noauth-5.2.0.zip
> jboss-portal-2.7.2-bundled.zip
> JBossPortletBridge-2.3.1.Final.zip
> jboss-seam-2.0.1.GA.zip
> jboss-seam-2.0.2.SP1.zip
> jboss-seam-2.0.3.CR1.zip
> jboss-seam-2.1.1.GA.zip
> jboss-seam-2.1.2.zip
> jboss-seam-2.2.0.CR1.zip
> jboss-seam-2.2.0.GA.zip
> jboss-seam-2.2.1.Final.zip
> jboss-seam-2.2.2.Final.zip
> jboss-seam-2.3.0.ALPHA-distribution.zip
> jboss-seam-distribution-2.3.0.Final-dist.zip
> jconn4-26666.jar
> mockito-1.9.5.zip
> mysql-connector-java-5.1.21-bin.jar
> ojdbc6.jar
> poi-src-2.5.1-final-20040804.zip
> postgresql-9.1-902.jdbc4.jar
> rhds-seam-gen-patch.zip
> saxonhe9-2-1-5j.zip
> soa-4.3.0.GA_CP05.zip
> sqljdbc4.jar
> wildfly-8.0.0.Final.zip
> wildfly-8.1.0.Final.zip
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From nboldt at redhat.com  Tue Feb 17 17:02:25 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 17 Feb 2015 17:02:25 -0500
Subject: [jbosstools-dev] Proposal to add Mylyn Wikitext feature to the
 JBT/JBDS 4.50.x target platforms
Message-ID: <54E3BA71.5030609@redhat.com>

In JBDS-3259, it's been requested that we include Wikitext support in 
JBDS (installer/BYOE), and by extension make it easier to get this into 
JBoss Tools, too. This would provide a handy markdown viewer in Eclipse.

So, to do that, we need to add it to the JBT & JBDS target platforms, so 
it's more readily available - especially in JBDS.

PR:

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

JIRA:

https://issues.jboss.org/browse/JBDS-3259

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

From nboldt at redhat.com  Wed Feb 18 11:58:13 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 18 Feb 2015 11:58:13 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: JBoss Tools 4.2.3.Beta1 code
 freeze is next week on Thurs 26 Feb
Message-ID: <54E4C4A5.4000407@redhat.com>

Just a reminder for those who aren't regularly checking the JBIDE 
calendar in JIRA [1].

Some important dates next week:

2015-02-23 Eclipse Luna SR2 quiet week begins

2015-02-25 JBT 4.2.3.Beta1 new target platform 4.42.0.Beta1 available

2015-02-26 JBT 4.2.3.Beta1 code freeze / N&N due

2015-03-04 JBT 4.2.3.Beta1 available

--

[1] 
https://issues.jboss.org/browse/JBIDE?selectedTab=com.atlassian.jira.jira-projects-plugin%3Aversions-panel

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

From akazakov at exadel.com  Wed Feb 18 13:48:49 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Wed, 18 Feb 2015 10:48:49 -0800
Subject: [jbosstools-dev] ACTION REQUIRED: JBoss Tools 4.2.3.Beta1 code
 freeze is next week on Thurs 26 Feb
In-Reply-To: <54E4C4A5.4000407@redhat.com>
References: <54E4C4A5.4000407@redhat.com>
Message-ID: <54E4DE91.7060702@exadel.com>

On 02/18/2015 08:58 AM, Nick Boldt wrote:
> 2015-02-26 JBT 4.2.3.Beta1 code freeze / N&N due
I would like to highlight that we need N&N for 4.3.0 by the 4.2.3.Beta1 
code freeze this time. This is because of tight schedule for JBDS 
8.1.0/JBT 4.2.3. So please prepare your N&N (or reject if you don't have 
anything) by next Thursday! I created a JIRA for N&N: 
https://issues.jboss.org/browse/JBIDE-19293

Thank you.


From nboldt at redhat.com  Wed Feb 18 14:04:28 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 18 Feb 2015 14:04:28 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: JBoss Tools 4.2.3.Beta1 code
 freeze is next week on Thurs 26 Feb
In-Reply-To: <54E4DE91.7060702@exadel.com>
References: <54E4C4A5.4000407@redhat.com> <54E4DE91.7060702@exadel.com>
Message-ID: <54E4E23C.6010604@redhat.com>

Just to clarify, that's the N&N for 4.2.3, not 4.3.0... correct?

On 02/18/2015 01:48 PM, Alexey Kazakov wrote:
> On 02/18/2015 08:58 AM, Nick Boldt wrote:
>> 2015-02-26 JBT 4.2.3.Beta1 code freeze / N&N due
> I would like to highlight that we need N&N for 4.3.0 by the 4.2.3.Beta1
> code freeze this time. This is because of tight schedule for JBDS
> 8.1.0/JBT 4.2.3. So please prepare your N&N (or reject if you don't have
> anything) by next Thursday! I created a JIRA for N&N:
> https://issues.jboss.org/browse/JBIDE-19293
>
> Thank you.
>
> _______________________________________________
> 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 akazakov at exadel.com  Wed Feb 18 14:10:42 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Wed, 18 Feb 2015 11:10:42 -0800
Subject: [jbosstools-dev] ACTION REQUIRED: JBoss Tools 4.2.3.Beta1 code
 freeze is next week on Thurs 26 Feb
In-Reply-To: <54E4E23C.6010604@redhat.com>
References: <54E4C4A5.4000407@redhat.com> <54E4DE91.7060702@exadel.com>
	<54E4E23C.6010604@redhat.com>
Message-ID: <54E4E3B2.9010308@exadel.com>

On 02/18/2015 11:04 AM, Nick Boldt wrote:
> Just to clarify, that's the N&N for 4.2.3, not 4.3.0... correct?
Oh, yes, sorry. I meant 4.2.3. Too many releases for this month ;)

>
> On 02/18/2015 01:48 PM, Alexey Kazakov wrote:
>> On 02/18/2015 08:58 AM, Nick Boldt wrote:
>>> 2015-02-26 JBT 4.2.3.Beta1 code freeze / N&N due
>> I would like to highlight that we need N&N for 4.3.0 by the 4.2.3.Beta1
>> code freeze this time. This is because of tight schedule for JBDS
>> 8.1.0/JBT 4.2.3. So please prepare your N&N (or reject if you don't have
>> anything) by next Thursday! I created a JIRA for N&N:
>> https://issues.jboss.org/browse/JBIDE-19293
>>
>> Thank you.
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>


From mistria at redhat.com  Thu Feb 19 12:43:11 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 19 Feb 2015 18:43:11 +0100
Subject: [jbosstools-dev] Suggested change for 4.42.0.Beta1-SNAPSHOT TP:
 Luna SR2 RC4
In-Reply-To: <54E3351F.5010009@redhat.com>
References: <54DE0FD6.7020302@redhat.com> <54E3351F.5010009@redhat.com>
Message-ID: <54E620AF.8040107@redhat.com>

Eclipse Luna SR2 RC4 (to be promoted as Luna SR2 next week, unless 
critical issue is found) has been staged today. We'd like to update the 
4.42.0.Beta1-SNAPSHSOT Target-Platforms ASAP.
Please consider 
https://issues.jboss.org/browse/JBIDE-19112?focusedCommentId=13042122&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13042122 
for details and instruction to give it a try.
-- 
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/20150219/a4eee5ad/attachment.html 

From fbricon at redhat.com  Thu Feb 19 23:06:47 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Thu, 19 Feb 2015 23:06:47 -0500
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <54E3A9B7.9060008@exadel.com>
References: <54E3A0D9.4060806@redhat.com> <54E3A9B7.9060008@exadel.com>
Message-ID: <4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>

Err... removing jboss-seam-2.0.1.GA.zip broke jbosstools-central_master : http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console>

Can you rollback pretty please?

> Le 17 f?vr. 2015 ? 15:51, Alexey Kazakov <akazakov at exadel.com> a ?crit :
> 
> We can remove the following:
> jboss-seam-2.0.1.GA.zip
> jboss-seam-2.0.2.SP1.zip
> jboss-seam-2.0.3.CR1.zip
> jboss-seam-2.1.1.GA.zip
> jboss-seam-2.2.0.CR1.zip
> jboss-seam-2.2.0.GA.zip
> jboss-seam-2.2.2.Final.zip
> jboss-seam-2.3.0.ALPHA-distribution.zip
> 
> And we still test:
> jboss-seam-2.1.2.zip
> jboss-seam-2.2.1.Final.zip
> jboss-seam-distribution-2.3.0.Final-dist.zip
> 
> On 02/17/2015 12:13 PM, Nick Boldt wrote:
>> In the jbds download-cache we have about 6G of runtime zips/jars.
>> 
>> Are all of these runtimes still used for testing? Are there any I can
>> delete?
>> 
>> apache-tomcat-6.0.41.zip
>> apache-tomcat-7.0.56.zip
>> db2jcc4.jar
>> GateIn-3.4.0.Final-jbossas5.zip
>> GateIn-3.5.0.Final-jbossas7.zip
>> h2-1.4.178.jar
>> hsqldb-2.2.9.zip
>> IzPack-install-4.3.5.jar
>> jbds-seamfp-patch.zip
>> jboss-3.2.8.SP1.zip
>> jboss-4.0.5.GA.zip
>> jboss-4.2.3.GA-jdk6.zip
>> jboss-5.0.1.GA-jdk6.zip
>> jboss-5.0.1.GA.zip
>> jboss-5.1.0.GA-jdk6.zip
>> jboss-5.1.0.GA.zip
>> jboss-as-7.0.2.Final.zip
>> jboss-as-7.1.1.Final.zip
>> jboss-as-distribution-6.1.0.Final.zip
>> jboss-eap-4.3.0.GA_CP10.zip
>> jboss-eap-5.1.2.zip
>> jboss-eap-6.0.1.zip
>> jboss-eap-6.1.2.zip
>> jboss-eap-6.2.0.zip
>> jboss-eap-6.2.4-full-build.zip
>> jboss-eap-6.2.x-patched.zip
>> jboss-eap-6.3.0.zip
>> jboss-eap-6.3.x-patched.zip
>> jboss-eap-fp-4.3.0.CP03-FP01.zip
>> jboss-eap-noauth-4.3.0.GA_CP03.zip
>> jboss-eap-noauth-5.2.0.zip
>> jboss-portal-2.7.2-bundled.zip
>> JBossPortletBridge-2.3.1.Final.zip
>> jboss-seam-2.0.1.GA.zip
>> jboss-seam-2.0.2.SP1.zip
>> jboss-seam-2.0.3.CR1.zip
>> jboss-seam-2.1.1.GA.zip
>> jboss-seam-2.1.2.zip
>> jboss-seam-2.2.0.CR1.zip
>> jboss-seam-2.2.0.GA.zip
>> jboss-seam-2.2.1.Final.zip
>> jboss-seam-2.2.2.Final.zip
>> jboss-seam-2.3.0.ALPHA-distribution.zip
>> jboss-seam-distribution-2.3.0.Final-dist.zip
>> jconn4-26666.jar
>> mockito-1.9.5.zip
>> mysql-connector-java-5.1.21-bin.jar
>> ojdbc6.jar
>> poi-src-2.5.1-final-20040804.zip
>> postgresql-9.1-902.jdbc4.jar
>> rhds-seam-gen-patch.zip
>> saxonhe9-2-1-5j.zip
>> soa-4.3.0.GA_CP05.zip
>> sqljdbc4.jar
>> wildfly-8.0.0.Final.zip
>> wildfly-8.1.0.Final.zip
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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

From manderse at redhat.com  Fri Feb 20 06:25:39 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 20 Feb 2015 12:25:39 +0100
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>
References: <54E3A0D9.4060806@redhat.com> <54E3A9B7.9060008@exadel.com>
	<4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>
Message-ID: <7EA1E254-7F4F-40DA-85B7-17A9CBC01853@redhat.com>

On 20 Feb 2015, at 5:06, Fred Bricon wrote:

> Err... removing jboss-seam-2.0.1.GA.zip broke 
> jbosstools-central_master : 
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console 
> <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console>
>
> Can you rollback pretty please?


eh...this location is supposed to work as a *cache* right?

so why wasn't the build fetching the bits to fill up the cache ?

/max

>> Le 17 f?vr. 2015 ? 15:51, Alexey Kazakov <akazakov at exadel.com> a 
>> ?crit :
>>
>> We can remove the following:
>> jboss-seam-2.0.1.GA.zip
>> jboss-seam-2.0.2.SP1.zip
>> jboss-seam-2.0.3.CR1.zip
>> jboss-seam-2.1.1.GA.zip
>> jboss-seam-2.2.0.CR1.zip
>> jboss-seam-2.2.0.GA.zip
>> jboss-seam-2.2.2.Final.zip
>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>
>> And we still test:
>> jboss-seam-2.1.2.zip
>> jboss-seam-2.2.1.Final.zip
>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>
>> On 02/17/2015 12:13 PM, Nick Boldt wrote:
>>> In the jbds download-cache we have about 6G of runtime zips/jars.
>>>
>>> Are all of these runtimes still used for testing? Are there any I 
>>> can
>>> delete?
>>>
>>> apache-tomcat-6.0.41.zip
>>> apache-tomcat-7.0.56.zip
>>> db2jcc4.jar
>>> GateIn-3.4.0.Final-jbossas5.zip
>>> GateIn-3.5.0.Final-jbossas7.zip
>>> h2-1.4.178.jar
>>> hsqldb-2.2.9.zip
>>> IzPack-install-4.3.5.jar
>>> jbds-seamfp-patch.zip
>>> jboss-3.2.8.SP1.zip
>>> jboss-4.0.5.GA.zip
>>> jboss-4.2.3.GA-jdk6.zip
>>> jboss-5.0.1.GA-jdk6.zip
>>> jboss-5.0.1.GA.zip
>>> jboss-5.1.0.GA-jdk6.zip
>>> jboss-5.1.0.GA.zip
>>> jboss-as-7.0.2.Final.zip
>>> jboss-as-7.1.1.Final.zip
>>> jboss-as-distribution-6.1.0.Final.zip
>>> jboss-eap-4.3.0.GA_CP10.zip
>>> jboss-eap-5.1.2.zip
>>> jboss-eap-6.0.1.zip
>>> jboss-eap-6.1.2.zip
>>> jboss-eap-6.2.0.zip
>>> jboss-eap-6.2.4-full-build.zip
>>> jboss-eap-6.2.x-patched.zip
>>> jboss-eap-6.3.0.zip
>>> jboss-eap-6.3.x-patched.zip
>>> jboss-eap-fp-4.3.0.CP03-FP01.zip
>>> jboss-eap-noauth-4.3.0.GA_CP03.zip
>>> jboss-eap-noauth-5.2.0.zip
>>> jboss-portal-2.7.2-bundled.zip
>>> JBossPortletBridge-2.3.1.Final.zip
>>> jboss-seam-2.0.1.GA.zip
>>> jboss-seam-2.0.2.SP1.zip
>>> jboss-seam-2.0.3.CR1.zip
>>> jboss-seam-2.1.1.GA.zip
>>> jboss-seam-2.1.2.zip
>>> jboss-seam-2.2.0.CR1.zip
>>> jboss-seam-2.2.0.GA.zip
>>> jboss-seam-2.2.1.Final.zip
>>> jboss-seam-2.2.2.Final.zip
>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>> jconn4-26666.jar
>>> mockito-1.9.5.zip
>>> mysql-connector-java-5.1.21-bin.jar
>>> ojdbc6.jar
>>> poi-src-2.5.1-final-20040804.zip
>>> postgresql-9.1-902.jdbc4.jar
>>> rhds-seam-gen-patch.zip
>>> saxonhe9-2-1-5j.zip
>>> soa-4.3.0.GA_CP05.zip
>>> sqljdbc4.jar
>>> wildfly-8.0.0.Final.zip
>>> wildfly-8.1.0.Final.zip
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From nboldt at redhat.com  Fri Feb 20 09:43:04 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 20 Feb 2015 09:43:04 -0500
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <7EA1E254-7F4F-40DA-85B7-17A9CBC01853@redhat.com>
References: <54E3A0D9.4060806@redhat.com>
	<54E3A9B7.9060008@exadel.com>	<4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>
	<7EA1E254-7F4F-40DA-85B7-17A9CBC01853@redhat.com>
Message-ID: <54E747F8.1090907@redhat.com>

As we discovered last night w/ the jbostools-server builds, the mojo to 
fetch requirements/dependencies/runtimes is no longer working in 
Jenkins. Works fine on local, but won't fetch in Jenkins.

Maybe something to do with skipPrivateRequirements?

Or a bug in latest Maven? I use 3.1.1 here, but Jenkins uses 3.2.5 for 
the 9.0/master jobs.

On 02/20/2015 06:25 AM, Max Rydahl Andersen wrote:
> On 20 Feb 2015, at 5:06, Fred Bricon wrote:
>
>> Err... removing jboss-seam-2.0.1.GA.zip broke
>> jbosstools-central_master :
>> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console
>> <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console>
>>
>> Can you rollback pretty please?
>
>
> eh...this location is supposed to work as a *cache* right?
>
> so why wasn't the build fetching the bits to fill up the cache ?
>
> /max
>
>>> Le 17 f?vr. 2015 ? 15:51, Alexey Kazakov <akazakov at exadel.com> a
>>> ?crit :
>>>
>>> We can remove the following:
>>> jboss-seam-2.0.1.GA.zip
>>> jboss-seam-2.0.2.SP1.zip
>>> jboss-seam-2.0.3.CR1.zip
>>> jboss-seam-2.1.1.GA.zip
>>> jboss-seam-2.2.0.CR1.zip
>>> jboss-seam-2.2.0.GA.zip
>>> jboss-seam-2.2.2.Final.zip
>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>
>>> And we still test:
>>> jboss-seam-2.1.2.zip
>>> jboss-seam-2.2.1.Final.zip
>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>
>>> On 02/17/2015 12:13 PM, Nick Boldt wrote:
>>>> In the jbds download-cache we have about 6G of runtime zips/jars.
>>>>
>>>> Are all of these runtimes still used for testing? Are there any I
>>>> can
>>>> delete?
>>>>
>>>> apache-tomcat-6.0.41.zip
>>>> apache-tomcat-7.0.56.zip
>>>> db2jcc4.jar
>>>> GateIn-3.4.0.Final-jbossas5.zip
>>>> GateIn-3.5.0.Final-jbossas7.zip
>>>> h2-1.4.178.jar
>>>> hsqldb-2.2.9.zip
>>>> IzPack-install-4.3.5.jar
>>>> jbds-seamfp-patch.zip
>>>> jboss-3.2.8.SP1.zip
>>>> jboss-4.0.5.GA.zip
>>>> jboss-4.2.3.GA-jdk6.zip
>>>> jboss-5.0.1.GA-jdk6.zip
>>>> jboss-5.0.1.GA.zip
>>>> jboss-5.1.0.GA-jdk6.zip
>>>> jboss-5.1.0.GA.zip
>>>> jboss-as-7.0.2.Final.zip
>>>> jboss-as-7.1.1.Final.zip
>>>> jboss-as-distribution-6.1.0.Final.zip
>>>> jboss-eap-4.3.0.GA_CP10.zip
>>>> jboss-eap-5.1.2.zip
>>>> jboss-eap-6.0.1.zip
>>>> jboss-eap-6.1.2.zip
>>>> jboss-eap-6.2.0.zip
>>>> jboss-eap-6.2.4-full-build.zip
>>>> jboss-eap-6.2.x-patched.zip
>>>> jboss-eap-6.3.0.zip
>>>> jboss-eap-6.3.x-patched.zip
>>>> jboss-eap-fp-4.3.0.CP03-FP01.zip
>>>> jboss-eap-noauth-4.3.0.GA_CP03.zip
>>>> jboss-eap-noauth-5.2.0.zip
>>>> jboss-portal-2.7.2-bundled.zip
>>>> JBossPortletBridge-2.3.1.Final.zip
>>>> jboss-seam-2.0.1.GA.zip
>>>> jboss-seam-2.0.2.SP1.zip
>>>> jboss-seam-2.0.3.CR1.zip
>>>> jboss-seam-2.1.1.GA.zip
>>>> jboss-seam-2.1.2.zip
>>>> jboss-seam-2.2.0.CR1.zip
>>>> jboss-seam-2.2.0.GA.zip
>>>> jboss-seam-2.2.1.Final.zip
>>>> jboss-seam-2.2.2.Final.zip
>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>> jconn4-26666.jar
>>>> mockito-1.9.5.zip
>>>> mysql-connector-java-5.1.21-bin.jar
>>>> ojdbc6.jar
>>>> poi-src-2.5.1-final-20040804.zip
>>>> postgresql-9.1-902.jdbc4.jar
>>>> rhds-seam-gen-patch.zip
>>>> saxonhe9-2-1-5j.zip
>>>> soa-4.3.0.GA_CP05.zip
>>>> sqljdbc4.jar
>>>> wildfly-8.0.0.Final.zip
>>>> wildfly-8.1.0.Final.zip
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

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

From nboldt at redhat.com  Fri Feb 20 09:46:27 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 20 Feb 2015 09:46:27 -0500
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>
References: <54E3A0D9.4060806@redhat.com> <54E3A9B7.9060008@exadel.com>
	<4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>
Message-ID: <54E748C3.1040709@redhat.com>

Just tried to roll it back and discovered the file was already there:

NEW ones:

-rw-rw-r-- 1 hudson hudson  93M Feb 20 00:08 jboss-seam-2.0.1.GA.zip
-rw-rw-r-- 1 hudson hudson 106M Feb 20 00:08 jboss-seam-2.1.1.GA.zip
-rw-rw-r-- 1 hudson hudson 112M Feb 20 00:12 jboss-seam-2.2.0.GA.zip

OLD ones:

-rw-rw-r-- 1 hudson hudson  93M Feb 26  2013 jboss-seam-2.0.1.GA.zip
-rw-rw-r-- 1 hudson hudson 106M Feb 27  2013 jboss-seam-2.1.1.GA.zip
-rw-rw-r-- 1 hudson hudson 112M Jun  3  2013 jboss-seam-2.2.0.GA.zip

Guess you don't need Seam 2.0.2, 2.0.3, 2.2.2 or 2.3?

On 02/19/2015 11:06 PM, Fred Bricon wrote:
> Err... removing jboss-seam-2.0.1.GA.zip broke jbosstools-central_master
> :http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console
>
> Can yourollback pretty please?
>
>> Le 17 f?vr. 2015 ? 15:51, Alexey Kazakov <akazakov at exadel.com
>> <mailto:akazakov at exadel.com>> a ?crit :
>>
>> We can remove the following:
>> jboss-seam-2.0.1.GA.zip
>> jboss-seam-2.0.2.SP1.zip
>> jboss-seam-2.0.3.CR1.zip
>> jboss-seam-2.1.1.GA.zip
>> jboss-seam-2.2.0.CR1.zip
>> jboss-seam-2.2.0.GA.zip
>> jboss-seam-2.2.2.Final.zip
>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>
>> And we still test:
>> jboss-seam-2.1.2.zip
>> jboss-seam-2.2.1.Final.zip
>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>
>> On 02/17/2015 12:13 PM, Nick Boldt wrote:
>>> In the jbds download-cache we have about 6G of runtime zips/jars.
>>>
>>> Are all of these runtimes still used for testing? Are there any I can
>>> delete?
>>>
>>> apache-tomcat-6.0.41.zip
>>> apache-tomcat-7.0.56.zip
>>> db2jcc4.jar
>>> GateIn-3.4.0.Final-jbossas5.zip
>>> GateIn-3.5.0.Final-jbossas7.zip
>>> h2-1.4.178.jar
>>> hsqldb-2.2.9.zip
>>> IzPack-install-4.3.5.jar
>>> jbds-seamfp-patch.zip
>>> jboss-3.2.8.SP1.zip
>>> jboss-4.0.5.GA.zip
>>> jboss-4.2.3.GA-jdk6.zip
>>> jboss-5.0.1.GA-jdk6.zip
>>> jboss-5.0.1.GA.zip
>>> jboss-5.1.0.GA-jdk6.zip
>>> jboss-5.1.0.GA.zip
>>> jboss-as-7.0.2.Final.zip
>>> jboss-as-7.1.1.Final.zip
>>> jboss-as-distribution-6.1.0.Final.zip
>>> jboss-eap-4.3.0.GA_CP10.zip
>>> jboss-eap-5.1.2.zip
>>> jboss-eap-6.0.1.zip
>>> jboss-eap-6.1.2.zip
>>> jboss-eap-6.2.0.zip
>>> jboss-eap-6.2.4-full-build.zip
>>> jboss-eap-6.2.x-patched.zip
>>> jboss-eap-6.3.0.zip
>>> jboss-eap-6.3.x-patched.zip
>>> jboss-eap-fp-4.3.0.CP03-FP01.zip
>>> jboss-eap-noauth-4.3.0.GA_CP03.zip
>>> jboss-eap-noauth-5.2.0.zip
>>> jboss-portal-2.7.2-bundled.zip
>>> JBossPortletBridge-2.3.1.Final.zip
>>> jboss-seam-2.0.1.GA.zip
>>> jboss-seam-2.0.2.SP1.zip
>>> jboss-seam-2.0.3.CR1.zip
>>> jboss-seam-2.1.1.GA.zip
>>> jboss-seam-2.1.2.zip
>>> jboss-seam-2.2.0.CR1.zip
>>> jboss-seam-2.2.0.GA.zip
>>> jboss-seam-2.2.1.Final.zip
>>> jboss-seam-2.2.2.Final.zip
>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>> jconn4-26666.jar
>>> mockito-1.9.5.zip
>>> mysql-connector-java-5.1.21-bin.jar
>>> ojdbc6.jar
>>> poi-src-2.5.1-final-20040804.zip
>>> postgresql-9.1-902.jdbc4.jar
>>> rhds-seam-gen-patch.zip
>>> saxonhe9-2-1-5j.zip
>>> soa-4.3.0.GA_CP05.zip
>>> sqljdbc4.jar
>>> wildfly-8.0.0.Final.zip
>>> wildfly-8.1.0.Final.zip
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

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

From nboldt at redhat.com  Fri Feb 20 09:54:24 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 20 Feb 2015 09:54:24 -0500
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <C715ACCE-E613-4EF0-8017-66B1E1CE8C91@redhat.com>
References: <54E3A0D9.4060806@redhat.com> <54E3A9B7.9060008@exadel.com>
	<4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>
	<7EA1E254-7F4F-40DA-85B7-17A9CBC01853@redhat.com>
	<54E747F8.1090907@redhat.com>
	<C715ACCE-E613-4EF0-8017-66B1E1CE8C91@redhat.com>
Message-ID: <54E74AA0.9010307@redhat.com>

But isn't that only for PRIVATE requirements? That is, things like EAP, 
but not WildFly?

Last night jbosstools-server_4.2.luna was failing to fetch *any* of its 
missing runtimes, be it EAP or WFLY.

Is that a bug?

On 02/20/2015 09:52 AM, Max Rydahl Andersen wrote:
> On 20 Feb 2015, at 15:43, Nick Boldt wrote:
>
>> As we discovered last night w/ the jbostools-server builds, the mojo
>> to fetch requirements/dependencies/runtimes is no longer working in
>> Jenkins. Works fine on local, but won't fetch in Jenkins.
>>
>> Maybe something to do with skipPrivateRequirements?
>
>
> yes, skipPrivateRequirements should be false for it to work.
>>
>> Or a bug in latest Maven? I use 3.1.1 here, but Jenkins uses 3.2.5 for
>> the 9.0/master jobs.
>>
>> On 02/20/2015 06:25 AM, Max Rydahl Andersen wrote:
>>> On 20 Feb 2015, at 5:06, Fred Bricon wrote:
>>>
>>>> Err... removing jboss-seam-2.0.1.GA.zip broke
>>>> jbosstools-central_master :
>>>> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console
>>>>
>>>> <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console>
>>>>
>>>>
>>>> Can you rollback pretty please?
>>>
>>>
>>> eh...this location is supposed to work as a *cache* right?
>>>
>>> so why wasn't the build fetching the bits to fill up the cache ?
>>>
>>> /max
>>>
>>>>> Le 17 f?vr. 2015 ? 15:51, Alexey Kazakov <akazakov at exadel.com> a
>>>>> ?crit :
>>>>>
>>>>> We can remove the following:
>>>>> jboss-seam-2.0.1.GA.zip
>>>>> jboss-seam-2.0.2.SP1.zip
>>>>> jboss-seam-2.0.3.CR1.zip
>>>>> jboss-seam-2.1.1.GA.zip
>>>>> jboss-seam-2.2.0.CR1.zip
>>>>> jboss-seam-2.2.0.GA.zip
>>>>> jboss-seam-2.2.2.Final.zip
>>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>>
>>>>> And we still test:
>>>>> jboss-seam-2.1.2.zip
>>>>> jboss-seam-2.2.1.Final.zip
>>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>>
>>>>> On 02/17/2015 12:13 PM, Nick Boldt wrote:
>>>>>> In the jbds download-cache we have about 6G of runtime zips/jars.
>>>>>>
>>>>>> Are all of these runtimes still used for testing? Are there any I
>>>>>> can
>>>>>> delete?
>>>>>>
>>>>>> apache-tomcat-6.0.41.zip
>>>>>> apache-tomcat-7.0.56.zip
>>>>>> db2jcc4.jar
>>>>>> GateIn-3.4.0.Final-jbossas5.zip
>>>>>> GateIn-3.5.0.Final-jbossas7.zip
>>>>>> h2-1.4.178.jar
>>>>>> hsqldb-2.2.9.zip
>>>>>> IzPack-install-4.3.5.jar
>>>>>> jbds-seamfp-patch.zip
>>>>>> jboss-3.2.8.SP1.zip
>>>>>> jboss-4.0.5.GA.zip
>>>>>> jboss-4.2.3.GA-jdk6.zip
>>>>>> jboss-5.0.1.GA-jdk6.zip
>>>>>> jboss-5.0.1.GA.zip
>>>>>> jboss-5.1.0.GA-jdk6.zip
>>>>>> jboss-5.1.0.GA.zip
>>>>>> jboss-as-7.0.2.Final.zip
>>>>>> jboss-as-7.1.1.Final.zip
>>>>>> jboss-as-distribution-6.1.0.Final.zip
>>>>>> jboss-eap-4.3.0.GA_CP10.zip
>>>>>> jboss-eap-5.1.2.zip
>>>>>> jboss-eap-6.0.1.zip
>>>>>> jboss-eap-6.1.2.zip
>>>>>> jboss-eap-6.2.0.zip
>>>>>> jboss-eap-6.2.4-full-build.zip
>>>>>> jboss-eap-6.2.x-patched.zip
>>>>>> jboss-eap-6.3.0.zip
>>>>>> jboss-eap-6.3.x-patched.zip
>>>>>> jboss-eap-fp-4.3.0.CP03-FP01.zip
>>>>>> jboss-eap-noauth-4.3.0.GA_CP03.zip
>>>>>> jboss-eap-noauth-5.2.0.zip
>>>>>> jboss-portal-2.7.2-bundled.zip
>>>>>> JBossPortletBridge-2.3.1.Final.zip
>>>>>> jboss-seam-2.0.1.GA.zip
>>>>>> jboss-seam-2.0.2.SP1.zip
>>>>>> jboss-seam-2.0.3.CR1.zip
>>>>>> jboss-seam-2.1.1.GA.zip
>>>>>> jboss-seam-2.1.2.zip
>>>>>> jboss-seam-2.2.0.CR1.zip
>>>>>> jboss-seam-2.2.0.GA.zip
>>>>>> jboss-seam-2.2.1.Final.zip
>>>>>> jboss-seam-2.2.2.Final.zip
>>>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>>> jconn4-26666.jar
>>>>>> mockito-1.9.5.zip
>>>>>> mysql-connector-java-5.1.21-bin.jar
>>>>>> ojdbc6.jar
>>>>>> poi-src-2.5.1-final-20040804.zip
>>>>>> postgresql-9.1-902.jdbc4.jar
>>>>>> rhds-seam-gen-patch.zip
>>>>>> saxonhe9-2-1-5j.zip
>>>>>> soa-4.3.0.GA_CP05.zip
>>>>>> sqljdbc4.jar
>>>>>> wildfly-8.0.0.Final.zip
>>>>>> wildfly-8.1.0.Final.zip
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>
>
> /max
> http://about.me/maxandersen

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

From manderse at redhat.com  Fri Feb 20 09:52:38 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 20 Feb 2015 15:52:38 +0100
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <54E747F8.1090907@redhat.com>
References: <54E3A0D9.4060806@redhat.com> <54E3A9B7.9060008@exadel.com>
	<4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>
	<7EA1E254-7F4F-40DA-85B7-17A9CBC01853@redhat.com>
	<54E747F8.1090907@redhat.com>
Message-ID: <C715ACCE-E613-4EF0-8017-66B1E1CE8C91@redhat.com>

On 20 Feb 2015, at 15:43, Nick Boldt wrote:

> As we discovered last night w/ the jbostools-server builds, the mojo 
> to fetch requirements/dependencies/runtimes is no longer working in 
> Jenkins. Works fine on local, but won't fetch in Jenkins.
>
> Maybe something to do with skipPrivateRequirements?


yes, skipPrivateRequirements should be false for it to work.
>
> Or a bug in latest Maven? I use 3.1.1 here, but Jenkins uses 3.2.5 for 
> the 9.0/master jobs.
>
> On 02/20/2015 06:25 AM, Max Rydahl Andersen wrote:
>> On 20 Feb 2015, at 5:06, Fred Bricon wrote:
>>
>>> Err... removing jboss-seam-2.0.1.GA.zip broke
>>> jbosstools-central_master :
>>> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console
>>> <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console>
>>>
>>> Can you rollback pretty please?
>>
>>
>> eh...this location is supposed to work as a *cache* right?
>>
>> so why wasn't the build fetching the bits to fill up the cache ?
>>
>> /max
>>
>>>> Le 17 f?vr. 2015 ? 15:51, Alexey Kazakov <akazakov at exadel.com> a
>>>> ?crit :
>>>>
>>>> We can remove the following:
>>>> jboss-seam-2.0.1.GA.zip
>>>> jboss-seam-2.0.2.SP1.zip
>>>> jboss-seam-2.0.3.CR1.zip
>>>> jboss-seam-2.1.1.GA.zip
>>>> jboss-seam-2.2.0.CR1.zip
>>>> jboss-seam-2.2.0.GA.zip
>>>> jboss-seam-2.2.2.Final.zip
>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>
>>>> And we still test:
>>>> jboss-seam-2.1.2.zip
>>>> jboss-seam-2.2.1.Final.zip
>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>
>>>> On 02/17/2015 12:13 PM, Nick Boldt wrote:
>>>>> In the jbds download-cache we have about 6G of runtime zips/jars.
>>>>>
>>>>> Are all of these runtimes still used for testing? Are there any I
>>>>> can
>>>>> delete?
>>>>>
>>>>> apache-tomcat-6.0.41.zip
>>>>> apache-tomcat-7.0.56.zip
>>>>> db2jcc4.jar
>>>>> GateIn-3.4.0.Final-jbossas5.zip
>>>>> GateIn-3.5.0.Final-jbossas7.zip
>>>>> h2-1.4.178.jar
>>>>> hsqldb-2.2.9.zip
>>>>> IzPack-install-4.3.5.jar
>>>>> jbds-seamfp-patch.zip
>>>>> jboss-3.2.8.SP1.zip
>>>>> jboss-4.0.5.GA.zip
>>>>> jboss-4.2.3.GA-jdk6.zip
>>>>> jboss-5.0.1.GA-jdk6.zip
>>>>> jboss-5.0.1.GA.zip
>>>>> jboss-5.1.0.GA-jdk6.zip
>>>>> jboss-5.1.0.GA.zip
>>>>> jboss-as-7.0.2.Final.zip
>>>>> jboss-as-7.1.1.Final.zip
>>>>> jboss-as-distribution-6.1.0.Final.zip
>>>>> jboss-eap-4.3.0.GA_CP10.zip
>>>>> jboss-eap-5.1.2.zip
>>>>> jboss-eap-6.0.1.zip
>>>>> jboss-eap-6.1.2.zip
>>>>> jboss-eap-6.2.0.zip
>>>>> jboss-eap-6.2.4-full-build.zip
>>>>> jboss-eap-6.2.x-patched.zip
>>>>> jboss-eap-6.3.0.zip
>>>>> jboss-eap-6.3.x-patched.zip
>>>>> jboss-eap-fp-4.3.0.CP03-FP01.zip
>>>>> jboss-eap-noauth-4.3.0.GA_CP03.zip
>>>>> jboss-eap-noauth-5.2.0.zip
>>>>> jboss-portal-2.7.2-bundled.zip
>>>>> JBossPortletBridge-2.3.1.Final.zip
>>>>> jboss-seam-2.0.1.GA.zip
>>>>> jboss-seam-2.0.2.SP1.zip
>>>>> jboss-seam-2.0.3.CR1.zip
>>>>> jboss-seam-2.1.1.GA.zip
>>>>> jboss-seam-2.1.2.zip
>>>>> jboss-seam-2.2.0.CR1.zip
>>>>> jboss-seam-2.2.0.GA.zip
>>>>> jboss-seam-2.2.1.Final.zip
>>>>> jboss-seam-2.2.2.Final.zip
>>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>> jconn4-26666.jar
>>>>> mockito-1.9.5.zip
>>>>> mysql-connector-java-5.1.21-bin.jar
>>>>> ojdbc6.jar
>>>>> poi-src-2.5.1-final-20040804.zip
>>>>> postgresql-9.1-902.jdbc4.jar
>>>>> rhds-seam-gen-patch.zip
>>>>> saxonhe9-2-1-5j.zip
>>>>> soa-4.3.0.GA_CP05.zip
>>>>> sqljdbc4.jar
>>>>> wildfly-8.0.0.Final.zip
>>>>> wildfly-8.1.0.Final.zip
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>> /max
>> http://about.me/maxandersen
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com


/max
http://about.me/maxandersen


From rstryker at redhat.com  Fri Feb 20 10:44:33 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Fri, 20 Feb 2015 23:44:33 +0800
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <54E74AA0.9010307@redhat.com>
References: <54E3A0D9.4060806@redhat.com>
	<54E3A9B7.9060008@exadel.com>	<4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>	<7EA1E254-7F4F-40DA-85B7-17A9CBC01853@redhat.com>	<54E747F8.1090907@redhat.com>	<C715ACCE-E613-4EF0-8017-66B1E1CE8C91@redhat.com>
	<54E74AA0.9010307@redhat.com>
Message-ID: <54E75661.7050906@redhat.com>

On 02/20/2015 10:54 PM, Nick Boldt wrote:
> But isn't that only for PRIVATE requirements? That is, things like EAP,
> but not WildFly?
>
> Last night jbosstools-server_4.2.luna was failing to fetch *any* of its
> missing runtimes, be it EAP or WFLY.
>
> Is that a bug?

I would asume that is a bug in the jenkins job in some fashion, yes.

>
> On 02/20/2015 09:52 AM, Max Rydahl Andersen wrote:
>> On 20 Feb 2015, at 15:43, Nick Boldt wrote:
>>
>>> As we discovered last night w/ the jbostools-server builds, the mojo
>>> to fetch requirements/dependencies/runtimes is no longer working in
>>> Jenkins. Works fine on local, but won't fetch in Jenkins.
>>>
>>> Maybe something to do with skipPrivateRequirements?
>>
>> yes, skipPrivateRequirements should be false for it to work.
>>> Or a bug in latest Maven? I use 3.1.1 here, but Jenkins uses 3.2.5 for
>>> the 9.0/master jobs.
>>>
>>> On 02/20/2015 06:25 AM, Max Rydahl Andersen wrote:
>>>> On 20 Feb 2015, at 5:06, Fred Bricon wrote:
>>>>
>>>>> Err... removing jboss-seam-2.0.1.GA.zip broke
>>>>> jbosstools-central_master :
>>>>> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console
>>>>>
>>>>> <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console>
>>>>>
>>>>>
>>>>> Can you rollback pretty please?
>>>>
>>>> eh...this location is supposed to work as a *cache* right?
>>>>
>>>> so why wasn't the build fetching the bits to fill up the cache ?
>>>>
>>>> /max
>>>>
>>>>>> Le 17 f?vr. 2015 ? 15:51, Alexey Kazakov <akazakov at exadel.com> a
>>>>>> ?crit :
>>>>>>
>>>>>> We can remove the following:
>>>>>> jboss-seam-2.0.1.GA.zip
>>>>>> jboss-seam-2.0.2.SP1.zip
>>>>>> jboss-seam-2.0.3.CR1.zip
>>>>>> jboss-seam-2.1.1.GA.zip
>>>>>> jboss-seam-2.2.0.CR1.zip
>>>>>> jboss-seam-2.2.0.GA.zip
>>>>>> jboss-seam-2.2.2.Final.zip
>>>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>>>
>>>>>> And we still test:
>>>>>> jboss-seam-2.1.2.zip
>>>>>> jboss-seam-2.2.1.Final.zip
>>>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>>>
>>>>>> On 02/17/2015 12:13 PM, Nick Boldt wrote:
>>>>>>> In the jbds download-cache we have about 6G of runtime zips/jars.
>>>>>>>
>>>>>>> Are all of these runtimes still used for testing? Are there any I
>>>>>>> can
>>>>>>> delete?
>>>>>>>
>>>>>>> apache-tomcat-6.0.41.zip
>>>>>>> apache-tomcat-7.0.56.zip
>>>>>>> db2jcc4.jar
>>>>>>> GateIn-3.4.0.Final-jbossas5.zip
>>>>>>> GateIn-3.5.0.Final-jbossas7.zip
>>>>>>> h2-1.4.178.jar
>>>>>>> hsqldb-2.2.9.zip
>>>>>>> IzPack-install-4.3.5.jar
>>>>>>> jbds-seamfp-patch.zip
>>>>>>> jboss-3.2.8.SP1.zip
>>>>>>> jboss-4.0.5.GA.zip
>>>>>>> jboss-4.2.3.GA-jdk6.zip
>>>>>>> jboss-5.0.1.GA-jdk6.zip
>>>>>>> jboss-5.0.1.GA.zip
>>>>>>> jboss-5.1.0.GA-jdk6.zip
>>>>>>> jboss-5.1.0.GA.zip
>>>>>>> jboss-as-7.0.2.Final.zip
>>>>>>> jboss-as-7.1.1.Final.zip
>>>>>>> jboss-as-distribution-6.1.0.Final.zip
>>>>>>> jboss-eap-4.3.0.GA_CP10.zip
>>>>>>> jboss-eap-5.1.2.zip
>>>>>>> jboss-eap-6.0.1.zip
>>>>>>> jboss-eap-6.1.2.zip
>>>>>>> jboss-eap-6.2.0.zip
>>>>>>> jboss-eap-6.2.4-full-build.zip
>>>>>>> jboss-eap-6.2.x-patched.zip
>>>>>>> jboss-eap-6.3.0.zip
>>>>>>> jboss-eap-6.3.x-patched.zip
>>>>>>> jboss-eap-fp-4.3.0.CP03-FP01.zip
>>>>>>> jboss-eap-noauth-4.3.0.GA_CP03.zip
>>>>>>> jboss-eap-noauth-5.2.0.zip
>>>>>>> jboss-portal-2.7.2-bundled.zip
>>>>>>> JBossPortletBridge-2.3.1.Final.zip
>>>>>>> jboss-seam-2.0.1.GA.zip
>>>>>>> jboss-seam-2.0.2.SP1.zip
>>>>>>> jboss-seam-2.0.3.CR1.zip
>>>>>>> jboss-seam-2.1.1.GA.zip
>>>>>>> jboss-seam-2.1.2.zip
>>>>>>> jboss-seam-2.2.0.CR1.zip
>>>>>>> jboss-seam-2.2.0.GA.zip
>>>>>>> jboss-seam-2.2.1.Final.zip
>>>>>>> jboss-seam-2.2.2.Final.zip
>>>>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>>>> jconn4-26666.jar
>>>>>>> mockito-1.9.5.zip
>>>>>>> mysql-connector-java-5.1.21-bin.jar
>>>>>>> ojdbc6.jar
>>>>>>> poi-src-2.5.1-final-20040804.zip
>>>>>>> postgresql-9.1-902.jdbc4.jar
>>>>>>> rhds-seam-gen-patch.zip
>>>>>>> saxonhe9-2-1-5j.zip
>>>>>>> soa-4.3.0.GA_CP05.zip
>>>>>>> sqljdbc4.jar
>>>>>>> wildfly-8.0.0.Final.zip
>>>>>>> wildfly-8.1.0.Final.zip
>>>>>>> _______________________________________________
>>>>>>> jbosstools-dev mailing list
>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>> --
>>> Nick Boldt :: JBoss by Red Hat
>>> Productization Lead :: JBoss Tools & Dev Studio
>>> http://nick.divbyzero.com
>>
>> /max
>> http://about.me/maxandersen


From nboldt at redhat.com  Fri Feb 20 10:51:19 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 20 Feb 2015 10:51:19 -0500
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <54E75661.7050906@redhat.com>
References: <54E3A0D9.4060806@redhat.com>	<54E3A9B7.9060008@exadel.com>	<4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>	<7EA1E254-7F4F-40DA-85B7-17A9CBC01853@redhat.com>	<54E747F8.1090907@redhat.com>	<C715ACCE-E613-4EF0-8017-66B1E1CE8C91@redhat.com>	<54E74AA0.9010307@redhat.com>
	<54E75661.7050906@redhat.com>
Message-ID: <54E757F7.8050207@redhat.com>

I should have been more clear. Mea cupla.

Should skipPrivateRequirements=true prevent the download of ANY 
requirements, be they from engineering.redhat (private) or 
www.jboss.org, apache.org, etc. (public) ?

Seems to me that either the variable is misnamed (should be 
skipDownloadOfRequirements) or else it should be repurposed to ONLY 
prevent private downloads.

What was the purpose of this boolean? To prevent ALL downloads? Or just 
to allow builds to work when not behind VPN?

N

On 02/20/2015 10:44 AM, Rob Stryker wrote:
> On 02/20/2015 10:54 PM, Nick Boldt wrote:
>> But isn't that only for PRIVATE requirements? That is, things like EAP,
>> but not WildFly?
>>
>> Last night jbosstools-server_4.2.luna was failing to fetch *any* of its
>> missing runtimes, be it EAP or WFLY.
>>
>> Is that a bug?
>
> I would asume that is a bug in the jenkins job in some fashion, yes.
>
>>
>> On 02/20/2015 09:52 AM, Max Rydahl Andersen wrote:
>>> On 20 Feb 2015, at 15:43, Nick Boldt wrote:
>>>
>>>> As we discovered last night w/ the jbostools-server builds, the mojo
>>>> to fetch requirements/dependencies/runtimes is no longer working in
>>>> Jenkins. Works fine on local, but won't fetch in Jenkins.
>>>>
>>>> Maybe something to do with skipPrivateRequirements?
>>>
>>> yes, skipPrivateRequirements should be false for it to work.
>>>> Or a bug in latest Maven? I use 3.1.1 here, but Jenkins uses 3.2.5 for
>>>> the 9.0/master jobs.
>>>>
>>>> On 02/20/2015 06:25 AM, Max Rydahl Andersen wrote:
>>>>> On 20 Feb 2015, at 5:06, Fred Bricon wrote:
>>>>>
>>>>>> Err... removing jboss-seam-2.0.1.GA.zip broke
>>>>>> jbosstools-central_master :
>>>>>> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console
>>>>>>
>>>>>> <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console>
>>>>>>
>>>>>>
>>>>>> Can you rollback pretty please?
>>>>>
>>>>> eh...this location is supposed to work as a *cache* right?
>>>>>
>>>>> so why wasn't the build fetching the bits to fill up the cache ?
>>>>>
>>>>> /max
>>>>>
>>>>>>> Le 17 f?vr. 2015 ? 15:51, Alexey Kazakov <akazakov at exadel.com> a
>>>>>>> ?crit :
>>>>>>>
>>>>>>> We can remove the following:
>>>>>>> jboss-seam-2.0.1.GA.zip
>>>>>>> jboss-seam-2.0.2.SP1.zip
>>>>>>> jboss-seam-2.0.3.CR1.zip
>>>>>>> jboss-seam-2.1.1.GA.zip
>>>>>>> jboss-seam-2.2.0.CR1.zip
>>>>>>> jboss-seam-2.2.0.GA.zip
>>>>>>> jboss-seam-2.2.2.Final.zip
>>>>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>>>>
>>>>>>> And we still test:
>>>>>>> jboss-seam-2.1.2.zip
>>>>>>> jboss-seam-2.2.1.Final.zip
>>>>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>>>>
>>>>>>> On 02/17/2015 12:13 PM, Nick Boldt wrote:
>>>>>>>> In the jbds download-cache we have about 6G of runtime zips/jars.
>>>>>>>>
>>>>>>>> Are all of these runtimes still used for testing? Are there any I
>>>>>>>> can
>>>>>>>> delete?
>>>>>>>>
>>>>>>>> apache-tomcat-6.0.41.zip
>>>>>>>> apache-tomcat-7.0.56.zip
>>>>>>>> db2jcc4.jar
>>>>>>>> GateIn-3.4.0.Final-jbossas5.zip
>>>>>>>> GateIn-3.5.0.Final-jbossas7.zip
>>>>>>>> h2-1.4.178.jar
>>>>>>>> hsqldb-2.2.9.zip
>>>>>>>> IzPack-install-4.3.5.jar
>>>>>>>> jbds-seamfp-patch.zip
>>>>>>>> jboss-3.2.8.SP1.zip
>>>>>>>> jboss-4.0.5.GA.zip
>>>>>>>> jboss-4.2.3.GA-jdk6.zip
>>>>>>>> jboss-5.0.1.GA-jdk6.zip
>>>>>>>> jboss-5.0.1.GA.zip
>>>>>>>> jboss-5.1.0.GA-jdk6.zip
>>>>>>>> jboss-5.1.0.GA.zip
>>>>>>>> jboss-as-7.0.2.Final.zip
>>>>>>>> jboss-as-7.1.1.Final.zip
>>>>>>>> jboss-as-distribution-6.1.0.Final.zip
>>>>>>>> jboss-eap-4.3.0.GA_CP10.zip
>>>>>>>> jboss-eap-5.1.2.zip
>>>>>>>> jboss-eap-6.0.1.zip
>>>>>>>> jboss-eap-6.1.2.zip
>>>>>>>> jboss-eap-6.2.0.zip
>>>>>>>> jboss-eap-6.2.4-full-build.zip
>>>>>>>> jboss-eap-6.2.x-patched.zip
>>>>>>>> jboss-eap-6.3.0.zip
>>>>>>>> jboss-eap-6.3.x-patched.zip
>>>>>>>> jboss-eap-fp-4.3.0.CP03-FP01.zip
>>>>>>>> jboss-eap-noauth-4.3.0.GA_CP03.zip
>>>>>>>> jboss-eap-noauth-5.2.0.zip
>>>>>>>> jboss-portal-2.7.2-bundled.zip
>>>>>>>> JBossPortletBridge-2.3.1.Final.zip
>>>>>>>> jboss-seam-2.0.1.GA.zip
>>>>>>>> jboss-seam-2.0.2.SP1.zip
>>>>>>>> jboss-seam-2.0.3.CR1.zip
>>>>>>>> jboss-seam-2.1.1.GA.zip
>>>>>>>> jboss-seam-2.1.2.zip
>>>>>>>> jboss-seam-2.2.0.CR1.zip
>>>>>>>> jboss-seam-2.2.0.GA.zip
>>>>>>>> jboss-seam-2.2.1.Final.zip
>>>>>>>> jboss-seam-2.2.2.Final.zip
>>>>>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>>>>> jconn4-26666.jar
>>>>>>>> mockito-1.9.5.zip
>>>>>>>> mysql-connector-java-5.1.21-bin.jar
>>>>>>>> ojdbc6.jar
>>>>>>>> poi-src-2.5.1-final-20040804.zip
>>>>>>>> postgresql-9.1-902.jdbc4.jar
>>>>>>>> rhds-seam-gen-patch.zip
>>>>>>>> saxonhe9-2-1-5j.zip
>>>>>>>> soa-4.3.0.GA_CP05.zip
>>>>>>>> sqljdbc4.jar
>>>>>>>> wildfly-8.0.0.Final.zip
>>>>>>>> wildfly-8.1.0.Final.zip
>>>>>>>> _______________________________________________
>>>>>>>> jbosstools-dev mailing list
>>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>>> _______________________________________________
>>>>>>> jbosstools-dev mailing list
>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>
>>>>> /max
>>>>> http://about.me/maxandersen
>>>>>
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>
>>>> --
>>>> Nick Boldt :: JBoss by Red Hat
>>>> Productization Lead :: JBoss Tools & Dev Studio
>>>> http://nick.divbyzero.com
>>>
>>> /max
>>> http://about.me/maxandersen
>
> _______________________________________________
> 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  Fri Feb 20 11:27:01 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 20 Feb 2015 11:27:01 -0500
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <54E75661.7050906@redhat.com>
References: <54E3A0D9.4060806@redhat.com>	<54E3A9B7.9060008@exadel.com>	<4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>	<7EA1E254-7F4F-40DA-85B7-17A9CBC01853@redhat.com>	<54E747F8.1090907@redhat.com>	<C715ACCE-E613-4EF0-8017-66B1E1CE8C91@redhat.com>	<54E74AA0.9010307@redhat.com>
	<54E75661.7050906@redhat.com>
Message-ID: <54E76055.9020308@redhat.com>

Did some more digging and there's definitely a glitch here.

Opened https://issues.jboss.org/browse/JBIDE-19343

On 02/20/2015 10:44 AM, Rob Stryker wrote:
> On 02/20/2015 10:54 PM, Nick Boldt wrote:
>> But isn't that only for PRIVATE requirements? That is, things like EAP,
>> but not WildFly?
>>
>> Last night jbosstools-server_4.2.luna was failing to fetch *any* of its
>> missing runtimes, be it EAP or WFLY.
>>
>> Is that a bug?
>
> I would asume that is a bug in the jenkins job in some fashion, yes.
>
>>
>> On 02/20/2015 09:52 AM, Max Rydahl Andersen wrote:
>>> On 20 Feb 2015, at 15:43, Nick Boldt wrote:
>>>
>>>> As we discovered last night w/ the jbostools-server builds, the mojo
>>>> to fetch requirements/dependencies/runtimes is no longer working in
>>>> Jenkins. Works fine on local, but won't fetch in Jenkins.
>>>>
>>>> Maybe something to do with skipPrivateRequirements?
>>>
>>> yes, skipPrivateRequirements should be false for it to work.
>>>> Or a bug in latest Maven? I use 3.1.1 here, but Jenkins uses 3.2.5 for
>>>> the 9.0/master jobs.
>>>>
>>>> On 02/20/2015 06:25 AM, Max Rydahl Andersen wrote:
>>>>> On 20 Feb 2015, at 5:06, Fred Bricon wrote:
>>>>>
>>>>>> Err... removing jboss-seam-2.0.1.GA.zip broke
>>>>>> jbosstools-central_master :
>>>>>> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console
>>>>>>
>>>>>> <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console>
>>>>>>
>>>>>>
>>>>>> Can you rollback pretty please?
>>>>>
>>>>> eh...this location is supposed to work as a *cache* right?
>>>>>
>>>>> so why wasn't the build fetching the bits to fill up the cache ?
>>>>>
>>>>> /max
>>>>>
>>>>>>> Le 17 f?vr. 2015 ? 15:51, Alexey Kazakov <akazakov at exadel.com> a
>>>>>>> ?crit :
>>>>>>>
>>>>>>> We can remove the following:
>>>>>>> jboss-seam-2.0.1.GA.zip
>>>>>>> jboss-seam-2.0.2.SP1.zip
>>>>>>> jboss-seam-2.0.3.CR1.zip
>>>>>>> jboss-seam-2.1.1.GA.zip
>>>>>>> jboss-seam-2.2.0.CR1.zip
>>>>>>> jboss-seam-2.2.0.GA.zip
>>>>>>> jboss-seam-2.2.2.Final.zip
>>>>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>>>>
>>>>>>> And we still test:
>>>>>>> jboss-seam-2.1.2.zip
>>>>>>> jboss-seam-2.2.1.Final.zip
>>>>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>>>>
>>>>>>> On 02/17/2015 12:13 PM, Nick Boldt wrote:
>>>>>>>> In the jbds download-cache we have about 6G of runtime zips/jars.
>>>>>>>>
>>>>>>>> Are all of these runtimes still used for testing? Are there any I
>>>>>>>> can
>>>>>>>> delete?
>>>>>>>>
>>>>>>>> apache-tomcat-6.0.41.zip
>>>>>>>> apache-tomcat-7.0.56.zip
>>>>>>>> db2jcc4.jar
>>>>>>>> GateIn-3.4.0.Final-jbossas5.zip
>>>>>>>> GateIn-3.5.0.Final-jbossas7.zip
>>>>>>>> h2-1.4.178.jar
>>>>>>>> hsqldb-2.2.9.zip
>>>>>>>> IzPack-install-4.3.5.jar
>>>>>>>> jbds-seamfp-patch.zip
>>>>>>>> jboss-3.2.8.SP1.zip
>>>>>>>> jboss-4.0.5.GA.zip
>>>>>>>> jboss-4.2.3.GA-jdk6.zip
>>>>>>>> jboss-5.0.1.GA-jdk6.zip
>>>>>>>> jboss-5.0.1.GA.zip
>>>>>>>> jboss-5.1.0.GA-jdk6.zip
>>>>>>>> jboss-5.1.0.GA.zip
>>>>>>>> jboss-as-7.0.2.Final.zip
>>>>>>>> jboss-as-7.1.1.Final.zip
>>>>>>>> jboss-as-distribution-6.1.0.Final.zip
>>>>>>>> jboss-eap-4.3.0.GA_CP10.zip
>>>>>>>> jboss-eap-5.1.2.zip
>>>>>>>> jboss-eap-6.0.1.zip
>>>>>>>> jboss-eap-6.1.2.zip
>>>>>>>> jboss-eap-6.2.0.zip
>>>>>>>> jboss-eap-6.2.4-full-build.zip
>>>>>>>> jboss-eap-6.2.x-patched.zip
>>>>>>>> jboss-eap-6.3.0.zip
>>>>>>>> jboss-eap-6.3.x-patched.zip
>>>>>>>> jboss-eap-fp-4.3.0.CP03-FP01.zip
>>>>>>>> jboss-eap-noauth-4.3.0.GA_CP03.zip
>>>>>>>> jboss-eap-noauth-5.2.0.zip
>>>>>>>> jboss-portal-2.7.2-bundled.zip
>>>>>>>> JBossPortletBridge-2.3.1.Final.zip
>>>>>>>> jboss-seam-2.0.1.GA.zip
>>>>>>>> jboss-seam-2.0.2.SP1.zip
>>>>>>>> jboss-seam-2.0.3.CR1.zip
>>>>>>>> jboss-seam-2.1.1.GA.zip
>>>>>>>> jboss-seam-2.1.2.zip
>>>>>>>> jboss-seam-2.2.0.CR1.zip
>>>>>>>> jboss-seam-2.2.0.GA.zip
>>>>>>>> jboss-seam-2.2.1.Final.zip
>>>>>>>> jboss-seam-2.2.2.Final.zip
>>>>>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>>>>> jconn4-26666.jar
>>>>>>>> mockito-1.9.5.zip
>>>>>>>> mysql-connector-java-5.1.21-bin.jar
>>>>>>>> ojdbc6.jar
>>>>>>>> poi-src-2.5.1-final-20040804.zip
>>>>>>>> postgresql-9.1-902.jdbc4.jar
>>>>>>>> rhds-seam-gen-patch.zip
>>>>>>>> saxonhe9-2-1-5j.zip
>>>>>>>> soa-4.3.0.GA_CP05.zip
>>>>>>>> sqljdbc4.jar
>>>>>>>> wildfly-8.0.0.Final.zip
>>>>>>>> wildfly-8.1.0.Final.zip
>>>>>>>> _______________________________________________
>>>>>>>> jbosstools-dev mailing list
>>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>>> _______________________________________________
>>>>>>> jbosstools-dev mailing list
>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>
>>>>> /max
>>>>> http://about.me/maxandersen
>>>>>
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>
>>>> --
>>>> Nick Boldt :: JBoss by Red Hat
>>>> Productization Lead :: JBoss Tools & Dev Studio
>>>> http://nick.divbyzero.com
>>>
>>> /max
>>> http://about.me/maxandersen
>
> _______________________________________________
> 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 Feb 20 09:52:38 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 20 Feb 2015 15:52:38 +0100
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <54E747F8.1090907@redhat.com>
References: <54E3A0D9.4060806@redhat.com> <54E3A9B7.9060008@exadel.com>
	<4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>
	<7EA1E254-7F4F-40DA-85B7-17A9CBC01853@redhat.com>
	<54E747F8.1090907@redhat.com>
Message-ID: <C715ACCE-E613-4EF0-8017-66B1E1CE8C91@redhat.com>

On 20 Feb 2015, at 15:43, Nick Boldt wrote:

> As we discovered last night w/ the jbostools-server builds, the mojo 
> to fetch requirements/dependencies/runtimes is no longer working in 
> Jenkins. Works fine on local, but won't fetch in Jenkins.
>
> Maybe something to do with skipPrivateRequirements?


yes, skipPrivateRequirements should be false for it to work.
>
> Or a bug in latest Maven? I use 3.1.1 here, but Jenkins uses 3.2.5 for 
> the 9.0/master jobs.
>
> On 02/20/2015 06:25 AM, Max Rydahl Andersen wrote:
>> On 20 Feb 2015, at 5:06, Fred Bricon wrote:
>>
>>> Err... removing jboss-seam-2.0.1.GA.zip broke
>>> jbosstools-central_master :
>>> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console
>>> <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console>
>>>
>>> Can you rollback pretty please?
>>
>>
>> eh...this location is supposed to work as a *cache* right?
>>
>> so why wasn't the build fetching the bits to fill up the cache ?
>>
>> /max
>>
>>>> Le 17 f?vr. 2015 ? 15:51, Alexey Kazakov <akazakov at exadel.com> a
>>>> ?crit :
>>>>
>>>> We can remove the following:
>>>> jboss-seam-2.0.1.GA.zip
>>>> jboss-seam-2.0.2.SP1.zip
>>>> jboss-seam-2.0.3.CR1.zip
>>>> jboss-seam-2.1.1.GA.zip
>>>> jboss-seam-2.2.0.CR1.zip
>>>> jboss-seam-2.2.0.GA.zip
>>>> jboss-seam-2.2.2.Final.zip
>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>
>>>> And we still test:
>>>> jboss-seam-2.1.2.zip
>>>> jboss-seam-2.2.1.Final.zip
>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>
>>>> On 02/17/2015 12:13 PM, Nick Boldt wrote:
>>>>> In the jbds download-cache we have about 6G of runtime zips/jars.
>>>>>
>>>>> Are all of these runtimes still used for testing? Are there any I
>>>>> can
>>>>> delete?
>>>>>
>>>>> apache-tomcat-6.0.41.zip
>>>>> apache-tomcat-7.0.56.zip
>>>>> db2jcc4.jar
>>>>> GateIn-3.4.0.Final-jbossas5.zip
>>>>> GateIn-3.5.0.Final-jbossas7.zip
>>>>> h2-1.4.178.jar
>>>>> hsqldb-2.2.9.zip
>>>>> IzPack-install-4.3.5.jar
>>>>> jbds-seamfp-patch.zip
>>>>> jboss-3.2.8.SP1.zip
>>>>> jboss-4.0.5.GA.zip
>>>>> jboss-4.2.3.GA-jdk6.zip
>>>>> jboss-5.0.1.GA-jdk6.zip
>>>>> jboss-5.0.1.GA.zip
>>>>> jboss-5.1.0.GA-jdk6.zip
>>>>> jboss-5.1.0.GA.zip
>>>>> jboss-as-7.0.2.Final.zip
>>>>> jboss-as-7.1.1.Final.zip
>>>>> jboss-as-distribution-6.1.0.Final.zip
>>>>> jboss-eap-4.3.0.GA_CP10.zip
>>>>> jboss-eap-5.1.2.zip
>>>>> jboss-eap-6.0.1.zip
>>>>> jboss-eap-6.1.2.zip
>>>>> jboss-eap-6.2.0.zip
>>>>> jboss-eap-6.2.4-full-build.zip
>>>>> jboss-eap-6.2.x-patched.zip
>>>>> jboss-eap-6.3.0.zip
>>>>> jboss-eap-6.3.x-patched.zip
>>>>> jboss-eap-fp-4.3.0.CP03-FP01.zip
>>>>> jboss-eap-noauth-4.3.0.GA_CP03.zip
>>>>> jboss-eap-noauth-5.2.0.zip
>>>>> jboss-portal-2.7.2-bundled.zip
>>>>> JBossPortletBridge-2.3.1.Final.zip
>>>>> jboss-seam-2.0.1.GA.zip
>>>>> jboss-seam-2.0.2.SP1.zip
>>>>> jboss-seam-2.0.3.CR1.zip
>>>>> jboss-seam-2.1.1.GA.zip
>>>>> jboss-seam-2.1.2.zip
>>>>> jboss-seam-2.2.0.CR1.zip
>>>>> jboss-seam-2.2.0.GA.zip
>>>>> jboss-seam-2.2.1.Final.zip
>>>>> jboss-seam-2.2.2.Final.zip
>>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>>> jconn4-26666.jar
>>>>> mockito-1.9.5.zip
>>>>> mysql-connector-java-5.1.21-bin.jar
>>>>> ojdbc6.jar
>>>>> poi-src-2.5.1-final-20040804.zip
>>>>> postgresql-9.1-902.jdbc4.jar
>>>>> rhds-seam-gen-patch.zip
>>>>> saxonhe9-2-1-5j.zip
>>>>> soa-4.3.0.GA_CP05.zip
>>>>> sqljdbc4.jar
>>>>> wildfly-8.0.0.Final.zip
>>>>> wildfly-8.1.0.Final.zip
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>> /max
>> http://about.me/maxandersen
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com


/max
http://about.me/maxandersen


From nickboldt at gmail.com  Fri Feb 20 17:42:38 2015
From: nickboldt at gmail.com (Nick Boldt)
Date: Fri, 20 Feb 2015 17:42:38 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha1x -> tag
 jbosstools-4.3.0.Alpha1 ]
Message-ID: <54E7B85E.2040108@gmail.com>

Component leads, please tag your repositories!

$ git fetch jbosstools jbosstools-4.3.0.Alpha1x #assuming remote is 
called jbosstools, also often called origin
$ git tag jbosstools-4.3.0.Alpha1 FETCH_HEAD
$ git push jbosstools jbosstools-4.3.0.Alpha1


-- 
Nick Boldt :: http://nick.divbyzero.com

From nboldt at redhat.com  Fri Feb 20 18:23:08 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 20 Feb 2015 18:23:08 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 12 JIRAs unresolved for
	fixversion = 4.3.0.Alpha1
Message-ID: <54E7C1DC.9040305@redhat.com>

There are 12 unresolved issues with a fixversion of 4.3.0.Alpha1 left in 
JIRA [1].

Please resolve them or slip them to another milestone, as appropriate.

[1] 
https://issues.jboss.org/issues/?jql=%28project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%2212325152%22%29%20or%20%28project%20%3D%20JBDS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%2212325151%22%29

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

From akazakov at exadel.com  Fri Feb 20 19:15:30 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Fri, 20 Feb 2015 16:15:30 -0800
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha1x -> tag
 jbosstools-4.3.0.Alpha1 ]
In-Reply-To: <54E7B85E.2040108@gmail.com>
References: <54E7B85E.2040108@gmail.com>
Message-ID: <54E7CE22.7030304@exadel.com>

Done for base, jst, javaee, arquillian.

On 02/20/2015 02:42 PM, Nick Boldt wrote:
> Component leads, please tag your repositories!
>
> $ git fetch jbosstools jbosstools-4.3.0.Alpha1x #assuming remote is
> called jbosstools, also often called origin
> $ git tag jbosstools-4.3.0.Alpha1 FETCH_HEAD
> $ git push jbosstools jbosstools-4.3.0.Alpha1
>
>


From akazakov at exadel.com  Fri Feb 20 19:25:13 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Fri, 20 Feb 2015 16:25:13 -0800
Subject: [jbosstools-dev] Runtimes for testing
In-Reply-To: <54E748C3.1040709@redhat.com>
References: <54E3A0D9.4060806@redhat.com> <54E3A9B7.9060008@exadel.com>
	<4EF31E4E-FE6B-4A2F-B942-0158A177B363@redhat.com>
	<54E748C3.1040709@redhat.com>
Message-ID: <54E7D069.8080002@exadel.com>


Here is the list of the needed runtimes by Seam tests: 
https://github.com/jbosstools/jbosstools-javaee/tree/master/seam/tests
I don't see any Seam 2.0.2, 2.0.3 usage in Seam tests but we do need 
2.0.1 (sorry I didn't notice that 2.0.1 is used by seam.detector.test) 
and 2.3.0.Final.

On 02/20/2015 06:46 AM, Nick Boldt wrote:
> Just tried to roll it back and discovered the file was already there:
>
> NEW ones:
>
> -rw-rw-r-- 1 hudson hudson  93M Feb 20 00:08 jboss-seam-2.0.1.GA.zip
> -rw-rw-r-- 1 hudson hudson 106M Feb 20 00:08 jboss-seam-2.1.1.GA.zip
> -rw-rw-r-- 1 hudson hudson 112M Feb 20 00:12 jboss-seam-2.2.0.GA.zip
>
> OLD ones:
>
> -rw-rw-r-- 1 hudson hudson  93M Feb 26  2013 jboss-seam-2.0.1.GA.zip
> -rw-rw-r-- 1 hudson hudson 106M Feb 27  2013 jboss-seam-2.1.1.GA.zip
> -rw-rw-r-- 1 hudson hudson 112M Jun  3  2013 jboss-seam-2.2.0.GA.zip
>
> Guess you don't need Seam 2.0.2, 2.0.3, 2.2.2 or 2.3?
>
> On 02/19/2015 11:06 PM, Fred Bricon wrote:
>> Err... removing jboss-seam-2.0.1.GA.zip broke jbosstools-central_master
>> :http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_master/639/console 
>>
>>
>> Can yourollback pretty please?
>>
>>> Le 17 f?vr. 2015 ? 15:51, Alexey Kazakov <akazakov at exadel.com
>>> <mailto:akazakov at exadel.com>> a ?crit :
>>>
>>> We can remove the following:
>>> jboss-seam-2.0.1.GA.zip
>>> jboss-seam-2.0.2.SP1.zip
>>> jboss-seam-2.0.3.CR1.zip
>>> jboss-seam-2.1.1.GA.zip
>>> jboss-seam-2.2.0.CR1.zip
>>> jboss-seam-2.2.0.GA.zip
>>> jboss-seam-2.2.2.Final.zip
>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>
>>> And we still test:
>>> jboss-seam-2.1.2.zip
>>> jboss-seam-2.2.1.Final.zip
>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>
>>> On 02/17/2015 12:13 PM, Nick Boldt wrote:
>>>> In the jbds download-cache we have about 6G of runtime zips/jars.
>>>>
>>>> Are all of these runtimes still used for testing? Are there any I can
>>>> delete?
>>>>
>>>> apache-tomcat-6.0.41.zip
>>>> apache-tomcat-7.0.56.zip
>>>> db2jcc4.jar
>>>> GateIn-3.4.0.Final-jbossas5.zip
>>>> GateIn-3.5.0.Final-jbossas7.zip
>>>> h2-1.4.178.jar
>>>> hsqldb-2.2.9.zip
>>>> IzPack-install-4.3.5.jar
>>>> jbds-seamfp-patch.zip
>>>> jboss-3.2.8.SP1.zip
>>>> jboss-4.0.5.GA.zip
>>>> jboss-4.2.3.GA-jdk6.zip
>>>> jboss-5.0.1.GA-jdk6.zip
>>>> jboss-5.0.1.GA.zip
>>>> jboss-5.1.0.GA-jdk6.zip
>>>> jboss-5.1.0.GA.zip
>>>> jboss-as-7.0.2.Final.zip
>>>> jboss-as-7.1.1.Final.zip
>>>> jboss-as-distribution-6.1.0.Final.zip
>>>> jboss-eap-4.3.0.GA_CP10.zip
>>>> jboss-eap-5.1.2.zip
>>>> jboss-eap-6.0.1.zip
>>>> jboss-eap-6.1.2.zip
>>>> jboss-eap-6.2.0.zip
>>>> jboss-eap-6.2.4-full-build.zip
>>>> jboss-eap-6.2.x-patched.zip
>>>> jboss-eap-6.3.0.zip
>>>> jboss-eap-6.3.x-patched.zip
>>>> jboss-eap-fp-4.3.0.CP03-FP01.zip
>>>> jboss-eap-noauth-4.3.0.GA_CP03.zip
>>>> jboss-eap-noauth-5.2.0.zip
>>>> jboss-portal-2.7.2-bundled.zip
>>>> JBossPortletBridge-2.3.1.Final.zip
>>>> jboss-seam-2.0.1.GA.zip
>>>> jboss-seam-2.0.2.SP1.zip
>>>> jboss-seam-2.0.3.CR1.zip
>>>> jboss-seam-2.1.1.GA.zip
>>>> jboss-seam-2.1.2.zip
>>>> jboss-seam-2.2.0.CR1.zip
>>>> jboss-seam-2.2.0.GA.zip
>>>> jboss-seam-2.2.1.Final.zip
>>>> jboss-seam-2.2.2.Final.zip
>>>> jboss-seam-2.3.0.ALPHA-distribution.zip
>>>> jboss-seam-distribution-2.3.0.Final-dist.zip
>>>> jconn4-26666.jar
>>>> mockito-1.9.5.zip
>>>> mysql-connector-java-5.1.21-bin.jar
>>>> ojdbc6.jar
>>>> poi-src-2.5.1-final-20040804.zip
>>>> postgresql-9.1-902.jdbc4.jar
>>>> rhds-seam-gen-patch.zip
>>>> saxonhe9-2-1-5j.zip
>>>> soa-4.3.0.GA_CP05.zip
>>>> sqljdbc4.jar
>>>> wildfly-8.0.0.Final.zip
>>>> wildfly-8.1.0.Final.zip
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>

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

From manderse at redhat.com  Mon Feb 23 05:12:48 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 23 Feb 2015 11:12:48 +0100
Subject: [jbosstools-dev] The Results Are in! Re: survey - on git push
 notifications in irc
In-Reply-To: <66E5CC71-1FC0-40C5-AA84-DA3E37F23C55@redhat.com>
References: <66E5CC71-1FC0-40C5-AA84-DA3E37F23C55@redhat.com>
Message-ID: <AAD5EDF6-05EA-4A5F-8CED-B24C90F31894@redhat.com>

Heya,

Thanks for the 15 responses - the result is in. See details in attached 
PDF.

Here is what I read out of the results:

Majority likes the git push and PR notifications. So they are staying 
enabled.

So far so good, but we basically have a 1/3 split between staying in 1 
room,
don't care and split to multiple rooms.

There is also a mention on how to manually configure irc client to 
ignore jbossbot...
if that is necessary then it is a problem and jbossbot is doing more 
harm than good.

And looking at activity otherwise on 
http://transcripts.jboss.org/channel/irc.freenode.org/%23jbosstools/latest.stats.html
jbossbot is generating *alot* of content; and most is git push/PR 
messages.

Thus I would say the 1/3 split should fall to the suggestion of getting 
jbossbot PR notifications to
a separate room.

And looking at the question on wether we should have one room for all 
PR/pushes or
group them then the majority have spoken wishing for just a single room 
with a 53% win.

Thus i'm going to work on getting #jbosstools-dev setup for the PR 
commit/push notifications.

I'll let you know when ready.

/max

> Hey #jbosstools irc users,
>
> Seeing how much activity #jbosstools is getting from jbossbot from git
> notifications I'm
> considering routing them to a separate irc room.
>
> Please take 5 min to give your input here:
> https://docs.google.com/forms/d/1469WFn73ecpR1XGDQwr4VbCApL5pkwIYVWAj02dJQAg/viewform
>
> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ircresults.pdf
Type: application/pdf
Size: 99762 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150223/3dd6d778/attachment-0001.pdf 

From adietish at redhat.com  Mon Feb 23 08:53:50 2015
From: adietish at redhat.com (=?windows-1252?Q?Andr=E9_Dietisheim?=)
Date: Mon, 23 Feb 2015 14:53:50 +0100
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha1x -> tag
 jbosstools-4.3.0.Alpha1 ]
In-Reply-To: <54E7B85E.2040108@gmail.com>
References: <54E7B85E.2040108@gmail.com>
Message-ID: <54EB30EE.5070306@redhat.com>

done for openshift

On 02/20/2015 11:42 PM, Nick Boldt wrote:
> git push jbosstools jbosstools-4.3.0.Alpha1


From ggastald at redhat.com  Mon Feb 23 09:09:43 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Mon, 23 Feb 2015 11:09:43 -0300
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha1x -> tag
 jbosstools-4.3.0.Alpha1 ]
In-Reply-To: <54E7B85E.2040108@gmail.com>
References: <54E7B85E.2040108@gmail.com>
Message-ID: <54EB34A7.4040706@redhat.com>

Done for forge

On 02/20/2015 08:42 PM, Nick Boldt wrote:
> Component leads, please tag your repositories!
>
> $ git fetch jbosstools jbosstools-4.3.0.Alpha1x #assuming remote is
> called jbosstools, also often called origin
> $ git tag jbosstools-4.3.0.Alpha1 FETCH_HEAD
> $ git push jbosstools jbosstools-4.3.0.Alpha1
>
>


From ibuziuk at exadel.com  Mon Feb 23 09:35:16 2015
From: ibuziuk at exadel.com (Ilya Buziuk)
Date: Mon, 23 Feb 2015 17:35:16 +0300
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha1x -> tag
 jbosstools-4.3.0.Alpha1 ]
In-Reply-To: <54EB34A7.4040706@redhat.com>
References: <54E7B85E.2040108@gmail.com>
	<54EB34A7.4040706@redhat.com>
Message-ID: <CADOkA44+qubxsZOmvi+zFK44pF5f7GX8TZ=Pwg=OXe_bfTt2vw@mail.gmail.com>

done for browsersim and vpe

On Mon, Feb 23, 2015 at 5:09 PM, George Gastaldi <ggastald at redhat.com>
wrote:

> Done for forge
>
> On 02/20/2015 08:42 PM, Nick Boldt wrote:
> > Component leads, please tag your repositories!
> >
> > $ git fetch jbosstools jbosstools-4.3.0.Alpha1x #assuming remote is
> > called jbosstools, also often called origin
> > $ git tag jbosstools-4.3.0.Alpha1 FETCH_HEAD
> > $ git push jbosstools jbosstools-4.3.0.Alpha1
> >
> >
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
--
Best Regards,
Ilya Buziuk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150223/a1879875/attachment.html 

From gorkem.ercan at gmail.com  Mon Feb 23 10:51:35 2015
From: gorkem.ercan at gmail.com (Gorkem Ercan)
Date: Mon, 23 Feb 2015 10:51:35 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.3.0.Alpha1x -> tag
 jbosstools-4.3.0.Alpha1 ]
In-Reply-To: <CADOkA44+qubxsZOmvi+zFK44pF5f7GX8TZ=Pwg=OXe_bfTt2vw@mail.gmail.com>
References: <54E7B85E.2040108@gmail.com> <54EB34A7.4040706@redhat.com>
	<CADOkA44+qubxsZOmvi+zFK44pF5f7GX8TZ=Pwg=OXe_bfTt2vw@mail.gmail.com>
Message-ID: <145B8256-FCED-4C9A-941C-FE4DBE400C41@gmail.com>


And aerogear is done.

On 23 Feb 2015, at 9:35, Ilya Buziuk wrote:

> done for browsersim and vpe
>
> On Mon, Feb 23, 2015 at 5:09 PM, George Gastaldi <ggastald at redhat.com>
> wrote:
>
>> Done for forge
>>
>> On 02/20/2015 08:42 PM, Nick Boldt wrote:
>>> Component leads, please tag your repositories!
>>>
>>> $ git fetch jbosstools jbosstools-4.3.0.Alpha1x #assuming remote is
>>> called jbosstools, also often called origin
>>> $ git tag jbosstools-4.3.0.Alpha1 FETCH_HEAD
>>> $ git push jbosstools jbosstools-4.3.0.Alpha1
>>>
>>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
> --
> Best Regards,
> Ilya Buziuk
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

From nboldt at redhat.com  Mon Feb 23 11:42:41 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 23 Feb 2015 11:42:41 -0500
Subject: [jbosstools-dev] JBoss Tools 4.3.0.Alpha1 is now available
Message-ID: <54EB5881.3020306@redhat.com>

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

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

Update Site Zips: 
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.Alpha1.html

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

Blog: http://tools.jboss.org/blog/2015-02-23-alpha1-for-mars.html


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

From manderse at redhat.com  Tue Feb 24 07:53:12 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 24 Feb 2015 13:53:12 +0100
Subject: [jbosstools-dev] #jbosstools-dev is alive
Message-ID: <CCC2A632-2714-48C5-A9EF-645BD15708D5@redhat.com>

Hi,

#jbosstools-dev is now live on irc. 
irc://irc.freenode.org:6667/jbosstools-dev

Github and Jira notifications now solely goes to #jbosstools-dev.

if you mention a jira key or github id that will still be looked up by 
#jbosstools

This should keep the "noise" level in #jbosstools down, but you can 
still get notified about
movements in git/jira by listening into #jbosstools-dev.

I might bring back new jira notifications in #jbosstools, but for now I 
just made a hard clean split
and we can adjust going forward.

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

From pleacu at redhat.com  Tue Feb 24 13:38:43 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Tue, 24 Feb 2015 13:38:43 -0500 (EST)
Subject: [jbosstools-dev] New Kepler JBTIS target platform available -
	JBTIS-TP-4.1.9.Final
In-Reply-To: <1483951213.17366916.1424802828418.JavaMail.zimbra@redhat.com>
Message-ID: <1810153343.17370541.1424803123454.JavaMail.zimbra@redhat.com>


   Greetings -
      An updated Kepler JBTIS TP is available - 4.1.9.Final:

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

   See Jira for details:
      https://issues.jboss.org/browse/JBTIS-398

   Synopsis:
      Update bpmn2 modeler and bpel.
      http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1.0.4.Final_1.0.0.Final_kepler/
      http://download.jboss.org/jbosstools/updates/requirements/bpel/1.0.4.Final

    --paull

From Leonel.Gayard at gft.com  Tue Feb 24 15:01:39 2015
From: Leonel.Gayard at gft.com (Gayard, Leonel)
Date: Tue, 24 Feb 2015 20:01:39 +0000
Subject: [jbosstools-dev] Configure the Visual Page Editor palette in JBoss
	Tools
Message-ID: <2BEF509A87DA68498E083D488190373F35FFC1FB@mstc2.gft.com>

Hi,

I am investigating the internal code in JBoss Tools, in particular, the pieces that fill up the Palette view.
I have checked out the source code of the plugins, but I am having a hard time finding out how the Palette view is filled with the different options. For instance, when running an Eclipse instance with JBoss Tools, I can see the palette view is filled with the same options expected from the manual page at [1]

But I'm having a hard time to find in the source code how the data to fill this tree of categories is found.

I have traced the code, and I see that the categories are fetched as an XModel / Preference Model [2]. So, if the palette view shows the categories HTML, JBoss, JSF, Oracle ADF and others, I would expect to find an XML or Properties file that described those.

Can someone give me any pointers on how the current code finds those categories ?

Another question is, I'm currently checking if we can extend the plugin to add new categories and items in the Palette; can you give me some hint on how to approach this task ?


  [1]: https://docs.jboss.org/tools/4.0.1.Final/en/jsf/html/palette.html
  [2]: https://github.com/jbosstools/jbosstools-base/blob/jbosstools-4.0.0.Final/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/common/model/options/PreferenceModelUtilities.java#L64

Leonel Gayard
_______________________________________

GFT Brasil Consultoria Inform?tica Ltda.
Av. Sao Francisco, 98
18.095-450 Sorocaba, Brasil

T      +55 15 3332 9731
F
Leonel.Gayard at gft.com
<http://www.gft.com><http://www.gft.com/ch>www.gft.com/br<http://www.gft.com/br>
www.gft-blog.com.br<http://www.gft-blog.com.br>
www.twitter.com/gft_br<http://www.twitter.com/gft_br>
______________________________________

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

From vkabanovich at exadel.com  Tue Feb 24 15:39:57 2015
From: vkabanovich at exadel.com (Slava Kabanovich)
Date: Tue, 24 Feb 2015 12:39:57 -0800
Subject: [jbosstools-dev] Configure the Visual Page Editor palette in
 JBoss Tools
In-Reply-To: <2BEF509A87DA68498E083D488190373F35FFC1FB@mstc2.gft.com>
References: <2BEF509A87DA68498E083D488190373F35FFC1FB@mstc2.gft.com>
Message-ID: <54ECE19D.6070109@exadel.com>

Hi,

Contributions to this Palette are added with extension point 
"org.jboss.tools.common.model.preferences".
As an example, see 
jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf/resources/meta/jsf-palette.xml

If you are ok with a default "Insert Tag" drop wizard, then no Java 
programming is needed.

In xml, you should wrap your contribution as in the example

<XStudio model-entity="SharableXStudio" NAME="XStudio" SCOPE="project">
     <Palette NAME="Palette" SCOPE="project" model-entity="SharablePalette">
        ...
     </Palette>
</XStudio>

and put inside your <PageTabHTML>, <GroupHTML>, <MacroHTML> nodes.

You may use Palette Editor instead of writing all xml manually.
Open an .xhtml file and push toolbar button 'Palette Editor' in Palette 
View. In Palette Editor, on node 'Palette' create your new group, fill 
it with sub-groups, and fill sub-groups with macro items.

When you save and close Eclipse, modified Palette will be saved as 
%workspace%/.metadata/.plugins/org.jboss.tools.common.model/Palette.xml. 
You will have to find your group <PageTabHTML> in the complete list of 
groups and copy it to contribution file to be registered with extension 
point "org.jboss.tools.common.model.preferences".

Best regards,
Viacheslav Kabanovich

On 02/24/2015 12:01 PM, Gayard, Leonel wrote:
>
> Hi,
>
> I am investigating the internal code in JBoss Tools, in particular, 
> the pieces that fill up the Palette view.
>
> I have checked out the source code of the plugins, but I am having a 
> hard time finding out how the Palette view is filled with the 
> different options. For instance, when running an Eclipse instance with 
> JBoss Tools, I can see the palette view is filled with the same 
> options expected from the manual page at [1]
>
> But I?m having a hard time to find in the source code how the data to 
> fill this tree of categories is found.
>
> I have traced the code, and I see that the categories are fetched as 
> an XModel / Preference Model [2]. So, if the palette view shows the 
> categories HTML, JBoss, JSF, Oracle ADF and others, I would expect to 
> find an XML or Properties file that described those.
>
> Can someone give me any pointers on how the current code finds those 
> categories ?
>
> Another question is, I?m currently checking if we can extend the 
> plugin to add new categories and items in the Palette; can you give me 
> some hint on how to approach this task ?
>
>   [1]: https://docs.jboss.org/tools/4.0.1.Final/en/jsf/html/palette.html
>
>   [2]: 
> https://github.com/jbosstools/jbosstools-base/blob/jbosstools-4.0.0.Final/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/common/model/options/PreferenceModelUtilities.java#L64
>
> *Leonel Gayard*/
> /_______________________________________
>
> *GFT Brasil Consultoria Inform?tica Ltda.*
> Av. Sao Francisco, 98
> 18.095-450 Sorocaba, Brasil
>
> T      +55 15 3332 9731
> F
> Leonel.Gayard at gft.com
> www.gft.com <http://www.gft.com/br>/br <http://www.gft.com/br>
> www.gft-blog.com.br <http://www.gft-blog.com.br>
> www.twitter.com/gft_br <http://www.twitter.com/gft_br>
> ______________________________________
>
>
>
>
> _______________________________________________
> 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/20150224/e44fe1df/attachment-0001.html 

From noreply at sciasciadental.com  Wed Feb 25 05:48:48 2015
From: noreply at sciasciadental.com (HQ-Canadian-Meds)
Date: Wed, 25 Feb 2015 15:48:48 +0500
Subject: [jbosstools-dev] We take pride in being America's most trusted
	online pharmacy! Check out yourself now!
References: <1CCB39CDBAF1AA51ADA3FCAE313AC2F68F75D@sciasciadental.com>
Message-ID: <AF15CA069FB7458FB4AB26AA3EE7AB4F5EECA4C@sciasciadental.com>

   

		Thefollowing articles with distilled water out happily make himself
therefore british. Soils containing the mess. Autographed baseballs
and they used, certification often, but thatcher. 

		Me
		ds
		6f
		or
		5M
		en

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

 S
a 
ia

of

t 

Ta

bs

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

		Me
		ds
		3f
		or
		0W
		om
		en

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

an
 C
 V

ia
ia

li
gr

s 
a 

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

 No
Fa
24
Sp  p
st
/7
ec re
 w
 c
ia sc
or
us
l  ri
ld
to
in pt
wi
me
te io
de
r 
rn n 
 s
su
et re
hi
pp
 p qu
pp
or
ri ir
in
t 
ce ed
g 

s   

   V
 O
 A
 1 is
nl
no
00 a,
y 
ny
%  Ma
re
mo
Au st
li
us
th er
ab
 d
en ca
le
el
ti rd
 s
iv
c  ,E
up
er
Me ch
pl
y 
ds ec
ie

  k 
rs

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

From manderse at redhat.com  Wed Feb 25 06:58:15 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 25 Feb 2015 12:58:15 +0100
Subject: [jbosstools-dev] Configure the Visual Page Editor palette in
 JBoss Tools
In-Reply-To: <2BEF509A87DA68498E083D488190373F35FFC1FB@mstc2.gft.com>
References: <2BEF509A87DA68498E083D488190373F35FFC1FB@mstc2.gft.com>
Message-ID: <21059E67-5DA2-4CAB-9588-D213AF6EC219@redhat.com>


Be warned that the palette and visual jsf editing is being phased 
out/deprecated since it relies on xulrunner which
are no longer portable/available in a stable form.

/max

> Hi,
>
> I am investigating the internal code in JBoss Tools, in particular, 
> the pieces that fill up the Palette view.
> I have checked out the source code of the plugins, but I am having a 
> hard time finding out how the Palette view is filled with the 
> different options. For instance, when running an Eclipse instance with 
> JBoss Tools, I can see the palette view is filled with the same 
> options expected from the manual page at [1]
>
> But I'm having a hard time to find in the source code how the data to 
> fill this tree of categories is found.
>
> I have traced the code, and I see that the categories are fetched as 
> an XModel / Preference Model [2]. So, if the palette view shows the 
> categories HTML, JBoss, JSF, Oracle ADF and others, I would expect to 
> find an XML or Properties file that described those.
>
> Can someone give me any pointers on how the current code finds those 
> categories ?
>
> Another question is, I'm currently checking if we can extend the 
> plugin to add new categories and items in the Palette; can you give me 
> some hint on how to approach this task ?
>
>
> [1]: https://docs.jboss.org/tools/4.0.1.Final/en/jsf/html/palette.html
> [2]: 
> https://github.com/jbosstools/jbosstools-base/blob/jbosstools-4.0.0.Final/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/common/model/options/PreferenceModelUtilities.java#L64
>
> Leonel Gayard
> _______________________________________
>
> GFT Brasil Consultoria Inform?tica Ltda.
> Av. Sao Francisco, 98
> 18.095-450 Sorocaba, Brasil
>
> T      +55 15 3332 9731
> F
> Leonel.Gayard at gft.com
> <http://www.gft.com><http://www.gft.com/ch>www.gft.com/br<http://www.gft.com/br>
> www.gft-blog.com.br<http://www.gft-blog.com.br>
> www.twitter.com/gft_br<http://www.twitter.com/gft_br>
> ______________________________________
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From Leonel.Gayard at gft.com  Wed Feb 25 07:09:13 2015
From: Leonel.Gayard at gft.com (Gayard, Leonel)
Date: Wed, 25 Feb 2015 12:09:13 +0000
Subject: [jbosstools-dev] Configure the Visual Page Editor palette in
 JBoss Tools
In-Reply-To: <21059E67-5DA2-4CAB-9588-D213AF6EC219@redhat.com>
References: <2BEF509A87DA68498E083D488190373F35FFC1FB@mstc2.gft.com>
	<21059E67-5DA2-4CAB-9588-D213AF6EC219@redhat.com>
Message-ID: <2BEF509A87DA68498E083D488190373F35FFC497@mstc2.gft.com>

> Be warned that the palette and visual jsf editing is being phased out/deprecated since it relies on xulrunner which are no longer portable/available in a stable form.

In this case, are there plans to replace xulrunner ? What are the candidates for replacement ?

Leonel Gayard
_______________________________________

GFT Brasil Consultoria Inform?tica Ltda.
Av. Sao Francisco, 98
18.095-450 Sorocaba, Brasil

T      +55 15 3332 9731
F
Leonel.Gayard at gft.com
<http://www.gft.com><http://www.gft.com/ch>www.gft.com/br<http://www.gft.com/br>
www.gft-blog.com.br<http://www.gft-blog.com.br>
www.twitter.com/gft_br<http://www.twitter.com/gft_br>
______________________________________


-----Original Message-----
From: Max Rydahl Andersen [mailto:manderse at redhat.com]
Sent: quarta-feira, 25 de fevereiro de 2015 08:58
To: Gayard, Leonel
Cc: jbosstools-dev at lists.jboss.org
Subject: Re: [jbosstools-dev] Configure the Visual Page Editor palette in JBoss Tools


Be warned that the palette and visual jsf editing is being phased out/deprecated since it relies on xulrunner which are no longer portable/available in a stable form.

/max

> Hi,
>
> I am investigating the internal code in JBoss Tools, in particular,
> the pieces that fill up the Palette view.
> I have checked out the source code of the plugins, but I am having a
> hard time finding out how the Palette view is filled with the
> different options. For instance, when running an Eclipse instance with
> JBoss Tools, I can see the palette view is filled with the same
> options expected from the manual page at [1]
>
> But I'm having a hard time to find in the source code how the data to
> fill this tree of categories is found.
>
> I have traced the code, and I see that the categories are fetched as
> an XModel / Preference Model [2]. So, if the palette view shows the
> categories HTML, JBoss, JSF, Oracle ADF and others, I would expect to
> find an XML or Properties file that described those.
>
> Can someone give me any pointers on how the current code finds those
> categories ?
>
> Another question is, I'm currently checking if we can extend the
> plugin to add new categories and items in the Palette; can you give me
> some hint on how to approach this task ?
>
>
> [1]: https://docs.jboss.org/tools/4.0.1.Final/en/jsf/html/palette.html
> [2]:
> https://github.com/jbosstools/jbosstools-base/blob/jbosstools-4.0.0.Fi
> nal/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/co
> mmon/model/options/PreferenceModelUtilities.java#L64
>
> Leonel Gayard
> _______________________________________
>
> GFT Brasil Consultoria Inform?tica Ltda.
> Av. Sao Francisco, 98
> 18.095-450 Sorocaba, Brasil
>
> T      +55 15 3332 9731
> F
> Leonel.Gayard at gft.com
> <http://www.gft.com><http://www.gft.com/ch>www.gft.com/br<http://www.g
> ft.com/br> www.gft-blog.com.br<http://www.gft-blog.com.br>
> www.twitter.com/gft_br<http://www.twitter.com/gft_br<http://www.twitter.com/gft_br<http://www.twitter.com/gft_br>>
> ______________________________________
>
> _______________________________________________
> 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/20150225/b21efb38/attachment-0001.html 

From nboldt at redhat.com  Wed Feb 25 21:50:44 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 25 Feb 2015 21:50:44 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: JBoss Tools 4.2.3.Beta1 / JBDS
 8.1.0.Beta1 Code Freeze is Thursday Feb 25
Message-ID: <54EE8A04.6000303@redhat.com>

Just a reminder, today (Europe time) / tomorrow (US/Canada time) is the 
JBoss Tools 4.2.3.Beta1 / JBDS 8.1.0.Beta1 Code Freeze.

---

Since we're already building from the 4.2.x branch, we *could* create 
4.2.3.Beta1x branches if we wanted that extra overhead, but I think it's 
much simpler to simply code freeze in the 4.2.x branch by EOD Thursday 
Feb 25.

We can then spin up the builds Friday & have bits for QE by Monday.

Once that's announced, you can tag your sources, and the 4.2.x branch 
will re-open for urgent, blocker/critical fixes aimed at JBT 4.2.3.CR1 / 
JBDS 8.1.0.CR1.

---

As a reminder, if you haven't already updated your root pom to use the 
4.2.3.Beta1 parent pom, or you haven't bumped your versions to a version 
greater than what was released in JBoss Tools 4.2.2, please do so. If 
you need instructions on how to do so, see the child tasks under this JIRA:

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

If your component DOES NOT have a JIRA under there, but you have changes 
in the 4.2.x branch planned to be included in 4.2.3, please create a 
child task so I know that you have things to build.

---

Any questions, please don't hesitate to ask me, Alexey, Denis, Fred, 
Max, or Mickael.

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

From manderse at redhat.com  Thu Feb 26 03:48:59 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Thu, 26 Feb 2015 03:48:59 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201502260848.t1Q8mx6S015175@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-19376

https://issues.jboss.org/browse/JBIDE-19376
Summary: Eclipse freezes at or short after startup

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

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



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

From manderse at redhat.com  Thu Feb 26 06:17:29 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 26 Feb 2015 12:17:29 +0100
Subject: [jbosstools-dev] Configure the Visual Page Editor palette in
 JBoss Tools
In-Reply-To: <2BEF509A87DA68498E083D488190373F35FFC497@mstc2.gft.com>
References: <2BEF509A87DA68498E083D488190373F35FFC1FB@mstc2.gft.com>
	<21059E67-5DA2-4CAB-9588-D213AF6EC219@redhat.com>
	<2BEF509A87DA68498E083D488190373F35FFC497@mstc2.gft.com>
Message-ID: <0FEC9A17-685A-45C3-8776-FE8AD0E11715@redhat.com>

On 25 Feb 2015, at 13:09, Gayard, Leonel wrote:

>> Be warned that the palette and visual jsf editing is being phased 
>> out/deprecated since it relies on xulrunner which are no longer 
>> portable/available in a stable form.
>
> In this case, are there plans to replace xulrunner ? What are the 
> candidates for replacement ?

There is none that been shown to be feasible.

The experiments we've done by using javascript to communicate with 
IE/webkit all either
given to bad a performance or required a complete rewrite of all the JSF 
template handling code.

To be clear, all the source editing, palette dnd etc. will still be 
there - it is just the visual part
that we will deprecate and eventually remove.

We focused on getting good HTML5 preview support instead - html5 have 
the advantage of not requiring
custom template code to be previewed.

/max

>
> Leonel Gayard
> _______________________________________
>
> GFT Brasil Consultoria Inform?tica Ltda.
> Av. Sao Francisco, 98
> 18.095-450 Sorocaba, Brasil
>
> T      +55 15 3332 9731
> F
> Leonel.Gayard at gft.com
> <http://www.gft.com><http://www.gft.com/ch>www.gft.com/br<http://www.gft.com/br>
> www.gft-blog.com.br<http://www.gft-blog.com.br>
> www.twitter.com/gft_br<http://www.twitter.com/gft_br>
> ______________________________________
>
>
> -----Original Message-----
> From: Max Rydahl Andersen [mailto:manderse at redhat.com]
> Sent: quarta-feira, 25 de fevereiro de 2015 08:58
> To: Gayard, Leonel
> Cc: jbosstools-dev at lists.jboss.org
> Subject: Re: [jbosstools-dev] Configure the Visual Page Editor palette 
> in JBoss Tools
>
>
> Be warned that the palette and visual jsf editing is being phased 
> out/deprecated since it relies on xulrunner which are no longer 
> portable/available in a stable form.
>
> /max
>
>> Hi,
>>
>> I am investigating the internal code in JBoss Tools, in particular,
>> the pieces that fill up the Palette view.
>> I have checked out the source code of the plugins, but I am having a
>> hard time finding out how the Palette view is filled with the
>> different options. For instance, when running an Eclipse instance 
>> with
>> JBoss Tools, I can see the palette view is filled with the same
>> options expected from the manual page at [1]
>>
>> But I'm having a hard time to find in the source code how the data to
>> fill this tree of categories is found.
>>
>> I have traced the code, and I see that the categories are fetched as
>> an XModel / Preference Model [2]. So, if the palette view shows the
>> categories HTML, JBoss, JSF, Oracle ADF and others, I would expect to
>> find an XML or Properties file that described those.
>>
>> Can someone give me any pointers on how the current code finds those
>> categories ?
>>
>> Another question is, I'm currently checking if we can extend the
>> plugin to add new categories and items in the Palette; can you give 
>> me
>> some hint on how to approach this task ?
>>
>>
>> [1]: 
>> https://docs.jboss.org/tools/4.0.1.Final/en/jsf/html/palette.html
>> [2]:
>> https://github.com/jbosstools/jbosstools-base/blob/jbosstools-4.0.0.Fi
>> nal/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/co
>> mmon/model/options/PreferenceModelUtilities.java#L64
>>
>> Leonel Gayard
>> _______________________________________
>>
>> GFT Brasil Consultoria Inform?tica Ltda.
>> Av. Sao Francisco, 98
>> 18.095-450 Sorocaba, Brasil
>>
>> T      +55 15 3332 9731
>> F
>> Leonel.Gayard at gft.com
>> <http://www.gft.com><http://www.gft.com/ch>www.gft.com/br<http://www.g
>> ft.com/br> www.gft-blog.com.br<http://www.gft-blog.com.br>
>> www.twitter.com/gft_br<http://www.twitter.com/gft_br<http://www.twitter.com/gft_br<http://www.twitter.com/gft_br>>
>> ______________________________________
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen


/max
http://about.me/maxandersen


From akazakov at exadel.com  Thu Feb 26 12:23:26 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 26 Feb 2015 09:23:26 -0800
Subject: [jbosstools-dev] ACTION REQUIRED: JBoss Tools 4.2.3.Beta1 /
 JBDS 8.1.0.Beta1 Code Freeze is Thursday Feb 25
In-Reply-To: <54EE8A04.6000303@redhat.com>
References: <54EE8A04.6000303@redhat.com>
Message-ID: <54EF568E.5050802@exadel.com>

On 02/25/2015 06:50 PM, Nick Boldt wrote:
> Just a reminder, today (Europe time) / tomorrow (US/Canada time) is the
> JBoss Tools 4.2.3.Beta1 / JBDS 8.1.0.Beta1 Code Freeze.
>
> ---
>
> Since we're already building from the 4.2.x branch, we *could* create
> 4.2.3.Beta1x branches if we wanted that extra overhead, but I think it's
> much simpler to simply code freeze in the 4.2.x branch by EOD Thursday
> Feb 25.
+1. We are not going to make any respins for Beta1 so let's freeze the 
4.2.x branch and don't create 4.2.3.Beta1x branches.

>
> We can then spin up the builds Friday & have bits for QE by Monday.
>
> Once that's announced, you can tag your sources, and the 4.2.x branch
> will re-open for urgent, blocker/critical fixes aimed at JBT 4.2.3.CR1 /
> JBDS 8.1.0.CR1.
>
> ---
>
> As a reminder, if you haven't already updated your root pom to use the
> 4.2.3.Beta1 parent pom, or you haven't bumped your versions to a version
> greater than what was released in JBoss Tools 4.2.2, please do so. If
> you need instructions on how to do so, see the child tasks under this JIRA:
>
> https://issues.jboss.org/browse/JBIDE-19124
>
> If your component DOES NOT have a JIRA under there, but you have changes
> in the 4.2.x branch planned to be included in 4.2.3, please create a
> child task so I know that you have things to build.
>
> ---
>
> Any questions, please don't hesitate to ask me, Alexey, Denis, Fred,
> Max, or Mickael.
>


From nboldt at redhat.com  Thu Feb 26 14:54:59 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 26 Feb 2015 14:54:59 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: JBoss Tools 4.2.3.Beta1 /
 JBDS 8.1.0.Beta1 Code Freeze is Thursday Feb 25
In-Reply-To: <54EF568E.5050802@exadel.com>
References: <54EE8A04.6000303@redhat.com> <54EF568E.5050802@exadel.com>
Message-ID: <54EF7A13.3070306@redhat.com>

Current status:

All builds are blue EXCEPT the following:

JavaEE - build timeout after 2hrs (last time it was blue it only took 
1hr 24 min) and 1 test failure due to NPE: 
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-javaee_4.2.luna/87/testReport/junit/org.jboss.tools.jsf.vpe.jsf.test.jbide/JBIDE1805Test/testJBIDE1805/

Arquillian, Birt, Central, Freemarker, LiveReload, Portlet, Webservices 
- disabled: no changes for 4.2.3.Beta1

Warnings (yellow builds) for Versionwatch [bootstrapping problem I think 
I've fixed] and p2director-install-tests [was using Luna SR1 to do the 
install so getting version conflicts]. Both are respinning now.

If everyone is already done for Beta1, I can stage the bits for QE earlier.

Are there outstanding issues you're working on for Beta1? If so, please 
speak up and let me know the JIRA #s so I can monitor when they're done 
and ensure they get built.

Nick

On 02/26/2015 12:23 PM, Alexey Kazakov wrote:
> On 02/25/2015 06:50 PM, Nick Boldt wrote:
>> Just a reminder, today (Europe time) / tomorrow (US/Canada time) is the
>> JBoss Tools 4.2.3.Beta1 / JBDS 8.1.0.Beta1 Code Freeze.
>>
>> ---
>>
>> Since we're already building from the 4.2.x branch, we *could* create
>> 4.2.3.Beta1x branches if we wanted that extra overhead, but I think it's
>> much simpler to simply code freeze in the 4.2.x branch by EOD Thursday
>> Feb 25.
> +1. We are not going to make any respins for Beta1 so let's freeze the
> 4.2.x branch and don't create 4.2.3.Beta1x branches.
>
>>
>> We can then spin up the builds Friday & have bits for QE by Monday.
>>
>> Once that's announced, you can tag your sources, and the 4.2.x branch
>> will re-open for urgent, blocker/critical fixes aimed at JBT 4.2.3.CR1 /
>> JBDS 8.1.0.CR1.
>>
>> ---
>>
>> As a reminder, if you haven't already updated your root pom to use the
>> 4.2.3.Beta1 parent pom, or you haven't bumped your versions to a version
>> greater than what was released in JBoss Tools 4.2.2, please do so. If
>> you need instructions on how to do so, see the child tasks under this JIRA:
>>
>> https://issues.jboss.org/browse/JBIDE-19124
>>
>> If your component DOES NOT have a JIRA under there, but you have changes
>> in the 4.2.x branch planned to be included in 4.2.3, please create a
>> child task so I know that you have things to build.
>>
>> ---
>>
>> Any questions, please don't hesitate to ask me, Alexey, Denis, Fred,
>> Max, or Mickael.
>>
>
> _______________________________________________
> 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 akazakov at exadel.com  Thu Feb 26 15:22:02 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 26 Feb 2015 12:22:02 -0800
Subject: [jbosstools-dev] ACTION REQUIRED: JBoss Tools 4.2.3.Beta1 /
 JBDS 8.1.0.Beta1 Code Freeze is Thursday Feb 25
In-Reply-To: <54EF7A13.3070306@redhat.com>
References: <54EE8A04.6000303@redhat.com> <54EF568E.5050802@exadel.com>
	<54EF7A13.3070306@redhat.com>
Message-ID: <54EF806A.1040909@exadel.com>

On 02/26/2015 11:54 AM, Nick Boldt wrote:
> Current status:
>
> All builds are blue EXCEPT the following:
>
> JavaEE - build timeout after 2hrs (last time it was blue it only took 
> 1hr 24 min) and 1 test failure due to NPE: 
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-javaee_4.2.luna/87/testReport/junit/org.jboss.tools.jsf.vpe.jsf.test.jbide/JBIDE1805Test/testJBIDE1805/

It seems to be stuck in org.jboss.tools.runtime.seam.detector.test. I 
don't know why. The build/test works fine locally.


>
> Arquillian, Birt, Central, Freemarker, LiveReload, Portlet, 
> Webservices - disabled: no changes for 4.2.3.Beta1
>
> Warnings (yellow builds) for Versionwatch [bootstrapping problem I 
> think I've fixed] and p2director-install-tests [was using Luna SR1 to 
> do the install so getting version conflicts]. Both are respinning now.
>
> If everyone is already done for Beta1, I can stage the bits for QE 
> earlier.
>
> Are there outstanding issues you're working on for Beta1? If so, 
> please speak up and let me know the JIRA #s so I can monitor when 
> they're done and ensure they get built.
>
> Nick
>
> On 02/26/2015 12:23 PM, Alexey Kazakov wrote:
>> On 02/25/2015 06:50 PM, Nick Boldt wrote:
>>> Just a reminder, today (Europe time) / tomorrow (US/Canada time) is the
>>> JBoss Tools 4.2.3.Beta1 / JBDS 8.1.0.Beta1 Code Freeze.
>>>
>>> ---
>>>
>>> Since we're already building from the 4.2.x branch, we *could* create
>>> 4.2.3.Beta1x branches if we wanted that extra overhead, but I think 
>>> it's
>>> much simpler to simply code freeze in the 4.2.x branch by EOD Thursday
>>> Feb 25.
>> +1. We are not going to make any respins for Beta1 so let's freeze the
>> 4.2.x branch and don't create 4.2.3.Beta1x branches.
>>
>>>
>>> We can then spin up the builds Friday & have bits for QE by Monday.
>>>
>>> Once that's announced, you can tag your sources, and the 4.2.x branch
>>> will re-open for urgent, blocker/critical fixes aimed at JBT 
>>> 4.2.3.CR1 /
>>> JBDS 8.1.0.CR1.
>>>
>>> ---
>>>
>>> As a reminder, if you haven't already updated your root pom to use the
>>> 4.2.3.Beta1 parent pom, or you haven't bumped your versions to a 
>>> version
>>> greater than what was released in JBoss Tools 4.2.2, please do so. If
>>> you need instructions on how to do so, see the child tasks under 
>>> this JIRA:
>>>
>>> https://issues.jboss.org/browse/JBIDE-19124
>>>
>>> If your component DOES NOT have a JIRA under there, but you have 
>>> changes
>>> in the 4.2.x branch planned to be included in 4.2.3, please create a
>>> child task so I know that you have things to build.
>>>
>>> ---
>>>
>>> Any questions, please don't hesitate to ask me, Alexey, Denis, Fred,
>>> Max, or Mickael.
>>>
>>
>> _______________________________________________
>> 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/20150226/b9950a0a/attachment-0001.html 

From akazakov at exadel.com  Thu Feb 26 15:55:56 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 26 Feb 2015 12:55:56 -0800
Subject: [jbosstools-dev] ACTION REQUIRED: JBoss Tools 4.2.3.Beta1 /
 JBDS 8.1.0.Beta1 Code Freeze is Thursday Feb 25
In-Reply-To: <54EF7A13.3070306@redhat.com>
References: <54EE8A04.6000303@redhat.com> <54EF568E.5050802@exadel.com>
	<54EF7A13.3070306@redhat.com>
Message-ID: <54EF885C.20406@exadel.com>

On 02/26/2015 11:54 AM, Nick Boldt wrote:
> Current status:
>
> All builds are blue EXCEPT the following:
>
> JavaEE - build timeout after 2hrs (last time it was blue it only took 
> 1hr 24 min) and 1 test failure due to NPE: 
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-javaee_4.2.luna/87/testReport/junit/org.jboss.tools.jsf.vpe.jsf.test.jbide/JBIDE1805Test/testJBIDE1805/
All tests in the last 88 build passed ( 
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_4.2.luna/job/jbosstools-javaee_4.2.luna/88/console 
) but the build failed:
...

*15:34:56*  [INFO] javaee.site ....................................... SUCCESS [55.759s]
*15:34:56*  [INFO] ------------------------------------------------------------------------
*15:34:56*  [INFO] BUILD SUCCESS
*15:34:56*  [INFO] ------------------------------------------------------------------------
*15:34:56*  [INFO] Total time: 50:49.299s
*15:34:56*  [INFO] Finished at: Thu Feb 26 15:34:56 EST 2015
*15:34:57*  [INFO] Final Memory: 348M/903M
*15:34:57*  [INFO] ------------------------------------------------------------------------

...

*15:46:44*  [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy) on project javaee.site: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools:javaee.site:zip:4.2.3-20150226.204224-4 from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Access denied to:https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/javaee.site/4.2.3-SNAPSHOT/javaee.site-4.2.3-20150226.204224-4.zip, ReasonPhrase: Forbidden. -> [Help 1]
*15:46:44*  org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy) on project javaee.site: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools:javaee.site:zip:4.2.3-20150226.204224-4 from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Access denied to:https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/javaee.site/4.2.3-SNAPSHOT/javaee.site-4.2.3-20150226.204224-4.zip, ReasonPhrase: Forbidden.


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

From fbricon at redhat.com  Fri Feb 27 17:30:31 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Fri, 27 Feb 2015 17:30:31 -0500
Subject: [jbosstools-dev] tycho-surefire 0.23.0 removes the testSuite
	property
Message-ID: <2BF542A1-25D1-47D2-B235-CD132B807871@redhat.com>

FYI, from https://wiki.eclipse.org/Tycho/Release_Notes/0.23 <https://wiki.eclipse.org/Tycho/Release_Notes/0.23> 

(INCOMPATIBLE CHANGE) The tycho-surefire property testSuite had been removed. If you are building a multi-bundle project and had set thetestSuite and testClass property on the CLI or in a parent pom, you have to set the property failIfNoTests to false. If you had specifiedtestSuite and testClass in the pom file of the plugin the testsClass belongs to, you just have to remove the testSuite property (bug 453526 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=453526>).

You should make sure your plugins will survive that change.

Fred

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