Thanks for the reply. When I look here ... http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle#Lifecycle_Reference
... generate-sources comes before generate-resources. Assuming I generate the wsdl during generate-resources, how do I roll back the clock to run wsdl2java? Alternatively, you say I might want these in different jars. What is the usual or best practice for placing the wsdl as such? I assume then I would have to place it in some artifact that I would have to access from the dependency plugin--my alternatives here being in an artifact by itself or with what is built from the original non-generated java. Clearly I'm a bit clueless here and will be happy to receive any advice or links. Thanks in advance! On 2/13/08, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: > deckrider wrote: > > I have a project that is being converted to maven2. > > > > It requires taking some *.java source code, requires generating a > > *.wsdl, and then from the *.wsdl generating some more java. > > > > What is the best way of doing this in maven2? > > > > Multi-module? If so, how many modules? Three? How does each module > > get deployed when I use the release plugin on the parent? > > > > Single module? What are the correct lifecycle phases? > > It could work in a single module, but the original and generated code > would end up in the same JAR which I suspect you don't want. > > The correct phases would be "generate-resources" and "generate-sources" > > -- > Trygve > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
