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.

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

1.7.x #536

Closed
wants to merge 100 commits into from
Closed

1.7.x #536

wants to merge 100 commits into from

Conversation

PankajSharma02-Nagarro
Copy link

No description provided.

cubasuarez and others added 30 commits May 12, 2015 20:25
Add possibility for service provider to add authorization by overriding setAuthentication
A NegotiateSecurityFilter that supports dependency injection to authorize principal at serviceprovider after
authenticating in AD.
We use slf4j - these were missed.
Set jacoco minimum coverage back to zero as it breaks site build.
Update assertj and mockito.
Exclude hamcrest from mockito so it doesn't pick up wrong version.
Add new plugin owasp to check for vulnerabilities
slf4j to 1.7.10
jstl to 1.2.4
maven-project-info-reports-plugin to 2.8
JavaEWAH to 1.0.0
jgit to 3.6.1.201501031845-r
sonar-maven-plugin to 2.5
Added report for owasp
Using jautodoc to automatically generate out missing javadocs.
Incorrect ones are fixed as well.
war plugin is managed in parent, remove drom demo level.
waffle-jna is used on all, it shouldn't then be managed as that makes no
sense.  It's also duplicated otherwise in dependencies so just move
version number and remove the duplicate in dependency management.
being created and used instead of pulling LoginConfig out of the
context.
1.7.x - Merging from master series
to 9.2.7.v20150116
updated waffle version link
updated copywrite year
adding missing serializable
adding missing this accessor
catch-exception relied on older mockito version.  In newer mockito
version which we use, code has been make class default thus no longer
available for external use.  I worked on catch-exception library trying
to address this but that never panned out as it was rather difficult
thing to address.  That said, this new library 'fluent-exception-rule'
utilizes junit rules and only relies on assertj which we also use.  In
fact, so did catch-exception.  The overall code is even cleaner to read.
Now that we have resolved issue with using catch-exception by replacing
it, we are free to upgrade back on target with mockito.
1.7.x - Cherry picking to the 1.7.4 release
Revert "Use ${project.version} throughout."
Fix all the tags to HEAD.
Backport handle leak and sonatype updates to 1.7.x
[gitignore] Update gitignore
Fix build for 1.7.5-SNAPSHOT and update all dependencies/plugins
[forced] Prepare for next release 1.7.6-SNAPSHOT
@hazendaz
Copy link
Member

hazendaz commented Jun 12, 2017 via email

@hazendaz hazendaz closed this Jun 13, 2017
@hazendaz
Copy link
Member

I see now what the attempt was. So let me explain.

1.7.x was cut off master when 1.7.x became supported for one final year as 1.8.x came into master. There were cherry-pick patches on 1.7.x, updates, and other things that don't need to ever come into master. This same pattern is being used with 1.8.x from the current master. Because the legacy branches are not part of the main code base any longer when these cuts are made, there is zero reason to try to pull commit history into master. It would be rather pointless as the paths were diverged and therefore no benefit to bringing it in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants