[JBoss JIRA] (JBIDE-13162) Cannot deploy dynamic web project to OpenShift (WATCHER)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13162?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13162:
-------------------------------------
Estimated Difficulty: Low
> Cannot deploy dynamic web project to OpenShift (WATCHER)
> --------------------------------------------------------
>
> Key: JBIDE-13162
> URL: https://issues.jboss.org/browse/JBIDE-13162
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.0.0.CR1
> Reporter: Stefan Bunciak
> Fix For: 4.2.x
>
>
> Dynamic web project should should be deployable to OpenShift (is visible when merging OpenShift application and the workspace project).
> After publishing, following output is returned from server:
> {code}
> [INFO] Packaging webapp
> [INFO] Assembling webapp [dw] in [/var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/target/dw]
> [INFO] Processing war project
> [INFO] Webapp assembled in [19 msecs]
> [INFO] Building war: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/deployments/ROOT.war
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 33.330s
> [INFO] Finished at: Tue Nov 27 11:27:40 EST 2012
> [INFO] Final Memory: 8M/169M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on project dw: Error assembling WAR: webxml attribute is required (or pre-existing WEB-INF/web.xml if executing in update mode) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> hot_deploy_added=false
> Found 127.3.36.1:8080 listening port
> /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
> Failed to start jbossas-7
> {code}
> Shouldn't this be a part of openshift maven profile?
> {code}
> <failOnMissingWebXml>false</failOnMissingWebXml>
> {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, 3 months
[JBoss JIRA] (JBIDE-14689) Application wizard: Investigate how to exclude .jsdtscope in .gitignore
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14689?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14689:
-------------------------------------
Summary: Application wizard: Investigate how to exclude .jsdtscope in .gitignore (was: Investigate how to exclude .jsdtscope in .gitignore)
Labels: application_wizard (was: )
Estimated Difficulty: Low
> Application wizard: Investigate how to exclude .jsdtscope in .gitignore
> -----------------------------------------------------------------------
>
> Key: JBIDE-14689
> URL: https://issues.jboss.org/browse/JBIDE-14689
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.x
>
>
> .settings/.jsdtscope is included in .gitignore by default as a prevention from JSDT errors.
> However this causes java applications imported from openshift to be still non synchronized after auto git push at the openshift application creation wizard end.
> Once the application is imported the .settings/.jsdtscope can be set in .gitignored to be actually ignored by git since the file is needed only in the eclipse workspace.
--
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, 3 months
[JBoss JIRA] (JBIDE-13162) Cannot deploy dynamic web project to OpenShift (WATCHER)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13162?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13162:
-------------------------------------
Assignee: (was: Andre Dietisheim)
> Cannot deploy dynamic web project to OpenShift (WATCHER)
> --------------------------------------------------------
>
> Key: JBIDE-13162
> URL: https://issues.jboss.org/browse/JBIDE-13162
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.0.0.CR1
> Reporter: Stefan Bunciak
> Fix For: 4.2.x
>
>
> Dynamic web project should should be deployable to OpenShift (is visible when merging OpenShift application and the workspace project).
> After publishing, following output is returned from server:
> {code}
> [INFO] Packaging webapp
> [INFO] Assembling webapp [dw] in [/var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/target/dw]
> [INFO] Processing war project
> [INFO] Webapp assembled in [19 msecs]
> [INFO] Building war: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/deployments/ROOT.war
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 33.330s
> [INFO] Finished at: Tue Nov 27 11:27:40 EST 2012
> [INFO] Final Memory: 8M/169M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on project dw: Error assembling WAR: webxml attribute is required (or pre-existing WEB-INF/web.xml if executing in update mode) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> hot_deploy_added=false
> Found 127.3.36.1:8080 listening port
> /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
> Failed to start jbossas-7
> {code}
> Shouldn't this be a part of openshift maven profile?
> {code}
> <failOnMissingWebXml>false</failOnMissingWebXml>
> {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, 3 months
[JBoss JIRA] (JBIDE-14850) Markers wizard: Restrict available markers depending on application type
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14850?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14850:
------------------------------------------
we were told that markers will get deprecated anyhow. So needs further investigation.
> Markers wizard: Restrict available markers depending on application type
> ------------------------------------------------------------------------
>
> Key: JBIDE-14850
> URL: https://issues.jboss.org/browse/JBIDE-14850
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Labels: markers_wizard
> Fix For: 4.2.x
>
>
> In JBIDE-14845 we allow users to add and remove markers. We dont filter the markers whether we have a java (jbossas, jbossews) or php, node, ruby etc. application even though some markers are specific to certain application types. We should tell the user what markers may make sense and suggest upon that.
--
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, 3 months
[JBoss JIRA] (JBIDE-15654) Application wizard: merge existing / new application forms into a single one
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15654?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15654:
-------------------------------------
Estimated Difficulty: Medium
> Application wizard: merge existing / new application forms into a single one
> ----------------------------------------------------------------------------
>
> Key: JBIDE-15654
> URL: https://issues.jboss.org/browse/JBIDE-15654
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.x
>
> Attachments: configure-application-wizard-page.png
>
>
> in the new / import application wizard the first page allows you to configure your app. It allows you to choose an existing or create a new app.
> !configure-application-wizard-page.png!
> Both forms should be merged into a single form in order to unclutter the current UI which is very crowded already.
--
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, 3 months