April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19602) "Warning: NLS unused message" in org.jboss.tools.common.jdt.debug

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19602?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19602. --------------------------------- Fix Version/s: 4.3.0.Beta1 Resolution: Done Cleaned up the rogue strings. > "Warning: NLS unused message" in org.jboss.tools.common.jdt.debug > ----------------------------------------------------------------- > > Key: JBIDE-19602 > URL: https://issues.jboss.org/browse/JBIDE-19602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > {code}Warning: NLS unused message: updatePeriodNotEnteredMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: illegalUpdatePeriodMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: updatePeriodOutOfRangeMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: loadAgentFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: agentJarNotFoundMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: agentJarFoundMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: corePluginNoFoundMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: charsetNotSupportedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: readInputStreamFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: updateTimerCanceledMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: getMonitoredJvmFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: getLocalConnectorAddressFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: connectTargetJvmFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: fileNotFoundMsg in: org.jboss.tools.common.jdt.debug.messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18570) Creating EJB 3.x bean is asking EJB 2.x values

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18570?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-18570. --------------------------------- Resolution: Won't Fix I've misidentified the cause here. These are actually the WTP wizards, not our JBT wizards which have already been removed. The section is an optional dropdown. It is clearly labeled EJB 2.x and is designed in such a way to be minimally intrusive. We won't be fixing this. > Creating EJB 3.x bean is asking EJB 2.x values > ---------------------------------------------- > > Key: JBIDE-18570 > URL: https://issues.jboss.org/browse/JBIDE-18570 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: ejb3, upstream > Reporter: Arun Gupta > Assignee: Rob Stryker > Fix For: 4.3.x > > Attachments: Screen Shot 2014-10-09 at 9.41.39 pm.png > > > Creating a singleton EJB using 3.x wizard and its asking for home and component interfaces from 2.x. This is confusing and redundant. > Image coming in attachment next. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ {quote}Why do we need to override these things - can't those few ones be customized to have that set properly ?{quote} You say "customized" I say "overridden". Same thing - in either case there's a default in parent pom, and a new value in the special root poms that need something else. Like we do for jbdevstudio-product/pom.xml, for example. {quote}About copy-or-rename stuff, we do we even have such step ? why don't we actually produce what we want/need ? {quote} Yes. Please re-read all the links to example I provided above, 4 days ago. https://issues.jboss.org/browse/JBIDE-18772?focusedCommentId=13061673&pag... > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19049. --------------------------------- Fix Version/s: 4.3.0.Beta1 (was: LATER) Resolution: Done To properly run a wf 8.x server using Java9: 1) Open server wizard 2) Create new server 3) Select new runtime 4) Note that java9 comes up in the list now. 5) Note that selecting the Java9 JRE / JDK will also show a warning about compatibility 6) Complete creating your server 7) Open the server editor 8) Open the launch configuration 9) Remove the flags for -XX:MaxPermSize from the VM Args 10) Save the launch config 11) Start the server. Everything works. woohoo. > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-15884: ------------------------------------- Pushed to master. Steps to verify: - BrowserSim command (with and without *url* parameter - @see comment above) must work with cheat sheets on every perspective > Allow the runBrowserSim command to accept a URL as a parameter > -------------------------------------------------------------- > > Key: JBIDE-15884 > URL: https://issues.jboss.org/browse/JBIDE-15884 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Vineet Reynolds > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected. > When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19715: ---------------------------------------- Branding and references are part of the generate-repository-facade mojo, which is not related to fullSite. The create-full-site mojo doesn't produce anything that isn't in the buildinfo.json. I'd be in favour of getting rid of it, and put metadata and zips directly in the repository/ folder, instead of maintaining an overhead hierarchy besides of the repostory.. I checked Mojos and scripts and the only references to fullSite are only in unused or useless mojos, and in comments in rsync.sh. It seems to be used only in CI job configuration, where we could publish repository/ as easily. > Get rid of "fullSite", stick with "repository" > ---------------------------------------------- > > Key: JBIDE-19715 > URL: https://issues.jboss.org/browse/JBIDE-19715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > > Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3423) JBDS update site has blue JBT branding instead of red JBDS branding

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3423?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3423: -------------------------------------- Actually, it's not the create-full-site mojo which generates the index.html, but the generate-repository-facade mojo, which can be customized to use other index.html and CSS resource remplate. The create-full-site mojo doesn't produce anything that isn't in the buildinfo.json. I'd be in favour of getting rid of it, and put metadata directly in the repository/ folder, instead of maintaining an overhead hierarchy besides of the repostory. > JBDS update site has blue JBT branding instead of red JBDS branding > ------------------------------------------------------------------- > > Key: JBDS-3423 > URL: https://issues.jboss.org/browse/JBDS-3423 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 9.0.0.Beta1 > > > Comparing these sites: > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma... (published w/ publish.sh) > https://devstudio.redhat.com/9.0/snapshots/updates/core/master/ (published w/ rsync.sh) > We see that some time after build 3003, the branding for the site was lost. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19681) OpenShift New and Noteworthy for 4.3.0.Alpha2

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19681?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19681. ------------------------------------ > OpenShift New and Noteworthy for 4.3.0.Alpha2 > --------------------------------------------- > > Key: JBIDE-19681 > URL: https://issues.jboss.org/browse/JBIDE-19681 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-429) JBDSIS 8.0.2 component updates

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-429?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-429: ---------------------------------- Hey [~bfitzpat] - I've got what I need to spin an initial JBTIS 4.2.2. Do you think you'll have a SwitchYard update soon? > JBDSIS 8.0.2 component updates > ------------------------------ > > Key: JBTIS-429 > URL: https://issues.jboss.org/browse/JBTIS-429 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.2.GA > > > Update components for JBDSIS 8.0.2/ JBTIS 4.2.2 (Luna). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19679) Forge New and Noteworthy for 4.3.0.Alpha2

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19679?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19679. ------------------------------ Verified. > Forge New and Noteworthy for 4.3.0.Alpha2 > ----------------------------------------- > > Key: JBIDE-19679 > URL: https://issues.jboss.org/browse/JBIDE-19679 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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