Joachim- >
> On 7 March 2013 22:27, Joachim Durchholz <[email protected]> wrote:
> [del]
> > That's not really what I want.
> > I want a declarative specification so the tool can decide what build steps
> > to run. MG>in other words you want to build out a new lifecycle.xml
> > I want full scripting only for the individual build steps. This probably
> > means an obligation to specify the declarative metadata so the tool can set
> > up its build plan. MG>in other words new lifecycle.xml Plus this probably
> > also means that people will need a way
> > to test whether their metadata are correct, since otherwise people will get
> > subtle errors into the build plans.
> > xml-maven-pluginhttp://mojo.codehaus.org/xml-maven-plugin/validation.html
> >
> > I also want Eclipse integration, so build configuration doesn't need to be
> > specified redundantly.
MG>we should concentrate on getting the mechanics of 1)enforcing the xml is
valid with
xml-maven-pluginhttp://mojo.codehaus.org/xml-maven-plugin/validation.html
2)Build a CustomMojo to implement altered lifecycle.xml
http://www.sonatype.com/books/mvnref-book/reference/writing-plugins-sect-plugins-lifecycle.html
these steps should be completed before any attempt at refactoring as eclipse
plugin
>
> If you find such a tool, I'd be interested to hear about it.
> I dont believe such a thing exists.
>
> Which means you are going to have to write it and support it.
>
> You would be much better off taking something that is "close enough"
> and joining in the effort with others to make it better. Whether that
> is Maven or Gradle, or some other thing.
>
MG>Martin
