[
https://issues.apache.org/jira/browse/HUPA-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht updated HUPA-69:
-----------------------------
Attachment: fix_build.patch
Apart from some unnecessary changes (...) the patch fixes build and site
generation.
NOTE:
- Only maven version >= 3.0.2 will work.
- Site generation works using mvn site:stage in the projects root directory to
generate the site in the target/staging/... directory.
- Documentation isn't up to date, e.g. when using ssl imap the certificate must
be added to javas cacerts file before, otherwise a SSL handshake is likely to
fail
Using the patch, adapt the configuration file to my needs [1] (no imaps, port
143), building and dropping the war into a clean jetty installation I got a
working application at http://localhost:8080/hupa-client/
[1] server/src/main/webapp/WEB-INF/conf/config.properties
> Current maven build is broken
> -----------------------------
>
> Key: HUPA-69
> URL: https://issues.apache.org/jira/browse/HUPA-69
> Project: JAMES Hupa
> Issue Type: Bug
> Environment: All
> Reporter: Felix Knecht
> Assignee: Norman Maurer
> Priority: Blocker
> Labels: build
> Attachments: fix_build.patch
>
>
> A checkout of the trunk doesn't builds using maven
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
