Unable to commit files to SVN after new branch has been created with the maven-release plugin

2010-11-22 Thread edgarosy 

Question for all maven gurus. Hope you can help me..

I've been using a maven-release plugin for over a year and it has always
work perfectly when creating new branch from source (trunk). Ever since our
SVN amdin upgraded the SVN server to use version 1.6 instead of 1.4 I have
not been able to commit files to svn successfully after the branch has been
created. 

my build servers is a windows 2003 server. I am using Maven version: 2.2.1,
and I upgraded the svn client to 1.6.1.



[INFO] Executing: cmd.exe /X /C svn --username . --password *
--non-interactive commit --file C:\Documents and
Settings\triacp\maven-scm-528237796.commit --targets C:\Documents and
Settings\triacp\maven-scm-1457486069711445316-targets
[INFO] Working directory: D:\build\buildScripts\mvnScripts\branching
org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to
commit files
Provider message:
The svn command failed.
Command output:
cygwin warning:
  MS-DOS style path detected: C:\Documents and
Settings\triacp\maven-scm-528237796.commit
  Preferred POSIX equivalent is: /cygdrive/c/Documents and
Settings/triacp/maven-scm-528237796.commit
  CYGWIN environment variable option nodosfilewarning turns off this
warning.
  Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
svn:
'/cygdrive/d/build/buildScripts/mvnScripts/branching/D:/build/buildScripts/mvnScripts/branching'
is not a working copy
svn:
'/cygdrive/d/build/buildScripts/mvnScripts/branching/D:/build/buildScripts/mvnScripts/branching'
does not exist

at
org.apache.maven.shared.release.phase.ScmCommitPhase.checkin(ScmCommitPhase.java:133)
at
org.apache.maven.shared.release.phase.ScmCommitPhase.execute(ScmCommitPhase.java:109)
at
org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:379)
at
org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:350)
at
org.apache.maven.plugins.release.BranchReleaseMojo.execute(BranchReleaseMojo.java:133)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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)
[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
cygwin warning:
  MS-DOS style path detected: C:\Documents and
Settings\triacp\maven-scm-528237796.commit
  Preferred POSIX equivalent is: /cygdrive/c/Documents and
Settings/triacp/maven-scm-528237796.commit
  CYGWIN environment variable option nodosfilewarning turns off this
warning.
  Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
svn:
'/cygdrive/d/build/buildScripts/mvnScripts/branching/D:/build/buildScripts/mvnScripts/branching'
is not a working copy
svn:
'/cygdrive/d/build/buildScripts/mvnScripts/branching/D:/build/buildScripts/mvnScripts/branching'
does not exist

[INFO]

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

[INFO] Total time: 11 minutes 49 seconds
[INFO]

Unable to build a maven project ufter updating JMS to 1.1

2009-01-16 Thread edgarosy 

All,

I changed a jms dependency on my Project parent pom to have version 1.1
instead of
1.0.2
I manually uploaded its jar file to Artifactory.

My question is: When I build my app using maven 2 it tries to download the
jms file from http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
instead of my own repo?

I ran a mvn help-effective-settings -Pacp command and all my repo URLs are
correct..

I get this error:



D:\acpwork\cruise\checkout\branch\modules\common-trilogymvn install -Pacp
[INFO] Scanning for projects...
WAGON_VERSION: 1.0-beta-2
[INFO]

[INFO] Building octanner common trilogy module
[INFO]task-segment: [install]
[INFO]

[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: 25845 at timestamp: 1231785672571
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading: http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

Missing:
--
1) javax.jms:jms:jar:1.1

 Try downloading the file manually from:
 http://java.sun.com/products/jms/docs.html

 Then, install it using the command:
 mvn install:install-file -DgroupId=javax.jms -DartifactId=jms
-Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file

 Alternatively, if you host your own repository you can deploy the file
there:
 mvn deploy:deploy-file -DgroupId=javax.jms -DartifactId=jms
-Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

 Path to dependency:
   1) com.octanner:common-trilogy:jar:8.12
   2) com.octanner:i18n:jar:8.12
   3) com.octanner:domainmodel:jar:8.12
   4) com.octanner:common:jar:8.12
   5) javax.jms:jms:jar:1.1

--
1 required artifact is missing.

for artifact:
 com.octanner:common-trilogy:jar:8.12

from the specified remote repositories:
 central (http://repo1.maven.org/maven2)


[INFO]

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

[INFO] Total time: 8 seconds
[INFO] Finished at: Mon Jan 12 11:41:15 MST 2009
[INFO] Final Memory: 11M/21M
[INFO]


D:\acpwork\cruise\checkout\branch\modules\common-trilogy

Any help would be greatly appreciate it.

-- 
View this message in context: 
http://www.nabble.com/Unable-to-build-a-maven-project-ufter-updating-JMS-to-1.1-tp21503052p21503052.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Unable to build a maven project ufter updating JMS to 1.1

2009-01-16 Thread edgarosy 

I forgot to mention that I am unable to build the project from the build
server, but if I run it from any other computer checking out the same
project from svn it would work. 

edgarosy wrote:
 
 All,
 
 I changed a jms dependency on my Project parent pom to have version 1.1
 instead of
 1.0.2
 I manually uploaded its jar file to Artifactory.
 
 My question is: When I build my app using maven 2 it tries to download the
 jms file from http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
 instead of my own repo?
 
 I ran a mvn help-effective-settings -Pacp command and all my repo URLs are
 correct..
 
 I get this error:
 
 
 
 D:\acpwork\cruise\checkout\branch\modules\common-trilogymvn install -Pacp
 [INFO] Scanning for projects...
 WAGON_VERSION: 1.0-beta-2
 [INFO]
 
 [INFO] Building octanner common trilogy module
 [INFO]task-segment: [install]
 [INFO]
 
 [INFO] [buildnumber:create {execution: default}]
 [INFO] Checking for local modifications: skipped.
 [INFO] Updating project files from SCM: skipped.
 [INFO] Storing buildNumber: 25845 at timestamp: 1231785672571
 [INFO] [resources:resources]
 [INFO] Using default encoding to copy filtered resources.
 Downloading: http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
 [INFO]
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] Failed to resolve artifact.
 
 Missing:
 --
 1) javax.jms:jms:jar:1.1
 
  Try downloading the file manually from:
  http://java.sun.com/products/jms/docs.html
 
  Then, install it using the command:
  mvn install:install-file -DgroupId=javax.jms -DartifactId=jms
 -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
 
  Alternatively, if you host your own repository you can deploy the file
 there:
  mvn deploy:deploy-file -DgroupId=javax.jms -DartifactId=jms
 -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
 -DrepositoryId=[id]
 
  Path to dependency:
