incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Balaji Ravi (JIRA)" <j...@apache.org>
Subject [jira] Created: (YOKO-297) M2 release - separate yoko runtime module
Date Wed, 21 Feb 2007 23:27:06 GMT
M2 release - separate yoko runtime module
-----------------------------------------

                 Key: YOKO-297
                 URL: https://issues.apache.org/jira/browse/YOKO-297
             Project: Yoko - CORBA Server
          Issue Type: Task
    Affects Versions: 1.0-incubating-M2
            Reporter: Balaji Ravi
         Assigned To: Balaji Ravi
             Fix For: 1.0-incubating-M2
         Attachments: profile_for_M2.patch

I have attached the patch that contains the fixes needed to release just the core orb part
of yoko using profiles.

So, when run with the profile runtime(mvn -Pruntime) it will build only the core, spec &
rmi modules. It will leave out the api,
bindings & tools modules. But by default, everything would be built.

And when building the distribution, again when using profile runtime, a
runtime binary assembly will be included. The src assembly remains the
same.

After the M2 release, we will get rid of the profiles & retain only the
runtime binary assembly part.

The reason for doing this is purely to help out Geronimo because cxf at
this point is not stable, so we cannot release the complete yoko because
parts of it are dependent on CXF.

I am against splitting yoko in to 2 projects because i think the ORB is stable and we could
built the tools & WS-bindings around it to keep the yoko project moving forward. This
is where i see most of the development happen.

Once M2 goes out of the door, we would add bindings & api modules to the
runtime assembly, so that we have a clean separation of tools & runtime.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message