October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15797) correct icons

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-15797: ---------------------------------------- Summary: correct icons Key: JBIDE-15797 URL: https://issues.jboss.org/browse/JBIDE-15797 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 There are a few quirks that we should fix for the icons: * the domain icon (globe) is cropped in MacOS * the "new connection" icon (in the explorer toolbar) is lacking some "+" and does not match the connection-icon in the explorer * "edit connection" is not matching the connection icon either (its a pen, should be pen with connection icon) -- 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-15796) Deployment error: No servlet class has been specified for servlet javax.ws.rs.core.Application

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15796?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-15796: ------------------------------- Attachment: forge-html5.server.log > Deployment error: No servlet class has been specified for servlet javax.ws.rs.core.Application > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15796 > URL: https://issues.jboss.org/browse/JBIDE-15796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.1.Beta1 > Reporter: Pavol Srna > Fix For: 4.1.1.Beta1 > > Attachments: forge-html5.server.log > > > Deployment with error: No servlet class has been specified for servlet javax.ws.rs.core.Application. > Prepare app in forge console: > 1) new-project --named testp --type war > 2) setup persistence (HIBERNATE, JBOSS_AS7) > 3) scaffold-x setup --scaffoldType angularjs --overwrite > 4) entity --named Customer > 5) field string --named name > Scaffold HTML5: > * scaffold-x from Customer.java > Build and deploy on the server. > See server.log attached for more description. > I assume this should work out of the box right? -- 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-15796) Deployment error: No servlet class has been specified for servlet javax.ws.rs.core.Application

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-15796: ---------------------------------- Summary: Deployment error: No servlet class has been specified for servlet javax.ws.rs.core.Application Key: JBIDE-15796 URL: https://issues.jboss.org/browse/JBIDE-15796 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.1.1.Beta1 Reporter: Pavol Srna Fix For: 4.1.1.Beta1 Deployment with error: No servlet class has been specified for servlet javax.ws.rs.core.Application. Prepare app in forge console: 1) new-project --named testp --type war 2) setup persistence (HIBERNATE, JBOSS_AS7) 3) scaffold-x setup --scaffoldType angularjs --overwrite 4) entity --named Customer 5) field string --named name Scaffold HTML5: * scaffold-x from Customer.java Build and deploy on the server. See server.log attached for more description. I assume this should work out of the box right? -- 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-15145) Published site (on Nexus) doesn't contain .pack.gz files

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15145?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-15145: ----------------------------------- Fix Version/s: (was: 1.1.0-LOCUS) > Published site (on Nexus) doesn't contain .pack.gz files > -------------------------------------------------------- > > Key: JBIDE-15145 > URL: https://issues.jboss.org/browse/JBIDE-15145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, locus, upstream > Reporter: Mickael Istria > Assignee: Mickael Istria > > This is a general issue with Maven: > $ mvn clean verify -P pack200 > $ cd site > $ mvn clean verify -P pack200 > makes that output site in site/target/repository doesn't contain .pack.gz files for the dependencies that are installed in Maven repo. > This is a general Tycho issue. We need to make sure this use-case.gets fixed in next version of Tycho. It seems related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=393004 -- 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-15765) JPP 6.1 recognized as AS 7.2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15765?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15765: --------------------------------------------- They dont conflict - they show the actual layers/products. JPP is based on top of EAP. The spec states the product slot should be searched for within the layers. > JPP 6.1 recognized as AS 7.2 > ---------------------------- > > Key: JBIDE-15765 > URL: https://issues.jboss.org/browse/JBIDE-15765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Critical > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: jpp 6.1 recognized as AS 72.jpg > > > JBoss Portal 6.1.0 Final is recognized as AS 7.2 in JBoss Runtime Detection (Type: AS, Version: 7.2). However, JPP 6.1.0 Beta is recognized correctly as JPP 6.1. -- 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-15792) JPP 6.1 project does not contain JBoss Portlet Libraries

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15792?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-15792: ------------------------------------ Priority: Blocker (was: Critical) > JPP 6.1 project does not contain JBoss Portlet Libraries > -------------------------------------------------------- > > Key: JBIDE-15792 > URL: https://issues.jboss.org/browse/JBIDE-15792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Priority: Blocker > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: portlet.jpg > > > Portal project with target runtime JPP 6.1.Final does not contain file "JBoss Portlet Libraries", so Java Portlet contains errors. However, if you create portal project with JPP 6.1.Beta then the file exists and no error is present. -- 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-15792) JPP 6.1 project does not contain JBoss Portlet Libraries

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15792?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-15792: ------------------------------------ Attachment: portlet.jpg > JPP 6.1 project does not contain JBoss Portlet Libraries > -------------------------------------------------------- > > Key: JBIDE-15792 > URL: https://issues.jboss.org/browse/JBIDE-15792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Priority: Critical > Fix For: 4.1.1.Beta1 > > Attachments: portlet.jpg > > > Portal project with target runtime JPP 6.1.Final does not contain file "JBoss Portlet Libraries", so Java Portlet contains errors. However, if you create portal project with JPP 6.1.Beta then the file exists and no error is present. -- 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-15792) JPP 6.1 project does not contain JBoss Portlet Libraries

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15792?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-15792: ------------------------------------ Labels: respin-a (was: ) > JPP 6.1 project does not contain JBoss Portlet Libraries > -------------------------------------------------------- > > Key: JBIDE-15792 > URL: https://issues.jboss.org/browse/JBIDE-15792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Priority: Critical > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: portlet.jpg > > > Portal project with target runtime JPP 6.1.Final does not contain file "JBoss Portlet Libraries", so Java Portlet contains errors. However, if you create portal project with JPP 6.1.Beta then the file exists and no error is present. -- 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-15795) Support multiselection of Feature in Cordova Configuration Editor for config.xml file

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-15795: ----------------------------------- Summary: Support multiselection of Feature in Cordova Configuration Editor for config.xml file Key: JBIDE-15795 URL: https://issues.jboss.org/browse/JBIDE-15795 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid Affects Versions: 4.1.1.Beta1 Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 Reporter: Vlado Pakan Priority: Minor Fix For: 4.1.1.CR1 Would be nice to support multiselection of feature in Cordova Configuration Editor when removing features from project configuration. User scenario: 1. Create new Hybrid Mobile project 2. Open config.xml file in Cordova Configuration Editor 3. Add more Features 4. Select more Features 5. Click on button remove ASSERT: All selected features are removed from project configuration -- 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-15793) Cordova Feature multiselection is not working

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15793?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-15793: -------------------------------- Summary: Cordova Feature multiselection is not working (was: Cordova Plugin multiselection is not working) > Cordova Feature multiselection is not working > --------------------------------------------- > > Key: JBIDE-15793 > URL: https://issues.jboss.org/browse/JBIDE-15793 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 > Reporter: Vlado Pakan > Fix For: 4.1.1.CR1 > > > 1. Create new Hybrid Mobile project > 2. Open config.xml file via Cordova Configuration Editor > 3. Choose Add.. to add features, select more than one feature and click Finish > ERROR: Only first selected feature is added to project and to config.xml file -- 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