You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shale.apache.org by Matthias Wessendorf <ma...@apache.org> on 2006/10/09 20:42:13 UTC

[repo] Snapshot vs. release (or "vaild" repo in pom file)

Since shale-master-1 depends on apache-apache-2.pom (both are
released) but has snapshot repo for the distr. management, the build
tries to get the apache-apache-2 only from the snapshot repo.

In my corp. environment, when don't use snapshots.
Howto enforce the build to download apache-apache-2 from a *valid* repo ?=
(valid means non-snap)

I opened a bug in the past on that, that we should remove the snapshot
distr. reop from the master-1.pom file.

Thanks!

-- 
Matthias Wessendorf
http://tinyurl.com/fmywh

further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

Re: [repo] Snapshot vs. release (or "vaild" repo in pom file)

Posted by Wendy Smoak <ws...@gmail.com>.
On 10/16/06, Matthias Wessendorf <ma...@apache.org> wrote:

> looks like we missed to update the pom...
>
> do all agree that the *snap repo* used is a bad thing?
>
> Btw. I didn't get any feedback on maven list regarding the "build
> behaivor" I was describing before...

Lets go ahead and change <releases><enabled>true</enabled></releases>
to "false" in the shale-parent pom, so Maven will stop searching the
snapshot repository for non-snapshot versions.

The other change we can make is <distributionManagement>/<repository> to
     people.apache.org/builds/shale/m2-staging-repository

See this pom for an example:
http://svn.apache.org/repos/asf/myfaces/maven/trunk/master-pom/pom.xml

This will let us stage releases in a separate, temporary repository.

Questions and comments welcome, I just haven't had time to write up
how it worked for MyFaces 1.1.4.  (And then it's going to change
anyway, based on discussion on dev@maven.)

Thanks,
-- 
Wendy

Re: [repo] Snapshot vs. release (or "vaild" repo in pom file)

Posted by Matthias Wessendorf <ma...@apache.org>.
Wendy,

looks like we missed to update the pom...

do all agree that the *snap repo* used is a bad thing?

Btw. I didn't get any feedback on maven list regarding the "build
behaivor" I was describing before...

-Matt


> > Having the snapshot repo in <distributionManagement><repository> isn't
> > ideal.  I like the MyFaces build better, which stages releases under
> > people.apache.org/builds, but I don't want to change the Shale build
> > without writing up a release procedure, and I haven't even managed to
> > do that for MyFaces yet.
>
> We can do that on Friday... :-)
>
> >
> > --
> > Wendy
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>


-- 
Matthias Wessendorf
http://tinyurl.com/fmywh

further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

Re: [repo] Snapshot vs. release (or "vaild" repo in pom file)

Posted by Matthias Wessendorf <ma...@apache.org>.
> The 'apache' pom org.apache:apache:2 does not exist in the snapshot
> repository, so you couldn't be downloading it from one.  I don't know

yep

> why Maven won't look in the central repo for the pom... are you behind
> a proxy?

yep, proxy

>
> Having the snapshot repo in <distributionManagement><repository> isn't
> ideal.  I like the MyFaces build better, which stages releases under
> people.apache.org/builds, but I don't want to change the Shale build
> without writing up a release procedure, and I haven't even managed to
> do that for MyFaces yet.

We can do that on Friday... :-)

>
> --
> Wendy
>


-- 
Matthias Wessendorf
http://tinyurl.com/fmywh

further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

Re: [repo] Snapshot vs. release (or "vaild" repo in pom file)

Posted by Wendy Smoak <ws...@gmail.com>.
On 10/9/06, Matthias Wessendorf <ma...@apache.org> wrote:

> Since shale-master-1 depends on apache-apache-2.pom (both are
> released) but has snapshot repo for the distr. management, the build
> tries to get the apache-apache-2 only from the snapshot repo.
>
> In my corp. environment, when don't use snapshots.
> Howto enforce the build to download apache-apache-2 from a *valid* repo ?=
> (valid means non-snap)

The 'apache' pom org.apache:apache:2 does not exist in the snapshot
repository, so you couldn't be downloading it from one.  I don't know
why Maven won't look in the central repo for the pom... are you behind
a proxy?

Having the snapshot repo in <distributionManagement><repository> isn't
ideal.  I like the MyFaces build better, which stages releases under
people.apache.org/builds, but I don't want to change the Shale build
without writing up a release procedure, and I haven't even managed to
do that for MyFaces yet.

-- 
Wendy