If I understand correctly, if we'd have released james-project already
separately, the build would have succeeded?

But not if I am offline, of course, which leads me to the general note
that I am very much in favor of self-contained releases.  Right?

My personal opinion is that a release which starts pulling stuff from
the internet to even build (putting hibernate et al. to the side when
it comes to running a system) is in fact only half a release.
<rant> We could start distributing svn checkout commands, this would
dramatically reduce the size of the distributions.</rant>

  Bernd

On 9/24/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
> Bernd Fondermann ha scritto:
> > Downloaded apache-jspf-0.9.5-src.tar.gz from the staging directory,
> > unpacked it and ran
> >   mvn -P local package
> > like suggested in BUILDING.txt. But it gives me an error:
> >
> >>>>>
> > [INFO] Failed to resolve artifact.
> >
> > GroupId: org.apache.james
> > ArtifactId: james-project
> > Version: 1.2
> >
> > Reason: Unable to download the artifact from any repository
> >
> >   org.apache.james:james-project:pom:1.2
> >
> > from the specified remote repositories:
> >   central (http://repo1.maven.org/maven2),
> >   local-jspf-stage-repository (file://${basedir}/stage)
> > <<<<
> >
> > So I am -0 on releasing this in its current state.
> >
> >   Bernd
>
> There is a bug in maven about resolving the parent from the local stage
> repository.
> When this vote will pass and the artifacts will be deployed then that
> file will be in the official repository and will be found.
> Otherwise, as described in the pom.xml, you have to manually install the
> parent pom before building:
>
> ----
> <id>local-jspf-stage-repository</id>
> <name>Local jSPF stage repository</name>
> <!-- Please note that due to http://jira.codehaus.org/browse/MNG-2896 -->
> <!-- If you don't have james-project checked out in ../james-project -->
> <!-- you will have to place your absolute path to the project instead -->
> <!-- of ${basedir}, or, otherwise, manually install the parent poms -->
> <!--
>    #windows:
>    mvn -fignorepom.xml install:install-file
>       -Dfile=stage\org.apache.james\poms\james-parent-1.1.pom
>       -Dpackaging=pom
>       -DgroupId=org.apache.james
>       -DartifactId=james-parent
>       -Dversion=1.1
>    mvn -fignorepom.xml install:install-file
>       -Dfile=stage\org.apache.james\poms\james-project-1.2.pom
>       -Dpackaging=pom
>       -DgroupId=org.apache.james
>       -DartifactId=james-project
>       -Dversion=1.2
>
>    #linux:
>    mvn -fignorepom.xml install:install-file
>       -Dfile=stage/org.apache.james/poms/james-parent-1.1.pom
>       -Dpackaging=pom
>       -DgroupId=org.apache.james
>       -DartifactId=james-parent
>       -Dversion=1.1
>    mvn -fignorepom.xml install:install-file
>       -Dfile=stage/org.apache.james/poms/james-project-1.2.pom
>       -Dpackaging=pom
>       -DgroupId=org.apache.james
>       -DartifactId=james-project
>       -Dversion=1.2
> -->
> <url>file://${basedir}/stage</url>
> <layout>legacy</layout>
> --------
>
> Stefano
>
>
> ---------------------------------------------------------------------
> 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