[JBoss JIRA] (JBIDE-19188) Lot of exceptions after renaming project
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19188?page=com.atlassian.jira.plugi... ]
Rastislav Wagner updated JBIDE-19188:
-------------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> 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.AM2
>
>
> {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
[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-4077:
------------------------------
Description:
Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
A full devstudio should open when the tests are run. Instead it looks like this:
!tpfail.png|thumbnail!
was:
Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
Screenshot incoming:
!tpfail.png|thumbnail!
> Cannot run integration tests against Devstudio with latest target platform
> --------------------------------------------------------------------------
>
> Key: JBDS-4077
> URL: https://issues.jboss.org/browse/JBDS-4077
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 10.2.0.AM1
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: tpfail.png
>
>
> Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
> A full devstudio should open when the tests are run. Instead it looks like this:
> !tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-4077:
------------------------------
Description:
Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
Screenshot incoming:
!tpfail.png|thumbnail!
was:
Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
Screenshot incoming:
!tpfail.png|thumbnail!
> Cannot run integration tests against Devstudio with latest target platform
> --------------------------------------------------------------------------
>
> Key: JBDS-4077
> URL: https://issues.jboss.org/browse/JBDS-4077
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 10.2.0.AM1
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: tpfail.png
>
>
> Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
> Screenshot incoming:
> !tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform
by Jan Richter (JIRA)
Jan Richter created JBDS-4077:
---------------------------------
Summary: Cannot run integration tests against Devstudio with latest target platform
Key: JBDS-4077
URL: https://issues.jboss.org/browse/JBDS-4077
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: build, target-platform
Affects Versions: 10.2.0.AM1
Reporter: Jan Richter
Assignee: Nick Boldt
Priority: Blocker
Attachments: tpfail.png
Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
Screenshot incoming:
!tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23177) Server Editor: Combo items have wrong size
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23177?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23177:
------------------------------------------
[~mlabuda][~bdshadow] Could anyone of you please verify this patch for FC24 (I only have FC23)?
> Server Editor: Combo items have wrong size
> ------------------------------------------
>
> Key: JBIDE-23177
> URL: https://issues.jboss.org/browse/JBIDE-23177
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_editor
> Fix For: 4.4.2.AM2
>
> Attachments: combos.png
>
>
> When I open an OpenShift 3 Server Editor the combo boxes have weird size, there are overlapping widgets.
> !combos.png!
> Spotted on Fedora 24 with GTK 3.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23208) SSLCertificatesPreference.isValid(String): Could not parse
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23208?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23208:
-------------------------------------
Fix Version/s: 4.4.2.AM2
> 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
> Fix For: 4.4.2.AM2
>
>
> 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
[JBoss JIRA] (JBIDE-23267) New application created by JBDS cannot specify "medium" or "large" size.
by Kenjiro Nakayama (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23267?page=com.atlassian.jira.plugi... ]
Kenjiro Nakayama commented on JBIDE-23267:
------------------------------------------
Thank you Andre so much for your prompt update.
> New application created by JBDS cannot specify "medium" or "large" size.
> ------------------------------------------------------------------------
>
> Key: JBIDE-23267
> URL: https://issues.jboss.org/browse/JBIDE-23267
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Environment: * All versions
> * I confirmed with latest version devstudio-10.0.0.GA-installer-standalone.jar
> Reporter: Kenjiro Nakayama
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: application_wizard, gear, openshift_v2
> Fix For: 4.4.2.AM2
>
> Original Estimate: 4 hours
> Time Spent: 1 hour
> Remaining Estimate: 3 hours
>
> * New application created by JBDS cannot specify "medium" or "large" size.
> * NOTE: This issue is critical if the users environment doesn't allow to create small gears. Since they cannot create any application via JBDS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4076) "RPM release" mismatch between src.rpm and x86_64.rpm
by Václav Kadlčík (JIRA)
Václav Kadlčík created JBDS-4076:
------------------------------------
Summary: "RPM release" mismatch between src.rpm and x86_64.rpm
Key: JBDS-4076
URL: https://issues.jboss.org/browse/JBDS-4076
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: installer
Reporter: Václav Kadlčík
This is an issue with upcoming rh-eclipse46-devstudio.rpm.
Sometimes there's a mismatch in the "RPM release" between a built RPM and its src.rpm. For example https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20... contains:
rh-eclipse46-devstudio-10.2-0.20161004.0056.el7.src.rpm
rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm
The RPM release part is "0.20161004.0057.el7"; looks constructed using the date and time of building. The time bits are different between the two files.
The SOURCERPM info in the RPM is broken as well:
{{$ rpm -q --qf='%{SOURCERPM}\n' -p rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm
rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.src.rpm
}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months