From manderse at redhat.com Mon Dec 1 02:59:04 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Mon, 1 Dec 2014 02:59:04 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201412010759.sB17x4V3000466@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-18851 https://issues.jboss.org/browse/JBIDE-18851 Summary: WATCH!>> Bosch Episode 2 Online Full Show LIVE STream. Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 19:22:25.846970 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From scabanovich at exadel.com Mon Dec 1 13:21:21 2014 From: scabanovich at exadel.com (Viacheslav Kabanovich) Date: Mon, 01 Dec 2014 10:21:21 -0800 Subject: [jbosstools-dev] Batch Job Configuration editor In-Reply-To: References: <5476E615.4000201@redhat.com> <5D18E490-FB30-4983-AFD4-FC56BAB33641@redhat.com> <63956478-E506-48AB-8E04-5004A8A74EC4@redhat.com> Message-ID: <547CB1A1.8060805@exadel.com> Hello, Max I suggest naming new plugin org.jboss.tools.javaee.batch.ui. Where in javaee component should I place it? Create new sub-component 'batch' along with existing 'cdi', 'jsf', 'seam'? Slava Kabanovich From dgolovin at exadel.com Mon Dec 1 13:33:45 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Mon, 01 Dec 2014 10:33:45 -0800 Subject: [jbosstools-dev] Batch Job Configuration editor In-Reply-To: <547CB1A1.8060805@exadel.com> References: <5476E615.4000201@redhat.com> <5D18E490-FB30-4983-AFD4-FC56BAB33641@redhat.com> <63956478-E506-48AB-8E04-5004A8A74EC4@redhat.com> <547CB1A1.8060805@exadel.com> Message-ID: <547CB489.4080108@exadel.com> It is better to match module or submodule name in namespace. I would name it org.jboss.tools.batch.ui and put it under jbosstools-javaee/batch/plugins to comply with current name pattern. Denis On 12/01/2014 10:21 AM, Viacheslav Kabanovich wrote: > Hello, Max > > I suggest naming new plugin org.jboss.tools.javaee.batch.ui. > Where in javaee component should I place it? > Create new sub-component 'batch' along with existing 'cdi', 'jsf', 'seam'? > > Slava Kabanovich > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From manderse at redhat.com Mon Dec 1 15:18:39 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 01 Dec 2014 21:18:39 +0100 Subject: [jbosstools-dev] Batch Job Configuration editor In-Reply-To: <547CB489.4080108@exadel.com> References: <5476E615.4000201@redhat.com> <5D18E490-FB30-4983-AFD4-FC56BAB33641@redhat.com> <63956478-E506-48AB-8E04-5004A8A74EC4@redhat.com> <547CB1A1.8060805@exadel.com> <547CB489.4080108@exadel.com> Message-ID: <579BB5F0-DC85-430D-968D-1083A6558BD0@redhat.com> On 1 Dec 2014, at 19:33, Denis Golovin wrote: > It is better to match module or submodule name in namespace. I would > name it org.jboss.tools.batch.ui and put it under > jbosstools-javaee/batch/plugins to comply with current name pattern. +1 for batch with org.jboss.tools.batch.* and also separate feature. /max > > Denis > > On 12/01/2014 10:21 AM, Viacheslav Kabanovich wrote: >> Hello, Max >> >> I suggest naming new plugin org.jboss.tools.javaee.batch.ui. >> Where in javaee component should I place it? >> Create new sub-component 'batch' along with existing 'cdi', 'jsf', >> 'seam'? >> >> Slava Kabanovich >> _______________________________________________ >> 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 Mon Dec 1 15:53:58 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Mon, 01 Dec 2014 12:53:58 -0800 Subject: [jbosstools-dev] Batch Job Configuration editor In-Reply-To: <579BB5F0-DC85-430D-968D-1083A6558BD0@redhat.com> References: <5476E615.4000201@redhat.com> <5D18E490-FB30-4983-AFD4-FC56BAB33641@redhat.com> <63956478-E506-48AB-8E04-5004A8A74EC4@redhat.com> <547CB1A1.8060805@exadel.com> <547CB489.4080108@exadel.com> <579BB5F0-DC85-430D-968D-1083A6558BD0@redhat.com> Message-ID: <547CD566.6020004@exadel.com> First PR must co contain full structure for submodule with features, tests and would be good to have itests as well with swt bot tests. Slava, Alexey, if you have questions about how to add swt bot tests ask me or look at jbosstools-integration-tests. Denis On 12/01/2014 12:18 PM, Max Rydahl Andersen wrote: > On 1 Dec 2014, at 19:33, Denis Golovin wrote: > >> It is better to match module or submodule name in namespace. I would >> name it org.jboss.tools.batch.ui and put it under >> jbosstools-javaee/batch/plugins to comply with current name pattern. > > +1 for batch with org.jboss.tools.batch.* and also separate feature. > > /max > >> >> Denis >> >> On 12/01/2014 10:21 AM, Viacheslav Kabanovich wrote: >>> Hello, Max >>> >>> I suggest naming new plugin org.jboss.tools.javaee.batch.ui. >>> Where in javaee component should I place it? >>> Create new sub-component 'batch' along with existing 'cdi', 'jsf', >>> 'seam'? >>> >>> Slava Kabanovich >>> _______________________________________________ >>> 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 Mon Dec 1 18:31:58 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Mon, 01 Dec 2014 15:31:58 -0800 Subject: [jbosstools-dev] Batch Job Configuration editor In-Reply-To: <547CD566.6020004@exadel.com> References: <5476E615.4000201@redhat.com> <5D18E490-FB30-4983-AFD4-FC56BAB33641@redhat.com> <63956478-E506-48AB-8E04-5004A8A74EC4@redhat.com> <547CB1A1.8060805@exadel.com> <547CB489.4080108@exadel.com> <579BB5F0-DC85-430D-968D-1083A6558BD0@redhat.com> <547CD566.6020004@exadel.com> Message-ID: <547CFA6E.6090109@exadel.com> Slava, if you have a topic branch for this in your fork, share it with us please, so we can help with module structure and anything related to JBDS-3160. Denis if you have a branch share it with u On 12/01/2014 12:53 PM, Denis Golovin wrote: > First PR must co contain full structure for submodule with features, > tests and would be good to have itests as well with swt bot tests. > > Slava, Alexey, if you have questions about how to add swt bot tests ask > me or look at jbosstools-integration-tests. > > Denis > > On 12/01/2014 12:18 PM, Max Rydahl Andersen wrote: >> On 1 Dec 2014, at 19:33, Denis Golovin wrote: >> >>> It is better to match module or submodule name in namespace. I would >>> name it org.jboss.tools.batch.ui and put it under >>> jbosstools-javaee/batch/plugins to comply with current name pattern. >> +1 for batch with org.jboss.tools.batch.* and also separate feature. >> >> /max >> >>> Denis >>> >>> On 12/01/2014 10:21 AM, Viacheslav Kabanovich wrote: >>>> Hello, Max >>>> >>>> I suggest naming new plugin org.jboss.tools.javaee.batch.ui. >>>> Where in javaee component should I place it? >>>> Create new sub-component 'batch' along with existing 'cdi', 'jsf', >>>> 'seam'? >>>> >>>> Slava Kabanovich >>>> _______________________________________________ >>>> 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/20141201/f68965ce/attachment.html From akazakov at exadel.com Tue Dec 2 17:48:19 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Tue, 02 Dec 2014 14:48:19 -0800 Subject: [jbosstools-dev] Updating Tern.java & AngularJS Eclipse IDE? Message-ID: <547E41B3.7070803@exadel.com> Hi, Today on Mobile/HTML5 team meeting we discussed possible updating Tern.java and AngularJS Eclipse IDE in Target Platform and central for JBT 4.2.1 Victor spent a few days testing the latest "stable" Terns/Angular builds 0.7.0 (we are using 0.6.0 right now). He didn't find any new issues there. So the new builds look OK to him. However, we decided not to update Tern/Angular for JBT 4.2.1 because: 1. We don't have (well, we are not aware of ;) any critical issue in current JBT/Tern/Angular which requires such update. 2. We would have only one week or so for testing JBT 4.2.1.CR1(respin-a) and we believe that Tern/Angular is still not stable enough to make sure we won't get any critical/blocker issue with new builds. 3. We also would have to update Angular in EA Central (not only Tern in TP) for JBT and JBDS which increases risks just ~ 10 days before the final JBT/JBDS release. We had such issues before when updated Tern/Angular for JBT 4.2.0. So let's do not update Tern/Angular in 4.2.1 but do it for 4.2.2 and 4.3. Max, anybody, any objections? From manderse at redhat.com Wed Dec 3 02:52:00 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 3 Dec 2014 02:52:00 -0500 (EST) Subject: [jbosstools-dev] Updating Tern.java & AngularJS Eclipse IDE? In-Reply-To: <547E41B3.7070803@exadel.com> References: <547E41B3.7070803@exadel.com> Message-ID: Sounds reasonable. +1. /max http://about.me/maxandersen > On 02 Dec 2014, at 23:48, Alexey Kazakov wrote: > > Hi, > > Today on Mobile/HTML5 team meeting we discussed possible updating > Tern.java and AngularJS Eclipse IDE in Target Platform and central for > JBT 4.2.1 > Victor spent a few days testing the latest "stable" Terns/Angular builds > 0.7.0 (we are using 0.6.0 right now). He didn't find any new issues > there. So the new builds look OK to him. > > However, we decided not to update Tern/Angular for JBT 4.2.1 because: > 1. We don't have (well, we are not aware of ;) any critical issue in > current JBT/Tern/Angular which requires such update. > 2. We would have only one week or so for testing JBT 4.2.1.CR1(respin-a) > and we believe that Tern/Angular is still not stable enough to make sure > we won't get any critical/blocker issue with new builds. > 3. We also would have to update Angular in EA Central (not only Tern in > TP) for JBT and JBDS which increases risks just ~ 10 days before the > final JBT/JBDS release. We had such issues before when updated > Tern/Angular for JBT 4.2.0. > > So let's do not update Tern/Angular in 4.2.1 but do it for 4.2.2 and 4.3. > > Max, anybody, any objections? > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From psrna at redhat.com Wed Dec 3 03:28:22 2014 From: psrna at redhat.com (Pavol Srna) Date: Wed, 03 Dec 2014 09:28:22 +0100 Subject: [jbosstools-dev] Updating Tern.java & AngularJS Eclipse IDE? In-Reply-To: References: <547E41B3.7070803@exadel.com> Message-ID: <547EC9A6.3010705@redhat.com> If decided to NO go for tern and angular update - is still the plan to fix https://issues.jboss.org/browse/JBIDE-18591 on THYM side and do a quick TP update? -Pavol On 3.12.2014 08:52, Max Rydahl Andersen wrote: > Sounds reasonable. +1. > > /max > http://about.me/maxandersen > > >> On 02 Dec 2014, at 23:48, Alexey Kazakov wrote: >> >> Hi, >> >> Today on Mobile/HTML5 team meeting we discussed possible updating >> Tern.java and AngularJS Eclipse IDE in Target Platform and central for >> JBT 4.2.1 >> Victor spent a few days testing the latest "stable" Terns/Angular builds >> 0.7.0 (we are using 0.6.0 right now). He didn't find any new issues >> there. So the new builds look OK to him. >> >> However, we decided not to update Tern/Angular for JBT 4.2.1 because: >> 1. We don't have (well, we are not aware of ;) any critical issue in >> current JBT/Tern/Angular which requires such update. >> 2. We would have only one week or so for testing JBT 4.2.1.CR1(respin-a) >> and we believe that Tern/Angular is still not stable enough to make sure >> we won't get any critical/blocker issue with new builds. >> 3. We also would have to update Angular in EA Central (not only Tern in >> TP) for JBT and JBDS which increases risks just ~ 10 days before the >> final JBT/JBDS release. We had such issues before when updated >> Tern/Angular for JBT 4.2.0. >> >> So let's do not update Tern/Angular in 4.2.1 but do it for 4.2.2 and 4.3. >> >> Max, anybody, any objections? >> _______________________________________________ >> 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 angelo.zerr at gmail.com Wed Dec 3 03:32:59 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Wed, 3 Dec 2014 09:32:59 +0100 Subject: [jbosstools-dev] Updating Tern.java & AngularJS Eclipse IDE? In-Reply-To: References: <547E41B3.7070803@exadel.com> Message-ID: Hi Guys, At first you can see new feature of Tern 0.7.0 at https://github.com/angelozerr/tern.java/wiki/New-and-Noteworthy-0.7.0 There were too big refactoring since MyEclipse PR to improve tern file synchronization. Today the big problem with tern.java is when you have a lot of JS files in your project (with bower tool you can have a lot of JS files). If you configure correctly your tern script path https://github.com/angelozerr/tern.java/wiki/Tern-Script-Path you can set the folder which contains JS you need to parse with tern. BUT since 0.6.0, tern script path is configured by using JSDT Install Path, and it can be a problem, because : * in 0.6.0, the JSDT Install Path -> Tern script path was not very managed. Problems comes from with lib configuration. In this case, project folder is used. I have fixed that in 0.7.0 * JSDT Install Path -> Tern script path must be improved again like managing exclude script path https://github.com/angelozerr/tern.java/issues/168 There is a problem too when JS file is removed (tern server keep this file in memory, although it is removed) See https://github.com/angelozerr/tern.java/issues/157 In other words: * tern.java must improve again tern file synchronization. * don't parse the whole JS files of your project if your project has a lot of JS files. To fix this problem : => JSDT Install Path -> Tern script path should be improved => tern file synchronization should be done in background => tern is able to support condense of JS files, but it is not very stable. I think in the future, it should be very cool if we can condense for the first time, JS files, store it in file system (do the JS files analyze just the first time) In 0.8.0, I have the intention to support completion, validation, hyperlink, hover inside string. See my work for tabris https://github.com/eclipsesource/tabris-js/issues/180#issuecomment-65137514 and node.js require https://github.com/marijnh/tern/pull/430 I will try too to develop a tern builder for tern-lint. See https://github.com/angelozerr/tern.java/issues/174 Don't hesitate to create issues or PR to improve tern.java, thank's for your help! Regard's Angelo 2014-12-03 8:52 GMT+01:00 Max Rydahl Andersen : > Sounds reasonable. +1. > > /max > http://about.me/maxandersen > > > > On 02 Dec 2014, at 23:48, Alexey Kazakov wrote: > > > > Hi, > > > > Today on Mobile/HTML5 team meeting we discussed possible updating > > Tern.java and AngularJS Eclipse IDE in Target Platform and central for > > JBT 4.2.1 > > Victor spent a few days testing the latest "stable" Terns/Angular builds > > 0.7.0 (we are using 0.6.0 right now). He didn't find any new issues > > there. So the new builds look OK to him. > > > > However, we decided not to update Tern/Angular for JBT 4.2.1 because: > > 1. We don't have (well, we are not aware of ;) any critical issue in > > current JBT/Tern/Angular which requires such update. > > 2. We would have only one week or so for testing JBT 4.2.1.CR1(respin-a) > > and we believe that Tern/Angular is still not stable enough to make sure > > we won't get any critical/blocker issue with new builds. > > 3. We also would have to update Angular in EA Central (not only Tern in > > TP) for JBT and JBDS which increases risks just ~ 10 days before the > > final JBT/JBDS release. We had such issues before when updated > > Tern/Angular for JBT 4.2.0. > > > > So let's do not update Tern/Angular in 4.2.1 but do it for 4.2.2 and 4.3. > > > > Max, anybody, any objections? > > _______________________________________________ > > jbosstools-dev mailing list > > jbosstools-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141203/88692816/attachment.html From mistria at redhat.com Wed Dec 3 03:54:32 2014 From: mistria at redhat.com (Mickael Istria) Date: Wed, 03 Dec 2014 09:54:32 +0100 Subject: [jbosstools-dev] Updating Tern.java & AngularJS Eclipse IDE? In-Reply-To: <547EC9A6.3010705@redhat.com> References: <547E41B3.7070803@exadel.com> <547EC9A6.3010705@redhat.com> Message-ID: <547ECFC8.9020006@redhat.com> On 12/03/2014 09:28 AM, Pavol Srna wrote: > If decided to NO go for tern and angular update - is still the plan to > fix https://issues.jboss.org/browse/JBIDE-18591 on THYM side and do a > quick TP update? I'm not sure my comment is relevant but TP 4.50.0.Alpha1-SNAPSHOT and 4.41.1.CR2-SNAPSHOT were updated to include a newer THyM yesterday: https://issues.jboss.org/browse/JBIDE-18858 -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141203/cd693d8e/attachment.html From psrna at redhat.com Wed Dec 3 04:26:32 2014 From: psrna at redhat.com (Pavol Srna) Date: Wed, 03 Dec 2014 10:26:32 +0100 Subject: [jbosstools-dev] Updating Tern.java & AngularJS Eclipse IDE? In-Reply-To: <547ECFC8.9020006@redhat.com> References: <547E41B3.7070803@exadel.com> <547EC9A6.3010705@redhat.com> <547ECFC8.9020006@redhat.com> Message-ID: <547ED748.60600@redhat.com> Unfortunately if speaking about JBIDE-18591 it is not relevant. We have more options here: 1) - Update tern so that JBIDE-18591 will be fixed as part of it (but we already rejected this because of too much risk) 2) - Fix JBIDE-18591 on thym side and release new TP 3) - Move JBIDE-18591 to later version My question was about if we go for 2) or 3) On 3.12.2014 09:54, Mickael Istria wrote: > On 12/03/2014 09:28 AM, Pavol Srna wrote: >> If decided to NO go for tern and angular update - is still the plan to >> fixhttps://issues.jboss.org/browse/JBIDE-18591 on THYM side and do a >> quick TP update? > I'm not sure my comment is relevant but TP 4.50.0.Alpha1-SNAPSHOT and > 4.41.1.CR2-SNAPSHOT were updated to include a newer THyM yesterday: > https://issues.jboss.org/browse/JBIDE-18858 > -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141203/956861f3/attachment.html From manderse at redhat.com Wed Dec 3 05:26:17 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 03 Dec 2014 11:26:17 +0100 Subject: [jbosstools-dev] Updating Tern.java & AngularJS Eclipse IDE? In-Reply-To: <547ED748.60600@redhat.com> References: <547E41B3.7070803@exadel.com> <547EC9A6.3010705@redhat.com> <547ECFC8.9020006@redhat.com> <547ED748.60600@redhat.com> Message-ID: What I got from Alexey via chat this morning was that Gorkem was looking at fixing JBIDE-18591 in Thym and do TP update - but if that won't be ready for TP deadline then JBIDE-18591 wont be fixed in 4.2.1. It would be great with an update on JBIDE-18591 in its comments since right now it does read like Thym 0.7 is required. /max > Unfortunately if speaking about JBIDE-18591 it is not relevant. > > We have more options here: > 1) - Update tern so that JBIDE-18591 will be fixed as part of it (but > we already rejected this because of too much risk) > 2) - Fix JBIDE-18591 on thym side and release new TP > 3) - Move JBIDE-18591 to later version > > My question was about if we go for 2) or 3) > > On 3.12.2014 09:54, Mickael Istria wrote: >> On 12/03/2014 09:28 AM, Pavol Srna wrote: >>> If decided to NO go for tern and angular update - is still the plan >>> to >>> fixhttps://issues.jboss.org/browse/JBIDE-18591 on THYM side and do >>> a >>> quick TP update? >> I'm not sure my comment is relevant but TP 4.50.0.Alpha1-SNAPSHOT and >> 4.41.1.CR2-SNAPSHOT were updated to include a newer THyM yesterday: >> https://issues.jboss.org/browse/JBIDE-18858 >> > > > -- > 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 Dec 3 05:28:51 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 03 Dec 2014 11:28:51 +0100 Subject: [jbosstools-dev] Updating Tern.java & AngularJS Eclipse IDE? In-Reply-To: References: <547E41B3.7070803@exadel.com> Message-ID: <19C96A8D-8E84-4698-8CB0-CF4F4631DD02@redhat.com> Hey Angelo, Thanks for the info and yes it does look like great changes, but we are trying to avoid last minute breakages in our 4.2.1 update and last time we updated Tern it broke more than fixed for us thus we are being a bit conservative here. I hope we can get this into our upcoming update of 4.2.2 in the new year. /max > Hi Guys, > > At first you can see new feature of Tern 0.7.0 at > https://github.com/angelozerr/tern.java/wiki/New-and-Noteworthy-0.7.0 > > There were too big refactoring since MyEclipse PR to improve tern file > synchronization. > > Today the big problem with tern.java is when you have a lot of JS files in > your project (with bower tool you can have a lot of JS files). > > If you configure correctly your tern script path > https://github.com/angelozerr/tern.java/wiki/Tern-Script-Path you can set > the folder which contains JS you need to parse with tern. > > BUT since 0.6.0, tern script path is configured by using JSDT Install Path, > and it can be a problem, because : > > * in 0.6.0, the JSDT Install Path -> Tern script path was not very > managed. Problems comes from with lib configuration. In this case, project > folder is used. I have fixed that in 0.7.0 > * JSDT Install Path -> Tern script path must be improved again like > managing exclude script path > https://github.com/angelozerr/tern.java/issues/168 > > There is a problem too when JS file is removed (tern server keep this file > in memory, although it is removed) See > https://github.com/angelozerr/tern.java/issues/157 > > In other words: > > * tern.java must improve again tern file synchronization. > * don't parse the whole JS files of your project if your project has a lot > of JS files. To fix this problem : > => JSDT Install Path -> Tern script path should be improved > => tern file synchronization should be done in background > => tern is able to support condense of JS files, but it is not very > stable. I think in the future, it should be very cool if we can condense > for the first time, JS files, store it in file system (do the JS files > analyze just the first time) > > In 0.8.0, I have the intention to support completion, validation, > hyperlink, hover inside string. See my work for tabris > https://github.com/eclipsesource/tabris-js/issues/180#issuecomment-65137514 > and node.js require https://github.com/marijnh/tern/pull/430 > > I will try too to develop a tern builder for tern-lint. See > https://github.com/angelozerr/tern.java/issues/174 > > Don't hesitate to create issues or PR to improve tern.java, thank's for > your help! > > Regard's Angelo > > 2014-12-03 8:52 GMT+01:00 Max Rydahl Andersen : > >> Sounds reasonable. +1. >> >> /max >> http://about.me/maxandersen >> >> >>> On 02 Dec 2014, at 23:48, Alexey Kazakov wrote: >>> >>> Hi, >>> >>> Today on Mobile/HTML5 team meeting we discussed possible updating >>> Tern.java and AngularJS Eclipse IDE in Target Platform and central for >>> JBT 4.2.1 >>> Victor spent a few days testing the latest "stable" Terns/Angular builds >>> 0.7.0 (we are using 0.6.0 right now). He didn't find any new issues >>> there. So the new builds look OK to him. >>> >>> However, we decided not to update Tern/Angular for JBT 4.2.1 because: >>> 1. We don't have (well, we are not aware of ;) any critical issue in >>> current JBT/Tern/Angular which requires such update. >>> 2. We would have only one week or so for testing JBT 4.2.1.CR1(respin-a) >>> and we believe that Tern/Angular is still not stable enough to make sure >>> we won't get any critical/blocker issue with new builds. >>> 3. We also would have to update Angular in EA Central (not only Tern in >>> TP) for JBT and JBDS which increases risks just ~ 10 days before the >>> final JBT/JBDS release. We had such issues before when updated >>> Tern/Angular for JBT 4.2.0. >>> >>> So let's do not update Tern/Angular in 4.2.1 but do it for 4.2.2 and 4.3. >>> >>> Max, anybody, any objections? >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> /max http://about.me/maxandersen From manderse at redhat.com Wed Dec 3 05:33:09 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 03 Dec 2014 11:33:09 +0100 Subject: [jbosstools-dev] Updating Tern.java & AngularJS Eclipse IDE? In-Reply-To: References: <547E41B3.7070803@exadel.com> Message-ID: > Today the big problem with tern.java is when you have a lot of JS files in > your project (with bower tool you can have a lot of JS files). > > If you configure correctly your tern script path > https://github.com/angelozerr/tern.java/wiki/Tern-Script-Path you can set > the folder which contains JS you need to parse with tern. > > BUT since 0.6.0, tern script path is configured by using JSDT Install Path, > and it can be a problem, because : > > * in 0.6.0, the JSDT Install Path -> Tern script path was not very > managed. Problems comes from with lib configuration. In this case, project > folder is used. Not following what you mean here ? Got example of how to reproduce ? > I have fixed that in 0.7.0 > * JSDT Install Path -> Tern script path must be improved again like > managing exclude script path > https://github.com/angelozerr/tern.java/issues/168 I looked at this and it does not say what is the thing to improve ? /max http://about.me/maxandersen From angelo.zerr at gmail.com Wed Dec 3 06:40:07 2014 From: angelo.zerr at gmail.com (Angelo zerr) Date: Wed, 3 Dec 2014 12:40:07 +0100 Subject: [jbosstools-dev] Updating Tern.java & AngularJS Eclipse IDE? In-Reply-To: References: <547E41B3.7070803@exadel.com> Message-ID: > * in 0.6.0, the JSDT Install Path -> Tern script path was not very > managed. Problems comes from with lib configuration. In this case, project > folder is used. > Not following what you mean here ? Got example of how to reproduce ? If you screenshot of https://cloud.githubusercontent.com/assets/1614482/4785634/de9e3852-5d82-11e4-876c-baf206c4ffff.PNG You can see tern script path which is computed from JSDT (you see (jsdt) ate the end of each entries). In this sample you have twice projects folder (it's wrong, because JSDT Install path defines this 2 entries with excluding), and try to parse node_modules as file. It's wrong, because node_modules is a lib (and not a file). In this case, you think that tern will post JS files to tern server, but it does nothing : * project tern script is never used to post JS files * node_modules is a folder and not a file. > I looked at this and it does not say what is the thing to improve ? Yes I know -( I have created this issue quicly to remember me that I must do it. I will try to fill it once I will understand more how JSDT manages JSDT Install Path (with excluding, etc) If some JBoss guys which knows JSDT could help me with this topic (like Victor), it should be very cool, thank's! I think 0.8.0 should improve a lot tern file synchronization (JSDT Tern script path, manage remove of JS file, do synchronization on background when project is opened, do the capability to stop the parse of JS files with a button to avoid freezing). 2014-12-03 11:33 GMT+01:00 Max Rydahl Andersen : > > > > Today the big problem with tern.java is when you have a lot of JS files > in > > your project (with bower tool you can have a lot of JS files). > > > > If you configure correctly your tern script path > > https://github.com/angelozerr/tern.java/wiki/Tern-Script-Path you can > set > > the folder which contains JS you need to parse with tern. > > > > BUT since 0.6.0, tern script path is configured by using JSDT Install > Path, > > and it can be a problem, because : > > > > * in 0.6.0, the JSDT Install Path -> Tern script path was not very > > managed. Problems comes from with lib configuration. In this case, > project > > folder is used. > > Not following what you mean here ? Got example of how to reproduce ? > > > I have fixed that in 0.7.0 > > * JSDT Install Path -> Tern script path must be improved again like > > managing exclude script path > > https://github.com/angelozerr/tern.java/issues/168 > > I looked at this and it does not say what is the thing to improve ? > > /max > http://about.me/maxandersen > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141203/639b7116/attachment.html From mistria at redhat.com Thu Dec 4 12:14:54 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 04 Dec 2014 18:14:54 +0100 Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? Message-ID: <5480968E.3040808@redhat.com> Hi all, We're strongly brainstorming about our publication process: how to make it simpler? how to make it more independent from Jenkins? how to organize our various site in a more straightforward way?... As part of this investigation, we'd like to get rid of some legacy things that don't seem to provide value any more. So, before we make big changes, I have a simple question to ask you all: /In the p2 repository that is the output of build/CI, such as http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/ , what exact files have you consulted recently?/ The files that won't be mentioned in your answers will be dropped (only those that are there for aggregation will be kept). Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141204/06b2b7d7/attachment.html From rcernich at redhat.com Thu Dec 4 12:24:31 2014 From: rcernich at redhat.com (Rob Cernich) Date: Thu, 4 Dec 2014 12:24:31 -0500 (EST) Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: <5480968E.3040808@redhat.com> References: <5480968E.3040808@redhat.com> Message-ID: <1590643113.18325466.1417713871971.JavaMail.zimbra@redhat.com> For SwitchYard, I think these files are only used as input to the publish script which chunks the bits up to the public repo, e.g. http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/switchyard/2.0.0/ ----- Original Message ----- > Hi all, > We're strongly brainstorming about our publication process: how to make it > simpler? how to make it more independent from Jenkins? how to organize our > various site in a more straightforward way?... > As part of this investigation, we'd like to get rid of some legacy things > that don't seem to provide value any more. So, before we make big changes, I > have a simple question to ask you all: > In the p2 repository that is the output of build/CI, such as > http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/ > , what exact files have you consulted recently? > The files that won't be mentioned in your answers will be dropped (only those > that are there for aggregation will be kept). > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141204/f78d05ca/attachment.html From nboldt at redhat.com Thu Dec 4 12:25:24 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 04 Dec 2014 12:25:24 -0500 Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: <5480968E.3040808@redhat.com> References: <5480968E.3040808@redhat.com> Message-ID: <54809904.5000400@redhat.com> To get you thinking about what artifacts we mean, and which you might use, here's a couple examples: http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/logs/GIT_REVISION.txt [contains the SHA used to create that CI build] http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/logs/build.properties [contains details re: slave used for the build] -- Note that aggregate builds contain MORE metadata files. For example, we currently create summaries of the contents of the aggregate based on which projects fed that specific build: http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/ALL_REVISIONS.txt http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/build.properties.all.xml Does anyone use these? Nick On 12/04/2014 12:14 PM, Mickael Istria wrote: > Hi all, > > We're strongly brainstorming about our publication process: how to make > it simpler? how to make it more independent from Jenkins? how to > organize our various site in a more straightforward way?... > As part of this investigation, we'd like to get rid of some legacy > things that don't seem to provide value any more. So, before we make big > changes, I have a simple question to ask you all: > > /In the p2 repository that is the output of build/CI, such as > http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/ > , what exact files have you consulted recently?/ > > The files that won't be mentioned in your answers will be dropped (only > those that are there for aggregation will be kept). > > 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 dgolovin at exadel.com Thu Dec 4 12:36:11 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Thu, 04 Dec 2014 09:36:11 -0800 Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: <5480968E.3040808@redhat.com> References: <5480968E.3040808@redhat.com> Message-ID: <54809B8B.5080505@exadel.com> I've never ever used any of additional metadata files. It is always just p2 artifacts and rarely index.html. Denis On 12/04/2014 09:14 AM, Mickael Istria wrote: > Hi all, > > We're strongly brainstorming about our publication process: how to > make it simpler? how to make it more independent from Jenkins? how to > organize our various site in a more straightforward way?... > As part of this investigation, we'd like to get rid of some legacy > things that don't seem to provide value any more. So, before we make > big changes, I have a simple question to ask you all: > > /In the p2 repository that is the output of build/CI, such as > http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/ > , what exact files have you consulted recently?/ > > The files that won't be mentioned in your answers will be dropped > (only those that are there for aggregation will be kept). > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141204/3c8dfd0b/attachment-0001.html From nboldt at redhat.com Thu Dec 4 12:38:38 2014 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 04 Dec 2014 12:38:38 -0500 Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: <54809904.5000400@redhat.com> References: <5480968E.3040808@redhat.com> <54809904.5000400@redhat.com> Message-ID: <54809C1E.10105@redhat.com> For those with VPN access, we'd also like to know if anyone uses the build-info.html pages for JBDS (we used to have something similar for JBT too): http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.0.luna/installer/build-info.html If no one says "yes, that's useful" we'll likely remove it entirely for JBDS 9. Thanks, On 12/04/2014 12:25 PM, Nick Boldt wrote: > To get you thinking about what artifacts we mean, and which you might > use, here's a couple examples: > > http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/logs/GIT_REVISION.txt > [contains the SHA used to create that CI build] > http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/logs/build.properties > [contains details re: slave used for the build] > > -- > > Note that aggregate builds contain MORE metadata files. For example, we > currently create summaries of the contents of the aggregate based on > which projects fed that specific build: > > http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/ALL_REVISIONS.txt > > http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/build.properties.all.xml > > > Does anyone use these? > > Nick > > On 12/04/2014 12:14 PM, Mickael Istria wrote: >> Hi all, >> >> We're strongly brainstorming about our publication process: how to make >> it simpler? how to make it more independent from Jenkins? how to >> organize our various site in a more straightforward way?... >> As part of this investigation, we'd like to get rid of some legacy >> things that don't seem to provide value any more. So, before we make big >> changes, I have a simple question to ask you all: >> >> /In the p2 repository that is the output of build/CI, such as >> http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/ >> >> , what exact files have you consulted recently?/ >> >> The files that won't be mentioned in your answers will be dropped (only >> those that are there for aggregation will be kept). >> >> 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 dgolovin at exadel.com Thu Dec 4 13:23:33 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Thu, 04 Dec 2014 10:23:33 -0800 Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: <54809C1E.10105@redhat.com> References: <5480968E.3040808@redhat.com> <54809904.5000400@redhat.com> <54809C1E.10105@redhat.com> Message-ID: <5480A6A5.3080704@exadel.com> +1 to keep it. Denis On 12/04/2014 09:38 AM, Nick Boldt wrote: > For those with VPN access, we'd also like to know if anyone uses the > build-info.html pages for JBDS (we used to have something similar for > JBT too): > > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.0.luna/installer/build-info.html > > If no one says "yes, that's useful" we'll likely remove it entirely for > JBDS 9. > > Thanks, > > On 12/04/2014 12:25 PM, Nick Boldt wrote: >> To get you thinking about what artifacts we mean, and which you might >> use, here's a couple examples: >> >> http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/logs/GIT_REVISION.txt >> [contains the SHA used to create that CI build] >> http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/logs/build.properties >> [contains details re: slave used for the build] >> >> -- >> >> Note that aggregate builds contain MORE metadata files. For example, we >> currently create summaries of the contents of the aggregate based on >> which projects fed that specific build: >> >> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/ALL_REVISIONS.txt >> >> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/build.properties.all.xml >> >> >> Does anyone use these? >> >> Nick >> >> On 12/04/2014 12:14 PM, Mickael Istria wrote: >>> Hi all, >>> >>> We're strongly brainstorming about our publication process: how to make >>> it simpler? how to make it more independent from Jenkins? how to >>> organize our various site in a more straightforward way?... >>> As part of this investigation, we'd like to get rid of some legacy >>> things that don't seem to provide value any more. So, before we make big >>> changes, I have a simple question to ask you all: >>> >>> /In the p2 repository that is the output of build/CI, such as >>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/ >>> >>> , what exact files have you consulted recently?/ >>> >>> The files that won't be mentioned in your answers will be dropped (only >>> those that are there for aggregation will be kept). >>> >>> 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 >>> From mistria at redhat.com Thu Dec 4 13:26:04 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 04 Dec 2014 19:26:04 +0100 Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: <5480A6A5.3080704@exadel.com> References: <5480968E.3040808@redhat.com> <54809904.5000400@redhat.com> <54809C1E.10105@redhat.com> <5480A6A5.3080704@exadel.com> Message-ID: <5480A73C.1060305@redhat.com> On 12/04/2014 07:23 PM, Denis Golovin wrote: > +1 to keep it. >> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.0.luna/installer/build-info.html What's useful in this page than the regular listing of contents would not show? -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141204/6d6238bc/attachment.html From dgolovin at exadel.com Thu Dec 4 15:32:24 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Thu, 04 Dec 2014 12:32:24 -0800 Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: <5480A73C.1060305@redhat.com> References: <5480968E.3040808@redhat.com> <54809904.5000400@redhat.com> <54809C1E.10105@redhat.com> <5480A6A5.3080704@exadel.com> <5480A73C.1060305@redhat.com> Message-ID: <5480C4D8.9060108@exadel.com> Almost all info seems to be useful, but some links should reference static resources and some is not needed. Here are some ideas: 1. Logs This console should point to http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.0.luna/logs/BUILDLOG.txt 2. Logs -> Latest Console is not needed IMO 3. Revisions are really not easy to use, why not just populate this sections with links to github.com? 4. Target Platforms - JBT TP is not really required IMO 5. Target Platform Min and Max provides no idea what are they for. Better to have build with TP Version and Tested with TP Version 6. Test results should be links to static resources Denis On 12/04/2014 10:26 AM, Mickael Istria wrote: > On 12/04/2014 07:23 PM, Denis Golovin wrote: >> +1 to keep it. >>> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.0.luna/installer/build-info.html > What's useful in this page than the regular listing of contents would > not show? > -- > 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/20141204/e31ac672/attachment.html From manderse at redhat.com Fri Dec 5 02:59:27 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Fri, 5 Dec 2014 02:59:27 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 11 issues with no component Message-ID: <201412050759.sB57xRBr021311@int-mx10.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3243 https://issues.jboss.org/browse/JBDS-3243 Summary: as a JavaEE developer I would like to be able to use newest features of the JavaEE platform so I can be more effective Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 21:10:51.505467 ---------------------------- * No component for JBDS-3251 https://issues.jboss.org/browse/JBDS-3251 Summary: Create screencasts for top features we like users to know more about from both JBoss Tools and base 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: 19:07:41.504183 ---------------------------- * No component for JBDS-3250 https://issues.jboss.org/browse/JBDS-3250 Summary: Support for OpenShift 2&3 with Docker and Kubernetes Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 20:21:58.504347 ---------------------------- * No component for JBIDE-18872 https://issues.jboss.org/browse/JBIDE-18872 Summary: Promote JBoss Tools CAT in JBT/JBDS About box 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:27:28.503819 ---------------------------- * No component for JBDS-3252 https://issues.jboss.org/browse/JBDS-3252 Summary: JBoss Modules support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 18:51:42.504016 ---------------------------- * No component for JBDS-3246 https://issues.jboss.org/browse/JBDS-3246 Summary: As part of JBoss Tools team I would like to gather usage, feedback, download statistics to get better insight into what are our users do/struggle with so I can fix issues and implement features that matters and help the user Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 20:30:49.504998 ---------------------------- * No component for JBDS-3247 https://issues.jboss.org/browse/JBDS-3247 Summary: Hybrid Mobile Tooling covering base Apache Cordova and FeedHenry support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 20:28:16.504836 ---------------------------- * No component for JBDS-3244 https://issues.jboss.org/browse/JBDS-3244 Summary: As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 21:08:54.505313 ---------------------------- * No component for JBDS-3245 https://issues.jboss.org/browse/JBDS-3245 Summary: Improve Eclipse Platform Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 20:45:44.505156 ---------------------------- * No component for JBDS-3248 https://issues.jboss.org/browse/JBDS-3248 Summary: As jboss.org Developer I would like to be able to present info in central faster so our users can get access to quickstarts, wizards, tutorials as they are made available Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 20:59:14.504664 ---------------------------- * No component for JBDS-3249 https://issues.jboss.org/browse/JBDS-3249 Summary: As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 20:25:06.504506 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From manderse at redhat.com Fri Dec 5 05:13:27 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Fri, 5 Dec 2014 05:13:27 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 11 issues with no component Message-ID: <201412051013.sB5ADRqJ006132@int-mx13.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3243 https://issues.jboss.org/browse/JBDS-3243 Summary: as a JavaEE developer I would like to be able to use newest features of the JavaEE platform so I can be more effective Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 23:24:51.432859 ---------------------------- * No component for JBDS-3251 https://issues.jboss.org/browse/JBDS-3251 Summary: Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 21:21:41.431289 ---------------------------- * No component for JBDS-3250 https://issues.jboss.org/browse/JBDS-3250 Summary: Support for OpenShift 2&3 with Docker and Kubernetes Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 22:35:58.431472 ---------------------------- * No component for JBIDE-18872 https://issues.jboss.org/browse/JBIDE-18872 Summary: Promote JBoss Tools CAT in JBT/JBDS About box 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:41:28.430883 ---------------------------- * No component for JBDS-3252 https://issues.jboss.org/browse/JBDS-3252 Summary: JBoss Modules support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 21:05:42.431105 ---------------------------- * No component for JBDS-3246 https://issues.jboss.org/browse/JBDS-3246 Summary: As part of JBoss Tools team I would like to gather usage, feedback, download statistics to get better insight into what are our users do/struggle with so I can fix issues and implement features that matters and help the user Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 22:44:49.432243 ---------------------------- * No component for JBDS-3247 https://issues.jboss.org/browse/JBDS-3247 Summary: Hybrid Mobile Tooling covering base Apache Cordova and FeedHenry support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 22:42:16.432060 ---------------------------- * No component for JBDS-3244 https://issues.jboss.org/browse/JBDS-3244 Summary: As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 23:22:54.432662 ---------------------------- * No component for JBDS-3245 https://issues.jboss.org/browse/JBDS-3245 Summary: Improve Eclipse Platform Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 22:59:44.432426 ---------------------------- * No component for JBDS-3248 https://issues.jboss.org/browse/JBDS-3248 Summary: As jboss.org Developer I would like to be able to present info in central faster so our users can get access to quickstarts, wizards, tutorials as they are made available Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 23:13:14.431877 ---------------------------- * No component for JBDS-3249 https://issues.jboss.org/browse/JBDS-3249 Summary: As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 22:39:06.431692 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From manderse at redhat.com Fri Dec 5 06:10:53 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 05 Dec 2014 12:10:53 +0100 Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: <5480A73C.1060305@redhat.com> References: <5480968E.3040808@redhat.com> <54809904.5000400@redhat.com> <54809C1E.10105@redhat.com> <5480A6A5.3080704@exadel.com> <5480A73C.1060305@redhat.com> Message-ID: On 4 Dec 2014, at 19:26, Mickael Istria wrote: > On 12/04/2014 07:23 PM, Denis Golovin wrote: >> +1 to keep it. >>> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.0.luna/installer/build-info.html > What's useful in this page than the regular listing of contents would > not show? what is regular listing of contents ? You mean direct raw dump of the files ? /max http://about.me/maxandersen From manderse at redhat.com Fri Dec 5 10:10:23 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 05 Dec 2014 16:10:23 +0100 Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: <54809904.5000400@redhat.com> References: <5480968E.3040808@redhat.com> <54809904.5000400@redhat.com> Message-ID: Great we are looking at rationalizing what metadata we generate but I think it is the wrong question being asked. It is not wether we use the files, it is wether we need them. i.e. git revisions we don't use actively, but we do need them since that is the only way we actually know which repository SHA's have been used. I think we catch most of this in eclipse source references today - but that is only for bundles, not for other artifacts like the udpdate sites, features etc. thus this information is relevant. Build properties are useful to actually reproduce or at least trace what actually was done in the build ? The build logs are also mostly for investigative purposes and if these were actually available within a build that would useful (removes need to wait for jenkins to load) What is missing is actually being able to find and read this info. Also, some of the files seem to be in a very hard to parse format even though it would be really great to do so. i.e. http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/md5sums.txt doesn't actually list the zip name the md5sum relate to...also it looks like the numbers are always the same which smells like a bug. Also the git logs only says the sha1, but not which repository it comes from. Thus I think most of this info is actually very relevant info to have but looks like it could be cleaned up, checked for errors and document it. for example what is zip.list.txt? /max > To get you thinking about what artifacts we mean, and which you might > use, here's a couple examples: > > http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/logs/GIT_REVISION.txt > [contains the SHA used to create that CI build] > http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/logs/build.properties > [contains details re: slave used for the build] > > -- > > Note that aggregate builds contain MORE metadata files. For example, > we > currently create summaries of the contents of the aggregate based on > which projects fed that specific build: > > http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/ALL_REVISIONS.txt > http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/build.properties.all.xml > > Does anyone use these? > > Nick > > On 12/04/2014 12:14 PM, Mickael Istria wrote: >> Hi all, >> >> We're strongly brainstorming about our publication process: how to >> make >> it simpler? how to make it more independent from Jenkins? how to >> organize our various site in a more straightforward way?... >> As part of this investigation, we'd like to get rid of some legacy >> things that don't seem to provide value any more. So, before we make >> big >> changes, I have a simple question to ask you all: >> >> /In the p2 repository that is the output of build/CI, such as >> http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/ >> , what exact files have you consulted recently?/ >> >> The files that won't be mentioned in your answers will be dropped >> (only >> those that are there for aggregation will be kept). >> >> 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 > _______________________________________________ > 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 Dec 5 12:09:51 2014 From: mistria at redhat.com (Mickael Istria) Date: Fri, 05 Dec 2014 18:09:51 +0100 Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: References: <5480968E.3040808@redhat.com> <54809904.5000400@redhat.com> Message-ID: <5481E6DF.90704@redhat.com> On 12/05/2014 04:10 PM, Max Rydahl Andersen wrote: > Great we are looking at rationalizing what metadata we generate but I > think > it is the wrong question being asked. It is not wether we use the files, > it is wether we need them. We'll obviously keep the ones we need. Nick and I seemed to identify that only GIT_REVISION.txt and build.properties are currently needed for aggregation and are actually used occasionally. > The build logs are also mostly for investigative purposes and if these > were actually available within a build that would useful (removes need > to wait for jenkins to load) Hypothetical "would" isn't enough here. For investigation, I find it pretty acceptable and consistent with the possible failures to either look at Jenkins log directly or re-run the build locally. > What is missing is actually being able to find and read this info. Can you please elaborate on an *actual* use-case which drives you to this assumption? > i.e. > http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/md5sums.txt > doesn't actually list the zip name the md5sum relate to...also it looks > like the numbers are always the same which smells like a bug. I agree on the smell of a bug there. > Also the git logs only says the sha1, but not which repository it comes > from. I plan to fix this in the publish mojo I'm working on. > Thus I think most of this info is actually very relevant info to have > but looks like it could be cleaned up, checked for errors and document > it. It may be relevant, but is it worth the maintenance effort? -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141205/0ba0c40b/attachment.html From manderse at redhat.com Fri Dec 5 12:36:06 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 5 Dec 2014 12:36:06 -0500 (EST) Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: <5481E6DF.90704@redhat.com> References: <5480968E.3040808@redhat.com> <54809904.5000400@redhat.com> <5481E6DF.90704@redhat.com> Message-ID: > On 05 Dec 2014, at 18:10, Mickael Istria wrote: > >> On 12/05/2014 04:10 PM, Max Rydahl Andersen wrote: >> Great we are looking at rationalizing what metadata we generate but I >> think >> it is the wrong question being asked. It is not wether we use the files, >> it is wether we need them. > We'll obviously keep the ones we need. Nick and I seemed to identify that only GIT_REVISION.txt and build.properties are currently needed for aggregation and are actually used occasionally. How are they used in aggregation ? For other things than just info to add to the aggregation ? >> The build logs are also mostly for investigative purposes and if these >> were actually available within a build that would useful (removes need >> to wait for jenkins to load) > Hypothetical "would" isn't enough here. For investigation, I find it pretty acceptable and consistent with the possible failures to either look at Jenkins log directly or re-run the build locally. Not everyone has access to Jenkins. Rerunning builds isn't possible if the jobs actually changed since then. Usecases are: knowing what version of what content was actually included in the build. And since we never go out of snapshot mode these logs are the only way to actually know the details. >> What is missing is actually being able to find and read this info. > Can you please elaborate on an *actual* use-case which drives you to this assumption? That these actually never are used and you have to know how to find them. >> i.e. >> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/md5sums.txt >> doesn't actually list the zip name the md5sum relate to...also it looks >> like the numbers are always the same which smells like a bug. > I agree on the smell of a bug there. >> Also the git logs only says the sha1, but not which repository it comes >> from. > I plan to fix this in the publish mojo I'm working on. >> Thus I think most of this info is actually very relevant info to have >> but looks like it could be cleaned up, checked for errors and document >> it. > It may be relevant, but is it worth the maintenance effort? What is the maintaence effort here ? Afaik it's copy of the files generated in the build ? > > -- > 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/20141205/5ff15e20/attachment.html From manderse at redhat.com Sat Dec 6 02:59:08 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Sat, 6 Dec 2014 02:59:08 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 9 issues with no component Message-ID: <201412060759.sB67x8j0006041@int-mx11.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3251 https://issues.jboss.org/browse/JBDS-3251 Summary: Create screencasts for top features we like users to know more about from both JBoss Tools and base 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: 1 day, 19:07:22.677177 ---------------------------- * No component for JBDS-3243 https://issues.jboss.org/browse/JBDS-3243 Summary: as a JavaEE developer I would like to be able to use newest features of the JavaEE platform so I can be more effective Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 21:10:32.678134 ---------------------------- * No component for JBIDE-18872 https://issues.jboss.org/browse/JBIDE-18872 Summary: Promote JBoss Tools CAT in JBT/JBDS About box Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 17:27:09.676820 ---------------------------- * No component for JBDS-3252 https://issues.jboss.org/browse/JBDS-3252 Summary: JBoss Modules support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 18:51:23.677009 ---------------------------- * No component for JBDS-3246 https://issues.jboss.org/browse/JBDS-3246 Summary: As part of JBoss Tools team I would like to gather usage, feedback, download statistics to get better insight into what are our users do/struggle with so I can fix issues and implement features that matters and help the user Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 20:30:30.677658 ---------------------------- * No component for JBDS-3244 https://issues.jboss.org/browse/JBDS-3244 Summary: As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 21:08:35.677977 ---------------------------- * No component for JBDS-3245 https://issues.jboss.org/browse/JBDS-3245 Summary: Improve Eclipse Platform Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 20:45:25.677814 ---------------------------- * No component for JBDS-3248 https://issues.jboss.org/browse/JBDS-3248 Summary: As jboss.org Developer I would like to be able to present info in central faster so our users can get access to quickstarts, wizards, tutorials as they are made available Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 20:58:55.677499 ---------------------------- * No component for JBDS-3249 https://issues.jboss.org/browse/JBDS-3249 Summary: As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 20:24:47.677340 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From manderse at redhat.com Sun Dec 7 02:59:05 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Sun, 7 Dec 2014 02:59:05 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 9 issues with no component Message-ID: <201412070759.sB77x5eR016637@int-mx10.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3251 https://issues.jboss.org/browse/JBDS-3251 Summary: Create screencasts for top features we like users to know more about from both JBoss Tools and base 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: 2 days, 19:07:19.395235 ---------------------------- * No component for JBDS-3243 https://issues.jboss.org/browse/JBDS-3243 Summary: as a JavaEE developer I would like to be able to use newest features of the JavaEE platform so I can be more effective Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 21:10:29.397368 ---------------------------- * No component for JBIDE-18872 https://issues.jboss.org/browse/JBIDE-18872 Summary: Promote JBoss Tools CAT in JBT/JBDS About box Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 17:27:06.394435 ---------------------------- * No component for JBDS-3252 https://issues.jboss.org/browse/JBDS-3252 Summary: JBoss Modules support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 18:51:20.394878 ---------------------------- * No component for JBDS-3246 https://issues.jboss.org/browse/JBDS-3246 Summary: As part of JBoss Tools team I would like to gather usage, feedback, download statistics to get better insight into what are our users do/struggle with so I can fix issues and implement features that matters and help the user Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 20:30:27.396300 ---------------------------- * No component for JBDS-3244 https://issues.jboss.org/browse/JBDS-3244 Summary: As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 21:08:32.397014 ---------------------------- * No component for JBDS-3245 https://issues.jboss.org/browse/JBDS-3245 Summary: Improve Eclipse Platform Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 20:45:22.396654 ---------------------------- * No component for JBDS-3248 https://issues.jboss.org/browse/JBDS-3248 Summary: As jboss.org Developer I would like to be able to present info in central faster so our users can get access to quickstarts, wizards, tutorials as they are made available Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 20:58:52.395943 ---------------------------- * No component for JBDS-3249 https://issues.jboss.org/browse/JBDS-3249 Summary: As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 20:24:44.395586 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From nboldt at redhat.com Sun Dec 7 12:31:25 2014 From: nboldt at redhat.com (Nick Boldt) Date: Sun, 07 Dec 2014 12:31:25 -0500 Subject: [jbosstools-dev] JBoss Tools Core 4.2.1.CR2 (CR1a) bits available for QE testing Message-ID: <54848EED.2020801@redhat.com> As always, these are not FINAL bits, but preliminary results for QE & community testing. Not for use by customers or end users. Update site: http://download.jboss.org/jbosstools/updates/staging/luna/ Target platforms: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Final * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.41.1.CR2 Until the above target platform site is released, you may need to add it to Eclipse to resolve dependencies at install time. Once released, dependencies will be found automatically from here: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ (latest release) * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.41.1.CR1-SNAPSHOT/ (upcoming milestone) * http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.41.1.CR1-SNAPSHOT/ (upcoming milestone) New + noteworthy (subject to change): * https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew * http://tools.jboss.org/documentation/whatsnew/ Schedule: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Additional update sites: * http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR2-updatesite-core/ * http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR2-updatesite-coretests/ * http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR2-updatesite-hibernatetools/ * http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.CR2-updatesite-webtools/ and build sites: * http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR2-build-core/ * http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR2-build-coretests/ * http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR2-build-hibernatetools/ * http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR2-build-webtools/ -- 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%228.0.1.CR1%22%29%29%20or%20%28project%20in%20%28%22JBIDE%22%2C%22TOOLSDOC%22%29%20and%20fixversion%20in%20%28%224.2.1.CR1%22%29%29%29 To compare the upcoming version of Central (4.2.1.CR2) 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/discovery/staging/4.2.1.CR2/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/staging/4.2.1.CR2/ -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/staging/4.2.1.CR2/ -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Sun Dec 7 22:18:50 2014 From: nboldt at redhat.com (Nick Boldt) Date: Sun, 07 Dec 2014 22:18:50 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Prepare for 4.2.1.Final / 8.0.1.GA (release is next week Dec 15 2014) Message-ID: <5485189A.3060601@redhat.com> This week is the "quiet period" in prep for 4.2.1.Final / 8.0.1.GA. You are required to update your root poms to point at the latest parent pom, version 4.2.1.Final-SNAPSHOT. Below you'll see a list of task jiras for that. -- Note too that the Final target platforms have NOT been released yet so please keep using the Final-SNAPSHOT versions until you see an announcement that the target platforms have been released (and -SNAPSHOT is removed). Latest Target Platform changes are linked from here: * https://issues.jboss.org/browse/JBDS-3215 There *MAY* be one more TP change for Thym as a result of https://issues.jboss.org/browse/JBIDE-18711. -- There are 3 outstanding issues pending for 4.2.1/8.0.1 (for Hibernate and Aerogear) - please take a look and triage them as blocker for this release, or move them to the next one. https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE%22%20and%20fixVersion%20in%20%28%224.2.1.CR1%22%2C%20%224.2.1.CR2%22%2C%20%224.2.1.Final%22%29%29%20or%20%28project%20%3D%20%22JBDS%22%20and%20fixversion%20in%20%28%228.0.1.CR1%22%2C%228.0.1.GA%22%29%29%29%20and%20resolution%20%3D%20Unresolved -- Task JIRA created for this milestone include: JBDS : https://issues.jboss.org/browse/JBDS-3254 JBoss Tools : https://issues.jboss.org/browse/JBIDE-18881 Aerogear : https://issues.jboss.org/browse/JBIDE-18882 JST : https://issues.jboss.org/browse/JBIDE-18883 VPE : https://issues.jboss.org/browse/JBIDE-18884 JBT Update Sites : https://issues.jboss.org/browse/JBIDE-18885 Server : https://issues.jboss.org/browse/JBIDE-18886 Base : https://issues.jboss.org/browse/JBIDE-18887 OpenShift : https://issues.jboss.org/browse/JBIDE-18888 JavaEE : https://issues.jboss.org/browse/JBIDE-18889 Birt : https://issues.jboss.org/browse/JBIDE-18890 Forge : https://issues.jboss.org/browse/JBIDE-18891 BrowserSim : https://issues.jboss.org/browse/JBIDE-18892 Webservices : https://issues.jboss.org/browse/JBIDE-18893 Arquillian : https://issues.jboss.org/browse/JBIDE-18894 Central : https://issues.jboss.org/browse/JBIDE-18895 Portlet : https://issues.jboss.org/browse/JBIDE-18896 Freemarker : https://issues.jboss.org/browse/JBIDE-18897 Central Discovery : https://issues.jboss.org/browse/JBIDE-18898 I did not create task JIRAs for Hibernate and Livereload, because neither of those have commits in the 4.2.x branch since 4.2.0.Final and therefore need not have their root poms adjusted. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Mon Dec 8 02:01:09 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 8 Dec 2014 02:01:09 -0500 (EST) Subject: [jbosstools-dev] ACTION REQUIRED: Prepare for 4.2.1.Final / 8.0.1.GA (release is next week Dec 15 2014) In-Reply-To: <5485189A.3060601@redhat.com> References: <5485189A.3060601@redhat.com> Message-ID: > On 08 Dec 2014, at 04:19, Nick Boldt wrote: > > his week is the "quiet period" in prep for 4.2.1.Final / 8.0.1.GA. > > You are required to update your root poms to point at the latest parent > pom, I assume you mean "If and only if the build your component is in has changed since 4.2.0.Final", correct ? As otherwise we are going to have updates to *everything* which is what we don't want for our maintanence builds. Just want to make sure the above is what you meant or to know if you found something in our build that requires *every* component to update parent Pom? From manderse at redhat.com Mon Dec 8 02:59:05 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Mon, 8 Dec 2014 02:59:05 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 8 issues with no component Message-ID: <201412080759.sB87x5q7029043@int-mx10.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3251 https://issues.jboss.org/browse/JBDS-3251 Summary: Create screencasts for top features we like users to know more about from both JBoss Tools and base 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: 3 days, 19:07:19.387545 ---------------------------- * No component for JBDS-3243 https://issues.jboss.org/browse/JBDS-3243 Summary: as a JavaEE developer I would like to be able to use newest features of the JavaEE platform so I can be more effective Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 21:10:29.389667 ---------------------------- * No component for JBDS-3252 https://issues.jboss.org/browse/JBDS-3252 Summary: JBoss Modules support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 18:51:20.387116 ---------------------------- * No component for JBDS-3246 https://issues.jboss.org/browse/JBDS-3246 Summary: As part of JBoss Tools team I would like to gather usage, feedback, download statistics to get better insight into what are our users do/struggle with so I can fix issues and implement features that matters and help the user Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 20:30:27.388608 ---------------------------- * No component for JBDS-3244 https://issues.jboss.org/browse/JBDS-3244 Summary: As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 21:08:32.389319 ---------------------------- * No component for JBDS-3245 https://issues.jboss.org/browse/JBDS-3245 Summary: Improve Eclipse Platform Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 20:45:22.388968 ---------------------------- * No component for JBDS-3248 https://issues.jboss.org/browse/JBDS-3248 Summary: As jboss.org Developer I would like to be able to present info in central faster so our users can get access to quickstarts, wizards, tutorials as they are made available Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 20:58:52.388260 ---------------------------- * No component for JBDS-3249 https://issues.jboss.org/browse/JBDS-3249 Summary: As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 20:24:44.387910 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From manderse at redhat.com Mon Dec 8 03:21:13 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Mon, 08 Dec 2014 09:21:13 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: 8 issues with no component In-Reply-To: <201412080759.sB87x5q7029043@int-mx10.intmail.prod.int.phx2.redhat.com> References: <201412080759.sB87x5q7029043@int-mx10.intmail.prod.int.phx2.redhat.com> Message-ID: sorry for these - now fixed. aside: its really annoying epic creation does not allow specifying components upfront ;/ /max > This email is the result of a query to locate stalled/invalid jiras. > Please fix them. Thanks! > > > * No component for JBDS-3251 > > https://issues.jboss.org/browse/JBDS-3251 > Summary: Create screencasts for top features we like users to know > more about from both JBoss Tools and base 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: 3 days, 19:07:19.387545 > > ---------------------------- > > > * No component for JBDS-3243 > > https://issues.jboss.org/browse/JBDS-3243 > Summary: as a JavaEE developer I would like to be able to use newest > features of the JavaEE platform so I can be more effective > > Assignee: None set - please fix. > Component: None set - please fix. > Problem: No component - please assign this issue to one or more > components. > Last Update: 3 days, 21:10:29.389667 > > ---------------------------- > > > * No component for JBDS-3252 > > https://issues.jboss.org/browse/JBDS-3252 > Summary: JBoss Modules support > > Assignee: None set - please fix. > Component: None set - please fix. > Problem: No component - please assign this issue to one or more > components. > Last Update: 3 days, 18:51:20.387116 > > ---------------------------- > > > * No component for JBDS-3246 > > https://issues.jboss.org/browse/JBDS-3246 > Summary: As part of JBoss Tools team I would like to gather usage, > feedback, download statistics to get better insight into what are our > users do/struggle with so I can fix issues and implement features that > matters and help the user > > Assignee: None set - please fix. > Component: None set - please fix. > Problem: No component - please assign this issue to one or more > components. > Last Update: 3 days, 20:30:27.388608 > > ---------------------------- > > > * No component for JBDS-3244 > > https://issues.jboss.org/browse/JBDS-3244 > Summary: As a JavaEE or Mobile developer I would like to have fast and > helpful HTML5 and JavaScript tooling so I can work on my projects that > contain more and more html5/javascript code > > Assignee: None set - please fix. > Component: None set - please fix. > Problem: No component - please assign this issue to one or more > components. > Last Update: 3 days, 21:08:32.389319 > > ---------------------------- > > > * No component for JBDS-3245 > > https://issues.jboss.org/browse/JBDS-3245 > Summary: Improve Eclipse Platform > > Assignee: None set - please fix. > Component: None set - please fix. > Problem: No component - please assign this issue to one or more > components. > Last Update: 3 days, 20:45:22.388968 > > ---------------------------- > > > * No component for JBDS-3248 > > https://issues.jboss.org/browse/JBDS-3248 > Summary: As jboss.org Developer I would like to be able to present > info in central faster so our users can get access to quickstarts, > wizards, tutorials as they are made available > > Assignee: None set - please fix. > Component: None set - please fix. > Problem: No component - please assign this issue to one or more > components. > Last Update: 3 days, 20:58:52.388260 > > ---------------------------- > > > * No component for JBDS-3249 > > https://issues.jboss.org/browse/JBDS-3249 > Summary: As an Integration User I would like to easily install parts > of IS without many unnecessary intermediate steps > > Assignee: None set - please fix. > Component: None set - please fix. > Problem: No component - please assign this issue to one or more > components. > Last Update: 3 days, 20:24:44.387910 > > ---------------------------- > > > > Query used: > https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From jmdominguez at gauzoniberica.com Mon Dec 8 15:55:16 2014 From: jmdominguez at gauzoniberica.com (Alexy G.) Date: Mon, 8 Dec 2014 22:55:16 +0200 Subject: [jbosstools-dev] Enjoying life Message-ID: <9C6609AD0FDBF566BABFF64A5EE9A51D@88.249.104.4.dynamic.ttnet.com.tr> Aloha my friend I am friendly, optimistic, tactful, not intrusive http://ur1.ca/j1osh People always feel comfortable talking with me and my friends say that I am a very good, devoted, caring friend. I can keep any conversation alive. I am ready to give much in a relationship and I want to devote all my love and care to the person who appreciates it. I hope to meet a kind, balanced and romantic man. Let me hear from you Alex G. From nboldt at redhat.com Mon Dec 8 15:54:09 2014 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 08 Dec 2014 15:54:09 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Prepare for 4.2.1.Final / 8.0.1.GA (release is next week Dec 15 2014) In-Reply-To: References: <5485189A.3060601@redhat.com> Message-ID: <54860FF1.5000003@redhat.com> TL;DR: Yes. > I did not create task JIRAs for Hibernate and Livereload, because > neither of those have commits in the 4.2.x branch since 4.2.0.Final and > therefore need not have their root poms adjusted. On 12/08/2014 02:01 AM, Max Rydahl Andersen wrote: > > >> On 08 Dec 2014, at 04:19, Nick Boldt wrote: >> >> his week is the "quiet period" in prep for 4.2.1.Final / 8.0.1.GA. >> >> You are required to update your root poms to point at the latest parent >> pom, > > I assume you mean "If and only if the build your component is in has changed since 4.2.0.Final", correct ? > > As otherwise we are going to have updates to *everything* which is what we don't want for our maintanence builds. > > Just want to make sure the above is what you meant or to know if you found something in our build that requires *every* component to update parent Pom? > > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From akazakov at exadel.com Mon Dec 8 20:19:10 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Mon, 08 Dec 2014 17:19:10 -0800 Subject: [jbosstools-dev] ACTION REQUIRED: Prepare for 4.2.1.Final / 8.0.1.GA (release is next week Dec 15 2014) In-Reply-To: <54860FF1.5000003@redhat.com> References: <5485189A.3060601@redhat.com> <54860FF1.5000003@redhat.com> Message-ID: <54864E0E.2070900@exadel.com> Thanks to all component leads who updated their root poms (and I updated the rest of components: forge, aerogear, central, freemarker). So all components that have been changed since 4.2.0 are using 4.2.1.Final-SNAPSHOT root pom now. However, two components, Birt and Portlet don't have any changes besides updated root poms. As I understand we should change the root pom versio ONLY if the component has been changed since 4.2.0.Final. I reopened the corresponding issues for Birt and Portlet for clarification: https://issues.jboss.org/browse/JBIDE-18890 https://issues.jboss.org/browse/JBIDE-18896 Should we ignore these changes and not to rebuild Birt & Portlet for 4.2.1? On 12/08/2014 12:54 PM, Nick Boldt wrote: > TL;DR: Yes. > >> I did not create task JIRAs for Hibernate and Livereload, because >> neither of those have commits in the 4.2.x branch since 4.2.0.Final and >> therefore need not have their root poms adjusted. > > On 12/08/2014 02:01 AM, Max Rydahl Andersen wrote: >> >>> On 08 Dec 2014, at 04:19, Nick Boldt wrote: >>> >>> his week is the "quiet period" in prep for 4.2.1.Final / 8.0.1.GA. >>> >>> You are required to update your root poms to point at the latest parent >>> pom, >> I assume you mean "If and only if the build your component is in has changed since 4.2.0.Final", correct ? >> >> As otherwise we are going to have updates to *everything* which is what we don't want for our maintanence builds. >> >> Just want to make sure the above is what you meant or to know if you found something in our build that requires *every* component to update parent Pom? >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141208/329f4cbc/attachment.html From akazakov at exadel.com Mon Dec 8 20:39:41 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Mon, 08 Dec 2014 17:39:41 -0800 Subject: [jbosstools-dev] ACTION REQUIRED: Blocker for 4.2.1 in Hibernate? In-Reply-To: <5485189A.3060601@redhat.com> References: <5485189A.3060601@redhat.com> Message-ID: <548652DD.3020608@exadel.com> On 12/07/2014 07:18 PM, Nick Boldt wrote: > There are 3 outstanding issues pending for 4.2.1/8.0.1 (for Hibernate > and Aerogear) - please take a look and triage them as blocker for this > release, or move them to the next one. > > https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE%22%20and%20fixVersion%20in%20%28%224.2.1.CR1%22%2C%20%224.2.1.CR2%22%2C%20%224.2.1.Final%22%29%29%20or%20%28project%20%3D%20%22JBDS%22%20and%20fixversion%20in%20%28%228.0.1.CR1%22%2C%228.0.1.GA%22%29%29%29%20and%20resolution%20%3D%20Unresolved > There is a blocker for https://issues.jboss.org/browse/JBIDE-18878 (Hibernate), Koen, Len (I don't know who tests hibernate) could you please take a look at this issue ASAP? We have to know how critical it's for coming 4.2.1 release. From manderse at redhat.com Tue Dec 9 03:04:13 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Tue, 9 Dec 2014 03:04:13 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 5 issues with no component Message-ID: <201412090804.sB984DAU011836@int-mx09.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3259 https://issues.jboss.org/browse/JBDS-3259 Summary: Markdown Viewer Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 15:24:02.228392 ---------------------------- * No component for JBDS-3261 https://issues.jboss.org/browse/JBDS-3261 Summary: JSR-356: Websockets Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 14:12:28.228212 ---------------------------- * No component for JBDS-3256 https://issues.jboss.org/browse/JBDS-3256 Summary: Docker Tooling (Basic Integration) Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 14:11:52.228874 ---------------------------- * No component for JBDS-3257 https://issues.jboss.org/browse/JBDS-3257 Summary: Basic FeedHenry Support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 16:07:22.228716 ---------------------------- * No component for JBDS-3258 https://issues.jboss.org/browse/JBDS-3258 Summary: Docker Tooling (Advanced Integration) Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 14:11:42.228556 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From manderse at redhat.com Tue Dec 9 05:19:49 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 09 Dec 2014 11:19:49 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Prepare for 4.2.1.Final / 8.0.1.GA (release is next week Dec 15 2014) In-Reply-To: <54864E0E.2070900@exadel.com> References: <5485189A.3060601@redhat.com> <54860FF1.5000003@redhat.com> <54864E0E.2070900@exadel.com> Message-ID: <61006C2C-02AB-45C0-9ED5-4F896A6E5133@redhat.com> On 9 Dec 2014, at 2:19, Alexey Kazakov wrote: > Thanks to all component leads who updated their root poms (and I > updated the rest of components: forge, aerogear, central, freemarker). > So all components that have been changed since 4.2.0 are using > 4.2.1.Final-SNAPSHOT root pom now. > However, two components, Birt and Portlet don't have any changes > besides updated root poms. As I understand we should change the root > pom versio ONLY if the component has been changed since 4.2.0.Final. > I reopened the corresponding issues for Birt and Portlet for > clarification: > https://issues.jboss.org/browse/JBIDE-18890 > https://issues.jboss.org/browse/JBIDE-18896 > Should we ignore these changes and not to rebuild Birt & Portlet for > 4.2.1? I would say so - we have the 4.2.0.Final updatesite to get these from so sounds weird why we need to update these. The whole intent we are going for is to *not* burden users with more bits to download AND avoid QE having to test/verify new binaries. Nick - if our build deletes our actual released bits and not allow using the previous bits then that is a problem. Did the check for publish fail to detect there was no change ? We have had and will have this situation for others than just "dormant" modules like birt and portlet so we should be able to handle this by now IMO. What is missing ? /max > > On 12/08/2014 12:54 PM, Nick Boldt wrote: >> TL;DR: Yes. >> >>> I did not create task JIRAs for Hibernate and Livereload, because >>> neither of those have commits in the 4.2.x branch since 4.2.0.Final >>> and >>> therefore need not have their root poms adjusted. >> >> On 12/08/2014 02:01 AM, Max Rydahl Andersen wrote: >>> >>>> On 08 Dec 2014, at 04:19, Nick Boldt wrote: >>>> >>>> his week is the "quiet period" in prep for 4.2.1.Final / 8.0.1.GA. >>>> >>>> You are required to update your root poms to point at the latest >>>> parent >>>> pom, >>> I assume you mean "If and only if the build your component is in has >>> changed since 4.2.0.Final", correct ? >>> >>> As otherwise we are going to have updates to *everything* which is >>> what we don't want for our maintanence builds. >>> >>> Just want to make sure the above is what you meant or to know if you >>> found something in our build that requires *every* component to >>> update parent Pom? >>> >>> > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From pleacu at redhat.com Tue Dec 9 10:15:36 2014 From: pleacu at redhat.com (Paul Leacu) Date: Tue, 9 Dec 2014 10:15:36 -0500 (EST) Subject: [jbosstools-dev] New JBTIS target platform available - JBTIS-TP-4.2.0.Beta2a In-Reply-To: <1001707053.18491093.1417721116013.JavaMail.zimbra@redhat.com> Message-ID: <1227317032.20056258.1418138136046.JavaMail.zimbra@redhat.com> Hey - An updated JBTIS TP is available - please note the version for your poms - 4.2.0.Beta2a https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.0.Beta2a/ http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Beta2a/ See Jira for details: https://issues.jboss.org/browse/JBTIS-367 [1] Update JBT core update site: 4.2.0.CR1 -> 4.2.0.Final [2] Use jbosstools-unified instead of jbosstools-multiple [3] Use luna 201406120900-RC4 Need to use version 4.4.0 of BIRT to align with JBT unified TP. [4] Update to latest bpmn2 modeler and bpel. [5] Remove graphiti 0.10.x dependency in favor of 0.11.x https://issues.jboss.org/browse/JBTIS-370 [1] BPEL source bundles The graphiti and BIRT issues have been discussed with the affected components. --paull From nboldt at redhat.com Tue Dec 9 10:25:19 2014 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 09 Dec 2014 10:25:19 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Prepare for 4.2.1.Final / 8.0.1.GA (release is next week Dec 15 2014) In-Reply-To: <54871406.60003@redhat.com> References: <54871406.60003@redhat.com> Message-ID: <5487145F.2060207@redhat.com> Max said: > Nick - if our build deletes our actual released bits and not allow using > the previous bits then that is a problem. We didn't "release" Birt and Portal. We only "released" JBT which contained those. We DID "release" the handful of components [1] that said they were not doing changes for 4.2.1 - Aerogear, Freemarker, Hibernate, Livereload, and Webservices . However, of those, only livereload and Hibernate remain unchanged, as well as parts of Central - everyone else has now contributed fixes into 4.2.1. So 60% of the effort to cache those 4.2.0.Final versions was wasted. [1] http://download.jboss.org/jbosstools/updates/stable/luna/core/ > Did the check for publish fail to detect there was no change ? Ah, but you see, the check is "has the source changed" not "has anything but one line in the root pom changed". Since the source changed, the /staging/ folder w/ the 4.2.0.Final bits was updated to include the new BIRT and Portal stuff. From your perspective, nothing changed. From github's perspective, there was a new SHA, and therefore the code needed to be rebuilt. > We have had and will have this situation for others than just "dormant" > modules like birt and portlet so we should be able to handle this by now > IMO. > What is missing ? 3 things: a) GA release process does normally include publishing all the components to their own folder under [1]. Because in the past, 99% of the components have changed during maintenance, so the effort to return (noise to signal) was too high. Even with this release, we tried to not build 5 of the 17 projects, and then ended up rebuilding 15 of them. b) changing the check in Jenkins jobs from "check Github for changes" to "check Github for changes that are different than just updating the root pom to point to a newer parent pom" c) educating people to the fact that they do NOT need to bump their root pom's reference to a newer parent pom IFF there are no OTHER changes in the repo since the previous .Final/GA release. Had Birt and Portal not been actually changed, (a) and (b) would have not been needed, as there would have been no fresh publish, and I could have just pulled the old staging bits into [1] for safe keeping. -- So long story short, if it's really important that these two components NOT release new timestamped versions of the same bits (which were run w/ fresh tests using the updated target platform), then yes, I can rebuild using [2] as the input for their bits to the composite [3] and aggregates [4]. However I don't like doing that because it will also include lots more than we want -- duplicate versions of other projects' bits, which are probably safe, but we've never done that before so I'm hesitant to start now. [2] http://download.jboss.org/jbosstools/updates/stable/luna/ [3] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.luna/ [4] https://github.com/jbosstools/jbosstools-build/blob/jbosstools-4.2.x/parent/pom.xml#L73 and https://github.com/jbosstools/jbosstools-build/blob/jbosstools-4.2.x/parent/pom.xml#L79 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mmalina at redhat.com Tue Dec 9 11:18:19 2014 From: mmalina at redhat.com (Martin Malina) Date: Tue, 9 Dec 2014 17:18:19 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Prepare for 4.2.1.Final / 8.0.1.GA (release is next week Dec 15 2014) In-Reply-To: <61006C2C-02AB-45C0-9ED5-4F896A6E5133@redhat.com> References: <5485189A.3060601@redhat.com> <54860FF1.5000003@redhat.com> <54864E0E.2070900@exadel.com> <61006C2C-02AB-45C0-9ED5-4F896A6E5133@redhat.com> Message-ID: <72590B61-1083-45F0-AB2B-0ADED923D210@redhat.com> > On 9. 12. 2014, at 11:19, Max Rydahl Andersen wrote: > > On 9 Dec 2014, at 2:19, Alexey Kazakov wrote: > >> Thanks to all component leads who updated their root poms (and I >> updated the rest of components: forge, aerogear, central, freemarker). >> So all components that have been changed since 4.2.0 are using >> 4.2.1.Final-SNAPSHOT root pom now. >> However, two components, Birt and Portlet don't have any changes >> besides updated root poms. As I understand we should change the root >> pom versio ONLY if the component has been changed since 4.2.0.Final. >> I reopened the corresponding issues for Birt and Portlet for >> clarification: >> https://issues.jboss.org/browse/JBIDE-18890 >> https://issues.jboss.org/browse/JBIDE-18896 >> Should we ignore these changes and not to rebuild Birt & Portlet for >> 4.2.1? > > I would say so - we have the 4.2.0.Final updatesite to get these from so > sounds weird why we need to update these. > > The whole intent we are going for is to *not* burden users with more > bits to download AND avoid QE having to test/verify new binaries. The idea is nice, but I'm not sure this can actually ever work. The target platform was changed anyway (including common/foundation JBT plugins). So theoretically you can never be 100 % sure that JBT 4.2.1.Final will work with the older portlet. So you can never say that no testing is needed. I'm actually not sure how much difference it makes - if you know that there were no changes but the bits are newly built as opposed to using exactly the same bits - in both cases you need at least some smoke testing. But I agree from use perspective it's probably nicer if they need to update less bits. -Martin > Nick - if our build deletes our actual released bits and not allow using > the previous bits then that is a problem. > > Did the check for publish fail to detect there was no change ? > > We have had and will have this situation for others than just "dormant" > modules like birt and portlet so we should be able to handle this by now > IMO. > > What is missing ? > > /max > >> >> On 12/08/2014 12:54 PM, Nick Boldt wrote: >>> TL;DR: Yes. >>> >>>> I did not create task JIRAs for Hibernate and Livereload, because >>>> neither of those have commits in the 4.2.x branch since 4.2.0.Final >>>> and >>>> therefore need not have their root poms adjusted. >>> >>> On 12/08/2014 02:01 AM, Max Rydahl Andersen wrote: >>>> >>>>> On 08 Dec 2014, at 04:19, Nick Boldt wrote: >>>>> >>>>> his week is the "quiet period" in prep for 4.2.1.Final / 8.0.1.GA. >>>>> >>>>> You are required to update your root poms to point at the latest >>>>> parent >>>>> pom, >>>> I assume you mean "If and only if the build your component is in has >>>> changed since 4.2.0.Final", correct ? >>>> >>>> As otherwise we are going to have updates to *everything* which is >>>> what we don't want for our maintanence builds. >>>> >>>> Just want to make sure the above is what you meant or to know if you >>>> found something in our build that requires *every* component to >>>> update parent Pom? >>>> >>>> >> >> _______________________________________________ >> 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/20141209/e20f9d13/attachment-0001.html From manderse at redhat.com Tue Dec 9 16:20:19 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 09 Dec 2014 22:20:19 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Prepare for 4.2.1.Final / 8.0.1.GA (release is next week Dec 15 2014) In-Reply-To: <72590B61-1083-45F0-AB2B-0ADED923D210@redhat.com> References: <5485189A.3060601@redhat.com> <54860FF1.5000003@redhat.com> <54864E0E.2070900@exadel.com> <61006C2C-02AB-45C0-9ED5-4F896A6E5133@redhat.com> <72590B61-1083-45F0-AB2B-0ADED923D210@redhat.com> Message-ID: <6822B269-D7F9-4211-A36D-3D12797F5820@redhat.com> >> I would say so - we have the 4.2.0.Final updatesite to get these from >> so >> sounds weird why we need to update these. >> >> The whole intent we are going for is to *not* burden users with more >> bits to download AND avoid QE having to test/verify new binaries. > > The idea is nice, but I'm not sure this can actually ever work. The > target platform was changed anyway (including common/foundation JBT > plugins). So theoretically you can never be 100 % sure that JBT > 4.2.1.Final will work with the older portlet. > So you can never say that no testing is needed. I'm actually not sure > how much difference it makes - if you know that there were no changes > but the bits are newly built as opposed to using exactly the same bits > - in both cases you need at least some smoke testing. I'm not saying *no* testing, I'm saying no need to test *new* binaries. My insistence on making us capable of making the most minimal rebuild is not me expecting that from the first time we do this we can do less testing. It is me expecting that if we can get our builds *automatically* be minimal and not require massive rebuilds, updates of parent poms and lots of other churning and just make it a few mb's of updates for a few set of components then we are much better prepared to do faster and faster releases. If our build process continues to enforce/require full rebuilds of everything then we keep having this uncertainty about how much was actually affected in this release ? how much do we need to test ? If we know -in this release livereload and hibernate changed - nothing else; then we can limit our testing to anything reliant on those changes. > But I agree from use perspective it's probably nicer if they need to > update less bits. Yes, this too. /max From nboldt at redhat.com Tue Dec 9 16:55:52 2014 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 09 Dec 2014 16:55:52 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Prepare for 4.2.1.Final / 8.0.1.GA (release is next week Dec 15 2014) In-Reply-To: <54876FC7.10103@redhat.com> References: <54876FC7.10103@redhat.com> Message-ID: <54876FE8.80100@redhat.com> > If our build process continues to enforce/require full rebuilds of > everything then we keep having this uncertainty about how much was > actually affected in this release ? how much do we need to test ? Today our requirements for tracking which projects feed the aggregates are *three tiny pieces* of information: a) build with the MINIMUM target platform b) test with the MAXIMUM target platform c) use the correct BUILD_ALIAS d) SPOILER ALERT, there's a 4th piece too - see below. All three of those *can be set in Jenkins* - in fact we set the first *two* already (we only set BUILD_ALIAS for JBDS to force it to be GA instead of Final). Then we would only need to *encourage* people to use the latest parent pom for local testing, and not actually need it for running builds. But IMHO the Task JIRAs force people to run local tests, and gentle encouragement will lead to things NOT getting done. -- If you'd like we can test this approach with the 8.1.0 builds in Feb/March. As long as BUILD_ALIAS & the max target target platform version (something like 4.42.0.*) are incremented in Jenkins (to move through Beta1/CR1/Final/GA), and all the projects w/ changes have properly upversioned their plugins/features where necessary, everyone can continue to use the 4.2.1.Final-SNAPSHOT version of the parent pom. Enforcing we all use the latest parent pom is a convention... but it isn't *strictly necessary* after we drop a x.y.0.Final (as long as Jenkins has the correct information needed). (It is required for 4.3.0.before-Final builds because the value of the *minimum* target platform IS changing every month or so, and we're adding variables to support migration of integration tests out of the unit test suites, etc. So for the ramp up to the 0.Final, we DO need everyone using the latest parent pom.) --- HOWEVER... there is a fourth reason to use the latest parent pom. Our parent pom defines the list of upstream sites used when building the individual projects (eg., Server depends on Base), which for 4.2.1.Final includes two unchanged project sites: Hibernate and LiveReload. https://github.com/jbosstools/jbosstools-build/blob/jbosstools-4.2.x/parent/pom.xml#L85-L86 For master branch, everything will be new, so we use all the staging (nightly) sites: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L65-L96 This list is also used when creating the composite site we use to determine that: * everything in the site can be co-installed (using headless p2.director installation test) * if there are changes to the contents of one or more project, the aggregate will be rebuilt to pick up those upstream changes, and we'll see failures as soon as possible* So again, this is important for x.y.0.before-Final builds, but not for x.y.z.maintenance builds (since those minor changes should be compatible. > If we know -in this release livereload and hibernate changed - nothing > else; then we can limit our testing to anything reliant on those > changes. Interesting example... you list the two projects out of 17 which in fact have no commits in github 4.2.x branch since 4.2.0.Final release. :D * - for example, recent refactorings in Server's AS Tools test plugins in master have caused webservices tests to fail due to a missing dependency. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Wed Dec 10 02:59:07 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Wed, 10 Dec 2014 02:59:07 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 23 issues with no component Message-ID: <201412100759.sBA7x7JW025065@int-mx09.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3285 https://issues.jboss.org/browse/JBDS-3285 Summary: Git: Easy Import Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 7:43:47.445410 ---------------------------- * No component for JBDS-3282 https://issues.jboss.org/browse/JBDS-3282 Summary: Screencasts: OpenShift v3 Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 8:05:37.445941 ---------------------------- * No component for JBDS-3283 https://issues.jboss.org/browse/JBDS-3283 Summary: Ionic graduate from Tech Preview Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 7:55:57.445772 ---------------------------- * No component for JBDS-3280 https://issues.jboss.org/browse/JBDS-3280 Summary: Screencasts: Java EE Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 8:26:42.446260 ---------------------------- * No component for JBDS-3281 https://issues.jboss.org/browse/JBDS-3281 Summary: Screencasts: Git Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 8:18:36.446102 ---------------------------- * No component for JBDS-3277 https://issues.jboss.org/browse/JBDS-3277 Summary: OpenShift v2 Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 8:42:50.446733 ---------------------------- * No component for JBDS-3276 https://issues.jboss.org/browse/JBDS-3276 Summary: JBDS-IS Installer Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 8:48:36.446902 ---------------------------- * No component for JBDS-3275 https://issues.jboss.org/browse/JBDS-3275 Summary: Add wildfly archetypes to JBoss Central Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 8:50:40.447061 ---------------------------- * No component for JBDS-3274 https://issues.jboss.org/browse/JBDS-3274 Summary: Marketplace Entry: Integration Stack (Fuse Focused) Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 8:57:22.447217 ---------------------------- * No component for JBDS-3273 https://issues.jboss.org/browse/JBDS-3273 Summary: JBoss Central: Automatic upstream quickstart integration Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 9:06:34.447370 ---------------------------- * No component for JBDS-3272 https://issues.jboss.org/browse/JBDS-3272 Summary: JBoss Central HTML Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 9:08:27.447524 ---------------------------- * No component for JBDS-3257 https://issues.jboss.org/browse/JBDS-3257 Summary: Basic FeedHenry Support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 16:02:16.449159 ---------------------------- * No component for JBDS-3270 https://issues.jboss.org/browse/JBDS-3270 Summary: Cordova App Icon Support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 9:22:04.448072 ---------------------------- * No component for JBDS-3259 https://issues.jboss.org/browse/JBDS-3259 Summary: Markdown Viewer Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 21:56:07.448854 ---------------------------- * No component for JBDS-3258 https://issues.jboss.org/browse/JBDS-3258 Summary: Docker Tooling (Advanced Integration) Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 14:06:36.449006 ---------------------------- * No component for JBDS-3279 https://issues.jboss.org/browse/JBDS-3279 Summary: Screencasts: Maven Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 8:27:43.446418 ---------------------------- * No component for JBDS-3278 https://issues.jboss.org/browse/JBDS-3278 Summary: OpenShift v3 Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 8:39:08.446576 ---------------------------- * No component for JBDS-3271 https://issues.jboss.org/browse/JBDS-3271 Summary: Cordova App Splash Screen Support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 9:20:54.447908 ---------------------------- * No component for JBDS-3256 https://issues.jboss.org/browse/JBDS-3256 Summary: Docker Tooling (Basic Integration) Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 14:06:46.449312 ---------------------------- * No component for JBDS-3268 https://issues.jboss.org/browse/JBDS-3268 Summary: New Cordova Project via JBDS with git push to FH Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 7:22:19.448386 ---------------------------- * No component for JBDS-3269 https://issues.jboss.org/browse/JBDS-3269 Summary: Build Farm Integration Level 1 Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 9:23:43.448230 ---------------------------- * No component for JBDS-3261 https://issues.jboss.org/browse/JBDS-3261 Summary: JSR-356: Websockets Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 14:07:22.448694 ---------------------------- * No component for JBDS-3267 https://issues.jboss.org/browse/JBDS-3267 Summary: JSON Editor Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 9:43:11.448541 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From nboldt at redhat.com Wed Dec 10 13:20:11 2014 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 10 Dec 2014 13:20:11 -0500 Subject: [jbosstools-dev] What are you using in p2 repositories produced by build/CI ? In-Reply-To: References: <5480968E.3040808@redhat.com> <54809904.5000400@redhat.com> <5481E6DF.90704@redhat.com> Message-ID: <54888EDB.8090408@redhat.com> > How are they used in aggregation ? For other things than just info to > add to the aggregation ? Not used in aggregation. Purely for archiving of information (knowing what went into the build w/o having to crack open 17 plugin jars). >>> The build logs are also mostly for investigative purposes and if these >>> were actually available within a build that would useful (removes need >>> to wait for jenkins to load) >> Hypothetical "would" isn't enough here. For investigation, I find it >> pretty acceptable and consistent with the possible failures to either >> look at Jenkins log directly or re-run the build locally. > Not everyone has access to Jenkins. And those who do have access sometimes find it HELLA slow. Therefore stashing a copy of the build log on dl.jb.org is IMHO still useful. > Rerunning builds isn't possible if the jobs actually changed since then. Editing for clarity, do you mean if the [job config has] actually changed since [the last run of the job] ? In that case you can look in the first few lines of the build log to see the exact syntax used to invoke maven and bash. >>> What is missing is actually being able to find and read this info. >> Can you please elaborate on an *actual* use-case which drives you to >> this assumption? > That these actually never are used and you have to know how to find them. At the risk of getting snarky, the logs folder has been in place for over 3 years, under every build folder created by Jenkins & our publish.sh script. If you still can't find it, you're using the wrong internet. http://download.jboss.org/jbosstools/builds/stable/3.2.2.Final/2011-11-14_23-06-23-H1430/logs/ >>> i.e. >>> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/md5sums.txt >>> doesn't actually list the zip name the md5sum relate to...also it looks >>> like the numbers are always the same which smells like a bug. >> I agree on the smell of a bug there. This might be a consequence of the file renaming we did for 4.2 (to support proper jboss.org conventions), or some other refactoring (eg., to use git SHAs from the Source-Ref in MANIFEST.MF files). Here's what it looks like for 4.1.2: http://download.jboss.org/jbosstools/builds/stable/4.1.2.Final.core/2014-03-18_15-46-19-B706/logs/md5sums.txt > What is the maintaence effort here ? Afaik it's copy of the files > generated in the build ? As proven by the fact that the md5sums.txt file no longer provides useful info, clearly there's a maintenance requirement - either we make sure it works, or it breaks. Or we stop producing it as it's no longer useful / needed. So it's not about copying files, it's about deciding WHAT files to generate. (Like every year when I ask if we still need to produce the hibernatetools update site, or if we can trash that and just tell people to use the Eclipse Marketplace instead. Every year I'm told the statistics say we need to keep it.) -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Thu Dec 11 03:43:32 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Thu, 11 Dec 2014 03:43:32 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 9 issues with no component Message-ID: <201412110843.sBB8hW3a010847@int-mx10.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3285 https://issues.jboss.org/browse/JBDS-3285 Summary: Git: Easy Import Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 15:50:14.607967 ---------------------------- * No component for JBDS-3280 https://issues.jboss.org/browse/JBDS-3280 Summary: Screencasts: Java EE Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 9:11:06.608332 ---------------------------- * No component for JBDS-3281 https://issues.jboss.org/browse/JBDS-3281 Summary: Screencasts: Git Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 9:03:00.608164 ---------------------------- * No component for JBDS-3261 https://issues.jboss.org/browse/JBDS-3261 Summary: JSR-356: Websockets Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 14:51:46.609304 ---------------------------- * No component for JBDS-3267 https://issues.jboss.org/browse/JBDS-3267 Summary: JSON Editor Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 22:31:12.609148 ---------------------------- * No component for JBDS-3274 https://issues.jboss.org/browse/JBDS-3274 Summary: Marketplace Entry: Integration Stack (Fuse Focused) Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 9:41:46.608820 ---------------------------- * No component for JBDS-3257 https://issues.jboss.org/browse/JBDS-3257 Summary: Basic FeedHenry Support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 16:46:40.609783 ---------------------------- * No component for JBDS-3259 https://issues.jboss.org/browse/JBDS-3259 Summary: Markdown Viewer Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 22:40:31.609466 ---------------------------- * No component for JBDS-3279 https://issues.jboss.org/browse/JBDS-3279 Summary: Screencasts: Maven Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 9:12:07.608493 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From mistria at redhat.com Thu Dec 11 12:01:44 2014 From: mistria at redhat.com (Mickael Istria) Date: Thu, 11 Dec 2014 18:01:44 +0100 Subject: [jbosstools-dev] Target Platform 4.41.1.Final for JBoss Tools 4.2.1.Final has been released. Message-ID: <5489CDF8.8070604@redhat.com> Target Platform 4.41.1.Final for JBoss Tools 4.2.1.Final has been released. Changes ======= * None, just release to include the "Final" label Usage ===== Target platform 4.41.1.Final is what JBoss Tools 4.2.1.Final will use. All Jenkins jobs for branch jbosstools-4.2.x and parent pom 4.2.1.Final-SNAPSHOT have been updated to use target platform 4.41.1.Final. The following p2 repositories *will be modified* to point to this new target platform once JBoss Tools 4.2.1.Final is released: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ * http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/luna/ Until then, you can access the target platform at the URLs below. Download ======== Update site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.41.1.Final/REPO/ Update site zip: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.41.1.Final/jbosstoolstarget-4.41.1.Final.zip Git tag: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.41.1.Final Testing/Development =================== If your root pom correctly specifies the latest parent pom version as 4.2.1.Final-SNAPSHOT, you need only this: $ mvn clean verify If you're using a different parent pom, use this: $ mvn clean verify -Dtpc.version=4.41.1.Final For advanced usage and help (using in IDE, building a mirror locally, using a zip), see: * https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.md -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141211/8a0990d0/attachment-0001.html From dgolovin at exadel.com Thu Dec 11 19:16:49 2014 From: dgolovin at exadel.com (Denis Golovin) Date: Thu, 11 Dec 2014 16:16:49 -0800 Subject: [jbosstools-dev] New component created in JIRA for Java EE 7 Batch Processing (JSR 352) Tooling Message-ID: <548A33F1.6090106@exadel.com> FYI: New component created in JBoss Tools JIRA Name: batch Description: Java EE 7 Batch Processing (JSR 352) Tooling https://issues.jboss.org/browse/JBIDE/component/12320844/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel Thanks Denis From manderse at redhat.com Fri Dec 12 02:59:18 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Fri, 12 Dec 2014 02:59:18 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 8 issues with no component Message-ID: <201412120759.sBC7xIpZ003279@int-mx10.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3280 https://issues.jboss.org/browse/JBDS-3280 Summary: Screencasts: Java EE Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 8:26:53.093329 ---------------------------- * No component for JBDS-3281 https://issues.jboss.org/browse/JBDS-3281 Summary: Screencasts: Git Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 8:18:47.093144 ---------------------------- * No component for JBDS-3261 https://issues.jboss.org/browse/JBDS-3261 Summary: JSR-356: Websockets Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 14:07:33.093988 ---------------------------- * No component for JBDS-3267 https://issues.jboss.org/browse/JBDS-3267 Summary: JSON Editor Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 21:46:59.093820 ---------------------------- * No component for JBDS-3274 https://issues.jboss.org/browse/JBDS-3274 Summary: Marketplace Entry: Integration Stack (Fuse Focused) Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 8:57:33.093659 ---------------------------- * No component for JBDS-3257 https://issues.jboss.org/browse/JBDS-3257 Summary: Basic FeedHenry Support 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:20:07.094467 ---------------------------- * No component for JBDS-3259 https://issues.jboss.org/browse/JBDS-3259 Summary: Markdown Viewer Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 21:56:18.094147 ---------------------------- * No component for JBDS-3279 https://issues.jboss.org/browse/JBDS-3279 Summary: Screencasts: Maven Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 8:27:54.093496 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From xcoulon at redhat.com Fri Dec 12 06:33:49 2014 From: xcoulon at redhat.com (Xavier Coulon) Date: Fri, 12 Dec 2014 12:33:49 +0100 Subject: [jbosstools-dev] Website updates Message-ID: Hello, I finally managed to fix the poor indentation on the code blocks -> \o/ I also added syntax coloring based on 'prettify' (https://code.google.com/p/google-code-prettify/ ), which has the benefit of colorizing the code like Eclipse does (more or less) -> \o/ \o/ You can see the result in action here -> http://tools.jboss.org/blog/2014-12-10-tip-1-foreach-template.html <- On a side note, I updated asciidoctor to version 1.5.2 (it's a bug fixes release), so you'll have to run 'bundle update' before building the site on your machine ;-) Happy browsing ! Best regards, /Xavier -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141212/f2e8cdd1/attachment.html From manderse at redhat.com Fri Dec 12 07:34:29 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 12 Dec 2014 13:34:29 +0100 Subject: [jbosstools-dev] Website updates In-Reply-To: References: Message-ID: <214CAFDD-9177-4A99-85E1-7AB42B1D76D9@redhat.com> very nice! looks great. > Hello, > > I finally managed to fix the poor indentation on the code blocks -> > \o/ > I also added syntax coloring based on 'prettify' > (https://code.google.com/p/google-code-prettify/ > ), which has the > benefit of colorizing the code like Eclipse does (more or less) -> \o/ > \o/ > You can see the result in action here -> > http://tools.jboss.org/blog/2014-12-10-tip-1-foreach-template.html > > <- > > On a side note, I updated asciidoctor to version 1.5.2 (it's a bug > fixes release), so you'll have to run 'bundle update' before building > the site on your machine ;-) > > Happy browsing ! > Best regards, > /Xavier > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From akazakov at exadel.com Fri Dec 12 13:41:15 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Fri, 12 Dec 2014 10:41:15 -0800 Subject: [jbosstools-dev] ACTION REQUIRED: Create New and Noteworthy for 4.2.1.Final In-Reply-To: <5487145F.2060207@redhat.com> References: <54871406.60003@redhat.com> <5487145F.2060207@redhat.com> Message-ID: <548B36CB.40505@exadel.com> Hi, Sorry for being late with this email but we need to create New and Noteworthy for JBT 4.2.1 release which is going to happen on Monday, December 15. Here is a JIRA with subtask for each component: https://issues.jboss.org/browse/JBIDE-18928 If JIRA is correct only CDI, VPE, Openshift and testing-tools ( Arquillian) have something for N&N this time: https://issues.jboss.org/issues/?jql=project%20in%20(JBIDE%2C%20JBDS)%20AND%20resolution%20%3D%20Done%20AND%20fixVersion%20in%20(4.2.1.CR1%2C%204.2.1.Final%2C%208.0.1.CR1%2C%208.0.1.GA)%20AND%20labels%20%3D%20new_and_noteworthy Please create a PR with N&N for you components ASAP or close the corresponding JIRA if nothing to document. Thank you! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141212/78677572/attachment.html From manderse at redhat.com Sat Dec 13 02:58:39 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Sat, 13 Dec 2014 02:58:39 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 6 issues with no component Message-ID: <201412130758.sBD7wdaq003195@int-mx09.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3261 https://issues.jboss.org/browse/JBDS-3261 Summary: JSR-356: Websockets Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 4 days, 14:06:53.135041 ---------------------------- * No component for JBDS-3267 https://issues.jboss.org/browse/JBDS-3267 Summary: JSON Editor Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 21:46:19.134869 ---------------------------- * No component for JBDS-3274 https://issues.jboss.org/browse/JBDS-3274 Summary: Marketplace Entry: Integration Stack (Fuse Focused) Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 8:56:53.134692 ---------------------------- * No component for JBDS-3257 https://issues.jboss.org/browse/JBDS-3257 Summary: Basic FeedHenry Support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 17:19:27.135694 ---------------------------- * No component for JBDS-3259 https://issues.jboss.org/browse/JBDS-3259 Summary: Markdown Viewer Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 21:55:38.135203 ---------------------------- * No component for JBDS-3279 https://issues.jboss.org/browse/JBDS-3279 Summary: Screencasts: Maven Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 8:27:14.134506 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From manderse at redhat.com Sun Dec 14 04:08:47 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Sun, 14 Dec 2014 04:08:47 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 6 issues with no component Message-ID: <201412140908.sBE98lNU014926@int-mx11.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3261 https://issues.jboss.org/browse/JBDS-3261 Summary: JSR-356: Websockets Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 5 days, 15:17:01.346015 ---------------------------- * No component for JBDS-3267 https://issues.jboss.org/browse/JBDS-3267 Summary: JSON Editor Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 22:56:27.345842 ---------------------------- * No component for JBDS-3274 https://issues.jboss.org/browse/JBDS-3274 Summary: Marketplace Entry: Integration Stack (Fuse Focused) Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 13:02:40.345667 ---------------------------- * No component for JBDS-3257 https://issues.jboss.org/browse/JBDS-3257 Summary: Basic FeedHenry Support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 2 days, 18:29:35.346670 ---------------------------- * No component for JBDS-3259 https://issues.jboss.org/browse/JBDS-3259 Summary: Markdown Viewer Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 4 days, 23:05:46.346178 ---------------------------- * No component for JBDS-3279 https://issues.jboss.org/browse/JBDS-3279 Summary: Screencasts: Maven Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 4 days, 9:37:22.345486 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From mmurray at redhat.com Sun Dec 14 18:34:27 2014 From: mmurray at redhat.com (Michelle Murray) Date: Sun, 14 Dec 2014 18:34:27 -0500 (EST) Subject: [jbosstools-dev] ACTION REQUIRED: Create New and Noteworthy for 4.2.1.Final In-Reply-To: <548B36CB.40505@exadel.com> References: <54871406.60003@redhat.com> <5487145F.2060207@redhat.com> <548B36CB.40505@exadel.com> Message-ID: <185864336.18515701.1418600067261.JavaMail.zimbra@redhat.com> I am very surprised to hear that there are N&N for 4.2.1. My understanding was that this is a bug fix release and should have no new features. I understand that sometimes bug fixes are worth announcing via N&N so sometimes there may be a need for N&N for a bug fix release. But how is the BrowserSim N&N related to a bug fix? Adding iPhone 6 and 6+ skins are not a bug fix. >From a JBDS release note perspective, late N&N are frustrating. Thanks, Michelle ----- Original Message ----- > From: "Alexey Kazakov" > To: jbosstools-dev at lists.jboss.org > Sent: Saturday, 13 December, 2014 4:41:15 AM > Subject: [jbosstools-dev] ACTION REQUIRED: Create New and Noteworthy for > 4.2.1.Final > Hi, > Sorry for being late with this email but we need to create New and Noteworthy > for JBT 4.2.1 release which is going to happen on Monday, December 15. > Here is a JIRA with subtask for each component: > https://issues.jboss.org/browse/JBIDE-18928 > If JIRA is correct only CDI, VPE, Openshift and testing-tools ( Arquillian) > have something for N&N this time: > https://issues.jboss.org/issues/?jql=project%20in%20(JBIDE%2C%20JBDS)%20AND%20resolution%20%3D%20Done%20AND%20fixVersion%20in%20(4.2.1.CR1%2C%204.2.1.Final%2C%208.0.1.CR1%2C%208.0.1.GA)%20AND%20labels%20%3D%20new_and_noteworthy > Please create a PR with N&N for you components ASAP or close the > corresponding JIRA if nothing to document. > 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/20141214/2ac0e203/attachment-0001.html From nboldt at redhat.com Mon Dec 15 00:08:17 2014 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 15 Dec 2014 00:08:17 -0500 Subject: [jbosstools-dev] JBoss Tools Core 4.2.1.Final bits available for QE testing Message-ID: <548E6CC1.5090809@redhat.com> As always, these are not FINAL bits, but preliminary results for QE & community testing. Not for use by customers or end users. Update site: http://download.jboss.org/jbosstools/updates/staging/luna/ Target platforms: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Final * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.41.1.Final Until the above target platform site is released, you may need to add it to Eclipse to resolve dependencies at install time. Once released, dependencies will be found automatically from here: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ (latest release) * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.41.1.Final-SNAPSHOT/ (upcoming release) * http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.41.1.Final-SNAPSHOT/ (upcoming release) 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/updates/staging/luna/jbosstools-4.2.1.Final-updatesite-core/ * http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.Final-updatesite-coretests/ * http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.Final-updatesite-hibernatetools/ * http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.1.Final-updatesite-webtools/ and build sites: * http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.Final-build-core/ * http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.Final-build-coretests/ * http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.Final-build-hibernatetools/ * http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.Final-build-webtools/ -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Mon Dec 15 02:43:31 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 15 Dec 2014 08:43:31 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Create New and Noteworthy for 4.2.1.Final In-Reply-To: <185864336.18515701.1418600067261.JavaMail.zimbra@redhat.com> References: <54871406.60003@redhat.com> <5487145F.2060207@redhat.com> <548B36CB.40505@exadel.com> <185864336.18515701.1418600067261.JavaMail.zimbra@redhat.com> Message-ID: On 15 Dec 2014, at 0:34, Michelle Murray wrote: > I am very surprised to hear that there are N&N for 4.2.1. > > My understanding was that this is a bug fix release and should have no > new features. > I understand that sometimes bug fixes are worth announcing via N&N so > sometimes there may be a need for N&N for a bug fix release. > > But how is the BrowserSim N&N related to a bug fix? Adding iPhone 6 > and 6+ skins are not a bug fix. iPhone 6 is already out - its not right if we have to wait 6-12+ months before adding it, is it ? This is not something that requires a new feature to be developed, it is simply adding another resolution and images to an already existing list of dynamic configurations we have. >> From a JBDS release note perspective, late N&N are frustrating. I agree it was done late - we need to fix that, but all of the jiras should already be there. Approved and reviewed by QE and dev. Full disclosure: I did explicitly encourage the iphone6 skin to be added since others also thought it was not a bugfix. If it had required new feature development and broken API's or in some way risked a breakage somewhere I would have agreed; since it is just adding an additional default configuration which users could manually configure anyway (tediously) I'm okey with doing it this way. /max > Thanks, > Michelle > > ----- Original Message ----- > >> From: "Alexey Kazakov" >> To: jbosstools-dev at lists.jboss.org >> Sent: Saturday, 13 December, 2014 4:41:15 AM >> Subject: [jbosstools-dev] ACTION REQUIRED: Create New and Noteworthy >> for >> 4.2.1.Final > >> Hi, > >> Sorry for being late with this email but we need to create New and >> Noteworthy >> for JBT 4.2.1 release which is going to happen on Monday, December >> 15. >> Here is a JIRA with subtask for each component: >> https://issues.jboss.org/browse/JBIDE-18928 > >> If JIRA is correct only CDI, VPE, Openshift and testing-tools ( >> Arquillian) >> have something for N&N this time: >> https://issues.jboss.org/issues/?jql=project%20in%20(JBIDE%2C%20JBDS)%20AND%20resolution%20%3D%20Done%20AND%20fixVersion%20in%20(4.2.1.CR1%2C%204.2.1.Final%2C%208.0.1.CR1%2C%208.0.1.GA)%20AND%20labels%20%3D%20new_and_noteworthy > >> Please create a PR with N&N for you components ASAP or close the >> corresponding JIRA if nothing to document. > >> Thank you! > >> _______________________________________________ >> 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 Mon Dec 15 02:58:49 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Mon, 15 Dec 2014 02:58:49 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 5 issues with no component Message-ID: <201412150758.sBF7wngr007008@int-mx11.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3259 https://issues.jboss.org/browse/JBDS-3259 Summary: Markdown Viewer Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 5 days, 21:55:49.070066 ---------------------------- * No component for JBDS-3261 https://issues.jboss.org/browse/JBDS-3261 Summary: JSR-356: Websockets Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 6 days, 14:07:04.069903 ---------------------------- * No component for JBDS-3257 https://issues.jboss.org/browse/JBDS-3257 Summary: Basic FeedHenry Support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 3 days, 9:45:47.070387 ---------------------------- * No component for JBDS-3279 https://issues.jboss.org/browse/JBDS-3279 Summary: Screencasts: Maven Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 5 days, 8:27:25.069547 ---------------------------- * No component for JBDS-3267 https://issues.jboss.org/browse/JBDS-3267 Summary: JSON Editor Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 4 days, 21:46:30.069736 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From akazakov at exadel.com Mon Dec 15 13:52:31 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Mon, 15 Dec 2014 10:52:31 -0800 Subject: [jbosstools-dev] ACTION REQUIRED: Create New and Noteworthy for 4.2.1.Final In-Reply-To: <185864336.18515701.1418600067261.JavaMail.zimbra@redhat.com> References: <54871406.60003@redhat.com> <5487145F.2060207@redhat.com> <548B36CB.40505@exadel.com> <185864336.18515701.1418600067261.JavaMail.zimbra@redhat.com> Message-ID: <548F2DEF.3050805@exadel.com> Michelle, As Max has already said we may include small features/enchantments which easy to implement and which are safe enough in maintenance releases. All these changes are approved by developers and QE before they going to JBT/JBDS. But it seems to not be enough from a documentation perspective. What can we do to help you here? On 12/14/2014 03:34 PM, Michelle Murray wrote: > I am very surprised to hear that there are N&N for 4.2.1. > > My understanding was that this is a bug fix release and should have no > new features. > I understand that sometimes bug fixes are worth announcing via N&N so > sometimes there may be a need for N&N for a bug fix release. > > But how is the BrowserSim N&N related to a bug fix? Adding iPhone 6 > and 6+ skins are not a bug fix. > > From a JBDS release note perspective, late N&N are frustrating. > > Thanks, > Michelle > > ------------------------------------------------------------------------ > > *From: *"Alexey Kazakov" > *To: *jbosstools-dev at lists.jboss.org > *Sent: *Saturday, 13 December, 2014 4:41:15 AM > *Subject: *[jbosstools-dev] ACTION REQUIRED: Create New and > Noteworthy for 4.2.1.Final > > > Hi, > > Sorry for being late with this email but we need to create New and > Noteworthy for JBT 4.2.1 release which is going to happen on > Monday, December 15. > Here is a JIRA with subtask for each component: > https://issues.jboss.org/browse/JBIDE-18928 > > If JIRA is correct only CDI, VPE, Openshift and testing-tools ( > Arquillian) have something for N&N this time: > https://issues.jboss.org/issues/?jql=project%20in%20(JBIDE%2C%20JBDS)%20AND%20resolution%20%3D%20Done%20AND%20fixVersion%20in%20(4.2.1.CR1%2C%204.2.1.Final%2C%208.0.1.CR1%2C%208.0.1.GA)%20AND%20labels%20%3D%20new_and_noteworthy > > Please create a PR with N&N for you components ASAP or close the > corresponding JIRA if nothing to document. > > 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/20141215/4fa5867d/attachment.html From mmurray at redhat.com Mon Dec 15 17:38:44 2014 From: mmurray at redhat.com (Michelle Murray) Date: Mon, 15 Dec 2014 17:38:44 -0500 (EST) Subject: [jbosstools-dev] ACTION REQUIRED: Create New and Noteworthy for 4.2.1.Final In-Reply-To: <548F2DEF.3050805@exadel.com> References: <54871406.60003@redhat.com> <5487145F.2060207@redhat.com> <548B36CB.40505@exadel.com> <185864336.18515701.1418600067261.JavaMail.zimbra@redhat.com> <548F2DEF.3050805@exadel.com> Message-ID: <1026036673.777799.1418683124521.JavaMail.zimbra@redhat.com> I was just surprised. It had continually been said that this was a bug fix release. I didn't check the jiras myself because it was touted as just a bug fix release so was surprised when these few small new features were announced. Agreed that iPhone skins should be included asap. I've nothing against new features being included, I just wasn't aware of them for this release, that's all. RNs have been updated to include info on the new features and are ready for the release. Thanks, Michelle ----- Original Message ----- > From: "Alexey Kazakov" > To: "Michelle Murray" > Cc: jbosstools-dev at lists.jboss.org > Sent: Tuesday, 16 December, 2014 4:52:31 AM > Subject: Re: [jbosstools-dev] ACTION REQUIRED: Create New and Noteworthy for > 4.2.1.Final > Michelle, > As Max has already said we may include small features/enchantments which easy > to implement and which are safe enough in maintenance releases. > All these changes are approved by developers and QE before they going to > JBT/JBDS. > But it seems to not be enough from a documentation perspective. > What can we do to help you here? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141215/9c7ea2fc/attachment.html From nboldt at redhat.com Mon Dec 15 18:06:43 2014 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 15 Dec 2014 18:06:43 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.1.Final ] Message-ID: <548F6983.10402@redhat.com> Component leads, please tag your repositories! $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called jbosstools, also often called origin $ git checkout FETCH_HEAD $ git tag jbosstools-4.2.1.Final $ git push jbosstools jbosstools-4.2.1.Final -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From akazakov at exadel.com Mon Dec 15 20:13:41 2014 From: akazakov at exadel.com (Alexey Kazakov) Date: Mon, 15 Dec 2014 17:13:41 -0800 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.1.Final ] In-Reply-To: <548F6983.10402@redhat.com> References: <548F6983.10402@redhat.com> Message-ID: <548F8745.1070701@exadel.com> I would like to add that as soon as you tag your repo the jbosstools-4.2.x branch is open for 4.2.2 development! Done for base, jst, javaee. On 12/15/2014 03:06 PM, Nick Boldt wrote: > Component leads, please tag your repositories! > > $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called > jbosstools, also often called origin > $ git checkout FETCH_HEAD > $ git tag jbosstools-4.2.1.Final > $ git push jbosstools jbosstools-4.2.1.Final > From nboldt at redhat.com Mon Dec 15 20:19:54 2014 From: nboldt at redhat.com (Nick Boldt) Date: Mon, 15 Dec 2014 20:19:54 -0500 Subject: [jbosstools-dev] JBoss Developer Studio 8.0.1.GA is available Message-ID: <548F88BA.5080602@redhat.com> JBoss Developer Studio 8.0.1.GA is available! This is an update site only release - no new installers. Update site: https://devstudio.jboss.com/updates/8.0/ Eclipse Marketplace: https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-luna -- Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBDS#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Tue Dec 16 02:59:17 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Tue, 16 Dec 2014 02:59:17 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 4 issues with no component Message-ID: <201412160759.sBG7xH56030655@int-mx10.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3259 https://issues.jboss.org/browse/JBDS-3259 Summary: Markdown Viewer Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 6 days, 21:56:17.094623 ---------------------------- * No component for JBDS-3261 https://issues.jboss.org/browse/JBDS-3261 Summary: JSR-356: Websockets Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 7 days, 14:07:32.094449 ---------------------------- * No component for JBDS-3257 https://issues.jboss.org/browse/JBDS-3257 Summary: Basic FeedHenry Support Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 4 days, 9:46:15.094957 ---------------------------- * No component for JBDS-3279 https://issues.jboss.org/browse/JBDS-3279 Summary: Screencasts: Maven Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 6 days, 8:27:53.094094 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From xcoulon at redhat.com Tue Dec 16 04:38:08 2014 From: xcoulon at redhat.com (Xavier Coulon) Date: Tue, 16 Dec 2014 10:38:08 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.1.Final ] In-Reply-To: <548F8745.1070701@exadel.com> References: <548F6983.10402@redhat.com> <548F8745.1070701@exadel.com> Message-ID: <84E8DA73-DB23-48E1-B154-FB7989C3EC3C@redhat.com> Done for Webservices and LiveReload Best regards, /Xavier > On 16 Dec 2014, at 02:13, Alexey Kazakov wrote: > > > I would like to add that as soon as you tag your repo the > jbosstools-4.2.x branch is open for 4.2.2 development! > Done for base, jst, javaee. > > > On 12/15/2014 03:06 PM, Nick Boldt wrote: >> Component leads, please tag your repositories! >> >> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called >> jbosstools, also often called origin >> $ git checkout FETCH_HEAD >> $ git tag jbosstools-4.2.1.Final >> $ git push jbosstools jbosstools-4.2.1.Final >> > > _______________________________________________ > 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/20141216/aa9cef79/attachment.html From snjeza.peco at gmail.com Tue Dec 16 05:35:16 2014 From: snjeza.peco at gmail.com (Snjezana Peco) Date: Tue, 16 Dec 2014 11:35:16 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.1.Final ] In-Reply-To: <548F6983.10402@redhat.com> References: <548F6983.10402@redhat.com> Message-ID: <54900AE4.90004@gmail.com> Done for arquillian, birt and portlet. Snjeza On 12/16/2014 12:06 AM, Nick Boldt wrote: > Component leads, please tag your repositories! > > $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called > jbosstools, also often called origin > $ git checkout FETCH_HEAD > $ git tag jbosstools-4.2.1.Final > $ git push jbosstools jbosstools-4.2.1.Final > From ggastald at redhat.com Tue Dec 16 08:21:08 2014 From: ggastald at redhat.com (George Gastaldi) Date: Tue, 16 Dec 2014 11:21:08 -0200 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.1.Final ] In-Reply-To: <548F6983.10402@redhat.com> References: <548F6983.10402@redhat.com> Message-ID: <549031C4.20307@redhat.com> Done for jbosstools-forge On 12/15/2014 09:06 PM, Nick Boldt wrote: > Component leads, please tag your repositories! > > $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called > jbosstools, also often called origin > $ git checkout FETCH_HEAD > $ git tag jbosstools-4.2.1.Final > $ git push jbosstools jbosstools-4.2.1.Final > From kmarmaliykov at exadel.com Tue Dec 16 08:24:00 2014 From: kmarmaliykov at exadel.com (Konstantin Marmalyukov) Date: Tue, 16 Dec 2014 16:24:00 +0300 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.1.Final ] In-Reply-To: <548F6983.10402@redhat.com> References: <548F6983.10402@redhat.com> Message-ID: <54903270.6090901@exadel.com> VPE and Browsersim done. On 12/16/2014 2:06 AM, Nick Boldt wrote: > Component leads, please tag your repositories! > > $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called > jbosstools, also often called origin > $ git checkout FETCH_HEAD > $ git tag jbosstools-4.2.1.Final > $ git push jbosstools jbosstools-4.2.1.Final > From mistria at redhat.com Tue Dec 16 12:09:13 2014 From: mistria at redhat.com (Mickael Istria) Date: Tue, 16 Dec 2014 18:09:13 +0100 Subject: [jbosstools-dev] JBoss Tools - Tycho plugins 0.22.0 released Message-ID: <54906739.5060401@redhat.com> Hi all, On popular demand ( https://github.com/jbosstools/jbosstools-maven-plugins/issues/26 ), I released a 0.22.0 of our custom mojos we use for JBoss Tools. This version is the one to use if your build uses Tycho 0.22.0 (you'll most likely get errors if you mix different versions of Tycho and JBoss Tools mojos). Artifacts are available with version 0.22.0 on JBoss Maven repository. Tag is https://github.com/jbosstools/jbosstools-maven-plugins/tree/0.22.0 master is now a 0.22.1-SNAPSHOT Enjoy. -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141216/ba5d1f15/attachment.html From fbricon at redhat.com Tue Dec 16 13:23:00 2014 From: fbricon at redhat.com (Fred Bricon) Date: Tue, 16 Dec 2014 13:23:00 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.1.Final ] In-Reply-To: <548F6983.10402@redhat.com> References: <548F6983.10402@redhat.com> Message-ID: <9DC78665-3F36-4545-9F8C-83DDC71A2D92@redhat.com> Central done > Le 15 d?c. 2014 ? 18:06, Nick Boldt a ?crit : > > git push jbosstools jbosstools-4.2.1.Final -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141216/770adfde/attachment.html From nboldt at redhat.com Tue Dec 16 13:45:21 2014 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 16 Dec 2014 13:45:21 -0500 Subject: [jbosstools-dev] JBoss Tools 4.2.1.Final is now available In-Reply-To: <548F69CE.10409@redhat.com> References: <548F69CE.10409@redhat.com> Message-ID: <54907DC1.6070301@redhat.com> This is a stable release aimed at Eclipse 4.4.1 Luna users. Eclipse Marketplace: https://marketplace.eclipse.org/content/jboss-tools-luna Update Site: http://download.jboss.org/jbosstools/updates/stable/luna/ Update Site Zips: http://sourceforge.net/projects/jboss/files/JBossTools/jbosstools4.2.x/ Installation instructions: http://tools.jboss.org/downloads/installation.html New + Noteworthy (subject to change): http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.1.Final.html Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Tue Dec 16 19:08:00 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 17 Dec 2014 01:08:00 +0100 Subject: [jbosstools-dev] edit and history button on website Message-ID: <3065BA09-506A-4785-A473-81080CF8C0FC@redhat.com> Hey, I just realised we could easily get edit and history buttons on the website for blog, event, feature, and a few other pages. so i did that ;) Here is how it works: http://screencast.com/t/3ioKKdoLcVjv if you dont have push rights the edits becomes PR's if you do have push rights you'll need to create PR manually, but at least you can get to the file really fast and do minor fixes ;) for Xavier - got somequestions over at https://issues.jboss.org/browse/JBIDE-17085 about it once you have time. /max http://about.me/maxandersen From manderse at redhat.com Wed Dec 17 02:58:34 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Wed, 17 Dec 2014 02:58:34 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201412170758.sBH7wYsX012572@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 JBDS-3293 https://issues.jboss.org/browse/JBDS-3293 Summary: Marketplace Entry: Integration Stack (Fuse Focused) Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 17:12:06.356084 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From pleacu at redhat.com Mon Dec 22 12:08:19 2014 From: pleacu at redhat.com (Paul Leacu) Date: Mon, 22 Dec 2014 12:08:19 -0500 (EST) Subject: [jbosstools-dev] New JBTIS target platform available - JBTIS-TP-4.2.0.Beta2b In-Reply-To: <1695245162.490894.1419267464353.JavaMail.zimbra@redhat.com> Message-ID: <1435358415.495850.1419268099882.JavaMail.zimbra@redhat.com> Greetings - An updated JBTIS TP is available - 4.2.0.Beta2b: https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.0.Beta2b/ http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Beta2b/ See Jira for details: https://issues.jboss.org/browse/JBTIS-377 1. Update BPMN2 Modeler to pick up fix for IS Beta2 blocker https://issues.jboss.org/browse/SWITCHYARD-2484 http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1.1.1.201412181844_0.7.0.201308220617_luna/ --paull From manderse at redhat.com Tue Dec 23 02:59:50 2014 From: manderse at redhat.com (manderse at redhat.com) Date: Tue, 23 Dec 2014 02:59:50 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201412230759.sBN7xo6V030790@int-mx10.intmail.prod.int.phx2.redhat.com> This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBIDE-18983 https://issues.jboss.org/browse/JBIDE-18983 Summary: Project cannot be built. Possible open file handle Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 15:31:07.912247 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=project+in+%28JBIDE%2CJBDS%29+AND+component+is+EMPTY+AND+resolution+is+EMPTY From noreply at dsa-avl.com Mon Dec 29 15:23:31 2014 From: noreply at dsa-avl.com (Dr Cure) Date: Mon, 29 Dec 2014 16:23:31 -0400 Subject: [jbosstools-dev] Your Best Sex--Ever Message-ID: Marsha marks, and drain and hindus. Recording would meet what, for blakes injuries that callahan. Alot they alsogive references to pupae they. Engrave our activities box lavallette, nj 08735 pesky johnny parsons. Sure threshold crossing signs of proclaimed. All, setting with ofbartlesville, 901 f should then. Erythrocytes in track on thatluncheon Colonel would take shape i-have. Architectural sculptor i-also think cinco de moresenvisioned creating. Reparations forced on shemya in 50,000 objects. Memory, he attended the clean. Unclog any different metal of feminism suddenly. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141229/7683e241/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 31116 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141229/7683e241/attachment-0001.jpe