Re: Status on namespace support for POM Elements ?

> With eclipse we do autocompletion for nested elements using reflection, if > type information is available (e.g. generics are used for List and Map > elements) in almost the same as in Maven (almost - because maven takes > config and tries to apply each separate value, while from the editor we

Re: Packaging doxygen output across modules?

On 2016-06-05T23:16:22 +0200 Karl Heinz Marbaise wrote: > Hi, > > so you need to have the packaging in the doxygen-maven-plugin as well > which is currently not done...? > Best would be to add a feature request ... Not necessarily, no. I think what I'm doing is a fairly

Re: Packaging doxygen output across modules?

Hi, so you need to have the packaging in the doxygen-maven-plugin as well which is currently not done...? Best would be to add a feature request ... Kind regards Karl Heinz Marbaise On 6/4/16 4:28 PM, org.apache.maven.u...@io7m.com wrote: Hello. I have a multi-module project: module-A

Re: Packaging doxygen output across modules?

On 2016-06-04T14:28:14 + wrote: > However, how do I now package up the resulting doxygen HTML such that > it can be added to the archive file produced by module-documentation? > What's the Maven way to handle this? I solved this by: 1. Not using the

Re: Status on namespace support for POM Elements ?

With eclipse we do autocompletion for nested elements using reflection, if type information is available (e.g. generics are used for List and Map elements) in almost the same as in Maven (almost - because maven takes config and tries to apply each separate value, while from the editor we need to

Re: Status on namespace support for POM Elements ?

> +1 to ALLOW (but not require) the second use case of xmlns=..>, this let you have autocomplete say in Eclipse's XML editor. > However I believe a xsi schemalocation would then still be needed per > plugin unless a catalogue is accessible out of bands, so it would still be > a bit verbose.

Re: Status on namespace support for POM Elements ?

> Just on a side note, eclipse m2e pom editor does have an autocomplete for > plugin configuration based on the plugin descriptor and the classes that > are used. > +1 to namespace support though, since it could be used to provide > autocomplete for parts that cannot be deduced by looking at the

Re: Status on namespace support for POM Elements ?

Just on a side note, eclipse m2e pom editor does have an autocomplete for plugin configuration based on the plugin descriptor and the classes that are used. +1 to namespace support though, since it could be used to provide autocomplete for parts that cannot be deduced by looking at the model

Re: Status on namespace support for POM Elements ?

+1 to ALLOW (but not require) the second use case of , this let you have autocomplete say in Eclipse's XML editor. However I believe a xsi schemalocation would then still be needed per plugin unless a catalogue is accessible out of bands, so it would still be a bit verbose. (I never understood

Re: Status on namespace support for POM Elements ?

> Do you really think introducing XML namespaces would make the handling > of the pom better ? In particular if you have a separate namespace for > every plugin? (At apache maven project we have 49 plugins ? This would > mean in consequence 49 namespaces? And at mojohaus there are about > another

Re: Status on namespace support for POM Elements ?

Hi, On 6/5/16 7:22 AM, Roland Huss wrote: Hi Karl Heinz, Really bad idea to hijack an existing jira issue.. Please open a new one or if you have problems creating an issue please ask here on the users list first... Agreed, but I really couldn't create a new ticket at that time (only service