Hi John,

1. I've faxed my CLA this morning. I've never really need it before...

2. Don't think there's a JIRA for this, do I need to create one?

Regards,

Sylvain

On 9/22/06, John Casey <[EMAIL PROTECTED]> wrote:

Ok, I found John's email from the ADFFaces project page, so I'm copying
him
in here.

John, what do you think about migrating that jdeveloper plugin over to the
Maven sandbox, so we can expose it to a wider community of interested
developers?

Thanks,

-john

On 9/22/06, John Casey <[EMAIL PROTECTED]> wrote:
>
> Three questions:
>
> 1. fneuch: do you have a CLA at apache, so we could grant access to you
> for this plugin in the sandbox?
>
> 2. Which JIRA is this logged under?
>
> 3. Does anyone have contact info for John Fallows? I don't seem to have
> any messages in my gmail account from him (or, he's not searchable using
the
> above name or just his last name).
>
> I'm happy to help with bringing this over to Maven, and with isolating
> common functionality from the eclipse plugin, but I'm not sure where to
> start right now. I'm also not sure exactly which eclipse-plugin classes
are
> being referenced here, so I need that jdev plugin source to look at
before I
> can factor anything out of the eclipse plugin.
>
> Thanks,
>
> John
>
> On 9/22/06, Fneuch <[EMAIL PROTECTED]> wrote:
> >
> > I've rewrited the JDev plugins to use the same ide functionality
that's
> > use
> > in the eclipse plugin. I've mixed it with what was done in the
> > JDeveloperMojo.
> >
> > I take the liberty to do some change like : I used the package
> > org.apache.maven.plugin.jdeveloper, I add a "clean" goal to remove all
> > JDev
> > files and workspace, I split all the section in the XML project in
> > separate
> > component (think it's gonna be easier to maintain and change) and the
> > goal
> > is now jdeveloper.
> >
> > It's a first Draft. Is there a place I can send them for evaluation?
> >
> > Regards,
> > Sylvain
> >
> > On 9/14/06, Fneuch <[EMAIL PROTECTED]> wrote:
> > >
> > > We use the Maven JDeveloper plugins and if you look in the issues
> > (JIRA),
> > > you're going to see we already contributed. We need the plugin to
help
> > us
> > > migrate our developers to maven, so i could give a hand. I have only
> > few
> > > hours a week to put on it.
> > >
> > > I don't know where to start but if John guides me, I can try to
> > convert
> > > the actual plugin to the one using the IDE stuff in the eclipse
> > plugin.
> > >
> > > Sylvain
> > >
> > > On 9/13/06, Martin van den Bemt <[EMAIL PROTECTED]> wrote:
> > > >
> > > > We are currently testing maven2 with jdeveloper and if we are
happy,
> > we
> > > > definitely will start using
> > > > that a whole lot :)
> > > > Although I approach this more from the maven site, it would
> > definitely
> > > > be a benefit to work on the
> > > > plugin (assuming it needs work that is :)
> > > >
> > > > Mvgr,
> > > > Martin
> > > >
> > > > Brett Porter wrote:
> > > > > Now that we have the sandbox open to anyone, should we do this?
> > > > >
> > > > > On 10/08/2006, at 3:02 PM, Brett Porter wrote:
> > > > >
> > > > >> I guess we don't have any jdeveloper users out there. Should we
> > bring
> > > > >> it into the Maven sandbox as something available for interested
> > > > >> parties to pick up and run with if they later come along?
> > > > >>
> > > > >> - Brett
> > > > >>
> > > > >> On 28/06/2006 12:53 AM, Brett Porter wrote:
> > > > >>> This seems an ideal opportunity to do that.
> > > > >>> John Fallows, who is a regular on the maven users list, is the
> > one
> > > > >>> that wrote this code and is an apache committer via the
adffaces
> > > > >>> incubation.
> > > > >>> If we think it is a good idea to bring this over to the plugin
> > > > >>> sandbox he'd be able to help out with it (which makes more
sense
> > > > than
> > > > >>> him working on it by himself inside a jsf project :)
> > > > >>> I think what we need is someone to work with him to do what
> > Edwin
> > > > said.
> > > > >>> - Brett
> > > > >>> On 28/06/2006 12:22 AM, Edwin Punzalan wrote:
> > > > >>>>
> > > > >>>>
> > > > >>>> There are classes inside maven-eclipse-plugin which are meant
> > to be
> > > > >>>> extended/used by IDE plugins.  Is it not worthwhile to
extract
> > it
> > > > >>>> into a separate artifact first, before working on another IDE
> > > > >>>> plugin?  After that, the idea plugin should also be updated
to
> > use
> > > > it.
> > > > >>>>
> > > > >>>> Just my two cents. ^_^
> > > > >>>>
> > > > >>>>
> > > > >>>> Brett Porter wrote:
> > > > >>>>> Hi,
> > > > >>>>>
> > > > >>>>> ADFFaces in incubation has a JDeveloper plugin similar to
the
> > > > >>>>> current eclipse and idea plugins:
> > > > >>>>>
> > > > >>>>>
> > > >
http://svn.apache.org/repos/asf/incubator/adffaces/trunk/plugins/maven-jdev-plugin/
> >
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> Is anyone interested in working with this? It probably needs
> > to
> > > > >>>>> have its features aligned with the other mentioned plugins
as
> > > > well.
> > > > >>>>>
> > > > >>>>> Cheers,
> > > > >>>>> Brett
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > >
> > ---------------------------------------------------------------------
> > > > >>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > >>>> For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >>>>
> > > > >>
> > > > >>
> > > > >> --Apache Maven - http://maven.apache.org/
> > > > >> Better Builds with Maven - http://library.mergere.com/
> > > > >>
> > > > >>
> > ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > >> For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >>
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> >
> >
>


Reply via email to