September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23208) SSLCertificatesPreference.isValid(String): Could not parse

by Martin Malina (JIRA)

Martin Malina created JBIDE-23208: ------------------------------------- Summary: SSLCertificatesPreference.isValid(String): Could not parse Key: JBIDE-23208 URL: https://issues.jboss.org/browse/JBIDE-23208 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk, openshift Affects Versions: 4.4.2.AM1 Reporter: Martin Malina When I start CDK and OpenShift connection is established, I get this in the Error Log view: org.jboss.tools.openshift.ui SSLCertificatesPreference.isValid(String): Could not parse 'Čt, 20 Zář 2018 12:54:07' in format E, d MMM yyyy HH:mm:ss An exception stack trace is not available. As you can see, the date is localized. I think this started happening after I updated to macOS Sierra last night - I never noticed it before. If we can figure out where the parsing is happening, perhaps we can come up with a switch for using english date here. Env: devstudio-10.2.0.AM1-v20160920-0457-B6061-installer-standalone.jar cdk 2.2.rc5 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19188) Lot of exceptions after renaming project

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19188?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-19188: ----------------------------------- OK, I got it reproduces > Lot of exceptions after renaming project > ---------------------------------------- > > Key: JBIDE-19188 > URL: https://issues.jboss.org/browse/JBIDE-19188 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.2.Final > Reporter: Rastislav Wagner > Assignee: Koen Aers > Fix For: 4.4.2.AM1 > > > {code} > java.lang.IndexOutOfBoundsException: Index: 0 > at java.util.Collections$EmptyList.get(Collections.java:4454) > at org.hibernate.eclipse.launch.core.refactoring.HibernateRefactoringUtil.updateClasspathEntries(HibernateRefactoringUtil.java:303) > at org.hibernate.eclipse.launch.core.refactoring.HibernateRefactoringUtil.updateConsoleConfig(HibernateRefactoringUtil.java:226) > at org.hibernate.eclipse.launch.core.refactoring.LaunchConfigurationResourceNameChange.perform(LaunchConfigurationResourceNameChange.java:102) > at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) > at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > {code} > {code} > java.lang.IndexOutOfBoundsException: Index: 0 > at java.util.Collections$EmptyList.get(Collections.java:4454) > at org.hibernate.eclipse.launch.core.refactoring.HibernateRefactoringUtil.updateClasspathEntries(HibernateRefactoringUtil.java:303) > at org.hibernate.eclipse.launch.core.refactoring.HibernateRefactoringUtil.updateConsoleConfig(HibernateRefactoringUtil.java:226) > at org.hibernate.eclipse.launch.core.refactoring.LaunchConfigurationResourceNameChange.perform(LaunchConfigurationResourceNameChange.java:102) > at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) > at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > {code} > {code} > java.lang.IndexOutOfBoundsException: Index: 0 > at java.util.Collections$EmptyList.get(Collections.java:4454) > at org.hibernate.eclipse.launch.core.refactoring.HibernateRefactoringUtil.updateClasspathEntries(HibernateRefactoringUtil.java:303) > at org.hibernate.eclipse.launch.core.refactoring.HibernateRefactoringUtil.updateConsoleConfig(HibernateRefactoringUtil.java:226) > at org.hibernate.eclipse.launch.core.refactoring.LaunchConfigurationResourceNameChange.perform(LaunchConfigurationResourceNameChange.java:102) > at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) > at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > {code} > {code} > org.eclipse.core.internal.resources.ResourceException: Resource '/jboss-javaee6-webapp' does not exist. > at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341) > at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215) > at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:147) > at org.eclipse.core.internal.resources.Resource.checkAccessibleAndLocal(Resource.java:221) > at org.eclipse.core.internal.resources.Resource.getPersistentProperty(Resource.java:1204) > at org.hibernate.eclipse.utils.HibernateEclipseUtils.getUserOverrideDefaultCatalog(HibernateEclipseUtils.java:72) > at org.hibernate.eclipse.console.EclipseLaunchConsoleConfigurationPreferences.getProjectOverrides(EclipseLaunchConsoleConfigurationPreferences.java:239) > at org.hibernate.eclipse.console.EclipseLaunchConsoleConfigurationPreferences.getProperties(EclipseLaunchConsoleConfigurationPreferences.java:166) > at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.getDefaultCatalog(HibernateJpaProject.java:175) > at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.buildDefaultCatalog(AbstractPersistenceUnit.java:1368) > at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.updatePersistenceUnitMetadata(AbstractPersistenceUnit.java:1421) > at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.update(AbstractPersistenceUnit.java:303) > at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit.update(HibernatePersistenceUnit.java:95) > at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel.updateModels(AbstractJpaContextModel.java:73) > at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.update(GenericPersistence.java:75) > at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.syncPersistence(GenericPersistenceXml.java:140) > at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.updatePersistence(GenericPersistenceXml.java:97) > at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.update(GenericPersistenceXml.java:93) > at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.syncPersistenceXml(GenericContextRoot.java:128) > at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.updatePersistenceXml(GenericContextRoot.java:162) > at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.update(GenericContextRoot.java:78) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.update(AbstractJpaProject.java:1994) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$UpdateJobCommand.execute(AbstractJpaProject.java:1981) > at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.executeCommand(RepeatingJobCommandWrapper.java:207) > at org.eclipse.jpt.common.core.internal.utility.command.NotifyingRepeatingJobCommandWrapper.executeCommand(NotifyingRepeatingJobCommandWrapper.java:68) > at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.execute_(RepeatingJobCommandWrapper.java:192) > at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper$StartJobCommand.execute(RepeatingJobCommandWrapper.java:172) > at org.eclipse.jpt.common.core.internal.utility.command.DefaultJobCommandContext.execute(DefaultJobCommandContext.java:38) > at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.executeStartCommand(RepeatingJobCommandWrapper.java:157) > at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.execute(RepeatingJobCommandWrapper.java:147) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.update(AbstractJpaProject.java:1973) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.initializeContextModel(AbstractJpaProject.java:303) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.<init>(AbstractJpaProject.java:264) > at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.<init>(HibernateJpaProject.java:71) > at org.jboss.tools.hibernate.jpt.core.internal.HibernateAbstractJpaFactory.buildJpaProject(HibernateAbstractJpaFactory.java:107) > at org.jboss.tools.hibernate.jpt.core.internal.jpa2.HibernateJpaFactory2_0.buildJpaProject(HibernateJpaFactory2_0.java:89) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:647) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:635) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:628) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.addJpaProject(InternalJpaProjectManager.java:609) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.checkForJpaFacetTransition_(InternalJpaProjectManager.java:846) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$FacetFileChangeEventHandlerCommand.execute(InternalJpaProjectManager.java:836) > at org.eclipse.jpt.common.core.internal.utility.command.CommandJobCommandAdapter.execute(CommandJobCommandAdapter.java:50) > at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > and much more.. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3982) create rh-eclipse46-devstudio rpm for linux installs

