[
https://issues.apache.org/jira/browse/FALCON-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13816887#comment-13816887
]
Venkatesh Seetharam commented on FALCON-165:
--------------------------------------------
I'm running into rat issues with this and FALCON-162 patch. The culprits are:
falcon.log.dir and falcon.embeddedmq.data. Both are created in the prism module
and rat complains. There should be sane defaults, say target/logs and
target/data.
The following command works but needs to be the default
{code}export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m" && mvn clean verify
-Dfalcon.log.dir=target/logs -Dfalcon.embeddedmq.data=target/data{code}
Not sure how to add these defaults in maven.
> simplify packaging to create one package instead of client, falcon and prism
> packages
> -------------------------------------------------------------------------------------
>
> Key: FALCON-165
> URL: https://issues.apache.org/jira/browse/FALCON-165
> Project: Falcon
> Issue Type: Improvement
> Affects Versions: 0.3
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Fix For: 0.4
>
> Attachments: FALCON-165-1383504173.patch,
> FALCON-165-1383504576.patch, FALCON-165-1383607413.patch,
> FALCON-165-1383669545.patch, FALCON-165-1383790699.patch,
> FALCON-165-1383837197.patch
>
>
> Currently we create multiple packages client, falcon server and prism server.
> Our scripts how ever already add only specific files to the class path based
> on what server we are running. I think we can also move to a single package.
> Introduced a new java property falcon.domain which will be set to falcon or
> prism based on what service is being started.
> Thus the user can set all the various startup and run time properties for
> both falcon and prism in the same file and the appropriate configs will be
> picked up based on what service is being started.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
