Blog

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Image AddedThe Maven plugin buildmetadata-maven-plugin has been released with version 1.2.0.

This version of the plugin will make it easier to replace the build.properties with its XML counterpart buildmetadata.xml. There are also fixes that prevented the inclusion of certain build metadata into one of its reports.

We also cleaned up some dependencies. Especially the dependencies to various SCM implementations have been removed. The only supported SCM provider is still SVN.

For details on this version of the library please visit the project's homepage, for changes since the last version, please consult the release report.

 

...

 

Quote External
authorJ. Norris
source-dateOctober 24, 2013 at 7:49 pm

When will this version be in the Maven repo? I’m trying to use V1.1.5 to get the SVN version but no SCM data appears in the build.properties file so I was hoping the new version would provide that info.

Quote External
authorJ. Norris
source-dateOctober 24, 2013 at 7:56 pm

I found that the reason I wasn’t seeing SCM information was because it is executing a command line and my SVN credentials are not saved.

Still would like to know when 1.2.0 is available in the maven repo.

Quote External
authorRobert
author-urihttps://www.smartics.eu/confluence/display/HOMESPACE/Robert+Reiner
source-dateOctober 25, 2013 at 10:09 am

Currently we have no plans to add our artifacts to Maven Central due to the additional work required. We have a couple of plugins, tools and libraries and we have to handle them all equally. Our projects usually depend on a number of other libraries, configurations, plugins, and POM files that are also not available in the Maven repository. So this is not a “deploy one artifact” effort. Due to our limited time resources, releasing them to our smartics repository is our preferred way.

As long as adding our artifact repository to our user’s repository configuration adds no significant burden or is otherwise not an option, we would continue with our current process of releasing our projects. You probably know the Accessing Artifacts information on our site. In the last years only very few users requested the availability in the Maven repository.

But we are reconsidering our strategy regularly … Image Added

BTW: The latest version of the buildmetadata plugin is available at http://www.smartics.eu/buildmetadata-maven-plugin.

Quote External
authorJ. Norris
source-dateOctober 25, 2013 at 1:39 pm

Hi Robert,

Thanks for the reply. It is the smartics repository I was referring to. The latest version I saw there was 1.1.6-SNAPSHOT.

Jim

Quote External
authorRobert
author-urihttps://www.smartics.eu/confluence/display/HOMESPACE/Robert+Reiner
source-dateOctober 25, 2013 at 2:08 pm

Hi Jim,

thank you for your comment!

This is a problem due to the Maven conventions we now adhere to, but haven’t been followed from the start. The naming scheme maven-xyz-plugin is reserved for plugins provided by Maven. Therefore we had to rename the maven-buildmetadata-plugin (latest release 1.1.5) to buildmetadata-maven-plugin (latest release as of today 1.3.0).

So here are the versions of maven-buildmetadata-plugin (up to version 1.1.6-SNAPSHOT as you reported) and here are the versions of buildmetadata-maven-plugin (version 1.1.6 and up).

We recognized the problem and are working on a solution to make our users aware of the renaming issue. I’m sorry for the lack of transparency and the mess it entails.

Robert

Quote External
authorJ. Norris
source-dateOctober 25, 2013 at 2:09 pm

Hi Robert,

I saw the blog about the renaming and it didn’t register in my brain. Thanks for the update. I’ll make the change.

Jim