Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Thanks. Reading further a couple pages later showed me the Release Plugin you were talking about. So, in short, it appears that this release plugin does exactly what I have been manually doing, and the only thing that it needs in order to do so is just an aggregator pom. And even then, that's only so that all projects aggregated into that aggregator can get promoted as a single unit. Do I understand that right? It sounds like this is that missing relationship that I was talking about in my original post? Are aggregator poms the way to show these relationships? Commented Mar 13 at 9:08
  • There is also one part of my question that I still don't see an answer for -- what do I put in the <version> tag of my dependencies? Sure, I could put a version into <properties> of UtilsLibrary and reference that in the application poms. But would the release plugin know to update that <properties> value? Can I configure it to do that? Commented Mar 13 at 9:13