Hello,
I am trying to find a way to create a super-jar with all three variants
together. I see that there is an option to set a package in the jastadd
ant task, but that's only one part of the equation.
What would be the other settings available, so that I can put each
front-end in their separate, non-conflicting, namespace?
On 07/17/2012 06:26 AM, Jesper Öqvist wrote:
> Unfortunately there is no such option in JastAddJ.
>
> I suppose it would be possible to build the three versions of JastAddJ
> using different main classes and then invoke the correct main method
> depending on which compatibility level is required.
>
> /Jesper
>
> On 07/17/2012 01:35 AM, Marc-Andre Laverdiere-Papineau wrote:
>> Hello,
>>
>> I am a Soot user. As you may know, Soot uses JastAddJ as its Java
>> front-end.
>>
>> Sadly, it hasn't been updated in a while, which means that Soot can't
>> handle newer constructs.
>>
>> I am volunteering to update it. The thing is, we'd like to be able to
>> switch between Java versions. As far as I can tell, things are woven
>> in statically in JastAddJ's different front-end.
>>
>> Is there some kind of option that we could give to JastAddJ to operate
>> within one mode (1.4, 5, 7) or the other?
>>
>> Regards,
>>
>
>
> _______________________________________________
> JastAdd mailing list
> JastAdd_at_cs.lth.se
> https://mail1.cs.lth.se/cgi-bin/mailman/listinfo/jastadd
--
Marc-André Laverdière-Papineau
Étudiant au doctorat - PhD Student
Received on Wed Jul 18 2012 - 00:15:35 CEST