[
http://jira.codehaus.org/browse/MRM-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110244
]
Brett Porter commented on MRM-523:
----------------------------------
suggested workaround to avoid the log spam: set -Duser.home in the wrapper (or
HOME in the env) before running to an effectively-homeless but writeable
location (eg /tmp/archiva-home) - the account can still have no real home, this
is just to tell Java where to treat $HOME.
Will fix this properly in 1.x - I would suggest:
- sourcing from the managed repositories instead of remote
- proxying if necessary
- not needing a local repository
- when saving a new POM, allow selection of the managed repository to store to
This makes the actions more specific to Archiva, so might need to come up with
something easier to work with there so we don't diverge from what is used in
Continuum.
> Appearance Actions do not work when ${user.home} is invalid.
> ------------------------------------------------------------
>
> Key: MRM-523
> URL: http://jira.codehaus.org/browse/MRM-523
> Project: Archiva
> Issue Type: Bug
> Components: system
> Affects Versions: 1.0-beta-2
> Reporter: Joakim Erdfelt
> Assignee: Brett Porter
> Priority: Minor
> Fix For: 1.x
>
>
> The reliance on maven core components with regards to Appearance / Company
> Info / Edit Pom actions, prevents server installations without a valid user
> $HOME directory. ( such as /dev/null )
> We should migrate away from maven core components at our earliest opportunity.
--
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
