[
https://issues.apache.org/jira/browse/TAP5-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730403#comment-14730403
]
Adam Zimowski edited comment on TAP5-2497 at 9/4/15 6:55 AM:
-------------------------------------------------------------
I have apache staging in the repository section. If I remove tapestry-test then
everything resolves fine. Here is my complete pom.
Adam
<project
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.vedime</groupId>
<artifactId>officemgr</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>war</packaging>
<name>officemgr Tapestry 5 Application</name>
<dependencies>
<!-- Too set up an application with a database, change the
artifactId below
to tapestry-hibernate, and add a dependency on your
JDBC driver. You'll also
need to add Hibernate configuration files, such as
hibernate.cfg.xml. -->
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-hibernate</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<!-- uncommenting this results in resolution errors
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-test</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
-->
<dependency>
<groupId>org.tynamo</groupId>
<artifactId>tapestry-resteasy</artifactId>
<version>0.4.0</version>
</dependency>
<dependency>
<groupId>org.jboss.resteasy</groupId>
<artifactId>resteasy-jettison-provider</artifactId>
<version>3.0.7.Final</version>
</dependency>
<!-- A dependency on either JUnit or TestNG is required, or the
surefire
plugin (which runs the tests) will fail, preventing
Maven from packaging
the WAR. Tapestry includes a large number of testing
facilities designed
for use with TestNG (http://testng.org/), so it's
recommended. -->
<dependency>
<groupId>org.easymock</groupId>
<artifactId>easymock</artifactId>
<version>${easymock-release-version}</version>
<scope>test</scope>
</dependency>
<!-- Provided by the servlet container, but sometimes
referenced in the
application code. -->
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<version>${servlet-api-release-version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.hsqldb</groupId>
<artifactId>hsqldb</artifactId>
<version>2.3.2</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.7.5</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.12</version>
</dependency>
</dependencies>
<build>
<finalName>officemgr</finalName>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
<optimize>true</optimize>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.7.2</version>
<configuration>
<systemPropertyVariables>
<tapestry.execution-mode>Qa</tapestry.execution-mode>
</systemPropertyVariables>
</configuration>
</plugin>
<!-- Run the application using "mvn jetty:run" -->
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1.16</version>
<configuration>
<!-- Log to the console. -->
<requestLog
implementation="org.mortbay.jetty.NCSARequestLog">
<!-- This doesn't do anything
for Jetty, but is a workaround for a
Maven bug that prevents
the requestLog from being set. -->
<append>true</append>
</requestLog>
<systemProperties>
<systemProperty>
<name>tapestry.execution-mode</name>
<value>development</value>
</systemProperty>
</systemProperties>
</configuration>
</plugin>
</plugins>
</build>
<reporting />
<repositories>
<!-- This repository is only needed when the Tapestry version
is a preview
release, rather than a final release. -->
<repository>
<id>apache-staging</id>
<url>https://repository.apache.org/content/groups/staging/</url>
</repository>
</repositories>
<properties>
<tapestry-release-version>5.4-beta-35</tapestry-release-version>
<servlet-api-release-version>2.5</servlet-api-release-version>
<testng-release-version>5.14.10</testng-release-version>
<easymock-release-version>3.0</easymock-release-version>
</properties>
</project>
was (Author: mrazjava):
That is exactly right. I have Maven Central in the repository section, and if I
remove tapestry-test then everything resolves fine. Here is my complete pom.
Adam
<project
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns="http://maven.apache.org/POM/4.0.0";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.vedime</groupId>
<artifactId>officemgr</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>war</packaging>
<name>officemgr Tapestry 5 Application</name>
<dependencies>
<!-- Too set up an application with a database, change the
artifactId below
to tapestry-hibernate, and add a dependency on your
JDBC driver. You'll also
need to add Hibernate configuration files, such as
hibernate.cfg.xml. -->
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-hibernate</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<!-- uncommenting this results in resolution errors
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-test</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
-->
<dependency>
<groupId>org.tynamo</groupId>
<artifactId>tapestry-resteasy</artifactId>
<version>0.4.0</version>
</dependency>
<dependency>
<groupId>org.jboss.resteasy</groupId>
<artifactId>resteasy-jettison-provider</artifactId>
<version>3.0.7.Final</version>
</dependency>
<!-- A dependency on either JUnit or TestNG is required, or the
surefire
plugin (which runs the tests) will fail, preventing
Maven from packaging
the WAR. Tapestry includes a large number of testing
facilities designed
for use with TestNG (http://testng.org/), so it's
recommended. -->
<dependency>
<groupId>org.easymock</groupId>
<artifactId>easymock</artifactId>
<version>${easymock-release-version}</version>
<scope>test</scope>
</dependency>
<!-- Provided by the servlet container, but sometimes
referenced in the
application code. -->
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<version>${servlet-api-release-version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.hsqldb</groupId>
<artifactId>hsqldb</artifactId>
<version>2.3.2</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.7.5</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.12</version>
</dependency>
</dependencies>
<build>
<finalName>officemgr</finalName>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
<optimize>true</optimize>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.7.2</version>
<configuration>
<systemPropertyVariables>
<tapestry.execution-mode>Qa</tapestry.execution-mode>
</systemPropertyVariables>
</configuration>
</plugin>
<!-- Run the application using "mvn jetty:run" -->
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1.16</version>
<configuration>
<!-- Log to the console. -->
<requestLog
implementation="org.mortbay.jetty.NCSARequestLog">
<!-- This doesn't do anything
for Jetty, but is a workaround for a
Maven bug that prevents
the requestLog from being set. -->
<append>true</append>
</requestLog>
<systemProperties>
<systemProperty>
<name>tapestry.execution-mode</name>
<value>development</value>
</systemProperty>
</systemProperties>
</configuration>
</plugin>
</plugins>
</build>
<reporting />
<repositories>
<!-- This repository is only needed when the Tapestry version
is a preview
release, rather than a final release. -->
<repository>
<id>apache-staging</id>
<url>https://repository.apache.org/content/groups/staging/</url>
</repository>
</repositories>
<properties>
<tapestry-release-version>5.4-beta-35</tapestry-release-version>
<servlet-api-release-version>2.5</servlet-api-release-version>
<testng-release-version>5.14.10</testng-release-version>
<easymock-release-version>3.0</easymock-release-version>
</properties>
</project>
> tapestry-test maven resolution
> ------------------------------
>
> Key: TAP5-2497
> URL: https://issues.apache.org/jira/browse/TAP5-2497
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-test
> Affects Versions: 5.4
> Reporter: Adam Zimowski
> Labels: maven, test
>
> <dependency>
> <groupId>org.apache.tapestry</groupId>
> <artifactId>tapestry-hibernate</artifactId>
> <version>${tapestry-release-version}</version>
> </dependency>
> <dependency>
> <groupId>org.apache.tapestry</groupId>
> <artifactId>tapestry-test</artifactId>
> <version>${tapestry-release-version}</version>
> </dependency>
> For any 5.4.x, adding tapestry-test Maven dependency (by following 5.3.x
> documentation) results in the following series of dependency errors (note
> that by merely changing ${tapestry-release-version} to any 5.3.x the issue is
> gone):
> Description Resource Path Location Type
> ArtifactDescriptorException: Failed to read artifact descriptor for
> commons-codec:commons-codec:jar:1.9: ArtifactResolutionException: Failure to
> transfer commons-codec:commons-codec:pom:1.9 from
> https://repository.apache.org/content/groups/staging/ was cached in the local
> repository, resolution will not be reattempted until the update interval of
> apache-staging has elapsed or updates are forced. Original error: Could not
> transfer artifact commons-codec:commons-codec:pom:1.9 from/to apache-staging
> (https://repository.apache.org/content/groups/staging/): The operation was
> cancelled. pom.xml /officemgr line 1 Maven Dependency Problem
> ArtifactDescriptorException: Failed to read artifact descriptor for
> commons-io:commons-io:jar:2.4: ArtifactResolutionException: Failure to
> transfer commons-io:commons-io:pom:2.4 from
> https://repository.apache.org/content/groups/staging/ was cached in the local
> repository, resolution will not be reattempted until the update interval of
> apache-staging has elapsed or updates are forced. Original error: Could not
> transfer artifact commons-io:commons-io:pom:2.4 from/to apache-staging
> (https://repository.apache.org/content/groups/staging/): The operation was
> cancelled. pom.xml /officemgr line 1 Maven Dependency Problem
> ArtifactDescriptorException: Failed to read artifact descriptor for
> xerces:xercesImpl:jar:2.11.0: ArtifactResolutionException: Failure to
> transfer xerces:xercesImpl:pom:2.11.0 from
> https://repository.apache.org/content/groups/staging/ was cached in the local
> repository, resolution will not be reattempted until the update interval of
> apache-staging has elapsed or updates are forced. Original error: Could not
> transfer artifact xerces:xercesImpl:pom:2.11.0 from/to apache-staging
> (https://repository.apache.org/content/groups/staging/): The operation was
> cancelled. pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact antlr:antlr:jar:2.7.7 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact cglib:cglib-nodep:jar:2.2 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact com.beust:jcommander:jar:1.27 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact com.google.code.gson:gson:jar:2.3.1 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact com.google.guava:guava:jar:18.0 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact com.sun.istack:istack-commons-runtime:jar:2.16 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact com.sun.xml.bind:jaxb-core:jar:2.2.7 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact com.sun.xml.bind:jaxb-impl:jar:2.2.7 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact commons-cli:commons-cli:jar:1.2 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact commons-codec:commons-codec:jar:1.10 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact commons-collections:commons-collections:jar:3.2.1 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact commons-io:commons-io:jar:2.1 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact commons-logging:commons-logging:jar:1.1.1 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact dom4j:dom4j:jar:1.6.1 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact io.netty:netty:jar:3.5.2.Final pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact javax.activation:activation:jar:1.1 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact javax.inject:javax.inject:jar:1 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact javax.servlet:servlet-api:jar:2.5 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact javax.xml.bind:jaxb-api:jar:2.2.7 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact javax.xml.bind:jsr173_api:jar:1.0 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact junit:junit:jar:4.12 pom.xml /officemgr line 1 Maven
> Dependency Problem
> Missing artifact log4j:log4j:jar:1.2.17 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact mx4j:mx4j-tools:jar:3.0.1 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact net.java.dev.jna:jna-platform:jar:4.1.0 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact net.java.dev.jna:jna:jar:4.1.0 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact net.jcip:jcip-annotations:jar:1.0 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact net.sourceforge.cssparser:cssparser:jar:0.9.16 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact net.sourceforge.htmlunit:htmlunit-core-js:jar:2.17 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact net.sourceforge.htmlunit:htmlunit:jar:2.17 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact net.sourceforge.nekohtml:nekohtml:jar:1.9.22 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.antlr:antlr-runtime:jar:3.5.2 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact org.apache.commons:commons-exec:jar:1.3 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.commons:commons-lang3:jar:3.4 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.httpcomponents:httpclient:jar:4.2.1 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.httpcomponents:httpcore:jar:4.2.1 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.httpcomponents:httpmime:jar:4.4.1 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:beanmodel:jar:5.4-beta-35 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:commons:jar:5.4-beta-35 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:plastic:jar:5.4-beta-35 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:tapestry-core:jar:5.4-beta-35 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:tapestry-func:jar:5.4-beta-35 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:tapestry-hibernate-core:jar:5.4-beta-35
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:tapestry-hibernate:jar:5.4-beta-35
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:tapestry-ioc:jar:5.4-beta-35 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:tapestry-json:jar:5.4-beta-35 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:tapestry-runner:jar:5.4-beta-35 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:tapestry-test-constants:jar:5.4-beta-35
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:tapestry-test-data:jar:5.4-beta-35
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:tapestry-test:jar:5.4-beta-35 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tapestry:tapestry5-annotations:jar:5.4-beta-35
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tomcat:annotations-api:jar:6.0.30 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tomcat:catalina:jar:6.0.30 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.apache.tomcat:coyote:jar:6.0.30 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact org.apache.tomcat:dbcp:jar:6.0.30 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact org.apache.tomcat:juli:jar:6.0.30 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact org.apache.tomcat:servlet-api:jar:6.0.30 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.beanshell:bsh:jar:2.0b4 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact org.bouncycastle:bcpkix-jdk15on:jar:1.48 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.bouncycastle:bcprov-jdk15on:jar:1.48 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.codehaus.jettison:jettison:jar:1.3.2 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.easymock:easymock:jar:3.0 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact org.eclipse.jetty:jetty-continuation:jar:7.6.11.v20130520
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.eclipse.jetty:jetty-http:jar:7.6.11.v20130520 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.eclipse.jetty:jetty-io:jar:7.6.11.v20130520 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.eclipse.jetty:jetty-jndi:jar:7.6.11.v20130520 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.eclipse.jetty:jetty-plus:jar:7.6.11.v20130520 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.eclipse.jetty:jetty-security:jar:7.6.11.v20130520
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.eclipse.jetty:jetty-server:jar:7.6.11.v20130520 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.eclipse.jetty:jetty-servlet:jar:7.6.11.v20130520 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.eclipse.jetty:jetty-util:jar:7.6.11.v20130520 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.eclipse.jetty:jetty-webapp:jar:7.6.11.v20130520 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.eclipse.jetty:jetty-xml:jar:7.6.11.v20130520 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.eclipse.jetty.orbit:javax.activation:jar:1.1.0.v201105071233 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.eclipse.jetty.orbit:javax.mail.glassfish:jar:1.4.1.v201005082020 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.eclipse.jetty.orbit:javax.servlet:jar:2.5.0.v201103041518 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.eclipse.jetty.orbit:javax.transaction:jar:1.1.1.v201105210645 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.eclipse.jetty.websocket:websocket-api:jar:9.2.11.v20150529 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.eclipse.jetty.websocket:websocket-client:jar:9.2.11.v20150529 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.eclipse.jetty.websocket:websocket-common:jar:9.2.11.v20150529 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.hamcrest:hamcrest-core:jar:1.3 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact org.hibernate:hibernate-core:jar:4.3.6.Final pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.hibernate.common:hibernate-commons-annotations:jar:4.0.5.Final pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.hsqldb:hsqldb:jar:2.3.2 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact org.javassist:javassist:jar:3.18.1-GA pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.jboss:jandex:jar:1.1.0.Final pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact org.jboss.logging:jboss-logging-annotations:jar:1.2.0.Beta1
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.jboss.logging:jboss-logging:jar:3.1.0.GA pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.jboss.resteasy:jaxrs-api:jar:3.0.7.Final pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.7.Final
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.jboss.resteasy:resteasy-jaxrs:jar:3.0.7.Final pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.jboss.resteasy:resteasy-jettison-provider:jar:3.0.7.Final pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.jboss.resteasy:resteasy-jsapi:jar:3.0.7.Final pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar:1.0.1.Final
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact
> org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.0.Final
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.mortbay.jetty:servlet-api-2.5:jar:6.1.9 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.objenesis:objenesis:jar:1.2 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:jetty-rc-repacked:jar:5 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:jetty-repacked:jar:7.6.1 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:selenium-api:jar:2.46.0 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:selenium-chrome-driver:jar:2.46.0
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:selenium-firefox-driver:jar:2.46.0
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:selenium-htmlunit-driver:jar:2.46.0
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:selenium-ie-driver:jar:2.46.0
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:selenium-java:jar:2.46.0 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:selenium-leg-rc:jar:2.46.0 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:selenium-remote-driver:jar:2.46.0
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:selenium-safari-driver:jar:2.46.0
> pom.xml /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:selenium-server:jar:2.46.0 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.seleniumhq.selenium:selenium-support:jar:2.46.0 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.slf4j:slf4j-api:jar:1.7.5 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact org.slf4j:slf4j-log4j12:jar:1.7.5 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact org.testng:testng:jar:6.8.21 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact org.tynamo:tapestry-resteasy:jar:0.4.0 pom.xml
> /officemgr line 1 Maven Dependency Problem
> Missing artifact org.w3c.css:sac:jar:1.3 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact org.webbitserver:webbit:jar:0.4.14 pom.xml /officemgr
> line 1 Maven Dependency Problem
> Missing artifact org.yaml:snakeyaml:jar:1.8 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact xalan:serializer:jar:2.7.2 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact xalan:xalan:jar:2.7.2 pom.xml /officemgr line 1
> Maven Dependency Problem
> Missing artifact xml-apis:xml-apis:jar:1.0.b2 pom.xml /officemgr line 1
> Maven Dependency Problem
> The container 'Maven Dependencies' references non existing library
> '/home/zima/.m2/repository/org/eclipse/jetty/jetty-jndi/7.6.11.v20130520/jetty-jndi-7.6.11.v20130520.jar'
> officemgr Build path Build Path Problem
> The project cannot be built until build path errors are resolved
> officemgr Unknown Java Problem
> The value of the local variable test is not used
> CustomerBeanFactory.java
> /oddajsiano-ejb-impl/src/main/java/pl/oddajsiano/ejb/dozer line 26 Java
> Problem
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
