September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15432) Run version comparisons to check components have been updated

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-15432: ------------------------------------------- Summary: Run version comparisons to check components have been updated Key: JBIDE-15432 URL: https://issues.jboss.org/browse/JBIDE-15432 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: qa Reporter: Max Rydahl Andersen Assignee: Jiri Peterka Priority: Blocker Fix For: 4.1.1.Alpha1 Can you run a version check to ensure all componnents have actually bumped their micro version before release? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14855) p2.mirrorsURL are kept in site metadata after mirroring with format attribute

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14855?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-14855: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > p2.mirrorsURL are kept in site metadata after mirroring with format attribute > ----------------------------------------------------------------------------- > > Key: JBIDE-14855 > URL: https://issues.jboss.org/browse/JBIDE-14855 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > When we mirror sites using the "format" argument (to keep the original repository layout with .pack.gz as siblings) it also keep the p2.mirrorsURL attribute. This is not bad per se, but since the mirrors are often not correctly sync'd with the Eclipse repositories/our mirrors, it leads to build failure. > Current workaround is to remove them by end in content.jar and artifact.jar. > We should think about removing this, for example as part of the remove-references script. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15012) Runtime download dialog cannot be stopped

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15012?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15012: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > Runtime download dialog cannot be stopped > ----------------------------------------- > > Key: JBIDE-15012 > URL: https://issues.jboss.org/browse/JBIDE-15012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.1.0.Beta2 > Environment: OS X Mountain Lion > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.1.1.Alpha1 > > > Go to Preferences -> JBoss Tools -> Runtime detection > and try to download a runtime using the Download button. > While the runtime is downloading, press Cancel/Stop to abort the download. Nothing will happen (at least in my case). -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15165) CordovaSim does not warn users that it needs Safari to run

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15165?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15165: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > CordovaSim does not warn users that it needs Safari to run > ---------------------------------------------------------- > > Key: JBIDE-15165 > URL: https://issues.jboss.org/browse/JBIDE-15165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.CR1 > Environment: Windows 8 > Reporter: Stefan Bunciak > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > Trying to run Hybrid Mobile Application in CordovaSim did nothing, then I tried to open standalone BrowserSim and it turned out that I'm missing Safari. I think the same applies to CordovaSim, so it should warn users of missing Safari installation. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13790) Prepare fast-filter script for integration-stack-tests split

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13790?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13790: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > Prepare fast-filter script for integration-stack-tests split > ------------------------------------------------------------ > > Key: JBIDE-13790 > URL: https://issues.jboss.org/browse/JBIDE-13790 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > As discussed in JBIDE-12974 and elsewhere, we need to split https://github.com/jbosstools/jbosstools-integration-tests in two: > - the current repo will contain tests for all features of JBT core > - the new repo - integration-stack-tests - will contain all soa/drools/teiid related tests > We need a fast-filter script to do the split while preserving history -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15378) Basic content assist for static AngularJS ng-* attributes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15378?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15378: ----------------------------------- Fix Version/s: 4.1.1.Alpha2 (was: 4.1.x) > Basic content assist for static AngularJS ng-* attributes > --------------------------------------------------------- > > Key: JBIDE-15378 > URL: https://issues.jboss.org/browse/JBIDE-15378 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15394) Add arquillian.xml GUI editor to jbosstools-arquillian

by Masao Kunii (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15394?page=com.atlassian.jira.plugi... ] Masao Kunii commented on JBIDE-15394: ------------------------------------- bq. why does the arquillian.xml editor need to modify pom.xml ? I think it would be more convinient to add dependencies automatically than just show them. But I am still thinking of which to do. What do you think better? may I have your advise? bq. what kind of changes is that for ? profile names or ? Profiles including container adapters dependencies and global dependencies including extensions and protocols dependencies which user selected in the editor. jbosstools-arquillian has already had a class(ArquillianUtility) for this, so I think I can use it. > Add arquillian.xml GUI editor to jbosstools-arquillian > ------------------------------------------------------ > > Key: JBIDE-15394 > URL: https://issues.jboss.org/browse/JBIDE-15394 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: testing-tools > Reporter: Masao Kunii > Priority: Optional > > The arquillian.xml editor is an editor to edit arquillian.xml easily and visually. This is a feature for jbosstools-arquillian(https://github.com/jbosstools/jbosstools-arquillian) and enables to: > - Edit containers, container groups, extensions, protocols and engines > - Modify pom.xml automatically corresponding settings in arquillian.xml > - Register favorite container/container groups from Eclipse preferences -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14526) Add 'quick fix' to 'warning missing deployment method'

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14526?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-14526. ----------------------------------------- Resolution: Done resolving this. please make sure other jiras contain info that allows QE/docs and users to understand the changes made when it involves changes to UI. > Add 'quick fix' to 'warning missing deployment method' > ------------------------------------------------------ > > Key: JBIDE-14526 > URL: https://issues.jboss.org/browse/JBIDE-14526 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > Given no deployment method > When 'warning missing deployment method' > Then add 'quick fix' open to 'generate 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2573) JBDS70_1411: [Uncommit] (Dev) (P1) Track more

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2573?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen closed JBDS-2573. ------------------------------------- Resolution: Deferred no major movement on this general issue for 7.x thus closing this down to track more specific ones. > JBDS70_1411: [Uncommit] (Dev) (P1) Track more > --------------------------------------------- > > Key: JBDS-2573 > URL: https://issues.jboss.org/browse/JBDS-2573 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Reporter: Jiri Pallich > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 7.1.0.Alpha1 > > Attachments: advanced-segments.png, as-users-segment.png > > > What JBoss and 3rd party plug-ins are end-users really using? Allowing us to invest more in the most popular. (Note: This was deferred JBDS60_0920.) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2572) JBDS70_1410: [Uncommit] (Dev) (P2) Make renaming of projects easier

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2572?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2572: -------------------------------------- CDW release: ? Status: New (was: New) Target Release: 7.1.0.GA Putting this for ack to drop. The requirement is old, haven't moved and no specific issues actually found nor reported. > JBDS70_1410: [Uncommit] (Dev) (P2) Make renaming of projects easier > ------------------------------------------------------------------- > > Key: JBDS-2572 > URL: https://issues.jboss.org/browse/JBDS-2572 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Reporter: Jiri Pallich > Assignee: Len DiMaggio > Fix For: 7.1.0.Alpha2 > > > Refactor/Rename a quickstart (project examples) and/or archetype generated project is difficult. Hibernate console error, maven pom.xml references, persistence.xml etc. > Check what issues there are and see which we can fix. -- 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, 7 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 September 2013