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

Doug Cutting commented on AVRO-890:
-----------------------------------

When I run 'mvn integration-test' it fails with:

[ERROR] Plugin org.apache.avro:avro-maven-plugin:1.6.0-SNAPSHOT or one of its 
dependencies could not be resolved: Could not find artifact 
org.apache.avro:avro-maven-plugin:jar:1.6.0-SNAPSHOT -> [Help 1]

But if I instead run 'mvn install' then it runs integration tests.  I generally 
don't run 'install' since I don't want to confuse myself by having working 
versions in my local maven repo.

What can I do to get the archetype tests run without installing?  I generally 
run 'mvn clean test' before each commit, and that's what the Jenkins build 
server runs after each commit, so my preference would be for the archetype code 
to be tested then too.  Is there an alternative that I should use that does not 
install artifacts in my local repo?  I tried 'verify', but it also fails with 
the above message.  Could we somehow fix things so that 'verify' works?

> 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

        

Reply via email to