You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by Lawrence Mandel <lm...@ca.ibm.com> on 2005/12/07 00:24:29 UTC
Problem with WS Commons
I found a problem in XmlSchema which I'd like to fix but found that I
don't have access to the repository. This lead me to what I think is a
larger problem with the WS Commons projects. There is no information about
these projects on the WS site, no bug tracking system, no regular builds,
and no developers (publically) committed to this code.
If we're to continue to have WS commons projects I'd like to suggest that
either these be transformed into WS projects with their own sites, jira,
etc., or that a page be added to the WS site that explains these common
projects and provides references to the projects that own these common
projects. (I'd still like to see public builds of these projects that
other projects, such as Woden, can depend on.)
Comments? Is someone already looking into some of these issues? If I'm way
off here because I've missed some information please correct me. If this
is the case we may just need to make the information more visible.
Thanks,
Lawrence Mandel
Re: Problem with WS Commons
Posted by Davanum Srinivas <da...@gmail.com>.
Perfect!!! thanks.
On 12/12/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> To follow up, turns out I do have the appropriate write permissions. There was a problem with my configuration. I've committed my fix to XmlSchema.
>
> Lawrence Mandel
>
>
>
>
> Davanum Srinivas <da...@gmail.com>
>
> 12/07/2005 07:36 AM
>
> Please respond to
> general
>
>
>
> To woden-dev@ws.apache.org
>
> cc general@ws.apache.org
>
> Subject Re: Problem with WS Commons
>
>
>
>
>
>
>
>
> Lawrence,
>
> All WS folks have write privs to ws-commons. If you are unable to
> commit your changes, give me a holler.
>
> Yes, we need to define a process like that. XmlSchema has been
> languishing in obscurity for years now it was in the scratch area for
> Axis 1.X and only now have we been pushing its use with Axis2 and
> Woden.
>
> Website is easy, just like the woden site, you can add contents to svn
> (site under https://svn.apache.org/repos/asf/webservices/) and do a
> svn checkout under (/www/ws.apache.org/commons/) on minotaur to
> publish it.
>
> Please send me your jira id, i'll make u an admin.
>
> For mailing lists, please open a jira request for infrastrastructure
> and follow up with email to infrastructure AT apache.org.
>
> thanks,
> dims
>
> On 12/7/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> >
> > Dims,
> >
> > Do you know who I should speak to about obtaining write access to that repository?
> >
> > The snapshots are really just head builds. Can we define a process where more stable builds are declared on a semi-regular basis?
> >
> > WRT my other suggestions, once I get a few spare minutes I will look into creating a WS commons virtual component complete with a site, Jira, and mailing lists. I'll post back to general@ws once I have a chance to look into this. If anyone else has time I'd be happy to get some help.
> >
> > Lawrence Mandel
> >
> >
> >
> >
> > Davanum Srinivas <da...@gmail.com>
> >
> > 12/06/2005 11:02 PM
> >
> > Please respond to
> > woden-dev
> >
> >
> > To woden-dev@ws.apache.org
> >
> > cc general@ws.apache.org
> >
> > Subject Re: Problem with WS Commons
> >
> >
> >
> >
> >
> >
> >
> >
> > Lawrence,
> >
> > - You should have write access to that repo.
> > - Snapshots are published every 6 hours
> > (http://cvs.apache.org/repository/ws-commons/jars/)
> >
> > +1 to do all the things that you mentioned. Please feel free to take
> > ownership of the bits where you can help.
> >
> > thanks,
> > dims
> >
> >
> > On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> > >
> > > I found a problem in XmlSchema which I'd like to fix but found that I don't
> > > have access to the repository. This lead me to what I think is a larger
> > > problem with the WS Commons projects. There is no information about these
> > > projects on the WS site, no bug tracking system, no regular builds, and no
> > > developers (publically) committed to this code.
> > >
> > > If we're to continue to have WS commons projects I'd like to suggest that
> > > either these be transformed into WS projects with their own sites, jira,
> > > etc., or that a page be added to the WS site that explains these common
> > > projects and provides references to the projects that own these common
> > > projects. (I'd still like to see public builds of these projects that other
> > > projects, such as Woden, can depend on.)
> > >
> > > Comments? Is someone already looking into some of these issues? If I'm way
> > > off here because I've missed some information please correct me. If this is
> > > the case we may just need to make the information more visible.
> > >
> > > Thanks,
> > >
> > > Lawrence Mandel
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: woden-dev-help@ws.apache.org
> >
> >
> >
>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Problem with WS Commons
Posted by Davanum Srinivas <da...@gmail.com>.
Perfect!!! thanks.
On 12/12/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> To follow up, turns out I do have the appropriate write permissions. There was a problem with my configuration. I've committed my fix to XmlSchema.
>
> Lawrence Mandel
>
>
>
>
> Davanum Srinivas <da...@gmail.com>
>
> 12/07/2005 07:36 AM
>
> Please respond to
> general
>
>
>
> To woden-dev@ws.apache.org
>
> cc general@ws.apache.org
>
> Subject Re: Problem with WS Commons
>
>
>
>
>
>
>
>
> Lawrence,
>
> All WS folks have write privs to ws-commons. If you are unable to
> commit your changes, give me a holler.
>
> Yes, we need to define a process like that. XmlSchema has been
> languishing in obscurity for years now it was in the scratch area for
> Axis 1.X and only now have we been pushing its use with Axis2 and
> Woden.
>
> Website is easy, just like the woden site, you can add contents to svn
> (site under https://svn.apache.org/repos/asf/webservices/) and do a
> svn checkout under (/www/ws.apache.org/commons/) on minotaur to
> publish it.
>
> Please send me your jira id, i'll make u an admin.
>
> For mailing lists, please open a jira request for infrastrastructure
> and follow up with email to infrastructure AT apache.org.
>
> thanks,
> dims
>
> On 12/7/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> >
> > Dims,
> >
> > Do you know who I should speak to about obtaining write access to that repository?
> >
> > The snapshots are really just head builds. Can we define a process where more stable builds are declared on a semi-regular basis?
> >
> > WRT my other suggestions, once I get a few spare minutes I will look into creating a WS commons virtual component complete with a site, Jira, and mailing lists. I'll post back to general@ws once I have a chance to look into this. If anyone else has time I'd be happy to get some help.
> >
> > Lawrence Mandel
> >
> >
> >
> >
> > Davanum Srinivas <da...@gmail.com>
> >
> > 12/06/2005 11:02 PM
> >
> > Please respond to
> > woden-dev
> >
> >
> > To woden-dev@ws.apache.org
> >
> > cc general@ws.apache.org
> >
> > Subject Re: Problem with WS Commons
> >
> >
> >
> >
> >
> >
> >
> >
> > Lawrence,
> >
> > - You should have write access to that repo.
> > - Snapshots are published every 6 hours
> > (http://cvs.apache.org/repository/ws-commons/jars/)
> >
> > +1 to do all the things that you mentioned. Please feel free to take
> > ownership of the bits where you can help.
> >
> > thanks,
> > dims
> >
> >
> > On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> > >
> > > I found a problem in XmlSchema which I'd like to fix but found that I don't
> > > have access to the repository. This lead me to what I think is a larger
> > > problem with the WS Commons projects. There is no information about these
> > > projects on the WS site, no bug tracking system, no regular builds, and no
> > > developers (publically) committed to this code.
> > >
> > > If we're to continue to have WS commons projects I'd like to suggest that
> > > either these be transformed into WS projects with their own sites, jira,
> > > etc., or that a page be added to the WS site that explains these common
> > > projects and provides references to the projects that own these common
> > > projects. (I'd still like to see public builds of these projects that other
> > > projects, such as Woden, can depend on.)
> > >
> > > Comments? Is someone already looking into some of these issues? If I'm way
> > > off here because I've missed some information please correct me. If this is
> > > the case we may just need to make the information more visible.
> > >
> > > Thanks,
> > >
> > > Lawrence Mandel
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: woden-dev-help@ws.apache.org
> >
> >
> >
>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Problem with WS Commons
Posted by Lawrence Mandel <lm...@ca.ibm.com>.
To follow up, turns out I do have the appropriate write permissions. There
was a problem with my configuration. I've committed my fix to XmlSchema.
Lawrence Mandel
Davanum Srinivas <da...@gmail.com>
12/07/2005 07:36 AM
Please respond to
general
To
woden-dev@ws.apache.org
cc
general@ws.apache.org
Subject
Re: Problem with WS Commons
Lawrence,
All WS folks have write privs to ws-commons. If you are unable to
commit your changes, give me a holler.
Yes, we need to define a process like that. XmlSchema has been
languishing in obscurity for years now it was in the scratch area for
Axis 1.X and only now have we been pushing its use with Axis2 and
Woden.
Website is easy, just like the woden site, you can add contents to svn
(site under https://svn.apache.org/repos/asf/webservices/) and do a
svn checkout under (/www/ws.apache.org/commons/) on minotaur to
publish it.
Please send me your jira id, i'll make u an admin.
For mailing lists, please open a jira request for infrastrastructure
and follow up with email to infrastructure AT apache.org.
thanks,
dims
On 12/7/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> Dims,
>
> Do you know who I should speak to about obtaining write access to that
repository?
>
> The snapshots are really just head builds. Can we define a process where
more stable builds are declared on a semi-regular basis?
>
> WRT my other suggestions, once I get a few spare minutes I will look
into creating a WS commons virtual component complete with a site, Jira,
and mailing lists. I'll post back to general@ws once I have a chance to
look into this. If anyone else has time I'd be happy to get some help.
>
> Lawrence Mandel
>
>
>
>
> Davanum Srinivas <da...@gmail.com>
>
> 12/06/2005 11:02 PM
>
> Please respond to
> woden-dev
>
>
> To woden-dev@ws.apache.org
>
> cc general@ws.apache.org
>
> Subject Re: Problem with WS Commons
>
>
>
>
>
>
>
>
> Lawrence,
>
> - You should have write access to that repo.
> - Snapshots are published every 6 hours
> (http://cvs.apache.org/repository/ws-commons/jars/)
>
> +1 to do all the things that you mentioned. Please feel free to take
> ownership of the bits where you can help.
>
> thanks,
> dims
>
>
> On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> >
> > I found a problem in XmlSchema which I'd like to fix but found that I
don't
> > have access to the repository. This lead me to what I think is a
larger
> > problem with the WS Commons projects. There is no information about
these
> > projects on the WS site, no bug tracking system, no regular builds,
and no
> > developers (publically) committed to this code.
> >
> > If we're to continue to have WS commons projects I'd like to suggest
that
> > either these be transformed into WS projects with their own sites,
jira,
> > etc., or that a page be added to the WS site that explains these
common
> > projects and provides references to the projects that own these
common
> > projects. (I'd still like to see public builds of these projects that
other
> > projects, such as Woden, can depend on.)
> >
> > Comments? Is someone already looking into some of these issues? If
I'm way
> > off here because I've missed some information please correct me. If
this is
> > the case we may just need to make the information more visible.
> >
> > Thanks,
> >
> > Lawrence Mandel
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Problem with WS Commons
Posted by Jeremy Hughes <hu...@apache.org>.
What error are you getting?
Are you using https://svn.apache.org/repos/asf/webservices/commons/trunk/XmlSchema
as the subversion url? and using your id instead of anonymous?
Sorry some pretty dumb questions I know but they've caught me out before.
Jeremy
On 12/8/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> Hi Jeremy,
>
> Yes. You've hit the problem I did. I have a fix. Just need to clear up why I can't commit to the repository. The Woden M2 candidate does contain a patched version of XmlSchema with this fix.
>
> Lawrence Mandel
>
>
>
>
> Jeremy Hughes <jp...@gmail.com>
>
> 12/08/2005 10:53 AM
>
> Please respond to
> general
>
>
> To general@ws.apache.org, dims@apache.org
>
> cc
>
>
>
> Subject Re: Problem with WS Commons
>
>
>
>
>
>
>
>
> Hi Lawrence, I've hit a problem which may be the same as yours in
> SchemaBuilder.getDerivation(). I'm using the HEAD of XmlSchema:
>
> line 1838:
> XmlSchemaDerivationMethod getDerivation(Element el, String attrName) {
> if (el.hasAttribute(attrName)) {
> //#all | List of (extension | restriction | substitution
> String derivationMethod = el.getAttribute(attrName).trim();
> char c = Character.toUpperCase(derivationMethod.charAt(0));
> if (derivationMethod.equals("#all"))
> return new XmlSchemaDerivationMethod("All");
> else
> return new XmlSchemaDerivationMethod(c +
> derivationMethod.substring(1));
> }
> return new XmlSchemaDerivationMethod("None");
> }
>
> I get a StringIndexOutOfBoundsException because derivationMethod is
> "". Is this what you saw and wanted to commit a fix to?
>
> Just noticed that the snapshot jar of XmlSchema in the candidate for
> Woden M2 works, so I'm guessing you patched XmlSchema for that but
> haven't checked in the change yet.
>
> Regards,
> Jeremy
>
> On 12/7/05, Davanum Srinivas <da...@gmail.com> wrote:
> > Lawrence,
> >
> > All WS folks have write privs to ws-commons. If you are unable to
> > commit your changes, give me a holler.
> >
> > Yes, we need to define a process like that. XmlSchema has been
> > languishing in obscurity for years now it was in the scratch area for
> > Axis 1.X and only now have we been pushing its use with Axis2 and
> > Woden.
> >
> > Website is easy, just like the woden site, you can add contents to svn
> > (site under https://svn.apache.org/repos/asf/webservices/) and do a
> > svn checkout under (/www/ws.apache.org/commons/) on minotaur to
> > publish it.
> >
> > Please send me your jira id, i'll make u an admin.
> >
> > For mailing lists, please open a jira request for infrastrastructure
> > and follow up with email to infrastructure AT apache.org.
> >
> > thanks,
> > dims
> >
> > On 12/7/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> > >
> > > Dims,
> > >
> > > Do you know who I should speak to about obtaining write access to that repository?
> > >
> > > The snapshots are really just head builds. Can we define a process where more stable builds are declared on a semi-regular basis?
> > >
> > > WRT my other suggestions, once I get a few spare minutes I will look into creating a WS commons virtual component complete with a site, Jira, and mailing lists. I'll post back to general@ws once I have a chance to look into this. If anyone else has time I'd be happy to get some help.
> > >
> > > Lawrence Mandel
> > >
> > >
> > >
> > >
> > > Davanum Srinivas <da...@gmail.com>
> > >
> > > 12/06/2005 11:02 PM
> > >
> > > Please respond to
> > > woden-dev
> > >
> > >
> > > To woden-dev@ws.apache.org
> > >
> > > cc general@ws.apache.org
> > >
> > > Subject Re: Problem with WS Commons
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Lawrence,
> > >
> > > - You should have write access to that repo.
> > > - Snapshots are published every 6 hours
> > > (http://cvs.apache.org/repository/ws-commons/jars/)
> > >
> > > +1 to do all the things that you mentioned. Please feel free to take
> > > ownership of the bits where you can help.
> > >
> > > thanks,
> > > dims
> > >
> > >
> > > On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> > > >
> > > > I found a problem in XmlSchema which I'd like to fix but found that I don't
> > > > have access to the repository. This lead me to what I think is a larger
> > > > problem with the WS Commons projects. There is no information about these
> > > > projects on the WS site, no bug tracking system, no regular builds, and no
> > > > developers (publically) committed to this code.
> > > >
> > > > If we're to continue to have WS commons projects I'd like to suggest that
> > > > either these be transformed into WS projects with their own sites, jira,
> > > > etc., or that a page be added to the WS site that explains these common
> > > > projects and provides references to the projects that own these common
> > > > projects. (I'd still like to see public builds of these projects that other
> > > > projects, such as Woden, can depend on.)
> > > >
> > > > Comments? Is someone already looking into some of these issues? If I'm way
> > > > off here because I've missed some information please correct me. If this is
> > > > the case we may just need to make the information more visible.
> > > >
> > > > Thanks,
> > > >
> > > > Lawrence Mandel
> > > >
> > >
> > >
> > > --
> > > Davanum Srinivas : http://wso2.com/blogs/
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: woden-dev-help@ws.apache.org
> > >
> > >
> > >
> >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
>
>
Re: Problem with WS Commons
Posted by Lawrence Mandel <lm...@ca.ibm.com>.
Hi Jeremy,
Yes. You've hit the problem I did. I have a fix. Just need to clear up why
I can't commit to the repository. The Woden M2 candidate does contain a
patched version of XmlSchema with this fix.
Lawrence Mandel
Jeremy Hughes <jp...@gmail.com>
12/08/2005 10:53 AM
Please respond to
general
To
general@ws.apache.org, dims@apache.org
cc
Subject
Re: Problem with WS Commons
Hi Lawrence, I've hit a problem which may be the same as yours in
SchemaBuilder.getDerivation(). I'm using the HEAD of XmlSchema:
line 1838:
XmlSchemaDerivationMethod getDerivation(Element el, String attrName) {
if (el.hasAttribute(attrName)) {
//#all | List of (extension | restriction | substitution
String derivationMethod = el.getAttribute(attrName).trim();
char c = Character.toUpperCase(derivationMethod.charAt(0));
if (derivationMethod.equals("#all"))
return new XmlSchemaDerivationMethod("All");
else
return new XmlSchemaDerivationMethod(c +
derivationMethod.substring(1));
}
return new XmlSchemaDerivationMethod("None");
}
I get a StringIndexOutOfBoundsException because derivationMethod is
"". Is this what you saw and wanted to commit a fix to?
Just noticed that the snapshot jar of XmlSchema in the candidate for
Woden M2 works, so I'm guessing you patched XmlSchema for that but
haven't checked in the change yet.
Regards,
Jeremy
On 12/7/05, Davanum Srinivas <da...@gmail.com> wrote:
> Lawrence,
>
> All WS folks have write privs to ws-commons. If you are unable to
> commit your changes, give me a holler.
>
> Yes, we need to define a process like that. XmlSchema has been
> languishing in obscurity for years now it was in the scratch area for
> Axis 1.X and only now have we been pushing its use with Axis2 and
> Woden.
>
> Website is easy, just like the woden site, you can add contents to svn
> (site under https://svn.apache.org/repos/asf/webservices/) and do a
> svn checkout under (/www/ws.apache.org/commons/) on minotaur to
> publish it.
>
> Please send me your jira id, i'll make u an admin.
>
> For mailing lists, please open a jira request for infrastrastructure
> and follow up with email to infrastructure AT apache.org.
>
> thanks,
> dims
>
> On 12/7/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> >
> > Dims,
> >
> > Do you know who I should speak to about obtaining write access to that
repository?
> >
> > The snapshots are really just head builds. Can we define a process
where more stable builds are declared on a semi-regular basis?
> >
> > WRT my other suggestions, once I get a few spare minutes I will look
into creating a WS commons virtual component complete with a site, Jira,
and mailing lists. I'll post back to general@ws once I have a chance to
look into this. If anyone else has time I'd be happy to get some help.
> >
> > Lawrence Mandel
> >
> >
> >
> >
> > Davanum Srinivas <da...@gmail.com>
> >
> > 12/06/2005 11:02 PM
> >
> > Please respond to
> > woden-dev
> >
> >
> > To woden-dev@ws.apache.org
> >
> > cc general@ws.apache.org
> >
> > Subject Re: Problem with WS Commons
> >
> >
> >
> >
> >
> >
> >
> >
> > Lawrence,
> >
> > - You should have write access to that repo.
> > - Snapshots are published every 6 hours
> > (http://cvs.apache.org/repository/ws-commons/jars/)
> >
> > +1 to do all the things that you mentioned. Please feel free to take
> > ownership of the bits where you can help.
> >
> > thanks,
> > dims
> >
> >
> > On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> > >
> > > I found a problem in XmlSchema which I'd like to fix but found that
I don't
> > > have access to the repository. This lead me to what I think is a
larger
> > > problem with the WS Commons projects. There is no information about
these
> > > projects on the WS site, no bug tracking system, no regular builds,
and no
> > > developers (publically) committed to this code.
> > >
> > > If we're to continue to have WS commons projects I'd like to
suggest that
> > > either these be transformed into WS projects with their own sites,
jira,
> > > etc., or that a page be added to the WS site that explains these
common
> > > projects and provides references to the projects that own these
common
> > > projects. (I'd still like to see public builds of these projects
that other
> > > projects, such as Woden, can depend on.)
> > >
> > > Comments? Is someone already looking into some of these issues? If
I'm way
> > > off here because I've missed some information please correct me. If
this is
> > > the case we may just need to make the information more visible.
> > >
> > > Thanks,
> > >
> > > Lawrence Mandel
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: woden-dev-help@ws.apache.org
> >
> >
> >
>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
Re: Problem with WS Commons
Posted by Jeremy Hughes <jp...@gmail.com>.
Hi Lawrence, I've hit a problem which may be the same as yours in
SchemaBuilder.getDerivation(). I'm using the HEAD of XmlSchema:
line 1838:
XmlSchemaDerivationMethod getDerivation(Element el, String attrName) {
if (el.hasAttribute(attrName)) {
//#all | List of (extension | restriction | substitution
String derivationMethod = el.getAttribute(attrName).trim();
char c = Character.toUpperCase(derivationMethod.charAt(0));
if (derivationMethod.equals("#all"))
return new XmlSchemaDerivationMethod("All");
else
return new XmlSchemaDerivationMethod(c +
derivationMethod.substring(1));
}
return new XmlSchemaDerivationMethod("None");
}
I get a StringIndexOutOfBoundsException because derivationMethod is
"". Is this what you saw and wanted to commit a fix to?
Just noticed that the snapshot jar of XmlSchema in the candidate for
Woden M2 works, so I'm guessing you patched XmlSchema for that but
haven't checked in the change yet.
Regards,
Jeremy
On 12/7/05, Davanum Srinivas <da...@gmail.com> wrote:
> Lawrence,
>
> All WS folks have write privs to ws-commons. If you are unable to
> commit your changes, give me a holler.
>
> Yes, we need to define a process like that. XmlSchema has been
> languishing in obscurity for years now it was in the scratch area for
> Axis 1.X and only now have we been pushing its use with Axis2 and
> Woden.
>
> Website is easy, just like the woden site, you can add contents to svn
> (site under https://svn.apache.org/repos/asf/webservices/) and do a
> svn checkout under (/www/ws.apache.org/commons/) on minotaur to
> publish it.
>
> Please send me your jira id, i'll make u an admin.
>
> For mailing lists, please open a jira request for infrastrastructure
> and follow up with email to infrastructure AT apache.org.
>
> thanks,
> dims
>
> On 12/7/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> >
> > Dims,
> >
> > Do you know who I should speak to about obtaining write access to that repository?
> >
> > The snapshots are really just head builds. Can we define a process where more stable builds are declared on a semi-regular basis?
> >
> > WRT my other suggestions, once I get a few spare minutes I will look into creating a WS commons virtual component complete with a site, Jira, and mailing lists. I'll post back to general@ws once I have a chance to look into this. If anyone else has time I'd be happy to get some help.
> >
> > Lawrence Mandel
> >
> >
> >
> >
> > Davanum Srinivas <da...@gmail.com>
> >
> > 12/06/2005 11:02 PM
> >
> > Please respond to
> > woden-dev
> >
> >
> > To woden-dev@ws.apache.org
> >
> > cc general@ws.apache.org
> >
> > Subject Re: Problem with WS Commons
> >
> >
> >
> >
> >
> >
> >
> >
> > Lawrence,
> >
> > - You should have write access to that repo.
> > - Snapshots are published every 6 hours
> > (http://cvs.apache.org/repository/ws-commons/jars/)
> >
> > +1 to do all the things that you mentioned. Please feel free to take
> > ownership of the bits where you can help.
> >
> > thanks,
> > dims
> >
> >
> > On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> > >
> > > I found a problem in XmlSchema which I'd like to fix but found that I don't
> > > have access to the repository. This lead me to what I think is a larger
> > > problem with the WS Commons projects. There is no information about these
> > > projects on the WS site, no bug tracking system, no regular builds, and no
> > > developers (publically) committed to this code.
> > >
> > > If we're to continue to have WS commons projects I'd like to suggest that
> > > either these be transformed into WS projects with their own sites, jira,
> > > etc., or that a page be added to the WS site that explains these common
> > > projects and provides references to the projects that own these common
> > > projects. (I'd still like to see public builds of these projects that other
> > > projects, such as Woden, can depend on.)
> > >
> > > Comments? Is someone already looking into some of these issues? If I'm way
> > > off here because I've missed some information please correct me. If this is
> > > the case we may just need to make the information more visible.
> > >
> > > Thanks,
> > >
> > > Lawrence Mandel
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: woden-dev-help@ws.apache.org
> >
> >
> >
>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
Re: Problem with WS Commons
Posted by Lawrence Mandel <lm...@ca.ibm.com>.
To follow up, turns out I do have the appropriate write permissions. There
was a problem with my configuration. I've committed my fix to XmlSchema.
Lawrence Mandel
Davanum Srinivas <da...@gmail.com>
12/07/2005 07:36 AM
Please respond to
general
To
woden-dev@ws.apache.org
cc
general@ws.apache.org
Subject
Re: Problem with WS Commons
Lawrence,
All WS folks have write privs to ws-commons. If you are unable to
commit your changes, give me a holler.
Yes, we need to define a process like that. XmlSchema has been
languishing in obscurity for years now it was in the scratch area for
Axis 1.X and only now have we been pushing its use with Axis2 and
Woden.
Website is easy, just like the woden site, you can add contents to svn
(site under https://svn.apache.org/repos/asf/webservices/) and do a
svn checkout under (/www/ws.apache.org/commons/) on minotaur to
publish it.
Please send me your jira id, i'll make u an admin.
For mailing lists, please open a jira request for infrastrastructure
and follow up with email to infrastructure AT apache.org.
thanks,
dims
On 12/7/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> Dims,
>
> Do you know who I should speak to about obtaining write access to that
repository?
>
> The snapshots are really just head builds. Can we define a process where
more stable builds are declared on a semi-regular basis?
>
> WRT my other suggestions, once I get a few spare minutes I will look
into creating a WS commons virtual component complete with a site, Jira,
and mailing lists. I'll post back to general@ws once I have a chance to
look into this. If anyone else has time I'd be happy to get some help.
>
> Lawrence Mandel
>
>
>
>
> Davanum Srinivas <da...@gmail.com>
>
> 12/06/2005 11:02 PM
>
> Please respond to
> woden-dev
>
>
> To woden-dev@ws.apache.org
>
> cc general@ws.apache.org
>
> Subject Re: Problem with WS Commons
>
>
>
>
>
>
>
>
> Lawrence,
>
> - You should have write access to that repo.
> - Snapshots are published every 6 hours
> (http://cvs.apache.org/repository/ws-commons/jars/)
>
> +1 to do all the things that you mentioned. Please feel free to take
> ownership of the bits where you can help.
>
> thanks,
> dims
>
>
> On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> >
> > I found a problem in XmlSchema which I'd like to fix but found that I
don't
> > have access to the repository. This lead me to what I think is a
larger
> > problem with the WS Commons projects. There is no information about
these
> > projects on the WS site, no bug tracking system, no regular builds,
and no
> > developers (publically) committed to this code.
> >
> > If we're to continue to have WS commons projects I'd like to suggest
that
> > either these be transformed into WS projects with their own sites,
jira,
> > etc., or that a page be added to the WS site that explains these
common
> > projects and provides references to the projects that own these
common
> > projects. (I'd still like to see public builds of these projects that
other
> > projects, such as Woden, can depend on.)
> >
> > Comments? Is someone already looking into some of these issues? If
I'm way
> > off here because I've missed some information please correct me. If
this is
> > the case we may just need to make the information more visible.
> >
> > Thanks,
> >
> > Lawrence Mandel
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Problem with WS Commons
Posted by Davanum Srinivas <da...@gmail.com>.
Lawrence,
All WS folks have write privs to ws-commons. If you are unable to
commit your changes, give me a holler.
Yes, we need to define a process like that. XmlSchema has been
languishing in obscurity for years now it was in the scratch area for
Axis 1.X and only now have we been pushing its use with Axis2 and
Woden.
Website is easy, just like the woden site, you can add contents to svn
(site under https://svn.apache.org/repos/asf/webservices/) and do a
svn checkout under (/www/ws.apache.org/commons/) on minotaur to
publish it.
Please send me your jira id, i'll make u an admin.
For mailing lists, please open a jira request for infrastrastructure
and follow up with email to infrastructure AT apache.org.
thanks,
dims
On 12/7/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> Dims,
>
> Do you know who I should speak to about obtaining write access to that repository?
>
> The snapshots are really just head builds. Can we define a process where more stable builds are declared on a semi-regular basis?
>
> WRT my other suggestions, once I get a few spare minutes I will look into creating a WS commons virtual component complete with a site, Jira, and mailing lists. I'll post back to general@ws once I have a chance to look into this. If anyone else has time I'd be happy to get some help.
>
> Lawrence Mandel
>
>
>
>
> Davanum Srinivas <da...@gmail.com>
>
> 12/06/2005 11:02 PM
>
> Please respond to
> woden-dev
>
>
> To woden-dev@ws.apache.org
>
> cc general@ws.apache.org
>
> Subject Re: Problem with WS Commons
>
>
>
>
>
>
>
>
> Lawrence,
>
> - You should have write access to that repo.
> - Snapshots are published every 6 hours
> (http://cvs.apache.org/repository/ws-commons/jars/)
>
> +1 to do all the things that you mentioned. Please feel free to take
> ownership of the bits where you can help.
>
> thanks,
> dims
>
>
> On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> >
> > I found a problem in XmlSchema which I'd like to fix but found that I don't
> > have access to the repository. This lead me to what I think is a larger
> > problem with the WS Commons projects. There is no information about these
> > projects on the WS site, no bug tracking system, no regular builds, and no
> > developers (publically) committed to this code.
> >
> > If we're to continue to have WS commons projects I'd like to suggest that
> > either these be transformed into WS projects with their own sites, jira,
> > etc., or that a page be added to the WS site that explains these common
> > projects and provides references to the projects that own these common
> > projects. (I'd still like to see public builds of these projects that other
> > projects, such as Woden, can depend on.)
> >
> > Comments? Is someone already looking into some of these issues? If I'm way
> > off here because I've missed some information please correct me. If this is
> > the case we may just need to make the information more visible.
> >
> > Thanks,
> >
> > Lawrence Mandel
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Problem with WS Commons
Posted by Davanum Srinivas <da...@gmail.com>.
Lawrence,
All WS folks have write privs to ws-commons. If you are unable to
commit your changes, give me a holler.
Yes, we need to define a process like that. XmlSchema has been
languishing in obscurity for years now it was in the scratch area for
Axis 1.X and only now have we been pushing its use with Axis2 and
Woden.
Website is easy, just like the woden site, you can add contents to svn
(site under https://svn.apache.org/repos/asf/webservices/) and do a
svn checkout under (/www/ws.apache.org/commons/) on minotaur to
publish it.
Please send me your jira id, i'll make u an admin.
For mailing lists, please open a jira request for infrastrastructure
and follow up with email to infrastructure AT apache.org.
thanks,
dims
On 12/7/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> Dims,
>
> Do you know who I should speak to about obtaining write access to that repository?
>
> The snapshots are really just head builds. Can we define a process where more stable builds are declared on a semi-regular basis?
>
> WRT my other suggestions, once I get a few spare minutes I will look into creating a WS commons virtual component complete with a site, Jira, and mailing lists. I'll post back to general@ws once I have a chance to look into this. If anyone else has time I'd be happy to get some help.
>
> Lawrence Mandel
>
>
>
>
> Davanum Srinivas <da...@gmail.com>
>
> 12/06/2005 11:02 PM
>
> Please respond to
> woden-dev
>
>
> To woden-dev@ws.apache.org
>
> cc general@ws.apache.org
>
> Subject Re: Problem with WS Commons
>
>
>
>
>
>
>
>
> Lawrence,
>
> - You should have write access to that repo.
> - Snapshots are published every 6 hours
> (http://cvs.apache.org/repository/ws-commons/jars/)
>
> +1 to do all the things that you mentioned. Please feel free to take
> ownership of the bits where you can help.
>
> thanks,
> dims
>
>
> On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> >
> > I found a problem in XmlSchema which I'd like to fix but found that I don't
> > have access to the repository. This lead me to what I think is a larger
> > problem with the WS Commons projects. There is no information about these
> > projects on the WS site, no bug tracking system, no regular builds, and no
> > developers (publically) committed to this code.
> >
> > If we're to continue to have WS commons projects I'd like to suggest that
> > either these be transformed into WS projects with their own sites, jira,
> > etc., or that a page be added to the WS site that explains these common
> > projects and provides references to the projects that own these common
> > projects. (I'd still like to see public builds of these projects that other
> > projects, such as Woden, can depend on.)
> >
> > Comments? Is someone already looking into some of these issues? If I'm way
> > off here because I've missed some information please correct me. If this is
> > the case we may just need to make the information more visible.
> >
> > Thanks,
> >
> > Lawrence Mandel
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Problem with WS Commons
Posted by Lawrence Mandel <lm...@ca.ibm.com>.
Dims,
Do you know who I should speak to about obtaining write access to that
repository?
The snapshots are really just head builds. Can we define a process where
more stable builds are declared on a semi-regular basis?
WRT my other suggestions, once I get a few spare minutes I will look into
creating a WS commons virtual component complete with a site, Jira, and
mailing lists. I'll post back to general@ws once I have a chance to look
into this. If anyone else has time I'd be happy to get some help.
Lawrence Mandel
Davanum Srinivas <da...@gmail.com>
12/06/2005 11:02 PM
Please respond to
woden-dev
To
woden-dev@ws.apache.org
cc
general@ws.apache.org
Subject
Re: Problem with WS Commons
Lawrence,
- You should have write access to that repo.
- Snapshots are published every 6 hours
(http://cvs.apache.org/repository/ws-commons/jars/)
+1 to do all the things that you mentioned. Please feel free to take
ownership of the bits where you can help.
thanks,
dims
On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> I found a problem in XmlSchema which I'd like to fix but found that I
don't
> have access to the repository. This lead me to what I think is a larger
> problem with the WS Commons projects. There is no information about
these
> projects on the WS site, no bug tracking system, no regular builds, and
no
> developers (publically) committed to this code.
>
> If we're to continue to have WS commons projects I'd like to suggest
that
> either these be transformed into WS projects with their own sites, jira,
> etc., or that a page be added to the WS site that explains these common
> projects and provides references to the projects that own these common
> projects. (I'd still like to see public builds of these projects that
other
> projects, such as Woden, can depend on.)
>
> Comments? Is someone already looking into some of these issues? If I'm
way
> off here because I've missed some information please correct me. If this
is
> the case we may just need to make the information more visible.
>
> Thanks,
>
> Lawrence Mandel
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Problem with WS Commons
Posted by Lawrence Mandel <lm...@ca.ibm.com>.
Dims,
Do you know who I should speak to about obtaining write access to that
repository?
The snapshots are really just head builds. Can we define a process where
more stable builds are declared on a semi-regular basis?
WRT my other suggestions, once I get a few spare minutes I will look into
creating a WS commons virtual component complete with a site, Jira, and
mailing lists. I'll post back to general@ws once I have a chance to look
into this. If anyone else has time I'd be happy to get some help.
Lawrence Mandel
Davanum Srinivas <da...@gmail.com>
12/06/2005 11:02 PM
Please respond to
woden-dev
To
woden-dev@ws.apache.org
cc
general@ws.apache.org
Subject
Re: Problem with WS Commons
Lawrence,
- You should have write access to that repo.
- Snapshots are published every 6 hours
(http://cvs.apache.org/repository/ws-commons/jars/)
+1 to do all the things that you mentioned. Please feel free to take
ownership of the bits where you can help.
thanks,
dims
On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> I found a problem in XmlSchema which I'd like to fix but found that I
don't
> have access to the repository. This lead me to what I think is a larger
> problem with the WS Commons projects. There is no information about
these
> projects on the WS site, no bug tracking system, no regular builds, and
no
> developers (publically) committed to this code.
>
> If we're to continue to have WS commons projects I'd like to suggest
that
> either these be transformed into WS projects with their own sites, jira,
> etc., or that a page be added to the WS site that explains these common
> projects and provides references to the projects that own these common
> projects. (I'd still like to see public builds of these projects that
other
> projects, such as Woden, can depend on.)
>
> Comments? Is someone already looking into some of these issues? If I'm
way
> off here because I've missed some information please correct me. If this
is
> the case we may just need to make the information more visible.
>
> Thanks,
>
> Lawrence Mandel
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Problem with WS Commons
Posted by Davanum Srinivas <da...@gmail.com>.
Lawrence,
- You should have write access to that repo.
- Snapshots are published every 6 hours
(http://cvs.apache.org/repository/ws-commons/jars/)
+1 to do all the things that you mentioned. Please feel free to take
ownership of the bits where you can help.
thanks,
dims
On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> I found a problem in XmlSchema which I'd like to fix but found that I don't
> have access to the repository. This lead me to what I think is a larger
> problem with the WS Commons projects. There is no information about these
> projects on the WS site, no bug tracking system, no regular builds, and no
> developers (publically) committed to this code.
>
> If we're to continue to have WS commons projects I'd like to suggest that
> either these be transformed into WS projects with their own sites, jira,
> etc., or that a page be added to the WS site that explains these common
> projects and provides references to the projects that own these common
> projects. (I'd still like to see public builds of these projects that other
> projects, such as Woden, can depend on.)
>
> Comments? Is someone already looking into some of these issues? If I'm way
> off here because I've missed some information please correct me. If this is
> the case we may just need to make the information more visible.
>
> Thanks,
>
> Lawrence Mandel
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Problem with WS Commons
Posted by Dan Diephouse <da...@envoisolutions.com>.
Lawrence Mandel wrote:
>
> I found a problem in XmlSchema which I'd like to fix but found that I
> don't have access to the repository. This lead me to what I think is a
> larger problem with the WS Commons projects. There is no information
> about these projects on the WS site, no bug tracking system, no
> regular builds, and no developers (publically) committed to this code.
>
> If we're to continue to have WS commons projects I'd like to suggest
> that either these be transformed into WS projects with their own
> sites, jira, etc., or that a page be added to the WS site that
> explains these common projects and provides references to the projects
> that own these common projects. (I'd still like to see public builds
> of these projects that other projects, such as Woden, can depend on.)
>
> Comments? Is someone already looking into some of these issues? If I'm
> way off here because I've missed some information please correct me.
> If this is the case we may just need to make the information more
> visible.
>
> Thanks,
>
> Lawrence Mandel
I totally agree on your comments. When I had an issue with the XmlSchema
stuff I just filed a jira issue under Axis2. I think the ws-commons
definitely needs both a website, jira, and mailing list. Cheers,
- Dan
--
Dan Diephouse
Envoi Solutions LLC
http://netzooid.com
Re: Problem with WS Commons
Posted by Davanum Srinivas <da...@gmail.com>.
Lawrence,
- You should have write access to that repo.
- Snapshots are published every 6 hours
(http://cvs.apache.org/repository/ws-commons/jars/)
+1 to do all the things that you mentioned. Please feel free to take
ownership of the bits where you can help.
thanks,
dims
On 12/6/05, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> I found a problem in XmlSchema which I'd like to fix but found that I don't
> have access to the repository. This lead me to what I think is a larger
> problem with the WS Commons projects. There is no information about these
> projects on the WS site, no bug tracking system, no regular builds, and no
> developers (publically) committed to this code.
>
> If we're to continue to have WS commons projects I'd like to suggest that
> either these be transformed into WS projects with their own sites, jira,
> etc., or that a page be added to the WS site that explains these common
> projects and provides references to the projects that own these common
> projects. (I'd still like to see public builds of these projects that other
> projects, such as Woden, can depend on.)
>
> Comments? Is someone already looking into some of these issues? If I'm way
> off here because I've missed some information please correct me. If this is
> the case we may just need to make the information more visible.
>
> Thanks,
>
> Lawrence Mandel
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org