From ggastald at redhat.com  Tue Sep  1 00:12:46 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Tue, 1 Sep 2015 01:12:46 -0300
Subject: [jbosstools-dev] Potential changes to New Server Wizard
 workflow in Mars.1 or Mars.2
In-Reply-To: <55E52154.9010606@redhat.com>
References: <55E52154.9010606@redhat.com>
Message-ID: <CAMmsnJhTt3g7SrNvn_OdzzAh0NKBQ8_dm33_v3NgrWbLYmctEQ@mail.gmail.com>

+1. I like this new proposal. It keeps the user in a single dialog

On Tue, Sep 1, 2015 at 12:53 AM, Rob Stryker <rstryker at redhat.com> wrote:

> https://wiki.eclipse.org/EDT:NewServerWizardFlow
>
> There's a thread on wtp-dev about this, in which Konstantin gives a
> pretty thorough critique and shuts down the idea. Whether or not
> servertools will agree remains to be seen.
>
> http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg09389.html
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
*George Gastaldi | Senior Software Engineer*

JBoss Forge Team
T: +55 11 3524-6169
M: +55 47 9711-1000
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150901/38224a08/attachment.html 

From manderse at redhat.com  Tue Sep  1 03:41:49 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 01 Sep 2015 09:41:49 +0200
Subject: [jbosstools-dev] Potential changes to New Server Wizard
 workflow in Mars.1 or Mars.2
In-Reply-To: <55E52154.9010606@redhat.com>
References: <55E52154.9010606@redhat.com>
Message-ID: <0C50C68C-4F82-45CD-9296-9A4C78AC3278@redhat.com>

I like the idea.

And I do not think Konstantin is shutting down the idea, he is simply 
pointing out the new flow
has not covered some obvious possible errors.

I agree with Konstantin that the UI will be (if implemented naively) 
noticeably slower and there
are very little the user can do to actually grok what went wrong if 
something fails.

I'll comment on the wtp-dev thread too.

/max


> https://wiki.eclipse.org/EDT:NewServerWizardFlow
>
> There's a thread on wtp-dev about this, in which Konstantin gives a
> pretty thorough critique and shuts down the idea. Whether or not
> servertools will agree remains to be seen.
>
> http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg09389.html
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From fbricon at gmail.com  Wed Sep  2 00:22:57 2015
From: fbricon at gmail.com (Fred Bricon)
Date: Wed, 2 Sep 2015 00:22:57 -0400
Subject: [jbosstools-dev] m2e 1.6.2 RC2 is available
Message-ID: <CAG2ouxTv3-rKhJsXBXO=kNWdQvbJ0Waob7rhBhOuTEQveKJA4Q@mail.gmail.com>

Hello World,

m2e 1.6.2 (1.6.2.20150902-0001) RC2 for Mars.1 has been released. 3 small
bugs were fixed, as you can see in the changelog[1]. I didn't initially
planned on pushing a new RC for m2e 1.6.2, but thanks to Konrad Windszus'
contributions, here we are.
m2e 1.6.2 can be installed from [2].

Enjoy,

Fred.

[1]
https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&list_id=12540793&product=m2e&query_format=advanced&resolution=FIXED&target_milestone=1.6.2%2FMars%20RC2
[2] http://download.eclipse.org/technology/m2e/milestones/1.6/


-- 
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150902/ecb6b4cc/attachment-0001.html 

From manderse at redhat.com  Wed Sep  2 02:59:31 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Wed, 2 Sep 2015 02:59:31 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201509020659.t826xV6U011185@int-mx09.intmail.prod.int.phx2.redhat.com>


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

 
* No component for JBIDE-20539

https://issues.jboss.org/browse/JBIDE-20539
Summary: wildfly-hibernate3 quickstart fails to validate in eclipse

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

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



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

From nboldt at redhat.com  Wed Sep  2 17:27:26 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 2 Sep 2015 17:27:26 -0400
Subject: [jbosstools-dev] Planning for Eclipse Neon (2016-2017)
Message-ID: <CA+QcL11ZLoh4L0KOVA_Y6RNz5LmwLOnGuHwCkEJ505NCMbHR8A@mail.gmail.com>

Just a quick heads up re: next year's Eclipse Simultaneous Release.

The Eclipse Planning Council is working on a plan to do 4 Neon
releases: 1 main one in June 2016 followed by 3 updates in September
2016, (early) December 2016, and March 2017. This is still being
finalized.

Projects will be able to join the train for any of these milestones,
not just the main one in June. Goal is to provide easier access to
joining the train and support more projects wanting to do updates at
more points throughout the year.

For Mars, the plan is to do the usual 1 main release (completed back
in June 2015) followed by 2 update releases at the usual dates:
September and February. For Luna these were called "Service Releases"
but from Mars onward they are "Update Releases", in that new features,
new projects, & minor updates are now allowed.

Gone is the annual monolith; long live quarterly releases!

More info: https://wiki.eclipse.org/Planning_Council/September_02_2015

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

From rcernich at redhat.com  Wed Sep  2 17:50:22 2015
From: rcernich at redhat.com (Rob Cernich)
Date: Wed, 2 Sep 2015 17:50:22 -0400 (EDT)
Subject: [jbosstools-dev] Planning for Eclipse Neon (2016-2017)
In-Reply-To: <CA+QcL11ZLoh4L0KOVA_Y6RNz5LmwLOnGuHwCkEJ505NCMbHR8A@mail.gmail.com>
References: <CA+QcL11ZLoh4L0KOVA_Y6RNz5LmwLOnGuHwCkEJ505NCMbHR8A@mail.gmail.com>
Message-ID: <2125936755.24279166.1441230622978.JavaMail.zimbra@redhat.com>

This is great news!

----- Original Message -----
> Just a quick heads up re: next year's Eclipse Simultaneous Release.
> 
> The Eclipse Planning Council is working on a plan to do 4 Neon
> releases: 1 main one in June 2016 followed by 3 updates in September
> 2016, (early) December 2016, and March 2017. This is still being
> finalized.
> 
> Projects will be able to join the train for any of these milestones,
> not just the main one in June. Goal is to provide easier access to
> joining the train and support more projects wanting to do updates at
> more points throughout the year.
> 
> For Mars, the plan is to do the usual 1 main release (completed back
> in June 2015) followed by 2 update releases at the usual dates:
> September and February. For Luna these were called "Service Releases"
> but from Mars onward they are "Update Releases", in that new features,
> new projects, & minor updates are now allowed.
> 
> Gone is the annual monolith; long live quarterly releases!
> 
> More info: https://wiki.eclipse.org/Planning_Council/September_02_2015
> 
> --
> 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
> 

From manderse at redhat.com  Thu Sep  3 03:18:54 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 03 Sep 2015 09:18:54 +0200
Subject: [jbosstools-dev] Planning for Eclipse Neon (2016-2017)
In-Reply-To: <2125936755.24279166.1441230622978.JavaMail.zimbra@redhat.com>
References: <CA+QcL11ZLoh4L0KOVA_Y6RNz5LmwLOnGuHwCkEJ505NCMbHR8A@mail.gmail.com>
	<2125936755.24279166.1441230622978.JavaMail.zimbra@redhat.com>
Message-ID: <4DB65F48-DBDD-4828-AA7C-CD8627F6BF21@redhat.com>

It is worth noting this system of new features and minor updates being 
allowed
is not *really* news.

This approach been allowed for the last 2-3 years.

The *new* part is that it is now formalised and made explicit
that completely new projects (like BuildShip) can join the release 
train.

Side effect of this is we'll need to be even more proactive to get 
updated
or at least verify compatibility. Unless we trust every eclipse project 
to
stay 100% source and binary API compatible now that it is official they 
are allowed to add features.

Hint: I don't trust it to be - but i'm also fine we ensure we can update 
more
aggressively ;)

/max

> This is great news!
>
> ----- Original Message -----
>> Just a quick heads up re: next year's Eclipse Simultaneous Release.
>>
>> The Eclipse Planning Council is working on a plan to do 4 Neon
>> releases: 1 main one in June 2016 followed by 3 updates in September
>> 2016, (early) December 2016, and March 2017. This is still being
>> finalized.
>>
>> Projects will be able to join the train for any of these milestones,
>> not just the main one in June. Goal is to provide easier access to
>> joining the train and support more projects wanting to do updates at
>> more points throughout the year.
>>
>> For Mars, the plan is to do the usual 1 main release (completed back
>> in June 2015) followed by 2 update releases at the usual dates:
>> September and February. For Luna these were called "Service Releases"
>> but from Mars onward they are "Update Releases", in that new 
>> features,
>> new projects, & minor updates are now allowed.
>>
>> Gone is the annual monolith; long live quarterly releases!
>>
>> More info: 
>> https://wiki.eclipse.org/Planning_Council/September_02_2015
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From manderse at redhat.com  Thu Sep  3 03:33:10 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 03 Sep 2015 09:33:10 +0200
Subject: [jbosstools-dev] Planning for Eclipse Neon (2016-2017)
In-Reply-To: <4DB65F48-DBDD-4828-AA7C-CD8627F6BF21@redhat.com>
References: <CA+QcL11ZLoh4L0KOVA_Y6RNz5LmwLOnGuHwCkEJ505NCMbHR8A@mail.gmail.com>
	<2125936755.24279166.1441230622978.JavaMail.zimbra@redhat.com>
	<4DB65F48-DBDD-4828-AA7C-CD8627F6BF21@redhat.com>
Message-ID: <E3FD0AB1-E995-409A-9EE3-5C9A69AC5535@redhat.com>

And just to be clear - I think all of this is good!

/max

> It is worth noting this system of new features and minor updates being
> allowed
> is not *really* news.
>
> This approach been allowed for the last 2-3 years.
>
> The *new* part is that it is now formalised and made explicit
> that completely new projects (like BuildShip) can join the release
> train.
>
> Side effect of this is we'll need to be even more proactive to get
> updated
> or at least verify compatibility. Unless we trust every eclipse project
> to
> stay 100% source and binary API compatible now that it is official they
> are allowed to add features.
>
> Hint: I don't trust it to be - but i'm also fine we ensure we can update
> more
> aggressively ;)
>
> /max
>
>> This is great news!
>>
>> ----- Original Message -----
>>> Just a quick heads up re: next year's Eclipse Simultaneous Release.
>>>
>>> The Eclipse Planning Council is working on a plan to do 4 Neon
>>> releases: 1 main one in June 2016 followed by 3 updates in September
>>> 2016, (early) December 2016, and March 2017. This is still being
>>> finalized.
>>>
>>> Projects will be able to join the train for any of these milestones,
>>> not just the main one in June. Goal is to provide easier access to
>>> joining the train and support more projects wanting to do updates at
>>> more points throughout the year.
>>>
>>> For Mars, the plan is to do the usual 1 main release (completed back
>>> in June 2015) followed by 2 update releases at the usual dates:
>>> September and February. For Luna these were called "Service Releases"
>>> but from Mars onward they are "Update Releases", in that new
>>> features,
>>> new projects, & minor updates are now allowed.
>>>
>>> Gone is the annual monolith; long live quarterly releases!
>>>
>>> More info:
>>> https://wiki.eclipse.org/Planning_Council/September_02_2015
>>>
>>> --
>>> Nick Boldt :: JBoss by Red Hat
>>> Productization Lead :: JBoss Tools & Dev Studio
>>> http://nick.divbyzero.com
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /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 alkazako at redhat.com  Thu Sep  3 13:26:38 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Thu, 3 Sep 2015 13:26:38 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: JBT 4.3.0.CR1 triage
In-Reply-To: <55CE5512.8020406@redhat.com>
References: <55CE5512.8020406@redhat.com>
Message-ID: <55E882CE.4050100@redhat.com>

Hi everybody,

JBT/JBDS CR1 JIRAs should be clean by the beginning of next week. What 
clean JIRA means: your component should have only two kind of issues:
1. You are sure you will work on this issue during next 6 days (the code 
freeze is on next Thursday).
2. It's critical/blocker for CR1 or GA even if you don't know how to fix 
it now. *Please speak up about such issues NOW**!*

All other issues MUST be moved to some later version. Don't wait until 
next Thursday. Spend an hour or so to triage all your CR1/GA issues now.
I will schedule a meeting with every component lead if there is 
unreasonable number of unresolved issues targeted for CR1/GA in your 
component.

Thank you.



On 08/14/2015 04:52 PM, Alexey Kazakov wrote:
> Hi all,
>
> As you know we have less than 4 weeks before the code freeze for CR1.
> And we still have a lot of unresolved issues targeted for CR1: 185 
> issues in https://issues.jboss.org/browse/JBIDE 
> <https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20%284.3.0.CR1%2C%204.3.0.Final%29%20ORDER%20BY%20component%20ASC%2C%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC>
>
> I know it happens every time we are approaching a release. We just 
> wait the next code freeze than move all unresolved issues to the next 
> version. It really doesn't help to see the status of development.
> Having a clean JIRA which reflects reality is a very important thing 
> for such a big team as ours.
>
> So please, give some love to *your component in JIRA* and move 
> everything which is not blocker/critical for CR1/GA (and you are not 
> sure if you have time to fix in next 3-4 weeks) out of 4.3.0 scope 
> *now*. Don't wait for the code freeze or personal ping.
>
> *So, the CR1/Final JIRA should have only:*
> - blocker/critical issues
> - major/minor issues you are sure you will fix safely during next 3-4 
> weeks.
>
> If something is blocker/critical but you can't fix it before the code 
> freeze, please *speak up now*!
>
>
>
>
> Here is the list of components with the biggest numbers of unresolved 
> issues /(I didn't include OpenShift with 52 issues because OS is a 
> special case and it's kinda expected)/:
>
> *Build, 24 issues:*
> https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(4.3.0.CR1%2C%204.3.0.Final)%20AND%20component%20%3D%20build%20ORDER%20BY%20priority%20DESC
>
> *Hibernate, 14 *(plus 6 Forge issues below as a bonus for Koen ;-) *:*
> https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20hibernate%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
> *
> **Server + runtime detection, 12:*
> https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20AND%20component%20in%20(runtime-detection%2C%20server)%20ORDER%20BY%20priority%20DESC
> *
> **Webservies, 10:*
> https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20webservices%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
>
> *Docker, 8:*
> https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20docker%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
>
> *Easymport, 8:*
> https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20easymport%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
>
> *Arquillian, 7:*
> https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20arquillian%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
> *
> **Central, 7:*
> https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20central%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
> *
> **Forge, 6:*
> https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20forge%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
> *
> **Freemarker, 6:*
> https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20freemarker%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
>
> *VPE, 6:*
> https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20AND%20component%20in%20(visual-page-editor-core%2C%20visual-page-editor-templates)%20ORDER%20BY%20priority%20DESC
>
> Thank you!
>
>
>
> _______________________________________________
> 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/20150903/8d1c609d/attachment-0001.html 

From manderse at redhat.com  Fri Sep  4 02:59:02 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Fri, 4 Sep 2015 02:59:02 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201509040659.t846x2Dn024588@int-mx09.intmail.prod.int.phx2.redhat.com>


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

 
* No component for JBIDE-20559

https://issues.jboss.org/browse/JBIDE-20559
Summary: org.jboss.tools.common.validation.JBTValidationException 	at org.jboss.tools.common.validation.AsYouTypeValidatorManager.

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

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



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

From manderse at redhat.com  Fri Sep  4 05:12:33 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Fri, 4 Sep 2015 05:12:33 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201509040912.t849CXZ7025535@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-20559

https://issues.jboss.org/browse/JBIDE-20559
Summary: org.jboss.tools.common.validation.JBTValidationException 	at org.jboss.tools.common.validation.AsYouTypeValidatorManager.

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please ensure this issue has a proper component set.
Last Update: 19:53:52.047075

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



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

From manderse at redhat.com  Mon Sep  7 03:52:35 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 07 Sep 2015 09:52:35 +0200
Subject: [jbosstools-dev] is install-grinder working ?
Message-ID: <0A933F2A-7586-40C3-8798-10631F0EBFC2@redhat.com>

Hey,

We have our install-grinder and p2 install tests to catch errors but
I don't notice them being mentioned when what looks like actual basic 
p2/metadata
  errors are fixed.

i.e. https://github.com/jbosstools/jbosstools-discovery/pull/299 simple 
issue, simple fix.

But was this caught by p2 install and install-grinder ?
  - if not, why not ? This seems like one that should have been easily 
caught.
  - if yes, why first now ? We made this change to sites a while ago 
(JBDS-3208 was resolved end-of-june)

Looking at the logs of install-grinder 
(https://ci.jboss.org/hudson/job/jbosstools-install-grinder_master/ or 
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder_master/) 
it shows perfect blue since Jun 13 2014.

So my assumption is that it was *not* caught.

Nick/Mickael - how come install-grinder can pass when the repos it is 
supposed to point to are 404 ?

If it's because the tests are using intermediary build urls then it 
sounds like we are missing an actual test for the
released bits as opposed only having for our current build ?

/max
http://about.me/maxandersen


From mistria at redhat.com  Mon Sep  7 04:53:37 2015
From: mistria at redhat.com (Mickael Istria)
Date: Mon, 7 Sep 2015 10:53:37 +0200
Subject: [jbosstools-dev] is install-grinder working ?
In-Reply-To: <0A933F2A-7586-40C3-8798-10631F0EBFC2@redhat.com>
References: <0A933F2A-7586-40C3-8798-10631F0EBFC2@redhat.com>
Message-ID: <55ED5091.2020108@redhat.com>

The job to look at is 
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/
It's currently unstable because of various issues, mainly with metacity 
on CI slaves, over and over again. So since it's often failing, the 
error notifications get ignored at the moment,
But anyway, specifically for the change about certification URL you 
linked, install-grinder doesn't follow certification URL links and such 
issues don't prevent Central or installation from working, so even with 
a wrong URL at that locaiton, install succeeds and we get no notification.

-- 
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/20150907/9fb991f3/attachment.html 

From manderse at redhat.com  Mon Sep  7 09:46:23 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 07 Sep 2015 15:46:23 +0200
Subject: [jbosstools-dev] is install-grinder working ?
In-Reply-To: <55ED5091.2020108@redhat.com>
References: <0A933F2A-7586-40C3-8798-10631F0EBFC2@redhat.com>
	<55ED5091.2020108@redhat.com>
Message-ID: <ACE141AA-B2A1-422F-A70A-A7336B104156@redhat.com>

On 7 Sep 2015, at 10:53, Mickael Istria wrote:

> The job to look at is 
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/
> It's currently unstable because of various issues, mainly with 
> metacity on CI slaves, over and over again.

Any jira tracking the progress on fixing this ?

> So since it's often failing, the error notifications get ignored at 
> the moment,
> But anyway, specifically for the change about certification URL you 
> linked, install-grinder doesn't follow certification URL links and 
> such issues don't prevent Central or installation from working, so 
> even with a wrong URL at that locaiton, install succeeds and we get no 
> notification.

good point.

But seems like at least when building the jbosstools-discovery a basic 
test of its result would be to follow those urls in the result. That 
should have catched it too.

/max
http://about.me/maxandersen


From nboldt at redhat.com  Tue Sep  8 11:42:36 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 8 Sep 2015 11:42:36 -0400
Subject: [jbosstools-dev] is install-grinder working ?
In-Reply-To: <0A933F2A-7586-40C3-8798-10631F0EBFC2@redhat.com>
References: <0A933F2A-7586-40C3-8798-10631F0EBFC2@redhat.com>
Message-ID: <CA+QcL11yZdJVb=R22tGyD_KRiNM3MLONAOjy4z+HYvJdhY+CTg@mail.gmail.com>

Re: jbosstools-discovery/pull/299 nothing pings those URLs. They're
only there so when a user clicks on a certification link for more
info, they get a page opened in a browser. None of the install tests
will catch what happens when a user clicks on a "more info" link. :D

Re: jiras for install grinder, yes. There are a few. There are also
eng-ops tickets.

On Mon, Sep 7, 2015 at 3:52 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
> Hey,
>
> We have our install-grinder and p2 install tests to catch errors but
> I don't notice them being mentioned when what looks like actual basic
> p2/metadata
>   errors are fixed.
>
> i.e. https://github.com/jbosstools/jbosstools-discovery/pull/299 simple
> issue, simple fix.
>
> But was this caught by p2 install and install-grinder ?
>   - if not, why not ? This seems like one that should have been easily
> caught.
>   - if yes, why first now ? We made this change to sites a while ago
> (JBDS-3208 was resolved end-of-june)
>
> Looking at the logs of install-grinder
> (https://ci.jboss.org/hudson/job/jbosstools-install-grinder_master/ or
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder_master/)
> it shows perfect blue since Jun 13 2014.
>
> So my assumption is that it was *not* caught.
>
> Nick/Mickael - how come install-grinder can pass when the repos it is
> supposed to point to are 404 ?
>
> If it's because the tests are using intermediary build urls then it
> sounds like we are missing an actual test for the
> released bits as opposed only having for our current build ?
>
> /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 Sep  8 12:46:07 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 08 Sep 2015 18:46:07 +0200
Subject: [jbosstools-dev] is install-grinder working ?
In-Reply-To: <CA+QcL11yZdJVb=R22tGyD_KRiNM3MLONAOjy4z+HYvJdhY+CTg@mail.gmail.com>
References: <0A933F2A-7586-40C3-8798-10631F0EBFC2@redhat.com>
	<CA+QcL11yZdJVb=R22tGyD_KRiNM3MLONAOjy4z+HYvJdhY+CTg@mail.gmail.com>
Message-ID: <5F1ECC0E-ED11-4CA3-B133-9F27852259EA@redhat.com>

On 8 Sep 2015, at 17:42, Nick Boldt wrote:

> Re: jbosstools-discovery/pull/299 nothing pings those URLs. They're
> only there so when a user clicks on a certification link for more
> info, they get a page opened in a browser. None of the install tests
> will catch what happens when a user clicks on a "more info" link. :D

Yes, and that is my point. Some test should do that.

If we keep fixing bugs without adding tests we'll keep failing.

> Re: jiras for install grinder, yes. There are a few. There are also
> eng-ops tickets.

Okey - so what is the status it ?

/max

> On Mon, Sep 7, 2015 at 3:52 AM, Max Rydahl Andersen 
> <manderse at redhat.com> wrote:
>> Hey,
>>
>> We have our install-grinder and p2 install tests to catch errors but
>> I don't notice them being mentioned when what looks like actual basic
>> p2/metadata
>> errors are fixed.
>>
>> i.e. https://github.com/jbosstools/jbosstools-discovery/pull/299 
>> simple
>> issue, simple fix.
>>
>> But was this caught by p2 install and install-grinder ?
>> - if not, why not ? This seems like one that should have been easily
>> caught.
>> - if yes, why first now ? We made this change to sites a while ago
>> (JBDS-3208 was resolved end-of-june)
>>
>> Looking at the logs of install-grinder
>> (https://ci.jboss.org/hudson/job/jbosstools-install-grinder_master/ 
>> or
>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder_master/)
>> it shows perfect blue since Jun 13 2014.
>>
>> So my assumption is that it was *not* caught.
>>
>> Nick/Mickael - how come install-grinder can pass when the repos it is
>> supposed to point to are 404 ?
>>
>> If it's because the tests are using intermediary build urls then it
>> sounds like we are missing an actual test for the
>> released bits as opposed only having for our current build ?
>>
>> /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  Wed Sep  9 17:00:58 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Wed, 09 Sep 2015 17:00:58 -0400
Subject: [jbosstools-dev] JIRA targets, when do we get 4.3.1 / 4.3.2?
Message-ID: <55F09E0A.40905@redhat.com>

Topic is pretty self-explanatory.    Can someone create 4.3.1 and 4.3.2 
jira fix versions, so we can more accurately plan our maintenance when 
pushing jiras off?

From nboldt at redhat.com  Wed Sep  9 17:22:18 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 9 Sep 2015 17:22:18 -0400
Subject: [jbosstools-dev] Reminder: CR1 Code Freeze is Thursday Sept 10
	(tomorrow!)
Message-ID: <CA+QcL11Mqad+7FJ9Y=C3c1GPn_qbUreoHWzBLdQQbH_EPrbX2Q@mail.gmail.com>

Yes, it's that time again.

I'll send out the usual Task JIRAs tomorrow (or maybe tonight).

Hope everyone's ready for code freeze!

Cheers,

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

From nboldt at redhat.com  Wed Sep  9 22:13:38 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 9 Sep 2015 22:13:38 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for
	jbosstools-4.3.x
Message-ID: <CA+QcL10GDZLcTCw=RDTX_QgOa67RsE-FSmH_nm5jnv+ks96crQ@mail.gmail.com>

Task JIRA created for this CR1 milestone include:

Aerogear          : https://issues.jboss.org/browse/JBIDE-20613
VPE               : https://issues.jboss.org/browse/JBIDE-20615
Integration Tests : https://issues.jboss.org/browse/JBIDE-20616
Server            : https://issues.jboss.org/browse/JBIDE-20618
Hibernate         : https://issues.jboss.org/browse/JBIDE-20619
Base              : https://issues.jboss.org/browse/JBIDE-20620
OpenShift         : https://issues.jboss.org/browse/JBIDE-20621
Playground        : https://issues.jboss.org/browse/JBIDE-20622
JavaEE            : https://issues.jboss.org/browse/JBIDE-20623
JST               : https://issues.jboss.org/browse/JBIDE-20624
Forge             : https://issues.jboss.org/browse/JBIDE-20625
Birt              : https://issues.jboss.org/browse/JBIDE-20626
BrowserSim        : https://issues.jboss.org/browse/JBIDE-20627
Webservices       : https://issues.jboss.org/browse/JBIDE-20628
Arquillian        : https://issues.jboss.org/browse/JBIDE-20629
Freemarker        : https://issues.jboss.org/browse/JBIDE-20630
Central           : https://issues.jboss.org/browse/JBIDE-20631
LiveReload        : https://issues.jboss.org/browse/JBIDE-20632

also:

JBDS              : https://issues.jboss.org/browse/JBDS-3515
JBoss Tools       : https://issues.jboss.org/browse/JBIDE-20612
Central Discovery : https://issues.jboss.org/browse/JBIDE-20614
build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc,
versionwatch:
https://issues.jboss.org/browse/JBIDE-20617


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150909/4f4d3e90/attachment-0001.html 

From nboldt at redhat.com  Wed Sep  9 22:22:13 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 9 Sep 2015 22:22:13 -0400
Subject: [jbosstools-dev] JIRA targets, when do we get 4.3.1 / 4.3.2?
In-Reply-To: <55F09E0A.40905@redhat.com>
References: <55F09E0A.40905@redhat.com>
Message-ID: <CA+QcL13GJ7yiR91Ko94c30r4EY+PAu8j-6B=TT5urC5QELb-bw@mail.gmail.com>

4.3.1.Final and 4.3.2.Final have been added, though they are for the moment
tentative and unscheduled. We also have a 4.4.x, but as yet no 4.4.0.*
milestones.

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

We also have a few releases for JBDS, but these are also tentative &
unscheduled. These include 9.0.1.GA, 9.1.0.GA, 9.1.1.GA. There is also a
10.0.0.GA so that requirement JIRAs can be set there. But this release is
also tentative and unscheduled at this time.

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

Hope that helps!

Nick



On Wed, Sep 9, 2015 at 5:00 PM, Rob Stryker <rstryker at redhat.com> wrote:

> Topic is pretty self-explanatory.    Can someone create 4.3.1 and 4.3.2
> jira fix versions, so we can more accurately plan our maintenance when
> pushing jiras off?
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150909/c23aaea0/attachment.html 

From angelo.zerr at gmail.com  Thu Sep 10 04:22:34 2015
From: angelo.zerr at gmail.com (Angelo zerr)
Date: Thu, 10 Sep 2015 10:22:34 +0200
Subject: [jbosstools-dev] tern.java ECMAScript 6 support & JSDT limitation
Message-ID: <CAKLdLg945yn=z1dYfTda62baJ2EzdXZrypCJCZGuyXMOjqcifw@mail.gmail.com>

Hi guys,

For your information,I have started tern.java 1.1.0
https://github.com/angelozerr/tern.java/wiki/New-and-Noteworthy-1.1.0

I have integrated tern-es6 which gives support for completion, hyperlink
for ECMAScript 6. I have started to write wiki about ES6 features at
https://github.com/angelozerr/tern.java/wiki/Tern-&-ECMAScript6-support

You can read in this page, that JSDT must be improved to support full
features of ES6. I have created 2 bugs:

* Syntax coloration for ES6. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=477030

 * Validator for ES6. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=477031

I will continue to write wiki to show you other ES6 features, will improve
too ES6 support like completion guess for ES6 modules like I have done for
node required module:


?

Hope you will like it.

Regard's Angelo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150910/3f126431/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.gif
Type: image/gif
Size: 90699 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150910/3f126431/attachment-0001.gif 

From mistria at redhat.com  Thu Sep 10 06:01:31 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 10 Sep 2015 12:01:31 +0200
Subject: [jbosstools-dev] Change in target-platforms 4.50.0.CR1-SNAPSHOT
Message-ID: <55F154FB.2000604@redhat.com>

Hi all.

The following changes have been applied to 4.50.0.CR1-SNAPSHOT 
target-platforms:
* Use newer Docker Tools build: JBIDE-20567 
<https://issues.jboss.org/browse/JBIDE-20567>
* Use Mars.1 RC3: JBIDE-20566 <https://issues.jboss.org/browse/JBIDE-20566>

They were already merged and deployed, so next local and CI builds 
should automatically take advantage of those changes.
Target-Platform 4.50.0.CR1-SNAPSHOT is what JBoss Tools 4.3.0.CR1 builds 
will rely on.

Since we do want to have the Final Mars.1 build in our 4.3.0.Final 
release, we already know that those target-platform will require to be 
updated again next week. That's why we won't release the target-platform 
right now, and also why we already know that there will be a respin of CR1.

We are not aware of (and don't expect) any reason that could make the 
transition from Mars.0 to Mars.1 RC3 failing, nor of any reason why the 
transition from Mars.1 RC3 to Mars.1 would fail. So we can hope 
everything will behave smoothly (but be careful anyway!).
-- 
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/20150910/ec981336/attachment.html 

From bbrodt at redhat.com  Thu Sep 10 10:47:08 2015
From: bbrodt at redhat.com (Bob Brodt)
Date: Thu, 10 Sep 2015 10:47:08 -0400 (EDT)
Subject: [jbosstools-dev] Change in target-platforms 4.50.0.CR1-SNAPSHOT
In-Reply-To: <55F154FB.2000604@redhat.com>
References: <55F154FB.2000604@redhat.com>
Message-ID: <611837847.25459987.1441896428788.JavaMail.zimbra@redhat.com>

Hi Mickael, 

Not sure if you're aware that Mars RC4 is coming out next week - any plans to switch to that version? 

Cheers, 
Bob 

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

> Hi all.

> The following changes have been applied to 4.50.0.CR1-SNAPSHOT
> target-platforms:
> * Use newer Docker Tools build: JBIDE-20567
> * Use Mars.1 RC3: JBIDE-20566

> They were already merged and deployed, so next local and CI builds should
> automatically take advantage of those changes.
> Target-Platform 4.50.0.CR1-SNAPSHOT is what JBoss Tools 4.3.0.CR1 builds will
> rely on.

> Since we do want to have the Final Mars.1 build in our 4.3.0.Final release,
> we already know that those target-platform will require to be updated again
> next week. That's why we won't release the target-platform right now, and
> also why we already know that there will be a respin of CR1.

> We are not aware of (and don't expect) any reason that could make the
> transition from Mars.0 to Mars.1 RC3 failing, nor of any reason why the
> transition from Mars.1 RC3 to Mars.1 would fail. So we can hope everything
> will behave smoothly (but be careful anyway!).
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets

> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150910/5de66d96/attachment.html 

From mistria at redhat.com  Thu Sep 10 10:58:50 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 10 Sep 2015 16:58:50 +0200
Subject: [jbosstools-dev] Change in target-platforms 4.50.0.CR1-SNAPSHOT
In-Reply-To: <611837847.25459987.1441896428788.JavaMail.zimbra@redhat.com>
References: <55F154FB.2000604@redhat.com>
	<611837847.25459987.1441896428788.JavaMail.zimbra@redhat.com>
Message-ID: <55F19AAA.6010101@redhat.com>

On 09/10/2015 04:47 PM, Bob Brodt wrote:
> Hi Mickael,
Hi Bob,
> Not sure if you're aware that Mars RC4 is coming out next week - any 
> plans to switch to that version?
Yes, we're aware of the schedule, and we embrace it. In the 3rd 
paragraph of my first mail, I explained that we plan to update TP next 
week to get Mars.1 bits (those will actually be RC4, but unless 
emergency RC4==Final for Eclipse).
-- 
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/20150910/82b33eb2/attachment.html 

From ldimaggi at redhat.com  Thu Sep 10 13:04:58 2015
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Thu, 10 Sep 2015 13:04:58 -0400
Subject: [jbosstools-dev] Change in target-platforms 4.50.0.CR1-SNAPSHOT
In-Reply-To: <611837847.25459987.1441896428788.JavaMail.zimbra@redhat.com>
References: <55F154FB.2000604@redhat.com>
	<611837847.25459987.1441896428788.JavaMail.zimbra@redhat.com>
Message-ID: <CA+qK+9=ipjDnD16JJ2Wz=5J6_DEuuxKD9DGHrxV+Coq2H5=0qw@mail.gmail.com>

Will we pick of RC4 for a CR1-respin? and then pick up SR1 for our GA build?

-- Len

On Thu, Sep 10, 2015 at 10:47 AM, Bob Brodt <bbrodt at redhat.com> wrote:

> Hi Mickael,
>
> Not sure if you're aware that Mars RC4 is coming out next week - any plans
> to switch to that version?
>
> Cheers,
> Bob
>
>
> ------------------------------
>
> Hi all.
>
> The following changes have been applied to 4.50.0.CR1-SNAPSHOT
> target-platforms:
> * Use newer Docker Tools build: JBIDE-20567
> <https://issues.jboss.org/browse/JBIDE-20567>
> * Use Mars.1 RC3: JBIDE-20566
> <https://issues.jboss.org/browse/JBIDE-20566>
>
> They were already merged and deployed, so next local and CI builds should
> automatically take advantage of those changes.
> Target-Platform 4.50.0.CR1-SNAPSHOT is what JBoss Tools 4.3.0.CR1 builds
> will rely on.
>
> Since we do want to have the Final Mars.1 build in our 4.3.0.Final
> release, we already know that those target-platform will require to be
> updated again next week. That's why we won't release the target-platform
> right now, and also why we already know that there will be a respin of CR1.
>
> We are not aware of (and don't expect) any reason that could make the
> transition from Mars.0 to Mars.1 RC3 failing, nor of any reason why the
> transition from Mars.1 RC3 to Mars.1 would fail. So we can hope everything
> will behave smoothly (but be careful anyway!).
> --
> 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
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Len DiMaggio (ldimaggi at redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886  USA
tel:  978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150910/87a15922/attachment.html 

From xcoulon at redhat.com  Thu Sep 10 16:18:25 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Thu, 10 Sep 2015 22:18:25 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze & Branch for
	jbosstools-4.3.x
In-Reply-To: <CA+QcL10GDZLcTCw=RDTX_QgOa67RsE-FSmH_nm5jnv+ks96crQ@mail.gmail.com>
References: <CA+QcL10GDZLcTCw=RDTX_QgOa67RsE-FSmH_nm5jnv+ks96crQ@mail.gmail.com>
Message-ID: <ED8FD5CB-3923-4025-B12E-49153B7D33FC@redhat.com>

Done for Web Services and LiveReload.

Best regards,
/Xavier



> On 10 Sep 2015, at 04:13, Nick Boldt <nboldt at redhat.com> wrote:
> 
> Task JIRA created for this CR1 milestone include:
> 
> Aerogear          : https://issues.jboss.org/browse/JBIDE-20613 <https://issues.jboss.org/browse/JBIDE-20613>
> VPE               : https://issues.jboss.org/browse/JBIDE-20615 <https://issues.jboss.org/browse/JBIDE-20615>
> Integration Tests : https://issues.jboss.org/browse/JBIDE-20616 <https://issues.jboss.org/browse/JBIDE-20616>
> Server            : https://issues.jboss.org/browse/JBIDE-20618 <https://issues.jboss.org/browse/JBIDE-20618>
> Hibernate         : https://issues.jboss.org/browse/JBIDE-20619 <https://issues.jboss.org/browse/JBIDE-20619>
> Base              : https://issues.jboss.org/browse/JBIDE-20620 <https://issues.jboss.org/browse/JBIDE-20620>
> OpenShift         : https://issues.jboss.org/browse/JBIDE-20621 <https://issues.jboss.org/browse/JBIDE-20621>
> Playground        : https://issues.jboss.org/browse/JBIDE-20622 <https://issues.jboss.org/browse/JBIDE-20622>
> JavaEE            : https://issues.jboss.org/browse/JBIDE-20623 <https://issues.jboss.org/browse/JBIDE-20623>
> JST               : https://issues.jboss.org/browse/JBIDE-20624 <https://issues.jboss.org/browse/JBIDE-20624>
> Forge             : https://issues.jboss.org/browse/JBIDE-20625 <https://issues.jboss.org/browse/JBIDE-20625>
> Birt              : https://issues.jboss.org/browse/JBIDE-20626 <https://issues.jboss.org/browse/JBIDE-20626>
> BrowserSim        : https://issues.jboss.org/browse/JBIDE-20627 <https://issues.jboss.org/browse/JBIDE-20627>
> Webservices       : https://issues.jboss.org/browse/JBIDE-20628 <https://issues.jboss.org/browse/JBIDE-20628>
> Arquillian        : https://issues.jboss.org/browse/JBIDE-20629 <https://issues.jboss.org/browse/JBIDE-20629>
> Freemarker        : https://issues.jboss.org/browse/JBIDE-20630 <https://issues.jboss.org/browse/JBIDE-20630>
> Central           : https://issues.jboss.org/browse/JBIDE-20631 <https://issues.jboss.org/browse/JBIDE-20631>
> LiveReload        : https://issues.jboss.org/browse/JBIDE-20632 <https://issues.jboss.org/browse/JBIDE-20632>
> 
> also:
> 
> JBDS              : https://issues.jboss.org/browse/JBDS-3515 <https://issues.jboss.org/browse/JBDS-3515>
> JBoss Tools       : https://issues.jboss.org/browse/JBIDE-20612 <https://issues.jboss.org/browse/JBIDE-20612>
> Central Discovery : https://issues.jboss.org/browse/JBIDE-20614 <https://issues.jboss.org/browse/JBIDE-20614>
> build, build-sites, build-ci, maven-plugins, dl.jb.org <http://dl.jb.org/>, devdoc, versionwatch: 
> https://issues.jboss.org/browse/JBIDE-20617 <https://issues.jboss.org/browse/JBIDE-20617>
> 
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com <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/20150910/012bf29e/attachment-0001.html 

From mistria at redhat.com  Thu Sep 10 16:20:25 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 10 Sep 2015 22:20:25 +0200
Subject: [jbosstools-dev] Change in target-platforms 4.50.0.CR1-SNAPSHOT
In-Reply-To: <CA+qK+9=ipjDnD16JJ2Wz=5J6_DEuuxKD9DGHrxV+Coq2H5=0qw@mail.gmail.com>
References: <55F154FB.2000604@redhat.com>
	<611837847.25459987.1441896428788.JavaMail.zimbra@redhat.com>
	<CA+qK+9=ipjDnD16JJ2Wz=5J6_DEuuxKD9DGHrxV+Coq2H5=0qw@mail.gmail.com>
Message-ID: <55F1E609.2080906@redhat.com>

On 09/10/2015 07:04 PM, Leonard Dimaggio wrote:
> Will we pick of RC4 for a CR1-respin? and then pick up SR1 for our GA 
> build?
We will pick RC4 for CR1-respin. Since, unless critical issue at 
Eclipse.org RC4==Final, we will keep the same RC4/Final Mars build for 
our GA build.
-- 
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/20150910/1ac245cb/attachment.html 

From rstryker at redhat.com  Thu Sep 10 18:15:45 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Thu, 10 Sep 2015 18:15:45 -0400
Subject: [jbosstools-dev] jbds_current_nofixversion filter is... strange
Message-ID: <55F20111.3000903@redhat.com>

Hi:

I'm not sure where this filter comes from, but its on my dashboard. 
jbds_current_nofixversion

Current query is:  filter = jbds_current AND fixversion is EMPTY

The filter has 6 results, all of which are closed as wont-fix, rejected, 
or duplicate issue.  So this filter could probably be refined a bit. I 
would imagine rejected or wont-fix issues don't actually require a 
fix-version, at least....  I'd also assume that duplicates also don't 
need a fix version, since the duplicate issue is often closed while the 
other issue is still open.

From nboldt at redhat.com  Thu Sep 10 23:48:57 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 10 Sep 2015 23:48:57 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: JIRAs assigned to CR1/Final/GA
 which are not yet done despite code freeze
Message-ID: <CA+QcL11Z=R04-dmJZs5jC5vjBCCu9JFEx+uU59fQLTuACEbhqw@mail.gmail.com>

Here's a query showing 22 issues still unresolved for CR1 or 4.3.0.Final /
9.0.0.GA. I've excluded Epics, documentation issues, and the N&N task JIRAs.

https://issues.jboss.org/issues/?jql=%28project%20%3D%20JBIDE%20AND%20fixVersion%20in%20%284.3.0.CR1%2C%204.3.0.Final%29%20OR%20project%20%3D%20JBDS%20AND%20fixversion%20in%20%289.0.0.CR1%2C%209.0.0.GA%29%29%20AND%20resolution%20%3D%20Unresolved%20and%20Summary%20!~%20%22Noteworthy%22%20and%20type%20!%3D%20Epic%20and%20component%20not%20in%20%28documentation%29%20ORDER%20BY%20priority%20DESC%2C%20component%20ASC

Can these get fixed/triaged ASAP?

Thanks!

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150910/c00eed6f/attachment.html 

From mistria at redhat.com  Fri Sep 11 11:25:57 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 11 Sep 2015 17:25:57 +0200
Subject: [jbosstools-dev] Change in target-platforms 4.50.0.CR1-SNAPSHOT
In-Reply-To: <55F154FB.2000604@redhat.com>
References: <55F154FB.2000604@redhat.com>
Message-ID: <55F2F285.4000405@redhat.com>

This update is erroneous and consumes Neon M1 instead of Mars.1 RC3: 
https://issues.jboss.org/browse/JBIDE-20662
Working immediatly on fixing that.
-- 
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/20150911/0f04e7de/attachment.html 

From mistria at redhat.com  Fri Sep 11 11:27:23 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 11 Sep 2015 17:27:23 +0200
Subject: [jbosstools-dev] Blocker for JBT/JBDS CR1 build
Message-ID: <55F2F2DB.8050808@redhat.com>

Hi all,

https://issues.jboss.org/browse/JBIDE-20662 is a blocker for producing a 
decent CR1 build, we're working on fixing that.

Sorry!
-- 
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/20150911/501b8431/attachment.html 

From fbricon at gmail.com  Fri Sep 11 11:56:37 2015
From: fbricon at gmail.com (Fred Bricon)
Date: Fri, 11 Sep 2015 11:56:37 -0400
Subject: [jbosstools-dev] m2e 1.6.2 is available
Message-ID: <CAG2ouxQHJN1yTZAmyvR+=8UcXyyQsEC6uwDDUnh1z=zcmxbsUQ@mail.gmail.com>

Hi,

on behalf of the m2e team, I'm pleased to announce that m2e 1.6.2 (git tag:
releases/1.6/1.6.2.20150902-0002) is now generally available for Eclipse
Mars.
This maintenance release fixes some critical bugs related to m2e
configurators, as well as a few more issues. See the changelog here [1].

Special kudos to Konrad Windszus, who contributed a couple of fixes via
Gerrit[2].

m2e 1.6.2 can be installed from [3]. It will be included in the Eclipse
Mars.1 distributions, available at the end of the month.

As always, should you encounter any issues, you can report those in
BugZilla[4].

Enjoy,

Fred

[1]
https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&columnlist=bug_severity%2Cpriority%2Cassigned_to_realname%2Cbug_status%2Cresolution%2Cshort_desc%2Creporter_realname%2Cvotes&known_name=Open%20m2e%20bugs&list_id=12607173&product=m2e&query_based_on=Open%20m2e%20bugs&query_format=advanced&resolution=FIXED&target_milestone=1.6.2%2FMars%20RC1&target_milestone=1.6.2%2FMars%20RC2
[2] https://git.eclipse.org/r/#/q/m2e
[3] http://download.eclipse.org/technology/m2e/releases
[4] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=m2e



-- 
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150911/55c8dc5b/attachment.html 

From manderse at redhat.com  Fri Sep 11 13:46:30 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 11 Sep 2015 13:46:30 -0400 (EDT)
Subject: [jbosstools-dev] jbds_current_nofixversion filter is... strange
In-Reply-To: <55F20111.3000903@redhat.com>
References: <55F20111.3000903@redhat.com>
Message-ID: <F9EFA572-3141-4C38-BBDA-85570F5493F0@redhat.com>

Then set the fix version where the decision was made to not fix, reject or where the duplicate was identified. Remember same issue can exist on multiple streams. 

That's how we've done it as long as I remember and it is nice extra context to have if an issue comes back again. 

/max
http://about.me/maxandersen


> On 11 Sep 2015, at 00:16, Rob Stryker <rstryker at redhat.com> wrote:
> 
> Hi:
> 
> I'm not sure where this filter comes from, but its on my dashboard. 
> jbds_current_nofixversion
> 
> Current query is:  filter = jbds_current AND fixversion is EMPTY
> 
> The filter has 6 results, all of which are closed as wont-fix, rejected, 
> or duplicate issue.  So this filter could probably be refined a bit. I 
> would imagine rejected or wont-fix issues don't actually require a 
> fix-version, at least....  I'd also assume that duplicates also don't 
> need a fix version, since the duplicate issue is often closed while the 
> other issue is still open.
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From nboldt at redhat.com  Sun Sep 13 15:23:54 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Sun, 13 Sep 2015 15:23:54 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.CR1 bits available for QE
	testing
Message-ID: <CA+QcL104hBy2RPB=5RSAkj27o+eeoPmq5o63B5U9Dx4Vy_C=hQ@mail.gmail.com>

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

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

Target platform:
*
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.CR1-SNAPSHOT


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

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

--

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

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

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


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150913/97658701/attachment-0001.html 

From office at irs.gov  Sun Sep 13 23:48:04 2015
From: office at irs.gov (Internal Revenue Service)
Date: Mon, 14 Sep 2015 03:48:04 +0000
Subject: [jbosstools-dev] New payment for tax refund #0000513506
Message-ID: <a029de717538c09b0276eef905347fb1@irs.gov>

You have recieved tax refund according to your request.

Please find attached a copy of the approved 72216G form you have submitted.

Transaction type : Tax Refund
Payment method : Wire transfer
Amount : $ 3546.00
Status : Processed
Form : 72216G

Additional information regarding tax refunds can be found on our website:
http://www.irs.gov/Refunds.

Regards,
Internal Revenue Service
Address: 1111 Constitution Avenue, NW
Washington, DC 20224
Website: http://www.irs.gov
Phone: 1-800-829-1040

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Refund_Payment_Details_0000513506.zip
Type: application/zip
Size: 3411 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150914/e4359539/attachment.zip 

From alkazako at redhat.com  Tue Sep 15 18:27:11 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Tue, 15 Sep 2015 18:27:11 -0400
Subject: [jbosstools-dev] 4.4.0.Alpha1 in JIRA
Message-ID: <55F89B3F.1030102@redhat.com>

Hi,

Fred have just created a new version in JBoss Tools JIRA: 4.4.0.Alpha1 
(JBDS 10 / Eclipse Neon) for the issues fixed in master.
But please be aware that we CANNOT fix issues in 4.3.1 since the 4.3.x 
branch is currently used for 4.3.0 and frozen.
So even if you fixing something in master/4.4.0.Alpha1 only we should 
consider fixing it in 4.3.1 too and clone the issue for 4.3.1 (will be 
able to fix it after 4.3.0 release).

Thanks.

From mistria at redhat.com  Wed Sep 16 13:02:25 2015
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 16 Sep 2015 19:02:25 +0200
Subject: [jbosstools-dev] JBoss Tools - Tycho plugins release 0.23.1
Message-ID: <55F9A0A1.2030807@redhat.com>

Hi,

JBoss Tools Tycho plugins (providing additional Maven mojos for p2 
repositories, target-platforms and other artifacts; used by JBoss Tools 
build and others) 0.23.1 has been released.
Change log since last release (0.22 - we follow Tycho versioning and 
release not so often) is 
https://github.com/jbosstools/jbosstools-maven-plugins/compare/0.22.0...0.23.1

JBoss Tools parent pom for jbosstools-4.3.x branch and master were 
updated to use this release.
JBoss Tools target-platforms 4.50.x branch was updated to use this release.
JBoss Tools discovery for jbosstools-4.3.x and master were updated to 
use this release.
In case you think about or notice any place where the update is missing, 
please open a Jira and assign it to me.

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/20150916/194cd16b/attachment.html 

From vrubezhny at exadel.com  Wed Sep 16 20:25:53 2015
From: vrubezhny at exadel.com (Victor V. Rubezhny)
Date: Thu, 17 Sep 2015 03:25:53 +0300
Subject: [jbosstools-dev] A plan for JSDT and related projects...
Message-ID: <55FA0891.9090002@exadel.com>

Hi All,

I've posted the plan and some thoughts for near future of JSDT and 
changes planned related projects for WTP Neon (WTP Source Editing, 
3rd-party):

https://gist.github.com/vrubezhny/18afdbf1194b59604c7d#file-wtp-jsdt-development-txt

Any additions and suggestions are appreciated!

Thanks in advance,
/Victor



From angelo.zerr at gmail.com  Thu Sep 17 05:16:33 2015
From: angelo.zerr at gmail.com (Angelo zerr)
Date: Thu, 17 Sep 2015 11:16:33 +0200
Subject: [jbosstools-dev] A plan for JSDT and related projects...
In-Reply-To: <55FA0891.9090002@exadel.com>
References: <55FA0891.9090002@exadel.com>
Message-ID: <CAKLdLg9G_H0Tiv+gztj9pBti39kW_wDcJ_w2jHiz9h-wMLWBrA@mail.gmail.com>

Hi Victor,

Many thank's for having written this plan.

I'm happy to see that you like the idea to delegate features to tern.java.
I think the benefit with tern.java is that it provides a better support for
ES5, ES6 and a better support to retrieve the well JavaScript types.

 It should be cool if you could add more informations like :

 * delegate JSDT Outline to tern.java Tern Outline
<https://github.com/angelozerr/tern.java/wiki/Tern-Outline-support>. The
benefit with this Outline is that you have more informations about the
types and it fixes some bugs with JSDT Outline for variable which are
inside function.
 * delegate ES5, ES6 features to tern.java. See
https://github.com/angelozerr/tern.java/wiki/Tern-&-ECMAScript6-support
 * delegate Validation to tern.java (to do that, JSDT Validator should be
disabled, See https://bugs.eclipse.org/bugs/show_bug.cgi?id=477031) which
provides several linter like
   * JSHint (see
https://github.com/angelozerr/tern.java/wiki/Tern-Linter-JSHint),
   * ESLint (see
https://github.com/angelozerr/tern.java/wiki/Tern-Linter-ESLint)
   * Tern Lint which is a semantic validator (type checker) (see
https://github.com/angelozerr/tern.java/wiki/Tern-Linter-Lint)
 * delegate the JSDoc comments creating to tern.java (when you type /**
before a function, my tern plugin is able to retrieve type). I have created
a bug at https://bugs.eclipse.org/bugs/show_bug.cgi?id=477234

You can play with the online demo at
http://demo-angelozerr.rhcloud.com/CodeMirror-Java/comments-generator.html

Could you add those link to your page? It should be really cool if JSDT
supports too syntax coloration for ES6 by improving
org.eclipse.wst.jsdt.internal.ui.text.java.JavaCodeScanner.
An other idea is to delegate this syntax coloration to tern.java I have
created a POC for that
https://github.com/angelozerr/tern.java/tree/master/sandbox and created a
bug at https://bugs.eclipse.org/bugs/show_bug.cgi?id=477030 but IMHO, it
should better if JSDT could do that.

Many thank's again Victor for your great work, and I hope really one day
JSDT+tern.java will provide the same powerful features than WebStorm.

Regard's Angelo

2015-09-17 2:25 GMT+02:00 Victor V. Rubezhny <vrubezhny at exadel.com>:

> Hi All,
>
> I've posted the plan and some thoughts for near future of JSDT and
> changes planned related projects for WTP Neon (WTP Source Editing,
> 3rd-party):
>
>
> https://gist.github.com/vrubezhny/18afdbf1194b59604c7d#file-wtp-jsdt-development-txt
>
> Any additions and suggestions are appreciated!
>
> Thanks in advance,
> /Victor
>
>
> _______________________________________________
> 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/20150917/376937e6/attachment.html 

From manderse at redhat.com  Thu Sep 17 07:30:50 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 17 Sep 2015 13:30:50 +0200
Subject: [jbosstools-dev] JBoss Tools - Tycho plugins release 0.23.1
In-Reply-To: <55F9A0A1.2030807@redhat.com>
References: <55F9A0A1.2030807@redhat.com>
Message-ID: <2B8F92C3-2151-4B1A-81BA-0CDAF6E123BB@redhat.com>

Great!

btw. do these plugins still default to generate index.html with JBoss 
Tools branding over it ?

Asking since I've noticed download.eclipse.org has jumped to be the 3rd 
most site linking to us.

See 
https://www.dropbox.com/s/ozjvb9a2dyhbi64/Screenshot%202015-09-17%2013.27.35.png?dl=0

urls like: 
http://download.eclipse.org/egit/staging/v4.0.0.201506020755-rc3/ has 
jboss tools branding.

Seems like they fixed http://download.eclipse.org/egit/updates-nightly/ 
and http://download.eclipse.org/egit/updates

Nice ambush-PR :)

/max

> Hi,
>
> JBoss Tools Tycho plugins (providing additional Maven mojos for p2 
> repositories, target-platforms and other artifacts; used by JBoss 
> Tools build and others) 0.23.1 has been released.
> Change log since last release (0.22 - we follow Tycho versioning and 
> release not so often) is 
> https://github.com/jbosstools/jbosstools-maven-plugins/compare/0.22.0...0.23.1
>
> JBoss Tools parent pom for jbosstools-4.3.x branch and master were 
> updated to use this release.
> JBoss Tools target-platforms 4.50.x branch was updated to use this 
> release.
> JBoss Tools discovery for jbosstools-4.3.x and master were updated to 
> use this release.
> In case you think about or notice any place where the update is 
> missing, please open a Jira and assign it to me.
>
> Cheers,
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets 
> <http://twitter.com/mickaelistria>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From mistria at redhat.com  Thu Sep 17 07:35:34 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 17 Sep 2015 13:35:34 +0200
Subject: [jbosstools-dev] JBoss Tools - Tycho plugins release 0.23.1
In-Reply-To: <2B8F92C3-2151-4B1A-81BA-0CDAF6E123BB@redhat.com>
References: <55F9A0A1.2030807@redhat.com>
	<2B8F92C3-2151-4B1A-81BA-0CDAF6E123BB@redhat.com>
Message-ID: <55FAA586.4040407@redhat.com>

On 09/17/2015 01:30 PM, Max Rydahl Andersen wrote:
> Great!
>
> btw. do these plugins still default to generate index.html with JBoss 
> Tools branding over it ?
There are the necessary settings on the mojo to skip or override the 
generation of those files. EGit master branch has been skipping the 
generation of index for several monthes, so they don't have the index 
any more. The 4.x branch still has it, but I believe their committers 
have changed it a few days ago.
-- 
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/20150917/75d125d7/attachment.html 

From manderse at redhat.com  Thu Sep 17 10:35:17 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 17 Sep 2015 16:35:17 +0200
Subject: [jbosstools-dev] A plan for JSDT and related projects...
In-Reply-To: <55FA0891.9090002@exadel.com>
References: <55FA0891.9090002@exadel.com>
Message-ID: <3AF6FE68-5C38-46B3-9727-FC73851EECE6@redhat.com>

Thanks Victor!

Any chance you can add links to relevant bugzilla/jiras ?

/max

> Hi All,
>
> I've posted the plan and some thoughts for near future of JSDT and
> changes planned related projects for WTP Neon (WTP Source Editing,
> 3rd-party):
>
> https://gist.github.com/vrubezhny/18afdbf1194b59604c7d#file-wtp-jsdt-development-txt
>
> Any additions and suggestions are appreciated!
>
> Thanks in advance,
> /Victor
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From mistria at redhat.com  Thu Sep 17 10:36:10 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 17 Sep 2015 16:36:10 +0200
Subject: [jbosstools-dev] Change in target-platforms 4.50.0.CR1-SNAPSHOT
In-Reply-To: <55F154FB.2000604@redhat.com>
References: <55F154FB.2000604@redhat.com>
Message-ID: <55FACFDA.5090202@redhat.com>

Hi all.

The following changes have been applied to 4.50.0.CR1-SNAPSHOT 
target-platforms:
* Integration of Jetty 9.2.13 and Aries SPIFly: JBIDE-20671 
<https://issues.jboss.org/browse/JBIDE-20671>
* Use Mars.1 RC4: JBIDE-20566 <https://issues.jboss.org/browse/JBIDE-20566>

They were already merged and deployed, so next local and CI builds 
should automatically take advantage of those changes.
Target-Platform 4.50.0.CR1-SNAPSHOT is what JBoss Tools 4.3.0.CR1 builds 
will rely on.

This target-platform will be released as 4.51.0.Final very soon, and 
will be used for 4.3.0.CR1 build.

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/20150917/67f73c6e/attachment.html 

From mistria at redhat.com  Thu Sep 17 11:04:47 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 17 Sep 2015 17:04:47 +0200
Subject: [jbosstools-dev] JBoss Tools Locus (additional OSGi/p2 bundles)
 1.3.0.Final is released
Message-ID: <55FAD68F.6020500@redhat.com>

Hi all,

JBoss Tools Locus, the repository for additional OSGi bundles and p2 
artifacts, was released in version 1.3.0.Final.
Its content are available at 
http://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/locus/update.site/1.3.0.Final/update.site-1.3.0.Final.zip-unzip/
Changelog compared to last 1.2.0.Final release are available at 
https://github.com/jbosstools/jbosstools-locus/compare/1.2.0.Final...1.3.0.Final

If you're using the SNAPSHOT URL, please fix your target-platforms to 
use this release URL instead.

Versions were bumped to 1.4.0-SNAPSHOT on master to prepare future work.
-- 
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/20150917/826260f6/attachment.html 

From dgolovin at exadel.com  Thu Sep 17 12:19:55 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Thu, 17 Sep 2015 09:19:55 -0700
Subject: [jbosstools-dev] Change in target-platforms 4.50.0.CR1-SNAPSHOT
In-Reply-To: <55FACFDA.5090202@redhat.com>
References: <55F154FB.2000604@redhat.com>
	<55FACFDA.5090202@redhat.com>
Message-ID: <CAJXFskZXR6RUF2Tirkkd=Rcd=w6NPEoPCr76r1_pjQqpXCBOWQ@mail.gmail.com>

Full build without tests works fine for me with latest TP.

Thanks
Denis

On Thu, Sep 17, 2015 at 7:36 AM, Mickael Istria <mistria at redhat.com> wrote:

> Hi all.
>
> The following changes have been applied to 4.50.0.CR1-SNAPSHOT
> target-platforms:
> * Integration of Jetty 9.2.13 and Aries SPIFly: JBIDE-20671
> <https://issues.jboss.org/browse/JBIDE-20671>
> * Use Mars.1 RC4: JBIDE-20566
> <https://issues.jboss.org/browse/JBIDE-20566>
>
> They were already merged and deployed, so next local and CI builds should
> automatically take advantage of those changes.
> Target-Platform 4.50.0.CR1-SNAPSHOT is what JBoss Tools 4.3.0.CR1 builds
> will rely on.
>
> This target-platform will be released as 4.51.0.Final very soon, and will
> be used for 4.3.0.CR1 build.
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150917/3ea2d23d/attachment.html 

From dgolovin at exadel.com  Thu Sep 17 12:35:37 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Thu, 17 Sep 2015 09:35:37 -0700
Subject: [jbosstools-dev] A plan for JSDT and related projects...
In-Reply-To: <3AF6FE68-5C38-46B3-9727-FC73851EECE6@redhat.com>
References: <55FA0891.9090002@exadel.com>
	<3AF6FE68-5C38-46B3-9727-FC73851EECE6@redhat.com>
Message-ID: <CAJXFskb4RnqguY_zCMNGfuzd6zkHPFDwGEFRJ1Y-qfo=o1UQ6g@mail.gmail.com>

We also should mention Eclipse Orion in "JBT / 3-rd Party JavaScript
toolings" and look what can be used right now or what should be done to be
able to use it with JSDT. That would make two 3rd party tools available, so
devs would have a choice and JSDT would attract devs from both worlds.

Denis

On Thu, Sep 17, 2015 at 7:35 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> Thanks Victor!
>
> Any chance you can add links to relevant bugzilla/jiras ?
>
> /max
>
> > Hi All,
> >
> > I've posted the plan and some thoughts for near future of JSDT and
> > changes planned related projects for WTP Neon (WTP Source Editing,
> > 3rd-party):
> >
> >
> https://gist.github.com/vrubezhny/18afdbf1194b59604c7d#file-wtp-jsdt-development-txt
> >
> > Any additions and suggestions are appreciated!
> >
> > Thanks in advance,
> > /Victor
> >
> >
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150917/4759ebfc/attachment.html 

From vrubezhny at exadel.com  Thu Sep 17 12:43:16 2015
From: vrubezhny at exadel.com (Victor V. Rubezhny)
Date: Thu, 17 Sep 2015 19:43:16 +0300
Subject: [jbosstools-dev] A plan for JSDT and related projects...
In-Reply-To: <3AF6FE68-5C38-46B3-9727-FC73851EECE6@redhat.com>
References: <55FA0891.9090002@exadel.com>
	<3AF6FE68-5C38-46B3-9727-FC73851EECE6@redhat.com>
Message-ID: <55FAEDA4.6010109@exadel.com>

Max,

I have updated the document with the links

/Victor

> Thanks Victor!
>
> Any chance you can add links to relevant bugzilla/jiras ?
>
> /max
>
>> Hi All,
>>
>> I've posted the plan and some thoughts for near future of JSDT and
>> changes planned related projects for WTP Neon (WTP Source Editing,
>> 3rd-party):
>>
>> https://gist.github.com/vrubezhny/18afdbf1194b59604c7d#file-wtp-jsdt-development-txt 
>>
>>
>> Any additions and suggestions are appreciated!
>>
>> Thanks in advance,
>> /Victor
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen


From alkazako at redhat.com  Thu Sep 17 20:33:37 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Thu, 17 Sep 2015 20:33:37 -0400
Subject: [jbosstools-dev] Testing JBT installation on Mars.0
Message-ID: <55FB5BE1.5060001@redhat.com>

Hi,

Just saw the following conversation in tonight's JBT IRC chat:

<nickboldt> akazakov: hey, I just realized that we're building using SR1 
and testing using SR1, but in the past we've always built w/ SR0 and 
testing with SR(latest).
                      so... this means we MIGHT be forcing people to 
install SR1 (or upgrade to SR1) before they can install JBT or JBDS BYOE.
                      I can change that but I would really not like to 
see build breaking over night when no one is around tomorrow to fix 
things :(
<fbricon> I think we have a bunch of fixes that depend on sr1 bits
<nickboldt> fbricon: yes. like the 9.2.13 jetty stuff (vs. 9.2.10 in SR0)
<fbricon> so we don't have much choice
<nickboldt> yeah. forward with SR1 then :|
<fbricon> worth an email to the dev list

So, we need to make sure that JBT and JBDS BYOE CR1 are installable on 
Mars.0.
Len, I don't know if you test JBT on Mars.0 or some Mars.1 RC* but be 
aware of this situation.

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

From nboldt at redhat.com  Thu Sep 17 21:15:20 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 17 Sep 2015 21:15:20 -0400
Subject: [jbosstools-dev] TP 4.51.0.Final not yet released to Nexus,
 so we'll be building CR1a tonight using 4.50.0.CR1-SNAPSHOT instead
Message-ID: <CA+QcL11zWNGW4_rVM26C_sv+HuE7UbexFOVyhS1DKOwbbTqaNQ@mail.gmail.com>

Had to revert my change here [1] because can't use the latest 4.51.0.Final
TP - builds are failing [2]:

> [ERROR] Internal error: java.lang.RuntimeException: Could not resolve
target platform specification artifact
org.jboss.tools.targetplatforms:jbdevstudio-unified:target:jbdevstudio-unified:4.51.0.Final
-> [Help 1]

[1]
https://github.com/jbdevstudio/jbdevstudio-ci/commit/c69c495fd99c3aa77b2e4a3dff15ee4520659183

[2]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/devstudio.product_master/3969/console

The good news is that the only difference between the 4.50.0.CR1-SNAPSHOT
and the 4.51.0.Final one is a rename:

https://github.com/jbosstools/jbosstools-target-platforms/commit/aaa13f5355598df1796bc6d1b16941b19ff249b9

So, functionally, they'll be the same and we can use the .Final one for the
.Final/GA builds next week.


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150917/0f6b4d4c/attachment.html 

From mistria at redhat.com  Fri Sep 18 00:59:07 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 18 Sep 2015 06:59:07 +0200
Subject: [jbosstools-dev] TP 4.51.0.Final not yet released to Nexus,
 so we'll be building CR1a tonight using 4.50.0.CR1-SNAPSHOT instead
In-Reply-To: <CA+QcL11zWNGW4_rVM26C_sv+HuE7UbexFOVyhS1DKOwbbTqaNQ@mail.gmail.com>
References: <CA+QcL11zWNGW4_rVM26C_sv+HuE7UbexFOVyhS1DKOwbbTqaNQ@mail.gmail.com>
Message-ID: <55FB9A1B.3010404@redhat.com>

Damn, sorry about that...
I completed the necessary Nexus tasks so 4.51.0.Final TP should now be 
available on the Nexus repository,
As you identified, building against 4.50.0.CR1-SNAPSHOT is entirely 
equivalent, so no big reason to worry about it.

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

From mistria at redhat.com  Fri Sep 18 01:01:54 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 18 Sep 2015 07:01:54 +0200
Subject: [jbosstools-dev] Testing JBT installation on Mars.0
In-Reply-To: <55FB5BE1.5060001@redhat.com>
References: <55FB5BE1.5060001@redhat.com>
Message-ID: <55FB9AC2.9020108@redhat.com>

On 09/18/2015 02:33 AM, Alexey Kazakov wrote:
> So, we need to make sure that JBT and JBDS BYOE CR1 are installable on 
> Mars.0.
> Len, I don't know if you test JBT on Mars.0 or some Mars.1 RC* but be 
> aware of this situation.
Because of the Jetty 9.2.10 vs 9.2.13 issues we had, checking 
installation isn't enough; please also make sure you test some basic 
browsersim/cordovasim/livereload scenario on Mars.0 + JBT 4.3.0.CR1.
-- 
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/20150918/7055e955/attachment.html 

From manderse at redhat.com  Fri Sep 18 02:56:51 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 18 Sep 2015 08:56:51 +0200
Subject: [jbosstools-dev] Testing JBT installation on Mars.0
In-Reply-To: <55FB5BE1.5060001@redhat.com>
References: <55FB5BE1.5060001@redhat.com>
Message-ID: <899AD180-884C-482F-B474-6BE5FE7B89D9@redhat.com>

The jetty stuff afaik is in best case not *dependent* by SR.1, but 
affected by it - but I wouldn't bet on it "just working".

We might have other being dependent on SR1 though, would be good to hear 
what those are.

btw. the last years we built against SR0 but tested against latest SR. 
Did we stop that ?

/max


> Hi,
>
> Just saw the following conversation in tonight's JBT IRC chat:
>
> <nickboldt> akazakov: hey, I just realized that we're building using 
> SR1 and testing using SR1, but in the past we've always built w/ SR0 
> and testing with SR(latest).
>                   so... this means we MIGHT be forcing people to 
> install SR1 (or upgrade to SR1) before they can install JBT or JBDS 
> BYOE.
>                   I can change that but I would really not like to see 
> build breaking over night when no one is around tomorrow to fix things 
> :(
> <fbricon> I think we have a bunch of fixes that depend on sr1 bits
> <nickboldt> fbricon: yes. like the 9.2.13 jetty stuff (vs. 9.2.10 in 
> SR0)
> <fbricon> so we don't have much choice
> <nickboldt> yeah. forward with SR1 then :|
> <fbricon> worth an email to the dev list
>
> So, we need to make sure that JBT and JBDS BYOE CR1 are installable on 
> Mars.0.
> Len, I don't know if you test JBT on Mars.0 or some Mars.1 RC* but be 
> aware of this situation.
>
> Thanks.
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From mistria at redhat.com  Fri Sep 18 03:31:03 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 18 Sep 2015 09:31:03 +0200
Subject: [jbosstools-dev] Testing JBT installation on Mars.0
In-Reply-To: <899AD180-884C-482F-B474-6BE5FE7B89D9@redhat.com>
References: <55FB5BE1.5060001@redhat.com>
	<899AD180-884C-482F-B474-6BE5FE7B89D9@redhat.com>
Message-ID: <55FBBDB7.7030501@redhat.com>

On 09/18/2015 08:56 AM, Max Rydahl Andersen wrote:
> The jetty stuff afaik is in best case not *dependent* by SR.1, but
> affected by it - but I wouldn't bet on it "just working".
I would bet that the Jetty part failed because of using Jetty 9.2.10 and 
9.2.13 and facing the ClassNotFoundException on SpinLock detected in 
4.3.0.CR1
> We might have other being dependent on SR1 though, would be good to hear
> what those are.
Several fixes depend on SR1. However, I don't know whether the version 
range are strictly set to "install" the necessary SR1 part while 
installing JBoss Tools.
> btw. the last years we built against SR0 but tested against latest SR.
> Did we stop that ?
>
Seems like yes, we stopped that. I can't find any reason except that 
we've forgotten to keep it in place, as the jetty issues somehow forced 
us to be more careful with SR1 than with SR0.
-- 
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/20150918/89cc5ad2/attachment.html 

From manderse at redhat.com  Fri Sep 18 03:42:31 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 18 Sep 2015 09:42:31 +0200
Subject: [jbosstools-dev] Testing JBT installation on Mars.0
In-Reply-To: <55FBBDB7.7030501@redhat.com>
References: <55FB5BE1.5060001@redhat.com>
	<899AD180-884C-482F-B474-6BE5FE7B89D9@redhat.com>
	<55FBBDB7.7030501@redhat.com>
Message-ID: <841549F8-D4C8-46DD-A047-967164BFE6FD@redhat.com>

On 18 Sep 2015, at 9:31, Mickael Istria wrote:

> On 09/18/2015 08:56 AM, Max Rydahl Andersen wrote:
>> The jetty stuff afaik is in best case not *dependent* by SR.1, but
>> affected by it - but I wouldn't bet on it "just working".
> I would bet that the Jetty part failed because of using Jetty 9.2.10 
> and 9.2.13 and facing the ClassNotFoundException on SpinLock detected 
> in 4.3.0.CR1

SR0 included jetty 9.2.9, but we used 9.2.10 so my guess is that using 
9.2.13 will continue to work on SR0 too as long as we have the version 
range limited.

>> We might have other being dependent on SR1 though, would be good to 
>> hear
>> what those are.
> Several fixes depend on SR1. However, I don't know whether the version 
> range are strictly set to "install" the necessary SR1 part while 
> installing JBoss Tools.

Which fixes are that ? those are important to have identified.

Last years we linked such issues to the jira referring the update to 
Mars SR1 to know this before hand.

>> btw. the last years we built against SR0 but tested against latest 
>> SR.
>> Did we stop that ?
>>
> Seems like yes, we stopped that. I can't find any reason except that 
> we've forgotten to keep it in place, as the jetty issues somehow 
> forced us to be more careful with SR1 than with SR0.

so I suggest we bring that back if we can't find anything that 
*actually* requires SR1.

/max
http://about.me/maxandersen

From ldimaggi at redhat.com  Fri Sep 18 07:16:15 2015
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Fri, 18 Sep 2015 07:16:15 -0400
Subject: [jbosstools-dev] Testing JBT installation on Mars.0
In-Reply-To: <55FB5BE1.5060001@redhat.com>
References: <55FB5BE1.5060001@redhat.com>
Message-ID: <CA+qK+9=ZqBXWaUx=pwiDrkhAvekJ7dHZfE642o1dR8tjx9otPQ@mail.gmail.com>

We have been testing on both:

   -
   http://download.eclipse.org/eclipse/downloads/drops4/R-4.5-201506032000/
   -
   http://download.eclipse.org/eclipse/downloads/drops4/M-4.5.1RC3-201509040015/

So - we are concerned about: installation, jetty, and what else?


-- Len


On Thu, Sep 17, 2015 at 8:33 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

> Hi,
>
> Just saw the following conversation in tonight's JBT IRC chat:
>
> <nickboldt> akazakov: hey, I just realized that we're building using SR1
> and testing using SR1, but in the past we've always built w/ SR0 and
> testing with SR(latest).
>                      so... this means we MIGHT be forcing people to
> install SR1 (or upgrade to SR1) before they can install JBT or JBDS BYOE.
>                      I can change that but I would really not like to see
> build breaking over night when no one is around tomorrow to fix things :(
> <fbricon> I think we have a bunch of fixes that depend on sr1 bits
> <nickboldt> fbricon: yes. like the 9.2.13 jetty stuff (vs. 9.2.10 in SR0)
> <fbricon> so we don't have much choice
> <nickboldt> yeah. forward with SR1 then :|
> <fbricon> worth an email to the dev list
>
> So, we need to make sure that JBT and JBDS BYOE CR1 are installable on
> Mars.0.
> Len, I don't know if you test JBT on Mars.0 or some Mars.1 RC* but be
> aware of this situation.
>
> Thanks.
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Len DiMaggio (ldimaggi at redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886  USA
tel:  978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150918/8968d272/attachment-0001.html 

From alkazako at redhat.com  Fri Sep 18 07:48:18 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Fri, 18 Sep 2015 07:48:18 -0400
Subject: [jbosstools-dev] Testing JBT installation on Mars.0
In-Reply-To: <841549F8-D4C8-46DD-A047-967164BFE6FD@redhat.com>
References: <55FB5BE1.5060001@redhat.com>
	<899AD180-884C-482F-B474-6BE5FE7B89D9@redhat.com>
	<55FBBDB7.7030501@redhat.com>
	<841549F8-D4C8-46DD-A047-967164BFE6FD@redhat.com>
Message-ID: <55FBFA02.4000006@redhat.com>



On 09/18/2015 03:42 AM, Max Rydahl Andersen wrote:
> On 18 Sep 2015, at 9:31, Mickael Istria wrote:
>
>> On 09/18/2015 08:56 AM, Max Rydahl Andersen wrote:
>>> The jetty stuff afaik is in best case not *dependent* by SR.1, but
>>> affected by it - but I wouldn't bet on it "just working".
>> I would bet that the Jetty part failed because of using Jetty 9.2.10
>> and 9.2.13 and facing the ClassNotFoundException on SpinLock detected
>> in 4.3.0.CR1
> SR0 included jetty 9.2.9, but we used 9.2.10 so my guess is that using
> 9.2.13 will continue to work on SR0 too as long as we have the version
> range limited.

Yes, this is what we guessed when decided to restrict our jetty 
dependency to 9.2.13.

>
>>> We might have other being dependent on SR1 though, would be good to
>>> hear
>>> what those are.
>> Several fixes depend on SR1. However, I don't know whether the version
>> range are strictly set to "install" the necessary SR1 part while
>> installing JBoss Tools.
> Which fixes are that ? those are important to have identified.

Agree, it's important to know. I'm not aware of any besides jetty for 
livereload/browsersim/cordovasim.

>
>>> btw. the last years we built against SR0 but tested against latest
>>> SR.
>>> Did we stop that ?
>>>
>> Seems like yes, we stopped that. I can't find any reason except that
>> we've forgotten to keep it in place, as the jetty issues somehow
>> forced us to be more careful with SR1 than with SR0.
> so I suggest we bring that back if we can't find anything that
> *actually* requires SR1.
But this time we can't build against a pure SR0 because of jetty.
So we need to build against SR0 + jetty 9.2.13 and we will see if it fails.

Thanks.


From manderse at redhat.com  Fri Sep 18 07:55:25 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 18 Sep 2015 13:55:25 +0200
Subject: [jbosstools-dev] Testing JBT installation on Mars.0
In-Reply-To: <55FBFA02.4000006@redhat.com>
References: <55FB5BE1.5060001@redhat.com>
	<899AD180-884C-482F-B474-6BE5FE7B89D9@redhat.com>
	<55FBBDB7.7030501@redhat.com>
	<841549F8-D4C8-46DD-A047-967164BFE6FD@redhat.com>
	<55FBFA02.4000006@redhat.com>
Message-ID: <F3176747-A6B6-4563-9C60-0B952A0CF142@redhat.com>


>>
>>>> btw. the last years we built against SR0 but tested against latest
>>>> SR.
>>>> Did we stop that ?
>>>>
>>> Seems like yes, we stopped that. I can't find any reason except that
>>> we've forgotten to keep it in place, as the jetty issues somehow
>>> forced us to be more careful with SR1 than with SR0.
>> so I suggest we bring that back if we can't find anything that
>> *actually* requires SR1.
> But this time we can't build against a pure SR0 because of jetty.
> So we need to build against SR0 + jetty 9.2.13 and we will see if it 
> fails.

But we did SR0+jetty 9.2.10 before didn't we ?

ah - I guess SR0's jetty 9.2.9 was then compatible with 9.2.10 jetty web 
socket but that broke in latest release.

Got it.

/max
http://about.me/maxandersen

From nboldt at redhat.com  Fri Sep 18 10:06:18 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 18 Sep 2015 10:06:18 -0400
Subject: [jbosstools-dev] Testing JBT installation on Mars.0
In-Reply-To: <F3176747-A6B6-4563-9C60-0B952A0CF142@redhat.com>
References: <55FB5BE1.5060001@redhat.com>
	<899AD180-884C-482F-B474-6BE5FE7B89D9@redhat.com>
	<55FBBDB7.7030501@redhat.com>
	<841549F8-D4C8-46DD-A047-967164BFE6FD@redhat.com>
	<55FBFA02.4000006@redhat.com>
	<F3176747-A6B6-4563-9C60-0B952A0CF142@redhat.com>
Message-ID: <CA+QcL13Ti+5m=w_GA7S3cyYhs9Y9vAXPRX3s63pwFt5xZbEOiA@mail.gmail.com>

This is the first time in years where we DID NOT do a .Final release on SR0
bits, then simply do minor/maintenance updates to SR1 & SR2. Because of
that, we never released the Beta2 TP (SR0) as .Final to use as a "build
baseline" while using the CR1 TP (SR1) for testing and JBDS installer
builds.

So... we SHOULD have been building w/ SR0, but then we might not have
noticed/caught the Jetty thing. Depending on users having SR1 means that if
they have SR0 and try to install JBT 4.3 / JBDS 9 they will likely be
prompted to updated their Eclipse as part of that install (to get newer
deps like Jetty 9.2.13).

But other than that example I'm confident that (hopefully) everyone's
plugins in JBT/JBDS still set version ranges such that they are compatible
with Mars.0, .1, or .2.

On Fri, Sep 18, 2015 at 7:55 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

>
> >>
> >>>> btw. the last years we built against SR0 but tested against latest
> >>>> SR.
> >>>> Did we stop that ?
> >>>>
> >>> Seems like yes, we stopped that. I can't find any reason except that
> >>> we've forgotten to keep it in place, as the jetty issues somehow
> >>> forced us to be more careful with SR1 than with SR0.
> >> so I suggest we bring that back if we can't find anything that
> >> *actually* requires SR1.
> > But this time we can't build against a pure SR0 because of jetty.
> > So we need to build against SR0 + jetty 9.2.13 and we will see if it
> > fails.
>
> But we did SR0+jetty 9.2.10 before didn't we ?
>
> ah - I guess SR0's jetty 9.2.9 was then compatible with 9.2.10 jetty web
> socket but that broke in latest release.
>
> Got it.
>
> /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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150918/cae56bfd/attachment.html 

From nboldt at redhat.com  Fri Sep 18 13:20:28 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 18 Sep 2015 13:20:28 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.CR1a bits available for QE
	testing
Message-ID: <CA+QcL12ZTqCYz=guVh2Li6SOB0kTSqYUi2YGvDKK12_oZC1uBg@mail.gmail.com>

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

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

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


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

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

--

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

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

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



--

Changes prompting this respin-a are:

https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-a%22%29%20and%20%28%28project%20in%20%28%22JBDS%22%29%20and%20fixversion%20in%20%28%229.0.0.CR1%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.3.0.CR1%22%29%29%29

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

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150918/3e28a224/attachment.html 

From pan at mail.shcnc.ac.cn  Sun Sep 20 17:36:20 2015
From: pan at mail.shcnc.ac.cn (lacbma722)
Date: Mon, 21 Sep 2015 05:36:20 +0800
Subject: [jbosstools-dev] =?gb2312?b?yOe6ztOmttTFyceyus/X99X50um6zcDNtq8=?=
	=?gb2312?b?1fnS6Wpib3NzaWRlLWRldg==?=
Message-ID: <201509202136.t8KLaJtU026396@lists01.dmz-a.mwc.hst.phx2.redhat.com>

??????????????????????????????????????????????????????
??????2015?9?24-25???A???  10?23-24???B???   10?30-31???B???11?6-7????B???
                       11?13-14???A??? 11?20-21???A???   11?27-28???A???

??????2???????A???B?????????????????????????????
?A????B????AB???????????A?????B???????B?????A?????A
???B????????????????
?????? ???????????????????/??/??????????????????
             ?????????????????
?????? ???? + ???? + ???? +???? + ????
?????? ??A???2800?/1??5000?/2????B???2800?/1??5000?/2?
             ??AB???5000?/???????????????????
?????? 15074275950   ? ?   0755-61283537
???Q Q?  529178751
?????? 15074275950  ? ?

?????
??2008???????????????????????????????????????????
????????????????????????2009?????????????????????
?2010?????????????????????????????????2011?????????
?????????<?????>??????2012????????????????????????
????????????????????2013?????????????????????????
???????2014???
???????????????????????????????????????????????
???????????????????????????????????????????????
???????????????????????????????????????????????
????????????????????????????????????????
???????????????????????????????????????????????
???????????????????????????????????????????????
??????????????????????????????

?????
1?????????????????
2??????????????????
3????????????????????
4??????????????????????

?????
???????????????????????????????????????
?????????????5?????????????????????????????????
        ????????????????????????????????
???????????????????????????????????????????????
        ????????????????

??????????
???????

????:
    ?????????????????????????????????????????????
???????????????????????????????????????????????
????????????????????
????????(??)????????????????????????????????????
???????????????????????????????????????????????
??????????????????????????100???????????????????
????????

????:
    ?????????????????????????????????????????????
???????????????????????????????????????????????
???????????????????????????????????????????????
???????????????????????????????????????????????
????????100%????

????:
    ????????????????????????????????????????400???
???????????500????????????????20???????400?????????
?????????????30?????200??????????????????????????
???????????????????????????????????????95%?
    2004????????????????????????????30000????????70000??
???????20???????????????????????????????????????
????????????????????????80%??????20%??????????????
????????????????????????????????????????95%?????
???????????????
???????????????????????????????????????????????
??
    ?????????????????????????????????????????????
??????????????????????50???

?????
A??????2??15????????
????????
1.????????????????????????????
2.??????????????????
3.????????????????????????
4.??????????????????????????
5.??????????????
6.??????????????????????????
7.??????????????????????????
8.???????????????????
9.???????????????????????

??????????
1.?????????????????????????????
2.??????????????????????????
3.?????????????????????????????????
4.?????????????????????????????????
5.??????????????????????
6.????2????????????????????????
7.???????????????????????????????
8.??????????????????????

???????
1.?????????????????????? 
2.??????????????????????????
3.?????????????2???????????
4.?????????????????70%??????
5.?????????????????50%??????
6.??????????????????????
7.???????????????????????????
8.????????????????????????????

?????????????
1.????????????????????????????
2.?????????????????????
3.???????????????????????
4.??????????????????????10???????????????????????
  ?
5.??????????????????????????????????????????????
  ?????
6.??????????????????????????????????????????????
  ??????????????????

??????????
1.??????????????????????????????????????
2.??????????????????????????????????????????????
  ?
3.???????????????????????????????????
4.?????????????????
5.??????????????????????
6.????????????????????
7.?????????????????
8.???????????????????

????????????
1.??????????????????????????????????????????????
  ?????????????????????
2.???????????????????????????????
3.?????30?????????????????????
4.?????????30??????????????????????
5.?????????30???????????????????????
6.?????????????????????????
7.?????????????????????????????????????????????
8.??????????????????????????????????????????????
  ??????????
9.???????????????????????????????????????????
10.?????????????????????????????????????????????
   ?????????????
11.????????????????????????????
12.?????????????????????????????????????????????
   ???????????????

?????????
1.??????????????????
2.??????????????????
3.??????????????????????????????
4.????????????????
5.????????????????????????????????
6.????????????????????????
7.???????????????????
8.??????????????????????????????

??????????
1.???????????????
2.?????????????????????
3.???????????????? 
4.??????????????????????
5.???????????????????????????
6.????????????????
7.?????????????????????
8.????????????????????

B??????2??15????????
?????????????
1.?????????????????????????????????
2.??????????????????2??????????????
3.???????????????????
4.???????????????????????????????
5.????????????????????????????????
6.???????????????????
7.???????????????????
8.????????????5%??????????????

?????????????
1.?????????????
2.????????????????
3.??????????????????
4.?????????????????????
5.????????
6.?????????????
7.?????????????????????
8.????????????????????????????
9.???????????????????
10.???????\???????????????????????
11.?????????????????????????????
12.??????????????????????????????

??????????????
1.???????????????????????
2.???????????????????????????????????
3.??????????????????
4.????????????????????
5.????????????????????????????????? 
6.????????????????????????????
7.??????????????????????????????????
8.????????????????????????
9.????????????????????????
10.?????????????????????????????????????????????
11.?????????????????????????????????????????????
   ??????
12.???????????????????????OA?????????????????????
   ???????????? 

????????
1.??????????????????????
2.????????????????????
3.???????????????????????
4.?????????????????
5.????????????????????
6.???????????????????????
7.??????????????????????????????????????????????
  ?
8.?????????50%???????????????

?????????????
1.?????????????????????????
2.????????????????????????
3.????????????????????????????
4.????????????????????
5.?????????????????????
6.??????????????????????
7.?????????????????? 
8.?????????????????????????????????

??????????
1.?????????????
2.??????????????
3.??????????????????????
4.???????????????????
5.???????????????????????
6.??????????????????????????????????????????????
  ? 
7.?????????????????????????
8.???????????????????????????

????????
1.?????????????????????
2.?????????????????????
3.??????????????????
4.??????????????????????????
5.???????????????????????????????
6.????????????????????????????
7.??????????????????
8.?????????????????????
9.????????????????????
10.???????????????????
11.????????????????????????????????
12.??????????????????
13.??????????????????
14.????????????????????

05:36:19164112164112jbosside-dev

From pleacu at redhat.com  Sun Sep 20 18:19:07 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Sun, 20 Sep 2015 18:19:07 -0400 (EDT)
Subject: [jbosstools-dev] QE Handoff - JBDSIS 9.0.0.Alpha2,
	JBTIS 4.3.0.Alpha2
In-Reply-To: <2039306441.24161302.1442256421184.JavaMail.zimbra@redhat.com>
Message-ID: <864893945.26576908.1442787547468.JavaMail.zimbra@redhat.com>


   Greetings,
      This Eclipse-Mars capable, JBDS 9.0.0.Beta2 compatible Integration Stack Alpha
   is available for QE testing.  This release contains the following:

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

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

   **NOTE - Use the p2 update sites or zip files.  The IS Discovery site has all IS components marked as unavailable until
            the QE test cycle is complete.  The IS Discovery mechanism will then be updated and a smoke test cycle will be
            created with the IS components available as early access.

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

   JBDSIS 9.0.0.Alpha2, JBTIS 4.3.0.Alpha2

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

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

          - use this for 'Location:' for the early access integration stack:
            http://www.qa.jboss.com/binaries/RHDS/mars/staging/updates/integration-stack/earlyaccess/
      Done!

   JBoss Central is supported for JBDSIS:

      * Specify the integration stack discovery artifact:

        ./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/mars/staging/updates/integration-stack/discovery/9.0.0.Alpha2/devstudio-directory.xml \
          -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/mars/staging/updates/integration-stack/discovery/9.0.0.Alpha2

   The standard p2 installer is available for JBTIS:

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

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

   JBoss Central is supported for JBTIS:

      * Install JBoss Tools 4.3.0.Beta2:
          Help > Eclipse Marketplace...
          - in the 'Search' tab enter 'jboss tools' in the 'Find' input widget
          - select the 'Go' button
          - install 'JBoss Tools 4.3.0.Beta2'
  
      * Specify the integration stack discovery artifacts:
        ./eclipse -vmargs \
           -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml \
           -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha2/

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

      1. http://www.qa.jboss.com/binaries/RHDS/mars/staging/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2.zip
         http://www.qa.jboss.com/binaries/RHDS/mars/staging/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2.zip.MD5

      2. http://www.qa.jboss.com/binaries/RHDS/mars/staging/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2-earlyaccess.zip
         http://www.qa.jboss.com/binaries/RHDS/mars/staging/updates/integration-stack/devstudio-integration-stack-9.0.0.Alpha2-earlyaccess.zip.MD5

      3. http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2.zip
         http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2.zip.MD5

      4. http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2-earlyaccess.zip
         http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/jbosstools-integration-stack-4.3.0.Alpha2-earlyaccess.zip.MD5

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

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

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

   --paull

From noreply at metalurgicasirom.com  Sun Sep 20 23:39:05 2015
From: noreply at metalurgicasirom.com (Discount-Canadian-Meds)
Date: Mon, 21 Sep 2015 09:39:05 +0600
Subject: [jbosstools-dev] If you are looking for a trusted and high quality
	pharmacy, look not further! It's all you need!
Message-ID: <op.sceaa5a1ba7a79@metalurgicasirom.com>

   

		Decrease in 2003, release document white. Battle another memorial to
clear franklin601a 0glout, johnm28 head. Arises from bbc site owner. 

		Me
		ds
		8f
		or
		9M
		en

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

 S
a 
ia

of

t 

Ta

bs

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

		Me
		ds
		5f
		or
		9W
		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
An
On
Sp  p
on
ly
ec re
ym
 r
ia sc
ou
el
l  ri
s 
ia
in pt
de
bl
te io
li
e 
rn n 
ve
su
et re
ry
pp
 p qu

li
ri ir

er
ce ed

s 
s   

   2
 F
 1
 V 4/
as
00
is 7 
t 
% 
a, cu
wo
Au
Ma st
rl
th
st om
dw
en
er er
id
ti
ca  s
e 
c 
rd up
sh
Me
,E po
ip
ds
ch rt
pi

ec  
ng

k   

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

From alkazako at redhat.com  Mon Sep 21 14:28:30 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Mon, 21 Sep 2015 14:28:30 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Update parent pom to 4.4.0.Alpha1
	in master
Message-ID: <56004C4E.10405@redhat.com>

Hi,

It's time to prepare the master branch for JBT 4.4 / JBDS 10 development.

1. Please update the parent pom in your component from 
4.3.0.CR1-SNAPSHOT to 4.4.0.Alpha1-SNAPSHOT:

jbosstools-*/pom.xml:

     <parent>
          <groupId>org.jboss.tools</groupId>
          <artifactId>parent</artifactId>
          <version>*4.4.0.Alpha1-SNAPSHOT*</version>
      </parent>

Please update the parent pom now.

2. Bump the version of your component. For example if the current 
version of your component is 4.3.0 then update it to 4.4.0 or 4.3.100 
(if you don't add any new functionality):

mvn org.eclipse.tycho:tycho-versions-plugin:set-version 
-DnewVersion=4.4.0.SNAPSHOT

You should update the component version when you pushing any changes to 
master that you don't have in JBT 4.3.0

I didn't create JIRAs for these updates, so, please, don't ignore this 
email :)

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150921/19cac7a0/attachment.html 

From snjezana.peco at redhat.com  Mon Sep 21 15:33:37 2015
From: snjezana.peco at redhat.com (Snjezana Peco)
Date: Mon, 21 Sep 2015 21:33:37 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Update parent pom to
 4.4.0.Alpha1 in master
In-Reply-To: <56004C4E.10405@redhat.com>
References: <56004C4E.10405@redhat.com>
Message-ID: <56005B91.7020102@redhat.com>

Done for arquillian and birt.

Snjeza
On 9/21/2015 8:28 PM, Alexey Kazakov wrote:
> Hi,
>
> It's time to prepare the master branch for JBT 4.4 / JBDS 10 development.
>
> 1. Please update the parent pom in your component from 
> 4.3.0.CR1-SNAPSHOT to 4.4.0.Alpha1-SNAPSHOT:
>
> jbosstools-*/pom.xml:
>
>     <parent>
>          <groupId>org.jboss.tools</groupId>
>          <artifactId>parent</artifactId>
>          <version>*4.4.0.Alpha1-SNAPSHOT*</version>
>      </parent>
>
> Please update the parent pom now.
>
> 2. Bump the version of your component. For example if the current 
> version of your component is 4.3.0 then update it to 4.4.0 or 4.3.100 
> (if you don't add any new functionality):
>
> mvn org.eclipse.tycho:tycho-versions-plugin:set-version 
> -DnewVersion=4.4.0.SNAPSHOT
>
> You should update the component version when you pushing any changes 
> to master that you don't have in JBT 4.3.0
>
> I didn't create JIRAs for these updates, so, please, don't ignore this 
> email :)
>
> Thanks.
>
>
> _______________________________________________
> 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/20150921/0b2a3609/attachment-0001.html 

From dgolovin at exadel.com  Mon Sep 21 15:51:42 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Mon, 21 Sep 2015 12:51:42 -0700
Subject: [jbosstools-dev] ACTION REQUIRED: Update parent pom to
 4.4.0.Alpha1 in master
In-Reply-To: <56005B91.7020102@redhat.com>
References: <56004C4E.10405@redhat.com>
	<56005B91.7020102@redhat.com>
Message-ID: <CAJXFskZBoWVAOO5qdZPm37rTYpB62hVhc2H5=+qBdXr_F2z4zw@mail.gmail.com>

Base updated to use 4.4.0.Alpha1.

Is there Neon based TP available?

Denis

On Mon, Sep 21, 2015 at 12:33 PM, Snjezana Peco <snjezana.peco at redhat.com>
wrote:

> Done for arquillian and birt.
>
> Snjeza
> On 9/21/2015 8:28 PM, Alexey Kazakov wrote:
>
> Hi,
>
> It's time to prepare the master branch for JBT 4.4 / JBDS 10 development.
>
> 1. Please update the parent pom in your component from 4.3.0.CR1-SNAPSHOT
> to 4.4.0.Alpha1-SNAPSHOT:
>
> jbosstools-*/pom.xml:
>
>     <parent>
>          <groupId>org.jboss.tools</groupId>
>          <artifactId>parent</artifactId>
>          <version>*4.4.0.Alpha1-SNAPSHOT*</version>
>      </parent>
>
> Please update the parent pom now.
>
> 2. Bump the version of your component. For example if the current version
> of your component is 4.3.0 then update it to 4.4.0 or 4.3.100 (if you don't
> add any new functionality):
>
> mvn org.eclipse.tycho:tycho-versions-plugin:set-version
> -DnewVersion=4.4.0.SNAPSHOT
>
> You should update the component version when you pushing any changes to
> master that you don't have in JBT 4.3.0
>
> I didn't create JIRAs for these updates, so, please, don't ignore this
> email :)
>
> Thanks.
>
>
> _______________________________________________
> jbosstools-dev mailing listjbosstools-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

-- 


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

From nboldt at redhat.com  Mon Sep 21 19:14:37 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 21 Sep 2015 19:14:37 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Update parent pom to
 4.4.0.Alpha1 in master
In-Reply-To: <CAJXFskZBoWVAOO5qdZPm37rTYpB62hVhc2H5=+qBdXr_F2z4zw@mail.gmail.com>
References: <56004C4E.10405@redhat.com> <56005B91.7020102@redhat.com>
	<CAJXFskZBoWVAOO5qdZPm37rTYpB62hVhc2H5=+qBdXr_F2z4zw@mail.gmail.com>
Message-ID: <CA+QcL13mux9hm9wRSyzgqvAZgeFK89agRyROh91FVfQhm1TvwQ@mail.gmail.com>

No, there's no Neon-based TP available yet, since there's no schedule
for Alpha1 yet.

Throw some votes at JBIDE-20749 if you need this escalated.

On Mon, Sep 21, 2015 at 3:51 PM, Denis Golovin <dgolovin at exadel.com> wrote:
> Base updated to use 4.4.0.Alpha1.
>
> Is there Neon based TP available?
>
> Denis
>
> On Mon, Sep 21, 2015 at 12:33 PM, Snjezana Peco <snjezana.peco at redhat.com>
> wrote:
>>
>> Done for arquillian and birt.
>>
>> Snjeza
>> On 9/21/2015 8:28 PM, Alexey Kazakov wrote:
>>
>> Hi,
>>
>> It's time to prepare the master branch for JBT 4.4 / JBDS 10 development.
>>
>> 1. Please update the parent pom in your component from 4.3.0.CR1-SNAPSHOT
>> to 4.4.0.Alpha1-SNAPSHOT:
>>
>> jbosstools-*/pom.xml:
>>
>>     <parent>
>>          <groupId>org.jboss.tools</groupId>
>>          <artifactId>parent</artifactId>
>>          <version>4.4.0.Alpha1-SNAPSHOT</version>
>>      </parent>
>>
>> Please update the parent pom now.
>>
>> 2. Bump the version of your component. For example if the current version
>> of your component is 4.3.0 then update it to 4.4.0 or 4.3.100 (if you don't
>> add any new functionality):
>>
>> mvn org.eclipse.tycho:tycho-versions-plugin:set-version
>> -DnewVersion=4.4.0.SNAPSHOT
>>
>> You should update the component version when you pushing any changes to
>> master that you don't have in JBT 4.3.0
>>
>> I didn't create JIRAs for these updates, so, please, don't ignore this
>> email :)
>>
>> Thanks.
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>
>
> _______________________________________________
> 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  Mon Sep 21 19:38:26 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 21 Sep 2015 19:38:26 -0400 (EDT)
Subject: [jbosstools-dev] ACTION REQUIRED: Update parent pom to
	4.4.0.Alpha1 in master
In-Reply-To: <CA+QcL13mux9hm9wRSyzgqvAZgeFK89agRyROh91FVfQhm1TvwQ@mail.gmail.com>
References: <56004C4E.10405@redhat.com> <56005B91.7020102@redhat.com>
	<CAJXFskZBoWVAOO5qdZPm37rTYpB62hVhc2H5=+qBdXr_F2z4zw@mail.gmail.com>
	<CA+QcL13mux9hm9wRSyzgqvAZgeFK89agRyROh91FVfQhm1TvwQ@mail.gmail.com>
Message-ID: <CDA860E9-A5CA-4A1B-8F08-C64D435C5CB6@redhat.com>

IMO We don't need a alpha1 schedule to get a neon TP to get started to see what breaks if anything. 

/max
http://about.me/maxandersen


> On 22 Sep 2015, at 01:15, Nick Boldt <nboldt at redhat.com> wrote:
> 
> No, there's no Neon-based TP available yet, since there's no schedule
> for Alpha1 yet.
> 
> Throw some votes at JBIDE-20749 if you need this escalated.
> 
>> On Mon, Sep 21, 2015 at 3:51 PM, Denis Golovin <dgolovin at exadel.com> wrote:
>> Base updated to use 4.4.0.Alpha1.
>> 
>> Is there Neon based TP available?
>> 
>> Denis
>> 
>> On Mon, Sep 21, 2015 at 12:33 PM, Snjezana Peco <snjezana.peco at redhat.com>
>> wrote:
>>> 
>>> Done for arquillian and birt.
>>> 
>>> Snjeza
>>> On 9/21/2015 8:28 PM, Alexey Kazakov wrote:
>>> 
>>> Hi,
>>> 
>>> It's time to prepare the master branch for JBT 4.4 / JBDS 10 development.
>>> 
>>> 1. Please update the parent pom in your component from 4.3.0.CR1-SNAPSHOT
>>> to 4.4.0.Alpha1-SNAPSHOT:
>>> 
>>> jbosstools-*/pom.xml:
>>> 
>>>    <parent>
>>>         <groupId>org.jboss.tools</groupId>
>>>         <artifactId>parent</artifactId>
>>>         <version>4.4.0.Alpha1-SNAPSHOT</version>
>>>     </parent>
>>> 
>>> Please update the parent pom now.
>>> 
>>> 2. Bump the version of your component. For example if the current version
>>> of your component is 4.3.0 then update it to 4.4.0 or 4.3.100 (if you don't
>>> add any new functionality):
>>> 
>>> mvn org.eclipse.tycho:tycho-versions-plugin:set-version
>>> -DnewVersion=4.4.0.SNAPSHOT
>>> 
>>> You should update the component version when you pushing any changes to
>>> master that you don't have in JBT 4.3.0
>>> 
>>> I didn't create JIRAs for these updates, so, please, don't ignore this
>>> email :)
>>> 
>>> Thanks.
>>> 
>>> 
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>> 
>>> 
>>> 
>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>> confidential. If you are not the intended recipient you are hereby notified
>>> that using, copying, distributing or taking any action in reliance on the
>>> contents of this information is strictly prohibited. If you have received
>>> this email in error please notify the sender and delete this email.
>>> 
>>> 
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> 
>> 
>> 
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>> 
>> 
>> _______________________________________________
>> 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


From alkazako at redhat.com  Mon Sep 21 19:42:02 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Mon, 21 Sep 2015 19:42:02 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Update parent pom to
 4.4.0.Alpha1 in master
In-Reply-To: <CDA860E9-A5CA-4A1B-8F08-C64D435C5CB6@redhat.com>
References: <56004C4E.10405@redhat.com> <56005B91.7020102@redhat.com>
	<CAJXFskZBoWVAOO5qdZPm37rTYpB62hVhc2H5=+qBdXr_F2z4zw@mail.gmail.com>
	<CA+QcL13mux9hm9wRSyzgqvAZgeFK89agRyROh91FVfQhm1TvwQ@mail.gmail.com>
	<CDA860E9-A5CA-4A1B-8F08-C64D435C5CB6@redhat.com>
Message-ID: <560095CA.4000307@redhat.com>



On 09/21/2015 07:38 PM, Max Rydahl Andersen wrote:
> IMO We don't need a alpha1 schedule to get a neon TP to get started to see what breaks if anything.

+1

From ggastald at redhat.com  Mon Sep 21 20:15:10 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Mon, 21 Sep 2015 21:15:10 -0300
Subject: [jbosstools-dev] ACTION REQUIRED: Update parent pom to
 4.4.0.Alpha1 in master
In-Reply-To: <56004C4E.10405@redhat.com>
References: <56004C4E.10405@redhat.com>
Message-ID: <CAMmsnJjgczDGLnam2E+MVReyvwvjaGckX-7CtkJAnrKs_Z-ASw@mail.gmail.com>

Parent pom updated in forge:
https://github.com/jbosstools/jbosstools-forge/commit/437c9fbd0001ec31795624b44bfda0fb3ef975bb
Em 21/09/2015 15:29, "Alexey Kazakov" <alkazako at redhat.com> escreveu:

> Hi,
>
> It's time to prepare the master branch for JBT 4.4 / JBDS 10 development.
>
> 1. Please update the parent pom in your component from 4.3.0.CR1-SNAPSHOT
> to 4.4.0.Alpha1-SNAPSHOT:
>
> jbosstools-*/pom.xml:
>
>     <parent>
>          <groupId>org.jboss.tools</groupId>
>          <artifactId>parent</artifactId>
>          <version>*4.4.0.Alpha1-SNAPSHOT*</version>
>      </parent>
>
> Please update the parent pom now.
>
> 2. Bump the version of your component. For example if the current version
> of your component is 4.3.0 then update it to 4.4.0 or 4.3.100 (if you don't
> add any new functionality):
>
> mvn org.eclipse.tycho:tycho-versions-plugin:set-version
> -DnewVersion=4.4.0.SNAPSHOT
>
> You should update the component version when you pushing any changes to
> master that you don't have in JBT 4.3.0
>
> I didn't create JIRAs for these updates, so, please, don't ignore this
> email :)
>
> Thanks.
>
> _______________________________________________
> 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/20150921/e2bdb5cc/attachment.html 

From orders at rabota-yandex-taksi.ru  Mon Sep 21 21:39:04 2015
From: orders at rabota-yandex-taksi.ru (America Airlines)
Date: Tue, 22 Sep 2015 05:39:04 +0400
Subject: [jbosstools-dev] Your E-Ticket information, order #00000360757
Message-ID: <5ec735d64c4f77461a0839b4833c2729@rabota-yandex-taksi.ru>

Dear customer,

Your payment has been processed and your credit card has been charged.

You can find your e-ticket in the attachment.

Order summary:

FLIGHT NUMBER / ML493953
DATE & TIME / Sep 28 2015, 16:10
DEPARTING / Detroit
TOTAL PRICE / $ 580.00

Thank you for flying with America Airlines.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Order_00000360757.zip
Type: application/zip
Size: 3160 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150922/30bc4c1d/attachment-0001.zip 

From xcoulon at redhat.com  Tue Sep 22 02:51:53 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Tue, 22 Sep 2015 08:51:53 +0200
Subject: [jbosstools-dev] ACTION REQUIRED: Update parent pom to
	4.4.0.Alpha1 in master
In-Reply-To: <56004C4E.10405@redhat.com>
References: <56004C4E.10405@redhat.com>
Message-ID: <2AA30492-F073-4090-83FB-AB77187A4B7D@redhat.com>

Done for LiveReload and Web Services.

Best regards,
/Xavier



> On 21 Sep 2015, at 20:28, Alexey Kazakov <alkazako at redhat.com> wrote:
> 
> Hi,
> 
> It's time to prepare the master branch for JBT 4.4 / JBDS 10 development.
> 
> 1. Please update the parent pom in your component from 4.3.0.CR1-SNAPSHOT to 4.4.0.Alpha1-SNAPSHOT:
> 
> jbosstools-*/pom.xml:
> 
>     <parent>
>          <groupId>org.jboss.tools</groupId>
>          <artifactId>parent</artifactId>
>          <version>4.4.0.Alpha1-SNAPSHOT</version>
>      </parent>
> 
> Please update the parent pom now.
> 
> 2. Bump the version of your component. For example if the current version of your component is 4.3.0 then update it to 4.4.0 or 4.3.100 (if you don't add any new functionality): 
> 
> mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=4.4.0.SNAPSHOT
> 
> You should update the component version when you pushing any changes to master that you don't have in JBT 4.3.0
> 
> I didn't create JIRAs for these updates, so, please, don't ignore this email :)
> 
> Thanks.
> _______________________________________________
> 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/20150922/bccb652f/attachment.html 

From ldimaggi at redhat.com  Tue Sep 22 10:55:20 2015
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Tue, 22 Sep 2015 10:55:20 -0400
Subject: [jbosstools-dev] JBDS 9.0.0.CR1.respin-a / JBT 4.3.0.CR1.respin-a -
	QE signoff to stage/release
Message-ID: <CA+qK+9mrfqVVeB329s0CtV0=g_bH01=TSDhk80Ho0DzNZ-orrg@mail.gmail.com>

Hey everyone,

QE approves CR1 (respin-a) - OK to stage the bits! Signoff doc is here:
https://mojo.redhat.com/docs/DOC-1047818


Thanks to everyone for their efforts on this!,
Len D.


-- 
Len DiMaggio (ldimaggi at redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886  USA
tel:  978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150922/d9430b9c/attachment.html 

From dgolovin at exadel.com  Tue Sep 22 12:26:24 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Tue, 22 Sep 2015 09:26:24 -0700
Subject: [jbosstools-dev] ACTION REQUIRED: Update parent pom to
 4.4.0.Alpha1 in master
In-Reply-To: <CDA860E9-A5CA-4A1B-8F08-C64D435C5CB6@redhat.com>
References: <56004C4E.10405@redhat.com> <56005B91.7020102@redhat.com>
	<CAJXFskZBoWVAOO5qdZPm37rTYpB62hVhc2H5=+qBdXr_F2z4zw@mail.gmail.com>
	<CA+QcL13mux9hm9wRSyzgqvAZgeFK89agRyROh91FVfQhm1TvwQ@mail.gmail.com>
	<CDA860E9-A5CA-4A1B-8F08-C64D435C5CB6@redhat.com>
Message-ID: <CAJXFskZgGy+sNmEAAif51W5co-njX-vzQdJ13SgNLXyCULex7A@mail.gmail.com>

+1

Lets just follow the process we have. Master is targeting Eclipse Neon,
which means we need Neon based Target Platform to get started.

Denis

On Mon, Sep 21, 2015 at 4:38 PM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> IMO We don't need a alpha1 schedule to get a neon TP to get started to see
> what breaks if anything.
>
> /max
> http://about.me/maxandersen
>
>
> > On 22 Sep 2015, at 01:15, Nick Boldt <nboldt at redhat.com> wrote:
> >
> > No, there's no Neon-based TP available yet, since there's no schedule
> > for Alpha1 yet.
> >
> > Throw some votes at JBIDE-20749 if you need this escalated.
> >
> >> On Mon, Sep 21, 2015 at 3:51 PM, Denis Golovin <dgolovin at exadel.com>
> wrote:
> >> Base updated to use 4.4.0.Alpha1.
> >>
> >> Is there Neon based TP available?
> >>
> >> Denis
> >>
> >> On Mon, Sep 21, 2015 at 12:33 PM, Snjezana Peco <
> snjezana.peco at redhat.com>
> >> wrote:
> >>>
> >>> Done for arquillian and birt.
> >>>
> >>> Snjeza
> >>> On 9/21/2015 8:28 PM, Alexey Kazakov wrote:
> >>>
> >>> Hi,
> >>>
> >>> It's time to prepare the master branch for JBT 4.4 / JBDS 10
> development.
> >>>
> >>> 1. Please update the parent pom in your component from
> 4.3.0.CR1-SNAPSHOT
> >>> to 4.4.0.Alpha1-SNAPSHOT:
> >>>
> >>> jbosstools-*/pom.xml:
> >>>
> >>>    <parent>
> >>>         <groupId>org.jboss.tools</groupId>
> >>>         <artifactId>parent</artifactId>
> >>>         <version>4.4.0.Alpha1-SNAPSHOT</version>
> >>>     </parent>
> >>>
> >>> Please update the parent pom now.
> >>>
> >>> 2. Bump the version of your component. For example if the current
> version
> >>> of your component is 4.3.0 then update it to 4.4.0 or 4.3.100 (if you
> don't
> >>> add any new functionality):
> >>>
> >>> mvn org.eclipse.tycho:tycho-versions-plugin:set-version
> >>> -DnewVersion=4.4.0.SNAPSHOT
> >>>
> >>> You should update the component version when you pushing any changes to
> >>> master that you don't have in JBT 4.3.0
> >>>
> >>> I didn't create JIRAs for these updates, so, please, don't ignore this
> >>> email :)
> >>>
> >>> Thanks.
> >>>
> >>>
> >>> _______________________________________________
> >>> jbosstools-dev mailing list
> >>> jbosstools-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >>>
> >>>
> >>>
> >>> CONFIDENTIALITY NOTICE: This email and files attached to it are
> >>> confidential. If you are not the intended recipient you are hereby
> notified
> >>> that using, copying, distributing or taking any action in reliance on
> the
> >>> contents of this information is strictly prohibited. If you have
> received
> >>> this email in error please notify the sender and delete this email.
> >>>
> >>>
> >>> _______________________________________________
> >>> jbosstools-dev mailing list
> >>> jbosstools-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >>
> >>
> >>
> >> CONFIDENTIALITY NOTICE: This email and files attached to it are
> >> confidential. If you are not the intended recipient you are hereby
> notified
> >> that using, copying, distributing or taking any action in reliance on
> the
> >> contents of this information is strictly prohibited. If you have
> received
> >> this email in error please notify the sender and delete this email.
> >>
> >>
> >> _______________________________________________
> >> jbosstools-dev mailing list
> >> jbosstools-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >
> >
> >
> > --
> > Nick Boldt :: JBoss by Red Hat
> > Productization Lead :: JBoss Tools & Dev Studio
> > http://nick.divbyzero.com
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> --
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>

-- 


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

From alkazako at redhat.com  Tue Sep 22 17:14:36 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Tue, 22 Sep 2015 17:14:36 -0400
Subject: [jbosstools-dev] Working on 4.3.1/4.4.0
Message-ID: <5601C4BC.8020907@redhat.com>

Hi,

Just a reminder that the jbosstools-4.3.x branch is still frozen and 
will remain frozen until we release JBT 4.3.0.Final (should happen in 
two weeks or later if we have to postpone it).

If you have something you want to fix for the future versions then please:

*a. If your change is something that should be fixed only for JBT 4.4*, 
for example some big changes or Eclipse Neon related fixed/updates then:
a.1. Create a PR for master. Apply it. Resolve the issue for JBT 
4.4.0.Alpha1. (don't forget to update the version of your component if 
you have not done it yet).

*b. If you have something that should be fixed in both JBT 4.4 (Eclipse 
Neon) and JBT 4.3.1* (maintenance release for Eclipse Mars) then:
b.1. Fix it in master. See a.1.
b.2.1. Create a PR for jbosstools-4.3.x and wait for that branch to be 
open for 4.3.1 development. You should keep your JIRA open until both PR 
are merged.
or if you really need some open branch to continue working on 4.3.1 
issues (for example the OpenShift team needs it) then you have the 
following option:
b.2.2. Create a new jbosstools-4.3.1.x branch from jbosstools-4.3.x, 
work with that to fix all needed issues (create a PR, apply after 
someone's review, resolve the jira, all usual stuff). And create a JIRA 
for JBT 4.3.1 which says the 4.3.1.x branch should be merged to 4.3.x. 
When the main 4.3.x branch is open, then you will be able to merge the 
branches and continue working on the main 4.3.x branch directly.

I hope it makes sense.

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150922/42d968a3/attachment-0001.html 

From fbricon at redhat.com  Tue Sep 22 17:30:48 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Tue, 22 Sep 2015 17:30:48 -0400
Subject: [jbosstools-dev] OpenShift branch targeting JBoss Tools 4.3.1
Message-ID: <CACvX+KjTgwWCeDJmPOmxsPdW+PeHUmTzOpxCReT7CKNY1g+m2A@mail.gmail.com>

Hi,

we have a bunch of stuff to do in OpenShift tooling, for the 4.3.1 release
and, given the jbosstools-4.3.x branch is closed for business for the next
2 weeks, the 4.3.1 work will happen in branch jbosstools-4.3.1x. Once
4.3.0.Final is released, the 4.3.1.x branch will be merged into 4.3.x[1].
Hopefully it should be a fast forward merge by then.

So currently we have the following branches:

jbosstools-4.3.x: jbosstools-openshift 3.0.0-SNAPSHOT (4.3.0.CR1-SNAPSHOT
parent)
jbosstools-4.3.1.x: jbosstools-openshift 3.1.0-SNAPSHOT (4.3.0.CR1-SNAPSHOT
parent)
master: jbosstools-openshift 3.2.0-SNAPSHOT (4.3.0.CR1-SNAPSHOT parent)

Appropriate parent versions will have to be changed ASAP.

For each fix pushed to the jbosstools-4.3.1.x, the matching JIRA can be
updated to 'Resolved'

Maybe not a perfect workflow but it's the least bad we could think of :-)

If other JBT components have similar requirements, feel free to implement a
similar pattern.


Fred

[1] https://issues.jboss.org/browse/JBIDE-20766
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150922/696e4674/attachment.html 

From dgolovin at exadel.com  Tue Sep 22 19:08:48 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Tue, 22 Sep 2015 16:08:48 -0700
Subject: [jbosstools-dev] TARGET_PLATFORM_VERSION value in parent/pom.xml
	for jbosstools-4.3.x branch
Message-ID: <CAJXFskZzS5D+0wioUxjqZQskyUu2NKdEMN=X89ZggrVQH1ZSKw@mail.gmail.com>

While having troubles with master build I realized parent/pom.xml property
TARGET_PLATFORM_VERSION has wrong value. As I remember the idea was to keep
building the code base with TP based on Mars.0 release and running tests
with TP based on latest Mars release.

Currently TARGET_PLATFORM_VERSION=4.50.0.CR1-SNAPSHOT which is far ahead
from Mars.0 based TP.

According to the commit history (see below) closest released target
platform based on Mars.0 is 4.3.0.Beta2:

....
* 57fb37d - JBIDE-20143 generate SHA-256 checksum instead of SHA-1 since
that's what CSP/GG uses (10 weeks ago) <nickboldt>
** ae5f7d5 - (tag: refs/tags/4.50.0.Beta2) TP release 4.50.0.Beta2 (10
weeks ago) <Mickael Istria>*
* 5462b74 - Revert "JBIDE-20216 'The general rule is to use the latest
stable or release train ...(2 months ago) <nickboldt>
* b4adf55 - JBIDE-20216 'The general rule is to use the latest stable or
release train ...(2 months ago) <nickboldt>
* e997da3 - JBIDE-20216 add wikitext asciidoc editor; exclude creole and
commonmark plugins (for now) (3 months ago) <nickboldt>
* 04569fa - LOCUS-37: Include assertj 2.1.0 in TP (3 months ago) <Mickael
Istria>
* 4e7f019 - Update easymport (3 months ago) <Mickael Istria>
* 295f16a - include m2e 1.6.1 (not part of Mars R release) (3 months ago)
<nickboldt>
* 3a13c1f - JBIDE-19981: JSDT importer from upstream (3 months ago)
<Mickael Istria>
** 6955ca7 - Mars release (3 months ago) <Mickael Istria>*
...

Shouldn't parent/pom.xm have TARGET_PLATFORM_VERSION=4.50.0.Beta2 instead
what it has now?

With 4.50.Beta2 we can be at least sure about being able to install on
Mars.0 without manual testing.

WDYT?

Denis

-- 


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

From mistria at redhat.com  Wed Sep 23 02:02:41 2015
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 23 Sep 2015 08:02:41 +0200
Subject: [jbosstools-dev] TARGET_PLATFORM_VERSION value in
 parent/pom.xml for jbosstools-4.3.x branch
In-Reply-To: <CAJXFskZzS5D+0wioUxjqZQskyUu2NKdEMN=X89ZggrVQH1ZSKw@mail.gmail.com>
References: <CAJXFskZzS5D+0wioUxjqZQskyUu2NKdEMN=X89ZggrVQH1ZSKw@mail.gmail.com>
Message-ID: <56024081.8050005@redhat.com>

Please use 4.50.0.Final-SNAPSHOT.

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

From mistria at redhat.com  Wed Sep 23 02:23:57 2015
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 23 Sep 2015 08:23:57 +0200
Subject: [jbosstools-dev] TARGET_PLATFORM_VERSION value in
 parent/pom.xml for jbosstools-4.3.x branch
In-Reply-To: <CAJXFskZzS5D+0wioUxjqZQskyUu2NKdEMN=X89ZggrVQH1ZSKw@mail.gmail.com>
References: <CAJXFskZzS5D+0wioUxjqZQskyUu2NKdEMN=X89ZggrVQH1ZSKw@mail.gmail.com>
Message-ID: <5602457D.9080307@redhat.com>

On 09/23/2015 01:08 AM, Denis Golovin wrote:
> While having troubles with master build I realized parent/pom.xml 
> property TARGET_PLATFORM_VERSION has wrong value. As I remember the 
> idea was to keep building the code base with TP based on Mars.0 
> release and running tests with TP based on latest Mars release.

On master, the idea is to build against Neon, and a few minutes ago, I 
made necessary changes in parent pom and CI jobs for master branch to 
consume TP 4.60.0.Alpha1-SNAPSHOT, which will soon host Neon bundles.
The idea of building against Mars.0 (4.50.0.Final) and testing against 
Mars.1 (4.51.0.Final) is for jbosstools-4.3.x jobs.

-- 
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/20150923/df1e4d82/attachment.html 

From mistria at redhat.com  Wed Sep 23 06:20:58 2015
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 23 Sep 2015 12:20:58 +0200
Subject: [jbosstools-dev] Suggested change in Target-Platform
	4.60.0.Alpha1-SNAPSHOT: Neon M1
Message-ID: <56027D0A.9000003@redhat.com>

Hi all,

Here is a suggested change for target-platforms 4.60.0.Alpha1-SNAPSHOT, 
which is currently used when building from master branch:
* Move to Neon M1 https://issues.jboss.org/browse/JBIDE-20749

Please review the suggested patch and the p2diff, and comment on the bug 
if you see anything worrying.
Goal is to merge this change within a couple of days.

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/20150923/b71a5463/attachment.html 

From psrna at redhat.com  Wed Sep 23 06:35:26 2015
From: psrna at redhat.com (Pavol Srna)
Date: Wed, 23 Sep 2015 12:35:26 +0200
Subject: [jbosstools-dev] Please create 4.3.0.CR2 version in Jira
Message-ID: <5602806E.3050806@redhat.com>

$subj

Thanks!

-- 
Pavol Srna
JBoss QA Engineer, JBDS
Phone: +420 532 294 352, +420 774 519 396

Red Hat Czech
Purkynova 99, 612 00 Brno, Czech Republic


From manderse at redhat.com  Wed Sep 23 08:21:14 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 23 Sep 2015 14:21:14 +0200
Subject: [jbosstools-dev] TARGET_PLATFORM_VERSION value in
 parent/pom.xml for jbosstools-4.3.x branch
In-Reply-To: <5602457D.9080307@redhat.com>
References: <CAJXFskZzS5D+0wioUxjqZQskyUu2NKdEMN=X89ZggrVQH1ZSKw@mail.gmail.com>
	<5602457D.9080307@redhat.com>
Message-ID: <1B55F7BF-8B98-4812-A147-146471AEEFA5@redhat.com>

On 23 Sep 2015, at 8:23, Mickael Istria wrote:

> On 09/23/2015 01:08 AM, Denis Golovin wrote:
>> While having troubles with master build I realized parent/pom.xml 
>> property TARGET_PLATFORM_VERSION has wrong value. As I remember the 
>> idea was to keep building the code base with TP based on Mars.0 
>> release and running tests with TP based on latest Mars release.
>
> On master, the idea is to build against Neon, and a few minutes ago, I 
> made necessary changes in parent pom and CI jobs for master branch to 
> consume TP 4.60.0.Alpha1-SNAPSHOT, which will soon host Neon bundles.
> The idea of building against Mars.0 (4.50.0.Final) and testing against 
> Mars.1 (4.51.0.Final) is for jbosstools-4.3.x jobs.

But is that not exactly what Denis is pointing out is currently broken ?

For 4.3.x: "TARGET_PLATFORM_VERSION has wrong value. As I remember the 
idea was to keep building the code base with TP based on Mars.0"

/max
http://about.me/maxandersen

From nboldt at redhat.com  Wed Sep 23 08:47:46 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 23 Sep 2015 08:47:46 -0400
Subject: [jbosstools-dev] Please create 4.3.0.CR2 version in Jira
In-Reply-To: <5602806E.3050806@redhat.com>
References: <5602806E.3050806@redhat.com>
Message-ID: <CA+QcL11Fb_QhdP3B89mSkWsu6yoYfYrhFfLnp1Xb7SXg9FedUQ@mail.gmail.com>

Please clarify. Have we (Max, Alexey, Burr, Jiri) decided we need a CR2?

Why can't you use 4.3.0.Final?

Nick

On Wed, Sep 23, 2015 at 6:35 AM, Pavol Srna <psrna at redhat.com> wrote:
> $subj
>
> Thanks!
>
> --
> Pavol Srna
> JBoss QA Engineer, JBDS
> Phone: +420 532 294 352, +420 774 519 396
>
> Red Hat Czech
> Purkynova 99, 612 00 Brno, Czech Republic
>
> _______________________________________________
> 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 psrna at redhat.com  Wed Sep 23 09:12:25 2015
From: psrna at redhat.com (Pavol Srna)
Date: Wed, 23 Sep 2015 15:12:25 +0200
Subject: [jbosstools-dev] Please create 4.3.0.CR2 version in Jira
In-Reply-To: <CA+QcL11Fb_QhdP3B89mSkWsu6yoYfYrhFfLnp1Xb7SXg9FedUQ@mail.gmail.com>
References: <5602806E.3050806@redhat.com>
	<CA+QcL11Fb_QhdP3B89mSkWsu6yoYfYrhFfLnp1Xb7SXg9FedUQ@mail.gmail.com>
Message-ID: <5602A539.5020300@redhat.com>

1) I thought it is set in stone that we do a CR2. Quoting Len's email:

"we should meet on Tuesday to assess our QE confidence level - release 
CR1 to obtain community feedback - then complete a full test cycle to 
ensure that all the bugs are caught in time to be fixed in CR2. Thanks!"

, but apparently it is not.

2) we have a blocker: https://issues.jboss.org/browse/JBIDE-20770

-P.

On 23.9.2015 14:47, Nick Boldt wrote:
> Please clarify. Have we (Max, Alexey, Burr, Jiri) decided we need a CR2?
>
> Why can't you use 4.3.0.Final?
>
> Nick
>
> On Wed, Sep 23, 2015 at 6:35 AM, Pavol Srna <psrna at redhat.com> wrote:
>> $subj
>>
>> Thanks!
>>
>> --
>> Pavol Srna
>> JBoss QA Engineer, JBDS
>> Phone: +420 532 294 352, +420 774 519 396
>>
>> Red Hat Czech
>> Purkynova 99, 612 00 Brno, Czech Republic
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>


-- 
Pavol Srna
JBoss QA Engineer, JBDS
Phone: +420 532 294 352, +420 774 519 396

Red Hat Czech
Purkynova 99, 612 00 Brno, Czech Republic


From alkazako at redhat.com  Wed Sep 23 09:27:08 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Wed, 23 Sep 2015 09:27:08 -0400
Subject: [jbosstools-dev] Please create 4.3.0.CR2 version in Jira
In-Reply-To: <5602A539.5020300@redhat.com>
References: <5602806E.3050806@redhat.com>
	<CA+QcL11Fb_QhdP3B89mSkWsu6yoYfYrhFfLnp1Xb7SXg9FedUQ@mail.gmail.com>
	<5602A539.5020300@redhat.com>
Message-ID: <5602A8AC.5030400@redhat.com>

What email are you quoting? Did I miss something?

On 09/23/2015 09:12 AM, Pavol Srna wrote:
> 1) I thought it is set in stone that we do a CR2. Quoting Len's email:
>
> "we should meet on Tuesday to assess our QE confidence level - release
> CR1 to obtain community feedback - then complete a full test cycle to
> ensure that all the bugs are caught in time to be fixed in CR2. Thanks!"
>
> , but apparently it is not.
>
> 2) we have a blocker: https://issues.jboss.org/browse/JBIDE-20770
>
> -P.
>
> On 23.9.2015 14:47, Nick Boldt wrote:
>> Please clarify. Have we (Max, Alexey, Burr, Jiri) decided we need a CR2?
>>
>> Why can't you use 4.3.0.Final?
>>
>> Nick
>>
>> On Wed, Sep 23, 2015 at 6:35 AM, Pavol Srna <psrna at redhat.com> wrote:
>>> $subj
>>>
>>> Thanks!
>>>
>>> --
>>> Pavol Srna
>>> JBoss QA Engineer, JBDS
>>> Phone: +420 532 294 352, +420 774 519 396
>>>
>>> Red Hat Czech
>>> Purkynova 99, 612 00 Brno, Czech Republic
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>


From psrna at redhat.com  Wed Sep 23 09:42:34 2015
From: psrna at redhat.com (Pavol Srna)
Date: Wed, 23 Sep 2015 15:42:34 +0200
Subject: [jbosstools-dev] Please create 4.3.0.CR2 version in Jira
In-Reply-To: <5602A8AC.5030400@redhat.com>
References: <5602806E.3050806@redhat.com>
	<CA+QcL11Fb_QhdP3B89mSkWsu6yoYfYrhFfLnp1Xb7SXg9FedUQ@mail.gmail.com>
	<5602A539.5020300@redhat.com> <5602A8AC.5030400@redhat.com>
Message-ID: <5602AC4A.6040700@redhat.com>

It was an email on jbds-qe-list as I see now, so it has not reached you 
probably.
 From that email *I thought* it is already decided to do a CR2. But 
apparently it was not decided.

Anyway since we have a blocker and we continue testing (more bugs may be 
found), we need to decide if we do CR2 on pm call.


-P.

On 23.9.2015 15:27, Alexey Kazakov wrote:
> What email are you quoting? Did I miss something?
>
> On 09/23/2015 09:12 AM, Pavol Srna wrote:
>> 1) I thought it is set in stone that we do a CR2. Quoting Len's email:
>>
>> "we should meet on Tuesday to assess our QE confidence level - release
>> CR1 to obtain community feedback - then complete a full test cycle to
>> ensure that all the bugs are caught in time to be fixed in CR2. Thanks!"
>>
>> , but apparently it is not.
>>
>> 2) we have a blocker: https://issues.jboss.org/browse/JBIDE-20770
>>
>> -P.
>>
>> On 23.9.2015 14:47, Nick Boldt wrote:
>>> Please clarify. Have we (Max, Alexey, Burr, Jiri) decided we need a CR2?
>>>
>>> Why can't you use 4.3.0.Final?
>>>
>>> Nick
>>>
>>> On Wed, Sep 23, 2015 at 6:35 AM, Pavol Srna <psrna at redhat.com> wrote:
>>>> $subj
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> Pavol Srna
>>>> JBoss QA Engineer, JBDS
>>>> Phone: +420 532 294 352, +420 774 519 396
>>>>
>>>> Red Hat Czech
>>>> Purkynova 99, 612 00 Brno, Czech Republic
>>>>
>>>> _______________________________________________
>>>> 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


-- 
Pavol Srna
JBoss QA Engineer, JBDS
Phone: +420 532 294 352, +420 774 519 396

Red Hat Czech
Purkynova 99, 612 00 Brno, Czech Republic


From alkazako at redhat.com  Wed Sep 23 09:44:47 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Wed, 23 Sep 2015 09:44:47 -0400
Subject: [jbosstools-dev] Please create 4.3.0.CR2 version in Jira
In-Reply-To: <5602AC4A.6040700@redhat.com>
References: <5602806E.3050806@redhat.com>
	<CA+QcL11Fb_QhdP3B89mSkWsu6yoYfYrhFfLnp1Xb7SXg9FedUQ@mail.gmail.com>
	<5602A539.5020300@redhat.com> <5602A8AC.5030400@redhat.com>
	<5602AC4A.6040700@redhat.com>
Message-ID: <5602ACCF.2000502@redhat.com>

Sure, we will discuss it on the next PM call tomorrow. Use 4.3.0.Final 
version for such bugs so far.

On 09/23/2015 09:42 AM, Pavol Srna wrote:
> It was an email on jbds-qe-list as I see now, so it has not reached you
> probably.
>   From that email *I thought* it is already decided to do a CR2. But
> apparently it was not decided.
>
> Anyway since we have a blocker and we continue testing (more bugs may be
> found), we need to decide if we do CR2 on pm call.
>
>
> -P.
>
> On 23.9.2015 15:27, Alexey Kazakov wrote:
>> What email are you quoting? Did I miss something?
>>
>> On 09/23/2015 09:12 AM, Pavol Srna wrote:
>>> 1) I thought it is set in stone that we do a CR2. Quoting Len's email:
>>>
>>> "we should meet on Tuesday to assess our QE confidence level - release
>>> CR1 to obtain community feedback - then complete a full test cycle to
>>> ensure that all the bugs are caught in time to be fixed in CR2. Thanks!"
>>>
>>> , but apparently it is not.
>>>
>>> 2) we have a blocker: https://issues.jboss.org/browse/JBIDE-20770
>>>
>>> -P.
>>>
>>> On 23.9.2015 14:47, Nick Boldt wrote:
>>>> Please clarify. Have we (Max, Alexey, Burr, Jiri) decided we need a CR2?
>>>>
>>>> Why can't you use 4.3.0.Final?
>>>>
>>>> Nick
>>>>
>>>> On Wed, Sep 23, 2015 at 6:35 AM, Pavol Srna <psrna at redhat.com> wrote:
>>>>> $subj
>>>>>
>>>>> Thanks!
>>>>>
>>>>> --
>>>>> Pavol Srna
>>>>> JBoss QA Engineer, JBDS
>>>>> Phone: +420 532 294 352, +420 774 519 396
>>>>>
>>>>> Red Hat Czech
>>>>> Purkynova 99, 612 00 Brno, Czech Republic
>>>>>
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>


From nickboldt at gmail.com  Wed Sep 23 10:06:54 2015
From: nickboldt at gmail.com (Nick Boldt)
Date: Wed, 23 Sep 2015 10:06:54 -0400
Subject: [jbosstools-dev] Possible Respin of Mars.1 (because of Buildship)
Message-ID: <CAAOoWTRP5DmRZqKw+iMiYmP_YzWDgE3rv=LmU5Bzj1ft9gEV7g@mail.gmail.com>

FYI.

Since we don't include Buildship, this probably won't affect us much.
But it DOES mean that some users of Mars.1 EPP bundles (who also use
Buildship) might hit the problem mentioned below, unless they upgrade
to Mars.1a.

Nick


---------- Forwarded message ----------
From: Doug Schaefer <dschaefer at qnx.com>
Date: Wed, Sep 23, 2015 at 9:55 AM
Subject: [eclipse.org-planning-council] FW: Respin of Mars 1 for Buildship
To: Eclipse Planning Council <eclipse.org-planning-council at eclipse.org>


For your consideration.

I?ve commented on the cross-projects list with my thinking here. Since
we don?t seem to have a way to ensure we get maintenance releases of
the projects to users of the EPP packages, we have to do what?s right
for the users of those packages and fix these problems how we can. And
unfortunately, right now, that requires a respin.

