[ 
https://issues.apache.org/jira/browse/OODT-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061770#comment-13061770
 ] 

Cameron Goodale commented on OODT-146:
--------------------------------------

Question for the Maven savvy in the group:  Does the svn path get built 
dynamically by maven during the mvn site command, meaning cas-catalog comes 
from the catalog's artifact_id?

I am not sure how to solve this issue, since renaming all the artifacts in the 
pom's is probably not an option.  If there is a way to force or over-ride this 
in maven, just help me get one sorted out and I can tackle the rest.

Thanks,

Cam

> Source Repository Pages Need Update
> -----------------------------------
>
>                 Key: OODT-146
>                 URL: https://issues.apache.org/jira/browse/OODT-146
>             Project: OODT
>          Issue Type: Bug
>          Components: website
>         Environment: people.apache.org
>            Reporter: Cameron Goodale
>            Assignee: Cameron Goodale
>            Priority: Minor
>              Labels: html,, maven,, site,, svn,
>             Fix For: 0.4
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> CAS Components have a 'cas-' prefix, but the source repo doesn't.
> GOTO:  http://oodt.apache.org/components/maven/catalog/source-repository.html
> http://svn.apache.org/viewvc/oodt/trunk/cas-catalog  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/catalog
> Other bad SVN links of the 'cas-' kind:
> http://svn.apache.org/viewvc/oodt/trunk/cas-curator  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/curator
> http://svn.apache.org/viewvc/oodt/trunk/cas-filemgr  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/filemgr
> http://svn.apache.org/viewvc/oodt/trunk/cas-metadata SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/metadata
> http://svn.apache.org/viewvc/oodt/trunk/pcs-input    SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/pcs
> http://svn.apache.org/viewvc/oodt/trunk/cas-pushpull SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/pushpull
> http://svn.apache.org/viewvc/oodt/trunk/cas-resource SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/resource
> http://svn.apache.org/viewvc/oodt/trunk/cas-workflow SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/workflow
> http://svn.apache.org/viewvc/oodt/trunk/cas-crawler  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/crawler
> http://svn.apache.org/viewvc/oodt/trunk/cas-pge  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/pge/
> Maven Plugin:
> http://svn.apache.org/viewvc/oodt/trunk/maven-cas-install-plugin  SHOULD BE 
> >>> http://svn.apache.org/viewvc/oodt/trunk/mvn
> Bad WebApp Links:
> http://svn.apache.org/viewvc/oodt/trunk/cas-fm-webapp  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/webapp/filemgr
> http://svn.apache.org/viewvc/oodt/trunk/cas-product  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/webapp/fmprod
> http://svn.apache.org/viewvc/oodt/trunk/cas-wm-webapp  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/webapp/workflow
> Bad Grid Components:
> http://svn.apache.org/viewvc/oodt/trunk/oodt-product  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/product
> http://svn.apache.org/viewvc/oodt/trunk/oodt-profile  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/profile
> http://svn.apache.org/viewvc/oodt/trunk/oodt-xmlps  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/xmlps
> http://oodt.apache.org/components/maven/grid/  =>  THIS HAS NO SOURCE REPO 
> LINK AT ALL.  PROJECT DOCUMENTATION IS SEVERELY LACKING.
> Common Components:
> http://svn.apache.org/viewvc/oodt/trunk/oodt-commons  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/commons
> http://svn.apache.org/viewvc/oodt/trunk/oodt-sso  SHOULD BE >>>  
> http://svn.apache.org/viewvc/oodt/trunk/sso
> http://svn.apache.org/viewvc/oodt/trunk/oodt-xmlquery  SHOULD BE >>> 
> http://svn.apache.org/viewvc/oodt/trunk/xmlquery

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to