You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Steve Vinoski <vi...@iona.com> on 2006/11/18 05:00:56 UTC

[java] maven now on trunk

I've completed bringing the initial maven work over from the branch  
to the trunk. It was kind of a manual process, given that svn merge  
can't handle directory moves. Everything should now build and test  
successfully, but the build in the distribution directory may or may  
not work completely yet, as it still needs work. I figure since we're  
not releasing M2 imminently, distributions aren't needed right away,  
but feel free to correct me if I'm guessing wrong there.

Also, I rolled the mina changes back because there were compilation  
problems even if I used the 1.1.0 snapshot jars. This means we're  
back to 1.0.0, temporarily I assume.

--steve

Re: [java] maven now on trunk

Posted by Steve Vinoski <vi...@iona.com>.
On Nov 18, 2006, at 3:02 PM, Robert Greig wrote:

> On 18/11/06, Steve Vinoski <vi...@iona.com> wrote:
>> Everything should now build and test
>> successfully, but the build in the distribution directory may or may
>> not work completely yet, as it still needs work. I figure since we're
>> not releasing M2 imminently, distributions aren't needed right away,
>> but feel free to correct me if I'm guessing wrong there.
>
> That's fine, we don't need a distribution right away but we will
> probably need one by the end of the week (roughly). We have a couple
> of teams who are eager to start developing using Qpid but need a
> couple of the (minor) missing JMS features added. We have said to them
> we'll give them a distribution to try out as soon as those features
> have been added. Obviously we don't need a full source distro with all
> the licences in place etc, just something that people can unzip on
> windows and linux and run the broker using the scripts.

Sounds reasonable. Note that as you were sending this message, I was  
filing a jira for it.

Hopefully we can pick up any cleanup being done of notices, licenses,  
readme files, etc. from the M1 effort as part of getting the maven  
distributions working.

--steve

Re: [java] maven now on trunk

Posted by Robert Greig <ro...@gmail.com>.
On 20/11/06, Carl Trieloff <cc...@redhat.com> wrote:
>
> I assume getting M1 out will meet the bill for this requirement once
> released, or am I mistaken?

No, M1 isn't enough for all our users.

We have some internal users for whom M1 is no use due to some
relatively straightforward JMS features they need (e.g. MapMessage
support).

So we are going to get onto that as a high priority item this week.

RG

Re: [java] maven now on trunk

Posted by Carl Trieloff <cc...@redhat.com>.
Robert,

I assume getting M1 out will meet the bill for this requirement once 
released, or am I mistaken?

On a related note, I will be working M2 into FC7, as there are a few 
projects there
that are using it.

Carl.

Robert Greig wrote:
> On 18/11/06, Steve Vinoski <vi...@iona.com> wrote:
>> Everything should now build and test
>> successfully, but the build in the distribution directory may or may
>> not work completely yet, as it still needs work. I figure since we're
>> not releasing M2 imminently, distributions aren't needed right away,
>> but feel free to correct me if I'm guessing wrong there.
>
> That's fine, we don't need a distribution right away but we will
> probably need one by the end of the week (roughly). We have a couple
> of teams who are eager to start developing using Qpid but need a
> couple of the (minor) missing JMS features added. We have said to them
> we'll give them a distribution to try out as soon as those features
> have been added. Obviously we don't need a full source distro with all
> the licences in place etc, just something that people can unzip on
> windows and linux and run the broker using the scripts.
>
> RG


Re: [java] maven now on trunk

Posted by Robert Greig <ro...@gmail.com>.
On 18/11/06, Steve Vinoski <vi...@iona.com> wrote:
> Everything should now build and test
> successfully, but the build in the distribution directory may or may
> not work completely yet, as it still needs work. I figure since we're
> not releasing M2 imminently, distributions aren't needed right away,
> but feel free to correct me if I'm guessing wrong there.

That's fine, we don't need a distribution right away but we will
probably need one by the end of the week (roughly). We have a couple
of teams who are eager to start developing using Qpid but need a
couple of the (minor) missing JMS features added. We have said to them
we'll give them a distribution to try out as soon as those features
have been added. Obviously we don't need a full source distro with all
the licences in place etc, just something that people can unzip on
windows and linux and run the broker using the scripts.

RG