[
https://issues.apache.org/jira/browse/SYNCOPE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495192#comment-13495192
]
Colm O hEigeartaigh commented on SYNCOPE-206:
---------------------------------------------
I get the following error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (Standalone Version) on
project syncope-standalone: An Ant BuildException has occured: Warning: Could
not find file
/home/colm/.m2/repository/org/apache/openjpa/openjpa-all/2.2.1/openjpa-all-2.2.1.jar
to copy.
openjpa-all does not appear to be a dependency for Syncope trunk and so that
line can be removed from standalone/pom.xml
Apart from that it looks good! One error I noticed is that Syncope is logging
to CATALINA_HOME/log instead of the root "log" directory.
Finally, I wonder instead of having a directory structure that looks like:
apache-tomcat-X
bundles
log
Should we not just merge the apache-tomcat-X/* into the root dir, e.g.:
bin bundles lib log NOTICE RELEASE-NOTES temp work
conf LICENSE logs README RUNNING.txt webapps
In that way we can just tell the user to execute "bin/startup.sh". I think
given that it is a standalone distribution we don't have to maintain total
separation between the container and the Syncope directories. But it's a minor
point...
Colm.
> Create standalone distribution
> ------------------------------
>
> Key: SYNCOPE-206
> URL: https://issues.apache.org/jira/browse/SYNCOPE-206
> Project: Syncope
> Issue Type: Improvement
> Reporter: Colm O hEigeartaigh
> Assignee: Massimiliano Perrone
> Fix For: 1.1.0
>
> Attachments: issueSYNCOPE206.patch, issueSYNCOPE206.patch,
> issueSYNCOPE206.patch
>
>
> This task is to create a Tomcat based standalone distribution by packing the
> cargo configuration currently used for the console's dev profile. See this
> discussion thread for more information:
> http://syncope-user.1051894.n5.nabble.com/DISCUSS-Create-Apache-Syncope-distribution-td5706676.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira