April 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10263) Prevent App creation when limit (5 apps per account) is reached

by Xavier Coulon (Created) (JIRA)

Prevent App creation when limit (5 apps per account) is reached --------------------------------------------------------------- Key: JBIDE-10263 URL: https://issues.jboss.org/browse/JBIDE-10263 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Andre Dietisheim The 'new' button should be disabled when the account already has 5 applications and a message should inform the user that he as reached his quota. Otherwise, Openshift responds with a 400 error when the user finished his app creation :-( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

8
26
0 / 0

[JBoss JIRA] (JBIDE-11521) Save and Save All actions are not available after inserting more than 1 tags from palette to source editor

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-11521: ----------------------------------- Summary: Save and Save All actions are not available after inserting more than 1 tags from palette to source editor Key: JBIDE-11521 URL: https://issues.jboss.org/browse/JBIDE-11521 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.Beta3 Environment: Linux 32bit, 3.3.0.v20120412-0201-H4578-Beta3 Reporter: Vlado Pakan Assignee: Yahor Radtsevich Fix For: 3.3.0.Beta3 1. Open some web page. 2. Insert tag from Palette to Source Part of VPE Assert: Save and Save All actions are enabled 3. Insert another tag from Palette to Source Part of VPE ERROR: Save and Save All actions are disabled Web page editor is marked as dirty. When trying to close dialog asking to save changes is displayed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-10454) provide capabability to edit ssh keys

by Andre Dietisheim (Created) (JIRA)

provide capabability to edit ssh keys ------------------------------------- Key: JBIDE-10454 URL: https://issues.jboss.org/browse/JBIDE-10454 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.M5 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 We currently only allow the user to rename the namespace (domain). There's currently no way to change the ssh key in our tooling (the Web GUI offers that capability to the user). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-10435) building my app with the embedded jenkins fails, if I already have 4 apps

by Andre Dietisheim (Created) (JIRA)

building my app with the embedded jenkins fails, if I already have 4 apps ------------------------------------------------------------------------- Key: JBIDE-10435 URL: https://issues.jboss.org/browse/JBIDE-10435 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
6
0 / 0

[JBoss JIRA] (JBDS-2003) review supported soa-p platforms available for automated testing

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2003: -------------------------------- Summary: review supported soa-p platforms available for automated testing Key: JBDS-2003 URL: https://issues.jboss.org/browse/JBDS-2003 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 5.0.0.Beta1 Reporter: Nick Boldt Assignee: Len DiMaggio Fix For: 5.0.0.Beta1 This file documents which runtimes, and which VERSIONS of runtimes, are available for testing. https://svn.jboss.org/repos/jbosstools/trunk/requirements/soap/build.prop... 1. Are the versions listed current? Eg., should there be 4.3.CP05 instead of 4.3.0? 2. Are there enough streams listed? Eg., should 5.3.0 be there too? 5.4.0? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
23
0 / 0

[JBoss JIRA] Created: (JBIDE-6932) Feature request - to support editing JBossESB/SOA-P deployment.xml and jbm-queue-service.xml files

by Len DiMaggio (JIRA)

