You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by Karl Wettin <ka...@gmail.com> on 2008/04/19 00:39:45 UTC
Maven (was: Thread safety)
Grant Ingersoll skrev:
> Of course, perhaps, if and when Mahout is a TLP, Taste will be a
> complete self-contained sub project.
I'm taking this oppertunity to lobby for moving the code base to
trunk/core so we get a Maven project structure and not Maven modeule
structure.
My arguments are:
It is a very small change and nothing else have to change.
We already committed to a Maven file structure and it is silly to not do
it all the way. It's going to be a bigger hassle to refactor it to a
Maven project structure if we want to do it in the future, i.e. when we
want to seperate things in to sub projects, modules, contrib area, et c.
I know I have the powers, but I'm not going to do this change when all
the other votes have been 0- (if there was such a thing). ;)
karl
Re: Maven
Posted by Isabel Drost <ap...@isabel-drost.de>.
On Saturday 19 April 2008, Karl Wettin wrote:
> I.e. create a module call core and mode all the code there.
+1 from me.
--
Strategy: A long-range plan whose merit cannot be evaluated until sometime
after those creating it have left the organization.
|\ _,,,---,,_ Web: <http://www.isabel-drost.de>
/,`.-'`' -. ;-;;,_
|,4- ) )-,_..;\ ( `'-'
'---''(_/--' `-'\_) (fL) IM: <xm...@spaceboyz.net>
Re: Maven
Posted by Karl Wettin <ka...@gmail.com>.
> I.e. create a module call core and mode all the code there.
>
I'm glad you're all cool with this.
I'll soon execute:
> svn mkdir https://svn.apache.org/repos/asf/lucene/mahout/trunk/core -m "MAHOUT-17, Use Maven project file system"
> svn mv https://svn.apache.org/repos/asf/lucene/mahout/trunk/build.xml https://svn.apache.org/repos/asf/lucene/mahout/trunk/core -m "MAHOUT-17, Use Maven project file system"
> svn mv https://svn.apache.org/repos/asf/lucene/mahout/trunk/src https://svn.apache.org/repos/asf/lucene/mahout/trunk/core -m "MAHOUT-17, Use Maven project file system"
> svn mv https://svn.apache.org/repos/asf/lucene/mahout/trunk/lib https://svn.apache.org/repos/asf/lucene/mahout/trunk/core -m "MAHOUT-17, Use Maven project file system"
karl
Re: Maven
Posted by Sean Owen <sr...@gmail.com>.
FWIW I am feeling a +1 on this. It feels like a decent bit of
future-proofing of our directory structure.
On Fri, Apr 18, 2008 at 7:25 PM, Karl Wettin <ka...@gmail.com> wrote:
> Nothing at all. I just want to:
>
> svn co http://svn.../trunk trunk
> cd trunk
> mkdir core
> svn mv * core
> svn commit
>
> I.e. create a module call core and mode all the code there.
>
> Future modules would then be placed in trunk root just as core, not as some
> sub directory of the core.
>
> I just want to support Maveners like my self the use it to set up the
> development environment. It is very handy when if you like me create a new
> copy of the trunk for each patch you work on.
>
> Official build, test, et c would still be Ant. Some root build.xml would
> have to be produced the day a second module is added.
Re: Maven
Posted by Karl Wettin <ka...@gmail.com>.
Sean Owen skrev:
> (What can I do to prepare? I think my stuff is laid out very very
> standardly and I have a Maven pom.xml even, which I can bring forward.
> I always thought Maven was a small pain to maintain, but, that's
> because I wasn't using it myself and getting value.)
Nothing at all. I just want to:
svn co http://svn.../trunk trunk
cd trunk
mkdir core
svn mv * core
svn commit
I.e. create a module call core and mode all the code there.
Future modules would then be placed in trunk root just as core, not as
some sub directory of the core.
I just want to support Maveners like my self the use it to set up the
development environment. It is very handy when if you like me create a
new copy of the trunk for each patch you work on.
Official build, test, et c would still be Ant. Some root build.xml would
have to be produced the day a second module is added.
karl
Re: Maven (was: Thread safety)
Posted by Ozgur Yilmazel <oz...@gmail.com>.
+1 for the change.
On Sat, Apr 19, 2008 at 8:05 AM, Grant Ingersoll <gs...@apache.org> wrote:
>
> On Apr 18, 2008, at 6:45 PM, Sean Owen wrote:
>
>
> > (What can I do to prepare? I think my stuff is laid out very very
> > standardly and I have a Maven pom.xml even, which I can bring forward.
> > I always thought Maven was a small pain to maintain, but, that's
> > because I wasn't using it myself and getting value.)
> >
> > I have no preference really but give it +0.5 on the grounds that Grant
> > thinks it is a good idea.
> >
>
> +1 on the change, but just note it is never just up to me. I don't have
> any more special powers than anyone else and my +/-1 weighs exactly the same
> as everyone else.
>
Re: Maven (was: Thread safety)
Posted by Grant Ingersoll <gs...@apache.org>.
On Apr 18, 2008, at 6:45 PM, Sean Owen wrote:
> (What can I do to prepare? I think my stuff is laid out very very
> standardly and I have a Maven pom.xml even, which I can bring forward.
> I always thought Maven was a small pain to maintain, but, that's
> because I wasn't using it myself and getting value.)
>
> I have no preference really but give it +0.5 on the grounds that Grant
> thinks it is a good idea.
+1 on the change, but just note it is never just up to me. I don't
have any more special powers than anyone else and my +/-1 weighs
exactly the same as everyone else.
Re: Maven (was: Thread safety)
Posted by Sean Owen <sr...@gmail.com>.
By "Grant" I mean "Karl".
On Fri, Apr 18, 2008 at 6:45 PM, Sean Owen <sr...@gmail.com> wrote:
> I have no preference really but give it +0.5 on the grounds that Grant
> thinks it is a good idea.
Re: Maven (was: Thread safety)
Posted by Sean Owen <sr...@gmail.com>.
(What can I do to prepare? I think my stuff is laid out very very
standardly and I have a Maven pom.xml even, which I can bring forward.
I always thought Maven was a small pain to maintain, but, that's
because I wasn't using it myself and getting value.)
I have no preference really but give it +0.5 on the grounds that Grant
thinks it is a good idea.
On Fri, Apr 18, 2008 at 6:39 PM, Karl Wettin <ka...@gmail.com> wrote:
> Grant Ingersoll skrev:
>
> > Of course, perhaps, if and when Mahout is a TLP, Taste will be a complete
> self-contained sub project.
> >
>
> I'm taking this oppertunity to lobby for moving the code base to trunk/core
> so we get a Maven project structure and not Maven modeule structure.
>
> My arguments are:
>
> It is a very small change and nothing else have to change.
>
> We already committed to a Maven file structure and it is silly to not do it
> all the way. It's going to be a bigger hassle to refactor it to a Maven
> project structure if we want to do it in the future, i.e. when we want to
> seperate things in to sub projects, modules, contrib area, et c.
>
>
> I know I have the powers, but I'm not going to do this change when all the
> other votes have been 0- (if there was such a thing). ;)
>
>
>
> karl
>
>