Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SEC-1673: Move bundlor ranges into gradle build #1914

Closed
spring-projects-issues opened this issue Feb 7, 2011 · 1 comment
Closed

SEC-1673: Move bundlor ranges into gradle build #1914

spring-projects-issues opened this issue Feb 7, 2011 · 1 comment
Labels
in: build An issue in the build type: jira An issue that was migrated from JIRA type: task A general task
Milestone
3.1.0.RC1

Comments

@spring-projects-issues
Copy link

Migrated from SEC-1673
@spring-projects-issues
Copy link
Author

Luke Taylor said:

The build ranges are currently stored in the templates. They should be pulled into the build files for consistency and to allow them to be defined at the same place as the other versioning information in the build.

@spring-projects-issues spring-projects-issues added in: build An issue in the build Closed type: task A general task type: jira An issue that was migrated from JIRA labels Feb 5, 2016
@spring-projects-issues spring-projects-issues added this to the 3.1.0.RC1 milestone Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
in: build An issue in the build type: jira An issue that was migrated from JIRA type: task A general task
Projects
None yet
Milestone
3.1.0.RC1
Development

No branches or pull requests
1 participant
@spring-projects-issues