Is there a planned release date for final version 1.0 of Spring Security SAML module? RC2 has been released a long time ago (March of 2013) and no further RC or final version has been released since then.
There's a 1.0.0 release out there, just the spring-security-saml website is out-dated
<dependency>
<groupId>org.springframework.security.extensions</groupId>
<artifactId>spring-security-saml2-core</artifactId>
<version>1.0.0.RELEASE</version>
</dependency>
Simon
Related
At https://mvnrepository.com/artifact/org.springframework.security.experimental/spring-security-oauth2-authorization-server the latest release 0.2.0 is missing.
It stopped there with 0.1.2, why?
0.2.0 is out almost a month ago.
As part of the 0.2.0 release, the Authorization Server moved out of experimental status and into the Spring projects portfolio.
You can find the 0.2.0 version under org.springframework.security:spring-security-oauth2-authorization-server.
https://mvnrepository.com/artifact/org.springframework.security/spring-security-oauth2-authorization-server
Instead of manually changing the version each time, i want the maven to load the released jar version automatically.
I'm using Eclipse with embedded Maven version 3.5.4
Could you anyone suggest on how to resolve this ?
I have tried LATEST and RELEASE keywords in
LATEST
But it does not work.
If i use version range like
[1.70.4,) it loads the snapshot version which i do NOT want
i have added the below mentioned dependency in my pom.xml
<dependency>
<groupId>com.xxx.portal</groupId>
<artifactId>portal-xxx-integrationtests</artifactId>
<version>1.70.4</version>
<classifier>tests</classifier>
<type>test-jar</type>
<scope>test</scope>
</dependency>
I am writing an Api and I need to do documentation using swagger. I am using spring boot 1.3.5 because application server is old and has java 6 configured cannot upgrade to 8 as of now. Can we use springfox swagger with java 6?
In the current version of Springfox is specified jdkVersion = 1.8, so you are out of luck. But slightly older versions like 1.0.1, should be compatible. Look at the values for sourceCompatibility and targetCompatibility
I have a big project running on Eclipse that uses Struts, I want to upgrade Struts from 2.0.11.1 to 2.5.3.
However, I checked the Migration Guide but there was no info detailing what should really be removed, updated, added, etc..
I downloaded struts 2.5.3 and there are a lot of libraries, plugins, source files, etc..
My question is that can I upgrade Struts from 2.0.11.1 to 2.5.3 directly?
If yes, then what should be changed and how will this be done?
If no, kindly propose a solution.
When you upgrade the version of Struts2, you have to update the libraries requires by your application to the target version. Each Struts2 release is supplied with the corresponding set of libraries in the lib folder that are compatible with the version of Struts. If you use maven to resolve and fetch the dependencies you should consider the artifact struts2-core.
<dependency>
<groupId>org.apache.struts</groupId>
<artifactId>struts2-core</artifactId>
<version>2.5.3</version>
</dependency>
It will fetch all required dependencies for this artifact, other dependencies, such as plugins you need to add separately. Use the same version targeted to plugins. For example to add a convention plugin use
<dependency>
<groupId>org.apache.struts</groupId>
<artifactId>struts2-convention-plugin</artifactId>
<version>2.5.3</version>
</dependency>
The targeted version number is 2.5.3, but it's possibly incompatible with the other features i.e. Hibernate and Spring which versions need to upgrade separately by adding corresponding artifacts to the dependencies.
And finally and most time consuming are changes to the source code of the project, update the configuration files according to newer DTDs, API changes, fix deprecations. For this purpose consider reading the release notes.
You can't upgrade Struts2 just changing the major version number.
Also see the example of developing a maven project: Create Struts 2 Web Application Using Maven To Manage Artifacts and To Build The Application.
I'm using IBM WebSphere 7.0 with MyFaces 2.0.7 installed as shared library.
Because there are issues with PrimeFaces (for example, p:messages autoUpdate not working) I'm considering the upgrade to newer version (which is not trivial, because this must be the team decision in corporation).
So, my question is, which is the newest version of MyFaces that will work with IBM WebSphere 7.0? The newest version is for now 2.1.10, but according to the answer to the question Can JSF 2.0 be used with Websphere application server version 7.x MyFaces versions starting from 2.1 will not work with WebSphere 7.0.
Have someone managed to run version 2.1.x? If so, which version, and was something additional to do? As I said, I've successfully configured shared library, similar to solution from article like that: http://wasbehindtheglass.blogspot.co.uk/2011/11/myfaces-20-and-websphere-application.html
The MyFaces Core 2.1.10 works well with IBM WebSphere 7.0.
Release notes can be found at MyFaces Core 2.1.10.