The following issue has been updated:

    Updater: Scott T Weaver (mailto:[EMAIL PROTECTED])
       Date: Wed, 19 May 2004 8:42 AM
    Changes:
             description changed from  to What I had started doing in my branch was 
moving interfaces out of the component implementations and portal/ and into commons.  
This makes it easier to test components that may access these other interfaces without 
having to specifically depend on the component implementation.  This also makes our 
code more modular and extensible.  Say, for example, some one wants to implement a 
persistence store using Hibernate.  As the current source layout is set up, the user 
would have a dependency on the the current persistence store implementation built with 
OJB because that is where the interfaces are leading them to having to have ALL the 
dependencies OJB required also.  By moving all the persistence store interfaces up 
into commons, all the developer needs as dependency is the jetspeed 2 commons jar.
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/JS2-30?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS2-30

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS2-30
    Summary: Create a Jetspeed 2 "core" sub project
       Type: Task

     Status: Open
   Priority: Major

    Project: Jetspeed 2
 Components: 
             Components Core
   Versions:
             2.0-a1

   Assignee: Scott T Weaver
   Reporter: Scott T Weaver

    Created: Wed, 19 May 2004 8:15 AM
    Updated: Wed, 19 May 2004 8:42 AM

Description:
What I had started doing in my branch was moving interfaces out of the component 
implementations and portal/ and into commons.  This makes it easier to test components 
that may access these other interfaces without having to specifically depend on the 
component implementation.  This also makes our code more modular and extensible.  Say, 
for example, some one wants to implement a persistence store using Hibernate.  As the 
current source layout is set up, the user would have a dependency on the the current 
persistence store implementation built with OJB because that is where the interfaces 
are leading them to having to have ALL the dependencies OJB required also.  By moving 
all the persistence store interfaces up into commons, all the developer needs as 
dependency is the jetspeed 2 commons jar.


---------------------------------------------------------------------
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]

Reply via email to