maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phillip Merensky (JIRA)" <>
Subject [jira] Commented: (MECLIPSE-130) extra empty lines are preserved when writing file
Date Wed, 13 Aug 2008 07:49:27 GMT


Phillip Merensky commented on MECLIPSE-130:

We are using the maven-bundle-plugin in combination with the maven-eclipse-plugin. The maven-bundle-plugin
generates the MANIFEST.MF-File with the bnd-tool which puts the classpath at the end and adds
a new line after it. This is needed because Eclipse requires the last line of the MANIFEST
file to be empty. When executing the eclipse:eclipse task with pde enabled after the MANIFEST.MF
generation of the bnd-tool the MANIFEST.MF file will be corrupted es explained in the original
bug description.

In short this means that it is not possible to use the maven-eclipse-plugin in combination
with the maven-bundle-plugin which is more than a "minor" priority to me.

Thanks for any help in advance.
Keep up the good work. The maven-eclipse-plugin is a real help to me.


> extra empty lines are preserved when writing file
> -------------------------------------------------------------
>                 Key: MECLIPSE-130
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: OSGi, Manifest
>    Affects Versions: 2.3
>         Environment: Windows Xp, eclipse 3.2.0, jdk 1.5, maven 2.0.4 
>            Reporter: stephane bouchet
>            Priority: Minor
>         Attachments: MECLIPSE_130_patch.diff
> Hi, 
> when i use the last snapshot in pde projects, i notice that bug : 
> the Bundle:Classpath entry is written in the end of the file, but if there is empty line
before writing this entry, they are not removed. 
> So eclipse complains about it. 
> To resolve this, i had to manually delete these empty lines. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message