March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19391) Properties File editor does not work properly

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19391?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19391: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > Properties File editor does not work properly > --------------------------------------------- > > Key: JBIDE-19391 > URL: https://issues.jboss.org/browse/JBIDE-19391 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common > Reporter: Ali Hopyar > Assignee: Viacheslav Kabanovich > Fix For: 4.4.4.AM2 > > Attachments: messages_en.properties > > > On eclipse luna, I can not use JBoss editor for properties files. When I clicked add button nothing happens. When I click source tab and try to add some property, it is disappears when saved. Also if I open a property file that has been written before, also its content disappears. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20346) Jts quickstart (EAP 6.4) contains XML validation errors

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20346?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-20346: ------------------------------------ [~fbricon] Shouldn't we closed this one ? > Jts quickstart (EAP 6.4) contains XML validation errors > ------------------------------------------------------- > > Key: JBIDE-20346 > URL: https://issues.jboss.org/browse/JBIDE-20346 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2 > Reporter: Radim Hopp > Fix For: 4.4.4.AM1 > > > jts quickstart contains XML validation errors after import: > {noformat} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected. jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 30 XML Problem > {noformat} > {noformat} > Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 1 XML Problem > {noformat} > The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20063) locked up machine with "Loading descriptor" ...

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20063?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20063: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > locked up machine with "Loading descriptor" ... > ----------------------------------------------- > > Key: JBIDE-20063 > URL: https://issues.jboss.org/browse/JBIDE-20063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.4.4.AM2 > > > when loaded javaee7-samples I ended up with frozen eclipse showing this: > https://www.dropbox.com/s/ttx9ppieads5m7n/Screenshot%202015-06-13%2001.31... > its so frozen I cannot even get a stacktrace from jps. > I tried looking for "Loading descriptor" in common and batch but no luck so maybe it is not in batch this is happening but something is definitely locking up ;/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20558) org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20558?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20558: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager. > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20558 > URL: https://issues.jboss.org/browse/JBIDE-20558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, common > Affects Versions: 4.3.0.Beta2 > Reporter: The Alchemist > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.4.AM2 > > > {noformat} > org.jboss.tools.common.validation.JBTValidationException > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:222) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:217) > at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:507) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697) > Caused by: java.lang.NullPointerException > at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1114) > at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1118) > at org.jboss.tools.cdi.core.CDIUtil.getAllInterceptorBindingDeclaratios(CDIUtil.java:1110) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.hasConflictedInterceptorBindings(CDICoreValidator.java:984) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInterceptorBindings(CDICoreValidator.java:970) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateClassBean(CDICoreValidator.java:952) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:792) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:641) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:574) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) > ... 4 more > {noformat} > I wish I could see which class is causing this error... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22964) Fuse examples are found even though Fuse is not installed (and is not available in Central)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22964?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22964: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > Fuse examples are found even though Fuse is not installed (and is not available in Central) > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22964 > URL: https://issues.jboss.org/browse/JBIDE-22964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.AM3 > Environment: Devstudio 10.1.0.AM3-v20160809-0722-B5729 > Reporter: Radim Hopp > Fix For: 4.4.4.AM2 > > > After turning Early Access on, camel, fuse, brms examples can be looked up in Central even though Integration stack is not on the Software/Update page. > That is probably because _jboss.discovery.site.integration-stack.url_ and _jboss.discovery.earlyaccess.site.integration-stack.url_ properties are configured in ide-config.properties. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21971) jboss-jsonp quickstart includes an empty description as displayed in Central

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21971?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21971: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM1) > jboss-jsonp quickstart includes an empty description as displayed in Central > ---------------------------------------------------------------------------- > > Key: JBIDE-21971 > URL: https://issues.jboss.org/browse/JBIDE-21971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, upstream > Affects Versions: 4.3.1.CR1 > Environment: 4.3.1-SNAPSHOT (CR1-v20160324-1710-B391) > Reporter: Len DiMaggio > Labels: havoc > Fix For: 4.4.4.Final > > Attachments: Empty_Desc.png > > > See attached screenshot - the quickstart's description is empty. > !Empty_Desc.png|width=800! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23656) Missing validation of step listener with empty attribute ref

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23656?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23656: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > Missing validation of step listener with empty attribute ref > ------------------------------------------------------------ > > Key: JBIDE-23656 > URL: https://issues.jboss.org/browse/JBIDE-23656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.2.Final > Reporter: Ondrej Dockal > Priority: Minor > Fix For: 4.4.4.AM2 > > Attachments: batch-test-project.zip > > > There is missing warning in listener's tag with empty reference in source view. Empty value of reference attribute in step listener should show warning like job listener does when there is empty ref: "Job listener is expected". Please, add warning. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23811) ZipException in CDICoreBuilder when indexing some Maven artifacts

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23811?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23811: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM1) > ZipException in CDICoreBuilder when indexing some Maven artifacts > ----------------------------------------------------------------- > > Key: JBIDE-23811 > URL: https://issues.jboss.org/browse/JBIDE-23811 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Fix For: 4.4.4.Final > > Attachments: org.apache.aries.blueprint.core-1.7.1.jar > > > it would be nice to provide more information in log such as the classes in inspection by CDI Core Builder. > Also if there are some issues with those jars, please report bugs to them. > {noformat} > !ENTRY org.jboss.tools.common.core 4 0 2017-01-17 11:17:20.815 > !MESSAGE invalid LOC header (bad signature) > !STACK 0 > java.util.zip.ZipException: invalid LOC header (bad signature) > at java.util.zip.ZipFile.read(Native Method) > at java.util.zip.ZipFile.access$1400(ZipFile.java:60) > at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717) > at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419) > at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at java.io.DataInputStream.readFully(DataInputStream.java:195) > at java.io.DataInputStream.readFully(DataInputStream.java:169) > at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:433) > at org.jboss.jandex.Indexer.index(Indexer.java:689) > at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56) > at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) > 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} > {noformat} > !ENTRY org.jboss.tools.common.model 4 0 2017-01-25 16:11:53.722 > !MESSAGE Exception occurs when reading C:\Users\Aurelien Pupier\.m2\repository\org\apache\aries\blueprint\org.apache.aries.blueprint.core\1.7.1\org.apache.aries.blueprint.core-1.7.1.jar > !STACK 0 > java.util.zip.ZipException: invalid LOC header (bad signature) > at java.util.zip.ZipFile.read(Native Method) > at java.util.zip.ZipFile.access$1400(Unknown Source) > at java.util.zip.ZipFile$ZipFileInputStream.read(Unknown Source) > at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(Unknown Source) > at java.util.zip.InflaterInputStream.read(Unknown Source) > at java.io.BufferedInputStream.fill(Unknown Source) > at java.io.BufferedInputStream.read1(Unknown Source) > at java.io.BufferedInputStream.read(Unknown Source) > at org.jboss.tools.common.model.filesystems.impl.JarAccess.getContent(JarAccess.java:235) > at org.jboss.tools.common.model.filesystems.impl.JarAccess.isTextEntry(JarAccess.java:266) > at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.createFileObject(JarFolderImpl.java:95) > at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.loadChildren(JarFolderImpl.java:78) > at org.jboss.tools.common.model.impl.RegularObjectImpl.getChildByPathPart(RegularObjectImpl.java:159) > at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.getChildByPathPart(JarFolderImpl.java:152) > at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:347) > at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:352) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.readRuntimes(ClassPathMonitor.java:286) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:103) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215) > at org.jboss.tools.cdi.core.CDICoreBuilder.<init>(CDICoreBuilder.java:101) > at org.jboss.tools.cdi.core.CDICoreNature.load(CDICoreNature.java:420) > at org.jboss.tools.cdi.core.CDICoreNature.resolveStorage(CDICoreNature.java:393) > at org.jboss.tools.cdi.core.CDICoreNature.resolve(CDICoreNature.java:406) > at org.jboss.tools.cdi.core.CDICorePlugin.getCDI(CDICorePlugin.java:165) > at org.jboss.tools.cdi.core.CDICorePlugin$RCL.resourceChanged(CDICorePlugin.java:104) > at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289) > at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152) > at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:374) > at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1469) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:46) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23779) Archive old JBoss Tools versions on Downloads and What's New pages

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23779?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23779: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM1) > Archive old JBoss Tools versions on Downloads and What's New pages > ------------------------------------------------------------------- > > Key: JBIDE-23779 > URL: https://issues.jboss.org/browse/JBIDE-23779 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Affects Versions: 4.4.3.AM1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.4.Final > > > there are too many versions displayed on https://tools.jboss.org/documentation/whatsnew/. Having 3 elements (1 development and 2 stable items) would be enough. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23861) CDI support is not enabled automatically with JBoss AS 7.1 runtime

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23861?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23861: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > CDI support is not enabled automatically with JBoss AS 7.1 runtime > ------------------------------------------------------------------ > > Key: JBIDE-23861 > URL: https://issues.jboss.org/browse/JBIDE-23861 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.4.3.AM2 > Environment: Devstudio AM2-v20170127-1155-B6970, Java 1.8.0_111-b15, JBoss AS 7.1.1.Final > Reporter: Lukáš Valach > Priority: Minor > Fix For: 4.4.4.AM2 > > Attachments: CdiSupport1.png, CdiSupport2.png > > > When I create a Dynamic Web Project or EJB Project the CDI support should be enabled automatically. It works properly when I have JBoss EAP 7 or Wildfly 10 as target platform, but it doesn't work with JBoss AS 7.1. > There is no error in the log, there is only warning in the problems view. > ??JBoss Tools Knowledge Base probelm: Nature/Builder is not installed on project. Use quick fix to enable %KB_REQUIRED_FOR_FACET and Faceted (test environment only) Content Assistant and Validation.?? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 March 2017