This sounds reasonable. Senthil, can you do that instead?
Thanks,
D
richard ratta wrote:
> How about just creating a separate build file for the maven changes
> "build-maven.xml" ?
> The build files are complicated enough and this will modularize them a
> little better.
> I would have liked to do more of this with the existing build files
> like a "build-designtime".xml
> etc., but have never had enough time to clean these files up.
>
> -rick
>
> Senthil Chidambaram wrote:
>
>> Hi,
>> Do you mind I make some build changes to push webui*.jar files to
>> maven repository. I won't touch your source code, and the target I
>> add won't be invoked at all by default, unless you invoke it
>> explicitly. I'll email the build script changes for review before I
>> check it in.
>>
>> I'll start working on this only if the woodstock team approves it,
>> because I've to checkin the repo directory at the top level of
>> woodstock src tree to hold the snapshot files before pushing it to
>> maven repository.
>>
>> P.S: I'm also looking at options to push the bits without touching
>> any of the woodstock files, which I'm successful so far. You can see
>> my test bits pushed here
>> http://download.java.net/maven/2/com/sun/woodstock/woodstock/0.1-SNAPSHOT/
>> . These bits are pushed to maven2 repo, not sure I'm still exploring
>> the differences between maven1, and maven2 repositories.
>>
>> thx
>> Senthil
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: dev-help_at_woodstock.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_woodstock.dev.java.net
> For additional commands, e-mail: dev-help_at_woodstock.dev.java.net
>