November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15928) Tweak publish.sh to allow copying of javadoc along with the p2 repo

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15928?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15928: ---------------------------------------- Fix Version/s: 4.1.x 4.1.2 (was: 4.1.1.Final) > Tweak publish.sh to allow copying of javadoc along with the p2 repo > ------------------------------------------------------------------- > > Key: JBIDE-15928 > URL: https://issues.jboss.org/browse/JBIDE-15928 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.1.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.1.x, 4.1.2 > > > We would like to be able to publish javadoc regularly along with the p2 repo. > E.g. we have this: > http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/all/repo/ > Generated by: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Using publish.sh: > http://raw.github.com/jbosstools/jbosstools-build-ci/master/publish/publi... > We would like to get something like this: > http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/all/ja... > To generate javadoc of RedDeer, you need to run: > mvn install > mvn javadoc:javadoc > See this PR that adds javadoc support for RedDeer: > https://github.com/jboss-reddeer/reddeer/pull/46 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15928) Tweak publish.sh to allow copying of javadoc along with the p2 repo

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15928?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15928: --------------------------------------------- not blocking final > Tweak publish.sh to allow copying of javadoc along with the p2 repo > ------------------------------------------------------------------- > > Key: JBIDE-15928 > URL: https://issues.jboss.org/browse/JBIDE-15928 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.1.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.1.x, 4.1.2 > > > We would like to be able to publish javadoc regularly along with the p2 repo. > E.g. we have this: > http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/all/repo/ > Generated by: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Using publish.sh: > http://raw.github.com/jbosstools/jbosstools-build-ci/master/publish/publi... > We would like to get something like this: > http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/all/ja... > To generate javadoc of RedDeer, you need to run: > mvn install > mvn javadoc:javadoc > See this PR that adds javadoc support for RedDeer: > https://github.com/jboss-reddeer/reddeer/pull/46 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15271) update default Central discovery URLs in JBT to point to Final / GA URLs instead of last dev milestone

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15271?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15271: ------------------------------- Fix Version/s: 4.1.0.Final (was: 4.1.1.Final) > update default Central discovery URLs in JBT to point to Final / GA URLs instead of last dev milestone > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15271 > URL: https://issues.jboss.org/browse/JBIDE-15271 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.1.0.Final > > > PRs for fixing the pom in the 4.1.x branch and adding more reminders so we don't forget to update in BOTH places next time: > https://github.com/jbosstools/jbosstools-central/pull/142 (41x) > https://github.com/jbosstools/jbosstools-central/pull/144 (master) > These do not block Final/GA release. > — > Effect of this bug is that users of JBT 4.1.0.Final will (at some point, if we release a dev milestone of 4.1.1.x) see 4.1.1.x discovery content rather waiting until 4.1.1.Final is released to see an update to their Discovery content. > But, since we duplicate the content in http://download.jboss.org/jbosstools/updates/stable/kepler/jbosstools-dir... to http://download.jboss.org/jbosstools/updates/development/kepler/jbosstool... this should not affect anyone adversely, and we can fix this for 4.1.1 (if there's to be a 4.1.1). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15271) update default Central discovery URLs in JBT to point to Final / GA URLs instead of last dev milestone

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15271?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-15271. ------------------------------ Resolution: Done Fixed in July. > update default Central discovery URLs in JBT to point to Final / GA URLs instead of last dev milestone > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15271 > URL: https://issues.jboss.org/browse/JBIDE-15271 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.1.0.Final > > > PRs for fixing the pom in the 4.1.x branch and adding more reminders so we don't forget to update in BOTH places next time: > https://github.com/jbosstools/jbosstools-central/pull/142 (41x) > https://github.com/jbosstools/jbosstools-central/pull/144 (master) > These do not block Final/GA release. > — > Effect of this bug is that users of JBT 4.1.0.Final will (at some point, if we release a dev milestone of 4.1.1.x) see 4.1.1.x discovery content rather waiting until 4.1.1.Final is released to see an update to their Discovery content. > But, since we duplicate the content in http://download.jboss.org/jbosstools/updates/stable/kepler/jbosstools-dir... to http://download.jboss.org/jbosstools/updates/development/kepler/jbosstool... this should not affect anyone adversely, and we can fix this for 4.1.1 (if there's to be a 4.1.1). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Nick Boldt updated JBIDE-2720: ------------------------------ Fix Version/s: 4.2.x (was: 4.1.x) > Need 64-bit windows support > --------------------------- > > Key: JBIDE-2720 > URL: https://issues.jboss.org/browse/JBIDE-2720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha > Reporter: Samuel Mendenhall > Assignee: Yahor Radtsevich > Fix For: 4.2.x > > Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png > > > If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for Windows 64-bit. > *Update:* > In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr... > {color:red}*Known problems:*{color} > * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK > *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:* > * Try to uninstall Intel OpenCL SDK > * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio) > If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16063) Aborting a command has strange behavior

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-16063: ---------------------------------- Summary: Aborting a command has strange behavior Key: JBIDE-16063 URL: https://issues.jboss.org/browse/JBIDE-16063 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: Pavol Srna Fix For: 4.1.1.Final Attachments: forge-screen-1.png, forge-screen-2.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16063) Aborting a command has strange behavior

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16063?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-16063: ------------------------------- Attachment: forge-screen-1.png forge-screen-2.png > Aborting a command has strange behavior > ---------------------------------------- > > Key: JBIDE-16063 > URL: https://issues.jboss.org/browse/JBIDE-16063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Fix For: 4.1.1.Final > > Attachments: forge-screen-1.png, forge-screen-2.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2727: ----------------------------------- [~sgilda], [~bleathem], [~vineet.reynolds] : guys, what's the status on your cheatsheets? > Cheatsheets for JBoss Central archetypes > ---------------------------------------- > > Key: JBDS-2727 > URL: https://issues.jboss.org/browse/JBDS-2727 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 7.1.0.GA > > Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md > > > Our archetypes should have cheatsheets when imported/opened into eclipse. > Priority > 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim > 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java > Basically walk the user through the flow of events (from the UI to the backend) in the application > 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14636) CordovaSim: Incorrect way of message processing since cordova-2.7.0.js

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14636?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-14636. ------------------------------- Verified with JBDS7.1.0.CR1 CR1-v20131116-1929-B543 > CordovaSim: Incorrect way of message processing since cordova-2.7.0.js > ----------------------------------------------------------------------- > > Key: JBIDE-14636 > URL: https://issues.jboss.org/browse/JBIDE-14636 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, upstream > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.1.1.CR1 > > Attachments: prompt.png > > > This is pretty annoying bug which appeares in CordovaSim from nowhere and was really difficult to reproduce. However, after some research the root of the problem was found - incorrect way of message processing in cordova-2.7.0.js. So I've created an issue for cordova team - https://issues.apache.org/jira/browse/CB-3503 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16006) "JBoss Tomcat" is not allowed according to apache trademark rules

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16006?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-16006. --------------------------------- Resolution: Done Proper label was applied on master, 4.1.x and 4.1.1.x > "JBoss Tomcat" is not allowed according to apache trademark rules > ----------------------------------------------------------------- > > Key: JBIDE-16006 > URL: https://issues.jboss.org/browse/JBIDE-16006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Labels: respin-a > > "JBoss Tomcat" is used in the Tomcat integration. That is borderline bad according to apache trademark policies. > Should find a different name like "JBoss Tools Apache Tomcat Integration" or something similar. -- 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, 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 2013