August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2713) Link to anonymous update stats source codes leads to old svn

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2713?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-2713. ------------------------------ Resolution: Done Fixed and rolled out to server: http://www.jboss.org/tools/usage/ Fixed and will roll out in 30 mins: https://devstudio.jboss.com/usage/ > Link to anonymous update stats source codes leads to old svn > ------------------------------------------------------------ > > Key: JBDS-2713 > URL: https://issues.jboss.org/browse/JBDS-2713 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Usage Reporting > Affects Versions: 7.0.0.GA > Reporter: Jiri Svitak > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > > Link to anonymous update stats source codes leads to old svn. Should be updated to relevant code on github, so a suspicious user can check that. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2713) Link to anonymous update stats source codes leads to old svn

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2713?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2713: ----------------------------- Fix Version/s: 7.0.0.GA > Link to anonymous update stats source codes leads to old svn > ------------------------------------------------------------ > > Key: JBDS-2713 > URL: https://issues.jboss.org/browse/JBDS-2713 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Usage Reporting > Affects Versions: 7.0.0.GA > Reporter: Jiri Svitak > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > > Link to anonymous update stats source codes leads to old svn. Should be updated to relevant code on github, so a suspicious user can check that. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-14341: ------------------------------------- And on this jira, I and the openshift team consider it to be fairly low priority as it is only for a very small subset of end-users, people who wish to build brand new carts (e.g. a Wordpress cart). > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Priority: Optional > Fix For: 4.2.x > > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-137) ESB Tests are failing locating project examples

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBTIS-137?page=com.atlassian.jira.plugin.... ] Len DiMaggio reassigned JBTIS-137: ---------------------------------- Assignee: Paul Leacu (was: Len DiMaggio) > ESB Tests are failing locating project examples > ----------------------------------------------- > > Key: JBTIS-137 > URL: https://issues.jboss.org/browse/JBTIS-137 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.1.1 > Reporter: Nick Boldt > Assignee: Paul Leacu > > Problem: > ESB tests stopped being able to find project examples when executing test. Why ? > Nick's original theory, but that does not answer why the content that is still there is not showing up: > Problem: > a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ > b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder > c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. > >> http://memegenerator.net/instance/33999035 << > Solution: > a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites > d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2665) Link under 'Other resources' on JBoss Central is incorrect for JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2665?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2665: ------------------------------------------- not sure why the url now is back to being the old url - @fbricon can you investigate ? But that said - the two urls now overlap in content (both have JBDS 6 content). Can't we make both have JBDS 7 content ? >From emails it sounds like this was what was supposed to happen - no change of the url and/or content to avoid lost links/info. > Link under 'Other resources' on JBoss Central is incorrect for JBDS > ------------------------------------------------------------------- > > Key: JBDS-2665 > URL: https://issues.jboss.org/browse/JBDS-2665 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Central > Reporter: Michelle Murray > Assignee: Fred Bricon > Labels: respin-a > Fix For: 7.0.0.Beta2 > > > I realise that JBoss Central is still under development but I wanted to point out an issue. Under 'Other resources' there is a link titled 'Product documentation' that links to http://docs.jboss.org/tools/latest/. > 1. Is this the right link for community docs? /tools/latest will store documentation under development for the next release. Should this link point to the community docs for the version of JBT installed (for example, tools/4.1.0 for JBT 4.1.0)? There is ongoing debate about what exactly the link will be - see TOOLSDOC-310. > 2. This link does not point to the right place for JBDS users. JBDS documentation is stored here: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ So how can the issue of two separate documentation locations for JBT and JBDS be got around? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2665) Link under 'Other resources' on JBoss Central is incorrect for JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2665?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2665: -------------------------------------- Assignee: Fred Bricon (was: Max Rydahl Andersen) > Link under 'Other resources' on JBoss Central is incorrect for JBDS > ------------------------------------------------------------------- > > Key: JBDS-2665 > URL: https://issues.jboss.org/browse/JBDS-2665 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Central > Reporter: Michelle Murray > Assignee: Fred Bricon > Labels: respin-a > Fix For: 7.0.0.Beta2 > > > I realise that JBoss Central is still under development but I wanted to point out an issue. Under 'Other resources' there is a link titled 'Product documentation' that links to http://docs.jboss.org/tools/latest/. > 1. Is this the right link for community docs? /tools/latest will store documentation under development for the next release. Should this link point to the community docs for the version of JBT installed (for example, tools/4.1.0 for JBT 4.1.0)? There is ongoing debate about what exactly the link will be - see TOOLSDOC-310. > 2. This link does not point to the right place for JBDS users. JBDS documentation is stored here: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ So how can the issue of two separate documentation locations for JBT and JBDS be got around? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15317) LiveReload script injection corrupted html encoding

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15317?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15317: ---------------------------------- Fix Version/s: 4.1.1.Final 4.2.0.Alpha1 > LiveReload script injection corrupted html encoding > --------------------------------------------------- > > Key: JBIDE-15317 > URL: https://issues.jboss.org/browse/JBIDE-15317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Pei-Tang Huang > Assignee: Max Rydahl Andersen > Priority: Critical > Labels: encoding, livereload > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > Attachments: chinese.html > > Original Estimate: 1 day > Remaining Estimate: 1 day > > LiveReload script injection dissmisses the encoding of the original HTML content, my page contains CJK character in UTF-8 all became "?" character. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15317) LiveReload script injection corrupted html encoding

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15317?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-15317: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) Please review the PR so it can be applied on JBT 4.1.x branch and master > LiveReload script injection corrupted html encoding > --------------------------------------------------- > > Key: JBIDE-15317 > URL: https://issues.jboss.org/browse/JBIDE-15317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Pei-Tang Huang > Assignee: Max Rydahl Andersen > Priority: Critical > Labels: encoding, livereload > Attachments: chinese.html > > Original Estimate: 1 day > Remaining Estimate: 1 day > > LiveReload script injection dissmisses the encoding of the original HTML content, my page contains CJK character in UTF-8 all became "?" character. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15287) Allow customization of automatically-added deployment scanner attributes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15287?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15287: ------------------------------------- Looking at the deployment scanner api, it seems only 2 attributes make sense to be exposed to users. 1) scan-interval 2) deployment-timeout > Allow customization of automatically-added deployment scanner attributes > ------------------------------------------------------------------------ > > Key: JBIDE-15287 > URL: https://issues.jboss.org/browse/JBIDE-15287 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.1.Final > > > Specifically timeouts. https://community.jboss.org/message/758366#758366 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15185) add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15185?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15185: ------------------------------------- As Max said, only servers can be shared items currently. Therefore when you share a server instance, it references a runtime name. When you import the server xml file, it will not find the runtime (because it doesn't exist), and so you'll need to create a new runtime pointing to your local installation and make sure it has the runtime name your server is looking for. Or, once you make your runtime, you can double-click your server and set the runtime to the new one you just made. Allowing this type of enhancement would be something that would have to be done upstream in WTP. But it still wouldn't help the usecase of trying to share servers, since you can't currently share runtimes at all. So this really should be a 'later' issue until other larger issues are worked out. > add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory. > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15185 > URL: https://issues.jboss.org/browse/JBIDE-15185 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > > The current jbds version only allow users to specify an absolute path for "Home Directory" when creating JBoss Runtime Server. Is it possible to use a user defined variable here? -- 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, 8 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 August 2013