You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Allison, Bob" <ro...@qwest.com> on 2005/11/14 20:08:31 UTC
Jar Manifest Problems
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).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Jar Manifest Problems
Posted by Brett Porter <br...@gmail.com>.
Thanks for looking into this. We certainly need to make some
improvements to the archiver.
Cheers,
Brett
On 11/15/05, Allison, Bob <ro...@qwest.com> wrote:
> 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).
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Cannot get release:perform to work
Posted by dan tran <da...@gmail.com>.
I wonder if release plugin need to issue login first for cvs.
So far i dont see it is doing so ( from source)
-D
On 11/18/05, Marcel Dullaart <md...@epo.org> wrote:
>
>
> Hi all,
>
> Can someone explain me how I should do a release cycle?
>
> I have setup a multi module project and after some fiddling about I got
> release:prepare to work using:
> mvn -Dproject.scm.developerConnection=scm:cvs:pserver:uid:pwd@cvsnode:/cvsroot:my_project_name
> release:prepare
>
> So now I'd like to do the release but I can't really figure out how to do
> it.
>
> Kind regards / Mit freundlichem Gruss / Salutations cordiales,
> Marcel Dullaart *Marcel Dullaart - my.epoline(r)Java architect (Portal
> specialist)* *
> **EUROPEAN PATENT OFFICE* <http://www.epo.org/> *
> **Patentlaan 2 - 2280HV Rijswijk (ZH) - Netherlands*<http://www.european-patent-office.org/epo/addresses/thehague/detail_denhaag_e.htm>
> Tel: +31 (0)70 340 41 68
> Web: *www.epoline.org* <http://www.epoline.org/> | email: *
> mdullaart@epo.org* <md...@epo.org>
>
Re: [m2] Cannot get release:perform to work
Posted by Emmanuel Venisse <em...@venisse.net>.
in release plugin, you have two goals :
- release:prepare
- release:perform
http://maven.apache.org/guides/mini/guide-releasing.html
release:prepare modify versions in pom and tag sources
release:perform checkout sources from tag and run the deploy phase to upload all artifacts in remote
repository.
Emmanuel
Marcel Dullaart a écrit :
>
> Hi all,
>
> Can someone explain me how I should do a release cycle?
>
> I have setup a multi module project and after some fiddling about I got
> release:prepare to work using:
> mvn
> -Dproject.scm.developerConnection=scm:cvs:pserver:uid:pwd@cvsnode:/cvsroot:my_project_name
> release:prepare
>
> So now I'd like to do the release but I can't really figure out how to
> do it.
>
> Kind regards / Mit freundlichem Gruss / Salutations cordiales,
> Marcel Dullaart
> *Marcel Dullaart - my./epoline®/Java architect (Portal specialist)* _
> __EUROPEAN PATENT OFFICE_ <http://www.epo.org/> _
> __Patentlaan 2 - 2280HV Rijswijk (ZH) - Netherlands_
> <http://www.european-patent-office.org/epo/addresses/thehague/detail_denhaag_e.htm>
>
> Tel: +31 (0)70 340 41 68
> Web: _www.epoline.org_ <http://www.epoline.org/> | email:
> _mdullaart@epo.org_ <ma...@epo.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
[m2] Cannot get release:perform to work
Posted by Marcel Dullaart <md...@epo.org>.
Hi all,
Can someone explain me how I should do a release cycle?
I have setup a multi module project and after some fiddling about I got
release:prepare to work using:
mvn
-Dproject.scm.developerConnection=scm:cvs:pserver:uid:pwd@cvsnode:/cvsroot:my_project_name
release:prepare
So now I'd like to do the release but I can't really figure out how to do
it.
Kind regards / Mit freundlichem Gruss / Salutations cordiales,
Marcel Dullaart
Marcel Dullaart - my.epoline®Java architect (Portal specialist)
EUROPEAN PATENT OFFICE
Patentlaan 2 - 2280HV Rijswijk (ZH) - Netherlands
Tel: +31 (0)70 340 41 68
Web: www.epoline.org | email: mdullaart@epo.org