[Hawkular-dev] maven stuff

Thomas Heute theute at redhat.com
Thu Feb 26 10:06:31 EST 2015


On 02/26/2015 03:54 PM, John Mazzitelli wrote:
>> You could have used that new version in the kettle pom (where this plugin is
>> actually needed?) and only release
>> this now. Then have the version added to the root-pom and when this is
>> available removed in kettle.
> It was actually in the nest distro module, not kettle.
>
> But that is what I ended up doing! But you realize that now you are asking people to have to remember to go back and remove code when a release is available (where this code was just a temporary fix that I had to add to work around this annoying workflow - so you just made it more annoying to have to remember to go back and take out code I didn't want to add in the first place :). And will I remember to do that once the release is made??
>
> And BTW it's against "convention" to use <versions> in our poms, no?
No, put them at the most top level of your project.
> We shouldn't be overriding <versions> - we should be just referring to <artifactId> and letting the parent pom decide what versions to use so we all use the same versions.
>
> In any event, yes, that is what I ended up doing. Which reminds me, I don't think I did remove my temporary <version> fix - I think I need to go do that :)
Don't put all versions in the POM/BOM for reasons I already explained a 
couple of times ;)

Thomas

> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev



More information about the hawkular-dev mailing list