chore: modify POMs to address changes due to migration

minherz · minherz · commit 8e6abdcbd796 · 2022-11-10T02:51:44.000Z
diff --git a/errorreporting/pom.xml b/errorreporting/pom.xml
@@ -2,11 +2,11 @@
 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
   <modelVersion>4.0.0</modelVersion>
   <groupId>com.google.cloud</groupId>
-  <artifactId>google-cloud-clouderrorreporting-samples</artifactId>
+  <artifactId>java-docs-samples-errorreporting</artifactId>
   <version>0.0.1-SNAPSHOT</version><!-- This artifact should not be released -->
   <packaging>pom</packaging>
   <name>Google Cloud Error Reporting Samples Parent</name>
-  <url>https://github.com/googleapis/java-errorreporting</url>
+  <url>https://github.com/GoogleCloudPlatform/java-docs-samples/errorreporting</url>
   <description>
     Java idiomatic client for Google Cloud Platform services.
   </description>
@@ -28,8 +28,6 @@
   </properties>
 
   <modules>
-    <module>install-without-bom</module>
-    <module>snapshot</module>
     <module>snippets</module>
   </modules>
 
diff --git a/errorreporting/snippets/pom.xml b/errorreporting/snippets/pom.xml
@@ -2,10 +2,10 @@
 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
   <modelVersion>4.0.0</modelVersion>
   <groupId>com.google.cloud</groupId>
-  <artifactId>clouderrorreporting-snippets</artifactId>
+  <artifactId>java-docs-samples-errorreporting-snippets</artifactId>
   <packaging>jar</packaging>
-  <name>Google Cloud Error Reporting Snippets</name>
-  <url>https://github.com/googleapis/java-errorreporting</url>
+  <name>Google Cloud Error Reporting Samples Parent</name>
+  <url>https://github.com/GoogleCloudPlatform/java-docs-samples/errorreporting</url>
 
   <!--
     The parent pom defines common style checks and testing strategies for our samples.
