Re: [wtp-dev] [webtools.webservices] Build issue - stuck tests in jst.ws.cxf

2018-05-31 Thread Nick Boldt 
OK, with the above changes, the job is now crapping out faster using the
180s timeout. Oops, wrong units. I'll trigger another one with a longer
timeout - 7200s should be better.

 https://ci.eclipse.org/webtools/job/webtools-webservices_R3_10/ >=191

On Thu, May 31, 2018 at 9:58 AM, Nick Boldt  wrote:

> Yes, GEF legacy is being used. I asked about this recently and Carl
> explained why [1].
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=533942#c5
>
> Side issue aside, old logs are potentially available if you see them in
> Jenkins. If you can't find them under artifacts for a given build, then
> they're gone. Since we haven't previously archived the .log files, they're
> gone. But for future builds we can fix that.
>
> Setting a longer timeout? Done: I've added -Dsurefire.exitTimeout=180
> -Dsurefire.timeout=180 to the maven invocations, and upped the overall
> build timeout from 150 to 300 mins.
>
> I've also increased the number of sets of artifacts to store in the job
> from 1 to 4, and the retention rules from 7/5/2/1 to 10/10/10/4. And...
> I've added **/.log to the list of files to archive for each build so those
> will be retained. This might have to change again later if we chew up too
> much disk, but for now it'll help with troubleshooting.
>
> I've also given you (using your email address above) access to configure
> the job once you're logged in to ci.eclipse.org. If that's not the email
> address associated with your eclipse.org userid, let me know and I can
> add your other identity.
>
> Job is running with the above config changes:
>
> https://ci.eclipse.org/webtools/job/webtools-webservices_R3_10/ >=189
>
> Anything else you think would help here?
>
> Thanks for looking into this problem!
>
> Nick
>
> On Tue, May 29, 2018 at 1:11 PM, Shane Clarke 
> wrote:
>
>> Hi Nick,
>>
>> I had a look at these.
>>
>> I'm not able to reproduce the issue locally and i'm running with a build
>> with the dependencies listed in http://git.eclipse.org/c/we
>> btools/webtools.releng.aggregator.git/tree/wtp-parent/pom.xml#n45
>>
>> Just to note the gef-repo.url and the gef-legacy-repo.url look like
>> they're both pulling in GEF 3.1.0 ? (unrelated to this issue)
>>
>> The log file https://ci.eclipse.org/webtools/job/webtools-webservice
>> s_R3_10/ws/jaxws/tests/org.eclipse.jst.ws.cxf.tests/
>> target/work/data/.metadata/.log/*view*/ is full of these type of errors:
>>
>> !MESSAGE No IModelProvider exists for project
>> P/TestProject2_1527516764789 of version: EJB Module 3.0
>> !STACK 0
>> java.lang.NullPointerException: No IModelProvider exists for project
>> P/TestProject2_1527516764789 of version: EJB Module 3.0
>> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProv
>> ider(ModelProviderManager.java:101)
>> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProv
>> ider(ModelProviderManager.java:281)
>> at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvide
>> r.getCachedModelProvider(JEE5ContentProvider.java:76)
>> at org.eclipse.jst.jee.ui.internal.navigator.Ejb3ContentProvide
>> r.getNewContentProviderInstance(Ejb3ContentProvider.java:212)
>> at org.eclipse.jst.jee.ui.internal.navigator.LoadingJeeDDJob.
>> run(LoadingJeeDDJob.java:50)
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
>>
>> !ENTRY org.eclipse.core.jobs 4 2 2018-05-28 10:14:37.987
>> !MESSAGE An internal error occurred during: "Loading descriptor for
>> TestProject2_1527516764789.".
>> !STACK 0
>> java.lang.NullPointerException
>> at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvide
>> r.getCachedModelProvider(JEE5ContentProvider.java:77)
>> at org.eclipse.jst.jee.ui.internal.navigator.Ejb3ContentProvide
>> r.getNewContentProviderInstance(Ejb3ContentProvider.java:212)
>> at org.eclipse.jst.jee.ui.internal.navigator.LoadingJeeDDJob.
>> run(LoadingJeeDDJob.java:50)
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
>>
>> What looks to be happening is the tests themselves aren't failing. The
>> errors are a result of the Project Explorer view (Common Navigator View)
>> being open in the Java EE perspective and it's refreshing as a result of
>> the tests creating EJB projects. The errors are introducing a lag in the
>> test run and the number of them is adding up to push the overall test
>> runtime over the 30 minute timeout.
>>
>> I'm not sure what's caused this to start happening now. These tests are
>> part of a SAP contribution to the project around 9 years ago and they
>> haven't really changed i think since that.
>>
>> Are the test log files for the earlier successful builds e.g. #183
>> maintained? And is it possible to extend the timeout limit for these tests
>> for a test run to see if they pass?
>>
>> Thanks,
>> Shane
>> --
>> *From:* Nick Boldt 
>> *Sent:* Monday 28 May 2018 20:42
>> *To:* Shane Clarke
>> *Cc:* General discussion of project-wide or architectural issues.; Keith
>> Chong
>> *Subject:* Re: [webtools.webservices] Build

Re: [wtp-dev] URGENT - Please review TODAY (was Re: gerrit review for JAXWS bugzilla)

2018-05-31 Thread Elson Yuen 
Nick,

I have added a comment to the first one.  In the future, it will be helpful
if you can following the PMC review process and fill in the PMC approval
template in https://wiki.eclipse.org/WTP_PMC_Defect_Review to help PMC to
understand the impact for approval.

Thanks,
Elson

-
Elson Yuen, P.Eng.
WebSphere Server Tools and Bluemix Tools Architect
IBM Toronto Lab
Tel: (905) 413-2689, T/L: 313-2689




From:   Nick Boldt 
To: Shane Clarke , "General discussion of
project-wide or architectural issues." 
Cc: Keith Chong , Mat Booth

Date:   2018/05/31 09:38 AM
Subject:[wtp-dev] URGENT - Please review TODAY (was Re: gerrit review
for JAXWS bugzilla)
Sent by:wtp-dev-boun...@eclipse.org



Adding PMC to cc: so they're aware of the need for a +1.

I've added the usual suspects to the first BZ - the second already has
Elson's +1 so I assume we're good there as generally everyone else just
ignores these things. :)

https://bugs.eclipse.org/bugs/show_bug.cgi?id=534747
https://bugs.eclipse.org/bugs/show_bug.cgi?id=265772

As TODAY is the usual day for spinning up a build for smoke test (so people
have Fri & Mon to review prior to the Tuesday deadline), this is somewhat
urgent.



On Thu, May 31, 2018 at 2:47 AM, Shane Clarke 
wrote:
  Hi Guys,

  Sorry for being late with getting to this.

  For https://git.eclipse.org/r/#/c/122761/ if we can get the PMC votes for
  RC3 i'll get it in.

  And for https://git.eclipse.org/r/#/c/122932/  i think Keith should sign
  off on it if possible.

  Thanks,
  Shane



  From: Nick Boldt 
  Sent: Wednesday 30 May 2018 14:18
  To: Mat Booth
  Cc: Shane Clarke; Keith Chong
  Subject: Re: gerrit review for JAXWS bugzilla

  I've merged the fix for parent pom and rebuilt it.

  https://hudson.eclipse.org/webtools/job/webtools-webservices-gerrit_master/
   will trigger once the current wtp common build is done (it's rebuilding
  because of the parent pom change).

  On Wed, May 30, 2018 at 8:19 AM, Mat Booth  wrote:
   Another update -- My Orbit fix is now available in an I-build, so I
   submitted the following change for the wtp-parent to update its orbit
   repo reference: https://git.eclipse.org/r/#/c/123635/

   If that is merged, then jenkins should be able to do a successful build
   of this change: https://git.eclipse.org/r/#/c/122932/


   On 23 May 2018 at 10:45, Mat Booth  wrote:
 Regarding this second change, my fix for Orbit was merged, and the new
 wsil4j bundle is available from the latest Orbit nightly repo:
 http://download.eclipse.org/tools/orbit/N-builds/N20180522205425/


 On 19 May 2018 at 01:18, Nick Boldt  wrote:
  There's also a second gerrit for review here [1] but that requires a
  fix in Orbit [2] first.

  [1] https://git.eclipse.org/r/#/c/122932/
  [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=534859

  So... I guess that will require the post-RC1 PMC approval process.

  On Fri, May 18, 2018 at 9:06 AM, Nick Boldt 
  wrote:
Please have a look and if you approve, merge this:

https://git.eclipse.org/r/#/c/122761/

> Bug 534747 - Use import-package for deps that can be supplied by
the jre

This makes WTP more compatible with other platforms (like linux)
where Eclipse can be installed via rpm.

Hopefully the Jenkins on which the gerrit is building won't crap
out like the ones the other day. Seems ci.eclipse.org is a bit
overloaded these days. Must be RC season. :)

