Prevent redirect misuse on user log in.
Fix for masthead link for biostar mainpage.
Fix for masthead link for biostar mainpage.
Merged in dan/galaxy-central-stable-prs/stable (pull request #374)

Prevent redirect misuse on user log in.
Merge stable changes into default.
Handle case where no network is available when attempting to determine repository dependencies for an installed repository.
rename biostar menu link
More quickly stop the process of checking for migrated tools when starting Galaxy if there is no internet connection to the tool shed.
UI: rework zh and ja locale data
Workflow Editor: Rework InputTerminal to implement/use an update method (w/tests).
This will enable replacing terminals instead of recreating them and reconnecting in subsequent changesets.
Workflow Editor: Replace instead of recreate terminal on update.
This fixes at least one subtle bug related to multiple input data parameters (actually probably two bugs) because the old logic assumed there was only one connector per input terminal.

This should be more efficient, lead to some code duplication deletion in subsequent changesets, and really help dataset collections where terminals are much more complex (there are data inputs and collection inputs, and each can be mapped over by collections) - this helps manage complexity downstream.
Workflow Editor: Merge addDataInput and replaceDataInput into common method.
Reduces some code duplication here and reduces even more code duplication downstream in dataset collections work.
Record history content type with output of history contents API.

Downstream in dataset collections branch this isn't just dataset, including this will allow clients to distinguish between different kinds of content.
Refactor backbone models to allow different kinds of history contents.

In particular, add a new backbone parent model (HistoryContent) refactored out of HistoryDatasetAssociation. This makes room for a forth coming HistoryDatasetCollectionAssociation model that will be emitted from the history contents API.

There are likely better ways to share common functionality between a dataset and a dataset collection contents - more JS savy developers should feel free to refactor into smaller mixins for instance. For now HistoryContent is just composed of the overlap in functionality between dataset and collection representations downstream and is an quick and dirty way to share said functionality.
Refactor backbone views to allow different kinds of history contents.

This makes room for a forth coming HistoryDatasetCollectionAssociation model that will be emitted from the history contents API. Same comment as previous changeset applies - this is a potentially crude way to share duplicated functionality and a better design would be most welcome.
Rename historyPanel.refershHdas to refreshContents.
Add simple module verions of validation stuff in base controller.

For reuse outside of controllers (i.e. in dataset collections). Objections to refactoring base controller stuff to use this?
Extract base class from DataToolParameter to be shared with DataCollectionToolParameter.
Dataset collections - models - basics.

Mapping, model definition, database migration, and model unit tests to support database collections.
Dataset collections - models - mapping to allow HDCA to hide HDAs under it.

Should help keep the history panel in check initially hopefully.