Hi Richard,

Thanks for your answer, I think my last example confused everyone :-).

My problem is a bit a different (I think) here it goes again:

*SETTINGS.XML snippet*

    <activeProfiles>
        <activeProfile>company.default.profile</activeProfile>
    </activeProfiles>

    <profiles>
        <profile>
            <id>company.default.profile</id>
            <properties>
*                <company.maven.repo>
                      http://maven:8080/repo
                </company.maven.repo>
*            </properties>
        </profile>
    </profiles>

*POM.XML snippet*

    <repositories>
        <repository>
            <id>company.repo</id>
                        <name>Main Respository</name>
*            <url>${company.maven.repo}</**url>*
        </repository>
    </repositories>

    <parent>
        <groupId>company.pom</groupId>
        <artifactId>company-pom</artifactId>
        <version>1.0.1-SNAPSHOT</version>
    </parent>

    <distributionManagement>
        <repository>
             <id>company.repo</id>
             <name>Main Respository</name>
            * <url>dav:${company.maven.repo}</url>*
        </repository>
    </distributionManagement>


How does this work:

*mvn -U -compile*
   I get this warning at the very beginning
   which implies SNAPSHOT is not updated, and property *company.maven.repo *is
not resolved

[WARNING] *Could not transfer metadata* *
company.pom:company-pom:1.0.1-SNAPSHOT*/maven-metadata.xml *from/to
brovada.repo (${company.maven.repo})*: No connector available to access
repository company.repo (${company.maven.repo}) of type default using the
available factories WagonRepositoryConnectorFactory

*mvn deploy*
*   *The company.maven.repo is correctly resolved.

*mvn help:effective-pom*
    **The company.maven.repo is correctly resolved.


So my problem is why does this variable is not resolved when trying to
update snapshots,
is this an expected behaviour ?

thanks in advance
tonio

Reply via email to