RE: Proxy connectors fails to download, Archiva needs restart

2008-04-22 Thread Jackson, Brian R 
Brett,
Sorry it took so long to respond.  I tried this finally but it broke my
Archiva instance and it just returned 404 errors.  So I had to rollback
to using the wagon-http-lightweight.

Brian

-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org] On Behalf Of Brett Porter
Sent: Friday, April 04, 2008 7:50 PM
To: [EMAIL PROTECTED]
Subject: Re: Proxy connectors fails to download, Archiva needs restart

Sorry about that Brian. I've reopened MRM-631 to track it. I've added
a couple of suggestions - I think the most likely to succeed is to
remove
apps/archiva/webapp/WEB-INF/lib/wagon-http-lightweight-1.0-beta-2.jar
and replace it with wagon-http-1.0-beta-2.jar which you can get from
the central repository.

Cheers,
Brett

On 05/04/2008, Jackson, Brian R [EMAIL PROTECTED] wrote:
 No luck.  Now I'm getting the following exception in my wrapper.log.
I
  sniffed the traffic and its still trying to connect through our HTTP
  proxy even though I configured it to connect directly.



  INFO   | jvm 1| 2008/04/04 15:34:02 | WARNING:

/archiva/repository/releases/com/go/trove/trove/1.7.1/trove-1.7.1.jar:
  INFO   | jvm 1| 2008/04/04 15:34:02 |
  org.apache.maven.archiva.policies.ProxyDownloadException: Failures
  occurred downloading from some remote repositories:
  INFO   | jvm 1| 2008/04/04 15:34:02 |   wdig.releases:
Download
  failure on resource

[http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/tro
  ve/trove/1.7.1/trove-1.7.1.pom]:Error transferring file
  INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFro

 mProxies(DefaultRepositoryProxyConnectors.java:197)
  INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSide

 Relocation(ProxiedDavServer.java:438)
  INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFro

 mProxies(ProxiedDavServer.java:353)
  INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.apache.maven.archiva.web.repository.ProxiedDavServer.process(Proxied

 DavServer.java:188)
  INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.
  service(MultiplexedWebDavServlet.java:119)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.apache.maven.archiva.web.repository.RepositoryServlet.service(Reposi
  toryServlet.java:155)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at

 javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at

 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
  ApplicationHandler.java:830)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at


com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDisp
  atcher.java:189)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
  ApplicationHandler.java:821)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at


com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.j
  ava:39)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
  ApplicationHandler.java:821)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at


com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(Action
  ContextCleanUp.java:88)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
  ApplicationHandler.java:821)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationH
  andler.java:471)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at

 org.mortbay.http.HttpContext.handle(HttpContext.java:1530)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at


org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationCon
  text.java:633)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at

 org.mortbay.http.HttpContext.handle(HttpContext.java:1482)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at

 org.mortbay.http.HttpServer.service(HttpServer.java:909)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at

 org.mortbay.http.HttpConnection.service(HttpConnection.java:816)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at

 org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)

 INFO   | jvm 1| 2008/04/04 15:34:02 |   at

 org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)

 INFO   | jvm 1| 2008/04

RE: Proxy connectors fails to download, Archiva needs restart

2008-04-03 Thread Jackson, Brian R 
It does just that.  The problem I'm having is with artifacts that
haven't been cached yet.

-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org] On Behalf Of Jason Chaffee
Sent: Thursday, April 03, 2008 2:44 PM
To: archiva-users@maven.apache.org
Subject: RE: Proxy connectors fails to download, Archiva needs restart

Also, if the artifact is in the local cache and this failure happens,
shouldn't is simply log it and then return the cached artifact? 

-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 03, 2008 6:29 AM
To: archiva-users@maven.apache.org
Subject: Re: Proxy connectors fails to download, Archiva needs restart

ok, it looks like maybe they've blocked you in some way.

Archiva 1.0.2 should improve on the reporting of this, and allows the
error handling to be configurable.

- Brett

