Re: [All] CP definitions
On Thu, 20 Sep 2018 08:53:38 -0400, Rob Tompkins wrote:
On Sep 20, 2018, at 3:10 AM, Benedikt Ritter <britter@xxxxxxxxxx>
Reverting this change was discussed here . It was a result of
commit  breaking multiple component builds. As Stefan points out
initial change does not make sense, since the componentId is always
the name without "commons-" (e.g. math4). But the folders for all
websites have the commons prefix (e.g. commons-math).
I just restored the old (working) behavior. I'm fine with making
easier/more straight forward. But let's make sure that all the other
components still work.
I’m relatively indifferent to how we accomplish this. For the sake of
discussion let our project.artifactId=commons-something where N
represents the major version of the release with N being the empty
string for a major version equal to 1. We still are stuck with half
our projects in one state for building with componentid=something and
the other half with componentid=somethingN. Furthermore we need a
properties representing both “something” as well as “somethingN”
that we have our dist urls and site urls not containing the major
Do you propose something other than:
and change [parent] back to
What about starting from maven requirements and try and avoid
redundancies (that ultimately lead to inconsistencies)?
Can the parent POM generate the properties values required by
the "Commons" infrastructure from those (using maven plugin
code, I guess)?
E.g. generate "commons-lang" (a.o. to generate the path to the
web site's SVN repository) from
[Side-effect would be to enforce the rule for changing top-level
package name in step with a new major version.]
If so, what is it? Let’s pick it and move forward.
June conversation on the matter as well.
To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx