July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17263) Table in Download Runtimes dialog is sometimes empty

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17263?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17263: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.CR1) > Table in Download Runtimes dialog is sometimes empty > ---------------------------------------------------- > > Key: JBIDE-17263 > URL: https://issues.jboss.org/browse/JBIDE-17263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.0.Beta2 > Environment: Eclipse 4.4.0M7 with JBT 4.2.0-SNAPSHOT (Beta2-v20140513-0450-B8804) > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.x > > Attachments: empty-runtimes-table.jpg, next-runtime-table.jpg > > > Table in Download Runtimes dialog with list of available runtimes is sometimes empty. > It's hard to reproduce but when running automatized UI tests, the runtime download table is always empty. Also invoking SWTBot tests from eclipse breaks the download runtime dialog, which will have empty table in eclipse from which the tests were invoked. > Interesting thing is that button Next works even when the table is empty. It behaves as the first item in table is selected. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3099) No Early Access features in Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3099?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3099: -------------------------------------- Sorry for this mistake! > No Early Access features in Central > ----------------------------------- > > Key: JBDS-3099 > URL: https://issues.jboss.org/browse/JBDS-3099 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: central, updatesite > Affects Versions: 8.0.0.Beta3 > Environment: JBDS 8.0.0.Beta3b > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Beta3 > > > There are no Early Access features in Central and there is error in error log: > {noformat:title=Provisioning exception} > org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.0.0.Beta3b-ta.... > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.jboss.tools.central.editors.xpl.P2CachedRepoUtil.getRepoForConnector(P2CachedRepoUtil.java:41) > at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.resolveConnectorUnits(ConnectorDescriptorItemUi.java:428) > at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.access$3(ConnectorDescriptorItemUi.java:427) > at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:309) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {noformat} > JBT 4.2.0.Beta3b seems not to be affected by this issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17942) tycho-plugins 0.19-snapshot is missing

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17942?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17942: ---------------------------------------- I think it's something I thought once: "I'll release it later" because I was busy with more important stuff, and forgot to do it after. I'll release it asap. As [~nickboldt] suggested, I'll first send a mail to jbosstools-dev to inform that 0.19.0-SNAPSHOT will disappear. > tycho-plugins 0.19-snapshot is missing > -------------------------------------- > > Key: JBIDE-17942 > URL: https://issues.jboss.org/browse/JBIDE-17942 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > this morning reports were coming in builds were failing because org.jboss.tools.tycho-plugins:repository-utils:0.19.0-SNAPSHOT was missing. > Turns out https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... failed to upload and then https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... ran but the machine running thought it was July 12th and not July 14th. > To fix it I respun the build and not the urgent issue is fixed but: > A) Why are we even using snapshots for this JBIDE-17941 > B) Why did the snapshot dissapear/why is jenkins build several days behind. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17983) track installations of JBoss Fuse Tooling

by Lars Heinemann (JIRA)

Lars Heinemann created JBIDE-17983: -------------------------------------- Summary: track installations of JBoss Fuse Tooling Key: JBIDE-17983 URL: https://issues.jboss.org/browse/JBIDE-17983 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: usage Affects Versions: 4.2.0.Beta3 Reporter: Lars Heinemann We should track installations of JBoss Fuse Tooling. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17905) Server Adapter: cannot publish commits (only) when there are local changes (can only commit and push)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17905?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17905: ------------------------------------- Description: # EXEC: Add file test.txt # EXEC: Commit test.txt # EXEC: Add file temporary.txt # EXEC: go to openshift server and publish # ASSERT: commit dialog shows up # ASSERT: I can push the new commits without having to do something about temporary.txt this worked in past, now the new commit dialog prevents me from doing this. I can use egit push to workaround this but that kinda defeats the purpose of making the server interaction simple via just the "Publish" command. was: Add file test.txt Commit test.txt Add file temporary.txt go to openshift server and push Assert: I can push the new commits without having to do something about temporary.txt this worked in past, now the new commit dialog prevents me from doing this. I can use egit push to workaround this but that kinda defeats the purpose of making the server interaction simple via just the "Publish" command. > Server Adapter: cannot publish commits (only) when there are local changes (can only commit and push) > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-17905 > URL: https://issues.jboss.org/browse/JBIDE-17905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Critical > Labels: server_adapter > Fix For: 4.2.0.CR1 > > > # EXEC: Add file test.txt > # EXEC: Commit test.txt > # EXEC: Add file temporary.txt > # EXEC: go to openshift server and publish > # ASSERT: commit dialog shows up > # ASSERT: I can push the new commits without having to do something about temporary.txt > this worked in past, now the new commit dialog prevents me from doing this. > I can use egit push to workaround this but that kinda defeats the purpose of making the server interaction simple via just the "Publish" command. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17905) Server Adapter: cannot publish commits (only) when there are local changes (can only commit and push)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17905?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17905: ------------------------------------- Summary: Server Adapter: cannot publish commits (only) when there are local changes (can only commit and push) (was: Server Adapter: cannot publish commits when there are local changes) > Server Adapter: cannot publish commits (only) when there are local changes (can only commit and push) > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-17905 > URL: https://issues.jboss.org/browse/JBIDE-17905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Critical > Labels: server_adapter > Fix For: 4.2.0.CR1 > > > Add file test.txt > Commit test.txt > Add file temporary.txt > go to openshift server and push > Assert: I can push the new commits without having to do something about temporary.txt > this worked in past, now the new commit dialog prevents me from doing this. > I can use egit push to workaround this but that kinda defeats the purpose of making the server interaction simple via just the "Publish" command. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17965) Update stacks url (jdf is now jboss developer)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17965?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17965: ---------------------------------------- Component/s: common/jst/core seam2 > Update stacks url (jdf is now jboss developer) > ---------------------------------------------- > > Key: JBIDE-17965 > URL: https://issues.jboss.org/browse/JBIDE-17965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, common/jst/core, seam2, server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > I'm not sure exactly which component is right here. > stacks.yaml is now on this location: > https://github.com/jboss-developer/jboss-stacks/blob/1.0.0.Final/stacks.yaml > It's no longer jdf, but jboss-developer. The old url still works through redirects, but it's probably a good idea to use the new one. > Reject this JIRA if this has already been done. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17905) Server Adapter: cannot publish commits when there are local changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17905?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-17905 at 7/28/14 6:52 AM: ------------------------------------------------------------------- In JBIDE-17190 we started presenting the commit dialog in the initial import and stopped doing an automatic commit. The new dialog allowed people to inspect the changes that the import did and to choose to commit/not commit them before possibly pushing changes back to OpenShift. In the UX review it turned out that the commit dialog was unexpected to the newbie user, he did not understand why he would have to commit changes upon import. In a discussion with [~maxandersen] we now decided to not commit the changes upon import (we'll make them more clever though: JBIDE-17904). This implies that we wont push local changes back to OpenShift automatically (as we we started doing it with JBIDE-13075) was (Author: adietish): In JBIDE-17190 we started presenting the commit dialog in the initial import and stopped doing an automatic commit. That should have allowed people to inspect the changes that the import does and choosing to commit/not commit them before possibly pushing changes back to OpenShift. In the UX review it turned out that the commit dialog was unexpected to the newbie user, he did not understand why he would have to commit changes upon import. In a discussion with [~maxandersen] we now decided to not commit the changes upon import (we'll make them more clever though: JBIDE-17904). This implies that we wont push local changes back to OpenShift automatically (as we we started doing it with JBIDE-13075) > Server Adapter: cannot publish commits when there are local changes > ------------------------------------------------------------------- > > Key: JBIDE-17905 > URL: https://issues.jboss.org/browse/JBIDE-17905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Critical > Labels: server_adapter > Fix For: 4.2.0.CR1 > > > Add file test.txt > Commit test.txt > Add file temporary.txt > go to openshift server and push > Assert: I can push the new commits without having to do something about temporary.txt > this worked in past, now the new commit dialog prevents me from doing this. > I can use egit push to workaround this but that kinda defeats the purpose of making the server interaction simple via just the "Publish" command. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17905) Server Adapter: cannot publish commits when there are local changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17905?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-17905: ------------------------------------------ In JBIDE-17190 we started presenting the commit dialog in the initial import and stopped doing an automatic commit. That should have allowed people to inspect the changes that the import does and choosing to commit/not commit them before possibly pushing changes back to OpenShift. In the UX review it turned out that the commit dialog was unexpected to the newbie user, he did not understand why he would have to commit changes upon import. In a discussion with [~maxandersen] we now decided to not commit the changes upon import (we'll make them more clever though: JBIDE-17904). This implies that we wont push local changes back to OpenShift automatically (as we we started doing it with JBIDE-13075) > Server Adapter: cannot publish commits when there are local changes > ------------------------------------------------------------------- > > Key: JBIDE-17905 > URL: https://issues.jboss.org/browse/JBIDE-17905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Critical > Labels: server_adapter > Fix For: 4.2.0.CR1 > > > Add file test.txt > Commit test.txt > Add file temporary.txt > go to openshift server and push > Assert: I can push the new commits without having to do something about temporary.txt > this worked in past, now the new commit dialog prevents me from doing this. > I can use egit push to workaround this but that kinda defeats the purpose of making the server interaction simple via just the "Publish" command. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17791) Forge New and Noteworthy for 4.2.0.Beta3

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17791?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17791: ------------------------------ Assignee: Koen Aers > Forge New and Noteworthy for 4.2.0.Beta3 > ---------------------------------------- > > Key: JBIDE-17791 > URL: https://issues.jboss.org/browse/JBIDE-17791 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.Beta3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/wha...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 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 July 2014