On 2012-09-22 23:13, Dan Tran wrote: > On Sat, Sep 22, 2012 at 1:48 PM, Robert Scholte <[email protected]> > wrote: >> So it is really another type of beast for file transportation. >> It's a shame that this won't work with Wagon, because that would mean that >> this can only be used as plugin and never as extension, right? > > Correct. I dont intend to make it as a maven extension until there is > a real need for it > >> So I'm ok with the maven-plugin (although it uses a weird package right now), > > you mean with the name: vfs-maven-plugin? if so, yes it wont make > any sense until user google it > >> but not with the patched fork. >> Forks can be a start for a lot of trouble (see Mark Strubergs mail about the >> osx-maven-plugin lately). >> If we start with such behavior, that's not a good sign. >> > > You have not convinced me that temporary release this plugin's vfs-smb > provider at codehaus is a bad sign. > I could not imaging this provider would land here forever.
If you fork a piece of open source software and plan to release it, you MUST change the groupId/artifactId/version. You cannot get an artifact with a groupId that starts with "org.apache" into central. Such an artifact can only come from the Apache sync. If you fork a piece of open source software and plan to release it, you SHOULD change the java package to prevent class conflicts with potentially upcoming releases from the original authors of the software. Let me see if I can do anything to facilitate the promotion of vfs-smb out of the sandbox over at the Commons project. >> There's one bug in the release-plugin, which would help in your case >> (actually, it is one I've started to work on recently) >> the maven-release-plugin can't detect SNAPSHOTs defined as plugin >> dependency. > > Not sure if the current discussion has any thing to do with release plugin > >> >> Anyhow, I'm just 1 of the team, maybe others think otherwise. >> > >> Robert > > Thanks > > >>> Date: Sat, 22 Sep 2012 13:10:53 -0700 >> >>> From: [email protected] >>> To: [email protected] >>> Subject: Re: [mojo-dev] Re: Intention to promote and release >>> vfs-maven-plugin beta 1 and its sub components >>> >>>> I hope you meant vfs-maven-plugin when you said svn-maven-plugin... >>> >>> Sorry, typo >>> >>>> So you forked the current commons-vfs, but did you patch it too? In not, >>>> why >>> >>> No I only fork commons-vfs's smb provider from commons-vfs's sandbox >>> I do provide a patch for it it at >>> https://issues.apache.org/jira/browse/VFS-438. >>> my vfs-maven-plugin works directory with commons-vfs-2.0 ( core and >>> all of its available providers ) >>> >>> I would prefer not to shade it, since i may not work with VFS >>> provider discovery. >>> >>> One compromise is to rename the codehaus's vfs-smb provider form >>> org.apache.commns.vfs >>> to org.codehaus.mojo.vfs. But I dont see it is logistically >>> necessary ( best to document it ) >>> >>> >>> >>>> Is there a reason why you need is this fast? >>> >>> Yes, i am about to use it in production ( I need to release my >>> internal project which depends on vfs-maven-plugin and its components >>> ( including the forked smb provider ) >>> >>>> Is there a way to merge this with >>>> http://mojo.codehaus.org/wagon-maven-plugin/ (I wasn't aware this was a >>>> codehaus project) >>> >>> It not possible to merge with wagon-maven-plugin( I am the main >>> maintainer of this w.m.p ) since the it heavily depends on maven local >>> runtime >>> >>> my vfs-maven-plugin, is the attempt to replace wagon-maven-plugin >>> >>> >>> >>> >>> On Sat, Sep 22, 2012 at 12:55 PM, Robert Scholte <[email protected]> >>> wrote: >>>> >>>> I hope you meant vfs-maven-plugin when you said svn-maven-plugin... >>>> >>>> I've reread your original mail and just noticed a small >>>> misunderstanding. >>>> So you forked the current commons-vfs, but did you patch it too? In not, >>>> why >>>> not use the maven-shade-plugin. >>>> Otherwise I'd prefer to wait for the first release of commons-vfs. >>>> Is there a reason why you need is this fast? >>>> >>>> Is there a way to merge this with >>>> http://mojo.codehaus.org/wagon-maven-plugin/ (I wasn't aware this was a >>>> codehaus project) >>>> >>>> -Robert >>>> >>>> ps. my verdict is -0 >>>>> Date: Sat, 22 Sep 2012 12:28:57 -0700 >>>>> From: [email protected] >>>>> To: [email protected] >>>> >>>>> Subject: Re: [mojo-dev] Re: Intention to promote and release >>>>> vfs-maven-plugin beta 1 and its sub components >>>>> >>>>> So what is the verdict here?, Is it ok to release my vfs-smb together >>>>> with svn-maven-plugin at codehaus until commons-vfs promote it. Let's >>>>> user test this out, that is why we call it beta. >>>>> I dont see any logistic problem with this approach. >>>>> >>>>> and I do like the ldea to campaigning commons-vfs to accept it and I >>>>> would volunteer to maintain it there. But that is another journey >>>>> >>>>> Thanks >>>>> >>>>> -D >>>>> >>>>> On Sat, Sep 22, 2012 at 12:11 PM, Robert Scholte >>>>> <[email protected]> >>>>> wrote: >>>>>> Let me rephrase this a bit: >>>>>> I think what happened to the tomcat-maven-plugin is a good thing: let >>>>>> the >>>>>> developers of the framework/webcontainer/tool/etc. maintain their own >>>>>> Maven >>>>>> plugin. >>>>>> Most of the time you want to keep these in sync. >>>>>> For instance: we're having quite some trouble to follow the pace of >>>>>> GWT. >>>>>> To me your situation looks similar to the tomcat-situation. >>>>>> >>>>>> About the wagon-extra: I thought the vfs-project is about >>>>>> InputStreams >>>>>> and >>>>>> OutputStreams, just like the Wagon-project. But I can be wrong here. >>>>>> >>>>>> Robert >>>>>>> Date: Sat, 22 Sep 2012 20:55:15 +0200 >>>>>>> From: [email protected] >>>>>>> To: [email protected] >>>>>>> Subject: Re: [mojo-dev] Re: Intention to promote and release >>>>>>> vfs-maven-plugin beta 1 and its sub components >>>>>> >>>>>>> >>>>>>>> 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. >>>>>>> >>>>>>> No. I was just saying that Mojo shouldn't be used just to get some >>>>>>> jar >>>>>>> to central. But it's a good place for a plugin that could be of >>>>>>> interest for other people. >>>>>>> >>>>>>> /Anders >>>>>>> >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> 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 >>> >>> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
