Re: [PROPOSAL] move doxia-book and doxia-maven-plugin from Doxia base to Doxia Sitetools

2012-03-30 Thread Lukas Theussl
Hervé BOUTEMY wrote: Le samedi 31 mars 2012 08:24:50 Lukas Theussl a écrit : The other way round was it? doxia-book into Doxia Tools and doxia-maven-plugin into Sitetools. -Lukas no, Tools can depend on Sitetools, but not the other way Right, didn't think about the dependencies. I'd move b

Re: [PROPOSAL] move doxia-book and doxia-maven-plugin from Doxia base to Doxia Sitetools

2012-03-30 Thread Hervé BOUTEMY
Le samedi 31 mars 2012 08:24:50 Lukas Theussl a écrit : > The other way round was it? doxia-book into Doxia Tools and > doxia-maven-plugin into Sitetools. > > -Lukas no, Tools can depend on Sitetools, but not the other way the other ways would be do move both modules to Tools or Sitetools but not

Re: [PROPOSAL] move doxia-book and doxia-maven-plugin from Doxia base to Doxia Sitetools

2012-03-30 Thread Lukas Theussl
Hervé BOUTEMY wrote: ok so: 1. doxia-book from Doxia to Doxia Sitetools, same artifact coordinates: org.apache.maven.doxia:doxia-book, 1.2 is from Doxia tree, 1.3-SNAPSHOT will be from Doxia Sitetools 2. doxia-maven-plugin from Doxia to Doxia Tools, same artifact coordinates: org.ap

Re: [PROPOSAL] move doxia-book and doxia-maven-plugin from Doxia base to Doxia Sitetools

2012-03-30 Thread Hervé BOUTEMY
ok so: 1. doxia-book from Doxia to Doxia Sitetools, same artifact coordinates: org.apache.maven.doxia:doxia-book, 1.2 is from Doxia tree, 1.3-SNAPSHOT will be from Doxia Sitetools 2. doxia-maven-plugin from Doxia to Doxia Tools, same artifact coordinates: org.apache.maven.doxia:doxia-maven

configuration maven 3

2012-03-30 Thread rachmery
hi, i want to install maven3 and when i execute this Command "mvn archetype:create -DgroupId=testapp -DartifactId=testapp" i receive this error: Code: Select all[ERROR] No plugin found for prefix 'archetype' in the current project and in the plugin groups [org.mortbay.jetty, org.apache.maven.plugi

instalation maven 3

2012-03-30 Thread rachmery
hi, i want to install maven3 and when i execute this Command "mvn archetype:create -DgroupId=testapp -DartifactId=testapp" i receive this error: Code: Select all[ERROR] No plugin found for prefix 'archetype' in the current project and in the plugin groups [org.mortbay.jetty, org.apache.maven.plugi

Re: SCM initRepo method

2012-03-30 Thread Chris Graham
True. But that is for another day, as those changes need to be looked at in the light of all of the CMS systems supported, including those in the non-apache codebase. Yes, I do see the need for a higher level of abstraction needed, as the original API's were very much built around CVS, later SVN a

Re: SCM initRepo method

2012-03-30 Thread Robert Scholte
Hi, Not every SCM is repository-based. I see more and more differences between SCM's. Should we split it into Client/Server versus Distributed model? -Robert Op Fri, 30 Mar 2012 09:46:51 +0200 schreef Chris Graham : Heh. Done! -Chris On Fri, Mar 30, 2012 at 6:03 PM, Olivier Lamy wrote:

Re: [PROPOSAL] move doxia-book and doxia-maven-plugin from Doxia base to Doxia Sitetools

2012-03-30 Thread Lukas Theussl
Dennis Lundberg wrote: On 2012-03-29 09:13, Lukas Theussl wrote: I agree that they don't belong into core, but I rather thought of moving them into doxia-tools instead. Not sure what is better. This was my thought also. OTOH, neither book nor maven-plugin have been maintained (AFAIK) sinc

Re: SCM initRepo method

2012-03-30 Thread Chris Graham
Heh. Done! -Chris On Fri, Mar 30, 2012 at 6:03 PM, Olivier Lamy wrote: > just do it in your coming patch :-) > > 2012/3/30 Chris Graham : > > Any ideas of how to get to initialised loggers (from the plexus > container) > > in this method? > > My only option so far, is a new DefaultLog(). > > >

Re: SCM initRepo method

2012-03-30 Thread Olivier Lamy
just do it in your coming patch :-) 2012/3/30 Chris Graham : > Any ideas of how to get to initialised loggers (from the plexus container) > in this method? > My only option so far, is a new DefaultLog(). > > I'd perfer to use the normal ConsoleLogger etc as set up by the container, > and available