On Dec 8, 2007 6:44 PM, sebb <[EMAIL PROTECTED]> wrote:
>
> On 20/11/2007, Phil Steitz <[EMAIL PROTECTED]> wrote:
> > On Nov 20, 2007 2:30 AM, Jörg Schaible
> > <[EMAIL PROTECTED]> wrote:
> > > Phil Steitz wrote:
> > > > On Nov 19, 2007 11:46 PM, Jörg Schaible
> > > > <[EMAIL PROTECTED]> wrote:
> >
On 20/11/2007, Phil Steitz <[EMAIL PROTECTED]> wrote:
> On Nov 20, 2007 2:30 AM, Jörg Schaible
> <[EMAIL PROTECTED]> wrote:
> > Phil Steitz wrote:
> > > On Nov 19, 2007 11:46 PM, Jörg Schaible
> > > <[EMAIL PROTECTED]> wrote:
> > >>
> > >> Phil Steitz wrote:
> > [snip]
> > >>> Any other comments on
On 09/12/2007, Phil Steitz <[EMAIL PROTECTED]> wrote:
> On Dec 8, 2007 6:01 PM, sebb <[EMAIL PROTECTED]> wrote:
> > On 09/12/2007, Phil Steitz <[EMAIL PROTECTED]> wrote:
> >
> > > On Dec 8, 2007 5:28 PM, sebb <[EMAIL PROTECTED]> wrote:
> > > > What is poll 1.4-SNAPSHOT built from? I could not find
On Dec 8, 2007 6:01 PM, sebb <[EMAIL PROTECTED]> wrote:
> On 09/12/2007, Phil Steitz <[EMAIL PROTECTED]> wrote:
>
> > On Dec 8, 2007 5:28 PM, sebb <[EMAIL PROTECTED]> wrote:
> > > What is poll 1.4-SNAPSHOT built from? I could not find a tag/branch for
> > > it.
> > >
> >
> > It is built from svn t
On 09/12/2007, Phil Steitz <[EMAIL PROTECTED]> wrote:
> On Dec 8, 2007 5:28 PM, sebb <[EMAIL PROTECTED]> wrote:
> > What is poll 1.4-SNAPSHOT built from? I could not find a tag/branch for it.
> >
>
> It is built from svn trunk. We should probably move the composite
> package to a new 2.0 branch or
On Dec 8, 2007 5:28 PM, sebb <[EMAIL PROTECTED]> wrote:
> What is poll 1.4-SNAPSHOT built from? I could not find a tag/branch for it.
>
It is built from svn trunk. We should probably move the composite
package to a new 2.0 branch or start a 1.4 release branch.
> If it is trunk, then there might
What is poll 1.4-SNAPSHOT built from? I could not find a tag/branch for it.
If it is trunk, then there might be a problem as there seem to be
several Java 1.5 dependencies (asserts).
On 09/12/2007, Phil Steitz <[EMAIL PROTECTED]> wrote:
> Anyone have any problems with this change as we work towar
Anyone have any problems with this change as we work toward pool 1.4
and dbcp 1.3 concurrently?
Phil
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 08/12/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> On 12/8/07, sebb <[EMAIL PROTECTED]> wrote:
> > On 08/12/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
>
> > >
> > > I've been adding clirr reports after the fact (running clirr at
> > > command line) so folks can glance at changes. I agre
On 12/8/07, sebb <[EMAIL PROTECTED]> wrote:
> On 08/12/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> >
> > I've been adding clirr reports after the fact (running clirr at
> > command line) so folks can glance at changes. I agree it would be good
> > to add a report to the site, I'll need to loo
On 08/12/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> Thanks a lot for the feedback. Replies below ...
>
> On 12/8/07, sebb <[EMAIL PROTECTED]> wrote:
> > On 08/12/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > > Tag:
> > >
> > > http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SC
Thanks a lot for the feedback. Replies below ...
On 12/8/07, sebb <[EMAIL PROTECTED]> wrote:
> On 08/12/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > Tag:
> >
> > http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SCXML_0_7_RC1/
> >
> > Artifacts:
> >
> > http://people.apache.org/~ra
On 08/12/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> Tag:
>
> http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SCXML_0_7_RC1/
>
> Artifacts:
>
> http://people.apache.org/~rahul/commons/scxml-0.7/rc1/
There's a clirr report here - does that not belong under the site structure?
Also
Tag:
http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SCXML_0_7_RC1/
Artifacts:
http://people.apache.org/~rahul/commons/scxml-0.7/rc1/
Staged site:
http://people.apache.org/~rahul/commons/scxml-0.7/rc1/site/
Notes:
* m1 release, JDK 1.4 minimum
* v0.7 release notes, Javadoc etc.
On 12/7/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
>
> For releases support artifacts that reside only in the Central repo
> (parent poms, skin) I have simply done:
> - vote based on svn revisions
> - mvn release:prepare
> - mvn -Prelease release:perform
>
This makes sense. However, I think
On 12/7/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>
> OK how about I just upload the artifacts manually - that seems the
> simpest solution.
Sounds good. Do the jars contain LICENSE / NOTICE files? Just saw that
skin-1.0 jars do not!
> Then we can do a commons-parent release removing the
Hi,
(I am not an active CLI committer, but have some interest in this
component.)
The best way of providing patches is by creating a new ticket in our bug
tracking system Jira [1]. This guarantees that the stuff won't get lost
in the high traffic of the mailing list.
Thanks
Oliver
[1] http://co
17 matches
Mail list logo