March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13599 at 3/13/13 1:34 PM: ------------------------------------------------------------- Does not appear to be working. Steps to repro: 1. Build JBDS 7 locally from trunk. {code} cd ~/devstudio/trunk/product mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate {code} 2. Apply this patch: [^JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt] 3. Build discovery plugins locally from trunk (with patch). {code} cd ~/devstudio/trunk/product/discovery mvn clean install -DUPDATE_SITE=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ -DEXTRAS_SITE=http://download.jboss.org/jbosstools/updates/kepler/extras/ {code} 4. launch local webserver (in a separate console window - do not close until done testing): {code} cd /tmp wget -nc https://raw.github.com/elonen/nanohttpd/master/NanoHTTPD.java /opt/sun-java2-7.0/bin/javac NanoHTTPD.java java NanoHTTPD -d ~/devstudio/trunk/product/ -p 8080 {code} 5. Install JBDS you just built. 6. Edit its jbdevstudio.ini file, setting these -D flags: {code} -Djboss.discovery.directory.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/devstudio-directory.xml -Djboss.discovery.site.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/ {code} 7. Launch JBDS: {code} ./jbdevstudio -consolelog -debug {code} 8. Open the Software/Updates tab in Central. For all the entries with siteUrl="${jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core/} you will see no connectors listed. Only Android and JRebel will be shown. was (Author: nickboldt): Does not appear to be working. Steps to repro: 1. build JBDS 7 locally from trunk. {code} cd ~/devstudio/trunk/product mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate {code} 2. apply this patch: [^JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt] 3. build discovery plugins locally from trunk (with patch). {code} cd ~/devstudio/trunk/product/discovery mvn clean install -DUPDATE_SITE=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ -DEXTRAS_SITE=http://download.jboss.org/jbosstools/updates/kepler/extras/ {code} 4. launch local webserver (in a separate console window - do not close until done testing): {code} cd /tmp wget -nc https://raw.github.com/elonen/nanohttpd/master/NanoHTTPD.java /opt/sun-java2-7.0/bin/javac NanoHTTPD.java java NanoHTTPD -d ~/devstudio/trunk/product/ -p 8080 {code} 5. > externalize Central site URL into a commandline property so that testing or mirroring is easier > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-13599 > URL: https://issues.jboss.org/browse/JBIDE-13599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > Attachments: JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt > > > As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE. > A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. > This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE. -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13599: ------------------------------- Attachment: JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt Does not appear to be working. Steps to repro: 1. build JBDS 7 locally from trunk. {code} cd ~/devstudio/trunk/product mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate {code} 2. apply this patch: [^JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt] 3. build discovery plugins locally from trunk (with patch). {code} cd ~/devstudio/trunk/product/discovery mvn clean install -DUPDATE_SITE=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ -DEXTRAS_SITE=http://download.jboss.org/jbosstools/updates/kepler/extras/ {code} 4. launch local webserver (in a separate console window - do not close until done testing): {code} cd /tmp wget -nc https://raw.github.com/elonen/nanohttpd/master/NanoHTTPD.java /opt/sun-java2-7.0/bin/javac NanoHTTPD.java java NanoHTTPD -d ~/devstudio/trunk/product/ -p 8080 {code} 5. > externalize Central site URL into a commandline property so that testing or mirroring is easier > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-13599 > URL: https://issues.jboss.org/browse/JBIDE-13599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > Attachments: JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt > > > As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE. > A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. > This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE. -- 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
0
0 / 0

[JBoss JIRA] (JBDS-2496) Installer should include EAP 6.1 instead of 6.0.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2496?page=com.atlassian.jira.plugin.... ] Nick Boldt reopened JBDS-2496: ------------------------------ Not fixed. Installer fails to install EAP 6.1 to disk. (Might be related to pack200 problem, JBDS-2497 as I just tested a locally-build version of JBDS, built w/ Tycho 0.17.0-SNAPSHOT) > Installer should include EAP 6.1 instead of 6.0.1 > ------------------------------------------------- > > Key: JBDS-2496 > URL: https://issues.jboss.org/browse/JBDS-2496 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.0.0.Alpha2 > > > Bundle EAP 6.1 in the installer. > EAP 6.1 Alpha is now available from here: http://www.jboss.org/jbossas/downloads -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-13787) Palette marks editor "changed" when there is nothing to insert

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-13787: ------------------------------------- Summary: Palette marks editor "changed" when there is nothing to insert Key: JBIDE-13787 URL: https://issues.jboss.org/browse/JBIDE-13787 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.1.0.Alpha1 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 4.1.0.Alpha2 Test case: EXECUTE: 1. Create Java Project "test" 2. Create folder "test" in test project 3. Create file "test.html" in test folder {code} <!DOCTYPE html> {code} 4. Open file test.html in Visual Page Editor ASSERT: Visual Page Editor appears with test.html and jQuery Mobile Widget Palette on the right side 5. Press mouse on "JS/CSS" palette element ASSERT: test.html is changed: {code} <!DOCTYPE html> <html> <head> <meta name="viewport" content="width=device-width, initial-scale=1"> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" /> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script> <script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script> </head> <body> </body> </html> {code} 6. Save the file and Press mouse on "JS/CSS" palette element again FAIL: test.html is not changed but editor marked as "changed" - "*test.html" in the editor title -- 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
0
0 / 0

