patience :)

They are all there now. If you get a 404, it's because ibiblio has a
cache that takes a while to expire, and Maven 1.0.2 isn't sending a
no-cache header. Manually download anything missing...

The file has also been updated in svn.

HTH,
Brett

On 4/21/05, Mykel Alvis <[EMAIL PROTECTED]> wrote:
> Thanks, Brett
>  I noticed that there's an http-lightweight but the dep is on http.
>  Is that another correction for the project.xml or is it a different dep?
> 
> 
> On 4/20/05, Brett Porter <[EMAIL PROTECTED] > wrote:
> > 
> > ok, the groupID should be org.apache.maven.wagon, not maven. I've
> > fixed it, will commit when the machine is working again. 
> > 
> > I'm copying the missing dependencies now, so if you make the above
> > change and try again in 5 minutes, it should work.
> > 
> > - Brett
> > 
> > On 4/21/05, Mykel Alvis <[EMAIL PROTECTED] > wrote:
> > > SNAPSHOTS they are.
> > >
> > >  Updating the project.xml to include SNAPSHOT for all the wagon deps
> gives
> > > me FNFs on only the following.
> > >  They are not in the maven repo.
> > > 
> > >  wagon-provider-api-1.0-alpha-3-SNAPSHOT.jar  <- there
> IS
> > > an alpha-2-SNAPSHOT
> > >  wagon-ssh-external-1.0-alpha-2-SNAPSHOT.jar  <- No
> such
> > > creature
> > >
> > >  This may not be correct.  Maybe everything doesn't need a -SNAPSHOT 
> > > appended to its version.
> > >  from modified project.xml
> > >  ----------------------------------------
> > >     <dependency>
> > >        <groupId>maven</groupId>
> > >        <artifactId>wagon-provider-api</artifactId> 
> > >        <version>1.0-alpha-3-SNAPSHOT</version>
> > >      </dependency>
> > >      <dependency>
> > >        <groupId>maven</groupId>
> > >        <artifactId>wagon-http</artifactId> 
> > >        <version>1.0-alpha-2-SNAPSHOT</version>
> > >      </dependency>
> > >      <dependency>
> > >        <groupId>maven</groupId>
> > >        <artifactId>wagon-ftp</artifactId> 
> > >        <version>1.0-alpha-2-SNAPSHOT</version>
> > >      </dependency>
> > >      <dependency>
> > >        <groupId>maven</groupId>
> > >        <artifactId>wagon-ssh</artifactId> 
> > >        <version>1.0-alpha-2-SNAPSHOT</version>
> > >      </dependency>
> > >      <dependency>
> > >        <groupId>maven</groupId>
> > >        <artifactId>wagon-ssh-external</artifactId> 
> > >        <version>1.0-alpha-2-SNAPSHOT</version>
> > >      </dependency>
> > >      <dependency>
> > >        <groupId>maven</groupId>
> > >        <artifactId>wagon-file</artifactId> 
> > >        <version>1.0-alpha-2-SNAPSHOT</version>
> > >      </dependency>
> > >    </dependencies>
> > >
> > >
> > > On 4/20/05, Mykel Alvis < [EMAIL PROTECTED]> wrote:
> > > > Yep.  They're there...as SNAPSHOTS (doh!)  When I surf to
> > > > http://www.ibiblio.org/maven/maven/jars/
> > > > I see a file called
> wagon-file-1.0-alpha-2-SNAPSHOT.jar
> > > > But the file from the project, per project.xml and from output of
> maven -X
> > > is wagon-file-1.0-alpha-2.jar
> > > >
> > > > -- snip --
> > > > Received status code: 404 
> > > > File not found on one of the repos
> > > > java.io.FileNotFoundException:
> > >
> http://www.ibiblio.org/maven/maven/jars/wagon-file-1.0-alpha-2.jar
> > > > -- snip --
> > > >
> > > > Do I need to change the version to xxx-SNAPSHOT?
> > > >
> > > >
> > > >
> > > > On 4/20/05, Brett Porter < [EMAIL PROTECTED] > wrote:
> > > > > On 4/21/05, Mykel Alvis <[EMAIL PROTECTED]> wrote:
> > > > > > My question is how to get maven1 to download those dependencies as
> > > part of
> > > > > > attaining the plugin:install goal.
> > > > >
> > > > > I don't understand why the main ones aren't working... they are in
> the
> > > > > right place.
> > > > > 
> > > > > For the others, you might need to put them in place until I can move
> > > > > them across.
> > > > >
> > > > > > Do I need to surf to the spot, download the jars manually, and 
> > > manually
> > > > > > place them in my repository? That seems a little "counter-maven".
> > > > > > More specifically, should I have installed the plugin plugin first
> so
> > > that 
> > > > > > it would recognize the maven2 repository structure? Would that
> help?
> > > > >
> > > > > No, m1 can't read the m2 repo yet.
> > > > >
> > > > > - Brett
> > > > > > 
> > > > > > On 4/20/05, Brett Porter <[EMAIL PROTECTED] > wrote:
> > > > > > >
> > > > > > >
> > >
> http://www.ibiblio.org/maven/org.apache.maven.wagon/jars/
> > > > > > >
> > > > > > > Most of them seem to be there... I'll look into the others, but
> you
> > > > > > > can get them from: 
> > > > > > >
> > > > > > >
> > > http://www.ibiblio.org/maven2/org/apache/maven/wagon/
> > > > > > >
> > > > > > > Either jsch should be fine... I'll probably update the SVN
> version 
> > > later
> > > > > > > on.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Brett
> > > > > > >
> > > > > > > On 4/21/05, Mykel Alvis < [EMAIL PROTECTED]> wrote:
> > > > > > > > Also, apparently there's a dependency on jsch-0.1.14 in the
> plugin
> > > > > > > > Earlier you mentioned to change to 0.1.17 of jsch. I was
> wondering
> > > if
> > > > > > > that
> > > > > > > > was still necessary/a good idea?
> > > > > > > >
> > > > > > > > On 4/20/05, Mykel Alvis < [EMAIL PROTECTED] > wrote:
> > > > > > > > >
> > > > > > > > > Brett,
> > > > > > > > > I've gotten a distro from svn and tried the plugin:install. 
> > > > > > > > > The following dependencies are apparently not available to
> me.
> > > > > > > > > Wrong repo or something else?
> > > > > > > > >
> > > > > > > > > wagon-provider-api-1.0-alpha-3-SNAPSHOT.jar
> > > > > > > > > wagon-http-1.0-alpha-2.jar
> > > > > > > > > wagon-ftp-1.0-alpha-2.jar
> > > > > > > > > wagon-ssh-1.0-alpha-2.jar 
> > > > > > > > > wagon-ssh-external-1.0-alpha-2.jar
> > > > > > > > > wagon-file-1.0-alpha-2.jar
> > > > > > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > 
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to