May 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17167) rse.ui source bundle not available in locally-built TP

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17167?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17167: ------------------------------------- Denis: Were you building with the include-sources flag? -Dmirror-target-to-repo.includeSources=true > rse.ui source bundle not available in locally-built TP > ------------------------------------------------------ > > Key: JBIDE-17167 > URL: https://issues.jboss.org/browse/JBIDE-17167 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Fix For: 4.2.0.Beta2 > > > Cannot find a source bundle for rse.ui using locally-built TP and the flags for include source. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17126) Add support for 1.8 java facet to JBoss runtimes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17126?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17126. --------------------------------- Resolution: Done pushed to master > Add support for 1.8 java facet to JBoss runtimes > ------------------------------------------------ > > Key: JBIDE-17126 > URL: https://issues.jboss.org/browse/JBIDE-17126 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta2 > > > Currently you cannot use java 1.8 facet for WildFly 8 runtime. > I'm not actually sure if WildFly 8.0 will support java 8 or it's only in 8.1. > Also, we're still not certain if we need a new server/runtime type for 8.1 - perhaps if 8.0 does not support java 8 and 8.1 does, that's one reason to have them separate? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17167) rse.ui source bundle not available in locally-built TP

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17167?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-17167: --------------------------------------- {quote}Have you tried to use the TP in IDE from the preferences and see whether the IDE can find the source?{quote} When I use unified jbosstools target file in Eclipse preferences I have no sources at all. > rse.ui source bundle not available in locally-built TP > ------------------------------------------------------ > > Key: JBIDE-17167 > URL: https://issues.jboss.org/browse/JBIDE-17167 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Fix For: 4.2.0.Beta2 > > > Cannot find a source bundle for rse.ui using locally-built TP and the flags for include source. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9479) Enhance custom classpath containers for additional support such as as7's modules tag

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9479?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-9479: ------------------------------------ Much work has been done to document all the strangeness in this small plugin, so that should help in the future as well. > Enhance custom classpath containers for additional support such as as7's modules tag > ------------------------------------------------------------------------------------ > > Key: JBIDE-9479 > URL: https://issues.jboss.org/browse/JBIDE-9479 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 3.3.0.M3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta2 > > > Enhance /JBIDE-1354 to allow for additional types of filesets. > 1) Maintain backwards compatibility in terms of reading legacy files stores and functioning properly > 2) If user makes a change, save in new persistance format > 3) Add core elements for a 'module id' based classpath provider, only for jboss servers that have jboss-modules as a base > 4) Expand UI to allow creation of a classpath element by using a module id instead of a basedir/includes/excludes pattern > Out of scope for this issue: Core/UI for a per-facet customized response. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9479) Enhance custom classpath containers for additional support such as as7's modules tag

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9479?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-9479: ------------------------------- Description: Enhance /JBIDE-1354 to allow for additional types of filesets. 1) Maintain backwards compatibility in terms of reading legacy files stores and functioning properly 2) If user makes a change, save in new persistance format 3) Add core elements for a 'module id' based classpath provider, only for jboss servers that have jboss-modules as a base 4) Expand UI to allow creation of a classpath element by using a module id instead of a basedir/includes/excludes pattern Out of scope for this issue: Core/UI for a per-facet customized response. was: Enhance /JBIDE-1354 to allow for additional types of filesets. 1) Add API 2) Add extension point 3) Add UI > Enhance custom classpath containers for additional support such as as7's modules tag > ------------------------------------------------------------------------------------ > > Key: JBIDE-9479 > URL: https://issues.jboss.org/browse/JBIDE-9479 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 3.3.0.M3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta2 > > > Enhance /JBIDE-1354 to allow for additional types of filesets. > 1) Maintain backwards compatibility in terms of reading legacy files stores and functioning properly > 2) If user makes a change, save in new persistance format > 3) Add core elements for a 'module id' based classpath provider, only for jboss servers that have jboss-modules as a base > 4) Expand UI to allow creation of a classpath element by using a module id instead of a basedir/includes/excludes pattern > Out of scope for this issue: Core/UI for a per-facet customized response. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9479) Enhance custom classpath containers for additional support such as as7's modules tag

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9479?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-9479: ------------------------------------ PR is complete for now, until I begin work on a new UI that allows per-facet customizations. > Enhance custom classpath containers for additional support such as as7's modules tag > ------------------------------------------------------------------------------------ > > Key: JBIDE-9479 > URL: https://issues.jboss.org/browse/JBIDE-9479 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 3.3.0.M3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta2 > > > Enhance /JBIDE-1354 to allow for additional types of filesets. > 1) Maintain backwards compatibility in terms of reading legacy files stores and functioning properly > 2) If user makes a change, save in new persistance format > 3) Add core elements for a 'module id' based classpath provider, only for jboss servers that have jboss-modules as a base > 4) Expand UI to allow creation of a classpath element by using a module id instead of a basedir/includes/excludes pattern > Out of scope for this issue: Core/UI for a per-facet customized response. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-1042) Problem with Render in RedHat Jsp Editor when use bean:write and logic struts tags

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-1042?page=com.atlassian.jira.plugin... ] Konstantin Marmalyukov closed JBIDE-1042. ----------------------------------------- Fix Version/s: 4.2.0.Beta2 (was: LATER) Resolution: Out of Date > Problem with Render in RedHat Jsp Editor when use bean:write and logic struts tags > ---------------------------------------------------------------------------------- > > Key: JBIDE-1042 > URL: https://issues.jboss.org/browse/JBIDE-1042 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-templates > Affects Versions: 2.0.0.Beta3 > Environment: Window XP Professional, Eclipse 3.3 Europa > Reporter: Hermes Waldemarin > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.Beta2 > > Attachments: screenshot-1.jpg, webFiles.zip > > > Now i have a problem with render of bean write and logicc tags of strus tag libraries. > When a put de bean:write tag in my page, the line broke to next line. > Thanks... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-776) VPE don't recognize some Struts tags

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-776?page=com.atlassian.jira.plugin.... ] Konstantin Marmalyukov closed JBIDE-776. ---------------------------------------- Fix Version/s: 4.2.0.Beta2 (was: LATER) Resolution: Out of Date > VPE don't recognize some Struts tags > ------------------------------------ > > Key: JBIDE-776 > URL: https://issues.jboss.org/browse/JBIDE-776 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-templates > Affects Versions: 2.0.0.Beta3 > Environment: WindowsXP SP2 > rhds-win32-1.0.0.ALPHA.jar > Red Hat Developer Studio > Version: 1.0.0 > Build id: 1.0.0 > Reporter: Aliaksey Nis > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.Beta2 > > Attachments: StrutsOpenOnsTestProjectZ.zip, Strutstags.JPG > > > The tag should display sting from corresponding message bundle. > Example: we have in struts-config.xml following declaration: > <message-resources key="resource" parameter="resource"/> > in file resource.properties: > badlogin=Your password or login is incorrect! > JSP: > <bean:message bundle="resource" key="badlogin"/> > Tag should dispay "Your password or login is incorrect!", but it is shown as unknown tag. > Look at attached screenshot with examples of unrecognized tags. > Test project attached -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2923) Verify whether JBDS really needs PDE

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2923?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2923: -------------------------------------- [~maxandersen] I asked for investigation around the removal of PDE, so just for the posterity, I can provide some arguments about why I opened this ticket: * I wasn't aware that OSGi development is something we do actually want to support in JBDS. (it's actually because there are some -around 0.1% maybe ;) - people doing Web Development with OSGi that Eclipse JEE is shipped with PDE too) * I just thought PDE might be there just because it has been implemented like that or to re-use some basic of its APIs that might be avoidable. * The cost of PDE is that the application is more complex, has more menus and more features than what our average users (JEE/Mobile/Web developers) may need. So for those who don't use PDE features, adding PDE actually reduce the quality of the application. But I'm fine with keeping it, since it is something we seem to actually want. > Verify whether JBDS really needs PDE > ------------------------------------ > > Key: JBDS-2923 > URL: https://issues.jboss.org/browse/JBDS-2923 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build > Reporter: Mickael Istria > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 8.0.0.Beta2 > > > It looks like by default, JBDS embeds PDE and its UI contributions, which are totally off-topic. > We should consider removing PDE. For this we need to check what depends on it first. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ] Nick Boldt edited comment on TOOLSDOC-492 at 5/2/14 4:08 AM: ------------------------------------------------------------- Looks like some formatting is correct and others ... not so much. Example: https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... (look for "+ __ Important") vs. https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... (again, an embedded "Important" callout, but formatted more cleanly More problems: * image captions gone * procedures lose numbered steps --> becomes paragraphs (should be ordered list) * backticks = <command> * should we wrap bold around guibutton, guilabel, or make them all command tags? * can't render to pdf using pandoc or asciidoc :( * random "+" concat symbols to merge paras w/ images, which github renders as a plus sign instead of paragraph joiners * need more hard rules to separate sections (just top levels, with =) was (Author: nickboldt): Looks like some formatting is correct and others ... not so much. Example: https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... (look for "+ __ Important") vs. https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... (again, an embedded "Important" callout, but formatted more cleanly More problems: * image captions gone * procedures lose numbered steps --> becomes paragraphs (should be ordered list) * backticks = <command> * should we wrap bold around guibutton, guilabel, or make them all command tags? * can't render to pdf using pandoc or asciidoc :( * random "+" concat symbols to merge paras w/ images, which github renders as "+" instead of paragraph joiners * need more hard rules to separate sections (just top levels, with =) > Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process) > ------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-492 > URL: https://issues.jboss.org/browse/TOOLSDOC-492 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 4.2.0.Beta2 > > > With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc! > What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these: > http://tools.jboss.org/features/ (with icons that link to projects' latest doc) > or > http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked) > And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release. > Questions: > a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype) > b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1). > c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported? > d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming. > [0] https://github.com/oreillymedia/docbook2asciidoc > e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone? > [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio... > f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]? > [2] http://tools.jboss.org/downloads/overview.html > [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 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 2014