This repository contains mini projects reproducing issues logged in Spring Web Flow's [issue tracker|https://jira.springsource.org]. There are many reasons why this is better than .zip or patch file attachments:
- A streamlined process for evaluating issues so more bugs get fixed more quickly!
- Two-way communication with the Spring team based on working code
- A set of template projects to choose from
- Improved code sharing across the Spring team
- A valuable archive of Spring Web Flow projects across a wide range of use cases and features
All around a better way of interacting with the Spring team.
Logging an issue against Spring Web Flow's JIRA issue tracker
- First, search SWF JIRA to see if your issue has already been reported. If so, there may already be a reproduction issue in this repository!
- If after verifying the issue doesn't exist, create a new issue
- You will now have an issue named, for example, "SWF-1502". Make note of this, as you'll need it below when creating your project.
Using this repository to demonstrate the issue
Assuming you've encountered and created an issue in the core Spring Web Flow project you can now add a project to demonstrate it.
Create a project that reproduces your issue
The idea is to create the smallest possible project to demonstrate the issue. The project may be built with Maven and must contain only sources, XML and other necessary text files. No JARs, please!
For the purpose of these instructions, we'll assume your new JIRA issue ID is "SWF-1502"
1. In your local clone of this repository, create a copy of the appopriate 'template' directory. Their names start with
For Spring Web Flow (non-JSF) issues:
cd spring-webflow-issues ./create-repro-project.sh SWF-0000/ SPR-1502 cd SPR-1502
For Spring Web Flow with JSF 2 issues:
cd spring-webflow-issues ./create-repro-project.sh SWF-JSF-0000/ SPR-1502 cd SPR-1502
2. Review the list of dependencies and version numbers and modify the pom.xml as necessary.
3. Import the project into your IDE and modify it as necessary to reproduce your issue.
- It is already a buildable Maven project, so you may use your IDE's built-in support for Maven to do the importing or generate them before importing (e.g.
4. Add, commit, and push your local fork
git add SPR-1502 git commit -m "Add repro project for SPR-1502" git push
- The Spring Web Flow team will be notified and will look at your request
... and that's it!
What if my issue is not a bug, but an improvement or new feature request?
In certain cases, it may make sense to submit a project for improvement requests. Feel free to submit a project here for your issue if you think it will help us to understand the scenario better.
What about patches against Spring Web Flow itself? Should I still attach those to my JIRA issue?
For now, yes. Spring Web Flow will move from it's current home in SVN to Github soon -- when that happens, we may consider pull requests against forks of that repository.
Can I still attach .zip files to my JIRA issue? Is it required to use this repository?
Yes, you may still attach zip files if it works best for you. Submitting pull requests against this repository as described above is the mechanism that the Spring Web Flow team prefers, but what's most important is that we get code from you that reproduces the problem! Please consider this approach, but zip files are still OK.