[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 Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-18995:
---------------------------------------
Arquillian is marked as (Experimental) and it is in EA, Forge Tools Extensions also marked as (Experimental), but not EA. This is confusing. Shouldn't we just use (Early Access).
> 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-18995) Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18995:
----------------------------------
Steps to Reproduce:
# Install all available features from stable update site by using "Select All" button in install dailog
# Restart eclipse
# ASSERT: Early access features are not installed.
was:
# Install all available features from stable update site
# Restart eclipse
# ASSERT: Early access features are not installed.
> 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-18997) Editor for batch.xml
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-18997:
---------------------------------------------
Summary: Editor for batch.xml
Key: JBIDE-18997
URL: https://issues.jboss.org/browse/JBIDE-18997
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: batch
Affects Versions: 4.3.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Priority: Minor
Fix For: 4.3.x
It is a very simple xml:
{code}
<batch-artifacts xmlns="http://xmlns.jcp.org/xml/ns/javaee">
<ref id="<reference-name>" class="<impl-class-name>" />
</batch-artifacts>
{code}
that can be easily managed in a text editor, but for our tool completeness we may provide a Tree+Source editor for it.
--
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 Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18995:
----------------------------------
Steps to Reproduce:
# Install all available features from stable update site
# Restart eclipse
# ASSERT: Early access features are not installed.
was:
# Install all available features from stable update site
# Restart eclipse
# ASSERT: Early access features are not installed.
> 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] (JBDS-3278) OpenShift v3
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3278?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-3278:
-----------------------------------
Description:
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_...
was:
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}
> 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.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] (JBIDE-18996) Support batch.xml in Batch project model
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-18996:
---------------------------------------------
Summary: Support batch.xml in Batch project model
Key: JBIDE-18996
URL: https://issues.jboss.org/browse/JBIDE-18996
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: batch
Affects Versions: 4.3.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Priority: Minor
Fix For: 4.3.x
Default loading of batch artifacts described by JSR-352 is provided by batch.xml:
{code}
<batch-artifacts xmlns="http://xmlns.jcp.org/xml/ns/javaee">
<ref id="<reference-name>" class="<impl-class-name>" />
</batch-artifacts>
{code}
Batch implementations may define specific loaders and probably most popular is going to be the use of javax.inject.Named annotation.
For the completeness, we have better to support the default way as well.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months