October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13790) Prepare fast-filter script for integration-stack-tests split

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13790?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13790: --------------------------------------- [~maxandersen], I'm trying to wrap this up. I ran the script, created the new repo here: https://github.com/mmalina/jbosstools-integration-stack-tests Andrej will verify the contents and also check with other committers. If he gives me green light, we can do the switch. Somebody will have to push this new repo to jbosstools github account. > Prepare fast-filter script for integration-stack-tests split > ------------------------------------------------------------ > > Key: JBIDE-13790 > URL: https://issues.jboss.org/browse/JBIDE-13790 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Martin Malina > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1 > > > As discussed in JBIDE-12974 and elsewhere, we need to split https://github.com/jbosstools/jbosstools-integration-tests in two: > - the current repo will contain tests for all features of JBT core > - the new repo - integration-stack-tests - will contain all soa/drools/teiid related tests > We need a fast-filter script to do the split while preserving history -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15641) Unable to change the CDI Facet from 1.0 to 1.1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15641?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15641: ------------------------------------- Wondering if, as part of the version upgrade, you shouldn't change the beans.xml schema to {noformat} <beans xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd" version="1.1" bean-discovery-mode="annotated"> {noformat} > Unable to change the CDI Facet from 1.0 to 1.1 > ---------------------------------------------- > > Key: JBIDE-15641 > URL: https://issues.jboss.org/browse/JBIDE-15641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.2.0.Alpha1 > Reporter: Fred Bricon > Assignee: Alexey Kazakov > Fix For: 4.2.0.Alpha1 > > > - Create a CDI project with Facet 1.0 > - Right-click on project > Properties > Project Facets > - change the CDI version to 1.1 > => "Cannot change version of project facet CDI (...) to 1.1" > No indications whatsoever of why you can't change it. Constraints seem ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15597) Environmental Variables UI

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15597: --------------------------------------------- Just my 2 cents : it just needs to show that some number of variables are defined so when users uses next/back does not have to click around on the wizard to know if they actually did fill out the right stuff and not having to click on several buttons to see so. > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-twochoices-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15428) No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15428?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-15428: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) Max, please review the PR ;-) > No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15428 > URL: https://issues.jboss.org/browse/JBIDE-15428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Radoslav Rábara > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > Attachments: After import.png, After workaround.png, Before import.png > > > After importing Dynamic Web Project with JAX-RS support with HTTPMethod annotation without @Target and @Retention annotations, there is no error. > This looks like a regression of JBIDE-12690. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13637) 'Go to Selection' command throws error

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13637?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13637. ------------------------------- Fix Version/s: (was: 4.1.x) Resolution: Cannot Reproduce Bug > 'Go to Selection' command throws error > -------------------------------------- > > Key: JBIDE-13637 > URL: https://issues.jboss.org/browse/JBIDE-13637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Pavol Srna > Assignee: Koen Aers > > When clicked on 'Go to Selection' button in Forge view the selected resource in Project Explorer should be picked-up in forge console. But what I get is: ***ERROR*** No such command. This happens only when using the command for the first time, all the following attempts to use that command are working. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13637) 'Go to Selection' command throws error

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13637?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-13637: ------------------------------------ Hi Koen, me neither, tried with the latest 4.1.0 Alpha milestone. Feel free to resolve. I'll reopen in case I hit the issue again. > 'Go to Selection' command throws error > -------------------------------------- > > Key: JBIDE-13637 > URL: https://issues.jboss.org/browse/JBIDE-13637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.x > > > When clicked on 'Go to Selection' button in Forge view the selected resource in Project Explorer should be picked-up in forge console. But what I get is: ***ERROR*** No such command. This happens only when using the command for the first time, all the following attempts to use that command are working. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-402) Write Release Notes document for JBDS 7.1.0.Beta1

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-402?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-402: ------------------------------------------ Generated a skeleton doc in CCMS but still need to populate new features, fixed and known issues. Also, should it refer to 7.1.0.Beta rather than simply 7.1.0? Something to think on. > Write Release Notes document for JBDS 7.1.0.Beta1 > ------------------------------------------------- > > Key: TOOLSDOC-402 > URL: https://issues.jboss.org/browse/TOOLSDOC-402 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Release Notes > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > > Things to document: > * EAP 6.1.1 available in bundled universal installer (TOOLSDOC-393) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15574) Wildfly management plugin getting unsupported class version unit test errors

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15574?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15574: ------------------------------------- This bug has been opened on the xnio side: https://issues.jboss.org/browse/XNIO-207 seems the compiler was being clever. We'll need to update dependencies to xnio 3.1.0.CR8, but I'm going to wait a day or two for some builds to be done on the xnio side before pushing the change. Making our tests and management plugin use 3.1.0.CR8 when it's unreleased is essentially using fast-changing code that is likely to break, but, on the other hand, leaving the plugins as they are now (after my recent commit) does not fully fix the issue, so I think it's appropriate to use the cr8 once a build of it is done. > Wildfly management plugin getting unsupported class version unit test errors > ---------------------------------------------------------------------------- > > Key: JBIDE-15574 > URL: https://issues.jboss.org/browse/JBIDE-15574 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > This should be fixed in wildfly beta. There is nothing that tools can do to fix this. The relevant server jars need to rebuilt with a lower class version. > https://issues.jboss.org/browse/WFLY-2072 > We will switch our unit tests to beta1 as soon as it is available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-393) Document bundled JBDS + EAP installer

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-393?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-393. -------------------------------------- Resolution: Done > Document bundled JBDS + EAP installer > ------------------------------------- > > Key: TOOLSDOC-393 > URL: https://issues.jboss.org/browse/TOOLSDOC-393 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.1.1 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > Original Estimate: 1 hour, 15 minutes > Time Spent: 1 hour, 55 minutes > Remaining Estimate: 0 minutes > > Description: adding the latest version of EAP (6.1.1 unless something newer comes along) to the bundled JBDS + EAP universal installer > Impact: > * Add RN about update to EAP version in bundled JBDS + EAP installer > * Installation Guide = > ** 3.1 Install Options - add info about availability of bundled JBDS + EAP universal installer > ** 3.2 Install JBoss Developer Studio - add info and note specifying what the bundled version provides, where to download and any additional step to get the bundles EAP installed > * [Getting Started Guide = update TicketMonster assumptions, so don't have to have EAP already installed and work through bundled installer?] > Estimate: write RN item + modify 2 sections = 1.25hr -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-402) Write Release Notes document for JBDS 7.1.0.Beta1

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-402?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-402: ------------------------------------- Description: Things to document: * EAP 6.1.1 available in bundled universal installer (TOOLSDOC-393) > Write Release Notes document for JBDS 7.1.0.Beta1 > ------------------------------------------------- > > Key: TOOLSDOC-402 > URL: https://issues.jboss.org/browse/TOOLSDOC-402 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Release Notes > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > > Things to document: > * EAP 6.1.1 available in bundled universal installer (TOOLSDOC-393) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 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 October 2013