[Build Issue] Cannot get web-app to build webdav dependency issue

Tim 

I have imported some of your recent changes into my local build environment but I am having some issues getting the build to complete....

Specifically the error I get when building the web-app is

Failed to execute goal on project openvpms-web-app: Could not resolve dependencies for project org.openvpms:openvpms-web-app:war:1.9-SNAPSHOT: Could not find artifact org.openvpms:openvpms-webdav-package:war:1.9-SNAPSHOT in openvpms-snapshots (http://repository.openvpms.org/snapshots) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[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/DependencyResolutionExc...
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :openvpms-web-app

Now interestinging when building that the webdav-package  I get the following warning.

[WARNING] Configuration options: 'appendAssemblyId' is set to false, and 'classifier' is missing.
Instead of attaching the assembly file: C:\Users\benjamincharlton\Dropbox\OpenVPMS\OpenVPMS Project\OpenVPMS\openvpms-web\openvpms-webdav-package\target\openvpms-webdav-package-1.9-SNAPSHOT.war, it will become the file for main project artifact.

To be fair the resolution makes sense as we arent using the repository on the server any more I dont think... but I cant understand why I the webdav-package build is not installing into my local repo...

 

Any ideas or tips .

 

Ben

 

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: [Build Issue] Cannot get web-app to build webdav ...

If you have maven 2 installed, try rebuilding with that. I'll need to make some changes to support maven 3.

Re: [Build Issue] Cannot get web-app to build webdav ...

Of course it doesnt like 1.8 JDK ....downloading 1.7 now...(I had removed it)....until we added the webdav stuff I wasnt getting these issues.

[INFO] Failed to resolve artifact.

Unable to get dependency information: Unable to read the metadata file for artifact 'org.glassfish.jersey.ext:jersey-proxy-client:jar': Invalid JDK version in profile 'jdk1.7+': Unbounded range: [1.7, for project org.glassfish.jersey:project
  org.glassfish.jersey.ext:jersey-proxy-client:jar:2.21

from the specified remote repositories:
  ibiblio (http://maven.ibiblio.org/maven2),
  openvpms-releases (http://repository.openvpms.org/releases),
  central (http://repo1.maven.org/maven2),
  jboss (https://repository.jboss.org/nexus/content/groups/public-jboss),
  openvpms-snapshots (http://repository.openvpms.org/snapshots),
  openvpms-dependencies (http://repository.openvpms.org/dependencies),
  jasper1 (http://jaspersoft.artifactoryonline.com/jaspersoft/jaspersoft-repo/),
  jasper (http://jasperreports.sourceforge.net/maven2/),
  openvpms-staging (http://repository.openvpms.org/staging)
Regards
 
Ben 
OpenVPMS Installer and Helper 
Ph: +61423044823 
Email: info[at]charltonit.com[dot]au

Re: [Build Issue] Cannot get web-app to build webdav ...

You need to massage the <MAVEN_REPOSITORY>/org/glassfish/jersey/project/2.21/project-2.21.pom to fix the dependency version. i.e. change:

<jdk>[1.7,</jdk>

to:

<jdk>[1.7,)</jdk>

See https://java.net/jira/browse/JERSEY-2881

Re: [Build Issue] Cannot get web-app to build webdav ...

Found another one of those in

\org\glassfish\hk2\hk2-parent\2.4.0-b31\hk2-parent-2.4.0-b31.pom

needs line 1098 changed from <jdk>[1.8</jdk> to jdk>[1.8,)</jdk>

Regards
 
Ben 
OpenVPMS Installer and Helper 
Ph: +61423044823 
Email: info[at]charltonit.com[dot]au

Re: [Build Issue] Cannot get web-app to build webdav ...

The jersey issue can be fixed by upgrading jersey to 2.22.1. The other one is probably easier to fix by editing the hk2-parent-2.4.0-b31.pom as you have done. Its fixed in the 2.4.0 release.

Syndicate content