[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3360:
-----------------------------
Attachment: JBDS3360_staging_site_contains_Beta1.png
{quote}It seems that https://devstudio.redhat.com/updates/8.0-staging-JBDS-3360/ does not really contain 8.1.0.Beta1 JBDS core product?{quote}
The site DOES include 8.1:
!JBDS3360_staging_site_contains_Beta1.png!
You can see even browse the site here:
https://devstudio.redhat.com/updates/8.0-staging-JBDS-3360/compositeConte... -> https://devstudio.redhat.com/updates/8.0.0/jboss-devstudio-8.1.0.Beta1-up...
> Align bits offered in JBoss Central with installed version of JBDS
> ------------------------------------------------------------------
>
> Key: JBDS-3360
> URL: https://issues.jboss.org/browse/JBDS-3360
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, updatesite
> Affects Versions: 8.0.2.GA
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 8.1.0.CR1
>
> Attachments: beta1-composite-remediation.png, JBDS3360_staging_site_contains_Beta1.png
>
>
> The problem in JBDS-3359 shows a broader issue.
> (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.)
> Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites:
> https://devstudio.redhat.com/updates/8.0/
> Initially this update site contained JBDS 8.0.0 core + 8.0.0 central.
> But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users:
> 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits
> 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits)
> Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also.
> I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3273:
-----------------------------------
initial focus will be put on search in JBoss Central, as discussed in JBIDE-18813.
Then, we'll see how this maps to the existing treeview based example wizard (accessible from current JBoss Central)
> JBoss Central: Automatic upstream quickstart integration
> ---------------------------------------------------------
>
> Key: JBDS-3273
> URL: https://issues.jboss.org/browse/JBDS-3273
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 9.0.0.Alpha2
>
>
> Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3160) JSR-352: Java EE 7 Batch
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3160?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3160:
-------------------------------
CDW qa_ack: + (was: ?)
> JSR-352: Java EE 7 Batch
> ------------------------
>
> Key: JBDS-3160
> URL: https://issues.jboss.org/browse/JBDS-3160
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 9.0.0.CR1
>
> Attachments: BatchEditor.png
>
>
> Custom XML Editor for the Batch configuration XML
> Example
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/chunk...
> JSR-352: Batch
> I, the Java EE application developer, wish to create new and maintain Batch (JSR-352) applications in Eclipse. I need XML editing support, content-assist where appropriate and a Maven-based quickstart to help with getting started.
> The quickstart should be easily importable into JBDS and allow for editing so that I, the Java EE app dev, can "make it my own" by changing its project name, group, artifact id and version, plus modifying the XML file, adding/removing classes, etc.
> This effort should primarily be focused on the XML editing experience. The normal New Java Class wizard should support the batch related super classes (extends). Run As Run on Server should work as well.
> Examples of the XML:
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch...
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3160) JSR-352: Java EE 7 Batch
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3160?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3160:
-----------------------------
CDW release: + (was: ?)
> JSR-352: Java EE 7 Batch
> ------------------------
>
> Key: JBDS-3160
> URL: https://issues.jboss.org/browse/JBDS-3160
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 9.0.0.CR1
>
> Attachments: BatchEditor.png
>
>
> Custom XML Editor for the Batch configuration XML
> Example
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/chunk...
> JSR-352: Batch
> I, the Java EE application developer, wish to create new and maintain Batch (JSR-352) applications in Eclipse. I need XML editing support, content-assist where appropriate and a Maven-based quickstart to help with getting started.
> The quickstart should be easily importable into JBDS and allow for editing so that I, the Java EE app dev, can "make it my own" by changing its project name, group, artifact id and version, plus modifying the XML file, adding/removing classes, etc.
> This effort should primarily be focused on the XML editing experience. The normal New Java Class wizard should support the batch related super classes (extends). Run As Run on Server should work as well.
> Examples of the XML:
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch...
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3160) JSR-352: Java EE 7 Batch
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3160?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3160:
--------------------------------
> JSR-352: Java EE 7 Batch
> ------------------------
>
> Key: JBDS-3160
> URL: https://issues.jboss.org/browse/JBDS-3160
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 9.0.0.CR1
>
> Attachments: BatchEditor.png
>
>
> Custom XML Editor for the Batch configuration XML
> Example
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/chunk...
> JSR-352: Batch
> I, the Java EE application developer, wish to create new and maintain Batch (JSR-352) applications in Eclipse. I need XML editing support, content-assist where appropriate and a Maven-based quickstart to help with getting started.
> The quickstart should be easily importable into JBDS and allow for editing so that I, the Java EE app dev, can "make it my own" by changing its project name, group, artifact id and version, plus modifying the XML file, adding/removing classes, etc.
> This effort should primarily be focused on the XML editing experience. The normal New Java Class wizard should support the batch related super classes (extends). Run As Run on Server should work as well.
> Examples of the XML:
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch...
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3160) JSR-352: Java EE 7 Batch
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3160?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3160:
------------------------------------
Thx! QE acking now.
> JSR-352: Java EE 7 Batch
> ------------------------
>
> Key: JBDS-3160
> URL: https://issues.jboss.org/browse/JBDS-3160
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 9.0.0.CR1
>
> Attachments: BatchEditor.png
>
>
> Custom XML Editor for the Batch configuration XML
> Example
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/chunk...
> JSR-352: Batch
> I, the Java EE application developer, wish to create new and maintain Batch (JSR-352) applications in Eclipse. I need XML editing support, content-assist where appropriate and a Maven-based quickstart to help with getting started.
> The quickstart should be easily importable into JBDS and allow for editing so that I, the Java EE app dev, can "make it my own" by changing its project name, group, artifact id and version, plus modifying the XML file, adding/removing classes, etc.
> This effort should primarily be focused on the XML editing experience. The normal New Java Class wizard should support the batch related super classes (extends). Run As Run on Server should work as well.
> Examples of the XML:
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch...
> https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months