Perhaps it might be better to use profiles then, instead of
settings.xml. Default profile defines the public repo's and can be deactivated for
product builds. WDYT?
this is not specific to product builds - anyone that references your pom will get this
repo "injected" into their build.
It's bad style in community too.
/max
----- Original Message -----
>>>
>>> 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
>
>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev