Hi Anders,
Anders Hammar wrote:
> I don't necessarily want a jar. I'm just wondering if anyone have run into
> issues using either one of the approaches. I'm thinking about classpaths,
> plugins etc.
>
> The packaging type is metadata and should be correct. For the this project
> the wsdl file is the primary artifact, but if the packing says 'pom' we're
> saying that the pom is the artifact. It's not a major issue, but could
> cause some problems for tools using the metadata (like a repo manager).
>
> How do you handle your schemas. Do the artifact's version follow the
> version of the schema?
Yes. The nice thing is that after rel,ease it is possible to access it
directly from a Maven repo.
If we need the file for further processing (e.g. XMLBeans) we simply add it
to the deps and use the dependencies plugin to pull it off the repo:
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>schema</id>
<phase>initialize</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<outputDirectory>target/xsd</outputDirectory>
<overWriteReleases>false</overWriteReleases>
<overWriteSnapshots>true</overWriteSnapshots>
<includeTypes>xsd</includeTypes>
<includeScope>provided</includeScope>
</configuration>
</execution>
</executions>
</plugin>
However, as Danial said, this is fine for self-containing files and can be
difficult if is is XML and contains includes.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]