Ok, you can use your sructure. Can you add poms files with this infos : - groupId - artifactId - name - currentVersion - dependencies
Emmanuel ----- Original Message ----- From: "Felipe Leme" <[EMAIL PROTECTED]> To: "Maven Developers List" <[EMAIL PROTECTED]> Sent: Friday, July 30, 2004 12:39 PM Subject: Re: Taglibs repository > On Fri, 2004-07-30 at 04:17, Emmanuel Venisse wrote: > > Structure is correct, but I prefer this: > > taglibs > > jars > > all jars > > The problem with that structure is that the project has many taglibs, so > the directory will be too packed (right now, for instance, there are 35 > jars, 87 tlds and 50 wars). The structure I proposed follows the same > approach used by the Jakarta Commons project. > > > and there are already a directory group taglibs on ibiblio. > > It's more usable if we have only one group by project. > > I agree, but that group is kind of rogue - nobody knows how it got there > and it has never been updated. And even if we use it, there is also a > jstl group too, so we would need to put the jstl jars over there (and > these jars are build from the Taglibs Standard project). > > I don't know how is the 'backward compatibility' policy on ibiblio, but > I rather remove these old groups (standard and jstl). If that is not > possible (and I guess it isn't), we could at least but a README there > stating they are obsolete groups. > > -- Felipe > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
