April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3529) For JBDS 10.0.0.Alpha1: Prepare for future Alpha1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3529?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3529. ---------------------------- Resolution: Done > For JBDS 10.0.0.Alpha1: Prepare for future Alpha1 > ------------------------------------------------- > > Key: JBDS-3529 > URL: https://issues.jboss.org/browse/JBDS-3529 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 10.0.0.Alpha1 > > > For JBDS 10.0.0.Alpha1: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3529) For JBDS 10.0.0.Alpha1: Prepare for future Alpha1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3529?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3529: ----------------------------- Story Points: 1 Sprint: devex #6 April 2016 > For JBDS 10.0.0.Alpha1: Prepare for future Alpha1 > ------------------------------------------------- > > Key: JBDS-3529 > URL: https://issues.jboss.org/browse/JBDS-3529 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 10.0.0.Alpha1 > > > For JBDS 10.0.0.Alpha1: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21118) Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21118?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21118: ------------------------------- Story Points: 2 Sprint: devex #7 May 2017 > Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21118 > URL: https://issues.jboss.org/browse/JBIDE-21118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 > {quote} > So, we need a new version of m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.60.x TPs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21118) Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21118?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21118: ------------------------------------ [~fbricon] Does http://download.eclipse.org/technology/m2e/milestones/1.7/1.7.0.20160321-... include a fix for this? > Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21118 > URL: https://issues.jboss.org/browse/JBIDE-21118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 > {quote} > So, we need a new version of m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.60.x TPs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22174) Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22174?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22174: -------------------------------- Sprint: devex #6 April 2016 > Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22174 > URL: https://issues.jboss.org/browse/JBIDE-22174 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > When opening Deploy Image to OpenShift wizard via context menu of a docker image in Docker Explorer, selected project (or a connection if no project under a connection is selected) should be selected in combo in the wizard. At the moment, if there is precisely 1 connection, it is selected (if there are more connections, no connection is selected and following steps is not reachable) and if there is precisely 1 project, that one is selected (if there are more projects, no project is selected). This could be refined a bit. In case of selection would be the selected one in combo. In case of existence of more connections/projects and no selection, maybe the first one listed could be selected (but this is probably personal preference, maybe it is not a good idea). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22157) On deployoment, utility JAR projects are being exploded on WEB-INF/LIB

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22157: -------------------------------- Sprint: devex #6 April 2016 > On deployoment, utility JAR projects are being exploded on WEB-INF/LIB > ---------------------------------------------------------------------- > > Key: JBIDE-22157 > URL: https://issues.jboss.org/browse/JBIDE-22157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Eclipse: Mars, latest version. > Webserver: Wilfly 10.0.0 > Maven: 3.3.3 > JBoss Tools: Latest version. > Reporter: Tiago Matias > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE22157.zip > > > Consider two eclipse maven projects: A Web project (WAR) and a Utility project JAR with a JSP TLD file inside. > After building the project and deploying to Wildfly the utiltiy JAR will be exploded under WEB-INF/LIB of the WAR project. > An exploded jar is incompatible with TLD files since the JSP engine search for the TLD file and then try to open/unzip the JAR. Since the JAR is just a folder, it causes an "Access Denied" exception, as shown below: > org.apache.jasper.JasperException: java.io.FileNotFoundException: C:\Program Files\Java\wildfly-10.0.0.Final\standalone\deployments\portal.web.war\WEB-INF\lib\portal.framework-0.0.1-SNAPSHOT.jar (Acesso negado) > org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:151) > org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:412) > org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475) > org.apache.jasper.compiler.Parser.parseElements(Parser.java:1456) > org.apache.jasper.compiler.Parser.parse(Parser.java:143) > A possible alternative would be to turnoff the option "Resolve dependencies from workspace projects" in Eclipse. In this scenario the JAR won't get exploded on WAR's WEB-INF/lib and everything works. However, any change to the JAR project won't get picked up and deployed to the target unless it's POM version is incremented which is incompatible with a development scenario where the projects are constantly updated and built. > I request that the eclipse wildfly connector provides an option to control weather the dependency JAR's are exploded or not into the final deployment. > Please note, this only applies to dependencies that are workspace projects. All the other dependencies (spring, hibernate, etc...) are simply copied as a JAR archive, as expected. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22066) Stopping debugging of OpenShift application should get application back to normal state.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22066: -------------------------------- Sprint: devex #6 April 2016 > Stopping debugging of OpenShift application should get application back to normal state. > ---------------------------------------------------------------------------------------- > > Key: JBIDE-22066 > URL: https://issues.jboss.org/browse/JBIDE-22066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When user stop or delete Server Adapter where debugging has been enabled, application should be able to get back to normal state - remove environment variable for debugging and remove ports for debugging from deployment config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22118) Openshift 3 plugin should support "builder" images

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22118?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22118: -------------------------------- Sprint: devex #6 April 2016 > Openshift 3 plugin should support "builder" images > -------------------------------------------------- > > Key: JBIDE-22118 > URL: https://issues.jboss.org/browse/JBIDE-22118 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > Attachments: buildconfig page.png, page_1.png > > > I installed the following image stream: https://raw.githubusercontent.com/jboss-openshift/application-templates/m... > It contains several "builder" images. I would like to use jboss-eap70-openshift:1.3-Beta to build a JavaEE 7 application available at https://github.com/redhat-helloworld-msa/hello . But the Openshift plugin only shows "templates". > Openshift plugin should support "builder" images. These images contain "builder" on their tags. > Ref: Jan-5-2016 discussion: http://etherpad.corp.redhat.com/OpenShiftAndJBossStudio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22125) Add docker connection management to deploy image wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22125?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22125: -------------------------------- Sprint: devex #6 April 2016 > Add docker connection management to deploy image wizard > ------------------------------------------------------- > > Key: JBIDE-22125 > URL: https://issues.jboss.org/browse/JBIDE-22125 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: docker, openshift > Fix For: 4.4.0.Alpha1 > > Attachments: cannot-choose-docker-connection.png > > > clicked this nice "Deploy to openshift" menu in Openshift explorer and the dialog that shows up is just a lot of fields with no values. > Cannot create a new docker connection. > Makes it hard to get started ;/ > steps to reproduce: > 1) ASSERT: No docker connections defined in your workspace > 2) EXEC: From the Openshift explorer, right click on an Openshift connection and select 'Deploy Docker image...' > Result: > You get a wizard page with an empty 'Docker connection' combo and no way to define one (unless you've applied the pull request) > !cannot-choose-docker-connection.png! > Expected result: > You should be able to create a new docker connection without leaving the wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22194) Select template: inform user of his mistake in a more friendly way

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22194?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22194: -------------------------------- Sprint: devex #6 April 2016 > Select template: inform user of his mistake in a more friendly way > ------------------------------------------------------------------ > > Key: JBIDE-22194 > URL: https://issues.jboss.org/browse/JBIDE-22194 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > When user selects a json file with wrong resource instead of template, he should be informed of his mistake in a more friendly way. > It is a ClassCastException now that user sees in an Error dialog, and he may be confused if it is his mistake or an application bug. Let's not log, nor show exception in this case, but just display what kind of resource user selected and what resource was expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016