You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Don Brown <do...@gmail.com> on 2005/08/07 09:17:35 UTC
[jci] Karma and status request
I'm not sure the policy regarding sandbox projects for one that
already is a member of several commons proper projects, but I figure
it couldn't hurt to ask.
For a Struts project in the sandbox, Ti, I've started playing around
with JCI, and its CompilingClassLoader in particular. I wanted to
make a small improvement which would allow the JavaCompiler
implementation to be passed in, rather than have it hardcoded for the
EclipseJavaCompiler.
What is the status of the JCI project? Do I have enough karma to add
myself to the project.xml and commit the patches?
Thanks,
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [jci] Karma and status request
Posted by Davanum Srinivas <da...@gmail.com>.
+1 from me.
On 8/7/05, Torsten Curdt <tc...@apache.org> wrote:
>
> On 07.08.2005, at 09:43, Don Brown wrote:
>
> > Torsten, what do you think? I basically added two more constructors
> > to allow the passing of the JavaCompiler instance to the
> > CompilingClassLoader. Nothing fancy, but it does let me externalize
> > the compiler choice and without impacting any existing usage of jci.
>
> Don,
>
> feel free to help out and improve jci.
> The more projects using it the better.
>
> At the moment I am focusing a bit more
> on javaflow. But both go hand in hand.
>
> The configuration part of the compilers
> should be externalized into the factory.
> Also I would like to be able to specify
> a dedicated classpath for compilation.
> Plus I would like to see more compiler
> implementations.
>
> ...and as always the testcases and
> documentation need a bit of attention
>
> :)
>
> cheers
> --
> Torsten
>
>
>
--
Davanum Srinivas -http://blogs.cocoondev.org/dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [jci] Karma and status request
Posted by Torsten Curdt <tc...@apache.org>.
+1 sounds great to me
On 07.08.2005, at 14:55, Brett Porter wrote:
> I'll also let you know (and remind myself) that I would like to
> incporate Maven's support for jikes, javac and eclipse (where it might
> differ) and have it use JCI. One thing I was going to do to help that
> was split it into several smaller JARs - a clean dependency-less
> API and
> implementations for each.
>
> If that's something that would help you, let me know. I'm aiming to do
> it in September right now.
>
> Cheers,
> Brett
Re: [jci] Karma and status request
Posted by Brett Porter <br...@apache.org>.
I'll also let you know (and remind myself) that I would like to
incporate Maven's support for jikes, javac and eclipse (where it might
differ) and have it use JCI. One thing I was going to do to help that
was split it into several smaller JARs - a clean dependency-less API and
implementations for each.
If that's something that would help you, let me know. I'm aiming to do
it in September right now.
Cheers,
Brett
Torsten Curdt wrote:
>
> On 07.08.2005, at 09:43, Don Brown wrote:
>
>> Torsten, what do you think? I basically added two more constructors
>> to allow the passing of the JavaCompiler instance to the
>> CompilingClassLoader. Nothing fancy, but it does let me externalize
>> the compiler choice and without impacting any existing usage of jci.
>
>
> Don,
>
> feel free to help out and improve jci.
> The more projects using it the better.
>
> At the moment I am focusing a bit more
> on javaflow. But both go hand in hand.
>
> The configuration part of the compilers
> should be externalized into the factory.
> Also I would like to be able to specify
> a dedicated classpath for compilation.
> Plus I would like to see more compiler
> implementations.
>
> ...and as always the testcases and
> documentation need a bit of attention
>
> :)
>
> cheers
> --
> Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [jci] Karma and status request
Posted by Torsten Curdt <tc...@apache.org>.
On 07.08.2005, at 09:43, Don Brown wrote:
> Torsten, what do you think? I basically added two more constructors
> to allow the passing of the JavaCompiler instance to the
> CompilingClassLoader. Nothing fancy, but it does let me externalize
> the compiler choice and without impacting any existing usage of jci.
Don,
feel free to help out and improve jci.
The more projects using it the better.
At the moment I am focusing a bit more
on javaflow. But both go hand in hand.
The configuration part of the compilers
should be externalized into the factory.
Also I would like to be able to specify
a dedicated classpath for compilation.
Plus I would like to see more compiler
implementations.
...and as always the testcases and
documentation need a bit of attention
:)
cheers
--
Torsten
Re: [jci] Karma and status request
Posted by Don Brown <do...@gmail.com>.
Torsten, what do you think? I basically added two more constructors
to allow the passing of the JavaCompiler instance to the
CompilingClassLoader. Nothing fancy, but it does let me externalize
the compiler choice and without impacting any existing usage of jci.
Ti is a project in the Struts sandbox I'm working on; sorry for the confusion.
Don
On 8/7/05, Simon Kitching <sk...@apache.org> wrote:
> Hi Don,
>
> On Sun, 2005-08-07 at 00:17 -0700, Don Brown wrote:
> > I'm not sure the policy regarding sandbox projects for one that
> > already is a member of several commons proper projects, but I figure
> > it couldn't hurt to ask.
> >
> > For a Struts project in the sandbox, Ti, I've started playing around
> > with JCI, and its CompilingClassLoader in particular. I wanted to
> > make a small improvement which would allow the JavaCompiler
> > implementation to be passed in, rather than have it hardcoded for the
> > EclipseJavaCompiler.
> >
> > What is the status of the JCI project? Do I have enough karma to add
> > myself to the project.xml and commit the patches?
>
> If you've got commit access to commons proper, then you already have
> access to the sandbox.
>
> However before modifying a project you've not been involved in before
> you should discuss this with the existing project maintainers. It's not
> just a matter of politeness (though that's important); it's also
> important to check that any change fits with the goals the original
> project maintainers are aiming for.
>
> I see that jci has just one developer listed in the project.xml file:
> Torsten Curdt. Torsten is reasonably active on the list so I suggest
> posting your patch proposal to the list and seeing what his response is;
> if he gives the ok you should be able to commit the patch yourself.
>
> BTW, you mention project "Ti" in the sandbox. This isn't in the commons
> sandbox; do you mean some other sandbox?
>
> Regards,
>
> Simon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [jci] Karma and status request
Posted by Simon Kitching <sk...@apache.org>.
Hi Don,
On Sun, 2005-08-07 at 00:17 -0700, Don Brown wrote:
> I'm not sure the policy regarding sandbox projects for one that
> already is a member of several commons proper projects, but I figure
> it couldn't hurt to ask.
>
> For a Struts project in the sandbox, Ti, I've started playing around
> with JCI, and its CompilingClassLoader in particular. I wanted to
> make a small improvement which would allow the JavaCompiler
> implementation to be passed in, rather than have it hardcoded for the
> EclipseJavaCompiler.
>
> What is the status of the JCI project? Do I have enough karma to add
> myself to the project.xml and commit the patches?
If you've got commit access to commons proper, then you already have
access to the sandbox.
However before modifying a project you've not been involved in before
you should discuss this with the existing project maintainers. It's not
just a matter of politeness (though that's important); it's also
important to check that any change fits with the goals the original
project maintainers are aiming for.
I see that jci has just one developer listed in the project.xml file:
Torsten Curdt. Torsten is reasonably active on the list so I suggest
posting your patch proposal to the list and seeing what his response is;
if he gives the ok you should be able to commit the patch yourself.
BTW, you mention project "Ti" in the sandbox. This isn't in the commons
sandbox; do you mean some other sandbox?
Regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org