You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jim Bethancourt <ji...@gmail.com> on 2007/02/18 21:08:53 UTC
Terracotta Maven plugin(s), anyone?
Hi all,
I was wondering if anyone would be interested in developing a Maven 2 plugin
/ plugins that would allow for developers to apply Terracotta bytecode
enhancement to their Java code through Maven. I've only worked through the
Terracotta DSO tutorial, but it seems like a Maven plugin would make a lot
of sense to automate the bytecode enhancement through the Maven build life
cycle. I can email the Terracotta folks and ask them if they would be able
to post the Terracotta files on Ibiblio since Maven 2.0.5 now supports
different licenses.
I've dabbled in plugin authoring before as well, but I don't know exactly
what all it would entail in this case.
Please write back and let me know
1) If you would find the plugin useful
and/or
2) If you would be interested in helping develop such a plugin
Thanks,
Jim
Re: [m2] [mojo-dev] Re: Terracotta Maven plugin(s), anyone?
Posted by Eric-Ellis <ee...@terracottatech.com>.
Hi Jim,
Just wanna let you guys know that Jason (he'll respond to the dev list)
should be your point of contact with Terracotta Dev. He's in charge of our
build system and is familiar with the 5000 some odd lines of Ruby code.
Also, so we don't get too much heat for it, I did set up Ivy to download our
3rd party libraries from Ibiblio's Maven repo; though the naming conventions
with Ivy are so strict that we had to host most of the stuff on our own
download site.
Briefly, our current architecture consists of JRuby scrips accessing ANT
tags through a Java API called LeafCutter. As I said before, we would
greatly appreciate your help with writing and integrating a new system. It
will certainly be faster, cleaner, more usable, and integrated with Eclipse.
Who could ask for more.
I'll spare you the details of how the existing system came to be. Try to
have a sense of humor about it. :)
Also, don't worry about uploading Jars and having a space to work. Jason can
post files to the download site for you right away and you'll be able to
create a branch using our svn repo.
Feel free to contact me as well.
Jim Bethancourt-2 wrote:
>
> I've started / moved the discussion over to the terracotta-dev mailing
> list
> (you can find it on www.terracotta.org) It looks like the first thing
> we'll
> need to do before we move forward is to first Mavenize the Terracotta
> build
> and post them on a repository, and then write plugins that make it easy to
> use in Maven. If we didn't, it would be a pain for users to use any
> plugins
> that were developed since they'd need to upload the jars to their local
> repository.
>
> Feel free to jump in if you'd like on the tc-dev mailing list. I'll get a
> discussion going again about developing plugins for Terracotta once the
> build is Mavenized. I must say, the ideas that came out of this
> discussion
> were quite impressive. Thanks to all who contributed!
>
>
> Thanks,
> Jim
>
> On 2/19/07, Eric-Ellis <ee...@terracottatech.com> wrote:
>>
>>
>> A Maven plugin could be written to configure and deploy a clustered
>> system
>> test scenario. Imagine you want to write JUnit tests to verify that data
>> is
>> being shared correctly across your cluster. We currently have several
>> ways
>> of doing this in our own code base; take a look at:
>> AbstractTransparentApp
>> and AbstractAppServerTestCase. Just last night I completed the initial
>> stages of the Lucene index cluster support which when merged with trunk
>> will
>> behave similarly to what the plugin may want to do.
>>
>> As for using Maven as our build system; we'd like to move forward but
>> it's
>> more of a cost/benefit decision that management will eventually make.
>> Essentially, our current system, in which I have few good things to
>> mention,
>> does get the job done and there is a huge backlog of features, platforms,
>> and software that we'd like to implement/support in the near future;
>> i.e.,
>> our hands are a bit full.
>>
>> Not to sound hopeless though, we could be moving to Maven in the next few
>> months. It would actually help the cause if you (anyone interested in
>> this
>> posting) were to join our "dev" mailing list and post a few thoughts
>> about
>> the contributor learning curve and the type of technical advice, related
>> to
>> Maven implementation, that our build engineers would receive from the
>> community.
>>
>>
>> Thanks,
>> Eric
>> --Terracotta, Software Engineer
>>
>>
>>
>> Jim Bethancourt-2 wrote:
>> >
>> > Hi all,
>> > It's great to see such fast response so far, even on a weekend. Please
>> > continue to write to this thread if you're interested in such a plugin
>> or
>> > want to help develop it.
>> >
>> > Eric -- I definitely see where you're coming from and understand
>> > completely
>> > with regards to Terracotta being a platform vs. a module. I was
>> thinking
>> > more along the lines of having a plugin that would bind to a build
>> > lifecycle
>> > phase (such as the install or deploy phase) and perform the bytecode
>> > enhancement at that point. But as Eugene mentioned, that probably
>> > wouldn't
>> > work so well for doing anything other than testing the
>> bytecode-enhanced
>> > code during the test phase of the Maven build cycle. However, it would
>> > certainly be a start to try that out. :-) Would that seem like a
>> > reasonable
>> > goal for now (write a surefire-terracotta / terracotta-surefire
>> plugin?),
>> > or
>> > do you think it would it be best to wait until Terracotta is Mavenized?
>> >
>> > As far as rewriting/Mavenizing Terracotta's build system goes, it would
>> > definitely be helpful for folks who would be interested in adding to
>> > Terracotta's codebase to get up to speed quickly. Any ideas on what
>> kind
>> > of
>> > timeline you're looking at? You could start out with a multi-pom
>> project
>> > with nonstanard directories to get things going and then refactor to a
>> > multi-pom project with standard directory structures once you feel
>> > confident. I've done the first half of what I mentioned to demo Maven
>> 2
>> > on
>> > an established codebase and it worked really well. Let me know and I'd
>> be
>> > happy to try and help with the effort.
>> >
>> > Thanks,
>> > Jim
>> >
>> >
>> >
>> > On 2/18/07, Eric-Ellis <ee...@terracottatech.com> wrote:
>> >>
>> >>
>> >>
>> >> Raphaël Piéroni-3 wrote:
>> >> >
>> >> > Hi Jim,
>> >> >
>> >> > I think the Mojo community would like to host your plugin.
>> >> >
>> >> > Just ask for at : dev@mojo.codehaus.org
>> >> >
>> >> > Raphaël
>> >> >
>> >> > 2007/2/18, Scott Ryan <sr...@gmail.com>:
>> >> >>
>> >> >> I would love to work with you on developing the plugin. I heard
>> >> >> about their presentation at the Denver Java User's Group and would
>> >> >> love to look at their technology deeper. I have developed some
>> >> >> plugins already for weblogic and appfuse.
>> >> >>
>> >> >> Scott Ryan
>> >> >> scott@theryansplace.com
>> >> >>
>> >> >>
>> >> >> On Feb 18, 2007, at 1:08 PM, Jim Bethancourt wrote:
>> >> >>
>> >> >> > Hi all,
>> >> >> > I was wondering if anyone would be interested in developing a
>> Maven
>> >> >> > 2 plugin
>> >> >> > / plugins that would allow for developers to apply Terracotta
>> >> bytecode
>> >> >> > enhancement to their Java code through Maven. I've only worked
>> >> >> > through the
>> >> >> > Terracotta DSO tutorial, but it seems like a Maven plugin would
>> >> >> > make a lot
>> >> >> > of sense to automate the bytecode enhancement through the Maven
>> >> >> > build life
>> >> >> > cycle. I can email the Terracotta folks and ask them if they
>> would
>> >> >> > be able
>> >> >> > to post the Terracotta files on Ibiblio since Maven 2.0.5 now
>> >> supports
>> >> >> > different licenses.
>> >> >> >
>> >> >> > I've dabbled in plugin authoring before as well, but I don't know
>> >> >> > exactly
>> >> >> > what all it would entail in this case.
>> >> >> >
>> >> >> > Please write back and let me know
>> >> >> > 1) If you would find the plugin useful
>> >> >> > and/or
>> >> >> > 2) If you would be interested in helping develop such a plugin
>> >> >> >
>> >> >> > Thanks,
>> >> >> > Jim
>> >> >>
>> >> >>
>> >> >>
>> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> >> For additional commands, e-mail: users-help@maven.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >> Hi guys,
>> >>
>> >> Eugene and I work for Terracotta as software engineers. As Eugene has
>> >> mentioned, our DSO implementation instruments bytecode at runtime so
>> >> integrating the product into a build cycle wont be possible. We're
>> really
>> >> working to develop Terracotta as a platform as opposed to a module
>> like
>> >> Apache Commons. We do think that Maven is the right way to go though
>> and
>> >> are
>> >> interested in rewriting our own custom build system to use it.
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9036598
>> >> Sent from the Maven - Users mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: users-help@maven.apache.org
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9047148
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9094788
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] [mojo-dev] Re: Terracotta Maven plugin(s), anyone?
Posted by Jim Bethancourt <ji...@gmail.com>.
I've started / moved the discussion over to the terracotta-dev mailing list
(you can find it on www.terracotta.org) It looks like the first thing we'll
need to do before we move forward is to first Mavenize the Terracotta build
and post them on a repository, and then write plugins that make it easy to
use in Maven. If we didn't, it would be a pain for users to use any plugins
that were developed since they'd need to upload the jars to their local
repository.
Feel free to jump in if you'd like on the tc-dev mailing list. I'll get a
discussion going again about developing plugins for Terracotta once the
build is Mavenized. I must say, the ideas that came out of this discussion
were quite impressive. Thanks to all who contributed!
Thanks,
Jim
On 2/19/07, Eric-Ellis <ee...@terracottatech.com> wrote:
>
>
> A Maven plugin could be written to configure and deploy a clustered system
> test scenario. Imagine you want to write JUnit tests to verify that data
> is
> being shared correctly across your cluster. We currently have several ways
> of doing this in our own code base; take a look at: AbstractTransparentApp
> and AbstractAppServerTestCase. Just last night I completed the initial
> stages of the Lucene index cluster support which when merged with trunk
> will
> behave similarly to what the plugin may want to do.
>
> As for using Maven as our build system; we'd like to move forward but it's
> more of a cost/benefit decision that management will eventually make.
> Essentially, our current system, in which I have few good things to
> mention,
> does get the job done and there is a huge backlog of features, platforms,
> and software that we'd like to implement/support in the near future; i.e.,
> our hands are a bit full.
>
> Not to sound hopeless though, we could be moving to Maven in the next few
> months. It would actually help the cause if you (anyone interested in this
> posting) were to join our "dev" mailing list and post a few thoughts about
> the contributor learning curve and the type of technical advice, related
> to
> Maven implementation, that our build engineers would receive from the
> community.
>
>
> Thanks,
> Eric
> --Terracotta, Software Engineer
>
>
>
> Jim Bethancourt-2 wrote:
> >
> > Hi all,
> > It's great to see such fast response so far, even on a weekend. Please
> > continue to write to this thread if you're interested in such a plugin
> or
> > want to help develop it.
> >
> > Eric -- I definitely see where you're coming from and understand
> > completely
> > with regards to Terracotta being a platform vs. a module. I was
> thinking
> > more along the lines of having a plugin that would bind to a build
> > lifecycle
> > phase (such as the install or deploy phase) and perform the bytecode
> > enhancement at that point. But as Eugene mentioned, that probably
> > wouldn't
> > work so well for doing anything other than testing the bytecode-enhanced
> > code during the test phase of the Maven build cycle. However, it would
> > certainly be a start to try that out. :-) Would that seem like a
> > reasonable
> > goal for now (write a surefire-terracotta / terracotta-surefire
> plugin?),
> > or
> > do you think it would it be best to wait until Terracotta is Mavenized?
> >
> > As far as rewriting/Mavenizing Terracotta's build system goes, it would
> > definitely be helpful for folks who would be interested in adding to
> > Terracotta's codebase to get up to speed quickly. Any ideas on what
> kind
> > of
> > timeline you're looking at? You could start out with a multi-pom
> project
> > with nonstanard directories to get things going and then refactor to a
> > multi-pom project with standard directory structures once you feel
> > confident. I've done the first half of what I mentioned to demo Maven 2
> > on
> > an established codebase and it worked really well. Let me know and I'd
> be
> > happy to try and help with the effort.
> >
> > Thanks,
> > Jim
> >
> >
> >
> > On 2/18/07, Eric-Ellis <ee...@terracottatech.com> wrote:
> >>
> >>
> >>
> >> Raphaël Piéroni-3 wrote:
> >> >
> >> > Hi Jim,
> >> >
> >> > I think the Mojo community would like to host your plugin.
> >> >
> >> > Just ask for at : dev@mojo.codehaus.org
> >> >
> >> > Raphaël
> >> >
> >> > 2007/2/18, Scott Ryan <sr...@gmail.com>:
> >> >>
> >> >> I would love to work with you on developing the plugin. I heard
> >> >> about their presentation at the Denver Java User's Group and would
> >> >> love to look at their technology deeper. I have developed some
> >> >> plugins already for weblogic and appfuse.
> >> >>
> >> >> Scott Ryan
> >> >> scott@theryansplace.com
> >> >>
> >> >>
> >> >> On Feb 18, 2007, at 1:08 PM, Jim Bethancourt wrote:
> >> >>
> >> >> > Hi all,
> >> >> > I was wondering if anyone would be interested in developing a
> Maven
> >> >> > 2 plugin
> >> >> > / plugins that would allow for developers to apply Terracotta
> >> bytecode
> >> >> > enhancement to their Java code through Maven. I've only worked
> >> >> > through the
> >> >> > Terracotta DSO tutorial, but it seems like a Maven plugin would
> >> >> > make a lot
> >> >> > of sense to automate the bytecode enhancement through the Maven
> >> >> > build life
> >> >> > cycle. I can email the Terracotta folks and ask them if they
> would
> >> >> > be able
> >> >> > to post the Terracotta files on Ibiblio since Maven 2.0.5 now
> >> supports
> >> >> > different licenses.
> >> >> >
> >> >> > I've dabbled in plugin authoring before as well, but I don't know
> >> >> > exactly
> >> >> > what all it would entail in this case.
> >> >> >
> >> >> > Please write back and let me know
> >> >> > 1) If you would find the plugin useful
> >> >> > and/or
> >> >> > 2) If you would be interested in helping develop such a plugin
> >> >> >
> >> >> > Thanks,
> >> >> > Jim
> >> >>
> >> >>
> >> >>
> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> >> For additional commands, e-mail: users-help@maven.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >> Hi guys,
> >>
> >> Eugene and I work for Terracotta as software engineers. As Eugene has
> >> mentioned, our DSO implementation instruments bytecode at runtime so
> >> integrating the product into a build cycle wont be possible. We're
> really
> >> working to develop Terracotta as a platform as opposed to a module like
> >> Apache Commons. We do think that Maven is the right way to go though
> and
> >> are
> >> interested in rewriting our own custom build system to use it.
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9036598
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9047148
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] [mojo-dev] Re: Terracotta Maven plugin(s), anyone?
Posted by Jim Bethancourt <ji...@gmail.com>.
I've started / moved the discussion over to the terracotta-dev mailing list
(you can find it on www.terracotta.org) It looks like the first thing we'll
need to do before we move forward is to first Mavenize the Terracotta build
and post them on a repository, and then write plugins that make it easy to
use in Maven. If we didn't, it would be a pain for users to use any plugins
that were developed since they'd need to upload the jars to their local
repository.
Feel free to jump in if you'd like on the tc-dev mailing list. I'll get a
discussion going again about developing plugins for Terracotta once the
build is Mavenized. I must say, the ideas that came out of this discussion
were quite impressive. Thanks to all who contributed!
Thanks,
Jim
On 2/19/07, Eric-Ellis <ee...@terracottatech.com> wrote:
>
>
> A Maven plugin could be written to configure and deploy a clustered system
> test scenario. Imagine you want to write JUnit tests to verify that data
> is
> being shared correctly across your cluster. We currently have several ways
> of doing this in our own code base; take a look at: AbstractTransparentApp
> and AbstractAppServerTestCase. Just last night I completed the initial
> stages of the Lucene index cluster support which when merged with trunk
> will
> behave similarly to what the plugin may want to do.
>
> As for using Maven as our build system; we'd like to move forward but it's
> more of a cost/benefit decision that management will eventually make.
> Essentially, our current system, in which I have few good things to
> mention,
> does get the job done and there is a huge backlog of features, platforms,
> and software that we'd like to implement/support in the near future; i.e.,
> our hands are a bit full.
>
> Not to sound hopeless though, we could be moving to Maven in the next few
> months. It would actually help the cause if you (anyone interested in this
> posting) were to join our "dev" mailing list and post a few thoughts about
> the contributor learning curve and the type of technical advice, related
> to
> Maven implementation, that our build engineers would receive from the
> community.
>
>
> Thanks,
> Eric
> --Terracotta, Software Engineer
>
>
>
> Jim Bethancourt-2 wrote:
> >
> > Hi all,
> > It's great to see such fast response so far, even on a weekend. Please
> > continue to write to this thread if you're interested in such a plugin
> or
> > want to help develop it.
> >
> > Eric -- I definitely see where you're coming from and understand
> > completely
> > with regards to Terracotta being a platform vs. a module. I was
> thinking
> > more along the lines of having a plugin that would bind to a build
> > lifecycle
> > phase (such as the install or deploy phase) and perform the bytecode
> > enhancement at that point. But as Eugene mentioned, that probably
> > wouldn't
> > work so well for doing anything other than testing the bytecode-enhanced
> > code during the test phase of the Maven build cycle. However, it would
> > certainly be a start to try that out. :-) Would that seem like a
> > reasonable
> > goal for now (write a surefire-terracotta / terracotta-surefire
> plugin?),
> > or
> > do you think it would it be best to wait until Terracotta is Mavenized?
> >
> > As far as rewriting/Mavenizing Terracotta's build system goes, it would
> > definitely be helpful for folks who would be interested in adding to
> > Terracotta's codebase to get up to speed quickly. Any ideas on what
> kind
> > of
> > timeline you're looking at? You could start out with a multi-pom
> project
> > with nonstanard directories to get things going and then refactor to a
> > multi-pom project with standard directory structures once you feel
> > confident. I've done the first half of what I mentioned to demo Maven 2
> > on
> > an established codebase and it worked really well. Let me know and I'd
> be
> > happy to try and help with the effort.
> >
> > Thanks,
> > Jim
> >
> >
> >
> > On 2/18/07, Eric-Ellis <ee...@terracottatech.com> wrote:
> >>
> >>
> >>
> >> Raphaël Piéroni-3 wrote:
> >> >
> >> > Hi Jim,
> >> >
> >> > I think the Mojo community would like to host your plugin.
> >> >
> >> > Just ask for at : dev@mojo.codehaus.org
> >> >
> >> > Raphaël
> >> >
> >> > 2007/2/18, Scott Ryan <sr...@gmail.com>:
> >> >>
> >> >> I would love to work with you on developing the plugin. I heard
> >> >> about their presentation at the Denver Java User's Group and would
> >> >> love to look at their technology deeper. I have developed some
> >> >> plugins already for weblogic and appfuse.
> >> >>
> >> >> Scott Ryan
> >> >> scott@theryansplace.com
> >> >>
> >> >>
> >> >> On Feb 18, 2007, at 1:08 PM, Jim Bethancourt wrote:
> >> >>
> >> >> > Hi all,
> >> >> > I was wondering if anyone would be interested in developing a
> Maven
> >> >> > 2 plugin
> >> >> > / plugins that would allow for developers to apply Terracotta
> >> bytecode
> >> >> > enhancement to their Java code through Maven. I've only worked
> >> >> > through the
> >> >> > Terracotta DSO tutorial, but it seems like a Maven plugin would
> >> >> > make a lot
> >> >> > of sense to automate the bytecode enhancement through the Maven
> >> >> > build life
> >> >> > cycle. I can email the Terracotta folks and ask them if they
> would
> >> >> > be able
> >> >> > to post the Terracotta files on Ibiblio since Maven 2.0.5 now
> >> supports
> >> >> > different licenses.
> >> >> >
> >> >> > I've dabbled in plugin authoring before as well, but I don't know
> >> >> > exactly
> >> >> > what all it would entail in this case.
> >> >> >
> >> >> > Please write back and let me know
> >> >> > 1) If you would find the plugin useful
> >> >> > and/or
> >> >> > 2) If you would be interested in helping develop such a plugin
> >> >> >
> >> >> > Thanks,
> >> >> > Jim
> >> >>
> >> >>
> >> >>
> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> >> For additional commands, e-mail: users-help@maven.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >> Hi guys,
> >>
> >> Eugene and I work for Terracotta as software engineers. As Eugene has
> >> mentioned, our DSO implementation instruments bytecode at runtime so
> >> integrating the product into a build cycle wont be possible. We're
> really
> >> working to develop Terracotta as a platform as opposed to a module like
> >> Apache Commons. We do think that Maven is the right way to go though
> and
> >> are
> >> interested in rewriting our own custom build system to use it.
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9036598
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9047148
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] [mojo-dev] Re: Terracotta Maven plugin(s), anyone?
Posted by Eric-Ellis <ee...@terracottatech.com>.
A Maven plugin could be written to configure and deploy a clustered system
test scenario. Imagine you want to write JUnit tests to verify that data is
being shared correctly across your cluster. We currently have several ways
of doing this in our own code base; take a look at: AbstractTransparentApp
and AbstractAppServerTestCase. Just last night I completed the initial
stages of the Lucene index cluster support which when merged with trunk will
behave similarly to what the plugin may want to do.
As for using Maven as our build system; we'd like to move forward but it's
more of a cost/benefit decision that management will eventually make.
Essentially, our current system, in which I have few good things to mention,
does get the job done and there is a huge backlog of features, platforms,
and software that we'd like to implement/support in the near future; i.e.,
our hands are a bit full.
Not to sound hopeless though, we could be moving to Maven in the next few
months. It would actually help the cause if you (anyone interested in this
posting) were to join our "dev" mailing list and post a few thoughts about
the contributor learning curve and the type of technical advice, related to
Maven implementation, that our build engineers would receive from the
community.
Thanks,
Eric
--Terracotta, Software Engineer
Jim Bethancourt-2 wrote:
>
> Hi all,
> It's great to see such fast response so far, even on a weekend. Please
> continue to write to this thread if you're interested in such a plugin or
> want to help develop it.
>
> Eric -- I definitely see where you're coming from and understand
> completely
> with regards to Terracotta being a platform vs. a module. I was thinking
> more along the lines of having a plugin that would bind to a build
> lifecycle
> phase (such as the install or deploy phase) and perform the bytecode
> enhancement at that point. But as Eugene mentioned, that probably
> wouldn't
> work so well for doing anything other than testing the bytecode-enhanced
> code during the test phase of the Maven build cycle. However, it would
> certainly be a start to try that out. :-) Would that seem like a
> reasonable
> goal for now (write a surefire-terracotta / terracotta-surefire plugin?),
> or
> do you think it would it be best to wait until Terracotta is Mavenized?
>
> As far as rewriting/Mavenizing Terracotta's build system goes, it would
> definitely be helpful for folks who would be interested in adding to
> Terracotta's codebase to get up to speed quickly. Any ideas on what kind
> of
> timeline you're looking at? You could start out with a multi-pom project
> with nonstanard directories to get things going and then refactor to a
> multi-pom project with standard directory structures once you feel
> confident. I've done the first half of what I mentioned to demo Maven 2
> on
> an established codebase and it worked really well. Let me know and I'd be
> happy to try and help with the effort.
>
> Thanks,
> Jim
>
>
>
> On 2/18/07, Eric-Ellis <ee...@terracottatech.com> wrote:
>>
>>
>>
>> Raphaël Piéroni-3 wrote:
>> >
>> > Hi Jim,
>> >
>> > I think the Mojo community would like to host your plugin.
>> >
>> > Just ask for at : dev@mojo.codehaus.org
>> >
>> > Raphaël
>> >
>> > 2007/2/18, Scott Ryan <sr...@gmail.com>:
>> >>
>> >> I would love to work with you on developing the plugin. I heard
>> >> about their presentation at the Denver Java User's Group and would
>> >> love to look at their technology deeper. I have developed some
>> >> plugins already for weblogic and appfuse.
>> >>
>> >> Scott Ryan
>> >> scott@theryansplace.com
>> >>
>> >>
>> >> On Feb 18, 2007, at 1:08 PM, Jim Bethancourt wrote:
>> >>
>> >> > Hi all,
>> >> > I was wondering if anyone would be interested in developing a Maven
>> >> > 2 plugin
>> >> > / plugins that would allow for developers to apply Terracotta
>> bytecode
>> >> > enhancement to their Java code through Maven. I've only worked
>> >> > through the
>> >> > Terracotta DSO tutorial, but it seems like a Maven plugin would
>> >> > make a lot
>> >> > of sense to automate the bytecode enhancement through the Maven
>> >> > build life
>> >> > cycle. I can email the Terracotta folks and ask them if they would
>> >> > be able
>> >> > to post the Terracotta files on Ibiblio since Maven 2.0.5 now
>> supports
>> >> > different licenses.
>> >> >
>> >> > I've dabbled in plugin authoring before as well, but I don't know
>> >> > exactly
>> >> > what all it would entail in this case.
>> >> >
>> >> > Please write back and let me know
>> >> > 1) If you would find the plugin useful
>> >> > and/or
>> >> > 2) If you would be interested in helping develop such a plugin
>> >> >
>> >> > Thanks,
>> >> > Jim
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: users-help@maven.apache.org
>> >>
>> >>
>> >
>> >
>>
>>
>> Hi guys,
>>
>> Eugene and I work for Terracotta as software engineers. As Eugene has
>> mentioned, our DSO implementation instruments bytecode at runtime so
>> integrating the product into a build cycle wont be possible. We're really
>> working to develop Terracotta as a platform as opposed to a module like
>> Apache Commons. We do think that Maven is the right way to go though and
>> are
>> interested in rewriting our own custom build system to use it.
>> --
>> View this message in context:
>> http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9036598
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9047148
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] [mojo-dev] Re: Terracotta Maven plugin(s), anyone?
Posted by Jim Bethancourt <ji...@gmail.com>.
Hi all,
It's great to see such fast response so far, even on a weekend. Please
continue to write to this thread if you're interested in such a plugin or
want to help develop it.
Eric -- I definitely see where you're coming from and understand completely
with regards to Terracotta being a platform vs. a module. I was thinking
more along the lines of having a plugin that would bind to a build lifecycle
phase (such as the install or deploy phase) and perform the bytecode
enhancement at that point. But as Eugene mentioned, that probably wouldn't
work so well for doing anything other than testing the bytecode-enhanced
code during the test phase of the Maven build cycle. However, it would
certainly be a start to try that out. :-) Would that seem like a reasonable
goal for now (write a surefire-terracotta / terracotta-surefire plugin?), or
do you think it would it be best to wait until Terracotta is Mavenized?
As far as rewriting/Mavenizing Terracotta's build system goes, it would
definitely be helpful for folks who would be interested in adding to
Terracotta's codebase to get up to speed quickly. Any ideas on what kind of
timeline you're looking at? You could start out with a multi-pom project
with nonstanard directories to get things going and then refactor to a
multi-pom project with standard directory structures once you feel
confident. I've done the first half of what I mentioned to demo Maven 2 on
an established codebase and it worked really well. Let me know and I'd be
happy to try and help with the effort.
Thanks,
Jim
On 2/18/07, Eric-Ellis <ee...@terracottatech.com> wrote:
>
>
>
> Raphaël Piéroni-3 wrote:
> >
> > Hi Jim,
> >
> > I think the Mojo community would like to host your plugin.
> >
> > Just ask for at : dev@mojo.codehaus.org
> >
> > Raphaël
> >
> > 2007/2/18, Scott Ryan <sr...@gmail.com>:
> >>
> >> I would love to work with you on developing the plugin. I heard
> >> about their presentation at the Denver Java User's Group and would
> >> love to look at their technology deeper. I have developed some
> >> plugins already for weblogic and appfuse.
> >>
> >> Scott Ryan
> >> scott@theryansplace.com
> >>
> >>
> >> On Feb 18, 2007, at 1:08 PM, Jim Bethancourt wrote:
> >>
> >> > Hi all,
> >> > I was wondering if anyone would be interested in developing a Maven
> >> > 2 plugin
> >> > / plugins that would allow for developers to apply Terracotta
> bytecode
> >> > enhancement to their Java code through Maven. I've only worked
> >> > through the
> >> > Terracotta DSO tutorial, but it seems like a Maven plugin would
> >> > make a lot
> >> > of sense to automate the bytecode enhancement through the Maven
> >> > build life
> >> > cycle. I can email the Terracotta folks and ask them if they would
> >> > be able
> >> > to post the Terracotta files on Ibiblio since Maven 2.0.5 now
> supports
> >> > different licenses.
> >> >
> >> > I've dabbled in plugin authoring before as well, but I don't know
> >> > exactly
> >> > what all it would entail in this case.
> >> >
> >> > Please write back and let me know
> >> > 1) If you would find the plugin useful
> >> > and/or
> >> > 2) If you would be interested in helping develop such a plugin
> >> >
> >> > Thanks,
> >> > Jim
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
>
> Hi guys,
>
> Eugene and I work for Terracotta as software engineers. As Eugene has
> mentioned, our DSO implementation instruments bytecode at runtime so
> integrating the product into a build cycle wont be possible. We're really
> working to develop Terracotta as a platform as opposed to a module like
> Apache Commons. We do think that Maven is the right way to go though and
> are
> interested in rewriting our own custom build system to use it.
> --
> View this message in context:
> http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9036598
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] [mojo-dev] Re: Terracotta Maven plugin(s), anyone?
Posted by Jim Bethancourt <ji...@gmail.com>.
Hi all,
It's great to see such fast response so far, even on a weekend. Please
continue to write to this thread if you're interested in such a plugin or
want to help develop it.
Eric -- I definitely see where you're coming from and understand completely
with regards to Terracotta being a platform vs. a module. I was thinking
more along the lines of having a plugin that would bind to a build lifecycle
phase (such as the install or deploy phase) and perform the bytecode
enhancement at that point. But as Eugene mentioned, that probably wouldn't
work so well for doing anything other than testing the bytecode-enhanced
code during the test phase of the Maven build cycle. However, it would
certainly be a start to try that out. :-) Would that seem like a reasonable
goal for now (write a surefire-terracotta / terracotta-surefire plugin?), or
do you think it would it be best to wait until Terracotta is Mavenized?
As far as rewriting/Mavenizing Terracotta's build system goes, it would
definitely be helpful for folks who would be interested in adding to
Terracotta's codebase to get up to speed quickly. Any ideas on what kind of
timeline you're looking at? You could start out with a multi-pom project
with nonstanard directories to get things going and then refactor to a
multi-pom project with standard directory structures once you feel
confident. I've done the first half of what I mentioned to demo Maven 2 on
an established codebase and it worked really well. Let me know and I'd be
happy to try and help with the effort.
Thanks,
Jim
On 2/18/07, Eric-Ellis <ee...@terracottatech.com> wrote:
>
>
>
> Raphaël Piéroni-3 wrote:
> >
> > Hi Jim,
> >
> > I think the Mojo community would like to host your plugin.
> >
> > Just ask for at : dev@mojo.codehaus.org
> >
> > Raphaël
> >
> > 2007/2/18, Scott Ryan <sr...@gmail.com>:
> >>
> >> I would love to work with you on developing the plugin. I heard
> >> about their presentation at the Denver Java User's Group and would
> >> love to look at their technology deeper. I have developed some
> >> plugins already for weblogic and appfuse.
> >>
> >> Scott Ryan
> >> scott@theryansplace.com
> >>
> >>
> >> On Feb 18, 2007, at 1:08 PM, Jim Bethancourt wrote:
> >>
> >> > Hi all,
> >> > I was wondering if anyone would be interested in developing a Maven
> >> > 2 plugin
> >> > / plugins that would allow for developers to apply Terracotta
> bytecode
> >> > enhancement to their Java code through Maven. I've only worked
> >> > through the
> >> > Terracotta DSO tutorial, but it seems like a Maven plugin would
> >> > make a lot
> >> > of sense to automate the bytecode enhancement through the Maven
> >> > build life
> >> > cycle. I can email the Terracotta folks and ask them if they would
> >> > be able
> >> > to post the Terracotta files on Ibiblio since Maven 2.0.5 now
> supports
> >> > different licenses.
> >> >
> >> > I've dabbled in plugin authoring before as well, but I don't know
> >> > exactly
> >> > what all it would entail in this case.
> >> >
> >> > Please write back and let me know
> >> > 1) If you would find the plugin useful
> >> > and/or
> >> > 2) If you would be interested in helping develop such a plugin
> >> >
> >> > Thanks,
> >> > Jim
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
>
> Hi guys,
>
> Eugene and I work for Terracotta as software engineers. As Eugene has
> mentioned, our DSO implementation instruments bytecode at runtime so
> integrating the product into a build cycle wont be possible. We're really
> working to develop Terracotta as a platform as opposed to a module like
> Apache Commons. We do think that Maven is the right way to go though and
> are
> interested in rewriting our own custom build system to use it.
> --
> View this message in context:
> http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9036598
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] [mojo-dev] Re: Terracotta Maven plugin(s), anyone?
Posted by Eric-Ellis <ee...@terracottatech.com>.
Raphaël Piéroni-3 wrote:
>
> Hi Jim,
>
> I think the Mojo community would like to host your plugin.
>
> Just ask for at : dev@mojo.codehaus.org
>
> Raphaël
>
> 2007/2/18, Scott Ryan <sr...@gmail.com>:
>>
>> I would love to work with you on developing the plugin. I heard
>> about their presentation at the Denver Java User's Group and would
>> love to look at their technology deeper. I have developed some
>> plugins already for weblogic and appfuse.
>>
>> Scott Ryan
>> scott@theryansplace.com
>>
>>
>> On Feb 18, 2007, at 1:08 PM, Jim Bethancourt wrote:
>>
>> > Hi all,
>> > I was wondering if anyone would be interested in developing a Maven
>> > 2 plugin
>> > / plugins that would allow for developers to apply Terracotta bytecode
>> > enhancement to their Java code through Maven. I've only worked
>> > through the
>> > Terracotta DSO tutorial, but it seems like a Maven plugin would
>> > make a lot
>> > of sense to automate the bytecode enhancement through the Maven
>> > build life
>> > cycle. I can email the Terracotta folks and ask them if they would
>> > be able
>> > to post the Terracotta files on Ibiblio since Maven 2.0.5 now supports
>> > different licenses.
>> >
>> > I've dabbled in plugin authoring before as well, but I don't know
>> > exactly
>> > what all it would entail in this case.
>> >
>> > Please write back and let me know
>> > 1) If you would find the plugin useful
>> > and/or
>> > 2) If you would be interested in helping develop such a plugin
>> >
>> > Thanks,
>> > Jim
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
Hi guys,
Eugene and I work for Terracotta as software engineers. As Eugene has
mentioned, our DSO implementation instruments bytecode at runtime so
integrating the product into a build cycle wont be possible. We're really
working to develop Terracotta as a platform as opposed to a module like
Apache Commons. We do think that Maven is the right way to go though and are
interested in rewriting our own custom build system to use it.
--
View this message in context: http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9036598
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Terracotta Maven plugin(s), anyone?
Posted by Raphaël Piéroni <ra...@gmail.com>.
Hi Jim,
I think the Mojo community would like to host your plugin.
Just ask for at : dev@mojo.codehaus.org
Raphaël
2007/2/18, Scott Ryan <sr...@gmail.com>:
>
> I would love to work with you on developing the plugin. I heard
> about their presentation at the Denver Java User's Group and would
> love to look at their technology deeper. I have developed some
> plugins already for weblogic and appfuse.
>
> Scott Ryan
> scott@theryansplace.com
>
>
> On Feb 18, 2007, at 1:08 PM, Jim Bethancourt wrote:
>
> > Hi all,
> > I was wondering if anyone would be interested in developing a Maven
> > 2 plugin
> > / plugins that would allow for developers to apply Terracotta bytecode
> > enhancement to their Java code through Maven. I've only worked
> > through the
> > Terracotta DSO tutorial, but it seems like a Maven plugin would
> > make a lot
> > of sense to automate the bytecode enhancement through the Maven
> > build life
> > cycle. I can email the Terracotta folks and ask them if they would
> > be able
> > to post the Terracotta files on Ibiblio since Maven 2.0.5 now supports
> > different licenses.
> >
> > I've dabbled in plugin authoring before as well, but I don't know
> > exactly
> > what all it would entail in this case.
> >
> > Please write back and let me know
> > 1) If you would find the plugin useful
> > and/or
> > 2) If you would be interested in helping develop such a plugin
> >
> > Thanks,
> > Jim
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Terracotta Maven plugin(s), anyone?
Posted by Scott Ryan <sr...@gmail.com>.
I would love to work with you on developing the plugin. I heard
about their presentation at the Denver Java User's Group and would
love to look at their technology deeper. I have developed some
plugins already for weblogic and appfuse.
Scott Ryan
scott@theryansplace.com
On Feb 18, 2007, at 1:08 PM, Jim Bethancourt wrote:
> Hi all,
> I was wondering if anyone would be interested in developing a Maven
> 2 plugin
> / plugins that would allow for developers to apply Terracotta bytecode
> enhancement to their Java code through Maven. I've only worked
> through the
> Terracotta DSO tutorial, but it seems like a Maven plugin would
> make a lot
> of sense to automate the bytecode enhancement through the Maven
> build life
> cycle. I can email the Terracotta folks and ask them if they would
> be able
> to post the Terracotta files on Ibiblio since Maven 2.0.5 now supports
> different licenses.
>
> I've dabbled in plugin authoring before as well, but I don't know
> exactly
> what all it would entail in this case.
>
> Please write back and let me know
> 1) If you would find the plugin useful
> and/or
> 2) If you would be interested in helping develop such a plugin
>
> Thanks,
> Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Terracotta Maven plugin(s), anyone?
Posted by Scott Ryan <sr...@gmail.com>.
I would love to work with you on developing the plugin. I heard
about their presentation at the Denver Java User's Group and would
love to look at their technology deeper. I have developed some
plugins already for weblogic and appfuse.
Scott Ryan
scott@theryansplace.com
On Feb 18, 2007, at 1:08 PM, Jim Bethancourt wrote:
> Hi all,
> I was wondering if anyone would be interested in developing a Maven
> 2 plugin
> / plugins that would allow for developers to apply Terracotta bytecode
> enhancement to their Java code through Maven. I've only worked
> through the
> Terracotta DSO tutorial, but it seems like a Maven plugin would
> make a lot
> of sense to automate the bytecode enhancement through the Maven
> build life
> cycle. I can email the Terracotta folks and ask them if they would
> be able
> to post the Terracotta files on Ibiblio since Maven 2.0.5 now supports
> different licenses.
>
> I've dabbled in plugin authoring before as well, but I don't know
> exactly
> what all it would entail in this case.
>
> Please write back and let me know
> 1) If you would find the plugin useful
> and/or
> 2) If you would be interested in helping develop such a plugin
>
> Thanks,
> Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m2] Terracotta Maven plugin(s), anyone?
Posted by Eugene Kuleshov <eu...@md.pp.ru>.
Jim Bethancourt-2 wrote:
>
> I was wondering if anyone would be interested in developing a Maven 2
> plugin
> / plugins that would allow for developers to apply Terracotta bytecode
> enhancement to their Java code through Maven. I've only worked through
> the
> Terracotta DSO tutorial, but it seems like a Maven plugin would make a lot
> of sense to automate the bytecode enhancement through the Maven build life
> cycle. I can email the Terracotta folks and ask them if they would be
> able
> to post the Terracotta files on Ibiblio since Maven 2.0.5 now supports
> different licenses.
>
Unfortunately it is not how Terracotta DSO works now.
Currently there is no tools for compile-time instrumentation and all
classes are instrumented at the load time. Such instrumentation is turned on
using few -Xbootclasspath/p: and some system properties. That basically
allows you to launch your tests with Terracotta runtime, as long as you
start them in a separate vm.
regards,
Eugene Kuleshov
Terracotta
--
View this message in context: http://www.nabble.com/Terracotta-Maven-plugin%28s%29%2C-anyone--tf3249559s177.html#a9034666
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org