September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16145) All wizards: Consider replacing "*"-decoration for for fields that require input

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16145?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16145: ------------------------------------- Summary: All wizards: Consider replacing "*"-decoration for for fields that require input (was: OpenShift Tools: info i icon missing from New OpenShift App wizard) > All wizards: Consider replacing "*"-decoration for for fields that require input > -------------------------------------------------------------------------------- > > Key: JBIDE-16145 > URL: https://issues.jboss.org/browse/JBIDE-16145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Fix For: 4.2.x > > Attachments: OpenShift_newapp.png > > > In New OpenShift Application wizard, the following have * (asterisk) at the beginning: > * use existing application check box > * name field > * type field > This should be the (i) icon (blue i in a circle) like in Window>Install New Software wizard. > There maybe more in the wizard but I haven't got past the first page. > !OpenShift_newapp.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16146) Application wizard: tooltips aren't useful (wrong or uninformative)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16146?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16146: ------------------------------------- Fix Version/s: 4.2.0.CR2 (was: 4.2.x) Estimated Difficulty: Low > Application wizard: tooltips aren't useful (wrong or uninformative) > ------------------------------------------------------------------- > > Key: JBIDE-16146 > URL: https://issues.jboss.org/browse/JBIDE-16146 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Priority: Minor > Labels: application_wizard > Fix For: 4.2.0.CR2 > > > In New OpenShift Application wizard, the following tooltips have the same text 'Create a new OpenShift application.': > * use existing application check box > * type field > The text should be made appropriate for the fields or the tooltips removed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15978) Properties view: URL for embedded cartridges is empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15978?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15978: ------------------------------------- Fix Version/s: 4.2.0.CR2 (was: 4.2.x) > Properties view: URL for embedded cartridges is empty > ----------------------------------------------------- > > Key: JBIDE-15978 > URL: https://issues.jboss.org/browse/JBIDE-15978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Fix For: 4.2.0.CR2 > > Attachments: empty-url-property.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18086) CordovaSim: Can't find config.xml in the root of the app

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18086?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18086. ------------------------------- Verified with JBDS 8.0.0.CR1-v20140831-0335-B201 > CordovaSim: Can't find config.xml in the root of the app > --------------------------------------------------------- > > Key: JBIDE-18086 > URL: https://issues.jboss.org/browse/JBIDE-18086 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Beta3 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.CR1 > > Attachments: config.png > > > CordovaSim can't find config.xml in the root of the app -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18223) Forge context should be set to the 'new project location' after 'project-new' command

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18223?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18223: --------------------------------------------- where/how ? not following what you mean here ? > Forge context should be set to the 'new project location' after 'project-new' command > ------------------------------------------------------------------------------------- > > Key: JBIDE-18223 > URL: https://issues.jboss.org/browse/JBIDE-18223 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Labels: respin-a > Fix For: 4.2.0.CR1 > > > Forge context should be set to the 'new project location' after project-new command execution. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18002) Changes to files in nested utility project need not always restart module

by Patrick Decat (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18002?page=com.atlassian.jira.plugi... ] Patrick Decat commented on JBIDE-18002: --------------------------------------- Fix confirmed in latest nightly builds. > Changes to files in nested utility project need not always restart module > ------------------------------------------------------------------------- > > Key: JBIDE-18002 > URL: https://issues.jboss.org/browse/JBIDE-18002 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: affects_documentation > Fix For: 4.2.0.CR1 > > Attachments: JBIDE-18002.png > > > Changes to a .class file inside a nested utility project currently marks the module as requiring a restart, because the application server won't pick up those changes without a restart. > When running in debug mode, though, the debugger will use the new classes as changed in the workspace, so a restart of a module is slow and costly. > The fix (for now) would be to only restart the web module if the publish is a full publish, or, if the nested archive's deployment name matches the strings in the server editor's restart-module regex clause. > Example project replicating the bug can be found at https://github.com/maxandersen/JBIDE-17724 > Unzip the attached project structure (stripped down from an existing project) > Run 'mvn clean install eclipse:clean eclipse:eclipse' at the root > Import existing projects into eclipse luna with JBoss Tools > Deploy to a "JBoss Enterprise Application Platform 5.x" runtime > Make a change to MyController.java inside the project-war webapp => the change is hot deployed > Make a change to MySecondController.java inside the project-module dependency => the full WAR is undeployed then redeployed -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2917) Improve how teams work and import projects. Developers rarely work alone :)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2917?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen resolved JBDS-2917. --------------------------------------- Resolution: Duplicate Issue > Improve how teams work and import projects. Developers rarely work alone :) > --------------------------------------------------------------------------- > > Key: JBDS-2917 > URL: https://issues.jboss.org/browse/JBDS-2917 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 8.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2917) Improve how teams work and import projects. Developers rarely work alone :)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2917?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2917: ------------------------------------------- not sure what happened with this jira - seemed it was migrated/duplicated to JBDS-2851 as epic but this was left behind. Anwyays - killing it with link . > Improve how teams work and import projects. Developers rarely work alone :) > --------------------------------------------------------------------------- > > Key: JBDS-2917 > URL: https://issues.jboss.org/browse/JBDS-2917 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 8.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18010?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-18010. ----------------------------------------- Resolution: Partially Completed central got its patch included. rest done if PR available, rest skipped for now. > For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-18010 > URL: https://issues.jboss.org/browse/JBIDE-18010 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1: 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...] > See also: JBDS-3114 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16444) Connection wizard: save accepted certificates in the Eclipse preferences and allow users to inspect/revoke them

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16444?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16444: ------------------------------------- Estimated Difficulty: Medium > Connection wizard: save accepted certificates in the Eclipse preferences and allow users to inspect/revoke them > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16444 > URL: https://issues.jboss.org/browse/JBIDE-16444 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.2.x > > Attachments: accept-certificate.png > > > In JBIDE-14768 we introduced a dialog that allows users to accept/refuse untrusted SSL certificates. > !accept-certificate.png! > The authorization is currently stored for the current Eclipse session. We should store those authorizations in the Eclipse preferences and add a preferences page which shows these and allows users to revoke the given authorizations. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 September 2014