[ http://jira.codehaus.org/browse/MNG-1228?page=comments#action_62050 ]
Josh Moore commented on MNG-1228:
---------------------------------
<artifact:pom ... /> isn't reading settings.xml either. We have a version
number stored in settings.xml. Error message:
[mvn:pom] An error has occurred while processing the Maven artifact tasks.
[mvn:pom] Diagnosis:
[mvn:pom]
[mvn:pom] Unable to build project: <dir>/pom.xml
[mvn:pom] The POM expression: ${omero.version} could not be evaluated.
Reason: omero:common:pom:${omero.version} references itself.
BUILD FAILED
> ant artifact doesn't read settings.xml
> --------------------------------------
>
> Key: MNG-1228
> URL: http://jira.codehaus.org/browse/MNG-1228
> Project: Maven 2
> Type: Bug
> Components: Ant tasks
> Versions: 2.0 (RC)
> Environment: winxp
> Reporter: Brian Fox
> Fix For: 2.0.4
>
>
> We are using an ant script to call maven deploy to auto deploy jar, pom and
> md5's and sh1's for 3rd party libraries to our remote repository. The maven
> deploy ant task isn't using the settings to find our mirrors or repositories
> for download. We have a parent pom that it should find, but it's not. The
> settings.xml is in maven/conf and in HOME/.m2/ and in HOME/.ant/
> The repositories are defined in our pom file, but the login information needs
> to be in the settings.xml. When we run this, it isn't finding the login
> information from settings. We also had an issue where the remote repositories
> where defined in settings and it wasn't working until we moved it to the pom.
> The underlying problem seems to be that settings isn't taken into account in
> either case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
