You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2006/09/12 23:59:22 UTC
[jira] Commented: (GERONIMO-2397) Need to use the jee5 schemas
without redistributing them
[ http://issues.apache.org/jira/browse/GERONIMO-2397?page=comments#action_12434292 ]
David Jencks commented on GERONIMO-2397:
----------------------------------------
I've committed a build of the jee5 schemas in the tck directory. Jason, could you take a look and if it looks ok push some snapshots to the appropriate location?
> Need to use the jee5 schemas without redistributing them
> --------------------------------------------------------
>
> Key: GERONIMO-2397
> URL: http://issues.apache.org/jira/browse/GERONIMO-2397
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 1.2
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 1.2
>
>
> AFAICT the jee5 schemas have the same vague language prohibiting redistribution as the j2ee 1.4 schemas, so we better not have them in publically accessible svn.
> Just as we did for the j2ee 1.4 schemas I'll set up a module in tck that builds xmlbeans source and binary jars for the jee5 schemas and remove them from the sandbox/servlet2.5 where they are publically available today.
--
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
Re: [jira] Commented: (GERONIMO-2397) Need to use the jee5 schemas without redistributing them
Posted by Jason Dillon <ja...@planet57.com>.
Why are jee5 bits in the schema/j2ee_1.4/trunk?
Do we need to rename this dir? If we want one project for all
schemas, then we should drop the intermediate j2ee_1.4 dir and just
make a schema/trunk.
Why is the version set to 1.0? Trunk versions should almost never
bet set to anything that does not have a SNAPSHOT in it.
Is geronimo-schema-jee_5 intended to be hooked up, as it is not
listed in the parents modules?
Its missing LICENSE.txt and NOTICE.txt
Why is jee5.patch checked in?
--jason
On Sep 12, 2006, at 2:59 PM, David Jencks (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/GERONIMO-2397?
> page=comments#action_12434292 ]
>
> David Jencks commented on GERONIMO-2397:
> ----------------------------------------
>
> I've committed a build of the jee5 schemas in the tck directory.
> Jason, could you take a look and if it looks ok push some snapshots
> to the appropriate location?
>
>> Need to use the jee5 schemas without redistributing them
>> --------------------------------------------------------
>>
>> Key: GERONIMO-2397
>> URL: http://issues.apache.org/jira/browse/
>> GERONIMO-2397
>> Project: Geronimo
>> Issue Type: Bug
>> Security Level: public(Regular issues)
>> Components: deployment
>> Affects Versions: 1.2
>> Reporter: David Jencks
>> Assigned To: David Jencks
>> Fix For: 1.2
>>
>>
>> AFAICT the jee5 schemas have the same vague language prohibiting
>> redistribution as the j2ee 1.4 schemas, so we better not have them
>> in publically accessible svn.
>> Just as we did for the j2ee 1.4 schemas I'll set up a module in
>> tck that builds xmlbeans source and binary jars for the jee5
>> schemas and remove them from the sandbox/servlet2.5 where they are
>> publically available today.
>
> --
> 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
>
>