You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Chris Harris (JIRA)" <ji...@codehaus.org> on 2012/09/13 06:19:21 UTC
[jira] (MRM-1670) non-default Repositories, Repository Groups, and
Proxy Connectors disappear when switching Archiva to Windows service
Chris Harris created MRM-1670:
---------------------------------
Summary: 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
[jira] (MRM-1670) non-default Repositories, Repository Groups, and
Proxy Connectors disappear when switching Archiva to Windows service
Posted by "Chris Harris (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308435#comment-308435 ]
Chris Harris commented on MRM-1670:
-----------------------------------
Understood, Eric.
Thanks for the clarification.
> 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
[jira] (MRM-1670) non-default Repositories, Repository Groups, and
Proxy Connectors disappear when switching Archiva to Windows service
Posted by "Eric Barboni (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308433#comment-308433 ]
Eric Barboni commented on MRM-1670:
-----------------------------------
${appserver.base}/conf/Catalina/localhost/archiva.xml is the Context configuration.
but the archiva.xml located in C:\Documents and Settings\<username>\.m2 or ${appserver.base}/conf are the archiva configuration file (with repos and so on)
archiva service in windows is not started as <username> but as local system with no home so archiva will default to ${appserver.base}/conf
you may try to use Services Control Panel (services.msc on windows 7) to make archiva service run as <username>.
> 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
[jira] (MRM-1670) non-default Repositories, Repository Groups, and
Proxy Connectors disappear when switching Archiva to Windows service
Posted by "Chris Harris (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MRM-1670) non-default Repositories, Repository Groups, and
Proxy Connectors disappear when switching Archiva to Windows service
Posted by "Eric Barboni (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308393#comment-308393 ]
Eric Barboni commented on MRM-1670:
-----------------------------------
Hi Chris the configuration used by service may be located in a different place than the standalone one.
You may have ~/.m2/archiva.xml configuration file in your home if you run from command prompt
but another archiva.xml may live at another place for the user in charge of the service.
If your allowed to do so I would try a full search on drive to see archiva.xml and check file modification time.
> 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
[jira] (MRM-1670) non-default Repositories, Repository Groups, and
Proxy Connectors disappear when switching Archiva to Windows service
Posted by "Eric Barboni (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Barboni closed MRM-1670.
-----------------------------
Resolution: Won't Fix
> 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