April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16966) Warning isn't shown if bom file is in local repository

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16966?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-16966: ------------------------------------------ Yeah, for maven its normal, but previous JBDS (I just tried JBDS6) shows warning even if I have bom in my local repo. > Warning isn't shown if bom file is in local repository > ------------------------------------------------------ > > Key: JBIDE-16966 > URL: https://issues.jboss.org/browse/JBIDE-16966 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.2.0.Beta2 > > > When I try to import some central example (HTML5, JavaEE) no warning is displayed if jboss-javaee-6.0-bom is in my local repository. This is causing issues when I had enterprise repo in my settings.xml in the past but right now its not there (but bom was downloaded into my local repo). > > I think that in past we didn't check local repository right ? Why was this behaviour changed ? Is it because of offline mode ? In that case maybe we should check if maven is in offline mode, if not than we should check remote repositories, not local. > Steps to reproduce: > 1. open HTML5 wizard from central > 2. add enterprise repo via warning > ASSERT: warning disappears > 3. close wizard > 4. remove enterprise repo from settings.xml > 5. open HTML5 wizard from central > FAIL: no warning is diplayed even that enterprise repo is missing (only local repo contains javaee-6.0-bom) -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-16966) Warning isn't shown if bom file is in local repository

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16966?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16966: -------------------------------- Priority: Minor (was: Major) > Warning isn't shown if bom file is in local repository > ------------------------------------------------------ > > Key: JBIDE-16966 > URL: https://issues.jboss.org/browse/JBIDE-16966 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.2.0.Beta2 > > > When I try to import some central example (HTML5, JavaEE) no warning is displayed if jboss-javaee-6.0-bom is in my local repository. This is causing issues when I had enterprise repo in my settings.xml in the past but right now its not there (but bom was downloaded into my local repo). > > I think that in past we didn't check local repository right ? Why was this behaviour changed ? Is it because of offline mode ? In that case maybe we should check if maven is in offline mode, if not than we should check remote repositories, not local. > Steps to reproduce: > 1. open HTML5 wizard from central > 2. add enterprise repo via warning > ASSERT: warning disappears > 3. close wizard > 4. remove enterprise repo from settings.xml > 5. open HTML5 wizard from central > FAIL: no warning is diplayed even that enterprise repo is missing (only local repo contains javaee-6.0-bom) -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-16966) Warning isn't shown if bom file is in local repository

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16966?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16966: ------------------------------------- this is expected, kinda. Once m2e/Maven has resolved a dependency, it won't try again for the next 24hrs. It's been the default behavior for years now. We can probably try override that behavior though. > Warning isn't shown if bom file is in local repository > ------------------------------------------------------ > > Key: JBIDE-16966 > URL: https://issues.jboss.org/browse/JBIDE-16966 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.2.0.Beta2 > > > When I try to import some central example (HTML5, JavaEE) no warning is displayed if jboss-javaee-6.0-bom is in my local repository. This is causing issues when I had enterprise repo in my settings.xml in the past but right now its not there (but bom was downloaded into my local repo). > > I think that in past we didn't check local repository right ? Why was this behaviour changed ? Is it because of offline mode ? In that case maybe we should check if maven is in offline mode, if not than we should check remote repositories, not local. > Steps to reproduce: > 1. open HTML5 wizard from central > 2. add enterprise repo via warning > ASSERT: warning disappears > 3. close wizard > 4. remove enterprise repo from settings.xml > 5. open HTML5 wizard from central > FAIL: no warning is diplayed even that enterprise repo is missing (only local repo contains javaee-6.0-bom) -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-16966) Warning isn't shown if bom file is in local repository

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16966?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-16966: ----------------------------------- Assignee: Fred Bricon > Warning isn't shown if bom file is in local repository > ------------------------------------------------------ > > Key: JBIDE-16966 > URL: https://issues.jboss.org/browse/JBIDE-16966 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.2.0.Beta2 > > > When I try to import some central example (HTML5, JavaEE) no warning is displayed if jboss-javaee-6.0-bom is in my local repository. This is causing issues when I had enterprise repo in my settings.xml in the past but right now its not there (but bom was downloaded into my local repo). > > I think that in past we didn't check local repository right ? Why was this behaviour changed ? Is it because of offline mode ? In that case maybe we should check if maven is in offline mode, if not than we should check remote repositories, not local. > Steps to reproduce: > 1. open HTML5 wizard from central > 2. add enterprise repo via warning > ASSERT: warning disappears > 3. close wizard > 4. remove enterprise repo from settings.xml > 5. open HTML5 wizard from central > FAIL: no warning is diplayed even that enterprise repo is missing (only local repo contains javaee-6.0-bom) -- 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
0
0 / 0

[JBoss JIRA] (JBDS-2979) Installer: NoSuchFieldException in console

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-2979?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-2979. ---------------------------- Verified in JBDS 8.0.0.Beta1a build. > Installer: NoSuchFieldException in console > ------------------------------------------ > > Key: JBDS-2979 > URL: https://issues.jboss.org/browse/JBDS-2979 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Environment: OS X 10.9 Mavericks > JBDS 8.0.0.Beta1 B78 > Oracle JDK 1.7, 1.8 > Reporter: Martin Malina > Assignee: Denis Golovin > Labels: respin-a > Fix For: 8.0.0.Beta1 > > > When I start the JBDS installer using "java -jar installer.jar", I get this exception in the console right away: > java.lang.NoSuchFieldException: awtAppClassName > {code} > java.lang.NoSuchFieldException: awtAppClassName > at java.lang.Class.getDeclaredField(Class.java:1948) > at com.izforge.izpack.installer.InstallerFrame.buildGUI(InstallerFrame.java:446) > at com.izforge.izpack.installer.InstallerFrame.<init>(InstallerFrame.java:215) > at com.izforge.izpack.installer.GUIInstaller.loadGUI(Unknown Source) > at com.izforge.izpack.installer.GUIInstaller.access$100(Unknown Source) > at com.izforge.izpack.installer.GUIInstaller$2.run(Unknown Source) > at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251) > at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733) > at java.awt.EventQueue.access$200(EventQueue.java:103) > at java.awt.EventQueue$3.run(EventQueue.java:694) > at java.awt.EventQueue$3.run(EventQueue.java:692) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) > at java.awt.EventQueue.dispatchEvent(EventQueue.java:703) > at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242) > at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161) > at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138) > at java.awt.EventDispatchThread.run(EventDispatchThread.java:91) > {code} > It happens both with java 7 and 8 and it's new - it doesn't happen with JBDS 7.1.1 or JBDS 8.0.0.Alpha2. > This issue doesn't seem it has any impact though - I can install JBDS just fine. -- 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
0
0 / 0

[JBoss JIRA] (JBDS-2975) versionwatch broken since com.jboss.* refactoring

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-2975?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-2975. ---------------------------- > versionwatch broken since com.jboss.* refactoring > ------------------------------------------------- > > Key: JBDS-2975 > URL: https://issues.jboss.org/browse/JBDS-2975 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, p2-product > Affects Versions: 8.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 8.0.0.Beta1 > > > Version watch job [1] is broken in master, possibly due to refactoring of com.jboss.jbds -> com.jboss.devstudio (JBDS-2669). > See https://gist.github.com/nickboldt/6041754/revisions for how to fix. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-16966) Warning isn't shown if bom file is in local repository

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16966?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-16966: ------------------------------------- Description: When I try to import some central example (HTML5, JavaEE) no warning is displayed if jboss-javaee-6.0-bom is in my local repository. This is causing issues when I had enterprise repo in my settings.xml in the past but right now its not there (but bom was downloaded into my local repo). I think that in past we didn't check local repository right ? Why was this behaviour changed ? Is it because of offline mode ? In that case maybe we should check if maven is in offline mode, if not than we should check remote repositories, not local. Steps to reproduce: 1. open HTML5 wizard from central 2. add enterprise repo via warning ASSERT: warning disappears 3. close wizard 4. remove enterprise repo from settings.xml 5. open HTML5 wizard from central FAIL: no warning is diplayed even that enterprise repo is missing (only local repo contains javaee-6.0-bom) was: When I try to import some central example (HTML5, JavaEE) no warning is displayed if jboss-javaee-6.0-bom is in my local repository. This is causing issues when I had enterprise repo in my settings.xml in the past but right now its not there (but bom was downloaded into my local repo). I think that in past we didn't check local repository right ? Why was this behaviour changed ? Steps to reproduce: 1. open HTML5 wizard from central 2. add enterprise repo via warning ASSERT: warning disappears 3. close wizard 4. remove enterprise repo from settings.xml 5. open HTML5 wizard from central FAIL: no warning is diplayed even that enterprise repo is missing (only local repo contains javaee-6.0-bom) > Warning isn't shown if bom file is in local repository > ------------------------------------------------------ > > Key: JBIDE-16966 > URL: https://issues.jboss.org/browse/JBIDE-16966 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Beta1 > Reporter: Rastislav Wagner > Fix For: 4.2.0.Beta2 > > > When I try to import some central example (HTML5, JavaEE) no warning is displayed if jboss-javaee-6.0-bom is in my local repository. This is causing issues when I had enterprise repo in my settings.xml in the past but right now its not there (but bom was downloaded into my local repo). > > I think that in past we didn't check local repository right ? Why was this behaviour changed ? Is it because of offline mode ? In that case maybe we should check if maven is in offline mode, if not than we should check remote repositories, not local. > Steps to reproduce: > 1. open HTML5 wizard from central > 2. add enterprise repo via warning > ASSERT: warning disappears > 3. close wizard > 4. remove enterprise repo from settings.xml > 5. open HTML5 wizard from central > FAIL: no warning is diplayed even that enterprise repo is missing (only local repo contains javaee-6.0-bom) -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-16966) Warning isn't shown if bom file is in local repository

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-16966: ---------------------------------------- Summary: Warning isn't shown if bom file is in local repository Key: JBIDE-16966 URL: https://issues.jboss.org/browse/JBIDE-16966 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: central Affects Versions: 4.2.0.Beta1 Reporter: Rastislav Wagner Fix For: 4.2.0.Beta2 When I try to import some central example (HTML5, JavaEE) no warning is displayed if jboss-javaee-6.0-bom is in my local repository. This is causing issues when I had enterprise repo in my settings.xml in the past but right now its not there (but bom was downloaded into my local repo). I think that in past we didn't check local repository right ? Why was this behaviour changed ? Steps to reproduce: 1. open HTML5 wizard from central 2. add enterprise repo via warning ASSERT: warning disappears 3. close wizard 4. remove enterprise repo from settings.xml 5. open HTML5 wizard from central FAIL: no warning is diplayed even that enterprise repo is missing (only local repo contains javaee-6.0-bom) -- 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
0
0 / 0

[JBoss JIRA] (JBDS-2747) Remove unjustified wording in installer welcome screen

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-2747?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-2747. ---------------------------- Verified in JBDS 8.0.0.Beta1 build. > Remove unjustified wording in installer welcome screen > ------------------------------------------------------ > > Key: JBDS-2747 > URL: https://issues.jboss.org/browse/JBDS-2747 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Emmanuel Bernard > Assignee: Nick Boldt > Fix For: 8.0.0.Beta1 > > > Step 1 of 9 says > {quote}It is strongly recommended that you quit all programs before continuing this installation.{quote} > Neither Max nor I see it as a justified recommendation. We are not in the 90s anymore :) > Plus the audience is developers, not your grand uncle. -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-16918) Using Forge TAB auto-completion inserts garbled text after the command

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16918?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-16918: ----------------------------------- Indeed, when starting from a terminal the issue appears, on Linux as well as on OSX. I'll investigate but defer to 4.2.0.Beta2 as there is a workaround (ie. not start from a terminal). > Using Forge TAB auto-completion inserts garbled text after the command > ---------------------------------------------------------------------- > > Key: JBIDE-16918 > URL: https://issues.jboss.org/browse/JBIDE-16918 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Beta1 > > Attachments: characters.png > > -- 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
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 April 2014