Ok this is more insanity... who was it that thought that renaming files as the simiplest solution to ordering? Right and I am a goat "moo moo".
It works as it is right now... leave it alone. There is no need for prefixed sorting or this cryptix semi-suffix sorting blah. If users want this maddness then implement a pluggable sorter/whatever and let the users complicate there lives. Lets not go renaming everything though just to meet this rather ridiculous rtequiremnt that Marc is demanding. Look at where this is going to be useful, who is going to be using it and what percentage of those users in those situations will need to make use of it to get around deployment problems. The pecentage is going to be very, very low... so why go changing a system that works? Especiall close to a final release... this is just plain madness. --jason Quoting Larry Sanderson <[EMAIL PROTECTED]>: > I *really* don't like jar1.jar, sar2.sar. Let's make the naming convention > a little less likely to stumbled upon by unknowing users. I suggest: > jar_jb1.jar, sar_jb2.sar, etc... then the default sorting can look for > "indexed" deployments first, and sort the remainder by type. This allows a > simple, global comparator, but removes the fine-grained support you > suggest. > So given the following within a directory: > > jetty.sar > my_ejb_ver4.jar > jar_jb5.jar > sar_jb10.sar > > This would order them thus: > jar_jb5.jar <-- all "indexed" deployments first > sar_jb10.sar > jetty.sar <-- all others second, in order of sar,rar,jar,war,ear > my_ejb_ver4.jar > > Hell, if they really need the flexibility you suggest then they can set up > a > second scanner, but I can't imagine any place where this is not sufficient. > > -Larry ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
