Skip to content

Build: Specify jQuery version as >=1.6, do custom install for this repo #1271

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.

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

Closed
wants to merge 2 commits into from
Closed

Build: Specify jQuery version as >=1.6, do custom install for this repo #1271

wants to merge 2 commits into from

Conversation

jzaefferer
Copy link
Member

The new bowerinstall task installs the jQuery version as specified in
devDependencies, while the dependencies field just specifies the minimal
version required.

Fixes #10110

Probably a bad idea to work on this before #1266 lands, but then I didn't change much in Gruntfile.js.

},
"devDependencies": {
"jquery": ">=1.6 <1.11",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems like we should either declare a specific version here or just go with "<2".

On a related note, maybe I don't know what I'm doing, but when I update this to "jquery": ">=1.6 < 1.12", and run grunt bower on this branch, nothing happens. It seems like I should get 1.11.1.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with changing this version. I'm okay with "<2", but I don't want to mix the jQuery update with this change.

Regarding the other problem, I've added a comment about that in the Gruntfile, where the path has to change. I also reported the poor error handling.

The new bowerinstall task installs the jQuery version as specified in
devDependencies, while the dependencies field just specifies the minimal
version required.

Fixes #10110
Closes gh-1271
@@ -245,5 +248,6 @@ grunt.registerTask( "lint", [ "asciilint", "jshint", "jscs", "csslint", "htmllin
grunt.registerTask( "test", [ "qunit" ]);
grunt.registerTask( "sizer", [ "concat:ui", "uglify:main", "compare_size:all" ]);
grunt.registerTask( "sizer_all", [ "concat:ui", "uglify", "compare_size" ]);
grunt.registerTask( "bower", [ "bowerinstall", "bowercopy" ]);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've removed the separate install command I had earlier, since the bower behaviour apparently is here to stay, always installing project dependencies even when a specific endpoint is specified.

@jzaefferer
Copy link
Member Author

If this is okay now, I could add a second commit to change the version in devDependencies to "<2" and include the update to jQuery 1.11.1.

@tjvantoll
Copy link
Member

This looks good to me and I like making the Core update in a separate commit.

@jzaefferer
Copy link
Member Author

Added a separate commit with the jQuery version update. To make sure we don't get regressions from TestSwarm after merging to master I've created a temporary Jenkins jobs. The result is the same as the last run on master, those four selectmenu tests still fail, everything else is green.

@tjvantoll can you take another look?

@tjvantoll
Copy link
Member

This branch looks good, and I still have fixing those tests on my list.

@jzaefferer
Copy link
Member Author

@timmywil could you take a look at this?

@jzaefferer
Copy link
Member Author

Update: After some discussion in timmywil/grunt-bowercopy#19, it looks like @timmywil will add an ignore option to grunt-bowercopy. Using that we can specify "jquery-1.x" in devDependencies, copy the version we want from there, and set tell it to ignore the "jquery" dependency, which we can then specify as ">=1.6".

},
"devDependencies": {
"jquery": "<2",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We actually want an explicit version here, not a range. We want to manually upgrade as new versions come out so we can make sure we fix any potential problems before switching to the new version.

@scottgonzalez
Copy link
Member

If this is okay now, I could add a second commit to change the version in devDependencies to "<2"

That would be wrong. We don't support jQuery <1.6.

@scottgonzalez
Copy link
Member

I think the simplest solution is to just throw the unused jQuery file into an ignored directory or add the file itself to .gitignore. Though if bowercopy gets an ignore option, we can use that. It probably makes sense to just deal with this in #1266.

@jzaefferer
Copy link
Member Author

We can copy the unused file to dist/ and switch to using bowercopy's ignore option once available. Makes sense to do that as part of #1266, so I'm going to close this.

@jzaefferer jzaefferer closed this Jun 23, 2014
@jzaefferer jzaefferer deleted the bower-jquery-version branch March 6, 2015 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants