Leo Simons wrote:
do that, but the big disadvantage with deviating from the existing maven/centipede/ruper
practice is that it deviates from that practice, thus requiring work and reducing compatibility. If you
feel like holding a vote, by all means feel free, I'll probably vote -1 for deviating from the existing
format (unless you've got a good argument rather than preference; I share your preference but it
is just that ;)
Speaking for Centipede, the format of the repository is of little matter.
Proabably only a day or two to update ruper. Since no one is use the Apache Jars Repository there is no campatability issue
The important thing is making the structure is relatively stable, while allowing for growth. We need to apply sams thoughts on coping with change http://www.intertwingly.net/stories/2002/03/15/copingWithChange.html to this directory strucutre.
So I am for
/projectname/[subproject]/[version]/file[-version].jar
That leo suggested.
cheers,
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Nick Chalko Show me the code. Centipede Ant + autodownloadable build plugins + needed jars autodownload. http://krysalis.org/centipede ---------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
