[JBoss JIRA] (JBDS-3305) Support OpenShift v2
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBDS-3305:
-----------------------------------------
Summary: Support OpenShift v2
Key: JBDS-3305
URL: https://issues.jboss.org/browse/JBDS-3305
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
OpenShift v2 is online and supported and needs to be maintained/updated.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBDS-3278) OpenShift v3
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3278?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen closed JBDS-3278.
-------------------------------------
Resolution: Duplicate Issue
Duplicates the Epic JBDS-3250 where overall topics/issues should be commented/linked to instead.
> OpenShift v3
> ------------
>
> Key: JBDS-3278
> URL: https://issues.jboss.org/browse/JBDS-3278
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Jeff Cantrill
> Fix For: 9.0.0.GA
>
> Attachments: OS Explorer Options.bmml, OS Explorer Options.bmml, OS Explorer Options.bmml, OS Explorer Options.bmml, OS Explorer Options.bmml, OS Explorer Options.png
>
>
> As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
> The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
> For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
> {quote}
> It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
> Our Eclipse end-user needs to be able to “browse” for it and select it
> git clone it
> make changes
> git push it back
> {quote}
> This gives us 3 main use cases (as in mail and chats):
> # Import existing OpenShift project (JBDS-3297)
> # Push Changes to Existing OpenShift project (JBDS-3298)
> # New Project from Template (template should have a default buildconfig, deployconfig and docker image)
> {quote}
> Use Case #1 assumes a TON about what has happened before me.
> - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL
> - Assumes end-user is already logged in (there is no auth method at this time)
> - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc.
> {quote}
> We have a more extensive document that outlines the usecases:
> https://docs.google.com/a/redhat.com/document/d/1VwYNuKWUzuorU-6GcF420Vl_...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen edited comment on JBDS-3298 at 1/6/15 4:54 AM:
-------------------------------------------------------------------
I: this is the user waiting, and dependent on the setup - I guess you mean the user will have to refresh the explorer to see the status of a buildconfig or something ?
J: I don't know where this url comes from. This is what is needed for show in browser that is on JBDS-3278 and listed as not planned ...this info about url is just not present or derivable in v3 in current state.
was (Author: maxandersen):
I: this is the user waiting, and dependent on the setup.
J: I don't know where this url comes from. This is what is needed for show in browser that is on JBDS-3278 and listed as not planned ...this info about url is just not present or derivable in v3 in current state.
> Push changes to Existing OpenShift Project
> ------------------------------------------
>
> Key: JBDS-3298
> URL: https://issues.jboss.org/browse/JBDS-3298
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
>
> Use Case #2 Push changes to Existing OpenShift Project
> a) assumes the steps in Use Case #1 JBDS-3297
> b) assumes the end-user has uploaded his SSH keys (to allow for git push)
> c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc
> d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP
> e) Eclipse user will test (JUnit, Arquillian)
> f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image)
> g) Eclipse user will git add and git commit as appropriate
> h) Eclipse user will git push to the original URL provided in Use Case #1
> i) Eclipse user will await the automatic rebuild of a new image, deployment of the same
> j) Eclipse user will then be provided a URL and the browser can be opened automatically
> Note:
> i) auto-build=true, auto-deploy=true
> assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c.
> A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear.
> If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen edited comment on JBDS-3298 at 1/6/15 4:52 AM:
-------------------------------------------------------------------
I: this is the user waiting, and dependent on the setup.
J: I don't know where this url comes from. This is what is needed for show in browser that is on JBDS-3278 and listed as not planned ...this info about url is just not present or derivable in v3 in current state.
was (Author: maxandersen):
I: this is the user waiting, and dependent on the setup.
J: I don't know where this url comes from. this is what is needed for show in browser that is on JBDS-3278 ...this info is just not present or derivable in v3 in current state.
> Push changes to Existing OpenShift Project
> ------------------------------------------
>
> Key: JBDS-3298
> URL: https://issues.jboss.org/browse/JBDS-3298
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
>
> Use Case #2 Push changes to Existing OpenShift Project
> a) assumes the steps in Use Case #1 JBDS-3297
> b) assumes the end-user has uploaded his SSH keys (to allow for git push)
> c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc
> d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP
> e) Eclipse user will test (JUnit, Arquillian)
> f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image)
> g) Eclipse user will git add and git commit as appropriate
> h) Eclipse user will git push to the original URL provided in Use Case #1
> i) Eclipse user will await the automatic rebuild of a new image, deployment of the same
> j) Eclipse user will then be provided a URL and the browser can be opened automatically
> Note:
> i) auto-build=true, auto-deploy=true
> assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c.
> A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear.
> If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3298:
-------------------------------------------
I: this is the user waiting, and dependent on the setup.
J: I don't know where this url comes from. this is what is needed for show in browser that is on JBDS-3278 ...this info is just not present or derivable in v3 in current state.
> Push changes to Existing OpenShift Project
> ------------------------------------------
>
> Key: JBDS-3298
> URL: https://issues.jboss.org/browse/JBDS-3298
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
>
> Use Case #2 Push changes to Existing OpenShift Project
> a) assumes the steps in Use Case #1 JBDS-3297
> b) assumes the end-user has uploaded his SSH keys (to allow for git push)
> c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc
> d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP
> e) Eclipse user will test (JUnit, Arquillian)
> f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image)
> g) Eclipse user will git add and git commit as appropriate
> h) Eclipse user will git push to the original URL provided in Use Case #1
> i) Eclipse user will await the automatic rebuild of a new image, deployment of the same
> j) Eclipse user will then be provided a URL and the browser can be opened automatically
> Note:
> i) auto-build=true, auto-deploy=true
> assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c.
> A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear.
> If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-15135:
----------------------------------------
The current scripts don't provide resolved values for the properties, and just give values of environments variables (that might be propagated to Maven as system properties). Current implementation of the Mojo gives the System Properties, so it's almost equivalent to current script.
Having resolved values could be an improvement when we start using the mojo, but it's not a blocker for adoption.
I updated commit on my local branch to include java.vendor/java.version/os.name/os.version/os.arch.
> Attach metadata during assembly instead of publish time
> -------------------------------------------------------
>
> Key: JBIDE-15135
> URL: https://issues.jboss.org/browse/JBIDE-15135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.x
>
>
> In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site.
> Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBIDE-18995) Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18995:
----------------------------------------
Well, if Arquillian is actually EA, then it means that we probably need to rebuild the aggregation site. Deciding whether a feature is EA or not is not only a matter of label. We should ask [~maxandersen] about whether it is ok to make Arquillian non-Early Access in JBT 4.2.1.
> Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18995
> URL: https://issues.jboss.org/browse/JBIDE-18995
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.2.1.Final
> Reporter: Denis Golovin
> Assignee: Mickael Istria
> Priority: Minor
> Attachments: ea-disabled.png, ea-installed.png
>
>
> I noticed central has "(Early Access Installed)" sign in after I installed everything from JBos Tools stable p2 repository.
> !ea-installed.png!
> "Enable Early Access" checkbox is not set by default in Central Editor
> !ea-disabled.png!
> This means I bypassed warning dialog in this scenario.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBIDE-14783) Licence for JBoss AS Downloads looks like HTML source
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14783?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-14783.
---------------------------------
Assignee: Rob Stryker (was: Snjezana Peco)
Fix Version/s: 4.2.2.Final
4.3.0.Alpha1
(was: 4.2.x)
Resolution: Done
Linked issue is solved. This is solved for all versions of jbt now with 0 commits in our repos.
> Licence for JBoss AS Downloads looks like HTML source
> -----------------------------------------------------
>
> Key: JBIDE-14783
> URL: https://issues.jboss.org/browse/JBIDE-14783
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.1.0.Beta1
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.2.Final, 4.3.0.Alpha1
>
> Attachments: license-3.2.8.SP1.png
>
>
> When JBoss AS 3.2.8.SP1 download is requested from new Runtime Dialog it shows license that looke like this:
> !license-3.2.8.SP1.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months