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...
Related
EvoSuite Version
1.2.0
latest version of org.evosuite.plugins:jar not present in maven central repo
any one know maven repo which has latest version of evosuite.
I tried to find it in in maven central , last version i can see is 1.0.6. https://mvnrepository.com/artifact/org.evosuite.plugins/evosuite-maven-plugin?repo=evosuite
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.
I have own maven2 repository in nexus, for publishing build artifacts.
I'm using maven deploy plugin for uploading artifacts there
Is it possible somehow to add custom aliases(links) to versions inside my repo, so project/script/whatever will use artifacts from repository, can refer to some static version-name(e.g. stable,earlier,development)
And during each publishing of new version to repo, I will update those aliases.
No, there's no version aliasing in maven. However, you can use version range for your dependency or use profiles to specify different versions for your builds.
Have a look at this question, so you get the idea what is possible: How do I tell Maven to use the latest version of a dependency?
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
While building Maven projects (Spring and jbpm 4.4 to be specific),
I see that the libraries that I already have in Maven local repository, gets downloaded again or the console log suggests so.
Say my local repo already have the commons-collection3.1 in my library, is it necessary to download from the maven repository?
Is there a setting that can let maven know to look in the local repo first?
Thanks,
Ayusman
You might have the updatePolicy for SNAPSHOT repository set to always in your settings.xml. See this guide to settings.xml.
Maven will look in the local repository first by default.
Downloading in Maven is triggered by a project declaring a dependency that is not present in the local repository.
http://maven.apache.org/guides/introduction/introduction-to-repositories.html