[jira] [Commented] (NPANDAY-377) released registry-config.xml contains a hardcoded path
[
https://issues.apache.org/jira/browse/NPANDAY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027524#comment-13027524
]
Brett Porter commented on NPANDAY-377:
--
are more ITs needed to test the different ways the settings are set, or did the
IT catch it in the end?
> 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
[jira] [Commented] (NPANDAY-377) released registry-config.xml contains a hardcoded path
[
https://issues.apache.org/jira/browse/NPANDAY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027502#comment-13027502
]
Lars Corneliussen commented on NPANDAY-377:
---
I reproduced and fixed the error you got in #1098424.
When this works for you, it might be enough for resolving the 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
[jira] [Commented] (NPANDAY-377) released registry-config.xml contains a hardcoded path
[
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
[jira] [Commented] (NPANDAY-377) released registry-config.xml contains a hardcoded path
[
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
[jira] [Commented] (NPANDAY-377) released registry-config.xml contains a hardcoded path
[
https://issues.apache.org/jira/browse/NPANDAY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026032#comment-13026032
]
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:
{code}
-
${user.home}/.m2/npanday-settings.xml
+ ${npanday.settings}
{code}
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
[jira] [Commented] (NPANDAY-377) released registry-config.xml contains a hardcoded path
[
https://issues.apache.org/jira/browse/NPANDAY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014437#comment-13014437
]
Lars Corneliussen commented on NPANDAY-377:
---
Liit looks into it next week.
> 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
[jira] [Commented] (NPANDAY-377) released registry-config.xml contains a hardcoded path
[
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
[jira] [Commented] (NPANDAY-377) released registry-config.xml contains a hardcoded path
[
https://issues.apache.org/jira/browse/NPANDAY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011188#comment-13011188
]
Lars Corneliussen commented on NPANDAY-377:
---
Well, I'm bootstrapping NPanday from trunk using with Maven 3 +
NPanday-SNAPSHOT as stable version.
My full log:
{code}
[DEBUG] Configuring mojo npanday.plugin:maven-xsd-plugin:2.0-SNAPSHOT:xsd from
plugin realm ClassRealm[plugin>npanday.plugin:maven-xsd-plugin:2.0-SNAPSHOT,
parent: sun.misc.Launcher$AppClassLoader@553f5d07]
[DEBUG] NPANDAY-102-012: Initialized rule factory
repositoryRegistry:npanday.registry.impl.RepositoryRegistryImpl@5450211a
[DEBUG] NPANDAY-103-036.0: Respository registry:
npanday.registry.impl.RepositoryRegistryImpl@5450211a
[DEBUG] NPANDAY-102-001: Unable to initialize rule factory.
npanday.InitializationException: NPANDAY-103-001: Settings Repository is null.
Aborting initialization of VendorInfoTranstionRuleFactory
at
npanday.vendor.impl.VendorInfoTransitionRuleFactory.init(VendorInfoTransitionRuleFactory.java:100)
at
npanday.vendor.impl.StateMachineProcessorImpl.initialize(StateMachineProcessorImpl.java:87)
at
org.codehaus.plexus.PlexusLifecycleManager.initialize(PlexusLifecycleManager.java:265)
at
org.codehaus.plexus.PlexusLifecycleManager.manageLifecycle(PlexusLifecycleManager.java:227)
at
org.codehaus.plexus.PlexusLifecycleManager.manageDeferredLifecycles(PlexusLifecycleManager.java:199)
at
org.codehaus.plexus.PlexusLifecycleManager.manage(PlexusLifecycleManager.java:124)
at
org.sonatype.guice.plexus.binders.PlexusBeanBinder.afterInjection(PlexusBeanBinder.java:79)
at
com.google.inject.internal.MembersInjectorImpl.notifyListeners(MembersInjectorImpl.java:97)
at
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:95)
at
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:253)
at
com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:949)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1002)
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:945)
at
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:984)
at
org.sonatype.guice.bean.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
at
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at
com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:949)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:995)
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:945)
at com.google.inject.Scopes$1$1.get(Scopes.java:59)
at
org.sonatype.guice.bean.locators.LazyQualifiedBean.getValue(LazyQualifiedBean.java:66)
at
org.sonatype.guice.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:54)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:247)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:239)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:451)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:98)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher
[jira] [Commented] (NPANDAY-377) released registry-config.xml contains a hardcoded path
[
https://issues.apache.org/jira/browse/NPANDAY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010582#comment-13010582
]
Joe Ocaba commented on NPANDAY-377:
---
I can build on trunk successfully with the revision.
Maybe its a configuration issue with settings.xml?
> 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
