April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12738) OpenShift Explorer: Empty SSH wizard titles

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12738?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-12738. ---------------------------------- Verified. > OpenShift Explorer: Empty SSH wizard titles > ------------------------------------------- > > Key: JBIDE-12738 > URL: https://issues.jboss.org/browse/JBIDE-12738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Alpha2 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta1 > > Attachments: add-ssh-key.png, manage-ssh-keys.png, new-ssh-key.png, sshtitles.png > > > The wizard title should be set in these dialogs (will help QE in SWTBot tests and will look much better imho): > !sshtitles.png|thumbnail! > Accessible via OpenShift Explorer -> #1 Manage SSH Keys -> #2 New... -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14319) CordovaSim: Aerogear default project isn't emulated by CordovaSim

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14319?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-14319: -------------------------------------- I am reluctant to add cordova.js to the workspace because this is a file that depends on the version of the Cordova you are running against. Although our tools support a single version at the moment, it is inevitable that we will eventually support at least upgrading to a newer version of Cordova. If the template adds a cordova.js to the workspace we can no longer manage it. Could [~yradtsevich]'s launch configuration for CordovaSim (JBIDE-14083) be actually the place to manage the cordova.js? > CordovaSim: Aerogear default project isn't emulated by CordovaSim > ----------------------------------------------------------------- > > Key: JBIDE-14319 > URL: https://issues.jboss.org/browse/JBIDE-14319 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Ilya Buziuk > Assignee: Gorkem Ercan > Fix For: 4.1.0.Beta1 > > > The root of the issue is pretty obvious - there is no cordova.js file in the aerogear project, which is vital for CordovaSim. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13977) updates/requirements/*/build.xml scripts should include pack.gz artifacts (using p2.process.artifacts pack="true") to make resolving multiple.target faster

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13977?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13977: ---------------------------------------- > artifacts.jar.pack.gz and content.jar.pack.gz but those are small files anyway, so the b/w and disk usage is relatively small. features/*.pack.gz are also quite small files. > updates/requirements/*/build.xml scripts should include pack.gz artifacts (using p2.process.artifacts pack="true") to make resolving multiple.target faster > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13977 > URL: https://issues.jboss.org/browse/JBIDE-13977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite, upstream > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Beta1 > > > All ant scripts (updates/requirements/*/build.xml) used to mirror 3rd party reqs from Eclipse.org and other places should be updated to generate .pack.gz artifacts too. > {code}<p2.process.artifacts pack="true" repositoryPath="file:/${repoDirLocation}" />{code} > Refs: > * http://git.eclipse.org/c/platform/eclipse.platform.releng.eclipsebuilder.... > * http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.... -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14119) look at how to handle the different jmx views/perspectives between AS and FuseSource plugins

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14119?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-14119: ---------------------------------------- On Fuse side we are currently using a not very actual version of the JMX plugins from http://www.jvmmonitor.org/. The source code of these plugins can be found at Google Code: https://code.google.com/a/eclipselabs.org/p/jvmmonitor/ We extend the JMX Navigator by providing new types of nodes which can be displayed / browsed. So if we go that way then we will need some kind of extension points to plug in our own node types / images / etc. >From what I understood so far this project is a fork of the plugins you are currently using. Not sure when this fork was done but it seems that this project is actively developed. Maybe you have the chance to compare both versions of JMX tooling and then decide based on the features of each project which to use in future. But it definitely makes no sense to maintain two versions of JMX tooling. A nice feature of jvmmonitor is that it can detect local VMs and connect to them without knowing the JMX URI. Though you can also manually create JMX connections the old style way. > look at how to handle the different jmx views/perspectives between AS and FuseSource plugins > -------------------------------------------------------------------------------------------- > > Key: JBIDE-14119 > URL: https://issues.jboss.org/browse/JBIDE-14119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > > Talk with [~lhein] he knows more -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-318) NeedInfo: Describing the software listed on Software/Update page

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-318?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-318: ------------------------------------- Assignee: Snjezana Peco (was: Michelle Murray) > NeedInfo: Describing the software listed on Software/Update page > ---------------------------------------------------------------- > > Key: TOOLSDOC-318 > URL: https://issues.jboss.org/browse/TOOLSDOC-318 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide - JBoss Central & JBoss Perspective > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Snjezana Peco > > Software is listed in the JBoss Central tab, on the Software/Update page. This is not all of the software available to install in Eclipse so why are these specific items listed here? How do I describe them to a user? Are they JBoss plug-ins or related to JBoss technology or ...? > Also, is the software/update page also going to be updated for JBDS 7.0? I can see that the Getting Started page is undergoing redevelopment. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-318) NeedInfo: Describing the software listed on Software/Update page

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-318: ---------------------------------------- Summary: NeedInfo: Describing the software listed on Software/Update page Key: TOOLSDOC-318 URL: https://issues.jboss.org/browse/TOOLSDOC-318 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Components: User Guide - JBoss Central & JBoss Perspective Affects Versions: 4.1.0 Reporter: Michelle Murray Assignee: Michelle Murray Software is listed in the JBoss Central tab, on the Software/Update page. This is not all of the software available to install in Eclipse so why are these specific items listed here? How do I describe them to a user? Are they JBoss plug-ins or related to JBoss technology or ...? Also, is the software/update page also going to be updated for JBDS 7.0? I can see that the Getting Started page is undergoing redevelopment. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13812) openshift-java-client: get rid of external class to (de)code base64

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13812?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13812: ------------------------------------------------- Fedora Update System <updates(a)fedoraproject.org> changed the Status of [bug 902017|https://bugzilla.redhat.com/show_bug.cgi?id=902017] from ON_QA to CLOSED > openshift-java-client: get rid of external class to (de)code base64 > ------------------------------------------------------------------- > > Key: JBIDE-13812 > URL: https://issues.jboss.org/browse/JBIDE-13812 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > We're currently using a class that we copied from a different project to (de)code base64. This contradicts the fedora project which wants to package us into an rpm. They suggested to package the full library instead. > Since we dont want to agument the numbers of dependencies, I'll switch to JDK means to (de)code base64. This will bind us to >= JDK6 which is IMHO perfectly fine. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13812) openshift-java-client: get rid of external class to (de)code base64

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13812?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13812: ------------------------------------------------- Fedora Update System <updates(a)fedoraproject.org> made a comment on [bug 902017|https://bugzilla.redhat.com/show_bug.cgi?id=902017] openshift-java-client-2.0.3-3.20130320git7073708.fc19 has been pushed to the Fedora 19 stable repository. > openshift-java-client: get rid of external class to (de)code base64 > ------------------------------------------------------------------- > > Key: JBIDE-13812 > URL: https://issues.jboss.org/browse/JBIDE-13812 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > We're currently using a class that we copied from a different project to (de)code base64. This contradicts the fedora project which wants to package us into an rpm. They suggested to package the full library instead. > Since we dont want to agument the numbers of dependencies, I'll switch to JDK means to (de)code base64. This will bind us to >= JDK6 which is IMHO perfectly fine. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-66) Mirror Eclipse BPMN2 Modeler v0.2.5 on jboss tools requirements

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-66?page=com.atlassian.jira.plugin.s... ] Nick Boldt commented on JBTIS-66: --------------------------------- *{color:green}Mirror updated:{color}* http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2... *{color:red}Mirror deleted:{color}* http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2... > Mirror Eclipse BPMN2 Modeler v0.2.5 on jboss tools requirements > --------------------------------------------------------------- > > Key: JBTIS-66 > URL: https://issues.jboss.org/browse/JBTIS-66 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: releng, switchyard, target-platform > Affects Versions: 4.0.0 > Reporter: Robert (Bob) Brodt > Assignee: Robert (Bob) Brodt > Fix For: 4.0.0 > > > Here is the site URL: http://download.eclipse.org/bpmn2-modeler/site/0.2.5/ > This is required for SwitchYard 0.8. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13977) updates/requirements/*/build.xml scripts should include pack.gz artifacts (using p2.process.artifacts pack="true") to make resolving multiple.target faster

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13977?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13977 at 4/27/13 3:16 PM: ------------------------------------------------------------- When I removed the extra packed jars from the ./features/ and ./ folders and regenerated the metadata... {code}<delete quiet="true" failonerror="false"><fileset dir="${workDir}" includes="*.pack.gz, features/*.pack.gz"/></delete> <p2.publish.featuresAndBundles metadataRepository="file:${workDir}" artifactRepository="file:${workDir}" publishartifacts="true" source="${workDir}" compress="${compress}" />{code} ... the resulting artifacts.xml file was the same, so I guess we might was well keep them in the resulting repo, as I'm guessing p2 will in fact see them. Not 100% sure about artifacts.jar.pack.gz and content.jar.pack.gz but those are small files anyway, so the b/w and disk usage is relatively small. was (Author: nickboldt): When I removed the extra packed jars from the ./features/ and ./ folders and regenerated the metadata... {code} <delete quiet="true" failonerror="false"><fileset dir="${workDir}" includes="*.pack.gz, features/*.pack.gz"/></delete> <p2.publish.featuresAndBundles metadataRepository="file:${workDir}" artifactRepository="file:${workDir}" publishartifacts="true" source="${workDir}" compress="${compress}" /> {code} ... the resulting artifacts.xml file was the same, so I guess we might was well keep them in the resulting repo, as I'm guessing p2 will in fact see them. Not 100% sure about artifacts.jar.pack.gz and content.jar.pack.gz but those are small files anyway, so the b/w and disk usage is relatively small. > updates/requirements/*/build.xml scripts should include pack.gz artifacts (using p2.process.artifacts pack="true") to make resolving multiple.target faster > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13977 > URL: https://issues.jboss.org/browse/JBIDE-13977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite, upstream > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Beta1 > > > All ant scripts (updates/requirements/*/build.xml) used to mirror 3rd party reqs from Eclipse.org and other places should be updated to generate .pack.gz artifacts too. > {code}<p2.process.artifacts pack="true" repositoryPath="file:/${repoDirLocation}" />{code} > Refs: > * http://git.eclipse.org/c/platform/eclipse.platform.releng.eclipsebuilder.... > * http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.... -- 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, 12 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 April 2013