Hi all,
I fat fingered that last comit a little, should be fixed now,
apologies if you get cruise control spam
- Aidan
--
Apache Qpid - World Domination through Advanced Message Queueing
http://cwiki.apache.org/qpid
There's a JIRA for the permissions issue to (it's the one before 1078 or
thereabouts :-)
Haven't had a chance to fix it yet though, sorry.
On 5/28/08, Aidan Skinner <[EMAIL PROTECTED]> wrote:
>
> On Wed, May 28, 2008 at 9:45 AM, Gordon Sim <[EMAIL PROTECTED]> wrote:
>
> > If you run 'ant bzip2' t
On Wed, May 28, 2008 at 9:45 AM, Gordon Sim <[EMAIL PROTECTED]> wrote:
> If you run 'ant bzip2' then unwrap the tarball, the classpath in the
> manifest for qpid-incubating.jar isn't correct:
>
> Class-Path: lib//build/lib/backport-util-concurrent-2.2.jar:lib//build
> /lib/commons-cli-1.0.jar:lib
If you run 'ant bzip2' then unwrap the tarball, the classpath in the
manifest for qpid-incubating.jar isn't correct:
Class-Path: lib//build/lib/backport-util-concurrent-2.2.jar:lib//build
/lib/commons-cli-1.0.jar:lib//build/lib/commons-codec-1.3.jar: etc etc
This means that when you try to sta
Martin,
I am not going to mentioning anything about TCK compliance for this release.
Hope thats ok with you.
I get this error frequently when I run the build and once or twice it passes
without an error.
Didn't have much time to investigate anyways.
Regards,
Rajith
On 7/20/07, Martin Ritchie
Interesting.. this is from a TCK run isn't it?
I just spent the day running them and never got a broker error... or
perhaps I just never saw the stack trace! The tests all pass with the
standard MemoryMessageStore.
I see the problem That when doing the message.expired check on
line 466 ... t
Here is the stack trace, any help is appreciated.
Currently I am trying to get the c++ build in place too.
Regards,
Rajith
[java] 2007-07-20 14:26:12,517 ERROR [pool-2-thread-3] state.AMQStateManager(
AMQStateManager.java:208) - State manager received error
notification[Current State:CONNECTION
Martin, Rupert,
Can u guys please double check and see whats failling?
Regards,
Rajith
Trunk is definitely broken at the moment (my fault!),
best to look at the M2 branch for working Java code.
On 11/04/07, Kamath, Navin <[EMAIL PROTECTED]> wrote:
Hi,
Just joined the mailing list and trying to poke around in the Java code
base and came up with the following failure. Any ide
Hi,
Just joined the mailing list and trying to poke around in the Java code
base and came up with the following failure. Any ideas? Is it a mainline
break?
I will obviously dig deeper but meanwhile if anyone knows the cause
upfront, it will be very helpful. BTW, I have just joined the maili
On Monday 22 January 2007 15:39, Robert Greig wrote:
> On 22/01/07, Kevin Smith <[EMAIL PROTECTED]> wrote:
> > > Are you building with the 1.6 jdk? I ran into similar issues when
> > > trying that, but reverting back to 1.5 seemed to do the trick.
>
> We have also been unable to build with 1.6 whic
On 22/01/07, Kevin Smith <[EMAIL PROTECTED]> wrote:
> Are you building with the 1.6 jdk? I ran into similar issues when trying
that, but reverting back to 1.5 seemed to do the trick.
We have also been unable to build with 1.6 which is *extremely*
frustrating since we want to run with 1.6 for
Tomas Restrepo wrote:
"Reason: Error getting POM for
'org.apache.maven.plugins:maven-install-plugin'
from the repository: Failed to resolve artifact, possibly due to a
repository list that is not appropriately equipped for this
artifact's metadata.
org.apache.maven.plugins:maven-install-plug
> "Reason: Error getting POM for
> 'org.apache.maven.plugins:maven-install-plugin'
> from the repository: Failed to resolve artifact, possibly due to a
> repository list that is not appropriately equipped for this
> artifact's metadata.
> org.apache.maven.plugins:maven-install-plugin:pom:2.2-S
Output attached.
--Kevin
Daniel Kulp wrote:
Can you run "mvn -X -e install" and send the output? Sometimes there's some
useful debug info there.
Dan
On Monday 22 January 2007 12:44, Kevin Smith wrote:
Tried this with no change in the error message. I have also tried deleting
my Maven i
Can you run "mvn -X -e install" and send the output? Sometimes there's some
useful debug info there.
Dan
On Monday 22 January 2007 12:44, Kevin Smith wrote:
> Tried this with no change in the error message. I have also tried deleting
> my Maven install, deleting my .m2 directory, and re-ins
Tried this with no change in the error message. I have also tried deleting my
Maven install, deleting my .m2 directory, and re-installing. Still the same error.
--Kevin
Martin Ritchie wrote:
Did maven download any files for you?
If you have a company firewall blocking maven's downloads like I d
Did maven download any files for you?
If you have a company firewall blocking maven's downloads like I did
you have to set the proxy details in the settings file.
~/.m2/settings.xml
c:/.mvn/repository/
true
http
my.webproxy.com
8000
On 22/01/07, Kevin Smith <[EMAIL
Hello all -
I've just checked out qpid from subversion and am trying to build the Java code.
I've followed the build setup docs on the wiki but Maven appears to be unhappy:
"Reason: Error getting POM for 'org.apache.maven.plugins:maven-install-plugin'
from the repository: Failed to resolve art
Ooops, that was really my fault. Robert has fixed it though.
Rupert
On 1/16/07, Robert Greig <[EMAIL PROTECTED]> wrote:
On 16/01/07, Gordon Sim <[EMAIL PROTECTED]> wrote:
> FYI: org.apache.qpid.util.concurrent.BooleanLatch seems to be missing
> from the repository.
Sorry Gordon, I've checked
On 16/01/07, Gordon Sim <[EMAIL PROTECTED]> wrote:
FYI: org.apache.qpid.util.concurrent.BooleanLatch seems to be missing
from the repository.
Sorry Gordon, I've checked in the missing file now (and double checked
the build works!).
RG
Rupert,
The exclusion shouldn't be needed anyway. In the pom.xml for commons-lang,
it's marked as test. Thus, we wouldn't be pulling it in
anyway.
Dan
On Monday 15 January 2007 07:52, Rupert Smith wrote:
> This seems to be due to the exclusion of junit (3.7.1) as an incorrect
> depency o
This seems to be due to the exclusion of junit (3.7.1) as an incorrect
depency of commons-lang:
commons-lang
commons-lang
2.1
junit
junit
Accoring to the article below, the exclusion from common-lang should
Well, I did a checkout going back to last thursday. It definitely built for
me then, but now I get the same error on that revision too. Must be
something with to do with maven, so I'll try a clean install of that and see
how I fare.
On 1/15/07, Robert Godfrey <[EMAIL PROTECTED]> wrote:
Works fi
Works fine for me on a clean checkout...
I have seen this before, but it was a problem with my local repository.
Anyone else having problems?
- Rob
On 15/01/07, Rupert Smith <[EMAIL PROTECTED]> wrote:
Did a complete, clean checkout just now and even cleared my local maven
repository.
I get
Did a complete, clean checkout just now and even cleared my local maven
repository.
I get an error compiling the unit tests, for example in the broker: "package
junit.framework does not exist". This is quite strange, as I can see junit
set up in the parent pom under dependency management and decl
I noticed that the new code generation stuff again breaks build
avoidance. It unconditionally generates code, which means the
generated code has to be compiled every single time you build.
We've already fixed this problem twice. Every time the code
generation stuff is modified, build avoida
Thanks for checking martin and once again sorry about the false alarm.
Regards,
Rajith
On 12/6/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:
np, was concerned as I was having an issue creating a branch earlier
and AJMSMessage was one of the classes I had touched so hopped I
haden't put the ch
np, was concerned as I was having an issue creating a branch earlier
and AJMSMessage was one of the classes I had touched so hopped I
haden't put the change on the trunk by mistake.
On 06/12/06, Rajith Attapattu <[EMAIL PROTECTED]> wrote:
I used mvn for building.
When I did a svn update it ha
I used mvn for building.
When I did a svn update it has done a merge with some errors which I didn't
noticed.
My bad, sorry about the false alarm.
Regards,
Rajith
On 12/6/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:
The head (r483136) builds and distributes fine for me.
Do you have any mor
The head (r483136) builds and distributes fine for me.
Do you have any more details.. Does the code compile in your IDE or do
you use mvn for building?
On 06/12/06, Rajith Attapattu <[EMAIL PROTECTED]> wrote:
Here are the errors
[INFO]
--
Here are the errors
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/opt/workspace/qpid/trunk/qpid/java/client/src/main/java/org/apache
; mvn -Dqpid.targetDir=$QPID_HOME/.. assembly:directory
>>
>> (Note, these are UNIX command lines. For Windows, change to a
>> backslash in the last line.)
>>
>> The first line is executed at the top level to do a Java build, as
>> normal. The "-Pfastinstall" tell
t;>
>> (Note, these are UNIX command lines. For Windows, change to a
>> backslash in the last line.)
>>
>> The first line is executed at the top level to do a Java build, as
>> normal. The "-Pfastinstall" tells it to skip tests, basically, by
>> invo
ackslash in the last line.)
>>
>> The first line is executed at the top level to do a Java build, as
>> normal. The "-Pfastinstall" tells it to skip tests, basically, by
>> invoking the fastinstall profile. You then change to the distribution
>> directory, and
indows, change to a
backslash in the last line.)
The first line is executed at the top level to do a Java build, as
normal. The "-Pfastinstall" tells it to skip tests, basically, by
invoking the fastinstall profile. You then change to the distribution
directory, and tell it you want the ass
eryone: shall we go with this approach then?
>
> It's better than nothing certainly!
>
> If the path wasn't so awkward and if you could create that layout
> from the base java directory (rather than from the distribution
> directory) it would be ideal. How easy is it to work ar
. If you want to do a quick
rebuild and redeploy into QPID_HOME, you can do this:
mvn -Pfastinstall
cd distribution
mvn -Dqpid.targetDir=$QPID_HOME/.. assembly:directory
(Note, these are UNIX command lines. For Windows, change to a backslash
in the last line.)
The first line is executed at the
OT . If you
want to do a quick rebuild and redeploy into QPID_HOME, you can do this:
mvn -Pfastinstall
cd distribution
mvn -Dqpid.targetDir=$QPID_HOME/.. assembly:directory
(Note, these are UNIX command lines. For Windows, change to a
backslash in the last line.)
The first line is executed
On Mon, 2006-12-04 at 08:59 +, Gordon Sim wrote:
> My thought was that if there was an easy way to do it we could have a
> task (or maven equivalent) that setup the installed package layout. We
> used to have this with the ant build.
This is the way to go: it means developers have to work wi
Steve Vinoski wrote:
On Dec 4, 2006, at 9:14 AM, Daniel Kulp wrote:
On Monday 04 December 2006 03:59, Gordon Sim wrote:
Steve Vinoski wrote:
Hi Gordon, I guess the issue here is that qpid-run is specifically
intended to work within the layout of the installed package
environment.
We could
On Dec 4, 2006, at 9:14 AM, Daniel Kulp wrote:
On Monday 04 December 2006 03:59, Gordon Sim wrote:
Steve Vinoski wrote:
Hi Gordon, I guess the issue here is that qpid-run is specifically
intended to work within the layout of the installed package
environment.
We could
1. Write a new scrip
On Monday 04 December 2006 03:59, Gordon Sim wrote:
> Steve Vinoski wrote:
> > Hi Gordon, I guess the issue here is that qpid-run is specifically
> > intended to work within the layout of the installed package environment.
> > We could
> >
> > 1. Write a new script to be used within your svn workin
Steve Vinoski wrote:
Hi Gordon, I guess the issue here is that qpid-run is specifically
intended to work within the layout of the installed package environment.
We could
1. Write a new script to be used within your svn working copy, perhaps
boiling the common parts of it and the qpid-run scr
On Dec 2, 2006, at 6:09 PM, Robert Greig wrote:
On 02/12/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
I don't think there's any need to generate such a script -- maybe we
should just create a bin directory at the java top level and add a
script there like the one you're describing?
But woul
On 02/12/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
I don't think there's any need to generate such a script -- maybe we
should just create a bin directory at the java top level and add a
script there like the one you're describing?
But would that not mean you had to edit the script every ti
On Dec 1, 2006, at 5:30 PM, Robert Greig wrote:
On 01/12/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
Hi Gordon, I guess the issue here is that qpid-run is specifically
intended to work within the layout of the installed package
environment. We could
1. Write a new script to be used within yo
On 01/12/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
Hi Gordon, I guess the issue here is that qpid-run is specifically
intended to work within the layout of the installed package
environment. We could
1. Write a new script to be used within your svn working copy,
perhaps boiling the common pa
On Dec 1, 2006, at 6:58 AM, Gordon Sim wrote:
Marnie McCormack wrote:
All,
I've made a brief initial contribution to the Build instructions
for the
java trunk here:
http://cwiki.apache.org/confluence/display/qpid/Qpid+Java+Build+How
+To
Please do contribute to/edit these instruc
Marnie McCormack wrote:
All,
I've made a brief initial contribution to the Build instructions for the
java trunk here:
http://cwiki.apache.org/confluence/display/qpid/Qpid+Java+Build+How+To
Please do contribute to/edit these instructions, especially if you have
some
maven tips to
All,
I've made a brief initial contribution to the Build instructions for the
java trunk here:
http://cwiki.apache.org/confluence/display/qpid/Qpid+Java+Build+How+To
Please do contribute to/edit these instructions, especially if you have some
maven tips to share which could be quickly
51 matches
Mail list logo
