Re: [jira] [Commented] (PROTON-488) Windows 7 64-bit VS2010 qpid-proton Crash on Startup with Send / Recv Application

2014-01-29 Thread Cliff Jansen 
Well thanks for all that.  I'll certainly take another look and report
back before committing anything.  Giving a compiler family indigestion
is certainly to be avoided.

Cliff

On Tue, Jan 28, 2014 at 11:29 AM, Fraser Adams
 wrote:
> Hi, me again Cliff.
> I've only had time to recheck this against my test case, which is
> representative of what I see for real.
>
> Doing:
>
> int pn_data_vfill2(const char *fmt, va_list ap)
> {
> // Process the PROPERTIES constant - this seems OK
> uint64_t prop = va_arg(ap, uint64_t);
> printf("prop = %llu\n", prop);
>
> {
> pn_bytes_t bytes = va_arg(ap, pn_bytes_t);
> printf("pn_data_vfill z, bytes.size = %zu, bytes.start = %s\n", bytes.size,
> bytes.start);
> }
>
> // Process the char* returned by pn_string_get()
> {
> char *start = va_arg(ap, char *);
> size_t size = strlen(start);
> printf("pn_data_vfill size = %zu\n", size);
> printf("pn_data_vfill string = %s\n", start);
> }
>
> return 0;
> }
>
> E.g. the both passing and retrieving structs approach of your second
> approach actually doesn't even compile for me with LLVM le32,  I get
>
> error:
>   cannot compile this aggregate va_arg expression yet
> pn_bytes_t bytes = va_arg(ap, pn_bytes_t);
>^~
> /home/fadams/emscripten/system/include/libc/stdarg.h:15:25: note: expanded
> from
>   macro 'va_arg'
> #define va_arg(v,l) __builtin_va_arg(v,l)
> ^
> 1 error generated.
> ERRORroot: compiler frontend failed to generate LLVM bitcode, halting
> make[2]: *** [CMakeFiles/test_varargs.dir/test_varargs.o] Error 1
> make[1]: *** [CMakeFiles/test_varargs.dir/all] Error 2
> make: *** [all] Error 2
>
> Though it *does* work if I do "EMCC_LLVM_TARGET=i386-pc-linux-gnu make"
>
>
> So in a nutshell:
> 1) if I fudge the LLVM front end pure struct, put  struct retrieve discrete
> and pure discrete values all work correctly.
>
> 2) with the standard emscripten le32 LLVM front end (which is what is
> recommended)
> * pure struct (as above) fails to compile
> * put  struct, retrieve discrete (as with the original Proton code) gives
> the wrong results - that messed with my head :-)
> * pure discrete values (as with your pn_string_size(msg->user_id),
> pn_string_get(msg->user_id),) patch works correctly.
>
>
> So I'd *really* like it if you could go down the path of your original patch
> 'cause that would fix what you've been seeing and let me compile the
> JavaScript stuff without needing the environment tweaked (which is an
> accident waiting to happen). I hope that you are agreeable to that?
>
> I think that it would probably be worth putting a comment in the call to
> pn_data_fill and within the pn_data_vfill() 'z' case body to document that
> it's safer to pass individual entries to va_arg to avoid upsetting some
> compilers - it's not entirely an *obvious* thing really :-D
>
> Cheers,
> Frase
>
>
>
>
> On 27/01/14 21:21, Cliff Jansen wrote:
>>
>> Thanks for the Javascript related info.
>>
>> Fraser: can you test if the review board patch (with the struct "in
>> and out" strategy) works in your case with the unhacked llvm setup?
>> If that works then I'll go ahead and check it in.
>>
>> If it fails, please try the first patch.  If that works, we will just
>> have to conclude that compilers have trouble with stucts in this case
>> and fall back to passing the two basic types.  That should be safe to
>> work in the greatest number of cases.
>>
>> Many thanks.
>>
>> On Mon, Jan 27, 2014 at 1:13 PM, Fraser Adams (JIRA) 
>> wrote:
>>>
>>>  [
>>> https://issues.apache.org/jira/browse/PROTON-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883314#comment-13883314
>>> ]
>>>
>>> Fraser Adams commented on PROTON-488:
>>> -
>>>
>>> Oh to be clear
>>> either "struct in and out", or "separate size_t and char* in and out"
>>>
>>> what I meant in my previous comment was that the separate size_t and
>>> char* in and out is what LLVM le32 is happiest with, the structs seem to
>>> confuse it, I hadn't realised that you'd changed your original patch to now
>>> do "all 'z' encodings to be passed as a single pn_bytes_t struct and
>>> "retrieved" as a single pn_bytes_t struct" - although this arguably looks
>>> neater I'd definitely prefer your first approach.
>>>
 Windows 7 64-bit VS2010 qpid-proton Crash on Startup with Send / Recv
 Application

 -

  Key: PROTON-488
  URL: https://issues.apache.org/jira/browse/PROTON-488
  Project: Qpid Proton
   Issue Type: Bug
   Components: proton-c
 Affects Versions: 0.6
  Environment: Windows 7 64-bit VS 2010
 Reporter: Frank Quinn
 Ass

[jira] [Created] (PROTON-500) [proton-c] Enable valgrind on C unit tests

2014-01-29 Thread Ken Giusti (JIRA) 
Ken Giusti created PROTON-500:
-

 Summary: [proton-c] Enable valgrind on C unit tests
 Key: PROTON-500
 URL: https://issues.apache.org/jira/browse/PROTON-500
 Project: Qpid Proton
  Issue Type: Test
  Components: proton-c
Affects Versions: 0.6
Reporter: Ken Giusti
Priority: Trivial
 Fix For: 0.7


Enable valgrind to run over the C unit tests if it is installed.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (PROTON-499) maven build is circularly dependent

2014-01-29 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886132#comment-13886132
 ] 

