mockobjects-java-dev — For people who are working on the implementation of the java version

Re: [Mockobjects-java-dev] Change of license ?

[Steve F. <st...@m3...>]

----- Original Message -----
From: "Vincent Massol" <vm...@oc...>
To: <moc...@li...>
Sent: Sunday, July 29, 2001 11:40 PM
Subject: [Mockobjects-java-dev] Change of license ?


> Hi,
>
> I would like to propose a change in the license. Would you agree to move
> from  Mozilla license to an Apache license (APL) ? The reason I have is
> simply that it is easier to change license early in a project rather than
> later and it seems Cactus and mockobjects might integrate/share/benefit
from
> each other more easily if the mockobject project was under an Apache
license
> (because Cactus is already using that license as an Apache project). For
> example, Cactus could use mockobjects as its implementation for a MO
> strategy ...
>
> What do you think ?
>

In principle I don't mind. What are the
differences between the two licences?

Steve

[Mockobjects-java-dev] Build process progress

[Vincent M. <vm...@oc...>]

We now have a fully functional build process which does :
- jar
- documentation (local web site + javadoc)
- site generation
- unit tests
- dist : build the distributables. Currently only one :

mockobjects-0.01.zip containing
  |_ lib
    |_ mockobjects.jar
  |_ doc
    |_ local web site + javadoc

Try it and tell me if you like it !

TODO: Depending on the answer to previous emails, we need to know what we do
with the extensions and samples. For samples, I guess we can put them in
mockobjects-0.01.zip.

-Vincent

[Mockobjects-java-dev] new changes page

[Vincent M. <vm...@oc...>]

Same as for the todo, there is now a changes page
(<root>/doc/xdocs/changes.xml) that contain the history changes for all
versions including the current one in CVS. This is a coarse-grained
changelog and is intended mostly for users so that they know what's new in
the latest release.

For example, if we modify a file because a comment was wrongly aligned, it
doesn't have to go in this changelog (it will be in the CVS changelog
anyway). however, if have fixed a bug or modified namings in the code or ...
then it needs to be there.

Please remember to always edit this file when you make a change. Otherwise
it is difficult and lengthy to find back what has been done (though it is
possible using CVS). It also shows us what's been done so far on the current
version, so it is a good indicator of progress.

Thanks
-Vincent

[Mockobjects-java-dev] new todo page

[Vincent M. <vm...@oc...>]

Hi,

I have added a todo/roadmap page : <root>/doc/xdocs/todo.xml
The goal of this page is twofold :
* first it shows to user what is left to be done before being able to
release the following version,
* second it lets everyone know who is working on what (I know there is also
a task assignment tracker in SF that we may use for that. This is just a
first draft. We may wish to remove the volunteer column later on and use
this tracker later on - we'll see).

So, if you think about a task that needs to be done, please update this
file. This will be our preferred way of deciding what tasks are left and for
what version to implement them.

Thanks
-Vincent

Re: [Mockobjects-java-dev] www.mockobjects.com and the mockobjects project ... same ?

[Vincent M. <vm...@oc...>]

----- Original Message -----
From: "Vincent Massol" <vm...@oc...>
To: <moc...@li...>
Sent: Monday, July 30, 2001 6:26 PM
Subject: [Mockobjects-java-dev] www.mockobjects.com and the mockobjects
project ... same ?


> I'd like to know if we want to make them be the same thing or if we want
to
> make www.mockobjects.com a portal site regrouping anything that's related
to
> Mock Objects : articles, tools, books, ... and have the mockobjects
project
> simply be a possible implementation (in java to start with) ?
>

I have drafted the main page of the Mock Objects web site (in
<root>/doc/xdocs/index.xml). Please tell me what you think. Also we need to
find a better logo. The problem with the mock turtle logo is that it being
black and white it does not lend well to resizing and is not clear and sharp
at all when in small ... But being too big it eats almost all the page and
the page titles look way too small in that big space ...:)

Ideally we would need a logo that takes more space horizontally than
vertically.

> Thanks
> -Vincent

-Vincent

[Mockobjects-java-dev] www.mockobjects.com and the mockobjects project ... same ?

[Vincent M. <vm...@oc...>]

I'd like to know if we want to make them be the same thing or if we want to
make www.mockobjects.com a portal site regrouping anything that's related to
Mock Objects : articles, tools, books, ... and have the mockobjects project
simply be a possible implementation (in java to start with) ?

Thanks
-Vincent

[Mockobjects-java-dev] Why 'vaj' and 'visualage' in extensions dir + others

[Vincent M. <vm...@oc...>]

Hi,

