You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Don Brown <mr...@twdata.org> on 2007/12/16 12:18:14 UTC
[s2] Build changes
FYI, I'm working on the XWork and Struts 2 builds, trying to do a few things:
* Automatic deployment of xwork and struts 2 snapshots (by Bamboo)
* Automatic deployment of struts 2 assemblies (by Bamboo)
* One step creation of assemblies, including j4 backport jars
One of the stumbling points of the project right now is releases are
still not as easy as they should be and this makes it hard to get
users involved early. By automatically deploying assemblies, users
can get usable versions of the code by downloading full builds that
even include docs.
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [s2] Build changes
Posted by Don Brown <mr...@twdata.org>.
Ok, I believe I have the first cut at the assembly builds. They were
very out of date, and didn't include all the jdk14 jars, particularly
for plugins.
I'm sure there are more jars we should be bundling, so take a look.
As far as I can tell, the steps go:
mvn -Pall,j4,alljars clean install
cd assembly
mvn assembly:assembly
Don
On 12/17/07, Don Brown <mr...@twdata.org> wrote:
> On 12/17/07, Martin Gilday <ma...@imap.cc> wrote:
> > Does this include getting artifacts published to a snapshot Struts 2
> > Maven repo (i.e. not central)?
>
> Yep, and as I mentioned, I'm hoping to get the full assembly builds
> automatically published as well.
>
> Don
>
> >
> >
> > ----- Original message -----
> > From: "Don Brown" <mr...@twdata.org>
> > To: "Struts Developers List" <de...@struts.apache.org>
> > Date: Sun, 16 Dec 2007 22:18:14 +1100
> > Subject: [s2] Build changes
> >
> > FYI, I'm working on the XWork and Struts 2 builds, trying to do a few
> > things:
> > * Automatic deployment of xwork and struts 2 snapshots (by Bamboo)
> > * Automatic deployment of struts 2 assemblies (by Bamboo)
> > * One step creation of assemblies, including j4 backport jars
> >
> > One of the stumbling points of the project right now is releases are
> > still not as easy as they should be and this makes it hard to get
> > users involved early. By automatically deploying assemblies, users
> > can get usable versions of the code by downloading full builds that
> > even include docs.
> >
> > Don
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [s2] Build changes
Posted by Don Brown <mr...@twdata.org>.
On 12/17/07, Martin Gilday <ma...@imap.cc> wrote:
> Does this include getting artifacts published to a snapshot Struts 2
> Maven repo (i.e. not central)?
Yep, and as I mentioned, I'm hoping to get the full assembly builds
automatically published as well.
Don
>
>
> ----- Original message -----
> From: "Don Brown" <mr...@twdata.org>
> To: "Struts Developers List" <de...@struts.apache.org>
> Date: Sun, 16 Dec 2007 22:18:14 +1100
> Subject: [s2] Build changes
>
> FYI, I'm working on the XWork and Struts 2 builds, trying to do a few
> things:
> * Automatic deployment of xwork and struts 2 snapshots (by Bamboo)
> * Automatic deployment of struts 2 assemblies (by Bamboo)
> * One step creation of assemblies, including j4 backport jars
>
> One of the stumbling points of the project right now is releases are
> still not as easy as they should be and this makes it hard to get
> users involved early. By automatically deploying assemblies, users
> can get usable versions of the code by downloading full builds that
> even include docs.
>
> Don
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [s2] Build changes
Posted by Martin Gilday <ma...@imap.cc>.
Sounds very useful, especially for people wanting to test out the latest
2.1.x.
Does this include getting artifacts published to a snapshot Struts 2
Maven repo (i.e. not central)?
----- Original message -----
From: "Don Brown" <mr...@twdata.org>
To: "Struts Developers List" <de...@struts.apache.org>
Date: Sun, 16 Dec 2007 22:18:14 +1100
Subject: [s2] Build changes
FYI, I'm working on the XWork and Struts 2 builds, trying to do a few
things:
* Automatic deployment of xwork and struts 2 snapshots (by Bamboo)
* Automatic deployment of struts 2 assemblies (by Bamboo)
* One step creation of assemblies, including j4 backport jars
One of the stumbling points of the project right now is releases are
still not as easy as they should be and this makes it hard to get
users involved early. By automatically deploying assemblies, users
can get usable versions of the code by downloading full builds that
even include docs.
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [s2] Build changes
Posted by Antonio Petrelli <an...@gmail.com>.
2007/12/17, Don Brown <do...@gmail.com>:
>
> Yep, if you look in the OpenSymphony maven 2 repository, you'll see
> the -jdk14 jar. I closed the ticket accordingly.
Well, thank you :-)
Ciao
Antonio
Re: [s2] Build changes
Posted by Don Brown <do...@gmail.com>.
Yep, if you look in the OpenSymphony maven 2 repository, you'll see
the -jdk14 jar. I closed the ticket accordingly.
I'm working on cleaning up the assembly right now as it is rather out
of date. I'm really hoping we can use the release plugin...will make
things much easier.
Don
On Dec 17, 2007 6:52 PM, Antonio Petrelli <an...@gmail.com> wrote:
> 2007/12/16, Don Brown <mr...@twdata.org>:
> >
> > * One step creation of assemblies, including j4 backport jars
>
>
>
> This might interest you, I noticed it was not applied:
> http://jira.opensymphony.com/browse/XW-585
>
> One of the stumbling points of the project right now is releases are
> > still not as easy as they should be
>
>
>
> Did you try to use the Maven release plugin? I configured it for Struts 2
> and I hope to use it for the next Struts 2.1.x release, but the patch
> mentioned above must be resolved to work.
> BTW, I could help configuring the Maven release plugin for XWork, but I
> think I can do it only in January.
>
> Ciao
> Antonio
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [s2] Build changes
Posted by Antonio Petrelli <an...@gmail.com>.
2007/12/16, Don Brown <mr...@twdata.org>:
>
> * One step creation of assemblies, including j4 backport jars
This might interest you, I noticed it was not applied:
http://jira.opensymphony.com/browse/XW-585
One of the stumbling points of the project right now is releases are
> still not as easy as they should be
Did you try to use the Maven release plugin? I configured it for Struts 2
and I hope to use it for the next Struts 2.1.x release, but the patch
mentioned above must be resolved to work.
BTW, I could help configuring the Maven release plugin for XWork, but I
think I can do it only in January.
Ciao
Antonio