I like not having my settings.xml messed up with project-specific settings.
I like Peter's suggestion of:
* we keep snapshots in hawkular-parent in a dedicated "snapshots" profile that
will be off by default
If you want to pull down a snapshot, you have to explicitly ask for it with something
(-Psnapshots or whatever).
You can put THAT in your settings.xml if you want it, but at least it won't be
required.
----- Original Message -----
On 2015-06-01 15:43, Thomas Segismont wrote:
> But then we won't be able to work with a component SNAPSHOT unless we
> built it, correct?
Yes, that is the option I prefer myself.
But there is a couple of intermediate options:
* you add the snapshots repo in your settings.xml
* we keep snapshots in hawkular-parent in a dedicated "snapshots"
profile that will be off by default
-- P
> In this case, I'm not sure I like the idea.
>
> Le 01/06/2015 15:26, Peter Palaga a écrit :
>> Hi *,
>>
>> I see it as a good occasion to remove the JBoss snapshots repository [1]
>> from hawkular-parent, once all version.org.hawkular.* props [2] become
>> "-SNAPSHOT"-less in hawkular master.
>>
>> Is there anybody against this?
>>
>> Thanks,
>>
>> Peter
>>
>> [1]
>>
https://github.com/hawkular/hawkular-parent-pom/blob/b4daf82bd3b9d98c34fc...
>>
>> [2]
https://github.com/hawkular/hawkular/blob/master/pom.xml#L87-L96
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev