The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 8 Sep 2004 12:37 AM
Body:
For me, it would be prudent to have the public API as a separate jar, jelly-api that
jelly itself depended on.
That way, people would easily know if they were dependent on the API or the
implementation.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JELLY-24?page=comments#action_52955
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JELLY-24
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JELLY-24
Summary: Release Issue 2 - Jelly public API
Type: Task
Status: Open
Priority: Minor
Project: jelly
Components:
documentation
Fix Fors:
1.0
Assignee: Morgan Delagrange
Reporter: Morgan Delagrange
Created: Thu, 23 Jan 2003 12:32 PM
Updated: Wed, 8 Sep 2004 12:37 AM
Description:
We started a discussion on what constitutes our public-facing API, but so far we
haven't nailed it down:
http://marc.theaimsgroup.com/?t=104153085900002&r=1&w=2
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
