April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23275) Rename doesn't change fully qualified name in job.xml file

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23275?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23275: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Rename doesn't change fully qualified name in job.xml file > ---------------------------------------------------------- > > Key: JBIDE-23275 > URL: https://issues.jboss.org/browse/JBIDE-23275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.2.AM1 > Environment: Fedora 24 > Reporter: Lukáš Valach > Fix For: 4.6.x > > Attachments: BatchRenameManualTest.zip > > > Refactoring doesn't modify job.xml when I renaming class which is referred in job.xml using the fully qualified name. > For example, when I have batchlet class > {code:java} > package test; > public class BatchletWithProperty extends AbstractBatchlet { > ... > } > {code} > ...and job.xml > {code:xml} > <job ...> > <step id="step1"> > <batchlet ref="test.BatchletWithProperty">  > ... > </batchlet> > </step> > ... > </job> > {code} > ...then, when I try to rename test.BatchletWithProperty the refactoring doesn't change fully qualified name in job.xml. > Renaming works properly when I refer to class using name coming from @Named annotation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22631) FreeMarker Editor regression or configuration question

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22631?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22631: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > FreeMarker Editor regression or configuration question > ------------------------------------------------------ > > Key: JBIDE-22631 > URL: https://issues.jboss.org/browse/JBIDE-22631 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Environment: Windows 7 > Reporter: Paul Verest > Fix For: 4.6.x > > Attachments: FMEditorWithTextMate.png, freemarker-editor.PNG > > > As initially raised at https://github.com/jbosstools/jbosstools-freemarker/issues/59 > latest FreeMarker Editor plugin (v of 2016) appear less functional than v of 2009, e.g. only highlight for freemarker syntax, but not any HTML support. > Both where installed in recent Eclipse Mars. > Or possibly something should be configured for FreeMarker Editor to support HTML editing as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24969) Add platform events to usage reporting

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24969?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24969: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Add platform events to usage reporting > -------------------------------------- > > Key: JBIDE-24969 > URL: https://issues.jboss.org/browse/JBIDE-24969 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: usage > Affects Versions: 4.5.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: usage > Fix For: 4.6.x > > > In addition to the jbosstools events reported, we should benefits from the events emitted by the Eclipse platform and send them to the usage reporting feature. > Those events may be: > * perspective events > * view events > * editor events > * menu events -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22416) Plugins dependency conflict when importing JavaEE7 Sample

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22416?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22416: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Plugins dependency conflict when importing JavaEE7 Sample > --------------------------------------------------------- > > Key: JBIDE-22416 > URL: https://issues.jboss.org/browse/JBIDE-22416 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples, upstream > Affects Versions: 4.4.0.Alpha1 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160520-0424-B5396 > Build date: 20160520-0424 > Reporter: Josef Kopriva > Assignee: Fred Bricon > Fix For: 4.6.x > > Attachments: import_issue.png > > > When I import JavaEE7 sample sample extra/spock-tests, I cannot install plugin due to plugin conflict issue. > {code:java} > Cannot complete the install because of a conflicting dependency. > Software being installed: Groovy-Eclipse M2E integration 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.m2eclipse.feature.feature.group 2.9.2.xx-201604081629-e45) > Software currently installed: Red Hat Developer Studio (Branded Product) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.package 10.0.0.Alpha1-v20160520-0424-B5396) > Software currently installed: TestNG 6.9.11.201604020423 (org.testng.eclipse.feature.group 6.9.11.201604020423) > Only one of the following can be installed at once: > Java Development Tools Core 3.12.0.v20160426-1326 (org.eclipse.jdt.core 3.12.0.v20160426-1326) > Java Development Tools Core 3.11.0.xx-201604081629-e45 (org.eclipse.jdt.core 3.11.0.xx-201604081629-e45) > Cannot satisfy dependency: > From: Red Hat Developer Studio (Core Features) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.feature.feature.group 10.0.0.Alpha1-v20160520-0424-B5396) > To: org.eclipse.jdt.feature.group 0.0.0 > Cannot satisfy dependency: > From: Red Hat Developer Studio (Branded Product) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.package 10.0.0.Alpha1-v20160520-0424-B5396) > To: com.jboss.devstudio.core.feature.feature.group [10.0.0.Alpha1-v20160520-0424-B5396] > Cannot satisfy dependency: > From: Groovy-Eclipse Compilerless Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.compilerless.feature.feature.group 2.9.2.xx-201604081629-e45) > To: org.codehaus.groovy.headless.feature.feature.group [2.9.2.xx-201604081629-e45] > Cannot satisfy dependency: > From: Groovy-Eclipse Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.eclipse.feature.feature.group 2.9.2.xx-201604081629-e45) > To: org.codehaus.groovy.compilerless.feature.feature.group [2.9.2.xx-201604081629-e45] > Cannot satisfy dependency: > From: Groovy-Eclipse Headless Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.headless.feature.feature.group 2.9.2.xx-201604081629-e45) > To: org.codehaus.groovy.jdt.patch.feature.group [2.9.2.xx-201604081629-e45] > Cannot satisfy dependency: > From: Groovy-Eclipse M2E integration 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.m2eclipse.feature.feature.group 2.9.2.xx-201604081629-e45) > To: org.codehaus.groovy.eclipse.feature.feature.group 0.0.0 > Cannot satisfy dependency: > From: Java Development Tools JUnit support 3.9.0.v20160421-1701 (org.eclipse.jdt.junit 3.9.0.v20160421-1701) > To: bundle org.eclipse.jdt.core [3.12.0,4.0.0) > Cannot satisfy dependency: > From: TestNG Eclipse Support 6.9.11.201604020423 (org.testng.eclipse 6.9.11.201604020423) > To: bundle org.eclipse.jdt.junit 0.0.0 > Cannot satisfy dependency: > From: TestNG 6.9.11.201604020423 (org.testng.eclipse.feature.group 6.9.11.201604020423) > To: org.testng.eclipse [6.9.11.201604020423] > Cannot satisfy dependency: > From Patch: org.codehaus.groovy.jdt.patch.feature.group 2.9.2.xx-201604081629-e45 Eclipse Java Development Tools 3.12.0.v20160428-0800 (org.eclipse.jdt.feature.group 3.12.0.v20160428-0800) > To: org.eclipse.jdt.core [3.11.0.xx-201604081629-e45] > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6554) Export configuration to orm.xml file

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6554?page=com.atlassian.jira.plugin... ] Jeff MAURY updated JBIDE-6554: ------------------------------ Fix Version/s: 4.6.x (was: 4.5.x) > Export configuration to orm.xml file > ------------------------------------ > > Key: JBIDE-6554 > URL: https://issues.jboss.org/browse/JBIDE-6554 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 3.1.1 > Reporter: Dmitry Geraskov > Assignee: Koen Aers > Labels: new_and_noteworthy > Fix For: 4.6.x > > > Need to create exporter and templates to export orm.xml like hbm files are exported now. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23003) NullPointerException below DependencyCache.getDependentTypes (thrown in AbstractCollection.addAll)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23003?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23003: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > NullPointerException below DependencyCache.getDependentTypes (thrown in AbstractCollection.addAll) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23003 > URL: https://issues.jboss.org/browse/JBIDE-23003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.4.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Snjezana Peco > Fix For: 4.6.x > > > The following problem was reported via the automated error reporting: > Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". > {noformat} > java.lang.NullPointerException: null > at java.util.AbstractCollection.addAll(AbstractCollection.java:343) > at org.jboss.tools.arquillian.core.internal.dependencies.DependencyCache.getDependentTypes(DependencyCache.java:101) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:373) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:222) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:112) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.jboss.tools.arquillian.core | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 | > Operating Systems: > | Windows | 6.1.0 | 6.1.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57aab86ee4b0f4d912...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21771) Simplest java project is imported sometimes as JDT, sometimes not.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21771?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21771: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Simplest java project is imported sometimes as JDT, sometimes not. > ------------------------------------------------------------------ > > Key: JBIDE-21771 > URL: https://issues.jboss.org/browse/JBIDE-21771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.6.x > > Attachments: PlainJavaProject > > > Importing simplest java project (in attachment) gets sometimes imported as "Java, JDT" and sometimes only as "Java". I am not able to provide exact steps to reproduce, as it seems to do that randomly. > Looking at http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles/org.eclips..., project should be detected as JDT, in case ".classpath" is found in the project. Couldn't be the issue the order of executing configurators? Like when Java configurator is called first, it creates .classpath and then JDT configurator is called and it sees the .classpath file. When the order is opposite, JDT is not configured, because .classpath is not there yet? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22122) No platforms added to project - Error when importing cordova examples from Central

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22122?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22122: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > No platforms added to project - Error when importing cordova examples from Central > ---------------------------------------------------------------------------------- > > Key: JBIDE-22122 > URL: https://issues.jboss.org/browse/JBIDE-22122 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.6.x > > Attachments: Screen Shot 2016-04-06 at 13.33.25.png > > > With upgrade to thym 2.0 the tooling is showing error about 'no platforms added' when importing mobile examples from central. > We should implement a dialog/action for adding a platform and offer it the the user. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20573) OpenShift Explorer: decorate project showing last build/deployment failed/succeeded

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20573?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20573: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > OpenShift Explorer: decorate project showing last build/deployment failed/succeeded > ----------------------------------------------------------------------------------- > > Key: JBIDE-20573 > URL: https://issues.jboss.org/browse/JBIDE-20573 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: explorer, openshift_v3 > Fix For: 4.6.x > > > As reported by [~sspeiche] (or was it [~crobson]?), it'd be nice to have a visual clue of a project state, in the OpenShift Explorer. We should display the last pod status (build failed or deployment succeeded) next to a project's node -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21522) Background color for JavaScript code assist changes from yellow to black the second time it is opened

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21522?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21522: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Background color for JavaScript code assist changes from yellow to black the second time it is opened > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-21522 > URL: https://issues.jboss.org/browse/JBIDE-21522 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Affects Versions: 4.3.1.Beta2 > Environment: RHEL 7 > JBDS build: > Version: 9.1.0.Beta2 > Build id: Beta2-v20160120-1207-B247 > Build date: 20160120-1207 > Reporter: Len DiMaggio > Assignee: Victor Rubezhny > Fix For: 4.6.x > > Attachments: 1_yellow.png, 2_black.png > > > See the attached screenshots. > To recreate: > 1) Access code assist (observe that the background is yellow) > 2) Close the code assist window > 3) Access code assist (observe that the background is now black) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018