[JBoss JIRA] (JBIDE-19411) early access install has no cancel button for p2 remediation
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19411?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19411:
------------------------------------
If you create a project in JIRA called communication-breakdown, I'll open a ticket there instead. :P
But since we don't have a place to log communication problems, we just track them ad hoc here and in mailing lists. :D
> early access install has no cancel button for p2 remediation
> ------------------------------------------------------------
>
> Key: JBIDE-19411
> URL: https://issues.jboss.org/browse/JBIDE-19411
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.Alpha2
>
>
> installing angularjs from earlyaccess from nightly build currently results in p2 remediation - which then just blocks all UI and cannot be cancelled.
> normal p2 remediation UI can be cancelled.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3264) Remove welcome/intro page
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3264?page=com.atlassian.jira.plugin.... ]
Mickael Istria updated JBDS-3264:
---------------------------------
Priority: Optional (was: Major)
> Remove welcome/intro page
> -------------------------
>
> Key: JBDS-3264
> URL: https://issues.jboss.org/browse/JBDS-3264
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: ui/branding
> Affects Versions: 8.0.0.GA
> Reporter: Mickael Istria
> Priority: Optional
> Fix For: 9.0.0.Beta1
>
>
> The welcome page for JBDS is really useless. It doesn't provide any value to the user. Moreover, it looks quite old-fashioned.
> In such case, it would be better to remove it and prevent users from seeing it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3264) Remove welcome/intro page
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3264?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3264:
--------------------------------------
IMO, it's a bad thing to show such a useless page. And branding is not a good reason for annoying user with yet another click.
However, that's only my opinion and it's a minor issue, you may want to run a poll.
> Remove welcome/intro page
> -------------------------
>
> Key: JBDS-3264
> URL: https://issues.jboss.org/browse/JBDS-3264
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: ui/branding
> Affects Versions: 8.0.0.GA
> Reporter: Mickael Istria
> Priority: Optional
> Fix For: 9.0.0.Beta1
>
>
> The welcome page for JBDS is really useless. It doesn't provide any value to the user. Moreover, it looks quite old-fashioned.
> In such case, it would be better to remove it and prevent users from seeing it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16128:
----------------------------------------
{quote}a proper way to do this would be to stop having to branch for each milestone and simply have a build/release cut by a developer to get fed into the build. That would work, right ?{quote}
Yes, avoiding to avoid several active branch with the same version would allow to use Nexus. This pattern of branching a still active branch to do a milestone is what prevents Nexus to work for us.
{quote}Just trying to figure out why so many are happy with the nexus zip publishing but for some reason it does not work for us. {quote}
Those projects don't have 2 branches with the same version, and prefer a tag-after based approach rather than a branch-before model.
> Publish component sites to Nexus
> --------------------------------
>
> Key: JBIDE-16128
> URL: https://issues.jboss.org/browse/JBIDE-16128
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Optional
> Fix For: 4.3.x
>
> Attachments: deployWithJenkins.png
>
>
> In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus.
> Then we'll see what are the pros/cons of this approach.
> Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3317) Basic Docker support
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3317?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3317:
-------------------------------
CDW docs_ack: + (was: ?)
> Basic Docker support
> --------------------
>
> Key: JBDS-3317
> URL: https://issues.jboss.org/browse/JBDS-3317
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: openshift, requirements
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.0.0.Beta1
>
>
> Basic docker support is to provide the following Docker features:
> * pull/add images from registry
> * list images
> * list containers
> * start containers from an image
> * stop/restart/kill containers
> * connect/disconnect from containers to show log/provide interactive console/terminal
> * build dockerfile (available via right click on DockerFile / project / file with DockerFile - this should support .dockerignore)
> * filter image/containers
> * provide details for image/containers
> * during launch be able to mount volumes, port forwards etc. in a simple UI (leave more advanced details to separate pages/different ui)
> * provide API for other tooling in eclipse to use it (like server launches etc.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3317) Basic Docker support
by Jiri Pallich (JIRA)
[ https://issues.jboss.org/browse/JBDS-3317?page=com.atlassian.jira.plugin.... ]
Jiri Pallich commented on JBDS-3317:
------------------------------------
Acked on behalf of [~burrsutter].
> Basic Docker support
> --------------------
>
> Key: JBDS-3317
> URL: https://issues.jboss.org/browse/JBDS-3317
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: openshift, requirements
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.0.0.Beta1
>
>
> Basic docker support is to provide the following Docker features:
> * pull/add images from registry
> * list images
> * list containers
> * start containers from an image
> * stop/restart/kill containers
> * connect/disconnect from containers to show log/provide interactive console/terminal
> * build dockerfile (available via right click on DockerFile / project / file with DockerFile - this should support .dockerignore)
> * filter image/containers
> * provide details for image/containers
> * during launch be able to mount volumes, port forwards etc. in a simple UI (leave more advanced details to separate pages/different ui)
> * provide API for other tooling in eclipse to use it (like server launches etc.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3317) Basic Docker support
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3317?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3317:
-----------------------------
CDW docs_ack: ?
CDW devel_ack: ?
CDW qa_ack: ?
> Basic Docker support
> --------------------
>
> Key: JBDS-3317
> URL: https://issues.jboss.org/browse/JBDS-3317
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: openshift, requirements
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.0.0.Beta1
>
>
> Basic docker support is to provide the following Docker features:
> * pull/add images from registry
> * list images
> * list containers
> * start containers from an image
> * stop/restart/kill containers
> * connect/disconnect from containers to show log/provide interactive console/terminal
> * build dockerfile (available via right click on DockerFile / project / file with DockerFile - this should support .dockerignore)
> * filter image/containers
> * provide details for image/containers
> * during launch be able to mount volumes, port forwards etc. in a simple UI (leave more advanced details to separate pages/different ui)
> * provide API for other tooling in eclipse to use it (like server launches etc.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3317) Basic Docker support
by Jiri Pallich (JIRA)
[ https://issues.jboss.org/browse/JBDS-3317?page=com.atlassian.jira.plugin.... ]
Jiri Pallich updated JBDS-3317:
-------------------------------
CDW pm_ack: + (was: ?)
Status: New (was: New)
> Basic Docker support
> --------------------
>
> Key: JBDS-3317
> URL: https://issues.jboss.org/browse/JBDS-3317
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: openshift, requirements
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.0.0.Beta1
>
>
> Basic docker support is to provide the following Docker features:
> * pull/add images from registry
> * list images
> * list containers
> * start containers from an image
> * stop/restart/kill containers
> * connect/disconnect from containers to show log/provide interactive console/terminal
> * build dockerfile (available via right click on DockerFile / project / file with DockerFile - this should support .dockerignore)
> * filter image/containers
> * provide details for image/containers
> * during launch be able to mount volumes, port forwards etc. in a simple UI (leave more advanced details to separate pages/different ui)
> * provide API for other tooling in eclipse to use it (like server launches etc.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years