[jira] Updated: (GERONIMO-2332) RTC Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a spec module so we don't need the schemas in svn at all
[ http://issues.apache.org/jira/browse/GERONIMO-2332?page=all ] David Jencks updated GERONIMO-2332: --- Attachment: GERONIMO-2332-trunk-v2.patch I believe this is a correct patch to use the tck-hosted schema jar in trunk, however there's a bit of other work in my tree so I might have missed something. > RTC Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a > spec module so we don't need the schemas in svn at all > > > Key: GERONIMO-2332 > URL: http://issues.apache.org/jira/browse/GERONIMO-2332 > Project: Geronimo > Issue Type: RTC > Security Level: public(Regular issues) > Components: specs >Affects Versions: 1.1.1, 1.1.2, 1.2 >Reporter: David Jencks > Assigned To: David Jencks > Fix For: 1.1.1, 1.1.2, 1.2 > > Attachments: GERONIMO-2332-1.1-openejb-v2.patch, > GERONIMO-2332-1.1-v2.patch, GERONIMO-2332-1.1.patch, > GERONIMO-2332-openejb-2.1.patch, GERONIMO-2332-trunk-v2.patch, > GERONIMO-2332-trunk.patch, geronimo-schema_1.4_spec-generated-src.zip, > geronimo-schema_1.4_spec-src.zip > > > See GERONIMO-2307. It seems that the option with the least legal exposure is > to not distribute and sun schema files and not have any in our svn. This is > a proposed spec module that uses a m2 profile to pull the schemas from suns > website (where they are freely available), run xmlbeans on them, and remove > the copies of the schemas that xmlbeasn helpfully tries to include in the > output. We can then check this stuff into svn. > A normal non-profile build then just builds these sources into a jar. We can > replace the xmlbeans step in j2ee-schema with a geronimo dependency on this > new spec jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2332) RTC Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a spec module so we don't need the schemas in svn at all
[ http://issues.apache.org/jira/browse/GERONIMO-2332?page=all ] David Jencks updated GERONIMO-2332: --- Attachment: GERONIMO-2332-1.1-v2.patch GERONIMO-2332-1.1-openejb-v2.patch I've created stuff in the tck project to generate a similar jar. Here are patches to the 1.1 branch that use the new jar. > RTC Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a > spec module so we don't need the schemas in svn at all > > > Key: GERONIMO-2332 > URL: http://issues.apache.org/jira/browse/GERONIMO-2332 > Project: Geronimo > Issue Type: RTC > Security Level: public(Regular issues) > Components: specs >Affects Versions: 1.2, 1.1.1, 1.1.2 >Reporter: David Jencks > Assigned To: David Jencks > Fix For: 1.2, 1.1.1, 1.1.2 > > Attachments: GERONIMO-2332-1.1-openejb-v2.patch, > GERONIMO-2332-1.1-v2.patch, GERONIMO-2332-1.1.patch, > GERONIMO-2332-openejb-2.1.patch, GERONIMO-2332-trunk.patch, > geronimo-schema_1.4_spec-generated-src.zip, geronimo-schema_1.4_spec-src.zip > > > See GERONIMO-2307. It seems that the option with the least legal exposure is > to not distribute and sun schema files and not have any in our svn. This is > a proposed spec module that uses a m2 profile to pull the schemas from suns > website (where they are freely available), run xmlbeans on them, and remove > the copies of the schemas that xmlbeasn helpfully tries to include in the > output. We can then check this stuff into svn. > A normal non-profile build then just builds these sources into a jar. We can > replace the xmlbeans step in j2ee-schema with a geronimo dependency on this > new spec jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2332) RTC Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a spec module so we don't need the schemas in svn at all
[ http://issues.apache.org/jira/browse/GERONIMO-2332?page=all ] Alan Cabrera updated GERONIMO-2332: --- Issue Type: RTC (was: Bug) Workflow: RTC Workflow (was: jira) > RTC Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a > spec module so we don't need the schemas in svn at all > > > Key: GERONIMO-2332 > URL: http://issues.apache.org/jira/browse/GERONIMO-2332 > Project: Geronimo > Issue Type: RTC > Security Level: public(Regular issues) > Components: specs >Affects Versions: 1.1.1, 1.1.2, 1.2 >Reporter: David Jencks > Assigned To: David Jencks > Fix For: 1.2, 1.1.1, 1.1.2 > > Attachments: GERONIMO-2332-1.1.patch, > GERONIMO-2332-openejb-2.1.patch, GERONIMO-2332-trunk.patch, > geronimo-schema_1.4_spec-generated-src.zip, geronimo-schema_1.4_spec-src.zip > > > See GERONIMO-2307. It seems that the option with the least legal exposure is > to not distribute and sun schema files and not have any in our svn. This is > a proposed spec module that uses a m2 profile to pull the schemas from suns > website (where they are freely available), run xmlbeans on them, and remove > the copies of the schemas that xmlbeasn helpfully tries to include in the > output. We can then check this stuff into svn. > A normal non-profile build then just builds these sources into a jar. We can > replace the xmlbeans step in j2ee-schema with a geronimo dependency on this > new spec jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2332) RTC Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a spec module so we don't need the schemas in svn at all
[ http://issues.apache.org/jira/browse/GERONIMO-2332?page=all ] David Jencks updated GERONIMO-2332: --- Summary: RTC Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a spec module so we don't need the schemas in svn at all (was: Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a spec module so we don't need the schemas in svn at all) > RTC Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a > spec module so we don't need the schemas in svn at all > > > Key: GERONIMO-2332 > URL: http://issues.apache.org/jira/browse/GERONIMO-2332 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Affects Versions: 1.2, 1.1.1, 1.1.2 >Reporter: David Jencks > Assigned To: David Jencks > Fix For: 1.2, 1.1.1, 1.1.2 > > Attachments: GERONIMO-2332-1.1.patch, > GERONIMO-2332-openejb-2.1.patch, GERONIMO-2332-trunk.patch, > geronimo-schema_1.4_spec-generated-src.zip, geronimo-schema_1.4_spec-src.zip > > > See GERONIMO-2307. It seems that the option with the least legal exposure is > to not distribute and sun schema files and not have any in our svn. This is > a proposed spec module that uses a m2 profile to pull the schemas from suns > website (where they are freely available), run xmlbeans on them, and remove > the copies of the schemas that xmlbeasn helpfully tries to include in the > output. We can then check this stuff into svn. > A normal non-profile build then just builds these sources into a jar. We can > replace the xmlbeans step in j2ee-schema with a geronimo dependency on this > new spec jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira