[jira] Commented: (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=comments#action_12433172 ] Matt Hogstrom commented on GERONIMO-2332: - I think this patch is complete and we can close it out :) Do you want the honors David? > 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] Commented: (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=comments#action_12433164 ] David Jencks commented on GERONIMO-2332: I believe that the work in this patch has actually been applied to all branches and trunk. anyone want to vote on it or should we just consider it rejected now that it's been applied :-) ? > 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] Commented: (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=comments#action_12430680 ] Anita Kulshreshtha commented on GERONIMO-2332: -- I agree with David Jencks that it should be possible to use pom.xml. I did not use dependency plugin for this reason. We added geronimo-dependency.xml files as a temporary measure to get the M2 build working fast.. > 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-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] Commented: (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=comments#action_12430666 ] Guillaume Nodet commented on GERONIMO-2332: --- We won' t end up with only 1 files. We can easily do the transformation on a per schema basis, though jaxb would not work for dtds. But it seems the only copyrighted stuff are the 1.4 schemas, so... But looking once more at the schema license, This document and the technology which it describes are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. IANAL, but do you think the term decompilation could be applied to such a transformation ? > 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-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] Commented: (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=comments#action_12430656 ] David Jencks commented on GERONIMO-2332: jason- re Should we be generating geronimo-dependency.xml ? Using explicit artifact references... so that we can keep these files in sync with the modules m2 dependency versions? - We did this with the m1 dependency plugin. For m2 I'd prefer to first prune dependencies as much as possible and see if we can use the pom.xml instead. Most of the geronimo-dependency.xml files don't include versions, at least for geronimo artifacts. Guillaume- I considered trying something like that with xmlbeans, although I don't know if you can get it to regenerate the schemas. One possible problem is that I imaging everything would end up in one file rather than the 7 or so we have come to know and love. I wonder if, instead, we should add a console action to download all the schemas and dtds from sun :-) > 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-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] Commented: (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=comments#action_12430601 ] Guillaume Nodet commented on GERONIMO-2332: --- Instead of re-writing the schemas from scratch, what about using jaxb2 to generate some pojos from the schemas, and then using jaxb2 to generate the new schemas from the pojos. We already generate pojos from the schemas using xmlbeans, so ... Would it be ok from a legal pov ? > 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-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] Commented: (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=comments#action_12430599 ] Jason Dillon commented on GERONIMO-2332: GERONIMO-2332-trunk-v2.patch has been applied in #436915 > 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-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] Commented: (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=comments#action_12430580 ] Jason Dillon commented on GERONIMO-2332: Should we be generating geronimo-dependency.xml ? Using explicit artifact references... so that we can keep these files in sync with the modules m2 dependency versions? > 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-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] Commented: (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=comments#action_12430574 ] Jason Dillon commented on GERONIMO-2332: I am going to verify and apply GERONIMO-2332-trunk-v2.patch to server/trunk as it overlaps with some of the restructure work to use the standard layout. > 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-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] Commented: (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=comments#action_12429499 ] David Jencks commented on GERONIMO-2332: I don't think we can type the schemas up without typos that will change the meaning compared to the sun schemas. I realized that my xml comparison tool only compares documents where the elements are all in the same order, and I'm not about to try to write one that can decide if two schemas are equivalent. > 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.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] Commented: (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=comments#action_12429482 ] Alan Cabrera commented on GERONIMO-2332: Wow, if we could do this and it will fly with Sun, then this is *THE* way to go. > 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.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] Commented: (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=comments#action_12429479 ] Matt Hogstrom commented on GERONIMO-2332: - I like this approach but it sounds like there are some kinks to be worked out. What if we re-type the specs by hand and then check them into branches/1.1.1. We'll cary that notion forward for the 1.1.x tree and address this larger problem in trunk. Thoughts? > 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.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] Commented: (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=comments#action_12429472 ] Alan Cabrera commented on GERONIMO-2332: Agreed. This is starting to look like the tail is wagging the dog. What is the problem that we are trying to solve? Shall we bring this up on the dev list? > 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.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] Commented: (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=comments#action_12429452 ] David Jencks commented on GERONIMO-2332: Theres a fairly serious problem with this proposal in that it involves generating source code that does not then have the required apache headers and checking it into svn. Is there a way to use m2 to change the headers on all the files? I don't think john's "minor point" about the possibility of getting an empty jar is relevant since whoever is setting this up will check the generated files into svn so that no one else has to run the generate source profile (at least until sun updates the schemas and we decide to use updated versions). As this points out another problem is that we have no record of how we got the generated classes: sun has fixed problems in the schemas in the past without changing anything that we can identify from the generated code. As a result of these factors I'm -0.99 on this proposal at the moment. > 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.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] Commented: (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=comments#action_12429261
]
John Sisson commented on GERONIMO-2332:
---
Agree with Alan's objection that it should be placed elsewhere.
I tested applying it to 1.1.1 and openejb/branches/v2_1_1/openejb2 and did a
build. I had to manually apply the changes to openejb's etc/project.properties
due to a conflict with the geronimo_dependency_plugin_version that is two lines
above the change.
Assuming Alan's argument is addressed *and* the new schema jar is fixed to
contain LICENSE.txt and NOTICE.txt files under META-INF, *then I'm +1*.
One other minor point is that if one builds the schema jar with just the
{{mvn}} command instead of {{mvn -o clean install -Pgenerate-source}} they will
get a BUILD SUCCESSFUL but the JAR won't contain any classes. The only other
hint of a problem is that there is the line {{[WARNING] JAR will be empty - no
content was marked for inclusion!}}. Is there something we can do to fail the
build?
> 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.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] Commented: (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=comments#action_12429219 ] David Jencks commented on GERONIMO-2332: I have no big argument against alan's objection. I'd kind of like to only have one copy of these and not one for each branch, but we can certainly keep many copies if that's what is generally desired. Once we decide where to put them I'll update the patches. > 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] Commented: (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=comments#action_12429207 ] Alan Cabrera commented on GERONIMO-2332: While I understand the problem that this is trying to solve, I do not agree with the way we are trying to solve it. I think we should just get permission from Sun to redistribute. That said, here is my opinion, which I *strongly* hold: These files must not be put into specs. They are a technology descision that was made by the Geronimo project and have no place in the technology agnostic spec jar. These files need to be placed into new jars like geronimo-xmlbeans-j2ee-mumbojumbo. I am willing to discuss this issue but be prepared for me to be slightly instransigent on this. > 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.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] Commented: (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=comments#action_12429164 ] David Jencks commented on GERONIMO-2332: The patches for 1.1 seem to work fine for 1.1.1 as well. > 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
