On 4/12/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
>
>
> George Harley wrote:
> > Geir Magnusson Jr wrote:
> >> so it is a top level parameter that can cascade down, right?
> >>
> >> geir
> >>
> >>
> >
> > Hi Geir,
> >
> > No, it isn't a top level parameter at the moment. A new JIRA will be
>
Geir Magnusson Jr wrote:
George Harley wrote:
Geir Magnusson Jr wrote:
so it is a top level parameter that can cascade down, right?
geir
Hi Geir,
No, it isn't a top level parameter at the moment. A new JIRA will be
opened to make it so after the initial switch-over takes place. Does
t
George Harley wrote:
Geir Magnusson Jr wrote:
so it is a top level parameter that can cascade down, right?
geir
Hi Geir,
No, it isn't a top level parameter at the moment. A new JIRA will be
opened to make it so after the initial switch-over takes place. Does
that sound reasonable ?
S
Geir Magnusson Jr wrote:
so it is a top level parameter that can cascade down, right?
geir
Hi Geir,
No, it isn't a top level parameter at the moment. A new JIRA will be
opened to make it so after the initial switch-over takes place. Does
that sound reasonable ?
Best regards,
George
G
so it is a top level parameter that can cascade down, right?
geir
George Harley wrote:
Yes, in my local workspace I updated the following while establishing
proof-of-concept :
* "top level" compile target in make/build-java.xml
* compilation of test support classes in make/build-test.xml
* t
As for me I'm looking forward seeing it in SVN :)
Then we'll see more green lines in Japi reports
Thanks,
Mikhail
2006/4/12, George Harley <[EMAIL PROTECTED]>:
> Yes, in my local workspace I updated the following while establishing
> proof-of-concept :
>
> * "top level" compile target in make/bui
Yes, in my local workspace I updated the following while establishing
proof-of-concept :
* "top level" compile target in make/build-java.xml
* compilation of test support classes in make/build-test.xml
* the "source.ver" property in the /build.xml
* the "build.compiler" property in the /build.xm
It isn't a top-level parameter. So each javac will need to be
annotated with source and target attributes. Of course, the values
could be taken from a top-level property - perhaps imported from
make/properties.xml.
Also, the build.compiler properties will need to be commented out in
each module/*
George Harley wrote:
Hi Paulex,
Thanks for the update. Just so you know, I have been able to take the
original patch containing the 5.0 features which mandated a 5.0 compiler
and compile things successfully using the "jsr14" target that has been
previously discussed on the list. Making furt
George,
George Harley wrote:
Hi Paulex,
Thanks for the update. Just so you know, I have been able to take the
original patch containing the 5.0 features which mandated a 5.0
compiler and compile things successfully using the "jsr14" target that
has been previously discussed on the list. Maki
Sounds great! :)
At least one benefit, poeple do not need to write code in 1.4, and then
re-write it to 1.5
2006/4/12, George Harley <[EMAIL PROTECTED]>:
>
> Hi Paulex,
>
> Thanks for the update. Just so you know, I have been able to take the
> original patch containing the 5.0 features which mand
George Harley wrote:
Hi Paulex,
Thanks for the update. Just so you know, I have been able to take the
original patch containing the 5.0 features which mandated a 5.0
compiler and compile things successfully using the "jsr14" target that
has been previously discussed on the list. Making furthe
Hi Paulex,
Thanks for the update. Just so you know, I have been able to take the
original patch containing the 5.0 features which mandated a 5.0 compiler
and compile things successfully using the "jsr14" target that has been
previously discussed on the list. Making further use of that compiler
13 matches
Mail list logo
