jkesselm commented on PR #110:
URL: https://github.com/apache/xalan-java/pull/110#issuecomment-1807568691

   STATUS UPDATE:
   
   1) Since we're now compiling the taglet ourselves, javadoc can't run until 
after that has happened. Changed the command line; would prefer to have 
dependencies drive that... Best thought I have is to move the javadoc operation 
into a lightweight module with dependency upon the taglet, possibly into the 
same one that is now doing the binary zipfile. Is there a better way for Maven 
to handle that? Note that this needs to happen before bin.zip is generated.
   
   2) Still need to move/copy 
./buildBinaryRelease/target/xalan-release-2.7.3-bin.zip and 
./target/xalan-project-2.7.3-source-release.zip into the build/ directory for 
Ant output emulation. (Which I still want to have if we can do it.) Again, 
there's the timing question of doing the copy only after the bin.zip exists; is 
that best handled through phase (pre-install?), another dependent module, or 
will just putting it in package do the right thing.
   
   3) I'm not certain which phase the source-release.zip should be generated 
during. Arguably, it can occur at any time, since it shouldn't be relying on 
generated artifacts, so leaving it in packaging of the parent module should 
work... but may not be stylistically correct. It can be copied to the 
appropriate place during package, assuming it has been generated by then.
   
   4) I'm still not generating the individual sample jarfiles, or the warfile 
for the one sample packaged that way. It isn't clear the former separations are 
needed now that everyone has lots of memory and bandwidth to play with, but the 
latter is an outstanding issue. Should this be a sub-submodule under samples, 
or is there a better way to handle it?
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org

Reply via email to