My $.02 (that's "my 2 cents worth" for the non-Americans, which a euphemism
for "my unsolicited and free opinion which is worth what you paid for it" :)
)
Having set up a couple of fairly complex proximity instance, I can tell you
that until recently I had very little luck publishing via dav directly into
proximity. I know Tamas is working on that issue, but it does sort of tie
you more into Proximity if the proximity app is the actual DAV provider.
My solution was to have all my repositories be filesystem DAV repositories
setup within Apache and then have Proximity consider them all to be remote
repositories and therefore reads from them into its own cache. I know it's
circumventing some of the things that Proximity does for you, but it's
extremely safe and allows you to replace your proxy (or upgrade/change it)
without worrying about what your proxy might be doing to your deployed
artifacts.
Of course, this means that you're storing up to 2x the number of artifacts
(one in your deployed dav repo and possibly one cached in the proximity
repo), but it also means that your proximity repo is easily replaced in the
event of some catastrophe. Thus you only have to back up the filesystem
that hosts your DAV repos. I know this is almost semantic, but it's been
very useful to me. In my case, the dav repos are actually on another box
entirely that gets backed up frequently while my proximity instance gets
backed up only when it changes (very infrequently) and the proximity cache
never gets backed up at all.
Actually, I'm trying to make a drawing of this entire thing for my current
employer. If I can get it done I'll post it somewhere.
On 4/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
in my settings.xml there's only this :
<mirrors>
<mirror>
<id>proximity</id>
<name>ilem.ma (local) Proximity instance</name>
http://localhost:8080/px-webapp-default-1.0.0-RC8/repository
<mirrorOf>*</mirrorOf>
</mirror>
</mirrors>
every thing else is set to default ==nothing (^_^)
Nice week-end everybody ;-)
Nawfel
www.ilem.ma
----- Message d'origine ----
De : Wayne Fay <[EMAIL PROTECTED]>
À : Maven Users List <[email protected]>
Envoyé le : Vendredi, 20 Avril 2007, 18h09mn 38s
Objet : Re: Re : Re : Proximity
"access denied to" seems like you need to check your file system
permissions on those directories. I'd guess that the user running
Proximity does not have the right privileges to write to those
directories. Not sure, but that's my guess.
Wayne
On 4/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I've tried this : (but I think I'm so far of the right way :-( !)
>
> >mvn deploy:deploy-file -Dfile=./lib/asm-1.5.3.jar-DrepositoryId=proximity \
> -Durl=
http://localhost:8080/px-webapp-default-1.0.0-RC8/px-webapp/dav/public \
> -DartifactId=asm -DgroupId=asm -Dversion=1.5.3 -Dpackaging=jar
-e
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'deploy'.
> [INFO]
-------------------------------------------------------------------------
> ---
> [INFO] Building Unnamed - com:TutelecOJV-v1.3:jar:1.3
> [INFO] task-segment: [deploy:deploy-file] (aggregator-style)
> [INFO]
-------------------------------------------------------------------------
> ---
> [INFO] [deploy:deploy-file]
> Uploading:
http://localhost:8080/px-webapp-default-1.0.0-RC8/px-webapp/dav/publi
> c/asm/asm/1.5.3/asm-1.5.3.jar
> 25K uploaded
> [INFO]
------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
------------------------------------------------------------------------
> [INFO] Error deploying artifact: Authorization failed: Access denied to:
http://
> localhost:8080/px-webapp-default-1.0.0-RC8
/px-webapp/dav/public/asm/asm/1.5.3/as
> m-1.5.3.jar
>
> [INFO]
------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifact
> : Authorization failed: Access denied to:
http://localhost:8080/px-webapp-defaul
> t-1.0.0-RC8/px-webapp/dav/public/asm/asm/1.5.3/asm-1.5.3.jar
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:564)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> Goal(DefaultLifecycleExecutor.java:493)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:463)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:311)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLi
> fecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
> java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(
Launcher.java:430)
>
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error
deploying artif
> act: Authorization failed: Access denied to:
http://localhost:8080/px-webapp-def
> ault-1.0.0-RC8/px-webapp/dav/public/asm/asm/1.5.3/asm-1.5.3.jar
> at org.apache.maven.plugin.deploy.DeployFileMojo.execute
(DeployFileMojo.
> java:243)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPlugi
> nManager.java:420)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:539)
> ... 16 more
> Caused by:
org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error
> deploying artifact: Authorization failed: Access denied to:
http://localhost:80
> 80/px-webapp-default-1.0.0-RC8/px-webapp/dav/public/asm/asm/1.5.3/asm-
1.5.3.jar
> at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Def
> aultArtifactDeployer.java:94)
> at org.apache.maven.plugin.deploy.DeployFileMojo.execute
(DeployFileMojo.
> java:239)
> ... 18 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Authorization
failed:
> Access denied to:
http://localhost:8080/px-webapp-default-1.0.0-RC8/px-webapp/d
> av/public/asm/asm/1.5.3/asm-1.5.3.jar
> at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(D
> efaultWagonManager.java:257)
> at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(Def
> aultWagonManager.java:151)
> at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Def
> aultArtifactDeployer.java:80)
> ... 19 more
> Caused by: org.apache.maven.wagon.authorization.AuthorizationException:
Access d
> enied to:
http://localhost:8080/px-webapp-default-1.0.0-RC8/px-webapp/dav/public
> /asm/asm/1.5.3/asm-1.5.3.jar
> at org.apache.maven.wagon.providers.http.LightweightHttpWagon.put
(Lightw
> eightHttpWagon.java:165)
> at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(D
> efaultWagonManager.java:222)
> ... 21 more
> [INFO]
------------------------------------------------------------------------
> [INFO] Total time: 1 second
> [INFO] Finished at: Fri Apr 20 17:28:13 GMT 2007
> [INFO] Final Memory: 2M/5M
> [INFO]
------------------------------------------------------------------------
>
>
> ----- Message d'origine ----
> De : Tamás Cservenák <[EMAIL PROTECTED]>
> À : Maven Users List <[email protected]>
> Envoyé le : Vendredi, 20 Avril 2007, 16h02mn 48s
> Objet : Re: Re : Proximity
>
> Hi,
>
> Proximity is not able to "receive" artifacts on URL
> http://localhost:8080/px-webapp-default-1.0.0-RC8/repository (that
> evaluates in this case to
> http://localhost:8080/px-webapp-default-1.0.0-RC8/repository/asm/asm/).
> This servlet is the "repository" servlet that is RO only and offers
> "view" to users and M2 itself.
>
> I will try to explain using DEMO site:
>
> Currently, with RC8 the only deployment way is via DAV or using some
"bypass".
>
> DAV:
> http://proximity.abstracthorizon.org:12000/px-webapp/dav/public
>
> You have to address the group, where you want to deploy. This might be
> bad, if you have multiple resposes in same group, but it works with
> "factory" configuration.
>
> "Bypass":
> Publish onto underlying FS, by publishing it over FTP or SFTP....
>
>
> Hope helps,
> ~t~
>
> On 4/20/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
> > Perhaps check your web/app server/Proximity log files and see why its
> > returning error 500. This is a pretty generic error message. You might
> > not be able to diagnose this from Maven's side.
> >
> > Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
>
>
>
>
>
___________________________________________________________________________
> Découvrez une nouvelle façon d'obtenir des réponses à toutes vos
questions !
> Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses
> http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
!
Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com
--
I'm just an unfrozen caveman software developer. I don't understand your
strange, "modern" ways.
