At some point you may become dissatisfied with <modelVersion>4.0</modelVersion model "limitations" in which case you will learn XML and become an expert and you will develop a)new ComplexTypes b)new XSDs that reference these new ComplexTypes c)create a new Model from the newly created XSDs d)build out a whole new (plexus-)classworlds-(newVersion).jar implementing the constructs from the new XSDs Eclipse deliberately obfuscates 99% of the "unnecessary engineering details" from the eclipse operator(s)
On the other hand *If* you can write a plugin for Eclipse (lets say a Android Terminal Emulator) you have my respect to write an eclipse plugin you will have to know xml (specfically plugin.xml) so eclipse can 'register' your plugin http://www.eclipse.org/articles/Article-Plug-in-architecture/plugin_architecture.html the analogy of learning XML in order to properly implement Maven is if you purchase a Masserati but you are unable to drive a stick then it stays in the garage Martin- > From: [email protected] > To: [email protected]; [email protected] > Subject: RE: Is it necessary to learn XML in order to lear Maven? > Date: Thu, 27 Jun 2013 15:54:20 +0000 > > I agree wholeheartedly. > > Cody Fyler > Lending Grid Build Team > [email protected] > (515)-441-0814 > > > -----Original Message----- > From: Ron Wheeler [mailto:[email protected]] > Sent: Thursday, June 27, 2013 10:52 AM > To: [email protected] > Subject: Re: Is it necessary to learn XML in order to lear Maven? > > On 27/06/2013 11:35 AM, [email protected] wrote: > > I would argue that to be a competent, modern computer programmer, you DO > > need to learn XML. > > > > There are many powerful things that can be accomplished once you have that > > knowledge. > You are right that in general XML is useful for lots of things and that > people who know lots of technologies have a much broader palette of solution > components However, the specific question relates to Maven and you really do > not need to have any more knowledge of XML than understanding that > <something> will be terminated by </something> and that they can be nested. > > You can use an IDE that will give you a graphic editor for your POM files. > You can cut and paste models of POMs. Your graphic editor should spot any > XML validation errors. > > Ron > > > > > Cody Fyler > > Lending Grid Build Team > > [email protected] > > (515)-441-0814 > > > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On > > Behalf Of Curtis Rueden > > Sent: Thursday, June 27, 2013 10:31 AM > > To: Maven Users List > > Subject: Re: Is it necessary to learn XML in order to lear Maven? > > > > Hi Nayana, > > > >> Is it necessary to learn XML in order to lear Maven? > > No, if you use Eclipse you can configure your POM in its graphical editor. > > Other IDEs may have similar things. > > > > Even if you edit POMs by hand, XML is "human readable" meaning you don't > > really need an in-depth understanding of XML in order to hack together a > > Maven POM. > > > > My definition of "learn XML" would be more like: > > * Understand basics: elements vs. attributes, etc. > > * Understand XML validation; e.g. XSD and DTD > > * Understand XSLT stylesheets > > * Understand parsing: SAX, DOM and XPath > > > > And you certainly do not need to know those things to configure a Maven POM. > > > > Regards, > > Curtis > > > > > > On Thu, Jun 27, 2013 at 10:22 AM, Nayana ABREU > > <[email protected]>wrote: > > > >> Is it necessary to learn XML in order to lear Maven? > >> > >> Thanks > >> > >> -- > >> Nayana Holanda de Abreu > >> [email protected] > >> Phone: 662-801-6349 > >> Skype: nayanexbourdon > >> > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > -- > Ron Wheeler > President > Artifact Software Inc > email: [email protected] > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
