[jira] [Commented] (NPANDAY-631) Something seems to be adding additional repo's partway through build?

["Brett Porter (JIRA)" <ji...@apache.org>]

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

Brett Porter commented on NPANDAY-631:
--------------------------------------

{{apache.snapshots}} comes from the Apache parent POM, {{npanday.snapshots}} from the NPanday top-most POM. These are used by the plugins, as well as to resolve plugins.

It's not clear why you would have got these inconsistently, or if there's anything wrong on NPanday here - just seems like more motivation to get a newer stable release out - do you agree?

> Something seems to be adding additional repo's partway through build?
> ---------------------------------------------------------------------
>
>                 Key: NPANDAY-631
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-631
>             Project: NPanday
>          Issue Type: Bug
>          Components: Maven Plugins
>    Affects Versions: 1.5.0-incubating
>            Reporter: Greg Domjan
>            Priority: Minor
>              Labels: newbie
>
> Perhaps a newbie question, but this was confusing this morning when our build started failing with no idea of external inputs.
> I have been able to resolve this by rebuilding our local from source to bring our local nexus up to date.
> It seems we may need to Add npanday.snapshots and apach.snapshots to our nexus to proxy, however I can't find where apache.snapshots is defined so far.
> We have these 2 repo's defined that appear like 
>  {code} 
> [INFO] snapshot org.apache.npanday:apache-npanday:1.5.0-incubating-SNAPSHOT: checking for updates from nsl.nexus
> [INFO] snapshot org.apache.npanday:apache-npanday:1.5.0-incubating-SNAPSHOT: checking for updates from public
>  {code} 
> Partway through artifact resolution 2 more 'appear'
>  {code} 
> [INFO] snapshot org.apache.npanday:dotnet-registry:1.5.0-incubating-SNAPSHOT: checking for updates from nsl.nexus
> [INFO] snapshot org.apache.npanday:dotnet-registry:1.5.0-incubating-SNAPSHOT: checking for updates from public
> [INFO] snapshot org.apache.npanday:dotnet-registry:1.5.0-incubating-SNAPSHOT: checking for updates from npanday.snapshots
> [INFO] snapshot org.apache.npanday:dotnet-registry:1.5.0-incubating-SNAPSHOT: checking for updates from apache.snapshots
>  {code} 
> With recent changes overnight our build started failing and the only thing I could find is that the following cause some external updates to be applied inconsitently.
> [INFO] [compile:initialize {execution: default-initialize}]
> [INFO] NPANDAY-148-009: Took 18ms to resolve dependencies for com.netIQ.IAM.SecureLogin:netWizardModel:dotnet-library:8.1.0-0-SNAPSHOT with
> filter org.apache.maven.artifact.resolver.filter.AndArtifactFilter@4b28899a
> [FATAL ERROR] npanday.plugin.compile.ComponentInitializerMojo#execute() caused a linkage error (java.lang.NoSuchMethodError) and may be out-
> of-date. Check the realms:
> [FATAL ERROR] Plugin realm = app0.child-container[org.apache.npanday.plugins:maven-compile-plugin:1.5.0-incubating-SNAPSHOT]
> urls[0] = file:/e:/data/.m2/repository/org/apache/npanday/plugins/maven-compile-plugin/1.5.0-incubating-SNAPSHOT/maven-compile-plugin-1.5.0-
> incubating-SNAPSHOT.jar
> urls[1] = file:/e:/data/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar
> urls[2] = file:/e:/data/.m2/repository/org/apache/npanday/dotnet-registry/1.5.0-incubating-SNAPSHOT/dotnet-registry-1.5.0-incubating-SNAPSHOT.jar
> ...
> urls[37] = file:/e:/data/.m2/repository/org/apache/npanday/dotnet-model-configuration-appenders/1.5.0-incubating-SNAPSHOT/dotnet-model-confi
> guration-appenders-1.5.0-incubating-SNAPSHOT.jar
> [FATAL ERROR] Container realm = plexus.core
> urls[0] = file:/E:/Data/Devtool/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] npanday.assembler.AssemblerContext.init(Lorg/apache/maven/project/MavenProject;)V
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NoSuchMethodError: npanday.assembler.AssemblerContext.init(Lorg/apache/maven/project/MavenProject;)V
>         at npanday.plugin.compile.ComponentInitializerMojo.execute(ComponentInitializerMojo.java:100)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>  {code} 



--
This message was sent by Atlassian JIRA
(v6.2#6252)