[
https://issues.apache.org/jira/browse/PROTON-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Harvey updated PROTON-194:
---------------------------------
Description:
The catalyst for this work was the need to conveniently build and test the JNI
bindings created in PROTON-192. However, there are a number of other
requirements for our build system that are worth reiterating.
Each of the following things should be easy to do in a small number of steps
(ideally in one step).
- Starting from a fresh checkout out the base proton directory:
- Build proton-c, including the language bindings
- Build proton-j
- Run the system tests against:
- proton-c via its Python binding
- proton-c via the JNI binding
- proton-j
It should also be convenient to run all of the above system test configurations
after making a local change to any of:
- proton-api
- proton-c implementation
- proton-c JNI bindings
- proton-j
- Starting from a *fresh checkout* of proton-c, release the proton-c tarball
- Starting from a *fresh checkout* of proton-j, publish the proton-j maven
artefacts
I'm not sure how fixed the aforementioned requirements for independent
checkouts are. Maybe we could relax the above requirement by stating that you
would also need to check out an accompanying top-level "api" module.
was:Change
> Change proton's build systems to support allow for the creation of a Java
> binding for proton-c.
> -----------------------------------------------------------------------------------------------
>
> Key: PROTON-194
> URL: https://issues.apache.org/jira/browse/PROTON-194
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c, proton-j
> Reporter: Keith Wall
>
> The catalyst for this work was the need to conveniently build and test the
> JNI bindings created in PROTON-192. However, there are a number of other
> requirements for our build system that are worth reiterating.
> Each of the following things should be easy to do in a small number of steps
> (ideally in one step).
> - Starting from a fresh checkout out the base proton directory:
> - Build proton-c, including the language bindings
> - Build proton-j
> - Run the system tests against:
> - proton-c via its Python binding
> - proton-c via the JNI binding
> - proton-j
> It should also be convenient to run all of the above system test
> configurations after making a local change to any of:
> - proton-api
> - proton-c implementation
> - proton-c JNI bindings
> - proton-j
> - Starting from a *fresh checkout* of proton-c, release the proton-c tarball
> - Starting from a *fresh checkout* of proton-j, publish the proton-j maven
> artefacts
> I'm not sure how fixed the aforementioned requirements for independent
> checkouts are. Maybe we could relax the above requirement by stating that
> you would also need to check out an accompanying top-level "api" module.
--
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
