Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Headless build: The type X is already defined
Headless build: The type X is already defined [message #487983] Fri, 25 September 2009 08:16 Go to next message
Christophe Fondacci is currently offline Christophe FondacciFriend
Messages: 95
Registered: July 2009
Location: Paris
Member
Hello all,

It's been a while i am trying to make a nightly build of my RCP application,
but when I run the pde-build ant task, the pde runs well at the begining,
and then fails with errors like :
"The type [type] is already defined"

I've found a bug for this :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=146324

But it seems to be closed. At the end someone say the problem had nothing to
do with Eclipse but didn't post what was the problem. In my situation,
everything compile fine with the UI compiler.

Thank you very much for your help,
Christophe.
Re: Headless build: The type X is already defined [message #488093 is a reply to message #487983] Fri, 25 September 2009 14:31 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
Is it possible that the error is real?

One thing I could imagine is if you had 2 source files defining the same
type, and in the workspace, one of those is filtered out with exclusions
on the source folder. The headless build does not have access to the
workspace and does not currently support exclusions on the source folder.

-Andrew

Christophe Fondacci wrote:
> Hello all,
>
> It's been a while i am trying to make a nightly build of my RCP
> application, but when I run the pde-build ant task, the pde runs well at
> the begining, and then fails with errors like :
> "The type [type] is already defined"
>
> I've found a bug for this :
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=146324
>
> But it seems to be closed. At the end someone say the problem had
> nothing to do with Eclipse but didn't post what was the problem. In my
> situation, everything compile fine with the UI compiler.
>
> Thank you very much for your help,
> Christophe.
Re: Headless build: The type X is already defined [message #488757 is a reply to message #488093] Wed, 30 September 2009 06:56 Go to previous message
Christophe Fondacci is currently offline Christophe FondacciFriend
Messages: 95
Registered: July 2009
Location: Paris
Member
Hello and thank you for your reply,

Nop this compilation error is not real. I got this error for many files of
this plugin, each of these file only exists one time and is not filtered
through some project settings for the "UI" compilation.
But the first error raised is on a class implementing the interface ICommand
(this interface comes from my code). The eclipse core components also
defines an interface named ICommand (but, of course, in another package and
plugin). Could there be problems ?

For example, for the first class on which I get this error, here is the
sequence of output from ant referencing this file :
[java] [javac] [parsing
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n extep\installer\impl\DatabaseCommand.java
- #24/49]
[java] [javac] [parsing
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n eXtep\installer\impl\DatabaseCommand.java
- #50/50]
[java] [javac] [analyzing
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n extep\installer\impl\DatabaseCommand.java
- #24/55]
[java] [javac] [writing
com\nextep\installer\impl\DatabaseCommand.class - #24]
[java] [javac] [completed
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n extep\installer\impl\DatabaseCommand.java
- #24/55]
[java] [javac] [analyzing
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n eXtep\installer\impl\DatabaseCommand.java
- #50/61]
[java] [javac] [completed
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n eXtep\installer\impl\DatabaseCommand.java
- #50/61]
[java] [javac] ----------
[java] [javac] 107. ERROR in
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n eXtep\installer\impl\DatabaseCommand.java
(at line 19)
[java] [javac] public abstract class DatabaseCommand implements
ICommand {
[java] [javac] ^^^^^^^^^^^^^^^
[java] [javac] The type DatabaseCommand is already defined
[java] [javac] ----------

Everything comes from the same plugin compilation inside a @dot: element.
I am out of ideas of what to try, what to test or what to check to
understand what is going on.

Thank you very much,
Christophe.


"Andrew Niefer" <aniefer@ca.ibm.com> a écrit dans le message de groupe de
discussion : h9ik75$tj2$1@build.eclipse.org...
> Is it possible that the error is real?
>
> One thing I could imagine is if you had 2 source files defining the same
> type, and in the workspace, one of those is filtered out with exclusions
> on the source folder. The headless build does not have access to the
> workspace and does not currently support exclusions on the source folder.
>
> -Andrew
>
> Christophe Fondacci wrote:
>> Hello all,
>>
>> It's been a while i am trying to make a nightly build of my RCP
>> application, but when I run the pde-build ant task, the pde runs well at
>> the begining, and then fails with errors like :
>> "The type [type] is already defined"
>>
>> I've found a bug for this :
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=146324
>>
>> But it seems to be closed. At the end someone say the problem had nothing
>> to do with Eclipse but didn't post what was the problem. In my situation,
>> everything compile fine with the UI compiler.
>>
>> Thank you very much for your help,
>> Christophe.
Re: Headless build: The type X is already defined [message #601993 is a reply to message #487983] Fri, 25 September 2009 14:31 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
Is it possible that the error is real?

One thing I could imagine is if you had 2 source files defining the same
type, and in the workspace, one of those is filtered out with exclusions
on the source folder. The headless build does not have access to the
workspace and does not currently support exclusions on the source folder.

-Andrew

Christophe Fondacci wrote:
> Hello all,
>
> It's been a while i am trying to make a nightly build of my RCP
> application, but when I run the pde-build ant task, the pde runs well at
> the begining, and then fails with errors like :
> "The type [type] is already defined"
>
> I've found a bug for this :
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=146324
>
> But it seems to be closed. At the end someone say the problem had
> nothing to do with Eclipse but didn't post what was the problem. In my
> situation, everything compile fine with the UI compiler.
>
> Thank you very much for your help,
> Christophe.
Re: Headless build: The type X is already defined [message #602155 is a reply to message #488093] Wed, 30 September 2009 06:56 Go to previous message
Christophe Fondacci is currently offline Christophe FondacciFriend
Messages: 95
Registered: July 2009
Location: Paris
Member
Hello and thank you for your reply,

Nop this compilation error is not real. I got this error for many files of
this plugin, each of these file only exists one time and is not filtered
through some project settings for the "UI" compilation.
But the first error raised is on a class implementing the interface ICommand
(this interface comes from my code). The eclipse core components also
defines an interface named ICommand (but, of course, in another package and
plugin). Could there be problems ?

For example, for the first class on which I get this error, here is the
sequence of output from ant referencing this file :
[java] [javac] [parsing
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n extep\installer\impl\DatabaseCommand.java
- #24/49]
[java] [javac] [parsing
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n eXtep\installer\impl\DatabaseCommand.java
- #50/50]
[java] [javac] [analyzing
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n extep\installer\impl\DatabaseCommand.java
- #24/55]
[java] [javac] [writing
com\nextep\installer\impl\DatabaseCommand.class - #24]
[java] [javac] [completed
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n extep\installer\impl\DatabaseCommand.java
- #24/55]
[java] [javac] [analyzing
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n eXtep\installer\impl\DatabaseCommand.java
- #50/61]
[java] [javac] [completed
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n eXtep\installer\impl\DatabaseCommand.java
- #50/61]
[java] [javac] ----------
[java] [javac] 107. ERROR in
F:\tmp\build\plugins\com.neXtep.designer.installer\src\com\n eXtep\installer\impl\DatabaseCommand.java
(at line 19)
[java] [javac] public abstract class DatabaseCommand implements
ICommand {
[java] [javac] ^^^^^^^^^^^^^^^
[java] [javac] The type DatabaseCommand is already defined
[java] [javac] ----------

Everything comes from the same plugin compilation inside a @dot: element.
I am out of ideas of what to try, what to test or what to check to
understand what is going on.

Thank you very much,
Christophe.


"Andrew Niefer" <aniefer@ca.ibm.com> a écrit dans le message de groupe de
discussion : h9ik75$tj2$1@build.eclipse.org...
> Is it possible that the error is real?
>
> One thing I could imagine is if you had 2 source files defining the same
> type, and in the workspace, one of those is filtered out with exclusions
> on the source folder. The headless build does not have access to the
> workspace and does not currently support exclusions on the source folder.
>
> -Andrew
>
> Christophe Fondacci wrote:
>> Hello all,
>>
>> It's been a while i am trying to make a nightly build of my RCP
>> application, but when I run the pde-build ant task, the pde runs well at
>> the begining, and then fails with errors like :
>> "The type [type] is already defined"
>>
>> I've found a bug for this :
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=146324
>>
>> But it seems to be closed. At the end someone say the problem had nothing
>> to do with Eclipse but didn't post what was the problem. In my situation,
>> everything compile fine with the UI compiler.
>>
>> Thank you very much for your help,
>> Christophe.
Previous Topic:Plug-in Fragment cannot resolve classes from host
Next Topic:Intention behind @noreference tag in API tools
Goto Forum:
  


Current Time: Tue Apr 23 17:38:33 GMT 2024

Powered by FUDForum. Page generated in 0.03351 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top