And you don't have those issues that Jamie reported?
-Lukas
Dion Gillard wrote:
In my limited experience, using Archiva (1.0-alpha1 on windows) with M1 is
painful and time consuming, and it seems geared to work with m2, as well as
being still in the early stages of development and hence functionally
flaky.
We're still using maven-proxy for those reasons.
On 6/27/07, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
I don't know. I didn't use maven-proxy for a long time.
Actually I'm using Archiva.
You some others choices like Proximity or Artifactory.
Arnaud
On 26/06/07, Jamie Bisotti <[EMAIL PROTECTED]> wrote:
> On 6/26/07, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> >
> > I checked that I get these dependencies downloaded from
> > http://repo1.maven.org/maven/, which is the default repo in m11 now.
> >
> > -Lukas
> >
> >
> > Jamie Bisotti wrote:
> > > We've been using 1.0.2 for a long time. Currently, I'm looking to
move
> > us
> > > to 1.1 (baby steps). After replacing my 1.0.2 installation with
1.1,
I
> > > cannot successfully build our project any longer. I'm getting the
> > > following:
> > >
> > > ...
> > >
> > >>> The build cannot continue because of the following unsatisfied
> > >
> > > dependencies:
> > > - org.codehaus.plexus:plexus-component-api:1.0-alpha-15:jar
> > > - org.codehaus.plexus:plexus-container-default:1.0-alpha-15:jar
> > > - org.codehaus.plexus:plexus-classworlds:1.2-alpha-5:jar
> > > - org.codehaus.plexus:plexus-utils:1.0.5:jar
> > > - org.apache.maven.scm:maven-scm-manager-plexus:1.0-beta-2:jar
> > > - org.apache.maven.scm:maven-scm-api:1.0-beta-2:jar
> > > - org.apache.maven.scm:maven-scm-provider-cvs:1.0-beta-2:jar
> > > - org.apache.maven.scm:maven-scm-provider-svn:1.0-beta-2:jar
> > > - org.apache.maven.scm:maven-scm-provider-starteam:1.0-beta-2:jar
> > >
> > > I'm sure I'm missing a repo somewhere, but I cannot seem to find
> > it. Any
> > > help would be greatly appreciated. Thanks
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> Thanks for the tip. Turns out it's actually a Maven-Proxy issue. I
added
> the repo1 repository to maven-proxy.properties, but Maven-Proxy doesn't
seem
> to acknowledge it. Anyone have any ideas on this new tangent? Thanks.
>
> --
> Jamie Bisotti
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - [EMAIL PROTECTED]
www.octo.com | blog.octo.com
..........................................................
ASF - [EMAIL PROTECTED]
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
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]
