Fulcrum Separation

[Jason van Zyl <jv...@apache.org>]

Hi,

I want to start checking in the fulcrum repository over the next two
days so I thought I'd go over the plan to see if anyone wants
to pipe up before I start.

There will be a core package which will consist of the classes in
the org.apache.turbine.services package. I would really like to
get rid of any turbine references so I would like to change
the package to:

org.apache.fulcrum

All of this code will exist in src/core and will be packaged
in a jar called fulcrum-core-{version}.jar

All the services will live in src/services and each service
will have it's own build with its own stated dependencies. The
build will look like that of Torque's.

I would also like to change the package for most of the services
except for rundata and intake which are turbine specific. Each
of the services will be packaged in a JAR with the following
convention: fulcrum-{service}-{version}.jar

I've borrowed the JAR loader from some code in Velocity that
Dave wrote.

I plan to be able to pull default configuration information out
of the JARS, but the core package will also obey a Fulcrum.properties
file if it is present. I am also working on a web console that can
be used to configure fulcrum from a webapp.

I would like to get Fulcrum (and Torque) in a state where they
are usable on their own and try to get non-turbiner's developing
with these tools which is why I'd like to ditch the turbine
package namespace.


-- 

jvz.

Jason van Zyl

http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons



---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org

Re: Fulcrum Separation

[Kasper Nielsen <ne...@kav.dk>]

----- Original Message -----
From: "Jon Stevens" <jo...@latchkey.com>
To: <tu...@jakarta.apache.org>
Sent: Tuesday, July 31, 2001 8:02 AM
Subject: Re: Fulcrum Separation


>
> The Java Apache "standards" have so far dicated that the top level package
> name reflect top level projects. Fulcrum is not a top level project, I'm
> not saying that this issue about package name "standards" can't be
> discussed on General@Jakarta, I'm just saying that this has been the
> history to date.
Standard??? well we allready have

org.apache.log (Avalon Logkit)
org.apache.testlet (Avalon testlet)
org.apache.service (Tomcat is creating a new service framework i guess) see
http://cvs.apache.org/viewcvs/jakarta-tomcat-4.0/service/java/Service.java?r
ev=1.1&content-type=text/vnd.viewcvs-markup if you don't believe me
org.apache.jasper34 (Tomcat)
org.apache.tools (Ant)

Didn't bother looking for more, im sure there are at least 10-20 more
So I guess this isn't much of a standard.

im +1 on org.apache.fulcrum


- Kasper



---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org

Re: Fulcrum Separation

[Jon Stevens <jo...@latchkey.com>]

The Java Apache "standards" have so far dicated that the top level package
name reflect top level projects. Fulcrum is not a top level project, I'm
not saying that this issue about package name "standards" can't be
discussed on General@Jakarta, I'm just saying that this has been the
history to date.

My personal feeling is that it should be org.apache.turbine.fulcrum

thanks,

-jon

On Mon, 30 Jul 2001, Jason van Zyl wrote:

> Hi,
>
> I want to start checking in the fulcrum repository over the next two
> days so I thought I'd go over the plan to see if anyone wants
> to pipe up before I start.
>
> There will be a core package which will consist of the classes in
> the org.apache.turbine.services package. I would really like to
> get rid of any turbine references so I would like to change
> the package to:
>
> org.apache.fulcrum
>
> All of this code will exist in src/core and will be packaged
> in a jar called fulcrum-core-{version}.jar
>
> All the services will live in src/services and each service
> will have it's own build with its own stated dependencies. The
> build will look like that of Torque's.
>
> I would also like to change the package for most of the services
> except for rundata and intake which are turbine specific. Each
> of the services will be packaged in a JAR with the following
> convention: fulcrum-{service}-{version}.jar
>
> I've borrowed the JAR loader from some code in Velocity that
> Dave wrote.
>
> I plan to be able to pull default configuration information out
> of the JARS, but the core package will also obey a Fulcrum.properties
> file if it is present. I am also working on a web console that can
> be used to configure fulcrum from a webapp.
>
> I would like to get Fulcrum (and Torque) in a state where they
> are usable on their own and try to get non-turbiner's developing
> with these tools which is why I'd like to ditch the turbine
> package namespace.
>
>
> --
>
> jvz.
>
> Jason van Zyl
>
> http://tambora.zenplex.org
> http://jakarta.apache.org/turbine
> http://jakarta.apache.org/velocity
> http://jakarta.apache.org/alexandria
> http://jakarta.apache.org/commons
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org