[ 
https://jira.codehaus.org/browse/WAGON-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308757#comment-308757
 ] 

Rob Elliot commented on WAGON-374:
----------------------------------

I don't understand why this is Won't Fix. The documentation as it stands does 
not work. If the intention is that the functionality is not changed so that the 
documentation is currect, then the documentation itself should be changed - 
perhaps to point at the new mechanism. Otherwise other people will waste hours 
of their time trying to get it to work, as I did.

Incidentally I'm surprised the Maven maintainers are pushing us towards a new 
means of publishing sites when the existing mechanism is meant to be extensible 
- particularly when the existing way nearly works, and the new mechanism 
actually aspires to working via the existing way ("Future dreams"). Surely the 
effort would be better spent fixing the existing mechanism?
                
> Deploying your Maven site to GitHub's gh-pages
> ----------------------------------------------
>
>                 Key: WAGON-374
>                 URL: https://jira.codehaus.org/browse/WAGON-374
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-scm
>    Affects Versions: 2.2
>            Reporter: Samuel Santos
>            Assignee: Olivier Lamy
>
> The example at 
> http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html for 
> deploying a Maven site to GitHub's pages does not work.

--
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