March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13696) Remove test plugins form code coverage reports

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13696?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-13696: --------------------------------------- Tests were always out of coverage reports in emma coverage and I don't remember any requests to include them int coverage. It looks like regression for me, but I am marking it as optional, since high code coverage is never was considered as a high priority task. > Remove test plugins form code coverage reports > ---------------------------------------------- > > Key: JBIDE-13696 > URL: https://issues.jboss.org/browse/JBIDE-13696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha2 > Reporter: Denis Golovin > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.1.0.Alpha2 > > -- 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-13696) Remove test plugins form code coverage reports

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13696?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13696: ---------------------------------- Priority: Optional (was: Major) > Remove test plugins form code coverage reports > ---------------------------------------------- > > Key: JBIDE-13696 > URL: https://issues.jboss.org/browse/JBIDE-13696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha2 > Reporter: Denis Golovin > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.1.0.Alpha2 > > -- 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-13704) Cannot build integration-tests from branch 4.0.x

by Tomas Remes (JIRA)

Tomas Remes created JBIDE-13704: ----------------------------------- Summary: 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: Len DiMaggio 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13483) Update as bot test for a new string in EAP 6.1

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13483?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-13483: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-tests/pull/176, https://github.com/jbosstools/jbosstools-integration-tests/pull/180 (was: https://github.com/jbosstools/jbosstools-integration-tests/pull/176) > Update as bot test for a new string in EAP 6.1 > ---------------------------------------------- > > Key: JBIDE-13483 > URL: https://issues.jboss.org/browse/JBIDE-13483 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: QA > Affects Versions: 4.0.2.Final, 4.1.0.Alpha1 > Reporter: Martin Malina > Assignee: Radim Hopp > Fix For: 4.0.x, 4.1.0.Alpha1 > > > Some of the tests in https://github.com/jbosstools/jbosstools-integration-tests/tree/master/te... will need to be updated to accommodate a slight change in EAP 6.1. > When you deploy a project the log used to contain: > Registering web context: /jsp-project > But now in EAP 6.1.0.DR3 it says: > Register web context: /jsp-project > See the test failure here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-JBDS... > The expected string is actually defined in org.jboss.ide.eclipse.as.ui.bot.test/src/org/jboss/ide/eclipse/as/ui/bot/test/eap6/DeployJSPProjectEAP6Server.java > and the fix would be trivial. But it's probably better to create a new template for 6.1 and have it separate from 6.0. -- 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 Burr Sutter (JIRA)

Burr Sutter created JBIDE-13703: ----------------------------------- Summary: 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 The average end-user would like to: check out (clone) a project from CVS, SVN or Git -- 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 favorite app server? - how do I step if there are no break points? 6) Make a change to a file 7) Run tests 8) Check the change back in 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-13701) New - the New sub-menu on a project is a problem

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13701?page=com.atlassian.jira.plugi... ] Burr Sutter reassigned JBIDE-13701: ----------------------------------- Assignee: Burr Sutter > New - the New sub-menu on a project is a problem > ------------------------------------------------ > > Key: JBIDE-13701 > URL: https://issues.jboss.org/browse/JBIDE-13701 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Burr Sutter > Assignee: Burr Sutter > > The New submenu off the project's context menu (Project Explorer) is either too cluttered or does not provide me with the right options. It needs more intelligence. -- 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-13702) ForgeCorePlugin could use an installed Forge 2 Runtime

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-13702: --------------------------------------- Summary: ForgeCorePlugin could use an installed Forge 2 Runtime Key: JBIDE-13702 URL: https://issues.jboss.org/browse/JBIDE-13702 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Reporter: George Gastaldi Assignee: Koen Aers In Forge 1, it is possible to configure external Forge runtimes. In Forge 2 it would be nice to allow configuration of that, but also avoid the need to unzip the files in the startup. -- 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-13701) New - the New sub-menu on a project is a problem

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-13701: ----------------------------------- Summary: New - the New sub-menu on a project is a problem Key: JBIDE-13701 URL: https://issues.jboss.org/browse/JBIDE-13701 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Burr Sutter The New submenu off the project's context menu (Project Explorer) is either too cluttered or does not provide me with the right options. It needs more intelligence. -- 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-13700) Run - The Eclipse Run button needs intelligence

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-13700: ----------------------------------- Summary: Run - The Eclipse Run button needs intelligence Key: JBIDE-13700 URL: https://issues.jboss.org/browse/JBIDE-13700 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Burr Sutter Assignee: Burr Sutter The Run button is a serious usability problem. At a minimum, we need to find a way to make it work as soon a new project is created or imported. -- 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-13699) Confusing web.xml declaration in generated CDI Web Project

by Tomas Remes (JIRA)

Tomas Remes created JBIDE-13699: ----------------------------------- Summary: Confusing web.xml declaration in generated CDI Web Project Key: JBIDE-13699 URL: https://issues.jboss.org/browse/JBIDE-13699 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 4.0.0.Final Environment: JBDS 6.0.0.GA Reporter: Tomas Remes Assignee: Alexey Kazakov Newly generated CDI Web project contains following web.xml declaration: {noformat} <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0"> {noformat} I think we would like to use 3.0 declaration and not any mixture. -- 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