> From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]] > > > On Thu, 2002-05-30 at 11:58, James Taylor wrote: > >> On Thu, 2002-05-30 at 11:28, Jason van Zyl wrote: > >>> Hi, > >>> > >>> I am currently cleaning up all the JAR names in the repository: > >>> giving them versioned names and giving the -dev JARs the > versioning > >>> we agreed > >>> upon: id-yy-mm-dd-build#.jar. This makes things sortable. > >> > >> -1 on this naming convention. Rather than build number I > would prefer > >> to see a higher precision timestamp (something to the > second) of when > >> the checkout was done, so that one could recreate the jar from CVS. > > You don't give a reason for your -1
I thought he clearly stated it: -1 on id-yy-mm-dd-build.jar because the proposed format was in his mind preferable: id-yy-mm-dd-hh-MM-ss.jar Honestly, I don't care either way--but the build number is shorter. The problem with the build number approach is the question of who creates it? How is it calculated (sorry if you covered it already, I just jumped in here)? If the build number is pulled from a tag, or entry in CVS, then it might make sense. There is an artifact that exists between users. An example of what I mean follows. Suppose both you and Jason decide to add a new build at different times in the day to the repository. So we have Jon posting id-02-05-30-1.jar with the build number being tracked locally on your machine. Then we have Jason posting the same jar name later in the day, with a new build. The name hasn't changed because the build number is tracked local. Posible solution #1: The build number is determined by the latest jar. That means the task to name the jar would have to search for the most recently dated and highest build number jar, and then increment the build number. There comes a synchronization problem--supposing that Jon posted a new jar, and Jason hadn't upgraded Maven yet before creating a new build. Posible solution #2: Store the build number in CVS (a text file or something), allowing CVS to maintain it. That way the build can be programmatically incremented each time a new build is created for the same version. This allows the following name: id-ver-build.jar (i.e.: cocoon-2.0.4dev-342.jar) The build number would either be reset for each official release, or it would simply increment forever (like Winblows NT build 1384...) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
