[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:
-------------------------------------------
Jeff - do we have some examples of kubernets.json or similar to show what we expect these to contain (at least for the jee cases?)
I think it would be much easier to discuss this with concrete examples.
> 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)
11 years, 2 months
[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3289:
-------------------------------------------
early access also affects our requirements for project examples etc.
Thus wether it is one on tab or another I would still prefer its from the software/update tab since that defines what is "installable".
Why is it that we can't simply check the connector id against the list of available connector ids ? if it is available to be installed we show the wizard and/or requirement but otherwise it gets ignored (no matter if earlyaccess is set or not as category ?) aren't the list of connector id's cached ?
> JBoss Central proxy wizards need to recognize early access.
> -----------------------------------------------------------
>
> Key: JBDS-3289
> URL: https://issues.jboss.org/browse/JBDS-3289
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.2.GA
> Reporter: Paul Leacu
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 8.0.2.GA
>
> Attachments: ea1.png
>
>
> Using a JBoss Central proxy wizard that references an early access feature will install that feature correctly even if the "Early Access Enabled" checkbox is unchecked.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18678) Make dependencies to org.jboss.tools.usage optional
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18678:
---------------------------------------------
requiring to update every feature we have is not exactly backwards compatible ;/
I thought the intent was that if the updatesite containts the usage plugin it will get installed, the third party would simply just exclude it from their updatesite? did that not work ?
> Make dependencies to org.jboss.tools.usage optional
> ---------------------------------------------------
>
> Key: JBIDE-18678
> URL: https://issues.jboss.org/browse/JBIDE-18678
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim, usage
> Affects Versions: 4.2.0.CR1
> Reporter: Kaloyan Raev
> Assignee: Alexey Kazakov
> Fix For: 4.3.x
>
>
> I am interested in adopting the CordovaSim feature in our product. However, most of the browsersim bundles have a strong dependency to org.jboss.tools.usage bundle, which force a Usage Reporting popup on startup. I want to avoid this and have the org.jboss.tools.usage excluded from my build.
> Is it possible to make the dependencies to org.jboss.tools.usage optional?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBTIS-295) utilize the tycho testing support for test bundles on JBTIS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-295?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-295:
-------------------------------------------
this jira was opened because Rob was asking/suggesting we found a way to test plugins against an installed eclipse or specific target platform instead of the default testing that for some of IS plugins uses their own TP.
Istria made that possible in tycho 0.19 thus I opened this jira to document and let IS (via Rob) look at if it would work for the testing needed.
I haven't heard anything back though ;/
It is still relevant I would say to try run the unit tests for each IS plugin against our TP as part of the validation of the release though and I think this could help make that possible.
> utilize the tycho testing support for test bundles on JBTIS
> -----------------------------------------------------------
>
> Key: JBTIS-295
> URL: https://issues.jboss.org/browse/JBTIS-295
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: testing
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Talking with [~rcernich] he was interested in doing testing of already packaged bundles on a packaged eclipse.
> [~mickael_istria] did this feature for tycho 0.19 documented at http://wiki.eclipse.org/Tycho/Release_Notes/0.19#Test_Execution
> [~rcernich] would this cover you intended use case ?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months