On Nov 9, 2006, at 1:47 AM, Steven Shaw wrote:
I'd personally prefer to see those release-doc files up at the root of
the tree (but I can see the other point of view that says that my
position makes the root "untidy"). It does seem pretty typical to see
them at the top of the tree...
We have had
I'd personally prefer to see those release-doc files up at the root of
the tree (but I can see the other point of view that says that my
position makes the root "untidy"). It does seem pretty typical to see
them at the top of the tree...
We have had some Ant "problems" with spaces and shell scrip
On Nov 8, 2006, at 7:07 PM, Martin Ritchie wrote:
I don't agree that spaces are that hard to deal with
C'mon, let's be realistic. Ever see any book by Brian Kernighan or
any other UNIX guru that recommends creating pathnames containing
spaces? No, because there's a reason for that. I guaran
I don't agree that spaces are that hard to deal with but I agree that
it should be change. I'm not usually one to create folders with
spaces. A hazard of using a GUI. If you change it back before the
morning then the releasesrc build target needs to be updated.
On 08/11/06, Steve Vinoski <[EMAIL
I noticed that in the java subdirectory today, somebody committed a
new directory named "Release Docs" under the doc directory. Let's
please change that to "release-docs" or something like that, as
pathnames containing spaces are just generally very hard to deal with
in automated tools and
Just FYI: those libs need to be removed from SVN, thus it can package all
libs as only the allowable ones will be in SVN.
When the incubator folks look at things, the ALSO look at the tag in svn.
If they see those things there, it's still a -1 vote and not allowed to
release.
Dan
On Wedn
Created target "releasesrc" that will create a source release but it
still includes libs that are not allowed AFAIK.
Do we want to exclude all libs or just those that are incompatible
with the Apache license.
On 08/11/06, Martin Ritchie (JIRA) wrote:
Create source distribtuion using build syst
[
http://issues.apache.org/jira/browse/QPID-74?page=comments#action_12448209 ]
Martin Ritchie commented on QPID-74:
Created target "releasesrc" that will create a source release but it still
includes libs that are not allowed.
> Create sou
[
http://issues.apache.org/jira/browse/QPID-73?page=comments#action_12448197 ]
Martin Ritchie commented on QPID-73:
Something more like:
qpid-java-1.0-incubator-M1-src.zip
> Create Build Artifacts for release process using ant/maven
> ---
[
http://issues.apache.org/jira/browse/QPID-73?page=comments#action_12448191 ]
Stephen Vinoski commented on QPID-73:
-
Actually, I don't think the prefix "apache-" should appear in the artifact
names. If you look around at other projects, the
Queue.Delete does not implement specification
-
Key: QPID-76
URL: http://issues.apache.org/jira/browse/QPID-76
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter:
Create source distribtuion using build system
-
Key: QPID-74
URL: http://issues.apache.org/jira/browse/QPID-74
Project: Qpid
Issue Type: Task
Components: Ant Build System
Repo
[ http://issues.apache.org/jira/browse/QPID-73?page=all ]
Martin Ritchie updated QPID-73:
---
Issue Type: Task (was: Improvement)
> Create Build Artifacts for release process using ant/maven
> --
>
>
Create Standard Binary distribution using build system
--
Key: QPID-75
URL: http://issues.apache.org/jira/browse/QPID-75
Project: Qpid
Issue Type: Task
Components: Ant Build Syste
[
http://issues.apache.org/jira/browse/QPID-73?page=comments#action_12448176 ]
Martin Ritchie commented on QPID-73:
Extra files in Meta-inf
--
In the META-INF dir of each jar, you also need to have a DISCLA
Create Build Artifacts for release process using ant/maven
--
Key: QPID-73
URL: http://issues.apache.org/jira/browse/QPID-73
Project: Qpid
Issue Type: Improvement
Components:
[ http://issues.apache.org/jira/browse/QPID-72?page=all ]
Steven Shaw resolved QPID-72.
-
Resolution: Fixed
Set module.dist back to false for the client-test module.
> Client tests should not be included in the binary release
> --
[ http://issues.apache.org/jira/browse/QPID-39?page=all ]
Martin Ritchie reassigned QPID-39:
--
Assignee: (was: Martin Ritchie)
> Restructure Java Client test package
>
>
> Key: QPID-39
>
[ http://issues.apache.org/jira/browse/QPID-72?page=all ]
Steven Shaw reassigned QPID-72:
---
Assignee: Steven Shaw
> Client tests should not be included in the binary release
> -
>
> Key
Client tests should not be included in the binary release
-
Key: QPID-72
URL: http://issues.apache.org/jira/browse/QPID-72
Project: Qpid
Issue Type: Task
Components: Java Clie
[ http://issues.apache.org/jira/browse/QPID-71?page=all ]
Martin Ritchie updated QPID-71:
---
Component/s: Java Client
> ConnectionURL Not parsed correctly under Java 1.6
> -
>
> Key: QPID-71
>
ConnectionURL Not parsed correctly under Java 1.6
-
Key: QPID-71
URL: http://issues.apache.org/jira/browse/QPID-71
Project: Qpid
Issue Type: Bug
Reporter: Martin Ritchie
InVM Broker has no authentication
-
Key: QPID-70
URL: http://issues.apache.org/jira/browse/QPID-70
Project: Qpid
Issue Type: New Feature
Components: Java Broker
Reporter: Martin Ritchie
Daniel Kulp wrote:
+1 to maven as well.. :-)
There is also the jbossall-client.jar in the source tree. I believe that
is LGPL or part LGPL, also not allowed as part of a distribution at
apache.
I understand that we may have these licenses in the tool chain or test
suite, but they can't
[
http://issues.apache.org/jira/browse/QPID-39?page=comments#action_12448128 ]
Martin Ritchie commented on QPID-39:
The main unit tests have been moved to package test/unit
There are a couple of tests that were not previously included in the
[ http://issues.apache.org/jira/browse/QPID-39?page=all ]
Martin Ritchie reassigned QPID-39:
--
Assignee: Martin Ritchie
> Restructure Java Client test package
>
>
> Key: QPID-39
> URL:
On 08/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
After the flurry of commits yesterday, I'm seeing the client tests
hang with an error about being unable to connect to the broker (see
below). Anyone else seeing the same?
I've just looked at our continuous build system which is still runnin
On 08/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
After the flurry of commits yesterday, I'm seeing the client tests
hang with an error about being unable to connect to the broker (see
below). Anyone else seeing the same?
--steve
[junit] 2006-11-08 00:08:45,746 INFO [pool-9-thread-3]
h
28 matches
Mail list logo
