I thought there already was a standard, at least as far as dependencies
go: under Project Info...Dependencies?  I recall asking about this a few
months back and was told all the Commons projects at least used this
convention... Maybe this isn't auto-generated?  I remember at the time I
said I thought it should be a bit easier to find, but regardless of that,
if it was a standard all projects (not just commons) followed, would that


Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
AIM/Yahoo: fzammetti
Author of "Practical Ajax Projects With Java Technology"
 (2006, Apress, ISBN 1-59059-695-1)
Java Web Parts - http://javawebparts.sourceforge.net
 Supplying the wheel, so you don't have to reinvent it!

On Tue, September 12, 2006 5:28 pm, Daniel F. Savarese wrote:
> In message <[EMAIL PROTECTED]>,
> "Yoav
> Shapira" writes:
>>(e.g. build.properties).  I'm hesitant to have a separate web page
>>just to list dependencies unless that page is auto-generated (as is
> I agree.  I'm sure there's a way to autogenerate a master table for
> all the mavenized projects, but since I'm not volunteering to do it,
> I'm not going to suggest it.  I haven't seen anyone listing their JDK
> requirements in the maven dependency report.  Could we then just ask
> mavenized projects to add their minimum JDK requirement to the
> dependencies
> report (I've never tried entering a 'fake' entry and ant projects
> to add the info to their docs if they don't already have it?
> These situations are always weird for me since I'm not the one
> experiencing the actual issue, yet have been asked to raise it.
> However, I think it's a reasonable reminder that despite all the
> progress Jakarta has made, users still have problems navigating
> our documentation.
> daniel
> ---------------------------------------------------------------------
> 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]

Reply via email to