<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=jpd9808" rel="nofollow">Jason Day</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-9801?redirect=false" rel="nofollow">SPR-9801</a></strong> and commented</p>
<p dir="auto">It appears the migration of the <a href="https://jira.springsource.org/browse/SPR-8116" rel="nofollow">build to use Gradle</a> dropped the OSGi manifest headers from getting added.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 3.2 M1, 3.2 M2</p>
<p dir="auto"><strong>Issue Links:</strong></p>
<ul dir="auto">
<li><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="398115932" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/13543" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/13543/hovercard" href="https://github.com/spring-projects/spring-framework/issues/13543">#13543</a> Users of the SpringSource EBR need Spring framework bundles to continue to be published there for Spring 3.2 (<em><strong>"duplicates"</strong></em>)</li>
</ul>
<p dir="auto">3 votes, 4 watchers</p>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=rwinch" rel="nofollow">Rob Winch</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-9858?redirect=false" rel="nofollow">SPR-9858</a></strong> and commented</p>
<p dir="auto">This is related to <a href="https://jira.spring.io/browse/SEC-2064" rel="nofollow">SEC-2064</a> which states:</p>
<blockquote>
<p dir="auto">It strikes me that <a href="http://static.springsource.org/spring-security/site/docs/3.0.x/apidocs/org/springframework/security/web/util/ThrowableAnalyzer.html" rel="nofollow">ThrowableAnalyzer</a> is not only suitable for its current role in Spring Security and is more generally useful. I've found a need for something along the lines of ThrowableAnalyzer in Spring Social, but do not wish to force a dependency on Spring Security. As things stand currently, I must duplicate ThrowableAnalyzer to avoid the otherwise unnecessary dependency on Spring Security.<br>
I wonder if ThrowableAnalyzer might be better suited for Spring Core's org.springframework.util package? I already depend on Spring Core, so I wouldn't have the same dependency concerns there and would be able to get rid of my duplicate ThrowableAnalyzer.</p>
</blockquote>
<p dir="auto">Let me know if this is something that is acceptable and I can put a pull request together.</p>
<hr>
<p dir="auto"><strong>Issue Links:</strong></p>
<ul dir="auto">
<li><a href="https://jira.spring.io/browse/SEC-2064" rel="nofollow">SEC-2064</a> Extract ThrowableAnalyzer, perhaps to Spring Core (<em><strong>"is depended on by"</strong></em>)</li>
</ul>