Hi Treloar,

first, thanks for you answer :o)

I am a bit confused about what you said. The page says :
      However the repositoryDefinitions profile section can be made
      simpler by using a proxy infront of the internal repositories.

What I understand from this (and which sounds obvious to me) is: if you're
using maven-proxy, you don't have to put those profile definitions in your
settings.xml any longer. Why ? Because the <mirror> element replaces them
all because maven-proxy handles everything from the URL
"http://NUCLEUS:9999/repository/"; (which is the actual purpose of a proxy).
So for what I've understood, you don't need to activate any extra
repository definition profile when you're using maven-proxy.
Am I wrong?
Maybe "central" is a repository for which snapshots are not activated by
default, and therefore when setting the mirror of "central" to maven-proxy,
it does not handle them?

As for the SNAPSHOT unique version, I put it to "false" because I don't
want to have my snapshot repository getting bigger and bigger too fast. I
know Maven knows well how to handle snapshots when unique version is
activated, but I just want to save space.

Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91  -  [EMAIL PROTECTED]


                                                                       
             "Treloar, Barrie                                          
             (SAPOL)"                                                  
             <barrie.treloar@                                         Pour
             police.sa.gov.au          'Maven Users List'              
             >                         <users@maven.apache.org>        
                                                                        cc
             08/02/2006 23:38                                          
                                                                     Objet
                                       RE: maven-proxy and snapshots   
                 Veuillez              problem                         
                répondre à                                         
             Maven Users List                                          
             <[EMAIL PROTECTED]                                          
                 che.org>                                              
                                                                       
                                                                       




> Hi everybody,
>
> I'm using maven-proxy as described in the doco "Using Maven in a
corporate
> environment"
> (
http://docs.codehaus.org/display/MAVENUSER/Using+Maven+in+a+corporate+env
> ironment),
>  and everything works well except for snapshots.
>
> I have snaphots of some of my components deployed in the inner snapshot
> repository (they are *not* deployed with a unique name, though, but only
> "SNAPSHOT"). When I build a projet that references those snapshots, I get
> the following error (with -e) :
>
>
==========================================================================
> =======
> [INFO]
>
--------------------------------------------------------------------------
> --
> [ERROR] BUILD ERROR
> [INFO]
>
--------------------------------------------------------------------------
> --
> [INFO] Failed to resolve artifact.
>
> required artifacts missing:
>   com.inetpsa.fwk:fwk-sql:jar:2.1.0-SNAPSHOT
>   com.inetpsa.fwk:fwk-vrn:jar:2.1.0-SNAPSHOT
>   com.inetpsa.fwk:fwk-noyau:jar:2.1.0-SNAPSHOT
>
> for the artifact:
>   com.inetpsa.xxx:xxxMetier:jar:1.0.0-SNAPSHOT
>
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)

Well remember the caveat at
http://docs.codehaus.org/display/MAVENUSER/Mini+Guides

NOTE: This page contains drafts of user contributed miniguides entries
which
are intended to supplement the official Maven documentation. The content
you
see here might not be fully fool-proof or might not comply with the best
practices promoted by Maven. What is only guaranteed is that they have
worked once for some members. It is best to treat these items as "works in
progress" until they have been reviewed and promoted to the main Maven
documentation site.

That page, since I put it together, is a work in progress and may not be
100% correct.


That being said, from the error message you have above
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
it looks like it is not checking your repositories for the snapshots.

The section "Defining repositories in settings.xml" says just above the
extract of settings.xml:
    The profile "repositoryDefinitions" is made active, but
    "inhouseSnapshot" is de-active by default.
    If you want your project to be built against snapshot versions
    then activate the profile on the mvn command line via
    "-PinhouseSnapshot".

Are you running maven like:
    mvn -PinhouseSnapshot
???

Also double check your pom.xml file.  The default value for
distributionManagement -> snapshotRepository -> uniqueVersion is true.
This will get you the snapshot unique version.

See
snapshotRepositoryhttp://blogs.codehaus.org/people/brett/archives/maven.html

#001045_improved_snapshots_in_maven2 for more details on snapshots.

But briefly, maven handles the -SNAPSHOT to unique timestamp version lookup
for you.  You don't have to worry about the fact that in the internal
snapshot repository that they have different suffixes.

---------------------------------------------------------------------
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