Re: confirm unsubscribe from users@maven.apache.org
On 2012-05-16 07:38, users-h...@maven.apache.org wrote: Hi! This is the ezmlm program. I'm managing the users@maven.apache.org mailing list. I'm working for my owner, who can be reached at users-ow...@maven.apache.org. To confirm that you would like n...@cynareae.com removed from the users mailing list, please send a short reply to this address: users-uc.1337168294.llekhlfokhdmmhollbkh-nate=cynareae@maven.apache.org Usually, this happens when you just hit the reply button. If this does not work, simply copy the address and paste it into the To: field of a new message. or click here: mailto:users-uc.1337168294.llekhlfokhdmmhollbkh-nate=cynareae@maven.apache.org I haven't checked whether your address is currently on the mailing list. To see what address you used to subscribe, look at the messages you are receiving from the mailing list. Each message has your address hidden inside its return path; for example, m...@xdd.ff.com receives messages with return path: users-return-number-mary=xdd.ff@maven.apache.org. Some mail programs are broken and cannot handle long addresses. If you cannot reply to this request, instead send a message to users-requ...@maven.apache.org and put the entire address listed above into the Subject: line. --- Administrative commands for the users list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: users-subscr...@maven.apache.org To remove your address from the list, send a message to: users-unsubscr...@maven.apache.org Send mail to the following for info and FAQ for this list: users-i...@maven.apache.org users-...@maven.apache.org Similar addresses exist for the digest list: users-digest-subscr...@maven.apache.org users-digest-unsubscr...@maven.apache.org To get messages 123 through 145 (a maximum of 100 per request), mail: users-get.123_...@maven.apache.org To get an index with subject and author for messages 123-456 , mail: users-index.123_...@maven.apache.org They are always returned as sets of 100, max 2000 per request, so you'll actually get 100-499. To receive all messages with the same subject as message 12345, send a short message to: users-thread.12...@maven.apache.org The messages should contain one line or word of text to avoid being treated as sp@m, but I will ignore their content. Only the ADDRESS you send to is important. You can start a subscription for an alternate address, for example john@host.domain, just add a hyphen and your address (with '=' instead of '@') after the command word: users-subscribe-john=host.dom...@maven.apache.org To stop subscription for this address, mail: users-unsubscribe-john=host.dom...@maven.apache.org In both cases, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete your subscription. If despite following these instructions, you do not get the desired results, please contact my owner at users-ow...@maven.apache.org. Please be patient, my owner is a lot slower than I am ;-) --- Enclosed is a copy of the request I received. Return-Path: n...@cynareae.com Received: (qmail 99188 invoked by uid 99); 16 May 2012 11:38:13 - Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 11:38:13 + X-ASF-Spam-Status: No, hits=-14.7 required=10.0 tests=ASF_EMPTY_LIST_OPS,ASF_LIST_OPS,ASF_LIST_UNSUB_A,EMPTY_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [173.248.187.2] (HELO echo.supportedns.com) (173.248.187.2) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 11:38:07 + Received: from cynareae by echo.supportedns.com with local (Exim 4.77) (envelope-from n...@cynareae.com) id 1SUcY6-003ofF-Jv for users-unsubscr...@maven.apache.org; Wed, 16 May 2012 07:37:46 -0400 To: users-unsubscr...@maven.apache.org Subject: X-PHP-Script: www.cynareae.com/roundcube/index.php for 38.109.144.30 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 16 May 2012 07:37:46 -0400 From: Nate Stoddard n...@cynareae.com Message-ID: e0359bf57e7c5e3ad791e79a5744a...@cynareae.com X-Sender: n...@cynareae.com User-Agent: Roundcube Webmail/0.7.1 Sender: cynar...@echo.supportedns.com X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - echo.supportedns.com X-AntiAbuse: Original Domain - maven.apache.org X-AntiAbuse: Originator/Caller UID/GID - [2158 32008] / [47 12] X-AntiAbuse: Sender Address Domain - cynareae.com X-Source: /usr/local/lsws/fcgi-bin/lsphp-5.2.17 X-Source-Args: lsphp5:home/cynareae/public_html/roundcube/index.php X-Source-Dir: cynareae.com
Report Plugin Dependencies (Maven 3 style) for Site
I'm trying to use the new Maven 3 style of generating reports, but
I'm having problems with one in particular. I have some custom
Checkstyle checks, but I'm not able to add the dependency in the right
spot to make everything work. Here's part of my POM:
org.apache.maven.plugins
maven-site-plugin
3.0-beta-3
[deleted]
checkstyle
${project.version}
org.apache.maven.plugins
maven-checkstyle-plugin
2.8
[deleted]/checkstyle.xml
In previous
versions of Maven, I could add dependencies to the actual report plugin,
but not anymore. Adding the dependency to the maven-site-plugin doesn't
work since it's added to the wrong level of the classloader. In this
case two classloaders are created: 1) maven-site-plugin, which is the
parent classloader of 2) maven-checkstyle-plugin. The Checkstyle JAR is
added to (2), so by adding my dependency to the the maven-site-plugin
(1) things won't work because it can't reference the Checkstyle types in
(2). Adding the Checkstyle JAR as an additional dependency doesn't work
either since the types from different classloaders are incompatible.
There's no way of adding the dependency such that it ends up in (2).
I've tried configuring the plugin under the pluginManagement section
also, but that seems to be ignored for the newest style.
I'm just
wondering if this is even possible, or if I need to roll back my
reporting configurations to the older style until the newer one is fixed
up and functioning better.
Nate Stoddard
Report Plugin Dependencies (Maven 3 style) for Site
I'm resending this because the formatting got butchered the first type.
Sorry for the duplicate.
Nate Stoddard
=
I'm trying to use the new Maven 3 style of generating reports, but I'm
having problems with one in particular. I have some custom Checkstyle
checks, but I'm not able to add the dependency in the right spot to make
everything work. Here's part of my POM:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version3.0-beta-3/version
dependencies
dependency
groupId[deleted]/groupId
artifactIdcheckstyle/artifactId
version${project.version}/version
/dependency
/dependencies
configuration
reportPlugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
version2.8/version
configuration
configLocation[deleted]/checkstyle.xml/configLocation
/configuration
/plugin
/reportPlugins
/configuration
/plugin
/plugins
/build
In previous versions of Maven, I could add dependencies to the actual
report plugin, but not anymore. Adding the dependency to the
maven-site-plugin doesn't work since it's added to the wrong level of
the classloader. In this case two classloaders are created: 1)
maven-site-plugin, which is the parent classloader of 2)
maven-checkstyle-plugin. The Checkstyle JAR is added to (2), so by
adding my dependency to the the maven-site-plugin (1) things won't work
because it can't reference the Checkstyle types in (2). Adding the
Checkstyle JAR as an additional dependency doesn't work either since the
types from different classloaders are incompatible. There's no way of
adding the dependency such that it ends up in (2). I've tried
configuring the plugin under the pluginManagement section also, but that
seems to be ignored for the newest style.
I'm just wondering if this is even possible, or if I need to roll back
my reporting configurations to the older style until the newer one is
fixed up and functioning better.
Nate Stoddard
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [M2] wagon-scm Unsupported protocol
If anyone is using the wagon-scm plugin, can you help me by posting the sections of your pom.xml that apply to this plugin? Thanks for the help, -Nate Here are the extensions I'm using for in my build: extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-scm/artifactId version1.0-beta-1-SNAPSHOT/version /extension /extensions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] wagon-scm Unsupported protocol
Hello, I'm getting the following error when I try to run site:deploy Unsupported protocol: 'scm' Here are the extensions I'm using for in my build: extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-scm/artifactId version1.0-beta-1-SNAPSHOT/version /extension /extensions I saw a post talking about http://jira.codehaus.org/browse/MNG-2227. I followed the workaround of MNG-2227 and changed the order of my repositories, but I was still unable to get past this error message. Is there something else I must include in the extensions list to get this working? Here is my latest repositories list: repositories repository idmavenSnapshots/id nameMaven Snapshots Repository/name urlhttp://people.apache.org/maven-snapshot-repository/url snapshots enabledtrue/enabled /snapshots releases / /repository repository idmavenCentral/id nameMaven Main Repository/name urlhttp://www.ibiblio.org/maven2/url snapshots/ releases / /repository repository idcodehausSnapshots/id nameCodehaus Snapshot Repository/name urlhttp://snapshots.maven.codehaus.org/maven2/url snapshots/ releases / /repository /repositories Thanks for the help, -Nate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] wagon-scm Unsupported protocol
I realize I should be beat for not running with X before posting to the users list, but better late then never. After running with debugging enabled, I found the wagon-scm snapshot version used by maven was 1.0-beta-1-20060509.172247-7. However, maven cannot find a wagon-providers-api POM with that version. I looked in the repository manually and didnt find that version of the POM. Does this matter? What does using stub model mean? Can snapshot versions be build separately and still work? Here is a snippet from the debug trace: ... [DEBUG] apache: resolved to version 2-20060311.221834-2 from repository mavenSnapshots [DEBUG] org.apache.maven.wagon:wagon-scm:jar:1.0-beta-1-SNAPSHOT:runtime (selected for runtime) [DEBUG] Trying repository mavenSnapshots Downloading: http://people.apache.org/maven-snapshot-repository/org/apache/maven/wagon/wagon-provider-api/1.0-beta-1-SNAPSHOT/wagon-provider-api-1.0-beta-1-20060509.172247-7.pom [WARNING] Unable to get resource from repository mavenSnapshots (http://people.apache.org/maven-snapshot-repository) [DEBUG] Trying repository mavenCentral Downloading: http://www.ibiblio.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-beta-1-SNAPSHOT/wagon-provider-api-1.0-beta-1-20060509.172247-7.pom [WARNING] Unable to get resource from repository mavenCentral (http://www.ibiblio.org/maven2) [DEBUG] Trying repository codehausSnapshots Downloading: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-beta-1-SNAPSHOT/wagon-provider-api-1.0-beta-1-20060509.172247-7.pom [WARNING] Unable to get resource from repository codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) [DEBUG] Skipping disabled repository central [DEBUG] Artifact not found - using stub model: Unable to download the artifact from any repository org.apache.maven.wagon:wagon-provider-api:pom:1.0-beta-1-20060509.172247-7 from the specified remote repositories: mavenSnapshots (http://people.apache.org/maven-snapshot-repository), central (http://repo1.maven.org/maven2), codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), mavenCentral (http://www.ibiblio.org/maven2) [DEBUG] Using defaults for missing POM org.apache.maven.wagon:wagon-provider-api:pom:1.0-beta-1-SNAPSHOT:runtime [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-1-20060509.172247-7:runtime (selected for runtime) [DEBUG] Skipping disabled repository central [DEBUG] maven-scm-api: resolved to version 1.0-20061031.134419-8 from repository mavenSnapshots [DEBUG] Retrieving parent-POM: org.apache.maven.scm:maven-scm::1.0-SNAPSHOT for project: null:maven-scm-api:jar:1.0-20061031.134419-8 from the repository. [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-1-20060509.172247-7:runtime (selected for runtime) [DEBUG] Skipping disabled repository central ... Thanks for the help, -Nate Hello, I'm getting the following error when I try to run site:deploy Unsupported protocol: 'scm' Here are the extensions I'm using for in my build: extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-scm/artifactId version1.0-beta-1-SNAPSHOT/version /extension /extensions I saw a post talking about http://jira.codehaus.org/browse/MNG-2227. I followed the workaround of MNG-2227 and changed the order of my repositories, but I was still unable to get past this error message. Is there something else I must include in the extensions list to get this working? Here is my latest repositories list: repositories repository idmavenSnapshots/id nameMaven Snapshots Repository/name urlhttp://people.apache.org/maven-snapshot-repository/url snapshots enabledtrue/enabled /snapshots releases / /repository repository idmavenCentral/id nameMaven Main Repository/name urlhttp://www.ibiblio.org/maven2/url snapshots/ releases / /repository repository idcodehausSnapshots/id nameCodehaus Snapshot Repository/name urlhttp://snapshots.maven.codehaus.org/maven2/url snapshots/ releases / /repository /repositories Thanks for the help, -Nate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: changelog-maven-plugin and scm error
Other Notes 1) I am not using the standard Maven directory structure. All I am supposed to do with Maven is create a project site for an existing project using mvn site:site. I don't know if this will help, but did you try using the basedir element under the changelog plugin configurations to set the source directory? configuration ... basediryourDir/main/java/basedir /configuration 2) Is there any way to get some more feedback regarding the error? My problem here is that I have NO IDEA where things are going wrong so I don't know where to start fixing. To turn on error stacktraces: mvn site -e To turn on debuging: mvn site -X Hope this helps, -Nate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Changelog Plugin and CVS Tags [SOLVED]
OK, I've tried using the command line cvs client from CVSNT 2.0.51 connecting to a cvs 1.11.20 server. I switched my client a couple of times (couldn't find that exact client version) and finally was successful withCVSNT 2.5.03 Build 2382 Thank you for taking the time to help me solve this problem. -Nate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Changelog plugin report unknown range
When I generate the changelog plugin using the tag type with CVS, I get the following string at the top of the page: Changes from an unknown range. Here is part of my POM: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId version2.0-SNAPSHOT/version reportSets reportSet idsingle-report/id configuration typetag/type tags tag implementation=java.lang.StringMyApp_0_7_rc1/tag tag implementation=java.lang.StringMyApp_0_7_rc2/tag /tags /configuration ... /reportSet /reportSets /plugin If I use the date or range type, that field is filled in correctly with the date range. I looked at the changelog.xml file that is generated for both the tag type and a date type, and the start and end dates attributes were not filled in for the tag output. I believe these start and end attributes are was is being read in by the report generator and used for the range. Generated changelog.xml from tag type: changelog changeset datePattern=MMdd HH:mm:ss z changelog-entry ... Generated changelog.xml from date type: changelog changeset datePattern=MMdd HH:mm:ss z start=20061018 00:00:00 CDT end=20061025 00:00:00 CDT changelog-entry ... I looked into the changelog plugin source, and found that the changeset element and attributes are generated by an SCM plugin object. I tried to go into that source code, but I was unsuccessful in tracking down the exact location where those fields are filled in. Is it possible to get the tag range displayed instead of an unknown date range? Thanks, -Nate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Changelog Plugin and CVS Tags
From your text I understand that you are using Windows as your client OS and the command line CVS client from WinCVS, is that correct? Windows OS (2000) running cygwin WinCVS gui version 2.0.2.4 (Build 4) What CVS server are you using and what OS does it run on? I tried this on two CVS servers. The first one is local on my windows box. CVSNT 2.0.51d The second is a remote server: cvs 1.11.22 Thanks for the help, -Nate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] XSLT Plugin
The site for xslt plugin is old. svn url is http://svn.codehaus.org/mojo/trunk/mojo/xslt-maven-plugin Excellent. apache snapshot repo http://snapshots.repository.codehaus.org/ codehaus snapshot repo Okay. Here is where I'm confused. I used to get the changelog plugin from the codehaus site (2.0-beta1). That version was not working correct, so I found a post that said to switch to the apache repo (2.0-SNAPSHOT). Did this plugin move? If not, why are plugins in both places? Here is the diff of my pom.xml 338,340c348,350 groupIdorg.codehaus.mojo/groupId artifactIdchangelog-maven-plugin/artifactId version2.0-beta-1/version --- groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId version2.0-SNAPSHOT/version Thanks, -Nate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] XSLT Plugin
The changelog plugin is one of those. So when it moved from Codehaus Mojo to Maven, its name changed, and so did the version. The maven-changelog-plugin is the newest version. That makes sense. Thanks for the information. -Nate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Changelog Plugin and CVS Tags
First of all, I'd like to say how impressed I've been with the speed of responses for this list. Thanks for all the help. - Im using the 2.0-SNAPSHOT version of the maven-changelog-plugin, and Im trying to get a report of, All changes after MyApp_0_7_rc1 that went into making MyApp_0_7_rc2. I have the following configuration for the plugin. typetag/type tags tag implementation=java.lang.StringMyApp_0_7_rc1/tag tag implementation=java.lang.StringMyApp_0_7_rc2/tag /tags Here is my file CVS tree of one of my files: UserDatabase.java 1.1 1.2 MyApp_0_7_rc1 1.3 1.4 1.5--- MyApp_0_7_rc2 1.6 When I look at the site generated change log page, I see only comments for v1.3 and v1.4. I would like to see the 1.5 comments because those change went into the MyApp_0_7_rc2 release. I see that -r MyApp_0_7_rc1::MyApp_0_7_rc2 is by the plugin used. I ran a log with WinCVS and the generated log file also only contained versions 1.3 and 1.4. The CVS documentation says the results of a log with the double colon should list all change versions except for the MyApp_0_7_rc1 version. When I modified the WinCVS command to only use one colon, I got versions 1.2, 1.3, 1.4, 1.5; however, I obviously dont want version 1.2 in my final results. Am I doing something wrong here with ChangeLog configuration? Is this a CVS issue? Thanks for the help, -Nate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] XSLT Plugin
Hello, http://mojo.codehaus.org/xslt-maven-plugin/index.html What is the status of the maven2 XSLT Plugin? The source repository links are invalid. Is there a different location of the source code? Also, what is the difference between the following servers? http://people.apache.org/maven-snapshot-repository/ http://snapshots.repository.codehaus.org/ Thanks for the help, -Nate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven XSLT Plugin Question
Andreas, Writing a plugin sounds like an interesting endeavor. I'll try that this weekend. This appears cleaner to me in the long run since it will just be another plugin execution. Marco, Since I need a short-term fix for this week's release, I think I'll use your ant xslt task idea. What execute phase should I set for this to execute every time before the changes plugin is executed during the site generation? Thanks for responding so quickly, -Nate Hello, my 2 cents ant has an xslt task, you could use maven antrun plugin to run it will that be a possible solution? hth marco On 10/11/06, Andreas Guther [EMAIL PROTECTED] wrote: I am not aware of an XSLT plug-in, but writing one should be a pretty straight forward task. I guess I then would try to associate the plug-in with source code generation or something similar during the site creation life cycle. Writing Maven 2 plug-ins is an easy to achieve task and there are plenty of examples available. Andreas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 11, 2006 7:24 AM To: users@maven.apache.org Subject: Maven XSLT Plugin Question I have an application that using XML to define the features added to each release version. I wrote an XSLT to convert this XML into the changes plugin XML format. This allows me to have the same information in the application and the generated site, but the XSLT execution is a manual step. I have a couple of ideas for a solution, but I'm not sure what is available. 1. Does the changes plugin allow a mapping XSL to be included to convert a different XML into a changes plugin? 2. If not, is there plugin to executes XSL transforms during the site cycle? 3. If not, can an ant script be setup to run before the changes plugin? Or is there a pre-site cycle that it can be executed. If you have a different idea, I would be interested in hearing it. Especially if the ant script is the only solution, since it seems hackish to call java with a Saxon jar to transform during the site generation. Thanks for the help, -Nate - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven XSLT Plugin Question
Ah, I figured there must be a pre-site phase. Thank you for including the link to all of the lifecycle phases. -Nate Lifecycle site has this phases [1] : lifecycle idsite/id phases phasepre-site/phase phasesite/phase phasepost-site/phase phasesite-deploy/phase /phases default-phases siteorg.apache.maven.plugins:maven-site-plugin:site/site site-deployorg.apache.maven.plugins:maven-site-plugin:deploy/site-deploy /default-phases /lifecycle You can do what you want if you attached plugins to phase pre-site. -- Olivier [1] https://svn.apache.org/repos/asf/maven/components/trunk/maven-core/src/main/resources/META-INF/plexus/components.xml -Message d'origine- De : Nate [mailto:[EMAIL PROTECTED] Envoyé : mercredi 11 octobre 2006 18:11 À : Maven Users List Objet : Re: Maven XSLT Plugin Question Andreas, Writing a plugin sounds like an interesting endeavor. I'll try that this weekend. This appears cleaner to me in the long run since it will just be another plugin execution. Marco, Since I need a short-term fix for this week's release, I think I'll use your ant xslt task idea. What execute phase should I set for this to execute every time before the changes plugin is executed during the site generation? Thanks for responding so quickly, -Nate Hello, my 2 cents ant has an xslt task, you could use maven antrun plugin to run it will that be a possible solution? hth marco On 10/11/06, Andreas Guther [EMAIL PROTECTED] wrote: I am not aware of an XSLT plug-in, but writing one should be a pretty straight forward task. I guess I then would try to associate the plug-in with source code generation or something similar during the site creation life cycle. Writing Maven 2 plug-ins is an easy to achieve task and there are plenty of examples available. Andreas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 11, 2006 7:24 AM To: users@maven.apache.org Subject: Maven XSLT Plugin Question I have an application that using XML to define the features added to each release version. I wrote an XSLT to convert this XML into the changes plugin XML format. This allows me to have the same information in the application and the generated site, but the XSLT execution is a manual step. I have a couple of ideas for a solution, but I'm not sure what is available. 1. Does the changes plugin allow a mapping XSL to be included to convert a different XML into a changes plugin? 2. If not, is there plugin to executes XSL transforms during the site cycle? 3. If not, can an ant script be setup to run before the changes plugin? Or is there a pre-site cycle that it can be executed. If you have a different idea, I would be interested in hearing it. Especially if the ant script is the only solution, since it seems hackish to call java with a Saxon jar to transform during the site generation. Thanks for the help, -Nate - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
