Plugin compile issue - Failure to find org.apache.xmlgraphics:batik:pom:1.9

Confluence Development Confluence Server
, , ,
1

The Altassian Maven compile process seems to be requesting - org.apache.xmlgraphics:batik:pom:1.9. But it doesn’t look like this actually exists. 1.9.1 does, but 1.9 does not. See here: xmlgraphics/batik.

This would seem to be an Atlassian SDK config issue, because my plugin POM isn’t requesting this. Confluence 6.5.1, SDK 6.3.4.

POM config:

	<properties>
		<confluence.version>6.5.1</confluence.version>
		<confluence.data.version>6.5.0</confluence.data.version>
		<amps.version>6.3.6</amps.version>
        <plugin.testrunner.version>1.2.3</plugin.testrunner.version>
        <atlassian.spring.scanner.version>1.2.13</atlassian.spring.scanner.version>
        <!-- This key is used to keep the consistency between the key in atlassian-plugin.xml and the key to generate bundle. -->
        <atlassian.plugin.key>${project.groupId}.${project.artifactId}</atlassian.plugin.key>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	</properties>

Error received:

[ERROR] Failed to execute goal on project WikiCustomPlugin: Could not resolve dependencies for project com.appfusions.confluence.addons.att:WikiCustomPlugin:atlassian-plugin:6.5.1.0: Failed to collect dependencies at com.atlassian.confluence:confluence:jar:6.5.1 -> org.apache.xmlgraphics:batik-css:jar:1.9 -> org.apache.xmlgraphics:batik-ext:jar:1.9: Failed to read artifact descriptor for org.apache.xmlgraphics:batik-ext:jar:1.9: Failure to find org.apache.xmlgraphics:batik:pom:1.9 in http://repo.jenkins-ci.org/public/ was cached in the local repository, resolution will not be reattempted until the update interval of repo.jenkins-ci.org has elapsed or updates are forced -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project WikiCustomPlugin: Could not resolve dependencies for project com.appfusions.confluence.addons.att:WikiCustomPlugin:atlassian-plugin:6.5.1.0: Failed to collect dependencies at com.atlassian.confluence:confluence:jar:6.5.1 -> org.apache.xmlgraphics:batik-css:jar:1.9 -> org.apache.xmlgraphics:batik-ext:jar:1.9
	at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:221)

http://repo.jenkins-ci.org/public/org/apache/xmlgraphics/batik/

2

@mpaisley, this might be something you could help out with.

4

Guys, can you please share what was your resolution, and what exactly does “had to do with new Atlassian repository settings” mean. I recently downloaded Atlassian SDK 3.6.6 and trying to build a bare bone Confluence plug-in I receive same error, that it cannot resolve batik-1.9, which I checked and can only see version 1.9.1.

5

1.9 seems completely wrong. I managed to hack it by first excluding both batik-css and batik-ext from the com.atlassian.confluence:confluence dependency, and then adding those 2 with specified version of 1.9.1 right below it in the generated pom.xml

    <dependency>
        <groupId>com.atlassian.confluence</groupId>
        <artifactId>confluence</artifactId>
        <version>${confluence.version}</version>
        <scope>provided</scope>
        <exclusions>
        	<exclusion>
        		<groupId>org.apache.xmlgraphics</groupId>
				<artifactId>batik-css</artifactId>
        	</exclusion>
        	<exclusion>
        		<groupId>org.apache.xmlgraphics</groupId>
				<artifactId>batik-ext</artifactId>
        	</exclusion>
        </exclusions>
    </dependency>
    <dependency>
        <groupId>org.apache.xmlgraphics</groupId>
        <artifactId>batik-css</artifactId>
        <version>1.9.1</version>
        <scope>provided</scope>
    </dependency>
    <dependency>
        <groupId>org.apache.xmlgraphics</groupId>
        <artifactId>batik-ext</artifactId>
        <version>1.9.1</version>
        <scope>provided</scope>
    </dependency>
7

Hey Steve, deleting your ~/.m2/repository every once in a while is a good idea. Also reboot your machine if things are still weird. Maven can be horrid and temperamental.

Turn it off and on again is always a good sanity check :+1: :+1:

8

korcdmi - So I’m working on lease rolling my workstation and I started with 6.3.6 of the Atlassian SDK, and I expected it to “work”. BUT - it does not. just as you expressed in your comment above. Its back to that evil batik-1.9 error. I remove 6.3.6, and installed 6.3.4 - and it compiles properly. You might have to do the same. (I also deleted my repository - its the 3rd time this morning)

@pvandevoorde and @mpaisley – What is going on? There needs to be a real fix for this, not the hack that I’m explaining.

  • Is my hack even the right thing to do?
  • Why doesn’t the 6.3.6 SDK build/compile my Confluence plugin? I’m using Confluence 6.6.1 and 6.6.2, and 6.3.6 is the latest SDK. Why does it want a package that is not publicly available?
  • How do we get it to retrieve the package that Atlassian seems to want to use?
  • Maybe the 6.3.6 SDK is not to be used for Confluence 6.5 or 6.6? But 6.3.4 doesn’t list 6.5 or 6.6 either.

A push in the right direction would be helpful. We cannot be the only two people facing this issue.

Windows 7 Pro 64 bit, Eclipse 4.6, JDK 1.8.0._152

9

And - I’m back to not being able to compile/build the 2nd plugin. So I do NOT have a workable solution for this.

Any ideas? Help?

10

Hey!
Can you please tell me exactly the error you’re seeing when you attempt to compile? When you say compile what is the command you’re actually running?
Cheers,
Melissa

12
  • Since I cannot upload attachments - even though its let me do it once - because I’m new?? – settings.xml as txt not pdf - which has worked on my previous workstation:
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
	<localRepository />
	<interactiveMode />
	<usePluginRegistry />
	<offline />
	<pluginGroups>
		<pluginGroup>org.jenkins-ci.tools</pluginGroup>
        <pluginGroup>org.sonatype.plugins</pluginGroup>
	</pluginGroups>

<!-- stolen from http://wiki.web.att.com/display/SED/Maven+Configuration
  <pluginGroups>
    <pluginGroup>org.mortbay.jetty</pluginGroup>
    <pluginGroup>com.att.r3.plugins</pluginGroup>
  </pluginGroups>
 -->

	<servers>
		<server>
			<id>tspace snapshots</id>
			<username>admin</username>
			<password>admin123</password>
		</server>
		<server>
			<id>tspace releases</id>
			<username>admin</username>
			<password>admin123</password>
		</server>
	</servers>

	<proxies>
		<proxy>
          <id>att</id>
		  <active>true</active>
		  <protocol>http</protocol>
		  <host>one.proxy.att.com</host>
		  <port>8080</port>
		</proxy>
    </proxies>
  
  <mirrors>
    <mirror>
      <id>ATT</id>
      <name>ATT Internal Mirror of Maven Central</name>
      <url>http://mavencentral.it.att.com:8084/nexus/content/repositories/central</url>
      <mirrorOf>central</mirrorOf>
    </mirror>
  </mirrors>
  
  <profiles>
<!-- tSpace repo - cannot be used for Atlassian plugin compiling. 
 -->
		<profile>
			<id>tspace Repo</id>
			<repositories>
				<repository>
					<id>tspace thirdparty</id>
					<url>https://tspace3.dev.att.com/nexus/content/repositories/thirdparty/</url>
					<snapshots>
						<enabled>true</enabled>
						<updatePolicy>daily</updatePolicy>
						<checksumPolicy>warn</checksumPolicy>
					</snapshots>
					<releases>
						<enabled>true</enabled>
						<checksumPolicy>warn</checksumPolicy>
					</releases>
				</repository>
				<repository>
					<id>tspace snapshots</id>
					<url>https://tspace3.dev.att.com/nexus/content/repositories/snapshots/</url>
					<snapshots>
						<enabled>true</enabled>
						<updatePolicy>daily</updatePolicy>
						<checksumPolicy>warn</checksumPolicy>
					</snapshots>
					<releases>
						<enabled>true</enabled>
						<checksumPolicy>warn</checksumPolicy>
					</releases>
				</repository>
				<repository>
					<id>tspace releases</id>
					<url>https://tspace3.dev.att.com/nexus/content/repositories/releases/</url>
					<releases>
						<enabled>true</enabled>
						<checksumPolicy>warn</checksumPolicy>
					</releases>
				</repository>
			</repositories>

		</profile>

		<profile> 
			<id>tspace Repo2</id> 
			<repositories> 
				<repository> 
					<id>tspace2 thirdparty</id> 
					<url>http://tspace3.dev.att.com:8081/nexus/content/repositories/thirdparty/</url> 
					<snapshots> 
						<enabled>true</enabled> 
						<updatePolicy>daily</updatePolicy> 
						<checksumPolicy>warn</checksumPolicy> 
					</snapshots> 
					<releases> 
						<enabled>true</enabled> 
						<checksumPolicy>warn</checksumPolicy> 
					</releases> 
				</repository> 
				<repository> 
					<id>tspace2 central</id> 
					<url>http://tspace3.dev.att.com:8081/nexus/content/repositories/central/</url> 
					<snapshots> 
						<enabled>true</enabled> 
						<updatePolicy>daily</updatePolicy> 
						<checksumPolicy>warn</checksumPolicy> 
					</snapshots> 
					<releases> 
						<enabled>true</enabled> 
						<checksumPolicy>warn</checksumPolicy> 
					</releases> 
				</repository> 
				<repository> 
					<id>tspace snapshots</id> 
					<url>http://tspace3.dev.att.com:8081/nexus/content/repositories/snapshots/</url> 
					<snapshots> 
						<enabled>true</enabled> 
						<updatePolicy>daily</updatePolicy> 
						<checksumPolicy>warn</checksumPolicy> 
					</snapshots> 
					<releases> 
						<enabled>true</enabled> 
						<checksumPolicy>warn</checksumPolicy> 
					</releases> 
				</repository> 
				<repository> 
					<id>tspace releases</id> 
					<url>http://tspace3.dev.att.com:8081/nexus/content/repositories/releases/</url> 
					<releases> 
						<enabled>true</enabled> 
						<checksumPolicy>warn</checksumPolicy> 
					</releases> 
				</repository> 
			</repositories> 
		</profile>
		
		<profile>
			<id>atlassian-repositories</id>
			<repositories>
	<!--
				<repository>
					<id>atlassian-proxy</id>
					<name>Atlassian Maven 2 Proxy</name>
					<url>https://m2proxy.atlassian.com/repository/public</url>
				</repository>
				<repository>
					<id>atlassian-m1-repository</id>
					<name>Atlassian Maven 1.x Repository</name>
					<url>https://maven.atlassian.com/repository/m1/</url>
				</repository>
				<repository>
					<id>atlassian-public</id>
					<url>https://maven.atlassian.com/repository/public</url>
					<snapshots>
						<enabled>true</enabled>
						<updatePolicy>never</updatePolicy>
						<checksumPolicy>warn</checksumPolicy>
					</snapshots>
					<releases>
						<enabled>true</enabled>
						<checksumPolicy>warn</checksumPolicy>
					</releases>
				</repository>
	-->
				<repository>
				  <id>atlassian-public</id>
				  <url>https://maven.atlassian.com/repository/public</url>
				  <snapshots>
					<enabled>true</enabled>
					<updatePolicy>never</updatePolicy>
					<checksumPolicy>warn</checksumPolicy>
				  </snapshots>
				  <releases>
					<enabled>true</enabled>
					<checksumPolicy>warn</checksumPolicy>
				  </releases>
				</repository>
			   <repository>
				 <id>atlassian-plugin-sdk</id>
				  <url>file://${env.ATLAS_HOME}/repository</url>
				  <snapshots>
					<enabled>true</enabled>
				  </snapshots>
				  <releases>
					<enabled>true</enabled>
					<checksumPolicy>warn</checksumPolicy>
				  </releases>
				</repository>

			</repositories>
			<pluginRepositories>
			
				<pluginRepository>
				  <id>atlassian-public</id>
				  <url>https://maven.atlassian.com/repository/public</url>
				  <releases>
					<enabled>true</enabled>
					<checksumPolicy>warn</checksumPolicy>
				  </releases>
				  <snapshots>
					<updatePolicy>never</updatePolicy>
					<checksumPolicy>warn</checksumPolicy>
				  </snapshots>
				</pluginRepository>
				<pluginRepository>
				  <id>atlassian-plugin-sdk</id>
				  <url>file://${env.ATLAS_HOME}/repository</url>
				  <releases>
					<enabled>true</enabled>
					<checksumPolicy>warn</checksumPolicy>
				  </releases>
				  <snapshots>
					<enabled>true</enabled>
				  </snapshots>
				</pluginRepository>

		<!--	
				<pluginRepository>
					<id>atlassian-proxy</id>
					<name>Atlassian Maven 2 Proxy</name>
					<url>https://m2proxy.atlassian.com/repository/public</url>
				</pluginRepository>
		-->
			</pluginRepositories>
			  <properties>
				<downloadSources>true</downloadSources>
				<downloadJavadocs>true</downloadJavadocs>
			  </properties>
		</profile>
		<profile>
			<id>jenkins</id>
			<activation>
				<activeByDefault>true</activeByDefault>
			</activation>
			<repositories>
				<repository>
					<id>repo.jenkins-ci.org</id>
					<url>http://repo.jenkins-ci.org/public/</url>
				</repository>
			</repositories>
			<pluginRepositories>
				<pluginRepository>
					<id>repo.jenkins-ci.org</id>
					<url>http://repo.jenkins-ci.org/public/</url>
				</pluginRepository>
			</pluginRepositories>
		</profile>

  <!-- repositories to compile the Atlassian plugin 
      <profile>
            <id>atlassian-repositories</id>
            <repositories>
                <repository>
                    <id>atlassian-proxy</id>
                    <name>Atlassian Maven 2 Proxy</name>
                    <url>http://mavencentral-alt.it.att.com:8084/nexus/content/repositories/atlassian/</url>
                </repository>
                <repository>
                    <id>atlassian-m1-repository</id>
                    <name>Atlassian Maven 1.x Repository</name>
                    <url>http://mavencentral-alt.it.att.com:8084/nexus/content/repositories/atlassian/</url>
                </repository>
                <repository>
                    <id>atlassian-public</id>
                    <url>http://mavencentral-alt.it.att.com:8084/nexus/content/repositories/atlassian/</url>
                    <snapshots>
                        <enabled>true</enabled>
                        <updatePolicy>never</updatePolicy>
                        <checksumPolicy>warn</checksumPolicy>
                    </snapshots>
                    <releases>
                        <enabled>true</enabled>
                        <checksumPolicy>warn</checksumPolicy>
                    </releases>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>atlassian-proxy</id>
                    <name>Atlassian Maven 2 Proxy</name>
                    <url>http://mavencentral-alt.it.att.com:8084/nexus/content/repositories/atlassian/</url>
                </pluginRepository>
            </pluginRepositories>
        </profile>
  -->
 
  </profiles>

	<activeProfiles>
	    <!-- comment out if compiling wiki plugin.
	     -->
		<activeProfile>tspace Repo</activeProfile>
		<activeProfile>tspace Repo2</activeProfile>
		<!-- Comment out with non-plugin compiling.
		 -->
		<activeProfile>atlassian-repositories</activeProfile>
		<activeProfile>jenkins</activeProfile>
	</activeProfiles>

