Mykel Alvis created MSITE-630:
---------------------------------

             Summary: URLs created by properties in the settings file don't get 
expanded 
                 Key: MSITE-630
                 URL: https://jira.codehaus.org/browse/MSITE-630
             Project: Maven 2.x and 3.x Site Plugin
          Issue Type: Bug
    Affects Versions: 3.0
         Environment: maven 3.0.4
            Reporter: Mykel Alvis
         Attachments: site-deploy-tests.zip

I use a properties set in the settings file to make migrations from multiple 
work locations easier.  One of these is the URL to deploy the site.
In 3.0, I get the following error unless I define the property as a 
-Dproperty=value on the command line.  With 3.0-beta-3 these work without error.

{noformat}
..... Error uploading site: Cannot connect. Reason: 
java.net.UnknownHostException: ${default.site.location}
{noformat}

Attached is a set of projects that will demonstrate this.
It will be necessary to do the following to set up the test
# determine a url for a site repository.  I use 
scp://documentation.mytest.net/var/www/html/documentation/m2-sites/IGNORE which 
is fake and will not work.
# Add a property in settings.xml 
{{<default.site.location>scp://documentation.mytest.net/var/www/html/documentation/m2-sites/IGNORE</default.site.location>}}
# unzip the tests and modify the pom in test-working1, test-working3, and 
test-working4 to point to your target site url.
# run test.sh

On my machine, all the test-working* projects deploy, test-notworking1 does not 
deploy (with the aforementioned error) and test-notworking1 will work with the 
property specified on the command line via 
-Ddefault.site.location=scp://documentation.mytest.net/var/www/html/documentation/m2-sites/IGNORE




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to