errors in the build that do not show in the IDE

[jbuchberger]

Hi.

We get some build errors, that do not appear in the IDE, e.g.

ERROR: L/analysis.core.test/META-INF/MANIFEST.MF:1(0-0): Manifest has
no main section

This particular manifest seems OK, though.

ERROR: P/analysis.cursorlogic:0(0-0): The project was not built since
the source file /analysis.cursorlogic/src/analysis/cursorlogic/
preferences/IImageKeys.java could not be read

Can be read from the IDE, though.

Do you have any idea, what could go wrong here?

Regards.
Joerg

[Lipi]

This is a test...

On Oct 21, 10:48 am, jbuchberger <joergbuchberger...@googlemail.com>
wrote:

[Lipi]

Did you open the same workspace the plugin worked in? Am i right?

Meta.inf: How is it created? By builder, or it has fixed content? What
kind of builders do you have in your project? Could you attach
metadata files of your project (.classpath, .project, .settings folder
and the manifest itself).

Cloud not be read stuff: I have no idea. We could modify the plugin to
dump error details. My idea is to dump the marker id of the error in
the log, and the error details could be written to a separate file
having the id as a name. What do you think? I also googled your error
like this : "java could not be read" eclipse. There were some results.
Probably you should check them.

On Oct 21, 10:48 am, jbuchberger <joergbuchberger...@googlemail.com>
wrote:

[Lipi]

And please close the issue you reported, since installation was
successful :)

On Oct 21, 10:48 am, jbuchberger <joergbuchberger...@googlemail.com>
wrote:

[jbuchberger]

Hm, how can I close this? Didn't see a button or link for that - so I
thought, that I'm not authorized for that.

[jbuchberger]

On Oct 21, 11:11 am, Lipi <gabor.lip...@gmail.com> wrote:
> Did you open the same workspace the plugin worked in? Am i right?

Yes ;-) same workspace.

>
> Meta.inf: How is it created? By builder, or it has fixed content? What
> kind of builders do you have in your project? Could you attach
> metadata files of your project (.classpath, .project, .settings folder
> and the manifest itself).

It has fixed content, i.e. it is put into and updated from version
control (SVN) along with the other sources.
As far as I know, all of our products projects do have these builders
in the same order as shown here below:
- Java Builder
- Plug-in Manifest Builder
- Extension Point Schema Builder

I'm not allowed to make sources public, but it should be OK to send it
to you privately.
Are you fine with that?

Regards,
Joerg.

[jbuchberger]

... thanks to László: http://groups.google.com/group/headlesseclipse/msg/553ce251b44f1c4a
Just needed to refresh the projects by adding the import parameter!

Regards.
Joerg


On Oct 21, 11:40 am, jbuchberger <joergbuchberger...@googlemail.com>
wrote:

[Lipi]

Ok. I take a look at it.

On Oct 21, 11:40 am, jbuchberger <joergbuchberger...@googlemail.com>
wrote:

[Gábor Lipták]

Ok. So are all problems solved (metainf and cannotfindstuff)?

On Oct 21, 12:33 pm, jbuchberger <joergbuchberger...@googlemail.com>
wrote:

[jbuchberger]

On Oct 21, 12:37 pm, Gábor Lipták <gabor.lip...@gmail.com> wrote:
> Ok. So are all problems solved (metainf and cannotfindstuff)?
>

Yes, Gábor.
Everything solved by refresh using the import parameter!

[Gábor Lipták]

Cool. Stay in touch. If You plan any new functionality into the plugin
(you mentioned something about unit tests), let us know, and we can
include it if You think so.

On Oct 21, 1:25 pm, jbuchberger <joergbuchberger...@googlemail.com>
wrote: