-
Notifications
You must be signed in to change notification settings - Fork 42
Open
Labels
S: SignificantSeverity: Significant - in the mainline planSeverity: Significant - in the mainline planepicEpic User StoryEpic User Storyuser storyUser StoryUser Story
Description
User Story
Essential components
- Title describes the story
- Stakeholder type is identified
- Outcome is described
- Rationale is explicit
- Acceptance criteria are verifiable and from the perspective of the stakeholder
Story
As a maintainer
I want the automated build process to update its configuration of Java versions specified for compilation and packaging
so that I don't need to manually update build configuration information (e.g., build.gradle) in response to newer versions of BlueJ
Acceptance Criteria
Scenario 1
Given an updated version of the BlueJ product,
when the updated bluejext.jar file appropriately appears in the QT4BJ repository, and the product build+packaging process is invoked
then the build process completes without error and the resulting product (extension jar file) is compatible with the updated version of BlueJ.
Related Information
See #136
Dependencies
Depends On
(Issues on which this story depends)
Dependents
(Issues dependent on this story)
Metadata
Metadata
Assignees
Labels
S: SignificantSeverity: Significant - in the mainline planSeverity: Significant - in the mainline planepicEpic User StoryEpic User Storyuser storyUser StoryUser Story