You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "M. Sean Gilligan (JIRA)" <ji...@codehaus.org> on 2005/04/24 23:26:46 UTC
[jira] Created: (MPXDOC-141) Perform JSL transforms on xdocs *only* when they have changed
Perform JSL transforms on xdocs *only* when they have changed
-------------------------------------------------------------
Key: MPXDOC-141
URL: http://jira.codehaus.org/browse/MPXDOC-141
Project: maven-xdoc-plugin
Type: Improvement
Versions: 1.8
Environment: Maven 1.0.2
Reporter: M. Sean Gilligan
Assigned to: Arnaud HERITIER
Attachments: speedup.diff
Speed up the "maven site" command be eliminating tranforms of unchanged documents. (Patch attached.)
There are also some ant image and stylesheet copies that seem to me should have overwrite="false" to eliminate redundant copies. Is there a reason for overwrite="true"?
Brent Worden said on the maven dev list: "You might want to include some more source files for the uptodate check. The pom, the site.jsl or custom jsl, navigation.xml, properties files, and other files all contribute to the site contents."
I'm not sure exactly what the build dependencies are (I can't really read jelly/jsl code that well) but I think some of the dependencies are handled before we get to this step, since it the performJSL tag is called for srcdir="${maven.gen.docs}" and srcdir="${maven.docs.src}" and the "uptodate" check is called inside a j:forEach loop. So, I *think* some of the dependencies you mentioned may have already been handled.
I'm pretty sure that the site.jsl and navigation dependencies should be handled within this "uptodate" tag. I'm just not comfortable enough with the jelly, jsl, etc. to be comfortable trying to handle all the dependencies.
The patch that I have does accelerate my build significantly when things haven't changed, but there is a risk that someone could be burned by a dependency not being handled and a source change not being reflected in the generated site.
(Estimated work remaining assumes strong knowledge of jelly and jsl)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPXDOC-141) Perform JSL transforms on xdocs *only* when they have changed
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPXDOC-141?page=all ]
Lukas Theussl updated MPXDOC-141:
---------------------------------
Description:
Speed up the "maven site" command be eliminating tranforms of unchanged documents. (Patch attached.)
There are also some ant image and stylesheet copies that seem to me should have overwrite="false" to eliminate redundant copies. Is there a reason for overwrite="true"?
Brent Worden said on the maven dev list: "You might want to include some more source files for the uptodate check. The pom, the site.jsl or custom jsl, navigation.xml, properties files, and other files all contribute to the site contents."
I'm not sure exactly what the build dependencies are (I can't really read jelly/jsl code that well) but I think some of the dependencies are handled before we get to this step, since it the performJSL tag is called for srcdir="${maven.gen.docs}" and srcdir="${maven.docs.src}" and the "uptodate" check is called inside a j:forEach loop. So, I *think* some of the dependencies you mentioned may have already been handled.
I'm pretty sure that the site.jsl and navigation dependencies should be handled within this "uptodate" tag. I'm just not comfortable enough with the jelly, jsl, etc. to be comfortable trying to handle all the dependencies.
The patch that I have does accelerate my build significantly when things haven't changed, but there is a risk that someone could be burned by a dependency not being handled and a source change not being reflected in the generated site.
(Estimated work remaining assumes strong knowledge of jelly and jsl)
was:
Speed up the "maven site" command be eliminating tranforms of unchanged documents. (Patch attached.)
There are also some ant image and stylesheet copies that seem to me should have overwrite="false" to eliminate redundant copies. Is there a reason for overwrite="true"?
Brent Worden said on the maven dev list: "You might want to include some more source files for the uptodate check. The pom, the site.jsl or custom jsl, navigation.xml, properties files, and other files all contribute to the site contents."
I'm not sure exactly what the build dependencies are (I can't really read jelly/jsl code that well) but I think some of the dependencies are handled before we get to this step, since it the performJSL tag is called for srcdir="${maven.gen.docs}" and srcdir="${maven.docs.src}" and the "uptodate" check is called inside a j:forEach loop. So, I *think* some of the dependencies you mentioned may have already been handled.
I'm pretty sure that the site.jsl and navigation dependencies should be handled within this "uptodate" tag. I'm just not comfortable enough with the jelly, jsl, etc. to be comfortable trying to handle all the dependencies.
The patch that I have does accelerate my build significantly when things haven't changed, but there is a risk that someone could be burned by a dependency not being handled and a source change not being reflected in the generated site.
(Estimated work remaining assumes strong knowledge of jelly and jsl)
Fix Version: 1.10
> Perform JSL transforms on xdocs *only* when they have changed
> -------------------------------------------------------------
>
> Key: MPXDOC-141
> URL: http://jira.codehaus.org/browse/MPXDOC-141
> Project: maven-xdoc-plugin
> Type: Improvement
> Versions: 1.8
> Environment: Maven 1.0.2
> Reporter: M. Sean Gilligan
> Fix For: 1.10
> Attachments: speedup.diff
>
> Original Estimate: 4 hours
> Remaining: 4 hours
>
> Speed up the "maven site" command be eliminating tranforms of unchanged documents. (Patch attached.)
> There are also some ant image and stylesheet copies that seem to me should have overwrite="false" to eliminate redundant copies. Is there a reason for overwrite="true"?
> Brent Worden said on the maven dev list: "You might want to include some more source files for the uptodate check. The pom, the site.jsl or custom jsl, navigation.xml, properties files, and other files all contribute to the site contents."
> I'm not sure exactly what the build dependencies are (I can't really read jelly/jsl code that well) but I think some of the dependencies are handled before we get to this step, since it the performJSL tag is called for srcdir="${maven.gen.docs}" and srcdir="${maven.docs.src}" and the "uptodate" check is called inside a j:forEach loop. So, I *think* some of the dependencies you mentioned may have already been handled.
> I'm pretty sure that the site.jsl and navigation dependencies should be handled within this "uptodate" tag. I'm just not comfortable enough with the jelly, jsl, etc. to be comfortable trying to handle all the dependencies.
> The patch that I have does accelerate my build significantly when things haven't changed, but there is a risk that someone could be burned by a dependency not being handled and a source change not being reflected in the generated site.
> (Estimated work remaining assumes strong knowledge of jelly and jsl)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MPXDOC-141) Perform JSL transforms on xdocs *only* when they have changed
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPXDOC-141?page=all ]
Lukas Theussl closed MPXDOC-141:
--------------------------------
Resolution: Fixed
Patch applied with slight modification: I introduced a new property 'maven.xdoc.skip.uptodate' so the speed-up may be switched on optionally (default is off). Thanks!
> Perform JSL transforms on xdocs *only* when they have changed
> -------------------------------------------------------------
>
> Key: MPXDOC-141
> URL: http://jira.codehaus.org/browse/MPXDOC-141
> Project: maven-xdoc-plugin
> Type: Improvement
> Versions: 1.8
> Environment: Maven 1.0.2
> Reporter: M. Sean Gilligan
> Fix For: 1.10
> Attachments: speedup.diff
>
> Original Estimate: 4 hours
> Remaining: 4 hours
>
> Speed up the "maven site" command be eliminating tranforms of unchanged documents. (Patch attached.)
> There are also some ant image and stylesheet copies that seem to me should have overwrite="false" to eliminate redundant copies. Is there a reason for overwrite="true"?
> Brent Worden said on the maven dev list: "You might want to include some more source files for the uptodate check. The pom, the site.jsl or custom jsl, navigation.xml, properties files, and other files all contribute to the site contents."
> I'm not sure exactly what the build dependencies are (I can't really read jelly/jsl code that well) but I think some of the dependencies are handled before we get to this step, since it the performJSL tag is called for srcdir="${maven.gen.docs}" and srcdir="${maven.docs.src}" and the "uptodate" check is called inside a j:forEach loop. So, I *think* some of the dependencies you mentioned may have already been handled.
> I'm pretty sure that the site.jsl and navigation dependencies should be handled within this "uptodate" tag. I'm just not comfortable enough with the jelly, jsl, etc. to be comfortable trying to handle all the dependencies.
> The patch that I have does accelerate my build significantly when things haven't changed, but there is a risk that someone could be burned by a dependency not being handled and a source change not being reflected in the generated site.
> (Estimated work remaining assumes strong knowledge of jelly and jsl)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPXDOC-141) Perform JSL transforms on xdocs *only* when they have changed
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPXDOC-141?page=all ]
Arnaud Heritier updated MPXDOC-141:
-----------------------------------
Assign To: (was: Arnaud Heritier)
> Perform JSL transforms on xdocs *only* when they have changed
> -------------------------------------------------------------
>
> Key: MPXDOC-141
> URL: http://jira.codehaus.org/browse/MPXDOC-141
> Project: maven-xdoc-plugin
> Type: Improvement
> Versions: 1.8
> Environment: Maven 1.0.2
> Reporter: M. Sean Gilligan
> Attachments: speedup.diff
>
> Original Estimate: 4 hours
> Remaining: 4 hours
>
> Speed up the "maven site" command be eliminating tranforms of unchanged documents. (Patch attached.)
> There are also some ant image and stylesheet copies that seem to me should have overwrite="false" to eliminate redundant copies. Is there a reason for overwrite="true"?
> Brent Worden said on the maven dev list: "You might want to include some more source files for the uptodate check. The pom, the site.jsl or custom jsl, navigation.xml, properties files, and other files all contribute to the site contents."
> I'm not sure exactly what the build dependencies are (I can't really read jelly/jsl code that well) but I think some of the dependencies are handled before we get to this step, since it the performJSL tag is called for srcdir="${maven.gen.docs}" and srcdir="${maven.docs.src}" and the "uptodate" check is called inside a j:forEach loop. So, I *think* some of the dependencies you mentioned may have already been handled.
> I'm pretty sure that the site.jsl and navigation dependencies should be handled within this "uptodate" tag. I'm just not comfortable enough with the jelly, jsl, etc. to be comfortable trying to handle all the dependencies.
> The patch that I have does accelerate my build significantly when things haven't changed, but there is a risk that someone could be burned by a dependency not being handled and a source change not being reflected in the generated site.
> (Estimated work remaining assumes strong knowledge of jelly and jsl)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org