[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:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have an as7 server adapter
# ASSERT: make sure you have a WTP project in your workspace that you can deplyo to as7
# EXEC: drag and drop the project to your server adapter
# EXEC: double click as7 server adapter, in the upcoming server editor choose "deployments" tab
Result:
The deployments table is disabled
!deployments-greyed-out.png!
Expected result:
The deployments table is enabled, I should be able to edit the deployments
was:
# ASSERT: make sure you have an as7 server adapter
# ASSERT: make sure you have a WTP project in your workspace that you can deplyo to as7
# EXEC: drag and drop the project to your server adapter
# EXEC: double click as7 server adapter, in the upcoming server editor choose "deployments" tab
Result:
The deployments table is disabled
Expected result:
The deployments table is enabled, I should be able to edit the deployments
> 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: openshift, 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
>
>
> 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
[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:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have an as7 server adapter
# ASSERT: make sure you have a WTP project in your workspace that you can deplyo to as7
# EXEC: drag and drop the project to your server adapter
# EXEC: double click as7 server adapter, in the upcoming server editor choose "deployments" tab
Result:
The deployments table is disabled
Expected result:
The deployments table is enabled, I should be able to edit the deployments
> 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: openshift, server
> Reporter: Max Rydahl Andersen
> 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
[JBoss JIRA] (JBIDE-14817) bump parent pom version used in root pom to Beta2
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14817?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-14817.
---------------------------------
Fix Version/s: 4.1.0.Beta2
Resolution: Done
pushed
> bump parent pom version used in root pom to Beta2
> -------------------------------------------------
>
> Key: JBIDE-14817
> URL: https://issues.jboss.org/browse/JBIDE-14817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta2
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta2
>
>
> [~rob.stryker]: Please bump parent pom version used in root pom to Beta2, in your master branch, so that you're using the correct upstream Foundation stuff, and not throwing errors like this:
> {code}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.ide.eclipse.archives.webtools 2.4.100.qualifier
> [ERROR] Missing requirement: org.jboss.tools.common.core 3.5.0.Beta1-v20130525-0108-B68 requires 'bundle org.eclipse.ecf.provider.filetransfer.httpclient 4.0.200' but it could not be found
> [ERROR] Cannot satisfy dependency: org.jboss.ide.eclipse.archives.webtools 2.4.100.qualifier depends on: bundle org.jboss.ide.eclipse.as.ui 0.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.ide.eclipse.as.ui 2.4.100.qualifier depends on: bundle org.jboss.tools.runtime.ui 2.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.tools.runtime.ui 2.1.0.Beta1-v20130525-0108-B68 depends on: bundle org.jboss.tools.common.core 3.4.0
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.common.core 3.5.0.Beta1-v20130525-0108-B68 to bundle org.eclipse.ecf.provider.filetransfer.httpclient 4.0.200.", "No solution found because the problem is unsatisfiable."] -> [Help 1]{code}
--
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