March 2013 - jbosstools-issues - Jboss List Archives

[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

13 years, 1 month

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

13 years, 1 month

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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13698) Build As submenu

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13698?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-13698: ------------------------------------- Note: in Java EE, the right option is normally "mvn package", not "mvn install" - where the goal is to produce a .war or .ear but not put everything in my local repo. > Build As submenu > ---------------- > > Key: JBIDE-13698 > URL: https://issues.jboss.org/browse/JBIDE-13698 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Burr Sutter > Attachments: Screen Shot 2013-03-01 at 8.03.01 AM.png > > > This is a usability issue - new users to Eclipse struggle with finding the "mvn package" or "mvn install" options hidden in the JBDS menu. Having those under Run As is simply not intuitive. Not too mention that there is a Maven menu, that does not have the build options - which would have been slightly more intuitive. > One proposal is a Build As menu - where I can issue my various mvn commands. > Screenshot of current JBDS 7 context menu (right-click) on a project attached. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13698) Build As submenu

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-13698: ----------------------------------- Summary: Build As submenu Key: JBIDE-13698 URL: https://issues.jboss.org/browse/JBIDE-13698 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Burr Sutter Attachments: Screen Shot 2013-03-01 at 8.03.01 AM.png This is a usability issue - new users to Eclipse struggle with finding the "mvn package" or "mvn install" options hidden in the JBDS menu. Having those under Run As is simply not intuitive. Not too mention that there is a Maven menu, that does not have the build options - which would have been slightly more intuitive. One proposal is a Build As menu - where I can issue my various mvn commands. Screenshot of current JBDS 7 context menu (right-click) on a project attached. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13698) Build As submenu

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13698?page=com.atlassian.jira.plugi... ] Burr Sutter updated JBIDE-13698: -------------------------------- Attachment: Screen Shot 2013-03-01 at 8.03.01 AM.png > Build As submenu > ---------------- > > Key: JBIDE-13698 > URL: https://issues.jboss.org/browse/JBIDE-13698 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Burr Sutter > Attachments: Screen Shot 2013-03-01 at 8.03.01 AM.png > > > This is a usability issue - new users to Eclipse struggle with finding the "mvn package" or "mvn install" options hidden in the JBDS menu. Having those under Run As is simply not intuitive. Not too mention that there is a Maven menu, that does not have the build options - which would have been slightly more intuitive. > One proposal is a Build As menu - where I can issue my various mvn commands. > Screenshot of current JBDS 7 context menu (right-click) on a project attached. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13697) Can't install Spring from Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13697?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-13697: -------------------------------------- Assignee: Mickael Istria (was: Nick Boldt) > Can't install Spring from Central > --------------------------------- > > Key: JBIDE-13697 > URL: https://issues.jboss.org/browse/JBIDE-13697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > Installation tests are failing on Central because of Spring: > {code} > Contains: Cannot complete the install because one or more required items could not be found. > Contains: Software being installed: Spring IDE Web Flow Extension (optional) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.webflow.feature.feature.group 3.2.0.201301251408-M2) > Contains: Missing requirement: Spring IDE Spring Configuration Editor (Core) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.config.core 3.2.0.201301251408-M2) requires 'bundle org.springsource.ide.eclipse.commons.core 0.0.0' but it could not be found > Contains: Cannot satisfy dependency: > Contains: From: Spring IDE Core (required) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.feature.feature.group 3.2.0.201301251408-M2) > Contains: To: org.springframework.ide.eclipse.config.core [3.2.0.201301251408-M2] > Contains: Cannot satisfy dependency: > Contains: From: Spring IDE Web Flow Extension (optional) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.webflow.feature.feature.group 3.2.0.201301251408-M2) > Contains: To: org.springframework.ide.eclipse.feature.feature.group 0.0.0 > {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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13697) Can't install Spring from Central

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-13697: -------------------------------------- Summary: Can't install Spring from Central Key: JBIDE-13697 URL: https://issues.jboss.org/browse/JBIDE-13697 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.1.0.Alpha1 Reporter: Mickael Istria Assignee: Nick Boldt Priority: Blocker Fix For: 4.1.0.Alpha1 Installation tests are failing on Central because of Spring: {code} Contains: Cannot complete the install because one or more required items could not be found. Contains: Software being installed: Spring IDE Web Flow Extension (optional) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.webflow.feature.feature.group 3.2.0.201301251408-M2) Contains: Missing requirement: Spring IDE Spring Configuration Editor (Core) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.config.core 3.2.0.201301251408-M2) requires 'bundle org.springsource.ide.eclipse.commons.core 0.0.0' but it could not be found Contains: Cannot satisfy dependency: Contains: From: Spring IDE Core (required) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.feature.feature.group 3.2.0.201301251408-M2) Contains: To: org.springframework.ide.eclipse.config.core [3.2.0.201301251408-M2] Contains: Cannot satisfy dependency: Contains: From: Spring IDE Web Flow Extension (optional) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.webflow.feature.feature.group 3.2.0.201301251408-M2) Contains: To: org.springframework.ide.eclipse.feature.feature.group 0.0.0 {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

13 years, 1 month

1
0
0 / 0

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

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13696?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13696: ---------------------------------------- It seems to me that test plugins should be part of coverage report, because it's important to see that the tests are correctly run (ie code coverage in tests is high). There is some value with analyzing tests code and giving coverage on them, since tests must be considered as first-class code. -1 for this request. > 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 > 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13671: ---------------------------------------- In order to change the version, you need to make a commit. So it will use the timestamp of the commit that changed the version. So it won't ignore the version. Using this git timestamp will allow us to use some new workflows, which won't require us to bump version and rebuild old stuff when nothing actually changes. In my opinion, the problem is not really what we use as qualifier, it's more that we bump version of things that don't change because we want all components to use the latest version of parent pom. We should avoid that, by replacing some parent pom configuration with build job configuration. > parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- 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

13 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 March 2013