Eclipse Community Forums: XML Schema Definition (XSD)

Help

Home

Home » Archived » XML Schema Definition (XSD) » CVS / Bug-Fixing-Process

Show: Today's Messages :: Show Polls :: Message Navigator

CVS / Bug-Fixing-Process [message #3510]

Tue, 22 October 2002 16:17

Eclipse User

Originally posted by: dims.yahoo.com

Hi,

We are researching using Schema Infoset Model in Apache Axis. Here are a
few questions related to administrative stuff...

#1. The main page says that the CVS repoistory is "to be populated"...Any
idea when?
#2. What's the process if we find a bug?
#3. Who does one get commit access to the cvs? (After it is populated, of
course :)

Thanks,
dims

Report message to a moderator

Re: CVS / Bug-Fixing-Process [message #3609 is a reply to message #3510]

Tue, 22 October 2002 18:34

Eclipse User

Originally posted by: merks.ca.ibm.com

Hi,

The build and development processes we've used over the last few years, and
our tight integration with EMF, make migrating the "master image" to CVS
problematic. All the source code is currently in CVS, but only as part of
the "source-linked" Javadoc. It is also available with each driver.
Committing changes to the base code is something we'd have to look at
carefully. Bugs should be opened in bugzilla, and I'll try to be very
responsive to fixing them.

Thanks for your interest!

Davanum Srinivas wrote:

> Hi,
>
> We are researching using Schema Infoset Model in Apache Axis. Here are a
> few questions related to administrative stuff...
>
> #1. The main page says that the CVS repoistory is "to be populated"...Any
> idea when?
> #2. What's the process if we find a bug?
> #3. Who does one get commit access to the cvs? (After it is populated, of
> course :)
>
> Thanks,
> dims

--
Ed Merks

Report message to a moderator

Re: CVS / Bug-Fixing-Process [message #4099 is a reply to message #3609]

Thu, 24 October 2002 13:33

Eclipse User

Originally posted by: dims.yahoo.com

Ed,

I'd like to see xsd to be part of the Gump build (see
http://jakarta.apache.org/builds/gump/latest/ and
http://jakarta.apache.org/gump/) Please talk to Sam Ruby (IBM) if you need
more information.

If we have to use XSD for Apache Axis, we need to get a daily build of XSD
for continuous testing. This is possible ONLY if your code is available
via a public cvs.

Thanks,
dims

Ed Merks wrote:

> Hi,

> The build and development processes we've used over the last few years, and
> our tight integration with EMF, make migrating the "master image" to CVS
> problematic. All the source code is currently in CVS, but only as part of
> the "source-linked" Javadoc. It is also available with each driver.
> Committing changes to the base code is something we'd have to look at
> carefully. Bugs should be opened in bugzilla, and I'll try to be very
> responsive to fixing them.

> Thanks for your interest!

> Davanum Srinivas wrote:

> > Hi,
> >
> > We are researching using Schema Infoset Model in Apache Axis. Here are a
> > few questions related to administrative stuff...
> >
> > #1. The main page says that the CVS repoistory is "to be populated"...Any
> > idea when?
> > #2. What's the process if we find a bug?
> > #3. Who does one get commit access to the cvs? (After it is populated, of
> > course :)
> >
> > Thanks,
> > dims

> --
> Ed Merks

Report message to a moderator

Re: CVS / Bug-Fixing-Process [message #4153 is a reply to message #4099]

Thu, 24 October 2002 15:23

Eclipse User

Originally posted by: merks.ca.ibm.com

Davanum,

This implies that you would have to reproduce the EMF build as well? And parts
of the Eclipse build? I can't simply commit to that without involving a whole
heck of a lot of other people; reproducing complex build processes doesn't sound
like a great starting point since it would seem to involve a massive coordination
effort. Why can't packaged builds be tested? Perhaps we need to have a
conversation about this when you've finished your evaluation work...

Davanum Srinivas wrote:

> Ed,
>
> I'd like to see xsd to be part of the Gump build (see
> http://jakarta.apache.org/builds/gump/latest/ and
> http://jakarta.apache.org/gump/) Please talk to Sam Ruby (IBM) if you need
> more information.
>
> If we have to use XSD for Apache Axis, we need to get a daily build of XSD
> for continuous testing. This is possible ONLY if your code is available
> via a public cvs.
>
> Thanks,
> dims
>
> Ed Merks wrote:
>
> > Hi,
>
> > The build and development processes we've used over the last few years, and
> > our tight integration with EMF, make migrating the "master image" to CVS
> > problematic. All the source code is currently in CVS, but only as part of
> > the "source-linked" Javadoc. It is also available with each driver.
> > Committing changes to the base code is something we'd have to look at
> > carefully. Bugs should be opened in bugzilla, and I'll try to be very
> > responsive to fixing them.
>
> > Thanks for your interest!
>
> > Davanum Srinivas wrote:
>
> > > Hi,
> > >
> > > We are researching using Schema Infoset Model in Apache Axis. Here are a
> > > few questions related to administrative stuff...
> > >
> > > #1. The main page says that the CVS repoistory is "to be populated"...Any
> > > idea when?
> > > #2. What's the process if we find a bug?
> > > #3. Who does one get commit access to the cvs? (After it is populated, of
> > > course :)
> > >
> > > Thanks,
> > > dims
>
> > --
> > Ed Merks

--
Ed Merks

Report message to a moderator

Re: CVS / Bug-Fixing-Process [message #4223 is a reply to message #4099]

Thu, 24 October 2002 15:26

Shane Curcuru

Messages: 30
Registered: July 2009

Member

Well, actually GUMP *can* use a precompiled, posted daily build somewhere, which would be much easier to arrange in the short
term. 8-)

And indeed the EMF jars will be required, although from an external perspective you may or may not want to simply lump them
together in the short term for simplicity. Unfortunately I'm far from an EMF or XSD build expert so I can't help much more.

- Shane

On Thu, 24 Oct 2002 13:33:38 +0000 (UTC), dims@yahoo.com (Davanum Srinivas) wrote:
> Ed,
>
> I'd like to see xsd to be part of the Gump build (see
> http://jakarta.apache.org/builds/gump/latest/ and
> http://jakarta.apache.org/gump/) Please talk to Sam Ruby (IBM) if you need
> more information.
>
> If we have to use XSD for Apache Axis, we need to get a daily build of XSD
> for continuous testing. This is possible ONLY if your code is available
> via a public cvs.
>
> Thanks,
> dims

Report message to a moderator

Re: CVS / Bug-Fixing-Process [message #563225 is a reply to message #3510]

Tue, 22 October 2002 18:34

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

Hi,

The build and development processes we've used over the last few years, and
our tight integration with EMF, make migrating the "master image" to CVS
problematic. All the source code is currently in CVS, but only as part of
the "source-linked" Javadoc. It is also available with each driver.
Committing changes to the base code is something we'd have to look at
carefully. Bugs should be opened in bugzilla, and I'll try to be very
responsive to fixing them.

Thanks for your interest!

Davanum Srinivas wrote:

> Hi,
>
> We are researching using Schema Infoset Model in Apache Axis. Here are a
> few questions related to administrative stuff...
>
> #1. The main page says that the CVS repoistory is "to be populated"...Any
> idea when?
> #2. What's the process if we find a bug?
> #3. Who does one get commit access to the cvs? (After it is populated, of
> course :)
>
> Thanks,
> dims

--
Ed Merks

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: CVS / Bug-Fixing-Process [message #563356 is a reply to message #3609]

Thu, 24 October 2002 13:33

Davanum Srinivas

Messages: 6
Registered: July 2009

Junior Member

Ed,

I'd like to see xsd to be part of the Gump build (see
http://jakarta.apache.org/builds/gump/latest/ and
http://jakarta.apache.org/gump/) Please talk to Sam Ruby (IBM) if you need
more information.

If we have to use XSD for Apache Axis, we need to get a daily build of XSD
for continuous testing. This is possible ONLY if your code is available
via a public cvs.

Thanks,
dims

Ed Merks wrote:

> Hi,

> The build and development processes we've used over the last few years, and
> our tight integration with EMF, make migrating the "master image" to CVS
> problematic. All the source code is currently in CVS, but only as part of
> the "source-linked" Javadoc. It is also available with each driver.
> Committing changes to the base code is something we'd have to look at
> carefully. Bugs should be opened in bugzilla, and I'll try to be very
> responsive to fixing them.

> Thanks for your interest!

> Davanum Srinivas wrote:

> > Hi,
> >
> > We are researching using Schema Infoset Model in Apache Axis. Here are a
> > few questions related to administrative stuff...
> >
> > #1. The main page says that the CVS repoistory is "to be populated"...Any
> > idea when?
> > #2. What's the process if we find a bug?
> > #3. Who does one get commit access to the cvs? (After it is populated, of
> > course :)
> >
> > Thanks,
> > dims

> --
> Ed Merks

Report message to a moderator

Re: CVS / Bug-Fixing-Process [message #563383 is a reply to message #4099]

Thu, 24 October 2002 15:23

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

Davanum,

This implies that you would have to reproduce the EMF build as well? And parts
of the Eclipse build? I can't simply commit to that without involving a whole
heck of a lot of other people; reproducing complex build processes doesn't sound
like a great starting point since it would seem to involve a massive coordination
effort. Why can't packaged builds be tested? Perhaps we need to have a
conversation about this when you've finished your evaluation work...

Davanum Srinivas wrote:

> Ed,
>
> I'd like to see xsd to be part of the Gump build (see
> http://jakarta.apache.org/builds/gump/latest/ and
> http://jakarta.apache.org/gump/) Please talk to Sam Ruby (IBM) if you need
> more information.
>
> If we have to use XSD for Apache Axis, we need to get a daily build of XSD
> for continuous testing. This is possible ONLY if your code is available
> via a public cvs.
>
> Thanks,
> dims
>
> Ed Merks wrote:
>
> > Hi,
>
> > The build and development processes we've used over the last few years, and
> > our tight integration with EMF, make migrating the "master image" to CVS
> > problematic. All the source code is currently in CVS, but only as part of
> > the "source-linked" Javadoc. It is also available with each driver.
> > Committing changes to the base code is something we'd have to look at
> > carefully. Bugs should be opened in bugzilla, and I'll try to be very
> > responsive to fixing them.
>
> > Thanks for your interest!
>
> > Davanum Srinivas wrote:
>
> > > Hi,
> > >
> > > We are researching using Schema Infoset Model in Apache Axis. Here are a
> > > few questions related to administrative stuff...
> > >
> > > #1. The main page says that the CVS repoistory is "to be populated"...Any
> > > idea when?
> > > #2. What's the process if we find a bug?
> > > #3. Who does one get commit access to the cvs? (After it is populated, of
> > > course :)
> > >
> > > Thanks,
> > > dims
>
> > --
> > Ed Merks

--
Ed Merks

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator