June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11436) we should use license features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11436?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11436: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/420, https://github.com/jbosstools/jbosstools-devdoc/pull/52, https://github.com/jbosstools/jbosstools-freemarker/pull/36 (was: https://github.com/jbosstools/jbosstools-base/pull/409, https://github.com/jbosstools/jbosstools-base/pull/420, https://github.com/jbosstools/jbosstools-devdoc/pull/52, https://github.com/jbosstools/jbosstools-freemarker/pull/36) > we should use license features > ------------------------------ > > Key: JBIDE-11436 > URL: https://issues.jboss.org/browse/JBIDE-11436 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > > See http://relengofthenerds.blogspot.fr/2011/01/implementing-shared-licenses-... for explanation -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-452) Unable to pull the Fuse Plugins directly from JBDS

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-452?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-452: ---------------------------------- Hey [~rogerhui] [~apodhrad] - I did this: 1. Into a clean eclipse Luna jee and a clean workspace - I used Eclipse Marketplace to install jbds 8.1.0 2. Restarted eclipse, from JBoss Central I selected 'Fuse Integration Project' 3. Installed Fuse Tooling from the wizard 4. All installed and came up correctly. Could you (Roger) one more time try these steps - including the fresh Eclipse Luna jee and workspace. Also - check to make sure there's nothing odd in your .eclipse folder, etc. Thkx > Unable to pull the Fuse Plugins directly from JBDS > -------------------------------------------------- > > Key: JBTIS-452 > URL: https://issues.jboss.org/browse/JBTIS-452 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Affects Versions: 8.0.2.GA > Reporter: Roger Hui > Attachments: JBDSError.png, Untitled.log > > > JBDS 8.1 and can't install the fuse plugins see attachment. > Looks like the plugin are not pushed to the public site. > The work around is to download the integration zip from access.redhat.com (CSP) and install it from there, but then I won't get auto update.. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20141: ------------------------------------ {quote}in just a week seen cases of where having the public urls be separate from the internal schemas are helpful.{quote} I agree with the policy of "simple public URLs which provide a facade over longer internal ones", but it's helpful to provide examples backing your thesis rather than just stating it. When did you see this? --- That aside, I suggested we remove these: * http://download.jboss.org/jbosstools/updates/nightly/master/ * http://download.jboss.org/jbosstools/updates/nightly/mars/ * http://download.jboss.org/jbosstools/updates/development/mars/ To clarify the original suggestion, I'm suggesting we replace them with these: * http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ [or something similar starting with /mars/snapshots/ ?] * http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/ [or something similar starting with /mars/snapshots/ ?] * http://download.jboss.org/jbosstools/mars/development/updates/ You said you like a & b, which sounds like "don't change anything" but then you said "no, /updates/snapshots works too" so I'm not sure what the net results is of these seemingly conflicting statements. Please clarify for those in the audience who don't read minds well on Monday mornings. :D > Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites > ----------------------------------------------------------------------------- > > Key: JBIDE-20141 > URL: https://issues.jboss.org/browse/JBIDE-20141 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Today, we produce a lot of artifacts w/ every CI (snapshot), staging, development, & stable build. > But sometimes, finding these artifacts can be a daunting task. > Below are some URLs where things can be found. > *CI builds / SNAPSHOTS / nightlies* > * http://download.jboss.org/jbosstools/updates/nightly/master/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*) > * http://download.jboss.org/jbosstools/updates/nightly/mars -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*) > * http://download.jboss.org/jbosstools/mars/nightly/updates/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central) > * http://download.jboss.org/jbosstools/mars/snapshots/updates/ (individual projects' update sites) > ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ > ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/ > ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/master/ > ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/4.3.... > ** .. > * http://download.jboss.org/jbosstools/mars/snapshots/builds/ (individual timestamped CI builds) > *Staging Sites* > * http://download.jboss.org/jbosstools/mars/staging/builds/ > * http://download.jboss.org/jbosstools/mars/staging/updates/ > *Development Milestones* > * http://download.jboss.org/jbosstools/updates/development/mars/ -> ../../mars/development/updates/ (*OLD URL PATTERN*) > * http://download.jboss.org/jbosstools/mars/development/updates/ (composites & content that isn't *static*) > * http://download.jboss.org/jbosstools/static/mars/development/updates/ (actual update sites, moved here for Akamai performance) > ---- > For JBDS, we follow the same pattern as above but use https://devstudio.redhat.com/9.0/ instead of http://download.jboss.org/jbosstools/mars/ ... but we also have a /builds/installer/ folder because the public JBDS site now includes the standalone installer: > * https://devstudio.redhat.com/9.0/development/builds/installer/ > Also, for JBDS we don't have to differentiate between /static/ and non-static content, since Akamai set up the entire server to be mirrored to their servers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17686: ------------------------------------ I guess that's why it's in component = upstream [1], not server. [1] https://issues.jboss.org/browse/JBIDE/component/12311230 > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3476) this is first phase of project

