Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-4185

Batch CDI extensions are meant for public use, but jberet's module is private

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • None
    • Batch
    • None

    Description

      The org.jberet.jberet-core module is marked as private in EAP.
      However, it contains at least three annotations which are meant to be used by applications:

      • org.jberet.cdi.JobScoped
      • org.jberet.cdi.StepScoped
      • org.jberet.cdi.PartitionScoped

      I guess we should either make the module public, or move these public-facing classes/annotations to a separate module

      Attachments

        Issue Links

          causes

          Sub-task - The sub-task of the issue JBEAP-4453 Document JBEAP-3998 for RN

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Task - Represents a small unit of work that is not end-user facing. JBERET-236 Move public API's out of jberet-core into a public jberet-api module

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              jperkins-rhn James Perkins
              jmartisk@redhat.com Jan Martiska
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: