March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19162) add new plugins to openshift pom and create feature

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19162?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19162: ------------------------------------------ Corrected labelling, typos and dates here: https://github.com/jbosstools/jbosstools-openshift/pull/578 > add new plugins to openshift pom and create feature > --------------------------------------------------- > > Key: JBIDE-19162 > URL: https://issues.jboss.org/browse/JBIDE-19162 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > Attachments: openshift-features.png > > > In JBIDE-19048 we created new plugins for the OpenShift v3 tooling and moved reusable parts to common plugins. We now need to get the maven build working (add the new modules) and create a v3 feature. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2260) Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2260?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-2260: --------------------------------- Forum Reference: https://community.jboss.org/message/756790#756790, https://developer.jboss.org/message/921557#921557 (was: https://community.jboss.org/message/756790#756790) > Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-2260 > URL: https://issues.jboss.org/browse/JBDS-2260 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.GA > Reporter: Isaac Rooskov > Assignee: Denis Golovin > Fix For: 9.0.x > > Attachments: JavaVersionReader.java.patch > > > *From customer in Bugzilla* > Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=850793 > Description of issue from customer: > Description of problem: > Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4 > Version-Release number of selected component (if applicable): > JBOSS Developer Studio 5.0.0.GA > How reproducible: > Start installation using > java - jar jbdevstudio-product-universal-5.0.0.v20120615-1714-H213-GA.jar > Actual results: > Installation is not passing at step 7 of 9, progress 1 of 4. > Expected results: > Additional info: -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19401) remove Seam & Portlet from JBT 4.3 default install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19401?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19401: ------------------------------------ PRs approved and merged. Building. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... >=65 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=3420 > remove Seam & Portlet from JBT 4.3 default install > --------------------------------------------------- > > Key: JBIDE-19401 > URL: https://issues.jboss.org/browse/JBIDE-19401 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein, seam2 > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Recently we removed Seams and Portlet from the default JBDS 9 install. Max said today we should do the same for JBT 4.3. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19401) remove Seam & Portlet from JBT 4.3 default install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19401?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19401: ------------------------------- Fix Version/s: 4.3.0.Alpha2 > remove Seam & Portlet from JBT 4.3 default install > --------------------------------------------------- > > Key: JBIDE-19401 > URL: https://issues.jboss.org/browse/JBIDE-19401 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein, seam2 > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Recently we removed Seams and Portlet from the default JBDS 9 install. Max said today we should do the same for JBT 4.3. -- 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 Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19395?page=com.atlassian.jira.plugi... ] Daniel Azarov edited comment on JBIDE-19395 at 3/17/15 4:06 PM: ---------------------------------------------------------------- [~ArunGupta], how about to use {code} response.getWriter().append("Served at: ").append(request.getContextPath()); {code} instead of: {code} response.getOutputStream().print("Served at: " + request.getContextPath()); {code} Roberto Sanchez Herrera asked in bugzilla: {quote} 3. Why did you decide to use response.getOutputStream(), which according to the javadoc: "Returns a ServletOutputStream suitable for writing binary data in the response", instead of response.getWriter(), which seems more appropriate (from javadoc: Returns a PrintWriter object that can send character text to the client.) {quote} was (Author: dazarov): [~ArunGupta], how about to use {code} response.getWriter().append("Served at: ").append(request.getContextPath()); {code} instead of: {code} response.getOutputStream().print("Served at: " + request.getContextPath()); {code} Roberto Sanchez Herrera asked in bugzilla: >3. Why did you decide to use response.getOutputStream(), which according to the javadoc: "Returns a >ServletOutputStream suitable for writing binary data in the response", instead of response.getWriter(), which seems more >appropriate (from javadoc: Returns a PrintWriter object that can send character text to the client.) > 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 Arun Gupta (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19395?page=com.atlassian.jira.plugi... ] Arun Gupta commented on JBIDE-19395: ------------------------------------ Sounds good. > 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 Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19395?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-19395: --------------------------------------- [~ArunGupta], how about to use {code} response.getWriter().append("Served at: ").append(request.getContextPath()); {code} instead of: {code} response.getOutputStream().print("Served at: " + request.getContextPath()); {code} Roberto Sanchez Herrera asked in bugzilla: >3. Why did you decide to use response.getOutputStream(), which according to the javadoc: "Returns a >ServletOutputStream suitable for writing binary data in the response", instead of response.getWriter(), which seems more >appropriate (from javadoc: Returns a PrintWriter object that can send character text to the client.) > 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] (JBTIS-396) JBoss Central doesn't recognise that a category item is already installed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-396?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-396: ---------------------------------- If you want things changed in Mylyn itself, open a bug at Eclipse. It's not too late to get stuff fixed/improved in the version of Mylyn in Luna. Or, if there's something we can do to improve/extend Mylyn, ping [~snjeza] or [~mickael_istria] and maybe they can take a look. > JBoss Central doesn't recognise that a category item is already installed > ------------------------------------------------------------------------- > > Key: JBTIS-396 > URL: https://issues.jboss.org/browse/JBTIS-396 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Reporter: Michelle Murray > Assignee: Paul Leacu > Attachments: dv1.png, dv2.png > > > I have JBDS 8.0.2 installed. > In JBoss Central Software/Update tab, I enabled Early Access. I then selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. I chose to only install ModeShape Client and followed the install through including restarting JBDS. > In JBoss Central Software/Update tab, 'JBoss Data Virtualization Developer' was still shown as uninstalled - as expected from JBTIS-363. I selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. ModeShape Client is listed and check box autoselected along with all of the Teiid items as available to install. BUT I just installed it!? > 1) I chose to only install the ModeShape Client again but then get an error message "Cannot complete the request. See the error log for details." > 2) So I chose to install all, including ModeShape Client, and the install proceeds to the next window without the error message but is listing that it will install ModeShape Client again. > As a user, this looks like a bug to me. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-396) JBoss Central doesn't recognise that a category item is already installed

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-396?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-396. ---------------------------- Resolution: Won't Fix I appreciate the feedback - however this would appear to be a Mylyn enhancement request when all is considered. There's really nothing that can be done on our end. Thanks for the input. > JBoss Central doesn't recognise that a category item is already installed > ------------------------------------------------------------------------- > > Key: JBTIS-396 > URL: https://issues.jboss.org/browse/JBTIS-396 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Reporter: Michelle Murray > Assignee: Paul Leacu > Attachments: dv1.png, dv2.png > > > I have JBDS 8.0.2 installed. > In JBoss Central Software/Update tab, I enabled Early Access. I then selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. I chose to only install ModeShape Client and followed the install through including restarting JBDS. > In JBoss Central Software/Update tab, 'JBoss Data Virtualization Developer' was still shown as uninstalled - as expected from JBTIS-363. I selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. ModeShape Client is listed and check box autoselected along with all of the Teiid items as available to install. BUT I just installed it!? > 1) I chose to only install the ModeShape Client again but then get an error message "Cannot complete the request. See the error log for details." > 2) So I chose to install all, including ModeShape Client, and the install proceeds to the next window without the error message but is listing that it will install ModeShape Client again. > As a user, this looks like a bug to me. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOCUS-40) Add Powermock to the target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-40?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated LOCUS-40: ---------------------------- Project: JBoss Tools Locus (was: Tools (JBoss Tools)) Key: LOCUS-40 (was: JBIDE-18053) Affects Version/s: 1.2.0 (was: 4.2.x) Component/s: (was: build) Fix Version/s: 1.2.0 (was: 1.2.0-LOCUS) (was: 4.3.0.Alpha2) > Add Powermock to the target platform > ------------------------------------ > > Key: LOCUS-40 > URL: https://issues.jboss.org/browse/LOCUS-40 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.2.0 > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Fix For: 1.2.0 > > > *Reason:* To improving testing by allowing the stubbing of scenerios like "new File(path).exists()" which require bytecode modifications in order to accomplish. Example of intended use: https://gist.github.com/jcantrill/fd83c27d3fc542742ec7 > *License and owner:* Apache 2.0 / https://github.com/jayway > *Original p2 repo:* http://powermock-osgi.googlecode.com/svn/updateSite/1.5.4.1/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/powermock/1.5.4.1/ > *Sources:* https://code.google.com/p/powermock-osgi/ , http://powermock-osgi.googlecode.com/svn/trunk/ > *Affected projects:* OpenShift tests > *Include in JBDS:* No > *Type of dependency:* testing > *List of bundles added/removed:* > {code} > + <unit id="org.powermock.mockito-junit.feature.feature.group" version="1.5.4.1"/> > + <unit id="org.objenesis" version="2.1.0"/> > + <unit id="javassist" version="3.18.1.GA"/> > {code} > *p2diff report:* > {code} > mistria@mistria--rh:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:$(pwd)/target/jbosstools-multiple.target.repo/ > > org.mockito.mockito-core [1.9.5] > > javassist [3.18.1.GA] > > org.powermock.powermock-api-support [1.5.4] > > org.powermock.powermock-reflect [1.5.4] > > org.powermock.powermock-api-mockito [1.5.4] > > org.powermock.powermock-module-junit4-common [1.5.4] > > org.powermock.powermock-module-junit4 [1.5.4] > > org.powermock.powermock-core [1.5.4] > > org.objenesis [2.1.0] > === Summary === > file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 9 unique IUs > {code} -- 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