ASF subversion and git services commented on PROTON-499:


Commit 1562665 from r...@apache.org in branch 'proton/trunk'
[ https://svn.apache.org/r1562665 ]

PROTON-499: fixed config.sh to reference new paths

> maven build is circularly dependent
> ---
>
> Key: PROTON-499
> URL: https://issues.apache.org/jira/browse/PROTON-499
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.6
>Reporter: Rafael H. Schloming
>Assignee: Rafael H. Schloming
> Fix For: 0.7
>
>
> The maven build depends on the binaries from the output of the prior 
> iteration of the build. This is a bit hard to notice because maven seems to 
> be downloading snapshot binaries from somewhere. Reproduce with the following 
> steps:
> # First ensure legitimate dependencies are downloaded:
> mvn compile
> # now blow away snapshots that should not be needed for a clean build
> rm -rf ~/.m2/repository/org/apache/qpid/
> # now run an offline build
> mvn -o compile
> You should see this failure:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process (default) 
> on project proton-tests: Failed to resolve dependencies for one or more 
> projects in the reactor. Reason: Missing:
> [ERROR] --
> [ERROR] 1) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] Try downloading the file manually from the project website.
> [ERROR] 
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file
> [ERROR] 
> [ERROR] Alternatively, if you host your own repository you can deploy the 
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> [ERROR] 
> [ERROR] Path to dependency:
> [ERROR] 1) org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 2) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] --
> [ERROR] 1 required artifact is missing.
> [ERROR] 
> [ERROR] for artifact:
> [ERROR] org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] from the specified remote repositories:
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots, 
> releases=false, snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, 
> snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :proton-tests



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (PROTON-499) maven build is circularly dependent

2014-01-29 Thread Robbie Gemmell (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885979#comment-13885979
 ] 

Robbie Gemmell commented on PROTON-499:
---

mvn test shouldn't have run against the nightlies so long as you are also 
building the proton-j module at the time (or installed it recently), because 
the build uses artifacts from the current reactor build rather than look 
elsewhere. If you happened to only build the tests module and never proton-j, 
then it would have no choice but to look elsewhere (i.e local repo or the 
remote repo) to try and satisfy the dependency. Where I do most of my builds, I 
can only get at a year-old remote snapshot (long story, think corporate 
stupidity and you will be on the right track) so I never tend to use anything 
other than the current reactor build or local installs.

> maven build is circularly dependent
> ---
>
> Key: PROTON-499
> URL: https://issues.apache.org/jira/browse/PROTON-499
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.6
>Reporter: Rafael H. Schloming
>Assignee: Rafael H. Schloming
> Fix For: 0.7
>
>
> The maven build depends on the binaries from the output of the prior 
> iteration of the build. This is a bit hard to notice because maven seems to 
> be downloading snapshot binaries from somewhere. Reproduce with the following 
> steps:
> # First ensure legitimate dependencies are downloaded:
> mvn compile
> # now blow away snapshots that should not be needed for a clean build
> rm -rf ~/.m2/repository/org/apache/qpid/
> # now run an offline build
> mvn -o compile
> You should see this failure:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process (default) 
> on project proton-tests: Failed to resolve dependencies for one or more 
> projects in the reactor. Reason: Missing:
> [ERROR] --
> [ERROR] 1) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] Try downloading the file manually from the project website.
> [ERROR] 
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file
> [ERROR] 
> [ERROR] Alternatively, if you host your own repository you can deploy the 
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> [ERROR] 
> [ERROR] Path to dependency:
> [ERROR] 1) org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 2) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] --
> [ERROR] 1 required artifact is missing.
> [ERROR] 
> [ERROR] for artifact:
> [ERROR] org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] from the specified remote repositories:
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots, 
> releases=false, snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, 
> snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :proton-tests



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: [RESULT] [VOTE]: Release Proton 0.6 RC3 as 0.6 final

2014-01-29 Thread Rafael Schloming 
Yup, thanks for the reminder, they should be available shortly.

--Rafael


On Wed, Jan 29, 2014 at 5:47 PM, Robbie Gemmell wrote:

> The Java binaries for 0.6 seem to be MIA. Still sitting in a staging repo
> somewhere?
>
> Robbie
>
> On 16 January 2014 10:42, Rafael Schloming  wrote:
>
> > The release artifacts for Proton 0.6 are now available from the web site:
> > http://qpid.apache.org/releases/qpid-proton-0.6/index.html
> >
> > --Rafael
> >
> >
> > On Tue, Jan 14, 2014 at 10:20 AM, Rafael Schloming 
> > wrote:
> >
> > > The vote carries with 3 binding +1's, 2 non-binding +1's, and no other
> > > votes. I'll post the artifacts shortly.
> > >
> > > --Rafael
> > >
> > > On Thu, Jan 2, 2014 at 2:17 PM, Rafael Schloming 
> > wrote:
> > >
> > >> Hi Everyone,
> > >>
> > >> It looks like there haven't been any major issues reported so far with
> > >> 0.6 RC3, so I guess it's about time to call for a formal vote.
> > >>
> > >> Source is here:
> > >>
> > >> http://people.apache.org/~rhs/qpid-proton-0.6rc3/
> > >>
> > >> Java binaries are here:
> > >>
> > >>
> > https://repository.apache.org/content/repositories/orgapacheqpid-003/
> > >>
> > >> Please peruse/test and register your vote:
> > >>
> > >> [ ] Yes, release 0.6 RC3 as 0.6 final
> > >> [ ] No, 0.6 RC3 has the following issues...
> > >>
> > >> --Rafael
> > >>
> > >
> > >
> >
>

[jira] [Commented] (PROTON-499) maven build is circularly dependent

2014-01-29 Thread Rafael H. Schloming (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885963#comment-13885963
 ] 

Rafael H. Schloming commented on PROTON-499:


That makes sense. I figured out the test-jar thing was involved somehow through 
trial and error and then I pared things down to the point where it all seemed 
to work.

I did observe mvn -o test succeeding even when mvn -o compile failed, although 
I *think* without the -o flag that mvn test was building against the nightlies. 
I really wish there was a way to enforce that the entire build is done across 
what is actually in the file system. The directories we have aren't actually as 
independent as maven seems to treat modules.

> maven build is circularly dependent
> ---
>
> Key: PROTON-499
> URL: https://issues.apache.org/jira/browse/PROTON-499
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.6
>Reporter: Rafael H. Schloming
>Assignee: Rafael H. Schloming
> Fix For: 0.7
>
>
> The maven build depends on the binaries from the output of the prior 
> iteration of the build. This is a bit hard to notice because maven seems to 
> be downloading snapshot binaries from somewhere. Reproduce with the following 
> steps:
> # First ensure legitimate dependencies are downloaded:
> mvn compile
> # now blow away snapshots that should not be needed for a clean build
> rm -rf ~/.m2/repository/org/apache/qpid/
> # now run an offline build
> mvn -o compile
> You should see this failure:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process (default) 
> on project proton-tests: Failed to resolve dependencies for one or more 
> projects in the reactor. Reason: Missing:
> [ERROR] --
> [ERROR] 1) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] Try downloading the file manually from the project website.
> [ERROR] 
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file
> [ERROR] 
> [ERROR] Alternatively, if you host your own repository you can deploy the 
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> [ERROR] 
> [ERROR] Path to dependency:
> [ERROR] 1) org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 2) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] --
> [ERROR] 1 required artifact is missing.
> [ERROR] 
> [ERROR] for artifact:
> [ERROR] org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] from the specified remote repositories:
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots, 
> releases=false, snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, 
> snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :proton-tests



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: [RESULT] [VOTE]: Release Proton 0.6 RC3 as 0.6 final

2014-01-29 Thread Robbie Gemmell 
The Java binaries for 0.6 seem to be MIA. Still sitting in a staging repo
somewhere?

Robbie

On 16 January 2014 10:42, Rafael Schloming  wrote:

> The release artifacts for Proton 0.6 are now available from the web site:
> http://qpid.apache.org/releases/qpid-proton-0.6/index.html
>
> --Rafael
>
>
> On Tue, Jan 14, 2014 at 10:20 AM, Rafael Schloming 
> wrote:
>
> > The vote carries with 3 binding +1's, 2 non-binding +1's, and no other
> > votes. I'll post the artifacts shortly.
> >
> > --Rafael
> >
> > On Thu, Jan 2, 2014 at 2:17 PM, Rafael Schloming 
> wrote:
> >
> >> Hi Everyone,
> >>
> >> It looks like there haven't been any major issues reported so far with
> >> 0.6 RC3, so I guess it's about time to call for a formal vote.
> >>
> >> Source is here:
> >>
> >> http://people.apache.org/~rhs/qpid-proton-0.6rc3/
> >>
> >> Java binaries are here:
> >>
> >>
> https://repository.apache.org/content/repositories/orgapacheqpid-003/
> >>
> >> Please peruse/test and register your vote:
> >>
> >> [ ] Yes, release 0.6 RC3 as 0.6 final
> >> [ ] No, 0.6 RC3 has the following issues...
> >>
> >> --Rafael
> >>
> >
> >
>

[jira] [Commented] (PROTON-253) Remove compile-time dependency on bouncycastle cryptography library

2014-01-29 Thread Robbie Gemmell (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885936#comment-13885936
 ] 

Robbie Gemmell commented on PROTON-253:
---

bouncycastle should probably still be listed as an optional runtime dependency 
in the pom, if thats what it now is.

> Remove compile-time dependency on bouncycastle cryptography library
> ---
>
> Key: PROTON-253
> URL: https://issues.apache.org/jira/browse/PROTON-253
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-j
>Affects Versions: 0.4
>Reporter: Philip Harvey
>Assignee: Philip Harvey
>Priority: Minor
>
> It is inconvenient that the proton-j requires bouncycastle to be on the 
> compile-time classpath, as the Proton user may wish to use an alternative 
> provider, or to use Java's vanilla SSL certificate support.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (PROTON-499) maven build is circularly dependent

2014-01-29 Thread Robbie Gemmell (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885885#comment-13885885
 ] 

Robbie Gemmell commented on PROTON-499:
---

This wasnt really a circular dependency as such, instead more of an unenforced 
ordering requirement. While it could use the artifacts from a previous build 
(as its really meant to be able to, for what it thinks are independent modules) 
it typically wouldnt be doing so.

The main reason you saw a problem (which admittedly is still quite an 
annoyance) is that the 'tests' module depended on the test jar from the 
proton-j module, which you explicitly didnt create by only running 'maven 
compile'. I have run the build on a number of fresh boxes recently without 
issue, the main diference being that the more typical 'maven test' or 'maven 
install' commands create the test artifacts for project-j before ever getting 
to the 'tests' module ('maven test-compile' might also have worked due to being 
in the same reactor build, not sure), which would then pick up the necessary 
artifact from the current reactor build. When using 'maven compile' by itself, 
it would have either been picking up a previously installed version if you had 
recently done that, or instead been hitting the Apache snapshots repository 
occasionally to download the nightly build, hence the offline flag making the 
difference when your local repo was cleared.

