is the source and target properties mandatory on the iajc task

[antofmr]

I am hoping not to have to specify the source or target properties for the iajc task. I have the correct jdk in my path so I was hoping it would just use properties for the underlying jdk found in the path.

[Ramnivas Laddad]

This is a manifestation of another underlying issue outlined in https://bugs.eclipse.org/bugs/show_bug.cgi?id=129989.

For now, you need to specify target and sources. 

As an aside, I think specifying an explicit target and source level is a good idea in any case. Even http://ant.apache.org/manual/CoreTasks/javac.html mentions that "We highly recommend to always specify this attribute.". So the only real issue here is the asymmetry between <javac> and <iajc> task in Ant. 

-Ramnivas

On Thu, Jun 25, 2009 at 9:47 AM, antofmr <Anthony.Conneely@...> wrote:

I am hoping not to have to specify the source or target properties for the
iajc task. I have the correct jdk in my path so I was hoping it would just

use properties for the underlying jdk found in the path.

--
View this message in context: http://www.nabble.com/is-the-source-and-target-properties-mandatory-on-the-iajc-task-tp24203603p24203603.html
Sent from the AspectJ - users mailing list archive at Nabble.com.

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

[antofmr]

Hi Ramnivas

Thanks for your help. I just have one query. Would it not be better if the ajc had the capability to use the source and target available on the local machine in stead of being hard coded to use one .

antofmr wrote:

I am hoping not to have to specify the source or target properties for the iajc task. I have the correct jdk in my path so I was hoping it would just use properties for the underlying jdk found in the path.

[antofmr]

Hi Ramnivas

Thanks for your help. I just have one query. Would it not be better if the ajc had the capability to use the source and target available on the local machine in stead of being hard coded to use one .

Anthony

antofmr wrote:

I am hoping not to have to specify the source or target properties for the iajc task. I have the correct jdk in my path so I was hoping it would just use properties for the underlying jdk found in the path.

[Ramnivas Laddad]

I agree that the default <iajc> behavior should match that of <javac> (although, we will need to be careful here, since this will break existing builds). I was just pointing that relying on default behavior isn't a best practice. For example, when we build the Spring Framework, we explicitly set the source and target to 1.5, even though my machine has only Java 6 installed on it. Essentially, building an application need to consider machines on which the application is going to be deployed and not the local machine.

-Ramnivas

On Thu, Jun 25, 2009 at 11:15 AM, antofmr <Anthony.Conneely@...> wrote:

Hi Ramnivas

Thanks for your help. I just have one query. Would it not be better if the
ajc had the capability to use the source and target available on the local
machine in stead of being hard coded to use one .

Anthony

antofmr wrote:
>
> I am hoping not to have to specify the source or target properties for the
> iajc task. I have the correct jdk in my path so I was hoping it would just
> use properties for the underlying jdk found in the path.
>
>
>

--

View this message in context: http://www.nabble.com/is-the-source-and-target-properties-mandatory-on-the-iajc-task-tp24203603p24205195.html

Sent from the AspectJ - users mailing list archive at Nabble.com.

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

[antofmr]

Thanks for clearing that up for me.

 

Anthony

---

From: aspectj-users-bounces@... [mailto:aspectj-users-bounces@...] On Behalf Of Ramnivas Laddad
Sent: Thursday, June 25, 2009 4:43 PM
To: aspectj-users@...
Subject: Re: [aspectj-users] is the source and target properties mandatory on the iajc task

I agree that the default <iajc> behavior should match that of <javac> (although, we will need to be careful here, since this will break existing builds). I was just pointing that relying on default behavior isn't a best practice. For example, when we build the Spring Framework, we explicitly set the source and target to 1.5, even though my machine has only Java 6 installed on it. Essentially, building an application need to consider machines on which the application is going to be deployed and not the local machine.

-Ramnivas

On Thu, Jun 25, 2009 at 11:15 AM, antofmr <Anthony.Conneely@...> wrote:

Hi Ramnivas

Thanks for your help. I just have one query. Would it not be better if the
ajc had the capability to use the source and target available on the local
machine in stead of being hard coded to use one .

Anthony

antofmr wrote:
>
> I am hoping not to have to specify the source or target properties for the
> iajc task. I have the correct jdk in my path so I was hoping it would just
> use properties for the underlying jdk found in the path.
>
>
>

--

View this message in context: http://www.nabble.com/is-the-source-and-target-properties-mandatory-on-the-iajc-task-tp24203603p24205195.html

Sent from the AspectJ - users mailing list archive at Nabble.com.

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users