Nick

--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com


 
  TRIED. TESTED. 
  TRUSTED.   
 


@ @redhatnews      Red Hat


“The Only Thing That Is Constant Is Change” - Heraclitus



  --
  Nick Boldt
  Principal Software Engineer, RHCSA
  Productization Lead :: JBoss Tools & Dev Studio
  IM: @nickboldt / @nboldt / http://nick.divbyzero.com


 
  TRIED. TESTED. 
  TRUSTED.   
 


  @ @redhatnews      Red Hat


  “The Only Thing That Is Constant Is Change” - Heraclitus





  --
  Nick Boldt
  Principal Software Engineer, RHCSA
  Productization Lead :: JBoss Tools & Dev Studio
  IM: @nickboldt / @nboldt / http://nick.divbyzero.com


 
  TRIED. TESTED. 
  TRUSTED.   
 


  @ @redhatnews      Red Hat


  “The Only Thing That Is Constant Is Change” - Heraclitus



--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM:

Re: [wtp-dev] [webtools.webservices] Build issue - stuck tests in jst.ws.cxf

2018-05-31 Thread Nick Boldt 
Three builds in a row with more time to run the tests, and we're green
every time.

https://ci.eclipse.org/webtools/job/webtools-webservices_R3_10/buildTimeTrend



On Thu, May 31, 2018 at 11:57 AM, Nick Boldt  wrote:

