You asked for that last night. The goal was that you could run with
`mvn
install` and no profiles.
I assumed that meant point to the TP site and run with .target file.
Nothing else :)
/max
Of course every solution brings with it a cost - the cost here is
downloading extra metadata when resolving.
If you want all those to be OPTIONAL and have the choice of "local" OR
"remote" rather than "local+remote" or "remote", then I can
revert to
what we had before.
N
On 04/01/2011 06:09 AM, Max Rydahl Andersen wrote:
>
>> That's a recent improvement:
>>
>> *30199 3/31/11 11:19 PM 1 nickboldt enable all activeByDefault=true
sites to be active w/o needing to specify via -P flag
>
> Yeah, not sure I would call that an improvement ;)
>
> adding "upstream" repos should be an additional flag IMO as long as p2 is
this slow to resolve against remote repos.
>
> /max
>
>> Denis
>>
>> On 04/01/2011 02:02 AM, Max Rydahl Andersen wrote:
>>>> This is ridiculously slow...
>>>>
>>> to be precise - on average 3m 50s is spent just checking/adding these sites
before it starts resolving anything.
>>>
>>> In every module...that's just stupid we have that as default.
>>>
>>> What became of the *single* Target Platform site which is meant to avoid all
this ?
>>> (maybe two for supporting upstream builds)
>>>
>>> /max
>>>
http://about.me/maxandersen
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
> /max
>
http://about.me/maxandersen
>
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev