You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2008/10/25 06:57:02 UTC

[jira] Created: (MRM-986) archiva.xml is saved in home directory instead of $ARCHIVA_BASE/conf

archiva.xml is saved in home directory instead of $ARCHIVA_BASE/conf
--------------------------------------------------------------------

                 Key: MRM-986
                 URL: http://jira.codehaus.org/browse/MRM-986
             Project: Archiva
          Issue Type: Bug
    Affects Versions: 1.1.3
            Reporter: Wendy Smoak


According to http://archiva.apache.org/docs/1.1.3/adminguide/standalone.html 

When Archiva saves it's configuration, all configuration is stored to a single file. The file chosen is by the following rules:

    * If ~/.m2/archiva.xml exists, it is saved there
    * Otherwise, it is saved to $ARCHIVA_BASE/conf/archiva.xml, regardless of whether it previously existed.

With 1.1.3, if no archiva.xml file exists, it incorrectly writes the file to ~/.m2.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (MRM-986) archiva.xml is saved in home directory instead of $ARCHIVA_BASE/conf

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-986:
---------------------------------

    Fix Version/s:     (was: 1.2)
                   1.2-M1

> archiva.xml is saved in home directory instead of $ARCHIVA_BASE/conf
> --------------------------------------------------------------------
>
>                 Key: MRM-986
>                 URL: http://jira.codehaus.org/browse/MRM-986
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.1.3
>            Reporter: Wendy Smoak
>            Assignee: Brett Porter
>             Fix For: 1.2-M1
>
>
> According to http://archiva.apache.org/docs/1.1.3/adminguide/standalone.html 
> When Archiva saves it's configuration, all configuration is stored to a single file. The file chosen is by the following rules:
>     * If ~/.m2/archiva.xml exists, it is saved there
>     * Otherwise, it is saved to $ARCHIVA_BASE/conf/archiva.xml, regardless of whether it previously existed.
> With 1.1.3, if no archiva.xml file exists, it incorrectly writes the file to ~/.m2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MRM-986) archiva.xml is saved in home directory instead of $ARCHIVA_BASE/conf

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151889#action_151889 ] 

Brett Porter commented on MRM-986:
----------------------------------

I think the docs are wrong. The behaviour is as expected, but I Think if $ARCHIVA_BASE/conf exists, then that will be written to instead.

> archiva.xml is saved in home directory instead of $ARCHIVA_BASE/conf
> --------------------------------------------------------------------
>
>                 Key: MRM-986
>                 URL: http://jira.codehaus.org/browse/MRM-986
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.1.3
>            Reporter: Wendy Smoak
>
> According to http://archiva.apache.org/docs/1.1.3/adminguide/standalone.html 
> When Archiva saves it's configuration, all configuration is stored to a single file. The file chosen is by the following rules:
>     * If ~/.m2/archiva.xml exists, it is saved there
>     * Otherwise, it is saved to $ARCHIVA_BASE/conf/archiva.xml, regardless of whether it previously existed.
> With 1.1.3, if no archiva.xml file exists, it incorrectly writes the file to ~/.m2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (MRM-986) archiva.xml is saved in home directory instead of $ARCHIVA_BASE/conf

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MRM-986.
----------------------------

         Assignee: Brett Porter
       Resolution: Fixed
    Fix Version/s: 1.2

> archiva.xml is saved in home directory instead of $ARCHIVA_BASE/conf
> --------------------------------------------------------------------
>
>                 Key: MRM-986
>                 URL: http://jira.codehaus.org/browse/MRM-986
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.1.3
>            Reporter: Wendy Smoak
>            Assignee: Brett Porter
>             Fix For: 1.2
>
>
> According to http://archiva.apache.org/docs/1.1.3/adminguide/standalone.html 
> When Archiva saves it's configuration, all configuration is stored to a single file. The file chosen is by the following rules:
>     * If ~/.m2/archiva.xml exists, it is saved there
>     * Otherwise, it is saved to $ARCHIVA_BASE/conf/archiva.xml, regardless of whether it previously existed.
> With 1.1.3, if no archiva.xml file exists, it incorrectly writes the file to ~/.m2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MRM-986) archiva.xml is saved in home directory instead of $ARCHIVA_BASE/conf

Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151883#action_151883 ] 

Wendy Smoak commented on MRM-986:
---------------------------------

To reproduce...

1. Confirm that no archiva.xml exists:

$ ls /Applications/apache-archiva-1.1.3/conf/archiva.xml
ls: /Applications/apache-archiva-1.1.3/conf/archiva.xml: No such file or directory

$ ls ~/.m2/archiva.xml
ls: /Users/wsmoak/.m2/archiva.xml: No such file or directory

2. Start Archiva

3. Add a repository through the web interface so it will have some new configuration to save 

4. Stop Archiva

5. Check where archiva.xml was written:

$ ls /Applications/apache-archiva-1.1.3/conf/archiva.xml
ls: /Applications/apache-archiva-1.1.3/conf/archiva.xml: No such file or directory

$ ls ~/.m2/archiva.xml
/Users/wsmoak/.m2/archiva.xml

Result: 

The archiva.xml file was written to ~/.m2/ when it should be in conf.


> archiva.xml is saved in home directory instead of $ARCHIVA_BASE/conf
> --------------------------------------------------------------------
>
>                 Key: MRM-986
>                 URL: http://jira.codehaus.org/browse/MRM-986
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.1.3
>            Reporter: Wendy Smoak
>
> According to http://archiva.apache.org/docs/1.1.3/adminguide/standalone.html 
> When Archiva saves it's configuration, all configuration is stored to a single file. The file chosen is by the following rules:
>     * If ~/.m2/archiva.xml exists, it is saved there
>     * Otherwise, it is saved to $ARCHIVA_BASE/conf/archiva.xml, regardless of whether it previously existed.
> With 1.1.3, if no archiva.xml file exists, it incorrectly writes the file to ~/.m2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira