March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-162) Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them?

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-162?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-162. ------------------------------ Resolution: Won't Fix I understand the principle - I guess we'll stay with referencing the upstream TP requirements - forming a JBTIS/ JBDSIS base/early access TP repo matrix. > Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them? > -------------------------------------------------------------------------------------------------------- > > Key: JBTIS-162 > URL: https://issues.jboss.org/browse/JBTIS-162 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.3 > Reporter: Nick Boldt > Assignee: Paul Leacu > > JBT has two types of .target files: > * multiple [1], which references multiple upstream URLs from which its IUs are sourced, and > * unified [2], which references a single update site, which is the published site generated from materializing the multiple target, then replacing all the URLs w/ that new single, unified URL. > [1] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > [2] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > Should JBTIS have a similar notion? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-372) Disable Fuse Tooling proxy wizards (temporary)

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-372?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-372. ------------------------------ Fix Version/s: 8.0.1.CR1 4.2.1.CR1 Resolution: Done https://github.com/jbosstools/jbosstools-integration-stack/commit/dbccd13... Re-enabled the Fuse Integration Project proxy wizard and set the earlyaccess category ID. <extension point="org.jboss.tools.central.proxyWizard"> <proxyWizard id="fuse.integration.wizard" category="earlyaccess" description="%fuse.integration.wizard.description" label="Fuse Integration Project" priority="3" iconPath="images/fuse_integration_wizard.png" wizardId="org.fusesource.ide.branding.wizards.FuseProjectWizard" requiredComponentIds="jboss.integration-stack.bundle.fuse"> </proxyWizard> </extension> Updated both jbosstools and devstudio. > Disable Fuse Tooling proxy wizards (temporary) > ---------------------------------------------- > > Key: JBTIS-372 > URL: https://issues.jboss.org/browse/JBTIS-372 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 4.2.0.Alpha2 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.1.CR1, 4.2.1.CR1 > > > Need to temporarily disable Fuse Tooling JBoss Central proxy wizards until this Jira is resolved: > https://issues.jboss.org/browse/JBDS-3289 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18813) Convert JBoss Central to an HTML5 page

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18813?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18813: --------------------------------------------- +1 on extra metadata/tags. This fits the idea of being able to mark which are to be promoted and be able to categorize them. I'm not that keen on having it in the readme.md if that means they are "stuck" and we can not move/change them easily after their release; but if updates are fairly easy to do then it seem like a pragmatic approach. > Convert JBoss Central to an HTML5 page > -------------------------------------- > > Key: JBIDE-18813 > URL: https://issues.jboss.org/browse/JBIDE-18813 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.3.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > Attachments: Central Design Concept A.bmml, Central Design Concept A.bmml, Central Design Concept A.bmml, Central Design Concept A.png, Central Design Concept B.bmml, Central Design Concept B.bmml, Central Design Concept B.png, Central design concept E.bmml, Central design concept E.png, Design concept C - Search centric layout.bmml, Design concept C - Search centric layout.png, Design Concept D - categories across top.bmml, Design Concept D - categories across top.bmml, Design Concept D - categories across top.png, JBoss Access Panel Concept.bmml, JBoss Access Panel Concept.png, JBoss Central User Stories and Flows.gliffy, JBossCentral_DesignC_HighFidelity_InitialState.png, JBossCentral_DesignC_HighFidelity_SearchState.png, JBossCentral_DesignC_HighFidelity_SmallScreen_InitialState.png, JBossCentral_DesignC_HighFidelity_SmallScreen_SearchState.png, JBossCentral_DesignC_HighFidelity_SmallScreen_StarterHover.png, JBossCentral_DesignC_HighFidelity_StarterHover.png, Screen Shot 2015-01-16 at 4.38.58 PM.png > > > Central Page requires new capabilities : > - needs more customization (display content depending on user preferences) > - needs to scale with JBDS-IS, Fuse content > - access to more examples, with filtering capabilities > Given that the existing page is pretty hard to maintain and suffers from scalability/UI bugs, we're heading towards an HTML5 approach : > - use an embedded SWT Browser widget (or Java FX), depending on the platform compatibility > - webpage and its content could be served remotely (as zip), and downloaded locally for offline use. this would give us more flexibility to update the content. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19403) Remove JSF validation that is covered by Eclipse wst.jsf validation

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19403?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19403: ----------------------------------- Summary: Remove JSF validation that is covered by Eclipse wst.jsf validation (was: Remove JSF validation that is covered by wst.jsf validation) > Remove JSF validation that is covered by Eclipse wst.jsf validation > ------------------------------------------------------------------- > > Key: JBIDE-19403 > URL: https://issues.jboss.org/browse/JBIDE-19403 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsf > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19403) Remove JSF validation that is covered by wst.jsf validation

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-19403: --------------------------------------------- Summary: Remove JSF validation that is covered by wst.jsf validation Key: JBIDE-19403 URL: https://issues.jboss.org/browse/JBIDE-19403 Project: Tools (JBoss Tools) Issue Type: Task Components: jsf Affects Versions: 4.3.0.Alpha1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19395) Default template code for Servlet

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19395?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19395: -------------------------------------- Assignee: Daniel Azarov New Servlet wizard is a part of Eclipse Web Tools. It's not JBoss Tools. [~dazarov], please report it to Eclipse bugzilla. We also can try to create a patch. > Default template code for Servlet > --------------------------------- > > Key: JBIDE-19395 > URL: https://issues.jboss.org/browse/JBIDE-19395 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Arun Gupta > Assignee: Daniel Azarov > Fix For: 4.3.x > > > It would be nice to have a default template code generated for Servlet. This will make the generated Servlet a little bit more useful, and much easier to showcase in demos. > For example, here is one template that could be generated in doGet(): > response.getOutputStream().print("Served at: " + request.getContextPath()); > And doGet() called from doPost(). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19395) Default template code for Servlet

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19395?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19395: ----------------------------------- Fix Version/s: 4.3.x > Default template code for Servlet > --------------------------------- > > Key: JBIDE-19395 > URL: https://issues.jboss.org/browse/JBIDE-19395 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Arun Gupta > Fix For: 4.3.x > > > It would be nice to have a default template code generated for Servlet. This will make the generated Servlet a little bit more useful, and much easier to showcase in demos. > For example, here is one template that could be generated in doGet(): > response.getOutputStream().print("Served at: " + request.getContextPath()); > And doGet() called from doPost(). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18547) Generate index.html in default Dynamic Web Project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18547?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18547: -------------------------------------- Assignee: Daniel Azarov (was: Alexey Kazakov) [~dazarov] please report this issue to Eclipse bugzilla. And we have to create a patch if we want to have it fixed in Eclipse ;) Make sure that patch works fine with our JSF and Seam wizards/facets which may create index.html too. I'm not sure it's double for JBDS 9.0.0 / JBT 4.3.0 since it's going to be based on Eclipse Mars. If it doesn't fixed in Mars then it won't be available in JBT 4.3.0. > Generate index.html in default Dynamic Web Project > -------------------------------------------------- > > Key: JBIDE-18547 > URL: https://issues.jboss.org/browse/JBIDE-18547 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Arun Gupta > Assignee: Daniel Azarov > Fix For: 4.3.x > > Attachments: screenshot-1.png > > > Default Dynamic Web Project does not contain index.html and so running it on a server always require to generate this file first. That's a very typical scenario and should be fixed for a more seamless experience. > Accessing the application at http://localhost:8080/helloworld/ shows "Forbidden" as shown in the attachment. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3269) FeedHenry Build Farm Integration Level 1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3269?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3269. ---------------------------------- Resolution: Done QE has approved Beta1 release. I'm resolving this issue. [~psrna] feel free to reopen/create a new issue if you find any problems with FH support in Beta1. > FeedHenry Build Farm Integration Level 1 > ---------------------------------------- > > Key: JBDS-3269 > URL: https://issues.jboss.org/browse/JBDS-3269 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Pavol Srna > Fix For: 8.1.0.Beta1 > > > Level 1: > 1) Import Cordova Project from FeedHenry into JBDS > 2) git push of *our changes* to FH provided URL > 3) Using the Web UI to start the build process > 4) Using the Web UI to review the QR Code -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-393) Update BPMN2 to 1.1.2.201502050700

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-393?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-393. ------------------------------ Resolution: Done Mirrored and updated to 1.1.2.Final https://github.com/jbosstools/jbosstools-integration-stack/commit/adb1eec... > Update BPMN2 to 1.1.2.201502050700 > ---------------------------------- > > Key: JBTIS-393 > URL: https://issues.jboss.org/browse/JBTIS-393 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2 > Affects Versions: 8.0.1.CR1, 4.2.1.CR1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.1.CR1, 4.2.1.CR1 > > > Mirror in jbosstools and update TP and aggregate composite - BPMN2 Modeler 1.1.2.201502050700. > ref: https://bugzilla.redhat.com/show_bug.cgi?id=1134711 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 2015