August 2014 - jbosstools-issues - Jboss List Archives

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18051?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-18051: --------------------------------------- Konstantin, please create this issue in THyM Eclipse Bugzilla https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Thym > 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-18046) Application wizard: Label for creating a server adapter is not quite correct

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18046?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-18046: --------------------------------------- PR looks good, released to master > Application wizard: Label for creating a server adapter is not quite correct > ---------------------------------------------------------------------------- > > Key: JBIDE-18046 > URL: https://issues.jboss.org/browse/JBIDE-18046 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Minor > Labels: application_wizard > Fix For: 4.2.0.CR1 > > Attachments: create_server_adapter_label.png > > > In a New application wizard on the 3rd wizard page is a check box to create a server adapter for an application. Label next to this check box is "Create and set up a server for easy publishing". I think this is not quite correct and there should be: "Create and set up a server adapter for easy publishing". > !create_server_adapter_label.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18053) Add Powermock to the target platform

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18053?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-18053: ---------------------------------- Summary: Add Powermock to the target platform (was: Add Powermockito to the target platform) > Add Powermock to the target platform > ------------------------------------ > > Key: JBIDE-18053 > URL: https://issues.jboss.org/browse/JBIDE-18053 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.x > Reporter: Jeff Cantrill > > Reason: To improving testing by allowing the stubbing of scenerios like "new File(path).exists()" which require bytecode modifications in order to accomplish. Example of intended use: https://gist.github.com/jcantrill/fd83c27d3fc542742ec7 > License and owner: Apache 2.0 / https://github.com/jayway > Original repo: https://github.com/jayway/powermock > JBoss mirror: Unknown > Sources: Unknown > Affected projects: > Include in JBDS: Yes|No > Type of dependency: testing > List of bundles added/removed: > If applicable: > non-p2 repository: > non-p2 ids: -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17808: ---------------------------------------- On this same branch, I added an installation page for Early Access. You can access it from the "About <product> > Installation Details" dialog. > Identify which installed IUs are from Early Access vs. supported/tested versions > -------------------------------------------------------------------------------- > > Key: JBIDE-17808 > URL: https://issues.jboss.org/browse/JBIDE-17808 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > [~maxandersen] brought up a good point on a call today: > we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location. > Thus we need some sort of UI to list installed IUs that are "Early Access". > This could be... (brainstorming now): > * a text file with the list of things installed from Early Access (features and plugins) > * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins > * a way to filter the plugin view (Help > About) to show only EA content (or exclude it) > * ... ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12473) Add Eclipse integration for mvn test

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12473?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-12473: ------------------------------------ Priority: Minor (was: Major) > Add Eclipse integration for mvn test > ------------------------------------ > > Key: JBIDE-12473 > URL: https://issues.jboss.org/browse/JBIDE-12473 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.0.0.Alpha2 > Reporter: Pete Muir > Assignee: Koen Aers > Priority: Minor > Fix For: 4.2.x > > > It would be really nice, if, on running > {code} > mvn clean test > {code} > This were to pop up the JUnit test result panel in Eclipse -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18020?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned JBIDE-18020: --------------------------------------- Assignee: George Gastaldi > For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Forge] > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18020 > URL: https://issues.jboss.org/browse/JBIDE-18020 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Forge]: 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 Forge 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-18053) Add Powermockito to the target platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18053?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18053: ---------------------------------------- Would https://code.google.com/p/powermock-osgi/ fit your needs? > Add Powermockito to the target platform > --------------------------------------- > > Key: JBIDE-18053 > URL: https://issues.jboss.org/browse/JBIDE-18053 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.x > Reporter: Jeff Cantrill > > Reason: To improving testing by allowing the stubbing of scenerios like "new File(path).exists()" which require bytecode modifications in order to accomplish. Example of intended use: https://gist.github.com/jcantrill/fd83c27d3fc542742ec7 > License and owner: Apache 2.0 / https://github.com/jayway > Original repo: https://github.com/jayway/powermock > JBoss mirror: Unknown > Sources: Unknown > Affected projects: > Include in JBDS: Yes|No > Type of dependency: testing > List of bundles added/removed: > If applicable: > non-p2 repository: > non-p2 ids: -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18053) Add Powermockito to the target platform

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-18053: ------------------------------------- Summary: Add Powermockito to the target platform Key: JBIDE-18053 URL: https://issues.jboss.org/browse/JBIDE-18053 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: build Affects Versions: 4.2.x Reporter: Jeff Cantrill Reason: To improving testing by allowing the stubbing of scenerios like "new File(path).exists()" which require bytecode modifications in order to accomplish. Example of intended use: https://gist.github.com/jcantrill/fd83c27d3fc542742ec7 License and owner: Apache 2.0 / https://github.com/jayway Original repo: https://github.com/jayway/powermock JBoss mirror: Unknown Sources: Unknown Affected projects: Include in JBDS: Yes|No Type of dependency: testing List of bundles added/removed: If applicable: non-p2 repository: non-p2 ids: -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

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

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ] Jiri Peterka commented on JBDS-2847: ------------------------------------ I have the same experience as Martin had. bean-discovery-all project cannot resolve many dependencies defined upstream (java-ee7-samples). And also source folders are not configured properly in Project Explorer so package names are resolved badly (The declared package "org.javaee7.jpa.jndi.context" does not match the expected package "main.java.org.javaee7.jpa.jndi.context" and similar) > 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] (JBIDE-18052) Default application name to project name

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-18052: ----------------------------------- Summary: Default application name to project name Key: JBIDE-18052 URL: https://issues.jboss.org/browse/JBIDE-18052 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Burr Sutter The application name should default to the project name http://screencast.com/t/xfyB3OZR -- 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