> maven build is circularly dependent
> ---
>
> Key: PROTON-499
> URL: https://issues.apache.org/jira/browse/PROTON-499
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.6
>Reporter: Rafael H. Schloming
>Assignee: Rafael H. Schloming
> Fix For: 0.7
>
>
> The maven build depends on the binaries from the output of the prior 
> iteration of the build. This is a bit hard to notice because maven seems to 
> be downloading snapshot binaries from somewhere. Reproduce with the following 
> steps:
> # First ensure legitimate dependencies are downloaded:
> mvn compile
> # now blow away snapshots that should not be needed for a clean build
> rm -rf ~/.m2/repository/org/apache/qpid/
> # now run an offline build
> mvn -o compile
> You should see this failure:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process (default) 
> on project proton-tests: Failed to resolve dependencies for one or more 
> projects in the reactor. Reason: Missing:
> [ERROR] --
> [ERROR] 1) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] Try downloading the file manually from the project website.
> [ERROR] 
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file
> [ERROR] 
> [ERROR] Alternatively, if you host your own repository you can deploy the 
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> [ERROR] 
> [ERROR] Path to dependency:
> [ERROR] 1) org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 2) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] --
> [ERROR] 1 required artifact is missing.
> [ERROR] 
> [ERROR] for artifact:
> [ERROR] org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] from the specified remote repositories:
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots, 
> releases=false, snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, 
> snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :proton-tests



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (PROTON-417) Remove/optionalize bouncycastle dependency

2014-01-29 Thread Rafael H. Schloming (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael H. Schloming resolved PROTON-417.


Resolution: Fixed

> Remove/optionalize bouncycastle dependency
> --
>
> Key: PROTON-417
> URL: https://issues.apache.org/jira/browse/PROTON-417
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Reporter: Rafael H. Schloming
> Fix For: 0.7
>
>




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (PROTON-253) Remove compile-time dependency on bouncycastle cryptography library

2014-01-29 Thread Rafael H. Schloming (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael H. Schloming resolved PROTON-253.


Resolution: Fixed

> Remove compile-time dependency on bouncycastle cryptography library
> ---
>
> Key: PROTON-253
> URL: https://issues.apache.org/jira/browse/PROTON-253
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-j
>Affects Versions: 0.4
>Reporter: Philip Harvey
>Assignee: Philip Harvey
>Priority: Minor
>
> It is inconvenient that the proton-j requires bouncycastle to be on the 
> compile-time classpath, as the Proton user may wish to use an alternative 
> provider, or to use Java's vanilla SSL certificate support.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (PROTON-499) maven build is circularly dependent

2014-01-29 Thread Rafael H. Schloming (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael H. Schloming resolved PROTON-499.


Resolution: Fixed

> maven build is circularly dependent
> ---
>
> Key: PROTON-499
> URL: https://issues.apache.org/jira/browse/PROTON-499
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.6
>Reporter: Rafael H. Schloming
>Assignee: Rafael H. Schloming
> Fix For: 0.7
>
>
> The maven build depends on the binaries from the output of the prior 
> iteration of the build. This is a bit hard to notice because maven seems to 
> be downloading snapshot binaries from somewhere. Reproduce with the following 
> steps:
> # First ensure legitimate dependencies are downloaded:
> mvn compile
> # now blow away snapshots that should not be needed for a clean build
> rm -rf ~/.m2/repository/org/apache/qpid/
> # now run an offline build
> mvn -o compile
> You should see this failure:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process (default) 
> on project proton-tests: Failed to resolve dependencies for one or more 
> projects in the reactor. Reason: Missing:
> [ERROR] --
> [ERROR] 1) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] Try downloading the file manually from the project website.
> [ERROR] 
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file
> [ERROR] 
> [ERROR] Alternatively, if you host your own repository you can deploy the 
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> [ERROR] 
> [ERROR] Path to dependency:
> [ERROR] 1) org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 2) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] --
> [ERROR] 1 required artifact is missing.
> [ERROR] 
> [ERROR] for artifact:
> [ERROR] org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] from the specified remote repositories:
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots, 
> releases=false, snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, 
> snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :proton-tests



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (PROTON-494) remove JNI binding

2014-01-29 Thread Rafael H. Schloming (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael H. Schloming resolved PROTON-494.


Resolution: Fixed

> remove JNI binding
> --
>
> Key: PROTON-494
> URL: https://issues.apache.org/jira/browse/PROTON-494
> Project: Qpid Proton
>  Issue Type: Task
>Reporter: Rafael H. Schloming
>




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

heads up on build changes

2014-01-29 Thread Rafael Schloming 
Hi,

I just wanted to give everyone a heads up on a change I just committed.
This may end up impacting downstream java users as the artifact names have
changed a bit.

You can see PROTON-499 for some of the gory details, but long story short I
ended up moving around some code and flattening out the structure a little
bit. Part of the changes were necessary to fix the aforementioned build
issue, and some of the changes are simply me taking advantage of the
opportunity to do a little cleanup.

I believe the impact on artifact names is that if you were previously
depending on proton-j-impl and/or proton-api, you should now just depend on
proton-j.

Please let me know if you run into any issues with this.

Thanks,

--Rafael

[jira] [Commented] (PROTON-494) remove JNI binding

2014-01-29 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885779#comment-13885779
 ] 

