You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2013/10/26 21:24:52 UTC

[jira] (SCM-518) wrong model in vss-settings.mdo works only with a bug in Modello 1.0-alpha-21 but not with Modello 1.0+

     [ https://jira.codehaus.org/browse/SCM-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte updated SCM-518:
-------------------------------

    Description: 
after [documentation|http://maven.apache.org/scm/vss.html], vss-settings.xml file content is 
{code:xml}<vss-settings>
  <Settings>
    <vssDirectory>ss_exe_directory</vssDirectory>
  </Settings>
</vss-settings>
{code}

but actual vss-settings.mdo does not define "Settings" field.

Reading such a file works only because of a bug in Modello parsing: MODELLO-152, which has been fixed in Modello 1.0.


There are 2 options for us: either change the documentation (and tell the users) to support following model (which was the initial intend IMHO):
{code:xml}<vss-settings>
  <vssDirectory>ss_exe_directory</vssDirectory>
</vss-settings>
{code}

or tweak the model and update the code to create an intermediate class for this Settings element (only useful to avoid changing the XML format)

  was:
after [documentation|http://maven.apache.org/scm/vss.html], vss-settings.xml file content is 
{code:xml}<vss-settings>
  <Settings>
    <vssDirectory>ss_exe_directory</vssDirectory>
  <Settings>
</vss-settings>
{code}

but actual vss-settings.mdo does not define "Settings" field.

Reading such a file works only because of a bug in Modello parsing: MODELLO-152, which has been fixed in Modello 1.0.


There are 2 options for us: either change the documentation (and tell the users) to support following model (which was the initial intend IMHO):
{code:xml}<vss-settings>
  <vssDirectory>ss_exe_directory</vssDirectory>
</vss-settings>
{code}

or tweak the model and update the code to create an intermediate class for this Settings element (only useful to avoid changing the XML format)

    
> wrong model in vss-settings.mdo works only with a bug in Modello 1.0-alpha-21 but not with Modello 1.0+
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SCM-518
>                 URL: https://jira.codehaus.org/browse/SCM-518
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-vss
>    Affects Versions: 1.2
>            Reporter: Herve Boutemy
>
> after [documentation|http://maven.apache.org/scm/vss.html], vss-settings.xml file content is 
> {code:xml}<vss-settings>
>   <Settings>
>     <vssDirectory>ss_exe_directory</vssDirectory>
>   </Settings>
> </vss-settings>
> {code}
> but actual vss-settings.mdo does not define "Settings" field.
> Reading such a file works only because of a bug in Modello parsing: MODELLO-152, which has been fixed in Modello 1.0.
> There are 2 options for us: either change the documentation (and tell the users) to support following model (which was the initial intend IMHO):
> {code:xml}<vss-settings>
>   <vssDirectory>ss_exe_directory</vssDirectory>
> </vss-settings>
> {code}
> or tweak the model and update the code to create an intermediate class for this Settings element (only useful to avoid changing the XML format)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira