avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Gargan <steve.gar...@gmail.com>
Subject Re: [jira] [Commented] (AVRO-890) Maven archetype for creating Avro service projects
Date Wed, 21 Sep 2011 21:55:54 GMT
The only issue with pointing it at a released plugin is that the generated
samples would not then reference the most recent build; projects generated
with the 1.6.0 archetype would generate a project referencing a 1.5.X
plugin. I completely agree that having a separate release cycle just for
this would be troublesome.

As a suggestion, I could try to veto the integration testing as part of the
normal build and separate it into a profile. The profile could be run during
development but otherwise be omitted from builds. It would remove the
independent verification you get from the continuous integration, but it
might be acceptable in this situation as the sample projects are pretty

How do you feel about this?

On Wed, Sep 21, 2011 at 9:45 PM, Scott Carey (JIRA) <jira@apache.org> wrote:

>    [
> https://issues.apache.org/jira/browse/AVRO-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109861#comment-13109861]
> Scott Carey commented on AVRO-890:
> ----------------------------------
> For a released artifact, this is not a problem.  The archetype will work
> fine because it won't point to a SNAPSHOT.
> In the case of testing the archetype then, it either needs to point to a
> released version, or we must install avro-maven-plugin before the archetype
> plugin forks the build.
> Or we could release it and version the archetype separately from the main
> project, but that has many other serious drawbacks.
> > 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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message