[GRADLE-650] Invalid date used for snapshot installs Created: 24/Sep/09  Updated: 04/Jan/13  Resolved: 24/Nov/10

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 0.9-rc-1

Type: Bug
Reporter: Russel Winder Assignee: Hans Dockter
Resolution: Fixed Votes: 0


Snapshot jars installed into the local Maven cache using the Maven plugin are being given version numbers with dates starting 09, where they should start 2009, i.e. the number is not a valid ISO 8601 date.

Comment by Hans Dockter [ 29/Sep/09 ]

But this is the way Maven want to do things. And we need to be Maven compatible in this case rather than ISO compatible. So this is an issue for the Maven Jira.

Comment by Russel Winder [ 29/Sep/09 ]

Can you point me at where Maven says this? The Maven Ant task by default uses numbers such as:


for labelling uploaded snapshots, so whilst not ISO8601 compliant at least they are using the full year.


Comment by Hans Dockter [ 29/Sep/09 ]

We are using the Maven Ant tasks.

Comment by Russel Winder [ 29/Sep/09 ]

OK, I will do some experiments and see what is going wrong. If I find something I will reopen this JIRA – or raise an issue against the Maven Ant task or Maven depending on who is doing this wrong.

Comment by Russel Winder [ 01/Oct/09 ]

According to Maven: The Definitive Guide, p157, snapshot version numbers are expanded to dates in the form yyyymmdd-hhmmss-n so a full date is expected not one starting with just the last two digits of the year.

Comment by Russel Winder [ 15/Oct/09 ]

Closing this again as it is not clear where the problem lies. If the problem hinted at can be reliably reproduced then this can be reopened or a new issue raised.

Generated at Wed Jun 30 11:35:21 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.