On 11/18/06, Craig L Russell <[EMAIL PROTECTED]> wrote:
The file is in the persistence-api component.
https://glassfish.dev.java.net/source/browse/glassfish/persistence-
api/schemas/persistence_1_0.xsd?view=markup
The xsd file in question is licensed under the terms of the CDDL
license under wh
For the IP clearance stuff... yes.
But code developed outside of the Apache community, then brought in...
that can be a problem. Especially when that is the "standard operating
procedure". I can think of a couple communities where a lot of code is
migrated from external locations into Apache. The
The file is in the persistence-api component.
https://glassfish.dev.java.net/source/browse/glassfish/persistence-
api/schemas/persistence_1_0.xsd?view=markup
The xsd file in question is licensed under the terms of the CDDL
license under which we already distribute the persistence jar file.
On 11/18/06, Craig L Russell <[EMAIL PROTECTED]> wrote:
Hi Robert,
I just have to give you a very public THANK YOU for your assistance
to projects in the incubator. I personally look forward to reading
your posts because I learn so much from them. I think you are a model
for how to give construc
Hi Robert,
I just have to give you a very public THANK YOU for your assistance
to projects in the incubator. I personally look forward to reading
your posts because I learn so much from them. I think you are a model
for how to give constructive feedback and nurture projects. Please
keep u
On 11/17/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote:
Henri Yandell wrote:
> One thing that came out of the board meeting was making sure that the
> community knew how to bring code into the ASF. What the scenarios are,
> and what the rules are.
I'm looking at some logistics and have been fol
I agree that we should instill Best Practice, which (IMHO) means
that podlings should learn a "real" Apache release process including
voting on new bits before graduating into the wild.
More today than ever, a podling controls the smoothness its release
cycle given improved Incubator documentat
robert burrell donkin wrote:
> Marc Prud'hommeaux wrote:
> > We'll correct these issues asap. Once corrected artifacts are
> > uploaded, I assume it will necessary to re-start the vote on the open-
> > jpa-dev list before re-starting the vote here. Please correct me if I
> > am wrong.
> there hav
On 11/17/06, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
On Nov 16, 2006, at 12:57 PM, robert burrell donkin wrote:
> On 11/16/06, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
> i have some issues i'd like to see fixed plus less important issues,
> some questions i'd like answered and som
On 11/17/06, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
Robert-
We'll correct these issues asap. Once corrected artifacts are
uploaded, I assume it will necessary to re-start the vote on the open-
jpa-dev list before re-starting the vote here. Please correct me if I
am wrong.
there have bee
On 11/18/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
On 11/17/06, Craig L Russell <[EMAIL PROTECTED]> wrote:
> Does RAT have enough smarts to do this kind of checking?
RAT is unlikely to be smarter than it's creator ;-)
(JCL 1.1 is one of mine)
what is or is not bad meta-data depends
On 11/17/06, Craig L Russell <[EMAIL PROTECTED]> wrote:
Does RAT have enough smarts to do this kind of checking?
RAT is unlikely to be smarter than it's creator ;-)
(JCL 1.1 is one of mine)
what is or is not bad meta-data depends on eye of the beholder (and
this is the wrong forum for argume
12 matches
Mail list logo
