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

Guy Marom updated MNG-5826:
---------------------------
    Description: 
I have a project with the dependency

{quote}
<dependency>
  <groupId>org.glassfish.web</groupId>
  <artifactId>javax.servlet.jsp</artifactId>
  <version>2.3.2</version>
</dependency>
{quote}

Which in turn has the following dependency:
{quote}
<dependency>
  <groupId>org.glassfish</groupId>
  <artifactId>javax.el</artifactId>
  <version>[3.0.0,)</version>
</dependency>
{quote}

When building this project maven also downloads snapshot versions of this 
artifact from 
"https://maven.java.net/content/repositories/snapshots/org/glassfish/javax.el/maven-metadata.xml";

However, if in my pom I add an exclusion for javax.el under javax.servlet.jsp, 
and then add that exact same dependency it does not attempt to download the 
snapshot version

----

*To reproduce:*
1) Create a maven project containing only the attached pom.xml.
2) Compile the attached pom as is, see that it downloads the snapshot version

3) Unignore the exclusion and the dependency
4) Delete <local-repo>/org/glassfish/javax.el (with sub directories) 
5) Re-compile to see it does not download the snapshot version

  was:
I have a project with the dependency
<dependency>
  <groupId>org.glassfish.web</groupId>
  <artifactId>javax.servlet.jsp</artifactId>
  <version>2.3.2</version>
</dependency>
Which in turn has the following dependency:
<dependency>
  <groupId>org.glassfish</groupId>
  <artifactId>javax.el</artifactId>
  <version>[3.0.0,)</version>
</dependency>

When building this project maven also downloads snapshot versions of this 
artifact from 
"https://maven.java.net/content/repositories/snapshots/org/glassfish/javax.el/maven-metadata.xml";

However, if in my pom I add an exclusion for javax.el under javax.servlet.jsp, 
and then add that exact same dependency it does not attempt to download the 
snapshot version

I created a maven project containing only the attached pom.xml.
To reproduce:
1) Compile the attached pom as is, see that it downloads the snapshot version
2) Unignore the exclusion and the dependency, delete 
<local-repo>/org/glassfish/javax.el (with sub directories) and re-compile to 
see it does not download the snapshot version


> Resolving of a transitive dependency with a range of versions includes 
> snapshot version
> ---------------------------------------------------------------------------------------
>
>                 Key: MNG-5826
>                 URL: https://issues.apache.org/jira/browse/MNG-5826
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies
>    Affects Versions: 3.0.5, 3.3.1, 3.3.3
>            Reporter: Guy Marom
>         Attachments: debug-log.txt, pom.xml
>
>
> I have a project with the dependency
> {quote}
> <dependency>
>   <groupId>org.glassfish.web</groupId>
>   <artifactId>javax.servlet.jsp</artifactId>
>   <version>2.3.2</version>
> </dependency>
> {quote}
> Which in turn has the following dependency:
> {quote}
> <dependency>
>   <groupId>org.glassfish</groupId>
>   <artifactId>javax.el</artifactId>
>   <version>[3.0.0,)</version>
> </dependency>
> {quote}
> When building this project maven also downloads snapshot versions of this 
> artifact from 
> "https://maven.java.net/content/repositories/snapshots/org/glassfish/javax.el/maven-metadata.xml";
> However, if in my pom I add an exclusion for javax.el under 
> javax.servlet.jsp, and then add that exact same dependency it does not 
> attempt to download the snapshot version
> ----
> *To reproduce:*
> 1) Create a maven project containing only the attached pom.xml.
> 2) Compile the attached pom as is, see that it downloads the snapshot version
> 3) Unignore the exclusion and the dependency
> 4) Delete <local-repo>/org/glassfish/javax.el (with sub directories) 
> 5) Re-compile to see it does not download the snapshot version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to