June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19791) Switch OpenShift plugins to require JDK7

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19791?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-19791. --------------------------------- Verified. > Switch OpenShift plugins to require JDK7 > ---------------------------------------- > > Key: JBIDE-19791 > URL: https://issues.jboss.org/browse/JBIDE-19791 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > With the switch to the new 4.50.0.Beta1-SNAPSHOT target platform (which is using Mars M7) OpenShift (especially the egit based parts) now require jdk7 to cleanly compilein Eclipse. Compilation error faced are references to java.land.AutoCloseable which was introduced in jdk7. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19712) Application wizard: Add create from template details pane

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19712?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-19712. --------------------------------- Verified in JBDS 9.0.0.Beta1 build ID B34. > Application wizard: Add create from template details pane > --------------------------------------------------------- > > Key: JBIDE-19712 > URL: https://issues.jboss.org/browse/JBIDE-19712 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > > Add details pane similiar to v2 where you get template details when you select an individual template. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17620) Explorer: "New" submenu is missing or misplaced

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17620?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-17620. ----------------------------------- Resolution: Duplicate Issue Resolving as duplicated issue. > Explorer: "New" submenu is missing or misplaced > ----------------------------------------------- > > Key: JBIDE-17620 > URL: https://issues.jboss.org/browse/JBIDE-17620 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: gtk3, upstream > Fix For: 4.3.0.Beta1 > > Attachments: missing-new-submenu.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17620) Explorer: "New" submenu is missing or misplaced

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17620?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-17620. --------------------------------- And closing. > Explorer: "New" submenu is missing or misplaced > ----------------------------------------------- > > Key: JBIDE-17620 > URL: https://issues.jboss.org/browse/JBIDE-17620 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: gtk3, upstream > Fix For: 4.3.0.Beta1 > > Attachments: missing-new-submenu.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20017) Edited v2 connection contains wrong server URL label

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20017?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-20017: ---------------------------------- Description: If I edit existing v2 connection and I change also server URL, then the connection use this new URL and also credentials, but in OpenShift Explorer view is still shown the old value for server URL. E.g I had connection to console.itos.redhat.com and I edited connection to use server openshift.redhat.com and with correct credentials, connection has changed but item in explorer view was still labeled with console.itos.redhat.com URL. Also properties for a connection show the wrong URL. was: If I edit existing v2 connection and I change also server URL, then the connection use this new URL and also credentials, but in OpenShift Explorer view is still shown the old value for server URL. E.g I had connection to console.itos.redhat.com and I editted connection to use server openshift.redhat.com and with correct credentials, connection has changed but item in explorer view was still labeled with console.itos.redhat.com URL. Also properties for a connection show the wrong URL. > Edited v2 connection contains wrong server URL label > ---------------------------------------------------- > > Key: JBIDE-20017 > URL: https://issues.jboss.org/browse/JBIDE-20017 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Critical > > If I edit existing v2 connection and I change also server URL, then the connection use this new URL and also credentials, but in OpenShift Explorer view is still shown the old value for server URL. E.g I had connection to console.itos.redhat.com and I edited connection to use server openshift.redhat.com and with correct credentials, connection has changed but item in explorer view was still labeled with console.itos.redhat.com URL. > Also properties for a connection show the wrong URL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20017) Edited v2 connection contains wrong server URL label

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-20017: ------------------------------------- Summary: Edited v2 connection contains wrong server URL label Key: JBIDE-20017 URL: https://issues.jboss.org/browse/JBIDE-20017 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Marián Labuda Priority: Critical If I edit existing v2 connection and I change also server URL, then the connection use this new URL and also credentials, but in OpenShift Explorer view is still shown the old value for server URL. E.g I had connection to console.itos.redhat.com and I editted connection to use server openshift.redhat.com and with correct credentials, connection has changed but item in explorer view was still labeled with console.itos.redhat.com URL. Also properties for a connection show the wrong URL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19457) implement wtp servertools integration with "launchbar"

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19457?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19457. --------------------------------- Closing. But JBIDE-19711 still needs to be verified. (I haven't tested launchbar yet.) > implement wtp servertools integration with "launchbar" > ------------------------------------------------------- > > Key: JBIDE-19457 > URL: https://issues.jboss.org/browse/JBIDE-19457 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > The launchbar is a new concept introduced in CDT (with no cdt deps) that allows for a more extensible and faster launching experience. > This should integrate with the run as -> Run on server APIs to enhance synnergy and other cool buzzwords. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19049. --------------------------------- Verified in JBDS 9.0.0.Beta1 B34. It would be nice though if we could automatically remove the max perm size argument from the launch config in the future. > Enable JBoss servers to run with java 9 > --------------------------------------- > > Key: JBIDE-19049 > URL: https://issues.jboss.org/browse/JBIDE-19049 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: Java9 > Fix For: 4.3.0.Beta1 > > > I briefly tried to use java 9 for our tooling and to run servers. > I downloaded it from here: > https://jdk9.java.net/download/ > {code} > nattura:8.0.2 rasp$ java -version > java version "1.9.0-ea" > Java(TM) SE Runtime Environment (build 1.9.0-ea-b45) > Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode) > {code} > I use OS X 10.10 Yosemite. > There are a couple of problems: > 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that. > 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all. > {code} > nattura:bin rasp$ ./standalone.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final > JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > Unrecognized VM option 'MaxPermSize=256m' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {code} > Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18377) Automatically add the dependencies specified in jboss-deployment-structure.xml to build path

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18377?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18377: --------------------------------------- [~rob.stryker], could you help me verify this? The example in this JIRA specifies custom modules that are not in the server by default. Perhaps you know some easy way to try this? Your help would be much appreciated! > Automatically add the dependencies specified in jboss-deployment-structure.xml to build path > -------------------------------------------------------------------------------------------- > > Key: JBIDE-18377 > URL: https://issues.jboss.org/browse/JBIDE-18377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > I am deploying a dynamic web project to EAP 6 using JBDS 6+. My project's build path includes the JRE System Library, EAP 6 Runtime, and Web App Libraries (the WEB-INF/lib folder). I also have a jboss-deployment-structure.xml file that defines additional module dependencies such as the following: > <jboss-deployment-structure> > <deployment> > <dependencies> > <module name="org.slf4j" /> > <module name="org.apache.log4j" /> > </dependencies> > </deployment> > </jboss-deployment-structure> > The problem is, the slf4j and log4j modules are not included in the project's build path. While the server resolves them correctly at runtime because of the jboss-deployment-structure.xml file, Eclipse doesn't include them. So the following declaration in the Java code would result in a build error because org.apache.log4j cannot be resolved to a type: > private static final org.apache.log4j.Logger log = org.apache.log4j.Logger.getLogger(Example.class); > Please note that the project has configured correctly the JBoss Server Runtime which points to a valid JBoss directory, and the module dependencies are properly installed in the server. > The dependencies specified in the jboss-deployment-structure.xml are some private modules installed at the server side but not included in the server runtime by default. > So, is there a way to automatically add the jboss-deployment-structure module dependencies to the Eclipse build path? So far, I've been unable to find a way to do this. > I have found a few workarounds, but none of them are ideal, and they seem to completely miss the point of module-based dependencies: > - Customize the Default Classpath Entries for the server runtime. This is not acceptable because it must be done in each developer's workspace – and possibly per project since projects may have different, conflicting dependencies. > - Add the libraries to WEB-INF/lib. This is not acceptable because it defeats the purpose of server modules. > - Add the libraries to a user library for the project. This could work, but it's very inconvenient, because each developer on the team would have to add the jars to the user libraries in their workspaces. > Here can find the discussion of exact same issue https://developer.jboss.org/thread/203309?tstart=0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19879) Add o.e.remote and o.e.launchbar to TP

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19879?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19879. --------------------------------- Both launchbar and org.eclipse.remote are available from here: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... So closing. I suppose potential updates will be handled elsewhere. > Add o.e.remote and o.e.launchbar to TP > -------------------------------------- > > Key: JBIDE-19879 > URL: https://issues.jboss.org/browse/JBIDE-19879 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, target-platform > Affects Versions: 4.3.0.Beta2 > Reporter: Rob Stryker > Assignee: Nick Boldt > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > *Reason:* JBIDE-19711 - WTP servertools integration with CDT launchbar > *Project page/sources:* ... Requires dependencies on CDT and Launchbar. Launchbar is in http://www.eclipse.org/cdt/ and o.e.remote is in http://www.eclipse.org/ptp/ > *Version:* - Required launchbar is 1.0.0 found in MASTER at their repository. There is no released version yet with the stable API required. Required o.e.remote version is 2.0.0 in MASTER at their repository. There is no released version yet with the stable API required. > *License and owner:* ... Both are eclipse projects licensed under EPL > *Original p2 repo:* I am unable to locate the original update sites / p2 repos. PTP does not seem to have an update site URL to the best of my searching (http://download.eclipse.org/tools/ptp/builds/9.0.0/ does not list an update site url, but does have a zip containing an update site). CDT does not list update sites for mars at https://eclipse.org/cdt/downloads.php > *JBoss mirror:* - Not sure what's applicable here. http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... does have all plugins needed, but none are the API required, as we require the code from Master. > *Include Sources: - It's always nice to include sources for devs who build tp locally with the fetch-sources flag ;) > *Affected projects: - jbosstools-server > *Include in JBDS:* - No, for now. > *Type of dependency:* distribution > *List of bundles added/removed:* - At this time, I expect to require org.eclipse.launchbar.core, org.eclipse.launchbar.ui, org.eclipse.remote.core, org.eclipse.remote.ui. > Unfortunately I'm unable to test if this is sufficient, at the moment. There may be other plugins that are transient deps somehow that I'm not seeing since I don't have a TP to build against that works. > If applicable: > *non-p2 repository:* ??? > *non-p2 ids:* ??? > Suggested Patch for TP: - At this point, I have no suggested patch. I do not know how to add a dependency on nightly builds for these two blocks of code. Also, I'm a bit confused why http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... will list a plugin (for example org.eclipse.cdt.core.native_5.8.0.201505050312.jar) but the .target file references a feature group (?) which is not present in the requirements/mars folder, such as <unit id="org.eclipse.cdt.native.feature.group" version="8.7.0.201505050312"/> > I'm also a bit confused where you're pulling the feature group name / id from, or its version, as the version of the feature group does not seem to match the version of the plugin. Furthermore, the mars repo mentioned above does not seem to include any file matching the string org.eclipse.cdt.native.feature.group > So I'm not sure how you're converting a required plugin id to a feature group. The devdoc also provides no assistance in this matter. -- 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