All,
For those wondering where the Geronimo 1.1.1 release is at here is a quick
summary and battle plan.
John Sisson discovered that we have several DTD and XSDs included in our build that are copies of
Sun's original material. The copyright in the material seems to indicate that we cannot
On Aug 18, 2006, at 8:28 AM, Matt Hogstrom wrote:
All,
For those wondering where the Geronimo 1.1.1 release is at here is
a quick summary and battle plan.
John Sisson discovered that we have several DTD and XSDs included
in our build that are copies of Sun's original material. The
Can't we just ship without those? We have pointers to them on our web
site at http://geronimo.apache.org/schemas.html -- is there any
additional reason we need them at runtime (e.g. does XMLBeans use the
actual schema to validate at runtime)?
Thanks,
Aaron
On 8/18/06, Matt Hogstrom [EMAIL
Excellent...thanks David...good ideas as well about the links.
David Jencks wrote:
On Aug 18, 2006, at 8:28 AM, Matt Hogstrom wrote:
All,
For those wondering where the Geronimo 1.1.1 release is at here is a
quick summary and battle plan.
John Sisson discovered that we have several DTD
They are used by XMLBeans during the build process. I guess we could do a one-time generation of
the XMLBeans classes but I'd be more comfortable with Jencks' input. If you don't have the schemas
you'd have to have network connectivity to build I suspect.
Aaron Mulder wrote:
Can't we just
If they are only used during the build process, then don't re-distribute
and therefore this issue then seems out of the critical path for 1.1.1
and can be solved for 1.1.1.1.1.1.1.1.1
gier
Matt Hogstrom wrote:
They are used by XMLBeans during the build process. I guess we could do
a one-time
Well, the problem is that we distribute the source code for Geronimo out of SVN and these would end
up being included. I think that falls into the category of redistribution. Hopefully I'm wrong on
that count :)
The remaining question is what about the previous releases? I would expect
On Aug 18, 2006, at 9:22 AM, Geir Magnusson Jr wrote:
If they are only used during the build process, then don't re-
distribute
and therefore this issue then seems out of the critical path for 1.1.1
and can be solved for 1.1.1.1.1.1.1.1.1
They are not needed at runtime, but xmlbeans packs
Heads up...we're using IRC for real-time collaboration on this and will post updates to the dev
list. IRC is at irc.freenode.net channel #geronimo.
Right now I'm removing ./modules/j2ee-schema/src/resources/* and building to see if these DTDs are
required for building in some odd way. Don't
Fair enough...I think we'll have a better idea in an hour or so. Hopefully we're eliminating these
skeletons from appearing again ;)
Aaron Mulder wrote:
I'm not claiming we don't have a problem, I'm claiming that we can
ship 1.1.1 anyway. We may have to manually delete some files from the
I'm not claiming we don't have a problem, I'm claiming that we can
ship 1.1.1 anyway. We may have to manually delete some files from the
source distribution, but it could be done in order to avoid holding
1.1.1 any longer.
Thanks,
Aaron
On 8/18/06, David Jencks [EMAIL PROTECTED] wrote:
Matt Hogstrom wrote:
Well, the problem is that we distribute the source code for Geronimo out
of SVN and these would end up being included. I think that falls into
the category of redistribution. Hopefully I'm wrong on that count :)
Right, so why not just take them out of SVN? I guess it
Matt Hogstrom wrote:
Heads up...we're using IRC for real-time collaboration on this and will
post updates to the dev list. IRC is at irc.freenode.net channel
#geronimo.
I won't be able to be there.
geir
Right now I'm removing ./modules/j2ee-schema/src/resources/* and
building to see
I personally don't know why we bother to regenerate that tree on
every build as those schemas are not going to change. Let's just
build them once, publish the jars, delete the schemas and be done
with it.
-David
On Aug 18, 2006, at 9:45 AM, David Jencks wrote:
On Aug 18, 2006, at 9:22
+1On Aug 18, 2006, at 1:36 PM, David Blevins wrote:I personally don't know why we bother to regenerate that tree on every build as those schemas are not going to change. Let's just build them once, publish the jars, delete the schemas and be done with it.-DavidOn Aug 18, 2006, at 9:45 AM, David
On Aug 18, 2006, at 10:36 AM, David Blevins wrote:
I personally don't know why we bother to regenerate that tree on
every build as those schemas are not going to change. Let's just
build them once, publish the jars, delete the schemas and be done
with it.
I think this will minimize our
+1
Exactly. Maybe put a note somewhere saying what schemas were used and
where a user can find them.
geir
David Blevins wrote:
I personally don't know why we bother to regenerate that tree on every
build as those schemas are not going to change. Let's just build them
once, publish the
On Aug 18, 2006, at 10:01 AM, Geir Magnusson Jr wrote:
Matt Hogstrom wrote:
Well, the problem is that we distribute the source code for
Geronimo out
of SVN and these would end up being included. I think that falls
into
the category of redistribution. Hopefully I'm wrong on that count :)
I've uploaded a preliminary version of the proposed schema jar at
people.apache.org/~djencks/geronimo-schema_1.4_spec-1.0-SNAPSHOT.jar
We should be able to remove all the schemas and xmlbeans stuff from
j2ee-schema module and instead have a geronimo-dependency.xml element
to pull in the
Dain Sundstrom wrote:
On Aug 18, 2006, at 10:01 AM, Geir Magnusson Jr wrote:
Matt Hogstrom wrote:
Well, the problem is that we distribute the source code for Geronimo out
of SVN and these would end up being included. I think that falls into
the category of redistribution. Hopefully I'm
Might there be a tool that could take the schema jar and produce xsd's
from it's contents?
:D
geir
David Jencks wrote:
I've uploaded a preliminary version of the proposed schema jar at
people.apache.org/~djencks/geronimo-schema_1.4_spec-1.0-SNAPSHOT.jar
We should be able to remove all
21 matches
Mail list logo
