January 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8261) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213

by Andre Dietisheim (JIRA)

Launch instance wizard: cannot access webapp (404) if using ami-7ad22213 ------------------------------------------------------------------------ Key: JBIDE-8261 URL: https://issues.jboss.org/browse/JBIDE-8261 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR2 (tentative) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
15
0 / 0

[JBoss JIRA] Created: (JBDS-1452) Unable to install JBDS from update site

by Vlado Pakan (JIRA)

Unable to install JBDS from update site --------------------------------------- Key: JBDS-1452 URL: https://jira.jboss.org/browse/JBDS-1452 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 4.0.0.Beta2 Environment: JBDS 4.0.0.v201010160636R-H52-Beta1 trying to update to JBDS 4.0.0.v201012070137R-H33-Beta2 Reporter: Vlado Pakan Assignee: Nick Boldt When trying to update from JBDS 4.0.0.Beta1 to JBDS 4.0.0.Beta2 I'm getting this error: Cannot complete the install because one or more required items could not be found. Software being installed: Spring IDE Integration, Flex and Web Services Extension (optional) 2.5.1.201011101000-RELEASE (org.springframework.ide.eclipse.integration.feature.feature.group 2.5.1.201011101000-RELEASE) Missing requirement: Spring Integration Security Support 2.0.0.M4 (org.springframework.integration.security 2.0.0.M4) requires 'package org.springframework.security [2.0.5.RELEASE,4.0.0)' but it could not be found Cannot satisfy dependency: From: Spring IDE Integration, Flex and Web Services Extension (optional) 2.5.1.201011101000-RELEASE (org.springframework.ide.eclipse.integration.feature.feature.group 2.5.1.201011101000-RELEASE) To: org.springframework.integration.security [2.0.0.M4] JBDS update site: http://reports.qa.atl.jboss.com/binaries/RHDS/builds/staging/devstudio-4.... Spring IDE update site: http://reports.qa.atl.jboss.com/binaries/RHDS/builds/staging/devstudio-4.... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7732) fixe for JBIDE-1029 breaks version control for SCM that reqiure checkout for writable files

by joe freeman (JIRA)

fixe for JBIDE-1029 breaks version control for SCM that reqiure checkout for writable files ------------------------------------------------------------------------------------------- Key: JBIDE-7732 URL: https://jira.jboss.org/browse/JBIDE-7732 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.0.M2 Environment: Eclipse 3.6 with JBPM 3 editor 3.2.0M2 probably introduced in 3.1 M3 Reporter: joe freeman Assignee: Koen Aers Priority: Critical JBIDE-1029 tried to fix the issue where the JBPM xml editor fails when editing non-writable files. The fix (015307?) in the URL below offers the user the opportunity to change the attributes from r/o to r/w bypassing the SCM hooks. So for an SCM like Perforce where all files are locked until checkout, the user will have changed the R/W bits without notifying the SCM so they can save their changes but they never get committed back to the repository. Users can lose changes without knowing it. If you answer NO to the panel offered by JBIDE-1029 then the editor will still let you edit and when you save it will check out the processdefinition.xml in the SCM file like it used to and will fail on the gpd and jpg files (like it used to). The fix should have used the same Eclipse hooks used by the editor so that all 3 files end up checked out. Changing the access bits directly seems like a bad idea http://lists.jboss.org/pipermail/jbosstools-commits/2009-September/015307... https://jira.jboss.org/browse/JBIDE-1029 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
10
0 / 0

[JBoss JIRA] Created: (JBDS-1518) Teiid breaks down JBDS installation

by Pavol Srna (JIRA)

Teiid breaks down JBDS installation ------------------------------------ Key: JBDS-1518 URL: https://issues.jboss.org/browse/JBDS-1518 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: teiid Affects Versions: 4.0.0.CR1 Environment: JBDS 4.0.0.CR1 (jbdevstudio-product-eap-linux-gtk-4.0.0.v201101192139R-H84-CR1), linux 32bit Reporter: Pavol Srna Priority: Blocker 1) Install JBDS 2) Open new workspace 3) Open Teiid Project Example (Help -> Project Examples -> Teiid -> Parts Model Project Set Example 4) Open Teiid Perspective 5) Close JBDS 6) Open JBDS * you will notice that JBDS will never prompt for workspace selection on startup * In some cases it was even unable to start JBDS and I had to reinstall the whole JBDS .. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

