February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19347) CordovaSim Gone

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19347?page=com.atlassian.jira.plugi... ] Burr Sutter updated JBIDE-19347: -------------------------------- Component/s: browsersim > CordovaSim Gone > --------------- > > Key: JBIDE-19347 > URL: https://issues.jboss.org/browse/JBIDE-19347 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Burr Sutter > Priority: Critical > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19347) CordovaSim Gone

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-19347: ----------------------------------- Summary: CordovaSim Gone Key: JBIDE-19347 URL: https://issues.jboss.org/browse/JBIDE-19347 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter Priority: Critical The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". Windows http://www.screencast.com/t/Wk8js7zf6kec Mac OSX http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19336) When JBT and Central both contain the same IU but different versions, p2-director installation fails

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19336?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19336: --------------------------------------------- just to be clear the actual title here "When JBT and Central both contain the same IU but different versions, p2-director installation fails" is expected IMO. Why should the p2 director install not fall if you try install both at the same time ? The issue is that we have two conflicting versions, and that is what this issue should be about, right? > When JBT and Central both contain the same IU but different versions, p2-director installation fails > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19336 > URL: https://issues.jboss.org/browse/JBIDE-19336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > Attachments: two-versions-of-a-feature-not-good.png > > > For master branch I'm getting conflicts between what's in JBT and what's in Central: > {code} > 17:01:57 [p2.dir] Only one of the following can be installed at once: > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150212-1941-B633 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150212-1941-B633) > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150213-0945-B3 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150213-0945-B3) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19265) Not able to deploy an archive packaged as a jboss-sar

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19265?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19265: -------------------------------- Component/s: maven upstream > Not able to deploy an archive packaged as a jboss-sar > ------------------------------------------------------ > > Key: JBIDE-19265 > URL: https://issues.jboss.org/browse/JBIDE-19265 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Reporter: Sande Gilda > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > > The `helloworld-mbean` quickstart project contains 2 subprojects: a `war` archive and a `jboss-sar` archive. You can deploy the WAR, but It is not possible to deploy the SAR. > > See https://bugzilla.redhat.com/show_bug.cgi?id=1191485 > The source is located here: https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x-devel... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19096: ---------------------------------------- Assignee: Andre Dietisheim Resolution: Done merged and pushed to upstream/master. The basic implementation works. Bugs and lacking features will be filed to new jiras > Connection wizard: Allow v2 and v3 Connections > ---------------------------------------------- > > Key: JBIDE-19096 > URL: https://issues.jboss.org/browse/JBIDE-19096 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > Attachments: existing-v2-connection.png, fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png > > > the existing UI for v2 OpenShift: > * new connection: > !screenshot-openshift-signin.png! > * existing connection: > !existing-v2-connection.png! > In order to allow us to present v2 and v3 connections we have to change the connection wizard: > When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different: > * v2 connections currently use username/password (and will most likely also allow x509, kerberos) > * v3 connections will most likely require OAuth settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19346) jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19346?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19346: --------------------------------------- Tern is not EA, only angularjs is. > jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19346 > URL: https://issues.jboss.org/browse/JBIDE-19346 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > While promoting JBT 4.3.0.Alpha1 to /development/ I realized that jbosstools-earlyaccess.properties contains old versions. We should have tern/angular 0.8 in there, right [~dgolovin] ? > {code} > $➔ cat jbosstools-earlyaccess.properties > #Mon Sep 01 18:54:14 CEST 2014 > org.eclipse.vjet.rt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.jboss.tools.arquillian.feature.feature.group=[1.1.2.CR1-v20140830-0003-B63,1.1.2.CR1-v20140830-0003-B63] > org.eclipse.vjet.extmod.jsdt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.web.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.extmod.dltk.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.codegen.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-server-nodejs-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.eclipse.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern.eclipse.ide.tools.feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > tern.eclipse.ide.server.nodejs.embed.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.vsf.domkit.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.equinox.server.jetty.feature.group=[1.1.100.v20140416-1649,1.1.100.v20140416-1649] > org.eclipse.vjet.extmod.rhino.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-jsdt-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > angularjs-eclipse-feature.feature.group=[0.5.0.201408281218,0.5.0.201408281218] > {code} > -- http://download.jboss.org/jbosstools/discovery/staging/4.3.0.Alpha1/jboss... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14427) should have a maven configurator for arquillian

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14427?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-14427. ------------------------------------ Resolution: Done The configurator is in Alpha1. Please create a separate issue for the remaining problems. > should have a maven configurator for arquillian > ----------------------------------------------- > > Key: JBIDE-14427 > URL: https://issues.jboss.org/browse/JBIDE-14427 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven, testing-tools > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > on import of a maven project that already have maven we should enable arquillian -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14782) Add ShrinkWrap Archive file location validation

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14782?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-14782. ------------------------------------ Resolution: Partially Completed Please create a separate issue for remaining problems. > Add ShrinkWrap Archive file location validation > ----------------------------------------------- > > Key: JBIDE-14782 > URL: https://issues.jboss.org/browse/JBIDE-14782 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > *Given* > A Deployment method > *When* > {code} > war.addAsManifestResource(X, "beans.xml") > ear.addAsManifestResource(X, "beans.xml") > war.addAsManifestResource(X, "persistence.xml") > {code} > *Then* > Warn that known EE descriptor files are in the wrong location > Some mapping on top of my head: > WebArchive > {code} > web.xml -> /WEB-INF/ > web-fragment.xml -> Not supported ? > beans.xml -> /WEB-INF/ > persistence.xml -> /WEB-INF/classes/META-INF/ > ejb-jar.xml -> /WEB-INF/classes/META-INF/ > {code} > JavaArchive > {code} > web.xml -> Not supported > web-fragment.xml -> /META-INF/ > beans.xml -> /META-INF/ > persistence.xml -> /META-INF/ > ejb-jar.xml -> /META-INF/ > {code} > EnterpriseArchive > {code} > beans.xml -> Not supported > persistence.xml -> Not supported > ejb-jar.xml -> Not supported > application.xml -> /META-INF/ > {code} > One common mistake is using addAsManifestResource on WebArchives. A quickfix / suggestion would be to use addAsWebInfResource for the files located in /WEB-INF/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18460) 'Add type to deployment' quickfix doesn't work with abstract classes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18460?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18460: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > 'Add type to deployment' quickfix doesn't work with abstract classes > -------------------------------------------------------------------- > > Key: JBIDE-18460 > URL: https://issues.jboss.org/browse/JBIDE-18460 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.2.0.CR1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.3.0.Alpha2 > > > Steps to reproduce: > - create an abstract Arquillian JUnit test with a deployment method > - create an Arquillian JUnit test extending the previous created abstract class > - add a type not included in the deployment method to the test created in the step 2 > The "Type is not included in any deployment" marker will be created properly > - call the "Add type to deployment" quickfix > You will get the "Cannot find a deployment method" dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19344) Update Tern.java & AngularJS to 0.8.2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19344?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-19344 at 2/20/15 6:50 PM: ----------------------------------------------------------------- Which has not been released yet. Tern 0.8.2.201502201459 is what we need. This is a final 0.8.2 release. But we don't have AngularJS 0.8.2 final release yet. I hope it will be released on Monday and it *may* be different than 0.8.2.201502201459. If 0.8.2 is not released by Beta1 Code freeze we will stay with AngularJS 0.8.2-SNAPSHOT. was (Author: akazakov): Which is not released yet. Tern 0.8.2.201502201459 is what we need. This is a final 0.8.2 release. But we don't have AngularJS 0.8.2 final release yet. I hope it will be released on Monday and it *may* be different than 0.8.2.201502201459. If 0.8.2 is not released by Beta1 Code freeze we will stay with AngularJS 0.8.2-SNAPSHOT. > Update Tern.java & AngularJS to 0.8.2 > ------------------------------------- > > Key: JBIDE-19344 > URL: https://issues.jboss.org/browse/JBIDE-19344 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.2.3.Beta1 > > > Tern.java v. 0.8.2 has been released: http://oss.opensagres.fr/tern.repository/0.8.2/ > We need to update Tern.java and AngualarJS in Central EA. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015