[JBoss JIRA] (JBIDE-16714) Embed wizard, Application wizard: Embed same cartridge with different version should show warning
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16714?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16714:
-------------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Embed wizard, Application wizard: Embed same cartridge with different version should show warning
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16714
> URL: https://issues.jboss.org/browse/JBIDE-16714
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: application_wizard, embed_wizard
> Fix For: LATER
>
>
> Nowadays, when on OpenShift Online are available multiple cartridges differentiated only by version (e.g. PostgreSQL 8.4 and 9.2) there should be some kind of warning about embedding both (what could happen accidentally or by ignorance...).
> How it works now? If user choose 2 cartridges of the same type, then just the first one is embedded and while trying to embed second cartridge user get error that application has already embedded that kind of cartridge (that they cannot coexist).
> I suggest to have similar dialog as in embedding e.g. Jenkins cartridge to application without having Jenkins Application (server) etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-16714) Embed wizard, Application wizard: Embed same cartridge with different version should show warning
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16714?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16714:
------------------------------------------
setting fixVersion to LATER since the main focus now is to create tooling for OpenShift v3.
> Embed wizard, Application wizard: Embed same cartridge with different version should show warning
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16714
> URL: https://issues.jboss.org/browse/JBIDE-16714
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: application_wizard, embed_wizard
> Fix For: LATER
>
>
> Nowadays, when on OpenShift Online are available multiple cartridges differentiated only by version (e.g. PostgreSQL 8.4 and 9.2) there should be some kind of warning about embedding both (what could happen accidentally or by ignorance...).
> How it works now? If user choose 2 cartridges of the same type, then just the first one is embedded and while trying to embed second cartridge user get error that application has already embedded that kind of cartridge (that they cannot coexist).
> I suggest to have similar dialog as in embedding e.g. Jenkins cartridge to application without having Jenkins Application (server) etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19008) As a user, I want to delete OpenShift resources
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19008?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19008:
-------------------------------------
Description:
We should allow users to remove OpenShift v3 resources.
Beside the primary usecase there's an additional requirement: If you submit several resource creations in 1 config/file the backend might stop processing right in the middle, the operation is not transactional. We therefore need to allow the user to clean up
was:OpenShift v3 resource creation operations are not atomic. If you submit several ones in 1 config/list it might happen that
> As a user, I want to delete OpenShift resources
> -----------------------------------------------
>
> Key: JBIDE-19008
> URL: https://issues.jboss.org/browse/JBIDE-19008
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.0.Beta1
>
>
> We should allow users to remove OpenShift v3 resources.
> Beside the primary usecase there's an additional requirement: If you submit several resource creations in 1 config/file the backend might stop processing right in the middle, the operation is not transactional. We therefore need to allow the user to clean up
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-11367) Application wizard should close and run maven import in background once the application was created
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11367:
-------------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.Alpha1)
> Application wizard should close and run maven import in background once the application was created
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11367
> URL: https://issues.jboss.org/browse/JBIDE-11367
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Xavier Coulon
> Labels: application_wizard
> Fix For: 4.3.x
>
>
> After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen.
> We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-13922) OpenShift "Secure Storage" dialog in infinite loop of prompting
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13922?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13922:
-------------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> OpenShift "Secure Storage" dialog in infinite loop of prompting
> ---------------------------------------------------------------
>
> Key: JBIDE-13922
> URL: https://issues.jboss.org/browse/JBIDE-13922
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Environment: Fedora 18
> Reporter: R Searls
> Priority: Minor
> Fix For: LATER
>
>
> Running : JBoss Developer Studio
> version:6.0.1.GA
> Build id:GA-v20130327-2052-B361
> OS: Fedora 18
> When creating a new OpenShift App in the "New OpenShift Application" dialog
> I type in my password, (I have an existing account.) and select the checkbox,
> "Save password (could trigger storage login)" and click next. The " Secure
> Storage" dialog displays. I click the cancel button. Each time I click cancel
> in this dialog, the dialog closes and pops back open. It's in an infinit loop.
> I must kill the app to get out of this cycle.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-13922) OpenShift "Secure Storage" dialog in infinite loop of prompting
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13922?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13922:
------------------------------------------
setting fixVersion to LATER since the main focus now is to create tooling for OpenShift v3.
> OpenShift "Secure Storage" dialog in infinite loop of prompting
> ---------------------------------------------------------------
>
> Key: JBIDE-13922
> URL: https://issues.jboss.org/browse/JBIDE-13922
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Environment: Fedora 18
> Reporter: R Searls
> Priority: Minor
> Fix For: LATER
>
>
> Running : JBoss Developer Studio
> version:6.0.1.GA
> Build id:GA-v20130327-2052-B361
> OS: Fedora 18
> When creating a new OpenShift App in the "New OpenShift Application" dialog
> I type in my password, (I have an existing account.) and select the checkbox,
> "Save password (could trigger storage login)" and click next. The " Secure
> Storage" dialog displays. I click the cancel button. Each time I click cancel
> in this dialog, the dialog closes and pops back open. It's in an infinit loop.
> I must kill the app to get out of this cycle.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-12121) Application wizard: the openshift profile is added to newly created maven projects, regardless of their packaging type
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12121?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12121:
-------------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> 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.11#6341)
11 years, 3 months