2:28 p.m.
OpenShift Express Use Case Scenarioo
------------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:11 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Burr Sutter updated JBIDE-10171:
--------------------------------
Summary: OpenShift Express Use Case Scenario (was: OpenShift Express Use Case
Scenarioo)
Description:
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
was:
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:48 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10171:
------------------------------------------
Both usecases require us to merge the openshift application with the local app the user
started with.
Forge did that by merging the local application with the OpenShift application overriding
remote changes with the local ones (see
https://github.com/forge/plugin-openshift-express/blob/master/src/main/ja...).
In the next step they then pushed the local app, that was merged, to OpenShift.
Another option would be to push (--force) the local app to OpenShift.
We had a lengthy discussion by mail and the last finding we had was the following approach
(proposed by Max):
{code}
git merge openshift/master -s recursive -X ours
# openshift/master will be the default to use but should be possible to change (i.e. rhc
uses origin/master by default)
git commit -a -m "deploy from JBoss OpenShift Tools"
# will have an option for skipping this step.
git push -f openshift/master
# same as in #1, but option for skipping -f (those that want to keep the history clean) ,
note yours say openshift HEAD, but I hope using same name as used in #1 is enough. If not
then that sucks
{code}
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:48 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10171 at 11/16/11 7:47 AM:
--------------------------------------------------------------------
Both usecases require us to merge the openshift application with the local app the user
started with.
Forge did that by merging the local application with the OpenShift application overriding
remote changes with the local ones (see
https://github.com/forge/plugin-openshift-express/blob/master/src/main/ja...).
In the next step they then pushed the local app, that was merged, to OpenShift.
Another option would be to push (--force) the local app to OpenShift.
We had a lengthy discussion by mail and the last finding we had was the following approach
(proposed by Max):
{code}
git merge openshift/master -s recursive -X ours
# openshift/master will be the default to use but should be possible to change (i.e. rhc
uses origin/master by default)
git commit -a -m "deploy from JBoss OpenShift Tools"
# will have an option for skipping this step.
git push -f openshift/master
# same as in #1, but option for skipping -f (those that want to keep the history clean) ,
note yours say openshift HEAD, but I hope using same name as used in #1 is enough. If not
then that sucks
{code}
was (Author: adietish):
Both usecases require us to merge the openshift application with the local app the
user started with.
Forge did that by merging the local application with the OpenShift application overriding
remote changes with the local ones (see
https://github.com/forge/plugin-openshift-express/blob/master/src/main/ja...).
In the next step they then pushed the local app, that was merged, to OpenShift.
Another option would be to push (--force) the local app to OpenShift.
We had a lengthy discussion by mail and the last finding we had was the following approach
(proposed by Max):
{code}
git merge openshift/master -s recursive -X ours
# openshift/master will be the default to use but should be possible to change (i.e. rhc
uses origin/master by default)
git commit -a -m "deploy from JBoss OpenShift Tools"
# will have an option for skipping this step.
git push -f openshift/master
# same as in #1, but option for skipping -f (those that want to keep the history clean) ,
note yours say openshift HEAD, but I hope using same name as used in #1 is enough. If not
then that sucks
{code}
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:49 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Burr Sutter commented on JBIDE-10171:
-------------------------------------
In the first scenario, what if we included the openshift profile in the archetypes?
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:34 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Pete Muir commented on JBIDE-10171:
-----------------------------------
I think you can skip the -f on the push if you want. It's going to make the experience
a bit less nice for newbies. There is a chance *they* screw up git -- not our merge -- and
thus their push will fail. It's going to make it better for people who want to keep
history there though (which with more development features like Jenkins is going to become
more prevalent).
Both usecases do require Eclipse to munge the POM to add the openshift profile. Is this
possible?
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:11 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10171:
------------------------------------------
according to fbricon modifying the pom is pretty easy, should be no problem at all.
For my own documentation sakes:
{code}
PomEdits#performOnDOMDocument()
{code}
and an example usage of it:
{code}
org.eclipse.m2e.core.ui.internal.actions.AddPluginAction
{code}
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:57 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Marius Bogoevici commented on JBIDE-10171:
------------------------------------------
Discussion from a separate e-mail thread: one way to address a part of this scenario for
archetypes would be to include the OpenShift profile in the archetype-generated projects
(with a possible switch to disable its inclusion, upon request).
This will make easy for developers to create projects that may deploy in OpenShift. Even
if it still requires copying the generated project into the Git repo of OpenShift, it
prevents users from actually tampering with the code in order to make it deployable, which
is a good thing, IMO.
There are a few extra things to be said about adding the profile to archetypes: it does
solve a part of the problem for newly generated projects and is IDE-independent (i.e. this
can be done in Netbeans, Intellij, command line, provided that the Git commit/push are
done manually). For existing projects, as well as dealing with the Git aspects of actually
running in OpenShift, tooling support would still be still necessary.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-10171:
----------------------------------------
Fix Version/s: 3.3.0.M5
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.M5
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:48 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10171:
------------------------------------------
time runs out for this issue. I'll try to provide a gapstopper that would provide the
following (discussed with max):
Provide a textfield that allows the user to provide a git-uri that shall be merged with
the OpenShift application.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.M5
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:12 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10171:
------------------------------------------
here's a preview of the UI that I want to offer.
!selectable-examples.png!
incompatible example chosen (application is jbossas-7.0, example is rack-1.1):
!not-compatible.png!
user provided url:
!merge-with-unknown.png!
@Max @Burr etc. please provide feedback.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.M5
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:14 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10171:
-------------------------------------
Attachment: selectable-examples.png
merge-with-unknown.png
not-compatible.png
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Pete Muir commented on JBIDE-10171:
-----------------------------------
I don't understand where the examples come into the workflow? The workflow I
understood was for a user to create an app using an archetype, and then to push to a new
openshift express appl...
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:41 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10171:
---------------------------------------------
Pete - its the suggested stopgap that can be implemented quickly as opposed to enabling
openshift generically on a project, should have been described in another jira and linked
as related to this.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:41 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10171:
------------------------------------------
what I did is not really fullfilling the usecase of this jira, it's just a gapstopper
since there were tremendous amounts of things to do in this iteration. I move the
"gapstopper" to its own jira, link it and move this issue to beta1.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:47 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10171:
---------------------------------------------
we are exploring options today - so hold tight ;)
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:36 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Pete Muir commented on JBIDE-10171:
-----------------------------------
Ok, but what is the user doing here? I still don't understand the workflow.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:51 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10171:
---------------------------------------------
Okey so here is the thing we came up with (its similar to what have been discussed
previously but "scoped" for M5 and then we can look at making things more easily
available after M5):
- In the OpenShift Wizard on its last page, we will add a way to optionally select *one*
existing project (<userproject>).
- If no userproject is specified the wizard behaves as it does now: git clone into a
directory, import that directory as a project.
- IF userproject is specified the wizard will do something similar to:
* cd <userproject>
* git init
* git add remote <remote-name> <openshift-app-url>
* git merge ... -X ours
This should bring that project in eclipse to look just the same as if it was an git cloned
project.
And it will work for all types of openshift apps.
For M5 the userproject:
- cannot have any existing Team providers (svn, egit, mecurial etc.) enabled on the
project.
- if there are any .git folders already in its root we probably won't handle that so
should check for that too and filter/warn if user chooses such a project.
- will not have pom.xml altered/checked for existence of 'openshift' profile for
AS7 style apps.
after M5 we should look at handling the addition of openshift profile to pom.xml etc.
plus also make this setup possibly to do directly from the context menu of the project.
WDYT?
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:51 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10171:
---------------------------------------------
note: if our archetypes/quickstarts etc. could get the "oppenshift" profile
predefined that would make this experience rather seamless then by M5.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:02 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Pete Muir commented on JBIDE-10171:
-----------------------------------
Sounds good. Assume this has nothing to do with examples as Andre's example did?
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:53 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10171:
---------------------------------------------
Andre's is now in JBIDE-10313, it was doing an attempt to at least be able to feed new
applications into the newly created openshift applications since at first run through it
was simpler than handling the full problem of existing projects. Thus it was looked into
as the best stopgap for M5.
It though turned out that the operations/code needed to do that is more or less exactly
the same to be able to provide the workflow I added above for "fresh new eclipse
projects" - so that is now what we are trying to get at since that usecase is more
important in merging from existing git projects.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:01 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Burr Sutter commented on JBIDE-10171:
-------------------------------------
Pete, can we get the openshift profile into all the archetypes?
If that is in place then it seems like this would allow the end-user to get started with
the HTML5 archetype, deploy to localhost:8080 and then turn around and deploy to openshift
without editing his pom.xml or figuring out a bunch of git setup.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:49 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Pete Muir commented on JBIDE-10171:
-----------------------------------
Burr, can you file an AS7 issue for this?
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:55 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Burr Sutter commented on JBIDE-10171:
-------------------------------------
Pete, https://issues.jboss.org/browse/AS7-2900
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Burr Sutter commented on JBIDE-10171:
-------------------------------------
"The example you've chosen is not compatible to your application"
should be
"The example you have chosen is not compatible with your OpenShift application"
- if that is in fact it correct meaning.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10171:
---------------------------------------------
turns out egit/jgit does not support recursive/OURS merge.
http://www.eclipse.org/forums/index.php/mv/msg/261278/753913/#msg_753913 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=354099
That leaves us in a bad place :(
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:29 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10171:
---------------------------------------------
latest idea:
cd tmp
git clone openshiftrepo;
cp -rn openshiftrepo fullpath/to/userproject; ## copy but do not overwrite existing
content
rm -rf openshiftrepo
cd fullpath/to/userproject;
git add -a
git commit -m "setup to openshift";
Maybe the cp could be reduced to just be first level directories to capture .openshift,
deployments, lib etc. for various openshift types ?
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:57 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10171:
------------------------------------------
just for documentation purposes: the bugzilla that is supposed to track recrusive merges
in jgit/egit is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=359951
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:17 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10171:
-------------------------------------
Attachment: import-exiting-project.patch
attached patch for the new approach. the ui is still not implemented. I took the shortest
path to the new approach so that we asap get an idea if that would work.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:20 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10171 at 12/5/11 6:20 PM:
-------------------------------------------------------------------
attached patch for the new approach. the ui is still not implemented. I took the shortest
path to the new approach so that we asap get an idea if that would work.
It pretty much looks like as if it works. I could push a dynamic web project (with seam
facet) and the seambooking example.
Currently you cannot just clone a git shared project and disconnect it. Disconnect in egit
does not remove the .git folder, it just deregisters the team provider. The recursive copy
I currently do will not overwrite the .git folder and seambooking then got reconnected to
its local clone. To nevertheless be able to check seambooking, I simply removed the .git
folder manually. I therefore guess that we should overwrite an existing .git folder when
copying.
was (Author: adietish):
attached patch for the new approach. the ui is still not implemented. I took the
shortest path to the new approach so that we asap get an idea if that would work.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:24 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10171:
------------------------------------------
I now implemented the following approach:
* checkbox "create new project" that is checked by default, which will allow you
to import the OpenShift Application to your workspace
* added a text field and a browse button that are enabled if you uncheck "create new
project"
* the browse button will allow you to choose among projects in your workspace. Valid
projects are
* not (team) shared
* has no .git folder
* is an Eclipse WTP project
* if the checkbox "create new project" is unchecked, you'll get the chosen
project "OpenShift enabled". I add the OpenShift configuration files
(.openshift, deployments, .git, pom.xml - No file is overwritten if it already exists),
connect it to a git repo and commit the files within the project.
* If you choose to "OpenShift enable" your existing project, you'll get
warning about the imminent modifications.
The missing corrections are the following:
* I should create (if it does not exist yet) a .gitignore file which will cover the
following items
* target
* .settings
* .project
* .classpath
* .factorypath
@Max: please review what's currently in trunk. The only item that is not there yet, is
the .gitignore file
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.M5
Attachments: import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:28 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10171:
-------------------------------------
Attachment: choose-existing-project.png
create-new-project.png
use-existing-project.png
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.M5
Attachments: choose-existing-project.png, create-new-project.png,
import-exiting-project.patch, merge-with-unknown.png, not-compatible.png,
selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:30 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10171 at 12/6/11 6:29 PM:
-------------------------------------------------------------------
I now implemented the following approach:
* checkbox "create new project" that is checked by default, which will allow you
to import the OpenShift Application to your workspace
!create-new-project.png!
* added a text field and a browse button that are enabled if you uncheck "create new
project"
!use-existing-project.png!
* the browse button will allow you to choose among projects in your workspace. Valid
projects are
* not (team) shared
* has no .git folder
* is an Eclipse WTP project
!choose-existing-project.png!
* if the checkbox "create new project" is unchecked, you'll get the chosen
project "OpenShift enabled". I add the OpenShift configuration files
(.openshift, deployments, .git, pom.xml - No file is overwritten if it already exists),
connect it to a git repo and commit the files within the project.
* If you choose to "OpenShift enable" your existing project, you'll get
warning about the imminent modifications.
The missing corrections are the following:
* I should create (if it does not exist yet) a .gitignore file which will cover the
following items
* target
* .settings
* .project
* .classpath
* .factorypath
@Max: please review what's currently in trunk. The only item that is not there yet, is
the .gitignore file
was (Author: adietish):
I now implemented the following approach:
* checkbox "create new project" that is checked by default, which will allow you
to import the OpenShift Application to your workspace
* added a text field and a browse button that are enabled if you uncheck "create new
project"
* the browse button will allow you to choose among projects in your workspace. Valid
projects are
* not (team) shared
* has no .git folder
* is an Eclipse WTP project
* if the checkbox "create new project" is unchecked, you'll get the chosen
project "OpenShift enabled". I add the OpenShift configuration files
(.openshift, deployments, .git, pom.xml - No file is overwritten if it already exists),
connect it to a git repo and commit the files within the project.
* If you choose to "OpenShift enable" your existing project, you'll get
warning about the imminent modifications.
The missing corrections are the following:
* I should create (if it does not exist yet) a .gitignore file which will cover the
following items
* target
* .settings
* .project
* .classpath
* .factorypath
@Max: please review what's currently in trunk. The only item that is not there yet, is
the .gitignore file
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.M5
Attachments: choose-existing-project.png, create-new-project.png,
import-exiting-project.patch, merge-with-unknown.png, not-compatible.png,
selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:30 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10171 at 12/6/11 6:30 PM:
-------------------------------------------------------------------
I now implemented the following approach:
* checkbox "create new project" that is checked by default, which will allow you
to import the OpenShift Application to your workspace
!create-new-project.png!
* added a text field and a browse button that are enabled if you uncheck "create new
project"
!use-existing-project.png!
* the browse button will allow you to choose among projects in your workspace. Valid
projects are
* not (team) shared
* has no .git folder
* is an Eclipse WTP project
!choose-existing-project.png!
* if the checkbox "create new project" is unchecked, you'll get the chosen
project "OpenShift enabled". I add the OpenShift configuration files
(.openshift, deployments, .git, pom.xml - No file is overwritten if it already exists),
connect it to a git repo and commit the files within the project.
* If you choose to "OpenShift enable" your existing project, you'll get
warning about the imminent modifications.
The missing corrections are the following:
* I should create (if it does not exist yet) a .gitignore file which will cover the
following items
* target
* .settings
* .project
* .classpath
* .factorypath
@Max: please review what's currently in trunk. The only item that is not there yet, is
the .gitignore file
was (Author: adietish):
I now implemented the following approach:
* checkbox "create new project" that is checked by default, which will allow you
to import the OpenShift Application to your workspace
!create-new-project.png!
* added a text field and a browse button that are enabled if you uncheck "create new
project"
!use-existing-project.png!
* the browse button will allow you to choose among projects in your workspace. Valid
projects are
* not (team) shared
* has no .git folder
* is an Eclipse WTP project
!choose-existing-project.png!
* if the checkbox "create new project" is unchecked, you'll get the chosen
project "OpenShift enabled". I add the OpenShift configuration files
(.openshift, deployments, .git, pom.xml - No file is overwritten if it already exists),
connect it to a git repo and commit the files within the project.
* If you choose to "OpenShift enable" your existing project, you'll get
warning about the imminent modifications.
The missing corrections are the following:
* I should create (if it does not exist yet) a .gitignore file which will cover the
following items
* target
* .settings
* .project
* .classpath
* .factorypath
@Max: please review what's currently in trunk. The only item that is not there yet, is
the .gitignore file
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: choose-existing-project.png, create-new-project.png,
import-exiting-project.patch, merge-with-unknown.png, not-compatible.png,
selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:30 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10171 at 12/6/11 6:30 PM:
-------------------------------------------------------------------
I now implemented the following approach:
* checkbox "create new project" that is checked by default, which will allow you
to import the OpenShift Application to your workspace
!create-new-project.png!
* added a text field and a browse button that are enabled if you uncheck "create new
project"
!use-existing-project.png!
* the browse button will allow you to choose among projects in your workspace. Valid
projects are
* not (team) shared
* has no .git folder
* is an Eclipse WTP project
!choose-existing-project.png!
* if the checkbox "create new project" is unchecked, you'll get the chosen
project "OpenShift enabled". I add the OpenShift configuration files
(.openshift, deployments, .git, pom.xml - No file is overwritten if it already exists),
connect it to a git repo and commit the files within the project.
* If you choose to "OpenShift enable" your existing project, you'll get
warning about the imminent modifications.
The missing corrections are the following:
* I should create (if it does not exist yet) a .gitignore file which will cover the
following items
- target
- .settings
- .project
- .classpath
- .factorypath
@Max: please review what's currently in trunk. The only item that is not there yet, is
the .gitignore file
was (Author: adietish):
I now implemented the following approach:
* checkbox "create new project" that is checked by default, which will allow you
to import the OpenShift Application to your workspace
!create-new-project.png!
* added a text field and a browse button that are enabled if you uncheck "create new
project"
!use-existing-project.png!
* the browse button will allow you to choose among projects in your workspace. Valid
projects are
* not (team) shared
* has no .git folder
* is an Eclipse WTP project
!choose-existing-project.png!
* if the checkbox "create new project" is unchecked, you'll get the chosen
project "OpenShift enabled". I add the OpenShift configuration files
(.openshift, deployments, .git, pom.xml - No file is overwritten if it already exists),
connect it to a git repo and commit the files within the project.
* If you choose to "OpenShift enable" your existing project, you'll get
warning about the imminent modifications.
The missing corrections are the following:
* I should create (if it does not exist yet) a .gitignore file which will cover the
following items
* target
* .settings
* .project
* .classpath
* .factorypath
@Max: please review what's currently in trunk. The only item that is not there yet, is
the .gitignore file
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: choose-existing-project.png, create-new-project.png,
import-exiting-project.patch, merge-with-unknown.png, not-compatible.png,
selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:32 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10171 at 12/6/11 6:31 PM:
-------------------------------------------------------------------
I now implemented the following approach:
* checkbox "create new project" that is checked by default, which will allow you
to import the OpenShift Application to your workspace
!create-new-project.png!
* added a text field and a browse button that are enabled if you uncheck "create new
project"
!use-existing-project.png!
* the browse button will allow you to choose among projects in your workspace. Valid
projects are
- not (team) shared
- has no .git folder
- is an Eclipse WTP project
!choose-existing-project.png!
* if the checkbox "create new project" is unchecked, you'll get the chosen
project "OpenShift enabled". I add the OpenShift configuration files
(.openshift, deployments, .git, pom.xml - No file is overwritten if it already exists),
connect it to a git repo and commit the files within the project.
* If you choose to "OpenShift enable" your existing project, you'll get
warning about the imminent modifications.
The missing corrections are the following:
* I should create (if it does not exist yet) a .gitignore file which will cover the
following items
- target
- .settings
- .project
- .classpath
- .factorypath
@Max: please review what's currently in trunk. The only item that is not there yet, is
the .gitignore file
was (Author: adietish):
I now implemented the following approach:
* checkbox "create new project" that is checked by default, which will allow you
to import the OpenShift Application to your workspace
!create-new-project.png!
* added a text field and a browse button that are enabled if you uncheck "create new
project"
!use-existing-project.png!
* the browse button will allow you to choose among projects in your workspace. Valid
projects are
* not (team) shared
* has no .git folder
* is an Eclipse WTP project
!choose-existing-project.png!
* if the checkbox "create new project" is unchecked, you'll get the chosen
project "OpenShift enabled". I add the OpenShift configuration files
(.openshift, deployments, .git, pom.xml - No file is overwritten if it already exists),
connect it to a git repo and commit the files within the project.
* If you choose to "OpenShift enable" your existing project, you'll get
warning about the imminent modifications.
The missing corrections are the following:
* I should create (if it does not exist yet) a .gitignore file which will cover the
following items
- target
- .settings
- .project
- .classpath
- .factorypath
@Max: please review what's currently in trunk. The only item that is not there yet, is
the .gitignore file
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: choose-existing-project.png, create-new-project.png,
import-exiting-project.patch, merge-with-unknown.png, not-compatible.png,
selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:20 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10171:
---------------------------------------------
For non-as7 projects the "Existing Project" label is still enabled.
Same goes when AS7 projects - here "existing project" is enabled even when the
checkbox is checked (text field and browse are correctly disabled)
The group "OpenShift JBoss Server Adapter" should just say "Server
Adapter", likewise the checkbox label should be consistent here and say
"OpenShift Server Adapter"
The word "shall" is still used in many places. The title is still saying
"project to enable".
"You have to select a project that shall be enabled..." -> "Select an
existing project to use with OpenShift"
"Confirm project modifcation"-dialog is different than discussed:
"Import OpenShift Application into <jayname>" "OpenShift Application
<jayname> will be enabled on project <yourproject> by copying OpenShift
configuration and enable Git for the project. This cannot be undone. Do you wish to
continue ? Yes | No"
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: choose-existing-project.png, create-new-project.png,
import-exiting-project.patch, merge-with-unknown.png, not-compatible.png,
selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:28 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10171:
------------------------------------------
fixed the issues.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: choose-existing-project.png, create-new-project.png,
import-exiting-project.patch, merge-with-unknown.png, not-compatible.png,
selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:50 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10171:
-------------------------------------
Attachment: import-existing-project2.patch
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10171:
------------------------------------------
the current implementation works and basically offers the requested functions.
Committed to TRUNK and M5.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim resolved JBIDE-10171.
--------------------------------------
Fix Version/s: 3.3.0.Beta1
Resolution: Done
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:28 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10171:
-------------------------------------
Labels: new_and_noteworthy (was: )
Release Notes Text: In M4 the JBoss Tools OpenShift wizard allowed you to check out
the OpenShift demo app that is created when you create a new OpenShift application on the
platform. M5 now offers you to push an Eclipse WTP ("Dynamic Web Project")
project from your workspace to an OpenShift application.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Labels: new_and_noteworthy
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:30 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10171:
-------------------------------------
Release Notes Text: In M4 the JBoss Tools OpenShift wizard allowed you to import the
OpenShift demo app (that is created when you create a new OpenShift application) to your
workspace. M5 now offers you to push an Eclipse WTP ("Dynamic Web Project")
project from your workspace to an OpenShift application. To do that you'd have to
uncheck "Create new project" and select the project (in your workspace) that
shall be pushed to OpenShift. (was: In M4 the JBoss Tools OpenShift wizard allowed you to
check out the OpenShift demo app that is created when you create a new OpenShift
application on the platform. M5 now offers you to push an Eclipse WTP ("Dynamic Web
Project") project from your workspace to an OpenShift application.)
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Labels: new_and_noteworthy
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:17 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10171:
---------------------------------------------
The remote files are not removed until you actually push the changes.
You can as a user git to do all the magic merges you want to do - not something we will
do. We warn users that we are changing the *local* project - not sure if we need more ?
btw. please open new issues for new things/improvement instead of on this issue please.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Labels: new_and_noteworthy
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:54 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10171:
------------------------------------------
@Lucia:
I see several interesting suggestions in your comment. Please file new issues for each of
them that seems like a real annoyance to you.
This jira was about bringing a first version of that usecase to the users - within the
limited time we had for the M5 release.
Furthermore we already code freezed, so we'll only (re)open issues for M5 that really
are blockers.
So if the the basic usecase in this issue is fullfilled (even if you think that it's
not ideal), please confirm this issue and close it.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Labels: new_and_noteworthy
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:56 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim resolved JBIDE-10171.
--------------------------------------
Resolution: Done
Closing this issue since there are no blockers that would have to be fixed within M5.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Labels: new_and_noteworthy
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:56 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10171 at 12/16/11 9:55 AM:
--------------------------------------------------------------------
Resolving this issue again, since there are no blockers that would have to be fixed within
M5.
was (Author: adietish):
Closing this issue since there are no blockers that would have to be fixed within M5.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Labels: new_and_noteworthy
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:31 p.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10171 at 12/16/11 3:31 PM:
--------------------------------------------------------------------
@Lucia:
I see several interesting suggestions in your comment. Please file new issues for each of
them that seem like a real annoyance to you.
This jira was about bringing a first version of that usecase to the users - within the
limited time we had for the M5 release.
Furthermore we already code freezed, so we'll only (re)open issues for M5 that are
blockers/need to be fixed.
So if the the basic usecase in this issue is fullfilled (even if you think that it's
not ideal), please confirm and close this issue.
was (Author: adietish):
@Lucia:
I see several interesting suggestions in your comment. Please file new issues for each of
them that seems like a real annoyance to you.
This jira was about bringing a first version of that usecase to the users - within the
limited time we had for the M5 release.
Furthermore we already code freezed, so we'll only (re)open issues for M5 that really
are blockers.
So if the the basic usecase in this issue is fullfilled (even if you think that it's
not ideal), please confirm this issue and close it.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Labels: new_and_noteworthy
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:54 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Lucia Jelinkova closed JBIDE-10171.
-----------------------------------
Yes, the basic use case works fine, closing the issue.
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Labels: new_and_noteworthy
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:04 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Isaac Rooskov updated JBIDE-10171:
----------------------------------
Release Notes Docs Status: Not Required
Writer: irooskov
This feature request does not need to be documented as the entire OpenShift tooling module
is new for this release
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Labels: new_and_noteworthy
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:09 a.m.
New subject: [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Isaac Rooskov closed JBIDE-10171.
---------------------------------
Resolution: Done
Re-closing issue as release note flag has now been set
OpenShift Express Use Case Scenario
-----------------------------------
Key: JBIDE-10171
URL: https://issues.jboss.org/browse/JBIDE-10171
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Priority: Critical
Labels: new_and_noteworthy
Fix For: 3.3.0.Beta1, 3.3.0.M5
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.png
Here is the workflow:
1) User starts with one of the 4 key archetypes (ee6 war, ee6 ear, springmvc, html5) to
create a default application
2) deploys that app to a local JBoss instance to manually test
3) user sets up a New Server attached to an application at OpenShift Express
4) User now deploys the project created in step 1 above to the openshift express server
And a related workflow:
1) User imports a pre-existing Maven project
2) Adjusts his dependencies for JBoss AS deployment
3) deploys and tests on a localhost version of JBoss AS7
4) Configures a OpenShift Server in the Servers tab
5) Deploys to Openshift
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4473
days inactive
4613
days old
jbosstools-issues@lists.jboss.org
50 comments
13 participants
participants (13)
-
Andre Dietisheim (Commented) (JIRA) -
Andre Dietisheim (Issue Comment Edited) (JIRA)
-
Andre Dietisheim (Resolved) (JIRA)
-
Andre Dietisheim (Updated) (JIRA)
-
Burr Sutter (Commented) (JIRA)
-
Burr Sutter (Created) (JIRA)
-
Burr Sutter (Updated) (JIRA)
-
Isaac Rooskov (JIRA)
-
Lucia Jelinkova (Closed) (JIRA)
-
Marius Bogoevici (Commented) (JIRA)
-
Max Rydahl Andersen (Commented) (JIRA)
-
Max Rydahl Andersen (Updated) (JIRA)
-
Pete Muir (Commented) (JIRA)