incubator-sanselan-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Matthew Chen" <charlesmc...@gmail.com>
Subject Re: New non-Apache Sanselan release
Date Sat, 26 Jan 2008 06:35:48 GMT
+1 to both points.

thanks,
   charles.


On Jan 25, 2008 1:58 PM, Craig L Russell <Craig.Russell@sun.com> 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:
> >>        <dependency>
> >>            <groupId>org.apache.sanselan</groupId>
> >>            <artifactId>sanselan</artifactId>
> >>            <version>1.0.0-SNAPSHOT</version>
> >>        </dependency>
> >>>
> >>>
> >>>  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!
>
>

Mime
View raw message