Filewatcher File Search File Search
Catalog
Content Search
» » » » doxia_1.1.4.orig.tar.gz » Content »
pkg://doxia_1.1.4.orig.tar.gz:751993/doxia-1.1.4/doxia-test-docs/src/main/resources/maven-changes-plugin/fml/  info  downloads

faq.fml

<?xml version="1.0" encoding="UTF-8"?>

<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<faqs id="FAQ" title="Frequently Asked Questions">
 <part id="General">
   <faq id="question1">
     <question>What's the difference between the changes-maven-plugin at Mojo and this one?</question>
     <answer>
       <p>
         This plugin started out at <a href="http://mojo.codehaus.org/">the Mojo project</a>.
         In March of 2006 the plugin was moved to Apache and the Maven sandbox.
         So it's the same plugin, but this one is newer.
       </p>
     </answer>
   </faq>

   <faq id="question2">
     <question>I get a <code>org.xml.sax.SAXParseException</code>, when generating the JIRA Report. What can do about it?</question>
     <answer>
       <p>
         If you have a lot of entities in the xml file returned from your JIRA
         installation, you might get an error like this one, when you run the
         JIRA Report:

         <source>
org.xml.sax.SAXParseException: Parser has reached the entity expansion limit "64,000" set by the Application.
         </source>

         If that happens you need to tell the xml parser to use a higher limit.
         This can be accomplished by adding a command line parameter. In the
         following example we have set it to double the original value:

         <source>
mvn -DentityExpansionLimit=128000 ...
         </source>
       </p>
       <p>
         Unfortunately we have not been able to set this in Java. If someone
         knows how to do this, then please reopen
         <a href="http://jira.codehaus.org/browse/MCHANGES-75">MCHANGES-75</a>,
         and tell us how. It would be nicer if this could be set using a
         parameter in the POM.
       </p>
     </answer>
   </faq>
 </part>
</faqs>
Results 1 - 1 of 1
Help - FTP Sites List - Software Dir.
Search over 15 billion files
© 1997-2017 FileWatcher.com