Jackson 2.10.0 was released today; I see the jars in central (e.g. databind), but the latest jar for dataformat-xml is 2.10.0.pr3.
-csv too.
I see there is an open issue on sonatype, perhaps related.
The problem has been resolved; the jars are there now.
Related
I recently updated my IntelliJ and I am having a problem with it showing import statements as nonexistent in the classpath despite the project building fine by doing mvn clean [install|verify] from the command line and the software actually works. So the dependencies are certainly there but the IDE seems to have a bug synchronizing against the pom file. I have tried to Maven --> Reimport multiple times, without success.
Considering that I recently updated IntelliJ (the version is as of 7/15/2017), could this be a newly introduced bug and is there a workaround?
The problem may be caused by a known bug in Maven integration which affects 2017.2 version. This bug is fixed in 2017.2.1 version.
You can find out if it's the case of your problem by searching idea.log for:
java.lang.AbstractMethodError: org.jetbrains.idea.maven.server.embedder.CustomModelValidator$ProxyModelProblemCollector.add(Lorg/apache/maven/model/building/ModelProblemCollectorRequest;)V
Having used RSpec in the past, I would like to use JSpec in my Java project. But I am unable to find install information in Maven Central repository or in JSpec. Would appreciate little direction.
It is part of the JavaLite Common Package. You can find it in Maven Central: http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22javalite-common%22
Here is my current understand of how Maven handles dependencies.
When a dependency is being actively worked on Maven attaches the "-SNAPSHOT" to the end of the version. ex) 1.1.1-SNAPSHOT. These snapshots are uploaded to a remote repository that is specifically responsible for snapshots. The same remote repository has a section for released versions of the packages. Now when a project has the dependencies updated, Maven pulls the most recent version of a package into the local repository. ONLY SNAPSHOTS are updated depending on the time stamp on the the snapshot. If Maven pulls down a release version (ex: 1.1.0) it will never look for another package with the current version.
Now my questions are:
What are the flaws in my understanding? Am I missing a conceptual piece?
When a package moves from a SNAPSHOT to a release version, how do the pom.xml get updated to reflect the released version of the package? Is this a manual process?
Lastly, if a package is released, we'll use the example from above, 1.1.1 is released. Is 1.1.2-SNAPSHOT created or 1.2.0-SNAPSHOT created, and is this the version that will be updated in the poms?
Snapshots are currently in development versions and could be not stable.
We are old fashioned company which still use svn:
The development is going in the trunk and version in pom files are snapshots (we have dependencies to some opensource libraries that have fixed version, and we update them as soon as new release happens and we are confident about switching)
As soon as we are going to release we are branching trunk and changing versions in pom to corresponded fixed one (some companies could mark them with suffix -rc)
Release (Companies that use -rc will change version in pom to fixed one)
Please take a look to release maven plugin to skip manual version changes.
I hope this answers some of your questions.
About the versioning answer - it depends. Please read about it more here:
http://en.wikipedia.org/wiki/Software_versioning
Best Practice: Software Versioning
Can anyone provide the link to the svn repository latest version/tag of of Plexus FTP Server project? I only see version 1.0-alpha-1 at the Maven repository which is released in 2005.
Is it the current latest version? Isn't there a stable release at all?
Have you taken a look into the pom of that project there is the location of the SVN repository...
I'm searching for a longer time, but without any solution.
My problem:
I configured my Grails project (1.2.4) with Maven and my own Nexus Repo. That seems to be working well. But can I also put the Grails plugins, which I am using, also to the Nexus Repo?
At the momement the plugin dependencies are resolved over the Grails Plugin repository.
Any ideas?
with regards
Fabian
Grails 1.3 has got support for dependency managing plugins. Details are here:
http://blog.springsource.com/2010/05/18/managing-plugins-with-grails-1-3/
The article discusses some of the problems that existing in previous versions of Grails.
Understand this thread is old, but posting a link in which the author explains the configuration of grails to fetch plugins and dependencies from Nexus:
Nexus Configuration for Grails plugins and other dependencies
This worked great for grails 2.2.2.