From jmaury at redhat.com Tue Aug 2 05:44:24 2016 From: jmaury at redhat.com (Jean-Francois Maury) Date: Tue, 2 Aug 2016 11:44:24 +0200 Subject: [jbosstools-dev] JBoss Tools 4.4.1.AM2 is now available Message-ID: This is a development release aimed at Eclipse 4.6.0 Neon.0 users. Announcement Blog: http://tools.jboss.org/blog/ Eclipse Marketplace: https://marketplace.eclipse.org/content/jboss-tools Update Site: http://download.jboss.org/jbosstools/neon/development/updates/ Zips: http://tools.jboss.org/downloads/jbosstools/neon/4.4.1.AM2.html#zips Installation instructions: http://tools.jboss.org/downloads/installation.html New + Noteworthy (subject to change): http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.1.AM2.html Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160802/aa968921/attachment.html From mmalina at redhat.com Tue Aug 2 08:06:35 2016 From: mmalina at redhat.com (Martin Malina) Date: Tue, 2 Aug 2016 14:06:35 +0200 Subject: [jbosstools-dev] [aeri] Now supports github logins In-Reply-To: References:

<6E12081D-8954-4FB4-B6C1-7634EA97977C@codetrails.com>

<39987F4E-70AC-4556-BBDD-F666BFE619F4@codetrails.com> Message-ID: <9A252B38-6650-4D5E-91C0-39A5E81F1C3F@redhat.com> > On 30. 7. 2016, at 2:30, Alexey Kazakov wrote: > > I think we should grant reviewer access to all members of jbosstools org. For example QE may not have push access in github but we still want them be able to create issues based on aeri reports. I agree :) So can you make it happen please, Marcel? Thanks, Martin > Regarding links in jira... Ideally the same link should work for everyone with optional GitHub authentication. If you do not login or you are not a jbosstools org member you see a public version of the report. Otherwise you see what you are supposed to see corresponding to your role. > If it requires significant efforts to implement then can we post a few links for different roles with clear descriptions as a workaround? > > WDYT? > > > On Jul 28, 2016, at 6:32 AM, Marcel Bruch > wrote: > >> >>> On 28 Jul 2016, at 15:00, Martin Malina > wrote: >>> In my opinion, it would make sense to just give the reporter role to the whole jbosstools team on github. >> >> Just a minor correction: >> >> We use different URL prefixes for reviewers and reporters. If a ?reporter" accesses a ?reviewer" url, he/she gets an "access denied?. That?s what you got when clicking on a JIRA link. >> >> The different url prefixes were required in previous versions of AERI. We could, however, change the current system to use only one url and so that *all* reporters get a public/anonymized view of a problem. Please note the word anonymized. Problems may contain senstive information like email addresses, error messages etc. We thus cannot make them public available to everyone as-is. >> >> However, at Eclipse we agreed on showing a anonymized view might be perfectly okay. So we could do the same here. >> >> Max, Alexey, Fred, >> what do you think? >> >> >> >> >> >> _______________________________________________ >> 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/20160802/3b557164/attachment.html From manderse at redhat.com Tue Aug 2 09:28:28 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Tue, 02 Aug 2016 15:28:28 +0200 Subject: [jbosstools-dev] [aeri] Now supports github logins In-Reply-To: <9A252B38-6650-4D5E-91C0-39A5E81F1C3F@redhat.com> References:

<6E12081D-8954-4FB4-B6C1-7634EA97977C@codetrails.com>

<39987F4E-70AC-4556-BBDD-F666BFE619F4@codetrails.com> <9A252B38-6650-4D5E-91C0-39A5E81F1C3F@redhat.com> Message-ID: <10FE43BF-C66A-4F86-B670-90CCB7496991@redhat.com> On 2 Aug 2016, at 14:06, Martin Malina wrote: > > On 30. 7. 2016, at 2:30, Alexey Kazakov wrote: >> >> I think we should grant reviewer access to all members of jbosstools >> org. For example QE may not have push access in github but we still >> want them be able to create issues based on aeri reports. > > I agree :) So can you make it happen please, Marcel? +1 As long as the possible private sensitive data are not publically available and we know who have access and we can add/remove people we should be fine. And by we I mean JBoss Tools and Developer Studio development team. /max > > Thanks, > Martin > >> Regarding links in jira... Ideally the same link should work for >> everyone with optional GitHub authentication. If you do not login or >> you are not a jbosstools org member you see a public version of the >> report. Otherwise you see what you are supposed to see corresponding >> to your role. >> If it requires significant efforts to implement then can we post a >> few links for different roles with clear descriptions as a >> workaround? >> >> WDYT? >> >> >> On Jul 28, 2016, at 6:32 AM, Marcel Bruch >> > >> wrote: >> >>> >>>> On 28 Jul 2016, at 15:00, Martin Malina >>> > wrote: >>>> In my opinion, it would make sense to just give the reporter role >>>> to the whole jbosstools team on github. >>> >>> Just a minor correction: >>> >>> We use different URL prefixes for reviewers and reporters. If a >>> ?reporter" accesses a ?reviewer" url, he/she gets an "access >>> denied?. That?s what you got when clicking on a JIRA link. >>> >>> The different url prefixes were required in previous versions of >>> AERI. We could, however, change the current system to use only one >>> url and so that *all* reporters get a public/anonymized view of a >>> problem. Please note the word anonymized. Problems may contain >>> senstive information like email addresses, error messages etc. We >>> thus cannot make them public available to everyone as-is. >>> >>> However, at Eclipse we agreed on showing a anonymized view might be >>> perfectly okay. So we could do the same here. >>> >>> Max, Alexey, Fred, >>> what do you think? >>> >>> >>> >>> >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen From nboldt at redhat.com Tue Aug 2 15:45:31 2016 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 2 Aug 2016 15:45:31 -0400 Subject: [jbosstools-dev] How do you set the default branch on a github repo? Message-ID: Does anyone have permissions to set the default branch in https://github.com/jbosstools/jbosstools-build-ci to jbosstools-4.4.x instead of 4.3.x? Similarly, can we set the default branch in https://github.com/jbosstools/jbosstools-target-platforms to 4.60.x instead of master? Could I be granted access to make these changes myself? Thanks, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From alkazako at redhat.com Tue Aug 2 23:29:36 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Tue, 2 Aug 2016 20:29:36 -0700 Subject: [jbosstools-dev] How do you set the default branch on a github repo? In-Reply-To: References: Message-ID: <57A16520.80008@redhat.com> I see these repos already have the default branches set as Nick requested. Probably someone has already changed it? On 08/02/2016 12:45 PM, Nick Boldt wrote: > Does anyone have permissions to set the default branch in > https://github.com/jbosstools/jbosstools-build-ci to jbosstools-4.4.x > instead of 4.3.x? > > Similarly, can we set the default branch in > https://github.com/jbosstools/jbosstools-target-platforms to 4.60.x > instead of master? > > Could I be granted access to make these changes myself? > > Thanks, > From marcel.bruch at codetrails.com Wed Aug 3 03:38:26 2016 From: marcel.bruch at codetrails.com (Marcel Bruch) Date: Wed, 3 Aug 2016 09:38:26 +0200 Subject: [jbosstools-dev] [aeri] Now supports github logins In-Reply-To: <10FE43BF-C66A-4F86-B670-90CCB7496991@redhat.com> References:

<6E12081D-8954-4FB4-B6C1-7634EA97977C@codetrails.com>

<39987F4E-70AC-4556-BBDD-F666BFE619F4@codetrails.com> <9A252B38-6650-4D5E-91C0-39A5E81F1C3F@redhat.com> <10FE43BF-C66A-4F86-B670-90CCB7496991@redhat.com> Message-ID: <3316F108-7DD3-44A6-87E8-4561F370C1FA@codetrails.com> > On 02 Aug 2016, at 15:28, Max Rydahl Andersen wrote: > > On 2 Aug 2016, at 14:06, Martin Malina wrote: > >>> On 30. 7. 2016, at 2:30, Alexey Kazakov wrote: >>> >>> I think we should grant reviewer access to all members of jbosstools >>> org. >> I agree :) So can you make it happen please, Marcel? > > +1 I cleared the teams. Now authorization is checked against organization membership only, not team membership. QE should have full access after logging in with GitHub (w/o log in you still get access denied). Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160803/fba0135d/attachment-0001.html From mmalina at redhat.com Wed Aug 3 05:23:40 2016 From: mmalina at redhat.com (Martin Malina) Date: Wed, 3 Aug 2016 11:23:40 +0200 Subject: [jbosstools-dev] [aeri] Now supports github logins In-Reply-To: <3316F108-7DD3-44A6-87E8-4561F370C1FA@codetrails.com> References:

<6E12081D-8954-4FB4-B6C1-7634EA97977C@codetrails.com>

<39987F4E-70AC-4556-BBDD-F666BFE619F4@codetrails.com> <9A252B38-6650-4D5E-91C0-39A5E81F1C3F@redhat.com> <10FE43BF-C66A-4F86-B670-90CCB7496991@redhat.com> <3316F108-7DD3-44A6-87E8-4561F370C1FA@codetrails.com> <01FAB676-95F2-4F87-8419-ADD2E18B60AB@redhat.com> <8983C589-2030-4B0E-B238-07D3EBD328F8@codetrails.com> Message-ID: <70E83865-8C4C-45DF-A9D3-90D444E5E832@redhat.com> > On 3. 8. 2016, at 13:06, Marcel Bruch wrote: > >> >> On 03 Aug 2016, at 11:23, Martin Malina > wrote: >> >>> >>> On 3. 8. 2016, at 9:38, Marcel Bruch > wrote: >>> >>> >>>> On 02 Aug 2016, at 15:28, Max Rydahl Andersen > wrote: >>>> >>>> On 2 Aug 2016, at 14:06, Martin Malina wrote: >>>> >>>>>> On 30. 7. 2016, at 2:30, Alexey Kazakov > wrote: >>>>>> >>>>>> I think we should grant reviewer access to all members of jbosstools >>>>>> org. >>>>> I agree :) So can you make it happen please, Marcel? >>>> >>>> +1 >>> >>> I cleared the teams. Now authorization is checked against organization membership only, not team membership. QE should have full access after logging in with GitHub (w/o log in you still get access denied). >> >> It still doesn't work for me. > > My excuse. It?s an oversight on my end. > The system placed you in the ?local database? authorization group after your first login b/c the JBoss Teams did not return any match for your username. I set all *@redhat.com users back to GitHub authorization. You should be able to log in as reviewer now. Yes, it works now! Thanks! -Martin > Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160803/edff102b/attachment.html From nboldt at redhat.com Wed Aug 3 16:22:01 2016 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 3 Aug 2016 16:22:01 -0400 Subject: [jbosstools-dev] FYI: Recent changes to parent pom & target platform for AM3 Message-ID: == Parent pom changes 1. https://issues.jboss.org/browse/JBIDE-22446 - Release process should disallow inclusion of snapshots artifacts If your build is now failing due to a maven enforcer plugin violation, it's because of the above issue. I've found two projects so far which are using SNAPSHOT dependencies: JST depends on snapshot version of the Early Access site, and the openshift.client plugin depends on openshift-restclient-java.version = 5.0.0-SNAPSHOT. 2. Parent pom is now using BUILD_ALIAS = AM3 in master branch. == Target platform change 3. https://issues.jboss.org/browse/JBIDE-22857 - Integration tests: include Red Deer UI feature in target platform I've added the single reddeer.ui.feature to the target platform and it's rebuilding now. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Thu Aug 4 22:20:34 2016 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 4 Aug 2016 22:20:34 -0400 Subject: [jbosstools-dev] FYI: Recent changes to parent pom & target platform for AM3 In-Reply-To: References: Message-ID: Another change has been requested: https://issues.jboss.org/browse/JBIDE-22877 - Update RedDeer to newer snapshot version 1.1.0.20160804. PR is being built now: https://github.com/jbosstools/jbosstools-target-platforms/pull/230 On Wed, Aug 3, 2016 at 4:22 PM, Nick Boldt wrote: > == Parent pom changes > > 1. https://issues.jboss.org/browse/JBIDE-22446 - Release process > should disallow inclusion of snapshots artifacts > > If your build is now failing due to a maven enforcer plugin violation, > it's because of the above issue. > > I've found two projects so far which are using SNAPSHOT dependencies: > JST depends on snapshot version of the Early Access site, and the > openshift.client plugin depends on openshift-restclient-java.version > = 5.0.0-SNAPSHOT. > > 2. Parent pom is now using BUILD_ALIAS = AM3 in master branch. > > == Target platform change > > 3. https://issues.jboss.org/browse/JBIDE-22857 - Integration tests: > include Red Deer UI feature in target platform > > I've added the single reddeer.ui.feature to the target platform and > it's rebuilding now. > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From marcel.bruch at codetrails.com Fri Aug 5 04:45:40 2016 From: marcel.bruch at codetrails.com (Marcel Bruch) Date: Fri, 5 Aug 2016 10:45:40 +0200 Subject: [jbosstools-dev] [aeri] Introducing (Custom) Error Report Processors Message-ID: <72E05791-4CCD-411A-928C-04CCDD95CD29@codetrails.com> Dear jbosstools-dev, the next version of AERI will allow to run client-side analyses before an error report is send. For example, when a ClassNotFoundException is logged, AERI will run an analyzer that tries to parse the class name from the exception?s error message, search for all bundles that export that class (i.e., the containing package) and check which bundles and packages the failing bundle was wired to. The results of these analyses are added to the error report as "auxiliary information? automatically (requires user consent). Besides the classpath analyzer AERI will provide a few more "common processors? that allow users to add all system properties, all user preferences, all installed bundles, resolution status, and wiring information, all installed features + bundles with id, name, and version information, to an error report on demand. We may also take this a step further to allow users to attach screenshots or code snippets to an error report. The analyzers will be added to the review dialog as outlined below and can be de/activated in one click. Reviewers can also demand auxiliary information which will then be automatically added to the report (after user consent): Every project will be able to register their own client-side analyses via an extension point. The exact details are not yet settled but I?d like to let you know early in the process to gather your requirements. If you have a requirement or feature request, please let me/us know in bug 496656 [1]. Thank you, Marcel [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=496656 -- Codetrails GmbH The knowledge transfer company Robert-Bosch-Str. 7, 64293 Darmstadt Phone: +49-6151-276-7092 Mobile: +49-179-131-7721 http://www.codetrails.com/ Managing Director: Dr. Marcel Bruch Handelsregister: Darmstadt HRB 91940 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160805/c3a21f3f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: client-side-analyzers.png Type: image/png Size: 92155 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160805/c3a21f3f/attachment-0001.png From marcel.bruch at codetrails.com Fri Aug 5 07:57:00 2016 From: marcel.bruch at codetrails.com (Marcel Bruch) Date: Fri, 5 Aug 2016 13:57:00 +0200 Subject: [jbosstools-dev] [aeri] Introducing Error Analyzers Message-ID: <0514A658-CC9A-4C14-85FB-06A768408BE2@codetrails.com> Dear jbosstools-dev, the next version of AERI will allow to run client-side analyses before an error report is send. For example, when a ClassNotFoundException is logged, AERI will run an analyzer that: tries to parse the class name from the exception?s error message, search for all bundles that export that class (i.e., the containing package) and check which bundles and packages the failing bundle was wired to. The results of these analyses are added automatically to the error report as "auxiliary information? (requires user consent). Besides the classpath analyzer we have a few more "common processors? in mind which allow users to easily add all system properties, all user preferences, all installed bundles, resolution status, and wiring information, all installed features + bundles with id, name, and version information, to an error report. We may also take this a step further to allow users to attach screenshots or code snippets to an error report. The analyzers will be added to the review dialog as outlined below and can be de/activated with one click. Reviewers can also demand auxiliary information by setting the appropriate needinfo flags on the problem: The exact API is not yet settled but I?d like to let you know early in the process to gather your requirements. In case you have a requirement or feature request, please let me/us know in bug 496656 [1]. Thank you, Marcel [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=496656 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160805/7c761487/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: client-side-analyzers.png Type: image/png Size: 92155 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160805/7c761487/attachment-0001.png From alkazako at redhat.com Fri Aug 5 11:54:59 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Fri, 5 Aug 2016 08:54:59 -0700 Subject: [jbosstools-dev] Testing JBoss Tools on Neon.1 Message-ID: Hi Len, As you know we are not going to migrate devstudio 10.1 to Neon.1. We will use Neon.0 as we did for devstudio 10.0. Neon.1 is planned to be released shortly after our release. And it would be great if we can test JBoss Tools plugins on Neon.1. Neon.1 final wont be available until after devstudio 10.1 / JBT 4.4.1 release but the first Neon.1 release candidates will be. So can you make sure you include in your test plan for Alpina release some testing against Neon.1 milestone/rc builds to minimize potential problems if users install our plugins on Neon.1 when it becomes available. Thank you. From ldimaggi at redhat.com Fri Aug 5 12:32:51 2016 From: ldimaggi at redhat.com (Leonard Dimaggio) Date: Fri, 5 Aug 2016 12:32:51 -0400 Subject: [jbosstools-dev] Testing JBoss Tools on Neon.1 In-Reply-To: References: Message-ID: Hi Alexey, That makes perfect sense. I've added it to the plan ( https://mojo.redhat.com/docs/DOC-1089818#jive_content_id_Eclipse_Test_Coverage ). I am out on PTO next week. Anyone on the QE team can fill you in on details along the way. Stay tuned, Len On Fri, Aug 5, 2016 at 11:54 AM, Alexey Kazakov wrote: > Hi Len, > > As you know we are not going to migrate devstudio 10.1 to Neon.1. We will > use Neon.0 as we did for devstudio 10.0. Neon.1 is planned to be released > shortly after our release. > And it would be great if we can test JBoss Tools plugins on Neon.1. Neon.1 > final wont be available until after devstudio 10.1 / JBT 4.4.1 release but > the first Neon.1 release candidates will be. > So can you make sure you include in your test plan for Alpina release some > testing against Neon.1 milestone/rc builds to minimize potential problems > if users install our plugins on Neon.1 when it becomes available. > > Thank you. > -- Len DiMaggio (ldimaggi at redhat.com) JBoss by Red Hat 314 Littleton Road Westford, MA 01886 USA tel: 978.392.3179 cell: 781.472.9912 http://www.redhat.com http://community.jboss.org/people/ldimaggio -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160805/f8f687a6/attachment.html From alkazako at redhat.com Fri Aug 5 16:03:17 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Fri, 5 Aug 2016 13:03:17 -0700 Subject: [jbosstools-dev] [aeri] Introducing Error Analyzers In-Reply-To: <0514A658-CC9A-4C14-85FB-06A768408BE2@codetrails.com> References: <0514A658-CC9A-4C14-85FB-06A768408BE2@codetrails.com> Message-ID: Thanks for sharing. Looks interesting. Will it be available in Neon.1? Or is it something planned for Oxygen? On 08/05/2016 04:57 AM, Marcel Bruch wrote: > Dear jbosstools-dev, > > the next version of AERI will allow to run *client-side > analyses* before an error report is send. > > For example, when a ClassNotFoundException is logged, AERI will run an > analyzer that: > > * tries to parse the class name from the exception?s error message, > * search for all bundles that export that class (i.e., the > containing package) and > * check which bundles and packages the failing bundle was wired to. > > The results of these analyses are added automatically to the error > report as "auxiliary information? (requires user consent). > > Besides the classpath analyzer we have a few more "common processors? > in mind which allow users to easily add > > * all system properties, > * all user preferences, > * all installed bundles, resolution status, and wiring information, > * all installed features + bundles with id, name, and version > information, > > to an error report. We *may* also take this a step further to allow > users to attach screenshots or code snippets to an error report. > > > The analyzers will be added to the review dialog as outlined below and > can be de/activated with one click. Reviewers can also > *demand* auxiliary information by setting the appropriate *needinfo > flags* on the problem: > > > > The exact API is not yet settled but I?d like to let you know early in > the process to gather your requirements. In case you have a > requirement or feature request, please let me/us know in bug 496656 [1]. > > Thank you, > Marcel > > > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=496656 > > > _______________________________________________ > 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/20160805/ac4cd3a2/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 92155 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160805/ac4cd3a2/attachment-0001.png From alkazako at redhat.com Fri Aug 5 16:39:41 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Fri, 5 Aug 2016 13:39:41 -0700 Subject: [jbosstools-dev] Need to update the list of components In-Reply-To: <0514A658-CC9A-4C14-85FB-06A768408BE2@codetrails.com> References: <0514A658-CC9A-4C14-85FB-06A768408BE2@codetrails.com> Message-ID: <6fd5e14a-df3d-3b9a-dc8d-d88e9a8c79b3@redhat.com> Hi Marcel, We need to update the list of JBoss Tools components. Is that list hardcoded and it's not downloaded from JIRA? For example we replaced "discovery" by "central-update" but it's not updated in redhat.ctrlflow.com Thanks. From marcel.bruch at codetrails.com Sun Aug 7 04:12:41 2016 From: marcel.bruch at codetrails.com (Marcel Bruch) Date: Sun, 7 Aug 2016 10:12:41 +0200 Subject: [jbosstools-dev] [aeri] Introducing Error Analyzers In-Reply-To: References: <0514A658-CC9A-4C14-85FB-06A768408BE2@codetrails.com> Message-ID: It?s planned that Neon.1 will already contain the key features as provisional API. Neon.2 and Neon.3 will step-by-step complete the feature set. Oxygen will contain the final feature set. > On 05 Aug 2016, at 22:03, Alexey Kazakov wrote: > > Thanks for sharing. Looks interesting. > Will it be available in Neon.1? Or is it something planned for Oxygen? > > On 08/05/2016 04:57 AM, Marcel Bruch wrote: >> Dear jbosstools-dev, >> >> the next version of AERI will allow to run client-side analyses before an error report is send. >> >> For example, when a ClassNotFoundException is logged, AERI will run an analyzer that: >> tries to parse the class name from the exception?s error message, >> search for all bundles that export that class (i.e., the containing package) and >> check which bundles and packages the failing bundle was wired to. >> The results of these analyses are added automatically to the error report as "auxiliary information? (requires user consent). >> >> Besides the classpath analyzer we have a few more "common processors? in mind which allow users to easily add >> all system properties, >> all user preferences, >> all installed bundles, resolution status, and wiring information, >> all installed features + bundles with id, name, and version information, >> to an error report. We may also take this a step further to allow users to attach screenshots or code snippets to an error report. >> >> >> The analyzers will be added to the review dialog as outlined below and can be de/activated with one click. Reviewers can also demand auxiliary information by setting the appropriate needinfo flags on the problem: >> >> >> >> >> The exact API is not yet settled but I?d like to let you know early in the process to gather your requirements. In case you have a requirement or feature request, please let me/us know in bug 496656 [1]. >> >> Thank you, >> Marcel >> >> >> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=496656 >> >> _______________________________________________ >> 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 -- Codetrails GmbH The knowledge transfer company Robert-Bosch-Str. 7, 64293 Darmstadt Phone: +49-6151-276-7092 Mobile: +49-179-131-7721 http://www.codetrails.com/ Managing Director: Dr. Marcel Bruch Handelsregister: Darmstadt HRB 91940 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160807/ffa1118f/attachment.html From aer-bot at ctrlflow.com Sun Aug 7 23:30:00 2016 From: aer-bot at ctrlflow.com (Automated Error Reporting Bot) Date: Mon, 8 Aug 2016 03:30:00 +0000 (UTC) Subject: [jbosstools-dev] [aeri] Weekly JBoss Tools Error Reports Digest Message-ID: <935020310.515.1470627000877.JavaMail.ec2-user@aeri-rh> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160808/a5ba96ae/attachment-0001.html From marcel.bruch at codetrails.com Mon Aug 8 11:24:23 2016 From: marcel.bruch at codetrails.com (Marcel Bruch) Date: Mon, 8 Aug 2016 17:24:23 +0200 Subject: [jbosstools-dev] Need to update the list of components In-Reply-To: <6fd5e14a-df3d-3b9a-dc8d-d88e9a8c79b3@redhat.com> References: <0514A658-CC9A-4C14-85FB-06A768408BE2@codetrails.com> <6fd5e14a-df3d-3b9a-dc8d-d88e9a8c79b3@redhat.com> Message-ID: > On 05 Aug 2016, at 22:39, Alexey Kazakov wrote: > > Hi Marcel, > > We need to update the list of JBoss Tools components. Is that list hardcoded and it's not downloaded from JIRA? It?s downloaded. > For example we replaced "discovery" by "central-update" but it's not updated in redhat.ctrlflow.com I triggered the update manually via "settings > bug tracking > synchronize projects? and can see central-update in the list now. Every org-admin can trigger that update (you, fred, max, jeff, jboss-dev). We?ll add a cron job for this to update the list every X hours. If, however, you need it immediately, you now know where to trigger the update manually. Best, Marcel > > Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160808/ef812108/attachment.html From alkazako at redhat.com Mon Aug 8 11:30:44 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Mon, 8 Aug 2016 08:30:44 -0700 Subject: [jbosstools-dev] Need to update the list of components In-Reply-To: References: <0514A658-CC9A-4C14-85FB-06A768408BE2@codetrails.com> <6fd5e14a-df3d-3b9a-dc8d-d88e9a8c79b3@redhat.com> Message-ID: Thanks Marcel. On 08/08/2016 08:24 AM, Marcel Bruch wrote: > > >> On 05 Aug 2016, at 22:39, Alexey Kazakov > > wrote: >> >> Hi Marcel, >> >> We need to update the list of JBoss Tools components. Is that list >> hardcoded and it's not downloaded from JIRA? > > > It?s downloaded. > > >> For example we replaced "discovery" by "central-update" but it's not >> updated in redhat.ctrlflow.com > > I triggered the update manually via "settings > bug tracking > > synchronize projects? and can see central-update in the list now. > Every org-admin can trigger that update (you, fred, max, jeff, > jboss-dev). We?ll add a cron job for this to update the list every X > hours. If, however, you need it immediately, you now know where to > trigger the update manually. > > Best, > Marcel > >> >> Thanks. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160808/37f953ca/attachment.html From marcel.bruch at codetrails.com Mon Aug 8 15:01:05 2016 From: marcel.bruch at codetrails.com (Marcel Bruch) Date: Mon, 8 Aug 2016 21:01:05 +0200 Subject: [jbosstools-dev] [aeri] Create multiple JIRAs from one search query Message-ID: <77C4F96C-47A8-46BA-98F7-7A18A88AAE8A@codetrails.com> Greetings JBosstools-Dev I just noticed that today a few people created many bug reports ?one-by-one?. This may be on purpose but if not, here is how you can create a set of JIRAs in one click: 1. Make sure that your project has a default JIRA project, component and version. If not set, go to projects > your project > bug tracking and select the values for your project. 2. Go to the problems page, filter all problems belonging to your project, and select the bulk edit action ?create bug report?. Finally select all problems you?d like to create a JIRA for and press ?Execute?. That?s all. Now, you can make the final adjustments in JIRA as needed (set the target version, assign the bug report to s/o etc.) HTH, Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160808/c72c607f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-08-08 at 20.54.51.png Type: image/png Size: 203087 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160808/c72c607f/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-08-08 at 20.46.52.png Type: image/png Size: 77482 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160808/c72c607f/attachment-0003.png From alkazako at redhat.com Mon Aug 8 16:38:35 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Mon, 8 Aug 2016 13:38:35 -0700 Subject: [jbosstools-dev] [aeri] Create multiple JIRAs from one search query In-Reply-To: <77C4F96C-47A8-46BA-98F7-7A18A88AAE8A@codetrails.com> References: <77C4F96C-47A8-46BA-98F7-7A18A88AAE8A@codetrails.com> Message-ID: <8a995466-abd1-17b0-fc10-e8b3c46cc76b@redhat.com> Thanks Marcel. This is helpful! On 08/08/2016 12:01 PM, Marcel Bruch wrote: > Greetings JBosstools-Dev > > I just noticed that today a few people created many bug reports > ?one-by-one?. This may be on purpose but if not, here is how you can > create a set of JIRAs in one click: > > 1. Make sure that your project has a default JIRA project, component > and version. If not set, go to projects > your project > bug tracking > and select the values for your project. > > > 2. Go to the problems page, filter all problems belonging to your > project, and select the bulk edit action ?create bug report?. Finally > select all problems you?d like to create a JIRA for and press ?Execute?. > > That?s all. Now, you can make the final adjustments in JIRA as needed > (set the target version, assign the bug report to s/o etc.) > > > > HTH, > Marcel > > > > _______________________________________________ > 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/20160808/d93b5466/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 203087 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160808/d93b5466/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 77482 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160808/d93b5466/attachment-0003.png From nboldt at redhat.com Tue Aug 9 14:58:11 2016 From: nboldt at redhat.com (Nick Boldt) Date: Tue, 9 Aug 2016 14:58:11 -0400 Subject: [jbosstools-dev] Jenkins pages take forever to load over https? Here's a solution! Message-ID: Having recently moved to Fedora 24, I forgot to set up kerberos when setting up my new machine. So, as a result, I've been seeing https pages from jenkins.mw taking as long as 2 mins to load fully. The solution? a) ensure kerberos is installed and properly set up [1] b) ensure kerberos ticket is enabled (kinit) [2] c) ensure chrome is USING the ticket [3] d) ensure chrome is configured to cache images/scripts/css files (so page loads are faster) [1] https://mojo.redhat.com/docs/DOC-1017803 [2] https://mojo.redhat.com/docs/DOC-1011190 [3] https://www.quora.com/How-can-I-configure-Google-Chrome-to-use-Kerberos I can now load the above https pages in mere seconds (under 20 for long /configure pages, under 10 for simpler ones) where before it was between 90-120 seconds! --- Something you might want to do is to have kinit run every time you start vpnc. Here are the aliases I use for starting/stopping vpnc: alias resolvconf8888='sudo ~/bin/resolvconf8888.sh' # see [4] alias V='sudo vpnc-disconnect; sleep 2s; kinit -r 7d && klist -f; sudo vpnc; resolvconf8888' alias VV='sudo vpnc-disconnect; resolvconf8888' [4] https://gist.github.com/nickboldt/7390a20ad5027a598d65ff44dcd5def5 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Wed Aug 10 14:00:21 2016 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 10 Aug 2016 14:00:21 -0400 Subject: [jbosstools-dev] REMINDER: Code Freeze for 4.4.1.AM3 / 10.1.0.AM3 is tomorrow, Thurs Aug 11 @ 5pm EST Message-ID: We'll be building the bits to stage for QE from the master branch, so there's no need to change your root poms or create branches. Just be sure to have everything you want included in the build pushed to github by 5pm EST on Thursday night. Build will run over night, and will be copied from /snapshots/ to /staging/ on Friday morning. If you have anything blocking you from being ready by EOD on Thursday (tomorrow!) let me know ASAP. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Wed Aug 10 16:37:14 2016 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 10 Aug 2016 16:37:14 -0400 Subject: [jbosstools-dev] Release date for Tycho 0.26: late August 2016 Message-ID: FYI, Tycho 0.26 should be available for use with 4.4.1.Final / 10.1.0.GA. ---------- Forwarded message ---------- From: Sievers, Jan Date: Mon, Aug 8, 2016 at 3:28 AM Subject: Re: [tycho-user] Release date for Tycho 0.26? To: Tycho user list Cc: Tycho list it's been almost 4 months since 0.25.0 [1] so I propose to schedule staging 0.26.0 this Friday, release one week later. the list of bugs fixed/features added is not long [2] but together with the support added for TestNG I guess there is enough interest for a release. @committers objections? Regards, Jan [1] https://wiki.eclipse.org/Tycho/Release_Notes [2] https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&list_id=14871210&product=Tycho&query_format=advanced&target_milestone=0.26.0 On 05/08/16 17:53, "tycho-user-bounces at eclipse.org on behalf of Nick Boldt" wrote: Just wondering if there's a planned date for Tycho 0.26. Looking forward to being able to use this new feature [1] but need a full release (not a snapshot) in order to use this in our .Final builds. [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.26#New_option_to_check_consistency_of_.target_files Thanks, -- Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat, Inc. http://nick.divbyzero.com _______________________________________________ tycho-user mailing list tycho-user at eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/tycho-user _______________________________________________ tycho-user mailing list tycho-user at eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/tycho-user -- Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat, Inc. http://nick.divbyzero.com From adietish at redhat.com Thu Aug 11 05:33:56 2016 From: adietish at redhat.com (=?UTF-8?Q?Andr=c3=a9_Dietisheim?=) Date: Thu, 11 Aug 2016 11:33:56 +0200 Subject: [jbosstools-dev] [devtools-team] Checkstyle proposal In-Reply-To: References: Message-ID: On 08/03/2016 10:00 PM, Dmitrii Bocharov wrote: > Good part of the day, team! > While reviewing someone's code or just looking through it while > coding, i often want to correct the style of the code: insert a space > or divide the line in two. I understand that it is really an > idealistic niggle and a matter of taste, but some things really annoy. +1, same to me. This being said there are a few gotchas: - if we dont want to duplicate Eclipse formatter and checkstyle rules we'd have to find a way to share there. Even though I believe that this isnt a big show stopper. Once done you wont change these often. - we also have to commit the Eclipse code formatter we're using. Ideally we'd have a way to facilitate workspace setup so that this wont get another additional step (http://stackoverflow.com/questions/17703706/any-way-to-automate-eclipse-workspace-setup): * Oomph (https://timdelbruegger.wordpress.com/2015/08/16/automating-project-specific-eclipse-setups-with-oomph/) ? * PSF? * Workspace mechanics? We have a jira covering code formatters and checkers: https://issues.jboss.org/browse/JBIDE-22439 > In my opinion it is a good practice to have agreements about the code > formatting. Luckily, there is a mechanism in IDEs and usually > checkstyle.xml-s are committed and then just imported by everybody. > This is an example of our Red Hat colleagues from EAP team (they're > just sitting next to me): > https://github.com/wildfly/wildfly-core/tree/master/ide-configs/eclipse > Of course if we apply such a checkstyle to one of our plugins, that > didn't have it before, it'll be a real mess. So i think it's better to > use it only for the files, where we correct the code. Soon we'll cover > a big part of the code like this. > Moreover, there is a maven checkstyle plugin: > http://maven.apache.org/plugins/maven-checkstyle-plugin/. However, i > suppose it makes sense to include it some time later when most of the > code will be formatted and that will help to cover the rest. > > So the proposal is to do the following for plugins, that don't have > such thing (didn't check all of them, but the ones, i'm working on - > don't): > 1) To create a checkstyle.xml file > 2) Commit it (for every plugin or just in jbosstools-devdoc, for > example) and add information about it to the Contribution part of the > plugins' descriptions > 3) All contributors should add it to their Eclipses > 4) Make remarks about code style in PRs. > 5*) configure maven checkstyle plugin in org.jboss.tools.parent (or in > every plugin) > > Best regards, > Dmitrii From nboldt at redhat.com Thu Aug 11 09:38:43 2016 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 11 Aug 2016 09:38:43 -0400 Subject: [jbosstools-dev] FYI: Target Platforms & Central will include newer docker/vagrant tools & subclipse/svnkit (updated to version AM3) Message-ID: Builds are in progress now to update target platforms & Central from 4.60.1.AM1/4.60.0.Final to 4.60.1.AM3, in prep for today's code freeze. Related issues w/ PRs and p2diffs: https://issues.jboss.org/browse/JBIDE-22885 docker/vagrant tools in jbt/devstudio target platforms https://issues.jboss.org/browse/JBIDE-22888 subclipse/svnkit update in Central -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Fri Aug 12 23:05:18 2016 From: nboldt at redhat.com (nboldt at redhat.com) Date: Fri, 12 Aug 2016 23:05:18 -0400 Subject: [jbosstools-dev] JBoss Tools Core 4.4.1.AM3 bits available for QE testing Message-ID: <201608130305.u7D35IFX009200@dev01.mw.lab.eng.bos.redhat.com> These are not FINAL bits, but preliminary results for QE & community testing. Not for redistribution to customers or end users. Update site: http://download.jboss.org/jbosstools/neon/staging/updates/ 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/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page -- Additional update sites: * http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.1.AM3/ * http://download.jboss.org/jbosstools/neon/staging/updates/coretests/4.4.1.AM3/ Target platforms: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.1.AM3-SNAPSHOT * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.1.AM3-SNAPSHOT Discovery sites: * http://download.jboss.org/jbosstools/neon/staging/updates/discovery.central/4.4.1.AM3/ * http://download.jboss.org/jbosstools/neon/staging/updates/discovery.earlyaccess/4.4.1.AM3/ Build folders (for build logs & update site zips): * http://download.jboss.org/jbosstools/neon/staging/builds/ From aer-bot at ctrlflow.com Sun Aug 14 23:30:01 2016 From: aer-bot at ctrlflow.com (Automated Error Reporting Bot) Date: Mon, 15 Aug 2016 03:30:01 +0000 (UTC) Subject: [jbosstools-dev] [aeri] Weekly JBoss Tools Error Reports Digest Message-ID: <1061084508.0.1471231801365.JavaMail.ec2-user@aeri-rh> An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160815/65588449/attachment-0001.html From odockal at redhat.com Tue Aug 16 10:01:46 2016 From: odockal at redhat.com (Ondrej Dockal) Date: Tue, 16 Aug 2016 16:01:46 +0200 Subject: [jbosstools-dev] Regarding AERI report system reviewing Message-ID: Hi, Recently, I tried to review some aeri reports on [1] via github account, but I dont have permission to do so. We found out that I need to be on github in jboostools organizitaion, this implies also for some other members of devstudio QE team. Is there any way how to request for membership? OR I would like to ask anybody who is administrator of [2] group/organization, if he could add these github members of devstudio QE to jboostools: jkopriva, odockal, mlabuda, jrichter, ppitonak and luvalach. Thanks in advance! [1]: https://redhat.ctrlflow.com/reviewers#!/ [2]: https://github.com/jbosstools -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160816/c68d8c9b/attachment.html From mmalina at redhat.com Wed Aug 17 07:21:10 2016 From: mmalina at redhat.com (Martin Malina) Date: Wed, 17 Aug 2016 13:21:10 +0200 Subject: [jbosstools-dev] Vagrant tooling in JBoss Tools TP Message-ID: <9897CF95-DE68-4152-9E9C-C5DCAD3B6049@redhat.com> Hi Xavier/Alexey/Nick, I have a question: Why do we have vagrant tooling in our TP when we don't include it in JBT/devstudio? See https://issues.jboss.org/browse/JBIDE-22885 Thanks, Martin -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265 From nboldt at redhat.com Wed Aug 17 10:52:18 2016 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 17 Aug 2016 10:52:18 -0400 Subject: [jbosstools-dev] Fwd: [eclipse.org-planning-council] ECF possibly leaving the train In-Reply-To: References: Message-ID: FYI. ECF might leave the simultaneous release train. Reasons why this is potentially bad for us are outlined below. https://dev.eclipse.org/mhonarc/lists/ecf-dev/msg07938.html ---------- Forwarded message ---------- From: Sam Davis Date: Tue, Aug 16, 2016 at 3:00 PM Subject: [eclipse.org-planning-council] ECF possibly leaving the train To: Eclipse Planning Council private list Hi, I want to bring to the Council's attention the fact that ECF is considering pulling out of the simultaneous release train, because I haven't seen any discussion about this. This is concerning for a couple of reasons: * a number of projects in the train, including Platform, depend on ECF, so we may end up with different projects pulling in different versions of ECF, which is not ideal * The fact that participation in the train entails so much overhead that an active project with a long history of successful participation is considering pulling out seems like a larger and quite serious problem for Eclipse. I believe at least part of the overhead is due to the instability of the build infrastructure. I'm afraid I don't have any concrete solutions to propose, but I wonder if, given the current resources, we should consider simplifying the contribution process (somehow), or reallocating resources from elsewhere to improve the stability of the infrastructure. Regarding the infrastructure, my experience from the Mylyn project is that projects must spend a great deal of time dealing with broken Hudson slaves, breakages in the signing service, and similar issues, to the point where I can see why it threatens projects' ability to participate. Just to be clear, I am not blaming anyone for this - I know that it takes a lot of work to keep all these things running smoothly. Cheers, Sam -- Sam Davis Software Engineer, Tasktop Dev Committer, Eclipse Mylyn http://tasktop.com _______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-council at eclipse.org https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo at eclipse.org to request removal. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Wed Aug 17 10:57:14 2016 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 17 Aug 2016 10:57:14 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: Please triage 23 unresolved issues with fixversion = 4.4.1.AM3 / 10.1.0.AM3 Message-ID: If they will be fixed by EOD or are already fixed, please mark them as such. If they won't be fixed today, please bump them to .Final or .GA https://issues.jboss.org/issues/?jql=project%20in%20(JBIDE%2CJBDS)%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(%2212330880%22%2C%2212330877%22) -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Wed Aug 17 17:46:09 2016 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 17 Aug 2016 17:46:09 -0400 Subject: [jbosstools-dev] Master branch open for business - but be sure to tag first! Message-ID: With the release of AM3, master branch is again open for business. Component leads, please be sure to tag your project from the master branch (tag: jbosstools-4.4.1.AM3) before committing any new changes toward the 4.4.1.Final release. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From akazakov at redhat.com Thu Aug 18 02:58:49 2016 From: akazakov at redhat.com (akazakov at redhat.com) Date: Thu, 18 Aug 2016 02:58:49 -0400 Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component Message-ID: <201608180658.u7I6wnOl009311@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-4006 https://issues.jboss.org/browse/JBDS-4006 Summary: Unable to add nested in Camel - Blueprint Assignee: None set. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 18:48:32.245865 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27 From jmaury at redhat.com Thu Aug 18 03:42:34 2016 From: jmaury at redhat.com (Jean-Francois Maury) Date: Thu, 18 Aug 2016 09:42:34 +0200 Subject: [jbosstools-dev] JBoss Tools 4.4.1.AM3 is now available Message-ID: This is a development release aimed at Eclipse 4.6.0 Neon.0 users. Announcement Blog: http://tools.jboss.org/blog/ Eclipse Marketplace: https://marketplace.eclipse.org/content/jboss-tools Update Site: http://download.jboss.org/jbosstools/neon/development/updates/ Zips: http://tools.jboss.org/downloads/jbosstools/neon/4.4.1.AM3.html#zips Installation instructions: http://tools.jboss.org/ downloads/installation.html New + Noteworthy (subject to change): http://tools.jboss.org/ documentation/whatsnew/jbosstools/4.4.1.AM3.html Schedule / Upcoming Releases: https://issues.jboss.org/ browse/JBIDE?selectedTab=com.atlassian.jira.jira-projects- plugin:versions-panel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160818/8f1c6ea1/attachment.html From xcoulon at redhat.com Thu Aug 18 04:15:23 2016 From: xcoulon at redhat.com (Xavier Coulon) Date: Thu, 18 Aug 2016 10:15:23 +0200 Subject: [jbosstools-dev] Master branch open for business - but be sure to tag first! In-Reply-To: References: Message-ID: hello, it's done on Web Services and LiveReload (thanks to Dmitry) components. Best regards, /Xavier. > On 17 Aug 2016, at 23:46, Nick Boldt wrote: > > With the release of AM3, master branch is again open for business. > > Component leads, please be sure to tag your project from the master > branch (tag: jbosstools-4.4.1.AM3) before committing any new changes > toward the 4.4.1.Final release. > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From jmaury at redhat.com Thu Aug 18 04:59:16 2016 From: jmaury at redhat.com (Jean-Francois Maury) Date: Thu, 18 Aug 2016 10:59:16 +0200 Subject: [jbosstools-dev] Master branch open for business - but be sure to tag first! In-Reply-To: References:

Message-ID: I'm not getting it. I created the tag on all repos through the Python script Nick sent me so what is to do at the component level. Jeff On Thu, Aug 18, 2016 at 10:15 AM, Xavier Coulon wrote: > hello, > > it's done on Web Services and LiveReload (thanks to Dmitry) components. > > Best regards, > /Xavier. > > > On 17 Aug 2016, at 23:46, Nick Boldt wrote: > > > > With the release of AM3, master branch is again open for business. > > > > Component leads, please be sure to tag your project from the master > > branch (tag: jbosstools-4.4.1.AM3) before committing any new changes > > toward the 4.4.1.Final release. > > > > -- > > Nick Boldt :: JBoss by Red Hat > > Productization Lead :: JBoss Tools & Dev Studio > > http://nick.divbyzero.com > > _______________________________________________ > > jbosstools-dev mailing list > > jbosstools-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160818/da6091e7/attachment-0001.html From nboldt at redhat.com Thu Aug 18 09:29:34 2016 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 18 Aug 2016 09:29:34 -0400 Subject: [jbosstools-dev] Master branch open for business - but be sure to tag first! In-Reply-To: References:

Message-ID: Component leads = people in charge of the jbosstools-* github repos, or jbosstools components in JIRA. I only mentioned the need to create the tags in this email in case you hadn't had a chance to create the tags BEFORE someone saw my email and started pushing changes to master. If you have created all the tags, then there's nothing left to do except fix all the bugs in master branch. :D On Thu, Aug 18, 2016 at 4:59 AM, Jean-Francois Maury wrote: > I'm not getting it. I created the tag on all repos through the Python script > Nick sent me so what is to do at the component level. > > Jeff > > On Thu, Aug 18, 2016 at 10:15 AM, Xavier Coulon wrote: >> >> hello, >> >> it's done on Web Services and LiveReload (thanks to Dmitry) components. >> >> Best regards, >> /Xavier. >> >> > On 17 Aug 2016, at 23:46, Nick Boldt wrote: >> > >> > With the release of AM3, master branch is again open for business. >> > >> > Component leads, please be sure to tag your project from the master >> > branch (tag: jbosstools-4.4.1.AM3) before committing any new changes >> > toward the 4.4.1.Final release. >> > >> > -- >> > Nick Boldt :: JBoss by Red Hat >> > Productization Lead :: JBoss Tools & Dev Studio >> > http://nick.divbyzero.com >> > _______________________________________________ >> > jbosstools-dev mailing list >> > jbosstools-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From mmalina at redhat.com Thu Aug 18 10:55:15 2016 From: mmalina at redhat.com (Martin Malina) Date: Thu, 18 Aug 2016 16:55:15 +0200 Subject: [jbosstools-dev] Master branch open for business - but be sure to tag first! In-Reply-To: References:

Message-ID: <9DE68742-15FA-4C08-AD8D-22DE8CF8474B@redhat.com> Shouldn't the BUILD_ALIAS be set to Final now? [1] No pressure, just curious where this fits in the workflow. Do we also want to update the version from 4.4.1.Alpha1-SNAPSHOT to Final at some point or is it not necessary at all? -Martin [1] http://www.rockpoint.cz/stan-msr-elixir-3/pMSR21010037-2/ > On 18. 8. 2016, at 15:29, Nick Boldt wrote: > > Component leads = people in charge of the jbosstools-* github repos, > or jbosstools components in JIRA. > > I only mentioned the need to create the tags in this email in case you > hadn't had a chance to create the tags BEFORE someone saw my email and > started pushing changes to master. > > If you have created all the tags, then there's nothing left to do > except fix all the bugs in master branch. :D > > > > On Thu, Aug 18, 2016 at 4:59 AM, Jean-Francois Maury > wrote: >> I'm not getting it. I created the tag on all repos through the Python script >> Nick sent me so what is to do at the component level. >> >> Jeff >> >> On Thu, Aug 18, 2016 at 10:15 AM, Xavier Coulon wrote: >>> >>> hello, >>> >>> it's done on Web Services and LiveReload (thanks to Dmitry) components. >>> >>> Best regards, >>> /Xavier. >>> >>>> On 17 Aug 2016, at 23:46, Nick Boldt wrote: >>>> >>>> With the release of AM3, master branch is again open for business. >>>> >>>> Component leads, please be sure to tag your project from the master >>>> branch (tag: jbosstools-4.4.1.AM3) before committing any new changes >>>> toward the 4.4.1.Final release. >>>> >>>> -- >>>> Nick Boldt :: JBoss by Red Hat >>>> Productization Lead :: JBoss Tools & Dev Studio >>>> http://nick.divbyzero.com >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> > > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160818/9c1f4a44/attachment.html From alkazako at redhat.com Thu Aug 18 15:57:30 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Thu, 18 Aug 2016 12:57:30 -0700 Subject: [jbosstools-dev] Regarding AERI report system reviewing In-Reply-To: References: Message-ID: On 08/16/2016 07:01 AM, Ondrej Dockal wrote: > Hi, > > Recently, I tried to review some aeri reports on [1] via github > account, but I dont have permission to do so. We found out that I need > to be on github in jboostools organizitaion, this implies also for > some other members of devstudio QE team. > > Is there any way how to request for membership? > > OR > > I would like to ask anybody who is administrator of [2] > group/organization, if he could add these github members of devstudio > QE to jboostools: jkopriva, odockal, mlabuda, jrichter, ppitonak and > luvalach. I added these users but jrichter. I added jrichter1 instead. I guess this is what you actually meant. Sorry for the delay. > > Thanks in advance! > > [1]: https://redhat.ctrlflow.com/reviewers#!/ > > [2]: https://github.com/jbosstools > > > _______________________________________________ > 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/20160818/926b5ab8/attachment-0001.html From alkazako at redhat.com Thu Aug 18 16:41:00 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Thu, 18 Aug 2016 13:41:00 -0700 Subject: [jbosstools-dev] Vagrant tooling in JBoss Tools TP In-Reply-To: <9897CF95-DE68-4152-9E9C-C5DCAD3B6049@redhat.com> References: <9897CF95-DE68-4152-9E9C-C5DCAD3B6049@redhat.com> Message-ID: <37f23338-9b3b-9b9b-62c0-89c4317aa962@redhat.com> As far as I remember there was an initiative to include vagrant tools to devstudio because it could help CDK users. But we wanted to test it and see if it actually provide any value for CDK users. So we included it to TP so it's easier to install but we do not install it by default. On 08/17/2016 04:21 AM, Martin Malina wrote: > Hi Xavier/Alexey/Nick, > > I have a question: Why do we have vagrant tooling in our TP when we don't include it in JBT/devstudio? > See https://issues.jboss.org/browse/JBIDE-22885 > > Thanks, > Martin > > -- > Martin Malina > JBoss QA Engineer > Red Hat Czech s.r.o. > Purkynova 99 > 612 45 Brno, Czech Republic > > Tel.: +420 532 294 265 > > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From nboldt at redhat.com Fri Aug 19 14:04:05 2016 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 19 Aug 2016 14:04:05 -0400 Subject: [jbosstools-dev] README: Updates to parent pom, target platforms, and CI publishing process Message-ID: Since AM3 is now released, it's time to upversion the jbt, devstudio, central, and EA target platforms from AM3 to Final. I've also moved parent pom to use Tycho 0.26.0 [0], which allows us to use the latest TP validation [1]. Simply enabling this new validator caught a problem w/ two different versions of the same atlassian feature in jbt/devstudio vs. central. So, that's been fixed. [0] http://wiki.eclipse.org/Tycho/Release_Notes/0.26 [1] https://issues.jboss.org/browse/JBIDE-22673 BUILD_ALIAS is now set to Final (or GA, for devstudio builds). Therefore, builds such as jbosstools-openshift should fail if a SNAPSHOT dependency is re-introduced [2]. Or if you use a SNAPSHOT dependency, like in jbosstools-aerogear [3] [2] https://issues.jboss.org/browse/JBIDE-22446 [3] https://issues.jboss.org/browse/JBIDE-22881 Finally, it should be noted that builds now use p2diff -mode=deep to determine if there's any reason to publish new bits onto download.jboss.org. Should you notice that your commits are not being built & published in a timely manner, please let me know ASAP. See also this issue [4]. [4] https://issues.jboss.org/browse/JBIDE-22968 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Fri Aug 19 14:06:15 2016 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 19 Aug 2016 14:06:15 -0400 Subject: [jbosstools-dev] README: Upcoming root pom changes & 4.4.1.x branches Message-ID: Soon, we'll be moving everyone to a new parent pom version (4.4.1.Final-SNAPSHOT) and creating branches (jbosstools-4.4.1.x) [5]. [5] https://issues.jboss.org/browse/JBIDE-22728 Once that's done, master branch will be open for new development work toward 4.4.2. Reminder, master branch is open right now, but ONLY for bugfixes for 4.4.1.Final. No new features! If you want to manually switch yourself over to using parent pom 4.4.1.Final-SNAPSHOT, and branch yourself from master to jbosstools-4.4.1.x branch, feel free. Or, you can wait until I get the automation done and Alexey or Jeff create all the branches / make all the changes for you in one step. Cheers, Nick -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From aer-bot at ctrlflow.com Sun Aug 21 23:30:01 2016 From: aer-bot at ctrlflow.com (Automated Error Reporting Bot) Date: Mon, 22 Aug 2016 03:30:01 +0000 (UTC) Subject: [jbosstools-dev] [aeri] Weekly JBoss Tools Error Reports Digest Message-ID: <361448135.1.1471836601394.JavaMail.ec2-user@aeri-rh> ------------------------------------------------------------------------ Project Arquillian Top new problems (last 7 days): Congrats, no problems in this section! Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. ResourceException below ArquillianProjectConfigurator.configureInternal (thrown in Resource.checkExists) 6 Open Major JBIDE-22720 2. ResourceException below ArquillianProjectConfigurator.configureInternal (thrown in Project.checkAccessible) 5 Open Major JBIDE-22720 3. NullPointerException below DependencyCache.getDependentTypes (thrown in AbstractCollection.addAll) 1 Open Major JBIDE-23003 Project Life-time Resolution Statistics Problem Resolutions Count Done: 8 Unresolved: 11 ------------------------------------------------------------------------ Project Batch Tools Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. JavaModelException below BatchPropertyHyperlinkDetector.detectHyperlinks (thrown in Openable.codeSelect) 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. JavaModelException below FileSet.checkType (thrown in JavaElement.newNotPresentException) 200 Open Major JBIDE-22285 2. FileNotFoundException below BatchBuilder$BatchResourceVisitor.visit (thrown in FileInputStream.open0) 13 Pull Request Sent Major JBIDE-22898 3. ResourceException below BatchBuilder$BatchResourceVisitor.visit (thrown in FileSystemResourceManager.read) 12 New Major - 4. JavaModelException below BatchPropertyHyperlinkDetector.detectHyperlinks (thrown in JavaElement.newJavaModelException) 3 New Major - 5. ConcurrentModificationException below BatchDiagramConnectionService$2.handleTypedEvent (thrown in ArrayList$Itr.checkForComodification) 2 New Major - 6. FileNotFoundException below FileSet.checkType (thrown in ZipFile.open) 2 New Major - 7. NoStackTrace below BatchBuilder.buildJars (thrown in JarPackageFragmentRoot.computeChildren) 2 New Major - 8. ClassNotFoundException below BatchArtifactRenameParticipant.initialize (thrown in BundleLoader.findClassInternal) 1 New Major - 9. JavaModelException below BatchPropertyHyperlinkDetector.detectHyperlinks (thrown in Openable.codeSelect) 1 New Major - 10. NullPointerException in BatchValidator.validateRefAndProperties 1 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Not JBoss: 1 Done: 1 Unresolved: 18 ------------------------------------------------------------------------ Project CDI Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. JavaModelException below AuthorizerHyperlinkDetector.detectHyperlinks (thrown in Openable.codeSelect) 1 New Major - 2. JavaModelException below EventAndObserverMethodHyperlinkDetector.detectHyperlinks (thrown in Openable.codeSelect) 1 New Major - 3. JavaModelException below GenericInjectedPointHyperlinkDetector.detectHyperlinks (thrown in Openable.codeSelect) 1 New Major - 4. JavaModelException below InjectedPointHyperlinkDetector.detectHyperlinks (thrown in Openable.codeSelect) 1 New Major - 5. JavaModelException below ProducerDisposerHyperlinkDetector.detectHyperlinks (thrown in Openable.codeSelect) 1 New Major - 6. JavaModelException below TypeDefinition.init (thrown in JavaElement.newNotPresentException) 1 New Major - 7. ZipException below BeanArchiveDetector.isAnnotatedBean (thrown in ZipFile.read) 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. JavaModelException below BeanArchiveDetector.isAnnotatedBean (thrown in JavaElement.newNotPresentException) 43 Open Major JBIDE-22900 2. NullPointerException in CDICoreBuilder$IncrementCheck. 33 Pull Request Sent Major JBIDE-22902 3. NoStackTrace in CDICoreValidator.init 32 Open Major JBIDE-22904 4. NullPointerException in CDICoreValidator$CDIValidationContext. 19 Pull Request Sent Major JBIDE-22906 5. ConcurrentModificationException below CDIProjectAsYouType.findCompilationUnit (thrown in FeatureMapUtil$BasicFeatureEIterator.checkModCount) 18 Open Major JBIDE-22905 6. JavaModelException below TypeDefinition.init (thrown in JavaElement.newJavaModelException) 9 New Major - 7. JavaModelException below CDICoreValidator.validateManagedBean (thrown in JavaElement.newNotPresentException) 5 New Major - 8. TeamException below PackageDefinition.setPackage (thrown in RepositoryProvider.mapNewProvider) 5 New Major - 9. ClassNotFoundException below CDICorePlugin$1.saving (thrown in BundleLoader.findClassInternal) 4 New Major - 10. FileNotFoundException below CDICoreBuilder$CDIResourceVisitor.visit (thrown in FileInputStream.open) 4 New Major - 11. JavaModelException below AbstractMemberDefinition.init (thrown in JavaElement.newNotPresentException) 4 New Major - 12. NullPointerException below CDIProjectAsYouType.findCompilationUnit (thrown in AnnotationsCoreProcessorFactory.getProcessorFor) 4 New Major - 13. NullPointerException below CDIProjectAsYouType.findCompilationUnit (thrown in BasicFeatureMap$FeatureEIterator.scanNext) 4 New Major - 14. NullPointerException below CDIProjectAsYouType.findCompilationUnit (thrown in EJBAnnotationReader.processRemoveBean) 4 New Major - 15. JavaModelException below AuthorizerHyperlinkDetector.detectHyperlinks (thrown in JavaElement.newJavaModelException) 3 New Major - 16. JavaModelException below EventAndObserverMethodHyperlinkDetector.detectHyperlinks (thrown in JavaElement.newJavaModelException) 3 New Major - 17. JavaModelException below InjectedPointHyperlinkDetector.detectHyperlinks (thrown in JavaElement.newJavaModelException) 3 New Major - 18. JavaModelException below ProducerDisposerHyperlinkDetector.detectHyperlinks (thrown in JavaElement.newJavaModelException) 3 New Major - 19. NullPointerException below CDIProjectAsYouType.findCompilationUnit (thrown in WebAnnotationReader.analyzeCompilationUnit) 3 New Major - 20. NullPointerException below DefinitionContext.addType (thrown in TreeMap.put) 3 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Out of Date: 1 Duplicate Issue: 1 Log Message: 8 Done: 3 Unresolved: 96 ------------------------------------------------------------------------ Project Drools Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. ClassCastException in KnowledgeBuilderConfigurationImpl.loadAccumulateFunction 1 New Major - 2. NoStackTrace below AbstractProjectPreferencePage.performOk (thrown in AbstractMergedModelProvider.getMergedModel) 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. Exception in ReteViewer.loadReteModel 10 New Major - 2. Throwable in AbstractRuntimeManager.recognizeJars 9 New Major - 3. JavaModelException below DroolsRuntimeManager.addBuilder (thrown in JavaModelOperation.runOperation) 7 New Major - 4. IllegalStateException below DroolsRuntimesBlock.setDroolsRuntimes (thrown in StructuredViewer.setInput) 4 New Major - 5. RuntimeDroolsException in JavaDialectConfiguration.setJavaLanguageLevel 3 New Major - 6. RuntimeDroolsException in JavaDialectConfiguration.setJavaLanguageLevel 3 New Major - 7. ClassCastException in PackageBuilderConfiguration.addDialect 2 New Major - 8. NullPointerException in DroolsThread.computeStackFrames 2 New Major - 9. ClassCastException in AbstractKiePropertyPage.getContentNode 1 New Major - 10. ClassCastException in KnowledgeBuilderConfigurationImpl.loadAccumulateFunction 1 New Major - 11. ClassNotFoundException below ExcelParser.parseFile (thrown in BundleLoader.findClassInternal) 1 New Major - 12. DebugException below DroolsDebugTarget.breakpointAdded (thrown in Breakpoint.ensureMarker) 1 New Major - 13. HIDDEN below ExtensibleXmlParser.read (thrown in ErrorHandlerWrapper.createSAXParseException) 1 New Major - 14. JavaModelException below ProjectClassLoader.getProjectClassPathURLs (thrown in JavaElement.newNotPresentException) 1 New Major - 15. NoClassDefFoundError below ExcelParser.parseFile (thrown in WorkbookFactory.create) 1 New Major - 16. NoStackTrace below AbstractProjectPreferencePage.performOk (thrown in AbstractMergedModelProvider.getMergedModel) 1 New Major - 17. NullPointerException in KieServerHandler.getOrganizations 1 New Major - 18. NullPointerException in KieServerHandler.loadDelegate 1 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Won't Fix: 1 Unresolved: 42 ------------------------------------------------------------------------ Project ESB Top new problems (last 7 days): Congrats, no problems in this section! Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. NoSuchMethodError in ESBProjectCorePlugin.start 5 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Unresolved: 3 ------------------------------------------------------------------------ Project Forge Tools Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. Throwable in AbstractCommand.handle 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. ResourceException below ProjectTools$1.runInWorkspace (thrown in Resource.delete) 16 New Major - 2. InvalidClassException below ForgeStarter.earlyStartup (thrown in ObjectStreamClass.initNonProxy) 6 New Major - 3. BadLocationException below DocumentImpl$3.run (thrown in AbstractDocument.replace) 5 New Major - 4. BadLocationException below DocumentImpl.getLineOfOffset (thrown in TreeLineTracker.fail) 4 New Major - 5. BadLocationException below DocumentImpl.getLineOffset (thrown in TreeLineTracker.fail) 4 New Major - 6. NullPointerException in WizardDialogHelper.openWizard 4 New Major - 7. StreamCorruptedException below ForgeStarter.earlyStartup (thrown in ObjectInputStream.readStreamHeader) 4 New Major - 8. LinkageError below ForgeStarter.earlyStartup (thrown in MavenPluginActivator.) 3 New Major - 9. IncompatibleClassChangeError below ForgeStarter.earlyStartup (thrown in MavenPluginActivator.) 2 New Major - 10. Throwable in AbstractCommand.handle 1 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Cannot Reproduce Bug: 1 Unresolved: 27 ------------------------------------------------------------------------ Project Hibernate Tools Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. ClassNotFoundException in ClassLoaderServiceImpl$AggregatedClassLoader.findClass 2 New Major - 2. ClassNotFoundException below HibernateJpaProject. (thrown in BundleLoader.findClassInternal) 1 New Major - 3. IllegalStateException below HibernateNature.getDefaultConsoleConfigurationName (thrown in EclipsePreferences.checkRemoved) 1 New Major - 4. NoClassDefFoundError below HibernateJpaProject. (thrown in EMFWorkbenchContext.createURIConverter) 1 New Major - 5. NoClassDefFoundError in TemplateHelper.setupContext 1 New Major - 6. NoSuchMethodError below Version. (thrown in SLF4JLocationAwareLog.info) 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. ClassNotFoundException below Util.invokeMethod (thrown in BundleLoader.findClassInternal) 107 New Major https://hibernate.atlassian.net/browse/HBX-1256 2. NullPointerException below HibernatePersistenceUnit.update (thrown in AttributeMapping$GeneratorsTransformer.transform) 95 New Major - 3. NullPointerException below HibernateJavaIdMappingImpl.update (thrown in AttributeMapping$KeyEquals.evaluate) 84 New Major - 4. NoStackTrace in BasicWorkbenchAdapter.handleError 73 New Major - 5. NullPointerException below HibernateJavaEntityImpl.validate (thrown in AttributeMapping$KeyEquals.evaluate) 68 New Major - 6. FileNotFoundException below HibernateJpaProject. (thrown in FileOutputStream.open0) 61 New Major - 7. ResourceException below HibernateEclipseUtils.getUserOverrideDefaultCatalog (thrown in Resource.checkExists) 61 New Major - 8. ResourceException below HibernateEclipseUtils.getUserOverrideDefaultSchema (thrown in Resource.checkExists) 61 New Major - 9. NoStackTrace in LazyDatabaseSchemaWorkbenchAdapter.getChildren 57 New Major - 10. NullPointerException below HibernateJpaProject.validate (thrown in AbstractJavaPersistentAttribute.getMappingKey) 53 New Major - 11. HibernateException in DialectFactoryImpl.determineDialect 50 New Major - 12. NoStackTrace in LazySessionFactoryAdapter.getChildren 47 New Major - 13. NullPointerException in ConfigurationActor.getService 47 New Major - 14. NullPointerException below HibernateJavaManyToOneMapping.update (thrown in AbstractJavaPersistentAttribute.getPrimaryKeyColumnName) 38 New Major - 15. NoStackTrace in HQLJavaCompletionProposalComputer.computeCompletionProposals 35 New Major - 16. NullPointerException in HibernateJpaProject.getBasicHibernateProperties 34 New Major - 17. NullPointerException below HibernateClassRef.synchronizeWithResourceModel (thrown in AbstractJavaPersistentAttribute.syncMapping) 31 New Major - 18. NoStackTrace in QueryPageViewer$ContentProviderImpl.getElements 30 New Major - 19. NullPointerException in AbstractQueryEditor.getQueryInputModel 28 New Major - 20. IllegalStateException in ConsoleConfigurationLaunchDelegate.launch 26 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Unresolved: 303 ------------------------------------------------------------------------ Project JBoss Central Top new problems (last 7 days): Congrats, no problems in this section! Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. IOException in CentralHelper.extractIfNeeded 169 Open Major JBIDE-22713 2. FileNotFoundException below BundleFamilyExtension.loadStream (thrown in HttpURLConnection.getInputStream0) 67 New Major - 3. NullPointerException below WizardSupport.openWizard (thrown in TextSearchControl.createLabelButtonControl) 19 Open Major JBIDE-22707 4. IOException below BundleFamilyExtension.loadStream (thrown in HttpURLConnection.getInputStream0) 10 New Major - 5. NoStackTrace in ConnectorDescriptorItemUi$6.run 9 New Major - 6. ProvisionException in InstallationChecker. 9 New Major - 7. IOException below BundleFamilyExtension.loadStream (thrown in HttpURLConnection.doTunneling) 5 New Major - 8. IllegalArgumentException below JBossCentralActivator.openJBossCentralEditor (thrown in ModelServiceImpl.findElementsRecursive) 4 New Major - 9. ProvisionException below P2CachedRepoUtil.getRepoForConnector (thrown in CacheManager.updateCache) 4 New Major - 10. HIDDEN below InstallationChecker. (thrown in AbstractSAXParser.parse) 2 New Major - 11. IllegalArgumentException below BundleFamilyExtension.loadBundleList (thrown in VersionRange.) 2 New Major - 12. NullPointerException in ConnectorDescriptorItemUi.resolveProfileUnits 2 New Major - 13. FileNotFoundException below CentralHelper.getLoadingPageUrl (thrown in FileOutputStream.open0) 1 New Major - 14. FileNotFoundException below UnArchiver.extract (thrown in FileOutputStream.open0) 1 New Major - 15. HIDDEN below DiscoveryViewer.getInstalledFeatures (thrown in AbstractSAXParser.parse) 1 New Major - 16. HIDDEN below P2CachedRepoUtil.getRepoForConnector (thrown in AbstractSAXParser.parse) 1 New Major - 17. NullPointerException in TextSearchControl.createLabelButtonControl 1 Open Major JBIDE-22890 Project Life-time Resolution Statistics Problem Resolutions Count Not JBoss: 2 Log Message: 9 Done: 8 Unresolved: 42 ------------------------------------------------------------------------ Project JBoss Server Tools Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. BackingStoreException below ChangeTimeStampActionDelegate.setModuleAndServer (thrown in ProjectPreferences.load) 1 New Major - 2. BadLocationException below RunServerActionDelegate.doRun (thrown in TreeLineTracker.fail) 1 New Major - 3. ClassCastException below Editor$Validator.run (thrown in ModuleStructuralModel.getPrimaryResource) 1 New Major - 4. ClassCastException below Editor.addProblemMarker (thrown in ModuleStructuralModel.getPrimaryResource) 1 New Major - 5. ClassCastException below FreemarkerMultiPageEditor.doSave (thrown in ModuleStructuralModel.getPrimaryResource) 1 New Major - 6. ClassNotFoundException below DownloadRuntimesProvider.getStacks (thrown in BundleLoader.findClassInternal) 1 New Major - 7. ClassNotFoundException below WorkspaceArchivesCore.createExtensionManager (thrown in BundleLoader.findClassInternal) 1 New Major - 8. CoreException in AbstractStartJavaServerLaunchDelegate.preLaunchCheck 1 New Major - 9. FileNotFoundException below ServerModelUtilities.getChildModules (thrown in FileInputStream.open) 1 New Major - 10. HIDDEN below ChangeTimeStampActionDelegate.setModuleAndServer (thrown in ErrorHandlerWrapper.createSAXParseException) 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. NoStackTrace in StandardLocalJBossStartLaunchDelegate.validateServerStructure 500+ New Major - 2. NoStackTrace in LocalLegacyShutdownController.addForceStopEvent 500+ New Major - 3. NoStackTrace in StandardFileSystemPublishController.removeModule 345 New Major - 4. FileNotFoundException below ServerModelUtilities.getChildModules (thrown in ZipFile.open) 284 New Major - 5. JBoss7ManangerException in Wildfly9Manager.execute 158 New Major - 6. DebugException below LocalLegacyShutdownController.forceStop (thrown in RuntimeProcess.terminate) 103 New Major - 7. NoStackTrace in UserPrompter.promptUser 87 New Major - 8. NoStackTrace in PollThread.alertEventLogTimeout 75 New Major - 9. NoStackTrace in ServerProfileModel.getController 61 New Major - 10. FileNotFoundException below ServerModelUtilities.getChildModules (thrown in JavaEEBinaryComponentLoadAdapter.physicallyOpen) 60 New Major - 11. IllegalStateException below ServerModelUtilities.getChildModules (thrown in DeadlockDetector.reportDeadlock) 57 New Major - 12. ZipException below ServerModelUtilities.getChildModules (thrown in ZipFile.open) 52 New Major - 13. JBoss7ManangerException in JBoss7ManagerServiceProxy.checkedGetService 50 New Major - 14. NoStackTrace in StandardFileSystemPublishController.handleZippedPublish 49 New Major - 15. NullPointerException in ControllableServerBehavior.setModulesStopped 43 New Major - 16. DebugException below AbstractStartJavaServerLaunchDelegate$2$1.run (thrown in RuntimeProcess.terminate) 41 New Major - 17. FileNotFoundException below FileUtil.writeTo (thrown in FileOutputStream.open0) 34 New Major - 18. NullPointerException in ModuleLaunchConfigurationProvider.supports 32 New Major - 19. ClassNotFoundException below AbstractJavaServerLaunchDelegate.fireVMRunner (thrown in BundleLoader.findClassInternal) 24 New Major - 20. FileNotFoundException below DriverUtility.createDriver2 (thrown in FileOutputStream.open0) 24 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Rejected: 4 Not JBoss: 6 Log Message: 5 Done: 1 Unresolved: 318 ------------------------------------------------------------------------ Project JBoss Tools Base Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. ClassNotFoundException below EclipseJavaUtil.findType (thrown in BundleLoader.findClassInternal) 1 New Major - 2. EOFException below ObjectMultiPageEditor.saveSelectedTab (thrown in DataInputStream.readByte) 1 New Major - 3. IllegalArgumentException below ChainTextHover.getHoverInfo2 (thrown in RegularExpressionLiteral.setRegularExpression) 1 New Major - 4. JavaModelException below EclipseJavaUtil.findAnnotationsByShortName (thrown in JavaElement.newNotPresentException) 1 New Major - 5. JavaModelException below JavaAnnotation.getMemberValuePairs (thrown in JavaElement.newJavaModelException) 1 New Major - 6. JavaModelException below TypeInfoCollector.getProperties (thrown in JavaElement.newNotPresentException) 1 New Major - 7. NoClassDefFoundError in JandexUtil.hasAnnotation 1 New Major - 8. NullPointerException below DecoratorPreferencesPage.createContents (thrown in TabFolder.gtk_switch_page) 1 New Major - 9. NullPointerException below EclipseJavaUtil.findType (thrown in MavenClasspathVariableInitializer.initialize) 1 New Major - 10. NullPointerException below EclipseUtil.getJavaSourceRoots (thrown in MavenClasspathContainerInitializer.getBuildPathManager) 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. ResourceException below TempMarkerManager$1.runInUIThread (thrown in Marker.checkInfo) 251 Open Major JBIDE-22891 2. ZipException below JarAccess.getContent (thrown in ZipFile.read) 140 Open Major JBIDE-22897 3. Exception in Tools.findFirstValidVMInstall 73 New Major - 4. NullPointerException below JavaDirtyRegionProcessor.isJavaElementValidationRequired (thrown in BasicFeatureMap.isEmpty) 73 New Major - 5. CoreException below ChainTextHover.getHoverInfo2 (thrown in FaceletTagRegistry.initialize) 71 New Major - 6. IllegalStateException in SProperties.get 71 New Major - 7. BadLocationException below JavaDirtyRegionProcessor.isJavaElementValidationRequired (thrown in AbstractDocument.computePartitioning) 66 New Major - 8. NullPointerException below JavaDirtyRegionProcessor.isJavaElementValidationRequired (thrown in BasicFeatureMap.remove) 57 New Major - 9. NoStackTrace below EclipseJavaUtil.findType (thrown in JarPackageFragmentRoot.computeChildren) 51 New Major - 10. ResourceException below FolderImpl.update (thrown in WorkManager.checkIn) 48 New Major - 11. FileNotFoundException below ChainTextHover.getHoverInfo2 (thrown in FileInputStream.open0) 47 New Major - 12. ClassNotFoundException below Tools.invokeGetMonitoredHost (thrown in URLClassLoader.findClass) 41 New Major - 13. JavaModelException below EclipseResourceUtil.getSourceFolders (thrown in JavaElement.newJavaModelException) 40 New Major - 14. NullPointerException in EclipseResourceUtil.createObjectForResource 39 New Major - 15. NullPointerException below JavaDirtyRegionProcessor.isJavaElementValidationRequired (thrown in BasicFeatureMap$FeatureEIterator.scanNext) 37 New Major - 16. ZipException below JandexUtil.createJarIndex (thrown in ZipFile.open) 37 New Major - 17. ResourceException below FolderImpl.update (thrown in FileSystemResourceManager.refreshResource) 36 New Major - 18. NullPointerException in FileUtil.getContentFromEditorOrFile 35 New Major - 19. ResourceException below FileSystemImpl.getResource (thrown in WorkManager.checkIn) 35 New Major - 20. JavaModelException below ValueResolver$ReferenceResolver.connect (thrown in JavaModelOperation.runOperation) 33 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Rejected: 1 Won't Do: 1 Cannot Reproduce Bug: 1 Not JBoss: 2 Log Message: 10 Done: 5 Unresolved: 411 ------------------------------------------------------------------------ Project Java Server Faces Top new problems (last 7 days): Congrats, no problems in this section! Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. NullPointerException in JSFProjectsTree.getProjectsRoot 42 Open Major JBIDE-22910 2. Exception below RenameMethodParticipant$RenameMethodSearcher.outOfSynch (thrown in Thread.getStackTrace) 13 Coding In Progress Major JBIDE-22911 3. NullPointerException in JSFPromptingProvider.getVariables 9 New Major - 4. NullPointerException in JSFPaletteViewerPreferences. 6 New Major - 5. NullPointerException in JsfJSPTagNameHyperlink.openJSF2Component