Bugzilla – Full Text Bug Listing
| Summary: | [jar exporter] 'select depended classes' button | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Rodion Dokhtorenko <rod> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | brian.lajevardi, sdb, simonlee |
| Version: | 3.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Rodion Dokhtorenko
Given that, without this, it seems impossible to actually package a stand-alone JAR (as required for a Pure Java application), I would say it was more than an enhancement... the lack of it really does seem to be a bug, IMO. Move to JDT/UI The JAR exporter just exports the files you selected. You can select files in any number of projects you want. I see that the 'add dependend' is a nice feature that can save you some clicking, but in general it can't help you looking at it closely to make sure you also have all resources in and classes reached through reflection. To avoid too many clicks, I recommend you to use a JAR-description file so you can easly rerun an export. Or use ANT to create a JAR. (In reply to comment #3) > The JAR exporter just exports the files you selected. You can select files in > any number of projects you want. > I see that the 'add dependend' is a nice feature that can save you some > clicking, but in general it can't help you looking at it closely to make sure > you also have all resources in and classes reached through reflection. > > To avoid too many clicks, I recommend you to use a JAR-description file so you > can easly rerun an export. Or use ANT to create a JAR. I think, perhaps, that I didn't make clear what I meant - I was referring to a more general situation than the original poster, although I realise I didn't make that clear at all :) Say I want to package up an application that uses SWT (a standalone one), or I want to include my junit test suite in a jar. It's either impossible to actually bundle these into the jar through the eclipse UI, or the way to do so is uninituitive and badly documented... if anyone can point out how one might do this, I'd be very grateful. I know that manually mucking about with an ant file would do the job, but that defeats the object of having a jar exporter in the IDE... So you want the JAR exporter to even extract class files out of other JAR's like SWT? (In reply to comment #5) > So you want the JAR exporter to even extract class files out of other JAR's > like SWT? Or at least include the whole JAR, thus creating a complete self-contained JAR, in line with portability conventions and pure java rules (at least, as reported by O'Reilly, and I tend to trust them). Essentially, a portable/pure java application should not rely on the system it is to be installed on having any classes available except core platform and standard extension classes. So it would be nice to be able to JAR up such an application. *** Bug 122466 has been marked as a duplicate of this bug. *** *** Bug 133055 has been marked as a duplicate of this bug. *** *** Bug 133051 has been marked as a duplicate of this bug. *** |