From jmaury at redhat.com Wed Mar 1 03:14:06 2017 From: jmaury at redhat.com (Jean-Francois Maury) Date: Wed, 1 Mar 2017 09:14:06 +0100 Subject: [jbosstools-dev] Versions bump policy change In-Reply-To: References: <6134BAA9-C3F5-46B7-9E40-27C761DBFC99@redhat.com>

Message-ID: On Wed, Mar 1, 2017 at 12:16 AM, Max Rydahl Andersen wrote: > On 28 Feb 2017, at 21:42, Mickael Istria wrote: > > > On 02/28/2017 07:24 PM, Max Rydahl Andersen wrote: > >> sounds awesome if you guys found a way to deal with having to > >> manually eep these from not overlapping and avoid rerelasing > >> different bits with the same version number. > > This was: > > * https://issues.jboss.org/browse/JBIDE-13671 > > * https://issues.jboss.org/browse/JBIDE-19056 > > * https://issues.jboss.org/browse/JBIDE-22689 > > none of these seem to be new ? these was what was fixe ages ago. > > So the version changes provides no benefits and becomes harder to keep > track on ? > > Before it could be done more or less automated. Just thought it was > changing because you guys found a benefit to do so. > No, just to lower the load during updates. It is now possible because less components are being changed now (mainly OpenShift; server and base) > > >> Will this mean that builds and release now only update the actual > >> changed plugins ? > Yes > >> and download diff will be smaller too ? > Yes > > At least, the build infrastructure makes it possible and safe to > > update plugins only when necessary, with the benefit mentioned above > > (among others) > > So is that a yes or no ? > > >> btw. how come stopping to do the 3.3.0, 3.3.100 etc. as is standard > >> in > >> p2/eclipse ? > > This versioning pattern is only useful if JBoss Tools properly manages > > API versions and relies on API tools for guidance and checks. Last > > time I heard about it, it was far from being the case. > > Not really, it is to allow updates by us or others in both branches > without colliding in p2 updates without having to rely on the fragile > date/timestamp pattern. > > API versioning was secondary concern here. > > /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/20170301/758a4fb8/attachment-0001.html From manderse at redhat.com Wed Mar 1 05:19:07 2017 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 01 Mar 2017 11:19:07 +0100 Subject: [jbosstools-dev] Versions bump policy change In-Reply-To: References: <6134BAA9-C3F5-46B7-9E40-27C761DBFC99@redhat.com>

Message-ID: <2E3738C1-F95A-485F-A97D-E24F4071E6B6@redhat.com> On 1 Mar 2017, at 9:14, Jean-Francois Maury wrote: > On Wed, Mar 1, 2017 at 12:16 AM, Max Rydahl Andersen > > wrote: > >> On 28 Feb 2017, at 21:42, Mickael Istria wrote: >> >>> On 02/28/2017 07:24 PM, Max Rydahl Andersen wrote: >>>> sounds awesome if you guys found a way to deal with having to >>>> manually eep these from not overlapping and avoid rerelasing >>>> different bits with the same version number. >>> This was: >>> * https://issues.jboss.org/browse/JBIDE-13671 >>> * https://issues.jboss.org/browse/JBIDE-19056 >>> * https://issues.jboss.org/browse/JBIDE-22689 >> >> none of these seem to be new ? these was what was fixe ages ago. >> >> So the version changes provides no benefits and becomes harder to >> keep >> track on ? >> >> Before it could be done more or less automated. Just thought it was >> changing because you guys found a benefit to do so. >> > No, just to lower the load during updates. It is now possible because > less > components are being changed now (mainly OpenShift; server and base) But that is cool. Just curious what happens in this case: Today I download and install latest server tools i.e. version 4.3.0 Tomorrow you release a new update to openshift tools i.e. version 3.4.1 I do check for updates - get nothing (as expected) Next week I install into a new jboss server tools ...do I get the exact same bits as the one I downloaded a week ago ? or is this a new set of binaries just with the same 4.3.0 number ? /max http://about.me/maxandersen From mistria at redhat.com Wed Mar 1 05:22:37 2017 From: mistria at redhat.com (Mickael Istria) Date: Wed, 1 Mar 2017 11:22:37 +0100 Subject: [jbosstools-dev] Versions bump policy change In-Reply-To: <2E3738C1-F95A-485F-A97D-E24F4071E6B6@redhat.com> References: <6134BAA9-C3F5-46B7-9E40-27C761DBFC99@redhat.com>

<2E3738C1-F95A-485F-A97D-E24F4071E6B6@redhat.com> Message-ID: On 03/01/2017 11:19 AM, Max Rydahl Andersen wrote: > Next week I install into a new jboss server tools ...do I get the > exact same bits as the one I downloaded a week ago ? or is this a new > set of binaries just with the same 4.3.0 number ? With https://issues.jboss.org/browse/JBIDE-22689 and https://issues.jboss.org/browse/JBIDE-19056, it's the same bits. -- Mickael Istria Eclipse developer for Red Hat Developers My blog - My Tweets -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20170301/f36a3df0/attachment.html From manderse at redhat.com Wed Mar 1 05:27:17 2017 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 01 Mar 2017 11:27:17 +0100 Subject: [jbosstools-dev] Versions bump policy change In-Reply-To: References: <6134BAA9-C3F5-46B7-9E40-27C761DBFC99@redhat.com>

<2E3738C1-F95A-485F-A97D-E24F4071E6B6@redhat.com> Message-ID: <977F7EF7-5E41-4E61-B092-2EFE7144079E@redhat.com> On 1 Mar 2017, at 11:22, Mickael Istria wrote: > On 03/01/2017 11:19 AM, Max Rydahl Andersen wrote: >> Next week I install into a new jboss server tools ...do I get the >> exact same bits as the one I downloaded a week ago ? or is this a new >> set of binaries just with the same 4.3.0 number ? > > With https://issues.jboss.org/browse/JBIDE-22689 and > https://issues.jboss.org/browse/JBIDE-19056, it's the same bits. cool - so we are comparing them for binary equivalency before releasing ? nice. I thought our builds that timestamps and maven properties that gets added that makes every build slightly different. You guys removed that ? If yes Awesome. If no - then I reckon those mojos would be failing and if not then that seems to be a bug ;) Thus next step would to add a filter for publish so we actually only upload diffs but thats a trickier one to solve due to p2 metadata files. This is awesome if you get it done. Good work! /max http://about.me/maxandersen From mmalina at redhat.com Wed Mar 1 08:14:42 2017 From: mmalina at redhat.com (Martin Malina) Date: Wed, 1 Mar 2017 14:14:42 +0100 Subject: [jbosstools-dev] FYI: parent pom releases this week: 4.4.3.Final and 4.3.2.Final In-Reply-To: References: Message-ID: <4404A072-C6BE-481F-8AC4-37A34087CFC8@redhat.com> I tried to run a test on the jbosstools-4.4.3.Final tag of jbosstools-server and it fails, because the pom still points to 4.4.3.Final-SNAPSHOT parent pom. This is understandable. But could we perhaps do the parent pom release before the tagging and have the released version in the tag next time, please? Right now my only option is probably make this change in 4.4.3.x and use that. -Martin > On 24 Feb 2017, at 22:51, Nick Boldt wrote: > > Recently, the Integration Stack guys requested that we start releasing > parent poms. > > So, today, the 4.4.3.Final parent pom has been released [1]. > > [1] https://repository.jboss.org/nexus/#nexus-search;gav~org.jboss.tools~parent~4.*.*.Final~~ > > I also released 4.3.2.Final [1] parent pom as I was testing some > automation / scripting of nexus staging and release steps. I can now > do a release to Nexus completely from a Jenkins job, without having to > do any manual steps. \0/ > > If you depend on either the 4.3.2.Final-SNAPSHOT or the > 4.4.3.Final-SNAPSHOT parent poms, please update your root poms > accordingly (to remove "-SNAPSHOT") as Nexus will purge the snapshots > soon. > > For more on this, see: https://issues.jboss.org/browse/JBIDE-23768 > > -- > 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 nboldt at redhat.com Wed Mar 1 13:29:51 2017 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 1 Mar 2017 13:29:51 -0500 Subject: [jbosstools-dev] FYI: parent pom releases this week: 4.4.3.Final and 4.3.2.Final In-Reply-To: <4404A072-C6BE-481F-8AC4-37A34087CFC8@redhat.com> References: <4404A072-C6BE-481F-8AC4-37A34087CFC8@redhat.com> Message-ID: We could move the tag(s) too, if you need. That's easy enough and while it doesn't 100% depict reality to say that the build used the 4.4.3.Final parent pom, rather than the 4.4.3.Final-SNAPSHOT one, it does make reproducibility easier. But since it's HIGHLY unlikely we'll be rebuilding 4.4.3.x when we have a 4.4.4.AM1 release coming up in a mere 13 days, I wouldn't worry too much about it. Do please document process snafus in JIRA so that we can achieve a better workflow for future releases. Thanks, Nick On Wed, Mar 1, 2017 at 8:14 AM, Martin Malina wrote: > I tried to run a test on the jbosstools-4.4.3.Final tag of jbosstools-server and it fails, because the pom still points to 4.4.3.Final-SNAPSHOT parent pom. > This is understandable. But could we perhaps do the parent pom release before the tagging and have the released version in the tag next time, please? > Right now my only option is probably make this change in 4.4.3.x and use that. > > > -Martin > > >> On 24 Feb 2017, at 22:51, Nick Boldt wrote: >> >> Recently, the Integration Stack guys requested that we start releasing >> parent poms. >> >> So, today, the 4.4.3.Final parent pom has been released [1]. >> >> [1] https://repository.jboss.org/nexus/#nexus-search;gav~org.jboss.tools~parent~4.*.*.Final~~ >> >> I also released 4.3.2.Final [1] parent pom as I was testing some >> automation / scripting of nexus staging and release steps. I can now >> do a release to Nexus completely from a Jenkins job, without having to >> do any manual steps. \0/ >> >> If you depend on either the 4.3.2.Final-SNAPSHOT or the >> 4.4.3.Final-SNAPSHOT parent poms, please update your root poms >> accordingly (to remove "-SNAPSHOT") as Nexus will purge the snapshots >> soon. >> >> For more on this, see: https://issues.jboss.org/browse/JBIDE-23768 >> >> -- >> 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 > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From nboldt at redhat.com Wed Mar 1 16:01:01 2017 From: nboldt at redhat.com (Nick Boldt) Date: Wed, 1 Mar 2017 16:01:01 -0500 Subject: [jbosstools-dev] FYI: The latest proposed schedule for Eclipse Oxygen (2017-2018) and Photon (2018-2019) Message-ID: Here's the latest proposal from the Planning Council on the Oxygen and Photon (Oxygen+1) releases. Note that there's still some contention around doing an Oxygen.0a "JDK 9 Update" release in July, but it's sounding like the foundation wants one, so there will be one. It might be simply an update to platform/JDT/webtools, or it might be bigger. https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg02690.html https://wiki.eclipse.org/Planning_Council/March_01_2017 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From manderse at redhat.com Wed Mar 1 17:59:58 2017 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 01 Mar 2017 23:59:58 +0100 Subject: [jbosstools-dev] FYI: The latest proposed schedule for Eclipse Oxygen (2017-2018) and Photon (2018-2019) In-Reply-To: References: Message-ID: <8C252008-A559-45F0-860A-1C311D4FBB8E@redhat.com> Last time we had a major JDK update - webtools and m2e was not updated if we (especially Fred Bricon) hadn't stepped up to do last minute fixes. You should push for all kinds of options to get enough JDK 9 API' exposed so those changes can be done sooner rather than later. /max > Here's the latest proposal from the Planning Council on the Oxygen and > Photon (Oxygen+1) releases. > > Note that there's still some contention around doing an Oxygen.0a "JDK > 9 Update" release in July, but it's sounding like the foundation wants > one, so there will be one. It might be simply an update to > platform/JDT/webtools, or it might be bigger. > > https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg02690.html > https://wiki.eclipse.org/Planning_Council/March_01_2017 > > -- > 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 gorkem.ercan at gmail.com Wed Mar 1 20:50:55 2017 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Wed, 01 Mar 2017 20:50:55 -0500 Subject: [jbosstools-dev] FYI: The latest proposed schedule for Eclipse Oxygen (2017-2018) and Photon (2018-2019) In-Reply-To: <8C252008-A559-45F0-860A-1C311D4FBB8E@redhat.com> References: <8C252008-A559-45F0-860A-1C311D4FBB8E@redhat.com> Message-ID: <90DE6377-D613-4CBC-B2B8-8C3528994944@gmail.com> If interested on some early testing Java 9 support is available on the marketplace https://marketplace.eclipse.org/content/java-9-support-beta-oxygen On 1 Mar 2017, at 17:59, Max Rydahl Andersen wrote: > Last time we had a major JDK update - webtools and m2e was not updated > if we (especially Fred Bricon) hadn't stepped up to do last minute > fixes. You should push for all kinds of options to get enough JDK 9 > API' > exposed so those changes can be done sooner rather than later. > > /max > >> Here's the latest proposal from the Planning Council on the Oxygen >> and >> Photon (Oxygen+1) releases. >> >> Note that there's still some contention around doing an Oxygen.0a >> "JDK >> 9 Update" release in July, but it's sounding like the foundation >> wants >> one, so there will be one. It might be simply an update to >> platform/JDT/webtools, or it might be bigger. >> >> https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg02690.html >> https://wiki.eclipse.org/Planning_Council/March_01_2017 >> >> -- >> 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 > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev From manderse at redhat.com Thu Mar 2 02:52:47 2017 From: manderse at redhat.com (Max Andersen) Date: Thu, 2 Mar 2017 08:52:47 +0100 Subject: [jbosstools-dev] FYI: The latest proposed schedule for Eclipse Oxygen (2017-2018) and Photon (2018-2019) In-Reply-To: <90DE6377-D613-4CBC-B2B8-8C3528994944@gmail.com> References: <8C252008-A559-45F0-860A-1C311D4FBB8E@redhat.com> <90DE6377-D613-4CBC-B2B8-8C3528994944@gmail.com> Message-ID: <194AD4FD-0839-4939-BD97-723A6D8E104D@redhat.com> I'm interested in that the apis needed to define a JDK9 gets added so plugins can actually refer to them. M2e uses that for example to map maven to/from jdt settings and launches. But Fred should know the details and if situation is same as last time. Note: this all happens because of a legal "glitch" where implementors of a JDK Cannot call itself a Java before the main JDK is released and after that point any betas need to be removed. It's annoying. /max http://about.me/maxandersen > On 2 Mar 2017, at 02:50, Gorkem Ercan wrote: > > > If interested on some early testing Java 9 support is available on the marketplace > https://marketplace.eclipse.org/content/java-9-support-beta-oxygen > > >> On 1 Mar 2017, at 17:59, Max Rydahl Andersen wrote: >> >> Last time we had a major JDK update - webtools and m2e was not updated >> if we (especially Fred Bricon) hadn't stepped up to do last minute >> fixes. You should push for all kinds of options to get enough JDK 9 API' >> exposed so those changes can be done sooner rather than later. >> >> /max >> >>> Here's the latest proposal from the Planning Council on the Oxygen and >>> Photon (Oxygen+1) releases. >>> >>> Note that there's still some contention around doing an Oxygen.0a "JDK >>> 9 Update" release in July, but it's sounding like the foundation wants >>> one, so there will be one. It might be simply an update to >>> platform/JDT/webtools, or it might be bigger. >>> >>> https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg02690.html >>> https://wiki.eclipse.org/Planning_Council/March_01_2017 >>> >>> -- >>> 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 >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev From nboldt at redhat.com Thu Mar 2 11:36:22 2017 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 2 Mar 2017 11:36:22 -0500 Subject: [jbosstools-dev] ACTION REQUIRED: broken builds in 4.4.x branch Message-ID: Just a reminder that if you're getting notifications from Jenkins that your build is red, *you need to take ownership* of that and solve the issue. You should be seeing the same build problems locally, so it's easy enough to increment your plugins and features to x.y.(z+1) to resolve the baseline comparison check failure. If the problem is/was some cryptic error about source features finding the wrong version of source plugin, that should be fixed after moving from Tycho 0.26 -> Tycho 1.0. Ref: https://issues.jboss.org/browse/JBIDE-23212 If you need help, feel free to ping me. Note that I'm on PTO from Mar 3-12, so the window for help is closing soon. :D Cheers, Nick On Thu, Feb 23, 2017 at 2:43 PM, Nick Boldt wrote: > Since QE signed off on the 4.4.3.Final/10.3.0.GA bits a couple days > ago, the _4.4.neon and _10.0.neon jobs are now being run against the > jbosstools-4.4.x branches. > > These jobs are for now using the Neon.2 target platform > (4.62.0.Final), but will be updated to Neon.3 once RC4 is available in > a couple weeks. > > Should you need us to move up faster to Neon.3, please ask for such a > change here: > > https://issues.jboss.org/browse/JBIDE-23963 > > Jobs can be found here: > > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devstudio_10.0.neon/ > > -- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20170302/51b63107/attachment.html From aer-bot at ctrlflow.com Sun Mar 5 21:30:01 2017 From: aer-bot at ctrlflow.com (Ctrlflow AER Bot) Date: Mon, 6 Mar 2017 03:30:01 +0100 (CET) Subject: [jbosstools-dev] [aeri] Weekly JBoss Tools Error Reports Digest Message-ID: <59496954.77.1488767401347.JavaMail.root@Debian-84-jessie-64-minimal> ------------------------------------------------------------------------ Project Central, Maven, Livereload & Webservices Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. IOException below DiscoveryViewer.getInstalledFeatures (thrown in SimpleProfileRegistry$Parser.parse) 1 New Major - 2. IllegalArgumentException below DiscoveryViewer.computeIconImage (thrown in DPIUtil.validateAndGetImagePathAtZoom) 1 New Major - 3. IllegalArgumentException below JBossWSRuntimeConfigBlock.validateandDisplayTargetRuntime (thrown in ResourceManager.getRuntime) 1 New Major - 4. NullPointerException below EndorsedLibProjectConfigurator.configure (thrown in JavaModelListener.isInClasspath) 1 New Major - 5. NullPointerException in JAXRSWSTestView2.getOpNameFromRequestBody 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. IOException in CentralHelper.extractIfNeeded 284 Open Major JBIDE-22713 2. NoStackTrace below ProxyWizardManager.loadWizards (thrown in ChainedDiscoveryStrategy.performDiscovery) 214 Open Major JBIDE-22893 3. FileNotFoundException below BundleFamilyExtension.loadStream (thrown in HttpURLConnection.getInputStream0) 156 New Major - 4. ConcurrentModificationException below JaxrsMetamodel.getProblemSeverity (thrown in HashMap$HashIterator.nextNode) 102 Open Major JBIDE-22331 5. NullPointerException in JaxrsMarkerResolutionGenerator.findJaxrsElement 82 Open Major JBIDE-22335 6. NullPointerException below SocketProposalComputer.computeCompletionProposals (thrown in BasicFeatureMap.remove) 77 Open Major JBIDE-22337 7. NullPointerException in JaxRsConfigurator.canConfigure 72 New Major - 8. NullPointerException below SocketProposalComputer.computeCompletionProposals (thrown in BasicFeatureMap.contains) 71 Open Major JBIDE-22338 9. JavaModelException below AttachSourcesActionDelegate.setActiveEditor (thrown in JavaElement.newJavaModelException) 65 Open Major JBIDE-22815 10. ConcurrentModificationException below JaxrsMetamodel.getAllEndpoints (thrown in HashMap$HashIterator.nextNode) 63 Open Major JBIDE-22345 11. CoreException below ArchetypeExamplesWizardPage.downloadArchetype (thrown in MavenImpl$5.call) 48 New Major - 12. JavaModelException below JdtUtils.resolveType (thrown in JavaElement.newJavaModelException) 45 Open Major JBIDE-22332 13. NoStackTrace below ProxyWizardManager.getDiscoveryUrl (thrown in DiscoveryActivator.getJBossDiscoveryDirectory) 45 New Major - 14. ProvisionException in InstallationChecker. 36 New Major - 15. HIDDEN below WtpUtils.evaluateXPathExpression (thrown in DOMParser.parse) 33 Open Major JBIDE-22333 16. CoreException below AnnotationProcessingSettingsPage$3.runInWorkspace (thrown in FacetedProject.modifyInternal) 31 New Major - 17. CoreException below ArchetypeExamplesWizardPage$4$1.call (thrown in MavenImpl$5.call) 31 New Major - 18. ResourceException below JaxrsMetamodelValidator.removeMarkers (thrown in Resource.checkExists) 30 Open Major JBIDE-22339 19. NoStackTrace below JdtUtils.resolveType (thrown in JarPackageFragmentRoot.computeChildren) 24 New Major - 20. NullPointerException in JdtUtils.findSubtypes 20 Open Major JBIDE-22334 Project Life-time Resolution Statistics Problem Resolutions Count Out of Date: 1 Rejected: 1 Not JBoss: 4 Log Message: 13 Done: 10 Unresolved: 266 ------------------------------------------------------------------------ Project Forge Tools Top new problems (last 7 days): Congrats, no problems in this section! Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. RuntimeException in SelectGraphicRendition.handleDefault 13 New Major - 2. InvalidClassException below ForgeStarter.earlyStartup (thrown in ObjectStreamClass.initNonProxy) 11 New Major - 3. BuildException below ForgeWizard$1.run (thrown in MavenProjectBuilder.build) 8 New Major - 4. Throwable in AbstractCommand.handle 8 New Major - 5. LinkageError below ForgeStarter.earlyStartup (thrown in MavenPluginActivator.) 3 New Major - 6. SWTException below ForgeUIProvider.err (thrown in Widget.checkWidget) 2 New Major - 7. CoreException below ProjectTools$1.runInWorkspace (thrown in WithExpression.evaluate) 1 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Cannot Reproduce Bug: 1 Not JBoss: 2 Done: 1 Unresolved: 48 ------------------------------------------------------------------------ Project Hibernate Tools Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. AnnotationException in CollectionBinder.getCollectionBinder 1 New Major - 2. IllegalArgumentException below AbstractTypeFactoryFacade.initializeTypeFormats (thrown in Currency.getInstance) 1 New Major - 3. NullPointerException below ConnectionProfileCtrl.getProfileNameList (thrown in ConnectionProfileMgmt.readCPsFromXML1_0) 1 New Major - 4. NullPointerException below GenericGeneratorsComposite.buildAddGenericGeneratorDialog (thrown in Dialog.) 1 New Major - 5. NullPointerException below HibernateJptPlugin$2.run (thrown in ItemTreeStateProviderManager.remove) 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. NullPointerException below HibernateJavaIdMappingImpl.update (thrown in AttributeMapping$KeyEquals.evaluate) 136 New Major - 2. NullPointerException below HibernatePersistenceUnit.update (thrown in AttributeMapping$GeneratorsTransformer.transform) 131 New Major - 3. HibernateException in DialectFactoryImpl.determineDialect 120 New Major - 4. NullPointerException below HibernateJavaEntityImpl.validate (thrown in AttributeMapping$KeyEquals.evaluate) 97 New Major - 5. NoStackTrace in BasicWorkbenchAdapter.handleError 85 New Major - 6. NoStackTrace in LazyDatabaseSchemaWorkbenchAdapter.getChildren 69 New Major - 7. NullPointerException below HibernateJpaProject.validate (thrown in AbstractJavaPersistentAttribute.getMappingKey) 69 New Major - 8. ResourceException below HibernateEclipseUtils.getUserOverrideDefaultSchema (thrown in Resource.checkExists) 61 New Major - 9. NullPointerException below HibernateJavaManyToOneMapping.update (thrown in AbstractJavaPersistentAttribute.getPrimaryKeyColumnName) 57 New Major - 10. ResourceException below HibernateEclipseUtils.getUserOverrideDefaultCatalog (thrown in Resource.checkExists) 53 New Major - 11. NoStackTrace in LazySessionFactoryAdapter.getChildren 47 New Major - 12. NoStackTrace in QueryPageViewer$ContentProviderImpl.getElements 46 New Major - 13. NullPointerException below HibernateClassRef.synchronizeWithResourceModel (thrown in AbstractJavaPersistentAttribute.syncMapping) 46 New Major - 14. FileNotFoundException below HibernateJpaProject. (thrown in FileOutputStream.open0) 44 New Major - 15. NullPointerException in AbstractQueryEditor.getQueryInputModel 43 New Major - 16. NullPointerException in HibernateJpaProject.getBasicHibernateProperties 41 New Major - 17. NoStackTrace in HQLJavaCompletionProposalComputer.computeCompletionProposals 39 New Major - 18. ResourceException below HibernateJpaProject. (thrown in FileSystemResourceManager.read) 35 New Major - 19. AbortCompilation below HibernateJpaProject. (thrown in ProblemHandler.handle) 34 New Major - 20. FileNotFoundException below HibernateJpaProject. (thrown in FileInputStream.open0) 30 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Won't Fix: 1 Not JBoss: 3 Done: 3 Unresolved: 317 ------------------------------------------------------------------------ Project Integration Stack Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. CoreException below BasicProjectCreator.create (thrown in LocalFile.checkTargetIsNotWritable) 1 New Major - 2. DebugException below CamelDebugUtils.getRawCamelContextFilePathFromLaunchConfig (thrown in LaunchManager.createDebugException) 1 New Major - 3. NullPointerException in SwitchYardCustomTaskFeatureContainer.isSwitchYardProject 1 New Major - 4. ResourceException below CamelFilesFinder.isFuseCamelContentType (thrown in Resource.checkLocal) 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. NullPointerException in UpdateCommand.updateFigure 39 Open Major FUSETOOLS-1831 2. NullPointerException in KarafJMXPublisher.publish 23 New Major - 3. Exception in ReteViewer.loadReteModel 19 New Major - 4. Throwable in AbstractRuntimeManager.recognizeJars 19 New Major - 5. NullPointerException in DiagramOperations.layoutDiagram 18 New Major - 6. ConnectException below KarafJMXPublisher.connect (thrown in DualStackPlainSocketImpl.connect0) 16 New Major - 7. JavaModelException below CamelComponentUtils.getComponentClass (thrown in JavaElement.newNotPresentException) 16 New Major - 8. Exception in CamelDebugTarget$JMXConnectJob.run 14 New Major - 9. JavaModelException below CamelComponentUtils.getComponentJSon (thrown in JavaElement.newNotPresentException) 14 New Major - 10. NullPointerException in UpdateNodeFeature.updateNeeded 14 New Major - 11. ClassNotFoundException below KarafBundleMBeanPublishBehaviour.installBundle (thrown in LoaderHandler.loadClass) 13 New Major - 12. ResourceException below CamelEditor.doSave (thrown in File.getContentDescription) 13 Open Major FUSETOOLS-1980 13. ClassCastException in LayoutDiagramFeature.mapDiagramToGraph 12 New Major - 14. NoStackTrace in Karaf2xPublishController.transferBuiltModule 12 New Major - 15. NullPointerException in KarafJMXPublisher.uninstall 11 New Major - 16. NullPointerException in CamelEditor$4.run 10 New Major - 17. ResourceException below JavaCamelFilesFinder.findJavaDSLRouteBuilderClass (thrown in Project$1.run) 10 New Major - 18. NullPointerException in Karaf2xPublishController.getModuleVersion 9 New Major - 19. ZipException below CamelComponentUtils.getComponentClass (thrown in ZipFile.open) 9 New Major - 20. ConnectException below KarafJMXPublisher.connect (thrown in PlainSocketImpl.socketConnect) 8 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Out of Date: 1 Won't Fix: 1 Won't Do: 1 Log Message: 10 Done: 20 Unresolved: 305 Duplicate: 1 ------------------------------------------------------------------------ Project Java EE Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. ClassFormatError below JSF2ProjectBuilder$JSF2ResourceVisitor.visit (thrown in CompilationUnit.getImportContainer) 1 New Major - 2. NoStackTrace below JSF2ProjectBuilder.buildJars (thrown in JarPackageFragmentRoot.computeChildren) 1 New Major - 3. NullPointerException below CDIProjectAsYouType.findCompilationUnit (thrown in EjbJarMerger.isEnterpriseBeansTagPresent) 1 New Major - 4. NullPointerException in DeltaspikeExceptionExtension.validateResource 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. JavaModelException below FileSet.checkType (thrown in JavaElement.newNotPresentException) 168 Open Major JBIDE-22285 2. JavaModelException below BeanArchiveDetector.isAnnotatedBean (thrown in JavaElement.newNotPresentException) 86 Open Major JBIDE-22900 3. IllegalStateException in SProperties.get 76 Open Major JBIDE-23052 4. ConcurrentModificationException below CDIProjectAsYouType.findCompilationUnit (thrown in FeatureMapUtil$BasicFeatureEIterator.checkModCount) 59 Open Major JBIDE-22905 5. NoStackTrace in CDICoreValidator.init 52 Open Major JBIDE-22904 6. NullPointerException in JSFProjectsTree.getProjectsRoot 51 Open Major JBIDE-22910 7. ClassCastException below BeanArchiveDetector.isAnnotatedBean (thrown in BinaryType.getAnnotations) 16 New Major - 8. NullPointerException in JSFPromptingProvider.getVariables 15 New Major - 9. ZipException below FileSet.checkType (thrown in ZipFile.read) 13 New Major - 10. ZipException below FileSet.checkType (thrown in ZipFile.read) 12 New Major - 11. BasicIndexOutOfBoundsException below CDIProjectAsYouType.findCompilationUnit (thrown in BasicEList.remove) 9 New Major - 12. JavaModelException below AbstractMemberDefinition.init (thrown in JavaElement.newJavaModelException) 9 New Major - 13. JavaModelException below AbstractMemberDefinition.init (thrown in JavaElement.newNotPresentException) 9 New Major - 14. JavaModelException below AuthorizerHyperlinkDetector.detectHyperlinks (thrown in JavaElement.newNotPresentException) 9 New Major - 15. NullPointerException in CDICoreBuilder$PackageInfo. 7 New Major - 16. NullPointerException in JSFPaletteViewerPreferences. 7 New Major - 17. ZipException below BeanArchiveDetector.isAnnotatedBean (thrown in ZipFile.read) 7 New Major - 18. AssertionFailedException below CDIProjectAsYouType.findCompilationUnit (thrown in DefaultJavaFoldingStructureProvider.computeCurrentStructure) 6 New Major - 19. JavaModelException below BeanMember.getTypeDeclaration (thrown in JavaElement.newJavaModelException) 6 New Major - 20. NullPointerException in CDICoreValidator.init 6 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Out of Date: 1 Rejected: 2 Duplicate Issue: 1 Not JBoss: 1 Log Message: 12 Done: 9 Unresolved: 195 ------------------------------------------------------------------------ Project JBoss Server Tools Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. AntSecurityException below ShowConsoleServerStateListener$1$1.run (thrown in AntSecurityManager.checkPermission) 1 New Major - 2. CoreException below SingleDeployableFactory$UndeployFromServerJob.run (thrown in WorkingCopyHelper.validateTimestamp) 1 New Major - 3. FileNotFoundException below EarArtifactAdapter.getArtifactFor (thrown in JavaEEBinaryComponentLoadAdapter.physicallyOpen) 1 New Major - 4. FileNotFoundException below WorkspaceArchivesCore.createNodeFactory (thrown in FileInputStream.open0) 1 New Major - 5. IndexOutOfBoundsException below ModuleResourceUtil.getResources (thrown in BufferedInputStream.read) 1 New Major - 6. NullPointerException below ClassCollectingHCRListener.removeBreakpoints (thrown in JavaBreakpoint.isExpired) 1 New Major - 7. NullPointerException in ShowInWelcomePageActionProvider$1$1$1.run 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. NoStackTrace in StandardFileSystemPublishController.markModulePublished 431 New Major - 2. JBoss7ManangerException in Wildfly9Manager.execute 247 Open Major JBIDE-23288 3. Exception in LocalFilesystemController.deleteResource 237 New Major - 4. NoStackTrace in ServerProfileModel.getController 121 Open Major JBIDE-23289 5. NoStackTrace in StandardFileSystemPublishController.removeModule 116 New Major - 6. NoStackTrace in UserPrompter.promptUser 113 New Major - 7. JBoss7ManangerException in JBoss7ManagerServiceProxy.checkedGetService 87 New Major - 8. IllegalStateException below ServerModelUtilities.getChildModules (thrown in DeadlockDetector.reportDeadlock) 86 New Major - 9. Exception in LocalFilesystemController.deleteDirectory 80 New Major - 10. FileNotFoundException below FileUtil.writeTo (thrown in FileOutputStream.open0) 64 New Major - 11. NoStackTrace in JBoss70ConnectionProvider$ExtendedDefaultConnectionWrapper.serverChanged 44 New Major - 12. NoStackTrace in StandardFileSystemPublishController.handleZippedPublish 44 New Major - 13. JBoss7ManangerException in EAP61PlusManager.execute 42 New Major - 14. CoreException in LocalFilesystemController.touchResource 33 New Major - 15. NotOpenException below ClassCollectingHCRListener$1.run (thrown in RemoteConnectionChannel.openOutboundMessage) 33 New Major - 16. FileNotFoundException below AbstractDeploymentScannerAdditions.getDeployLocationFolders (thrown in EMF2DOMSSERenderer.initializeXMLModel) 27 New Major - 17. NoStackTrace in ManagementPublishController.publishModule 25 New Major - 18. IndexOutOfBoundsException below ModuleResourceUtil.getMembers (thrown in BufferedInputStream.read) 22 New Major - 19. NoStackTrace below ChangeTimeStampActionDelegate.setModuleAndServer (thrown in ProblemLog.reportMissingFacet) 21 New Major - 20. NoStackTrace in JBossServer.findPort 21 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Out of Date: 2 Rejected: 9 Won't Fix: 1 Not JBoss: 11 Log Message: 19 Done: 13 Unresolved: 393 ------------------------------------------------------------------------ Project JBoss Tools Base Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. ClassNotFoundException below JandexUtil.hasAnnotation (thrown in BundleLoader.findClassInternal) 1 New Major - 2. NoClassDefFoundError in JandexUtil.hasAnnotation 1 New Major - 3. NullPointerException below EclipseResourceUtil$LibraryCollector.process (thrown in SystemLibrariesSetting.getSourcePath) 1 New Major - 4. NullPointerException below EclipseUtil.addNatureToProject (thrown in ItemTreeStateProviderManager.getChildren) 1 New Major - 5. NullPointerException below JavaDirtyRegionProcessor.isJavaElementValidationRequired (thrown in EJBAnnotationReader.processAddedInterface) 1 New Major - 6. NullPointerException below ValueResolver$ReferenceResolver.dispose (thrown in JavaModelListener.isInClasspath) 1 New Major - 7. NullPointerException in JarAccess.getMain 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. ResourceException below TempMarkerManager$1.runInUIThread (thrown in Marker.checkInfo) 228 Open Major JBIDE-22891 2. NoStackTrace below EclipseJavaUtil.findType (thrown in JarPackageFragmentRoot.computeChildren) 137 New Major - 3. ResourceException below FolderImpl.update (thrown in WorkManager.checkIn) 100 New Major - 4. JavaModelException below BeanArchiveDetector.isAnnotatedBean (thrown in JavaElement.newNotPresentException) 86 Open Major JBIDE-22900 5. ZipException below JandexUtil.createJarIndex (thrown in ZipFile.open) 85 New Major - 6. IllegalStateException in SProperties.get 76 Open Major JBIDE-23052 7. JavaModelException below ValueResolver$ReferenceResolver.connect (thrown in JavaModelOperation.runOperation) 70 New Major - 8. NullPointerException in FileUtil.getContentFromEditorOrFile 68 New Major - 9. CoreException below ChainTextHover.getHoverInfo2 (thrown in FaceletTagRegistry.initialize) 66 Open Major JBIDE-23051 10. ConcurrentModificationException below CDIProjectAsYouType.findCompilationUnit (thrown in FeatureMapUtil$BasicFeatureEIterator.checkModCount) 59 Open Major JBIDE-22905 11. FileNotFoundException below ChainTextHover.getHoverInfo2 (thrown in FileInputStream.open0) 58 New Major - 12. NullPointerException below JavaDirtyRegionProcessor.isJavaElementValidationRequired (thrown in BasicFeatureMap$FeatureEIterator.scanNext) 54 New Major - 13. ResourceException below FolderImpl.update (thrown in FileSystemResourceManager.refreshResource) 54 New Major - 14. NoStackTrace in CDICoreValidator.init 52 Open Major JBIDE-22904 15. NoStackTrace below EclipseFileBodySource.write (thrown in AbstractMergedModelProvider.getMergedModel) 51 New Major - 16. JavaModelException below EclipseResourceUtil.getSourceFolders (thrown in JavaElement.newJavaModelException) 49 New Major - 17. IllegalArgumentException below EclipseUtil.getCompilationUnit (thrown in PackageFragment.getCompilationUnit) 42 New Major - 18. ResourceException below FileSystemImpl.getResource (thrown in WorkManager.checkIn) 40 New Major - 19. ClassNotFoundException below Tools.invokeGetMonitoredHost (thrown in URLClassLoader.findClass) 35 New Major - 20. ResourceException below EclipseResourceUtil.getModelNature (thrown in Resource.checkExists) 34 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Out of Date: 1 Rejected: 2 Won't Do: 1 Cannot Reproduce Bug: 1 Not JBoss: 6 Log Message: 11 Done: 11 Unresolved: 486 ------------------------------------------------------------------------ Project OpenShift Top new problems (last 7 days): Congrats, no problems in this section! Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. AssertionFailedException in ExpressServerUtils.getDefaultDeployFolder 10 New Major - 2. TeamException below EGitUtils.isShared (thrown in RepositoryProvider.mapNewProvider) 10 New Major - 3. OpenShiftNotReadyPollingException in VagrantPoller.checkOpenShiftHealth 3 New Major - 4. CoreException in VagrantPoller.createErrorStatus 1 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Rejected: 2 Won't Fix: 1 Cannot Reproduce: 3 Not JBoss: 7 Log Message: 1 Done: 9 Unresolved: 39 ------------------------------------------------------------------------ Project Unkown JBoss Project Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. BackingStoreException below UsageReportPreferencesUtils.checkedSavePreferences (thrown in EclipsePreferences.write) 1 New Major - 2. Error below ProtocolConnectionUtils.isLocal (thrown in NetworkInterface.getByInetAddress0) 1 New Major - 3. FileNotFoundException below UsageReportPreferencesUtils.checkedSavePreferences (thrown in FileInputStream.open0) 1 New Major - 4. IOException below PrepareInstallProfileJob.addRepositories (thrown in SimpleProfileRegistry$Parser.parse) 1 New Major - 5. IOException below PrepareInstallProfileJob.resolveInstall (thrown in SimpleProfileRegistry$Parser.parse) 1 New Major - 6. IOException in AbstractMessageHandler.handleChannelClosed 1 New Major - 7. IllegalArgumentException below PrepareInstallProfileJob.resolveInstall (thrown in ProfileChangeRequest.createByProfileId) 1 New Major - 8. NoStackTrace below MavenProjectConfigurator$UpdateMavenConfigurationJob.run (thrown in JarPackageFragmentRoot.computeChildren) 1 New Major - 9. NoStackTrace in JBossDiscoveryUi.resolveToConnectors 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. CoreException below RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call (thrown in RepositoryStatusHelper.wrap) 231 Open Major JBDS-3987 2. ZipException below Indexer.verifyMagic (thrown in ZipFile.read) 193 New Major - 3. NoStackTrace below PrepareInstallProfileJob.openInstallWizard (thrown in ProvUI.reportStatus) 63 New Major - 4. XMLStreamException below JaxbParser.unmarshall (thrown in XMLStreamReaderImpl.next) 54 New Major - 5. IllegalStateException in Indexer.processConstantPool 53 New Major - 6. FileNotFoundException below EventRegister.saveProperties (thrown in FileOutputStream.open0) 38 New Major - 7. EOFException below Indexer.processConstantPool (thrown in ZipFile$ZipFileInflaterInputStream.fill) 30 New Major - 8. NullPointerException in NewProjectExamplesReadyPage.configure 30 New Major - 9. CancellationException in AsyncFutureTask.operationCancelled 21 New Major - 10. InstanceNotFoundException in BasicMBeanRegistry.get 18 New Major - 11. RuntimeException in RemotingConnector.connect 16 New Major - 12. NoStackTrace in FinalizeRuntimeDownloadFragment.openErrorMessage 15 New Major - 13. NoStackTrace in HttpRemotePropertiesProvider.logStatusCode 15 New Major - 14. IllegalStateException in WizardCommandControllerImpl.addNextFlowStep 13 New Major - 15. IllegalArgumentException below ProjectExampleUtil.getProjectExamplesFile (thrown in File.setLastModified) 11 New Major - 16. ResourceException below ArquillianProjectConfigurator.configureInternal (thrown in Project.checkAccessible) 10 Open Major JBIDE-22720 17. ClassCastException below SeamEarProjectValidator.validateInJob (thrown in ModuleStructuralModel.getPrimaryResource) 9 New Major - 18. IllegalStateException in MavenProjectConfigurator$CumulativeMappingDiscoveryJob.addProjects 8 New Major - 19. NullPointerException in RuntimePathPreferenceIO.loadRuntimePathsFromPreferenceString 8 New Major - 20. NoSuchMethodError in RequirementModelUtil.createServerRuntimeRequirement 7 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Duplicate Issue: 1 Won't Do: 1 Cannot Reproduce Bug: 1 Not JBoss: 4 Log Message: 8 Done: 9 Unresolved: 206 ------------------------------------------------------------------------ Project VPE & Mobile Top new problems (last 7 days): Summary Reporters Status Severity Bug 1. NoClassDefFoundError below WebNatureOperation.createWTPNature2 (thrown in ModuleCoreNature.createURIConverter) 1 New Major - 2. NoSuchMethodError in TernValidationHelper.validate 1 New Major - 3. NullPointerException below PageContextFactory.createPageContext (thrown in File.) 1 New Major - 4. NullPointerException below PageContextFactory.fillContextForChildNodes (thrown in NodeContainer$ChildNodesCache.item) 1 New Major - 5. NullPointerException below WebNatureOperation.createWTPNature2 (thrown in WorkbenchURIConverterImpl.) 1 New Major - 6. NullPointerException in ServerCreator.createServer 1 New Major - Top unresolved, active problems (last month): Summary Reporters Status Severity Bug 1. XulRunnerBundleNotFoundException in XulRunnerBrowser.getXulRunnerPath 500+ Open Major JBIDE-22960 2. TernException in NodejsTernHelper.makeRequest 340 Open Major JBIDE-22892 3. ResourceException below IDETernProject.getTernProject (thrown in Project.checkAccessible) 268 Open Major JBIDE-22894 4. JavaModelException below FileSet.checkType (thrown in JavaElement.newNotPresentException) 168 Open Major JBIDE-22285 5. NullPointerException in TernOutlineContentProvider.dispose 145 New Major - 6. NullPointerException in MyEclipseResourcesDelegatingManager.init 141 New Major - 7. NodejsProcessException in AbstractNodejsProcess.waitOnStartNodejs 111 New Major - 8. TernException in NodejsTernServer.makeRequest 105 New Major - 9. CoreException below PageContextFactory.getConnectedDocument (thrown in ResourceFileBuffer.create) 97 New Major - 10. StructuredDocumentRegionManagementException below JSPTextEditor$JSPStructuredTextViewer.doOperation (thrown in XMLModelParser.removeStructuredDocumentRegion) 82 Open Major JBIDE-22961 11. IOException below JSPTextEditor$JSPStructuredTextViewer.doOperation (thrown in ResourceBundleMapSource.createCachedBundleFile) 81 New Major - 12. IllegalStateException in SProperties.get 76 Open Major JBIDE-23052 13. ConcurrentModificationException below TernFileSynchronizer.ensureSynchronized (thrown in ArrayList$Itr.checkForComodification) 72 New Major - 14. Exception in IDETernFileUploader.serverToBeDisposed 67 New Major - 15. ResourceException below KbBuilderMarker.getOwnedMarkers (thrown in Marker.checkInfo) 62 New Major - 16. IllegalArgumentException below MozillaEditor.dispose (thrown in ListenerList.remove) 49 Open Major JBIDE-22921 17. ResourceException below StorageRevisionEditorInputAdapter$StorageAdapter.getContents (thrown in Resource.checkExists) 47 New Major - 18. ResourceException below IDETernFile.getContents (thrown in FileSystemResourceManager.read) 40 New Major - 19. TernException in TernExceptionFactory.create 37 New Major - 20. IllegalStateException below JSPTextEditor.createPartControl (thrown in EclipsePreferences.checkRemoved) 33 New Major - Project Life-time Resolution Statistics Problem Resolutions Count Undefined: 1 Rejected: 1 Log Message: 15 Done: 8 Unresolved: 341 -- You are receiving this email because you are subscribed to digest of All JBoss Tools Projects. To alter your subscriptions, contact your administrator. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20170306/0033b345/attachment-0001.html From dbocharo at redhat.com Mon Mar 6 08:02:47 2017 From: dbocharo at redhat.com (Dmitrii Bocharov) Date: Mon, 6 Mar 2017 14:02:47 +0100 Subject: [jbosstools-dev] Link from Ctrlflow AER Bot mail to aer.ctrlflow.com doesn't work Message-ID: Hi, Marcel! I have a problem when going through a link from an email by Ctrlflow AER Bot to aer.ctrlflow.com. Say, i'm already logged in to aer.ctrlflow.com with my Github account. Now i'm clicking the link from the mail. A new tab is opened in browser (e.g. https://aer.ctrlflow.com/redhat/reviewers/#!/problems/58b80248e4b069efe534fc2d). But nothing is displayed, just an error message - see the attached image. Then i go directly to https://aer.ctrlflow.com/redhat/reporters. And put issue id (58b80248e4b069efe534fc2d) into the problem id field and press Go and the page displays fine. It's very uncomfortable to always go to the search page and paste in the issue id. What can be the problem? Best regards, Dmitrii -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20170306/dce03712/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ctrlflow_no_access.png Type: image/png Size: 39641 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20170306/dce03712/attachment-0001.png From marcel.bruch at codetrails.com Mon Mar 6 08:25:55 2017 From: marcel.bruch at codetrails.com (Marcel Bruch) Date: Mon, 6 Mar 2017 14:25:55 +0100 Subject: [jbosstools-dev] Link from Ctrlflow AER Bot mail to aer.ctrlflow.com doesn't work In-Reply-To: References: Message-ID: <9FE4309D-A193-492B-B926-62DD0DD63712@codetrails.com> Hi Dmitrii, > It's very uncomfortable to always go to the search page and paste in the issue id. true. > What can be the problem? The reason why you get the permission denied view is that you only have reporter permissions but need reviewer access rights for that url. The links in the emails go to the separate reviewer interface. The search interface you are referring to is the reporters user interface (which only gives limited access to the details of the error reports - no comments, no messages etc.) but does not require any login. If you are a committer on Redhat?s, Jeff can give you the required permissions (I mailed him about a similar case this morning) in the web ui to fix that. HTH. Cheers, Marcel P.S.: We may merge both URLs into one. But that?s something I have to discuss with Jeff before. > On 06 Mar 2017, at 14:02, Dmitrii Bocharov wrote: > > Hi, Marcel! > > I have a problem when going through a link from an email by Ctrlflow AER Bot to aer.ctrlflow.com . > Say, i'm already logged in to aer.ctrlflow.com with my Github account. Now i'm clicking the link from the mail. A new tab is opened in browser (e.g. https://aer.ctrlflow.com/redhat/reviewers/#!/problems/58b80248e4b069efe534fc2d ). But nothing is displayed, just an error message - see the attached image. > Then i go directly to https://aer.ctrlflow.com/redhat/reporters . And put issue id (58b80248e4b069efe534fc2d) into the problem id field and press Go and the page displays fine. > > It's very uncomfortable to always go to the search page and paste in the issue id. What can be the problem? > > Best regards, > Dmitrii > -- 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/20170306/ef67ca78/attachment.html From mat.booth at redhat.com Thu Mar 9 07:50:35 2017 From: mat.booth at redhat.com (Mat Booth) Date: Thu, 9 Mar 2017 12:50:35 +0000 Subject: [jbosstools-dev] ACTION REQUIRED: broken build in 4.4.x branch Message-ID: It looks like a last minute change went in and broke the jbosstools-forge_4.4.neon build: https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/devstudio_10.0.neon/job/jbosstools-forge_4.4.neon/ The error is: [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.forge.runtime: Only qualifier changed for (org.jboss.tools.forge.runtime/2.0.103.v20170308-2246). Expected to have bigger x.y.z than what is available in baseline (2.0.103.v20170213-1751) This usually means that a change was made to a bundle without bumping it's version. If the change was a bug fix, the most likely correct course of action is bump the "service" portion of the version to "x.y.z+1" This blocks the AM1 staging process, so please resolve as soon as possible. Thanks, Mat -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20170309/897d8810/attachment.html From jmaury at redhat.com Thu Mar 9 07:55:02 2017 From: jmaury at redhat.com (Jean-Francois Maury) Date: Thu, 9 Mar 2017 13:55:02 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: broken build in 4.4.x branch In-Reply-To: References: Message-ID: I'm on it; let you know when this is fixed. Jeff On Thu, Mar 9, 2017 at 1:50 PM, Mat Booth wrote: > It looks like a last minute change went in and broke the > jbosstools-forge_4.4.neon build: > > https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/ > view/DevStudio/view/devstudio_10.0.neon/job/jbosstools-forge_4.4.neon/ > > The error is: > > [ERROR] Failed to execute goal org.eclipse.tycho.extras: > tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on > project org.jboss.tools.forge.runtime: Only qualifier changed for > (org.jboss.tools.forge.runtime/2.0.103.v20170308-2246). Expected to have > bigger x.y.z than what is available in baseline (2.0.103.v20170213-1751) > > This usually means that a change was made to a bundle without bumping it's > version. If the change was a bug fix, the most likely correct course of > action is bump the "service" portion of the version to "x.y.z+1" > > This blocks the AM1 staging process, so please resolve as soon as possible. > > Thanks, > Mat > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20170309/6887ca3a/attachment.html From mat.booth at redhat.com Thu Mar 9 08:09:43 2017 From: mat.booth at redhat.com (Mat Booth) Date: Thu, 9 Mar 2017 13:09:43 +0000 Subject: [jbosstools-dev] ACTION REQUIRED: Triage 183 unresolved issues for 4.4.4.AM1 / 10.4.0.AM1 Message-ID: There are currently 183 unresolved issues for 4.4.4.AM1 / 10.4.0.AM1 https://issues.jboss.org/issues?jql=project%20in%20(JBIDE%2C%20JBDS)%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(%2212333594%22%2C%20%2212333593%22) If these issues are not yet resolved, please move them to a future milestone. Thanks, Mat -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20170309/2631f570/attachment.html From jmaury at redhat.com Thu Mar 9 08:54:48 2017 From: jmaury at redhat.com (Jean-Francois Maury) Date: Thu, 9 Mar 2017 14:54:48 +0100 Subject: [jbosstools-dev] ACTION REQUIRED: broken build in 4.4.x branch In-Reply-To: References:

