RE: Setting up Maven-New

2003-06-03 Thread Michal Maczka 



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, June 03, 2003 12:26 PM
 To: [EMAIL PROTECTED]
 Subject: RE: Setting up Maven-New


 I know that Maven new is not really usable yet,

I would say: it is really unusable ;)

but the
 committers have got
 a setup that they can use to test their changes, right?  I want
 to have this
 kind of setup, enabling me to evaluate Maven new.

There is ongoing development in maven-new/core maven-new/fetcher etc...
But as a whole it is still a puzzle box in 100 pieces, which needs to
be assembled.


If I have to create my
 own plugins, I want to make sure I use Maven new instead of Maven.

Maven-new should be backward compatible (not sure if in 100% but close).
So you can still write your plugins without looking at what is going on with
maven-new

In
 particular because I have seen better decomposition allowing me to e.g.
 extend the Project class and parse the project.xml myself.

Certainly there are side effects of the decomposition made in maven-new
which might result in such temptation to personalize your instance
of maven.
But if something is technicaly possible it does not necessarily mean that it
should be
applied/used.


Michal


 Regards,
 Gino.

 -Original Message-
 From: Michal Maczka [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, June 03, 2003 12:15 PM
 To: Maven Developers List
 Subject: RE: Setting up Maven-New


 AFAIK: maven-new is not yet usable.

 Michal

  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, June 03, 2003 12:09 PM
  To: [EMAIL PROTECTED]
  Subject: Setting up Maven-New
 
 
  Can someone guide me through the process of setting up and using
  Maven New?
  I always seem to get an XMLRPC exception upon execution of
  run-client -g,
  so I must be doing something wrong...
 
  On the client
  Exception in thread main java.lang.reflect.InvocationTargetException
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorIm
  pl.java:39
  )
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc
  cessorImpl
  .java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at
  com.werken.classworlds.Launcher.launchStandard(Launcher.java:408)
  at com.werken.classworlds.Launcher.launch(Launcher.java:342)
  at com.werken.classworlds.Launcher.main(Launcher.java:470)
  Caused by: org.apache.xmlrpc.XmlRpcException:
  java.lang.NullPointerException
  at
  org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(Xm
  lRpcClient
  ResponseProcessor.java:133)
  at
  org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(Xml
  RpcClientR
  esponseProcessor.java:101)
  at
 
 org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:102)
  at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:187)
  at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
  at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:172)
  at org.apache.maven.cli.CLI.doMain(CLI.java:116)
  at org.apache.maven.cli.CLI.main(CLI.java:83)
  ... 7 more
 
  On the server
  [DEBUG] Found a service descriptor for key: org.apache.maven.Maven
  [ERROR] Cannot start component lifecycle with role :
  org.apache.maven.Maven
  java.lang.NullPointerException
  at
  org.apache.maven.DefaultMaven.service(DefaultMaven.java;org/apache
  /maven/Pom
  InheritanceAspect.java[1k]:207)
  at
  org.apache.plexus.lifecycle.phase.ServicePhase.execute(ServicePhas
  e.java:24)
  at
  org.apache.plexus.lifecycle.AbstractLifecycleHandler.startLifecycl
  e(Abstract
  LifecycleHandler.java:145)
  at
  org.apache.plexus.service.repository.DefaultComponentRepository.st
  artCompone
  ntLifecycle(DefaultComponentRepository.java:426)
  at
  org.apache.plexus.service.repository.DefaultComponentRepository.lo
  okup(Defau
  ltComponentRepository.java:316)
  at org.apache.maven.server.XMLThing.execute(XMLThing.java:80)
  at
  org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:128)
  at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:185)
  at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:151)
  at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
  at
 org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:773)
  at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:656)
  at java.lang.Thread.run(Thread.java:536)
  basedir is set to Maven
 
  Many thanks,
  Gino.
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED

RE: Setting up Maven-New

2003-06-03 Thread Marckx_Gino 
  In particular because I have seen better decomposition allowing me to
  e.g. extend the Project class and parse the project.xml myself.
 
 Certainly there are side effects of the decomposition made in maven-new
 which might result in such temptation to personalize your instance
 of maven.
 But if something is technicaly possible it does not necessarily mean
 that it should be applied/used.

Well, we need a few features that cannot be integrated into the old maven
without actually changing the whole lot, while it can be plugged in as a
component easily in maven new's structure.
We have got two specific requirements.  One is that we cannot use the
central repository, but are bound to a local FTP repository, which follows
other naming conventions than the ones proposed by Maven.
The other thing is dat we need to support and publish multiple target
artifacts per project, and we need to be able to specify this somehow using
the Project class, meaning we need to parse the project.xml file ourselves,
although it is just a little extension.
If you can show me how to do this with plugins in the old Maven, I would be
glad to do so, but I'm afraid Maven old is just not flexible enough for our
needs...

Regards,
Gino.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]