> OK, with the above changes, the job is now crapping out faster using the
> 180s timeout. Oops, wrong units. I'll trigger another one with a longer
> timeout - 7200s should be better.
>
>  https://ci.eclipse.org/webtools/job/webtools-webservices_R3_10/ >=191
>
> On Thu, May 31, 2018 at 9:58 AM, Nick Boldt  wrote:
>
>> Yes, GEF legacy is being used. I asked about this recently and Carl
>> explained why [1].
>>
>> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=533942#c5
>>
>> Side issue aside, old logs are potentially available if you see them in
>> Jenkins. If you can't find them under artifacts for a given build, then
>> they're gone. Since we haven't previously archived the .log files, they're
>> gone. But for future builds we can fix that.
>>
>> Setting a longer timeout? Done: I've added -Dsurefire.exitTimeout=180
>> -Dsurefire.timeout=180 to the maven invocations, and upped the overall
>> build timeout from 150 to 300 mins.
>>
>> I've also increased the number of sets of artifacts to store in the job
>> from 1 to 4, and the retention rules from 7/5/2/1 to 10/10/10/4. And...
>> I've added **/.log to the list of files to archive for each build so those
>> will be retained. This might have to change again later if we chew up too
>> much disk, but for now it'll help with troubleshooting.
>>
>> I've also given you (using your email address above) access to configure
>> the job once you're logged in to ci.eclipse.org. If that's not the email
>> address associated with your eclipse.org userid, let me know and I can
>> add your other identity.
>>
>> Job is running with the above config changes:
>>
>> https://ci.eclipse.org/webtools/job/webtools-webservices_R3_10/ >=189
>>
>> Anything else you think would help here?
>>
>> Thanks for looking into this problem!
>>
>> Nick
>>
>> On Tue, May 29, 2018 at 1:11 PM, Shane Clarke 
>> wrote:
>>
>>> Hi Nick,
>>>
>>> I had a look at these.
>>>
>>> I'm not able to reproduce the issue locally and i'm running with a build
>>> with the dependencies listed in http://git.eclipse.org/c/we
>>> btools/webtools.releng.aggregator.git/tree/wtp-parent/pom.xml#n45
>>>
>>> Just to note the gef-repo.url and the gef-legacy-repo.url look like
>>> they're both pulling in GEF 3.1.0 ? (unrelated to this issue)
>>>
>>> The log file https://ci.eclipse.org/webtools/job/webtools-webservice
>>> s_R3_10/ws/jaxws/tests/org.eclipse.jst.ws.cxf.tests/target/
>>> work/data/.metadata/.log/*view*/ is full of these type of errors:
>>>
>>> !MESSAGE No IModelProvider exists for project
>>> P/TestProject2_1527516764789 of version: EJB Module 3.0
>>> !STACK 0
>>> java.lang.NullPointerException: No IModelProvider exists for project
>>> P/TestProject2_1527516764789 of version: EJB Module 3.0
>>> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProv
>>> ider(ModelProviderManager.java:101)
>>> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProv
>>> ider(ModelProviderManager.java:281)
>>> at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvide
>>> r.getCachedModelProvider(JEE5ContentProvider.java:76)
>>> at org.eclipse.jst.jee.ui.internal.navigator.Ejb3ContentProvide
>>> r.getNewContentProviderInstance(Ejb3ContentProvider.java:212)
>>> at org.eclipse.jst.jee.ui.internal.navigator.LoadingJeeDDJob.ru
>>> n(LoadingJeeDDJob.java:50)
>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
>>>
>>> !ENTRY org.eclipse.core.jobs 4 2 2018-05-28 10:14:37.987
>>> !MESSAGE An internal error occurred during: "Loading descriptor for
>>> TestProject2_1527516764789.".
>>> !STACK 0
>>> java.lang.NullPointerException
>>> at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvide
>>> r.getCachedModelProvider(JEE5ContentProvider.java:77)
>>> at org.eclipse.jst.jee.ui.internal.navigator.Ejb3ContentProvide
>>> r.getNewContentProviderInstance(Ejb3ContentProvider.java:212)
>>> at org.eclipse.jst.jee.ui.internal.navigator.LoadingJeeDDJob.ru
>>> n(LoadingJeeDDJob.java:50)
>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
>>>
>>> What looks to be happening is the tests themselves aren't failing. The
>>> errors are a result of the Project Explorer view (Common Navigator View)
>>> being open in the Java EE perspective and it's refreshing as a result of
>>> the tests creating EJB projects. The errors are introducing a lag in the
>>> test run and the number of them is adding up to push the overall test
>>> runtime over the 30 minute timeout.
>>>
>>> I'm not sure what's caused this to start happening now. These tests are
>>> part of a SAP contribution to the project around 9 years ago and they
>>> haven't really changed i think since that.
>>>
>>> Are the test log files for the earlier successful builds e.g. #183
>>> maintained? And is it possible to extend the timeout

Re: [wtp-dev] [webtools.webservices] Build issue - stuck tests in jst.ws.cxf

2018-05-31 Thread Nick Boldt 
Yes, GEF legacy is being used. I asked about this recently and Carl
explained why [1].

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=533942#c5

Side issue aside, old logs are potentially available if you see them in
Jenkins. If you can't find them under artifacts for a given build, then
they're gone. Since we haven't previously archived the .log files, they're
gone. But for future builds we can fix that.

Setting a longer timeout? Done: I've added -Dsurefire.exitTimeout=180
-Dsurefire.timeout=180 to the maven invocations, and upped the overall
build timeout from 150 to 300 mins.

I've also increased the number of sets of artifacts to store in the job
from 1 to 4, and the retention rules from 7/5/2/1 to 10/10/10/4. And...
I've added **/.log to the list of files to archive for each build so those
will be retained. This might have to change again later if we chew up too
much disk, but for now it'll help with troubleshooting.

I've also given you (using your email address above) access to configure
the job once you're logged in to ci.eclipse.org. If that's not the email
address associated with your eclipse.org userid, let me know and I can add
your other identity.

Job is running with the above config changes:

