avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Carey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-890) Maven archetype for creating Avro service projects
Date Tue, 20 Sep 2011 22:04:08 GMT

    [ https://issues.apache.org/jira/browse/AVRO-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109021#comment-13109021

Scott Carey commented on AVRO-890:

All targets before 'install' should work without having any SNAPSHOT artifacts in your local
repo.  This ensures that all build actions occur from code in the Maven reactor, and not cached
outputs in the local repo.  If it requires "install" then the build may not be reproducible
without running 'install'.

I am not sure if it is configuration on our end, or a bug in the failsafe plugin.  Usually
these sorts of errors are plugin bugs -- plugins looking for artifacts in the local repo instead
of the maven reactor.  If it is a configuration issue, it may have something to do with <pluginManagement>
or the scoping of the avro-maven-plugin dependency.

> Maven archetype for creating Avro service projects 
> ---------------------------------------------------
>                 Key: AVRO-890
>                 URL: https://issues.apache.org/jira/browse/AVRO-890
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 1.5.4
>            Reporter: Stephen Gargan
>            Assignee: Stephen Gargan
>            Priority: Minor
>              Labels: archetype, maven
>             Fix For: 1.6.0
>         Attachments: archetypes.patch, archetypes.patch, archetypes.patch
> I've put together the beginnings of an maven archetypes subproject in the java module
to help folks kickstart avro projects. The first archetype creates a simple avro based ordering
service using the netty transport and includes an integration test for the service. The service
is very naive, though its really only the plumbing that is important and the example is illustrative
enough to get people going.
> Once built, it can be added to the local archetypes catalog via
> mvn archetype:crawl
> and then will be available via the generate plugin
> mvn archetype:generate
> or it can be invoked directly as follows
> mvn archetype:generate -DarchetypeArtifactId=avro-service-archetype -DarchetypeGroupId=org.apache.avro
-DgroupId=org.simple -DartifactId=simple-service -Dversion=1.0-SNAPSHOT   
> The parent pom contains common config for generating a pom for the archetype that references
the current avro build version. This takes some slight of hand with maven resources to insert
the version and will be reusable for other archetypes in the future.
> I intend putting together a map-reduce archetype soon and am open to suggestions for
other archetypes that might be useful. Perhaps one that included the code from AVRO-883 to
kick start a basic serialization project?  

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message