ASF subversion and git services commented on PROTON-494:


Commit 1562580 from r...@apache.org in branch 'proton/trunk'
[ https://svn.apache.org/r1562580 ]

PROTON-494: updated the README

> remove JNI binding
> --
>
> Key: PROTON-494
> URL: https://issues.apache.org/jira/browse/PROTON-494
> Project: Qpid Proton
>  Issue Type: Task
>Reporter: Rafael H. Schloming
>




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (PROTON-253) Remove compile-time dependency on bouncycastle cryptography library

2014-01-29 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885759#comment-13885759
 ] 

ASF subversion and git services commented on PROTON-253:


Commit 1562574 from r...@apache.org in branch 'proton/trunk'
[ https://svn.apache.org/r1562574 ]

PROTON-253, PROTON-417, and PROTON-499: This change consits mostly of
moving stuff around to avoid using the "test-jar" mechanism introduced
into the proton-j build a while ago. It appears that use of this
mechanism causes the maven build to be circularly self-dependent, i.e.
it requires an older stale binary version of its own output in order
to successfully complete the mvn compile stage. There are also some
fairly small code changes included that make the bouncycastle
dependency a runtime dependency rather than a compile-time dependency.

> Remove compile-time dependency on bouncycastle cryptography library
> ---
>
> Key: PROTON-253
> URL: https://issues.apache.org/jira/browse/PROTON-253
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-j
>Affects Versions: 0.4
>Reporter: Philip Harvey
>Assignee: Philip Harvey
>Priority: Minor
>
> It is inconvenient that the proton-j requires bouncycastle to be on the 
> compile-time classpath, as the Proton user may wish to use an alternative 
> provider, or to use Java's vanilla SSL certificate support.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (PROTON-499) maven build is circularly dependent

2014-01-29 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885761#comment-13885761
 ] 

ASF subversion and git services commented on PROTON-499:


Commit 1562574 from r...@apache.org in branch 'proton/trunk'
[ https://svn.apache.org/r1562574 ]

PROTON-253, PROTON-417, and PROTON-499: This change consits mostly of
moving stuff around to avoid using the "test-jar" mechanism introduced
into the proton-j build a while ago. It appears that use of this
mechanism causes the maven build to be circularly self-dependent, i.e.
it requires an older stale binary version of its own output in order
to successfully complete the mvn compile stage. There are also some
fairly small code changes included that make the bouncycastle
dependency a runtime dependency rather than a compile-time dependency.

> maven build is circularly dependent
> ---
>
> Key: PROTON-499
> URL: https://issues.apache.org/jira/browse/PROTON-499
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.6
>Reporter: Rafael H. Schloming
>Assignee: Rafael H. Schloming
> Fix For: 0.7
>
>
> The maven build depends on the binaries from the output of the prior 
> iteration of the build. This is a bit hard to notice because maven seems to 
> be downloading snapshot binaries from somewhere. Reproduce with the following 
> steps:
> # First ensure legitimate dependencies are downloaded:
> mvn compile
> # now blow away snapshots that should not be needed for a clean build
> rm -rf ~/.m2/repository/org/apache/qpid/
> # now run an offline build
> mvn -o compile
> You should see this failure:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process (default) 
> on project proton-tests: Failed to resolve dependencies for one or more 
> projects in the reactor. Reason: Missing:
> [ERROR] --
> [ERROR] 1) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] Try downloading the file manually from the project website.
> [ERROR] 
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file
> [ERROR] 
> [ERROR] Alternatively, if you host your own repository you can deploy the 
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.qpid 
> -DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
> -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> [ERROR] 
> [ERROR] Path to dependency:
> [ERROR] 1) org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 2) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] --
> [ERROR] 1 required artifact is missing.
> [ERROR] 
> [ERROR] for artifact:
> [ERROR] org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
> [ERROR] 
> [ERROR] from the specified remote repositories:
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots, 
> releases=false, snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, 
> snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :proton-tests



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (PROTON-417) Remove/optionalize bouncycastle dependency

