builder/nature order [message #165703] |
Wed, 23 June 2004 18:45  |
Eclipse User |
|
|
|
Originally posted by: zero_law.yahoo.com
Hey again everyone :)
Is there a known bug in Eclipse 3.0RC2 for executing builders that are
associated with a project in an incorrect order?
I have two builders that I've created, one goes BEFORE the java build,
and the other after. The problem is -- it seems that eclipse is calling
the java builder before either of mine, then calling mine.. is this
intended behaviour or did I miss something?
Here's a snip of the buildSpec from my .project file:
<buildSpec>
<buildCommand>
<name>org.jboss.ide.eclipse.jdt.aop.ui.AopProjectPreBuilder </name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.jboss.ide.eclipse.jdt.aop.ui.AopProjectBuilder</name >
<arguments>
</arguments>
</buildCommand>
</buildSpec>
Also, putting my project nature before or after the java project nature
doesn't seem to change this behaviour.
Thanks!
-Marshall
|
|
|
|
Re: builder/nature order [message #165827 is a reply to message #165719] |
Thu, 24 June 2004 23:05   |
Eclipse User |
|
|
|
Originally posted by: zero_law.yahoo.com
Darins,
Thanks for the pointer -- I was actually mistaken. The builders are
being executed in the order I specify, but it's the behaviour of the
Java Builder that I thought would be different. Basically I'm trying to
make a first pass and invalidate/remove class files that need to be
cleanly built, and then take the fresh class files (after the java
build) and transform them.
The problem is, when I call resource.delete(true, null) or try setting
the timestamp a year back, the java builder isn't picking up that the
class files need to be re-written. Is there anyway to force the java
builder to create a clean class file from scratch for a certain class?
Thanks again!
-Marshall
Darin Swanson wrote:
> If you right click on your project > Properties and select Builders is the
> order showing as correct?
> Have you tried ordering the builders from this UI?
> The order as shown there should be respected.
>
> HTH
> Darins
>
> "Marshall Culpepper" <zero_law@yahoo.com> wrote in message
> news:cbd14v$2fm$1@eclipse.org...
>
>>Hey again everyone :)
>>
>>Is there a known bug in Eclipse 3.0RC2 for executing builders that are
>>associated with a project in an incorrect order?
>>
>>I have two builders that I've created, one goes BEFORE the java build,
>>and the other after. The problem is -- it seems that eclipse is calling
>>the java builder before either of mine, then calling mine.. is this
>>intended behaviour or did I miss something?
>>
>>Here's a snip of the buildSpec from my .project file:
>><buildSpec>
>><buildCommand>
>><name>org.jboss.ide.eclipse.jdt.aop.ui.AopProjectPreBuilder </name>
>><arguments>
>></arguments>
>></buildCommand>
>><buildCommand>
>><name>org.eclipse.jdt.core.javabuilder</name>
>><arguments>
>></arguments>
>></buildCommand>
>><buildCommand>
>><name>org.jboss.ide.eclipse.jdt.aop.ui.AopProjectBuilder</name >
>><arguments>
>></arguments>
>></buildCommand>
>></buildSpec>
>>
>>Also, putting my project nature before or after the java project nature
>>doesn't seem to change this behaviour.
>>
>>Thanks!
>>-Marshall
>
>
>
|
|
|
Re: builder/nature order [message #165833 is a reply to message #165827] |
Fri, 25 June 2004 01:37   |
Eclipse User |
|
|
|
I would expect that deleting the .class file would force a rebuild.
But if you are attempting to do this from a builder I do not believe it will
work as no resource change notifications go out during the build (I
think...needs checking)
HTH
Darins
"Marshall Culpepper" <zero_law@yahoo.com> wrote in message
news:cbg4o4$ch8$1@eclipse.org...
> Darins,
>
> Thanks for the pointer -- I was actually mistaken. The builders are
> being executed in the order I specify, but it's the behaviour of the
> Java Builder that I thought would be different. Basically I'm trying to
> make a first pass and invalidate/remove class files that need to be
> cleanly built, and then take the fresh class files (after the java
> build) and transform them.
>
> The problem is, when I call resource.delete(true, null) or try setting
> the timestamp a year back, the java builder isn't picking up that the
> class files need to be re-written. Is there anyway to force the java
> builder to create a clean class file from scratch for a certain class?
>
> Thanks again!
> -Marshall
>
> Darin Swanson wrote:
> > If you right click on your project > Properties and select Builders is
the
> > order showing as correct?
> > Have you tried ordering the builders from this UI?
> > The order as shown there should be respected.
> >
> > HTH
> > Darins
> >
> > "Marshall Culpepper" <zero_law@yahoo.com> wrote in message
> > news:cbd14v$2fm$1@eclipse.org...
> >
> >>Hey again everyone :)
> >>
> >>Is there a known bug in Eclipse 3.0RC2 for executing builders that are
> >>associated with a project in an incorrect order?
> >>
> >>I have two builders that I've created, one goes BEFORE the java build,
> >>and the other after. The problem is -- it seems that eclipse is calling
> >>the java builder before either of mine, then calling mine.. is this
> >>intended behaviour or did I miss something?
> >>
> >>Here's a snip of the buildSpec from my .project file:
> >><buildSpec>
> >><buildCommand>
> >><name>org.jboss.ide.eclipse.jdt.aop.ui.AopProjectPreBuilder </name>
> >><arguments>
> >></arguments>
> >></buildCommand>
> >><buildCommand>
> >><name>org.eclipse.jdt.core.javabuilder</name>
> >><arguments>
> >></arguments>
> >></buildCommand>
> >><buildCommand>
> >><name>org.jboss.ide.eclipse.jdt.aop.ui.AopProjectBuilder</name >
> >><arguments>
> >></arguments>
> >></buildCommand>
> >></buildSpec>
> >>
> >>Also, putting my project nature before or after the java project nature
> >>doesn't seem to change this behaviour.
> >>
> >>Thanks!
> >>-Marshall
> >
> >
> >
|
|
|
Re: builder/nature order [message #165882 is a reply to message #165833] |
Fri, 25 June 2004 10:14  |
Eclipse User |
|
|
|
Originally posted by: zero_law.yahoo.com
Do you think there's a way to invoke the resource change notification
manually?
Thanks.. you're pointing me in the right direction =)
Darin Swanson wrote:
> I would expect that deleting the .class file would force a rebuild.
> But if you are attempting to do this from a builder I do not believe it will
> work as no resource change notifications go out during the build (I
> think...needs checking)
>
> HTH
> Darins
>
> "Marshall Culpepper" <zero_law@yahoo.com> wrote in message
> news:cbg4o4$ch8$1@eclipse.org...
>
>>Darins,
>>
>>Thanks for the pointer -- I was actually mistaken. The builders are
>>being executed in the order I specify, but it's the behaviour of the
>>Java Builder that I thought would be different. Basically I'm trying to
>>make a first pass and invalidate/remove class files that need to be
>>cleanly built, and then take the fresh class files (after the java
>>build) and transform them.
>>
>>The problem is, when I call resource.delete(true, null) or try setting
>>the timestamp a year back, the java builder isn't picking up that the
>>class files need to be re-written. Is there anyway to force the java
>>builder to create a clean class file from scratch for a certain class?
>>
>>Thanks again!
>>-Marshall
>>
>>Darin Swanson wrote:
>>
>>>If you right click on your project > Properties and select Builders is
>
> the
>
>>>order showing as correct?
>>>Have you tried ordering the builders from this UI?
>>>The order as shown there should be respected.
>>>
>>>HTH
>>>Darins
>>>
>>>"Marshall Culpepper" <zero_law@yahoo.com> wrote in message
>>>news:cbd14v$2fm$1@eclipse.org...
>>>
>>>
>>>>Hey again everyone :)
>>>>
>>>>Is there a known bug in Eclipse 3.0RC2 for executing builders that are
>>>>associated with a project in an incorrect order?
>>>>
>>>>I have two builders that I've created, one goes BEFORE the java build,
>>>>and the other after. The problem is -- it seems that eclipse is calling
>>>>the java builder before either of mine, then calling mine.. is this
>>>>intended behaviour or did I miss something?
>>>>
>>>>Here's a snip of the buildSpec from my .project file:
>>>><buildSpec>
>>>><buildCommand>
>>>><name>org.jboss.ide.eclipse.jdt.aop.ui.AopProjectPreBuilder </name>
>>>><arguments>
>>>></arguments>
>>>></buildCommand>
>>>><buildCommand>
>>>><name>org.eclipse.jdt.core.javabuilder</name>
>>>><arguments>
>>>></arguments>
>>>></buildCommand>
>>>><buildCommand>
>>>><name>org.jboss.ide.eclipse.jdt.aop.ui.AopProjectBuilder </name>
>>>><arguments>
>>>></arguments>
>>>></buildCommand>
>>>></buildSpec>
>>>>
>>>>Also, putting my project nature before or after the java project nature
>>>>doesn't seem to change this behaviour.
>>>>
>>>>Thanks!
>>>>-Marshall
>>>
>>>
>>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04496 seconds