[
https://issues.apache.org/jira/browse/FALCON-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748411#comment-13748411
]
Shwetha G S edited comment on FALCON-83 at 8/23/13 9:25 AM:
------------------------------------------------------------
1. Can we ship the libs & classes, and exclude the war from bin-package &
prism-packages
- war is required for jetty
2. Can we exclude the client libs from bin & prism packages
- Instead of installing another client tgz, its better to just package it in
the same tgz
3. Does it make sense to add a falcon bin script that works in dev mode.
Currently the falcon bin script doesn't work with the mvn jetty:run version
- Will address it as part of adding examples
4. I see the id in bin-package.xml set as bin. But the installationstep.twiki
refers to falcon-server. Are they consistent ?
- Yes. Option <baseDirectory>falcon-server-${project.version}</baseDirectory>
expands bin package as falcon-server
5. Just curious why it was required for the embedded mq port to be settable
through args with default as 61616. Change looks fine though.
- Just in case if the port is not available
6. I see references to prism-start, but dont find it in the patch
- It didn't show up in status as it was ignored by .gitignore. Will add it
7. falcon-stop seems to be renamed to prism-stop. What happens to the pid file?
How is it named ? Has the possibility of falcon-server and prism-server on the
same host been considered?
- pid file is still falcon.pid. The pid file goes into {package}/logs. Since
they are different packages, they will not conflict
Will check the build failure
was (Author: shwethags):
1. Can we ship the libs & classes, and exclude the war from bin-package &
prism-packages
- war is required for jetty
2. Can we exclude the client libs from bin & prism packages
- Instead of installing another client tgz, its better to just package it in
the same tgz
3. Does it make sense to add a falcon bin script that works in dev mode.
Currently the falcon bin script doesn't work with the mvn jetty:run version
- Will address it as part of adding examples
4. I see the id in bin-package.xml set as bin. But the installationstep.twiki
refers to falcon-server. Are they consistent ?
- Yes. Option <baseDirectory>falcon-server-${project.version}</baseDirectory>
expands bin package as falcon-server
5. Just curious why it was required for the embedded mq port to be settable
through args with default as 61616. Change looks fine though.
- Just in case if the port is not available
6. I see references to prism-start, but dont find it in the patch
- It didn't show up in status as it was ignored by .gitignore. Will add it
7. falcon-stop seems to be renamed to prism-stop. What happens to the pid file?
How is it named ? Has the possibility of falcon-server and prism-server on the
same host been considered?
- pid file is still falcon.pid. The pid file goes into {package}/logs. Since
they are different packages, they will not conflict
Will check the build failure. Worked for me
> Option to build distributed packages
> ------------------------------------
>
> Key: FALCON-83
> URL: https://issues.apache.org/jira/browse/FALCON-83
> Project: Falcon
> Issue Type: Improvement
> Affects Versions: 0.4
> Reporter: Shwetha G S
> Assignee: Shwetha G S
> Labels: package
> Attachments: FALCON-83.patch, FALCON-83-v2.patch, FALCON-83-v3.patch,
> FALCON-83-v4.patch
>
>
> distributed profile builds 2 wars - one for prism and another for falcon
> server. The assembly plugin with distributed profile should also build 2
> packages - one for prism and another for falcon server
--
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
