> 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
>
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 di
> +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.
That'
> 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 m
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
(xpp3d
+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 why
> 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 5
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
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 desk ticket were enabled) so that what my
Hi,
On 6/1/16 9:57 PM, Roland Huss wrote:
Hi,
I tried to use a namespace different than the default one for POM
elements and failed. After some research through various JIRA tickets
its seems that this is a quite old topic, but I couldn't find a
statement whether namespace it is now planned or
Hi,
I tried to use a namespace different than the default one for POM
elements and failed. After some research through various JIRA tickets
its seems that this is a quite old topic, but I couldn't find a
statement whether namespace it is now planned or not. It's not that I
would expect any special
11 matches
Mail list logo
