Olivier, if you have a link to a JIRA issue for the NPE I would be more than
happy to take a look at it.

-Ryan



On Sun, Feb 27, 2011 at 10:37 AM, Ryan Connolly <[email protected]> wrote:

> Oh ok.. anything I can do to help just let me know.
>
> Thanks,
> -Ryan
> On Feb 25, 2011 4:47 PM, "Olivier Lamy" <[email protected]> wrote:
> > An other user has reported a NPE to me so I have to fix that first.
> >
> > Thanks
> > --
> > Olivier Lamy
> > http://twitter.com/olamy
> > http://www.linkedin.com/in/olamy
> >
> > 2011/2/24 Ryan Connolly <[email protected]>:
> >> Olivier:  My team mates and I have been using the 1.2-SNAPSHOT daily.
>  Any
> >> plans to cut a release in the near future?
> >> Thanks,
> >> -Ryan
> >>
> >>
> >> On Mon, Feb 7, 2011 at 1:56 PM, Ryan Connolly <[email protected]> wrote:
> >>>
> >>> Olivier:
> >>> Please see the new patch "MTOMCAT-15-checks-contextXml.patch" attached
> >>> to http://jira.codehaus.org/browse/MTOMCAT-15
> >>> This patch will check context.xml should one exist for reloadable
> >>> configuration.  If context.xml is not supplied, tomcat:run will use
> context
> >>> reloading by default.
> >>>
> >>> Thanks again,
> >>> -Ryan
> >>>
> >>>
> >>> On Sat, Feb 5, 2011 at 7:51 PM, Ryan Connolly <[email protected]>
> wrote:
> >>>>
> >>>> Olivier,
> >>>> Thanks for the quick reply and willingness to get this feature
> >>>> introduced!  I was unaware of the upcoming move to Apache but it only
> makes
> >>>> sense that this is happening.  Sounds like a good move to me.
> >>>> In regards to the CLA, I've emailed this to your apache.org address.
> >>>> Thanks again!
> >>>> -Ryan Connolly
> >>>>
> >>>>
> >>>> On Sat, Feb 5, 2011 at 4:46 PM, Olivier Lamy <[email protected]>
> wrote:
> >>>>>
> >>>>> Hello,
> >>>>>
> >>>>> We are in the process about moving this mojo to ASF see [1].
> >>>>> So I can certainly push a 1.1.1 release.
> >>>>> But so if you provide a patch and as the code will move to ASF I will
> >>>>> need a cla from you (see [2])
> >>>>> Thanks,
> >>>>> --
> >>>>> Olivier Lamy
> >>>>> http://twitter.com/olamy
> >>>>> http://www.linkedin.com/in/olamy
> >>>>> [1]
> >>>>>
> http://markmail.org/search/?q=mojo+dev+tomcat#query:mojo%20dev%20tomcat+page:1+mid:brxxc37rozz6kyf4+state:results
> >>>>> [2] http://apache.org/licenses/icla.txt
> >>>>>
> >>>>> 2011/2/5 Ryan Connolly <[email protected]>:
> >>>>> > I have updated the patch in
> >>>>> > http://jira.codehaus.org/browse/MTOMCAT-15 to
> >>>>> > work with the current state of trunk as it was created in '08 and
> >>>>> > closed the
> >>>>> > below mentioned issue as a duplicate of the aforementioned.  Any
> >>>>> > chance of
> >>>>> > getting this into 1.2?
> >>>>> > Thanks,
> >>>>> > -Ryan
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> > On Sat, Feb 5, 2011 at 7:14 AM, Ryan Connolly <[email protected]>
> >>>>> > wrote:
> >>>>> >>
> >>>>> >> Hello!
> >>>>> >>      I was hoping to illicit some opinions from tomcat-m-p
> developers
> >>>>> >> regarding the possibility of fixing the context reloading in the
> >>>>> >> tomcat:run
> >>>>> >> goal.  I've created a JIRA
> >>>>> >> (http://jira.codehaus.org/browse/MTOMCAT-76) for
> >>>>> >> the feature request and would be most happy to contribute a patch
> (or
> >>>>> >> two).
> >>>>> >>  I guess I'm hoping to get some input on the likelihood of getting
> >>>>> >> this
> >>>>> >> implemented as well as opinions on how best to approach the issue
> as
> >>>>> >> I'm
> >>>>> >> sure the project owners would have a preference as to how this
> should
> >>>>> >> be
> >>>>> >> implemented.  Looking forward to any and all feedback on the
> issue.
> >>>>> >> Thanks in advance!
> >>>>> >> -Ryan Connolly
> >>>>> >
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe from this list, please visit:
> >>>>>
> >>>>>    http://xircles.codehaus.org/manage_email
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
>

Reply via email to