Hi,
If you are using assembly pluging to build the distribution, try this in
your assembly xml,
...
<dependencySet>
<outputFileNameMapping>${artifactId}.SNPAHOT.${extension}</outputFileNameMapping>
<outputDirectory>/lib</outputDirectory>
<includes>
<include>*:SNAPSHOT:jar:*</include>
</includes>
</dependencySet>
...
Above is just a temporally solution, but I think you get the idea. You need
the latest assembly pluging to do the prior. Try version 2.2-beta-1 and
above.
Thank you
Saminda
On 8/27/07, Lahiru Sandakith <[EMAIL PROTECTED]> wrote:
>
> Hi devs,
> When we have SNAPSHOT dependencies for a particular module, maven2 on line
> build include them in to the module dependencies with a date suffix. What we
> need is when we do nightly builds maven2 should rename that to SNAPSHOT and
> include that in to the nightly builds. For example In order for the eclipse
> plugins nightly builds to work we have to have the exact 3rd party library
> name to elcipse framework to load it through the plugin.xml. (There is no
> question about releases , since we are not going with SNAPSHOTs)
> Is there a way that we can have renamed SNAPSHOT included in the builds.
> (AFAIK maven2 get the latest from the repos and rename that to SNAPSHOT in
> local)
> For example We have the neethi dependency in the eclipse plugin pom.xml as
>
> <dependency>
> <groupId>org.apache.neethi</groupId>
> <artifactId>neethi</artifactId>
> <version>${neethi.version}</version>
> </dependency>
> the version coming from the parent which is SNAPSHOT. Problem comes when
> there is a new neethi nightly build available in the repos compare to my
> local machine, the build include it as neethi-20070825.224622-550.jar not
> as neethi-SNAPSHOT.jar with the on-line build.
> --
> Thanks
> Lahiru Sandakith
>
> http://sandakith.wordpress.com/
> GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
--
Saminda Abeyruwan
Software Engineer
WSO2 Inc. - www.wso2.org
