February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16645) Seam Portlet deployed on EPP 5.2 is in error

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16645?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-16645: ------------------------------------ Summary: Seam Portlet deployed on EPP 5.2 is in error (was: Seam Portlet deployed on EPP 5.2 in error) > Seam Portlet deployed on EPP 5.2 is in error > -------------------------------------------- > > Key: JBIDE-16645 > URL: https://issues.jboss.org/browse/JBIDE-16645 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.2.0.Alpha2 > Environment: EPP-5.2.2.GA with Seam 2.2.5.EAP5 > Reporter: Radoslav Rábara > Priority: Blocker > Fix For: 4.2.0.Beta1 > > > Seam portal project deployed on EPP 5.2 is in error. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16592) Allow to update/remove software installed from Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16592: ---------------------------------------- A single "Install/Update" button sounds good. About Early-Access, my idea was that the same entry could show the Early-Access and "Release" component. It seems in your proposal that you expect those to be different entries in the catalog. Did I get it right? I agree that splitting "Normal" and "Early-Access" entries is a good thing. It reduces the number of status to handle and then the number of possible actions. > Allow to update/remove software installed from Central > ------------------------------------------------------ > > Key: JBIDE-16592 > URL: https://issues.jboss.org/browse/JBIDE-16592 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Fix For: 4.2.0.Beta1 > > Attachments: JBIDE-16592-wip.jpeg, JBIDE_16592_shot2.jpeg > > > Central software page should allow user to update or uninstall some modules. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2943: ------------------------------ CDW devel_ack: ? CDW qa_ack: ? > Add m2eclipse-egit to JBDS installer > ------------------------------------ > > Key: JBDS-2943 > URL: https://issues.jboss.org/browse/JBDS-2943 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, installer > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Burr Sutter > > Since [m2eclipse-egit|https://github.com/tesla/m2eclipse-egit] (nor any other m2e SCM connector) is installed by default with JBDS, the Maven SCM import wizard is useless (see JBIDE-16574) > I propose we add m2eclipse-egit to the JBDS installer, as we already have m2e and egit in there, so the use case described in JBIDE-16574 can work OOTB. > Other, less ideal solution would be to add m2eclipse-egit to JBoss Central, but that would add little value over the existing m2e discovery mechanism. > Latest m2eclipse-egit build is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0.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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2943: ----------------------------- CDW devel_ack: (was: ?) CDW pm_ack: (was: ?) CDW qa_ack: (was: ?) > Add m2eclipse-egit to JBDS installer > ------------------------------------ > > Key: JBDS-2943 > URL: https://issues.jboss.org/browse/JBDS-2943 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, installer > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Burr Sutter > > Since [m2eclipse-egit|https://github.com/tesla/m2eclipse-egit] (nor any other m2e SCM connector) is installed by default with JBDS, the Maven SCM import wizard is useless (see JBIDE-16574) > I propose we add m2eclipse-egit to the JBDS installer, as we already have m2e and egit in there, so the use case described in JBIDE-16574 can work OOTB. > Other, less ideal solution would be to add m2eclipse-egit to JBoss Central, but that would add little value over the existing m2e discovery mechanism. > Latest m2eclipse-egit build is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0.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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2943: ------------------------------ CDW release: ? Status: New (was: New) Target Release: 8.0.0.GA > Add m2eclipse-egit to JBDS installer > ------------------------------------ > > Key: JBDS-2943 > URL: https://issues.jboss.org/browse/JBDS-2943 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, installer > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Burr Sutter > > Since [m2eclipse-egit|https://github.com/tesla/m2eclipse-egit] (nor any other m2e SCM connector) is installed by default with JBDS, the Maven SCM import wizard is useless (see JBIDE-16574) > I propose we add m2eclipse-egit to the JBDS installer, as we already have m2e and egit in there, so the use case described in JBIDE-16574 can work OOTB. > Other, less ideal solution would be to add m2eclipse-egit to JBoss Central, but that would add little value over the existing m2e discovery mechanism. > Latest m2eclipse-egit build is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0.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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2943: ----------------------------- CDW pm_ack: ? > Add m2eclipse-egit to JBDS installer > ------------------------------------ > > Key: JBDS-2943 > URL: https://issues.jboss.org/browse/JBDS-2943 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, installer > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Burr Sutter > > Since [m2eclipse-egit|https://github.com/tesla/m2eclipse-egit] (nor any other m2e SCM connector) is installed by default with JBDS, the Maven SCM import wizard is useless (see JBIDE-16574) > I propose we add m2eclipse-egit to the JBDS installer, as we already have m2e and egit in there, so the use case described in JBIDE-16574 can work OOTB. > Other, less ideal solution would be to add m2eclipse-egit to JBoss Central, but that would add little value over the existing m2e discovery mechanism. > Latest m2eclipse-egit build is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0.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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer

by Fred Bricon (JIRA)

Fred Bricon created JBDS-2943: --------------------------------- Summary: Add m2eclipse-egit to JBDS installer Key: JBDS-2943 URL: https://issues.jboss.org/browse/JBDS-2943 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: central, installer Affects Versions: 7.1.0.GA Reporter: Fred Bricon Assignee: Burr Sutter Since [m2eclipse-egit|https://github.com/tesla/m2eclipse-egit] (nor any other m2e SCM connector) is installed by default with JBDS, the Maven SCM import wizard is useless (see JBIDE-16574) I propose we add m2eclipse-egit to the JBDS installer, as we already have m2e and egit in there, so the use case described in JBIDE-16574 can work OOTB. Other, less ideal solution would be to add m2eclipse-egit to JBoss Central, but that would add little value over the existing m2e discovery mechanism. Latest m2eclipse-egit build is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0.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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2943: ------------------------------ CDW devel_ack: ? CDW pm_ack: ? CDW qa_ack: ? > Add m2eclipse-egit to JBDS installer > ------------------------------------ > > Key: JBDS-2943 > URL: https://issues.jboss.org/browse/JBDS-2943 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, installer > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Burr Sutter > > Since [m2eclipse-egit|https://github.com/tesla/m2eclipse-egit] (nor any other m2e SCM connector) is installed by default with JBDS, the Maven SCM import wizard is useless (see JBIDE-16574) > I propose we add m2eclipse-egit to the JBDS installer, as we already have m2e and egit in there, so the use case described in JBIDE-16574 can work OOTB. > Other, less ideal solution would be to add m2eclipse-egit to JBoss Central, but that would add little value over the existing m2e discovery mechanism. > Latest m2eclipse-egit build is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0.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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16630) Table of seam runtimes is not updated after seam was added via runtime detection

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16630?page=com.atlassian.jira.plugi... ] Radoslav Rábara commented on JBIDE-16630: ----------------------------------------- Hi [~snjeza], I use jboss-epp-5.2.2.GA. > Table of seam runtimes is not updated after seam was added via runtime detection > -------------------------------------------------------------------------------- > > Key: JBIDE-16630 > URL: https://issues.jboss.org/browse/JBIDE-16630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.0.Alpha2 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Fix For: 4.2.0.Beta1 > > > The table Seam Runtime Environment in Preferences is not updated right after the runtime with seam was added via runtime detection. -- 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, 1 month

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 updated JBIDE-15896: -------------------------------- Priority: Minor (was: Major) > 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 > Priority: Minor > > 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, 1 month

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