[JBoss JIRA] (JBIDE-11129) Switch application Properties view to 'Tabbed Properties' view
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11129?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-11129.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Switch application Properties view to 'Tabbed Properties' view
> --------------------------------------------------------------
>
> Key: JBIDE-11129
> URL: https://issues.jboss.org/browse/JBIDE-11129
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Stefan Bunciak
> Labels: properties
> Fix For: LATER
>
> Attachments: appprops.png, appselection.png
>
>
> Switch application Properties view to 'Tabbed Properties' view to support hypertext links in the application properties (accessible via OpenShift Console view):
> * !appprops.png|thumbnail!
> like in the Existing application selection dialog
> * !appselection.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-13723) Application wizard: "uncommitted changes" when merging ticket-monster with OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13723?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-13723.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Application wizard: "uncommitted changes" when merging ticket-monster with OpenShift application
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13723
> URL: https://issues.jboss.org/browse/JBIDE-13723
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Labels: application_wizard
> Fix For: LATER
>
> Attachments: out.ogv, uncommitted-changes.png
>
>
> OpenShift wizard shows an error dialog with "Could not import project to the workspace." message:
> {code}
> org.jboss.tools.openshift.express.internal.ui.UnCommittedChangesException: The project ticket-monster has uncommitted changes. Please commit those changes first.
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.ConfigureGitSharedProject.execute(ConfigureGitSharedProject.java:101)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftExpressApplicationWizardModel.configureGitSharedProject(OpenShiftExpressApplicationWizardModel.java:158)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftExpressApplicationWizard$ImportJob.runInWorkspace(OpenShiftExpressApplicationWizard.java:319)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> Although git status says there nothing to commit:
> {code}
> [sbunciak@dhcp-27-195 ticket-monster]$ git status
> # On branch master
> nothing to commit (working directory clean)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12121) Application wizard: the openshift profile is added to newly created maven projects, regardless of their packaging type
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12121?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-12121.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Application wizard: the openshift profile is added to newly created maven projects, regardless of their packaging type
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12121
> URL: https://issues.jboss.org/browse/JBIDE-12121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Fred Bricon
> Labels: application_wizard
> Fix For: LATER
>
> Attachments: new-openarchetype-project-2.png, new-openarchetype-project.png
>
>
> I created a project using the org.openarchetypes:multi-javaee6-archetype:0.0.1-SNAPSHOT from http://open-archetypes.github.com/maven-repo/snapshots/archetype-catalog.xml (Maven > Archetypes > Add Remote Catalog)
> This creates a multi module project, containing a parent pom, an ear, war, ejb and utility projects. This openshift profile was added to the pom project :
> {code:xml}
> <profiles>
> <profile>
> <!-- When built in OpenShift the openshift profile will be used when invoking mvn. -->
> <!-- Use this profile for any OpenShift specific customization your app will need. -->
> <!-- By default that is to put the resulting archive into the deployments folder. -->
> <!-- http://maven.apache.org/guides/mini/guide-building-for-different-environm... -->
> <id>openshift</id>
> <build>
> <finalName>hello</finalName>
> <plugins>
> <plugin>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.1.1</version>
> <configuration>
> <outputDirectory>deployments</outputDirectory>
> <warName>ROOT</warName>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </profile>
> {code}
> Actually, it should :
> - check the packaging type of *all* the generated projects
> - if some EARs are found, then add the following to the parent pom (pay attention to the <pluginManagement> section) :
> {code:xml}
> <profile>
> <id>openshift</id>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.7</version>
> <configuration>
> <outputDirectory>deployments</outputDirectory>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
> </build>
> </profile>
> {code}
> - if there are no EARs but some WARs are found (count them), then add the following to the parent pom (pay attention to the <pluginManagement> section) :
> {code:xml}
> <profiles>
> <profile>
> <id>openshift</id>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.2</version>
> <configuration>
> <outputDirectory>deployments</outputDirectory>
> <!-- Add warName ROOT ONLY if there's ONE War, otherwise, skip it -->
> <warName>ROOT</warName>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
> </build>
> </profile>
> {code}
> The finalName is irrelevant to openshift, only the warName counts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-13162) Server adapter: Cannot deploy dynamic web project to OpenShift without a web.xml
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13162?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-13162.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Server adapter: Cannot deploy dynamic web project to OpenShift without a web.xml
> --------------------------------------------------------------------------------
>
> Key: JBIDE-13162
> URL: https://issues.jboss.org/browse/JBIDE-13162
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift, upstream
> Affects Versions: 4.0.0.CR1
> Reporter: Stefan Bunciak
> Labels: server_adapter
> Fix For: LATER
>
>
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-16444) Connection wizard: save accepted certificates in the Eclipse preferences and allow users to inspect/revoke them
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16444?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-16444.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Connection wizard: save accepted certificates in the Eclipse preferences and allow users to inspect/revoke them
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16444
> URL: https://issues.jboss.org/browse/JBIDE-16444
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Andre Dietisheim
> Labels: connection_wizard
> Fix For: LATER
>
> Attachments: accept-certificate.png
>
>
> In JBIDE-14768 we introduced a dialog that allows users to accept/refuse untrusted SSL certificates.
> !accept-certificate.png!
> The authorization is currently stored for the current Eclipse session. We should store those authorizations in the Eclipse preferences and add a preferences page which shows these and allows users to revoke the given authorizations.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-15495) Server Adapter: publish locks the whole workspace
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-15495.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Server Adapter: publish locks the whole workspace
> -------------------------------------------------
>
> Key: JBIDE-15495
> URL: https://issues.jboss.org/browse/JBIDE-15495
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Labels: server_adapter
> Fix For: LATER
>
> Attachments: Screen Shot 2013-09-17 at 10.42.43 AM.png
>
>
> Have 2 projects in a workspace, one of them is an OpenShift application
> Deploy some changes on OpenShift, and while the publication is performed (git push, then OS restarts the server), go to the second (unrelated) project and try to move a file from a package to another package in the same project.
> The 'Publish' operation locked the whoel workspace, which means that the move operation needs to wait.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-16108) Preferences: Timeout preferences should not set system properties but operation specific timeout
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16108?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-16108.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Preferences: Timeout preferences should not set system properties but operation specific timeout
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16108
> URL: https://issues.jboss.org/browse/JBIDE-16108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Labels: preferences
> Fix For: LATER
>
>
> In JBIDE-16046 we introduced an Eclipse Preferences to set the openshift-java-clilent timeouts. These preferences currently set the lib specific system property which is not good. Consider the following usecase:
> 1) User launches Eclipse and has system property set to 10000 (-D): Eclipse Preferences display 10000
> 2) User sets preference to 1234
> 3) restarts Ecllipse: Preferences display 1234
> 3) happens because we load the value from eclipse preferences and override the system property
> We should keep both separate: System property and Eclipse preferences:
> We use operation specific timeouts in all Eclipse code and make the Eclipse preferences provide some value for this. Leaving the system property alone.
> We should also:
> * add a checkbox for "[ ] use default"
> * change openshift-java-client to differentiate "no value" (<0) and value set (>=0)
> * remove current hard-coded safe default in openshift-java-client, replace it by system-property we already have).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-16885) Embed wizard: Can provide "Code Anything" without url, should not be able to
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16885?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-16885.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Embed wizard: Can provide "Code Anything" without url, should not be able to
> ----------------------------------------------------------------------------
>
> Key: JBIDE-16885
> URL: https://issues.jboss.org/browse/JBIDE-16885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Reporter: Marián Labuda
> Labels: embed_wizard
> Fix For: LATER
>
> Attachments: wrong_button_accessibility.png, wrong_button_accessibility.png, wrong_button_accessibility2.png, wrong_button_accessibility2.png
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> In the wizard to edit the embeddable cartridges there is "Code Anything" cartridge which requires URL of cartridge. If user just selects and does not check this cartridge, it is not possible to hit the OK button (see attached screen wrong_button_accessibility).
> Also if user check this cartridge but select another one without providing URL to the Code anything cartridge, it is possible to hit the OK button (it should not be - see attached screenshot wrong_button_accessibility2.)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months