Currently, I'm looking at the springsource community download site.
It shows that 3.2.4 is the latest general release. Its zip file has dist suffix and the content is different than the latest in 3.1 branch 3.1.4 (which does not have dist ending).
3.1.4 has the following directories:
dist
projects
src
dist folder contains org.springframework...* jars.
3.2.4 has the following directories:
docs
libs
schema
lib folder contains spring-... jars
Was there a major change between 3.1 and 3.2 releases?
According to this accepted answer there was but I was not able to find anything about it.
Does anybody have any particulars?
Should I get 3.1.4 for now?
It was a spring source decision to change it. (I think there was an blog article somewhere, but I can`t found it)
The distribution archive for release 3.2 RC1 is called spring-3.2.0.RC1-dist.zip; whereas, all releases prior to 3.2 generated distribution archives called spring-framework-*-dist.zip.
It is not a bug, it is not a major change in the code, and I highly doubt that they will switch back to the old layout (so there is no reason to stay with 3.1.4).
For the changes: have a look at the feature list and change log:
http://static.springsource.org/spring/docs/3.2.x/spring-framework-reference/html/new-in-3.2.html
http://static.springsource.org/spring/docs/3.2.2.RELEASE/changelog.txt
Related
What is the recommended way of upgrading the quarkus version used in an existing application?
I have taken a look at my pom.xml, since the quarkus extensions dont specify the version used, I assume that they will get updated based on the main quarkus version.
The properties which look to be relevant in the update are quarkus-plugin.version, quarkus.platform.group-id and surefire-plugin.version.
How can I decide which ones to change, and is there anything else to be aware of?
There is one important thing to know, we have:
Quarkus Core: this is the main Quarkus artifacts + all the core extensions: the quarkus-bom is the one of Core. The Quarkus Maven plugin is part of it too.
Quarkus Platform: it contains more extensions such as Camel Quarkus: the quarkus-universe-bom is the one from the Platform, it contains the Core + the additional extensions
We usually release Quarkus core then Quarkus Platform with a few days between the two as we often need a release of Camel Quarkus, which is an Apache project and organizes a 72 hours vote for each release.
In a newly created project, you have the following properties:
<quarkus-plugin.version>1.1.1.Final</quarkus-plugin.version>
<quarkus.platform.artifact-id>quarkus-universe-bom</quarkus.platform.artifact-id>
<quarkus.platform.group-id>io.quarkus</quarkus.platform.group-id>
<quarkus.platform.version>1.1.1.Final</quarkus.platform.version>
quarkus-plugin.version is the version of the Quarkus Maven plugin, it should be in line with the version of the core you use
quarkus.platform.artifact-id can right now either be quarkus-universe-bom for the whole Platform or just quarkus-bom for the Core only.
quarkus.platform.version is the version of the BOM.
Usually all these versions should be aligned. But... it could happen that we would need some quick update in the Platform and not of the core and we could then only release a new version of the platform. This hasn't happened yet to be honest.
Let's take an example of what happened today: I released Quarkus Core 1.2.0.Final but we are still waiting for Camel Quarkus to be released to release the Platform.
If you want to update early, you can change the BOM to use the quarkus-bom and update everything to 1.2.0.Final.
Or you can wait for the Platform to be released early next week and stay on the Platform quarkus-universe-bom.
We also only update the website documentation and code.quarkus.io when the full Platform is released.
It used to work to simply issue the command
mvn io.quarkus:quarkus-maven-plugin:1.4.2.Final:create
in the base project directory for it to automatically update the Quarkus versions in the project pom.xml file, but since 1.6.0.Final it errors:
project XXXXX: Unable to generate the project in a directory that already contains a pom.xml -> [Help 1]
I will create an improvement suggestion ticket at Quarkus to restore this functionality, maybe with a dedicated maven goal (like update)
In the src/test/resources folder of a maven project there's a relative symbolic link.
With the 2.6 version of the plugin, the actual file is copied.
After updating to the 3.0.1 version, it copies the link instead of the file and on a subsequent run (without clean) fails (mvn -e shows it's because of a FileAlreadyExistsException).
Is there any config option to restore the behavior from the previous version ?
I agree, having a link as a test resource is a really bad idea.
This is a known bug in the maven-resources-plugin: MRESOURCES-237 Resource plugin’s handling of symbolic links changed in 3.0.x, broke existing behaviour, unfixed but known for 1½ years.
Unfortunately, there’s not (yet) a configuration option. Introducing it (and defaulting it to “follow symlinks” instead of copy-preserving them) would fix this issue.
For now, the only solution is to downgrade the maven-resources-plugin. I also upgraded from 2.6, and have just now downgraded to 2.7 (last of the 2.x series), and can confirm that it works around this bug and properly copies the symlinks’ contents.
Update: due to the “Mark invalid” issue (a bug in maven-filtering) you should consider staying with 2.6 if you don’t need any of the new 2.7 features, or have to amend the plugin definition with an updated dependency on maven-filtering 1.3 (or maybe newer).
I am performing a server upgrade for some pretty old portlets developed with Spring. Developers no longer in the team used Spring version 3.0RC1 and I want to upgrade those Spring framework jars to last 3.0 version (I believe it is 3.0.7) but I cannot find any "previous versions" repository anywhere.
In Spring official site the oldest available is 3.1.4 but as quite a lot of code is developed for 3.0RC1 I don't find a good idea to do a major/minor version change.
Are older jars available anywhere? I've dedicated some time googling and can't find them anywhere.
http://grepcode.com has some of the files but not all. Files in the project are:
org.springframework.asm-3.0.0.RC1.jar
org.springframework.beans-3.0.0.RC1.jar
org.springframework.context-3.0.0.RC1.jar
org.springframework.context.support-3.0.0.RC1.jar
org.springframework.core-3.0.0.RC1.jar
org.springframework.expression-3.0.0.RC1.jar
org.springframework.web-3.0.0.RC1.jar
org.springframework.web.portlet-3.0.0.RC1.jar
org.springframework.web.servlet-3.0.0.RC1.jar
spring-aop-1.2.6.jar
spring-jdbc-2.5.4.jar
spring-tx-2.5.4.jar
Thanks
Spring makes its releases available in Maven central: http://search.maven.org/#browse|528292745
I tried to add jasper reports library (net.sf.jasperreports:jasperreports:5.2.0) as a maven dependency to my project , unfortunately one of it's dependencies com.lowagie:itext:2.1.7.js2 is a little bit untypical and cannot be located in maven central. I've found, however, that it's available at http://jasperreports.sourceforge.net/maven2/com/lowagie/itext/ .
My questions are:
What is the purpose of jaspersoft custom-build of iText? Patches?
Is it safe to use regular iText library, version 2.1.7 found in maven central repo?
Since the iText license changed from MPL/LGPL Jasper Report couldn't upgrade. So according to the LGPL they supplied a jar file with their changes.
You may ask what changes are:
they added a pom.xml (not relevant in your case)
they did a minor change to the ant.properties for their own version numbering (not relevant in your case)
patched the PdfGraphics2D.java file (fixed a transparency bug)
The change is about the currentFillGState, Lines 1089, 1490, 1616-1628.
What this means for you is difficult to tell but you have the following possibilities:
exchange the patched.jar with the default and run (extensive) tests
add the patched.jar to your repository
add the public jasper report repo to your repo (http://jasperreports.sourceforge.net/maven2)
and as others pointed out ask jr folks for further details, e.g. here would be a start:
http://community.jaspersoft.com/jasperreports-library/issues/2594-0
We have a project where we're using Spring-js. With it comes Spring-dojo and the full dojo package. But in the current version of Spring-js (2.0.9), it's using dojo 1.3. Is there a way to upgrade manually to dojo 1.4? Or even a new Spring-js.jar-file that can be donwloaded that uses dojo 1.4?
Yes. If you are using the ResourceServlet, you can simply drop the new version of Dojo in the top-level directory of your WAR structure. The ResourceServlet always looks there before it looks on the classpath, thus resources in top-level of the WAR take precedence. I would suggest using a full uncompressed source distro of Dojo during development, and then doing a custom build that is tailored to your usage patterns for production.
Beware that we've occasionally seen some minor incompatibilities when upgrading Dojo versions, so be on the lookout for that and report any issues in the Web Flow Jira.
I suspect we'll be upgrading to Dojo 1.4 in the official distribution for the upcoming Spring Web Flow 2.1 release.
Btw., spring webflow 2.0.9 uses dojo 1.2.4 not 1.3 as the release notes tell