August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-2847: ------------------------------------- I forgot to comment here: I tried this based on Xavier's instructions and started with cdi/bean-discovery-all. For me, it doesn't work. I didn't have any modules checked in the Projects Facets settings. And after the first import and eclipse restart, I always had around 30 errors because the build path was wrong - Eclipse was assuming that src/ is the source path, not src/test/java etc. And since Xavier ran out of ideas to fix my problems, I asked [~jpeterka] to try this on his system. > Java EE 7 Tech Preview > ---------------------- > > Key: JBDS-2847 > URL: https://issues.jboss.org/browse/JBDS-2847 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Burr Sutter > Assignee: Xavier Coulon > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.CR1 > > > Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly > https://github.com/javaee-samples/javaee7-samples > They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-507) https://ticketmonster-jdf.rhcloud.com/ not accessible

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-507?page=com.atlassian.jira.plug... ] Vineet Reynolds resolved TOOLSDOC-507. -------------------------------------- Resolution: Done I've just restarted this. Let me know if you run into this again - there is a memory leak that I've been chasing and I don't think this can be resolved through a code fix in TicketMonster. > https://ticketmonster-jdf.rhcloud.com/ not accessible > ----------------------------------------------------- > > Key: TOOLSDOC-507 > URL: https://issues.jboss.org/browse/TOOLSDOC-507 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Affects Versions: 4.1.1 > Environment: Build Name: 22437, Getting Started Guide-7.1 > Build Date: 11-12-2013 15:10:35 > Topic ID: 13792-564146 [Latest] > Reporter: Christian Damand > Assignee: Vineet Reynolds > Priority: Critical > > Title: About the TicketMonster Application > Describe the issue: > Suggestions for improvement: > Additional information: -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18011) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Aerogear]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18011?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18011: -------------------------------------- Just to confirm what is expected in order to resolve this issue (1) revert the commit(s) that fix this issue (2) send a PR that includes those commit(s) (3) get verification for them from someone. [~nickboldt1] can you confirm the steps and also the verifier. > For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Aerogear] > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18011 > URL: https://issues.jboss.org/browse/JBIDE-18011 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Aerogear]: Please perform the following *2* tasks: > 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below. > Be sure to also include *translated* files, where they exist. > *java files* > {code:title=*.java} > Copyright (c) 2010-2014 Red Hat, Inc. and others. > {code} > *html files* > {code:title=about.html} > © 2014 Red Hat, Inc. All rights reserved > {code} > *properties files* > {code:title=about.properties} > Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved > {code} > {code:title=about_fr.properties} > Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s. > {code} > {code:title=feature.properties} > Copyright (c) 2010-2014 Red Hat, Inc. and others. > {code} > {code:title=Messages.properties} > # Copyright (c) 2014 Red Hat, Inc. and others. > {code} > *xsd files* > {code:title=jboss-as-naming_1_3.xsd} > Copyright 2014, Red Hat, Inc., and individual contributors > {code} > 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*. > Be sure to also include *translated* files, where they exist. > *This step is particularly important for new plugins and features that have been added recently.* > Depending on how your plugin is configured you should see something like this in your *plugin.properties* files: > {code}BundleName = JMX Resources Bundle > BundleProvider = JBoss by Red Hat{code} > or > {code}Bundle-Name.0 = JBossTools Archives Core Plugin > Bundle-Vendor.0 = JBoss by Red Hat{code} > Then in your MANIFEST.MF files, you will reference these variables like this. > *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file! > {code}Bundle-Localization: plugin > Bundle-Name: %BundleName > Bundle-Vendor: %BundleProvider{code} > or > {code}Bundle-Localization: plugin > Bundle-Name: %Bundle-Name.0 > Bundle-Vendor: %Bundle-Vendor.0{code} > For features, check that your *feature.properties* file contains good values too: > {code}featureName=JMX Console > featureProvider=JBoss by Red Hat{code} > or > {code}featureName=JBoss Archives Tools > providerName=JBoss by Red Hat{code} > Then in your feature.xml files, you will reference these variables like this: > {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code} > or > {code}<feature label="%featureName" provider-name="%providerName" ...>{code} > 3. If you would like QE to review your changes, please *Resolve* this JIRA when done. > 4. If you do not require QE to review your changes, please *Close* this JIRA when done. > 5. If you have any questions, please contact [~nickboldt]. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17309) Move JVMMonitor to jbosstools-server/jmx repo

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17309?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17309. --------------------------------- > Move JVMMonitor to jbosstools-server/jmx repo > --------------------------------------------- > > Key: JBIDE-17309 > URL: https://issues.jboss.org/browse/JBIDE-17309 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jmx > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta2 > > > The first step to enabling profiling for local servers and unifying the views is to get jvm-monitor into the jmx repo. This is a pre-requisite in order to unify the top-level nodes and API of the JMX Explorer. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17694) Update TP/Installer with m2eclipse-egit 0.14.0.201406241643

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17694?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17694. --------------------------------- > Update TP/Installer with m2eclipse-egit 0.14.0.201406241643 > ----------------------------------------------------------- > > Key: JBIDE-17694 > URL: https://issues.jboss.org/browse/JBIDE-17694 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Fred Bricon > Assignee: Mickael Istria > Fix For: 4.2.0.Beta3 > > > *Reason:* > JBIDE-17446 requires the latest version of m2eclipse-egit, available from http://central.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0... > *License and owner:* > EPL, Sonatype > *Original repo:* > http://central.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0... > *JBoss mirror:* > http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-egit/... > *Sources:* > Not included. But source repo at https://github.com/tesla/m2eclipse-egit > *Affected projects:* > JBoss Central > *Include in JBDS:* > Yes (already done) > *Type of dependency:* > distribution. Added to the TP but not categorized. > *List of bundles added/removed:* > org.sonatype.m2e.egit.feature -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18050) CordovaSim: Ionic Keyboard plugin is not supported

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18050?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18050: -------------------------------- Assignee: Gorkem Ercan (was: Ilya Buziuk) > CordovaSim: Ionic Keyboard plugin is not supported > -------------------------------------------------- > > Key: JBIDE-18050 > URL: https://issues.jboss.org/browse/JBIDE-18050 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Gorkem Ercan > Fix For: 4.2.0.CR1 > > > Ionic keyboard plugin https://github.com/driftyco/ionic-plugins-keyboard is not supported -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17938) No local processes in JMX Navigator when Eclipse is run with java 7

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17938?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17938. --------------------------------- Resolution: Done This has been fixed. Error messages have been updated as well. > No local processes in JMX Navigator when Eclipse is run with java 7 > ------------------------------------------------------------------- > > Key: JBIDE-17938 > URL: https://issues.jboss.org/browse/JBIDE-17938 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3b B193 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > When I install and run JBDS with java 7, there are no local processes shown in the JMX navigator. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18051) Aerogear: Could not add plugin from platform properties

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18051?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-18051: ------------------------------------------------ But I see plugin added to config.xml, but config file is not saved. When I try to save it I get Update Conflict which asks me to overwrite file in the file system. After overwriting plugin appears in Platform properties > Aerogear: Could not add plugin from platform properties > ------------------------------------------------------- > > Key: JBIDE-18051 > URL: https://issues.jboss.org/browse/JBIDE-18051 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta3 > Reporter: Konstantin Marmalyukov > Assignee: Gorkem Ercan > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18051) Aerogear: Could not add plugin from platform properties

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-18051: ---------------------------------------------- Summary: Aerogear: Could not add plugin from platform properties Key: JBIDE-18051 URL: https://issues.jboss.org/browse/JBIDE-18051 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.2.0.Beta3 Reporter: Konstantin Marmalyukov Assignee: Gorkem Ercan -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18050) CordovaSim: Ionic Keyboard plugin is not supported

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18050?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18050: ------------------------------------- I do believe the same trick should be done as for JBIDE-17581 (mocking plugin's API) > CordovaSim: Ionic Keyboard plugin is not supported > -------------------------------------------------- > > Key: JBIDE-18050 > URL: https://issues.jboss.org/browse/JBIDE-18050 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.CR1 > > > Ionic keyboard plugin https://github.com/driftyco/ionic-plugins-keyboard is not supported -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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 August 2014