1/ Why is there 2 directories : 'vaj' and 'visualage' in the extensions
directory ?
2/ What is eziba ?
3/ Do we want to generate a separate jar file per extension, like one for
atg, one for visualage, one for eziba, ... ? My answer would be yes and it
seems it is the approach currently followed as proved by the released
packages on SF

Thanks
-Vincent

[Mockobjects-java-dev] Project description

[Vincent M. <vm...@oc...>]

I have entered the following project description on SF
(http://sf.net/projects/mockobjects).

"Generic unit testing framework and methodology for testing any kind of
code"

Tell me what you think. If you have a better description, feel free to post
it here.
Thanks

-Vincent

Re: [Mockobjects-java-dev] Prepackaged Ant version

[Vincent M. <vm...@oc...>]

----- Original Message -----
From: "Vincent Massol" <vm...@oc...>
To: <moc...@li...>
Sent: Monday, July 30, 2001 12:43 PM
Subject: [Mockobjects-java-dev] Prepackaged Ant version


> Building the mockobjects project requires :
> - a JDK installed
> - Ant installed with the needed tasks : stylebook (version 2), junit
> - depending on what mocks we want to build, some external jars (like
> servlet.jar if we want to build the servlet mocks, ...)
>
> In order to facilitate building the mockobjects project, I propose to
> provide on the developer web site (i.e. SF) a prepackaged zip containing
Ant
> with the needed tasks already in there. This is what I have done on the
> Cactus project and it's been very successful.
>

More precisely, I propose a new package named mockobjects-tools (in the
notes area we mention that it contains tools to help build the project for
developers and that it is not needed for end users) and put a file named :
mockobjects-java-ant-YYYYMMDD.zip

> Ok ?
> -Vincent Massol

[Mockobjects-java-dev] Prepackaged Ant version

[Vincent M. <vm...@oc...>]

Building the mockobjects project requires :
- a JDK installed
- Ant installed with the needed tasks : stylebook (version 2), junit
- depending on what mocks we want to build, some external jars (like
servlet.jar if we want to build the servlet mocks, ...)

In order to facilitate building the mockobjects project, I propose to
provide on the developer web site (i.e. SF) a prepackaged zip containing Ant
with the needed tasks already in there. This is what I have done on the
Cactus project and it's been very successful.

Ok ?
-Vincent Massol

[Mockobjects-java-dev] Deliverables and organization of the src tree

[Vincent M. <vm...@oc...>]

Hi,

I'd like to propose the following src directory hierarchy

src
  |_ framework
    |_ com
      |_ ...
  |_ tests
    |_ com
      |_ ...
  |_ extensions
    |_ com
      |_ ...
  |_ examples
    |_ com
      |_ ...

Where :

* framework : the core classes + mock implementations for the standard
J2SE/J2EE classes, i.e. the standard APIs making the Java platform (servlet,
taglib, io, sql, ...)
* tests : the core classes unit tests. Note that there is no need for test
classes for the mock implementations themselves as they don't contain logic
(just getters/setters)
* extensions : mock implementations for APIs that are _not_ part of the Java
platform (J2SE/J2EE), like VisualAge for Java Tools API, Struts, ATG
proprietary classes, ...
* examples : comprehensive examples showing how to use the mockobject
framework and also acting as functional tests for the mockobject framework.

Can I go ahead with this and make the little needed modifications and put a
README file that explains this ?
Thanks
-Vincent Massol

[Mockobjects-java-dev] What is mo_java1_compatibility.jar ?

[Vincent M. <vm...@oc...>]

In <root>/src/core, there is jar file (mo_java1_compatibility.jar)
containing sources. What is it and why are the sources in it not expanded,
like the rest ?

Thanks
-Vincent

[Mockobjects-java-dev] Forum removal

[Vincent M. <vm...@oc...>]

I have removed the forum feature from the mockobjects SF developers' page as
we have now switched to a mailing-list mechanism.

Note: There were only a few messages posted on the forum and none contained
information important enough to republish it to the mailing-list. However,
the messages posted to the forum are not lost and the forum can be
reactivated at any time by an admin if need be.

Thanks
-Vincent

[Mockobjects-java-dev] Change of license ?

[Vincent M. <vm...@oc...>]

Hi,

I would like to propose a change in the license. Would you agree to move
from  Mozilla license to an Apache license (APL) ? The reason I have is
simply that it is easier to change license early in a project rather than
later and it seems Cactus and mockobjects might integrate/share/benefit from
each other more easily if the mockobject project was under an Apache license
(because Cactus is already using that license as an Apache project). For
example, Cactus could use mockobjects as its implementation for a MO
strategy ...

What do you think ?

Thanks
-Vincent Massol