🚀 go-pugleaf

Really, it works fine on my W2k machine. So, it should be the rigtht place
where the file resides.
And I checked the cases of all names. Everything ok.

But my trouble is that the target machine is Linux. And there it does not
work anymore.

Klaus



"Joi Ellis [TeamB]" <joi@aravox.com> schrieb im Newsbeitrag
news:3bf9032b_1@dnews...
> Klaus Kaal <klaus@kaal.de> wrote:
> > When I start my application on the target-machine, I get
>
> > "Failed to load Main-Class manifest attribute from ..." and then my
jar-file
>
> > In JBuilder, I looked into the maifest.MF file and it contains:
>
> Is that the correct case?  Java is pretty particular about the location
and
> name of the manifest file, including its case:
>
> META-INF/MANIFEST.MF
>
> Did you build your jar manually and tell the jar command where to find the
> manifest file?  Or did you create one and drop it into the jar's input
> directory yourself?
>
> > "Manifest-Version: 1.0
> > Main-Class: ParserMain.Parser "
>
> > The class exists and works in JBuilder.
>
> > I have no idea about the manifest thing. Can anyone help me?
>
> What level of JBuilder are you using?  Does it have the Archive Wizard?
>
> --
> Joi Ellis (TeamB)               http://www.teamb.com/
> No direct email, please.
> For best results, post on news server newsgroups.borland.com!
> Newsgroup Guidelines: http://www.borland.com/newsgroups/guide.html
> Only posts which violate the rules in guide.html are subject to
cancelation.