October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15670) openshift-java-client: allow users to list quickstarts

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15670?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15670: ------------------------------------- Labels: openshift-java-client (was: ) > openshift-java-client: allow users to list quickstarts > ------------------------------------------------------ > > Key: JBIDE-15670 > URL: https://issues.jboss.org/browse/JBIDE-15670 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.2.x > > > {quote} > For QuickStarts, brokers may choose to > a) enable community quickstarts > (the URL you saw below, set by COMMUNITY_QUICKSTART_URL being a URL in /etc/openshift/broker.conf) > b) enable their own list of quickstarts > (a different url, /broker/rest/quickstarts, configured from /etc/openshift/quickstarts.json) > c) disable the quickstarts link > (delete /etc/openshift/quickstarts.json) > To correctly fetch the quickstarts for a server, retrieve the API document > /broker/rest/api > and look for the LIST_QUICKSTARTS link. If it is present, you may retrieve quickstarts. If it is absent, you should assume there are no quickstarts. > Retrieving the list of quickstarts, unlike other REST API feed calls, is very specific: > * API versioning is not supported > * Only JSON is supported > * The body of the response is slightly different than standard REST API feed results > * If you encounter a parse error or an unexpected data value you are required to handle it gracefully by omitting the entry - the API may change without warning (although hopefully not) > The format of the JSON response (in either a) or b) above) is: > {quote} > {code} > { > data: [ > quickstart: { > id: "<string id>", > href: "<absolute URL to a display URL for the quickstart>", > name: "<name>", > updated: "<last update date in seconds from the epoch>", > summary: "<brief HTML body of the item>", > body: "<full HTML body of the item>", > cartridges: "<cartridge spec>", > website: "<URL of metadata about the source of the quickstart or the technology>", > tags: "<comma delimited list of tags>", > language: "<display name of the type of quickstart>", > initial_git_url: "<absolute URL or Git reference to source>", > provider: "openshift|reviewed|partner|community", # default is community > }, > ] > } > {code} > {quote} > You should assume that arbitrary content could be injected into any of these fields and defend yourself against XSS appropriately. You should also assume that the structure could be changed at any time. > Cartridge spec: > The cartridge spec is defined as either: > a) a comma delimited list of cartridge name search conditions > b) a string containing a JSON array > If the leading character of the cartridge spec is '[', you must convert the cartridge spec to JSON and submit the value provided to the server on creation as the "cartridges" field. > Otherwise, > 1) split the string by "," into "segments" > 2) trim whitespace from each segment > 3) split each segment by "|" into "matches" - these represent logical ORs > 4) strip leading and trailing "*" characters > 5) For each segment, return all cartridges that have a case-insensitive substring match on any of the "matches" in that segment for the user to select. > See https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea... > and https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea... > {quote} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15581) openshift-java-client: support PATCH http method

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15581?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-15581. -------------------------------------- Fix Version/s: 4.1.1.Beta1 Resolution: Done > openshift-java-client: support PATCH http method > ------------------------------------------------ > > Key: JBIDE-15581 > URL: https://issues.jboss.org/browse/JBIDE-15581 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > OpenShift's using the PATCH http method in links for protocol 1.6 (will those links get backported?). > The OpenShift java client does not support any method that differs from GET, POST, PUT, DELETE and should support links that use the PATCH http method. > {quote} > (06:35:55 PM) clayton: we're adding PATCH methods and I'm ensuring that the client tools will be future compatible when that happens > (06:36:06 PM) clayton: they'll only be in API 1.6 but want to fix it now > {quote} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15669) Compile Errors While Building Server Component Against Luna Based Target Platform

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15669?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15669: ---------------------------------- Description: {code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.18.1:compile (default-compile) on project org.jboss.ide.eclipse.as.core: Compilation failure: Compilation failure: [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[18,0] [ERROR] import org.eclipse.core.runtime.internal.adaptor.EclipseEnvironmentInfo; [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [ERROR] The import org.eclipse.core.runtime.internal.adaptor.EclipseEnvironmentInfo cannot be resolved [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[19,0] [ERROR] import org.eclipse.osgi.framework.internal.core.FrameworkProperties; [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [ERROR] The import org.eclipse.osgi.framework.internal.core cannot be resolved [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[160,0] [ERROR] String ts = FrameworkProperties.getProperty("eclipse.startTime"); //$NON-NLS-1$ [ERROR] ^^^^^^^^^^^^^^^^^^^ [ERROR] FrameworkProperties cannot be resolved [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[188,0] [ERROR] String value = FrameworkProperties.getProperty(key, "unknown"); //$NON-NLS-1$ [ERROR] ^^^^^^^^^^^^^^^^^^^ [ERROR] FrameworkProperties cannot be resolved [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[208,0] [ERROR] write("BootLoader constants: OS=" + EclipseEnvironmentInfo.getDefault().getOS()); //$NON-NLS-1$ [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ [ERROR] EclipseEnvironmentInfo cannot be resolved [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[209,0] [ERROR] write(", ARCH=" + EclipseEnvironmentInfo.getDefault().getOSArch()); //$NON-NLS-1$ [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ [ERROR] EclipseEnvironmentInfo cannot be resolved [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[210,0] [ERROR] write(", WS=" + EclipseEnvironmentInfo.getDefault().getWS()); //$NON-NLS-1$ [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ [ERROR] EclipseEnvironmentInfo cannot be resolved [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[211,0] [ERROR] writeln(", NL=" + EclipseEnvironmentInfo.getDefault().getNL()); //$NON-NLS-1$ [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ [ERROR] EclipseEnvironmentInfo cannot be resolved [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[214,0] [ERROR] writeArgs("Framework arguments: ", EclipseEnvironmentInfo.getDefault().getNonFrameworkArgs()); //$NON-NLS-1$ [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ [ERROR] EclipseEnvironmentInfo cannot be resolved [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[215,0] [ERROR] writeArgs("Command-line arguments: ", EclipseEnvironmentInfo.getDefault().getCommandLineArgs()); //$NON-NLS-1$ [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ [ERROR] EclipseEnvironmentInfo cannot be resolved [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[335,0] [ERROR] FrameworkProperties.setProperty(PROP_LOGFILE, newFile == null ? "" : newFile.getAbsolutePath()); //$NON-NLS-1$ [ERROR] ^^^^^^^^^^^^^^^^^^^ [ERROR] FrameworkProperties cannot be resolved{code} > Compile Errors While Building Server Component Against Luna Based Target Platform > --------------------------------------------------------------------------------- > > Key: JBIDE-15669 > URL: https://issues.jboss.org/browse/JBIDE-15669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Denis Golovin > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > > {code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.18.1:compile (default-compile) on project org.jboss.ide.eclipse.as.core: Compilation failure: Compilation failure: > [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[18,0] > [ERROR] import org.eclipse.core.runtime.internal.adaptor.EclipseEnvironmentInfo; > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The import org.eclipse.core.runtime.internal.adaptor.EclipseEnvironmentInfo cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[19,0] > [ERROR] import org.eclipse.osgi.framework.internal.core.FrameworkProperties; > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The import org.eclipse.osgi.framework.internal.core cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[160,0] > [ERROR] String ts = FrameworkProperties.getProperty("eclipse.startTime"); //$NON-NLS-1$ > [ERROR] ^^^^^^^^^^^^^^^^^^^ > [ERROR] FrameworkProperties cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[188,0] > [ERROR] String value = FrameworkProperties.getProperty(key, "unknown"); //$NON-NLS-1$ > [ERROR] ^^^^^^^^^^^^^^^^^^^ > [ERROR] FrameworkProperties cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[208,0] > [ERROR] write("BootLoader constants: OS=" + EclipseEnvironmentInfo.getDefault().getOS()); //$NON-NLS-1$ > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] EclipseEnvironmentInfo cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[209,0] > [ERROR] write(", ARCH=" + EclipseEnvironmentInfo.getDefault().getOSArch()); //$NON-NLS-1$ > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] EclipseEnvironmentInfo cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[210,0] > [ERROR] write(", WS=" + EclipseEnvironmentInfo.getDefault().getWS()); //$NON-NLS-1$ > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] EclipseEnvironmentInfo cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[211,0] > [ERROR] writeln(", NL=" + EclipseEnvironmentInfo.getDefault().getNL()); //$NON-NLS-1$ > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] EclipseEnvironmentInfo cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[214,0] > [ERROR] writeArgs("Framework arguments: ", EclipseEnvironmentInfo.getDefault().getNonFrameworkArgs()); //$NON-NLS-1$ > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] EclipseEnvironmentInfo cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[215,0] > [ERROR] writeArgs("Command-line arguments: ", EclipseEnvironmentInfo.getDefault().getCommandLineArgs()); //$NON-NLS-1$ > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] EclipseEnvironmentInfo cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/src-fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/extensions/events/DeprecatedEclipseLog.java:[335,0] > [ERROR] FrameworkProperties.setProperty(PROP_LOGFILE, newFile == null ? "" : newFile.getAbsolutePath()); //$NON-NLS-1$ > [ERROR] ^^^^^^^^^^^^^^^^^^^ > [ERROR] FrameworkProperties cannot be resolved{code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15598) Environmental Variable API interface

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15598?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15598: ------------------------------------- Git Pull Request: https://github.com/openshift/openshift-java-client/pull/84 (was: https://github.com/openshift/openshift-java-client/pull/83) > Environmental Variable API interface > ------------------------------------ > > Key: JBIDE-15598 > URL: https://issues.jboss.org/browse/JBIDE-15598 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Martes Wigglesworth > Priority: Blocker > > API calls to OpenShift for use with the JBDS OpenShift plugin's environmental variables interface. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15667) JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15667?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15667: ----------------------------------- Workaround Description: Clean/rebuild the projects Workaround: Workaround Exists > JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import > --------------------------------------------------------------------------------- > > Key: JBIDE-15667 > URL: https://issues.jboss.org/browse/JBIDE-15667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2, upstream > Affects Versions: 4.2.0.Alpha1 > Environment: JBDS 7.1.0.Alpha2 > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: 4.2.x > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15667) JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15667?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15667: ---------------------------------------- There is some upstream problem. I can't reproduce it everytime I reimport the projects but sometimes I don't see EL validation problems. Eclipse WST validation is not invoked so Seam validator is not invoked either and it doesn't create any problems. I don't know why WST validation builder is not invoked. We need to investigate it. > JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import > --------------------------------------------------------------------------------- > > Key: JBIDE-15667 > URL: https://issues.jboss.org/browse/JBIDE-15667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2, upstream > Environment: JBDS 7.1.0.Alpha2 > Reporter: Ron Šmeral > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15667) JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15667?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15667: ----------------------------------- Affects Version/s: 4.2.0.Alpha1 > JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import > --------------------------------------------------------------------------------- > > Key: JBIDE-15667 > URL: https://issues.jboss.org/browse/JBIDE-15667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2, upstream > Affects Versions: 4.2.0.Alpha1 > Environment: JBDS 7.1.0.Alpha2 > Reporter: Ron Šmeral > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15667) JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15667?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15667: ----------------------------------- Fix Version/s: 4.2.x > JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import > --------------------------------------------------------------------------------- > > Key: JBIDE-15667 > URL: https://issues.jboss.org/browse/JBIDE-15667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2, upstream > Affects Versions: 4.2.0.Alpha1 > Environment: JBDS 7.1.0.Alpha2 > Reporter: Ron Šmeral > Fix For: 4.2.x > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15667) JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15667?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-15667: -------------------------------------- Assignee: Alexey Kazakov > JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import > --------------------------------------------------------------------------------- > > Key: JBIDE-15667 > URL: https://issues.jboss.org/browse/JBIDE-15667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2, upstream > Affects Versions: 4.2.0.Alpha1 > Environment: JBDS 7.1.0.Alpha2 > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: 4.2.x > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15667) JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15667?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15667: ----------------------------------- Component/s: upstream > JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import > --------------------------------------------------------------------------------- > > Key: JBIDE-15667 > URL: https://issues.jboss.org/browse/JBIDE-15667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2, upstream > Environment: JBDS 7.1.0.Alpha2 > Reporter: Ron Šmeral > -- 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, 6 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 October 2013