What I like in particular is that you change the element 'build' into set.
The name build gives the impression it is an action that is described, while
it is actually a structure of a project, upon which the generic actions are
based.
Gino.
> -Original Message-
> Hi,
>
> Based on the dis
> > > The layout in repository was intentionally fixed. There
> > > are good reasons for that.
> > > I think that support for other protocols than file:// and
> > > http:// can be considered if there will be more users
> > > demanding it.
> > > If you want to use ftp:// you can rise an issue in J
> The layout in repository was intentionally fixed. There are good reasons
for
> that.
> I think that support for other protocols than file:// and http:// can be
> considered
> if there will be more users demanding it.
> If you want to use ftp:// you can rise an issue in JIRA.
>
> I personally th
> > 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 mav
I know that Maven new is not really usable yet, 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. If I have to create my
own plugins, I want to make sure I use Maven new instead of Maven. In
p
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.
