[JBoss JIRA] (JBDS-3160) JSR-352: Java EE 7 Batch
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3160?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov resolved JBDS-3160.
----------------------------------
Resolution: Done
> 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.15#6346)
10 years, 9 months
[JBoss JIRA] (LOCUS-46) refactor update site zip to new name for consistency with other JBoss artifacts
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/LOCUS-46?page=com.atlassian.jira.plugin.s... ]
Max Rydahl Andersen commented on LOCUS-46:
------------------------------------------
not following why you say JBDS has jboss-tools-locus as name and JBT has something different.
JBDS naming is for *product artifacts*, thus not really relevant here.
and the jbt consistent name would be jbosstools-locus-1.3.0-<version|SNAPSHOT>-updatesite.zip afaik.
What other artifacts are you seeing the jbosstools-1.3.0-SNAPSHOT-updatesite-locus.zip format ?
> refactor update site zip to new name for consistency with other JBoss artifacts
> -------------------------------------------------------------------------------
>
> Key: LOCUS-46
> URL: https://issues.jboss.org/browse/LOCUS-46
> Project: JBoss Tools Locus
> Issue Type: Feature Request
> Affects Versions: 1.3.0
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 1.3.0
>
>
> There was a question raised about what to call the update site zip.
> It's called *update.site-1.3.0-SNAPSHOT.zip* today [1].
> [1] https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo...
> If we want a different artifact name / classifier, I can easily do that. Got a preference?
> We could do:
> * update.site-1.3.0-SNAPSHOT.zip (no change)
> * org.jboss.tools.locus-1.3.0-SNAPSHOT-update.site.zip
> * jboss-tools-locus-1.3.0-SNAPSHOT-updatesite.zip (consistent w/ JBDS)
> * jbosstools-1.3.0-SNAPSHOT-updatesite-locus.zip (consistent w/ JBT)
> * ...?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months