On 16/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
Besides, maven can't cleanly merge to trunk anymore because
Martin changed the mina code, which is what started this whole issue
regarding snapshots and code drops and such. If I merge what's on the
branch, then we'll revert to mina 1.0.0 and
These additions don't seem onerous but IANAL. Point 4 doesn't apply as
we are not deriving from it, only using it. Point 5 would be satisfied
by a prominent thank you note in our README file or on our Wiki I
imagine. Note that the Exolab project no longer exists...
Point 5 should be able to
On 11/16/06, Daniel Kulp <[EMAIL PROTECTED]> wrote:
From my standpoint, I will vote -1 (non-binding) on the [EMAIL PROTECTED]
list (as well as here) for a release with a SNAPSHOT of an Apache
project.
Allowed by the license or not, I don't think the ASF should do anything to
promote having unof
On 16/11/06, Marnie McCormack <[EMAIL PROTECTED]> wrote:
http://jmscts.sourceforge.net/license.html
That's a very slightly modified "New BSD" license which is allowed on
http://www.apache.org/legal/3party.html
which points to the definition here:
http://opensource.org/licenses/bsd-lice
Hi Folks,
Feel free to have a party with the trunk.
I have already cut a branch for the M1 release.
Also if there is any change required to make M1 work ***PLEASE*** make sure
you do it in the M1 branch as well.
If this change is preventing future direction please don't put that in the
trunk.
S
On Nov 16, 2006, at 3:04 PM, Marnie McCormack wrote:
Copied from a separate post:
A salient point in all of these (about maven/release) discussions -
what's
the current status of the issues with the maven build ? Is it ready
to go -
if not, what is outstanding ?
Umm, did you read my prev
Copied from a separate post:
A salient point in all of these (about maven/release) discussions - what's
the current status of the issues with the maven build ? Is it ready to go -
if not, what is outstanding ?
I think it'd be very useful to state where the maven build is ? Been lots of
discussio
There are clearly several threads on the go discussing this point.
Just wanted to point out that we are working closely with the MINA team and
afaik there is no disagreement about the changes made.
Martin/Robert both know more of the detail, but I think it's important to
note that we are working
Cliff,
Can we get clarification about the inubator releases? As in, should they
be put in http://www.apache.org/dist/incubator where they are sent out to
the mirrors or not?
I know there was a lot of discussion about whether incubator stuff goes to
mirrors or not.Was there actually a res
A timely post just sent to [EMAIL PROTECTED]
Cliff
On 11/16/06, Joe Schaefer wrote:
This week, infrastructure has clarified ASF policy
regarding releases. Please review
http://www.apache.org/dev/release.html
and in particular the sections on "What is a release?"
and "Where can I find AS
On 11/16/06, John O'Hara <[EMAIL PROTECTED]> wrote:
That's what we need -- some mentor time!
We can use any code (a license is a license is a license).
The question is whether the Incubator PMC will allow it to become M1?
Cliff, James, Paul - any opinion?
In a nutshell: we have a "fix" for MIN
On Thursday November 16 2006 12:54 pm, Paul Fremantle wrote:
> John
>
> There isn't any license issue about using the code. The only problem
> is that you release code will not be rebuildable at some point in the
> future. If you want a possible technical solution to that problem here
> is one.
>
>
From my standpoint, I will vote -1 (non-binding) on the [EMAIL PROTECTED]
list (as well as here) for a release with a SNAPSHOT of an Apache
project.
Allowed by the license or not, I don't think the ASF should do anything to
promote having unofficial versions of ASF artifacts being distributed
John
There isn't any license issue about using the code. The only problem
is that you release code will not be rebuildable at some point in the
future. If you want a possible technical solution to that problem here
is one.
I suggest that you take a specific revision of the MINA code - say
nn
That's what we need -- some mentor time!
We can use any code (a license is a license is a license).
The question is whether the Incubator PMC will allow it to become M1?
Cliff, James, Paul - any opinion?
In a nutshell: we have a "fix" for MINA that Qpid depends on, but has not
yet been adopted
On Nov 16, 2006, at 11:26 AM, John O'Hara wrote:
On 15/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
Yes, it can be long. But those are the rules by which we must abide
under Apache. As Rajith points out in a separate email, it's not even
clear that M1 as it stands can get out the door give
On 15/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
Yes, it can be long. But those are the rules by which we must abide
under Apache. As Rajith points out in a separate email, it's not even
clear that M1 as it stands can get out the door given its dependency
on an unreleased version of mina.
I completely agree with Robert's statements here.
John
On 15/11/06, Robert Greig <[EMAIL PROTECTED]> wrote:
On 15/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
>
> Carl, the better question is, "Why would you want do that?"
As an example: Martin and I have been working on enhancements to M
[ http://issues.apache.org/jira/browse/QPID-98?page=all ]
Gordon Sim updated QPID-98:
---
Affects Version/s: M2
> implement durable exchanges
> ---
>
> Key: QPID-98
> URL: http://issues.apache.org/jira/brows
[ http://issues.apache.org/jira/browse/QPID-41?page=all ]
Gordon Sim updated QPID-41:
---
Affects Version/s: M2
> Persistent storage for messages & durable queues
>
>
> Key: QPID-41
>
[ http://issues.apache.org/jira/browse/QPID-40?page=all ]
Gordon Sim updated QPID-40:
---
Fix Version/s: M2
(was: M1)
> Implement tx.select, tx.commit & tx.rollback from AMQP
> --
>
>
On 16/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
What is somewhat ironic to me is that you guys see no harm into
reaching into upstream svn repositories for artifacts, yet you insist
on doing a whole M1 release for this existing customer. Since
grabbing directly from svn is OK in your book,
On Thursday November 16 2006 10:23 am, Gordon Sim wrote:
> > Most of the "legal mumbo jumbo" is to help Carlos.Carlos has a
> > script that runs on the maven upload things. If all the legal stuff
> > is met, the script runs automatically and he doesn't have to do
> > anything. If the script
Daniel Kulp wrote:
Gordon,
On Thursday November 16 2006 4:26 am, Gordon Sim wrote:
Can we put third party artifacts (whose license is acceptable to ASF)
into a maven repository?
E.g. if we wanted to use evs4j for clustering
(http://freshmeat.net/projects/evs4j/, apache license 2.0), can we
upl
On Thursday November 16 2006 10:03 am, Daniel Kulp wrote:
> Yep. Basically, we would create a pom.xml that accurate describes the
> jar. The pom would have to include the licenses section, URL, proper
> dependencies (if any) and stuff like that. You would then zip up
> the pom.xml, the jar
On Nov 16, 2006, at 4:14 AM, Robert Greig wrote:
On 15/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
> However, we don't know for sure when MINA will decide to adopt the
> patch. They may have competing priorities for their release.
Right. So one avenue open to you is to lobby them to prepa
[ http://issues.apache.org/jira/browse/QPID-103?page=all ]
Tejeswar Das reassigned QPID-103:
-
Assignee: Tejeswar Das
> Implement support for MessageListener interface
> ---
>
> Key: QPID-103
>
[ http://issues.apache.org/jira/browse/QPID-101?page=all ]
Tejeswar Das reassigned QPID-101:
-
Assignee: Tejeswar Das
> Add Queue Browsing feature to Java client (AMQSession)
> --
>
> Key
Gordon,
On Thursday November 16 2006 4:26 am, Gordon Sim wrote:
> Daniel Kulp wrote:
> > On Wednesday November 15 2006 2:23 pm, Carl Trieloff wrote:
> >> This is key as for most projects. everything that we use might
> >> not/will not be in a maven repository. How is this best handled with
> >> m
Hi All,
I have raised a few JMS compliance related items in JIRA today - off the
back of my knowledge of the code base as it currently stands.
(See QPID-101, 102, 103).
Sadly, there are sure to be more :-(
Wanted to highlight these items as they do, imho, offer a good opportunity
to get famili
[
http://issues.apache.org/jira/browse/QPID-39?page=comments#action_12450414 ]
Marnie McCormack commented on QPID-39:
--
Steve - could you update this with info on the restructure changes you've added
when appropriate please ? Thanks !
> Res
[ http://issues.apache.org/jira/browse/QPID-55?page=all ]
Marnie McCormack resolved QPID-55.
--
Resolution: Fixed
Resolving as obsolete/resolved by infrastructure.
> Links from old MoinMoin wiki pages to new Confluence wiki pages are broken
> ---
[ http://issues.apache.org/jira/browse/QPID-93?page=all ]
Bhupendra Bhardwaj resolved QPID-93.
Resolution: Fixed
old management modules removed.
> Delete the old management modules (trunk\qpid\java\management)
> -
Implement support for MessageListener interface
---
Key: QPID-103
URL: http://issues.apache.org/jira/browse/QPID-103
Project: Qpid
Issue Type: Bug
Components: Java Client
Repo
[ http://issues.apache.org/jira/browse/QPID-102?page=all ]
Marnie McCormack reassigned QPID-102:
-
Assignee: Robert Greig
> Provide support for StreamMessage in Java client (AMQSession)
> -
>
Provide support for StreamMessage in Java client (AMQSession)
-
Key: QPID-102
URL: http://issues.apache.org/jira/browse/QPID-102
Project: Qpid
Issue Type: Bug
Components:
Add Queue Browsing feature to Java client (AMQSession)
--
Key: QPID-101
URL: http://issues.apache.org/jira/browse/QPID-101
Project: Qpid
Issue Type: Bug
Components: Java Client
[ http://issues.apache.org/jira/browse/QPID-82?page=all ]
Rajith Attapattu resolved QPID-82.
--
Resolution: Fixed
The keys have been added the KEYS file and checked into svn
> Create keys ready for singing the release
> --
Martin,
Please make all changes on the branch as well.
We are making the release from the branch.
Regards,
Rajith
On 11/16/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:
The updated build.xml is now in the trunk and should address both
points 1 and 5 of Brian's email.
On 16/11/06, Martin Rit
[ http://issues.apache.org/jira/browse/QPID-99?page=all ]
Marnie McCormack reassigned QPID-99:
Assignee: Steven Shaw
> Update web pages to include wiki content
>
>
> Key: QPID-99
>
[ http://issues.apache.org/jira/browse/QPID-100?page=all ]
Marnie McCormack reassigned QPID-100:
-
Assignee: Marnie McCormack
> Enhance example classes in client/test/example
> --
>
> Key: QP
Enhance example classes in client/test/example
--
Key: QPID-100
URL: http://issues.apache.org/jira/browse/QPID-100
Project: Qpid
Issue Type: Improvement
Components: Java Client
Update web pages to include wiki content
Key: QPID-99
URL: http://issues.apache.org/jira/browse/QPID-99
Project: Qpid
Issue Type: Improvement
Reporter: Marnie McCormack
The Qpid web page
[ http://issues.apache.org/jira/browse/QPID-82?page=all ]
Marnie McCormack reassigned QPID-82:
Assignee: Rajith Attapattu
> Create keys ready for singing the release
> -
>
> Key: QPID-82
>
Daniel Kulp wrote:
On Wednesday November 15 2006 2:23 pm, Carl Trieloff wrote:
This is key as for most projects. everything that we use might not/will
not be in a maven repository. How is this best handled with maven?
Get the artifacts into the repository. From an apache standpoint, all
t
The updated build.xml is now in the trunk and should address both
points 1 and 5 of Brian's email.
On 16/11/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:
Thanks Gordon I just realised that was what Brian was referring to.
I also realised that windows has been creating the initial directory
for
On 15/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
> However, we don't know for sure when MINA will decide to adopt the
> patch. They may have competing priorities for their release.
Right. So one avenue open to you is to lobby them to prepare a
release, just as you lobby them to accept desi
Thanks Gordon I just realised that was what Brian was referring to.
I also realised that windows has been creating the initial directory
for me. I thought the files were all included in a directory so I have
adjusted that aswell.
On 16/11/06, Gordon Sim <[EMAIL PROTECTED]> wrote:
Martin Ritchie
Martin Ritchie wrote:
Brian,
What version of ant were you using? I just checked out M1 and did
ant
ant std-release
and everything worked fine.
I'm using ant 1.6.5 with java 1.5.0_08 on XP.
I don't believe I have any local peculiarities that would impact the
builds.
My only thoughts are that t
Hi All,
On the jython front - I'll remove the entry in notice for it as since the
management modules were removed last night it is (as Brian spotted) no
longer in use !
Thanks,
Marnie
On 11/16/06, Marnie McCormack <[EMAIL PROTECTED]> wrote:
Hi Rajith & Brian,
I don't *think* there is anythi
Brian,
What version of ant were you using? I just checked out M1 and did
ant
ant std-release
and everything worked fine.
I'm using ant 1.6.5 with java 1.5.0_08 on XP.
I don't believe I have any local peculiarities that would impact the builds.
My only thoughts are that the systests where not che
Hi Rajith & Brian,
I don't *think* there is anything in the CTS license that is an issue. I
hadn't appreciated that the 'All Rights Reserved' line in the copyright was
an issue for us ?
Cliff - could you kindly take a look and advise for us please - the license
info is at:
http://jmscts.sourcef
52 matches
Mail list logo
