As I was surprised by the use case you're describing, I just downloaded a
fresh maven 2.2.1 with default configuration.
Then I created a dumb project with archetype:generate/#15.
Finally, I added the jms dependency:
<dependency>
<groupId>javax.jms</groupId>
<artifactId>jms</artifactId>
<version>1.1</version>
</dependency>
I don't receive the same error. Maven just says it can't download jms jar
(quite ok, since it's actually not here:
http://repo1.maven.org/maven2/javax/jms/jms/1.1/).
Could you please upload your sample project and your settings.xml somewhere
so that someone can try and reproduce your problem?
If you're sure there's a problem with the 301/30x maven handling, I guess
you could also file the corresponding issue, attaching your sample project.
I you do that, please give us here the link to the new issue you file.
Cheers.
2010/2/13 KARR, DAVID (ATTSI) <dk0...@att.com>
> > -----Original Message-----
> > From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of
> > Baptiste MATHUS
> > Sent: Saturday, February 13, 2010 1:02 PM
> > To: Maven Users List
> > Subject: Re: Error opening zip file (because it isn't there)
> >
> > Hi David,
> >
> > JMS jar is a special case, and maven not being able to download isn't
> a
> > bug.
> > You'll have to download and install it manually due to license
> > restrictions.
>
> If anything, I'd say that the fact that Maven attempts to download the
> jar, but doesn't notice that it's not actually a jar file, might be
> considered inconvenient, if not a bug.
>
> When setting up a new Maven installation, there appear to be a handful
> of these that have to be treated the same way. The build fails, delete
> the false jar file, rerun the build, get the nice url to download it
> from, along with the command line to install it, download it, install
> it, and rerun the build. I had to do that about 3-4 times. If Maven
> had detected that what it downloaded wasn't a jar file, I would have
> saved a step or two there.
>
> It may not seem like much, but every step that makes it easier for old
> Anters to move to Maven is a good thing. There is a common notion that
> "Maven is too complicated", and simple obstacles like this are not
> simple for people who haven't used Maven before. It appears that every
> single person who starts using Maven will run into these exact same
> issues.
>
> > Note that when you'll have found the jar, the command to install it
> > locally
> > is provided in the log you just gave.
> >
> > Cheers.
> >
> > 2010/2/13 KARR, DAVID (ATTSI) <dk0...@att.com>
> >
> > > > -----Original Message-----
> > > > From: KARR, DAVID (ATTSI)
> > > > Sent: Saturday, February 13, 2010 11:47 AM
> > > > To: users@maven.apache.org
> > > > Subject: Error opening zip file (because it isn't there)
> > > >
> > > > I haven't used Maven in a while, so I'm sure I'm making several
> > > obvious
> > > > mistakes.
> > > >
> > > > I installed the latest m2eclipse in Eclipse 3.5.1 and created a
> > simple
> > > > Spring project, just to build a simple test case for a problem I'm
> > > > seeing in Spring. I've deleted lots of plugin and dependency
> > > > information to try to whittle it down to just what I need, just to
> > > > produce a simple WAR file with Spring, a context file, and a
> simple
> > > > class.
> > > >
> > > > At some point, I'm now down to the following error:
> > > >
> > > > [INFO] Compilation failure
> > > > error: error reading ...\.m2\repository\javax\jms\jms\1.1\jms-
> > 1.1.jar;
> > > > error in opening zip file
> > > >
> > > > When I searched for this, I found some people have already hit
> > this:
> > > > <http://groups.google.com/group/sakai-
> > > > kernel/browse_thread/thread/52a3e4
> > > > fe52b84d99?fwc=1>
> > > >
> > > > At this point, I just need to get past this, so the war will
> build.
> > > > I'm
> > > > not using JMS.
> > >
> > > Just so it's clear, my subject line was inaccurate. The file is
> > there,
> > > but it's in the wrong format. It's not a jar file, but HTML output
> > from
> > > a 301 error ("Moved Permanently").
> > >
> > > I would have thought that Maven would handle 301s, but in this case
> > it
> > > doesn't matter, as the URL the 301 gives for the permanent location
> > of
> > > the file doesn't exist either, and that gets a 404.
> > >
> > > At this point, I thought I would try just deleting the "1.1"
> > directory.
> > > That obviously isn't clever enough for Maven, as it just tries to
> > > download again, although it fails in a different way this time:
> > >
> > > -------------------------------------
> > > [INFO] Copying 1 resource
> > > Downloading:
> > > http://static.appfuse.org/repository/javax/jms/jms/1.1/jms-1.1.pom
> > > [INFO] Unable to find resource 'javax.jms:jms:pom:1.1' in repository
> > > appfuse (http://static.appfuse.org/repository)
> > > Downloading:
> > > https://maven-
> > repository.dev.java.net/nonav/repository/javax.jms/poms/jm
> > > s-1.1.pom
> > > [WARNING] Unable to get resource 'javax.jms:jms:pom:1.1' from
> > repository
> > > java.net (https://maven-repository.dev.java.net/nonav/repository):
> > Error
> > > transferring file: Connection timed out: connect
> > > Downloading: http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-
> > 1.1.pom
> > >
> > > Downloading:
> > > http://static.appfuse.org/repository/javax/jms/jms/1.1/jms-1.1.jar
> > > [INFO] Unable to find resource 'javax.jms:jms:jar:1.1' in repository
> > > appfuse (http://static.appfuse.org/repository)
> > > Downloading:
> > > https://maven-
> > repository.dev.java.net/nonav/repository/javax.jms/jars/jm
> > > s-1.1.jar
> > > [WARNING] Unable to get resource 'javax.jms:jms:jar:1.1' from
> > repository
> > > java.net (https://maven-repository.dev.java.net/nonav/repository):
> > Error
> > > transferring file: Connection timed out: connect
> > > Downloading: http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-
> > 1.1.jar
> > > [INFO] Unable to find resource 'javax.jms:jms:jar:1.1' in repository
> > > central (http://repo1.maven.org/maven2)
> > > [INFO]
> > >
> ---------------------------------------------------------------------
> > ---
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
> ---------------------------------------------------------------------
> > ---
> > > [INFO] Failed to resolve artifact.
> > >
> > > Missing:
> > > ----------
> > > 1) javax.jms:jms:jar:1.1
> > >
> > > Try downloading the file manually from:
> > > http://java.sun.com/products/jms/docs.html
> > >
> > > Then, install it using the command:
> > > mvn install:install-file -DgroupId=javax.jms -DartifactId=jms
> > > -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
> > >
> > > Alternatively, if you host your own repository you can deploy the
> > file
> > > there:
> > > mvn deploy:deploy-file -DgroupId=javax.jms -DartifactId=jms
> > > -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> > > -DrepositoryId=[id]
> > >
> > > Path to dependency:
> > > 1) springjmxbug:springjmxbug:war:0.0.1-SNAPSHOT
> > > 2) log4j:log4j:jar:1.2.15
> > > 3) javax.jms:jms:jar:1.1
> > >
> > > ----------
> > > 1 required artifact is missing.
> > >
> > > for artifact:
> > > springjmxbug:springjmxbug:war:0.0.1-SNAPSHOT
> > >
> > > from the specified remote repositories:
> > > central (http://repo1.maven.org/maven2),
> > > appfuse (http://static.appfuse.org/repository)
> > > ----------------------------------------------------
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: users-h...@maven.apache.org
> > >
> > >
> >
> >
> > --
> > Baptiste <Batmat> MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor !
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
