March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2424) Still seeing screen corruption after an initial install

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2424?page=com.atlassian.jira.plugin.... ] Len DiMaggio reopened JBDS-2424: -------------------------------- > Still seeing screen corruption after an initial install > ------------------------------------------------------- > > Key: JBDS-2424 > URL: https://issues.jboss.org/browse/JBDS-2424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 6.0.0.CR1 > Environment: Version: 6.0.0.CR1 > Build id: CR1-v20121204-0201-B166 > Build date: 20121204-0201 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: LATER > > Attachments: Screenshot-4.png, Screenshot-5.png > > > See attached screen shot - this is seen on the initial startup after install. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13704) Cannot build integration-tests from branch 4.0.x

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13704?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-13704: ------------------------------------ Assignee: Martin Malina (was: Len DiMaggio) > Cannot build integration-tests from branch 4.0.x > ------------------------------------------------ > > Key: JBIDE-13704 > URL: https://issues.jboss.org/browse/JBIDE-13704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: QA > Reporter: Tomas Remes > Assignee: Martin Malina > > Running mvn clean install -DskipTests on the clean repo, I got: > {noformat} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.ide.eclipse.as.ui.bot.test 4.0.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.ui.bot.ext 4.0.0.qualifier requires 'bundle org.eclipse.zest.core 1.2.0' but it could not be found > [ERROR] Cannot satisfy dependency: org.jboss.ide.eclipse.as.ui.bot.test 4.0.0.qualifier depends on: bundle org.jboss.tools.ui.bot.ext 1.0.0 > [ERROR] > [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.core 1.2.0.", "Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.layouts 1.1.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.core 1.2.0.", "Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.layouts 1.1.0.", "No solution found because the problem is unsatisfiable."] > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.core 1.2.0.", "Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.layouts 1.1.0.", "No solution found because the problem is unsatisfiable."] > at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:77) > at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:89) > at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:122) > at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:80) > at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:377) > at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:354) > at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:103) > at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:82) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > ... 11 more > {noformat} -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2485) Investigate use of Subclipse 1.8.18 & SVNKit 1.7.8.1 in Central

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2485?page=com.atlassian.jira.plugin.... ] Len DiMaggio reassigned JBDS-2485: ---------------------------------- Assignee: Vlado Pakan (was: Len DiMaggio) > Investigate use of Subclipse 1.8.18 & SVNKit 1.7.8.1 in Central > --------------------------------------------------------------- > > Key: JBDS-2485 > URL: https://issues.jboss.org/browse/JBDS-2485 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Vlado Pakan > Fix For: 7.0.0.Alpha2 > > > New mirrors: > http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.8.1... > https://devstudio.jboss.com/updates/requirements/subclipse/1.8.18_1.7.8.1/ > New composites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/ > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2395) Investigate use of SpringIDE 3.x in JBoss 6.x & 7.x Central

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2395?page=com.atlassian.jira.plugin.... ] Len DiMaggio reassigned JBDS-2395: ---------------------------------- Assignee: Jaroslav Jankovič (was: Len DiMaggio) > Investigate use of SpringIDE 3.x in JBoss 6.x & 7.x Central > ----------------------------------------------------------- > > Key: JBDS-2395 > URL: https://issues.jboss.org/browse/JBDS-2395 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 6.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jaroslav Jankovič > Priority: Blocker > Fix For: 6.0.1.GA, 7.0.0.Alpha2 > > > As reported in JBDS-2280, there are two problems with Spring IDE 3.0: > * [IDE-1263|https://jira.springsource.org/browse/IDE-1263] - fixed in 3.1.0 > * [IDE-1264|https://jira.springsource.org/browse/IDE-1264] - fixed in 3.2.0.M1 > Cannot find a site w/ a 3.2.0 milestone on it (yet), but did find these: > https://dist.springframework.org/milestone/IDE/ - 3.1.0.201209120646-M1 (maybe misnamed?) > http://dist.springframework.org/snapshot/IDE/nightly/ - 3.2.0.201211201813-CI-B170 > Also, 3.1.0 release version is currently on Eclipse Marketplace. > Suggest we wait until they release 3.2.0 in March and include it then in our next release. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13682) Investigate use of Atlassian 3.2 in JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-13682: ---------------------------------- Assignee: Nick Boldt (was: Victor Rubezhny) TODO (in this JIRA, no need for separate ones): * target platform to include subset of 3.2.0 (4 plugins only) * common.mylyn plugin to depend on 3.2.0 (4 plugins only) * central site to include Atlassian 3.2.0 (full release) * central discovery plugin to list the correct content (updated list of features) > Investigate use of Atlassian 3.2 in JBoss Central > ------------------------------------------------- > > Key: JBIDE-13682 > URL: https://issues.jboss.org/browse/JBIDE-13682 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno. > There is also a 3.2 available: > https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo... > available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-12320) support protocol version 1.2 in openshift-java-client

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12320?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12320: ------------------------------------- Description: The protocol for the OpenShift REST service has evolved over time and currently has v1.3. The rest service currently delivers 1.0, 1.1, 1.2 and 1.3. OpenShift Enterprise talks 1.2 and we therefore want to drop everything below it 2012-03-14 in #libra {quote} 07:08:20 PM) clayton: then adietish that's your answer - you're good to drop 1.1 and 1.0 support because we have no supported products in the field that use those api versions {quote} was: The protocol for the OpenShift REST service has evolved over time and currently has v1.3. The rest service currently delivers 1.0, 1.1, 1.2 and 1.3. OpenShift Enterprise talks 1.2 and we therefore want to drop everything below it {quote:title=2012-03-14 in #libra} 07:08:20 PM) clayton: then adietish that's your answer - you're good to drop 1.1 and 1.0 support because we have no supported products in the field that use those api versions {quote} > support protocol version 1.2 in openshift-java-client > ----------------------------------------------------- > > Key: JBIDE-12320 > URL: https://issues.jboss.org/browse/JBIDE-12320 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.1.x > > > The protocol for the OpenShift REST service has evolved over time and currently has v1.3. The rest service currently delivers 1.0, 1.1, 1.2 and 1.3. > OpenShift Enterprise talks 1.2 and we therefore want to drop everything below it > 2012-03-14 in #libra > {quote} > 07:08:20 PM) clayton: then adietish that's your answer - you're good to drop 1.1 and 1.0 support because we have no supported products in the field that use those api versions > {quote} -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-12320) support protocol version 1.2 in openshift-java-client

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12320?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12320: ------------------------------------- Summary: support protocol version 1.2 in openshift-java-client (was: support protocol version 1.1 in openshift-java-client) Description: The protocol for the OpenShift REST service has evolved over time and currently has v1.3. The rest service currently delivers 1.0, 1.1, 1.2 and 1.3. OpenShift Enterprise talks 1.2 and we therefore want to drop everything below it {quote:title=2012-03-14 in #libra} 07:08:20 PM) clayton: then adietish that's your answer - you're good to drop 1.1 and 1.0 support because we have no supported products in the field that use those api versions {quote} was:the REST protocol that we use to talk to the OpenShift broker was bumped to 1.1 today. The change that triggers it is a change in the cartridges that you get reported when listing them on a application. We have to support protocol 1.1 for the openshift-java-client > support protocol version 1.2 in openshift-java-client > ----------------------------------------------------- > > Key: JBIDE-12320 > URL: https://issues.jboss.org/browse/JBIDE-12320 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.1.x > > > The protocol for the OpenShift REST service has evolved over time and currently has v1.3. The rest service currently delivers 1.0, 1.1, 1.2 and 1.3. > OpenShift Enterprise talks 1.2 and we therefore want to drop everything below it > {quote:title=2012-03-14 in #libra} > 07:08:20 PM) clayton: then adietish that's your answer - you're good to drop 1.1 and 1.0 support because we have no supported products in the field that use those api versions > {quote} -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13672: ------------------------------------ Ugh. The above idea doesn't work because the property file has to exist BEFORE the job starts, not at the end. And you can't embed HTML in a Build Name, only in the Build Description. So... new approach. Dump a pile of HTML into the log, then scoop it up with a regex match in the Build Description. > could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13672 > URL: https://issues.jboss.org/browse/JBIDE-13672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. > May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > Sample files to check: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13791) Visual Page Editor does not show current cursor position during drag & drop

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13791?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13791: ---------------------------------- Description: Test case: EXECUTE: 1. Create Java Project "test" 2. Create folder "test" in test project 3. Create file "test.html" in test folder {code} <!DOCTYPE html> <html> <head> <meta name="viewport" content="width=device-width, initial-scale=1"> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" /> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script> <script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script> </head> <body> </body> </html> {code} 4. Open file test.html in Visual Page Editor ASSERT: Visual Page Editor appears with test.html and jQuery Mobile Widget Palette on the right side 5. Select tab "Source" of Visual Page Editor 6. Try to drag over the editor any element from palette FAIL: Visual Page Editor does not show current cursor position was: Test case: EXECUTE: 1. Create Java Project "test" 2. Create folder "test" in test project 3. Create file "test.html" in test folder {code} <!DOCTYPE html> <html> <head> <meta name="viewport" content="width=device-width, initial-scale=1"> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" /> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script> <script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script> </head> <body> </body> </html> {code} 4. Open file test.html in Visual Page Editor ASSERT: Visual Page Editor appears with test.html and jQuery Mobile Widget Palette on the right side 5. Select tab "Source" of Visual Page Editor 5. Try to drag over the editor any element from palette FAIL: Visual Page Editor does not show current cursor position > Visual Page Editor does not show current cursor position during drag & drop > --------------------------------------------------------------------------- > > Key: JBIDE-13791 > URL: https://issues.jboss.org/browse/JBIDE-13791 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Fix For: 4.1.0.Alpha2 > > > Test case: > EXECUTE: > 1. Create Java Project "test" > 2. Create folder "test" in test project > 3. Create file "test.html" in test folder > {code} > <!DOCTYPE html> > <html> > <head> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" /> > <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script> > <script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script> > </head> > <body> > </body> > </html> > {code} > 4. Open file test.html in Visual Page Editor > ASSERT: Visual Page Editor appears with test.html and jQuery Mobile Widget Palette on the right side > 5. Select tab "Source" of Visual Page Editor > 6. Try to drag over the editor any element from palette > FAIL: Visual Page Editor does not show current cursor position -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13791) Visual Page Editor does not show current cursor position during drag & drop

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-13791: ------------------------------------- Summary: Visual Page Editor does not show current cursor position during drag & drop Key: JBIDE-13791 URL: https://issues.jboss.org/browse/JBIDE-13791 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.1.0.Alpha1 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 4.1.0.Alpha2 Test case: EXECUTE: 1. Create Java Project "test" 2. Create folder "test" in test project 3. Create file "test.html" in test folder {code} <!DOCTYPE html> <html> <head> <meta name="viewport" content="width=device-width, initial-scale=1"> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" /> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script> <script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script> </head> <body> </body> </html> {code} 4. Open file test.html in Visual Page Editor ASSERT: Visual Page Editor appears with test.html and jQuery Mobile Widget Palette on the right side 5. Select tab "Source" of Visual Page Editor 5. Try to drag over the editor any element from palette FAIL: Visual Page Editor does not show current cursor position -- 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

13 years

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 March 2013