One of the best thing about Java mojos too, is that as long as you
don't tie it to any M2 APIs (or are prepared to translate the
resulting objects), you can also wrap them in a thin Jelly plugin for
use in Maven 1 and maintain one codebase. We'll be moving more of the
Maven1 plugins towards this model as the M2 plugins mature.

- Brett

On 6/14/05, dan tran <[EMAIL PROTECTED]> wrote:
> I may be wrong, but i think the reason of cpptasks is not maintainable because
> it tries to know too much.  If I am going to convert it to M2 mojo, i will 
> just
> try to make it to replace 'make' functionality and leave the
> compiler and linker settings to the user.
> 
> After that, we may have ton of independent add-ins (MOJO) for compiler
> specifics.
> 
> thoughts?
> 
> -D
> 
> On 6/14/05, Donszelmann, Mark <[EMAIL PROTECTED]> wrote:
> > Dan (and others),
> >
> > a port to M2, whenever we migrate to it. This all depends on how stable and
> > goo M2 is. Have not investigated yet. The current NAR plugin could do with
> > some improvements. The jelly script is around 50 Kbytes, and could be more
> > easily written in Java. There are a lot of properties used, of which I have
> > no idea where they go in M2.
> >
> > I did make my own improvements to cpptasks, and reported some of them:
> > new compilers, some options changed, etc. The cpptasks system is usable
> > and quite ok I think, just not maintained (very well).
> >
> > Let me know.
> >
> > Mark
> >
> > -----Original Message-----
> > From: dan tran [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, June 14, 2005 12:05 AM
> > To: Maven Users List
> > Subject: Re: Native dependencies
> >
> > Mark, Do you plan to port your plugin to M2?
> >
> > I think cpp-task is basically dead, I ended up to maintain cpptask with my 
> > own changes to support more option.  Perhaps we can team up to merge 
> > cpptask into M2 mojo
> >
> > -D
> >
> > On 6/13/05, Donszelmann, Mark <[EMAIL PROTECTED]> wrote:
> > > Hi
> > >
> > > we found the maven-native-plugin limited in its functionality,
> > > especially where it concerns:
> > >
> > > 1. true cross-platform development
> > > 2. declaring dependencies on other native libraries
> > >
> > > so, we developed our own. Feel free to have a look, and use it:
> > >
> > > http://java.freehep.org/freehep-nar-plugin
> > >
> > > builds, unpacks and distributes Native Archives.
> > >
> > > Its not complete, see the issues in JIRA, but we are getting there.
> > >
> > > Regards
> > > Mark Donszelmann
> > >
> > >
> > > -----Original Message-----
> > > From: dan tran [mailto:[EMAIL PROTECTED]
> > > Sent: Monday, June 13, 2005 2:07 PM
> > > To: Maven Users List
> > > Subject: Re: Native dependencies
> > >
> > > In case you are going to build native code, take a look at
> > > maven-native-plugin
> > >
> > > -D
> > >
> > > On 6/13/05, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> > > > Will give it a try.  I am targeting Windows and *nix.
> > > >
> > > > Am new to Maven, so will have to go figure out the pregoal stuff
> > > > (ironically, I was just looking into that for something else!)
> > > >
> > > > >>> [EMAIL PROTECTED] 6/13/2005 3:44:55 PM >>>
> > > > - put the native files under your local repo
> > > > - add them to your dependencies list
> > > >
> > > > At run time system use pregoal to add the native files to a
> > > > localtion understand by your system, ORuse some sort of environment
> > > > valiable to add your file to linkage path
> > > >
> > > > What OS are you targeting?
> > > >
> > > > -D
> > > >
> > > >
> > > >
> > > > On 6/13/05, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> > > > > Hi,
> > > > >
> > > > > I have a 3rd party JAR that requires a native library.  How do I
> > > > > specify the dependency such that the native library gets put in a
> > > > place
> > > > > where I can link with it at runtime?
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Grant Ingersoll
> > > > >
> > > > >
> > > > --------------------------------------------------------------------
> > > > -
> > > > > 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]
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > 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]
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to