January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-380) Update jbosstools website for JBTIS 4.2.0.Beta2/ JBDSIS 8.0.0.Beta2

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-380: -------------------------------- Summary: Update jbosstools website for JBTIS 4.2.0.Beta2/ JBDSIS 8.0.0.Beta2 Key: JBTIS-380 URL: https://issues.jboss.org/browse/JBTIS-380 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution Affects Versions: 8.0.0.Beta2, 4.2.0.Beta2 Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 8.0.0.Beta2, 4.2.0.Beta2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-350) Missing BPEL source plugins

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-350?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-350. ----------------------------------- Verified with JBDS-IS 8.0.0.Beta2a > Missing BPEL source plugins > --------------------------- > > Key: JBTIS-350 > URL: https://issues.jboss.org/browse/JBTIS-350 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Fix For: 8.0.0.Beta2a, 4.2.0.Beta2a > > > After installing all components included in Beta1 there are only the following souce plugins for BPEL > org.jboss.tools.bpel.runtimes.source_1.2.101.Final-v20140108-1353-B1045.jar > org.switchyard.tools.ui.bpel.source_2.0.0.v20141011-0508-H499-Alpha3.jar > but there are much more BPEL plugins such as > org.eclipse.bpel.ui, org.eclipse.bpel.ui.validator -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3276) JBDS-IS Installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen edited comment on JBDS-3276 at 1/12/15 9:45 AM: -------------------------------------------------------------------- having devstudio go out and install Fuse from a remote site was the option suggested to avoid having to build and ship another installer. But that is not what Fuse users/PM was asking for - it was one download, one install. Thus the idea was born that JBDS IS builds will take jbds core installer unzip it, add their updatesite to the installer + list of features to install. to suppor this our jbds core installer would need to detect this and show the extra page of installation options. this reduce the amount of build/QE/testing that needs doing and provides the one download, one install option. was (Author: maxandersen): having devstudio go out and install Fuse from a remote site was the option suggested to avoid having to build and ship another installer. But that is not what Fuse users/PM was asking for - it was one download, one install. Thus the idea was born that JBDS IS builds will take jbds core installer unzip it, add their updatesite to the installer + list of features to install. to suppor this our jbds core installer would need to detect this and show the extra page of installation options. this reduce the amount of build/QE/testing that needs doing. > JBDS-IS Installer > ----------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3276) JBDS-IS Installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3276: ------------------------------------------- having devstudio go out and install Fuse from a remote site was the option suggested to avoid having to build and ship another installer. But that is not what Fuse users/PM was asking for - it was one download, one install. Thus the idea was born that JBDS IS builds will take jbds core installer unzip it, add their updatesite to the installer + list of features to install. to suppor this our jbds core installer would need to detect this and show the extra page of installation options. this reduce the amount of build/QE/testing that needs doing. > JBDS-IS Installer > ----------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18900: ------------------------------------- guys, frankly I can't see the point of adding the parameters section. I do believe it will be even more ambiguous then the start page. in the 'content' tag user can define all parameters that he want to have and there will be no equivocality. > CordovaSim: Can't run default FeedHenry app locally > --------------------------------------------------- > > Key: JBIDE-18900 > URL: https://issues.jboss.org/browse/JBIDE-18900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > Attachments: configuration.png, cordovasimFH.png, hello_tom.png, newLaunch.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip > > > Basically, the situation is the following: > 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field ) > 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio > 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail! > 4. However, there is an option to use *local* server instead of *remote* one > 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner > 6. In order to run local server one needs: > - unpack the app > - run *npm install .* > - run *grunt serve* > Need to find the way to made CordovaSim use this *local* server -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3275) Add wildfly archetypes to JBoss Central

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBDS-3275?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on JBDS-3275: ---------------------------------------- Archetypes staged at https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... > Add wildfly archetypes to JBoss Central > --------------------------------------- > > Key: JBDS-3275 > URL: https://issues.jboss.org/browse/JBDS-3275 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > Supporting Wildfly archetypes with JBoss Central. As an Java EE developer, I need to be able to switch between EAP and Wildfly, when I select Wildfly, the archetype needs to correctly include the right BOMs, where all artifacts are available only on Maven Central. > This should include both the Java EE Web Project, Java EE EAR Project, and HTML5 Project -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19029) Error: "Attribute name is not allowed to appear in element sub-deployment" in two Seam examples

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19029?page=com.atlassian.jira.plugi... ] Matous Jobanek updated JBIDE-19029: ----------------------------------- Environment: JBDS 8.0.1.GA > Error: "Attribute name is not allowed to appear in element sub-deployment" in two Seam examples > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19029 > URL: https://issues.jboss.org/browse/JBIDE-19029 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: JBDS 8.0.1.GA > Reporter: Matous Jobanek > > When the projects > * mail-ear from the Seam example mail \[1\] > * tasks-ear from the Seam example tasks \[2\] > are imported into JBDS the error > {panel} > Attribute 'name' is not allowed to appear in element 'sub-deployment' > {panel} > will be shown for the file jboss-deployment-structure.xml. > It is caused by the bug in _jboss-deployment-structure-1_0.xsd_; see AS7-1345 > This bug should be IMHO ignored and the error shouldn't be shown. > \[1\] https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/mail > \[2\] https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/tasks -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19029) Error: "Attribute name is not allowed to appear in element sub-deployment" in two Seam examples

by Matous Jobanek (JIRA)

Matous Jobanek created JBIDE-19029: -------------------------------------- Summary: Error: "Attribute name is not allowed to appear in element sub-deployment" in two Seam examples Key: JBIDE-19029 URL: https://issues.jboss.org/browse/JBIDE-19029 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Matous Jobanek When the projects * mail-ear from the Seam example mail \[1\] * tasks-ear from the Seam example tasks \[2\] are imported into JBDS the error {panel} Attribute 'name' is not allowed to appear in element 'sub-deployment' {panel} will be shown for the file jboss-deployment-structure.xml. It is caused by the bug in _jboss-deployment-structure-1_0.xsd_; see AS7-1345 This bug should be IMHO ignored and the error shouldn't be shown. \[1\] https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/mail \[2\] https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/tasks -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-348) User can not download the release note from Red Hat Customer Portal

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-348?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-348. ----------------------------------- Verified > User can not download the release note from Red Hat Customer Portal > ------------------------------------------------------------------- > > Key: JBTIS-348 > URL: https://issues.jboss.org/browse/JBTIS-348 > Project: JBoss Tools Integration Stack > Issue Type: Documentation > Environment: JBDSIS 7.0.3.GA > Reporter: hisao furuichi > Assignee: Paul Leacu > > From Red Hat Customer Portal[1][2], user can not download the release note for JBDSIS 7.0.3[3]. > [1] https://access.redhat.com/documentation/ja-JP/Red_Hat_JBoss_Developer_Stu... > [2] https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl... > [3] https://devstudio.jboss.com/updates/7.0/integration-stack/release-notes/R... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18900: -------------------------------------- +1 for removing the start page from CordovaSim launch configuration. Perhaps we can add a parameters section. I am not comfortable about adding a new menu item, whether it is backed up a new launch config type or not, at this point. However if we must I do agree that "Run FeedHenry locally" as a men item is confusing and I prefer "Run CordovaSim \wFeedHenry". An alternate is to document the local FH use and let users modify the CordovaSim launch config. > CordovaSim: Can't run default FeedHenry app locally > --------------------------------------------------- > > Key: JBIDE-18900 > URL: https://issues.jboss.org/browse/JBIDE-18900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > Attachments: configuration.png, cordovasimFH.png, hello_tom.png, newLaunch.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip > > > Basically, the situation is the following: > 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field ) > 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio > 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail! > 4. However, there is an option to use *local* server instead of *remote* one > 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner > 6. In order to run local server one needs: > - unpack the app > - run *npm install .* > - run *grunt serve* > Need to find the way to made CordovaSim use this *local* server -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 January 2015