On 04/04/2008, Jackson, Brian R [EMAIL PROTECTED] wrote:
 That didn't take long.

  Here's the full stacktrace, which implies that the remote repository
is
  returning a 500 error, but if I hit the same URL through a browser I
  can't reproduce the 500 error.  I will coordinate with the owner of
the
  remote repository and see if I can get more info from the logs on his
  end.

  418722 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -
Path
  [com/go/tea/tea/3.3.11/tea-3.3.11.pom] is part of blacklist (skipping
  transfer from repository [Central Repository]).
  418722 [SocketListener0-1] DEBUG

 org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -

 Applying [cache-failures] policy with [no]
  418722 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures  -
OK
  to fetch, check-failures policy set to NO.
  418722 [SocketListener0-1] DEBUG

 org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -

 Applying [releases] policy with [once]
  418722 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.policies.PreDownloadPolicy:releases  - OK to
  update releases, local file does not exist.
  418722 [SocketListener0-1] DEBUG

 org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -

 Applying [snapshots] policy with [never]
  418722 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.policies.PreDownloadPolicy:snapshots  - OK
to
  update, snapshot policy does not apply for non-snapshot versions.
  418722 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -
No
  authentication for remote repository needed
  418722 [SocketListener0-1] DEBUG

 org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -

 Retrieving com/go/tea/tea/3.3.11/tea-3.3.11.pom from WDIG Releases
  419035 [SocketListener0-1] WARN

 org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -
  Transfer error from repository wdig.releases for artifact

 com.go.tea:tea:3.3.11::pom, continuing to next repository. Error

 message: Download failure on resource


[http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/tea
  /tea/3.3.11/tea-3.3.11.pom]:Error transferring file
  419035 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -
Full
  stack trace
  org.apache.maven.archiva.proxy.ProxyException: Download failure on
  resource

[http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/tea
  /tea/3.3.11/tea-3.3.11.pom]:Error transferring file
 at

org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transfer
  SimpleFile(DefaultRepositoryProxyConnectors.java:717)
 at

org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transfer
  File(DefaultRepositoryProxyConnectors.java:542)
 at

org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFro
  mProxies(DefaultRepositoryProxyConnectors.java:155)
 at

org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSide
  Relocation(ProxiedDavServer.java:447)
 at

org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFro
  mProxies(ProxiedDavServer.java:354)
 at

org.apache.maven.archiva.web.repository.ProxiedDavServer.process(Proxied
  DavServer.java:189)
 at

org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.
  service(MultiplexedWebDavServlet.java:119)
 at

org.apache.maven.archiva.web.repository.RepositoryServlet.service(Reposi
  toryServlet.java:155)
 at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 at

org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
 at

org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
  ApplicationHandler.java:830)
 at

com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDisp
  atcher.java:189)
 at

org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
  ApplicationHandler.java:821

RE: Proxy connectors fails to download, Archiva needs restart

2008-04-03 Thread Jackson, Brian R 
Why would restarting MY instance of Archiva temporarily fix this issue
though?  I'll get more information from the remote side when the owner
is available.

-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org] On Behalf Of Brett Porter
Sent: Thursday, April 03, 2008 9:29 AM
To: [EMAIL PROTECTED]
Subject: Re: Proxy connectors fails to download, Archiva needs restart

ok, it looks like maybe they've blocked you in some way.

Archiva 1.0.2 should improve on the reporting of this, and allows the
error handling to be configurable.

- Brett

On 04/04/2008, Jackson, Brian R [EMAIL PROTECTED] wrote:
 That didn't take long.

  Here's the full stacktrace, which implies that the remote repository
is
  returning a 500 error, but if I hit the same URL through a browser I
  can't reproduce the 500 error.  I will coordinate with the owner of
the
  remote repository and see if I can get more info from the logs on his
  end.

  418722 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -
Path
  [com/go/tea/tea/3.3.11/tea-3.3.11.pom] is part of blacklist (skipping
  transfer from repository [Central Repository]).
  418722 [SocketListener0-1] DEBUG

 org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -

 Applying [cache-failures] policy with [no]
  418722 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures  -
OK
  to fetch, check-failures policy set to NO.
  418722 [SocketListener0-1] DEBUG

 org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -

 Applying [releases] policy with [once]
  418722 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.policies.PreDownloadPolicy:releases  - OK to
  update releases, local file does not exist.
  418722 [SocketListener0-1] DEBUG

 org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -

 Applying [snapshots] policy with [never]
  418722 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.policies.PreDownloadPolicy:snapshots  - OK
to
  update, snapshot policy does not apply for non-snapshot versions.
  418722 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -
No
  authentication for remote repository needed
  418722 [SocketListener0-1] DEBUG

 org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -

 Retrieving com/go/tea/tea/3.3.11/tea-3.3.11.pom from WDIG Releases
  419035 [SocketListener0-1] WARN

 org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -
  Transfer error from repository wdig.releases for artifact

 com.go.tea:tea:3.3.11::pom, continuing to next repository. Error

 message: Download failure on resource


[http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/tea
  /tea/3.3.11/tea-3.3.11.pom]:Error transferring file
  419035 [SocketListener0-1] DEBUG
  org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  -
Full
  stack trace
  org.apache.maven.archiva.proxy.ProxyException: Download failure on
  resource

[http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/tea
  /tea/3.3.11/tea-3.3.11.pom]:Error transferring file
 at

org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transfer
  SimpleFile(DefaultRepositoryProxyConnectors.java:717)
 at

org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transfer
  File(DefaultRepositoryProxyConnectors.java:542)
 at

org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFro
  mProxies(DefaultRepositoryProxyConnectors.java:155)
 at

org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSide
  Relocation(ProxiedDavServer.java:447)
 at

org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFro
  mProxies(ProxiedDavServer.java:354)
 at

org.apache.maven.archiva.web.repository.ProxiedDavServer.process(Proxied
  DavServer.java:189)
 at

org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.
  service(MultiplexedWebDavServlet.java:119)
 at

org.apache.maven.archiva.web.repository.RepositoryServlet.service(Reposi
  toryServlet.java:155)
 at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 at

org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
 at

org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
  ApplicationHandler.java:830)
 at

com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDisp
  atcher.java:189)
 at

org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
  ApplicationHandler.java:821)
 at

com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.j
  ava:39)
 at

org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
  ApplicationHandler.java:821)
 at

com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(Action

RE: Proxy connectors fails to download, Archiva needs restart

2008-04-03 Thread Jackson, Brian R 
I sniffed the traffic and it's attempting to connect through the network
proxy I've setup for some of my other Proxy Connectors.  I've
double-checked that the Proxy Connector for wdig.releases, the remote
repo that is failing, is configured to (direct connection).


-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org] On Behalf Of Jackson, Brian R
Sent: Thursday, April 03, 2008 11:36 AM
To: [EMAIL PROTECTED]
Subject: RE: Proxy connectors fails to download, Archiva needs restart

I spoke with Joe, the owner of the remote repository, and we tested it.
Apparently the request is not getting to the remote repository as the
archiva.log, audit.log and wrapper.log on that server showed no activity
at all while mine reports the exception caused by the 500 error.  I will
now follow up with our MIS and operations team to trace the request as
see where it is being blocked.

-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org] On Behalf Of Brett Porter
Sent: Thursday, April 03, 2008 9:52 AM
To: [EMAIL PROTECTED]
Subject: Re: Proxy connectors fails to download, Archiva needs restart

On 04/04/2008, Jackson, Brian R [EMAIL PROTECTED] wrote:
 Why would restarting MY instance of Archiva temporarily fix this issue
  though?  I'll get more information from the remote side when the
owner
  is available.


Good point - sorry I forgot that.

Let's see what they have to say - though others have also reported
this so perhaps there is something else going on here.

Thanks,
Brett

-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Configuring Archiva to proxy a Proximity instance

2007-12-13 Thread Jackson, Brian R 
All,

I'm having trouble configurating Archiva to proxy an instance of
Proximity because I'm required to set a property on the proxy connector.
Unfortunately Archiva 1.0 bombs when I try to save a proxy connector
with a property:

 


HTTP ERROR: 500

[Ljava.lang.String; cannot be cast to java.lang.String

RequestURI=/archiva/admin/editProxyConnector!commit.action

Powered by Jetty:// http://jetty.mortbay.org 

 

 

___

Brian Jackson

Sr. Software Engineer

ESPN.com Fantasy Games

(860) 766-2511

RE: Configuring Archiva to proxy a Proximity instance

2007-12-13 Thread Jackson, Brian R 
 a bug?

What is the property that is required? Perhaps it can be put into your
configuration file by hand.

- Brett

On 14/12/2007, Jackson, Brian R [EMAIL PROTECTED] wrote:
 All,

 I'm having trouble configurating Archiva to proxy an instance of
 Proximity because I'm required to set a property on the proxy
connector.
 Unfortunately Archiva 1.0 bombs when I try to save a proxy connector
 with a property:




 HTTP ERROR: 500

 [Ljava.lang.String; cannot be cast to java.lang.String

 RequestURI=/archiva/admin/editProxyConnector!commit.action

 Powered by Jetty:// http://jetty.mortbay.org





 ___

 Brian Jackson

 Sr. Software Engineer

 ESPN.com Fantasy Games

 (860) 766-2511






-- 
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/

changelog and perforce

2007-07-17 Thread Jackson, Brian R 
I'm trying to use the changelog with Perforce but after some
investigation it appear that the SCM provider for Perforce in not
creating the necessary client.  The changelog plugin executes this
command:

 

p4 -p perforce:1666 -c
JACKSBRR-LW-CT-JACKSBRR-MavenSCM-C:\Projects\SuperPOMs\espn filelog -t
-l ...

 

It must be failing silently because when I try to execute the same
command I get this error:

 

... - must create client
'JACKSBRR-LW-CT-JACKSBRR-MavenSCM-C:\Projects\SuperPOMs\espn' to access
local files.

 

 

My changelog config is:

 

plugin

artifactIdmaven-changelog-plugin/artifactId

version2.0-SNAPSHOT/version

reportSets

reportSet

idperforce-report/id

configuration

typerange/type

range10/range

properties

 
maven.changelog.factoryorg.apache.maven.perforcelib.PerforceChangeLogF
actory/maven.changelog.factory

/properties

dateFormat/MM/dd HH:mm:ss/dateFormat

basedir${basedir}/basedir

/configuration

reports

reportchangelog/report

reportfile-activity/report

reportdev-activity/report

/reports

/reportSet

/reportSets

/plugin

changelog and perforce

2007-07-16 Thread Jackson, Brian R 
I'm trying to use the changelog with Perforce but after some
investigation it appear that the SCM provider for Perforce in not
creating the necessary client.  The changelog plugin executes this
command:

 

p4 -p perforce:1666 -c
JACKSBRR-LW-CT-JACKSBRR-MavenSCM-C:\Projects\SuperPOMs\espn filelog -t
-l ...

 

It must be failing silently because when I try to execute the same
command I get this error:

 

... - must create client
'JACKSBRR-LW-CT-JACKSBRR-MavenSCM-C:\Projects\SuperPOMs\espn' to access
local files.

 

 

My changelog config is:

 

plugin

artifactIdmaven-changelog-plugin/artifactId

version2.0-SNAPSHOT/version

reportSets

reportSet

idperforce-report/id

configuration

typerange/type

range10/range

properties

 
maven.changelog.factoryorg.apache.maven.perforcelib.PerforceChangeLogF
actory/maven.changelog.factory

/properties

dateFormat/MM/dd HH:mm:ss/dateFormat

basedir${basedir}/basedir

/configuration

reports

reportchangelog/report

reportfile-activity/report

reportdev-activity/report

/reports

/reportSet

/reportSets

/plugin

Compilation issues

2007-07-16 Thread Jackson, Brian R 
Anyone know why mvn compile runs with no goals needed for project -
skipping but mvn compiler:compile runs just fine for my project?

 

Thanks,

Brian

Telling Maven to not append project hierarchy to parent's scm

2007-07-09 Thread Jackson, Brian R 
So I've configured my scm in a company super POM as such:

 

scm

 
connectionscm:perforce:${perforce.host}:${perforce.port}:${perforce.pa
th}/connection

 
developerConnectionscm:perforce:${perforce.host}:${perforce.port}:${pe
rforce.path}

/developerConnection

 
urlhttp://${perforce.host}:${perforce.web.port}/@md=damp;cd=//amp;cd
f=${perforce.path}amp;[EMAIL PROTECTED]/url

/scm

 

 

I want child projects to only define the property 'perforce.path'.

 

This would work the way I want but Maven appends project.name to
'project.scm.connection'.  Any ideas for how I can tell maven or the scm
plugin to use the connection url as-is since perforce.path will be
overridden by each project?

 

Thanks,

Brian

RE: Perforce login

2007-06-25 Thread Jackson, Brian R 
The problem was that I was missing a colon after the port number in the
connection URL.

 

Thank you for the response though.

 

Brian

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Yuri Schimke
Sent: Monday, June 25, 2007 2:06 AM
To: [EMAIL PROTECTED]
Subject: Re: Perforce login

 

Hey,

I don't think this is documented well enough, but apart from the release
process which uses a temporary client spec, you really need everything
to be working from the command line already.  This means having a local
checkout and a clientspec that uses the correct root for that checkout. 

It may very well be an issue with login, but its worth checking this as
well.

I was getting similar errors with my projects until I made sure that
from the command line e.g. DOS prompt, you can run 

p4 sync ...

The easiest way to ensure this works is to setup a p4.config file

http://www.perforce.com/perforce/doc.042/manuals/cmdref/env.P4CONFIG.htm
l 

On 6/21/07, Jackson, Brian R [EMAIL PROTECTED] wrote:

I'm attempting to run mvn scm:update on my project but I get the
following output:

 


-

C:\Projects\SuperPOMs\espnmvn scm:update

[INFO] Scanning for projects...

[INFO] Searching repository for plugin with prefix: 'scm'.

[INFO]

-

---

[INFO] Building The ESPN Super POM

[INFO]task-segment: [scm:update] (aggregator-style)

[INFO]

-

---

[INFO] [scm:update]

[INFO] Checkout working directory: C:\Projects\SuperPOMs\espn

[INFO] Executing: p4 -d C:\Projects\SuperPOMs\espn -p
sw-ct-perfor01c.dev.espn3.

com client -i

[ERROR] Provider message:

[ERROR] Unable to sync.  Are you logged in?

[ERROR] Command output:

[ERROR]

[INFO]


[ERROR] BUILD ERROR

[INFO]


[INFO] Command failed.Unable to sync.  Are you logged in?

[INFO]


[INFO] For more information, run Maven with the -e switch

[INFO]


[INFO] Total time: 3 seconds

[INFO] Finished at: Thu Jun 21 18:12:19 EDT 2007

[INFO] Final Memory: 5M/12M

[INFO]


 

C:\Projects\SuperPOMs\espn


-

 

 

Any idea what I'm doing wrong.  I've configured my username in my
pom.xml as such:

build

plugins

plugin

artifactIdmaven-idea-plugin/artifactId

configuration

downloadSourcestrue/downloadSources

downloadJavadocstrue/downloadJavadocs

/configuration

/plugin

plugin

!-- All ESPN projects must deploy a JAR containing the
source files

 to the repository.  This allows other developers to
use browse

 the source files while developing

 --

artifactIdmaven-source-plugin/artifactId

/plugin

plugin

artifactIdmaven-scm-plugin/artifactId

configuration

username${scm.username}/username

password${scm.password}/password

/configuration

/plugin

/plugins

/build

 

And setup my scm info as such:

scm

 
connectionscm:perforce:${perforce.host}:${perforce.port}//vss_espneng/
Projects/SuperPOMs/espn/connection

 
developerConnectionscm:perforce:${perforce.host}:${perforce.port}//vss
_espneng/Projects/SuperPOMs/espn

/developerConnection

urlhttp://longurl... http://longurl%E2%80%A6 /url

/scm

 

The properties referenced are configured in my settings.xml:

 

 

profiles

profile

activation

activeByDefault/

/activation

idespn3.profile.dev/id

repositories

repository

releases

updatePolicynever/updatePolicy

/releases

idespn3/id

url
http://example.corp.espn3.com/px/repository/espn3
http://example.corp.espn3.com/px/repository/espn3 /url

/repository

repository

idespn3.snapshot/id

releases

enabledfalse/enabled

/releases

snapshots

enabledtrue/enabled

Perforce login

2007-06-21 Thread Jackson, Brian R 
I'm attempting to run mvn scm:update on my project but I get the
following output:

 


-

C:\Projects\SuperPOMs\espnmvn scm:update

[INFO] Scanning for projects...

[INFO] Searching repository for plugin with prefix: 'scm'.

[INFO]

-

---

[INFO] Building The ESPN Super POM

[INFO]task-segment: [scm:update] (aggregator-style)

[INFO]

-

---

[INFO] [scm:update]

[INFO] Checkout working directory: C:\Projects\SuperPOMs\espn

[INFO] Executing: p4 -d C:\Projects\SuperPOMs\espn -p
sw-ct-perfor01c.dev.espn3.

com client -i

[ERROR] Provider message:

[ERROR] Unable to sync.  Are you logged in?

[ERROR] Command output:

[ERROR]

[INFO]


[ERROR] BUILD ERROR

[INFO]


[INFO] Command failed.Unable to sync.  Are you logged in?

[INFO]


[INFO] For more information, run Maven with the -e switch

[INFO]


[INFO] Total time: 3 seconds

[INFO] Finished at: Thu Jun 21 18:12:19 EDT 2007

[INFO] Final Memory: 5M/12M

[INFO]


 

C:\Projects\SuperPOMs\espn


-

 

 

Any idea what I'm doing wrong.  I've configured my username in my
pom.xml as such:

build

plugins

plugin

artifactIdmaven-idea-plugin/artifactId

configuration

downloadSourcestrue/downloadSources

downloadJavadocstrue/downloadJavadocs

/configuration

/plugin

plugin

!-- All ESPN projects must deploy a JAR containing the
source files

 to the repository.  This allows other developers to
use browse

 the source files while developing

 --

artifactIdmaven-source-plugin/artifactId

/plugin

plugin

artifactIdmaven-scm-plugin/artifactId

configuration

username${scm.username}/username

password${scm.password}/password

/configuration

/plugin

/plugins

/build

 

And setup my scm info as such:

scm

 
connectionscm:perforce:${perforce.host}:${perforce.port}//vss_espneng/
Projects/SuperPOMs/espn/connection

 
developerConnectionscm:perforce:${perforce.host}:${perforce.port}//vss
_espneng/Projects/SuperPOMs/espn

/developerConnection

urlhttp://longurl.../url

/scm

 

The properties referenced are configured in my settings.xml:

 

 

profiles

profile

activation

activeByDefault/

/activation

idespn3.profile.dev/id

repositories

repository

releases

updatePolicynever/updatePolicy

/releases

idespn3/id

 
urlhttp://example.corp.espn3.com/px/repository/espn3/url

/repository

repository

idespn3.snapshot/id

releases

enabledfalse/enabled

/releases

snapshots

enabledtrue/enabled

updatePolicyinterval:30/updatePolicy

/snapshots

urlhttp://
example.corp.espn3.com/px/repository/espn3.snapshot/url

/repository

/repositories

properties

scm.usernameMYUSERNAME/scm.username

scm.password123456/scm.password

perforce.hostexample.dev.espn3.com/perforce.host

perforce.port1234/perforce.port

/properties

/profile

/profiles