Hi guys,
I quite like @Grab for small applications/demo/scripting but it has a big
pitfall in development at the moment - at least for me: it doesn't support
maven snapshots.
Concretely without tuning ivy.xml config or grapes you will resolve once
the snapshot then use an outdated version.
I ope
Hi guys,
Using groovy bundle (export PATH=$GROOVY_HOME/bin:$PATH) I often hit a
blocker: servlet-api is there. It means that if you use tomcat you will use
the wrong servlet api and get some troubles (missing message bundle, wrong
version etc...).
It can be overriden with setting up a custom groo
On 06.01.2017 10:45, Romain Manni-Bucau wrote:
[...]
I opened https://issues.apache.org/jira/browse/GROOVY-8037 to try to
enhance it but there are still a few questions to solve before coding:
- does groovy prefer a snapshot hack in ivy resolution or a full
aether/maven resolution support?
bei
2017-01-06 14:54 GMT+01:00 Jochen Theodorou :
> On 06.01.2017 10:45, Romain Manni-Bucau wrote:
> [...]
>
>> I opened https://issues.apache.org/jira/browse/GROOVY-8037 to try to
>> enhance it but there are still a few questions to solve before coding:
>>
>> - does groovy prefer a snapshot hack in i
On 06.01.2017 15:00, Romain Manni-Bucau wrote:
[...]
Means SNAPSHOT patterns needs to be identified (likely a flag in the
@Grab(snapshot=true)?) and groovy should clean up the artifacts before
resolving to avoid to let ivy mess up its repo.
which means it is more than just a change in the confi
2017-01-06 15:33 GMT+01:00 Jochen Theodorou :
> On 06.01.2017 15:00, Romain Manni-Bucau wrote:
> [...]
>
>> Means SNAPSHOT patterns needs to be identified (likely a flag in the
>> @Grab(snapshot=true)?) and groovy should clean up the artifacts before
>> resolving to avoid to let ivy mess up its re
