maven repo is not public?
63 views
Skip to first unread message
brentryan
Oct 4, 2011, 3:18:53 PM10/4/11
to PlayN
Can this maven repo be made public?
http://samskivert.github.com/gwt-maven-plugin/repository
I'm currently using an internal maven repository which needs to proxy
to the above repository, but it can't because this repo isn't public.
So when I try to build my project I get this error:
[INFO] Reactor Summary:
[INFO]
[INFO] PlayN Project ..................................... SUCCESS
[10.191s]
[INFO] PlayN Project Archetype ........................... SUCCESS
[44.360s]
[INFO] PlayN Core ........................................ SUCCESS
[30.370s]
[INFO] PlayN JBox2D ...................................... SUCCESS
[1:56.831s]
[INFO] PlayN WebGL ....................................... SUCCESS
[0.972s]
[INFO] PlayN Java ........................................ SUCCESS
[12.199s]
[INFO] PlayN HTML ........................................ SUCCESS
[26.611s]
[INFO] PlayN Flash ....................................... SUCCESS
[5.306s]
[INFO] PlayN Android ..................................... SUCCESS
[30.136s]
[INFO] PlayN Server ...................................... SUCCESS
[9.231s]
[INFO] PlayN Demos Project ............................... SUCCESS
[0.006s]
[INFO] PlayN Hello Metaproject ........................... SUCCESS
[0.006s]
[INFO] PlayN Hello Core .................................. SUCCESS
[0.696s]
[INFO] PlayN Hello HTML .................................. FAILURE
[0.276s]
[INFO] PlayN Hello Flash ................................. SKIPPED
[INFO] PlayN Hello Android ............................... SKIPPED
[INFO] PlayN Showcase Metaproject ........................ SKIPPED
[INFO] PlayN Showcase Core ............................... SKIPPED
[INFO] PlayN Showcase HTML ............................... SKIPPED
[INFO] PlayN Showcase Flash .............................. SKIPPED
[INFO] PlayN Showcase Android ............................ SKIPPED
[INFO] PlayN Cute Metaproject ............................ SKIPPED
[INFO] PlayN Cute Core ................................... SKIPPED
[INFO] PlayN Cute HTML ................................... SKIPPED
[INFO] PlayN Cute Flash .................................. SKIPPED
[INFO] PlayN Cute Android ................................ SKIPPED
[INFO] PlayN Payments .................................... SKIPPED
[INFO] PlayN Payments Core ............................... SKIPPED
[INFO] PlayN Payments Demo Metaproject ................... SKIPPED
[INFO] PlayN Payments Demo Core .......................... SKIPPED
[INFO] PlayN payments HTML ............................... SKIPPED
[INFO] PlayN payments Server ............................. SKIPPED
[INFO] PlayN Payments Demo HTML .......................... SKIPPED
[INFO] PlayN Tests Metaproject ........................... SKIPPED
[INFO] PlayN Benchmark Metaproject ....................... SKIPPED
[INFO] PlayN Benchmarks Core ............................. SKIPPED
[INFO] PlayN Benchmark HTML .............................. SKIPPED
[INFO] PlayN Manual Tests Metaproject .................... SKIPPED
[INFO] PlayN Manual Tests Core ........................... SKIPPED
[INFO] PlayN Manual Tests HTML ........................... SKIPPED
[INFO] PlayN Manual Tests Flash .......................... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 7:00.049s
[INFO] Finished at: Tue Oct 04 15:17:53 EDT 2011
[INFO] Final Memory: 13M/81M
[INFO]
------------------------------------------------------------------------
[ERROR] Plugin org.codehaus.mojo:gwt-maven-plugin:2.3.0-2-playn or one
of its dependencies could not be resolved: Failed to read artifact
descriptor for org.codehaus.mojo:gwt-maven-plugin:jar:2.3.0-2-playn:
Could not find artifact org.codehaus.mojo:gwt-maven-plugin:pom:2.3.0-2-
playn in nexus (http://dev2-settler-01:8081/nexus/content/groups/
public) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
Any ideas?
http://samskivert.github.com/gwt-maven-plugin/repository
I'm currently using an internal maven repository which needs to proxy
to the above repository, but it can't because this repo isn't public.
So when I try to build my project I get this error:
[INFO] Reactor Summary:
[INFO]
[INFO] PlayN Project ..................................... SUCCESS
[10.191s]
[INFO] PlayN Project Archetype ........................... SUCCESS
[44.360s]
[INFO] PlayN Core ........................................ SUCCESS
[30.370s]
[INFO] PlayN JBox2D ...................................... SUCCESS
[1:56.831s]
[INFO] PlayN WebGL ....................................... SUCCESS
[0.972s]
[INFO] PlayN Java ........................................ SUCCESS
[12.199s]
[INFO] PlayN HTML ........................................ SUCCESS
[26.611s]
[INFO] PlayN Flash ....................................... SUCCESS
[5.306s]
[INFO] PlayN Android ..................................... SUCCESS
[30.136s]
[INFO] PlayN Server ...................................... SUCCESS
[9.231s]
[INFO] PlayN Demos Project ............................... SUCCESS
[0.006s]
[INFO] PlayN Hello Metaproject ........................... SUCCESS
[0.006s]
[INFO] PlayN Hello Core .................................. SUCCESS
[0.696s]
[INFO] PlayN Hello HTML .................................. FAILURE
[0.276s]
[INFO] PlayN Hello Flash ................................. SKIPPED
[INFO] PlayN Hello Android ............................... SKIPPED
[INFO] PlayN Showcase Metaproject ........................ SKIPPED
[INFO] PlayN Showcase Core ............................... SKIPPED
[INFO] PlayN Showcase HTML ............................... SKIPPED
[INFO] PlayN Showcase Flash .............................. SKIPPED
[INFO] PlayN Showcase Android ............................ SKIPPED
[INFO] PlayN Cute Metaproject ............................ SKIPPED
[INFO] PlayN Cute Core ................................... SKIPPED
[INFO] PlayN Cute HTML ................................... SKIPPED
[INFO] PlayN Cute Flash .................................. SKIPPED
[INFO] PlayN Cute Android ................................ SKIPPED
[INFO] PlayN Payments .................................... SKIPPED
[INFO] PlayN Payments Core ............................... SKIPPED
[INFO] PlayN Payments Demo Metaproject ................... SKIPPED
[INFO] PlayN Payments Demo Core .......................... SKIPPED
[INFO] PlayN payments HTML ............................... SKIPPED
[INFO] PlayN payments Server ............................. SKIPPED
[INFO] PlayN Payments Demo HTML .......................... SKIPPED
[INFO] PlayN Tests Metaproject ........................... SKIPPED
[INFO] PlayN Benchmark Metaproject ....................... SKIPPED
[INFO] PlayN Benchmarks Core ............................. SKIPPED
[INFO] PlayN Benchmark HTML .............................. SKIPPED
[INFO] PlayN Manual Tests Metaproject .................... SKIPPED
[INFO] PlayN Manual Tests Core ........................... SKIPPED
[INFO] PlayN Manual Tests HTML ........................... SKIPPED
[INFO] PlayN Manual Tests Flash .......................... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 7:00.049s
[INFO] Finished at: Tue Oct 04 15:17:53 EDT 2011
[INFO] Final Memory: 13M/81M
[INFO]
------------------------------------------------------------------------
[ERROR] Plugin org.codehaus.mojo:gwt-maven-plugin:2.3.0-2-playn or one
of its dependencies could not be resolved: Failed to read artifact
descriptor for org.codehaus.mojo:gwt-maven-plugin:jar:2.3.0-2-playn:
Could not find artifact org.codehaus.mojo:gwt-maven-plugin:pom:2.3.0-2-
playn in nexus (http://dev2-settler-01:8081/nexus/content/groups/
public) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
Any ideas?
Michael Bayne
Oct 4, 2011, 3:26:49 PM10/4/11
to pl...@googlegroups.com
On Tue, Oct 4, 2011 at 12:18 PM, brentryan <brent...@gmail.com> wrote:
> Can this maven repo be made public?
>
> http://samskivert.github.com/gwt-maven-plugin/repository
>
> I'm currently using an internal maven repository which needs to proxy
> to the above repository, but it can't because this repo isn't public.
> Can this maven repo be made public?
>
> http://samskivert.github.com/gwt-maven-plugin/repository
>
> I'm currently using an internal maven repository which needs to proxy
> to the above repository, but it can't because this repo isn't public.
What does that mean? It's as public as any other repository, in that
you can access it from anywhere on the Internet. Is there some other
public/non-public distinction that Maven makes?
You can't get a directory listing, but the necessary files are there:
http://samskivert.github.com/gwt-maven-plugin/repository/org/codehaus/mojo/gwt-maven-plugin/2.3.0-2-playn/gwt-maven-plugin-2.3.0-2-playn.pom
http://samskivert.github.com/gwt-maven-plugin/repository/org/codehaus/mojo/gwt-maven-plugin/2.3.0-2-playn/gwt-maven-plugin-2.3.0-2-playn.jar
Hopefully the gwt-maven-plugin maintainers will apply the patch I sent
them and we can go back to using the stock gwt-maven-plugin with the
next release.
brentryan
Oct 4, 2011, 3:44:54 PM10/4/11
to PlayN
Ya, I'm not sure yet either... I noticed that I could download the
artifact directly, but I can't get to it through my internal maven
repository proxy.
Here's the error I see in the logs of my internal nexus server:
2011-10-04 15:41:36 ERROR [tp-72609960-137] -
org.sonatype.nexus.proxy.maven.maven2.M2Repository - Got
RemoteStorageException in proxy repository "gwt-maven-plugin-
playn" [id=gwt-maven-plugin-playn] while retrieving remote artifact
"/.meta/repository-metadata.xml" from URL http://samskivert.github.com/gwt-maven-plugin/repository/,
this is 1 (re)try, cause: java.net.SocketTimeoutException: connect
timed out
2011-10-04 15:41:57 WARN [xy-2-thread-101] -
org.sonatype.nexus.proxy.maven.maven2.M2Repository - Remote peer of
proxy repository "gwt-maven-plugin-playn" (id=gwt-maven-plugin-playn)
threw a org.sonatype.nexus.proxy.RemoteAccessDeniedException
exception. Please set up authorization information for this
repository. - Cause(s): Forbidden
I even tried creating a github user/password and using that but it
still didn't like it... Usually I can add any remote repository to
nexus and it just works without issues... Maybe the remote repository
must be browsable for it to work...???
Thoughts?
On Oct 4, 3:26 pm, Michael Bayne <m...@samskivert.com> wrote:
artifact directly, but I can't get to it through my internal maven
repository proxy.
Here's the error I see in the logs of my internal nexus server:
2011-10-04 15:41:36 ERROR [tp-72609960-137] -
org.sonatype.nexus.proxy.maven.maven2.M2Repository - Got
RemoteStorageException in proxy repository "gwt-maven-plugin-
playn" [id=gwt-maven-plugin-playn] while retrieving remote artifact
"/.meta/repository-metadata.xml" from URL http://samskivert.github.com/gwt-maven-plugin/repository/,
this is 1 (re)try, cause: java.net.SocketTimeoutException: connect
timed out
2011-10-04 15:41:57 WARN [xy-2-thread-101] -
org.sonatype.nexus.proxy.maven.maven2.M2Repository - Remote peer of
proxy repository "gwt-maven-plugin-playn" (id=gwt-maven-plugin-playn)
threw a org.sonatype.nexus.proxy.RemoteAccessDeniedException
exception. Please set up authorization information for this
repository. - Cause(s): Forbidden
I even tried creating a github user/password and using that but it
still didn't like it... Usually I can add any remote repository to
nexus and it just works without issues... Maybe the remote repository
must be browsable for it to work...???
Thoughts?
On Oct 4, 3:26 pm, Michael Bayne <m...@samskivert.com> wrote:
> On Tue, Oct 4, 2011 at 12:18 PM, brentryan <brent.r...@gmail.com> wrote:
> > Can this maven repo be made public?
>
> >http://samskivert.github.com/gwt-maven-plugin/repository
>
> > I'm currently using an internal maven repository which needs to proxy
> > to the above repository, but it can't because this repo isn't public.
>
> What does that mean? It's as public as any other repository, in that
> you can access it from anywhere on the Internet. Is there some other
> public/non-public distinction that Maven makes?
>
> You can't get a directory listing, but the necessary files are there:
>
> http://samskivert.github.com/gwt-maven-plugin/repository/org/codehaus...http://samskivert.github.com/gwt-maven-plugin/repository/org/codehaus...
> > Can this maven repo be made public?
>
> >http://samskivert.github.com/gwt-maven-plugin/repository
>
> > I'm currently using an internal maven repository which needs to proxy
> > to the above repository, but it can't because this repo isn't public.
>
> What does that mean? It's as public as any other repository, in that
> you can access it from anywhere on the Internet. Is there some other
> public/non-public distinction that Maven makes?
>
> You can't get a directory listing, but the necessary files are there:
>
Michael Bayne
Oct 4, 2011, 3:49:07 PM10/4/11
to pl...@googlegroups.com
On Tue, Oct 4, 2011 at 12:44 PM, brentryan <brent...@gmail.com> wrote:
> Usually I can add any remote repository to
> nexus and it just works without issues... Maybe the remote repository
> must be browsable for it to work...???
> Usually I can add any remote repository to
> nexus and it just works without issues... Maybe the remote repository
> must be browsable for it to work...???
I don't know. I have no experience with Maven repository proxying.
You can just install that artifact into a local repository, or into
your proxying nexus repository for the time being.
brentryan
Oct 4, 2011, 4:06:05 PM10/4/11
to PlayN
I tried to add that jar file to my repo, but then I get this error:
[ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:
2.3.0-2-playn:compile (default) on project playn-hello-html: Execution
default of goal org.codehaus.mojo:gwt-maven-plugin:2.3.0-2-
playn:compile failed. NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.codehaus.mojo:gwt-maven-plugin:2.3.0-2-playn:compile
(default) on project playn-hello-html: Execution default of goal
org.codehaus.mojo:gwt-maven-plugin:2.3.0-2-playn:compile failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:
225)
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:537)
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.launchEnhanced(Launcher.java:
290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:
230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:
409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
352)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default of goal org.codehaus.mojo:gwt-maven-plugin:2.3.0-2-
playn:compile failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:
110)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:
209)
... 19 more
Caused by: java.lang.NullPointerException
at
org.codehaus.mojo.gwt.AbstractGwtMojo.getGwtUserJar(AbstractGwtMojo.java:
299)
at org.codehaus.mojo.gwt.shell.CompileMojo.compile(CompileMojo.java:
255)
at org.codehaus.mojo.gwt.shell.CompileMojo.doExecute(CompileMojo.java:
237)
at
org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo.execute(AbstractGwtShellMojo.java:
142)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:
101)
... 20 more
On Oct 4, 3:49 pm, Michael Bayne <m...@samskivert.com> wrote:
[ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:
2.3.0-2-playn:compile (default) on project playn-hello-html: Execution
default of goal org.codehaus.mojo:gwt-maven-plugin:2.3.0-2-
playn:compile failed. NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.codehaus.mojo:gwt-maven-plugin:2.3.0-2-playn:compile
(default) on project playn-hello-html: Execution default of goal
org.codehaus.mojo:gwt-maven-plugin:2.3.0-2-playn:compile failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:
225)
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:537)
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.launchEnhanced(Launcher.java:
290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:
230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:
409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
352)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default of goal org.codehaus.mojo:gwt-maven-plugin:2.3.0-2-
playn:compile failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:
110)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:
209)
... 19 more
Caused by: java.lang.NullPointerException
at
org.codehaus.mojo.gwt.AbstractGwtMojo.getGwtUserJar(AbstractGwtMojo.java:
299)
at org.codehaus.mojo.gwt.shell.CompileMojo.compile(CompileMojo.java:
255)
at org.codehaus.mojo.gwt.shell.CompileMojo.doExecute(CompileMojo.java:
237)
at
org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo.execute(AbstractGwtShellMojo.java:
142)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:
101)
... 20 more
On Oct 4, 3:49 pm, Michael Bayne <m...@samskivert.com> wrote:
brentryan
Oct 4, 2011, 4:13:59 PM10/4/11
to PlayN
I believe I figured it out. At least, I may have it working by adding
both the jar file and pom file to my maven proxy. The pom file for
your version of the plugin probably refers to some other dependencies
that differ from the defaults. Once I updated that then everything
was fine.
Thanks!
both the jar file and pom file to my maven proxy. The pom file for
your version of the plugin probably refers to some other dependencies
that differ from the defaults. Once I updated that then everything
was fine.
Thanks!
Reply all
Reply to author
Forward
0 new messages