5
30
0 / 0

[JBoss JIRA] Created: (JBIDE-8248) Connection wizard: error when using username ""ami-7ad22213"" on MacOS

by Andre Dietisheim (JIRA)

Connection wizard: error when using username ""ami-7ad22213"" on MacOS ---------------------------------------------------------------------- Key: JBIDE-8248 URL: https://issues.jboss.org/browse/JBIDE-8248 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR2 (tentative) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
13
0 / 0

[JBoss JIRA] Created: (JBDS-1524) Add symbolic link/shell script to launch OSX, Linux and Windows eclipse

by Max Rydahl Andersen (JIRA)

Add symbolic link/shell script to launch OSX, Linux and Windows eclipse ----------------------------------------------------------------------- Key: JBDS-1524 URL: https://issues.jboss.org/browse/JBDS-1524 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Environment: Reporter: Max Rydahl Andersen Assignee: Denis Golovin Fix For: 4.0.0.CR2, 4.0.x as discussed in JBDS-1382 it would make sense to have a jbdevstudio.sh/jbdevstudio.bat in the root installation to the proper launch. might have to be OS specific for linux/osx...need to validate. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8254) Launch instance wizard: warning about an key that is not known to the ssh-subsystem should be a field decoration

by Andre Dietisheim (JIRA)

Launch instance wizard: warning about an key that is not known to the ssh-subsystem should be a field decoration ---------------------------------------------------------------------------------------------------------------- Key: JBIDE-8254 URL: https://issues.jboss.org/browse/JBIDE-8254 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR2 (tentative) Attachments: unknwon-key-warning.png The current UI warns the user if a key that was chosen to launch the instance, is not known to the ssh-subsystem (it's not listed in the private keys). Using a dialog is not a good solution.We should use a field decoration for this purpose. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
16
0 / 0

[JBoss JIRA] Created: (JBIDE-8253) Launch instance wizard: you get warned of a key that is not known to the ssh-subsystem even if the key is listed in the ssh-prefsde

by Andre Dietisheim (JIRA)

Launch instance wizard: you get warned of a key that is not known to the ssh-subsystem even if the key is listed in the ssh-prefsde ----------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8253 URL: https://issues.jboss.org/browse/JBIDE-8253 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR2 (tentative) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
16
0 / 0

[JBoss JIRA] Created: (JBIDE-8250) connection wizard: authorisation error is reported in a dialog, title area says test was successful

by Andre Dietisheim (JIRA)

connection wizard: authorisation error is reported in a dialog, title area says test was successful --------------------------------------------------------------------------------------------------- Key: JBIDE-8250 URL: https://issues.jboss.org/browse/JBIDE-8250 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR2 (tentative) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
13
0 / 0

[JBoss JIRA] Created: (JBDS-1150) Installer chooses 64-bit VM as the default VM even with 32-bit distribution

by Trustin Lee (JIRA)

Installer chooses 64-bit VM as the default VM even with 32-bit distribution --------------------------------------------------------------------------- Key: JBDS-1150 URL: https://jira.jboss.org/jira/browse/JBDS-1150 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 3.0.0.CR2 Environment: Windows 7 x64 Ultimate Edition Reporter: Trustin Lee At step 4 of 11, the default Java VM path points to C:\Program Files\Java\jre6. However, it is a 64-bit VM which does not work with the 32-bit distribution. If the default system JVM is 64-bit, the installer should ask user to specify the correct VM path or try to guess more paths (e.g. C:\Program Files (x86)\Java\jre6). Otherwise, JBDS will fail on startup even if the installation succeeds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

6
17
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 January 2011