You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martijn Dashorst (JIRA)" <ji...@apache.org> on 2008/11/24 16:35:44 UTC
[jira] Closed: (WICKET-1952) Unable to resolve 1.4-SNAPSHOT all of
a sudden
[ https://issues.apache.org/jira/browse/WICKET-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn Dashorst closed WICKET-1952.
------------------------------------
Resolution: Invalid
This is a problem in your settings of your maven installation. Wicket's snapshots are not published to central, only to our wicketstuff.org repository. Apparently you or someone in your company removed any reference to the wicketstuff.org repository.
> Unable to resolve 1.4-SNAPSHOT all of a sudden
> ----------------------------------------------
>
> Key: WICKET-1952
> URL: https://issues.apache.org/jira/browse/WICKET-1952
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Reporter: Brill Pappin
>
> I am all of a sudden unable to resolve thw 1.4-SNAPSHOT deps... did something get corrupted on deployment?
> maven error outout is:
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Error building POM (may not be this project's POM).
> Project ID: null:wicket-extensions:jar:null
> Reason: Cannot find parent: org.apache.wicket:wicket-parent for project: null:wicket-extensions:jar:null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.wicket:wicket-extensions:jar': Cannot find parent: org.apache.wicket:wicket-parent for project: null:wicket-extensions:jar:null
> org.apache.wicket:wicket-extensions:jar:1.4-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> internal (http://emd0.emineollc.com:8080/archiva/repository/internal/)
> Path to dependency:
> 1) com.emineollc:emineo-wicket:jar:1.0.0-SNAPSHOT
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.wicket:wicket-extensions:jar': Cannot find parent: org.apache.wicket:wicket-parent for project: null:wicket-extensions:jar:null
> org.apache.wicket:wicket-extensions:jar:1.4-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> internal (http://emd0.emineollc.com:8080/archiva/repository/internal/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.