Source changes - FishEye

Shows the 20 most recent commits for Dvsl.

Steve Loughran <stevel@apache.org> committed 3732eb195b3d24d6480a2d7edb2818b325a3e199 (2 files)
Reviews: none

working to get Axis & smartfrog to generate their task docs from this code. the generation is good, dvsl bad.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@276256 13f79535-47bb-0310-9956-ffa450edef68

Antoine Levy-Lambert <antoine@apache.org> committed 7cfb38d8871ff458c7f69ac9d1372947b7512921 (2 files)
Reviews: none

fixing dvsl to process CDATA embedded into <source> tags
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@275804 13f79535-47bb-0310-9956-ffa450edef68

Jason van Zyl committed 119870 (1 file)
Reviews: none

o forgot some dvsl refs

Jason van Zyl committed 119869 (1 file)
Reviews: none

o Removing dvsl references as it's no longer used.
o Adding entry about problems generating the site when there are
  conflicting versions of Jelly.

prickett committed 146901 (1 file)
Reviews: none

Added a dependency to the velocity-dvsl package so tat we could use
the xdoc plugin for maven.

Jason van Zyl committed 118869 (1 file)
Reviews: none

o Revert last change. I was trying to track the dvsl leak.

Søren Mortensen committed 118710 (1 file)
Reviews: none

o Using a new output format for the GoalsToXML tag, that wraps the goals in
  plugins. This allows to use the generated file much more easily in DVSL
  files, as we don't have to fight with DVSL tricks to guess the plugins.
o Thus, the xdoc generated from the tag is separated in plugins, one
  subsection for each.
o The image should soon gather the goals in plugins, to save space and to
  ease the reading of the relations between plugins. (Right now the
  generated graph doesn't fit on one page, but it should hopefully happen
  soon ... the next thing is to figure out how to arbitrarly add links to
  the Maven-generated pages :-) )

Jason van Zyl committed 118636 (3 files)
Reviews: none

o moving images into the xdocs/images directory where they should be. will
  probably have to tweak the dvsl.

james strachan committed 135095 (1 file)
Reviews: none

Patched the tag doclet so that the HTML documentation contained inside the javadoc comments comes out as XML so that it can be styled via XSLT, JSL, DVSL etc.

james strachan committed 145119 (1 file)
Reviews: none

Patched the tag doclet so that the HTML documentation contained inside the javadoc comments comes out as XML so that it can be styled via XSLT, JSL, DVSL etc.

Jason van Zyl committed 118419 (1 file)
Reviews: none

o Updating with new jelly and dvsl
PR:
Obtained from:
Submitted by:
Reviewed by:

Jason van Zyl committed 118418 (1 file)
Reviews: none

o Updating with new jelly and dvsl.
PR:
Obtained from:
Submitted by:
Reviewed by:

Jason van Zyl committed 118417 (1 file)
Reviews: none

o A couple <j:if>s in the xdoc generation to allow a site with no
  sources to generate documentation. The sourcesPresent and
  unitTestSourcesPresent are set to "false" in the driver so that
  the dvsl context doesn't freak out.

Søren Mortensen committed 118363 (3 files)
Reviews: none

- Added a new goal : "graph:goals-to-xdoc".
With this you generate an xdoc document in ${maven.gen.docs}/goals-report.xml.
This shows you Maven's and the project's goals, their description and their
prerequisites.

- goalstoxdoc.dvsl processed the template

- GoalsToXML has been tweaked to sort the goals by name, so that in the output,
  they are also sorted.

There is currently no link anywhere to the generated html file.

Jason van Zyl committed 118203 (1 file)
Reviews: none

Need the checkstyle dvsl. Decoupling is fun!

Jason van Zyl committed 118190 (1 file)
Reviews: none

I don't think the pdf.dvsl is actually being used, but i'm collecting
it with the pdf plugin.

kaz committed 117807 (4 files)
Reviews: none

Patch from St�phane MOR <stephane_listes@yahoo.fr>. Thanks!

[Stephane's comments]

- when you were on the "task-list.html" page, you didn't see the same
  menu as the other pages under "Project Reports". I added
  "task-list.xml" to the check for $infilename in
  "src/dvsl/xdocs/site.dvsl". While I was there, I reorganized this
  check, setting an array of files that are under "Project Info" and
  "Project Reports", and checking against that array. This way, the only
  thing we have to do is to add a file name in these arrays, and the
  menu will be the same than the other files under those categories.

- when you were on the "tasks.html" page, in the menu you didn't see the
  "Task List" link. This was because "tasks.xml" is not a generated page
  but a user page, and because the dvsl task generating the user docs in
  "src/templates/build/plugins/docs/build.xml" didn't set the tool
  "toolbox.string.genDoc", so you got an "invalid reference" error. I
  added the tool to the task.

- the "Project Reports" page had a title "Project Information". I set it
  to "Project Reports". (btw, on this page, you don't see the "Tasks"
  and "Task List" links. The "Tasks" link is commented for later
  use. What about the "Task List" link ? Should it be there ?)

- the "Source XReference" pages had a notice that said "This page
  generated by Maven", which misses a verb, no ? ;-) I set it to "This
  page was generated by Maven", "Maven" now being a link to the Maven
  homepage (btw, when will maven be a top-project ?).

kaz committed 117746 (2 files)
Reviews: none

The activity dvsl assumed project.xml was in the current directory.
This fails if maven was not invoked from the project's base directory as
pointed out by jmacgill. Thanks!

Dmitry Nezhevenko committed 117740 (19 files)
Reviews: none

- Converted core and bootstrap to using new parse less plugin process
- Fixed problem with gump converter dvsl
- Changed @todo tags to @tasks