I am looking for a Java Exporter for Moose. Earlier I had tried IPlasma but I am getting some problems in its interface so I cannot use it. I also tried J2Moose but the format generated by the tool is not accepted by moose. Is there a Java exporter for moose that is compatible with the current MSE file format?
thanx in advance,
Usman
Hi Usman,
You can use inFusion (http://www.intooitus.com/inFusion-tryit.html). It allows us one to import in mse-famix2 for VW and in mse-famix3 for Pharo.
Cheers, Jannik
On Dec 30, 2009, at 07:50 , Usman Bhatti wrote:
I am looking for a Java Exporter for Moose. Earlier I had tried IPlasma but I am getting some problems in its interface so I cannot use it. I also tried J2Moose but the format generated by the tool is not accepted by moose. Is there a Java exporter for moose that is compatible with the current MSE file format?
thanx in advance,
Usman _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
Here are the instructions: http://www.moosetechnology.org/docs/faq/importJavaWithinFusion
Cheers, Doru
On 30 Dec 2009, at 08:47, Laval Jannik wrote:
Hi Usman,
You can use inFusion (http://www.intooitus.com/inFusion-tryit.html). It allows us one to import in mse-famix2 for VW and in mse-famix3 for Pharo.
Cheers, Jannik
On Dec 30, 2009, at 07:50 , Usman Bhatti wrote:
I am looking for a Java Exporter for Moose. Earlier I had tried IPlasma but I am getting some problems in its interface so I cannot use it. I also tried J2Moose but the format generated by the tool is not accepted by moose. Is there a Java exporter for moose that is compatible with the current MSE file format?
thanx in advance,
Usman _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
Hi all,
I was just thinking about the Java import for moose, I am wondering how many people are using moose to analyze Java code. I think an interesting alternative to using infusion would be an Eclipse plugin that exports to mse-famix3. Is there any interest here for such a plugin?
On 30 Dec 2009, at 07:03, Tudor Girba wrote:
Hi,
Here are the instructions: http://www.moosetechnology.org/docs/faq/importJavaWithinFusion
Cheers, Doru
On 30 Dec 2009, at 08:47, Laval Jannik wrote:
Hi Usman,
You can use inFusion (http://www.intooitus.com/inFusion-tryit.html). It allows us one to import in mse-famix2 for VW and in mse-famix3 for Pharo.
Cheers, Jannik
On Dec 30, 2009, at 07:50 , Usman Bhatti wrote:
I am looking for a Java Exporter for Moose. Earlier I had tried IPlasma but I am getting some problems in its interface so I cannot use it. I also tried J2Moose but the format generated by the tool is not accepted by moose. Is there a Java exporter for moose that is compatible with the current MSE file format?
thanx in advance,
Usman _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Hi Johan,
Sure there is plenty of interest for any parser :).
In fact, we had several Eclipse plugins as Moose exporters: - http://www.moosetechnology.org/tools/retired/moosebrewer - http://www.moosetechnology.org/tools/retired/j2moose - http://www.moosetechnology.org/tools/retired/jfamix
Alex also worked on a Java parser written in VW: http://www.moosetechnology.org/tools/retired/java4moose
Yet another solution was based on JavaConnect/Penumbra: http://www.moosetechnology.org/docs/others/importWithPenumbraInVW
Unfortunately, none of these are maintained anymore. In general, the problem with parsers is that they are tedious to maintain for complicated languages, because many problems appear in very specific contexts.
So, we need solutions that have support behind, and inFusion is great because it has it, and I maintain the exporter to make sure it is working with the latest Moose.
But, as I said, there is always more interest in getting more importers around Moose, and it would be great if someone would be willing to invest longer term effort into :).
Cheers, Doru
On 30 Dec 2009, at 16:47, Johan Fabry wrote:
Hi all,
I was just thinking about the Java import for moose, I am wondering how many people are using moose to analyze Java code. I think an interesting alternative to using infusion would be an Eclipse plugin that exports to mse-famix3. Is there any interest here for such a plugin?
On 30 Dec 2009, at 07:03, Tudor Girba wrote:
Hi,
Here are the instructions: http://www.moosetechnology.org/docs/faq/importJavaWithinFusion
Cheers, Doru
On 30 Dec 2009, at 08:47, Laval Jannik wrote:
Hi Usman,
You can use inFusion (http://www.intooitus.com/inFusion-tryit.html). It allows us one to import in mse-famix2 for VW and in mse-famix3 for Pharo.
Cheers, Jannik
On Dec 30, 2009, at 07:50 , Usman Bhatti wrote:
I am looking for a Java Exporter for Moose. Earlier I had tried IPlasma but I am getting some problems in its interface so I cannot use it. I also tried J2Moose but the format generated by the tool is not accepted by moose. Is there a Java exporter for moose that is compatible with the current MSE file format?
thanx in advance,
Usman _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
jean-remi told me that he will do a bytecode driven java extractor for FAMIX30.
Stef On Dec 30, 2009, at 5:45 PM, Tudor Girba wrote:
Hi Johan,
Sure there is plenty of interest for any parser :).
In fact, we had several Eclipse plugins as Moose exporters:
- http://www.moosetechnology.org/tools/retired/moosebrewer
- http://www.moosetechnology.org/tools/retired/j2moose
- http://www.moosetechnology.org/tools/retired/jfamix
Alex also worked on a Java parser written in VW: http://www.moosetechnology.org/tools/retired/java4moose
Yet another solution was based on JavaConnect/Penumbra: http://www.moosetechnology.org/docs/others/importWithPenumbraInVW
Unfortunately, none of these are maintained anymore. In general, the problem with parsers is that they are tedious to maintain for complicated languages, because many problems appear in very specific contexts.
So, we need solutions that have support behind, and inFusion is great because it has it, and I maintain the exporter to make sure it is working with the latest Moose.
But, as I said, there is always more interest in getting more importers around Moose, and it would be great if someone would be willing to invest longer term effort into :).
Cheers, Doru
On 30 Dec 2009, at 16:47, Johan Fabry wrote:
Hi all,
I was just thinking about the Java import for moose, I am wondering how many people are using moose to analyze Java code. I think an interesting alternative to using infusion would be an Eclipse plugin that exports to mse-famix3. Is there any interest here for such a plugin?
On 30 Dec 2009, at 07:03, Tudor Girba wrote:
Hi,
Here are the instructions: http://www.moosetechnology.org/docs/faq/importJavaWithinFusion
Cheers, Doru
On 30 Dec 2009, at 08:47, Laval Jannik wrote:
Hi Usman,
You can use inFusion (http://www.intooitus.com/inFusion-tryit.html). It allows us one to import in mse-famix2 for VW and in mse-famix3 for Pharo.
Cheers, Jannik
On Dec 30, 2009, at 07:50 , Usman Bhatti wrote:
I am looking for a Java Exporter for Moose. Earlier I had tried IPlasma but I am getting some problems in its interface so I cannot use it. I also tried J2Moose but the format generated by the tool is not accepted by moose. Is there a Java exporter for moose that is compatible with the current MSE file format?
thanx in advance,
Usman _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
jean-remi told me that he will do a bytecode driven java extractor for FAMIX30.
That would be very cool!
Alexandre
On Dec 30, 2009, at 5:45 PM, Tudor Girba wrote:
Hi Johan,
Sure there is plenty of interest for any parser :).
In fact, we had several Eclipse plugins as Moose exporters:
- http://www.moosetechnology.org/tools/retired/moosebrewer
- http://www.moosetechnology.org/tools/retired/j2moose
- http://www.moosetechnology.org/tools/retired/jfamix
Alex also worked on a Java parser written in VW: http://www.moosetechnology.org/tools/retired/java4moose
Yet another solution was based on JavaConnect/Penumbra: http://www.moosetechnology.org/docs/others/importWithPenumbraInVW
Unfortunately, none of these are maintained anymore. In general, the problem with parsers is that they are tedious to maintain for complicated languages, because many problems appear in very specific contexts.
So, we need solutions that have support behind, and inFusion is great because it has it, and I maintain the exporter to make sure it is working with the latest Moose.
But, as I said, there is always more interest in getting more importers around Moose, and it would be great if someone would be willing to invest longer term effort into :).
Cheers, Doru
On 30 Dec 2009, at 16:47, Johan Fabry wrote:
Hi all,
I was just thinking about the Java import for moose, I am wondering how many people are using moose to analyze Java code. I think an interesting alternative to using infusion would be an Eclipse plugin that exports to mse-famix3. Is there any interest here for such a plugin?
On 30 Dec 2009, at 07:03, Tudor Girba wrote:
Hi,
Here are the instructions: http://www.moosetechnology.org/docs/faq/importJavaWithinFusion
Cheers, Doru
On 30 Dec 2009, at 08:47, Laval Jannik wrote:
Hi Usman,
You can use inFusion (http://www.intooitus.com/inFusion- tryit.html). It allows us one to import in mse-famix2 for VW and in mse- famix3 for Pharo.
Cheers, Jannik
On Dec 30, 2009, at 07:50 , Usman Bhatti wrote:
I am looking for a Java Exporter for Moose. Earlier I had tried IPlasma but I am getting some problems in its interface so I cannot use it. I also tried J2Moose but the format generated by the tool is not accepted by moose. Is there a Java exporter for moose that is compatible with the current MSE file format?
thanx in advance,
Usman _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Doru,
I am not really considering this as a parser, as the plugin would directly rely on the Eclipse model of the underlying code, which solves the parsing issues for us. (But certainly there will be other issues :-/ )
It's cool to see that there has been work done before on that! So my question is what we can learn of these efforts, what is the story here? Is there any clear picture on what was wrong with these multiple plugins and how each successive attempt solved/failed to solve issues ?
On 30 Dec 2009, at 13:45, Tudor Girba wrote:
Hi Johan,
Sure there is plenty of interest for any parser :).
In fact, we had several Eclipse plugins as Moose exporters:
- http://www.moosetechnology.org/tools/retired/moosebrewer
- http://www.moosetechnology.org/tools/retired/j2moose
- http://www.moosetechnology.org/tools/retired/jfamix
Alex also worked on a Java parser written in VW: http://www.moosetechnology.org/tools/retired/java4moose
Yet another solution was based on JavaConnect/Penumbra: http://www.moosetechnology.org/docs/others/importWithPenumbraInVW
Unfortunately, none of these are maintained anymore. In general, the problem with parsers is that they are tedious to maintain for complicated languages, because many problems appear in very specific contexts.
So, we need solutions that have support behind, and inFusion is great because it has it, and I maintain the exporter to make sure it is working with the latest Moose.
But, as I said, there is always more interest in getting more importers around Moose, and it would be great if someone would be willing to invest longer term effort into :).
Cheers, Doru
On 30 Dec 2009, at 16:47, Johan Fabry wrote:
Hi all,
I was just thinking about the Java import for moose, I am wondering how many people are using moose to analyze Java code. I think an interesting alternative to using infusion would be an Eclipse plugin that exports to mse-famix3. Is there any interest here for such a plugin?
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Hi Johan,
I am not really considering this as a parser, as the plugin would directly rely on the Eclipse model of the underlying code, which solves the parsing issues for us. (But certainly there will be other issues :-/ )
Sure, the parsing part will be solved, but you will still have to deal with the evolution of the AST and the interpretation of the AST, which is not trivial at all.
It's cool to see that there has been work done before on that! So my question is what we can learn of these efforts, what is the story here? Is there any clear picture on what was wrong with these multiple plugins and how each successive attempt solved/failed to solve issues ?
Well, probably Moose Brewer is the most advanced and up to date solution, being also the latest effort.
The main problem is that people have just left or shifted their interest. The Moose Brewer and j2moose plugins were started by students and as they left, nobody picked them up. jfamix was started by Frank Buchli as a side project, but as he got more busy with work he shifted away.
In the end, nobody picked these projects up and they all remained unmaintained.
So, all in all, the main lesson for me is that this kind of projects should not be dealt with through a one-time effort.
Cheers, Doru
On 30 Dec 2009, at 13:45, Tudor Girba wrote:
Hi Johan,
Sure there is plenty of interest for any parser :).
In fact, we had several Eclipse plugins as Moose exporters:
- http://www.moosetechnology.org/tools/retired/moosebrewer
- http://www.moosetechnology.org/tools/retired/j2moose
- http://www.moosetechnology.org/tools/retired/jfamix
Alex also worked on a Java parser written in VW: http://www.moosetechnology.org/tools/retired/java4moose
Yet another solution was based on JavaConnect/Penumbra: http://www.moosetechnology.org/docs/others/importWithPenumbraInVW
Unfortunately, none of these are maintained anymore. In general, the problem with parsers is that they are tedious to maintain for complicated languages, because many problems appear in very specific contexts.
So, we need solutions that have support behind, and inFusion is great because it has it, and I maintain the exporter to make sure it is working with the latest Moose.
But, as I said, there is always more interest in getting more importers around Moose, and it would be great if someone would be willing to invest longer term effort into :).
Cheers, Doru
On 30 Dec 2009, at 16:47, Johan Fabry wrote:
Hi all,
I was just thinking about the Java import for moose, I am wondering how many people are using moose to analyze Java code. I think an interesting alternative to using infusion would be an Eclipse plugin that exports to mse-famix3. Is there any interest here for such a plugin?
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Value is always contextual."
I am not really considering this as a parser, as the plugin would directly rely on the Eclipse model of the underlying code, which solves the parsing issues for us. (But certainly there will be other issues :-/ )
Sure, the parsing part will be solved, but you will still have to deal with the evolution of the AST and the interpretation of the AST, which is not trivial at all.
Not at all. I did this with Java4Moose and CAnalyzer. Analyzing the AST is not easy. Johan, do you know whether the Java AST in Eclipse is linked somehow with Subversion? As far as I know, comments are missing from what inFusion produce. Getting comments will be a good plus.
Just some ideas, Alexandre
It's cool to see that there has been work done before on that! So my question is what we can learn of these efforts, what is the story here? Is there any clear picture on what was wrong with these multiple plugins and how each successive attempt solved/failed to solve issues ?
Well, probably Moose Brewer is the most advanced and up to date solution, being also the latest effort.
The main problem is that people have just left or shifted their interest. The Moose Brewer and j2moose plugins were started by students and as they left, nobody picked them up. jfamix was started by Frank Buchli as a side project, but as he got more busy with work he shifted away.
In the end, nobody picked these projects up and they all remained unmaintained.
So, all in all, the main lesson for me is that this kind of projects should not be dealt with through a one-time effort.
Cheers, Doru
On 30 Dec 2009, at 13:45, Tudor Girba wrote:
Hi Johan,
Sure there is plenty of interest for any parser :).
In fact, we had several Eclipse plugins as Moose exporters:
- http://www.moosetechnology.org/tools/retired/moosebrewer
- http://www.moosetechnology.org/tools/retired/j2moose
- http://www.moosetechnology.org/tools/retired/jfamix
Alex also worked on a Java parser written in VW: http://www.moosetechnology.org/tools/retired/java4moose
Yet another solution was based on JavaConnect/Penumbra: http://www.moosetechnology.org/docs/others/importWithPenumbraInVW
Unfortunately, none of these are maintained anymore. In general, the problem with parsers is that they are tedious to maintain for complicated languages, because many problems appear in very specific contexts.
So, we need solutions that have support behind, and inFusion is great because it has it, and I maintain the exporter to make sure it is working with the latest Moose.
But, as I said, there is always more interest in getting more importers around Moose, and it would be great if someone would be willing to invest longer term effort into :).
Cheers, Doru
On 30 Dec 2009, at 16:47, Johan Fabry wrote:
Hi all,
I was just thinking about the Java import for moose, I am wondering how many people are using moose to analyze Java code. I think an interesting alternative to using infusion would be an Eclipse plugin that exports to mse-famix3. Is there any interest here for such a plugin?
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Value is always contextual."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 30 Dec 2009, at 21:46, Alexandre Bergel wrote:
Sure, the parsing part will be solved, but you will still have to deal with the evolution of the AST and the interpretation of the AST, which is not trivial at all.
Not at all. I did this with Java4Moose and CAnalyzer. Analyzing the AST is not easy. Johan, do you know whether the Java AST in Eclipse is linked somehow with Subversion?
AFAIK there is no integration AST wise, it's just file based, you can version anything.
As far as I know, comments are missing from what inFusion produce. Getting comments will be a good plus.
I was thinking about the comments as well as the full source code, maybe through some form of a file handle to keep memory overhead to a minimum.
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
On 30 Dec 2009, at 18:22, Tudor Girba wrote:
Hi Johan,
I am not really considering this as a parser, as the plugin would directly rely on the Eclipse model of the underlying code, which solves the parsing issues for us. (But certainly there will be other issues :-/ )
Sure, the parsing part will be solved, but you will still have to deal with the evolution of the AST and the interpretation of the AST, which is not trivial at all.
As I said, other issues ;-)
It's cool to see that there has been work done before on that! So my question is what we can learn of these efforts, what is the story here? Is there any clear picture on what was wrong with these multiple plugins and how each successive attempt solved/failed to solve issues ?
Well, probably Moose Brewer is the most advanced and up to date solution, being also the latest effort.
OK, so that could be a starting point.
The main problem is that people have just left or shifted their interest. The Moose Brewer and j2moose plugins were started by students and as they left, nobody picked them up. jfamix was started by Frank Buchli as a side project, but as he got more busy with work he shifted away.
In the end, nobody picked these projects up and they all remained unmaintained.
So, all in all, the main lesson for me is that this kind of projects should not be dealt with through a one-time effort.
True, to keep it up-to-date it needs to follow the evolution of the language, which with Java is a considerable issue :-/ Sounds like a yearly student project ;-)
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
True, to keep it up-to-date it needs to follow the evolution of the language, which with Java is a considerable issue :-/ Sounds like a yearly student project ;-)
Even that. The student needs to be an excellent engineer. This is difficult.
Alexandre
On 30 déc. 2009, at 16:47, Johan Fabry wrote:
Hi all,
I was just thinking about the Java import for moose, I am wondering how many people are using moose to analyze Java code. I think an interesting alternative to using infusion would be an Eclipse plugin that exports to mse-famix3. Is there any interest here for such a plugin?
Johan Brichau is doing something *different* with eclipse: he can import eclipse project directly within moose (in VW). Porting under Pharo was in progress last time I heard of it. It might be interesting to exchange with him on the subject.
On 30 Dec 2009, at 07:03, Tudor Girba wrote:
Hi,
Here are the instructions: http://www.moosetechnology.org/docs/faq/importJavaWithinFusion
Cheers, Doru
On 30 Dec 2009, at 08:47, Laval Jannik wrote:
Hi Usman,
You can use inFusion (http://www.intooitus.com/inFusion-tryit.html). It allows us one to import in mse-famix2 for VW and in mse-famix3 for Pharo.
Cheers, Jannik
On Dec 30, 2009, at 07:50 , Usman Bhatti wrote:
I am looking for a Java Exporter for Moose. Earlier I had tried IPlasma but I am getting some problems in its interface so I cannot use it. I also tried J2Moose but the format generated by the tool is not accepted by moose. Is there a Java exporter for moose that is compatible with the current MSE file format?
thanx in advance,
Usman _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
cool to see u having fun with Moose. Let us know if you have any problem
Stef
On Dec 30, 2009, at 7:50 AM, Usman Bhatti wrote:
I am looking for a Java Exporter for Moose. Earlier I had tried IPlasma but I am getting some problems in its interface so I cannot use it. I also tried J2Moose but the format generated by the tool is not accepted by moose. Is there a Java exporter for moose that is compatible with the current MSE file format?
thanx in advance,
Usman _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Johan Fabry -
Laval Jannik -
Simon Denier -
Stéphane Ducasse -
Tudor Girba -
Usman Bhatti