maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GregDomjan <gorf4...@gmail.com>
Subject Managing alternate source types to Java/Script/Resource across pluggins
Date Tue, 17 Jul 2012 17:02:35 GMT
I'm looking at Native compilation, particularly with NAR and want to make
some other extensions that will add sources for NAR to compile - if it is
being used already.  For instance XSD code generation like XMLBeans.

For Java the MavenProject provides access to the
CompileSourceRoots/TestCompileSourceRoots adding across plugins.

NAR also goes through these locations to potentially add files to compile (I
think it should not because it adds for all native types) 

Is there some appropriate location to do the same for Extension Plugins for
alternate file types?
I've had a look around extending MavenProject, Build/BuildOverlay and this
just doesn't seem right.

It seems like MavenProject.getBuildExtensions might be a way to go, the
other projects needing to depend on NAR seems a bit heavy at the moment.

--
View this message in context: http://maven.40175.n5.nabble.com/Managing-alternate-source-types-to-Java-Script-Resource-across-pluggins-tp5714310.html
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


Mime
View raw message