[
https://issues.apache.org/jira/browse/NPANDAY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011189#comment-13011189
]
Lars Corneliussen commented on NPANDAY-377:
-------------------------------------------
It might be this code fragment that troubles... Is it the right thing to catch
this exception silently?
{code}
try
{
StandardRepositoryLoader repoLoader = new
StandardRepositoryLoader();
repoLoader.setRepositoryRegistry( repositoryRegistry );
settingsRepository = (SettingsRepository)
repoLoader.loadRepository( file.getAbsolutePath(),
SettingsRepository.class.getName(), new Hashtable() );
repositoryRegistry.addRepository( "npanday-settings",
settingsRepository );
}
catch ( IOException e )
{
}
{code}
> 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-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