1) com.octanner:common-trilogy:jar:8.12
2) com.octanner:i18n:jar:8.12
3) com.octanner:domainmodel:jar:8.12
4) com.octanner:common:jar:8.12
5) javax.jms:jms:jar:1.1
 
 --
 1 required artifact is missing.
 
 for artifact:
  com.octanner:common-trilogy:jar:8.12
 
 from the specified remote repositories:
  central (http://repo1.maven.org/maven2)
 
 
 [INFO]
 
 [INFO] For more information, run Maven with the -e switch
 [INFO]
 
 [INFO] Total time: 8 seconds
 [INFO] Finished at: Mon Jan 12 11:41:15 MST 2009
 [INFO] Final Memory: 11M/21M
 [INFO]
 
 
 D:\acpwork\cruise\checkout\branch\modules\common-trilogy
 
 Any help would be greatly appreciate it.
 
 

-- 
View this message in context: 
http://www.nabble.com/Unable-to-build-a-maven-project-ufter-updating-JMS-to-1.1-tp21503052p21503101.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Unable to build a maven project ufter updating JMS to 1.1

2009-01-16 Thread edgarosy 

Thanks

Baptiste MATHUS-4 wrote:
 
 If you wipe out (or just temporarily rename) the local repository, where
 will it download the artifacts from? In fact, isn't it possible you might
 have been using your local repository instead of ever using your maven
 repository manager installation?
 
 I myself regularly completely wipe out my local repository to check my
 builds are not dependent to some local particularity (note I'm in the
 support team, so I want to be the first to encounter such problem. You
 might
 not want to investigate this if it's not your day job...).
 
 My 2 cents.
 Cheers.
 
 2009/1/16 edgarosy edgar.l...@gmail.com
 

 I forgot to mention that I am unable to build the project from the build
 server, but if I run it from any other computer checking out the same
 project from svn it would work.

 edgarosy wrote:
 
  All,
 
  I changed a jms dependency on my Project parent pom to have version 1.1
  instead of
  1.0.2
  I manually uploaded its jar file to Artifactory.
 
  My question is: When I build my app using maven 2 it tries to download
 the
  jms file from
 http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
  instead of my own repo?
 
  I ran a mvn help-effective-settings -Pacp command and all my repo URLs
 are
  correct..
 
  I get this error:
 
 
 
  D:\acpwork\cruise\checkout\branch\modules\common-trilogymvn install
 -Pacp
  [INFO] Scanning for projects...
  WAGON_VERSION: 1.0-beta-2
  [INFO]
 
 
  [INFO] Building octanner common trilogy module
  [INFO]task-segment: [install]
  [INFO]
 
 
  [INFO] [buildnumber:create {execution: default}]
  [INFO] Checking for local modifications: skipped.
  [INFO] Updating project files from SCM: skipped.
  [INFO] Storing buildNumber: 25845 at timestamp: 1231785672571
  [INFO] [resources:resources]
  [INFO] Using default encoding to copy filtered resources.
  Downloading:
 http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
  [INFO]
 
 
  [ERROR] BUILD ERROR
  [INFO]
 
 
  [INFO] Failed to resolve artifact.
 
  Missing:
  --
  1) javax.jms:jms:jar:1.1
 
   Try downloading the file manually from:
   http://java.sun.com/products/jms/docs.html
 
   Then, install it using the command:
   mvn install:install-file -DgroupId=javax.jms -DartifactId=jms
  -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
 
   Alternatively, if you host your own repository you can deploy the file
  there:
   mvn deploy:deploy-file -DgroupId=javax.jms -DartifactId=jms
  -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
  -DrepositoryId=[id]
 
   Path to dependency:
 1) com.octanner:common-trilogy:jar:8.12
 2) com.octanner:i18n:jar:8.12
 3) com.octanner:domainmodel:jar:8.12
 4) com.octanner:common:jar:8.12
 5) javax.jms:jms:jar:1.1
 
  --
  1 required artifact is missing.
 
  for artifact:
   com.octanner:common-trilogy:jar:8.12
 
  from the specified remote repositories:
   central (http://repo1.maven.org/maven2)
 
 
  [INFO]
 
 
  [INFO] For more information, run Maven with the -e switch
  [INFO]
 
 
  [INFO] Total time: 8 seconds
  [INFO] Finished at: Mon Jan 12 11:41:15 MST 2009
  [INFO] Final Memory: 11M/21M
  [INFO]
 
 
 
  D:\acpwork\cruise\checkout\branch\modules\common-trilogy
 
  Any help would be greatly appreciate it.
 
 

 --
 View this message in context:
 http://www.nabble.com/Unable-to-build-a-maven-project-ufter-updating-JMS-to-1.1-tp21503052p21503101.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


 
 
 -- 
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !
 
 

-- 
View this message in context: 
http://www.nabble.com/Unable-to-build-a-maven-project-ufter-updating-JMS-to-1.1-tp21503052p21503684.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Unable to successfully complete a mvn install on one of my apps

2008-12-22 Thread edgarosy 

Yes My repository URL all look fine.

Thanks for your help Justin.

justinedelson wrote:
 
 Right, but does it show your artifactory repository?
 
 -Original Message-
 From: edgarosy [mailto:edgar.l...@gmail.com] 
 Sent: Friday, December 19, 2008 5:13 PM
 To: users@maven.apache.org
 Subject: RE: Unable to successfully complete a mvn install on one of my
 apps
 
 
 When I run the mvn help:effective-settings -Pacp command I get a
 successfull build. 
 
 
 justinedelson wrote:
 
 You might want to try running mvn help:effective-settings.
 
 Justin
 
 -Original Message-
 From: edgarosy [mailto:edgar.l...@gmail.com]
 Sent: Friday, December 19, 2008 4:36 PM
 To: users@maven.apache.org
 Subject: Unable to successfully complete a mvn install on one of my 
 apps
 
 
 I have an application that I have been able to install successfully in
 
 the past until I upgraded its pom and added the following
 dependencies:
 
 dependency
   groupIdSAP/groupId
   artifactIdLOG/artifactId
version7.0/version
   scoperuntime/scope
 /dependency
 
  dependency
   groupIdSAP/groupId
   artifactIdEXCEPTION/artifactId
version7.0/version
   scoperuntime/scope
 /dependency
 
  dependency
   groupIdSAP/groupId
   artifactIdSAPCLIENT/artifactId
version7.0/version
   scoperuntime/scope
 /dependency
 
  dependency
   groupIdSAP/groupId
   artifactIdJMS/artifactId
version1.1/version
   scoperuntime/scope
 /dependency
 
 I use artifactory so I uploaded all the listed dependencies jar files 
 to my artifactory repository.
 
 I verified that my settings.xml file have the right configuration on 
 the url for artifactory as well.
 
 After I do a mvn install -Pacp command I get the following error
 message:
 
 [ERROR] BUILD ERROR
 [INFO]
 --
 --
 [INFO] Failed to resolve artifact.
 
 Missing:
 --
 1) SAP:LOG:jar:7.0
 
   Try downloading the file manually from the project website.
 
   Then, install it using the command:
   mvn install:install-file -DgroupId=SAP -DartifactId=LOG 
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file
 
   Alternatively, if you host your own repository you can deploy the 
 file
 there:
   mvn deploy:deploy-file -DgroupId=SAP -DartifactId=LOG 
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
 -DrepositoryId=[id]
 
   Path to dependency:
 1) com.octanner.batchapplications:pdr:jar:8.12
 2) SAP:LOG:jar:7.0
 
 2) SAP:EXCEPTION:jar:7.0
 
   Try downloading the file manually from the project website.
 
   Then, install it using the command:
   mvn install:install-file -DgroupId=SAP -DartifactId=EXCEPTION 
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file
 
   Alternatively, if you host your own repository you can deploy the 
 file
 there:
   mvn deploy:deploy-file -DgroupId=SAP -DartifactId=EXCEPTION 
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
 -DrepositoryId=[id]
 
   Path to dependency:
 1) com.octanner.batchapplications:pdr:jar:8.12
 2) SAP:EXCEPTION:jar:7.0
 
 3) SAP:SAPCLIENT:jar:7.0
 
   Try downloading the file manually from the project website.
 
   Then, install it using the command:
   mvn install:install-file -DgroupId=SAP -DartifactId=SAPCLIENT 
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file
 
   Alternatively, if you host your own repository you can deploy the 
 file
 there:
   mvn deploy:deploy-file -DgroupId=SAP -DartifactId=SAPCLIENT 
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
 -DrepositoryId=[id]
 
   Path to dependency:
 1) com.octanner.batchapplications:pdr:jar:8.12
 2) SAP:SAPCLIENT:jar:7.0
 
 4) SAP:JMS:jar:1.1
 
   Try downloading the file manually from the project website.
 
   Then, install it using the command:
   mvn install:install-file -DgroupId=SAP -DartifactId=JMS
 -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
 
   Alternatively, if you host your own repository you can deploy the 
 file
 there:
   mvn deploy:deploy-file -DgroupId=SAP -DartifactId=JMS
 -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
 -DrepositoryId=[id]
 
   Path to dependency:
 1) com.octanner.batchapplications:pdr:jar:8.12
 2) SAP:JMS:jar:1.1
 
 --
 4 required artifacts are missing.
 
 for artifact:
   com.octanner.batchapplications:pdr:jar:8.12
 
 from the specified remote repositories:
   central (http://repo1.maven.org/maven2)
 
 I don't understand why is trying to download these files from
 http://repo1 instead of my own repository.
 
 any help would be greatly appreciated.
 
 -Miguel
 --
 View this message in context:
 http://www.nabble.com/Unable-to-successfully-complete-a-mvn-install-on
 -o ne-of-my-apps-tp21098689p21098689.html
 Sent from the Maven - Users mailing list archive at Nabble.com

Unable to successfully complete a mvn install on one of my apps

2008-12-19 Thread edgarosy 

I have an application that I have been able to install successfully in the
past until I upgraded its pom and added the following dependencies:

dependency
  groupIdSAP/groupId
  artifactIdLOG/artifactId
  version7.0/version
  scoperuntime/scope
/dependency

dependency
  groupIdSAP/groupId
  artifactIdEXCEPTION/artifactId
  version7.0/version
  scoperuntime/scope
/dependency

dependency
  groupIdSAP/groupId
  artifactIdSAPCLIENT/artifactId
  version7.0/version
  scoperuntime/scope
/dependency

dependency
  groupIdSAP/groupId
  artifactIdJMS/artifactId
  version1.1/version
  scoperuntime/scope
/dependency

I use artifactory so I uploaded all the listed dependencies jar files to my
artifactory repository.

I verified that my settings.xml file have the right configuration on the url
for artifactory as well.

After I do a mvn install -Pacp command I get the following error message:

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

Missing:
--
1) SAP:LOG:jar:7.0

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=SAP -DartifactId=LOG -Dversion=7.0
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=SAP -DartifactId=LOG -Dversion=7.0
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
1) com.octanner.batchapplications:pdr:jar:8.12
2) SAP:LOG:jar:7.0

2) SAP:EXCEPTION:jar:7.0

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=SAP -DartifactId=EXCEPTION
-Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=SAP -DartifactId=EXCEPTION
-Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

  Path to dependency:
1) com.octanner.batchapplications:pdr:jar:8.12
2) SAP:EXCEPTION:jar:7.0

3) SAP:SAPCLIENT:jar:7.0

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=SAP -DartifactId=SAPCLIENT
-Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=SAP -DartifactId=SAPCLIENT
-Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

  Path to dependency:
1) com.octanner.batchapplications:pdr:jar:8.12
2) SAP:SAPCLIENT:jar:7.0

4) SAP:JMS:jar:1.1

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=SAP -DartifactId=JMS -Dversion=1.1
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=SAP -DartifactId=JMS -Dversion=1.1
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
1) com.octanner.batchapplications:pdr:jar:8.12
2) SAP:JMS:jar:1.1

--
4 required artifacts are missing.

for artifact:
  com.octanner.batchapplications:pdr:jar:8.12

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

I don't understand why is trying to download these files from http://repo1
instead of my own repository.

any help would be greatly appreciated.

-Miguel
-- 
View this message in context: 
http://www.nabble.com/Unable-to-successfully-complete-a-mvn-install-on-one-of-my-apps-tp21098689p21098689.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Unable to successfully complete a mvn install on one of my apps

2008-12-19 Thread edgarosy 

When I run the mvn help:effective-settings -Pacp command I get a successfull
build. 


justinedelson wrote:
 
 You might want to try running mvn help:effective-settings.
 
 Justin
 
 -Original Message-
 From: edgarosy [mailto:edgar.l...@gmail.com] 
 Sent: Friday, December 19, 2008 4:36 PM
 To: users@maven.apache.org
 Subject: Unable to successfully complete a mvn install on one of my apps
 
 
 I have an application that I have been able to install successfully in
 the past until I upgraded its pom and added the following dependencies:
 
 dependency
   groupIdSAP/groupId
   artifactIdLOG/artifactId
 version7.0/version
   scoperuntime/scope
 /dependency
 
   dependency
   groupIdSAP/groupId
   artifactIdEXCEPTION/artifactId
 version7.0/version
   scoperuntime/scope
 /dependency
 
   dependency
   groupIdSAP/groupId
   artifactIdSAPCLIENT/artifactId
 version7.0/version
   scoperuntime/scope
 /dependency
 
   dependency
   groupIdSAP/groupId
   artifactIdJMS/artifactId
 version1.1/version
   scoperuntime/scope
 /dependency
 
 I use artifactory so I uploaded all the listed dependencies jar files to
 my artifactory repository.
 
 I verified that my settings.xml file have the right configuration on the
 url for artifactory as well.
 
 After I do a mvn install -Pacp command I get the following error
 message:
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] Failed to resolve artifact.
 
 Missing:
 --
 1) SAP:LOG:jar:7.0
 
   Try downloading the file manually from the project website.
 
   Then, install it using the command:
   mvn install:install-file -DgroupId=SAP -DartifactId=LOG
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file
 
   Alternatively, if you host your own repository you can deploy the file
 there:
   mvn deploy:deploy-file -DgroupId=SAP -DartifactId=LOG
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
 -DrepositoryId=[id]
 
   Path to dependency:
 1) com.octanner.batchapplications:pdr:jar:8.12
 2) SAP:LOG:jar:7.0
 
 2) SAP:EXCEPTION:jar:7.0
 
   Try downloading the file manually from the project website.
 
   Then, install it using the command:
   mvn install:install-file -DgroupId=SAP -DartifactId=EXCEPTION
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file
 
   Alternatively, if you host your own repository you can deploy the file
 there:
   mvn deploy:deploy-file -DgroupId=SAP -DartifactId=EXCEPTION
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
 -DrepositoryId=[id]
 
   Path to dependency:
 1) com.octanner.batchapplications:pdr:jar:8.12
 2) SAP:EXCEPTION:jar:7.0
 
 3) SAP:SAPCLIENT:jar:7.0
 
   Try downloading the file manually from the project website.
 
   Then, install it using the command:
   mvn install:install-file -DgroupId=SAP -DartifactId=SAPCLIENT
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file
 
   Alternatively, if you host your own repository you can deploy the file
 there:
   mvn deploy:deploy-file -DgroupId=SAP -DartifactId=SAPCLIENT
 -Dversion=7.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
 -DrepositoryId=[id]
 
   Path to dependency:
 1) com.octanner.batchapplications:pdr:jar:8.12
 2) SAP:SAPCLIENT:jar:7.0
 
 4) SAP:JMS:jar:1.1
 
   Try downloading the file manually from the project website.
 
   Then, install it using the command:
   mvn install:install-file -DgroupId=SAP -DartifactId=JMS
 -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
 
   Alternatively, if you host your own repository you can deploy the file
 there:
   mvn deploy:deploy-file -DgroupId=SAP -DartifactId=JMS
 -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
 -DrepositoryId=[id]
 
   Path to dependency:
 1) com.octanner.batchapplications:pdr:jar:8.12
 2) SAP:JMS:jar:1.1
 
 --
 4 required artifacts are missing.
 
 for artifact:
   com.octanner.batchapplications:pdr:jar:8.12
 
 from the specified remote repositories:
   central (http://repo1.maven.org/maven2)
 
 I don't understand why is trying to download these files from
 http://repo1 instead of my own repository.
 
 any help would be greatly appreciated.
 
 -Miguel
 --
 View this message in context:
 http://www.nabble.com/Unable-to-successfully-complete-a-mvn-install-on-o
 ne-of-my-apps-tp21098689p21098689.html
 Sent from the Maven - Users mailing list archive at Nabble.com.
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 
 

-- 
View this message in context: 
http