Feature request - to support editing JBossESB/SOA-P deployment.xml and jbm-queue-service.xml files --------------------------------------------------------------------------------------------------- Key: JBIDE-6932 URL: https://jira.jboss.org/browse/JBIDE-6932 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: common Affects Versions: 3.2.0.M1 Reporter: Len DiMaggio Assignee: Alexey Kazakov Feature request - to support editing JBossESB/SOA-P deployment.xml and jbm-queue-service.xml files A wizard to populate and an editor to view/modify these files would be a good addition. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] (JBDS-2082) Error (ERROR o.e.m.c.i.i.nexus.NexusIndexManager - Unable to update index for central|http://repo1.maven.org/maven2) when beta2 is closed

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2082: ---------------------------------- Summary: Error (ERROR o.e.m.c.i.i.nexus.NexusIndexManager - Unable to update index for central|http://repo1.maven.org/maven2) when beta2 is closed Key: JBDS-2082 URL: https://issues.jboss.org/browse/JBDS-2082 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: maven Affects Versions: 5.0.0.Beta2 Environment: Version: 5.0.0.Beta2 Build id: v20120328-1758-H123-Beta2 Build date: 20120328-1758 Reporter: Len DiMaggio Assignee: Snjezana Peco Fix For: 5.0.0.Beta3 When JBDS 5.0.beta2 is closed, this error is written to stdout: 12:25:54.899 [Worker-11] ERROR o.e.m.c.i.i.nexus.NexusIndexManager - Unable to update index for central|http://repo1.maven.org/maven2 org.apache.lucene.index.CorruptIndexException: Unknown format version: -9 at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:225) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52] at org.apache.lucene.index.DirectoryIndexReader$1.doBody(DirectoryIndexReader.java:95) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:653) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52] at org.apache.lucene.index.DirectoryIndexReader.open(DirectoryIndexReader.java:115) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52] at org.apache.lucene.index.IndexReader.open(IndexReader.java:316) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52] at org.apache.lucene.index.IndexReader.open(IndexReader.java:227) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52] at org.apache.maven.index.updater.DefaultIndexUpdater.copyUpdatedDocuments(DefaultIndexUpdater.java:352) ~[indexer-core-3.1.0.jar:3.1.0] at org.apache.maven.index.updater.DefaultIndexUpdater.unpackIndexArchive(DefaultIndexUpdater.java:288) ~[indexer-core-3.1.0.jar:3.1.0] at org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:218) ~[indexer-core-3.1.0.jar:3.1.0] at org.apache.maven.index.updater.DefaultIndexUpdater.access$300(DefaultIndexUpdater.java:75) ~[indexer-core-3.1.0.jar:3.1.0] at org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile(DefaultIndexUpdater.java:645) ~[indexer-core-3.1.0.jar:3.1.0] at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:844) ~[indexer-core-3.1.0.jar:3.1.0] at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:156) ~[indexer-core-3.1.0.jar:3.1.0] at org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.updateRemoteIndex(NexusIndexManager.java:1137) [org.eclipse.m2e.core_1.0.200.20111228-1245.jar:na] at org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.updateIndex(NexusIndexManager.java:1081) [org.eclipse.m2e.core_1.0.200.20111228-1245.jar:na] at org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager$1.run(NexusIndexManager.java:658) [org.eclipse.m2e.core_1.0.200.20111228-1245.jar:na] at org.eclipse.m2e.core.internal.index.nexus.IndexUpdaterJob.run(IndexUpdaterJob.java:71) [org.eclipse.m2e.core_1.0.200.20111228-1245.jar:na] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) [org.eclipse.core.jobs_3.5.101.v20120113-1953.jar:na] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
18
0 / 0

[JBoss JIRA] (JBIDE-11248) Invalid web.xml warning for welcome-file and error-page

by Cody Lerum (JIRA)

Cody Lerum created JBIDE-11248: ---------------------------------- Summary: Invalid web.xml warning for welcome-file and error-page Key: JBIDE-11248 URL: https://issues.jboss.org/browse/JBIDE-11248 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.M5 Environment: Nightly Build as of 3/8/2012 Reporter: Cody Lerum web.xml shows warning "file name references to login.jsp that does not exist in web content" for {code} <welcome-file-list> <welcome-file>login.jsf</welcome-file> </welcome-file-list> {code} and "location references to /error/403.jsp that does not exist in web content" for {code} <error-page> <error-code>403</error-code> <location>/error/403.jsf</location> </error-page> {code} This just changed in a recent nightly and the actual pages are .xhtml not jsp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
15
0 / 0

[JBoss JIRA] (JBIDE-10251) JBossTools/Server Runtime fails to pick up new JDK/JRE runtime

by Gregor Rosenauer (Created) (JIRA)

JBossTools/Server Runtime fails to pick up new JDK/JRE runtime -------------------------------------------------------------- Key: JBIDE-10251 URL: https://issues.jboss.org/browse/JBIDE-10251 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M3 Environment: JBoss AS 6.1.0.Final, JDK 1.6.0_27, Eclipse 3.7.1 "Indigo", WindowsXP 32bit Reporter: Gregor Rosenauer Assignee: Rob Stryker After installing a new Java version and changing JAVA_HOME and Eclipse JDK and JBoss Runtime settings accordingly, exisiting Server runtime configurations fail to pick up the changed VM and refuse to start. The only solution is to delete the server runtime configuration and create a fresh one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

7
10
0 / 0

[JBoss JIRA] (JBIDE-11227) reverse engineering for h2 (and possible other db's) fail if a . in catalog/schema name

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11227: ------------------------------------------- Summary: reverse engineering for h2 (and possible other db's) fail if a . in catalog/schema name Key: JBIDE-11227 URL: https://issues.jboss.org/browse/JBIDE-11227 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: hibernate Reporter: Max Rydahl Andersen Assignee: Dmitry Geraskov Priority: Minor setup h2 db which name is xyz.db.h2.db so the catalog name becomes xyz.db. Then no tables are found by reverse engineering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
14
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 2012