[JBoss JIRA] (JBIDE-13758) Update Forge Embedded Runtime to 1.2.2.Final

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13758?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13758. ------------------------------- Resolution: Done > Update Forge Embedded Runtime to 1.2.2.Final > -------------------------------------------- > > Key: JBIDE-13758 > URL: https://issues.jboss.org/browse/JBIDE-13758 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > The embedded forge should be updated to make sure that the html5 scaffolding works well with it. > The ticket monster tutorial was checked to work fine with Forge 1.2.1. > As for the ticket monster demo part, it needs a little fix in the admin_layer.fsh file. But running this file seems to fail also with Forge 1.1.2. > The problem can be viewed here: http://pastebin.com/tgxGgrN0 -- 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
0
0 / 0

[JBoss JIRA] (JBDS-2497) Building JBDS product w/ -Ppack200 results in NPE and build failure

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2497?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2497: -------------------------------------- pack200 profile was removed from CI job and will be re-enabled once we migrate to Tycho 0.17. > Building JBDS product w/ -Ppack200 results in NPE and build failure > ------------------------------------------------------------------- > > Key: JBDS-2497 > URL: https://issues.jboss.org/browse/JBDS-2497 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Mickael Istria > Attachments: log.txt, log2.zip > > > Building JBDS product w/ -Ppack200 results in NPE and build failure: > {code} > cd ~/trunk/product > mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate,pack200 -X | tee log.txt > {code} > whereas: > {code} > cd ~/trunk/product > mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate > {code} > works 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2497) Building JBDS product w/ -Ppack200 results in NPE and build failure

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2497?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2497: --------------------------------- Fix Version/s: 7.0.x > Building JBDS product w/ -Ppack200 results in NPE and build failure > ------------------------------------------------------------------- > > Key: JBDS-2497 > URL: https://issues.jboss.org/browse/JBDS-2497 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 7.0.x > > Attachments: log.txt, log2.zip > > > Building JBDS product w/ -Ppack200 results in NPE and build failure: > {code} > cd ~/trunk/product > mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate,pack200 -X | tee log.txt > {code} > whereas: > {code} > cd ~/trunk/product > mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate > {code} > works 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2497) Building JBDS product w/ -Ppack200 results in NPE and build failure

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2497?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2497: --------------------------------- Component/s: Build > Building JBDS product w/ -Ppack200 results in NPE and build failure > ------------------------------------------------------------------- > > Key: JBDS-2497 > URL: https://issues.jboss.org/browse/JBDS-2497 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 7.0.x > > Attachments: log.txt, log2.zip > > > Building JBDS product w/ -Ppack200 results in NPE and build failure: > {code} > cd ~/trunk/product > mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate,pack200 -X | tee log.txt > {code} > whereas: > {code} > cd ~/trunk/product > mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate > {code} > works 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2497) Building JBDS product w/ -Ppack200 results in NPE and build failure

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2497?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2497: -------------------------------------- So this is pending on release of Tycho 0.17, good news. > Building JBDS product w/ -Ppack200 results in NPE and build failure > ------------------------------------------------------------------- > > Key: JBDS-2497 > URL: https://issues.jboss.org/browse/JBDS-2497 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Mickael Istria > Attachments: log.txt, log2.zip > > > Building JBDS product w/ -Ppack200 results in NPE and build failure: > {code} > cd ~/trunk/product > mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate,pack200 -X | tee log.txt > {code} > whereas: > {code} > cd ~/trunk/product > mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate > {code} > works 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2497) Building JBDS product w/ -Ppack200 results in NPE and build failure

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2497?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2497: ----------------------------- Assignee: Mickael Istria > Building JBDS product w/ -Ppack200 results in NPE and build failure > ------------------------------------------------------------------- > > Key: JBDS-2497 > URL: https://issues.jboss.org/browse/JBDS-2497 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Mickael Istria > Attachments: log.txt, log2.zip > > > Building JBDS product w/ -Ppack200 results in NPE and build failure: > {code} > cd ~/trunk/product > mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate,pack200 -X | tee log.txt > {code} > whereas: > {code} > cd ~/trunk/product > mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate > {code} > works 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

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