by Adittya Jung Shahi (JIRA)

Adittya Jung Shahi created JBDS-3476: ---------------------------------------- Summary: this is first phase of project Key: JBDS-3476 URL: https://issues.jboss.org/browse/JBDS-3476 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Environment: PHP Reporter: Adittya Jung Shahi -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20054) Connection wizard: Cannot remove secure storage of v3 connection token

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20054?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20054 at 6/29/15 12:39 PM: -------------------------------------------------------------------- [~jcantrill] this was a higher prio bug since one could not easily remove the token from secure storage and security related issues are generally looked at in higher prios. I verified it, it works for me, the token is now correctly removed from secure storage if I uncheck the checkbox. merging and pushing to upstream/master was (Author: adietish): [~jcantrill] this was a higher prio bug since one could not easily remove the token from secure storage and security related issues are generally looked in higher prios. I verified it, it works for me. merging and pushing to upstream/master > Connection wizard: Cannot remove secure storage of v3 connection token > ---------------------------------------------------------------------- > > Key: JBIDE-20054 > URL: https://issues.jboss.org/browse/JBIDE-20054 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > > If I create a new v3 connection with OAuth authentization method and choose to store token in secure storage (or I edit the existing one connection with token and check the checkbox to store the token in secure storage), token is stored. But if I decide later to prevent it to being stored by unchecking the checkbox in Edit connection dialog, it does not work. If I uncheck the checbox and hit the Finish button and come back to edit connection dialog, the checkbox is still checked. This is related only to OAuth authentization method (basic authentization method works as expected). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20054) Connection wizard: Cannot remove secure storage of v3 connection token

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20054?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20054: ------------------------------------------ [~jcantrill] this was a higher prio bug since one could not easily remove the token from secure storage and security related issues are generally looked in higher prios. I verified it, it works for me. merging and pushing to upstream/master > Connection wizard: Cannot remove secure storage of v3 connection token > ---------------------------------------------------------------------- > > Key: JBIDE-20054 > URL: https://issues.jboss.org/browse/JBIDE-20054 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > > If I create a new v3 connection with OAuth authentization method and choose to store token in secure storage (or I edit the existing one connection with token and check the checkbox to store the token in secure storage), token is stored. But if I decide later to prevent it to being stored by unchecking the checkbox in Edit connection dialog, it does not work. If I uncheck the checbox and hit the Finish button and come back to edit connection dialog, the checkbox is still checked. This is related only to OAuth authentization method (basic authentization method works as expected). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19854) When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19854?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19854: ------------------------------------- [~mmalina] Have you replicated anything like this? I can't replicate, but it doesn't seem like the logmodule issue https://community.jboss.org/thread/195016 > When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19854 > URL: https://issues.jboss.org/browse/JBIDE-19854 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: OS: Windows 8.1; Intel Core i3 540 3.07Ghz; 4GB DDR3 1333Mhz; Java Version 1.7.0_75; > Reporter: Giancarlo giulian > Labels: classnotfound, debug, debugging, jboss, main, wildfly > Attachments: image2.png, image3.png, imagem1.png > > > This problem has recently begun, before that is it working in debug mode. Errors log are not created and doesn't appear in console output using Eclipse Luna. > Program Arguments: > {quote} > -mp "C:/wildfly-8.1/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\wildfly-8.1\standalone > {quote} > VM Arguments: > {quote} > "-Dprogram.name=JBossTools: WildFly 8.1" -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=C:/wildfly-8.1/standalone/log/boot.log" "-Dlogging.configuration=file:/C:/wildfly-8.1/standalone/configuration/logging.properties" "-Djboss.home.dir=C:/wildfly-8.1" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost > {quote} > Images: > https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png > https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17686. --------------------------------- Resolution: Done If you download Mars RC1 or RC2 or something, and install JBT beta1 into it, then it's not fixed. If you download Mars actual release JEE edition, then it is fixed. It is independent of which JBT you use. It is solely dependent on which Mars you use. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17686: -------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Beta2) > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015