December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-19941) Create a JUnit integration test for o.j.t.foundation.checkup plugin to cover the case if Eclipse log message about unsupported JVM is changed

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19941?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19941: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > Create a JUnit integration test for o.j.t.foundation.checkup plugin to cover the case if Eclipse log message about unsupported JVM is changed > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19941 > URL: https://issues.jboss.org/browse/JBIDE-19941 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Fix For: 4.3.x > > > Currently we don't test any real eclipse errors. It would be useful to have an integration test which will help us to be aware if Eclipse change the format of such errors in log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11338) JBoss AS 7.0.2 do not start when Java Agent is run and throws log error with JVM 6 update 15 and above

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11338?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-11338: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > JBoss AS 7.0.2 do not start when Java Agent is run and throws log error with JVM 6 update 15 and above > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-11338 > URL: https://issues.jboss.org/browse/JBIDE-11338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: profiler > Affects Versions: LATER > Reporter: Ramesh Pa > Assignee: Jeff MAURY > Priority: Blocker > Labels: JBoss > Fix For: LATER > > > Workaround as below is also not working. > set JAVA_OPTS= %JAVA_OPTS% -Xbootclasspath/p:C:\jboss-6.1.0.Final\lib\jboss-logmanager.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger .pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl > No issues with JVM 6 update 14 and earlier. > Error message > INFO: 801. Dummy Java Agent:: Transformer to Transform Class: java/lang/ExceptionInInitializerError > Exception in thread "main" java.lang.ExceptionInInitializerError > at org.jboss.as.server.Main.main(Main.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.modules.Module.run(Module.java:272) > at org.jboss.modules.Main.main(Main.java:313) > Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system proper > ty to "org.jboss.logmanager.LogManager") > at org.jboss.logmanager.Logger.getLogger(Logger.java:60) > at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42) > ... 7 more -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6343) Create a "sanity check plugin/feature" tool for running on integration builds

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6343?page=com.atlassian.jira.plugin... ] Alexey Kazakov reassigned JBIDE-6343: ------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > Create a "sanity check plugin/feature" tool for running on integration builds > ----------------------------------------------------------------------------- > > Key: JBIDE-6343 > URL: https://issues.jboss.org/browse/JBIDE-6343 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Priority: Minor > Fix For: LATER > > > I keep seeing the following antipatterns or oversights happening in our codebase, most of them I believe we could mechanically check for. > No duplicate names in .project since it makes it impossible to import into Eclipse > bin folders should be svn:ignored and not be committed (causes problems when doing svn synchronization and all the .class files are showing up and some even commits it) > things in svn:ignore should be committed (either someone overrode svn:ignore or the svn:ignore were added later) > if pom.xml file exists target should be svn:ignored too. > Execution environment should be specified in manifest.mf's -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9356) NLS.bind vs MessageFormat.format

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9356?page=com.atlassian.jira.plugin... ] Alexey Kazakov reassigned JBIDE-9356: ------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > NLS.bind vs MessageFormat.format > -------------------------------- > > Key: JBIDE-9356 > URL: https://issues.jboss.org/browse/JBIDE-9356 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cleanup > Affects Versions: 3.3.0.M3 > Reporter: Rob Stryker > Assignee: Jeff MAURY > Fix For: 4.0.x > > > A substantial number of classes use NLS.bind(Messages.SomeString, name) to bind message strings. Another subset of the classes use MessageFormat.format(etc). > I believe NLS.bind() is the correct solution which works properly with eclipse osgi and all that jazz. Should this be standardized? Is it confusing to be using two interchangable APIs? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11527) JSF project created with JBoss AS 7.1.1 has lot of warnings

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11527?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-11527: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > JSF project created with JBoss AS 7.1.1 has lot of warnings > ----------------------------------------------------------- > > Key: JBIDE-11527 > URL: https://issues.jboss.org/browse/JBIDE-11527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 3.3.0.Beta3 > Environment: Linux 32bit, JBT 3.3.0.v20120412-0201-H4578-Beta3, JBoss AS 7.1.1. Final > Reporter: Vlado Pakan > Assignee: Jeff MAURY > Fix For: LATER > > Attachments: noWarningIcon.png > > > 1. Create JSF 1.2 KickStart project with JBoss AS 7.1.1 Runtime > ERROR: There is lot of warnings after project is created and workspace is built. Both web pages created within project has warnings but do not have warning decorators in package explorer: > !noWarningIcon.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1504) allow users to create cases from JBDS

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-1504?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-1504: ------------------------------------ Assignee: Jeff MAURY (was: Alexey Kazakov) > allow users to create cases from JBDS > ------------------------------------- > > Key: JBDS-1504 > URL: https://issues.jboss.org/browse/JBDS-1504 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: integration > Environment: All > Reporter: Andrew Hecox > Assignee: Jeff MAURY > Fix For: LATER > > > user-story: as a JBoss customer, I can create a case with support from JBDS so that I can easily get help solving the problem I'm working on in my editor > notes: I think something which allowed a user to create a problem description, as well as send any applicable files, would be a good value add to JBDS. We have a public, stable, API for this: > https://access.redhat.com/knowledge/docs/Red_Hat_Customer_Portal/ > we may deprecate some schema items in the next month or two, but otherwise it's locked in place for the next 7+ years. This functionality presumably would only be in the productized version, unless it was replaced with JIRA integration (or comparable) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18899) symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18899?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18899: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18899 > URL: https://issues.jboss.org/browse/JBIDE-18899 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.2.1.CR1 > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Fix For: 4.2.x > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ says last folder published is B14 but http://download.jboss.org/jbosstools/updates/nightly/luna/compositeArtifa... contains the following: > {{{ > <?compositeArtifactRepository version='1.0.0'?><repository name="JBoss Tools Builds - builds/nightly/core/4.2.luna" type="org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository" version="1.0.0"><properties size="2"><property name="p2.timestamp" value="1417970049000"/><property name="p2.compressed" value="true"/></properties><children size="9"> > <child location="2014-12-06_19-43-15-B315/all/repo/"/> > <child location="2014-12-06_01-42-39-B314/all/repo/"/> > <child location="2014-12-05_16-52-33-B313/all/repo/"/><child location="2014-12-05_13-48-06-B312/all/repo/"/><child location="2014-12-04_19-55-14-B311/all/repo/"/><child location="2014-12-04_14-48-07-B310/all/repo/"/><child location="2014-12-03_17-44-02-B309/all/repo/"/><child location="2014-12-02_13-44-05-B308/all/repo/"/><child location="2014-12-01_16-57-02-B307/all/repo/"/></children></repository> > }}} > Indicating that http://download.jboss.org/jbosstools/updates/nightly/luna/2014-12-06_19-4... should exist - but it does not. > I assume this is due to a nightly being used for publishing results to staging - thus it might just be cleanup step that is missing ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13226) "Marker Not Found" error messages appeare in As-You-Type validation

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13226?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-13226: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > "Marker Not Found" error messages appeare in As-You-Type validation > ------------------------------------------------------------------- > > Key: JBIDE-13226 > URL: https://issues.jboss.org/browse/JBIDE-13226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, common, jsf > Affects Versions: 4.1.x > Environment: JBT 4.1.0.Alpha1 > Reporter: Victor Rubezhny > Assignee: Jeff MAURY > Priority: Minor > Fix For: LATER > > > Steps to reproduce: > EXECUTE: Open in Java Editor some Java class from a project with CDI Capabilities enabled > EXECUTE: Make sure or add some CDI Problem on that file, save and wait for the build is finished. > ASSERT: There is a CDI Problem marker in Probems View. > EXECUTE: Type some text into the file due to make it "dirty". > EXECUTE: Remove CDI Capabilities from the project. > EXECUTE: Add CDI Capabilities back to the project. > ASSERT: There are no exceptions/error messages like "Marker not found" logged (FAIL) > {code} > !ENTRY org.jboss.tools.common 4 0 2012-12-03 19:51:09.134 > !MESSAGE Marker id 14549 not found. > !STACK 1 > org.eclipse.core.internal.resources.ResourceException: Marker id 14549 not found. > at org.eclipse.core.internal.resources.Marker.checkInfo(Marker.java:57) > at org.eclipse.core.internal.resources.Marker.getType(Marker.java:195) > at org.jboss.tools.common.validation.TempMarkerManager$1.runInUIThread(TempMarkerManager.java:286) > at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3529) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3182) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) > at org.eclipse.equinox.launcher.Main.run(Main.java:1438) > at org.eclipse.equinox.launcher.Main.main(Main.java:1414) > !SUBENTRY 1 org.eclipse.core.resources 4 376 2012-12-03 19:51:09.135 > !MESSAGE Marker id 14549 not found. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13748) Create a Run As... GWT Development Mode

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13748?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-13748: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > Create a Run As... GWT Development Mode > --------------------------------------- > > Key: JBIDE-13748 > URL: https://issues.jboss.org/browse/JBIDE-13748 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: gwt > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Fix For: LATER > > > Create a LaunchShortCut as outlined on https://github.com/maxandersen/gwt-launcher/wiki/Run-As...GWT-Development... > Plugin and feature should have *zero* compile/install dependency on GPE/GWT plugin. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16906) Track successful/unsuccessful installations from JBoss Central

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16906?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-16906: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > Track successful/unsuccessful installations from JBoss Central > -------------------------------------------------------------- > > Key: JBIDE-16906 > URL: https://issues.jboss.org/browse/JBIDE-16906 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Affects Versions: 4.2.0.Beta1 > Reporter: Radim Hopp > Assignee: Jeff MAURY > Labels: new_and_noteworthy > Fix For: LATER > > > In JBDS-2732 Alexey said "It seems there is not a good way to track successful installations from central." > I've created this issue in case somebody found a way to track this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016