sonatype-nexus-community / nexus-repository-p2 Goto Github PK
View Code? Open in Web Editor NEWV Eclipse, hella P2, much OSGi
License: Eclipse Public License 1.0
nexus-repository-p2's People
Contributors
Stargazers
Watchers
Forkers
mk100120 mgh87 afischer211 ruspl-afed ischindl laeubi hannjos matthiasbeyer trinhpham arboehme airaketa blacktiger gaybro8777 isabella232nexus-repository-p2's Issues
Update to use newer version of Nexus Repo
Thanks for creating an issue! Please fill out this form so we can be
sure to have all the information we need, and to minimize back and forth.
-
What are you trying to do?
Right now this plugin is based on Nexus Repo 3.8.0-02, we should update it! -
What feature or behavior is this required for?
Just ensures compatibility with newer versions of Nexus Repo, as some dependencies have changed (commons-compress, etc...) -
How could we solve this issue? (Not knowing is okay!)
Update thepom.xml,DockerfileandREADME.mdto the new versions, and as well test these changes against a newer version of Nexus Repo, updating any API calls that might have changed or been deprecated along the way -
Anything else?
Have fun!
Does not compile
Hi, I'm trying to build the plugin to test it with nexus3 (3.15.2-01), but it won't compile (backtrace below).
I'm not a Java guy and don't know whether I'm simply missing the obvious or whether it is a legitimate bug/error/misbehaviour.
- What are you trying to do?
Compile the plugin
- What feature or behavior is this required for?
To test the plugin with nexus 3.15.2-01
- How could we solve this issue? (Not knowing is okay!)
I don't know
- Anything else?
Run with maven -eX clean package:
[...]
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.299 s
[INFO] Finished at: 2019-03-14T18:09:33+01:00
[INFO] Final Memory: 63M/753M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on project nexus-repository-p2: There are test failures.
[ERROR]
[ERROR] Please refer to /home/soco/p2/nexus-repository-p2/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd /home/soco/p2/nexus-repository-p2 && /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xmx300M -XX:MaxDirectMemorySize=2G -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/soco/p2/nexus-repository-p2/target/surefire-reports -jar /home/soco/p2/nexus-repository-p2/target/surefire
/surefirebooter104369308177869763.jar /home/soco/p2/nexus-repository-p2/target/surefire 2019-03-14T18-09-33_182-jvmRun1 surefire5207152270256291511tmp surefire_01450174911470624684tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd /home/soco/p2/nexus-repository-p2 && /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xmx300M -XX:MaxDirectMemorySize=2G -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/soco/p2/nexus-repository-p2/target/surefire-reports -jar /home/soco/p2/nexus-repository-p2/target/surefire
/surefirebooter104369308177869763.jar /home/soco/p2/nexus-repository-p2/target/surefire 2019-03-14T18-09-33_182-jvmRun1 surefire5207152270256291511tmp surefire_01450174911470624684tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:679)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
[ERROR] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
[ERROR] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
[ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on project nexus-repository-p2: There are test failures.
Please refer to /home/soco/p2/nexus-repository-p2/target/surefire-reports for the individual test results.
Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Command was /bin/sh -c cd /home/soco/p2/nexus-repository-p2 && /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xmx300M -XX:MaxDirectMemorySize=2G -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/soco/p2/nexus-repository-p2/target/surefire-reports -jar /home/soco/p2/nexus-repository-p2/target/surefire/surefir
ebooter104369308177869763.jar /home/soco/p2/nexus-repository-p2/target/surefire 2019-03-14T18-09-33_182-jvmRun1 surefire5207152270256291511tmp surefire_01450174911470624684tmp
Error occurred in starting fork, check output in log
Process Exit Code: 1
org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Command was /bin/sh -c cd /home/soco/p2/nexus-repository-p2 && /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xmx300M -XX:MaxDirectMemorySize=2G -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/soco/p2/nexus-repository-p2/target/surefire-reports -jar /home/soco/p2/nexus-repository-p2/target/surefire/surefir
ebooter104369308177869763.jar /home/soco/p2/nexus-repository-p2/target/surefire 2019-03-14T18-09-33_182-jvmRun1 surefire5207152270256291511tmp surefire_01450174911470624684tmp
Error occurred in starting fork, check output in log
Process Exit Code: 1
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:679)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
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:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
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:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: There are test failures.
Please refer to /home/soco/p2/nexus-repository-p2/target/surefire-reports for the individual test results.
Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Command was /bin/sh -c cd /home/soco/p2/nexus-repository-p2 && /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xmx300M -XX:MaxDirectMemorySize=2G -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/soco/p2/nexus-repository-p2/target/surefire-reports -jar /home/soco/p2/nexus-repository-p2/target/surefire/surefirebooter104369308177869763.jar /home/soco/p2/nexus-repository-p2/target/surefire 2019-03-14T18-09-33_182-jvmRun1 surefire5207152270256291511tmp surefire_01450174911470624684tmp
Error occurred in starting fork, check output in log
Process Exit Code: 1
org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Command was /bin/sh -c cd /home/soco/p2/nexus-repository-p2 && /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xmx300M -XX:MaxDirectMemorySize=2G -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/soco/p2/nexus-repository-p2/target/surefire-reports -jar /home/soco/p2/nexus-repository-p2/target/surefire/surefirebooter104369308177869763.jar /home/soco/p2/nexus-repository-p2/target/surefire 2019-03-14T18-09-33_182-jvmRun1 surefire5207152270256291511tmp surefire_01450174911470624684tmp
Error occurred in starting fork, check output in log
Process Exit Code: 1
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:679)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
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:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
at org.apache.maven.plugin.surefire.SurefireHelper.throwException(SurefireHelper.java:199)
at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:98)
at org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:334)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:937)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Command was /bin/sh -c cd /home/soco/p2/nexus-repository-p2 && /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xmx300M -XX:MaxDirectMemorySize=2G -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/soco/p2/nexus-repository-p2/target/surefire-reports -jar /home/soco/p2/nexus-repository-p2/target/surefire/surefirebooter104369308177869763.jar /home/soco/p2/nexus-repository-p2/target/surefire 2019-03-14T18-09-33_182-jvmRun1 surefire5207152270256291511tmp surefire_01450174911470624684tmp
Error occurred in starting fork, check output in log
Process Exit Code: 1
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:679)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
... 23 more
[ERROR]
[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/MojoExecutionException
"(most) Permanent Install" doesn't work
We are trying to do the "(most) Permanent Install" from the Readme.md to our Nexus 3.10.0-04.
We've copied the jar to the plugin-dir and inserted 'nexus-repository-p2' in '/opt/nexus-3.10.0-04/system/org/sonatype/nexus/assemblies/nexus-core-feature/3.10.0-04/nexus-core-feature-3.x.y-features.xml' (please look at attached nexus-core-feature-3.10.0-04-features.xml.txt).
The Server doesn't start (please look at attached nexus.log)
Do you have any hint?
Bug with proxy repo
Hi,
We would like to know why we can't download the artifacts even when they are cached.
It is pointing to Nexus 2 which we turned it off days ago.
We understand the it is not possible to download new artifacts but the artifacts that are already in cache should work right? I can see them in the browse.
Thanks!
This is from Sonatype ticket:
" Cassandra Seney Yesterday at 14:58
Hi Rafael,
According to the nexus log the content is not in cache and the 502 response occurred attempting to retrieve it from the remote.
2019-08-20 20:16:48,452+0000 WARN [qtp1301073200-929261] dddp1lc9a001 rxv112 org.sonatype.nexus.repository.p2.internal.proxy.P2ProxyFacetImpl - Exception org.sonatype.nexus.repository.proxy.ProxyServiceException: HTTP/1.1 502 Bad Gateway checking remote for update, proxy repo xtext-2.4.3-p2 failed to fetch plugins/org.eclipse.osgi.services_3.3.100.v20130513-1956.jar with status line HTTP/1.1 502 Bad Gateway, content not in cache.
Do you see this jar file when you browse the xtext-2.4.3-p2 proxy repository?
Thanks,
Cassie"
Do not shrink artifacts.xml during processsing
java.vm.version=25.172-b11
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.vendor=Oracle Corporation
java.vm.specification.version=1.8
java.vm.vendor=Oracle Corporation
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "dos"
After creating p2 proxy to "http://download.eclipse.org/releases/mars/" and attempt to use it in the local maven build it fails with error like:
[Fatal Error] :112850:13: XML document structures must start and end within the same entity.
[ERROR] Internal error: java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at https://.../repository/eclipse-mars. Unable to read repository at file:/C:/Users/.../.m2/repository/.cache/tycho/p2-repository-metadata/2116131570. XML document structures must start and end within the same entity. -> [Help 1]
The mentioned file "2116131570" appears to be zip with 1 file named "2116131570" inside it.
The inner file "2116131570" was an XML that ends with
<property name="format" value="packed"></property>
<pro
So, it was shrinked somethere during processing.
The solution is to work with XML processing more carefully, thanks to @afischer211 who found it. PR is following.
DepShield encountered errors while building your project
The project could not be analyzed because of build errors. Please review the error messages here. Another build will be scheduled when a change to a manifest file* occurs. If the build is successful this issue will be closed, otherwise the error message will be updated.
This is an automated GitHub Issue created by Sonatype DepShield. GitHub Apps, including DepShield, can be managed from the Developer settings of the repository administrators.
* Supported manifest files are: pom.xml, package.json, package-lock.json, npm-shrinkwrap.json, Cargo.lock, Cargo.toml, main.rs, lib.rs, build.gradle, build.gradle.kts, settings.gradle, settings.gradle.kts, gradle.properties, gradle-wrapper.properties, go.mod, go.sum
P2 plugin logs warnings on boot
Recipes should use the helper method addBrowseUnsupportedRoute(builder) which was added back in 3.1.0 (sonatype/nexus-internal#976) rather than attempt to inject the handler directly and manually add the route.
This came up before with the Go format (sonatype/nexus-internal#4354) and it was noted that most of the plugins under https://github.com/sonatype-nexus-community/ needed a similar fix. Unfortunately the incorrect approach of injecting the handler directly continues to be copy-pasted around :/
This is the warning that appears at the moment:
2020-01-27 12:55:10,514-0800 WARN [FelixStartLevel] *SYSTEM com.google.inject.spi.InjectionPoint -
Method: public void org.sonatype.nexus.repository.p2.internal.proxy.P2ProxyRecipe.setBrowseUnsupportedHandler(org.sonatype.nexus.repository.view.handlers.BrowseUnsupportedHandler)
is not annotated with @Inject but is overriding a method that is annotated with @javax.inject.Inject.
Because it is not annotated with @Inject, the method will not be injected. To fix this, annotate the method with @Inject.
2020-01-27 12:55:10,547-0800 WARN [FelixStartLevel] *SYSTEM com.google.inject.spi.InjectionPoint -
Method: public void org.sonatype.nexus.repository.p2.internal.proxy.P2ProxyRecipe.setBrowseUnsupportedHandler(org.sonatype.nexus.repository.view.handlers.BrowseUnsupportedHandler)
is not annotated with @Inject but is overriding a method that is annotated with @javax.inject.Inject.
Because it is not annotated with @Inject, the method will not be injected. To fix this, annotate the method with @Inject.
DepShield encountered errors while building your project
The project could not be analyzed because of build errors. Please review the error messages here. Another build will be scheduled within 24 hours. If the build is successful this issue will be closed, otherwise the error message will be updated.
This is an automated GitHub Issue created by Sonatype DepShield. GitHub Apps, including DepShield, can be managed from the Developer settings of the repository administrators.
Support repository mappings
p2 artifact repositories contain blocks which indicate how to construct URLs to request artifacts, e.g.
<mappings size='5'>
<rule filter='(& (classifier=osgi.bundle) (format=packed))' output='${repoUrl}/plugins/${id}_${version}.jar.pack.gz'/>
<rule filter='(& (classifier=osgi.bundle))' output='${repoUrl}/plugins/${id}_${version}.jar'/>
<rule filter='(& (classifier=binary))' output='${repoUrl}/binary/${id}_${version}'/>
<rule filter='(& (classifier=org.eclipse.update.feature) (format=packed))' output='${repoUrl}/features/${id}_${version}.jar.pack.gz'/>
<rule filter='(& (classifier=org.eclipse.update.feature))' output='${repoUrl}/features/${id}_${version}.jar'/>
</mappings>
These could map artifacts to arbitrary domains or relative paths outside of of the Nexus proxied repository
Nexus tries to connect to remote even if "Blocked" option checked
Thanks for creating an issue! Please fill out this form so we can be
sure to have all the information we need, and to minimize back and forth.
- What are you trying to do?
I am trying to prevent Nexus from contacting a remote server after the local cache has been primed. I hence check Blocked ("Block outbound connections on the repository") and uncheck Auto blocking enabled.
Nevertheless, the log is full of entries like the following occurring in rapid succession, i.e., every few seconds:
2019-11-25 11:05:12,073+0100 INFO [qtp275201327-37226] *UNKNOWN org.apache.http.impl.execchain.RetryExec - I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://download.eclipse.org:443: The target server failed to respond
2019-11-25 11:05:12,074+0100 INFO [qtp275201327-37226] *UNKNOWN org.apache.http.impl.execchain.RetryExec - Retrying request to {s}->https://download.eclipse.org:443
From the log, I unfortunately cannot tell which specific repository on download.eclipse.org was queried.
- What feature or behavior is this required for?
Isolation from an upstream server that either faces regular outages or blocks clients (like Nexus) that use the service too much.
- Anything else?
Other options I tried, in various combinations:
- Setting maximum component age to -1
- Setting maximum component age to a large value (10080, i.e., 1 week)
- Setting maximum metadata age to -1(not sure whether this is a valid value)
- Setting maximum metadata age to a large value (10080, i.e., 1 week)
Documentation for using this plugin with Nexus 3
- What are you trying to do?
Learn about the P2 plugin for Nexus Repository Manager 3
The link under the "Using p2 With Nexus Repository Manager 3" heading in the README.md is broken. But when I go to the formats section of the Nexus 3 documentation I do find a "P2" format but it points back to this GitHub repository. Is there any documentation for installing and using this P2 plugin for Nexus 3 in addition to what's in the README.md in this repo?
P2 Group functionality
Thanks for creating an issue! Please fill out this form so we can be
sure to have all the information we need, and to minimize back and forth.
- What are you trying to do?
Implement Group functionality! Allow people to group together a bunch of proxies so they can use one URL, which would simplify Eclipse setup for sure.
- What feature or behavior is this required for?
Group repositories.
- How could we solve this issue? (Not knowing is okay!)
A good first start would be to look at how we did this in R (since it's Nexus Repository 3 based), and then take a gander at how we did it in Nexus Repository 2, as concepts etc... can be inspired from that.
- Anything else?
I'll personally send anyone who does this all of my United Miles.
Handle mirror.xml files
Thanks for creating an issue! Please fill out this form so we can be
sure to have all the information we need, and to minimize back and forth.
- What are you trying to do?
In some artifacts.xml files you'll see something similar to this:
<repository name='Eclipse Project Repository for Oxygen' type='org.eclipse.equinox.p2.artifact.repository.simpleRepository' version='1.0.0'>
<properties size='4'>
<property name='publishPackFilesAsSiblings' value='true'/>
<property name='p2.compressed' value='true'/>
<property name='p2.timestamp' value='1498225223662'/>
<property name='p2.mirrorsURL' value='http://www.eclipse.org/downloads/download.php?format=xml&file=/eclipse/updates/4.7/R-4.7-201706120950'/>
</properties>
The p2.mirrorsURL gives a list of mirrors that are valid for downloading Eclipse packages.
What we want to do is write some code that if someone has configured Nexus Repository to proxy the actual downloads.eclipse.org URL (or really any URL that has a p2.mirrorsURL configured), to use the list of mirrors to do the actual downloads rather than the Eclipse foundation URL.
- What feature or behavior is this required for?
If people misconfigure Nexus Repository to use the downloads.eclipse.org, it can result in the UA being blacklisted, as I believe this has happened in the past.
- How could we solve this issue? (Not knowing is okay!)
You could take a look at how this was handled in Nexus Repository 2 for inspiration here
Composite repo refs to composite: Issues on some P2 update sites (Orbit & Eclipse)
Hello ,
I am using
Sonatype Nexus Repository Manager
OSS 3.20.1-01 and P2 plugin.
At the current , we are using CI Maven/Jenkins and Eclipse RCP.
All is working fine by using external P2 sites
Just some P2 sites with Nexus
Example
i am trying to create a P2 repository (proxy) Version 0.0.3 for these 2 eclipse update site
http://download.eclipse.org/ecp/releases/releases_123/
https://download.eclipse.org/tools/orbit/downloads/drops/R20170307180635/
http://download.eclipse.org/tm/terminal/marketplace/
Is it solved in 1.0.0 version ?
Best regards
Erwan
What's the difference to the built in "raw poxy"
At our company we struggle heavy with build/Ci of an Maven based Eclipse RCP application build. At the moment we use https://github.com/reficio/p2-maven-plugin to generate own P2 sites with our own bundles for that build. But this is not the best solution: We can only rebuilt whole sites which takes lot of time.
So we decided to look at this Plugin, but after installing it and read the docs it looks like it only provides the capability of mirroring an existing P2 site. We do this already with the Nexus built in "raw proxy". So my questions:
- What is the difference of the P2 proxy to that Raw proxy?
- Is there a plan/idea to extend this Plugin to host a full fledged P2 repo in Nexus (whatever that means)?
Handle Composite Sites with Absolute Paths in their XML files
Thanks for creating an issue! Please fill out this form so we can be
sure to have all the information we need, and to minimize back and forth.
- What are you trying to do?
The following files:
compositeArtifacts.jar|xmlcompositeContent.jar|xml
Can have absolute paths embedded in them, which would bypass Nexus Repository in the P2 client. Likely these should be rewritten to relative paths, and potentially turned into Proxy Repositories as well (since they will be external to the proxy you've created)
- What feature or behavior is this required for?
Fully supporting Composite Repositories
- How could we solve this issue? (Not knowing is okay!)
I think we would need to rewrite these xml files (the jar file is just a compressed xml file in reality), and potentially add a new step to P2 proxy creation that will take the absolute paths and use them to create new Proxy Repositories.
- Anything else?
Have fun :)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.