Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of mario@ops.co.at designates
 194.152.182.4 as permitted sender)
Message-ID: <44C89721.2020105@ops.co.at>
Date: Thu, 27 Jul 2006 12:36:17 +0200
From: Mario Ivankovits <mario@ops.co.at>
User-Agent: Thunderbird 1.5.0.4 (X11/20060527)
MIME-Version: 1.0
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
Subject: Re: [VFS] Snapshot timestamped version has disappeared from the m1
 snapshot repo!
References: <010601c6b163$dc68c450$6601a8c0@massol>
In-Reply-To: <010601c6b163$dc68c450$6601a8c0@massol>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Vincent!
> 1) Do a release of those projects.
Commons-compress is on the way.
Slide is simply not my project, I am neither a committer nor a
contributor, so I cant decide to release it.
What I'll do once compress is there and the lgpl stuff has solved, is,
to have a oversight about the activity of this project then, and then
move the parts depending on inactive projects into its own jar as you
outline below.

> 2) Separate VFS core from the different filesystem implementations:
> - vfs-core.jar
> - vfs-fs-ram.jar, etc
>   
I dont think that the users want have such fine grained bundles, I
perfectly understand that it fits your needs, but having to put e.g. 10
vfs jars to get what you have now might become a pain.
This decision is not put in stone, if other users come up telling me
that they would appreciate it, I can go to the dev list and discuss this
further.

Though, an additional question come in my mind with such a solution:
I have to release each "artifact" on its own to make the scenario work,
not only that the releases then start to divergence, do I have to start
a vote for each of them then?
The other developer have to check releases during the vote, this means a
great multiplication of work.
Whew .... I already hear what they will tell me ;-)

Hmmm .... but having
- vfs.jar
- vfs-extensions.jar - where in extensions (or what name ever) all the
code is which is not releasable ... well ... this can be done.

I'll move to commons-dev with this - Follow me :-)

Ciao,
Mario


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