geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Kashyap" <goyathlay.geron...@gmail.com>
Subject Re: Migrating to maven 2
Date Mon, 27 Feb 2006 14:44:21 GMT
Anita,

Do you have the following in your POM ?

<repositories>
    <repository>
      <snapshots>
        <enabled>true</enabled>
      </snapshots>
      <id>Apache CVS</id>
      <name>Apache CVS of the Central Repository</name>
      <url>http://cvs.apache.org/maven-snapshot-repository</url>
    </repository>
  </repositories>

That jar exists there
http://cvs.apache.org/maven-snapshot-repository/org/apache/geronimo/specs/geronimo-javamail_1.3.1_spec/1.1-SNAPSHOT/

Cheers
Prasad

On 2/27/06, anita kulshreshtha <a_kulshre@yahoo.com> wrote:
> inline .....
>
> --- "Alan D. Cabrera" <list@toolazydogs.com> wrote:
>
> > On 2/20/2006 3:20 AM, Gianny Damour wrote:
> >
> > > Alan D. Cabrera wrote:
> > >
> > >> Does the entire system need to build using a
> > single command for this
> > >> interim conversion?  Why not have people do a
> > >>
> > >> mvn install
> > >> maven new
> > >>
> > >> The "mvn install" will build both maven 1 and 2
> > jars.  The "maven
> > >> new" will use the maven 1 jars.
> > >
> > >
> > > That also works. This approach assmes that the M2
> > modules that we
> > > migrate do not depend on modules which have not
> > yet been migrated to
> > > M2 - basically, this implies that modules are
> > migrated in the same
> > > order than the build order derived by the M1
> > reactor.
> > >
> > > I think that I like this approach better than my
> > previous idea, where
> > > any module could be migrated - whatever its
> > dependencies. However, I
> > > am not really keen to have people use two commands
> > and would prefer to
> > > simply use the maven command which triggers the
> > mvn command under the
> > > cover.
> > >
> > > I think that this has already been suggested by
> > David J.: we add a
> > > goal, e.g. new000, which is executed between new00
> > and new1. new000
> > > launches mvn install in the root project
> > directory. We add to the
> > > excludes list of new1 the migrated modules (we
> > could also remove the
> > > M1 project files after migration).
> >
> >
> > If I see yet *another* new fangled way to build
> > Geronimo, I'll go
> > postal.  Let's go w/ the two command system whereby
> > we do things the
> > sane way in maven 2, i.e. "mvn install".  Let us
> > leave our sordid past
> > behind and begin anew.
> >
> > Seriously, this futzing has got to stop.
>
>      I am trying to build with mvn install! I get the
> following error?
> [INFO]
> ---------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ---------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> required artifacts missing:
>
> org.apache.geronimo.specs:geronimo-javamail_1.3.1_spec:jar:1.1-SNAPSHOT
>    I am wondering if 'mvn install' still works?
> >
> >
> > Regards,
> > Alan
> >
> >
> >
> >
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>

Mime
View raw message