Hi,
this is fixed on the trunk, so instead of xmlpull we now use xpp3
version 1.1.4c.
If you need to build the older version, you can use a bit older
version 1.1.3.4a of xmlpull, just change xmlpull-version in pom.xml
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration
Hi David,
Maven sites for 5.3.x releases are at
http://activemq.apache.org/maven/5.3.http://activemq.apache.org/maven/5.3.0/
x
Not referenced from anywhere I'm afraid.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action
+1
BTW we don't need to redo a release to change svn tag. Let's do it manually
with svn mv. It would be good to have apache pom 7 and everything fixed
for the 5.4 release though.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ
: incubation
Reporter: Dejan Bosanac
Priority: Minor
When you include activemq-core as a dependency on an empty project, even
simplest examples fails with
java.io.FileNotFoundException: /target/test.log (No such file or directory)
exception.
First of all, the core package
[
https://issues.apache.org/activemq/browse/AMQ-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac reopened AMQ-1010:
Patch that changes group property into groups and fixed some minor bugs in
the test class. I would
[
https://issues.apache.org/activemq/browse/AMQ-1010?page=comments#action_37479 ]
Dejan Bosanac commented on AMQ-1010:
Now I see that I named the last attribute group instead of groups (which is
more descriptive in this case). I'll provide
As far as I know retrotranslator has a maven plugin, so it is just a
matter of build process ... I've used it in Ant build process and it
was pretty straightforward. The scenario was something like this:
- build the source 1.5
- pack it in a jar
- use retrotranslator to make it 1.4 compatible
-
How about for creation of META-INF/services files for FactoryFinder?
On 11/15/06, James Strachan [EMAIL PROTECTED] wrote:
It'd be good to use annotations for the xbean stuff
On 11/15/06, Hiram Chirino [EMAIL PROTECTED] wrote:
On 11/15/06, Guillaume Nodet [EMAIL PROTECTED] wrote:
Sounds
Affects Versions: 4.1
Reporter: Dejan Bosanac
Fix For: 4.1
Attachments: simple-auth.patch
In order to be useful, SimpleAuthenticationPlugin has to be easy to configure
and well documented. I added some additional logic in order to make it play
well
I'm planning to implement a cross-domain Ajax support for ActiveMQ
(and messaging in general) for one of my future projects. I think it
would be great to have that feature built in ActiveMQ, so I did a
little research on the current implementation and possible techniques
that could be used. I
interfaces, you
have a much better way of selecting mappings though!
-Brian
On Oct 6, 2006, at 12:22 AM, Dejan Bosanac wrote:
Hi Brian,
did you check my patch with similar functionality (
https://issues.apache.org/activemq/browse/AMQ-943).
I've implemented Hiram's idea:
Translator (Mapper
Hi Brian,
did you check my patch with similar functionality (
https://issues.apache.org/activemq/browse/AMQ-943).
I've implemented Hiram's idea:
Translator (Mapper in that patch's terminology) is selected when the client
sends a CONNECT message, according to the value of the protocol-mapping
(content-length header).
Regards,
Dejan
On 9/27/06, Dejan Bosanac (JIRA) [EMAIL PROTECTED] wrote:
Pluggable Stomp Message Mapping
---
Key: AMQ-943
URL: https://issues.apache.org/activemq/browse/AMQ-943
Project: ActiveMQ
Reporter: Dejan Bosanac
Fix For: 4.1
Attachments: protocol-mapping.patch
I have finally found time to finish this. Here's the draft version of the
Pluggable Stomp Message Mapping implementation.
Few notes:
- New interface has been defined: ProtocolMapping (I wanted
conform to that format.
On 9/19/06, Dejan Bosanac [EMAIL PROTECTED] wrote:
And one copy for this list as I assume that we will continue discussion here
:)
On 9/19/06, Dejan Bosanac [EMAIL PROTECTED] wrote:
I think that in order to make this framework usable, it has to be
simple. It could
And one copy for this list as I assume that we will continue discussion here :)
On 9/19/06, Dejan Bosanac [EMAIL PROTECTED] wrote:
I think that in order to make this framework usable, it has to be
simple. It could be a simple interface such as
public interface ProtocolTransformer
16 matches
Mail list logo