by Mat Booth (JIRA)

[ https://issues.jboss.org/browse/JBDS-3982?page=com.atlassian.jira.plugin.... ] Mat Booth commented on JBDS-3982: --------------------------------- Would it be good idea to have the devstudio version be the rpm version? E.g. rh-eclipse46-devstudio-10.1-3.20160920.2211.el7.x86_64.rpm and rh-eclipse46-devstudio-10.2-3.20160920.2211.el7.x86_64.rpm That way upgrades always go the right way -- you probably don't want to be upgraded to a 10.1 rpm with a higher timestamp from a 10.2 rpm with a lower timestamp -- does that make sense? > create rh-eclipse46-devstudio rpm for linux installs > ---------------------------------------------------- > > Key: JBDS-3982 > URL: https://issues.jboss.org/browse/JBDS-3982 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM1 > > > wrap new update site (JBDS-3981) in a rh-eclipse46-devstudio*.rpm so we can install it on Fedora 24 and RHEL 7 > will need to port http://download.jboss.org/jbosstools/updates/scripted-install/director.xml to bash so it can be called along with rpmbuilder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-892) Test BPMN2 modeler on JBTIS 4.4.0.Alpha1

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-892?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-892. ----------------------------------- All sub-tasks were successfully merge so we can close this task. > Test BPMN2 modeler on JBTIS 4.4.0.Alpha1 > ---------------------------------------- > > Key: JBTIS-892 > URL: https://issues.jboss.org/browse/JBTIS-892 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-901) Fix failing ComplexSendTaskTest

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-901?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-901. ----------------------------------- Fix Version/s: 4.4.0.Alpha1 Resolution: Done pushed to jbtis-4.4.x > Fix failing ComplexSendTaskTest > ------------------------------- > > Key: JBTIS-901 > URL: https://issues.jboss.org/browse/JBTIS-901 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 4.4.0.Alpha1 > > > The test fails as result of new feature, that prevents user from putting 'Message' mapping from 'I/O' tab and forces him to put this mapping from 'Send Task' tab. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-875) Fix failing test for JBDS-IS 9.0.2.x

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-875?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-875. ----------------------------------- All sub-tasks were successfully merged so we can close this task. > Fix failing test for JBDS-IS 9.0.2.x > ------------------------------------ > > Key: JBTIS-875 > URL: https://issues.jboss.org/browse/JBTIS-875 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 9.0.2.CR1 > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 9.0.2.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23207) Maven configuration error whe using maven-jar-plugin and maven-war-plugin

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23207?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-23207: --------------------------------------- [~fbricon] could be solved by updating org.sonatype.m2e.mavenarchiver ? > Maven configuration error whe using maven-jar-plugin and maven-war-plugin > ------------------------------------------------------------------------- > > Key: JBIDE-23207 > URL: https://issues.jboss.org/browse/JBIDE-23207 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform > Reporter: Josef Kopriva > > Error in project when using maven-jar-plugin and maven-war-plugin. > Example POM file: > {code:java} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>test</groupId> > <artifactId>test</artifactId> > <version>1.0-SNAPSHOT</version> > <build> > <pluginManagement> > <plugins> > <plugin> > <artifactId>maven-jar-plugin</artifactId> > <version>3.0.2</version> > </plugin> > </plugins> > </pluginManagement> > </build> > </project> > {code} > Error: > Description Resource Path Location Type > org.codehaus.plexus.archiver.jar.Manifest.write(java.io.PrintWriter) pom.xml /test line 1 Maven Configuration Problem > Devstudio: > Red Hat JBoss Developer Studio > Version: 10.2.0.AM1 > Build id: AM1-v20160920-0457-B6061 > Build date: 20160920-0457 > org.sonatype.m2e.mavenarchiver version: > 0.17.1.201602251832-signed-20160525150658 > This issue is also logged on Github with more information: > https://github.com/tesla/m2eclipse-mavenarchiver/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23207) Maven configuration error whe using maven-jar-plugin and maven-war-plugin

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-23207: ------------------------------------- Summary: Maven configuration error whe using maven-jar-plugin and maven-war-plugin Key: JBIDE-23207 URL: https://issues.jboss.org/browse/JBIDE-23207 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, target-platform Reporter: Josef Kopriva Error in project when using maven-jar-plugin and maven-war-plugin. Example POM file: {code:java} <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>test</groupId> <artifactId>test</artifactId> <version>1.0-SNAPSHOT</version> <build> <pluginManagement> <plugins> <plugin> <artifactId>maven-jar-plugin</artifactId> <version>3.0.2</version> </plugin> </plugins> </pluginManagement> </build> </project> {code} Error: Description Resource Path Location Type org.codehaus.plexus.archiver.jar.Manifest.write(java.io.PrintWriter) pom.xml /test line 1 Maven Configuration Problem Devstudio: Red Hat JBoss Developer Studio Version: 10.2.0.AM1 Build id: AM1-v20160920-0457-B6061 Build date: 20160920-0457 org.sonatype.m2e.mavenarchiver version: 0.17.1.201602251832-signed-20160525150658 This issue is also logged on Github with more information: https://github.com/tesla/m2eclipse-mavenarchiver/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-904) Update structure of WebServiceCreationTest

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-904?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-904. ----------------------------------- pushed to master > Update structure of WebServiceCreationTest > ------------------------------------------- > > Key: JBTIS-904 > URL: https://issues.jboss.org/browse/JBTIS-904 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.1.Final > Reporter: stanislav kaleta > Assignee: Andrej Podhradsky > Fix For: 4.3.2.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-907) Unify a logic for skipping known issues

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-907: --------------------------------------- Summary: Unify a logic for skipping known issues Key: JBTIS-907 URL: https://issues.jboss.org/browse/JBTIS-907 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE Affects Versions: 4.3.1.Final Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Priority: Minor There at least 2 classes IssueIsClosed in the following packages * org.jboss.tools.common.reddeer.condition * org.jboss.tools.switchyard.ui.bot.test.condition Use only the first one in Mars. In Neon completely remove the classes and use the one in RedDeer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016