June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14795) after installing svn from central, javahl seem to not be installed/working

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14795?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14795: ------------------------------- Attachment: no-svn-bad-svn.png Error reproduced in JBDS 7 Beta1, on 64-bit Fedora 16 (3.6.11-4.fc16.x86_64) linux: !no-svn-bad-svn.png! > after installing svn from central, javahl seem to not be installed/working > -------------------------------------------------------------------------- > > Key: JBIDE-14795 > URL: https://issues.jboss.org/browse/JBIDE-14795 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, updatesite > Reporter: Max Rydahl Andersen > Attachments: no-svn-bad-svn.png > > > installed svn + mylyn and gets error on startup with respect to javahl working. > "Failed to load JavaHL Library. > These are the errors that were encountered: > no libsvnjavahl-1 in java.library.path > no svnjavahl-1 in java.library.path > no svnjavahl in java.library.path > java.library.path = /Users/max/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:." -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14791) cannot rename deployed modules in AS7 server adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14791?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14791: ------------------------------------- Description: The as7 server adapter seem not to allow one to rename deployed modules. i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in / was: openshift nor as7 seem to anymore be able to rename their deployed modules. i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in / > cannot rename deployed modules in AS7 server adapter > ---------------------------------------------------- > > Key: JBIDE-14791 > URL: https://issues.jboss.org/browse/JBIDE-14791 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.0.Beta2 > > Attachments: deployments-greyed-out.png > > > The as7 server adapter seem not to allow one to rename deployed modules. > i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in / -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1574) What's up with the "ISO downloads" of JBDS PE 2.x and 3.x?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-1574?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-1574. ---------------------------- Assignee: Nick Boldt (was: mark yarborough) Release Notes Text: As of the 7.0.0.Beta1 release to CSP, the offending pages no longer exist. Closing "Out Of Date". Fix Version/s: 7.0.0.Beta1 (was: LATER) (was: 5.x) Resolution: Out of Date > What's up with the "ISO downloads" of JBDS PE 2.x and 3.x? > ---------------------------------------------------------- > > Key: JBDS-1574 > URL: https://issues.jboss.org/browse/JBDS-1574 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Beta1 > > Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot.png, software_downloads_rhn.png > > > Found some interestingly described JBDS 3.0 and earlier downloads in the CSP. > Steps to repro: > 1. Log in here: https://www.redhat.com/wapps/sso/login.html > 2. Click "Red Hat Network Preferences" -> https://rhn.redhat.com/network/my_account/my_prefs.pxt > 3. Click the "Download software" icon/button on the left-hand side of the site: > !software_downloads_rhn.png! > 4. Observe list of downloads - CTRL-F to search for Developer Studio > https://rhn.redhat.com/rhn/software/downloads/SupportedISOs.do > !Screenshot-1.png! > 5. Click on one of the entries, such as "JBoss Developer Studio - Portfolio Edition for Linux ", and get here: > https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=9103 > "ISO Image Downloads > NOTE: By downloading this software, you agree to the terms and conditions of the applicable License Agreement (available at http://www.redhat.com/licenses/) > Not sure how to download and use these images? Check out our ISO Download Help. > Latest Release > Below please find the complete set of ISO images for the latest release of JBoss Developer Studio - Portfolio Edition for Linux. Depending on the variant of JBoss Developer Studio - Portfolio Edition for Linux you'd like to install, you may only need a subset of these discs. (more information) " > !Screenshot-2.png! > 6. Have a WTF moment as you consider how a jarred installer can be classified as an ISO image. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14818: ------------------------------------- Description: In JDF-172 a users tries to deploy a GWT application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the GWT project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. (was: In JDF-172 a users tries to deploy a GWT application to OpenShift. He'll use the binary deployment. In order to have the app showing up at / he'll want to rename the war to ROOT.war. If he does this in the *Project Explorer* things are fine as long as the GWT project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.) > there's no "deployments" page for OpenShift that would allow me to rename a module > ---------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.0.Beta2 > > > In JDF-172 a users tries to deploy a GWT application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the GWT project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1574) What's up with the "ISO downloads" of JBDS PE 2.x and 3.x?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-1574?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-1574. ---------------------------- Release Notes Text: (was: As of the 7.0.0.Beta1 release to CSP, the offending pages no longer exist. Closing "Out Of Date".) Resolution: Done As of the 7.0.0.Beta1 release to CSP, the offending pages no longer exist. Closing "Out Of Date". > What's up with the "ISO downloads" of JBDS PE 2.x and 3.x? > ---------------------------------------------------------- > > Key: JBDS-1574 > URL: https://issues.jboss.org/browse/JBDS-1574 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Beta1 > > Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot.png, software_downloads_rhn.png > > > Found some interestingly described JBDS 3.0 and earlier downloads in the CSP. > Steps to repro: > 1. Log in here: https://www.redhat.com/wapps/sso/login.html > 2. Click "Red Hat Network Preferences" -> https://rhn.redhat.com/network/my_account/my_prefs.pxt > 3. Click the "Download software" icon/button on the left-hand side of the site: > !software_downloads_rhn.png! > 4. Observe list of downloads - CTRL-F to search for Developer Studio > https://rhn.redhat.com/rhn/software/downloads/SupportedISOs.do > !Screenshot-1.png! > 5. Click on one of the entries, such as "JBoss Developer Studio - Portfolio Edition for Linux ", and get here: > https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=9103 > "ISO Image Downloads > NOTE: By downloading this software, you agree to the terms and conditions of the applicable License Agreement (available at http://www.redhat.com/licenses/) > Not sure how to download and use these images? Check out our ISO Download Help. > Latest Release > Below please find the complete set of ISO images for the latest release of JBoss Developer Studio - Portfolio Edition for Linux. Depending on the variant of JBoss Developer Studio - Portfolio Edition for Linux you'd like to install, you may only need a subset of these discs. (more information) " > !Screenshot-2.png! > 6. Have a WTF moment as you consider how a jarred installer can be classified as an ISO image. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1574) What's up with the "ISO downloads" of JBDS PE 2.x and 3.x?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-1574?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-1574. ---------------------------- Resolution: Out of Date > What's up with the "ISO downloads" of JBDS PE 2.x and 3.x? > ---------------------------------------------------------- > > Key: JBDS-1574 > URL: https://issues.jboss.org/browse/JBDS-1574 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Beta1 > > Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot.png, software_downloads_rhn.png > > > Found some interestingly described JBDS 3.0 and earlier downloads in the CSP. > Steps to repro: > 1. Log in here: https://www.redhat.com/wapps/sso/login.html > 2. Click "Red Hat Network Preferences" -> https://rhn.redhat.com/network/my_account/my_prefs.pxt > 3. Click the "Download software" icon/button on the left-hand side of the site: > !software_downloads_rhn.png! > 4. Observe list of downloads - CTRL-F to search for Developer Studio > https://rhn.redhat.com/rhn/software/downloads/SupportedISOs.do > !Screenshot-1.png! > 5. Click on one of the entries, such as "JBoss Developer Studio - Portfolio Edition for Linux ", and get here: > https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=9103 > "ISO Image Downloads > NOTE: By downloading this software, you agree to the terms and conditions of the applicable License Agreement (available at http://www.redhat.com/licenses/) > Not sure how to download and use these images? Check out our ISO Download Help. > Latest Release > Below please find the complete set of ISO images for the latest release of JBoss Developer Studio - Portfolio Edition for Linux. Depending on the variant of JBoss Developer Studio - Portfolio Edition for Linux you'd like to install, you may only need a subset of these discs. (more information) " > !Screenshot-2.png! > 6. Have a WTF moment as you consider how a jarred installer can be classified as an ISO image. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14818: ---------------------------------------- Description: In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. (was: In JDF-172 a users tries to deploy a GWT application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the GWT project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.) > there's no "deployments" page for OpenShift that would allow me to rename a module > ---------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.0.Beta2 > > > In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14818: ------------------------------------- Affects Version/s: 4.1.0.Beta2 > there's no "deployments" page for OpenShift that would allow me to rename a module > ---------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.0.Beta2 > > > In JDF-172 a users tries to deploy a GWT application to OpenShift. He'll use the binary deployment. In order to have the app showing up at / he'll want to rename the war to ROOT.war. If he does this in the *Project Explorer* things are fine as long as the GWT project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14818: ------------------------------------- Description: In JDF-172 a users tries to deploy a GWT application to OpenShift. He'll use the binary deployment. In order to have the app showing up at / he'll want to rename the war to ROOT.war. If he does this in the *Project Explorer* things are fine as long as the GWT project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. (was: openshift nor as7 seem to anymore be able to rename their deployed modules. i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in /) > there's no "deployments" page for OpenShift that would allow me to rename a module > ---------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.0.Beta2 > > > In JDF-172 a users tries to deploy a GWT application to OpenShift. He'll use the binary deployment. In order to have the app showing up at / he'll want to rename the war to ROOT.war. If he does this in the *Project Explorer* things are fine as long as the GWT project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-14818: ---------------------------------------- Assignee: Rob Stryker > there's no "deployments" page for OpenShift that would allow me to rename a module > ---------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.0.Beta2 > > > openshift nor as7 seem to anymore be able to rename their deployed modules. > i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in / -- 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, 10 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 June 2013