You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Thornton (JIRA)" <ji...@apache.org> on 2019/02/05 17:22:00 UTC

[jira] [Updated] (MNG-6585) Unable to load snapshot extensions from extensions.xml

     [ https://issues.apache.org/jira/browse/MNG-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Thornton updated MNG-6585:
---------------------------------
    Description: 
I'm developing an extension in a continuous build environment and Maven doesn't even attempt to download the extension if the entry in .mvn/extensions.xml has a -SNAPSHOT version. It simply fails with the message that it could not find the extension without explaining why it didn't try to download it. This means that in order for me to try out the extension, I have either have to build it locally or make a release first. I've been unable to find any documentation that identifies this as an intentional limitation, which leads me to believe it must be a bug.

For example, my extension allows the pom.xml to be written in a Kotlin DSL. Because my pom is named pom.kts instead of pom.xml, my build will fail if it cannot download the extension as defined below:
{code:java}
<?xml version="1.0" encoding="UTF-8"?>
<extensions>
  <extension>
    <groupId>io.takari.polyglot</groupId>
    <artifactId>polyglot-kotlin</artifactId>
    <version>0.3.3-SNAPSHOT</version>
  </extension>
</extensions> 
{code}
However, if I change the version to a non-snapshot, Maven does attempt to download the extension:
{code:java}
<?xml version="1.0" encoding="UTF-8"?>
<extensions>
  <extension>
    <groupId>io.takari.polyglot</groupId>
    <artifactId>polyglot-kotlin</artifactId>
    <version>0.3.3.beta01</version>
  </extension>
</extensions> {code}
It seems to me that Maven should attempt to resolve the extension regardless of whether it is a snapshot or now.

  was:
I'm developing an extension in a continuous build environment and Maven doesn't even attempt to download the extension if the entry in .mvn/extensions.xml has a -SNAPSHOT version. It simply fails with the message that it could not find the extension without explaining why it didn't try to download it. This means that in order for other builds to try out the extension, I have to make a release first. I've been unable to find any documentation that identifies this as an intentional limitation, which leads me to believe it must be a bug.

For example, my extension allows the pom.xml to be written in a Kotlin DSL. Because my pom is named pom.kts instead of pom.xml, my build will fail if it cannot download the extension as defined below:
{code:java}
<?xml version="1.0" encoding="UTF-8"?>
<extensions>
  <extension>
    <groupId>io.takari.polyglot</groupId>
    <artifactId>polyglot-kotlin</artifactId>
    <version>0.3.3-SNAPSHOT</version>
  </extension>
</extensions> 
{code}
However, if I change the version to a non-snapshot, Maven does attempt to download the extension:
{code:java}
<?xml version="1.0" encoding="UTF-8"?>
<extensions>
  <extension>
    <groupId>io.takari.polyglot</groupId>
    <artifactId>polyglot-kotlin</artifactId>
    <version>0.3.3.beta01</version>
  </extension>
</extensions> {code}
It seems to me that Maven should attempt to resolve the extension regardless of whether it is a snapshot or now.


> Unable to load snapshot extensions from extensions.xml
> ------------------------------------------------------
>
>                 Key: MNG-6585
>                 URL: https://issues.apache.org/jira/browse/MNG-6585
>             Project: Maven
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.3.9, 3.5.4, 3.6.0
>            Reporter: Robert Thornton
>            Priority: Major
>
> I'm developing an extension in a continuous build environment and Maven doesn't even attempt to download the extension if the entry in .mvn/extensions.xml has a -SNAPSHOT version. It simply fails with the message that it could not find the extension without explaining why it didn't try to download it. This means that in order for me to try out the extension, I have either have to build it locally or make a release first. I've been unable to find any documentation that identifies this as an intentional limitation, which leads me to believe it must be a bug.
> For example, my extension allows the pom.xml to be written in a Kotlin DSL. Because my pom is named pom.kts instead of pom.xml, my build will fail if it cannot download the extension as defined below:
> {code:java}
> <?xml version="1.0" encoding="UTF-8"?>
> <extensions>
>   <extension>
>     <groupId>io.takari.polyglot</groupId>
>     <artifactId>polyglot-kotlin</artifactId>
>     <version>0.3.3-SNAPSHOT</version>
>   </extension>
> </extensions> 
> {code}
> However, if I change the version to a non-snapshot, Maven does attempt to download the extension:
> {code:java}
> <?xml version="1.0" encoding="UTF-8"?>
> <extensions>
>   <extension>
>     <groupId>io.takari.polyglot</groupId>
>     <artifactId>polyglot-kotlin</artifactId>
>     <version>0.3.3.beta01</version>
>   </extension>
> </extensions> {code}
> It seems to me that Maven should attempt to resolve the extension regardless of whether it is a snapshot or now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)