Looks good to me. Only the name "archetype" should be "archetypes" because probably we will need more then one :) So i should wait a while till new folder structure will be create and move that code from the sandbox? Or someone must first check if that code is valid ?
On 6/8/07, James Mao <[EMAIL PROTECTED]> wrote:
Andrea， I agreed We should have a 'maven-plugins' top level module, and put all the maven plugins in it. I'm trying to move the wsdlgen into the codegen first. there's cycle-dependency issues. So, i would suggest have a layout like this /trunk/maven-plugins/codegen-plugin/ # include the wsdl2java and java2wsdl /trunk/maven-plugins/archetype /trunk/maven-plugins/eclipse-plugin We also have a xsd2java maven plugin, ideally this should also in maven-plugins, although it may not be in the codegen-plugin James > Tomek Sztelak wrote: > >> Hello >> I just committed maven archetype ( based on spring_http sample) to CXF >> sandbox. Since i'm new to CXF project, i want to ask for some >> guidelines on where this code should be placed in trunk tree and how >> it should be properly configured for deployment. >> >> >> Thanks. > > Hi Tomek, > > We have codegen-plugin and wsdlgen-plugin as directories in the trunk. > If I understand correctly and what a maven archetype does is generate > pom.xml and other stuff to set up a maven project, then maybe we > should have maven-support (or similar) as a top level directory > instead with wsdlgen, codegen, and archetype directories in it. > What do others think? > > Andrea. > > ---------------------------- > IONA Technologies PLC (registered in Ireland) > Registered Number: 171387 > Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland >
-- ----- When one of our products stops working, we'll blame another vendor within 24 hours.
