February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16638) Improve UI of Deployment Scanner settings

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16638?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-16638: ---------------------------------- Attachment: scanner-options.png > Improve UI of Deployment Scanner settings > ----------------------------------------- > > Key: JBIDE-16638 > URL: https://issues.jboss.org/browse/JBIDE-16638 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2b B71 > Reporter: Martin Malina > Fix For: 4.2.0.Beta1 > > Attachments: scanner-options.png > > > Looking at the new options introduced in JBIDE-15287, I don't quite like to look of it. > Let me know if you disagree, but using "(default)" in a field that's supposed to take numbers is not very nice. > Instead, I propose adding a checkbox in front of the options: -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16638) Improve UI of Deployment Scanner settings

by Martin Malina (JIRA)

Martin Malina created JBIDE-16638: ------------------------------------- Summary: Improve UI of Deployment Scanner settings Key: JBIDE-16638 URL: https://issues.jboss.org/browse/JBIDE-16638 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Affects Versions: 4.2.0.Alpha2 Environment: JBDS 8.0.0.Alpha2b B71 Reporter: Martin Malina Fix For: 4.2.0.Beta1 Looking at the new options introduced in JBIDE-15287, I don't quite like to look of it. Let me know if you disagree, but using "(default)" in a field that's supposed to take numbers is not very nice. Instead, I propose adding a checkbox in front of the options: -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16535) Deploy only server missing several subsystems

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16535?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-16535. --------------------------------- Verified in JBDS 8.0.0.Alpha2b B71 > Deploy only server missing several subsystems > --------------------------------------------- > > Key: JBIDE-16535 > URL: https://issues.jboss.org/browse/JBIDE-16535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Labels: respin-a > Fix For: 4.2.0.Alpha2 > > > Several subsystems are not mapped into deploy-only server at all. This makes the server behave very badly, with many operations failing. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15928) Tweak publish.sh to allow copying of javadoc along with the p2 repo

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15928?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-15928. ----------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.x) Resolution: Won't Fix I'm resolving this as Won't fix. I decided that it would be too cumbersome to use publish.sh for this. I used openshift to host the javadoc - it's not something critical, so I think openshift is fine here. If you're interested in more details, see here: https://github.com/jboss-reddeer/reddeer/pull/46 > Tweak publish.sh to allow copying of javadoc along with the p2 repo > ------------------------------------------------------------------- > > Key: JBIDE-15928 > URL: https://issues.jboss.org/browse/JBIDE-15928 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.1.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.2.0.Alpha2 > > > We would like to be able to publish javadoc regularly along with the p2 repo. > E.g. we have this: > http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/all/repo/ > Generated by: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Using publish.sh: > http://raw.github.com/jbosstools/jbosstools-build-ci/master/publish/publi... > We would like to get something like this: > http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/all/ja... > To generate javadoc of RedDeer, you need to run: > mvn install > mvn javadoc:javadoc > See this PR that adds javadoc support for RedDeer: > https://github.com/jboss-reddeer/reddeer/pull/46 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16173) org.jboss.tools.stacks.core.test.StacksCoreTest fails

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16173?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-16173: -------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > org.jboss.tools.stacks.core.test.StacksCoreTest fails > ----------------------------------------------------- > > Key: JBIDE-16173 > URL: https://issues.jboss.org/browse/JBIDE-16173 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.tools.stacks.core.test.StacksAllTests > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 0.353 sec <<< FAILURE! > testManagerUseDefaultStacks(org.jboss.tools.stacks.core.test.StacksCoreTest) Time elapsed: 0.308 sec <<< FAILURE! > junit.framework.AssertionFailedError > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertNotNull(Assert.java:256) > at junit.framework.Assert.assertNotNull(Assert.java:248) > at junit.framework.TestCase.assertNotNull(TestCase.java:417) > at org.jboss.tools.stacks.core.test.StacksCoreTest.testManagerUseDefaultStacks(StacksCoreTest.java:48) > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16173) org.jboss.tools.stacks.core.test.StacksCoreTest fails

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16173?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-16173. --------------------------------- Resolution: Done Fixed for beta. Not necessary for a2. Can leave the test ignored for now. > org.jboss.tools.stacks.core.test.StacksCoreTest fails > ----------------------------------------------------- > > Key: JBIDE-16173 > URL: https://issues.jboss.org/browse/JBIDE-16173 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.tools.stacks.core.test.StacksAllTests > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 0.353 sec <<< FAILURE! > testManagerUseDefaultStacks(org.jboss.tools.stacks.core.test.StacksCoreTest) Time elapsed: 0.308 sec <<< FAILURE! > junit.framework.AssertionFailedError > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertNotNull(Assert.java:256) > at junit.framework.Assert.assertNotNull(Assert.java:248) > at junit.framework.TestCase.assertNotNull(TestCase.java:417) > at org.jboss.tools.stacks.core.test.StacksCoreTest.testManagerUseDefaultStacks(StacksCoreTest.java:48) > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15896) RuntimeWorkbenchUtils.refreshServersView() throws exception sometimes when running tycho tests

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15896?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15896: ------------------------------------- [~snjeza] is there a stacktrace available that has jbt code in it instead of just build code? > RuntimeWorkbenchUtils.refreshServersView() throws exception sometimes when running tycho tests > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-15896 > URL: https://issues.jboss.org/browse/JBIDE-15896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.1.x > Reporter: Snjezana Peco > Assignee: Rob Stryker > > The issue can happen in a component that requires the runtime component. > See build #307 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-portlet_m... > {code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.19.0:test (default-test) on project org.jboss.tools.portlet.core.test: An unexpected error occured (return code 13). See log for details. -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.19.0:test (default-test) on project org.jboss.tools.portlet.core.test: An unexpected error occured (return code 13). See log for details. > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > 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: org.apache.maven.plugin.MojoFailureException: An unexpected error occured (return code 13). See log for details. > at org.eclipse.tycho.surefire.TestMojo.runTest(TestMojo.java:970) > at org.eclipse.tycho.surefire.TestMojo.execute(TestMojo.java:668) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16467) Streamline server groups in New Server dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16467?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16467: ------------------------------------- [~gercan] Do you have a link to a bugzilla about removing the 'jboss' category in servertools? > Streamline server groups in New Server dialog > --------------------------------------------- > > Key: JBIDE-16467 > URL: https://issues.jboss.org/browse/JBIDE-16467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > > Today I noticed that the group for JBoss EAP servers is now called Red Hat JBoss Middleware (JBIDE-15269). Seeing it got me thinking that the way it is now is actually pretty confusing and looks like a mess. Let me explain. > When you have JBoss Tools installed today, you get 3 JBoss-related groups in the New Server dialog. > 1. JBoss - this is in Eclipse by default. It contains very old servers only - up to JBoss AS 5. Could we possibly lobby for getting this removed/replaced with our own adapters? > 2. JBoss Community - this is where all our JBoss AS and Wildfly adapters are. > 3. Red Hat JBoss Middleware - this contains all EAP servers. > When you try to look at it from a new user's perspective, somebody who doesn't work at RH, it can give the impression that probably nobody took the time to put some order to this - there are 3 different groups, not even next to one another (because it's sorted alphabetically of course). > Granted, the Eclipse's JBoss group is not in our control, but maybe we can try to do something there, too? > I'm not sure what's the solution here. But if we must use Red Hat JBoss Middleware, couldn't we put everything in this group? Or are there any other alternatives to the current state? Or is it just me who finds this confusing? Opinions welcome. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16297) Label for JMX Content is missing in 'Cusomize View ...-> Contents' for Servers View

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16297?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-16297. --------------------------------- Resolution: Done pushed to master > Label for JMX Content is missing in 'Cusomize View ...-> Contents' for Servers View > ----------------------------------------------------------------------------------- > > Key: JBIDE-16297 > URL: https://issues.jboss.org/browse/JBIDE-16297 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, server > Affects Versions: 4.1.1.Final > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Trivial > Attachments: Selection_022.png > > > It seems Server Content is also should have icon > !Selection_022.png! -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9212) Consider introducing Profiles of AS Server adapteres

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9212?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-9212: ------------------------------- Fix Version/s: 4.2.0.Beta1 (was: LATER) > Consider introducing Profiles of AS Server adapteres > ---------------------------------------------------- > > Key: JBIDE-9212 > URL: https://issues.jboss.org/browse/JBIDE-9212 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.0.Beta1 > > > With all the different combinations of server behaviors and pollers dependent if you are runnig locally, remotely, openshift express or openshift flex it becomes hard to configure/tweak. > Idea is to introduce the notion of profiles, provide a set of default ones users can apply in Server Wizard or even in the server editor and allow them to create new ones based on existing ones. > These profiles would cover: > ports, start/stop behavior, pollers, deployments and launch setup. (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, 2 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 February 2014