Lars Corneliussen commented on NPANDAY-377:

I created a fix that works for me and does not break your integration test. 
Also refactored a bit.

I think this is the problem:
+      <repository-config>${npanday.settings}</repository-config>

When there is no ${npanday.settings}, as in my case, this will just be empty 
and not default to ${user.home}/.m2/npanday-settings.xml

Also when not using -Dnpanday-settings, but pom configuration, I do not think 
this would ever be correct. This might still be an issue.

> 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

Reply via email to