On Wed, Jan 30, 2013 at 02:53:17PM +, Phil Harvey wrote:
I've been looking at where make install writes files to, and came across
something that seems like a wrinkle. I'd like to get views on whether it's
worth fixing.
You can control the destination of most files using the
Thanks Darryl, that makes sense.
Phil
On 30 January 2013 15:00, Darryl L. Pierce dpie...@redhat.com wrote:
On Wed, Jan 30, 2013 at 02:53:17PM +, Phil Harvey wrote:
I've been looking at where make install writes files to, and came
across
something that seems like a wrinkle. I'd like
Darryl L. Pierce created PROTON-208:
---
Summary: Create an upstream Perl language tarball
Key: PROTON-208
URL: https://issues.apache.org/jira/browse/PROTON-208
Project: Qpid Proton
Issue
Philip Harvey created PROTON-209:
Summary: Update README file(s) to more specific about required
versions of tools
Key: PROTON-209
URL: https://issues.apache.org/jira/browse/PROTON-209
Project: Qpid
[
https://issues.apache.org/jira/browse/PROTON-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Harvey updated PROTON-194:
-
Summary: Change proton's build systems to allow for the creation of a Java
binding for proton-c.
[
https://issues.apache.org/jira/browse/PROTON-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13566594#comment-13566594
]
Keith Wall commented on PROTON-194:
---
The changes on the jni-branch are nearing
Keith Wall created PROTON-210:
-
Summary: Proton release.sh should create a single release tarball
for proton-c/proton-j
Key: PROTON-210
URL: https://issues.apache.org/jira/browse/PROTON-210
Project: Qpid
[
https://issues.apache.org/jira/browse/PROTON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated PROTON-210:
--
Issue Type: New Feature (was: Task)
Proton release.sh should create a single release tarball for
[
https://issues.apache.org/jira/browse/PROTON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated PROTON-210:
--
Component/s: proton-j
Proton release.sh should create a single release tarball for
[
https://issues.apache.org/jira/browse/PROTON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated PROTON-210:
--
Component/s: (was: proton-j)
Proton release.sh should create a single release tarball for
Keith Wall created PROTON-211:
-
Summary: Non-maven users should have ability to run all system
tests
Key: PROTON-211
URL: https://issues.apache.org/jira/browse/PROTON-211
Project: Qpid Proton
I've created a Proton page on Confluence [1] and moved all existing Proton
pages underneath it.
One of these is a Proton Testing page [2], which contains a diagram
illustrating the Python, proton-c, proton-j and JNI layers involved.
I used the Gliffy Confluence plugin to draw the diagram. As we
I updated the testing diagram to include the python and C code that swig
generates. This was mostly just as an excuse to play with the tool. I
haven't used it before, but so far it seems promising. I think we could
definitely benefit from using it more.
--Rafael
On Wed, Jan 30, 2013 at 12:32 PM,
Cliff Jansen created PROTON-212:
---
Summary: Windows snprintf and vsnprintf differ on overflow from C99
Key: PROTON-212
URL: https://issues.apache.org/jira/browse/PROTON-212
Project: Qpid Proton
Wow, it's been a long time since I worked on a software diagram that was
edited by multiple people :)
With classic desktop tools like MS Visio, I find that diagrams tend to be
owned by specific individuals. I'm hopeful that the Gliffy diagrams will,
to a greater extent, reside in the commons.
Cliff Jansen created PROTON-213:
---
Summary: Reconcile C99 and C++ inconsistencies within proton
Key: PROTON-213
URL: https://issues.apache.org/jira/browse/PROTON-213
Project: Qpid Proton
Issue
16 matches
Mail list logo