</settings>

This is the eclipse logfile:

[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] 
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building ATT Customizations Plugin for Confluence 6.6.2 6.6.2.0
[INFO] ------------------------------------------------------------------------
[INFO] Downloading: file://C:\Users\sh4990\tSpace\atlassian-plugin-sdk-6.3.4/repository/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
[INFO] Downloading: https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
[INFO] Downloading: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
[INFO] Downloaded: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml (812 B at 1.8 KB/sec)
[INFO] Downloaded: https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml (812 B at 0.9 KB/sec)
[INFO] Downloading: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-compiler-plugin/maven-metadata.xml
[INFO] Downloading: https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-compiler-plugin/maven-metadata.xml
[INFO] Downloading: file://C:\Users\sh4990\tSpace\atlassian-plugin-sdk-6.3.4/repository/org/apache/maven/plugins/maven-compiler-plugin/maven-metadata.xml
[INFO] Downloaded: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-compiler-plugin/maven-metadata.xml (2 KB at 4.4 KB/sec)
[INFO] Downloaded: https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-compiler-plugin/maven-metadata.xml (2 KB at 4.0 KB/sec)
[INFO] Downloading: https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-install-plugin/maven-metadata.xml
[INFO] Downloading: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-install-plugin/maven-metadata.xml
[INFO] Downloading: file://C:\Users\sh4990\tSpace\atlassian-plugin-sdk-6.3.4/repository/org/apache/maven/plugins/maven-install-plugin/maven-metadata.xml
[INFO] Downloaded: https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-install-plugin/maven-metadata.xml (623 B at 3.1 KB/sec)
[INFO] Downloaded: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-install-plugin/maven-metadata.xml (623 B at 2.5 KB/sec)
[INFO] Downloading: file://C:\Users\sh4990\tSpace\atlassian-plugin-sdk-6.3.4/repository/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
[INFO] Downloading: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
[INFO] Downloading: https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
[INFO] Downloaded: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml (709 B at 3.2 KB/sec)
[INFO] Downloaded: https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml (709 B at 3.1 KB/sec)
[INFO] Downloading: https://maven.atlassian.com/repository/public/org/apache/xmlgraphics/batik/1.9/batik-1.9.pom
[INFO] Downloading: file://C:\Users\sh4990\tSpace\atlassian-plugin-sdk-6.3.4/repository/org/apache/xmlgraphics/batik/1.9/batik-1.9.pom
[INFO] Downloading: http://repo.jenkins-ci.org/public/org/apache/xmlgraphics/batik/1.9/batik-1.9.pom
[INFO] Downloading: http://tspace3.dev.att.com:8081/nexus/content/repositories/thirdparty/org/apache/xmlgraphics/batik/1.9/batik-1.9.pom
[INFO] Downloading: http://tspace3.dev.att.com:8081/nexus/content/repositories/central/org/apache/xmlgraphics/batik/1.9/batik-1.9.pom
[INFO] Downloading: http://tspace3.dev.att.com:8081/nexus/content/repositories/snapshots/org/apache/xmlgraphics/batik/1.9/batik-1.9.pom
[INFO] Downloading: http://tspace3.dev.att.com:8081/nexus/content/repositories/releases/org/apache/xmlgraphics/batik/1.9/batik-1.9.pom
[INFO] Downloading: https://tspace3.dev.att.com/nexus/content/repositories/thirdparty/org/apache/xmlgraphics/batik/1.9/batik-1.9.pom
[INFO] Downloading: http://mavencentral.it.att.com:8084/nexus/content/repositories/central/org/apache/xmlgraphics/batik/1.9/batik-1.9.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9.285 s
[INFO] Finished at: 2018-02-02T07:04:19-06:00
[INFO] Final Memory: 30M/422M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project WikiCustomPlugin: Could not resolve dependencies for project com.appfusions.confluence.addons.att:WikiCustomPlugin:atlassian-plugin:6.6.2.0: Failed to collect dependencies at com.atlassian.confluence:confluence:jar:6.5.1 -> org.apache.xmlgraphics:batik-css:jar:1.9 -> org.apache.xmlgraphics:batik-ext:jar:1.9: Failed to read artifact descriptor for org.apache.xmlgraphics:batik-ext:jar:1.9: Could not find artifact org.apache.xmlgraphics:batik:pom:1.9 in atlassian-public (https://maven.atlassian.com/repository/public) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project WikiCustomPlugin: Could not resolve dependencies for project com.appfusions.confluence.addons.att:WikiCustomPlugin:atlassian-plugin:6.6.2.0: Failed to collect dependencies at com.atlassian.confluence:confluence:jar:6.5.1 -> org.apache.xmlgraphics:batik-css:jar:1.9 -> org.apache.xmlgraphics:batik-ext:jar:1.9
	at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)
	at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
	at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
	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:108)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
	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.project.DependencyResolutionException: Could not resolve dependencies for project com.appfusions.confluence.addons.att:WikiCustomPlugin:atlassian-plugin:6.6.2.0: Failed to collect dependencies at com.atlassian.confluence:confluence:jar:6.5.1 -> org.apache.xmlgraphics:batik-css:jar:1.9 -> org.apache.xmlgraphics:batik-ext:jar:1.9
	at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:167)
	at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195)
	... 22 more
Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed to collect dependencies at com.atlassian.confluence:confluence:jar:6.5.1 -> org.apache.xmlgraphics:batik-css:jar:1.9 -> org.apache.xmlgraphics:batik-ext:jar:1.9
	at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:292)
	at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:317)
	at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:159)
	... 23 more
Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.xmlgraphics:batik-ext:jar:1.9
	at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:370)
	at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:217)
	at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:461)
	at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:573)
	at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:573)
	at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:261)
	... 25 more
Caused by: org.apache.maven.model.resolution.UnresolvableModelException: Could not find artifact org.apache.xmlgraphics:batik:pom:1.9 in atlassian-public (https://maven.atlassian.com/repository/public)
	at org.apache.maven.repository.internal.DefaultModelResolver.resolveModel(DefaultModelResolver.java:126)
	at org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:817)
	at org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:669)
	at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:307)
	at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:361)
	... 30 more
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.apache.xmlgraphics:batik:pom:1.9 in atlassian-public (https://maven.atlassian.com/repository/public)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:459)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:262)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:239)
	at org.apache.maven.repository.internal.DefaultModelResolver.resolveModel(DefaultModelResolver.java:122)
	... 34 more
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.apache.xmlgraphics:batik:pom:1.9 in atlassian-public (https://maven.atlassian.com/repository/public)
	at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1012)
	at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1004)
	at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:725)
	at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
[ERROR] 
[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/DependencyResolutionException
13
  • Atlassian Repo for batik – “maven atlassian com repository/public” is redirected to “maven atlassian com maven-external” - but see here: “org apache xmlgraphics batik” (I would have included links, but this editor will not let me.)
  • all I see is is 1.9.1 - not 1.9, which doesn’t seem to exist, and seems to be the source of the error.
    atlassian-batik-repo
    atlassian-batik-repo843×249 14.1 KB

Glad to provide anything else that might help resolve this.

And, “Sorry cannot post a link to that host” - WHAT host? Your editor limitations are quite frustrating, as they make you assume what the problem might be.

14

I attempted to create a new plugin and then attempted to do an atlas-run -

This is the atlas-create-confluence-plugin:

create-plugin
create-plugin656×1039 43.1 KB

Steve Hadfield

15

I got the following for atlas-run:

atlas-run-err
atlas-run-err669×1000 47.8 KB

Steve Hadfield

16

Hey Steve,
The errors you’re getting would seem to indicate some kind of Maven config problem. Can you please share the output of the atlas-version command?
Thanks,
Melissa

17

Here is the output of the atlas-version, as requested: atlas-version

Steve Hadfield

18

Melissa,

I was able to get the plugin to compile in Eclipse, but I’m not sure I consider this - resolved. This is what I did:

  1. Since I accidentally remove the 6.3.4 sdk repo, I uninstalled sdk 6.3.4, then re-installed 6.3.4. (6.3.7 is out, but I don’t know what “new” stuff is in it)
  2. I deleted the maven repo (sh4990.m2\repository)
  3. Create a helloWorld plugin (atlas-create-confluence-plugin).
  4. Attempted to execute the plugin (atlas-run), which downloaded all of the repository entries into my .m2/repository
  5. Once complete, I was able to log into Confluence, which was 6.4.0 - default for the plugin creation process.
  6. Changed the pom.xml to 6.5.0 (<confluence.version>6.5.0</confluence.version>)
  7. Attempted to execute the plugin for 6.5.0 - Even though it appeared to have started properly, could not access Confluence.
  8. Change the pom.xml to 6.6.0
  9. Attempted to execute the plugin for 6.6.0 - Even though it appeared to have started properly, could not access Confluence.
  10. I then started Eclipse 4.6 (which was working just fine before everything stopped working), and Compiled our custom plugin (set to ver 6.6.0). Compile built a JAR file - WHICH has not been tested yet.
  11. We also have a custom login module, which compiled properly as well (but is still untested).

So, I think I’m working again, BUT I still think there is an issue with Batik. I’m sort of thinking I should NOT have to create a dummy plugin every time I want to update the version of Confluence.

PLEASE NOTE: As part of my upgrade process, I do attempt to use the latest Enterprise version for clustering (i.e., recommended by Premier Support) I started with 6.5.0 because it has something in it that I want. But I figured 6.6.x would be Atlassian’s enterprise recommended version, so I updated to it. And now, 6.7.0 is out. I’d like to consider going to it, since I don’t expect to release until Aug-Sep 2018. But I do NOT want to break every again because I’m not sure I have confidence that I can get it all working again, since Batik is such a PIA. I still don’t understand what is happening, and what is the proper way to “correct” the problem I continue to encounter.

Steve Hadfield

19

@mpaisley

I decided to try executing the plugin for 6.7.0 (changing the pom.xml to ver 6.7.0) and once again got the the batik error. I reverted back to 6.6.0, and the server starts. Interestingly, I was able to get into Confluence the version was 6.4.0, even though I have the version set to 6.6.0. I don’t use this capability much, so maybe this is normal.

But I could not build for 6.7.0.

conf67-batik-err
conf67-batik-err645×546 20.3 KB

I suppose that I could delete my repository and rebuild for 6.7.0; it might build correctly. But I have a working system right now, and that is more important to me right now.

Steve Hadfield

20

Hi Steve,

The errors you’re seeing seem to indicate maven is having trouble finding important resources. I’ve tested this version after removing my maven settings to make sure I’m not getting a special advantage by having our internal maven settings configured on my machine and I’m still able to get Confluence 6.7.0 started without issues.

Another thing to check - you mentioned you changed the confluence verison to 6.7.0 in your POM, did you also change the confluence.data.version to 6.7.0?

Since it’s working for 6.6.0 and not 6.7.0 it’s possible that the issue could be because you’re using an older version of AMPS and the Atlassian Plugin SDK.

I would strongly recommend updating your version of the SDK. I have updated the release notes for the SDK on Atlassian Marketplace now, however the most significant changes will be to the version of AMPS it uses by default. You can find the AMPS release notes on the Developer documentation - AMPS SDK release notes page.

Let me know how you go.
Mel

21

First, Thank you for the reply, and especially the link. I most likely don’t know this link because I’m sort of a newbie for this developer community, even if I’ve been maintaining the plugin for 4-5 years. But as I’ve discovered upgrading the plugin can be a bit of a hassle at times.

Second, I will attempt all of this with 6.3.7. (better update notes here) Something else of note: I have never gotten SDK 6.3.6 to work, under any circumstance. Granted, I didn’t mess with it much because I started my investigations way back when 6.3.4 was the latest available release on the Marketplace. My goal was to determine how difficult dealing with the JS globals would be.

Third, I left the confluence.data.version at 6.4.0. That one has never seemed to matter, but maybe it does? It was created at 6.4.0, I only changed the confluence.version from 6.4.0 to 6.5.0, then 6.6.0 - all three worked fine. Then I changed it to 6.7.0 and that is when it failed.

Fourth, I’m in a difficult position right now. Since I found a way to “get it to work” and I can update both the Java and any other resources in the plugin I need to, it puts me in “fear” mode, afraid to “mess with success”. I’d honestly rather know why it fails. (when you clean out your Eclipse Maven project “target” dir and can no longer compile, you know you have even more problems that you thought) So, my plan is to attempt it on my Mac Mini at home this week and get back with you on those results (Sadly, I’m more of Mac user than a Mac developer). I’d much rather use 6.3.7, at a minimum, as its designed for 6.6.x, which is going to be my target version for our next Confluence release in 3Q. I’ve never experienced any of these issues before with versions under 6.x; I could switch to any version, update the sdk, etc, at will. (Eclipse 4.6, SDK 6.3.7, Conf 6.6 and 6.7)

Steve Hadfield

22

I ran into the same issue recently. It looks like there was a release of batik-css-1.9 that referenced the parent pom batik-1.9. However, batik-1.9 is not available. Instead, it looks like batik-css-1.9.pom was modified, published again, and does no longer reference the non-existing parent pom (compare [Apache-SVN] Contents of /xmlgraphics/batik/tags/batik-1_9/batik-css/pom.xml and http://repo1.maven.org/maven2/org/apache/xmlgraphics/batik-css/1.9/batik-css-1.9.pom). Anybody coming across this issue, too, try cleaning your local Maven repository and building again.

1 Like