| The jar file cannot be exported into itself [message #247432] |
Fri, 01 February 2008 17:53  |
Eclipse User |
|
|
|
Originally posted by: dgresh.mail.rochester.edu
Hi,
When I go to overwrite a JAR file with the JAR export wizard I get the
error "The jar file cannot be exported into itself" unless I first delete
the old jar. Is there some way to avoid this, just as a matter of
convenience?
Thanks,
Dan
|
|
|
| Re: The jar file cannot be exported into itself [message #247444 is a reply to message #247432] |
Fri, 01 February 2008 19:11  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Dan wrote:
> Hi,
>
> When I go to overwrite a JAR file with the JAR export wizard I get the
> error "The jar file cannot be exported into itself" unless I first
> delete the old jar. Is there some way to avoid this, just as a matter of
> convenience?
What I think this means is that the JAR that you are exporting to is
included in the files you have selected to export. This can happen if
you choose as the destination for your JAR the project that you are
exporting.
Hope this helps,
Eric
|
|
|
| Re: The jar file cannot be exported into itself [message #247454 is a reply to message #247444] |
Fri, 01 February 2008 19:44 |
| Eclipse User |
|
|
|
Originally posted by: dgresh.mail.rochester.edu
Eric Rizzo wrote:
> Dan wrote:
> What I think this means is that the JAR that you are exporting to is
> included in the files you have selected to export. This can happen if
> you choose as the destination for your JAR the project that you are
> exporting.
> Hope this helps,
> Eric
This is exactly the problem. I moved the jar destination outside of the
project, and it works fine.
Thank you very much,
Dan
|
|
|
| Re: The jar file cannot be exported into itself [message #247617 is a reply to message #247454] |
Mon, 04 February 2008 11:55 |
| Eclipse User |
|
|
|
Originally posted by: 4cs6fcg02.sneakemail.com
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4817417286A0797C482CB82B
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Dan schreef:
> Eric Rizzo wrote:
>=20
>> Dan wrote:
>=20
>> What I think this means is that the JAR that you are exporting to is=20
>> included in the files you have selected to export. This can happen if =
>> you choose as the destination for your JAR the project that you are=20
>> exporting.
>=20
>> Hope this helps,
>> Eric
>=20
> This is exactly the problem. I moved the jar destination outside of the=
=20
> project, and it works fine.
No need for that if you unselect the jar file itself in the jar packager.=
H.
--=20
Hendrik Maryns
http://tcl.sfs.uni-tuebingen.de/~hendrik/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
http://aouw.org
Ask smart questions, get good answers:
http://www.catb.org/~esr/faqs/smart-questions.html
--------------enig4817417286A0797C482CB82B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFHpv0Ze+7xMGD3itQRAgRrAJ9QyTwBmsjTZ4DnoN1bZKwuO8nvTACc CUmT
OMnRlhpq3U1DNzuOw30PTn8=
=6o3H
-----END PGP SIGNATURE-----
--------------enig4817417286A0797C482CB82B--
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.09054 seconds
] 
Search
Help
Register
Login
Home
