Thanks for the response. Yes, I believe I am on an older beta, but don't have an idea of which, i'm guessing <= beta5 (README.txt is empty and have misplaced the original zip)
http://jakarta.apache.org/turbine/maven/reference/properties.html is broken (referring page is http://jakarta.apache.org/turbine/maven/reference/project-descriptor.html) http://jakarta.apache.org/turbine/maven/reference/build-file.html is broken (same referring page) There are other broken ones from that referring page. I will take a look at most recent beta, and perhaps will address my issue with maven.dependency.classpath, etc. Thanks Chuck Scott [EMAIL PROTECTED] http://www.networkgps.com/ ----- Original Message ----- From: chuck scott To: [EMAIL PROTECTED] Sent: Sunday, October 20, 2002 2:06 PM Subject: maven plugin architecture and classpath Hi, I've seen in the past, doc of the maven plugin architecture, on maven's website. However, those pages seem to be broken and have resorted to Google's cache to access them. Is this documentation in the process of being overhauled/updated? I am trying to access maven.dependency.classpath in a plugin since it seems impossible to access from top level build.xml (integrated w/maven delegator targets). I have a forked process from ant that would benefit from a non hardcoded classpath. I have attempted integration of this script in one of the callback plugins (such as post-env-callback) via assoc property settings, but am frustrated because this plugin like others get called multiple times (even though it does give me access to this property). Any thoughts or ways around this problem without hardcoding the CLASSPATH? Thanks in advance. Chuck Scott NetworkGPS http://www.networkgps.com/ [EMAIL PROTECTED]
