| How to avoid double-builds from console and from eclipse [message #758790] |
Thu, 24 November 2011 14:56  |
|
Hi to anyone,
I looked for my problem in internet and got very different even conflicting options which, so I ask here.
In our development-process we generate artifacts, which are compiled afterwards together with implemented java-files.
If a developer checks out a project and cleanly compiles his project, and he opens this project in Eclipse afterwards, the IDE builds all java-files, that are already built before, again. This takes a lot of time, because we have very large projects.
My questions:
1. I found a hint, that the eclipse-java-compiler does additional things to the classfiles, so it must run itself, even if classes are compiled by another JDK - is this correct?
2. Is there anywhere a solution for building our classfiles not twice?
Any help would be welcome,
Thanks by now
Best regards
Markus
|
|
|
| Re: How to avoid double-builds from console and from eclipse [message #758838 is a reply to message #758790] |
Thu, 24 November 2011 16:51  |
 Deepak Azad
Messages: 543
Registered: July 2009 |
Senior Member |
|
|
On 11/24/2011 8:26 PM, Markus Oley wrote:
> Hi to anyone,
> I looked for my problem in internet and got very different even
> conflicting options which, so I ask here.
> In our development-process we generate artifacts, which are compiled
> afterwards together with implemented java-files.
> If a developer checks out a project and cleanly compiles his project,
> and he opens this project in Eclipse afterwards, the IDE builds all
> java-files, that are already built before, again. This takes a lot of
> time, because we have very large projects.
> My questions:
> 1. I found a hint, that the eclipse-java-compiler does additional things
> to the classfiles, so it must run itself, even if classes are compiled
> by another JDK - is this correct?
I think apart from adding debug information to the class files, there
isn't much else that JDT compiler will do differently with the class files.
However, several other IDE features depend on compiler output which is
not just the class files. For example, it produces problem markers
(error and warnings) which are used to provide quick fixes.
> 2. Is there anywhere a solution for building our classfiles not twice?
> Any help would be welcome, Thanks by now
Can't you use the output of Eclipse compiler in your custom compilation
process ?
I think the problem you face is similar to those who use Maven. Maybe
you need to check with some Maven experts.
--
Deepak Azad
http://wiki.eclipse.org/JDT/FAQ
|
|
|
|
|
| Re: How to avoid double-builds from console and from eclipse [message #759045 is a reply to message #758890] |
Fri, 25 November 2011 19:29 |
|
Hi Depaak,
thank you for your answer.
OK, I guess I have to go another way....
I will adapt our buildprocess, that I can do generating without compile afterwards.
And then I compile it in eclipse.
Or I compile with JDT-compiler in commandline, if eclipse-home is set.
I guess, that will be a solution, that is OK,
Best regards
Markus
|
|
|
Powered by
FUDForum. Page generated in 0.02288 seconds
] 
Search
Help
Register
Login
Home
