>
> Since the only usecase for this is to get our current parent
> snapshots and every other jboss project already require changes to
> settings.xml i'm not too worried - especially if we can just provide
> a settings.xml to do it.
Sounds like the right solution is to move the repository settings down into the
individual project parent poms (SwitchYard uses this approach). That said, if they're
all including the same repo, it makes me wonder if we'd just be jumping through hoops
for no real benefit.
Any project that needs to go into a product and not infect your users pom's will need
to remove this reference.
It is simply wrong to do. And yes it sucks but the consequences are rather annoying for
those users wanting to do reproducible builds.
/max