Thank Robert and Anders for the feedback.
There may be some confusion here, so let me add some clarification first:
The vfs plugin currently in the sandbox has 3 parts:
1. the plugin itself
2. vfs-utils: a java component that the plugin depends on
3. vfs-smb is the vfs provider comes right out of apache
commons-vfs's sandbox.
with minor change due newer cifs dependency. I already have a discussion
at commons-dev and filed a task to release it. However, due to lacking of
source, i dont think it will be release any time soon
Here are my answer to Robert
> shouldn't vfs be something like wagon-extra?
not sure vfs has any thing to do with wagon extra
> What is your idea what will happen once commons-vfs is released?
Once vfs promote its smb provider out of sand box and release it
together with commons-vfs ( 2.x ). I will immediately release another
version of vfs-maven-plugin without its vfs-smb module ( ie retire it )
> I cannot imagine they'll make a maven-plugin as part of their release
that is the idea situation, we have quite a few plugins started at MOJO
and transfer back to the upstream project
>IMO codehaus shouldn't be used as a kickoff area if you're sure that this is
>not the final destination of the plugin.
@for Anders as well
This something i am confuse about, we are doing it for years.
Are you suggesting me to move the entire vfs-maven-plugin to github?
I am not ready to go there yet, this is where I comfortable with for years
and feedbacks and helps here are great.
Thanks
-Dan
On Sat, Sep 22, 2012 at 7:11 AM, Anders Hammar <[email protected]> wrote:
> I'm with Robert here. If you're just looking for some area to do
> releases from you should start your own Github account and use
> Sonatype OSSRH for syncing to central.
>
> /Anders
>
> On Sat, Sep 22, 2012 at 11:45 AM, Robert Scholte <[email protected]>
> wrote:
>> Hi Dan,
>>
>> shouldn't vfs be something like wagon-extra?
>> What is your idea what will happen once commons-vfs is released? I cannot
>> imagine they'll make a maven-plugin as part of their release (that would be
>> the first commons-project).
>> As you mentioned yourself: the packaging is now confusing, but that all
>> depends on the future of this plugin.
>> IMO codehaus shouldn't be used as a kickoff area if you're sure that this is
>> not the final destination of the plugin.
>>
>> Robert
>>> Date: Fri, 21 Sep 2012 10:35:58 -0700
>>> From: [email protected]
>>> To: [email protected]
>>> Subject: [mojo-dev] Re: Intention to promote and release vfs-maven-plugin
>>> beta 1 and its sub components
>>>
>>> ping,
>>>
>>> Looks like no objection on proceeding to release vfs-smb at codehaus :-)
>>>
>>> -D
>>>
>>> On Thu, Sep 20, 2012 at 9:26 AM, Dan Tran <[email protected]> wrote:
>>> > Hello,
>>> >
>>> > After a few months of testing internally, I would like to proceed with
>>> > the first beta release. However, I would like to open a discussion on
>>> > distribution of vfs-smb which is a fork from apacche's commons-vfs's
>>> > sandbox. This provider passes all of the generic test suite ( except
>>> > 2 related to classloader, may related to osgi requirements ), the
>>> > provider will not be release any time soon either.
>>> >
>>> > So I would like release vfs-smb at codehaus, keep the same java
>>> > package name, until commns-vfs officially release it
>>> >
>>> > Any objection for me do so, otherwise please provide alternative
>>> > solution
>>> >
>>> > big thanks ahead
>>> >
>>> > -Dan
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>> http://xircles.codehaus.org/manage_email
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
