September 2013 - jbosstools-issues

[JBoss JIRA] (JBTIS-163) Failed to resolve target definition

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-163?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTIS-163: ----------------------------------------------- Marek Baluch <mbaluch(a)redhat.com> made a comment on [bug 1005683|https://bugzilla.redhat.com/show_bug.cgi?id=1005683] Description of problem: See linked issue. Blocks all test execution. > Failed to resolve target definition > ----------------------------------- > > Key: JBTIS-163 > URL: https://issues.jboss.org/browse/JBTIS-163 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.2, 4.1.3, 4.1.4-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.1.4-TP > > > During building with target platform 4.1.2-SNAPSHOT / 4.1.2.Final (the same for 4.1.3) I'm getting the following error: > [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.2-SNAPSHOT/target-platform-4.1.2-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20130729-2113-B39" in the repositories of the current location -> [Help 1] -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15451) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Webservices]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15451?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15451: --------------------------------------- Hello [~nickboldt], first, sorry for missing step #1 in the description above :-/ I applied PR #82 and #83 to fix the pom parent version, but why to you suggest to bump version from 1.5.0 to 1.5.100 and not 1.6.0 in master branch ? Thanks > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Webservices] > ---------------------------------------------------------- > > Key: JBIDE-15451 > URL: https://issues.jboss.org/browse/JBIDE-15451 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; > 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; > 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; > 4. Close (not resolve) this JIRA when done. [Webservices] > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15469) {MASTER] CLONE - Increment version's service part for jbosstools-base/foundation submodule

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15469?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-15469: ----------------------------------- Assignee: Rob Stryker (was: Denis Golovin) > {MASTER] CLONE - Increment version's service part for jbosstools-base/foundation submodule > ------------------------------------------------------------------------------------------ > > Key: JBIDE-15469 > URL: https://issues.jboss.org/browse/JBIDE-15469 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.1.1.Alpha1 > > > jbosstools-base/foundation submodule had changes since 4.1.0.Final is released: > {code}$ git diff --name-only jbosstools-4.1.0.Final -- foundation > foundation/plugins/org.jboss.tools.foundation.core/.options > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/Trace.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/ecf/internal/InternalURLTransport.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/ecf/internal/URLTransportCache.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/BarrierProgressWaitJob.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/BarrierWaitJob.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/InterruptableJoinJob.java > foundation/pom.xml{code} > No changes in Public API so far and hat means only service version should be incremented: > 1.0.0-SNAPSHOT => 1.0.1-SNAPSHOT -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-163) Failed to resolve target definition

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-163?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-163: ------------------------------------ Affects Version/s: 4.1.4-TP > Failed to resolve target definition > ----------------------------------- > > Key: JBTIS-163 > URL: https://issues.jboss.org/browse/JBTIS-163 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.2, 4.1.3, 4.1.4-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.1.4-TP > > > During building with target platform 4.1.2-SNAPSHOT / 4.1.2.Final (the same for 4.1.3) I'm getting the following error: > [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.2-SNAPSHOT/target-platform-4.1.2-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20130729-2113-B39" in the repositories of the current location -> [Help 1] -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15469) {MASTER] CLONE - Increment version's service part for jbosstools-base/foundation submodule

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15469?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15469: ------------------------------------- Two things to note here: 1) Denis is obviously getting very excited about keeping version numbers compatible with API changes. 2) Foundation is not expected to change much (at this time) for next release 3) Foundation's master version is now BEHIND 4.1.x branch's version. This is bad. I think foundation is a perfect place to try to mark the version as 1.0.100. If there comes a point where API changes are added, it will become very apparent in API Tools, and a proper version bump to minor will occur. I will also be more vigilant on it, and, as it seems, so is Denis. So I think this is a perfect time to mimic the wtp-style of version increments between master and maintenance. > {MASTER] CLONE - Increment version's service part for jbosstools-base/foundation submodule > ------------------------------------------------------------------------------------------ > > Key: JBIDE-15469 > URL: https://issues.jboss.org/browse/JBIDE-15469 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Rob Stryker > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.1.1.Alpha1 > > > jbosstools-base/foundation submodule had changes since 4.1.0.Final is released: > {code}$ git diff --name-only jbosstools-4.1.0.Final -- foundation > foundation/plugins/org.jboss.tools.foundation.core/.options > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/Trace.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/ecf/internal/InternalURLTransport.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/ecf/internal/URLTransportCache.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/BarrierProgressWaitJob.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/BarrierWaitJob.java > foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/InterruptableJoinJob.java > foundation/pom.xml{code} > No changes in Public API so far and hat means only service version should be incremented: > 1.0.0-SNAPSHOT => 1.0.1-SNAPSHOT -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15469) {MASTER] CLONE - Increment version's service part for jbosstools-base/foundation submodule

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15469: ----------------------------------- Summary: {MASTER] CLONE - Increment version's service part for jbosstools-base/foundation submodule Key: JBIDE-15469 URL: https://issues.jboss.org/browse/JBIDE-15469 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core Affects Versions: 4.1.1.Alpha1 Reporter: Rob Stryker Assignee: Denis Golovin Priority: Blocker Fix For: 4.1.1.Alpha1 jbosstools-base/foundation submodule had changes since 4.1.0.Final is released: {code}$ git diff --name-only jbosstools-4.1.0.Final -- foundation foundation/plugins/org.jboss.tools.foundation.core/.options foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/Trace.java foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/ecf/internal/InternalURLTransport.java foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/ecf/internal/URLTransportCache.java foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/BarrierProgressWaitJob.java foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/BarrierWaitJob.java foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/InterruptableJoinJob.java foundation/pom.xml{code} No changes in Public API so far and hat means only service version should be incremented: 1.0.0-SNAPSHOT => 1.0.1-SNAPSHOT -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15396) cannot log into OpenShift (even though credentials are valid)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15396?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15396: ------------------------------------------------- Carlos Díaz <carlosdiazsuarez(a)gmail.com> made a comment on [bug 1003037|https://bugzilla.redhat.com/show_bug.cgi?id=1003037] (In reply to Nam Duong from comment #1) > See > https://www.openshift.com/forums/openshift/the-credentials-for-user-are-not- > valid#comment-33837 > > Upgrade to Kepler worked for me. Ok I did and It works! Thanks. > cannot log into OpenShift (even though credentials are valid) > ------------------------------------------------------------- > > Key: JBIDE-15396 > URL: https://issues.jboss.org/browse/JBIDE-15396 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Attachments: cannot-login.png > > > You cannot log into OpenShift Online using JBoss Tools 4.0 / JBDS6 (JBDS7 and OpenShift Enterprise are not affected) any 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15396) cannot log into OpenShift (even though credentials are valid)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15396?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15396: ------------------------------------------------- weiwei jiang <wjiang(a)redhat.com> made a comment on [bug 1003037|https://bugzilla.redhat.com/show_bug.cgi?id=1003037] Reproduced with eclipse Juno & jboss tool for Juno on PROD; Reproduced with eclipse kepler & jboss tool 4.1.0.final.core on PROD; Can not reproduced with Jboss Developer Studio 7.0.0.GA on PROD; > cannot log into OpenShift (even though credentials are valid) > ------------------------------------------------------------- > > Key: JBIDE-15396 > URL: https://issues.jboss.org/browse/JBIDE-15396 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Attachments: cannot-login.png > > > You cannot log into OpenShift Online using JBoss Tools 4.0 / JBDS6 (JBDS7 and OpenShift Enterprise are not affected) any 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15396) cannot log into OpenShift (even though credentials are valid)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15396?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15396: ------------------------------------------------- weiwei jiang <wjiang(a)redhat.com> changed the Status of [bug 1003037|https://bugzilla.redhat.com/show_bug.cgi?id=1003037] from ON_QA to VERIFIED > cannot log into OpenShift (even though credentials are valid) > ------------------------------------------------------------- > > Key: JBIDE-15396 > URL: https://issues.jboss.org/browse/JBIDE-15396 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Attachments: cannot-login.png > > > You cannot log into OpenShift Online using JBoss Tools 4.0 / JBDS6 (JBDS7 and OpenShift Enterprise are not affected) any 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15396) cannot log into OpenShift (even though credentials are valid)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15396?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15396: ------------------------------------------------- weiwei jiang <wjiang(a)redhat.com> made a comment on [bug 1003037|https://bugzilla.redhat.com/show_bug.cgi?id=1003037] Test on STG(dev_stage_375), and work well, so verified this. > cannot log into OpenShift (even though credentials are valid) > ------------------------------------------------------------- > > Key: JBIDE-15396 > URL: https://issues.jboss.org/browse/JBIDE-15396 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Attachments: cannot-login.png > > > You cannot log into OpenShift Online using JBoss Tools 4.0 / JBDS6 (JBDS7 and OpenShift Enterprise are not affected) any 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, 7 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 2013