Doug.

From: <tools-pmc-bounces at eclipse.org> on behalf of Etienne Studer
<etienne at gradle.com>
Reply-To: Tools PMC mailing list <tools-pmc at eclipse.org>
Date: Wednesday, September 23, 2015 at 7:28 AM
To: Tools PMC mailing list <tools-pmc at eclipse.org>
Subject: [tools-pmc] [Request] Respin of Mars 1

Hello

I?d like to ask the Tools PMC to do a re-spin of Mars 1 due to a
critical bug in Buildship 1.0.3, the Buildship version that is
currently in Mars 1 RC4 and its EPP packages (Java / Committer / RCP).
The bug has been fixed in Buildship 1.0.5.

See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=478151

Some details below:

What is the bug?
Buildship calls Bundle#start() to eagerly activate its UI plugin. This
is a problem since it causes the OSGi framework to persistently mark
that bundle for eager activation upon restart. Once Eclipse is
restarted, the bundle that was persistently activated will be
activated very early in the startup process which will likely cause it
to touch preferences 'too early' which results in no workspace prompt
and the default workspace being used.

See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=478054.

How does the bug become apparent?
Once a Gradle task has been launched from the Tasks View, the user
will not be prompted for the workspace anymore the next time he starts
Eclipse, but instead the very default Eclipse workspace is used.

Who is affected?
The bug affects those users (and only those users) that run a Gradle
task through Buildship from within Eclipse.

When was the bug identified and investigated?
We were able to confirm that this is a Buildship bug yesterday. We
also found the cause and a fix yesterday. All Buildship versions <
1.0.5 contain the bug.

When was this bug introduced?
The bug is there since June 6th, as we have found out in retrospect (yesterday).

Why was this bug not found earlier?
Most likely, because the relation between Buildship and how the bug
manifests itself in Eclipse is not obvious to the user observing the
issue.

Is there a fix available?
Yes, the fix is available in Buildship 1.0.5, available as of last
night. It has been confirmed by three Gradle forum users that the
issue has been resolved in Buildship 1.0.5 .

I believe that it is critical for the introduction of Buildship into
the Eclipse SimRel and the Eclipse distributions that we get this fix
in for Mars 1. Otherwise, it will be a bad start for Buildship,
especially considering that the bug was known before the release and a
fix would have been available. Also, users might associate the bug
with a general Eclipse problem, which could cause unfair frustrations
about the Eclipse IDE.

Thanks for considering it.

Regards, Etienne


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public information. Any use of this information by anyone other
than the intended recipient is prohibited. If you have received this
transmission in error, please immediately reply to the sender and
delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended
recipients is not authorized and may be unlawful.

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

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


-- 
Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat, Inc.
http://nick.divbyzero.com
-------------- next part --------------
_______________________________________________
tools-pmc mailing list
tools-pmc at eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tools-pmc

From nboldt at redhat.com  Wed Sep 23 10:10:44 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 23 Sep 2015 10:10:44 -0400
Subject: [jbosstools-dev] Please create 4.3.0.CR2 version in Jira
In-Reply-To: <5602ACCF.2000502@redhat.com>
References: <5602806E.3050806@redhat.com>
	<CA+QcL11Fb_QhdP3B89mSkWsu6yoYfYrhFfLnp1Xb7SXg9FedUQ@mail.gmail.com>
	<5602A539.5020300@redhat.com> <5602A8AC.5030400@redhat.com>
	<5602AC4A.6040700@redhat.com> <5602ACCF.2000502@redhat.com>
Message-ID: <CA+QcL13a7JmUpkVtvi=e2EE_k5oR0z801nq0rJj1mwFHzx=wHw@mail.gmail.com>

Bear in mind that we can fix blockers as part of the respin(s) for
.Final/.GA coming up this/next week. The first of these should be out
on Friday (if all goes well) or Sunday (if not).

So we only need a CR2 if we feel we need ANOTHER 2 weeks beyond Oct 6
for more testing / blocker fixing, AND if we need to actually RELEASE
something as CR2 to public.

If we need to slip but DON'T need to release anything to public, we
can simply call the next builds .Final and hold them back from release
(left in /staging/ folders) until everyone is happy.



On Wed, Sep 23, 2015 at 9:44 AM, Alexey Kazakov <alkazako at redhat.com> wrote:
> Sure, we will discuss it on the next PM call tomorrow. Use 4.3.0.Final
> version for such bugs so far.
>
> On 09/23/2015 09:42 AM, Pavol Srna wrote:
>> It was an email on jbds-qe-list as I see now, so it has not reached you
>> probably.
>>   From that email *I thought* it is already decided to do a CR2. But
>> apparently it was not decided.
>>
>> Anyway since we have a blocker and we continue testing (more bugs may be
>> found), we need to decide if we do CR2 on pm call.
>>
>>
>> -P.
>>
>> On 23.9.2015 15:27, Alexey Kazakov wrote:
>>> What email are you quoting? Did I miss something?
>>>
>>> On 09/23/2015 09:12 AM, Pavol Srna wrote:
>>>> 1) I thought it is set in stone that we do a CR2. Quoting Len's email:
>>>>
>>>> "we should meet on Tuesday to assess our QE confidence level - release
>>>> CR1 to obtain community feedback - then complete a full test cycle to
>>>> ensure that all the bugs are caught in time to be fixed in CR2. Thanks!"
>>>>
>>>> , but apparently it is not.
>>>>
>>>> 2) we have a blocker: https://issues.jboss.org/browse/JBIDE-20770
>>>>
>>>> -P.
>>>>
>>>> On 23.9.2015 14:47, Nick Boldt wrote:
>>>>> Please clarify. Have we (Max, Alexey, Burr, Jiri) decided we need a CR2?
>>>>>
>>>>> Why can't you use 4.3.0.Final?
>>>>>
>>>>> Nick
>>>>>
>>>>> On Wed, Sep 23, 2015 at 6:35 AM, Pavol Srna <psrna at redhat.com> wrote:
>>>>>> $subj
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> --
>>>>>> Pavol Srna
>>>>>> JBoss QA Engineer, JBDS
>>>>>> Phone: +420 532 294 352, +420 774 519 396
>>>>>>
>>>>>> Red Hat Czech
>>>>>> Purkynova 99, 612 00 Brno, Czech Republic
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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



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

From mistria at redhat.com  Wed Sep 23 10:58:34 2015
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 23 Sep 2015 16:58:34 +0200
Subject: [jbosstools-dev] TARGET_PLATFORM_VERSION value in
 parent/pom.xml for jbosstools-4.3.x branch
In-Reply-To: <1B55F7BF-8B98-4812-A147-146471AEEFA5@redhat.com>
References: <CAJXFskZzS5D+0wioUxjqZQskyUu2NKdEMN=X89ZggrVQH1ZSKw@mail.gmail.com>
	<5602457D.9080307@redhat.com>
	<1B55F7BF-8B98-4812-A147-146471AEEFA5@redhat.com>
Message-ID: <5602BE1A.6070303@redhat.com>

Ok. I misunderstood.
Here is a proposal for change on jbosstools-4.3.x branch: 
https://github.com/jbosstools/jbosstools-build/pull/203
Note that TP 4.50.0.Final-SNAPSHOT should be released soon, but I 
believe it's better to merge suggested commit ASAP and to append another 
one when 4.50.0.Final is released.

-- 
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/20150923/af0a5bde/attachment-0001.html 

From manderse at redhat.com  Wed Sep 23 11:10:51 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 23 Sep 2015 17:10:51 +0200
Subject: [jbosstools-dev] TARGET_PLATFORM_VERSION value in
 parent/pom.xml for jbosstools-4.3.x branch
In-Reply-To: <5602BE1A.6070303@redhat.com>
References: <CAJXFskZzS5D+0wioUxjqZQskyUu2NKdEMN=X89ZggrVQH1ZSKw@mail.gmail.com>
	<5602457D.9080307@redhat.com>
	<1B55F7BF-8B98-4812-A147-146471AEEFA5@redhat.com>
	<5602BE1A.6070303@redhat.com>
Message-ID: <DEF80C9B-7CB7-4DDC-9784-32C2B8333090@redhat.com>

On 23 Sep 2015, at 16:58, Mickael Istria wrote:

> Ok. I misunderstood.
> Here is a proposal for change on jbosstools-4.3.x branch: 
> https://github.com/jbosstools/jbosstools-build/pull/203
> Note that TP 4.50.0.Final-SNAPSHOT should be released soon, but I 
> believe it's better to merge suggested commit ASAP and to append 
> another one when 4.50.0.Final is released.

so...what was our CR1 built with if not the 4.50.0 ? 4.51.0 ?


/max
http://about.me/maxandersen

From mistria at redhat.com  Wed Sep 23 11:12:11 2015
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 23 Sep 2015 17:12:11 +0200
Subject: [jbosstools-dev] TARGET_PLATFORM_VERSION value in
 parent/pom.xml for jbosstools-4.3.x branch
In-Reply-To: <DEF80C9B-7CB7-4DDC-9784-32C2B8333090@redhat.com>
References: <CAJXFskZzS5D+0wioUxjqZQskyUu2NKdEMN=X89ZggrVQH1ZSKw@mail.gmail.com>
	<5602457D.9080307@redhat.com>
	<1B55F7BF-8B98-4812-A147-146471AEEFA5@redhat.com>
	<5602BE1A.6070303@redhat.com>
	<DEF80C9B-7CB7-4DDC-9784-32C2B8333090@redhat.com>
Message-ID: <5602C14B.7070202@redhat.com>

On 09/23/2015 05:10 PM, Max Rydahl Andersen wrote:
> so...what was our CR1 built with if not the 4.50.0 ? 4.51.0 ?
CR1a was using 4.50.0.CR1-SNAPSHOT, which at that time, had the same 
content as current 4.51.0.Final.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150923/20594fd9/attachment.html 

From alkazako at redhat.com  Wed Sep 23 13:49:19 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Wed, 23 Sep 2015 13:49:19 -0400
Subject: [jbosstools-dev] JBoss Tools 4.3.0.CR1 is now available
Message-ID: <5602E61F.1020807@redhat.com>

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

Announcement Blog: http://tools.jboss.org/blog/cr1-for-mars.html

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

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

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

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

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

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



From nboldt at redhat.com  Wed Sep 23 15:07:06 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 23 Sep 2015 15:07:06 -0400
Subject: [jbosstools-dev] ACTION REQUIRED :Prepare master branch for Alpha1
Message-ID: <CA+QcL10ErpA0hhtLSe_zUSWnFAeG2_NYUg9OZ_NMj2jXz5gjDA@mail.gmail.com>

Some of you may have already upversioned your features/plugins, and
moved to the correct 4.60 target platform / 4.4.0 parent pom.

For those who haven't, or were not sure how, here's a pile of task
JIRAs for you.

Enjoy!

JBDS              : https://issues.jboss.org/browse/JBDS-3529
JBoss Tools       : https://issues.jboss.org/browse/JBIDE-20774
Aerogear          : https://issues.jboss.org/browse/JBIDE-20775
Central Discovery : https://issues.jboss.org/browse/JBIDE-20776
VPE               : https://issues.jboss.org/browse/JBIDE-20777
Integration Tests : https://issues.jboss.org/browse/JBIDE-20778
build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc,
versionwatch: https://issues.jboss.org/browse/JBIDE-20779
Server            : https://issues.jboss.org/browse/JBIDE-20780
Hibernate         : https://issues.jboss.org/browse/JBIDE-20781
Base              : https://issues.jboss.org/browse/JBIDE-20782
OpenShift         : https://issues.jboss.org/browse/JBIDE-20783
Playground        : https://issues.jboss.org/browse/JBIDE-20784
JavaEE            : https://issues.jboss.org/browse/JBIDE-20785
JST               : https://issues.jboss.org/browse/JBIDE-20786
Forge             : https://issues.jboss.org/browse/JBIDE-20787
Birt              : https://issues.jboss.org/browse/JBIDE-20788
BrowserSim        : https://issues.jboss.org/browse/JBIDE-20789
Webservices       : https://issues.jboss.org/browse/JBIDE-20790
Arquillian        : https://issues.jboss.org/browse/JBIDE-20791
Freemarker        : https://issues.jboss.org/browse/JBIDE-20792
Central           : https://issues.jboss.org/browse/JBIDE-20793
LiveReload        : https://issues.jboss.org/browse/JBIDE-20794


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

From manderse at redhat.com  Wed Sep 23 15:33:51 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 23 Sep 2015 21:33:51 +0200
Subject: [jbosstools-dev] Please create 4.3.0.CR2 version in Jira
In-Reply-To: <5602AC4A.6040700@redhat.com>
References: <5602806E.3050806@redhat.com>
	<CA+QcL11Fb_QhdP3B89mSkWsu6yoYfYrhFfLnp1Xb7SXg9FedUQ@mail.gmail.com>
	<5602A539.5020300@redhat.com> <5602A8AC.5030400@redhat.com>
	<5602AC4A.6040700@redhat.com>
Message-ID: <675498BC-DB20-4A80-B713-9BEFE94244F8@redhat.com>

On 23 Sep 2015, at 15:42, Pavol Srna wrote:

> It was an email on jbds-qe-list as I see now, so it has not reached 
> you
> probably.
> From that email *I thought* it is already decided to do a CR2. But
> apparently it was not decided.

It was decided we most likely were not ready for GA after CR1.

Hence why we talk about a CR2.

I've created it in jira now so it can be target for issues.

In case CR2 becomes GA then we can just merge them; but at least it is 
now clearly
separated from CR1.

/max

>
> Anyway since we have a blocker and we continue testing (more bugs may 
> be
> found), we need to decide if we do CR2 on pm call.
>
>
> -P.
>
> On 23.9.2015 15:27, Alexey Kazakov wrote:
>> What email are you quoting? Did I miss something?
>>
>> On 09/23/2015 09:12 AM, Pavol Srna wrote:
>>> 1) I thought it is set in stone that we do a CR2. Quoting Len's 
>>> email:
>>>
>>> "we should meet on Tuesday to assess our QE confidence level - 
>>> release
>>> CR1 to obtain community feedback - then complete a full test cycle 
>>> to
>>> ensure that all the bugs are caught in time to be fixed in CR2. 
>>> Thanks!"
>>>
>>> , but apparently it is not.
>>>
>>> 2) we have a blocker: https://issues.jboss.org/browse/JBIDE-20770
>>>
>>> -P.
>>>
>>> On 23.9.2015 14:47, Nick Boldt wrote:
>>>> Please clarify. Have we (Max, Alexey, Burr, Jiri) decided we need a 
>>>> CR2?
>>>>
>>>> Why can't you use 4.3.0.Final?
>>>>
>>>> Nick
>>>>
>>>> On Wed, Sep 23, 2015 at 6:35 AM, Pavol Srna <psrna at redhat.com> 
>>>> wrote:
>>>>> $subj
>>>>>
>>>>> Thanks!
>>>>>
>>>>> --
>>>>> Pavol Srna
>>>>> JBoss QA Engineer, JBDS
>>>>> Phone: +420 532 294 352, +420 774 519 396
>>>>>
>>>>> Red Hat Czech
>>>>> Purkynova 99, 612 00 Brno, Czech Republic
>>>>>
>>>>> _______________________________________________
>>>>> 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
>
>
> -- 
> Pavol Srna
> JBoss QA Engineer, JBDS
> Phone: +420 532 294 352, +420 774 519 396
>
> Red Hat Czech
> Purkynova 99, 612 00 Brno, Czech Republic
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From manderse at redhat.com  Wed Sep 23 15:48:05 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 23 Sep 2015 21:48:05 +0200
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
	starts
Message-ID: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>

Hey,

A few have noticed that when you build on master after updating parent 
pom you get build failures due to missing neon repos.

This will unfortunately happen until neon streams start (note, this does 
not require any Neon TP to be present but jenkinsare busy doing CR1 
builds so we'll have to wait).

You can use the CR1 parent pom in the meantime - the minimal change 
required is just the version bump so your master and branch builds does 
not collide when building locally.

sorry for this, but I hope Michael/Nick soon can kick of the master 
builds so this will not be a problem. (and no,it does not require usage 
of an actual neon tp - we just need the stream urls built)

/max
http://about.me/maxandersen

From isaac.hickey at diosdesign-wp.com  Wed Sep 23 16:32:49 2015
From: isaac.hickey at diosdesign-wp.com (FedEx SmartPost)
Date: Wed, 23 Sep 2015 13:32:49 -0700
Subject: [jbosstools-dev] Courier was unable to deliver the parcel,
	ID00641460
Message-ID: <ae7517de10da681b169d2481b8f33479@diosdesign-wp.com>

Dear Customer,

Your parcel has arrived at September 20. Courier was unable to deliver the parcel to you.
You can review complete details of your order in the find attached.

Yours faithfully,
Isaac Hickey,
FedEx Station Manager.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 00641460.zip
Type: application/zip
Size: 3061 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150923/e06d73dc/attachment.zip 

From alkazako at redhat.com  Wed Sep 23 16:32:51 2015
From: alkazako at redhat.com (Alexey Kazakov)
Date: Wed, 23 Sep 2015 16:32:51 -0400
Subject: [jbosstools-dev] JBT 4.3.0.CR1 tags have been created
Message-ID: <56030C73.10407@redhat.com>

Hi,

Thanks to Max's script we were be able to create jbosstools-4.3.0.CR1 
tags for every jbosstools-* repo we use in JBT.

So, no need to manually tag our 4.3.x branch after CR1 release this time.

Thanks.

From nboldt at redhat.com  Wed Sep 23 16:37:11 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 23 Sep 2015 16:37:11 -0400
Subject: [jbosstools-dev] Suggested change in Target-Platform
 4.60.0.Alpha1-SNAPSHOT: Neon M1
In-Reply-To: <56027D0A.9000003@redhat.com>
References: <56027D0A.9000003@redhat.com>
Message-ID: <CA+QcL1072yZXBmdGYgVzPcgz8xnuvHiBZgEqAXZ_a6sgSNAb4g@mail.gmail.com>

Seems legit. Merge with impunity.

On Wed, Sep 23, 2015 at 6:20 AM, Mickael Istria <mistria at redhat.com> wrote:
> Hi all,
>
> Here is a suggested change for target-platforms 4.60.0.Alpha1-SNAPSHOT,
> which is currently used when building from master branch:
> * Move to Neon M1 https://issues.jboss.org/browse/JBIDE-20749
>
> Please review the suggested patch and the p2diff, and comment on the bug if
> you see anything worrying.
> Goal is to merge this change within a couple of days.
>
> Cheers,
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev



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

From manderse at redhat.com  Thu Sep 24 01:28:19 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 24 Sep 2015 07:28:19 +0200
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
 starts
In-Reply-To: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
Message-ID: <20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>

Looks like this are now fixed since I now see 
http://download.jboss.org/jbosstools/neon/snapshots/builds/ filled up.

Nick/Michael - can you give an update on what changed ?

Have we restarted the master builds fully now using for now mars based 
TP, or was it just a single run to make builds
work ?

Thanks,
/max

> Hey,
>
> A few have noticed that when you build on master after updating parent
> pom you get build failures due to missing neon repos.
>
> This will unfortunately happen until neon streams start (note, this 
> does
> not require any Neon TP to be present but jenkinsare busy doing CR1
> builds so we'll have to wait).
>
> You can use the CR1 parent pom in the meantime - the minimal change
> required is just the version bump so your master and branch builds 
> does
> not collide when building locally.
>
> sorry for this, but I hope Michael/Nick soon can kick of the master
> builds so this will not be a problem. (and no,it does not require 
> usage
> of an actual neon tp - we just need the stream urls built)
>
> /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 mistria at redhat.com  Thu Sep 24 02:17:36 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 24 Sep 2015 08:17:36 +0200
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
 starts
In-Reply-To: <20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
Message-ID: <56039580.8010107@redhat.com>

On 09/24/2015 07:28 AM, Max Rydahl Andersen wrote:
> Looks like this are now fixed since I now see
> http://download.jboss.org/jbosstools/neon/snapshots/builds/ filled up.
>
> Nick/Michael - can you give an update on what changed ?

What changed is:
* Update of the 4.4.0.Alpha1-SNAPSHOT parent pom to reference an existing TP
* Update of components to bump their version and reference to parent pom 
(to publish to the right location and not conflict with baseline)
> Have we restarted the master builds fully now using for now mars based
> TP, or was it just a single run to make builds
> work ?
AFAIK, the builds for master were kept running, but since they weren't 
using the newer TP at that time, their output wasn't visible in the Neon 
folder.
The branching steps for components should include steps for immediate 
adoption of newer pom on master.

-- 
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/20150924/d4d20e94/attachment.html 

From manderse at redhat.com  Thu Sep 24 02:20:04 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 24 Sep 2015 08:20:04 +0200
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
 starts
In-Reply-To: <20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
Message-ID: <A52E11CD-7C50-4997-B390-A6A1E6BC7DC0@redhat.com>

On 24 Sep 2015, at 7:28, Max Rydahl Andersen wrote:

> Looks like this are now fixed since I now see
> http://download.jboss.org/jbosstools/neon/snapshots/builds/ filled up.
>
> Nick/Michael - can you give an update on what changed ?

Talked with Michael and seems what changed is just that jbosstools-base 
were missing
version bump. Now that is done it trickles down to all builds as soon
as they get their version bumped.

In past master builds were stopped since jenkins was overloaded, that 
seem not to be
the case anymore so if we just do proper branching with a version bump 
and stream name change both master and branch can be developed 
concurrently without any accidental overlaps.

/max

>
> Have we restarted the master builds fully now using for now mars based
> TP, or was it just a single run to make builds
> work ?
>
> Thanks,
> /max
>
>> Hey,
>>
>> A few have noticed that when you build on master after updating 
>> parent
>> pom you get build failures due to missing neon repos.
>>
>> This will unfortunately happen until neon streams start (note, this
>> does
>> not require any Neon TP to be present but jenkinsare busy doing CR1
>> builds so we'll have to wait).
>>
>> You can use the CR1 parent pom in the meantime - the minimal change
>> required is just the version bump so your master and branch builds
>> does
>> not collide when building locally.
>>
>> sorry for this, but I hope Michael/Nick soon can kick of the master
>> builds so this will not be a problem. (and no,it does not require
>> usage
>> of an actual neon tp - we just need the stream urls built)
>>
>> /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


/max
http://about.me/maxandersen

From mistria at redhat.com  Thu Sep 24 04:52:53 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 24 Sep 2015 10:52:53 +0200
Subject: [jbosstools-dev] Suggested change in Target-Platform
 4.60.0.Alpha1-SNAPSHOT: Neon M1
In-Reply-To: <CA+QcL1072yZXBmdGYgVzPcgz8xnuvHiBZgEqAXZ_a6sgSNAb4g@mail.gmail.com>
References: <56027D0A.9000003@redhat.com>
	<CA+QcL1072yZXBmdGYgVzPcgz8xnuvHiBZgEqAXZ_a6sgSNAb4g@mail.gmail.com>
Message-ID: <5603B9E5.5090004@redhat.com>

On 09/23/2015 10:37 PM, Nick Boldt wrote:
> Seems legit. Merge with impunity.
Merged with impunity.


-- 
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/20150924/e367d036/attachment.html 

From manderse at redhat.com  Thu Sep 24 08:40:12 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 24 Sep 2015 14:40:12 +0200
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
 starts
In-Reply-To: <56039580.8010107@redhat.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
	<56039580.8010107@redhat.com>
Message-ID: <CB397233-232E-4C54-87E2-7EC1D9D80CDE@redhat.com>

>> Have we restarted the master builds fully now using for now mars 
>> based
>> TP, or was it just a single run to make builds
>> work ?
> AFAIK, the builds for master were kept running, but since they weren't 
> using the newer TP at that time, their output wasn't visible in the 
> Neon folder.

why would the TP matter ? what TP we target and what the stream name is 
completely separate concerns for us and in the parent pom afaics.

> The branching steps for components should include steps for immediate 
> adoption of newer pom on master.

+1

thanks for the info and discussion this morning - verified we truly can 
make this simpler now that jenkins has enough power to run more builds.
/max
http://about.me/maxandersen

From mistria at redhat.com  Thu Sep 24 08:40:59 2015
From: mistria at redhat.com (Mickael Istria)
Date: Thu, 24 Sep 2015 14:40:59 +0200
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
 starts
In-Reply-To: <CB397233-232E-4C54-87E2-7EC1D9D80CDE@redhat.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
	<56039580.8010107@redhat.com>
	<CB397233-232E-4C54-87E2-7EC1D9D80CDE@redhat.com>
Message-ID: <5603EF5B.4090101@redhat.com>

On 09/24/2015 02:40 PM, Max Rydahl Andersen wrote:
>>> Have we restarted the master builds fully now using for now mars based
>>> TP, or was it just a single run to make builds
>>> work ?
>> AFAIK, the builds for master were kept running, but since they 
>> weren't using the newer TP at that time, their output wasn't visible 
>> in the Neon folder.
> why would the TP matter ? what TP we target and what the stream name 
> is completely separate concerns for us and in the parent pom afaics.
Sorry! But you got it: I meant "parent"
-- 
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/20150924/7b95e6b4/attachment.html 

From nboldt at redhat.com  Thu Sep 24 08:56:16 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 24 Sep 2015 08:56:16 -0400
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
	starts
In-Reply-To: <A52E11CD-7C50-4997-B390-A6A1E6BC7DC0@redhat.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
	<A52E11CD-7C50-4997-B390-A6A1E6BC7DC0@redhat.com>
Message-ID: <CA+QcL10TYQfaC_mP-+dqeYbjc=zxWNnAknzLRTjq7wXgV1n10g@mail.gmail.com>

What changed was that I moved all the _master build results folders
under /mars/snapshots/ to /neon/snapshots/ so that all the URLs listed
in the Alpha1 parent pom could be resolved and therefore all the
interproject dependencies could be found.

This was verified by Fred saying "my job is broken" then I did the
move, and he confirmed "build completed ok".



On Thu, Sep 24, 2015 at 2:20 AM, Max Rydahl Andersen
<manderse at redhat.com> wrote:
> On 24 Sep 2015, at 7:28, Max Rydahl Andersen wrote:
>
>> Looks like this are now fixed since I now see
>> http://download.jboss.org/jbosstools/neon/snapshots/builds/ filled up.
>>
>> Nick/Michael - can you give an update on what changed ?
>
> Talked with Michael and seems what changed is just that jbosstools-base
> were missing
> version bump. Now that is done it trickles down to all builds as soon
> as they get their version bumped.
>
> In past master builds were stopped since jenkins was overloaded, that
> seem not to be
> the case anymore so if we just do proper branching with a version bump
> and stream name change both master and branch can be developed
> concurrently without any accidental overlaps.
>
> /max
>
>>
>> Have we restarted the master builds fully now using for now mars based
>> TP, or was it just a single run to make builds
>> work ?
>>
>> Thanks,
>> /max
>>
>>> Hey,
>>>
>>> A few have noticed that when you build on master after updating
>>> parent
>>> pom you get build failures due to missing neon repos.
>>>
>>> This will unfortunately happen until neon streams start (note, this
>>> does
>>> not require any Neon TP to be present but jenkinsare busy doing CR1
>>> builds so we'll have to wait).
>>>
>>> You can use the CR1 parent pom in the meantime - the minimal change
>>> required is just the version bump so your master and branch builds
>>> does
>>> not collide when building locally.
>>>
>>> sorry for this, but I hope Michael/Nick soon can kick of the master
>>> builds so this will not be a problem. (and no,it does not require
>>> usage
>>> of an actual neon tp - we just need the stream urls built)
>>>
>>> /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
>
>
> /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 mmalina at redhat.com  Thu Sep 24 10:05:33 2015
From: mmalina at redhat.com (Martin Malina)
Date: Thu, 24 Sep 2015 16:05:33 +0200
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
	starts
In-Reply-To: <CA+QcL10TYQfaC_mP-+dqeYbjc=zxWNnAknzLRTjq7wXgV1n10g@mail.gmail.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
	<A52E11CD-7C50-4997-B390-A6A1E6BC7DC0@redhat.com>
	<CA+QcL10TYQfaC_mP-+dqeYbjc=zxWNnAknzLRTjq7wXgV1n10g@mail.gmail.com>
Message-ID: <D4EC9A7A-4C15-4F5B-A7A0-7525FAF75F7C@redhat.com>

Did you forget about integration tests?
http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-tests/master/ <http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-tests/master/>

-Martin

> On 24. 9. 2015, at 14:56, Nick Boldt <nboldt at redhat.com> wrote:
> 
> What changed was that I moved all the _master build results folders
> under /mars/snapshots/ to /neon/snapshots/ so that all the URLs listed
> in the Alpha1 parent pom could be resolved and therefore all the
> interproject dependencies could be found.
> 
> This was verified by Fred saying "my job is broken" then I did the
> move, and he confirmed "build completed ok".
> 
> 
> 
> On Thu, Sep 24, 2015 at 2:20 AM, Max Rydahl Andersen
> <manderse at redhat.com> wrote:
>> On 24 Sep 2015, at 7:28, Max Rydahl Andersen wrote:
>> 
>>> Looks like this are now fixed since I now see
>>> http://download.jboss.org/jbosstools/neon/snapshots/builds/ filled up.
>>> 
>>> Nick/Michael - can you give an update on what changed ?
>> 
>> Talked with Michael and seems what changed is just that jbosstools-base
>> were missing
>> version bump. Now that is done it trickles down to all builds as soon
>> as they get their version bumped.
>> 
>> In past master builds were stopped since jenkins was overloaded, that
>> seem not to be
>> the case anymore so if we just do proper branching with a version bump
>> and stream name change both master and branch can be developed
>> concurrently without any accidental overlaps.
>> 
>> /max
>> 
>>> 
>>> Have we restarted the master builds fully now using for now mars based
>>> TP, or was it just a single run to make builds
>>> work ?
>>> 
>>> Thanks,
>>> /max
>>> 
>>>> Hey,
>>>> 
>>>> A few have noticed that when you build on master after updating
>>>> parent
>>>> pom you get build failures due to missing neon repos.
>>>> 
>>>> This will unfortunately happen until neon streams start (note, this
>>>> does
>>>> not require any Neon TP to be present but jenkinsare busy doing CR1
>>>> builds so we'll have to wait).
>>>> 
>>>> You can use the CR1 parent pom in the meantime - the minimal change
>>>> required is just the version bump so your master and branch builds
>>>> does
>>>> not collide when building locally.
>>>> 
>>>> sorry for this, but I hope Michael/Nick soon can kick of the master
>>>> builds so this will not be a problem. (and no,it does not require
>>>> usage
>>>> of an actual neon tp - we just need the stream urls built)
>>>> 
>>>> /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
>> 
>> 
>> /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/20150924/96beb7cb/attachment-0001.html 

From nboldt at redhat.com  Thu Sep 24 15:03:43 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 24 Sep 2015 15:03:43 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze for 4.3.0.Final /
	9.0.0.GA
Message-ID: <CA+QcL10anRbhsU1=N2zbp4nU+YbQruBciiC7my-F+Ss53LDJNQ@mail.gmail.com>

It's time to update your root poms to use the latest
4.3.0.Final-SNAPSHOT parent pom.

Here's some Task JIRAs:

JBDS              : https://issues.jboss.org/browse/JBDS-3530
JBoss Tools       : https://issues.jboss.org/browse/JBIDE-20805
Aerogear          : https://issues.jboss.org/browse/JBIDE-20806
Central Discovery : https://issues.jboss.org/browse/JBIDE-20807
VPE               : https://issues.jboss.org/browse/JBIDE-20808
Integration Tests : https://issues.jboss.org/browse/JBIDE-20809
build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc,
versionwatch: https://issues.jboss.org/browse/JBIDE-20810
Server            : https://issues.jboss.org/browse/JBIDE-20811
Hibernate         : https://issues.jboss.org/browse/JBIDE-20812
Base              : https://issues.jboss.org/browse/JBIDE-20813
OpenShift         : https://issues.jboss.org/browse/JBIDE-20814
Playground        : https://issues.jboss.org/browse/JBIDE-20815
JavaEE            : https://issues.jboss.org/browse/JBIDE-20816
JST               : https://issues.jboss.org/browse/JBIDE-20817
Forge             : https://issues.jboss.org/browse/JBIDE-20818
Birt              : https://issues.jboss.org/browse/JBIDE-20819
BrowserSim        : https://issues.jboss.org/browse/JBIDE-20820
Webservices       : https://issues.jboss.org/browse/JBIDE-20821
Arquillian        : https://issues.jboss.org/browse/JBIDE-20822
Freemarker        : https://issues.jboss.org/browse/JBIDE-20823
Central           : https://issues.jboss.org/browse/JBIDE-20824
LiveReload        : https://issues.jboss.org/browse/JBIDE-20825


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

From dgolovin at exadel.com  Thu Sep 24 22:51:58 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Thu, 24 Sep 2015 19:51:58 -0700
Subject: [jbosstools-dev] Suggested change in Target-Platform
 4.60.0.Alpha1-SNAPSHOT: Neon M1
In-Reply-To: <5603B9E5.5090004@redhat.com>
References: <56027D0A.9000003@redhat.com>
	<CA+QcL1072yZXBmdGYgVzPcgz8xnuvHiBZgEqAXZ_a6sgSNAb4g@mail.gmail.com>
	<5603B9E5.5090004@redhat.com>
Message-ID: <CAJXFskYvcrVrtqhmdBw85CDgtVpB9zZd9hxuXkkoeaWGJkHsdg@mail.gmail.com>

All JBoss Tools projects can be built with latest TP, but I still have
couple glitches:
1. jbds sources download fails 8 out of 10 builds
[INFO] [ERROR] Failed to execute goal
org.jboss.tools.tycho-plugins:repository-utils:0.23.1:fetch-sources-from-manifests
(fetch-sources) on project com.jboss.devstudio.core.site: Error cloning
from /home/eskimo/Projects/jbdevstudio/4.4.x/releng/jbdevstudio-product to
/tmp/git at github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip:
/tmp/git at github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip
(No such file or directory) -> [Help 1]

2. Portlet is not using parent pom 4.4.0.Alpha2-SNAPSHOT.
On 09/23/2015 10:37 PM, Nick Boldt wrote:

Seems legit. Merge with impunity.

Merged with impunity.


-- 
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>

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

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

-- 


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

From manderse at redhat.com  Fri Sep 25 08:03:44 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 25 Sep 2015 08:03:44 -0400 (EDT)
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
	starts
In-Reply-To: <CA+QcL10TYQfaC_mP-+dqeYbjc=zxWNnAknzLRTjq7wXgV1n10g@mail.gmail.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
	<A52E11CD-7C50-4997-B390-A6A1E6BC7DC0@redhat.com>
	<CA+QcL10TYQfaC_mP-+dqeYbjc=zxWNnAknzLRTjq7wXgV1n10g@mail.gmail.com>
Message-ID: <EFA3DE16-6A79-4735-A151-AE051EFAB0B7@redhat.com>

Great. Now it makes sense. 

That explains why I could do builds that shouldn't be possible and confused he heck out of me. 

In future I think it is much saner to point out which components haven't properly built and ask Dev to fix those rather than make it look like the neon stream of components actually are in a buildable state. 

Please also share such moves to the team when they happen. Would spare a lot of time not having to second guess why builds failed/worked when expected they shouldn't.

/max
http://about.me/maxandersen


> On 24 Sep 2015, at 14:56, Nick Boldt <nboldt at redhat.com> wrote:
> 
> What changed was that I moved all the _master build results folders
> under /mars/snapshots/ to /neon/snapshots/ so that all the URLs listed
> in the Alpha1 parent pom could be resolved and therefore all the
> interproject dependencies could be found.
> 
> This was verified by Fred saying "my job is broken" then I did the
> move, and he confirmed "build completed ok".
> 
> 
> 
> On Thu, Sep 24, 2015 at 2:20 AM, Max Rydahl Andersen
> <manderse at redhat.com> wrote:
>> On 24 Sep 2015, at 7:28, Max Rydahl Andersen wrote:
>> 
>>> Looks like this are now fixed since I now see
>>> http://download.jboss.org/jbosstools/neon/snapshots/builds/ filled up.
>>> 
>>> Nick/Michael - can you give an update on what changed ?
>> 
>> Talked with Michael and seems what changed is just that jbosstools-base
>> were missing
>> version bump. Now that is done it trickles down to all builds as soon
>> as they get their version bumped.
>> 
>> In past master builds were stopped since jenkins was overloaded, that
>> seem not to be
>> the case anymore so if we just do proper branching with a version bump
>> and stream name change both master and branch can be developed
>> concurrently without any accidental overlaps.
>> 
>> /max
>> 
>>> 
>>> Have we restarted the master builds fully now using for now mars based
>>> TP, or was it just a single run to make builds
>>> work ?
>>> 
>>> Thanks,
>>> /max
>>> 
>>>> Hey,
>>>> 
>>>> A few have noticed that when you build on master after updating
>>>> parent
>>>> pom you get build failures due to missing neon repos.
>>>> 
>>>> This will unfortunately happen until neon streams start (note, this
>>>> does
>>>> not require any Neon TP to be present but jenkinsare busy doing CR1
>>>> builds so we'll have to wait).
>>>> 
>>>> You can use the CR1 parent pom in the meantime - the minimal change
>>>> required is just the version bump so your master and branch builds
>>>> does
>>>> not collide when building locally.
>>>> 
>>>> sorry for this, but I hope Michael/Nick soon can kick of the master
>>>> builds so this will not be a problem. (and no,it does not require
>>>> usage
>>>> of an actual neon tp - we just need the stream urls built)
>>>> 
>>>> /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
>> 
>> 
>> /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 Sep 25 08:05:37 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 25 Sep 2015 08:05:37 -0400 (EDT)
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
	starts
In-Reply-To: <D4EC9A7A-4C15-4F5B-A7A0-7525FAF75F7C@redhat.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
	<A52E11CD-7C50-4997-B390-A6A1E6BC7DC0@redhat.com>
	<CA+QcL10TYQfaC_mP-+dqeYbjc=zxWNnAknzLRTjq7wXgV1n10g@mail.gmail.com>
	<D4EC9A7A-4C15-4F5B-A7A0-7525FAF75F7C@redhat.com>
Message-ID: <0D3E8095-7FCA-42FE-99EA-C9E7AAD82D4B@redhat.com>

These really should not be moved - it's up to components itself to use the right parent Pom which will make it publish to the right place. 

Tricks like moving them over and/or override settings in Jenkins builds should a "last option" tool. 

/max
http://about.me/maxandersen


> On 24 Sep 2015, at 16:05, Martin Malina <mmalina at redhat.com> wrote:
> 
> Did you forget about integration tests?
> http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-tests/master/
> 
> -Martin
> 
>> On 24. 9. 2015, at 14:56, Nick Boldt <nboldt at redhat.com> wrote:
>> 
>> What changed was that I moved all the _master build results folders
>> under /mars/snapshots/ to /neon/snapshots/ so that all the URLs listed
>> in the Alpha1 parent pom could be resolved and therefore all the
>> interproject dependencies could be found.
>> 
>> This was verified by Fred saying "my job is broken" then I did the
>> move, and he confirmed "build completed ok".
>> 
>> 
>> 
>> On Thu, Sep 24, 2015 at 2:20 AM, Max Rydahl Andersen
>> <manderse at redhat.com> wrote:
>>> On 24 Sep 2015, at 7:28, Max Rydahl Andersen wrote:
>>> 
>>>> Looks like this are now fixed since I now see
>>>> http://download.jboss.org/jbosstools/neon/snapshots/builds/ filled up.
>>>> 
>>>> Nick/Michael - can you give an update on what changed ?
>>> 
>>> Talked with Michael and seems what changed is just that jbosstools-base
>>> were missing
>>> version bump. Now that is done it trickles down to all builds as soon
>>> as they get their version bumped.
>>> 
>>> In past master builds were stopped since jenkins was overloaded, that
>>> seem not to be
>>> the case anymore so if we just do proper branching with a version bump
>>> and stream name change both master and branch can be developed
>>> concurrently without any accidental overlaps.
>>> 
>>> /max
>>> 
>>>> 
>>>> Have we restarted the master builds fully now using for now mars based
>>>> TP, or was it just a single run to make builds
>>>> work ?
>>>> 
>>>> Thanks,
>>>> /max
>>>> 
>>>>> Hey,
>>>>> 
>>>>> A few have noticed that when you build on master after updating
>>>>> parent
>>>>> pom you get build failures due to missing neon repos.
>>>>> 
>>>>> This will unfortunately happen until neon streams start (note, this
>>>>> does
>>>>> not require any Neon TP to be present but jenkinsare busy doing CR1
>>>>> builds so we'll have to wait).
>>>>> 
>>>>> You can use the CR1 parent pom in the meantime - the minimal change
>>>>> required is just the version bump so your master and branch builds
>>>>> does
>>>>> not collide when building locally.
>>>>> 
>>>>> sorry for this, but I hope Michael/Nick soon can kick of the master
>>>>> builds so this will not be a problem. (and no,it does not require
>>>>> usage
>>>>> of an actual neon tp - we just need the stream urls built)
>>>>> 
>>>>> /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
>>> 
>>> 
>>> /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/20150925/9f414c52/attachment-0001.html 

From nboldt at redhat.com  Fri Sep 25 08:08:14 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 25 Sep 2015 08:08:14 -0400
Subject: [jbosstools-dev] Suggested change in Target-Platform
 4.60.0.Alpha1-SNAPSHOT: Neon M1
In-Reply-To: <CAJXFskYvcrVrtqhmdBw85CDgtVpB9zZd9hxuXkkoeaWGJkHsdg@mail.gmail.com>
References: <56027D0A.9000003@redhat.com>
	<CA+QcL1072yZXBmdGYgVzPcgz8xnuvHiBZgEqAXZ_a6sgSNAb4g@mail.gmail.com>
	<5603B9E5.5090004@redhat.com>
	<CAJXFskYvcrVrtqhmdBw85CDgtVpB9zZd9hxuXkkoeaWGJkHsdg@mail.gmail.com>
Message-ID: <CA+QcL13f2a_fua_pnuWtHZxO89Rw=bMSKSJJVQVw84nf_wj6jA@mail.gmail.com>

1. You have a colon and @ in your /tmp path. Try again with a less
unfriendly path?

2. Portlet is not currently being built at all. It has no new commits since
JBT 4.2.x.
On Sep 24, 2015 10:52 PM, "Denis Golovin" <dgolovin at exadel.com> wrote:

> All JBoss Tools projects can be built with latest TP, but I still have
> couple glitches:
> 1. jbds sources download fails 8 out of 10 builds
> [INFO] [ERROR] Failed to execute goal
> org.jboss.tools.tycho-plugins:repository-utils:0.23.1:fetch-sources-from-manifests
> (fetch-sources) on project com.jboss.devstudio.core.site: Error cloning
> from /home/eskimo/Projects/jbdevstudio/4.4.x/releng/jbdevstudio-product to
> /tmp/git at github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip:
> /tmp/git at github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip
> (No such file or directory) -> [Help 1]
>
> 2. Portlet is not using parent pom 4.4.0.Alpha2-SNAPSHOT.
> On 09/23/2015 10:37 PM, Nick Boldt wrote:
>
> Seems legit. Merge with impunity.
>
> Merged with impunity.
>
>
> --
> 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>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150925/d2f25b07/attachment.html 

From nboldt at redhat.com  Fri Sep 25 08:10:11 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 25 Sep 2015 08:10:11 -0400
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
	starts
In-Reply-To: <0D3E8095-7FCA-42FE-99EA-C9E7AAD82D4B@redhat.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
	<A52E11CD-7C50-4997-B390-A6A1E6BC7DC0@redhat.com>
	<CA+QcL10TYQfaC_mP-+dqeYbjc=zxWNnAknzLRTjq7wXgV1n10g@mail.gmail.com>
	<D4EC9A7A-4C15-4F5B-A7A0-7525FAF75F7C@redhat.com>
	<0D3E8095-7FCA-42FE-99EA-C9E7AAD82D4B@redhat.com>
Message-ID: <CA+QcL10ykco27Kv57+_97R=agL-MZ=Uc5w7aSje=sK83jyUsSg@mail.gmail.com>

Had I not moved them you'd be getting red balls for all the projects with
long dep chains simply because a project like Server had not migrated to
Alpha1 parent and kicked a new build.

Why inconvenience everyone with false reds and the inability to build
locally?
On Sep 25, 2015 8:05 AM, "Max Rydahl Andersen" <manderse at redhat.com> wrote:

> These really should not be moved - it's up to components itself to use the
> right parent Pom which will make it publish to the right place.
>
> Tricks like moving them over and/or override settings in Jenkins builds
> should a "last option" tool.
>
> /max
> http://about.me/maxandersen
>
>
> On 24 Sep 2015, at 16:05, Martin Malina <mmalina at redhat.com> wrote:
>
> Did you forget about integration tests?
>
> http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-tests/master/
>
> -Martin
>
> On 24. 9. 2015, at 14:56, Nick Boldt <nboldt at redhat.com> wrote:
>
> What changed was that I moved all the _master build results folders
> under /mars/snapshots/ to /neon/snapshots/ so that all the URLs listed
> in the Alpha1 parent pom could be resolved and therefore all the
> interproject dependencies could be found.
>
> This was verified by Fred saying "my job is broken" then I did the
> move, and he confirmed "build completed ok".
>
>
>
> On Thu, Sep 24, 2015 at 2:20 AM, Max Rydahl Andersen
> <manderse at redhat.com> wrote:
>
> On 24 Sep 2015, at 7:28, Max Rydahl Andersen wrote:
>
> Looks like this are now fixed since I now see
> http://download.jboss.org/jbosstools/neon/snapshots/builds/ filled up.
>
> Nick/Michael - can you give an update on what changed ?
>
>
> Talked with Michael and seems what changed is just that jbosstools-base
> were missing
> version bump. Now that is done it trickles down to all builds as soon
> as they get their version bumped.
>
> In past master builds were stopped since jenkins was overloaded, that
> seem not to be
> the case anymore so if we just do proper branching with a version bump
> and stream name change both master and branch can be developed
> concurrently without any accidental overlaps.
>
> /max
>
>
> Have we restarted the master builds fully now using for now mars based
> TP, or was it just a single run to make builds
> work ?
>
> Thanks,
> /max
>
> Hey,
>
> A few have noticed that when you build on master after updating
> parent
> pom you get build failures due to missing neon repos.
>
> This will unfortunately happen until neon streams start (note, this
> does
> not require any Neon TP to be present but jenkinsare busy doing CR1
> builds so we'll have to wait).
>
> You can use the CR1 parent pom in the meantime - the minimal change
> required is just the version bump so your master and branch builds
> does
> not collide when building locally.
>
> sorry for this, but I hope Michael/Nick soon can kick of the master
> builds so this will not be a problem. (and no,it does not require
> usage
> of an actual neon tp - we just need the stream urls built)
>
> /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
>
>
>
> /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/20150925/23b3a0e5/attachment.html 

From nboldt at redhat.com  Fri Sep 25 08:13:35 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 25 Sep 2015 08:13:35 -0400
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
	starts
In-Reply-To: <EFA3DE16-6A79-4735-A151-AE051EFAB0B7@redhat.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
	<A52E11CD-7C50-4997-B390-A6A1E6BC7DC0@redhat.com>
	<CA+QcL10TYQfaC_mP-+dqeYbjc=zxWNnAknzLRTjq7wXgV1n10g@mail.gmail.com>
	<EFA3DE16-6A79-4735-A151-AE051EFAB0B7@redhat.com>
Message-ID: <CA+QcL13H+p8eQhuCX-s-+8nz+6fnihdi3hTqSo8O4Y1B=w89Dw@mail.gmail.com>

No second guessing required. No first guessing either.

Fred reported to me he couldnt build Central because one or more
/neon/snapshots/builds project folder was missing.

Fix: bootstrap those folders by moving content from
/mars/snapshots/builds/jbosstools-*_master into equivalent /neon/ folder.

So... Where was the guesswork?
On Sep 25, 2015 8:03 AM, "Max Rydahl Andersen" <manderse at redhat.com> wrote:

> Great. Now it makes sense.
>
> That explains why I could do builds that shouldn't be possible and
> confused he heck out of me.
>
> In future I think it is much saner to point out which components haven't
> properly built and ask Dev to fix those rather than make it look like the
> neon stream of components actually are in a buildable state.
>
> Please also share such moves to the team when they happen. Would spare a
> lot of time not having to second guess why builds failed/worked when
> expected they shouldn't.
>
> /max
> http://about.me/maxandersen
>
>
> > On 24 Sep 2015, at 14:56, Nick Boldt <nboldt at redhat.com> wrote:
> >
> > What changed was that I moved all the _master build results folders
> > under /mars/snapshots/ to /neon/snapshots/ so that all the URLs listed
> > in the Alpha1 parent pom could be resolved and therefore all the
> > interproject dependencies could be found.
> >
> > This was verified by Fred saying "my job is broken" then I did the
> > move, and he confirmed "build completed ok".
> >
> >
> >
> > On Thu, Sep 24, 2015 at 2:20 AM, Max Rydahl Andersen
> > <manderse at redhat.com> wrote:
> >> On 24 Sep 2015, at 7:28, Max Rydahl Andersen wrote:
> >>
> >>> Looks like this are now fixed since I now see
> >>> http://download.jboss.org/jbosstools/neon/snapshots/builds/ filled up.
> >>>
> >>> Nick/Michael - can you give an update on what changed ?
> >>
> >> Talked with Michael and seems what changed is just that jbosstools-base
> >> were missing
> >> version bump. Now that is done it trickles down to all builds as soon
> >> as they get their version bumped.
> >>
> >> In past master builds were stopped since jenkins was overloaded, that
> >> seem not to be
> >> the case anymore so if we just do proper branching with a version bump
> >> and stream name change both master and branch can be developed
> >> concurrently without any accidental overlaps.
> >>
> >> /max
> >>
> >>>
> >>> Have we restarted the master builds fully now using for now mars based
> >>> TP, or was it just a single run to make builds
> >>> work ?
> >>>
> >>> Thanks,
> >>> /max
> >>>
> >>>> Hey,
> >>>>
> >>>> A few have noticed that when you build on master after updating
> >>>> parent
> >>>> pom you get build failures due to missing neon repos.
> >>>>
> >>>> This will unfortunately happen until neon streams start (note, this
> >>>> does
> >>>> not require any Neon TP to be present but jenkinsare busy doing CR1
> >>>> builds so we'll have to wait).
> >>>>
> >>>> You can use the CR1 parent pom in the meantime - the minimal change
> >>>> required is just the version bump so your master and branch builds
> >>>> does
> >>>> not collide when building locally.
> >>>>
> >>>> sorry for this, but I hope Michael/Nick soon can kick of the master
> >>>> builds so this will not be a problem. (and no,it does not require
> >>>> usage
> >>>> of an actual neon tp - we just need the stream urls built)
> >>>>
> >>>> /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
> >>
> >>
> >> /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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150925/0764045d/attachment-0001.html 

From manderse at redhat.com  Fri Sep 25 10:45:19 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 25 Sep 2015 10:45:19 -0400 (EDT)
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
	starts
In-Reply-To: <CA+QcL13H+p8eQhuCX-s-+8nz+6fnihdi3hTqSo8O4Y1B=w89Dw@mail.gmail.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
	<A52E11CD-7C50-4997-B390-A6A1E6BC7DC0@redhat.com>
	<CA+QcL10TYQfaC_mP-+dqeYbjc=zxWNnAknzLRTjq7wXgV1n10g@mail.gmail.com>
	<EFA3DE16-6A79-4735-A151-AE051EFAB0B7@redhat.com>
	<CA+QcL13H+p8eQhuCX-s-+8nz+6fnihdi3hTqSo8O4Y1B=w89Dw@mail.gmail.com>
Message-ID: <A41E974C-2E5A-424B-A537-D3222B62ED82@redhat.com>

You didn't tell anyone. 
And when I looked at the sources they were not on neon stream yet hence it did not make sense. 

As I have tried explain before and I think mistria stated very nicely yesterday:

Red balls for a known good reason is much better than green balls for an unknown bad reason. 

/max
http://about.me/maxandersen


> On 25 Sep 2015, at 14:13, Nick Boldt <nboldt at redhat.com> wrote:
> 
> No second guessing required. No first guessing either.
> 
> Fred reported to me he couldnt build Central because one or more /neon/snapshots/builds project folder was missing.
> 
> Fix: bootstrap those folders by moving content from /mars/snapshots/builds/jbosstools-*_master into equivalent /neon/ folder.
> 
> So... Where was the guesswork?
> 
>> On Sep 25, 2015 8:03 AM, "Max Rydahl Andersen" <manderse at redhat.com> wrote:
>> Great. Now it makes sense.
>> 
>> That explains why I could do builds that shouldn't be possible and confused he heck out of me.
>> 
>> In future I think it is much saner to point out which components haven't properly built and ask Dev to fix those rather than make it look like the neon stream of components actually are in a buildable state.
>> 
>> Please also share such moves to the team when they happen. Would spare a lot of time not having to second guess why builds failed/worked when expected they shouldn't.
>> 
>> /max
>> http://about.me/maxandersen
>> 
>> 
>> > On 24 Sep 2015, at 14:56, Nick Boldt <nboldt at redhat.com> wrote:
>> >
>> > What changed was that I moved all the _master build results folders
>> > under /mars/snapshots/ to /neon/snapshots/ so that all the URLs listed
>> > in the Alpha1 parent pom could be resolved and therefore all the
>> > interproject dependencies could be found.
>> >
>> > This was verified by Fred saying "my job is broken" then I did the
>> > move, and he confirmed "build completed ok".
>> >
>> >
>> >
>> > On Thu, Sep 24, 2015 at 2:20 AM, Max Rydahl Andersen
>> > <manderse at redhat.com> wrote:
>> >> On 24 Sep 2015, at 7:28, Max Rydahl Andersen wrote:
>> >>
>> >>> Looks like this are now fixed since I now see
>> >>> http://download.jboss.org/jbosstools/neon/snapshots/builds/ filled up.
>> >>>
>> >>> Nick/Michael - can you give an update on what changed ?
>> >>
>> >> Talked with Michael and seems what changed is just that jbosstools-base
>> >> were missing
>> >> version bump. Now that is done it trickles down to all builds as soon
>> >> as they get their version bumped.
>> >>
>> >> In past master builds were stopped since jenkins was overloaded, that
>> >> seem not to be
>> >> the case anymore so if we just do proper branching with a version bump
>> >> and stream name change both master and branch can be developed
>> >> concurrently without any accidental overlaps.
>> >>
>> >> /max
>> >>
>> >>>
>> >>> Have we restarted the master builds fully now using for now mars based
>> >>> TP, or was it just a single run to make builds
>> >>> work ?
>> >>>
>> >>> Thanks,
>> >>> /max
>> >>>
>> >>>> Hey,
>> >>>>
>> >>>> A few have noticed that when you build on master after updating
>> >>>> parent
>> >>>> pom you get build failures due to missing neon repos.
>> >>>>
>> >>>> This will unfortunately happen until neon streams start (note, this
>> >>>> does
>> >>>> not require any Neon TP to be present but jenkinsare busy doing CR1
>> >>>> builds so we'll have to wait).
>> >>>>
>> >>>> You can use the CR1 parent pom in the meantime - the minimal change
>> >>>> required is just the version bump so your master and branch builds
>> >>>> does
>> >>>> not collide when building locally.
>> >>>>
>> >>>> sorry for this, but I hope Michael/Nick soon can kick of the master
>> >>>> builds so this will not be a problem. (and no,it does not require
>> >>>> usage
>> >>>> of an actual neon tp - we just need the stream urls built)
>> >>>>
>> >>>> /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
>> >>
>> >>
>> >> /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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150925/b693a9c6/attachment.html 

From manderse at redhat.com  Fri Sep 25 10:48:36 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 25 Sep 2015 10:48:36 -0400 (EDT)
Subject: [jbosstools-dev] be aware 'master' is broken until neon-builds
	starts
In-Reply-To: <CA+QcL10ykco27Kv57+_97R=agL-MZ=Uc5w7aSje=sK83jyUsSg@mail.gmail.com>
References: <E843FDEE-23C3-49DE-86F6-01A8A6F784DD@redhat.com>
	<20AE60E0-45BD-4688-BC82-BC00FF1C1F40@redhat.com>
	<A52E11CD-7C50-4997-B390-A6A1E6BC7DC0@redhat.com>
	<CA+QcL10TYQfaC_mP-+dqeYbjc=zxWNnAknzLRTjq7wXgV1n10g@mail.gmail.com>
	<D4EC9A7A-4C15-4F5B-A7A0-7525FAF75F7C@redhat.com>
	<0D3E8095-7FCA-42FE-99EA-C9E7AAD82D4B@redhat.com>
	<CA+QcL10ykco27Kv57+_97R=agL-MZ=Uc5w7aSje=sK83jyUsSg@mail.gmail.com>
Message-ID: <C4BE6D4A-8ACA-4825-BB9E-C9C099A62380@redhat.com>



> On 25 Sep 2015, at 14:10, Nick Boldt <nboldt at redhat.com> wrote:
> 
> Had I not moved them you'd be getting red balls for all the projects with long dep chains simply because a project like Server had not migrated to Alpha1 parent and kicked a new build.
> 

Which is fully expected to happen. Hiding the issue is bad/unnecessary. 
> Why inconvenience everyone with false reds and the inability to build locally?
> 

They are not false reds. It's sounds more like we are producing false greens. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150925/0050a398/attachment.html 

From nboldt at redhat.com  Fri Sep 25 15:25:18 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 25 Sep 2015 15:25:18 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.3.0.CR2 (Final) bits available
	for QE testing
Message-ID: <CA+QcL11datup8h4aXLNhns_YegqGcmwLcAkvGWiMFe38frbO+w@mail.gmail.com>

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

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

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

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

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

--

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

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

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


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

From rstryker at redhat.com  Sun Sep 27 01:37:29 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Sun, 27 Sep 2015 01:37:29 -0400
Subject: [jbosstools-dev] Where's Rob? Not here, that's for sure.
Message-ID: <56078099.3060608@redhat.com>

Rob (that's me) is now on PTO. I will remain on PTO until October 12th. 
The upcoming 8 days will probably have minimal to no internet, as I run 
around off-grid doing things with people who also do things. I'll also 
be staring at and sitting on my new personal transport device 
<https://content.kawasaki.com/Content/Uploads/Products/6050/Colors/ohknwg24.eft.png> 
and trying to figure out how to use it.  If I don't return on the 12th, 
I probably used it incorrectly, and you should read through the New York 
obituaries (just in case) or police arrest records (also just in case).

I will likely regain some internet use on the 6th or 7th of October, and 
will then be (minimally) responsive for criticals or questions. Any 
critical issues, ping me on my gmail (rawblem at gmail.com) or skype 
(rawblem).

\m/  Rob *STRYKER*  \m/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150927/db0ae199/attachment.html 

From xcoulon at redhat.com  Mon Sep 28 10:35:54 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Mon, 28 Sep 2015 16:35:54 +0200
Subject: [jbosstools-dev] Where's Rob? Not here, that's for sure.
In-Reply-To: <56078099.3060608@redhat.com>
References: <56078099.3060608@redhat.com>
Message-ID: <A9670B6E-123B-4ADD-ABE7-169C3A63E950@redhat.com>


> On 27 Sep 2015, at 07:37, Rob Stryker <rstryker at redhat.com> wrote:
> 
> Rob (that's me) is now on PTO. I will remain on PTO until October 12th. The upcoming 8 days will probably have minimal to no internet, as I run around off-grid doing things with people who also do things. I'll also be staring at and sitting on my new personal transport device <https://content.kawasaki.com/Content/Uploads/Products/6050/Colors/ohknwg24.eft.png> and trying to figure out how to use it.  If I don't return on the 12th, I probably used it incorrectly, and you should read through the New York obituaries (just in case) or police arrest records (also just in case).   
> 

As far as mandatory RTFMs are concerned, may I suggest to start with Reading The F*g Manual before Riding That Freaking Motorcycle ?

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

From lheinema at redhat.com  Mon Sep 28 10:39:43 2015
From: lheinema at redhat.com (Lars Heinemann)
Date: Mon, 28 Sep 2015 16:39:43 +0200
Subject: [jbosstools-dev] Where's Rob? Not here, that's for sure.
In-Reply-To: <A9670B6E-123B-4ADD-ABE7-169C3A63E950@redhat.com>
References: <56078099.3060608@redhat.com>
	<A9670B6E-123B-4ADD-ABE7-169C3A63E950@redhat.com>
Message-ID: <1443451183.9710.1.camel@redhat.com>

Yeah, at least not without getting a proper driving license! 

Lars
-------- Weitergeleitete Nachricht --------
Von: Xavier Coulon <xcoulon at redhat.com>
An: Rob Stryker <rstryker at redhat.com>
Kopie: jbosstools-dev jbosstools-dev <jbosstools-dev at lists.jboss.org>
Betreff: Re: [jbosstools-dev] Where's Rob? Not here, that's for sure.
Datum: Mon, 28 Sep 2015 16:35:54 +0200
> On 27 Sep 2015, at 07:37, Rob Stryker <rstryker at redhat.com> wrote:
> 
> Rob (that's me) is now on PTO. I will remain on PTO until October
> 12th. The upcoming 8 days will probably have minimal to no internet,
> as I run around off-grid doing things with people who also do things.
> I'll also be staring at and sitting on my new persona transport
> device and trying to figure out how to use it.  If I don't return on
> the 12th, I probably used it incorrectly, and you should read through
> the New York obituaries (just in case) or police arrest records (also
> just in case).   
> 
As far as mandatory RTFMs are concerned, may I suggest to start with
Reading The F*g Manual before Riding That Freaking Motorcycle ?
_______________________________________________
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/20150928/43a489e4/attachment.html 

From manderse at redhat.com  Tue Sep 29 05:17:14 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 29 Sep 2015 11:17:14 +0200
Subject: [jbosstools-dev] Suggested change in Target-Platform
 4.60.0.Alpha1-SNAPSHOT: Neon M1
In-Reply-To: <CA+QcL13f2a_fua_pnuWtHZxO89Rw=bMSKSJJVQVw84nf_wj6jA@mail.gmail.com>
References: <56027D0A.9000003@redhat.com>
	<CA+QcL1072yZXBmdGYgVzPcgz8xnuvHiBZgEqAXZ_a6sgSNAb4g@mail.gmail.com>
	<5603B9E5.5090004@redhat.com>
	<CAJXFskYvcrVrtqhmdBw85CDgtVpB9zZd9hxuXkkoeaWGJkHsdg@mail.gmail.com>
	<CA+QcL13f2a_fua_pnuWtHZxO89Rw=bMSKSJJVQVw84nf_wj6jA@mail.gmail.com>
Message-ID: <7C4AF47A-FE37-485B-9B1B-BB75927C1AD5@redhat.com>

On 25 Sep 2015, at 14:08, Nick Boldt wrote:

> 1. You have a colon and @ in your /tmp path. Try again with a less
> unfriendly path?

is this not the build itself that does this ?

this is this funky workaround where instead of git cloning from 
jbdevstudio it
uses the disk since otherwise it needs to be authorised ?

> 2. Portlet is not currently being built at all. It has no new commits 
> since
> JBT 4.2.x.

yup, which is why we got 
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L107 
in parent pom (using luna build).

Denis - your overall build should not have to build portlet at the 
moment I would think ?

/max

> On Sep 24, 2015 10:52 PM, "Denis Golovin" <dgolovin at exadel.com> wrote:
>
>> All JBoss Tools projects can be built with latest TP, but I still 
>> have
>> couple glitches:
>> 1. jbds sources download fails 8 out of 10 builds
>> [INFO] [ERROR] Failed to execute goal
>> org.jboss.tools.tycho-plugins:repository-utils:0.23.1:fetch-sources-from-manifests
>> (fetch-sources) on project com.jboss.devstudio.core.site: Error 
>> cloning
>> from 
>> /home/eskimo/Projects/jbdevstudio/4.4.x/releng/jbdevstudio-product to
>> /tmp/git at github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip:
>> /tmp/git at github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip
>> (No such file or directory) -> [Help 1]
>>
>> 2. Portlet is not using parent pom 4.4.0.Alpha2-SNAPSHOT.
>> On 09/23/2015 10:37 PM, Nick Boldt wrote:
>>
>> Seems legit. Merge with impunity.
>>
>> Merged with impunity.
>>
>>
>> --
>> 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>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby 
>> notified
>> that using, copying, distributing or taking any action in reliance on 
>> the
>> contents of this information is strictly prohibited. If you have 
>> received
>> this email in error please notify the sender and delete this email.
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby 
>> notified
>> that using, copying, distributing or taking any action in reliance on 
>> the
>> contents of this information is strictly prohibited. If you have 
>> received
>> this email in error please notify the sender and delete this email.
>>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From dgolovin at exadel.com  Tue Sep 29 13:38:37 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Tue, 29 Sep 2015 10:38:37 -0700
Subject: [jbosstools-dev] Suggested change in Target-Platform
 4.60.0.Alpha1-SNAPSHOT: Neon M1
In-Reply-To: <7C4AF47A-FE37-485B-9B1B-BB75927C1AD5@redhat.com>
References: <56027D0A.9000003@redhat.com>
	<CA+QcL1072yZXBmdGYgVzPcgz8xnuvHiBZgEqAXZ_a6sgSNAb4g@mail.gmail.com>
	<5603B9E5.5090004@redhat.com>
	<CAJXFskYvcrVrtqhmdBw85CDgtVpB9zZd9hxuXkkoeaWGJkHsdg@mail.gmail.com>
	<CA+QcL13f2a_fua_pnuWtHZxO89Rw=bMSKSJJVQVw84nf_wj6jA@mail.gmail.com>
	<7C4AF47A-FE37-485B-9B1B-BB75927C1AD5@redhat.com>
Message-ID: <CAJXFskY62tA0Y_=DLB0C95tog4gYyAtqT8bweDw0QXn1bdYEbg@mail.gmail.com>

On Tue, Sep 29, 2015 at 2:17 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> On 25 Sep 2015, at 14:08, Nick Boldt wrote:
>
> 1. You have a colon and @ in your /tmp path. Try again with a less
>> unfriendly path?
>>
>
> is this not the build itself that does this ?
>
> this is this funky workaround where instead of git cloning from
> jbdevstudio it
> uses the disk since otherwise it needs to be authorised ?


I have no answers for any of yo questions, because I didn't look inside the
code.

For me this downloading it another build overhead, because we already have
sources in resulting repository for JBDS and I would rather find the way to
use them instead of downloading them again.


>
>
> 2. Portlet is not currently being built at all. It has no new commits since
>> JBT 4.2.x.
>>
>
> yup, which is why we got
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L107
> in parent pom (using luna build).
>
> Denis - your overall build should not have to build portlet at the moment
> I would think ?
>

I know we have it in parent.pom, but still it is not confirmed that it
compiles with eclipse neon and with every TP update to include latest
Eclipse M build there is a chance the portlet build fails, but we would not
know, because we don't even build it.

Denis


> /max
>
> On Sep 24, 2015 10:52 PM, "Denis Golovin" <dgolovin at exadel.com> wrote:
>>
>> All JBoss Tools projects can be built with latest TP, but I still have
>>> couple glitches:
>>> 1. jbds sources download fails 8 out of 10 builds
>>> [INFO] [ERROR] Failed to execute goal
>>>
>>> org.jboss.tools.tycho-plugins:repository-utils:0.23.1:fetch-sources-from-manifests
>>> (fetch-sources) on project com.jboss.devstudio.core.site: Error cloning
>>> from /home/eskimo/Projects/jbdevstudio/4.4.x/releng/jbdevstudio-product
>>> to
>>> /tmp/git at github.com
>>> :dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip:
>>> /tmp/git at github.com
>>> :dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip
>>> (No such file or directory) -> [Help 1]
>>>
>>> 2. Portlet is not using parent pom 4.4.0.Alpha2-SNAPSHOT.
>>> On 09/23/2015 10:37 PM, Nick Boldt wrote:
>>>
>>> Seems legit. Merge with impunity.
>>>
>>> Merged with impunity.
>>>
>>>
>>> --
>>> 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>
>>>
>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>> confidential. If you are not the intended recipient you are hereby
>>> notified
>>> that using, copying, distributing or taking any action in reliance on the
>>> contents of this information is strictly prohibited. If you have received
>>> this email in error please notify the sender and delete this email.
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>> confidential. If you are not the intended recipient you are hereby
>>> notified
>>> that using, copying, distributing or taking any action in reliance on the
>>> contents of this information is strictly prohibited. If you have received
>>> this email in error please notify the sender and delete this email.
>>>
>>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
> /max
> http://about.me/maxandersen
>
> --
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>

-- 


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

From nboldt at redhat.com  Tue Sep 29 14:13:55 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 29 Sep 2015 14:13:55 -0400
Subject: [jbosstools-dev] Suggested change in Target-Platform
 4.60.0.Alpha1-SNAPSHOT: Neon M1
In-Reply-To: <CAJXFskY62tA0Y_=DLB0C95tog4gYyAtqT8bweDw0QXn1bdYEbg@mail.gmail.com>
References: <56027D0A.9000003@redhat.com>
	<CA+QcL1072yZXBmdGYgVzPcgz8xnuvHiBZgEqAXZ_a6sgSNAb4g@mail.gmail.com>
	<5603B9E5.5090004@redhat.com>
	<CAJXFskYvcrVrtqhmdBw85CDgtVpB9zZd9hxuXkkoeaWGJkHsdg@mail.gmail.com>
	<CA+QcL13f2a_fua_pnuWtHZxO89Rw=bMSKSJJVQVw84nf_wj6jA@mail.gmail.com>
	<7C4AF47A-FE37-485B-9B1B-BB75927C1AD5@redhat.com>
	<CAJXFskY62tA0Y_=DLB0C95tog4gYyAtqT8bweDw0QXn1bdYEbg@mail.gmail.com>
Message-ID: <CA+QcL11rNo-i4xSQhP3oAgWOyLJJbsaAN3apo9Zz12HarocTbw@mail.gmail.com>

OK, so the bug here is that I'm reusing something of the github path
to create a temp folder / file to house the downloaded sources from
github. I'll need to ensure that colons and ats are replaced with
something that's more path-friendly.

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

Regarding Portlet, if you want to update its root pom, bump its
versions, commit your changes, and rebuild it in the
jbosstools-portlet_master job, feel free. I'm not convinced we need to
INCLUDE those new built versions however, but your test might show
there's a problem which DOES require us to rebuild to be
Neon-compatible.

I'll let you open a JIRA for that task.


On Tue, Sep 29, 2015 at 1:38 PM, Denis Golovin <dgolovin at exadel.com> wrote:
>
>
> On Tue, Sep 29, 2015 at 2:17 AM, Max Rydahl Andersen <manderse at redhat.com>
> wrote:
>>
>> On 25 Sep 2015, at 14:08, Nick Boldt wrote:
>>
>>> 1. You have a colon and @ in your /tmp path. Try again with a less
>>> unfriendly path?
>>
>>
>> is this not the build itself that does this ?
>>
>> this is this funky workaround where instead of git cloning from
>> jbdevstudio it
>> uses the disk since otherwise it needs to be authorised ?
>
>
> I have no answers for any of yo questions, because I didn't look inside the
> code.
>
> For me this downloading it another build overhead, because we already have
> sources in resulting repository for JBDS and I would rather find the way to
> use them instead of downloading them again.
>
>>
>>
>>
>>> 2. Portlet is not currently being built at all. It has no new commits
>>> since
>>> JBT 4.2.x.
>>
>>
>> yup, which is why we got
>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L107
>> in parent pom (using luna build).
>>
>> Denis - your overall build should not have to build portlet at the moment
>> I would think ?
>
>
> I know we have it in parent.pom, but still it is not confirmed that it
> compiles with eclipse neon and with every TP update to include latest
> Eclipse M build there is a chance the portlet build fails, but we would not
> know, because we don't even build it.
>
> Denis
>
>>
>> /max
>>
>>> On Sep 24, 2015 10:52 PM, "Denis Golovin" <dgolovin at exadel.com> wrote:
>>>
>>>> All JBoss Tools projects can be built with latest TP, but I still have
>>>> couple glitches:
>>>> 1. jbds sources download fails 8 out of 10 builds
>>>> [INFO] [ERROR] Failed to execute goal
>>>>
>>>> org.jboss.tools.tycho-plugins:repository-utils:0.23.1:fetch-sources-from-manifests
>>>> (fetch-sources) on project com.jboss.devstudio.core.site: Error cloning
>>>> from /home/eskimo/Projects/jbdevstudio/4.4.x/releng/jbdevstudio-product
>>>> to
>>>>
>>>> /tmp/git at github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip:
>>>>
>>>> /tmp/git at github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip
>>>> (No such file or directory) -> [Help 1]
>>>>
>>>> 2. Portlet is not using parent pom 4.4.0.Alpha2-SNAPSHOT.
>>>> On 09/23/2015 10:37 PM, Nick Boldt wrote:
>>>>
>>>> Seems legit. Merge with impunity.
>>>>
>>>> Merged with impunity.
>>>>
>>>>
>>>> --
>>>> 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>
>>>>
>>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>>> confidential. If you are not the intended recipient you are hereby
>>>> notified
>>>> that using, copying, distributing or taking any action in reliance on
>>>> the
>>>> contents of this information is strictly prohibited. If you have
>>>> received
>>>> this email in error please notify the sender and delete this email.
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>>> confidential. If you are not the intended recipient you are hereby
>>>> notified
>>>> that using, copying, distributing or taking any action in reliance on
>>>> the
>>>> contents of this information is strictly prohibited. If you have
>>>> received
>>>> this email in error please notify the sender and delete this email.
>>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>> --
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.



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

From nboldt at redhat.com  Tue Sep 29 14:21:41 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 29 Sep 2015 14:21:41 -0400
Subject: [jbosstools-dev] Coming soon to a Tycho build near you: pomless
	builds!
Message-ID: <CA+QcL103JiEO-8mmWjbo+6Mn_R-D2XVGM+bFPJ0kYz8g8N0xzQ@mail.gmail.com>

... well, NEARLY pomless. Still need a root pom or parent pom.

And might need to refactor your test plugins to end with ".tests" in
their Bundle-SymbolicName (in MANIFEST.MF).

But hey, less crufty metadata!

Details:

http://wiki.eclipse.org/Tycho/Release_Notes/0.24

Sample project:

http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/tree/tycho-extras-its/src/test/resources/testpomless



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

From dgolovin at gmail.com  Tue Sep 29 23:07:59 2015
From: dgolovin at gmail.com (Denis Golovin)
Date: Tue, 29 Sep 2015 20:07:59 -0700
Subject: [jbosstools-dev] Coming soon to a Tycho build near you: pomless
	builds!
In-Reply-To: <CA+QcL103JiEO-8mmWjbo+6Mn_R-D2XVGM+bFPJ0kYz8g8N0xzQ@mail.gmail.com>
References: <CA+QcL103JiEO-8mmWjbo+6Mn_R-D2XVGM+bFPJ0kYz8g8N0xzQ@mail.gmail.com>
Message-ID: <CAJXFskYvMKBtd5Fc32Rn3ApYfxVSJTtd70bRurd0nd+7OPbW2Q@mail.gmail.com>

Since it requires maven 3.3.x there are some new maven features that might
be helpful. See release notes for 3.3.1 here
http://blog.soebes.de/blog/2015/03/17/apache-maven-3-dot-3-1-features
On Sep 29, 2015 11:23 AM, "Nick Boldt" <nboldt at redhat.com> wrote:

> ... well, NEARLY pomless. Still need a root pom or parent pom.
>
> And might need to refactor your test plugins to end with ".tests" in
> their Bundle-SymbolicName (in MANIFEST.MF).
>
> But hey, less crufty metadata!
>
> Details:
>
> http://wiki.eclipse.org/Tycho/Release_Notes/0.24
>
> Sample project:
>
>
> http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/tree/tycho-extras-its/src/test/resources/testpomless
>
>
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> --
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150929/293cf6be/attachment.html 

From manderse at redhat.com  Wed Sep 30 03:52:04 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 30 Sep 2015 09:52:04 +0200
Subject: [jbosstools-dev] Coming soon to a Tycho build near you: pomless
 builds!
In-Reply-To: <CA+QcL103JiEO-8mmWjbo+6Mn_R-D2XVGM+bFPJ0kYz8g8N0xzQ@mail.gmail.com>
References: <CA+QcL103JiEO-8mmWjbo+6Mn_R-D2XVGM+bFPJ0kYz8g8N0xzQ@mail.gmail.com>
Message-ID: <23C066BE-8C6C-452A-9E52-48ED2C953BF3@redhat.com>

On 29 Sep 2015, at 20:21, Nick Boldt wrote:

> ... well, NEARLY pomless. Still need a root pom or parent pom.
>
> And might need to refactor your test plugins to end with ".tests" in
> their Bundle-SymbolicName (in MANIFEST.MF).
>
> But hey, less crufty metadata!
>
> Details:
>
> http://wiki.eclipse.org/Tycho/Release_Notes/0.24
>
> Sample project:
>
> http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/tree/tycho-extras-its/src/test/resources/testpomless

Anyone tried if this work without issues in m2e yet ?

How about the mvn plugin for bumping of versions ? Does it change the 
manifest.mf when no pom.xml present ?

If that works then a loose count [1] indicates we can delete about 433 
files.


[1] `grep -Rl --include "pom.xml" "packaging>eclipse" jbosstools-* | 
xargs -n 1 grep -lL "module" | xargs -n 1 grep -lL "build" | xargs -n 1 
grep -1L "dependency"`

The above simply try locate all pom.xml, that has custom eclipse 
packaging enabled, don't have module listed and do not have custom build 
or dependency instructions.

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


/max
http://about.me/maxandersen


From dgolovin at exadel.com  Wed Sep 30 15:11:00 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Wed, 30 Sep 2015 12:11:00 -0700
Subject: [jbosstools-dev] Suggested change in Target-Platform
 4.60.0.Alpha1-SNAPSHOT: Neon M1
In-Reply-To: <CA+QcL11rNo-i4xSQhP3oAgWOyLJJbsaAN3apo9Zz12HarocTbw@mail.gmail.com>
References: <56027D0A.9000003@redhat.com>
	<CA+QcL1072yZXBmdGYgVzPcgz8xnuvHiBZgEqAXZ_a6sgSNAb4g@mail.gmail.com>
	<5603B9E5.5090004@redhat.com>
	<CAJXFskYvcrVrtqhmdBw85CDgtVpB9zZd9hxuXkkoeaWGJkHsdg@mail.gmail.com>
	<CA+QcL13f2a_fua_pnuWtHZxO89Rw=bMSKSJJVQVw84nf_wj6jA@mail.gmail.com>
	<7C4AF47A-FE37-485B-9B1B-BB75927C1AD5@redhat.com>
	<CAJXFskY62tA0Y_=DLB0C95tog4gYyAtqT8bweDw0QXn1bdYEbg@mail.gmail.com>
	<CA+QcL11rNo-i4xSQhP3oAgWOyLJJbsaAN3apo9Zz12HarocTbw@mail.gmail.com>
Message-ID: <CAJXFskbYvnqcWGOxZqcPy3-=36Z8Dj1JS4Xs5umbJ-6D3Cue9w@mail.gmail.com>

On Tue, Sep 29, 2015 at 11:13 AM, Nick Boldt <nboldt at redhat.com> wrote:

> OK, so the bug here is that I'm reusing something of the github path
> to create a temp folder / file to house the downloaded sources from
> github. I'll need to ensure that colons and ats are replaced with
> something that's more path-friendly.
>
> https://issues.jboss.org/browse/JBIDE-20839


replacing chars that is not allowed in file names to "_" should work.


> <https://issues.jboss.org/browse/JBIDE-20839>Regarding Portlet, if you
> want to update its root pom, bump its
> versions, commit your changes, and rebuild it in the
> jbosstools-portlet_master job, feel free. I'm not convinced we need to
> INCLUDE those new built versions however, but your test might show
> there's a problem which DOES require us to rebuild to be
> Neon-compatible.
>

That was the idea, but now I realized I have to bump versions to avoid
failures with backward version update checks in place.
Anyway I think it is worth to do to discover neon compatibility problems
early.


>
> I'll let you open a JIRA for that task.
>
>
> On Tue, Sep 29, 2015 at 1:38 PM, Denis Golovin <dgolovin at exadel.com>
> wrote:
> >
> >
> > On Tue, Sep 29, 2015 at 2:17 AM, Max Rydahl Andersen <
> manderse at redhat.com>
> > wrote:
> >>
> >> On 25 Sep 2015, at 14:08, Nick Boldt wrote:
> >>
> >>> 1. You have a colon and @ in your /tmp path. Try again with a less
> >>> unfriendly path?
> >>
> >>
> >> is this not the build itself that does this ?
> >>
> >> this is this funky workaround where instead of git cloning from
> >> jbdevstudio it
> >> uses the disk since otherwise it needs to be authorised ?
> >
> >
> > I have no answers for any of yo questions, because I didn't look inside
> the
> > code.
> >
> > For me this downloading it another build overhead, because we already
> have
> > sources in resulting repository for JBDS and I would rather find the way
> to
> > use them instead of downloading them again.
> >
> >>
> >>
> >>
> >>> 2. Portlet is not currently being built at all. It has no new commits
> >>> since
> >>> JBT 4.2.x.
> >>
> >>
> >> yup, which is why we got
> >>
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L107
> >> in parent pom (using luna build).
> >>
> >> Denis - your overall build should not have to build portlet at the
> moment
> >> I would think ?
> >
> >
> > I know we have it in parent.pom, but still it is not confirmed that it
> > compiles with eclipse neon and with every TP update to include latest
> > Eclipse M build there is a chance the portlet build fails, but we would
> not
> > know, because we don't even build it.
> >
> > Denis
> >
> >>
> >> /max
> >>
> >>> On Sep 24, 2015 10:52 PM, "Denis Golovin" <dgolovin at exadel.com> wrote:
> >>>
> >>>> All JBoss Tools projects can be built with latest TP, but I still have
> >>>> couple glitches:
> >>>> 1. jbds sources download fails 8 out of 10 builds
> >>>> [INFO] [ERROR] Failed to execute goal
> >>>>
> >>>>
> org.jboss.tools.tycho-plugins:repository-utils:0.23.1:fetch-sources-from-manifests
> >>>> (fetch-sources) on project com.jboss.devstudio.core.site: Error
> cloning
> >>>> from
> /home/eskimo/Projects/jbdevstudio/4.4.x/releng/jbdevstudio-product
> >>>> to
> >>>>
> >>>> /tmp/git at github.com
> :dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip:
> >>>>
> >>>> /tmp/git at github.com
> :dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip
> >>>> (No such file or directory) -> [Help 1]
> >>>>
> >>>> 2. Portlet is not using parent pom 4.4.0.Alpha2-SNAPSHOT.
> >>>> On 09/23/2015 10:37 PM, Nick Boldt wrote:
> >>>>
> >>>> Seems legit. Merge with impunity.
> >>>>
> >>>> Merged with impunity.
> >>>>
> >>>>
> >>>> --
> >>>> 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>
> >>>>
> >>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
> >>>> confidential. If you are not the intended recipient you are hereby
> >>>> notified
> >>>> that using, copying, distributing or taking any action in reliance on
> >>>> the
> >>>> contents of this information is strictly prohibited. If you have
> >>>> received
> >>>> this email in error please notify the sender and delete this email.
> >>>>
> >>>> _______________________________________________
> >>>> jbosstools-dev mailing list
> >>>> jbosstools-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >>>>
> >>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
> >>>> confidential. If you are not the intended recipient you are hereby
> >>>> notified
> >>>> that using, copying, distributing or taking any action in reliance on
> >>>> the
> >>>> contents of this information is strictly prohibited. If you have
> >>>> received
> >>>> this email in error please notify the sender and delete this email.
> >>>>
> >>> _______________________________________________
> >>> jbosstools-dev mailing list
> >>> jbosstools-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >>
> >>
> >>
> >> /max
> >> http://about.me/maxandersen
> >>
> >>
> >> --
> >>
> >>
> >> CONFIDENTIALITY NOTICE: This email and files attached to it are
> >> confidential. If you are not the intended recipient you are hereby
> notified
> >> that using, copying, distributing or taking any action in reliance on
> the
> >> contents of this information is strictly prohibited. If you have
> received
> >> this email in error please notify the sender and delete this email.
> >
> >
> >
> > CONFIDENTIALITY NOTICE: This email and files attached to it are
> > confidential. If you are not the intended recipient you are hereby
> notified
> > that using, copying, distributing or taking any action in reliance on the
> > contents of this information is strictly prohibited. If you have received
> > this email in error please notify the sender and delete this email.
>
>
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
>
> --
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>

-- 


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

From dgolovin at exadel.com  Wed Sep 30 18:34:47 2015
From: dgolovin at exadel.com (Denis Golovin)
Date: Wed, 30 Sep 2015 15:34:47 -0700
Subject: [jbosstools-dev] Suggested change in Target-Platform
 4.60.0.Alpha1-SNAPSHOT: Neon M1
In-Reply-To: <CAJXFskbYvnqcWGOxZqcPy3-=36Z8Dj1JS4Xs5umbJ-6D3Cue9w@mail.gmail.com>
References: <56027D0A.9000003@redhat.com>
	<CA+QcL1072yZXBmdGYgVzPcgz8xnuvHiBZgEqAXZ_a6sgSNAb4g@mail.gmail.com>
	<5603B9E5.5090004@redhat.com>
	<CAJXFskYvcrVrtqhmdBw85CDgtVpB9zZd9hxuXkkoeaWGJkHsdg@mail.gmail.com>
	<CA+QcL13f2a_fua_pnuWtHZxO89Rw=bMSKSJJVQVw84nf_wj6jA@mail.gmail.com>
	<7C4AF47A-FE37-485B-9B1B-BB75927C1AD5@redhat.com>
	<CAJXFskY62tA0Y_=DLB0C95tog4gYyAtqT8bweDw0QXn1bdYEbg@mail.gmail.com>
	<CA+QcL11rNo-i4xSQhP3oAgWOyLJJbsaAN3apo9Zz12HarocTbw@mail.gmail.com>
	<CAJXFskbYvnqcWGOxZqcPy3-=36Z8Dj1JS4Xs5umbJ-6D3Cue9w@mail.gmail.com>
Message-ID: <CAJXFskaNHpOFq+oPinRPW55=Qf7hUpB8NK7PUVCG4aMpi1birw@mail.gmail.com>

I have updated portlet parent/pom.xml reference and bumped the version
 from 1.6.100-SNAPSHOT to 1.6.200-SNAPSHOT.

On Wed, Sep 30, 2015 at 12:11 PM, Denis Golovin <dgolovin at exadel.com> wrote:

> On Tue, Sep 29, 2015 at 11:13 AM, Nick Boldt <nboldt at redhat.com> wrote:
>
>> OK, so the bug here is that I'm reusing something of the github path
>> to create a temp folder / file to house the downloaded sources from
>> github. I'll need to ensure that colons and ats are replaced with
>> something that's more path-friendly.
>>
>> https://issues.jboss.org/browse/JBIDE-20839
>
>
> replacing chars that is not allowed in file names to "_" should work.
>
>
>> <https://issues.jboss.org/browse/JBIDE-20839>Regarding Portlet, if you
>> want to update its root pom, bump its
>> versions, commit your changes, and rebuild it in the
>> jbosstools-portlet_master job, feel free. I'm not convinced we need to
>> INCLUDE those new built versions however, but your test might show
>> there's a problem which DOES require us to rebuild to be
>> Neon-compatible.
>>
>
> That was the idea, but now I realized I have to bump versions to avoid
> failures with backward version update checks in place.
> Anyway I think it is worth to do to discover neon compatibility problems
> early.
>
>
>>
>> I'll let you open a JIRA for that task.
>>
>>
>> On Tue, Sep 29, 2015 at 1:38 PM, Denis Golovin <dgolovin at exadel.com>
>> wrote:
>> >
>> >
>> > On Tue, Sep 29, 2015 at 2:17 AM, Max Rydahl Andersen <
>> manderse at redhat.com>
>> > wrote:
>> >>
>> >> On 25 Sep 2015, at 14:08, Nick Boldt wrote:
>> >>
>> >>> 1. You have a colon and @ in your /tmp path. Try again with a less
>> >>> unfriendly path?
>> >>
>> >>
>> >> is this not the build itself that does this ?
>> >>
>> >> this is this funky workaround where instead of git cloning from
>> >> jbdevstudio it
>> >> uses the disk since otherwise it needs to be authorised ?
>> >
>> >
>> > I have no answers for any of yo questions, because I didn't look inside
>> the
>> > code.
>> >
>> > For me this downloading it another build overhead, because we already
>> have
>> > sources in resulting repository for JBDS and I would rather find the
>> way to
>> > use them instead of downloading them again.
>> >
>> >>
>> >>
>> >>
>> >>> 2. Portlet is not currently being built at all. It has no new commits
>> >>> since
>> >>> JBT 4.2.x.
>> >>
>> >>
>> >> yup, which is why we got
>> >>
>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L107
>> >> in parent pom (using luna build).
>> >>
>> >> Denis - your overall build should not have to build portlet at the
>> moment
>> >> I would think ?
>> >
>> >
>> > I know we have it in parent.pom, but still it is not confirmed that it
>> > compiles with eclipse neon and with every TP update to include latest
>> > Eclipse M build there is a chance the portlet build fails, but we would
>> not
>> > know, because we don't even build it.
>> >
>> > Denis
>> >
>> >>
>> >> /max
>> >>
>> >>> On Sep 24, 2015 10:52 PM, "Denis Golovin" <dgolovin at exadel.com>
>> wrote:
>> >>>
>> >>>> All JBoss Tools projects can be built with latest TP, but I still
>> have
>> >>>> couple glitches:
>> >>>> 1. jbds sources download fails 8 out of 10 builds
>> >>>> [INFO] [ERROR] Failed to execute goal
>> >>>>
>> >>>>
>> org.jboss.tools.tycho-plugins:repository-utils:0.23.1:fetch-sources-from-manifests
>> >>>> (fetch-sources) on project com.jboss.devstudio.core.site: Error
>> cloning
>> >>>> from
>> /home/eskimo/Projects/jbdevstudio/4.4.x/releng/jbdevstudio-product
>> >>>> to
>> >>>>
>> >>>> /tmp/git at github.com
>> :dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip:
>> >>>>
>> >>>> /tmp/git at github.com
>> :dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip
>> >>>> (No such file or directory) -> [Help 1]
>> >>>>
>> >>>> 2. Portlet is not using parent pom 4.4.0.Alpha2-SNAPSHOT.
>> >>>> On 09/23/2015 10:37 PM, Nick Boldt wrote:
>> >>>>
>> >>>> Seems legit. Merge with impunity.
>> >>>>
>> >>>> Merged with impunity.
>> >>>>
>> >>>>
>> >>>> --
>> >>>> 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>
>> >>>>
>> >>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> >>>> confidential. If you are not the intended recipient you are hereby
>> >>>> notified
>> >>>> that using, copying, distributing or taking any action in reliance on
>> >>>> the
>> >>>> contents of this information is strictly prohibited. If you have
>> >>>> received
>> >>>> this email in error please notify the sender and delete this email.
>> >>>>
>> >>>> _______________________________________________
>> >>>> jbosstools-dev mailing list
>> >>>> jbosstools-dev at lists.jboss.org
>> >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> >>>>
>> >>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> >>>> confidential. If you are not the intended recipient you are hereby
>> >>>> notified
>> >>>> that using, copying, distributing or taking any action in reliance on
>> >>>> the
>> >>>> contents of this information is strictly prohibited. If you have
>> >>>> received
>> >>>> this email in error please notify the sender and delete this email.
>> >>>>
>> >>> _______________________________________________
>> >>> jbosstools-dev mailing list
>> >>> jbosstools-dev at lists.jboss.org
>> >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> >>
>> >>
>> >>
>> >> /max
>> >> http://about.me/maxandersen
>> >>
>> >>
>> >> --
>> >>
>> >>
>> >> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> >> confidential. If you are not the intended recipient you are hereby
>> notified
>> >> that using, copying, distributing or taking any action in reliance on
>> the
>> >> contents of this information is strictly prohibited. If you have
>> received
>> >> this email in error please notify the sender and delete this email.
>> >
>> >
>> >
>> > CONFIDENTIALITY NOTICE: This email and files attached to it are
>> > confidential. If you are not the intended recipient you are hereby
>> notified
>> > that using, copying, distributing or taking any action in reliance on
>> the
>> > contents of this information is strictly prohibited. If you have
>> received
>> > this email in error please notify the sender and delete this email.
>>
>>
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>>
>> --
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby
>> notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>>
>
>

-- 


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