https://ci.eclipse.org/webtools/job/webtools-webservices_R3_10/ >=189

Anything else you think would help here?

Thanks for looking into this problem!

Nick

On Tue, May 29, 2018 at 1:11 PM, Shane Clarke 
wrote:

> Hi Nick,
>
> I had a look at these.
>
> I'm not able to reproduce the issue locally and i'm running with a build
> with the dependencies listed in http://git.eclipse.org/c/
> webtools/webtools.releng.aggregator.git/tree/wtp-parent/pom.xml#n45
>
> Just to note the gef-repo.url and the gef-legacy-repo.url look like
> they're both pulling in GEF 3.1.0 ? (unrelated to this issue)
>
> The log file https://ci.eclipse.org/webtools/job/webtools-
> webservices_R3_10/ws/jaxws/tests/org.eclipse.jst.ws.cxf.
> tests/target/work/data/.metadata/.log/*view*/ is full of these type of
> errors:
>
> !MESSAGE No IModelProvider exists for project P/TestProject2_1527516764789
> of version: EJB Module 3.0
> !STACK 0
> java.lang.NullPointerException: No IModelProvider exists for project
> P/TestProject2_1527516764789 of version: EJB Module 3.0
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(
> ModelProviderManager.java:101)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(
> ModelProviderManager.java:281)
> at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider.
> getCachedModelProvider(JEE5ContentProvider.java:76)
> at org.eclipse.jst.jee.ui.internal.navigator.Ejb3ContentProvider.
> getNewContentProviderInstance(Ejb3ContentProvider.java:212)
> at org.eclipse.jst.jee.ui.internal.navigator.LoadingJeeDDJob.run(
> LoadingJeeDDJob.java:50)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
>
> !ENTRY org.eclipse.core.jobs 4 2 2018-05-28 10:14:37.987
> !MESSAGE An internal error occurred during: "Loading descriptor for
> TestProject2_1527516764789.".
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider.
> getCachedModelProvider(JEE5ContentProvider.java:77)
> at org.eclipse.jst.jee.ui.internal.navigator.Ejb3ContentProvider.
> getNewContentProviderInstance(Ejb3ContentProvider.java:212)
> at org.eclipse.jst.jee.ui.internal.navigator.LoadingJeeDDJob.run(
> LoadingJeeDDJob.java:50)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
>
> What looks to be happening is the tests themselves aren't failing. The
> errors are a result of the Project Explorer view (Common Navigator View)
> being open in the Java EE perspective and it's refreshing as a result of
> the tests creating EJB projects. The errors are introducing a lag in the
> test run and the number of them is adding up to push the overall test
> runtime over the 30 minute timeout.
>
> I'm not sure what's caused this to start happening now. These tests are
> part of a SAP contribution to the project around 9 years ago and they
> haven't really changed i think since that.
>
> Are the test log files for the earlier successful builds e.g. #183
> maintained? And is it possible to extend the timeout limit for these tests
> for a test run to see if they pass?
>
> Thanks,
> Shane
> --
> *From:* Nick Boldt 
> *Sent:* Monday 28 May 2018 20:42
> *To:* Shane Clarke
> *Cc:* General discussion of project-wide or architectural issues.; Keith
> Chong
> *Subject:* Re: [webtools.webservices] Build issue - stuck tests in
> jst.ws.cxf
>
> No dep changes since May 9, in terms of URLs used.
>
> http://git.eclipse.org/c/webtools/webtools.releng.aggregator
> .git/log/wtp-parent/pom.xml
>
> However, since some URLs are a "latest build" style, you can see that the
> deps can change for Platform, DTP, JGit/EGit, & EMF.
>
> http://git.eclipse.org/c/webtools/webtools.releng.aggregator.git/tree/wtp-
> parent/pom.xml#n45
>
> The rest of

[wtp-dev] URGENT - Please review TODAY (was Re: gerrit review for JAXWS bugzilla)

2018-05-31 Thread Nick Boldt 
Adding PMC to cc: so they're aware of the need for a +1.

I've added the usual suspects to the first BZ - the second already has
Elson's +1 so I assume we're good there as generally everyone else just
ignores these things. :)

https://bugs.eclipse.org/bugs/show_bug.cgi?id=534747
https://bugs.eclipse.org/bugs/show_bug.cgi?id=265772

As TODAY is the usual day for spinning up a build for smoke test (so people
have Fri & Mon to review prior to the Tuesday deadline), this is somewhat
urgent.



On Thu, May 31, 2018 at 2:47 AM, Shane Clarke 
wrote:

> Hi Guys,
>
> Sorry for being late with getting to this.
>
> For https://git.eclipse.org/r/#/c/122761/ if we can get the PMC votes for
> RC3 i'll get it in.
>
> And for https://git.eclipse.org/r/#/c/122932/  i think Keith should sign
> off on it if possible.
>
> Thanks,
> Shane
>
>
> --
> *From:* Nick Boldt 
> *Sent:* Wednesday 30 May 2018 14:18
> *To:* Mat Booth
> *Cc:* Shane Clarke; Keith Chong
> *Subject:* Re: gerrit review for JAXWS bugzilla
>
> I've merged the fix for parent pom and rebuilt it.
>
> https://hudson.eclipse.org/webtools/job/webtools-
> webservices-gerrit_master/ will trigger once the current wtp common build
> is done (it's rebuilding because of the parent pom change).
>
> On Wed, May 30, 2018 at 8:19 AM, Mat Booth  wrote:
>
> Another update -- My Orbit fix is now available in an I-build, so I
> submitted the following change for the wtp-parent to update its orbit repo
> reference: https://git.eclipse.org/r/#/c/123635/
>
> If that is merged, then jenkins should be able to do a successful build of
> this change: https://git.eclipse.org/r/#/c/122932/
>
>
> On 23 May 2018 at 10:45, Mat Booth  wrote:
>
> Regarding this second change, my fix for Orbit was merged, and the new
> wsil4j bundle is available from the latest Orbit nightly repo:
> http://download.eclipse.org/tools/orbit/N-builds/N20180522205425/
>
>
> On 19 May 2018 at 01:18, Nick Boldt  wrote:
>
> There's also a second gerrit for review here [1] but that requires a fix
> in Orbit [2] first.
>
> [1] https://git.eclipse.org/r/#/c/122932/
> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=534859
>
> So... I guess that will require the post-RC1 PMC approval process.
>
> On Fri, May 18, 2018 at 9:06 AM, Nick Boldt  wrote:
>
> Please have a look and if you approve, merge this:
>
> https://git.eclipse.org/r/#/c/122761/
>
> > Bug 534747 - Use import-package for deps that can be supplied by the jre
>
> This makes WTP more compatible with other platforms (like linux) where
> Eclipse can be installed via rpm.
>
> Hopefully the Jenkins on which the gerrit is building won't crap out like
> the ones the other day. Seems ci.eclipse.org is a bit overloaded these
> days. Must be RC season. :)
>
> Nick
>
> --
>
> Nick Boldt
>
> Principal Software Engineer, RHCSA
>
> Productization Lead :: JBoss Tools & Dev Studio
>
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> 
> TRIED. TESTED. TRUSTED. 
> @ @redhatnews   Red Hat
> 
> 
>
>
> “The Only Thing That Is Constant Is Change” - Heraclitus
>
>
>
>
> --
>
> Nick Boldt
>
> Principal Software Engineer, RHCSA
>
> Productization Lead :: JBoss Tools & Dev Studio
>
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> 
> TRIED. TESTED. TRUSTED. 
> @ @redhatnews   Red Hat
> 
> 
>
>
> “The Only Thing That Is Constant Is Change” - Heraclitus
>
>
>
>
>
>
> --
>
> Nick Boldt
>
> Principal Software Engineer, RHCSA
>
> Productization Lead :: JBoss Tools & Dev Studio
>
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> 
> TRIED. TESTED. TRUSTED. 
> @ @redhatnews   Red Hat
> 
> 
>
>
> “The Only Thing That Is Constant Is Change” - Heraclitus
>



-- 

Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com

TRIED. TESTED. TRUSTED. 
@ @redhatnews   Red Hat




“The Only Thing That Is Constant Is Change” - Heraclitus
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev