AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Maven will download metadata files (or look them into your local repository if they are already downloaded), called maven-metadata.xml, from each remote repositories at those group ids. The second step is how that search is actually performed. Therefore, with the configuration above, and a command of mvn foo:bar, Maven will look for a plugin having a prefix of foo inside the group id, and. It searches those default ones after the ones you configured in the settings. By default, and in addition to the groups specified in the settings, Maven also searches the group ids and. What this does, is telling Maven which group id it is supposed to consider when you're using a prefix in a command. In the settings.xml file, you can add plugin groups, in the form of: Maven must have a way to deduce that foo actually means my.oupId:foo-maven-plugin. If you don't want this default assignment, you can still configure your own with the help of the maven-plugin-plugin and its goalPrefix parameter. Put another way, if your plugin's artifact id is named foo-maven-plugin, Maven will automatically assign it a prefix of foo. If your plugin's artifactId fits this pattern, Maven will automatically map your plugin to the correct prefix in the metadata stored within your plugin's groupId path on the repository.
0 Comments
Read More
Leave a Reply. |