forked from jboss/ticket-monster
-
Notifications
You must be signed in to change notification settings - Fork 462
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
Updating to PicketLink 2.5.1.Final. Merging latest changes from master. #41
Open
pedroigor
wants to merge
74
commits into
jboss-developer:picketlink
Choose a base branch
from
pedroigor:picketlink-ticketmonster
base: picketlink
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Updating to PicketLink 2.5.1.Final. Merging latest changes from master. #41
pedroigor
wants to merge
74
commits into
jboss-developer:picketlink
from
pedroigor:picketlink-ticketmonster
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previous commit took out the fix for main index.html I don't think the admin/index.xhtml needs to be changed Add guava version Moving the index.xhtml file to the proper location Mostly putting the patch back to the way it was Changing the method name so forge doesn't think it's a getter
This reverts commit 2b80ca6.
Add forge setting file to gitignore. Fix typos in tutorial and code. Fixed improper reference to js/main-desktop.js -> js/configurations/desktop.js
In addition to updating the versions, Twitter Bootstrap was also updated to 2.3.1 since lower versions are incompatible with jQuery 1.9, due to reliance on $.browser. jQuery 1.9 no longer support CSS pseudo selectors like :valid and :invalid, requiring use of querySelectorAll for detecting valid/invalid HTML5 form input fields. Regexp based validation is used as a fallback, especially for IE9.
A MSIE9+10 specific media-query hack is used to disable the box-shadow style due to a MSIE10 glitch in displaying box-shadow transitions.
…ediaItems. The fix allows events and venues (without corresponding MediaItems) to be created via the admin front end, and to be used in the rest of the application.
OpenShift tends to delete files in /tmp if they're untouched for 10 days. This fix uses the OPENSHIFT_DATA_DIR directory instead, which is persistent by nature.
Corrected the HybridUI doc for Cordova on Android development noted in JDF-197, and kept them up to date with the Cordova 2.7.0 upgrade. Also corrected a bug involving loading of Cordova on iOS.
And fixed some issues with the JDG tutorial.
This is because they were deprecated in jQM 1.3.0 and they also prevent the filter widget from appearing. The nested listviews have been replaced with non-inset accordions. This works better since page transitions do not occur, thus not affecting the Backbone Router.
Contains multiple fixes to ensure that the ticket shopping cart in the mobile view behaves almost similarly as the desktop one. Fixed the back button behavior in checkout. The back button now navigates to the create booking view. The ticket summary view has also been changed to use a listview instead of table. This is to allow bookings to be deleted via the split button design, as well as to aid in responsive design. Booking can be deleted at the level of categories. Also fixed an issue involving a JavaScript exception thrown on triggering the jQueryMobile pagecreate event in the Create Booking view.
This is to recommend newer Forge versions that contain fixes for handling Maven repositories.
This required a server-side change to return HTTP 204 No Content responses instead of HTTP 200 OK. This is primarily due to a change in jQuery 1.9 that treats empty 200 OK responses as errors which cascaded to Backbone and eventually resulted in no updates to the view. The server-side change now results in a 204 response preventing this hidden failure.
This patch also updates a few issues in the TicketMonster application that are not fixed in the Forge scaffolding or cannot be fixed in the Forge scaffolding. Code in PerformanceBean.java has been enhanced to allow correct deletion of Performances. Code in ShowBean.java and show/create.xhtml has been enhanced to allow correct selection of Venue sections when a different venue is chosen during creation/updation of Shows. RichFaces calendar widgets for datetime values have the Apply button enabled via this patch.
Updated JBoss BOM version in use to 1.0.7.CR8. Modified the RESTDeployment class to use the newer Maven.resolver() API.
The styles of the code listings for the site as well as for the generated PDF have been improved. Upquote handling has been performed for the PDF. Additionally, the line break characters generated in code listing have been suppressed to allow for copy&paste of listings.
This was done to prevent JDF site generation issues, since the upgrade to Awestruct 0.5.2 causes the preface section to be generated without sufficient metadata.
Also added a note on ensuring the right JBoss BOM versions for SW Resolvers 2.0.0.Final
Upgraded the RequireJS version to prevent occassional failures in MSIE 10. Removed the order plugin since it is no longer required. Reworked the configuration of jQuery Mobile to disable the jQuery Mobile router on mobileinit. The router is also defined and initialized only after the binding on mobileinit is established, since the router module has a dependency on jQuery Mobile. Also updated the RequireJS text plugin to 2.0.8.
Modified usages of "bind" to "on". Modified all invocations of Collection.fetch() to use "reset:true".
Incorporated the custom Modernizr.js build to make it consistent with the quickstarts.
The version of JDT used in Forge Java parser fails to distinguish long x[][] as an array, resulting in uncompilable code.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.