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

Chris Harris commented on MRM-1670:
-----------------------------------

I'm glad you pointed that out.  I indeed found another archiva.xml that I 
didn't create, but it's located under ${appserver.base}/conf.  The archiva.xml 
that I created is under ${appserver.base}/conf/Catalina/localhost.  There is an 
additional archiva.xml under C:\Documents and Settings\<username>\.m2.

I'm still using Archiva as a service, so the only archiva.xml with a timestamp 
for today is the one located at ${appserver.base}/conf.  I wasn't expecting 
that since the .war installation instructions tell me to put archiva.xml in 
${appserver.base}/conf/Catalina/localhost.

Nonetheless, thank you for pointing this out.  I never would have thought that 
the .war running on Tomcat as a service would create and use a config file 
elsewhere than if it weren't a service.
                
> non-default Repositories, Repository Groups, and Proxy Connectors disappear 
> when switching Archiva to Windows service
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRM-1670
>                 URL: https://jira.codehaus.org/browse/MRM-1670
>             Project: Archiva
>          Issue Type: Bug
>          Components: Design, repository interface
>    Affects Versions: 1.4-M3
>         Environment: Windows XP Professional, Tomcat 7.0.2 (base separated 
> from installation), Apache 2.2 w/ mod_proxy, MySQL 5.5 for FileSystem, 
> DataStore, and PM.
>            Reporter: Chris Harris
>            Priority: Minor
>         Attachments: archiva-admin-ui.JPG, windows-explorer.JPG
>
>
> When I set up Archiva on Tomcat, I was launching Tomcat manually via the 
> command prompt.  During this time, I set up 2 repositories (1 with a Stage 
> repository), many remote repositories, a repository group, and a proxy 
> connector. Once I was satisfied with my setup, I set the Tomcat instance as a 
> Windows service.
> I was surprised to find that the repositories, repository group, and proxy 
> connector I created were missing.  Only the default internal and snapshots 
> repositories remained.  The default central remote repository remained. The 
> default proxy connector was still present (the one connecting internal to 
> central).  No repository groups remained.
> I located ${appserver.base} and found data/repositories.  Within that 
> subdirectory path, I found my 2 repositories (+ the stage repository for a 
> total of 3 repos).
> Suspecting buggery, I created a new managed repository named test.  Sure 
> enough, test appeared in the same subdirectory as the 3 repos I created when 
> Archiva was not launched via Tomcat as a Windows service.  Archiva could see 
> test, but it could not see the other 3 repos.
> I've attached screenshots showing the Archiva ui and Windows Explorer after I 
> created "test".

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