You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Bob Allison (JIRA)" <ji...@codehaus.org> on 2005/11/14 20:21:06 UTC
[jira] Created: (MNG-1558) Manifest generation problems caused by valid POM information
Manifest generation problems caused by valid POM information
------------------------------------------------------------
Key: MNG-1558
URL: http://jira.codehaus.org/browse/MNG-1558
Project: Maven 2
Type: Bug
Components: maven-jar-plugin
Versions: 2.0
Reporter: Bob Allison
It looks like we have some problems with the contents of manifests in jar files.
According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced:
1) All text must be UTF-8
2) Lines are limited to 72 characters; longer lines must be continued
3) Sections are divided by blank lines
Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking.
Example:
The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded.
Workarounds for the present:
-- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters.
-- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commenté: (MNG-1558) Manifest generation problems caused by valid POM information
Posted by "Lilians Auvigne (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1558?page=comments#action_52653 ]
Lilians Auvigne commented on MNG-1558:
--------------------------------------
I have the same problem with description.length < 72 and multi lines description
<description>Test multi
lines</description>
maven-archiver generate invalid Manifest
Extension-Name: module
Specification-Title: Test multi
lines
Specification-Vendor...
> Manifest generation problems caused by valid POM information
> ------------------------------------------------------------
>
> Key: MNG-1558
> URL: http://jira.codehaus.org/browse/MNG-1558
> Project: Maven 2
> Type: Bug
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Bob Allison
> Fix For: 2.0.1
>
>
> It looks like we have some problems with the contents of manifests in jar files.
> According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced:
> 1) All text must be UTF-8
> 2) Lines are limited to 72 characters; longer lines must be continued
> 3) Sections are divided by blank lines
> Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking.
>
> Example:
> The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded.
> Workarounds for the present:
> -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters.
> -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-1558) Manifest generation problems caused by
valid POM information
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1558?page=all ]
John Casey closed MNG-1558:
---------------------------
Resolution: Fixed
Applied the patch, and added code to force output to UTF-8 encoding.
> Manifest generation problems caused by valid POM information
> ------------------------------------------------------------
>
> Key: MNG-1558
> URL: http://jira.codehaus.org/browse/MNG-1558
> Project: Maven 2
> Type: Bug
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Bob Allison
> Assignee: John Casey
> Fix For: 2.0.1
> Attachments: MNG-1558-plexus-archiver.patch
>
>
> It looks like we have some problems with the contents of manifests in jar files.
> According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced:
> 1) All text must be UTF-8
> 2) Lines are limited to 72 characters; longer lines must be continued
> 3) Sections are divided by blank lines
> Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking.
>
> Example:
> The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded.
> Workarounds for the present:
> -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters.
> -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1558) Manifest generation problems caused by valid POM information
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1558?page=all ]
Edwin Punzalan updated MNG-1558:
--------------------------------
Attachment: MNG-1558-plexus-archiver.patch
Attached patch with updated test cases for the problem.
> Manifest generation problems caused by valid POM information
> ------------------------------------------------------------
>
> Key: MNG-1558
> URL: http://jira.codehaus.org/browse/MNG-1558
> Project: Maven 2
> Type: Bug
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Bob Allison
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
> Attachments: MNG-1558-plexus-archiver.patch
>
>
> It looks like we have some problems with the contents of manifests in jar files.
> According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced:
> 1) All text must be UTF-8
> 2) Lines are limited to 72 characters; longer lines must be continued
> 3) Sections are divided by blank lines
> Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking.
>
> Example:
> The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded.
> Workarounds for the present:
> -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters.
> -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1558) Manifest generation problems caused by valid POM information
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1558?page=all ]
Edwin Punzalan updated MNG-1558:
--------------------------------
Attachment: (was: MNG-1558-plexus-archiver.patch)
> Manifest generation problems caused by valid POM information
> ------------------------------------------------------------
>
> Key: MNG-1558
> URL: http://jira.codehaus.org/browse/MNG-1558
> Project: Maven 2
> Type: Bug
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Bob Allison
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
> Attachments: MNG-1558-plexus-archiver.patch
>
>
> It looks like we have some problems with the contents of manifests in jar files.
> According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced:
> 1) All text must be UTF-8
> 2) Lines are limited to 72 characters; longer lines must be continued
> 3) Sections are divided by blank lines
> Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking.
>
> Example:
> The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded.
> Workarounds for the present:
> -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters.
> -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1558) Manifest generation problems caused by valid POM information
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1558?page=all ]
Edwin Punzalan updated MNG-1558:
--------------------------------
Attachment: MNG-1558-plexus-archiver.patch
> Manifest generation problems caused by valid POM information
> ------------------------------------------------------------
>
> Key: MNG-1558
> URL: http://jira.codehaus.org/browse/MNG-1558
> Project: Maven 2
> Type: Bug
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Bob Allison
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
> Attachments: MNG-1558-plexus-archiver.patch
>
>
> It looks like we have some problems with the contents of manifests in jar files.
> According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced:
> 1) All text must be UTF-8
> 2) Lines are limited to 72 characters; longer lines must be continued
> 3) Sections are divided by blank lines
> Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking.
>
> Example:
> The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded.
> Workarounds for the present:
> -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters.
> -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1558) Manifest generation problems caused by valid POM information
Posted by "Michal Stochmialek (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1558?page=comments#action_52009 ]
Michal Stochmialek commented on MNG-1558:
-----------------------------------------
I also had some problems connected with this issue.
I had problems while running tests. Surefire was throwning NoClassDefFound for classes in jar created by maven. After longer investigation I've discovered that Specification-Title of the jar was filled with description field's content. After removing the description field and rebuilding the jar, the problem dissapeared.
I've voted on this bug.
best regards
> Manifest generation problems caused by valid POM information
> ------------------------------------------------------------
>
> Key: MNG-1558
> URL: http://jira.codehaus.org/browse/MNG-1558
> Project: Maven 2
> Type: Bug
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Bob Allison
> Fix For: 2.0.1
>
>
> It looks like we have some problems with the contents of manifests in jar files.
> According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced:
> 1) All text must be UTF-8
> 2) Lines are limited to 72 characters; longer lines must be continued
> 3) Sections are divided by blank lines
> Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking.
>
> Example:
> The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded.
> Workarounds for the present:
> -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters.
> -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1558) Manifest generation problems caused by valid POM information
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1558?page=all ]
Edwin Punzalan updated MNG-1558:
--------------------------------
Attachment: (was: MNG-1558-plexus-archiver.patch)
> Manifest generation problems caused by valid POM information
> ------------------------------------------------------------
>
> Key: MNG-1558
> URL: http://jira.codehaus.org/browse/MNG-1558
> Project: Maven 2
> Type: Bug
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Bob Allison
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
> Attachments: MNG-1558-plexus-archiver.patch
>
>
> It looks like we have some problems with the contents of manifests in jar files.
> According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced:
> 1) All text must be UTF-8
> 2) Lines are limited to 72 characters; longer lines must be continued
> 3) Sections are divided by blank lines
> Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking.
>
> Example:
> The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded.
> Workarounds for the present:
> -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters.
> -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1558) Manifest generation problems caused by valid POM information
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1558?page=all ]
Brett Porter updated MNG-1558:
------------------------------
Fix Version: 2.0.1
> Manifest generation problems caused by valid POM information
> ------------------------------------------------------------
>
> Key: MNG-1558
> URL: http://jira.codehaus.org/browse/MNG-1558
> Project: Maven 2
> Type: Bug
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Bob Allison
> Fix For: 2.0.1
>
>
> It looks like we have some problems with the contents of manifests in jar files.
> According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced:
> 1) All text must be UTF-8
> 2) Lines are limited to 72 characters; longer lines must be continued
> 3) Sections are divided by blank lines
> Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking.
>
> Example:
> The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded.
> Workarounds for the present:
> -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters.
> -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1558) Manifest generation problems caused by valid POM information
Posted by "Zeger Hendrikse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1558?page=comments#action_51923 ]
Zeger Hendrikse commented on MNG-1558:
--------------------------------------
We (at Fortis bank) are seriously hampered by this issue as well.
- Trying to let Maven add entries to the manifest by specifying <addMavenDescriptor>false</addMavenDescriptor> results in a null-pointer exception
- Specifying <Specification-Title> ourselves in the jar plug-in configuration results in a multiple specification error
- Concatenating the content of the description element in the POM to one line only, results in a Specification-Title entry in the manifest that is broken up at 72 chars (as it should by the spec), but which makes the WARs and JARS undeployable on the application server (WPS 5.1.0.1)
We concluded, it should either be possible to
- Specify your own manifest file in the JAR plug-in (and not let Maven append the contents of your private manifest file to the one generated by Maven itself, as it seems to do currently)
- Be able to switch on/off all separate attributes of the manifest generation
- Don't put the contents of the description element in the POM in the Specification-Title entry in the manifest. If the length cannot be more than 72 chars, what would be the added value of the description in the POM?
Currently we see ourselves forced to abbreviate all the descriptions to 72-"Specification-Title".length() characters, but this doesn't result in a nice entry page in the Maven site generated pages )-:
> Manifest generation problems caused by valid POM information
> ------------------------------------------------------------
>
> Key: MNG-1558
> URL: http://jira.codehaus.org/browse/MNG-1558
> Project: Maven 2
> Type: Bug
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Bob Allison
> Fix For: 2.0.1
>
>
> It looks like we have some problems with the contents of manifests in jar files.
> According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced:
> 1) All text must be UTF-8
> 2) Lines are limited to 72 characters; longer lines must be continued
> 3) Sections are divided by blank lines
> Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking.
>
> Example:
> The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded.
> Workarounds for the present:
> -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters.
> -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1558) Manifest generation problems caused by valid POM information
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1558?page=all ]
Edwin Punzalan updated MNG-1558:
--------------------------------
Attachment: MNG-1558-plexus-archiver.patch
Sorry about that the multiple attach/delete... was cleaning the unit test output.
> Manifest generation problems caused by valid POM information
> ------------------------------------------------------------
>
> Key: MNG-1558
> URL: http://jira.codehaus.org/browse/MNG-1558
> Project: Maven 2
> Type: Bug
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Bob Allison
> Assignee: Edwin Punzalan
> Fix For: 2.0.1
> Attachments: MNG-1558-plexus-archiver.patch
>
>
> It looks like we have some problems with the contents of manifests in jar files.
> According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced:
> 1) All text must be UTF-8
> 2) Lines are limited to 72 characters; longer lines must be continued
> 3) Sections are divided by blank lines
> Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking.
>
> Example:
> The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded.
> Workarounds for the present:
> -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters.
> -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org