2014-01-29 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885760#comment-13885760
 ] 

ASF subversion and git services commented on PROTON-417:


Commit 1562574 from r...@apache.org in branch 'proton/trunk'
[ https://svn.apache.org/r1562574 ]

PROTON-253, PROTON-417, and PROTON-499: This change consits mostly of
moving stuff around to avoid using the "test-jar" mechanism introduced
into the proton-j build a while ago. It appears that use of this
mechanism causes the maven build to be circularly self-dependent, i.e.
it requires an older stale binary version of its own output in order
to successfully complete the mvn compile stage. There are also some
fairly small code changes included that make the bouncycastle
dependency a runtime dependency rather than a compile-time dependency.

> Remove/optionalize bouncycastle dependency
> --
>
> Key: PROTON-417
> URL: https://issues.apache.org/jira/browse/PROTON-417
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Reporter: Rafael H. Schloming
> Fix For: 0.7
>
>




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: Qpid Proton messenger on 32 bit linux

2014-01-29 Thread Ted Ross 

I haven't had a change to try it yet.

I think we typically use "-m32 -march=i686"

-Ted

On 01/29/2014 09:56 AM, serega wrote:

The attached example is a  send.c
   slightly modified
send.c example. It works in 64 bit environment, but crashes when proton is
build with export CFLAGS=-m32  . Can you execute it on 32 bit linux?

Thanks,
Sergey.



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-Proton-messenger-on-32-bit-linux-tp7603445p7603555.html
Sent from the Apache Qpid Proton mailing list archive at Nabble.com.

[jira] [Created] (PROTON-499) maven build is circularly dependent

2014-01-29 Thread Rafael H. Schloming (JIRA) 
Rafael H. Schloming created PROTON-499:
--

 Summary: maven build is circularly dependent
 Key: PROTON-499
 URL: https://issues.apache.org/jira/browse/PROTON-499
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-j
Affects Versions: 0.6
Reporter: Rafael H. Schloming
Assignee: Rafael H. Schloming
 Fix For: 0.7


The maven build depends on the binaries from the output of the prior iteration 
of the build. This is a bit hard to notice because maven seems to be 
downloading snapshot binaries from somewhere. Reproduce with the following 
steps:

# First ensure legitimate dependencies are downloaded:
mvn compile
# now blow away snapshots that should not be needed for a clean build
rm -rf ~/.m2/repository/org/apache/qpid/
# now run an offline build
mvn -o compile

You should see this failure:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process (default) on 
project proton-tests: Failed to resolve dependencies for one or more projects 
in the reactor. Reason: Missing:
[ERROR] --
[ERROR] 1) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
[ERROR] 
[ERROR] Try downloading the file manually from the project website.
[ERROR] 
[ERROR] Then, install it using the command:
[ERROR] mvn install:install-file -DgroupId=org.apache.qpid 
-DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
-Dpackaging=test-jar -Dfile=/path/to/file
[ERROR] 
[ERROR] Alternatively, if you host your own repository you can deploy the file 
there:
[ERROR] mvn deploy:deploy-file -DgroupId=org.apache.qpid 
-DartifactId=proton-j-impl -Dversion=1.0-SNAPSHOT -Dclassifier=tests 
-Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR] Path to dependency:
[ERROR] 1) org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
[ERROR] 2) org.apache.qpid:proton-j-impl:test-jar:tests:1.0-SNAPSHOT
[ERROR] 
[ERROR] --
[ERROR] 1 required artifact is missing.
[ERROR] 
[ERROR] for artifact:
[ERROR] org.apache.qpid:proton-tests:jar:1.0-SNAPSHOT
[ERROR] 
[ERROR] from the specified remote repositories:
[ERROR] apache.snapshots (http://repository.apache.org/snapshots, 
releases=false, snapshots=true),
[ERROR] central (http://repo.maven.apache.org/maven2, releases=true, 
snapshots=false)
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :proton-tests




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: Qpid Proton messenger on 32 bit linux

2014-01-29 Thread serega 
The attached example is a  send.c
   slightly modified
send.c example. It works in 64 bit environment, but crashes when proton is
build with export CFLAGS=-m32  . Can you execute it on 32 bit linux? 

Thanks,
Sergey.



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-Proton-messenger-on-32-bit-linux-tp7603445p7603555.html
Sent from the Apache Qpid Proton mailing list archive at Nabble.com.