I remember, long time ago, I saw an overview of what sub-project of Spring Data contributes in which version to the single release trains.
At the moment I can only infer this knowledge from the respective BOM. I also could not find it anywhere on the Spring Data project page.
Could anyone please point me to a convenient overview of past, current and maybe future release trains with their containing sub-project versions?
Ah just found that wiki page which holds a sidebar with all the yet-known release trains, for example Release Train Moore.
Maybe someone from the team could link to this location a little more prominent from the start page of Spring Data.
Related
I'm working with a Grails application version 2.2.4 and I need a procedure for upgrade to latest version (I hope it can be possible). I have thought as a first step to follow the indications of the official site, but that let me to upgrade to version 3.
I'd like to know if anyone already did it or have experience about that. How long take it?, the process and the main problems.
Many thanks in advance.
I think you need to follow both upgrade instructions. the one for 3.x and the 4.x.
start with the 3.x and them move to the 4.x changes.
Another approach I think may be better is to start an empty 4.x application and then start moving you code there. also check first that all the plugins that you are you sing have 3+ version.
The effort required to upgrade can change massively depending on multiple factors, including the size of the project, the quality of the original code, were plugins used and if so have they been updated or will the functionality need replacing, were deprecated taglibs used, e.g remoteFunction etc. etc.
There is not a great deal of difference between 3.x and 4.x so it makes sense to upgrade to 4.x.
Tackle it in stages from the basis of a new project, attempting to rebuild the project between stages.
Reestablish configuration, you don't have to use application.yaml (the default in 4.x) so can create an application.groovy with the same parameters as per your old project.
Move over domain objects but use a new database URL, compare the schema's between the old db and new db to ensure the database is the same. Unless you don't rely on GORM to recreate/update the schema.
Move over any other source and command objects ensuring the project will build. You may need to modify buildconfig at this stage to bring in dependencies and plugins.
Move over services, ensure all compiles and make sure transactions are behaving as intending.
Move over controllers ensuring any tests run successfully.
Move over the views.
Hopefully if the project is still building at this stage, you can run it!
In the old version, there was a dashboard for the whole project from different views, but in the latest version there isn't. Why was this dashboard removed?
The short answer is that rather than making you figure out which measures are most important, and making you figure out how to display them, recent versions of SonarQube handle the hard work for you with a standard, non-customizable project homepage, and the new Projects space.
I am developing a Java framework/API to solve a problem at a client. The code/idea is my property (not the client's). I think it might be useful for others, so I would like to publish it as a open source project.
By publishing I mean bringing it out in the open - making it available as a Maven project.
I can think of conforming to Maven structure, proper documentation/example usage available on a web site, and unit tests, maybe some code coverage threshold.
But does it have to be run by some committee? Do I have to present it to somebody? What steps do I need to take to eventually have it available as a Maven dependency?
There's no committee or approval process that I know of. All you have to do is put your code into a public Github repo. This is how open source software works.
Per Kapep's excellent suggestion below, you have to choose a license as well. Apache, Creative Commons, Gnu, MIT - these are a few of your choices. Know what they mean before you decide.
Your problem begins on that day - you'll have to make others aware of it and see if it's adopted by others. If it's good, you'll have the nice problems of dealing with a user base and having others change your code. If not, it'll languish in the repo.
Noticed that there is a 2.0 version of the Spring IO Platform available as a snapshot. I am looking to understand what might be driving the major version number change. Can someone with better insight into the changes share the themes here (or point to somewhere where this is better documented)?
Look at the "Upgrading" section of the documentation: http://docs.spring.io/platform/docs/2.0.0.BUILD-SNAPSHOT/reference/htmlsingle/#upgrading-removal
Some dependencies were removed, which leads to a major version, since it's a breaking change.
Does anyone have any information on Spring Web Flow 3 status?
Here are a few relevant links that support my sense that springsource has essentially abandoned the project:
1)Official roadmap indicates they are missing milestones by over a year now with no update to the roadmap.
2)Forum thread filled with these questions ignored by Keith Donald and Spring team.
3)Official Download page says the latest release is 2.2.1 but is actually 2.3 so that is not even being kept up-to-date anymore.
While Web Flow version 2 I'm sure is a great product, the issues above are all obvious red flags when it comes to evaluating an open source product -- as well as evaluating the company behind that project. Am I simply missing some communication channel where all this has been discussed in detail before? I find it hard to believe that springsource, a company that seemingly had their act together, would be this negligent with one of their flagship products.
They just added a graphical web flow editor into STS. See this InfoQ post. Also, I just checked JIRA and Fisheye and it looks like there's bug fixes going into a 2.3.1 coming that corresponds with Spring 3.1. So I don't think it's abandoned, it's just not getting new features.
Just wanted to mention that the latest version (2.3.1) of Spring Web Flow was released on Mar 27, 2012. See the changelog file: http://static.springsource.org/spring-webflow/docs/2.3.x/changelog.txt