You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2006/07/14 08:21:16 UTC
[jira] Created: (WW-1378) Need a Struts release or assembly build
Need a Struts release or assembly build
---------------------------------------
Key: WW-1378
URL: http://issues.apache.org/struts/browse/WW-1378
Project: Struts 2
Type: New Feature
Reporter: Don Brown
Priority: Blocker
Fix For: 2.0.0
We need a full release or assembly build to automate the process of creating a release as much as possible.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (WW-1378) Need a Struts release or assembly build
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1378?page=all ]
Ted Husted updated WW-1378:
---------------------------
Priority: Critical (was: Blocker)
I think we are close enough now that a reasonable distribution can be cobbled together, so I am downgrading this from blocker to critical.
> Need a Struts release or assembly build
> ---------------------------------------
>
> Key: WW-1378
> URL: http://issues.apache.org/struts/browse/WW-1378
> Project: Struts 2
> Issue Type: New Feature
> Reporter: Don Brown
> Priority: Critical
> Fix For: 2.0.0
>
>
> We need a full release or assembly build to automate the process of creating a release as much as possible.
> STATUS: A preliminary buid is working but we still need to aggregate Javadocs and include a snapshot of the s2 wiki (see related tickets).
> Assembly w/o applications
> $ mvn install
> $ cd assembly
> $ mv assembly:assembly
> To include apps, use
> $ mvn install -Papps
> ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WW-1378) Need a Struts release or assembly build
Posted by "Wendy Smoak (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1378?page=comments#action_37756 ]
Wendy Smoak commented on WW-1378:
---------------------------------
Try deleting xwork from your local repository so that Maven will download new snapshots. Or, build xwork from source locally -- though a couple of tests are failing for me when I try.
> Need a Struts release or assembly build
> ---------------------------------------
>
> Key: WW-1378
> URL: http://issues.apache.org/struts/browse/WW-1378
> Project: Struts 2
> Issue Type: New Feature
> Reporter: Don Brown
> Priority: Blocker
> Fix For: 2.0.0
>
>
> We need a full release or assembly build to automate the process of creating a release as much as possible.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WW-1378) Need a Struts release or assembly build
Posted by "Wendy Smoak (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1378?page=comments#action_37873 ]
Wendy Smoak commented on WW-1378:
---------------------------------
Please try out the changes and adjust as necessary.
* The site is now copied in using relative paths. (Top level site plus api, core and extras. The sites for the example apps might need to be added.)
* The xwork javadoc comes from the -javadoc jar published in a repository (or built locally, if you prefer.)
* The xwork version is set in <dependencyManagement> in the parent pom and can be removed if it is specified anywhere else in the build.
Based on your notes, I came up with this sequence:
svn co ...
mvn install site -Papps,extras
cd assembly
mvn assembly:assembly
The files will be in target/assembly/out.
What is the ''svn export tags ...' command used for?
> Need a Struts release or assembly build
> ---------------------------------------
>
> Key: WW-1378
> URL: http://issues.apache.org/struts/browse/WW-1378
> Project: Struts 2
> Issue Type: New Feature
> Reporter: Don Brown
> Priority: Critical
> Fix For: 2.0.0
>
>
> We need a full release or assembly build to automate the process of creating a release as much as possible.
> STATUS: A preliminary buid is working but we still need to aggregate Javadocs and include a snapshot of the s2 wiki (see related tickets).
> Assembly w/o applications
> $ mvn install
> $ cd assembly
> $ mv assembly:assembly
> To include apps, use
> $ mvn install -Papps
> ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WW-1378) Need a Struts release or assembly build
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1378?page=comments#action_37817 ]
Don Brown commented on WW-1378:
-------------------------------
See also: http://confluence.twdata.org/display/WW/Building+with+Maven
> Need a Struts release or assembly build
> ---------------------------------------
>
> Key: WW-1378
> URL: http://issues.apache.org/struts/browse/WW-1378
> Project: Struts 2
> Issue Type: New Feature
> Reporter: Don Brown
> Priority: Blocker
> Fix For: 2.0.0
>
>
> We need a full release or assembly build to automate the process of creating a release as much as possible.
> STATUS: A preliminary buid is working but we still need to aggregate Javadocs and include a snapshot of the s2 wiki (see related tickets).
> Assembly w/o applications
> $ mvn install
> $ cd assembly
> $ mv assembly:assembly
> To include apps, use
> $ mvn install -Papps
> ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WW-1378) Need a Struts release or assembly build
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1378?page=all ]
Ted Husted updated WW-1378:
---------------------------
Description:
We need a full release or assembly build to automate the process of creating a release as much as possible.
STATUS: A preliminary buid is working but we still need to aggregate Javadocs and include a snapshot of the s2 wiki (see related tickets).
Assembly w/o applications
$ mvn install
$ cd assembly
$ mv assembly:assembly
To include apps, use
$ mvn install -Papps
...
was:We need a full release or assembly build to automate the process of creating a release as much as possible.
> Need a Struts release or assembly build
> ---------------------------------------
>
> Key: WW-1378
> URL: http://issues.apache.org/struts/browse/WW-1378
> Project: Struts 2
> Issue Type: New Feature
> Reporter: Don Brown
> Priority: Blocker
> Fix For: 2.0.0
>
>
> We need a full release or assembly build to automate the process of creating a release as much as possible.
> STATUS: A preliminary buid is working but we still need to aggregate Javadocs and include a snapshot of the s2 wiki (see related tickets).
> Assembly w/o applications
> $ mvn install
> $ cd assembly
> $ mv assembly:assembly
> To include apps, use
> $ mvn install -Papps
> ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (WW-1378) Need a Struts release or assembly build
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1378?page=all ]
Ted Husted resolved WW-1378.
----------------------------
Resolution: Fixed
Except for the part where we hack in a copy of the website documentation, the build seems to be working fine now.
> Need a Struts release or assembly build
> ---------------------------------------
>
> Key: WW-1378
> URL: http://issues.apache.org/struts/browse/WW-1378
> Project: Struts 2
> Issue Type: New Feature
> Reporter: Don Brown
> Priority: Critical
> Fix For: 2.0.0
>
>
> We need a full release or assembly build to automate the process of creating a release as much as possible.
> STATUS: A preliminary buid is working but we still need to aggregate Javadocs and include a snapshot of the s2 wiki (see related tickets).
> Assembly w/o applications
> $ mvn install
> $ cd assembly
> $ mv assembly:assembly
> To include apps, use
> $ mvn install -Papps
> ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WW-1378) Need a Struts release or assembly build
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1378?page=comments#action_37834 ]
Ted Husted commented on WW-1378:
--------------------------------
Fabricating a distribution
While a fully automated build is being refined, here are notes on how to patch one together (some commands may be approximate).
* Checkout and build a Struts 2 snapshot assembly
** $ svn co
** $ mvn -Pextras,apps install
** $ cd assembly
* $ mvn assembly:assembly
* Extract the all assembly
** $ unzip target/assembly/out/struts-2.0.0-SNAPSHOT-all /
* Run the site target
** $ cd ..
** $ mvn site
* Copy the site to a docs folder in the assembly
** $ copy target/site /struts-2.0.0-sNAPSHOT/docs
* Export the struts2 tags folder to the assembly
** $ svn export tags /struts-2.0.0-sNAPSHOT
* Checkout and build xwork 2 from svn
** $ svn co http://svn.opensymphony.com/svn/xwork/trunk xwork
** $ mvn install
* Create an xwork-apidocs folder
** $ mkdir /docs/work-apidocs
* Extract the xwork-javadoc.jar to the xwork-apidocs folder
** $ unzip build/xwork-javadoc.jar /struts-2.0.0-sNAPSHOT/xwork-apidocs/
* Rezip the folder as the all assembly
* Delete the other folders and create the docs assembly.
> Need a Struts release or assembly build
> ---------------------------------------
>
> Key: WW-1378
> URL: http://issues.apache.org/struts/browse/WW-1378
> Project: Struts 2
> Issue Type: New Feature
> Reporter: Don Brown
> Priority: Critical
> Fix For: 2.0.0
>
>
> We need a full release or assembly build to automate the process of creating a release as much as possible.
> STATUS: A preliminary buid is working but we still need to aggregate Javadocs and include a snapshot of the s2 wiki (see related tickets).
> Assembly w/o applications
> $ mvn install
> $ cd assembly
> $ mv assembly:assembly
> To include apps, use
> $ mvn install -Papps
> ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WW-1378) Need a Struts release or assembly build
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1378?page=comments#action_37740 ]
Ted Husted commented on WW-1378:
--------------------------------
So, with the documentation, here's the thing. One way or the other, we can export the Confluence space to HTML and integrate it with the website. There's a test export here.
* http://struts.apache.org/2.0/docs/Home.html
The formatting on the test run isn't great, but Pier's autoexport plug does a much better job. (I'd say a *stellar* job.)
Right now, the infrastructure group is suggesting that all ASF projects check the formatted websites into Subversion, to simplify disaster recovery. (This is not consider the best idea, only a prudent idea for the time being.) One upside of doing a checkin is that the checkouts can be automated, so that we don't have to visit people.apache.org to update the website. We update SVN, and a cron job updates p.a.o.
So, I wonder if we could use a website checkin as way to accomplish transfering HTML to SVN and exposing it to Maven.
>From WW-1346:
1 Autoexport Plugin outputs Confluence space to HTML at location on Confluence server (twdata.org or cwiki.apache.org)
2 Cron job on Confluence server creates/refreshes zip archive of exported HTML in a downloadable location
3 Local build assembles/copies Maven output into a uniified website (/current/docs)
4 Local build downloads HTML zip archive from Confluence server and freshens local copy of exported s2 website (/current/docs/2.0/docs).
>From here we could scp the website as we do now, or go through SVN, as infrastructure suggests.
5 Local build copies website files to current/docs
6 Committer checks in /current/docs folder to repository
7 Committer or cron job updates website from repository
The big snag in exporting HTML to the website is access. We have to be careful about giving scripts write access to p.a.o. In this scenario, it's part of the build controlled by a committer.
If we decide to try a website checkin, we could checkin the site now, including the test export of the s2 docs, and skip 4 until we have the plugin in place. (4 could even be done by a corn job on p.a.o.)
-Ted.
> Need a Struts release or assembly build
> ---------------------------------------
>
> Key: WW-1378
> URL: http://issues.apache.org/struts/browse/WW-1378
> Project: Struts 2
> Issue Type: New Feature
> Reporter: Don Brown
> Priority: Blocker
> Fix For: 2.0.0
>
>
> We need a full release or assembly build to automate the process of creating a release as much as possible.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WW-1378) Need a Struts release or assembly build
Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1378?page=comments#action_37755 ]
Ted Husted commented on WW-1378:
--------------------------------
The first time I ran this, it just worked, and I ended up with an assembly. Now, I'm getting
---.
...
C:\projects\Apache\struts-current\struts2\core\src\main\java\org\apache\struts2\
util\MergeIteratorFilter.java:[34,84] cannot find symbol
symbol: class Action
public class MergeIteratorFilter extends IteratorFilterSupport implements Iterat
or, Action {
C:\projects\Apache\struts-current\struts2\core\src\main\java\org\apache\struts2\
views\jsp\ui\DivTag.java:[22,36] package com.opensymphony.xwork2.util does not exist
C:\projects\Apache\struts-current\struts2\core\src\main\java\org\apache\struts2\
views\jsp\ComponentTagSupport.java:[21,36] package com.opensymphony.xwork2.util
does not exist
C:\projects\Apache\struts-current\struts2\core\src\main\java\org\apache\struts2\
views\jsp\StrutsBodyTagSupport.java:[22,36] package com.opensymphony.xwork2.util
does not exist
C:\projects\Apache\struts-current\struts2\core\src\main\java\org\apache\struts2\
views\jsp\ui\DivTag.java:[40,29] cannot find symbol
symbol : class OgnlValueStack
location: class org.apache.struts2.views.jsp.ui.DivTag
...
C:\projects\Apache\struts-current\struts2\core\src\main\java\org\apache\struts2\
views\jsp\BeanTag.java:[22,36] package com.opensymphony.xwork2.util does not exi
st
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: Compilation failure
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:555)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:454)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation fail
ure
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompiler
Mojo.java:505)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
... 16 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9 seconds
[INFO] Finished at: Sun Jul 16 09:48:13 EDT 2006
[INFO] Final Memory: 5M/36M
[INFO] ------------------------------------------------------------------------
> Need a Struts release or assembly build
> ---------------------------------------
>
> Key: WW-1378
> URL: http://issues.apache.org/struts/browse/WW-1378
> Project: Struts 2
> Issue Type: New Feature
> Reporter: Don Brown
> Priority: Blocker
> Fix For: 2.0.0
>
>
> We need a full release or assembly build to automate the process of creating a release as much as possible.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira