November 2014 - jbosstools-issues

[JBoss JIRA] (JBTIS-360) earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-360?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-360: ------------------------------------------- http://download.jboss.org/jbosstools/configuration/ide-config.properties seem to have the 8.0.0.GA settings commented out. That explains the devstudio issue. > earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls > --------------------------------------------------------------------------------- > > Key: JBTIS-360 > URL: https://issues.jboss.org/browse/JBTIS-360 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.0.Beta1 > > Attachments: ea-jbdsis.png, ea-jbtis.png > > > using IS earlyacces from jbosstools stable release I get: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > That should never get into stable. > Only the earlyaccess site should be added here. > For developer studio it gets even messier. > https://www.dropbox.com/s/3wlmw9hd6pey4mc > /Screenshot%202014-11-12%2013.13.34.png?dl=0 > https://devstudio.redhat.com/earlyaccess/8.0/ is correct, but then there are these two added sites that should not be present: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > This should be rolledback ASAP since users that install these will now get all the latest development updates instead of just the tested and verified to be in earlyaccess bits. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-360) earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-360?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-360: ------------------------------------------- Would be great to actually *test* these before putting them live. You can test it by using -D to override the preferences pointing to discovery and ide properties. > earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls > --------------------------------------------------------------------------------- > > Key: JBTIS-360 > URL: https://issues.jboss.org/browse/JBTIS-360 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.0.Beta1 > > Attachments: ea-jbdsis.png, ea-jbtis.png > > > using IS earlyacces from jbosstools stable release I get: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > That should never get into stable. > Only the earlyaccess site should be added here. > For developer studio it gets even messier. > https://www.dropbox.com/s/3wlmw9hd6pey4mc > /Screenshot%202014-11-12%2013.13.34.png?dl=0 > https://devstudio.redhat.com/earlyaccess/8.0/ is correct, but then there are these two added sites that should not be present: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > This should be rolledback ASAP since users that install these will now get all the latest development updates instead of just the tested and verified to be in earlyaccess bits. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-360) earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-360?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-360: ------------------------------------------- and with jbosstools its now doing: http://download.jboss.org/jbosstools/earlyaccess/development/luna/ AND http://download.jboss.org/jbosstools/earlyaccess/stable/luna/ so again, seems like stable is mixing streams with the development sites. > earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls > --------------------------------------------------------------------------------- > > Key: JBTIS-360 > URL: https://issues.jboss.org/browse/JBTIS-360 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.0.Beta1 > > Attachments: ea-jbdsis.png, ea-jbtis.png > > > using IS earlyacces from jbosstools stable release I get: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > That should never get into stable. > Only the earlyaccess site should be added here. > For developer studio it gets even messier. > https://www.dropbox.com/s/3wlmw9hd6pey4mc > /Screenshot%202014-11-12%2013.13.34.png?dl=0 > https://devstudio.redhat.com/earlyaccess/8.0/ is correct, but then there are these two added sites that should not be present: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > This should be rolledback ASAP since users that install these will now get all the latest development updates instead of just the tested and verified to be in earlyaccess bits. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18745) Separate Eclipse Marketplace entry for Hybrid Mobile

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18745?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18745: -------------------------------------- I did not understand the comma comment. Perhaps this is complicated and Nick should continue to do it as he obviously has the experience :) > Separate Eclipse Marketplace entry for Hybrid Mobile > ---------------------------------------------------- > > Key: JBIDE-18745 > URL: https://issues.jboss.org/browse/JBIDE-18745 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.0.Final > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Blocker > > Create a new marketplace entry for JBoss tools Hybrid Mobile which should include the following features. > - org.jboss.tools.aerogear.thym.feature > - org.jboss.tools.vpe.cordovasim.feature > - org.jboss.tools.jst.angularjs.feature > - org.jboss.tools.livereload.feature > And central > - org.jboss.tools.community.central.feature > - org.jboss.tools.community.project.examples.feature -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18724) HTML Validation: Ability to ignore custom htm tags (e.g. <ion-*>)

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18724?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-18724: ----------------------------------------- [~akazakov], please do not resolve the issue for a while (I should update a JUnit Test for quick fix) https://github.com/jbosstools/jbosstools-jst/pull/404 is to be applied on jbosstools-4.2.x only it's compatible with any versions of WTP 3.6.x, but is to be used with WTP v/3.6.3 and later (It states at the preference page that it cannot be used with WTP < 3.6.3. It can be successfully built on any WTP 3.6.x as well) JUnit Test for Quick Fix follows > HTML Validation: Ability to ignore custom htm tags (e.g. <ion-*>) > ----------------------------------------------------------------- > > Key: JBIDE-18724 > URL: https://issues.jboss.org/browse/JBIDE-18724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing, upstream > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Labels: new_and_noteworthy > Fix For: 4.2.1.Final > > > WTP HTML validator marks any custom html tags as unknown. It's possible to disable this validation at all: Window->Preferences->Web->HTML Files->Validation ==> Set Elements -> Unknown tag name severity to "Ignore": > !00001262.png! > But it would be useful to have ability to make HTML validator ignore some particular tags only. > I suggest to contribute a patch to WTP to fix it. > We have already did it for attributes, so lets do it for tags too: > - New preferences with a list of ignored tags (a mask can be used) > - A new preference page to set these preferences > - QuickFix for validation problem which will add the tag name/mask to this list/preferences > - Extension in our angular/ionic plugin which will disable validation for <ion-*> tags. > I've filed it to bugzilla - https://bugs.eclipse.org/bugs/show_bug.cgi?id=444545 but we have to provide a patch for it if we want to have it done ;) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18724) HTML Validation: Ability to ignore custom htm tags (e.g. <ion-*>)

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18724?page=com.atlassian.jira.plugi... ] Victor Rubezhny edited comment on JBIDE-18724 at 11/12/14 7:12 PM: ------------------------------------------------------------------- The fix for the Upstream issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=444545) is split into two separated Core and UI (https://bugs.eclipse.org/bugs/show_bug.cgi?id=448152 is created for the UI part) patches and the only its Core part will be included into WTP 3.6.2 release. As such we have to adapt it locally in JBT. There are number of cases are possible in order to adopt JBT to the upstream fix: 1. Since no UI part will be added to WTP to control the tag name ignorance preferences, we can force the default values (and/or even the actual values) for the Syntax Validator to ignore all the names that match ion-* pattern. No UI is requires with this fix, all the WTP installations are to use these preference values, but it will be impossible to change the preferences. So, the list of tag name patterns is to be carefully defined. 2. The second solution is to create an additional preference page for the WTP Syntax Validator preferences as well as QuickFix that allows to add tag names into ignorance list in JBT's Ionic plug-in. This will give a user the possibility to ignore any tag names on his own. I'd like not force the change of the default/actual values for these preferences because otherwise it will be a behaviour opposite to the WTP one and as such it might confuse the users. As Max sad on F2F: we need to go the case #2 was (Author: vrubezhny): The fix for the Upstream issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=444545) is split into two separated Core and UI (https://bugs.eclipse.org/bugs/show_bug.cgi?id=448152 is created for the UI part) patches and the only its Core part will be included into WTP 3.6.2 release. As such we have to adapt it locally in JBT. There are number of cases are possible in order to adopt JBT to the upstream fix: 1. Since no UI part will be added to WTP to control the tag name ignorance preferences, we can force the default values (and/or even the actual values) for the Syntax Validator to ignore all the names that match ion-* pattern. No UI is requires with this fix, all the WTP installations are to use these preference values, but it will be impossible to change the preferences. So, the list of tag name patterns is to be carefully defined. 2. The second solution is to create an additional preference page for the WTP Syntax Validator preferences as well as QuickFix that allows to add tag names into ignorance list in JBT's Ionic plug-in. This will give a user the possibility to ignore any tag names on his own. I'd like not force the change of the default/actual values for these preferences because otherwise it will be a behaviour opposite to the WTP one and as such it might confuse the users. WDYT? My +1 is for the case 1. > HTML Validation: Ability to ignore custom htm tags (e.g. <ion-*>) > ----------------------------------------------------------------- > > Key: JBIDE-18724 > URL: https://issues.jboss.org/browse/JBIDE-18724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing, upstream > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Labels: new_and_noteworthy > Fix For: 4.2.1.Final > > > WTP HTML validator marks any custom html tags as unknown. It's possible to disable this validation at all: Window->Preferences->Web->HTML Files->Validation ==> Set Elements -> Unknown tag name severity to "Ignore": > !00001262.png! > But it would be useful to have ability to make HTML validator ignore some particular tags only. > I suggest to contribute a patch to WTP to fix it. > We have already did it for attributes, so lets do it for tags too: > - New preferences with a list of ignored tags (a mask can be used) > - A new preference page to set these preferences > - QuickFix for validation problem which will add the tag name/mask to this list/preferences > - Extension in our angular/ionic plugin which will disable validation for <ion-*> tags. > I've filed it to bugzilla - https://bugs.eclipse.org/bugs/show_bug.cgi?id=444545 but we have to provide a patch for it if we want to have it done ;) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-361) JBDS IS 8 Beta1 features not showing up in EA view

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-361?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-361 at 11/12/14 6:13 PM: ------------------------------------------------------------ PRs applied, and verified working for JBT 4.2 / JBDS 8, so resolving. If QE wants to verify, the steps are: a) install JBDS 8 or JBT 4.2 from marketplace b) open Central, enable early access, install IS features, restart c) Help > About > Installation details button > JBoss Central tab was (Author: nickboldt): PRs applied, and verified working for JBT 4.2 / JBDS 8, so resolving. If QE wants to verify, the steps are above. > JBDS IS 8 Beta1 features not showing up in EA view > -------------------------------------------------- > > Key: JBTIS-361 > URL: https://issues.jboss.org/browse/JBTIS-361 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 8.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.Beta1 > > Attachments: JBDS800-marketplace+JBDSIS800Beta1_EA-empty.png, JBDS800-marketplace+JBDSIS800Beta1_EA-found.png, JBT420-marketplace+JBTIS420Beta1_EA-empty.png, JBT420-marketplace+JBTIS420Beta1_EA-found.png > > > 0. Install JBDS 8 from Marketplace. Restart. > 1. Open Central > Software Update tab > [x] Enable Early Access > Yes > 2. Install the JBDS IS connectors, including: > * JBoss Business Process and Rules Development > * JBoss Data Virtualization Development > * JBoss Integration and SOA Development > * JBoss SOA 5.x Development > 3. Restart. Open Central and uncheck the [ ] Enable Early Access box - note the 4 connectors listed as being EA are: > * JBoss Business Process and Rules Development > * JBoss Data Virtualization Development > * JBoss Integration and SOA Development > * JBoss SOA 5.x Development > Hit OK. > 4. Open Help > About and verify the Fuse, Teiid, Modeshape and SwitchYard icons are shown, among others. > 5. Click Installation Details > Installed Software and verify Fuse, BPMN2, BPEL, Drools, Guvnor, etc. are all installed. > 6. Select the JBoss Central tab. Note that the list of EA features installed is empty. > !JBDS800-marketplace+JBDSIS800Beta1_EA-empty.png! -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-361) JBDS IS 8 Beta1 features not showing up in EA view

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-361?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-361: ----------------------------- Attachment: JBT420-marketplace+JBTIS420Beta1_EA-found.png > JBDS IS 8 Beta1 features not showing up in EA view > -------------------------------------------------- > > Key: JBTIS-361 > URL: https://issues.jboss.org/browse/JBTIS-361 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 8.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 8.0.0.Beta1 > > Attachments: JBDS800-marketplace+JBDSIS800Beta1_EA-empty.png, JBDS800-marketplace+JBDSIS800Beta1_EA-found.png, JBT420-marketplace+JBTIS420Beta1_EA-empty.png, JBT420-marketplace+JBTIS420Beta1_EA-found.png > > > 0. Install JBDS 8 from Marketplace. Restart. > 1. Open Central > Software Update tab > [x] Enable Early Access > Yes > 2. Install the JBDS IS connectors, including: > * JBoss Business Process and Rules Development > * JBoss Data Virtualization Development > * JBoss Integration and SOA Development > * JBoss SOA 5.x Development > 3. Restart. Open Central and uncheck the [ ] Enable Early Access box - note the 4 connectors listed as being EA are: > * JBoss Business Process and Rules Development > * JBoss Data Virtualization Development > * JBoss Integration and SOA Development > * JBoss SOA 5.x Development > Hit OK. > 4. Open Help > About and verify the Fuse, Teiid, Modeshape and SwitchYard icons are shown, among others. > 5. Click Installation Details > Installed Software and verify Fuse, BPMN2, BPEL, Drools, Guvnor, etc. are all installed. > 6. Select the JBoss Central tab. Note that the list of EA features installed is empty. > !JBDS800-marketplace+JBDSIS800Beta1_EA-empty.png! -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-361) JBDS IS 8 Beta1 features not showing up in EA view

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-361?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-361: ----------------------------- Attachment: (was: JBT420-marketplace+JBTIS420Beta1_EA-found.png) > JBDS IS 8 Beta1 features not showing up in EA view > -------------------------------------------------- > > Key: JBTIS-361 > URL: https://issues.jboss.org/browse/JBTIS-361 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 8.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 8.0.0.Beta1 > > Attachments: JBDS800-marketplace+JBDSIS800Beta1_EA-empty.png, JBDS800-marketplace+JBDSIS800Beta1_EA-found.png, JBT420-marketplace+JBTIS420Beta1_EA-empty.png, JBT420-marketplace+JBTIS420Beta1_EA-found.png > > > 0. Install JBDS 8 from Marketplace. Restart. > 1. Open Central > Software Update tab > [x] Enable Early Access > Yes > 2. Install the JBDS IS connectors, including: > * JBoss Business Process and Rules Development > * JBoss Data Virtualization Development > * JBoss Integration and SOA Development > * JBoss SOA 5.x Development > 3. Restart. Open Central and uncheck the [ ] Enable Early Access box - note the 4 connectors listed as being EA are: > * JBoss Business Process and Rules Development > * JBoss Data Virtualization Development > * JBoss Integration and SOA Development > * JBoss SOA 5.x Development > Hit OK. > 4. Open Help > About and verify the Fuse, Teiid, Modeshape and SwitchYard icons are shown, among others. > 5. Click Installation Details > Installed Software and verify Fuse, BPMN2, BPEL, Drools, Guvnor, etc. are all installed. > 6. Select the JBoss Central tab. Note that the list of EA features installed is empty. > !JBDS800-marketplace+JBDSIS800Beta1_EA-empty.png! -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-361) JBDS IS 8 Beta1 features not showing up in EA view

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-361?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-361: ----------------------------- Attachment: JBT420-marketplace+JBTIS420Beta1_EA-found.png JBT420-marketplace+JBTIS420Beta1_EA-empty.png Similar solution for JBT IS 4.2.0.Beta1: Before: !JBT420-marketplace+JBTIS420Beta1_EA-empty.png! PR: https://github.com/jbosstools/jbosstools-download.jboss.org/pull/457 After: !JBT420-marketplace+JBTIS420Beta1_EA-found.png! > JBDS IS 8 Beta1 features not showing up in EA view > -------------------------------------------------- > > Key: JBTIS-361 > URL: https://issues.jboss.org/browse/JBTIS-361 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 8.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 8.0.0.Beta1 > > Attachments: JBDS800-marketplace+JBDSIS800Beta1_EA-empty.png, JBDS800-marketplace+JBDSIS800Beta1_EA-found.png, JBT420-marketplace+JBTIS420Beta1_EA-empty.png, JBT420-marketplace+JBTIS420Beta1_EA-found.png > > > 0. Install JBDS 8 from Marketplace. Restart. > 1. Open Central > Software Update tab > [x] Enable Early Access > Yes > 2. Install the JBDS IS connectors, including: > * JBoss Business Process and Rules Development > * JBoss Data Virtualization Development > * JBoss Integration and SOA Development > * JBoss SOA 5.x Development > 3. Restart. Open Central and uncheck the [ ] Enable Early Access box - note the 4 connectors listed as being EA are: > * JBoss Business Process and Rules Development > * JBoss Data Virtualization Development > * JBoss Integration and SOA Development > * JBoss SOA 5.x Development > Hit OK. > 4. Open Help > About and verify the Fuse, Teiid, Modeshape and SwitchYard icons are shown, among others. > 5. Click Installation Details > Installed Software and verify Fuse, BPMN2, BPEL, Drools, Guvnor, etc. are all installed. > 6. Select the JBoss Central tab. Note that the list of EA features installed is empty. > !JBDS800-marketplace+JBDSIS800Beta1_EA-empty.png! -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 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 November 2014