I'm not moving it to a plugin, I was going to move it to a profile. I
was testing a simple change (you can see below). Basically, 'mvn clean
install' will build everything and install it all into your ~/.m2/repo
But, if you do 'mvn -Pall,assembly clean install' it will also build the zips.
The problem Wendy is that, right now, if you do a 'mvn clean install'
from the top-level Struts 2 source directory, the assembly will use
wget on the command line to mirror the wiki. This takes a while :)
It's kind of a pain when you just want to make some incremental
changes. I haven't made any changes yet and I will make sure that the
release process remains easy, but we also need to keep development
easy too!
-Wes
patch->
Index: pom.xml
===================================================================
--- pom.xml (revision 766816)
+++ pom.xml (working copy)
@@ -62,7 +62,6 @@
<module>apps</module>
<module>plugins</module>
<module>bundles</module>
- <module>assembly</module>
</modules>
<licenses>
@@ -92,6 +91,12 @@
</modules>
</profile>
<profile>
+ <id>assembly</id>
+ <modules>
+ <module>assembly</module>
+ </modules>
+ </profile>
+ <profile>
<id>struts-annotations</id>
<modules>
<module>../maven/struts-annotations</module>
On Thu, Apr 23, 2009 at 12:32 PM, Wendy Smoak <wsm...@gmail.com> wrote:
> On Thu, Apr 23, 2009 at 5:52 AM, Wes Wannemacher <w...@wantii.com> wrote:
>
>> Unless someone can raise a decent reason not to do it, I'd like to
>> move the assembly in the struts2 build into it's own profile. I don't
>> mind Hudson and Bamboo creating the zips through the assembly module,
>> but I like to keep up-to-date and running mvn clean install -Pall on
>> my machine takes an extra ten minutes. Moving it into a profile will
>> still leave it available, but you'll have to do 'mvn -Pall,assembly
>> install' to build. 'mvn -Pall install' will build everything it builds
>> now, except the assembly.
>
> Wait! I think Musachy just spent some time rearranging things so that
> the default build does *everything* in order to make the release
> process simpler. I wasn't aware we still had the 'all' thing though.
>
> If you put the assembly back in a plugin, consider activating it on
> the absence of a property. That is, 'mvn clean install' builds
> everything, and if you *don't* want the assembly, you do something
> like mvn clean install -Dno-assembly or -Dassembly=false
>
> Ideally someone who knows Maven and is new to Struts just has to type
> "mvn clean install" and they get absolutely everything without having
> to consult the README file or know what exact incantation to invoke.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>
--
Wes Wannemacher
Author - Struts 2 In Practice
Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more
http://www.manning.com/wannemacher
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
