Thanks!

Jörg's approach is what I was thinking of. The only drawback is
bad/incorrect metadata (pom packaging). That could be fixed though.
The nice thing is that this would also work great with a ws registry
containing wsdl files, which could quite easily be proxied by a repo manager
as a maven repo.

Any drawback not packing it as a jar that someone could think of?

/Anders

On Wed, Sep 15, 2010 at 12:31, Jörg Schaible <joerg.schai...@gmx.de> wrote:

> Hi ANders
>
> Anders Hammar wrote:
>
> > How do people manage wsdl files in their repo. Do you manage them in a
> jar
> > artifact or any other way?
>
> Use the build-helper plugin. We manage xsd files as artifacts:
>
> ========== %< ==============
>  <plugin>
>  <groupId>org.codehaus.mojo</groupId>
>  <artifactId>build-helper-maven-plugin</artifactId>
>  <executions>
>   <execution>
>    <id>xml-schema</id>
>    <goals>
>     <goal>attach-artifact</goal>
>    </goals>
>    <configuration>
>     <artifacts>
>      <artifact>
>       <file>src/main/schema/UserGroup.xsd</file>
>       <type>xsd</type>
>      </artifact>
>     </artifacts>
>    </configuration>
>   </execution>
>  </executions>
>  </plugin>
> ========== %< ==============
>
> The packaging type of the project is "pom". We can reference the xsd
> artifact later as normal dependency with type xsd.
>
> Hope this helps,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Reply via email to