[ 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
