March 2014 - jbosstools-issues - Jboss List Archives

[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: ------------------------------ Fix Version/s: 8.0.0.Beta1 > 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: installer, maven > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Burr Sutter > Priority: Critical > Fix For: 8.0.0.Beta1 > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16608) Central tab is empty for IS and Core download

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16608?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16608: ------------------------------------ I'll morph a version of http://marketplace.eclipse.org/sites/all/modules/custom/marketplace/image... to include the JBT and JBDS logoballs. > Central tab is empty for IS and Core download > --------------------------------------------- > > Key: JBIDE-16608 > URL: https://issues.jboss.org/browse/JBIDE-16608 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.2.0.Beta1 > > > Expected the central tab to actually describe how to use Central to get IS (similar to marketplace) -- 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, 3 months

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 commented on JBDS-2943: ----------------------------------- I updated the m2e discovery catalog last night, so can now install (https://bugs.eclipse.org/bugs/show_bug.cgi?id=429360). When did you try it? Not sure about BYOE, I don't see where the problem is actually. If the JBDS feature we install from BYOE depends on the m2eclipse-egit one, then what's the issue? > 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: installer, maven > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Burr Sutter > Priority: Critical > > 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, 3 months

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 edited comment on JBDS-2943 at 3/5/14 9:48 AM: ----------------------------------------------------------- I updated the m2e discovery catalog last night, so it can now install (https://bugs.eclipse.org/bugs/show_bug.cgi?id=429360). When did you try it? Not sure about BYOE, I don't see where the problem is actually. If the JBDS feature we install from BYOE depends on the m2eclipse-egit one, then what's the issue? was (Author: fbricon): I updated the m2e discovery catalog last night, so can now install (https://bugs.eclipse.org/bugs/show_bug.cgi?id=429360). When did you try it? Not sure about BYOE, I don't see where the problem is actually. If the JBDS feature we install from BYOE depends on the m2eclipse-egit one, then what's the issue? > 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: installer, maven > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Burr Sutter > Priority: Critical > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2691) Incomplete build path for Spring Web Project when Spring plugins are installed

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-2691?page=com.atlassian.jira.plugin.... ] Radim Hopp updated JBDS-2691: ----------------------------- Affects Version/s: 7.1.1.CR1 > Incomplete build path for Spring Web Project when Spring plugins are installed > ------------------------------------------------------------------------------ > > Key: JBDS-2691 > URL: https://issues.jboss.org/browse/JBDS-2691 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies, central, upstream > Affects Versions: 7.0.0.CR1, 7.1.1.CR1 > Environment: JBDS 7.0.0.CR1a, L64 > Reporter: Jiri Peterka > Assignee: Fred Bricon > Fix For: 8.0.0.GA > > Attachments: build-path-is-incomplete.png > > > Build path is incomplete. Cannot find class file for javax/servlet/ServletContext -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2691) Incomplete build path for Spring Web Project when Spring plugins are installed

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-2691?page=com.atlassian.jira.plugin.... ] Radim Hopp commented on JBDS-2691: ---------------------------------- In JBDS 7.1.1.CR1 I came across error after importing Spring Project archetype from JBoss Central (both enterprise=true,false) {noformat}The superclass "javax.servlet.http.HttpServlet" was not found on the Java Build Path{noformat} The error marker was on first line jboss-springmvc-webapp/src/main/webapp/WEB-INF/views/index.jsp This seems rather similar to this JIRA. Also workaround described in this jira is applicable here thus adding 7.1.1.CR1 to affets version. If you think this should be separate jira, please let me know. > Incomplete build path for Spring Web Project when Spring plugins are installed > ------------------------------------------------------------------------------ > > Key: JBDS-2691 > URL: https://issues.jboss.org/browse/JBDS-2691 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies, central, upstream > Affects Versions: 7.0.0.CR1 > Environment: JBDS 7.0.0.CR1a, L64 > Reporter: Jiri Peterka > Assignee: Fred Bricon > Fix For: 8.0.0.GA > > Attachments: build-path-is-incomplete.png > > > Build path is incomplete. Cannot find class file for javax/servlet/ServletContext -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16402) A newly created project is not imported into Eclipse when the project location is non-existent

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16402?page=com.atlassian.jira.plugi... ] Vineet Reynolds commented on JBIDE-16402: ----------------------------------------- Well this seems to have been fixed. I cannot reproduce this with the recollection of what must have been the test case: specify {{/tmp/foo/bar}} as the Project location (where the subdirectories are non-existent), and create a project with name {{helloworld}}. This now creates a project at {{/tmp/foo/bar/helloworld}} and imports it as expected. > A newly created project is not imported into Eclipse when the project location is non-existent > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-16402 > URL: https://issues.jboss.org/browse/JBIDE-16402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Vineet Reynolds > Assignee: Koen Aers > Fix For: 4.2.0.Beta1 > > > When a non-existent location is specified in Eclipse, Forge creates the project, but fails to import the project into the Eclipse workspace. > This also seems to be related to an issue where the Location field is not pre-filled (not sure why; I'm reporting this bug on behalf of a user, so I'm hoping to get more details). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16695) Arquillian deployment method detection does not consider Archive subclasses

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16695?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16695: --------------------------------------- The issue has been fixed in the master branch. Could you upgrade to Arquillian 1.1 using the http://download.jboss.org/jbosstools/updates/nightly/core/master/ update site? That version is compatible with Eclipse Kepler/Luna and includes a lot of fixes/enhancements. It isn't necessary to upgrade other parts of Eclipse/JBoss Tools. {quote} I just discovered that this behavior also occurs if the @Deployment method is non-static. {quote} An Arquillian deployment method must be static. See https://docs.jboss.org/author/display/ARQ/Deployment+archives We could add a new problem marker (with a quick fix): "The method annotated with org.jboss.arquillian.container.test.api.Deployment is not static" or something similar that. > Arquillian deployment method detection does not consider Archive subclasses > --------------------------------------------------------------------------- > > Key: JBIDE-16695 > URL: https://issues.jboss.org/browse/JBIDE-16695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.Final > Reporter: Rich DiCroce > Assignee: Snjezana Peco > Fix For: 4.2.0.Beta1 > > > In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive: > {code} > @Deployment > public static WebArchive createDeployment() { > ...code to create deployment here... > } > {code} > As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method. -- 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, 3 months

1
0
0 / 0

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

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16630?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16630: --------------------------------------- The issue is related to the Seam Settings page. The page isn't refreshed when adding a new runtime. It can be reproduced in the following way: - open the JBoss Runtime Detection page(Preferences > JBoss Tools > JBoss Runtime Detection) - select the Seam preferences page (JBoss Tools > Web > Seam) - select the JBoss Runtime Detection page (JBoss Tools > JBoss Runtime Detection) - add a seam runtime - select the Seam preferences page(JBoss Tools > Web > Seam) (Don't close the Preferences dialog during the test case) The added Seam runtime isn't shown in the Seam preferences page. A workaround: close/open the Preferences dialog. > 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, 3 months

1
0
0 / 0

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

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16630?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16630: ---------------------------------- Component/s: seam2 (was: runtime-detection) > 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: seam2 > 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, 3 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 March 2014