Uploaded image for project: 'JBoss Modules'
  1. JBoss Modules
  2. MODULES-283

proxies parsing in MavenSettings missing final 'break';

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 1.6.0.Beta8
    • None
    • Maven
    • None

      My settings.xml is based on an old template so contains: -

        <!-- proxies
         | This is a list of proxies which can be used on this machine to connect to the network.
         | Unless otherwise specified (by system property or command-line switch), the first proxy
         | specification in this list marked as active will be used.
         |-->
        <proxies>
          <!-- proxy
           | Specification for one proxy, to be used in connecting to the network.
           |
          <proxy>
            <id>optional</id>
            <active>true</active>
            <protocol>http</protocol>
            <username>proxyuser</username>
            <password>proxypass</password>
            <host>proxy.host.net</host>
            <port>80</port>
            <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
          </proxy>
          -->
        </proxies>
      
      

      Although lots of comments the <proxies> element are uncommented.

      This results in the followind exception: -

      org.jboss.modules.xml.XmlPullParserException: expected START_TAG or END_TAG not TEXT (position: TEXT seen ...<server>\n <id>jboss-snapshots-repository</... @114:39)
      at org.jboss.modules.xml.MXParser.nextTag(MXParser.java:1081)
      at org.jboss.modules.maven.MavenSettings.parseSettings(MavenSettings.java:180)
      at org.jboss.modules.maven.MavenSettings.parseSettingsXml(MavenSettings.java:130)
      at org.jboss.modules.maven.MavenSettings.lambda$getSettings$0(MavenSettings.java:106)

              darran.lofthouse@redhat.com Darran Lofthouse
              darran.lofthouse@redhat.com Darran Lofthouse
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: