JPAContainer address book demo

Flow
1

Hello, hope i can get some help. trying to learn JPA container using the demo app and getting an error:
“Project build error: Non-resolvable parent POM: Failure to find com.vaadin.addon:jpacontainer-modules:pom:3.0.0 in http://www.eclipse.org/downloads/download.php?r=1&nf=1&file=/rt/eclipselink/maven.repo was cached in the local repository, resolution will not be reattempted until the update interval of EclipseLink Repo has elapsed or updates are forced and ‘parent.relativePath’ points at wrong local POM”
Tried changing parent version (as found on various threads) to 3.1.1, 3.0.0.beta1 but nothing helps.
Thank you.

2

I ran into the same problem. Any idea?

3

Check that the POM includes the Vaadin add-on repository and then try “mvn clean install -U” to force updating dependencies. It is perfectly normal that JPAContainer is not found in the EclipseLink repository.

It might be that the the demo project is configured assuming you are developing JPAContainer on the same computer and have performed “mvn install” for JPAContainer itself locally. In that case, the missing repository entry is something like

<repository>
   <id>vaadin-addons</id>
   <url>http://maven.vaadin.com/vaadin-addons</url>
</repository>
4

Henri, thank you for response.
However, it did not help. Repository entry you specified already was in my POM. I tried “mvn clean install -U” with verious versions and the results are still the same:

1sr attempt:
Non-resolvable parent POM: Could not find artifact com.vaadin.addon:jpacontainer-modules:pom:3.1.0-SNAPSHOT in EclipseLink Repo (http://www.eclipse.org/downloads/download.php?r=1&nf=1&file=/rt/eclipselink/maven.repo) and ‘parent.relativePath’ points at wrong local POM @ line 4, column 13 → [Help 2]

2nd attempt:
Non-resolvable parent POM: Could not find artifact com.vaadin.addon:jpacontainer-modules:pom:3.1.1 in EclipseLink Repo (http://www.eclipse.org/downloads/download.php?r=1&nf=1&file=/rt/eclipselink/maven.repo) and ‘parent.relativePath’ points at wrong local POM @ line 4, column 13 → [Help 2]

3rd:
Non-resolvable parent POM: Could not find artifact com.vaadin.addon:jpacontainer-modules:pom:3.1.0 in EclipseLink Repo (http://www.eclipse.org/downloads/download.php?r=1&nf=1&file=/rt/eclipselink/maven.repo) and ‘parent.relativePath’ points at wrong local POM @ line 4, column 13 → [Help 2]

4th:
Non-resolvable parent POM: Could not find artifact com.vaadin.addon:jpacontainer-modules:pom:3.0.0 in EclipseLink Repo (http://www.eclipse.org/downloads/download.php?r=1&nf=1&file=/rt/eclipselink/maven.repo) and ‘parent.relativePath’ points at wrong local POM @ line 4, column 13 → [Help 2]

5

Maybe the demo subproject does depend on something that is built by the JPAContainer project but not published to Maven repositories (or the add-on repository).

I’d try the easy way to make sure you have the parent pom of the project: download the whole JPAContainer project and perform “mvn -U clean install” in the root of that project (not just one subproject). It should build and install everything to your local repository - all the sub-projects including the parent project.

Note also that the error messages you are getting might be a bit misleading as if Maven does not find an artifact in one repository, it complains about that and tries the next one in the list of repositories so it is perfectly normal to get one or multiple messages like you got if the artifact is found in another repository in the end.

6

Might be a little late but I was able to solve the problem when I ran into it too by commenting out the parent node in the POM pointing to jpacontainer-modules and copying the version element into the main project node like this


<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/maven-v4_0_0.xsd">
    <!--<parent>
        <artifactId>jpacontainer-modules</artifactId>
        <groupId>com.vaadin.addon</groupId>
        <version>3.1.0</version>
    </parent>-->
	<version>3.1.0</version>
    <modelVersion>4.0.0</modelVersion>
...
</project>

Afterwards the project could be built and run even though I don’t know whether it’s the right version for the demo

7

Thank you Mark, it fixed the problem for me.

But then maven have reported problem with vaadin-shared artifact since its version was changed probably. So I added those lines to pom.xml and now the demo works:

        <dependency>
            <groupId>com.vaadin</groupId>
            <artifactId>vaadin-shared</artifactId>
            <version>7.1.3</version>
        </dependency>