[jira] [Commented] (NPANDAY-377) released registry-config.xml contains a hardcoded path

["Adelita L. Padilla (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NPANDAY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027434#comment-13027434 ] 

Adelita L. Padilla commented on NPANDAY-377:
--------------------------------------------

Hi Lars,

The changes I made in regsitry-config.xml, is only a dummy value.  My fix would set/reload the value for registry-config.xml base on the -Dnpanday.settings property (if no value was provided, this will be set to default which is ${user.home}\.m2) in the getNPandaySettingsPath() method I created.

I checked out the source code (r1097262) but got this error after building the source code -> http://pastie.org/1852650.  After I manually added the npanday-settings.xml file, I got a successful build.

When building a simple class library project (no npanday-settings.xml), got this error -> http://pastie.org/1852655. And after manually adding the file, got a successful build.

In my previous fix (r1096145), building source code with no npanday-settings.xml would still give a successful build.  The file would only be created/needed when building projects.  If I don't have npanday-settings.xml when building projects, I still don't get any errors since it will be generated if no such file existed.

If I also set a property -Dnpanday.settings and in that path, no npanday-settings.xml existed, I would still get a successful build since the file would be generated in that specified path.

So in the current revision now, npanday-settings.xml is needed to be able to build the source code and sample project successfully.  The npanday-settings.xml file would not be automatically generated if ever it doesn't exist.  We also need to reopen the ff issues since they are not fixed in the current revision:

https://issues.apache.org/jira/browse/NPANDAY-376
https://issues.apache.org/jira/browse/NPANDAY-361


Thanks,

liit

> 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