Thanks.
I forced a maven update and it works now.
Stephane
Ulrich Stärk a écrit :
Stephane Decleire schrieb:
I get this morning the bug described in JIRA TAP5-290.
Since this bug is supposed to be closed for 3 days now, how can i
know if the correction is taken into account in the last snaps
Stephane Decleire schrieb:
I get this morning the bug described in JIRA TAP5-290.
Since this bug is supposed to be closed for 3 days now, how can i know
if the correction is taken into account in the last snapshot ?
Thanks in advance.
Stephane
Check the date of the snapshot. They should be
Looking at Jira, the bug is supposed to be closed since 10/20, the
tapestry framework has been updated in my maven repository on 10/22 but
the error is still there, that's why i put this question ;-)
Stephane
Andy Pahne a écrit :
You may have a look at your local maven repo after mvn update
You may have a look at your local maven repo after mvn update. You can
tell from the snapshot's filename when it has been built.
You could also just give it a try to see if the error has gone...
Stephane Decleire schrieb:
I get this morning the bug described in JIRA TAP5-290.
Since this b
I get this morning the bug described in JIRA TAP5-290.
Since this bug is supposed to be closed for 3 days now, how can i know
if the correction is taken into account in the last snapshot ?
Thanks in advance.
Stephane
