Another minor release of Maven: The Definitive Guide. This update changes some screenshots in the m2eclipse chapter, and it also adds a section about the Goal selection dialog.
I’ve released another version of the Maven Book today. The PDF version is back by popular demand (weighing in about 550 pages), and the Eclipse chapter has been updated. Also, some tweaks to the HTML formatting.
Nothing major, but I’m trying to consistently announce any changes no matter how substantial on this blog because there seems to be a loyal following of RSS subscribers (sorry ATOM, RSS is the legacy feed format). Again, thanks for *Everyone* who has emailed me with feedback and who has identified typos and errors.
If anyone has any feedback on the format and presentation of the HTML version, please let me know. Questions I’m asking you (the audience) are:
I answer this question often enough that I decided to burn it to a blog so I don’t have to dig it out of the source anymore…and maybe save someone else the time along the way.
Here is the relevant code that Maven uses to determine if an artifact is a snapshot or not: Continue reading
Gaining a larger user base is usually a goal of most OSS projects and obviously making it easier for users to get and user your project will help to grow that base. That’s why I was disappointed to see the following statement from a fellow OSS developer in response to the donation of a pom to get a new artifact added to the repo: “That’s great and all, but I don’t really care about Maven, nor do I really want to add or maintain a pom.xml in the project. Sorry.” Disclaimer: I’ve never used this project, nor do I know any of the developers, but the statement stands for itself.
The Maven Central repository is a great resource to the community. The
artifacts contained here represent a vast variety of open source
projects. Having the artifacts here not only enables easy consumption
by Maven users, but even Ant users via Ivy. Beyond the jars themselves, complete poms can be a wealth of information for users, such as where the source is located, mailing lists, which license is used, etc. Often the source and javadocs are packaged up for easy development in IDEs
There is some work occurring to abstract the artifact, metadata and
transport of artifacts to enable easy consumption by other tools. The intent of the maven-artifact-3.0 project is to provide a simple set of APIs that can operate against the repository data for dependency analysis and retrieval. The framework is being designed to allow pluggable rules to extend and support the various concepts in use out there such as Maven, OSGI and Ivy. All this is being done in a way to keep it fully decoupled from the Maven core code.
In
summary, the Central repository is a resource that enables greater
distribution and consumption of your project by many types of users. The desire make life easier for your users should transcend your personal views on any particular tool.
The Maven project does have a mechanism for taking community created poms (although we prefer they come from the project itself). If you run into a wall with some project and that isn’t enough to cause you to choose another implementation, then you can read more about how to get said walled project into the repository here.
Making it easier to get things into the Central repository is something we have been looking in to. We have some ideas, but the first step is working through the MEV list and we have recently started doing just that.
Maven has two sections in the pom relating to plugin configuration: project.build.plugins and project.build.pluginManagment.plugins. These two sections are unfortunately often confused and misused. Continue reading
