Valid points. I add docs to that list. When unable to work on them, I suggest finding or creating JIRA issues and lobbying others to vote on them! This gives some indication to the Maven dev team what us users value.
_____ From: David Sag [mailto:[EMAIL PROTECTED] Sent: Friday, November 11, 2005 3:50 AM To: Maven Users List Subject: Re: CheckStyle html report contains no source link Unfortunately our firewalls here don't let me checkout the source from subversion servers that are not on https, so in this case I would need to go home, use my laptop to check out the source, build it there and then manually copy the jars to my windoze box at work. It would be easier for me, and anyone else where I work, if the update could just be released, as it clearly was fixed weeks ago. Isn't one of the points of using something like continuum that you can release nightly snapshot releases? It does make me wonder about other developers - the main issues i have with m2 are this javadoc bug, the lack of plugins for the standards code-quality tools, lack of support for the assert statement, and the obviously broken PMD and checkstyle plugins. All of this seems to indicate that formal code quality is not a concern for the majority of developers. Kind regards, Dave Sag Rik Bosman <[EMAIL PROTECTED]> wrote on 11-11-2005 09:16:35: > David, > The simplest solution before the release of Maven 2.0.1 is to download the > newest release yourself: > Actually it is quite simple: > - Download SVN (if not already on your machine) > - Checkout the maven source tree. "svn checkout > http://svn.apache.org/repos/asf/maven/components/trunk/ maven-site" > - Find the plugins directory, drill down to maven-javadoc > - Run the mvn commands "mvn compile" and "mvn install". > - The newest plugin is automatically added to your repository. > --rik > > 2005/11/11, David Sag <[EMAIL PROTECTED]>: > > > > > > I'm quite amazed that this long-standing bug with the javadoc plugin > > hasn't been addressed sooner. I know it's been fixed but is there a problem > > with actually releasing the fixed javadoc plugin? It's quite embarrassing > > giving demos of maven 2 and having to constantly explain that "this blank > > page is where the javadocs would be but for a bug." Or is javadoc generation > > a very very low priority for most developers? > > > > Kind regards, > > Dave Sag > > > > > > > > > > > > > > Brett Porter <[EMAIL PROTECTED]> wrote on 11-11-2005 05:12:23: > > > > > The fix will occur when the next javadoc plugin release is made. It > > > isn't currently scheduled. > > > > > > I'm not sure if the checkstyle plugin is correctly linking them - you > > > might need to file a bug. > > > > > > - Brett > > > > > > On 11/11/05, Rik Bosman <[EMAIL PROTECTED]> wrote: > > > > Brett, > > > > The plugin is working, the sources were generated. > > > > But still no links in the generated checkstyle report. Any > > suggestions? > > > > Another question: I read about the problem with the empty javadoc " > > > > index.html". > > > > The solution would be in maven 2.0.1. for what date is this release > > planned? > > > > --rik > > > > > > > > 2005/11/10, Brett Porter <[EMAIL PROTECTED]>: > > > > > > > > > > groupId = org.codehaus.mojo > > > > > artifactId = jxr-maven-plugin > > > > > > > > > > it is still in beta. > > > > > > > > > > On 11/10/05, Rik Bosman <[EMAIL PROTECTED]> wrote: > > > > > > Hi, > > > > > > I want to use maven2 to generate some reports (e.g. mvn site) to > > check > > > > > code > > > > > > produced by a company working for us in India. Generating the > > reports > > > > > for > > > > > > pmd and checkstyle goes pretty straightforward, but the html links > > (the > > > > > > mentioned line should be a link) are missing. I saw this feature > > in some > > > > > > examples which I found on the Internet. > > > > > > How could this be done? > > > > > > Currenty I only have a simple pom.xml with only 2 plugins. Do I > > need > > > > > > another plugin to generate the (xref?) sources? Where can > > thisplugin be > > > > > > found? > > > > > > Thanks a lot. > > > > > > Rik > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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] > > > > >