Message-ID: OK I bumped the versions in 4.4.x. However, I can't check on my local laptop as I got an error processing addons (and the PR check has the same). Jeff On Thu, Mar 9, 2017 at 2:10 PM, Mat Booth wrote: > Thanks! > > > On 9 March 2017 at 12:55, Jean-Francois Maury wrote: > >> I'm on it; let you know when this is fixed. >> >> Jeff >> >> On Thu, Mar 9, 2017 at 1:50 PM, Mat Booth wrote: >> >>> It looks like a last minute change went in and broke the >>> jbosstools-forge_4.4.neon build: >>> >>> https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/De >>> vStudio/view/devstudio_10.0.neon/job/jbosstools-forge_4.4.neon/ >>> >>> The error is: >>> >>> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho >>> -p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on >>> project org.jboss.tools.forge.runtime: Only qualifier changed for >>> (org.jboss.tools.forge.runtime/2.0.103.v20170308-2246). Expected to >>> have bigger x.y.z than what is available in baseline >>> (2.0.103.v20170213-1751) >>> >>> This usually means that a change was made to a bundle without bumping >>> it's version. If the change was a bug fix, the most likely correct course >>> of action is bump the "service" portion of the version to "x.y.z+1" >>> >>> This blocks the AM1 staging process, so please resolve as soon as >>> possible. >>> >>> Thanks, >>> Mat >>> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20170309/112dc8af/attachment-0001.html From ggastald at redhat.com Thu Mar 9 09:18:10 2017 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 9 Mar 2017 11:18:10 -0300 Subject: [jbosstools-dev] ACTION REQUIRED: broken build in 4.4.x branch In-Reply-To: References:

Message-ID: Hi Jean, What is the error you get? I'll try to reproduce locally Em 9 de mar de 2017 10:56, "Jean-Francois Maury" escreveu: > OK I bumped the versions in 4.4.x. > However, I can't check on my local laptop as I got an error processing > addons (and the PR check has the same). > > Jeff > > > On Thu, Mar 9, 2017 at 2:10 PM, Mat Booth wrote: > >> Thanks! >> >> >> On 9 March 2017 at 12:55, Jean-Francois Maury