From sanselan-dev-return-127-apmail-incubator-sanselan-dev-archive=incubator.apache.org@incubator.apache.org Fri Feb 01 07:22:26 2008 Return-Path: Delivered-To: apmail-incubator-sanselan-dev-archive@locus.apache.org Received: (qmail 95324 invoked from network); 1 Feb 2008 07:22:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Feb 2008 07:22:26 -0000 Received: (qmail 21933 invoked by uid 500); 1 Feb 2008 07:22:18 -0000 Delivered-To: apmail-incubator-sanselan-dev-archive@incubator.apache.org Received: (qmail 21909 invoked by uid 500); 1 Feb 2008 07:22:18 -0000 Mailing-List: contact sanselan-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: sanselan-dev@incubator.apache.org Delivered-To: mailing list sanselan-dev@incubator.apache.org Received: (qmail 21900 invoked by uid 99); 1 Feb 2008 07:22:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2008 23:22:17 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 01 Feb 2008 07:22:11 +0000 Received: (qmail 94934 invoked from network); 1 Feb 2008 07:22:02 -0000 Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; 1 Feb 2008 07:22:02 -0000 Message-ID: <47A2C899.4010809@apache.org> Date: Fri, 01 Feb 2008 08:22:01 +0100 From: Carsten Ziegeler User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: sanselan-dev@incubator.apache.org Subject: Re: New non-Apache Sanselan release References: <43B5A00D-9CA1-4573-B197-BBEE46BF3320@SUN.com> <479A2103.6090403@apache.org> <2A0D3CFB-7E24-4057-9906-1094432A8C7A@SUN.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Charles Matthew Chen wrote: > On reflection, I think we should make the test data separate from > the unit tests. Not all of the unit tests use the test data. > Moreover, the test data is quite large (and will hopefully continue to > grow). > I'm not exactly sure what you mean by separating? I hope to make a test run for building a release sometime next week, so we can all have a look and see which things are missing/need to change in terms of a distribution. Carsten > Charles. > > On Jan 26, 2008 1:35 AM, Charles Matthew Chen wrote: >> +1 to both points. >> >> thanks, >> charles. >> >> >> >> On Jan 25, 2008 1:58 PM, Craig L Russell wrote: >>> On Jan 25, 2008, at 9:48 AM, Carsten Ziegeler wrote: >>> >>>> Hi, >>>> >>>> as we are using maven to build sanselan, we get this for free; the >>>> only extra work we have to do later on is to put the maven artifact >>>> (the jar and the pom) into the maven repository (but that's fairly >>>> simple). >>> +1 >>>> >>>> For the download distribution I don't think we should add the wiki >>>> docs itself as this might give us some legal headaches right now - >>>> everyone who wrote something on the wiki needs to have a signed CLA >>>> on file *if* we include this in our releases. I think a link to the >>>> wiki is enough - at least for a first step. >>> RIght. I don't see a need to put wiki content into the releases. >>> >>> Craig >>> >>>> >>>> Regards >>>> Carsten >>>> >>>> Craig L Russell wrote: >>>>> Hi Charles, >>>>> On Jan 24, 2008, at 9:32 PM, Charles Matthew Chen wrote: >>>>>> Hi Craig, >>>>>> >>>>>> I'm not really familiar with that option. Can you elaborate or >>>>>> perhaps share a url? >>>>> http://maven.apache.org is the starting point for information. I've >>>>> been using maven for a while now and it's very popular among open >>>>> source projects. In order to use sanselan in a project, all you >>>>> need to do is to include a few lines of code in an xml file and >>>>> you're done. Maven will download the jar file and include it in >>>>> your build and run environments. >>>>> For example, to use sanselan in another project, you'd declare this >>>>> in your configuration file: >>>>> >>>>> org.apache.sanselan >>>>> sanselan >>>>> 1.0.0-SNAPSHOT >>>>> >>>>>> >>>>>> What trade-offs do we face in this decision? >>>>> It's just a bit more work setting up the publication of the jar >>>>> file in the maven repository. All the usual due diligence is still >>>>> required to prepare the jar file for publication. >>>> >>>> -- >>>> Carsten Ziegeler >>>> cziegeler@apache.org >>> >>> Craig Russell >>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo >>> 408 276-5638 mailto:Craig.Russell@sun.com >>> P.S. A good JDO? O, Gasp! >>> >>> > -- Carsten Ziegeler cziegeler@apache.org