I may be smoking crack (if I am, don't hesitate to let me know), but it is
my understanding that whitespace (including line breaks) within a tag
should not alter how the tag is handled.

For example:

<element
      attr1="..."
      attr2="..."
      attr3="...">

should be parsed the same as

<element attr1="..." attr2="..." attr2="...">

I know that I've encountered issues with Cocoon where it generates
TextNodes for whitespace-only content between elements.  Perhaps this is an
issue with Xalan?

It's better to be hated for who you are
than loved for who you are not

Ian D. Stewart
Appl Dev Analyst-Advisory, DCS Automation
JPMorganChase Global Technology Infrastructure
Phone: (614) 244-2564
Pager: (888) 260-0078


                                                                       
                      "Brett Porter"                                   
                      <[EMAIL PROTECTED]        To:       "Maven Users List" 
<[email protected]>
                      il.com>                  cc:                     
                                               Subject:  Re: [m2] release 
plugin removes all comments from pom.xml
                      05/08/2006 10:24                                 
                      AM                                               
                      Please respond to                                
                      "Maven Users                                     
                      List"                                            
                                                                       




I thought I was working around this as well, but you should find that
if you remove the line breaks in the <project element in your
original, that doesn't happen.

- Brett

On 5/9/06, Jens Zastrow <[EMAIL PROTECTED]> wrote:
> Yes it - almost - works.
>
> Our pom´s should include some kind of documentation in the header.
> Unf. this comments get removed from the pom during the release.
> I´m not sure but maybe this is jdom related - a "well formed" xml
document should only have 1 root node but our ones have 2 (project +
comment).
>
>
> [original pom.xml]
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!--
==================================================================================

>    |
>    |   This pom.xml    :
http://maven.apache.org/maven-model/maven.html
>    |
>    |   Getting
Started : http://maven.apache.org/guides/getting-started/index.html
>    |
Guides          : http://maven.apache.org/guides/index.html
>    |
>
================================================================================
 -->
> <project xmlns="http://maven.apache.org/POM/4.0.0";
>          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>              xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
>         <modelVersion>4.0.0</modelVersion>
>         ...
>
> [transformed pom.xml]
> <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd
">
>         <modelVersion>4.0.0</modelVersion>
>         ...
>
> -----Original Message-----
> From: dan tran [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 08, 2006 4:08 PM
> To: Maven Users List
> Subject: Re: [m2] release plugin removes all comments from pom.xml
>
> http://jira.codehaus.org/browse/MRELEASE-45
>
> It is fixed in svn, please test.
>
> -D
>
>
> On 5/8/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote:
> >
> > Yes, I added one, but it was a duplicate of an existing one already.
> > Forgot the id though.
> >
> > Jens Zastrow wrote:
> > > Is tehre any technical issue why the release plugin needs to remove
> > > all the comments and to reformat the whole pom.xml?
> > >
> > > Thanks
> > > Jens Zastrow
> >
> > --
> > With kind regards,
> > Geoffrey De Smet
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>
>

---------------------------------------------------------------------
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]

Reply via email to