[ http://jira.codehaus.org/browse/MNG-2396?page=comments#action_67724 ]
Xavier Dury commented on MNG-2396:
----------------------------------
well, at first, I would like to have some auto-completion and validation
capabilities when editing my profiles.xml file in my favourite IDE (tm).
second, I'd like to know why only a subset of the {pom.xml}/project/profiles
can be included in the {profiles.xml}/settings/profiles?
For example, the build element cannot appear in the
{profiles.xml}/settings/profiles/profile but if I want to use jetty for my
tests, I wouldn't want it to "pollute" my pom.xml (other developpers don't like
jetty) so putting it in profiles.xml would keep my pom.xml clean... but this is
currently not possible.
Would that be possible or is it something you've already carefully thought
about and decided not to allow?
> Define "profiles" element in Maven POM Schema
> ---------------------------------------------
>
> Key: MNG-2396
> URL: http://jira.codehaus.org/browse/MNG-2396
> Project: Maven 2
> Type: Improvement
> Components: General
> Reporter: Xavier Dury
> Priority: Trivial
>
>
> Currently, only the "project" element of the pom schema is declared as an
> element, others are complexTypes. As the profiles section of the pom can be
> externalized in a "profiles.xml" file, it would be great to use the same
> schema for validation and auto-completion by declaring "profiles" as a (root)
> element too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
