July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17955) Application wizard: Opening quickstart link opens all previously selected quickstarts

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17955?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17955: ------------------------------------- Summary: Application wizard: Opening quickstart link opens all previously selected quickstarts (was: Opening quickstart link opens all previously clicked quickstarts in OpenShift tools) > Application wizard: Opening quickstart link opens all previously selected quickstarts > ------------------------------------------------------------------------------------- > > Key: JBIDE-17955 > URL: https://issues.jboss.org/browse/JBIDE-17955 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Labels: application_wizard > > In New application wizard Quickstarts contain details area. In this area is a link for each quickstart leading to website describing the given quickstart. After clicking on several quickstart (not links, just quickstarts in Tree) and then click on link, several web sites are opened (for each clicked quickstart). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17955) Opening quickstart link opens all previously clicked quickstarts in OpenShift tools

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17955?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17955: ------------------------------------- Summary: Opening quickstart link opens all previously clicked quickstarts in OpenShift tools (was: Opening quickstart link open all previously clicked quickstarts in OpenShift tools) > Opening quickstart link opens all previously clicked quickstarts in OpenShift tools > ----------------------------------------------------------------------------------- > > Key: JBIDE-17955 > URL: https://issues.jboss.org/browse/JBIDE-17955 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Labels: application_wizard > > In New application wizard Quickstarts contain details area. In this area is a link for each quickstart leading to website describing the given quickstart. After clicking on several quickstart (not links, just quickstarts in Tree) and then click on link, several web sites are opened (for each clicked quickstart). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17964) add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17964: ------------------------------------ OK, so we need: * a list of features to INCLUDE in the existing JBDS marketplace entry (culled from those available here: https://devstudio.jboss.com/updates/7.0/integration-stack/ ) ** https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... * a list of feature to EXCLUDE from the existing JBDS marketplace entry (culled from those available here: https://devstudio.jboss.com/updates/7.0/integration-stack/ ) ** SOA-P 5.x legacy features: https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... What about the bpel-examples being re-added to JBDS IS 7.x? Include or exclude? (cc: [~bfitzpat] [~pleacu] ) > add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric > ------------------------------------------------------------------------------------------ > > Key: JBIDE-17964 > URL: https://issues.jboss.org/browse/JBIDE-17964 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 4.1.2.Final > Reporter: Lars Heinemann > Assignee: Nick Boldt > Fix For: 4.1.2.Final > > > Currently when people search the marketplace for Fuse, Fabric, Fabric8 or Camel they don't find JBoss products. We should add those keywords to JBT and JBDS. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17984) Application wizard: dont commit nor push changes back to OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17984?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17984: ------------------------------------- Description: In JBIDE-10541 we added a "Publish Changes" dialog that shows the dirty changes for the local project, allows users to provide a commit msg and to commit/publish changes to OpenShift. In JBIDE-17190 we switched from automatic commit to explicit commit via this dialog when import new/existing OpenShift application. The "Publish Changes" dialog popping up after the OpenShift application was imported (application wizard) proved to be unexpected, disturbing in UX tests. We could get back to automatic commit but this is very much opaque for the user (discussed it in length with [~maxandersen]). We therefore decided to fully drop any commit and push when doing the initial import. We just process our changes and keep the imported project dirty. The user can then push the changes back to OpenShift via the server adapter. was: In JBIDE-10541 we added a "Publish Changes" dialog that shows the dirty changes for the local project, allows users to provide a commit msg and to commit/publish changes to OpenShift. This resulted in having a "Publish Changes" dialog popping up after the OpenShift application was imported (application wizard). UX tests revealed that this dialog is disturbing to users, it is pretty much unexpected for them. We could solve this via automatic commit as we did so far but this is very much opaque for the user (discussed it in length with [~maxandersen]). We therefore decided to fully drop any commit and push when doing the initial import. We just process our changes and keep the imported project dirty. The user can then push the changes back to OpenShift via the server adapter. > Application wizard: dont commit nor push changes back to OpenShift > ------------------------------------------------------------------ > > Key: JBIDE-17984 > URL: https://issues.jboss.org/browse/JBIDE-17984 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.CR1 > > > In JBIDE-10541 we added a "Publish Changes" dialog that shows the dirty changes for the local project, allows users to provide a commit msg and to commit/publish changes to OpenShift. > In JBIDE-17190 we switched from automatic commit to explicit commit via this dialog when import new/existing OpenShift application. The "Publish Changes" dialog popping up after the OpenShift application was imported (application wizard) proved to be unexpected, disturbing in UX tests. > We could get back to automatic commit but this is very much opaque for the user (discussed it in length with [~maxandersen]). We therefore decided to fully drop any commit and push when doing the initial import. We just process our changes and keep the imported project dirty. The user can then push the changes back to OpenShift via the server adapter. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17964) add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17964: --------------------------------------------- it should also be able to get Central, also maybe SOA-P legacy should not be installed by default but just an addon. > add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric > ------------------------------------------------------------------------------------------ > > Key: JBIDE-17964 > URL: https://issues.jboss.org/browse/JBIDE-17964 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 4.1.2.Final > Reporter: Lars Heinemann > Assignee: Nick Boldt > Fix For: 4.1.2.Final > > > Currently when people search the marketplace for Fuse, Fabric, Fabric8 or Camel they don't find JBoss products. We should add those keywords to JBT and JBDS. -- 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: ---------------------------------------- If we release 0.19.0, then 0.19.0-SNAPSHOT will disappear and all people consuming parent pom referencing it (prior to 4.2.0.CR1-SNAPSHOT) will see their build fail. If we release 0.21.0, then 0.19.0-SNAPSHOT will still be there, and we put a release in parent pom. However, moving to newer Tycho requires some changes, so I find it safer to build and adopt a 0.21.0-SNAPSHOT for let's say a week and then release it within a few day (not to be forgotten!). > 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-17942) tycho-plugins 0.19-snapshot is missing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17942?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17942: ------------------------------------ Either way people will have to update their poms to move from 0.19.0-SNAPSHOT to 0.19.0 or 0.21.0-SNAPSHOT or 0.21.0. I would suggest we get 0.19.0 released, start a 0.21.0-SNAPSHOT, and get that new 0.21.0 released in a month or so, if nothing wacky happens. > 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-17917) copy/paste of server stopped working

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17917?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17917. --------------------------------- Fix Version/s: 4.2.0.Beta3 Resolution: Cannot Reproduce Bug not able to replicate > copy/paste of server stopped working > ------------------------------------ > > Key: JBIDE-17917 > URL: https://issues.jboss.org/browse/JBIDE-17917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Fix For: 4.2.0.Beta3 > > > create a wildfly 8 server. > Copy and then paste it > see new additional server created. > Assert: possible to start the second server. > Fail: errors at startup as if not all paramters are set. -- 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 commented on JBIDE-17905: ------------------------------------------ this is how the new "Publish Changes"-dialog behaves: [^publish-dialog.ogv] > 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 > > Attachments: publish-dialog.ogv > > > # 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: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/456 (was: https://github.com/jbosstools/jbosstools-openshift/pull/453) > 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 > > Attachments: publish-dialog.ogv > > > # 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

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