March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13708) openshift-java-client: make sure is not affected by REST response without Reason phrase

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13708: ------------------------------------- Summary: openshift-java-client: make sure is not affected by REST response without Reason phrase (was: openshift-java-client: make sure is not affected by change in status line response) > openshift-java-client: make sure is not affected by REST response without Reason phrase > --------------------------------------------------------------------------------------- > > Key: JBIDE-13708 > URL: https://issues.jboss.org/browse/JBIDE-13708 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Reporter: Andre Dietisheim > > the latest OpenShift REST service is apparently responding without reason phrase: > It will respond with *"HTTP/1.1 200 "* and ommit the reason phrase it usually reported before *"HTTP/1.1 200 OK"*. According to RFC 1945 a server doesn't have to give a reason phrase. The reason phrase is optional:http://www.w3.org/Protocols/rfc1945/rfc1945 / Section 6.1.1. > We have to make sure openshift-java-client can deal with it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13708) openshift-java-client: make sure is not affected by change in status line response

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13708: ------------------------------------- Description: the latest OpenShift REST service is apparently responding without reason phrase: It will respond with *"HTTP/1.1 200 "* and ommit the reason phrase it usually reported before *"HTTP/1.1 200 OK"*. We have to make sure openshift-java-client can deal with it was: the latest OpenShift REST service is apparently responding without reason phrase: It will respond with *HTTP/1.1 200 * and ommit the reason phrase it usually reported before *HTTP/1.1 200 OK*. We have to make sure openshift-java-client can deal with it > openshift-java-client: make sure is not affected by change in status line response > ---------------------------------------------------------------------------------- > > Key: JBIDE-13708 > URL: https://issues.jboss.org/browse/JBIDE-13708 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Reporter: Andre Dietisheim > > the latest OpenShift REST service is apparently responding without reason phrase: > It will respond with *"HTTP/1.1 200 "* and ommit the reason phrase it usually reported before *"HTTP/1.1 200 OK"*. We have to make sure openshift-java-client can deal with it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13708) openshift-java-client: make sure is not affected by change in status line response

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13708: ------------------------------------- Description: the latest OpenShift REST service is apparently responding without reason phrase: It will respond with *HTTP/1.1 200 * and ommit the reason phrase it usually reported before *HTTP/1.1 200 OK*. We have to make sure openshift-java-client can deal with it > openshift-java-client: make sure is not affected by change in status line response > ---------------------------------------------------------------------------------- > > Key: JBIDE-13708 > URL: https://issues.jboss.org/browse/JBIDE-13708 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Reporter: Andre Dietisheim > > the latest OpenShift REST service is apparently responding without reason phrase: > It will respond with *HTTP/1.1 200 * and ommit the reason phrase it usually reported before *HTTP/1.1 200 OK*. We have to make sure openshift-java-client can deal with it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13708) openshift-java-client: make sure is not affected by change in status line response

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13708: ------------------------------------- Summary: openshift-java-client: make sure is not affected by change in status line response (was: openshift-java-client) > openshift-java-client: make sure is not affected by change in status line response > ---------------------------------------------------------------------------------- > > Key: JBIDE-13708 > URL: https://issues.jboss.org/browse/JBIDE-13708 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Reporter: Andre Dietisheim > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13708) openshift-java-client

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13708: ---------------------------------------- Summary: openshift-java-client Key: JBIDE-13708 URL: https://issues.jboss.org/browse/JBIDE-13708 Project: Tools (JBoss Tools) Issue Type: Enhancement Reporter: Andre Dietisheim -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13611) forge failing to compile due to two poms w/ the same GAV

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13611?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13611: ------------------------------ Fix Version/s: 4.1.0.Alpha2 Affects Version/s: (was: 4.1.0.Alpha1) The problem was only there for a few hours and I it was only in master. > forge failing to compile due to two poms w/ the same GAV > -------------------------------------------------------- > > Key: JBIDE-13611 > URL: https://issues.jboss.org/browse/JBIDE-13611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Koen Aers > Fix For: 4.1.0.Alpha2 > > > {code} > [ERROR] Two or more projects in the reactor have the same identifier, please make sure that <groupId>:<artifactId>:<version> is unique for each project: > {org.jboss.tools.forge.features:org.jboss.tools.forge.feature:1.2.0-SNAPSHOT=[/mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.feature/pom.xml, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.ext.feature/pom.xml], > org.jboss.tools.forge.features:org.jboss.tools.forge.test.feature:1.2.0-SNAPSHOT=[/mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.test.feature/pom.xml, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.ext.test.feature/pom.xml]} -> [Help 1] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13703) Team - Verify the workflow

by Guillaume Radde (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi... ] Guillaume Radde commented on JBIDE-13703: ----------------------------------------- Hey Burr. If I use File - Import -Maven - Existing Maven Projects, then the project opens properly, it detects the Maven project and the pom.xml from the sub-modules and opens them all. The CVS features don't work however if I do that. > Team - Verify the workflow > -------------------------- > > Key: JBIDE-13703 > URL: https://issues.jboss.org/browse/JBIDE-13703 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Burr Sutter > Assignee: Burr Sutter > Attachments: JBDS-usability.pdf > > > The average end-user would like to: > 1) check out (clone) a project from CVS, SVN or Git > -- add repo, navigate repo, check out a project > -- project may or may not have .classpath, .project or .settings files > -- project may be Maven-based > and see if the following work > 2) Are the appropriate facets enabled? > 3) Does it build immediately? > 4) Can I immediately hit the run button to launch it on my app server? > 5) Can I immediately hit the debug button to debug it on my app server? > -- how do I step if there are no break points? > 6) Make a change to a file, re-run/debug again > 7) Run JUnit tests > 8) Check the change back into the repo with comments -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13611) forge failing to compile due to two poms w/ the same GAV

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13611?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13611. ------------------------------- Resolution: Done > forge failing to compile due to two poms w/ the same GAV > -------------------------------------------------------- > > Key: JBIDE-13611 > URL: https://issues.jboss.org/browse/JBIDE-13611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Koen Aers > Fix For: 4.1.0.Alpha2 > > > {code} > [ERROR] Two or more projects in the reactor have the same identifier, please make sure that <groupId>:<artifactId>:<version> is unique for each project: > {org.jboss.tools.forge.features:org.jboss.tools.forge.feature:1.2.0-SNAPSHOT=[/mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.feature/pom.xml, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.ext.feature/pom.xml], > org.jboss.tools.forge.features:org.jboss.tools.forge.test.feature:1.2.0-SNAPSHOT=[/mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.test.feature/pom.xml, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.ext.test.feature/pom.xml]} -> [Help 1] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13707) "Mylyn Issue Tracker connector" cannot be installed from Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13707?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13707: ----------------------------------- Description: When trying to install Maven connectors from Central, one can read: "The following connectors are not available: Mylyn Issue Tracker Connector" https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Log doesn't tell more, excet {code} org.eclipse.core.runtime.CoreException: The following connectors are not available: Mylyn Issue Tracker Connectors (id=org.jboss.tools.common.mylyn.feature.feature.group, site=http://download.jboss.org/jbosstools/updates/development/kepler/cent...) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.checkForUnavailable(PrepareInstallProfileJob_e_3_6.java:300) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.computeInstallableUnits(PrepareInstallProfileJob_e_3_6.java:210) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.run(PrepareInstallProfileJob_e_3_6.java:95) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code} was: When trying to install Maven connectors from Central, one can read: "The following connectors are not available: Mylyn Issue Tracker Connector" https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Log doesn't tell more. > "Mylyn Issue Tracker connector" cannot be installed from Central > ---------------------------------------------------------------- > > Key: JBIDE-13707 > URL: https://issues.jboss.org/browse/JBIDE-13707 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Mickael Istria > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > When trying to install Maven connectors from Central, one can read: > "The following connectors are not available: Mylyn Issue Tracker Connector" > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Log doesn't tell more, excet > {code} > org.eclipse.core.runtime.CoreException: The following connectors are not available: Mylyn Issue Tracker Connectors (id=org.jboss.tools.common.mylyn.feature.feature.group, site=http://download.jboss.org/jbosstools/updates/development/kepler/cent...) > at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.checkForUnavailable(PrepareInstallProfileJob_e_3_6.java:300) > at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.computeInstallableUnits(PrepareInstallProfileJob_e_3_6.java:210) > at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.run(PrepareInstallProfileJob_e_3_6.java:95) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13707) "Mylyn Issue Tracker connector" cannot be installed from Central

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-13707: -------------------------------------- Summary: "Mylyn Issue Tracker connector" cannot be installed from Central Key: JBIDE-13707 URL: https://issues.jboss.org/browse/JBIDE-13707 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.1.0.Alpha1 Reporter: Mickael Istria Assignee: Snjezana Peco Priority: Blocker Fix For: 4.1.0.Alpha1 When trying to install Maven connectors from Central, one can read: "The following connectors are not available: Mylyn Issue Tracker Connector" https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Log doesn't tell more. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2013