May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-4455) Add JUnit tests for org.hibernate.eclipse.mapper.editors.reveng

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4455?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-4455: --------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > Add JUnit tests for org.hibernate.eclipse.mapper.editors.reveng > --------------------------------------------------------------- > > Key: JBIDE-4455 > URL: https://issues.jboss.org/browse/JBIDE-4455 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Affects Versions: 3.1.0.M2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.x > > > 1. Test editor is opened on reveng XML file. > 2. Test editor is able to process all kinds of elements in xml file. > tests should try to achieve at least 100% classes coverage for org.hibernate.eclipse.mapper.editors.reveng package. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14080) Browsersim > ScreenShot > Save is not clear where it saves images

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14080?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14080: ---------------------------------------- Issue Type: Enhancement (was: Feature Request) > Browsersim > ScreenShot > Save is not clear where it saves images > ----------------------------------------------------------------- > > Key: JBIDE-14080 > URL: https://issues.jboss.org/browse/JBIDE-14080 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.1.0.Beta1 > > > As a first time user of browserim clicking Screenshot > Save looks like it does nothing. > As it turns out it is actually saving funky timestamped .png's into my home folder. > I think that is a bad default behavior. > Here is my suggestion: > A) prefix the file with browsersim- (making it easier to find) > B) use a ISO date format instead of the current mix of _'s and -'s. i.e. 2013-04-17-103221.png or just 20130417103221.png > C) if user have not set preferences (i.e. blank field) ask the user on his first Save > to specify which folder to save to. > D) on Screenshot > Save show dialog stating the full path of the save file in a way that makes it possible to copy/paste the path (maybe even copy/paste it to the clipboard). > Option D could be made more smooth/better by having something like: > Title: Screenshot saved > Text: Screenshot saved to [filename]. > [ ] Copy path to clipboard > [ ] Do this always and do not show this again > [Ok] [Cancel] > And as usual have a "reset dialog settings" in preferences to reset this. > Then on first users they are informed about where the file is saved and can get to it instantly - and experienced users can just dismiss this dialog and have the action they want every time. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4474) Clean up unused dependencies from plug-ins

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4474?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-4474: --------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > Clean up unused dependencies from plug-ins > ------------------------------------------ > > Key: JBIDE-4474 > URL: https://issues.jboss.org/browse/JBIDE-4474 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cleanup > Affects Versions: 3.1.0.M2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.x > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3515) Actions that modifies resources (Add JSF/Custom Capabilities) should let user review the changes as Java Code refactoring and clean-up do

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3515?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-3515: --------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > Actions that modifies resources (Add JSF/Custom Capabilities) should let user review the changes as Java Code refactoring and clean-up do > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-3515 > URL: https://issues.jboss.org/browse/JBIDE-3515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JSF > Affects Versions: 3.0.0.cr1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.x > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14297) add missing metadata to stacks.yml

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14297?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-14297: ------------------------------------- I would like to note that EAP 6.0 and eap 6.1 are already added to the stacks.yaml. EAP 4.3 and 5.0 will not be added because, as of now, they are not publicly downloadable as far as I know. This is not a regression, since currently we do not provide any way to download those runtimes anyway. > add missing metadata to stacks.yml > ---------------------------------- > > Key: JBIDE-14297 > URL: https://issues.jboss.org/browse/JBIDE-14297 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples, runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.1.0.Beta1 > > > Current missing: > * license > * filesize > * matching wtp server id > * ... ? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13686) Compatible runtime constraints should be declared in Stack.yaml

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13686?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13686. --------------------------------- Resolution: Duplicate Issue To trim jira list, I'm marking this as a duplicate of JBIDE-14297 > Compatible runtime constraints should be declared in Stack.yaml > --------------------------------------------------------------- > > Key: JBIDE-13686 > URL: https://issues.jboss.org/browse/JBIDE-13686 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, project-examples > Affects Versions: 4.1.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > Runtime constraints are currently read from project descriptor xmls. > This causes JBIDE-13656. > That info should be read from the stacks instead. The wtp server id should be added as a label for each runtime in stacks.yaml. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14297) add missing metadata to stacks.yml

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14297?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-14297: ----------------------------------- Assignee: Rob Stryker > add missing metadata to stacks.yml > ---------------------------------- > > Key: JBIDE-14297 > URL: https://issues.jboss.org/browse/JBIDE-14297 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples, runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.1.0.Beta1 > > > Current missing: > * license > * filesize > * matching wtp server id > * ... ? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14319) CordovaSim: Aerogear default project isn't emulated by CordovaSim

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14319?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14319: --------------------------------------------- My thinking would be that if our proxy gets a request for a cordova.js (no matter the file location) and this file does not exist in ripple or the app we will serve out the latest cordova.js we got. We can provide an option for specified version in launch config but preferably we should be able to detect this automatically and not have to hardcode it. > CordovaSim: Aerogear default project isn't emulated by CordovaSim > ----------------------------------------------------------------- > > Key: JBIDE-14319 > URL: https://issues.jboss.org/browse/JBIDE-14319 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, browsersim > Reporter: Ilya Buziuk > Assignee: Gorkem Ercan > Fix For: 4.1.0.Beta1 > > > The root of the issue is pretty obvious - there is no cordova.js file in the aerogear project, which is vital for CordovaSim. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-5435) JSF Resource identifier validator

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-5435?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-5435: --------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > JSF Resource identifier validator > --------------------------------- > > Key: JBIDE-5435 > URL: https://issues.jboss.org/browse/JBIDE-5435 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JSF > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: jsf2, new_and_noteworthy > Fix For: 4.2.x > > > Validator should check: > 1. resource references in pages: xhtml, jsp, jspxand etc. > 2. resource names defined in current project or related projects > 3. resource names defined in jars > It should perform verification for JSF2 resources as it is defined in spec's "2.6.1.3 Resource Identifiers" chapter: "<resourceIdentifier> consists of several segments, specified as follows. > [localePrefix/][libraryName/][libraryVersion/]resourceName[/resourceVersion] > The run-time must enforce the following rules to consider a <resourceIdentifier>s valid. A <resourceIdentifier> that does not follow these rules must not be considered valid and must be ignored silently. > * Every character in a resource identifier must be a valid character suitable for use in a string passed to the constructor of java.io.File that takes a single String argument. > * Segments in square brackets [] are optional. > * The segments must appear in the order shown above. > * If libraryVersion is present, it must be preceded by libraryName. > * If libraryVersion is present, any leaf files under libraryName must be ignored. > * If resourceVersion is present, it must be preceded by resourceName. > * There must be a '/' between adjacent segments in a <resourceIdentifier> > * If libraryVersion or resourceVersion are present, both must be a '_' separated list of integers, neither starting nor ending with '_' > * If resourceVersion is present, it must be a version number in the same format as libraryVersion. An optional "file extension" may be used with the resourceVersion. If "file extension" is used, a "." character, followed by a "file extension" must be appended to the version number. See the following table for an example." -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14319) CordovaSim: Aerogear default project isn't emulated by CordovaSim

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14319?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14319: ---------------------------------------- Priority: Critical (was: Major) > CordovaSim: Aerogear default project isn't emulated by CordovaSim > ----------------------------------------------------------------- > > Key: JBIDE-14319 > URL: https://issues.jboss.org/browse/JBIDE-14319 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, browsersim > Reporter: Ilya Buziuk > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.1.0.Beta1 > > > The root of the issue is pretty obvious - there is no cordova.js file in the aerogear project, which is vital for CordovaSim. -- 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, 11 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 May 2013