[
https://issues.apache.org/jira/browse/NPANDAY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027496#comment-13027496
]
Lars Corneliussen commented on NPANDAY-377:
-------------------------------------------
Hi liit,
I'll have a look at this. Sorry for breaking it for you again. Together we'll
lead this to more robustness.
I ran the IT you created for 377, and it passed. I think it did create the
settings. Let me retry now.
:-)
_
Lars
> released registry-config.xml contains a hardcoded path
> ------------------------------------------------------
>
> Key: NPANDAY-377
> URL: https://issues.apache.org/jira/browse/NPANDAY-377
> Project: NPanday
> Issue Type: Bug
> Affects Versions: 1.3.1-incubating
> Reporter: Adelita L. Padilla
> Assignee: Adelita L. Padilla
> Priority: Minor
> Fix For: 1.3.1-incubating
>
>
> Extract the jar file found in
> http://vmbuild.apache.org/archiva/repository/staged-npanday/npanday/dotnet-core/
>
> Noticed that the registry-config.xml file contains a hardcoded path (The
> {user.home} of the release manager was hardcoded).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
