February 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-2937) Verify subclipse/1.10_1.8 with JBDS 8.0

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2937?page=com.atlassian.jira.plugin.... ] Vlado Pakan commented on JBDS-2937: ----------------------------------- Works fine with Subclipse installed from http://subclipse.tigris.org/update_1.10.x and JBDS 8.0.0.Alpha2-v20140212-2251-B70 > Verify subclipse/1.10_1.8 with JBDS 8.0 > --------------------------------------- > > Key: JBDS-2937 > URL: https://issues.jboss.org/browse/JBDS-2937 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Vlado Pakan > Fix For: 8.0.0.Beta1 > > -- 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-15888) Update the Spring Archetype reference

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15888?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15888: ------------------------------------- Radim, you're right, the fix for JBIDE-14629 didn't fix the case when jboss:deployment-structure:1.2 is used :-/ I reopened JBIDE-14534 > Update the Spring Archetype reference > ------------------------------------- > > Key: JBIDE-15888 > URL: https://issues.jboss.org/browse/JBIDE-15888 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Joshua Wilson > Assignee: Fred Bricon > Labels: spring > Fix For: 4.1.2.CR1 > > Attachments: springmvc-test.xml > > > I updated the Spring Archetype. The one in JBDS/JBIDE needs to point to the new version. -- 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-2931) Verify testng/6.8.6.20130914_0724 with JBDS 8.0

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2931?page=com.atlassian.jira.plugin.... ] Vlado Pakan updated JBDS-2931: ------------------------------ Fix Version/s: 8.0.0.Alpha2 (was: 8.0.0.Beta1) > Verify testng/6.8.6.20130914_0724 with JBDS 8.0 > ----------------------------------------------- > > Key: JBDS-2931 > URL: https://issues.jboss.org/browse/JBDS-2931 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Vlado Pakan > Fix For: 8.0.0.Alpha2 > > > See: https://issues.jboss.org/browse/JBDS-2800 -- 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-2931) Verify testng/6.8.6.20130914_0724 with JBDS 8.0

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2931?page=com.atlassian.jira.plugin.... ] Vlado Pakan resolved JBDS-2931. ------------------------------- Resolution: Done > Verify testng/6.8.6.20130914_0724 with JBDS 8.0 > ----------------------------------------------- > > Key: JBDS-2931 > URL: https://issues.jboss.org/browse/JBDS-2931 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Vlado Pakan > Fix For: 8.0.0.Alpha2 > > > See: https://issues.jboss.org/browse/JBDS-2800 -- 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-2931) Verify testng/6.8.6.20130914_0724 with JBDS 8.0

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2931?page=com.atlassian.jira.plugin.... ] Vlado Pakan commented on JBDS-2931: ----------------------------------- Works fine with JBDS 8.0.Alpha2-v20140212-2251-B70 and TestNG installed from http://download.jboss.org/jbosstools/updates/requirements/testng/6.8.6.20... > Verify testng/6.8.6.20130914_0724 with JBDS 8.0 > ----------------------------------------------- > > Key: JBDS-2931 > URL: https://issues.jboss.org/browse/JBDS-2931 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Vlado Pakan > Fix For: 8.0.0.Beta1 > > > See: https://issues.jboss.org/browse/JBDS-2800 -- 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-2945) Unable to import Maven project from Git perspective

by Jozef Hartinger (JIRA)

Jozef Hartinger created JBDS-2945: ------------------------------------- Summary: Unable to import Maven project from Git perspective Key: JBDS-2945 URL: https://issues.jboss.org/browse/JBDS-2945 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: maven Affects Versions: 7.1.0.GA Reporter: Jozef Hartinger I am roughly following these steps https://community.jboss.org/wiki/AdvancedJavaEELabjaro2014 to import a project from a Git repository. I firstly use the Git perspective to clone a remote repository. Then, still in the Git perspective when I right-click on the "Working directory" there is an option to "Import projects". However, this option only allows for eclipse or general projects to be imported. A Maven project is not recognized. I am aware of other ways of importing the Maven project. However, I think that Maven should be supported consistently across all the "import-project-like" dialogs, not only some of them. -- 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-2938) Verify findbugs/2.0.3.20131122 with JBDS 8.0

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2938?page=com.atlassian.jira.plugin.... ] Martin Malina resolved JBDS-2938. --------------------------------- Resolution: Done > Verify findbugs/2.0.3.20131122 with JBDS 8.0 > --------------------------------------------- > > Key: JBDS-2938 > URL: https://issues.jboss.org/browse/JBDS-2938 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 8.0.0.Beta1 > > -- 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-2934) Verify springide/3.4.0.201310051539-RELEASE with JBDS 8.0

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2934?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2934: ------------------------------- Fix Version/s: 8.0.0.Beta1 (was: 8.0.0.Alpha2) > Verify springide/3.4.0.201310051539-RELEASE with JBDS 8.0 > --------------------------------------------------------- > > Key: JBDS-2934 > URL: https://issues.jboss.org/browse/JBDS-2934 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Marián Labuda > Fix For: 8.0.0.Beta1 > > > See: https://issues.jboss.org/browse/JBDS-2808 -- 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-16658) Extract browsersim from VPE git repository

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16658?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-16658: ------------------------------------------------ I totally agree with idea to extract browsersim and cordovasim into its own repo. Ideally we should have all branches/tags history, but having only active branches(master) history will also be ok. About VPV: at first we need to decide in what way we will use it. Will it be a new editor or we will replace visual part of current editor or will it be a simple view. Will discuss it with [~dgolovin]. > Extract browsersim from VPE git repository > ------------------------------------------ > > Key: JBIDE-16658 > URL: https://issues.jboss.org/browse/JBIDE-16658 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.Beta1 > > > BrowserSim and CordovaSim is standalone and does not and should have no dependencies on VPE, > Suggestion is to extract browsersim and cordovasim to a separate repository. > Should we put upcoming VPV into this repository too ? (JBIDE-16414) > This would allow VPV to be used by VPE and other components without full VPE dependency set. > Need to define what plugins/bundles should be moved and what git history/branches needs to be moved. -- 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-15888) Update the Spring Archetype reference

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15888?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15888: ------------------------------------- Hey [~burrsutter], [~jowilson] do you still want to update JBoss Central with jboss-spring-mvc-archetype:1.0.3.Final for JBDS 7.1.1 or do we wait till an archetype version with embedded RH Maven repo comes out? > Update the Spring Archetype reference > ------------------------------------- > > Key: JBIDE-15888 > URL: https://issues.jboss.org/browse/JBIDE-15888 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Joshua Wilson > Assignee: Fred Bricon > Labels: spring > Fix For: 4.1.2.CR1 > > Attachments: springmvc-test.xml > > > I updated the Spring Archetype. The one in JBDS/JBIDE needs to point to the new version. -- 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