[jira] Updated: (SHALE-281) Eliminate direct dependencies on Commons Logging

[Wendy Smoak (JIRA)]

 [ 
https://issues.apache.org/struts/browse/SHALE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wendy Smoak updated SHALE-281:
--

Comment: was deleted

> Eliminate direct dependencies on Commons Logging
> 
>
> Key: SHALE-281
> URL: https://issues.apache.org/struts/browse/SHALE-281
> Project: Shale
>  Issue Type: Task
>  Components: Clay, Core, Dialog, Remoting, Sandbox, Spring, Test, 
> Tiger, Tiles
>Reporter: Craig McClanahan
> Fix For: TBD
>
>
> Since we depend on JDK 1.4 or later anyway, and since the logging 
> requirements of the framework itself are minial, update the framework classes 
> from dependency on Commons Logging to use JDK 1.4 logging instead.  This does 
> not necessarily need to apply to example applications.  The focus is on 
> minimizing dependencies for the framework itself.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SHALE-446) Build fails on virgin system because the Cobertura version need to be set in pom.xml

[Wendy Smoak (JIRA)]

[ 
https://issues.apache.org/struts/browse/SHALE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41202
 ] 

Wendy Smoak commented on SHALE-446:
---

Actually, we should add version numbers for all plugins.

See 
http://www.nabble.com/-IMPORTANT--Maven-2-Plugin-Auto-Versioning-Considered-Dangerous-t3560426s177.html



> Build fails on virgin system because the Cobertura version need to be set in 
> pom.xml
> 
>
> Key: SHALE-446
> URL: https://issues.apache.org/struts/browse/SHALE-446
> Project: Shale
>  Issue Type: Bug
>Affects Versions: 1.1.0-SNAPSHOT
>Reporter: Paul Spencer
> Attachments: shale-446.patch
>
>
> Building Shale on a system for the first time will fail because the Cobertura 
> plugin was not found.  Adding a version number resolves the problem. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SHALE-444) Eclipse Plugin

[Wendy Smoak (JIRA)]

[ 
https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40969
 ] 

Wendy Smoak commented on SHALE-444:
---

Thanks, Ryan!

Because this is "a substantial contribution that was not developed within the 
ASF's source control system and on our public mailing lists," it will need to 
go through the Incubator IP clearance process, as described here:  
http://incubator.apache.org/ip-clearance/index.html

A quick read through indicates that we need two more things from Ryan...
  1) a checksum (md5 hash) for the zip file
  2) a software grant - http://www.apache.org/licenses/software-grant.txt

There were license headers on the few files I looked at, and Ryan already has 
an iCLA on file.



> Eclipse Plugin
> --
>
> Key: SHALE-444
> URL: https://issues.apache.org/struts/browse/SHALE-444
> Project: Shale
>  Issue Type: New Feature
>  Components: Clay
> Environment: Any environment supported by Eclipse
>Reporter: Ryan Wynn
> Attachments: shale-clay-plugin-src.zip
>
>
> Provide a clay plugin for eclipse.  Create a visual editor targeted towards 
> creating/maintaining clay component metadata.  Support autodetection of clay 
> component definitions in the workspace.  Allow component extension through 
> drag and drop from a component palette.  Provide autocompletion of managed 
> bean names and methods.  Support both visual and text modes.
>   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SHALE-188) Add a default outcome to the dialog manager

[Wendy Smoak (JIRA)]

 [ 
http://issues.apache.org/struts/browse/SHALE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wendy Smoak updated SHALE-188:
--

Comment: was deleted

> Add a default outcome to the dialog manager
> ---
>
> Key: SHALE-188
> URL: http://issues.apache.org/struts/browse/SHALE-188
> Project: Shale
>  Issue Type: Improvement
>  Components: Dialog
> Environment: Debian Linux - JDK 1.5
>Reporter: Laure Goudon
> Fix For: 1.0.4-SNAPSHOT
>
>
> Version from manifest: Implementation-Version: 20060326
> Hello,
> When we click on the browser back button while in a dialog and then click on 
> another link or button, an Illegal argument exception comes (see stacktrace). 
> This error occurs because Shale can't find any transition for this action. It 
> would be a good idea that we could have a default transition (for instance 
> named "*" or "default") that the dialog navigation handler class would use if 
> no other transition was found for this state or dialog.
> Thanks.
> stacktrace :
> java.lang.IllegalArgumentException: You have requested a transition outcome 
> named "clusterMenu" from a state named "viewApplicationView" in a dialog 
> named "viewApplication", but no transition definition can be found.  Double 
> check the spelling of the transition outcome name.
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.transition(DialogNavigationHandler.java:526)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.postprocess(DialogNavigationHandler.java:353)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.handleNavigation(DialogNavigationHandler.java:219)
>   at 
> org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:84)
>   at javax.faces.component.UICommand.broadcast(UICommand.java:106)
>   at 
> org.apache.myfaces.custom.navmenu.htmlnavmenu.HtmlCommandNavigationItem.broadcast(HtmlCommandNavigationItem.java:228)
> Proposed solution :
> In the class DialogNavigationHandler in the method transition
>   /** Default outcome name constant as in :
>*  
>*/
>   public static final String DEFAULT_OUTCOME_NAME = "*";
> // Identify the appropriate Transition
> Transition transition = state.findTransition(outcome);
> if (transition == null) {
> transition = state.getDialog().findTransition(outcome);
> //  Begin patch 
> // If not found, check the default outcome for the current state
>   if (transition == null) {
>Transition transition = state.findTransition(outcome);
>// If not found, check the default outcome for the current dialog.
>if (transition == null) {
>  transition = 
> state.getDialog().findTransition(DEFAULT_OUTCOME_NAME);
>}
> }
> //  End patch 
> }
>   if (transition == null) {
> throw new 
> IllegalArgumentException(messages.getMessage("dialog.noTransition",
>new Object[] { outcome,
>   state.getName(),
>   
> state.getDialog().getName() }));
> }

-- 
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: (SHALE-188) Add a default outcome to the dialog manager

[Wendy Smoak (JIRA)]

 [ 
http://issues.apache.org/struts/browse/SHALE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wendy Smoak updated SHALE-188:
--

Comment: was deleted

> Add a default outcome to the dialog manager
> ---
>
> Key: SHALE-188
> URL: http://issues.apache.org/struts/browse/SHALE-188
> Project: Shale
>  Issue Type: Improvement
>  Components: Dialog
> Environment: Debian Linux - JDK 1.5
>Reporter: Laure Goudon
> Fix For: 1.0.4-SNAPSHOT
>
>
> Version from manifest: Implementation-Version: 20060326
> Hello,
> When we click on the browser back button while in a dialog and then click on 
> another link or button, an Illegal argument exception comes (see stacktrace). 
> This error occurs because Shale can't find any transition for this action. It 
> would be a good idea that we could have a default transition (for instance 
> named "*" or "default") that the dialog navigation handler class would use if 
> no other transition was found for this state or dialog.
> Thanks.
> stacktrace :
> java.lang.IllegalArgumentException: You have requested a transition outcome 
> named "clusterMenu" from a state named "viewApplicationView" in a dialog 
> named "viewApplication", but no transition definition can be found.  Double 
> check the spelling of the transition outcome name.
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.transition(DialogNavigationHandler.java:526)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.postprocess(DialogNavigationHandler.java:353)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.handleNavigation(DialogNavigationHandler.java:219)
>   at 
> org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:84)
>   at javax.faces.component.UICommand.broadcast(UICommand.java:106)
>   at 
> org.apache.myfaces.custom.navmenu.htmlnavmenu.HtmlCommandNavigationItem.broadcast(HtmlCommandNavigationItem.java:228)
> Proposed solution :
> In the class DialogNavigationHandler in the method transition
>   /** Default outcome name constant as in :
>*  
>*/
>   public static final String DEFAULT_OUTCOME_NAME = "*";
> // Identify the appropriate Transition
> Transition transition = state.findTransition(outcome);
> if (transition == null) {
> transition = state.getDialog().findTransition(outcome);
> //  Begin patch 
> // If not found, check the default outcome for the current state
>   if (transition == null) {
>Transition transition = state.findTransition(outcome);
>// If not found, check the default outcome for the current dialog.
>if (transition == null) {
>  transition = 
> state.getDialog().findTransition(DEFAULT_OUTCOME_NAME);
>}
> }
> //  End patch 
> }
>   if (transition == null) {
> throw new 
> IllegalArgumentException(messages.getMessage("dialog.noTransition",
>new Object[] { outcome,
>   state.getName(),
>   
> state.getDialog().getName() }));
> }

-- 
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: (SHALE-188) Add a default outcome to the dialog manager

[Wendy Smoak (JIRA)]

 [ 
http://issues.apache.org/struts/browse/SHALE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wendy Smoak updated SHALE-188:
--

Comment: was deleted

> Add a default outcome to the dialog manager
> ---
>
> Key: SHALE-188
> URL: http://issues.apache.org/struts/browse/SHALE-188
> Project: Shale
>  Issue Type: Improvement
>  Components: Dialog
> Environment: Debian Linux - JDK 1.5
>Reporter: Laure Goudon
> Fix For: 1.0.4-SNAPSHOT
>
>
> Version from manifest: Implementation-Version: 20060326
> Hello,
> When we click on the browser back button while in a dialog and then click on 
> another link or button, an Illegal argument exception comes (see stacktrace). 
> This error occurs because Shale can't find any transition for this action. It 
> would be a good idea that we could have a default transition (for instance 
> named "*" or "default") that the dialog navigation handler class would use if 
> no other transition was found for this state or dialog.
> Thanks.
> stacktrace :
> java.lang.IllegalArgumentException: You have requested a transition outcome 
> named "clusterMenu" from a state named "viewApplicationView" in a dialog 
> named "viewApplication", but no transition definition can be found.  Double 
> check the spelling of the transition outcome name.
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.transition(DialogNavigationHandler.java:526)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.postprocess(DialogNavigationHandler.java:353)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.handleNavigation(DialogNavigationHandler.java:219)
>   at 
> org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:84)
>   at javax.faces.component.UICommand.broadcast(UICommand.java:106)
>   at 
> org.apache.myfaces.custom.navmenu.htmlnavmenu.HtmlCommandNavigationItem.broadcast(HtmlCommandNavigationItem.java:228)
> Proposed solution :
> In the class DialogNavigationHandler in the method transition
>   /** Default outcome name constant as in :
>*  
>*/
>   public static final String DEFAULT_OUTCOME_NAME = "*";
> // Identify the appropriate Transition
> Transition transition = state.findTransition(outcome);
> if (transition == null) {
> transition = state.getDialog().findTransition(outcome);
> //  Begin patch 
> // If not found, check the default outcome for the current state
>   if (transition == null) {
>Transition transition = state.findTransition(outcome);
>// If not found, check the default outcome for the current dialog.
>if (transition == null) {
>  transition = 
> state.getDialog().findTransition(DEFAULT_OUTCOME_NAME);
>}
> }
> //  End patch 
> }
>   if (transition == null) {
> throw new 
> IllegalArgumentException(messages.getMessage("dialog.noTransition",
>new Object[] { outcome,
>   state.getName(),
>   
> state.getDialog().getName() }));
> }

-- 
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: (SHALE-188) Add a default outcome to the dialog manager

[Wendy Smoak (JIRA)]

 [ 
http://issues.apache.org/struts/browse/SHALE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wendy Smoak updated SHALE-188:
--

Comment: was deleted

> Add a default outcome to the dialog manager
> ---
>
> Key: SHALE-188
> URL: http://issues.apache.org/struts/browse/SHALE-188
> Project: Shale
>  Issue Type: Improvement
>  Components: Dialog
> Environment: Debian Linux - JDK 1.5
>Reporter: Laure Goudon
> Fix For: 1.0.4-SNAPSHOT
>
>
> Version from manifest: Implementation-Version: 20060326
> Hello,
> When we click on the browser back button while in a dialog and then click on 
> another link or button, an Illegal argument exception comes (see stacktrace). 
> This error occurs because Shale can't find any transition for this action. It 
> would be a good idea that we could have a default transition (for instance 
> named "*" or "default") that the dialog navigation handler class would use if 
> no other transition was found for this state or dialog.
> Thanks.
> stacktrace :
> java.lang.IllegalArgumentException: You have requested a transition outcome 
> named "clusterMenu" from a state named "viewApplicationView" in a dialog 
> named "viewApplication", but no transition definition can be found.  Double 
> check the spelling of the transition outcome name.
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.transition(DialogNavigationHandler.java:526)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.postprocess(DialogNavigationHandler.java:353)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.handleNavigation(DialogNavigationHandler.java:219)
>   at 
> org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:84)
>   at javax.faces.component.UICommand.broadcast(UICommand.java:106)
>   at 
> org.apache.myfaces.custom.navmenu.htmlnavmenu.HtmlCommandNavigationItem.broadcast(HtmlCommandNavigationItem.java:228)
> Proposed solution :
> In the class DialogNavigationHandler in the method transition
>   /** Default outcome name constant as in :
>*  
>*/
>   public static final String DEFAULT_OUTCOME_NAME = "*";
> // Identify the appropriate Transition
> Transition transition = state.findTransition(outcome);
> if (transition == null) {
> transition = state.getDialog().findTransition(outcome);
> //  Begin patch 
> // If not found, check the default outcome for the current state
>   if (transition == null) {
>Transition transition = state.findTransition(outcome);
>// If not found, check the default outcome for the current dialog.
>if (transition == null) {
>  transition = 
> state.getDialog().findTransition(DEFAULT_OUTCOME_NAME);
>}
> }
> //  End patch 
> }
>   if (transition == null) {
> throw new 
> IllegalArgumentException(messages.getMessage("dialog.noTransition",
>new Object[] { outcome,
>   state.getName(),
>   
> state.getDialog().getName() }));
> }

-- 
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: (SHALE-188) Add a default outcome to the dialog manager

[Wendy Smoak (JIRA)]

 [ 
http://issues.apache.org/struts/browse/SHALE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wendy Smoak updated SHALE-188:
--

Comment: was deleted

> Add a default outcome to the dialog manager
> ---
>
> Key: SHALE-188
> URL: http://issues.apache.org/struts/browse/SHALE-188
> Project: Shale
>  Issue Type: Improvement
>  Components: Dialog
> Environment: Debian Linux - JDK 1.5
>Reporter: Laure Goudon
> Fix For: 1.0.4-SNAPSHOT
>
>
> Version from manifest: Implementation-Version: 20060326
> Hello,
> When we click on the browser back button while in a dialog and then click on 
> another link or button, an Illegal argument exception comes (see stacktrace). 
> This error occurs because Shale can't find any transition for this action. It 
> would be a good idea that we could have a default transition (for instance 
> named "*" or "default") that the dialog navigation handler class would use if 
> no other transition was found for this state or dialog.
> Thanks.
> stacktrace :
> java.lang.IllegalArgumentException: You have requested a transition outcome 
> named "clusterMenu" from a state named "viewApplicationView" in a dialog 
> named "viewApplication", but no transition definition can be found.  Double 
> check the spelling of the transition outcome name.
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.transition(DialogNavigationHandler.java:526)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.postprocess(DialogNavigationHandler.java:353)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.handleNavigation(DialogNavigationHandler.java:219)
>   at 
> org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:84)
>   at javax.faces.component.UICommand.broadcast(UICommand.java:106)
>   at 
> org.apache.myfaces.custom.navmenu.htmlnavmenu.HtmlCommandNavigationItem.broadcast(HtmlCommandNavigationItem.java:228)
> Proposed solution :
> In the class DialogNavigationHandler in the method transition
>   /** Default outcome name constant as in :
>*  
>*/
>   public static final String DEFAULT_OUTCOME_NAME = "*";
> // Identify the appropriate Transition
> Transition transition = state.findTransition(outcome);
> if (transition == null) {
> transition = state.getDialog().findTransition(outcome);
> //  Begin patch 
> // If not found, check the default outcome for the current state
>   if (transition == null) {
>Transition transition = state.findTransition(outcome);
>// If not found, check the default outcome for the current dialog.
>if (transition == null) {
>  transition = 
> state.getDialog().findTransition(DEFAULT_OUTCOME_NAME);
>}
> }
> //  End patch 
> }
>   if (transition == null) {
> throw new 
> IllegalArgumentException(messages.getMessage("dialog.noTransition",
>new Object[] { outcome,
>   state.getName(),
>   
> state.getDialog().getName() }));
> }

-- 
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: (SHALE-375) Framework should build on JDK 1.4

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-375?page=comments#action_39172 ] 

Wendy Smoak commented on SHALE-375:
---

The build itself (not the Shale code) may require JDK 1.5.  At one point the 
taglib plugin would not work on JDK 1.4.  I'm not sure if it's been released 
since this was fixed.

   
http://sourceforge.net/tracker/index.php?func=detail&aid=1483561&group_id=93991&atid=606303

The compiler plugin is configured to target 1.4 (except for a few modules) so 
it should be fine in any case.

> Framework should build on JDK 1.4
> -
>
> Key: SHALE-375
> URL: http://issues.apache.org/struts/browse/SHALE-375
> Project: Shale
>  Issue Type: Bug
>Reporter: Rahul Akolkar
> Assigned To: Rahul Akolkar
> Fix For: 1.0.4-SNAPSHOT
>
>
> 'mvn -Papps install' on JDK 1.4 should result in a successful build.

-- 
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] Created: (SHALE-363) Review dependency and plugin version numbers

[Wendy Smoak (JIRA)]

Review dependency and plugin version numbers


 Key: SHALE-363
 URL: http://issues.apache.org/struts/browse/SHALE-363
 Project: Shale
  Issue Type: Task
Affects Versions: 1.0.4-SNAPSHOT
Reporter: Wendy Smoak
 Fix For: 1.0.4-SNAPSHOT


Review version numbers for all dependencies and plugins.  Eliminate snapshots, 
use latest release where appropriate, etc.

-- 
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: (SHALE-243) Use Selenium for functional testing of the example apps

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-243?page=all ]

Wendy Smoak resolved SHALE-243.
---

Resolution: Fixed

Resolving as the Selenium test for the mailreader app is working for me, and 
the infrastructure is in place to add Selenium tests to any of the other apps.  
(Just add files in src/test/selenium and package with the 'selenium' profile 
activated: -P selenium .)



> Use Selenium for functional testing of the example apps
> ---
>
> Key: SHALE-243
> URL: http://issues.apache.org/struts/browse/SHALE-243
> Project: Shale
>  Issue Type: Improvement
>  Components: Examples
>Affects Versions: 1.0.3-SNAPSHOT
>Reporter: Wendy Smoak
>Priority: Minor
> Fix For: 1.0.4-SNAPSHOT
>
> Attachments: SHALE-243-wsmoak.diff
>
>
> Use Selenium from OpenQA to verify that the example apps work properly.

-- 
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: (SHALE-220) init() lifecycle method called twice

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-220?page=all ]

Wendy Smoak updated SHALE-220:
--

Comment: was deleted

> init() lifecycle method called twice
> 
>
> Key: SHALE-220
> URL: http://issues.apache.org/struts/browse/SHALE-220
> Project: Shale
>  Issue Type: Bug
>  Components: View
>Affects Versions: 1.0.2, 1.0.3
>Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
> Fix For: 1.0.4-SNAPSHOT
>
>
> From a user mailing list posting by Viswanath , 
> following up on earlier mailing list conversations:
> ==
> Hi Craig,
> Now that I have subscribed to Shale user group, I am posting this issue again.
> Just to make sure that I am not using older version of Shale libraries, I 
> have downloaded shale-framework-20060713.zip and tried, same problem. This is 
> what I did,  to reproduce the issue in usecases project. ( I am not able to 
> post code from my project because of lot of dependencies on EJBs/Database)
> I downloaded the latest usecases zip (07/14/2006). Unzipped the war file into 
> a directory, created a project in eclipse, added the java source files,  
> built and deployed it into JBOSS and it ran fine.  Added the following code 
> at the end of  org/apache/shale/usecases/locale/Select.java overriding the 
> "do-nothing" init() from ActionViewController.
>public void init()
>{
> System.out.println("Select.java - Init - PostBack Value: " + 
> Boolean.toString(isPostBack()));
>}
> redeployed and ran. The console output when I click on "Select Language" link
> 15:20:27,515 INFO  [STDOUT] Select.java - Init - PostBack Value: false
> 15:20:27,515 INFO  [STDOUT] Select.java - Init - PostBack Value: false
> and on sumbit (when I click on "Go" )
> 15:20:33,546 INFO  [STDOUT] Select.java - Init - PostBack Value: false
> 15:20:33,562 INFO  [STDOUT] Select.java - Init - PostBack Value: true
> My environment is :
> OS : Windows XP Home
> JBOSS 4.0.4 Patch1 with Tomcat 5.5
> JRE : 1.5.0_06
> Eclipse 3.1.1
> Thanks
> Vish
> ==
> I was able to reproduce this with latest trunk bits, using the default 
> testing configuration (MyFaces, Tomcat 5.5).  It's clearly a bug in how init 
> and destroy method callbacks are being triggered for view controllers, most 
> likely related to the fact that the mechanism for this was recently changed.

-- 
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: (SHALE-323) Wrong output directoryname in shale-archetype-blank pom

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-323?page=comments#action_38666 ] 

Wendy Smoak commented on SHALE-323:
---

As far as I can tell, ${project.build.directory} is a valid property, and it 
works.  It's listed in the properties guide [1] and that same configuration is 
in use in multiple poms to copy the Selenium code into various example apps.

Hermod, let me know if the pom configuration is not working (not copying the 
files) otherwise I'm inclined to close this as won't fix.

[1] http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide



> Wrong output directoryname in shale-archetype-blank pom
> ---
>
> Key: SHALE-323
> URL: http://issues.apache.org/struts/browse/SHALE-323
> Project: Shale
>  Issue Type: Bug
>Affects Versions: 1.0.3
>Reporter: Hermod Opstvedt
>
> In the shale-archetype-blank pom (under archetype-resources)  the wrong maven 
> output directory name has been used. Below is the patch
> Index: pom.xml
> ===
> --- pom.xml   (revisjon 469786)
> +++ pom.xml   (arbeidskopi)
> @@ -72,7 +72,7 @@
> c:/java/apache-tomcat-5.5.17
> 
> target/tomcat5x.log
> target/tomcat5x.out
> @@ -128,7 +128,7 @@
>  0.7.0
>  
>  
> -
> ${project.build.directory}/selenium
> +
> ${project.build.outputDirectory}/selenium
>  
>  
>  
> @@ -141,10 +141,10 @@
>  process-resources
>  
>  
> - todir="${project.build.directory}/${artifactId}/selenium/core">
> - dir="${project.build.directory}/selenium/core"/>
> + todir="${project.build.outputDirectory}/${artifactId}/selenium/core">
> + dir="${project.build.outputDirectory}/selenium/core"/>
>  
> - todir="${project.build.directory}/${artifactId}/selenium/tests">
> + todir="${project.build.outputDirectory}/${artifactId}/selenium/tests">
>   dir="src/test/selenium"/>
>  
>  

-- 
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: (SHALE-22) Change Log and Developer Activity reports are blank

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-22?page=all ]

Wendy Smoak resolved SHALE-22.
--

Resolution: Not A Problem

This is related to the Maven 1 build and is no longer relevant.

> Change Log and Developer Activity reports are blank
> ---
>
> Key: SHALE-22
> URL: http://issues.apache.org/struts/browse/SHALE-22
> Project: Shale
>  Issue Type: Bug
>  Components: Website
> Environment: Operating System: other
> Platform: Other
>Reporter: Wendy Smoak
>
> The Maven-generated Change Log and Developer Activity reports show no 
> activity.
> This has worked in the past, see the docs for Struts EL 1.3.0 published on
> 2006-02-17: http://struts.apache.org/struts-el/changelog-report.html
> $ maven site
> ...
> [echo] Generating the Change Log...
> maven-changelog-plugin:report:
> [echo] Generating the changelog report
> SCM Working Directory: e:\svn\struts\STRUTS_ACTION_1_3_1
> SCM Command Line[0]: svn
> SCM Command Line[1]: log
> SCM Command Line[2]: -v
> SCM Command Line[3]: -r{2006-03-13}:{2005-11-12}
> svn: Syntax error in revision argument '2006-03-13:2005-11-12'
> ChangeLog found: 0 entries
> [echo] Generating the Developer Activity...
> maven-developer-activity-plugin:report:
> [echo] Generating the developer activity report

-- 
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: (SHALE-230) Restore publishing the dialog-config_1.0.dtd file (and any other DTDs defined by Shale)

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-230?page=all ]

Wendy Smoak resolved SHALE-230.
---

Fix Version/s: 1.0.4-SNAPSHOT
   Resolution: Fixed

> Restore publishing the dialog-config_1.0.dtd file (and any other DTDs defined 
> by Shale)
> ---
>
> Key: SHALE-230
> URL: http://issues.apache.org/struts/browse/SHALE-230
> Project: Shale
>  Issue Type: Bug
>  Components: Website
>Affects Versions: 1.0.2
>Reporter: Craig McClanahan
> Assigned To: Wendy Smoak
> Fix For: 1.0.4-SNAPSHOT
>
>
> As part of our transition to the shale.apache.org website, it appears that 
> publishing the DTD for dialog configuration (to subdirectory "dtds" on the 
> website) got inadvertently dropped.  It needs to be restored to the build 
> process.

-- 
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: (SHALE-319) Shale-Parent--pom contains repositories

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-319?page=all ]

Wendy Smoak resolved SHALE-319.
---

Resolution: Fixed

> Shale-Parent--pom contains repositories
> ---
>
> Key: SHALE-319
> URL: http://issues.apache.org/struts/browse/SHALE-319
> Project: Shale
>  Issue Type: Bug
> Environment: behind a firewall / proxy
>Reporter: Matthias Wessendorf
> Assigned To: Matthias Wessendorf
> Fix For: 1.0.4-SNAPSHOT
>
>
> The "parent pom" in Shale has an "abuse" of . It
> specifies two repositories inside the  xml element. IMO
> this should be handled by the user's settings.xml file and not by a
> lib.
> So, if you are behind a proxy, a corp.-m2-mirrow and a
> corp-own-m2-repo, you can't build stuff which uses Shale. (This
> envoironment is sorta production like.)
> Why can't you build the stuff?
> Because maven sees only (to fetch Shale dependencies) these two repos:
> -Apache M2 Snapshot
> -Java.net
> So it tries to download apache2-pom from these... it doesn't look in
> other repos.
> (currently the apache m2 snapshot repo is down... so it doesn't get
> Shale-master too,
> which is! available within a regular m2 repo)
> Our work around, we changed the shale-parent-pom in our corp. m2 repo
> and commented those repositories out. That works.

-- 
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: (SHALE-321) Update TilesViewHandler to support new Tiles 2 Snapshot

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-321?page=all ]

Wendy Smoak resolved SHALE-321.
---

Resolution: Fixed

http://svn.apache.org/viewvc?view=rev&rev=472373

Resolving this once again as Shale Tiles now builds against this snapshot of 
Tiles 2.


> Update TilesViewHandler to support new Tiles 2 Snapshot
> ---
>
> Key: SHALE-321
> URL: http://issues.apache.org/struts/browse/SHALE-321
> Project: Shale
>  Issue Type: Bug
>  Components: Tiles
>Affects Versions: 1.0.4-SNAPSHOT, 1.0.5-SNAPSHOT, 1.0.6-SNAPSHOT
>Reporter: Greg Reddin
> Assigned To: Greg Reddin
>Priority: Blocker
> Fix For: 1.0.4-SNAPSHOT
>
>
> Changes to the Tiles 2 API have broken Tiles support in Shale.  We need to 
> modify TilesViewHandler so it will compile.

-- 
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: (SHALE-325) Add a custom validation example to the Use Cases example app

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-325?page=comments#action_38605 ] 

Wendy Smoak commented on SHALE-325:
---


The error message key is specified in the rule itself, in custom-rules.xml.

   
   
   
   

There is no  tag in faces-config, and adding it didn't help.

The attribute for val:commonsValidator is 'message' (not msg).  Adding that 
fixes the NPE, but see above-- the message is specified in the rule, I 
shouldn't have to say it again.

What do I need to do so that CommonsValidator.getErrorMessage can "see" the 
resource bundle?


> Add a custom validation example to the Use Cases example app
> 
>
> Key: SHALE-325
> URL: http://issues.apache.org/struts/browse/SHALE-325
> Project: Shale
>  Issue Type: Improvement
>  Components: Validator
>Reporter: Wendy Smoak
>Priority: Minor
> Fix For: 1.0.4-SNAPSHOT
>
>
> Add an example of using a custom validator to the Commons Validator  
> Integration section of the  use-cases example app.

-- 
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: (SHALE-325) Add a custom validation example to the Use Cases example app

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-325?page=comments#action_38601 ] 

Wendy Smoak commented on SHALE-325:
---

See:  http://svn.apache.org/viewvc?view=rev&rev=471907

This is incomplete.  I added a third section on the 'Commons Validator 
Integration' page.  If you enter an odd number for 'Priority', you get:

java.lang.NullPointerException
java.text.MessageFormat.applyPattern(MessageFormat.java:414)
java.text.MessageFormat.(MessageFormat.java:368)

org.apache.shale.validator.CommonsValidator.getErrorMessage(CommonsValidator.java:965)

org.apache.shale.validator.CommonsValidator.validate(CommonsValidator.java:849)

javax.faces.component._ComponentUtils.callValidators(_ComponentUtils.java:157)
javax.faces.component.UIInput.validateValue(UIInput.java:312)
javax.faces.component.UIInput.validate(UIInput.java:353)
javax.faces.component.UIInput.processValidators(UIInput.java:183)

javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:624)
javax.faces.component.UIForm.processValidators(UIForm.java:70)

javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:624)

javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:624)
javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:146)

org.apache.myfaces.lifecycle.LifecycleImpl.processValidations(LifecycleImpl.java:262)

org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:76)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)

org.apache.shale.application.faces.ShaleApplicationFilter.doFilter(ShaleApplicationFilter.java:267)



> Add a custom validation example to the Use Cases example app
> 
>
> Key: SHALE-325
> URL: http://issues.apache.org/struts/browse/SHALE-325
> Project: Shale
>  Issue Type: Improvement
>  Components: Validator
>Reporter: Wendy Smoak
>Priority: Minor
> Fix For: 1.0.4-SNAPSHOT
>
>
> Add an example of using a custom validator to the Commons Validator  
> Integration section of the  use-cases example app.

-- 
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] Created: (SHALE-325) Add a custom validation example to the Use Cases example app

[Wendy Smoak (JIRA)]

Add a custom validation example to the Use Cases example app


 Key: SHALE-325
 URL: http://issues.apache.org/struts/browse/SHALE-325
 Project: Shale
  Issue Type: Improvement
  Components: Validator
Reporter: Wendy Smoak
Priority: Minor
 Fix For: 1.0.4-SNAPSHOT


Add an example of using a custom validator to the Commons Validator  
Integration section of the  use-cases example app.

-- 
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] Reopened: (SHALE-321) Update TilesViewHandler to support new Tiles 2 Snapshot

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-321?page=all ]

Wendy Smoak reopened SHALE-321:
---

 
I'm having trouble building Shale Tiles against  r471763 of Tiles 2.

[INFO] Building Shale Tiles Integration
[INFO]task-segment: [install]
[INFO] -
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 1 source file to e:\svn\shale\framework\shale-tiles\target\classes
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Compilation failure

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[35,24] cannot find symbol
symbol  : class ComponentDefinition
location: package org.apache.tiles

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[36,24] cannot find symbol
symbol  : class DefinitionsFactoryException
location: package org.apache.tiles

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[37,24] cannot find symbol
symbol  : class NoSuchDefinitionException
location: package org.apache.tiles

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[38,24] cannot find symbol
symbol  : class TilesRequestContext
location: package org.apache.tiles

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[39,24] cannot find symbol
symbol  : class TilesUtil
location: package org.apache.tiles

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[253,11] cannot find symbol
symbol  : class ComponentDefinition
location: class org.apache.shale.tiles.TilesViewHandler

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[302,31] cannot find symbol
symbol  : class ComponentDefinition
location: class org.apache.shale.tiles.TilesViewHandler

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[130,6] cannot find symbol
symbol  : class ComponentDefinition
location: class org.apache.shale.tiles.TilesViewHandler

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[262,6] cannot find symbol
symbol  : class ComponentDefinition
location: class org.apache.shale.tiles.TilesViewHandler

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[264,8] cannot find symbol
symbol  : class TilesRequestContext
location: class org.apache.shale.tiles.TilesViewHandler

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[265,12] cannot find symbol
symbol  : method createRequestContext(java.lang.Object,java.lang.Object,java.lan
g.Object)
location: class org.apache.tiles.context.BasicTilesContextFactory

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[267,15] cannot find symbol
symbol  : variable TilesUtil
location: class org.apache.shale.tiles.TilesViewHandler

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[268,15] cannot find symbol
symbol  : class NoSuchDefinitionException
location: class org.apache.shale.tiles.TilesViewHandler

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[270,15] cannot find symbol
symbol  : class DefinitionsFactoryException
location: class org.apache.shale.tiles.TilesViewHandler

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[307,6] cannot find symbol
symbol  : class TilesRequestContext
location: class org.apache.shale.tiles.TilesViewHandler

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[308,10] cannot find symbol
symbol  : method createRequestContext(java.lang.Object,java.lang.Object,java.lan
g.Object)
location: class org.apache.tiles.context.BasicTilesContextFactory

e:\svn\shale\framework\shale-tiles\src\main\java\org\apache\shale\tiles\TilesVie
wHandler.java:[312,23] org.apache.tiles.ComponentContext is abstract; cannot be
instantiated



> Update TilesViewHandler to support new Tiles 2 Snapshot
> ---
>
> Key: SHALE-321
> URL: http://issues.apache.org/struts/browse/SHALE-321
> Project: Shale
>  Issue Type: Bug
>  Components: Tiles
>Affects Versions: 1.0.4-SNAPSHOT, 1.0.5-SNAPSHOT, 1.0.6-SNAPSHOT
>Reporter: Greg Reddin
> Assigned To: Greg Reddin
>Priority: Blocker
> Fix For: 1.0.4-SNAPSHOT
>
>
> Changes to the Tiles 2 API have broken T

[jira] Updated: (SHALE-188) Add a default outcome to the dialog manager

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-188?page=all ]

Wendy Smoak updated SHALE-188:
--

Comment: was deleted

> Add a default outcome to the dialog manager
> ---
>
> Key: SHALE-188
> URL: http://issues.apache.org/struts/browse/SHALE-188
> Project: Shale
>  Issue Type: Improvement
>  Components: Core
> Environment: Debian Linux - JDK 1.5
>Reporter: Laure Goudon
>
> Version from manifest: Implementation-Version: 20060326
> Hello,
> When we click on the browser back button while in a dialog and then click on 
> another link or button, an Illegal argument exception comes (see stacktrace). 
> This error occurs because Shale can't find any transition for this action. It 
> would be a good idea that we could have a default transition (for instance 
> named "*" or "default") that the dialog navigation handler class would use if 
> no other transition was found for this state or dialog.
> Thanks.
> stacktrace :
> java.lang.IllegalArgumentException: You have requested a transition outcome 
> named "clusterMenu" from a state named "viewApplicationView" in a dialog 
> named "viewApplication", but no transition definition can be found.  Double 
> check the spelling of the transition outcome name.
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.transition(DialogNavigationHandler.java:526)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.postprocess(DialogNavigationHandler.java:353)
>   at 
> org.apache.shale.dialog.faces.DialogNavigationHandler.handleNavigation(DialogNavigationHandler.java:219)
>   at 
> org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:84)
>   at javax.faces.component.UICommand.broadcast(UICommand.java:106)
>   at 
> org.apache.myfaces.custom.navmenu.htmlnavmenu.HtmlCommandNavigationItem.broadcast(HtmlCommandNavigationItem.java:228)
> Proposed solution :
> In the class DialogNavigationHandler in the method transition
>   /** Default outcome name constant as in :
>*  
>*/
>   public static final String DEFAULT_OUTCOME_NAME = "*";
> // Identify the appropriate Transition
> Transition transition = state.findTransition(outcome);
> if (transition == null) {
> transition = state.getDialog().findTransition(outcome);
> //  Begin patch 
> // If not found, check the default outcome for the current state
>   if (transition == null) {
>Transition transition = state.findTransition(outcome);
>// If not found, check the default outcome for the current dialog.
>if (transition == null) {
>  transition = 
> state.getDialog().findTransition(DEFAULT_OUTCOME_NAME);
>}
> }
> //  End patch 
> }
>   if (transition == null) {
> throw new 
> IllegalArgumentException(messages.getMessage("dialog.noTransition",
>new Object[] { outcome,
>   state.getName(),
>   
> state.getDialog().getName() }));
> }

-- 
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: (SHALE-211) Add Shale to the projects.apache.org site

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-211?page=all ]

Wendy Smoak updated SHALE-211:
--

Comment: was deleted

> Add Shale to the projects.apache.org site
> -
>
> Key: SHALE-211
> URL: http://issues.apache.org/struts/browse/SHALE-211
> Project: Shale
>  Issue Type: Task
>  Components: Documentation
>Reporter: Wendy Smoak
>Priority: Minor
> Fix For: 1.0.4-SNAPSHOT
>
>
> We should be listed on projects.apache.org.  There is a utility to create the 
> file:  http://projects.apache.org/create.html
> shale/trunk/src/site/resources seems like a good place for it.

-- 
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: (SHALE-319) Shale-Parent--pom contains repositories

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-319?page=comments#action_38496 ] 

Wendy Smoak commented on SHALE-319:
---

I added apache.snapshots back to shale-parent last night, after Torsten had 
trouble building the framework.

I added it with releases/enabled/false, so it is the same definition that would 
be inherited from the top-level Apache pom.  The issue is that with nothing in 
your local repo, Maven can't find the snapshot of shale-master in order to 
inherit the repository definitions.  Typical bootstrap problem. :)

Matthias, I'm curious whether this makes the problem you were having re-appear. 
 I think it might have been the 'releases enabled' part that exposed whatever 
Maven bug you were running into.  I hope so, anyway!



> Shale-Parent--pom contains repositories
> ---
>
> Key: SHALE-319
> URL: http://issues.apache.org/struts/browse/SHALE-319
> Project: Shale
>  Issue Type: Bug
> Environment: behind a firewall / proxy
>Reporter: Matthias Wessendorf
> Assigned To: Matthias Wessendorf
> Fix For: 1.0.4-SNAPSHOT
>
>
> The "parent pom" in Shale has an "abuse" of . It
> specifies two repositories inside the  xml element. IMO
> this should be handled by the user's settings.xml file and not by a
> lib.
> So, if you are behind a proxy, a corp.-m2-mirrow and a
> corp-own-m2-repo, you can't build stuff which uses Shale. (This
> envoironment is sorta production like.)
> Why can't you build the stuff?
> Because maven sees only (to fetch Shale dependencies) these two repos:
> -Apache M2 Snapshot
> -Java.net
> So it tries to download apache2-pom from these... it doesn't look in
> other repos.
> (currently the apache m2 snapshot repo is down... so it doesn't get
> Shale-master too,
> which is! available within a regular m2 repo)
> Our work around, we changed the shale-parent-pom in our corp. m2 repo
> and commented those repositories out. That works.

-- 
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] Reopened: (SHALE-319) Shale-Parent--pom contains repositories

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-319?page=all ]

Wendy Smoak reopened SHALE-319:
---

 

Disabling releases on the snapshot repository means we need to modify our 
release process to stage them somewhere else.

We still need to: 
 * Choose a location 
(http://people.apache.org/builds/shale/m2-staging-repository)
 * Update the shale-master pom's 'distributionManagement' section
 * Update the release process documentation.

> Shale-Parent--pom contains repositories
> ---
>
> Key: SHALE-319
> URL: http://issues.apache.org/struts/browse/SHALE-319
> Project: Shale
>  Issue Type: Bug
> Environment: behind a firewall / proxy
>Reporter: Matthias Wessendorf
> Assigned To: Matthias Wessendorf
> Fix For: 1.0.4-SNAPSHOT
>
>
> The "parent pom" in Shale has an "abuse" of . It
> specifies two repositories inside the  xml element. IMO
> this should be handled by the user's settings.xml file and not by a
> lib.
> So, if you are behind a proxy, a corp.-m2-mirrow and a
> corp-own-m2-repo, you can't build stuff which uses Shale. (This
> envoironment is sorta production like.)
> Why can't you build the stuff?
> Because maven sees only (to fetch Shale dependencies) these two repos:
> -Apache M2 Snapshot
> -Java.net
> So it tries to download apache2-pom from these... it doesn't look in
> other repos.
> (currently the apache m2 snapshot repo is down... so it doesn't get
> Shale-master too,
> which is! available within a regular m2 repo)
> Our work around, we changed the shale-parent-pom in our corp. m2 repo
> and commented those repositories out. That works.

-- 
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: (SHALE-319) Shale-Parent--pom contains repositories

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-319?page=comments#action_38483 ] 

Wendy Smoak commented on SHALE-319:
---


I'm also not in favor of a solution that requires developers to edit 
settings.xml in order to build Shale, but I don't think that is the case here.

We have releases enabled on apache.snapshots because that is where we have been 
staging releases.  A better idea would be to stage them elsewhere, such as 
http://people.apache.org/builds/shale/m2-staging-repository, and remove this 
repository definition from shale-parent.

For the java.net repo, I thought I heard that it would be synced with the 
central repository.  If that is true, then we don't need that one, either.

The build failures seem to be a bug in Maven's dependency resolution mechanism. 
 It should check all of the repositories, and from the log output, it never 
checks its own central repo.  We had a similar report at Struts this morning.

> Shale-Parent--pom contains repositories
> ---
>
> Key: SHALE-319
> URL: http://issues.apache.org/struts/browse/SHALE-319
> Project: Shale
>  Issue Type: Bug
> Environment: behind a firewall / proxy
>Reporter: Matthias Wessendorf
> Assigned To: Matthias Wessendorf
>
> The "parent pom" in Shale has an "abuse" of . It
> specifies two repositories inside the  xml element. IMO
> this should be handled by the user's settings.xml file and not by a
> lib.
> So, if you are behind a proxy, a corp.-m2-mirrow and a
> corp-own-m2-repo, you can't build stuff which uses Shale. (This
> envoironment is sorta production like.)
> Why can't you build the stuff?
> Because maven sees only (to fetch Shale dependencies) these two repos:
> -Apache M2 Snapshot
> -Java.net
> So it tries to download apache2-pom from these... it doesn't look in
> other repos.
> (currently the apache m2 snapshot repo is down... so it doesn't get
> Shale-master too,
> which is! available within a regular m2 repo)
> Our work around, we changed the shale-parent-pom in our corp. m2 repo
> and commented those repositories out. That works.

-- 
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: (SHALE-319) Shale-Parent--pom contains repositories

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-319?page=comments#action_38471 ] 

Wendy Smoak commented on SHALE-319:
---

Related discussion thread: 
http://www.nabble.com/Bug-in-pom.xml--...-%21-t2496797.html

> Shale-Parent--pom contains repositories
> ---
>
> Key: SHALE-319
> URL: http://issues.apache.org/struts/browse/SHALE-319
> Project: Shale
>  Issue Type: Bug
> Environment: behind a firewall / proxy
>Reporter: Matthias Wessendorf
> Assigned To: Matthias Wessendorf
>
> The "parent pom" in Shale has an "abuse" of . It
> specifies two repositories inside the  xml element. IMO
> this should be handled by the user's settings.xml file and not by a
> lib.
> So, if you are behind a proxy, a corp.-m2-mirrow and a
> corp-own-m2-repo, you can't build stuff which uses Shale. (This
> envoironment is sorta production like.)
> Why can't you build the stuff?
> Because maven sees only (to fetch Shale dependencies) these two repos:
> -Apache M2 Snapshot
> -Java.net
> So it tries to download apache2-pom from these... it doesn't look in
> other repos.
> (currently the apache m2 snapshot repo is down... so it doesn't get
> Shale-master too,
> which is! available within a regular m2 repo)
> Our work around, we changed the shale-parent-pom in our corp. m2 repo
> and commented those repositories out. That works.

-- 
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: (SHALE-318) Upgrade Shale Test to Cargo 0.9

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-318?page=all ]

Wendy Smoak updated SHALE-318:
--

Attachment: shale-test-cargo-upgrade.diff

> Upgrade Shale Test to Cargo 0.9
> ---
>
> Key: SHALE-318
> URL: http://issues.apache.org/struts/browse/SHALE-318
> Project: Shale
>  Issue Type: Improvement
>  Components: Test
>Affects Versions: 1.0.3
>Reporter: Wendy Smoak
> Attachments: shale-test-cargo-upgrade.diff
>
>
> Upgrade to Cargo 0.9 when it is released.
> Adjust to API changes, some method signatures changed from File to String.

-- 
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] Created: (SHALE-318) Upgrade Shale Test to Cargo 0.9

[Wendy Smoak (JIRA)]

Upgrade Shale Test to Cargo 0.9
---

 Key: SHALE-318
 URL: http://issues.apache.org/struts/browse/SHALE-318
 Project: Shale
  Issue Type: Improvement
  Components: Test
Affects Versions: 1.0.3
Reporter: Wendy Smoak
 Attachments: shale-test-cargo-upgrade.diff

Upgrade to Cargo 0.9 when it is released.

Adjust to API changes, some method signatures changed from File to String.

-- 
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: (SHALE-308) October 12 nightly is missing org.apache.shale.faces.ShaleApplicationFilter

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-308?page=all ]

Wendy Smoak resolved SHALE-308.
---

Fix Version/s: 1.0.4-SNAPSHOT
   Resolution: Fixed

All of the 'dialog2' directories have been deleted from the snapshot repository.

The shale-validator module was added to Continuum.


> October 12 nightly is missing org.apache.shale.faces.ShaleApplicationFilter
> ---
>
> Key: SHALE-308
> URL: http://issues.apache.org/struts/browse/SHALE-308
> Project: Shale
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.0.5-SNAPSHOT
> Environment: facelets 1.1.11
> jsf ri 1.2.03 recent nightly
>Reporter: Reind
> Assigned To: Craig McClanahan
> Fix For: 1.0.4-SNAPSHOT
>
>
> The 2006/10/12 Shale nightly is missing class 
> org.apache.shale.faces.ShaleApplicationFilter
> stacktrace:
> 16:21:27,859 ERROR [[/Merlin-Admin]] Exception starting filter shale
> java.lang.ClassNotFoundException: 
> org.apache.shale.faces.ShaleApplicationFilter
> at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1352)
> at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
> at 
> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:209)
> at 
> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:304)
> at 
> org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:77)
> at 
> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3600)
> at 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4193)
> at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
> at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
> at 
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
> at sun.reflect.GeneratedMethodAccessor1308.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at 
> org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> at 
> org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
> at 
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at 
> org.apache.catalina.core.StandardContext.init(StandardContext.java:5116)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at 
> org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> at 
> org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
> at 
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at 
> org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
> at 
> org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
> at 
> org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
> at org.jboss.web.WebModule.startModule(WebModule.java:83)
> at org.jboss.web.WebModule.startService(WebModule.java:61)
> at 
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> at 
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at 
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at 
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> at 
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at 
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> at $Proxy0.start(Unknown Source)
> at 
> org.jboss.system.ServiceController.start(ServiceController.java:417)
> at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown 

[jira] Commented: (SHALE-308) October 12 nightly is missing org.apache.shale.faces.ShaleApplicationFilter

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-308?page=comments#action_38400 ] 

Wendy Smoak commented on SHALE-308:
---


I added the following modules to Continuum:
 * shale-view
 * shale-dialog
 * shale-dialog-basic
 * shale-dialog-scxml
 * shale-application

TODO:  Clean up the snapshot repo (delete shale-dialog2, etc.,) and add any 
missing modules.

> October 12 nightly is missing org.apache.shale.faces.ShaleApplicationFilter
> ---
>
> Key: SHALE-308
> URL: http://issues.apache.org/struts/browse/SHALE-308
> Project: Shale
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.0.5-SNAPSHOT
> Environment: facelets 1.1.11
> jsf ri 1.2.03 recent nightly
>Reporter: Reind
> Assigned To: Craig McClanahan
>
> The 2006/10/12 Shale nightly is missing class 
> org.apache.shale.faces.ShaleApplicationFilter
> stacktrace:
> 16:21:27,859 ERROR [[/Merlin-Admin]] Exception starting filter shale
> java.lang.ClassNotFoundException: 
> org.apache.shale.faces.ShaleApplicationFilter
> at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1352)
> at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
> at 
> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:209)
> at 
> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:304)
> at 
> org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:77)
> at 
> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3600)
> at 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4193)
> at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
> at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
> at 
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
> at sun.reflect.GeneratedMethodAccessor1308.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at 
> org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> at 
> org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
> at 
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at 
> org.apache.catalina.core.StandardContext.init(StandardContext.java:5116)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at 
> org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> at 
> org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
> at 
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at 
> org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
> at 
> org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
> at 
> org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
> at org.jboss.web.WebModule.startModule(WebModule.java:83)
> at org.jboss.web.WebModule.startService(WebModule.java:61)
> at 
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> at 
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at 
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at 
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> at 
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at 
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> at $Proxy0.start(Unknown Source)
> at 
> org.jboss.system.ServiceController.start(ServiceController.java:417)
> at sun.reflect.

[jira] Commented: (SHALE-308) October 12 nightly is missing org.apache.shale.faces.ShaleApplicationFilter

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-308?page=comments#action_38382 ] 

Wendy Smoak commented on SHALE-308:
---

This is related to SHALE-299, refactoring the core into separate modules.

> October 12 nightly is missing org.apache.shale.faces.ShaleApplicationFilter
> ---
>
> Key: SHALE-308
> URL: http://issues.apache.org/struts/browse/SHALE-308
> Project: Shale
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.0.5-SNAPSHOT
> Environment: facelets 1.1.11
> jsf ri 1.2.03 recent nightly
>Reporter: Reind
>
> The 2006/10/12 Shale nightly is missing class 
> org.apache.shale.faces.ShaleApplicationFilter
> stacktrace:
> 16:21:27,859 ERROR [[/Merlin-Admin]] Exception starting filter shale
> java.lang.ClassNotFoundException: 
> org.apache.shale.faces.ShaleApplicationFilter
> at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1352)
> at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
> at 
> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:209)
> at 
> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:304)
> at 
> org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:77)
> at 
> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3600)
> at 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4193)
> at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
> at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
> at 
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
> at sun.reflect.GeneratedMethodAccessor1308.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at 
> org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> at 
> org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
> at 
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at 
> org.apache.catalina.core.StandardContext.init(StandardContext.java:5116)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at 
> org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> at 
> org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
> at 
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at 
> org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
> at 
> org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
> at 
> org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
> at org.jboss.web.WebModule.startModule(WebModule.java:83)
> at org.jboss.web.WebModule.startService(WebModule.java:61)
> at 
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> at 
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at 
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> at 
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> at 
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at 
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> at $Proxy0.start(Unknown Source)
> at 
> org.jboss.system.ServiceController.start(ServiceController.java:417)
> at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method

[jira] Updated: (SHALE-220) init() lifecycle method called twice

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-220?page=all ]

Wendy Smoak updated SHALE-220:
--

Fix Version/s: 1.0.4-SNAPSHOT
   (was: 1.0.3)
Affects Version/s: 1.0.3

Adjusted affects and fix-for versions

> init() lifecycle method called twice
> 
>
> Key: SHALE-220
> URL: http://issues.apache.org/struts/browse/SHALE-220
> Project: Shale
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.0.2, 1.0.3
>Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
> Fix For: 1.0.4-SNAPSHOT
>
>
> From a user mailing list posting by Viswanath , 
> following up on earlier mailing list conversations:
> ==
> Hi Craig,
> Now that I have subscribed to Shale user group, I am posting this issue again.
> Just to make sure that I am not using older version of Shale libraries, I 
> have downloaded shale-framework-20060713.zip and tried, same problem. This is 
> what I did,  to reproduce the issue in usecases project. ( I am not able to 
> post code from my project because of lot of dependencies on EJBs/Database)
> I downloaded the latest usecases zip (07/14/2006). Unzipped the war file into 
> a directory, created a project in eclipse, added the java source files,  
> built and deployed it into JBOSS and it ran fine.  Added the following code 
> at the end of  org/apache/shale/usecases/locale/Select.java overriding the 
> "do-nothing" init() from ActionViewController.
>public void init()
>{
> System.out.println("Select.java - Init - PostBack Value: " + 
> Boolean.toString(isPostBack()));
>}
> redeployed and ran. The console output when I click on "Select Language" link
> 15:20:27,515 INFO  [STDOUT] Select.java - Init - PostBack Value: false
> 15:20:27,515 INFO  [STDOUT] Select.java - Init - PostBack Value: false
> and on sumbit (when I click on "Go" )
> 15:20:33,546 INFO  [STDOUT] Select.java - Init - PostBack Value: false
> 15:20:33,562 INFO  [STDOUT] Select.java - Init - PostBack Value: true
> My environment is :
> OS : Windows XP Home
> JBOSS 4.0.4 Patch1 with Tomcat 5.5
> JRE : 1.5.0_06
> Eclipse 3.1.1
> Thanks
> Vish
> ==
> I was able to reproduce this with latest trunk bits, using the default 
> testing configuration (MyFaces, Tomcat 5.5).  It's clearly a bug in how init 
> and destroy method callbacks are being triggered for view controllers, most 
> likely related to the fact that the mechanism for this was recently changed.

-- 
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: (SHALE-293) Upgrade to MyFaces 1.1.4

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-293?page=all ]

Wendy Smoak resolved SHALE-293.
---

Resolution: Fixed

Fixed in r449902.

Rahul, does it build for you with these changes?

> Upgrade to MyFaces 1.1.4
> 
>
> Key: SHALE-293
> URL: http://issues.apache.org/struts/browse/SHALE-293
> Project: Shale
>  Issue Type: Task
>  Components: Core, Examples
>Reporter: Wendy Smoak
> Assigned To: Wendy Smoak
> Fix For: 1.0.4-SNAPSHOT
>
>
> Now that MyFaces Core 1.1.4 is released and available in the central Maven 
> repository, upgrade our dependencies.

-- 
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] Created: (SHALE-293) Upgrade to MyFaces 1.1.4

[Wendy Smoak (JIRA)]

Upgrade to MyFaces 1.1.4


 Key: SHALE-293
 URL: http://issues.apache.org/struts/browse/SHALE-293
 Project: Shale
  Issue Type: Task
  Components: Core, Examples
Reporter: Wendy Smoak
 Assigned To: Wendy Smoak
 Fix For: 1.0.4-SNAPSHOT


Now that MyFaces Core 1.1.4 is released and available in the central Maven 
repository, upgrade our dependencies.



-- 
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: (SHALE-289) Build failures post r443256 refactoring

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-289?page=comments#action_38250 ] 

Wendy Smoak commented on SHALE-289:
---

My proposed workaround is to explicitly declare a dependency on 
commons-validator with a version number in shale-core.

To make sure this gets fixed, we should construct a simple two-level project 
with just commons-validator and myfaces as dependencies, and attach it to a 
Maven JIRA issue.


> Build failures post r443256 refactoring
> ---
>
> Key: SHALE-289
> URL: http://issues.apache.org/struts/browse/SHALE-289
> Project: Shale
>  Issue Type: Bug
>Affects Versions: 1.0.4-SNAPSHOT
>Reporter: Rahul Akolkar
>
> Post r443256 [1], the framework build is failing for vanilla m204 users. 
> Details are in this [2] discussion thread.
> [1] http://svn.apache.org/viewvc?view=rev&revision=443256
> [2] http://www.nabble.com/Building-from-subversion-source-tf2296108.html

-- 
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: (SHALE-283) shale-framework-1.0.3.zip is missing a number of jar files

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-283?page=comments#action_38217 ] 

Wendy Smoak commented on SHALE-283:
---


I think only required dependencies were included in the zip file.

Cargo, HtmlUnit and JMock are optional for Shale Test.   Maven should retrieve 
them for you at compile time.  Is that not happening?

Shale Designtime was not supposed to be part of the 1.0.3 release, so the 
Creator jars should not be required (and we probably can't redistribute them 
anyway. )  There are instructions in the shale-designtime pom.xml file about 
how to find and install the jars locally.

The commons-validator version issue is likely related to the known problems 
with Maven's dependency management.  We'll be addressing that along with the 
problem of the wrong jars being included in the example apps.

> shale-framework-1.0.3.zip is missing a number of jar files
> --
>
> Key: SHALE-283
> URL: http://issues.apache.org/struts/browse/SHALE-283
> Project: Shale
>  Issue Type: Improvement
>Affects Versions: 1.0.3
> Environment: NA
>Reporter: Henry Li
>Priority: Minor
>
> The following jar files are missing in the lib folder:
> cargo-core-api-util-0.8.jar
> cargo-core-api-container-0.8.jar
> cargo-core-api-generic-0.8.jar
> cargo-core-container-tomcat-0.8.jar
> cglib-2.2_beta1.jar
> jmock-cglib-1.1.0.jar
> jmock-1.1.0.jar
> com-sun-rave-designtime.jar
> jsfcl.jar
> jsfcl-dt.jar
> htmlunit-1.9.jar
> Also the commons validator is using the wrong version 1.1.4. It should be 
> newer. It compiles for me with 1.3.0.

-- 
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: (SHALE-258) Shale core and test framework 1.0.3 includes MyFaces 1.1.1

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-258?page=all ]

Wendy Smoak updated SHALE-258:
--

Fix Version/s: 1.0.4-SNAPSHOT
Affects Version/s: 1.0.3

> Shale core and test framework 1.0.3 includes MyFaces 1.1.1
> --
>
> Key: SHALE-258
> URL: http://issues.apache.org/struts/browse/SHALE-258
> Project: Shale
>  Issue Type: Bug
>  Components: Core, Test
>Affects Versions: 1.0.3-SNAPSHOT, 1.0.3
>Reporter: Paul Spencer
> Fix For: 1.0.4-SNAPSHOT
>
>
> Shale's core and test framwork includes MyFaces 1.1.1 in the classpath when 
> testing via Maven. The testing framework should not impose the JSF 
> implementation on 
> what is being tested.  
> A related issue was reported, and fixed, in MyFaces. See 
> http://issues.apache.org/jira/browse/TOMAHAWK-612

-- 
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: (SHALE-267) Promote the best practice of avoiding spaces in dialog state names

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-267?page=all ]

Wendy Smoak resolved SHALE-267.
---

Fix Version/s: 1.0.4-SNAPSHOT
   Resolution: Fixed

URL: http://svn.apache.org/viewvc?rev=439525&view=rev
Log:
Per discussion on the dev list, make dialog and state names omit embedded 
spaces.



> Promote the best practice of avoiding spaces in dialog state names
> --
>
> Key: SHALE-267
> URL: http://issues.apache.org/struts/browse/SHALE-267
> Project: Shale
>  Issue Type: Task
>  Components: Dialog
>Affects Versions: 1.0.3
>Reporter: Rahul Akolkar
>Priority: Minor
> Fix For: 1.0.4-SNAPSHOT
>
>
> More of a task reminder for myself.
> Discussion thread:
> http://www.nabble.com/-dialog--Name-attribute-best-practice-tf2166188.html
> Summary (fallback in case archives link fails):
> On 8/25/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> > On 8/25/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > >
> > > On 8/25/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> > > > On 8/25/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > I would like to propose a best practice for the name attribute used in
> > > > > various bits of the XML vocabulary for Shale dialogs that recommends
> > > > > restricting these to alphanumeric characters (no spaces etc.)
> > > >
> > > >
> > > > I suppose there's a technical reason for this ... I really like the
> > > > readability of these if we can keep them and it was why I chose "name"
> > > > instead of "id' for that attribute in the first place.
> > > >
> > > 
> > >
> > > Yes, the state IDs are meant to be IDREFs in space separated lists on
> > > transition targets when the SCXML  element is used, where it
> > > will be possible to have more than one transition target, as long as
> > > the targets belong to the regions of the same parallel.
> > >
> > > Ofcourse, when using a space separated list, having spaces in
> > > individual tokens will throw a wrench in the works.
> > 
> > 
> > Yah, that makes sense.  Go ahead and do the patch, and I'll apply it.
> > 
> > -Rahul
> > 
> > 
> > Craig
> > 

-- 
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: (SHALE-273) Document the Sandbox policy on access for existing Apache committers

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-273?page=all ]

Wendy Smoak resolved SHALE-273.
---

Resolution: Fixed
  Assignee: Wendy Smoak

Done  http://shale.apache.org/sandbox/

> Document the Sandbox policy on access for existing Apache committers
> 
>
> Key: SHALE-273
> URL: http://issues.apache.org/struts/browse/SHALE-273
> Project: Shale
>  Issue Type: Task
>  Components: Documentation
>Reporter: Wendy Smoak
> Assigned To: Wendy Smoak
> Fix For: 1.0.4-SNAPSHOT
>
>
> Proposal thread: 
> http://www.nabble.com/-PROPOSAL--Open-the-Shale-Sandbox-to-any-interested-Apache-committer-t2200372.html
> The Shale Sandbox is now open to any existing Apache committer.
> Add an index page for the sandbox, and add a link to the Sandbox from the 
> shale.apache.org website.
> Though it doesn't affect the framework, I'm marking this as fix-for 1.0.4 so 
> it will show up in the release notes.

-- 
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] Created: (SHALE-273) Document the Sandbox policy on access for existing Apache committers

[Wendy Smoak (JIRA)]

Document the Sandbox policy on access for existing Apache committers


 Key: SHALE-273
 URL: http://issues.apache.org/struts/browse/SHALE-273
 Project: Shale
  Issue Type: Task
  Components: Documentation
Reporter: Wendy Smoak
 Fix For: 1.0.4-SNAPSHOT



Proposal thread: 
http://www.nabble.com/-PROPOSAL--Open-the-Shale-Sandbox-to-any-interested-Apache-committer-t2200372.html

The Shale Sandbox is now open to any existing Apache committer.

Add an index page for the sandbox, and add a link to the Sandbox from the 
shale.apache.org website.

Though it doesn't affect the framework, I'm marking this as fix-for 1.0.4 so it 
will show up in the release notes.

-- 
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: (SHALE-265) Parent-POM has snapshot repository dependency

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-265?page=all ]

Wendy Smoak updated SHALE-265:
--

Comment: was deleted

> Parent-POM has snapshot repository dependency
> -
>
> Key: SHALE-265
> URL: http://issues.apache.org/struts/browse/SHALE-265
> Project: Shale
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.0.4-SNAPSHOT, 1.0.3
>Reporter: Matthias Wessendorf
>Priority: Critical
>
> the parent pom 103 defines the maven-snapshot-repository.
> that should not be in there, maybe only inside "distributionManagement" 
> section.
>
> 
> apache.snapshots
> Apache Maven Repository (Snapshots and Test Builds)
> http://people.apache.org/maven-snapshot-repository
> true
> true
> 
> 
> java.net
> java.net Maven 1 Repository
> https://maven-repository.dev.java.net/nonav/repository
> legacy
> 
> ...

-- 
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: (SHALE-265) Parent-POM has snapshot repository dependency

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-265?page=comments#action_38056 ] 

Wendy Smoak commented on SHALE-265:
---

Discussion thread: 
  http://mail-archives.apache.org/mod_mbox/shale-dev/200608.mbox/[EMAIL 
PROTECTED]

> Parent-POM has snapshot repository dependency
> -
>
> Key: SHALE-265
> URL: http://issues.apache.org/struts/browse/SHALE-265
> Project: Shale
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.0.4-SNAPSHOT, 1.0.3
>Reporter: Matthias Wessendorf
>Priority: Critical
>
> the parent pom 103 defines the maven-snapshot-repository.
> that should not be in there, maybe only inside "distributionManagement" 
> section.
>
> 
> apache.snapshots
> Apache Maven Repository (Snapshots and Test Builds)
> http://people.apache.org/maven-snapshot-repository
> true
> true
> 
> 
> java.net
> java.net Maven 1 Repository
> https://maven-repository.dev.java.net/nonav/repository
> legacy
> 
> ...

-- 
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: (SHALE-265) Parent-POM has snapshot repository dependency

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-265?page=comments#action_38055 ] 

Wendy Smoak commented on SHALE-265:
---

Discussion thread: 
http://mail-archives.apache.org/mod_mbox/shale-dev/200608.mbox/[EMAIL PROTECTED]


> Parent-POM has snapshot repository dependency
> -
>
> Key: SHALE-265
> URL: http://issues.apache.org/struts/browse/SHALE-265
> Project: Shale
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.0.4-SNAPSHOT, 1.0.3
>Reporter: Matthias Wessendorf
>Priority: Critical
>
> the parent pom 103 defines the maven-snapshot-repository.
> that should not be in there, maybe only inside "distributionManagement" 
> section.
>
> 
> apache.snapshots
> Apache Maven Repository (Snapshots and Test Builds)
> http://people.apache.org/maven-snapshot-repository
> true
> true
> 
> 
> java.net
> java.net Maven 1 Repository
> https://maven-repository.dev.java.net/nonav/repository
> legacy
> 
> ...

-- 
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: (SHALE-258) Shale core and test framework 1.0.3 includes MyFaces 1.1.1

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-258?page=comments#action_38013 ] 

Wendy Smoak commented on SHALE-258:
---


To avoid enforcing the choice of JSF implementation on users, all of the JSF 
api and impl dependencies should be marked 'provided'.

Since these definitions are in the shale-parent pom, this issue affects all of 
the Shale jars.

This will be addressed as part of a larger effort that will also fix the 
dependencies for the webapps and work around some issues with Maven's 
dependency resolution.

Users can work around this issue in Shale 1.0.3 by using  in their 
own project poms.


> Shale core and test framework 1.0.3 includes MyFaces 1.1.1
> --
>
> Key: SHALE-258
> URL: http://issues.apache.org/struts/browse/SHALE-258
> Project: Shale
>  Issue Type: Bug
>  Components: Core, Test
>Affects Versions: 1.0.3-SNAPSHOT
>Reporter: Paul Spencer
>
> Shale's core and test framwork includes MyFaces 1.1.1 in the classpath when 
> testing via Maven. The testing framework should not impose the JSF 
> implementation on 
> what is being tested.  
> A related issue was reported, and fixed, in MyFaces. See 
> http://issues.apache.org/jira/browse/TOMAHAWK-612

-- 
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: (SHALE-259) Release the Shale Blank archetype for 1.0.3

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-259?page=all ]

Wendy Smoak updated SHALE-259:
--

Description: Release and publish the Shale Blank Archetype associated with 
Shale 1.0.3.  (was: Once Shale 1.0.3 is available on ibiblio, release and 
publish the associated Shale Blank Archetype.)

> Release the Shale Blank archetype for 1.0.3
> ---
>
> Key: SHALE-259
> URL: http://issues.apache.org/struts/browse/SHALE-259
> Project: Shale
>  Issue Type: Task
>Affects Versions: 1.0.3-SNAPSHOT
>Reporter: Wendy Smoak
>Priority: Minor
>
> Release and publish the Shale Blank Archetype associated with Shale 1.0.3.

-- 
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] Created: (SHALE-259) Release the Shale Blank archetype for 1.0.3

[Wendy Smoak (JIRA)]

Release the Shale Blank archetype for 1.0.3
---

 Key: SHALE-259
 URL: http://issues.apache.org/struts/browse/SHALE-259
 Project: Shale
  Issue Type: Task
Affects Versions: 1.0.3-SNAPSHOT
Reporter: Wendy Smoak
Priority: Minor


Once Shale 1.0.3 is available on ibiblio, release and publish the associated 
Shale Blank Archetype.

-- 
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: (SHALE-242) Review dependency version numbers

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-242?page=comments#action_37977 ] 

Wendy Smoak commented on SHALE-242:
---

Probably not.  Eventually someone will provide poms for Spring 1.2.8.

> Review dependency version numbers
> -
>
> Key: SHALE-242
> URL: http://issues.apache.org/struts/browse/SHALE-242
> Project: Shale
>  Issue Type: Task
>  Components: Clay, Core, Remoting, Test, Tiger, Tiles
>Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
> Fix For: 1.0.3-SNAPSHOT
>
>
> Review version numbers of dependencies listed in our POMs to make sure we've 
> got the desired versions (normally latest release).

-- 
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: (SHALE-242) Review dependency version numbers

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-242?page=all ]

Wendy Smoak updated SHALE-242:
--


There are no poms in ibiblio for Spring 1.2.8.  Are we missing any of its 
transitive dependencies because of that?

> Review dependency version numbers
> -
>
> Key: SHALE-242
> URL: http://issues.apache.org/struts/browse/SHALE-242
> Project: Shale
>  Issue Type: Task
>  Components: Core, Clay, Remoting, Tiger, Test, Tiles
>Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
> Fix For: 1.0.3-SNAPSHOT
>
>
> Review version numbers of dependencies listed in our POMs to make sure we've 
> got the desired versions (normally latest release).

-- 
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: (SHALE-249) Add "throws Exception" to signatures of setUp() and tearDown() in AbstractJsfTestCase

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-249?page=comments#action_37947 ] 

Wendy Smoak commented on SHALE-249:
---

I'm with James -- if it's incorrect, lets fix it.  We've only had an alpha 
release, people will understand that things may change.

> Add "throws Exception" to signatures of setUp() and tearDown() in 
> AbstractJsfTestCase
> -
>
> Key: SHALE-249
> URL: http://issues.apache.org/struts/browse/SHALE-249
> Project: Shale
>  Issue Type: Improvement
>  Components: Test
>Reporter: Craig McClanahan
>
> (From a discussion on the user mailing list 
>  PROTECTED]>)
> In JUnit 3.8.1, the TestCase base class declares "throws Exception" in its 
> method signatures for setUp() and tearDown(), but this is not the case on 
> AbstractJsfTestCase.  Should be added for consistency.

-- 
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: (SHALE-241) Release Shale Master POM in preparation for a 1.0.3 release

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-241?page=comments#action_37946 ] 

Wendy Smoak commented on SHALE-241:
---

When we switch shale-master to 2-SNAPSHOT, we can switch to version 3 of the 
Apache pom.

http://www.ibiblio.org/maven2/org/apache/apache/

> Release Shale Master POM in preparation for a 1.0.3 release
> ---
>
> Key: SHALE-241
> URL: http://issues.apache.org/struts/browse/SHALE-241
> Project: Shale
>  Issue Type: Task
>Reporter: Craig McClanahan
> Fix For: 1.0.3-SNAPSHOT
>
>
> In order to do a 1.0.3 release of Shale as a whole, we're going to need to 
> release the master POM with a version number of "1" instead of "1-SNAPSHOT".

-- 
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: (SHALE-130) [shale] Add documentation for "tiles" and "remoting" features

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-130?page=comments#action_37935 ] 

Wendy Smoak commented on SHALE-130:
---

Applied in r429947 with some reformatting.  Thanks, David!
http://svn.apache.org/viewvc?rev=429947&view=rev


> [shale] Add documentation for "tiles" and "remoting" features
> -
>
> Key: SHALE-130
> URL: http://issues.apache.org/struts/browse/SHALE-130
> Project: Shale
>  Issue Type: Improvement
>  Components: Documentation
> Environment: Operating System: other
> Platform: Other
>Reporter: Craig McClanahan
>Priority: Minor
> Attachments: features-remoting.zip, features-remoting.zip
>
>
> The feature documentation pages for these two topices are currently
> placeholders, and need to be fleshed out in a format similar to the other
> sections (Introduction, Services Provided, and Using XXX).

-- 
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: (SHALE-242) Review dependency version numbers

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-242?page=comments#action_37930 ] 

Wendy Smoak commented on SHALE-242:
---

tiles-core should be 2.0-SNAPSHOT.  It has changed since 0.2-SNAPSHOT, so check 
for breakage.

> Review dependency version numbers
> -
>
> Key: SHALE-242
> URL: http://issues.apache.org/struts/browse/SHALE-242
> Project: Shale
>  Issue Type: Task
>  Components: Core, Clay, Remoting, Tiger, Test, Tiles
>Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
> Fix For: 1.0.3-SNAPSHOT
>
>
> Review version numbers of dependencies listed in our POMs to make sure we've 
> got the desired versions (normally latest release).

-- 
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: (SHALE-230) Restore publishing the dialog-config_1.0.dtd file (and any other DTDs defined by Shale)

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-230?page=comments#action_37902 ] 

Wendy Smoak commented on SHALE-230:
---

See r427910 for antrun plugin config to copy in the dtds.

I'd like to move the Clay dtd into org/apache/clay/config and copy it to 
META-INF during the Clay build, rather than the other way around.  This will 
allow us to copy everything in that directory instead of picking filenames out 
of META-INF which contains various other things, and it will be consistent with 
the location of the dialog dtd in shale-core.





> Restore publishing the dialog-config_1.0.dtd file (and any other DTDs defined 
> by Shale)
> ---
>
> Key: SHALE-230
> URL: http://issues.apache.org/struts/browse/SHALE-230
> Project: Shale
>  Issue Type: Bug
>  Components: Website
>Affects Versions: 1.0.2
>Reporter: Craig McClanahan
> Assigned To: Wendy Smoak
>
> As part of our transition to the shale.apache.org website, it appears that 
> publishing the DTD for dialog configuration (to subdirectory "dtds" on the 
> website) got inadvertently dropped.  It needs to be restored to the build 
> process.

-- 
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: (SHALE-227) Restructure the svn repo to establish a 'sandbox' and separate the 'maven' module from the framework

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-227?page=all ]

Wendy Smoak resolved SHALE-227.
---

Resolution: Fixed

> Restructure the svn repo to establish a 'sandbox' and separate the 'maven' 
> module from the framework
> 
>
> Key: SHALE-227
> URL: http://issues.apache.org/struts/browse/SHALE-227
> Project: Shale
>  Issue Type: Task
>Affects Versions: Nightly
>Reporter: Wendy Smoak
> Assigned To: Greg Reddin
> Fix For: 1.0.3
>
>
> Proposed organization:
>   
> shale/framework/trunk
> shale/maven/trunk
> shale/sandbox
> Discussion thread: 
> http://www.mail-archive.com/dev%40shale.apache.org/msg00161.html

-- 
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: (SHALE-211) Add Shale to the projects.apache.org site

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-211?page=all ]

Wendy Smoak updated SHALE-211:
--

Fix Version/s: 1.0.4
   (was: 1.0.3)

> Add Shale to the projects.apache.org site
> -
>
> Key: SHALE-211
> URL: http://issues.apache.org/struts/browse/SHALE-211
> Project: Shale
>  Issue Type: Task
>  Components: Documentation
>Reporter: Wendy Smoak
>Priority: Minor
> Fix For: 1.0.4
>
>
> We should be listed on projects.apache.org.  There is a utility to create the 
> file:  http://projects.apache.org/create.html
> shale/trunk/src/site/resources seems like a good place for it.

-- 
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: (SHALE-243) Use Selenium for functional testing of the example apps

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-243?page=all ]

Wendy Smoak updated SHALE-243:
--

Attachment: SHALE-243-wsmoak.diff

Packaging the webapp is not working properly after r427581 this morning.
 * http://svn.apache.org/viewvc?rev=427581&view=rev

When I switched from the distribution to the selenium-core jar in the Maven 
repo, I didn't synchronize the location where it gets unpacked with the 
location where the antrun plugin expects to find the files to copy. 

After the patch, 'mvn package -Pselenium' works again.


> Use Selenium for functional testing of the example apps
> ---
>
> Key: SHALE-243
> URL: http://issues.apache.org/struts/browse/SHALE-243
> Project: Shale
>  Issue Type: Improvement
>  Components: Examples
>Affects Versions: Nightly
>Reporter: Wendy Smoak
>Priority: Minor
> Fix For: 1.0.4
>
> Attachments: SHALE-243-wsmoak.diff
>
>
> Use Selenium from OpenQA to verify that the example apps work properly.

-- 
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: (SHALE-243) Use Selenium for functional testing of the example apps

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-243?page=comments#action_37884 ] 

Wendy Smoak commented on SHALE-243:
---


See this page for information on installing Selenium and running the tests:
   http://shale.apache.org/shale-apps/selenium.html

Commits:
* http://svn.apache.org/viewvc?rev=427397&view=rev
* http://svn.apache.org/viewvc?rev=427419&view=rev



> Use Selenium for functional testing of the example apps
> ---
>
> Key: SHALE-243
> URL: http://issues.apache.org/struts/browse/SHALE-243
> Project: Shale
>  Issue Type: Improvement
>  Components: Examples
>Affects Versions: Nightly
>Reporter: Wendy Smoak
>Priority: Minor
> Fix For: 1.0.4
>
>
> Use Selenium from OpenQA to verify that the example apps work properly.

-- 
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] Created: (SHALE-243) Use Selenium for functional testing of the example apps

[Wendy Smoak (JIRA)]

Use Selenium for functional testing of the example apps
---

 Key: SHALE-243
 URL: http://issues.apache.org/struts/browse/SHALE-243
 Project: Shale
  Issue Type: Improvement
  Components: Examples
Affects Versions: Nightly
Reporter: Wendy Smoak
Priority: Minor
 Fix For: 1.0.4


Use Selenium from OpenQA to verify that the example apps work properly.



-- 
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: (SHALE-179) Convert the Shale build to Maven 2

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-179?page=all ]

Wendy Smoak resolved SHALE-179.
---

Resolution: Fixed

The Maven 2 build seems to be complete, so I'm going to resolve this.

Commits can still refer to this issue number if anything else needs to be done.

> Convert the Shale build to Maven 2
> --
>
> Key: SHALE-179
> URL: http://issues.apache.org/struts/browse/SHALE-179
> Project: Shale
>  Issue Type: Task
>  Components: Core, Clay, Remoting, Tiger, Test, Examples, 
> Documentation, Website
>Reporter: Wendy Smoak
> Fix For: 1.0.3
>
>
> Convert the Shale project structure and build to Maven 2.

-- 
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] Reopened: (SHALE-211) Add Shale to the projects.apache.org site

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-211?page=all ]

Wendy Smoak reopened SHALE-211:
---

  Assignee: (was: James Mitchell)
 
Use the new maven-doap-plugin to generate the doap file.

Let site-dev@ know of the new doap file location, it was moved under 
'frameworks'.

> Add Shale to the projects.apache.org site
> -
>
> Key: SHALE-211
> URL: http://issues.apache.org/struts/browse/SHALE-211
> Project: Shale
>  Issue Type: Task
>  Components: Documentation
>Reporter: Wendy Smoak
>Priority: Minor
> Fix For: 1.0.3
>
>
> We should be listed on projects.apache.org.  There is a utility to create the 
> file:  http://projects.apache.org/create.html
> shale/trunk/src/site/resources seems like a good place for it.

-- 
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: (SHALE-225) Example application ilustrating Java Persistence Architecture (JPA) integration

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-225?page=comments#action_37844 ] 

Wendy Smoak commented on SHALE-225:
---


Some interesting parts of shale-test have no dependencies on Shale, and they're 
included under 'framework'.

I'm not sure it's worth significantly complicating the release process (it 
would require a separate release of mailreader-jpa) in order to keep this out 
of the framework directory.

How about putting it in shale-apps/mailreader-jpa, and using
   groupId org.apache.shale.extras 
   artifactIdmailreader-jpa
?


> Example application ilustrating Java Persistence Architecture (JPA) 
> integration
> ---
>
> Key: SHALE-225
> URL: http://issues.apache.org/struts/browse/SHALE-225
> Project: Shale
>  Issue Type: New Feature
>  Components: Examples
>Affects Versions: 1.0.2
>Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
> Fix For: 1.0.3
>
>
> Provide an example application (most likely based on the Struts MailReader 
> example) that illustrates the use of Java Persistence Architecture (JPA) 
> classes in a Shale based application.

-- 
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: (SHALE-230) Restore publishing the dialog-config_1.0.dtd file (and any other DTDs defined by Shale)

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-230?page=all ]

Wendy Smoak updated SHALE-230:
--

Assignee: Wendy Smoak

It hasn't synced yet -- did you rename dialog.dtd with the version number?

At Struts it's published as shale-dialog-config_1_0.dtd
http://struts.apache.org/dtds/

> Restore publishing the dialog-config_1.0.dtd file (and any other DTDs defined 
> by Shale)
> ---
>
> Key: SHALE-230
> URL: http://issues.apache.org/struts/browse/SHALE-230
> Project: Shale
>  Issue Type: Bug
>  Components: Website
>Affects Versions: 1.0.2
>Reporter: Craig McClanahan
> Assigned To: Wendy Smoak
>
> As part of our transition to the shale.apache.org website, it appears that 
> publishing the DTD for dialog configuration (to subdirectory "dtds" on the 
> website) got inadvertently dropped.  It needs to be restored to the build 
> process.

-- 
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: (SHALE-225) Example application ilustrating Java Persistence Architecture (JPA) integration

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-225?page=comments#action_37839 ] 

Wendy Smoak commented on SHALE-225:
---


Why is mailreader-jpa in the sandbox?  If we follow the normal rules, sandbox 
components are not allowed to have releases.  That would leave this example app 
dependent on a snapshot of mailreader-jpa.  (Which should be named 
shale-mailreader-jpa, I think...)

I seem to recall you mentioning struts-mailreader-dao being in the Struts 
sandbox, and that is not the case.  It is a module at the same level as 
struts-core and struts-extras.


> Example application ilustrating Java Persistence Architecture (JPA) 
> integration
> ---
>
> Key: SHALE-225
> URL: http://issues.apache.org/struts/browse/SHALE-225
> Project: Shale
>  Issue Type: New Feature
>  Components: Examples
>Affects Versions: 1.0.2
>Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
> Fix For: 1.0.3
>
>
> Provide an example application (most likely based on the Struts MailReader 
> example) that illustrates the use of Java Persistence Architecture (JPA) 
> classes in a Shale based application.

-- 
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: (SHALE-179) Convert the Shale build to Maven 2

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-179?page=comments#action_37836 ] 

Wendy Smoak commented on SHALE-179:
---

Reported by Stephan Opitz on the user list:
 * http://www.mail-archive.com/user%40shale.apache.org/msg00120.html

Caused by: java.util.MissingResourceException: Can't find bundle for
base name org.apache.shale.tiles.Bundle, locale de_DE
  at 
java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:836)

Resolved by Gary in r424820
 * http://svn.apache.org/viewvc?rev=424820&view=rev




> Convert the Shale build to Maven 2
> --
>
> Key: SHALE-179
> URL: http://issues.apache.org/struts/browse/SHALE-179
> Project: Shale
>  Issue Type: Task
>  Components: Core, Clay, Remoting, Tiger, Test, Examples, 
> Documentation, Website
>Reporter: Wendy Smoak
> Fix For: 1.0.3
>
>
> Convert the Shale project structure and build to Maven 2.

-- 
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: (SHALE-230) Restore publishing the dialog-config_1.0.dtd file (and any other DTDs defined by Shale)

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-230?page=comments#action_37824 ] 

Wendy Smoak commented on SHALE-230:
---


Copying the dtds for the website (and the release distribution) was recently 
added to the Struts 1 build, and that config can be adopted for Shale.

(Publishing the dtds on the website was never part of the build process before, 
it was done manually.)

> Restore publishing the dialog-config_1.0.dtd file (and any other DTDs defined 
> by Shale)
> ---
>
> Key: SHALE-230
> URL: http://issues.apache.org/struts/browse/SHALE-230
> Project: Shale
>  Issue Type: Bug
>  Components: Website
>Affects Versions: 1.0.2
>Reporter: Craig McClanahan
> Fix For: 1.0.3
>
>
> As part of our transition to the shale.apache.org website, it appears that 
> publishing the DTD for dialog configuration (to subdirectory "dtds" on the 
> website) got inadvertently dropped.  It needs to be restored to the build 
> process.

-- 
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] Reopened: (SHALE-210) Adding JMock environment for convenience

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-210?page=all ]

Wendy Smoak reopened SHALE-210:
---

 
Reopening for possible renaming.
See: 
http://www.nabble.com/Shale-Test-and-AbstractJsfTestCase%28s%29-t1968684.html

> Adding JMock environment for convenience
> 
>
> Key: SHALE-210
> URL: http://issues.apache.org/struts/browse/SHALE-210
> Project: Shale
>  Issue Type: New Feature
>  Components: Test
>Affects Versions: 1.0.3
>Reporter: Matthias Wessendorf
> Assigned To: Matthias Wessendorf
> Fix For: 1.0.3, Nightly
>
> Attachments: jmock_base_clazz.patch, jmock_base_clazz.patch, 
> jmock_shale_test.patch, jmock_shale_test.patch
>
>
> Having a clazz like AbstractJMockJsfTestCase is a nice convenience for people 
> are interested in using JMock.
> for some reasons this approach is needed.

-- 
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: (SHALE-227) Restructure the svn repo to establish a 'sandbox' and separate the 'maven' module from the framework

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-227?page=all ]

Wendy Smoak updated SHALE-227:
--

Assignee: (was: Wendy Smoak)

Un-assigning this as I'm not going to get to it tonight.

> Restructure the svn repo to establish a 'sandbox' and separate the 'maven' 
> module from the framework
> 
>
> Key: SHALE-227
> URL: http://issues.apache.org/struts/browse/SHALE-227
> Project: Shale
>  Issue Type: Task
>Affects Versions: Nightly
>Reporter: Wendy Smoak
> Fix For: 1.0.3
>
>
> Proposed organization:
>   
> shale/framework/trunk
> shale/maven/trunk
> shale/sandbox
> Discussion thread: 
> http://www.mail-archive.com/dev%40shale.apache.org/msg00161.html

-- 
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] Created: (SHALE-227) Restructure the svn repo to establish a 'sandbox' and separate the 'maven' module from the framework

[Wendy Smoak (JIRA)]

Restructure the svn repo to establish a 'sandbox' and separate the 'maven' 
module from the framework


 Key: SHALE-227
 URL: http://issues.apache.org/struts/browse/SHALE-227
 Project: Shale
  Issue Type: Task
Affects Versions: Nightly
Reporter: Wendy Smoak
 Assigned To: Wendy Smoak
 Fix For: 1.0.3


Proposed organization:
  
shale/framework/trunk
shale/maven/trunk
shale/sandbox

Discussion thread: 
http://www.mail-archive.com/dev%40shale.apache.org/msg00161.html

-- 
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: (SHALE-221) Make build environment support JSF RI 1.2 as an option for the JSF dependency

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-221?page=comments#action_37762 ] 

Wendy Smoak commented on SHALE-221:
---

Done using the available snapshots and JSP 2.1 from Mortbay:  
http://svn.apache.org/viewvc?rev=422615&view=rev

We'll leave this open until the correct jars are available.

> Make build environment support JSF RI 1.2 as an option for the JSF dependency
> -
>
> Key: SHALE-221
> URL: http://issues.apache.org/struts/browse/SHALE-221
> Project: Shale
>  Issue Type: Task
>Affects Versions: 1.0.2
>Reporter: Craig McClanahan
> Assigned To: Wendy Smoak
> Fix For: 1.0.3
>
>
> Version 1.2 of the JSF RI is available in a Maven repository at java.net, so 
> it should be made possible to optionally build Shale against this version as 
> well as MyFaces 1.1 (the default) and the JSF RI 1.1.

-- 
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: (SHALE-221) Make build environment support JSF RI 1.2 as an option for the JSF dependency

[Wendy Smoak (JIRA)]

[ 
http://issues.apache.org/struts/browse/SHALE-221?page=comments#action_37759 ] 

Wendy Smoak commented on SHALE-221:
---

Is there a released version?  I only see snapshots here:  
https://maven-repository.dev.java.net/repository/javax.faces/jars/



> Make build environment support JSF RI 1.2 as an option for the JSF dependency
> -
>
> Key: SHALE-221
> URL: http://issues.apache.org/struts/browse/SHALE-221
> Project: Shale
>  Issue Type: Task
>Affects Versions: 1.0.2
>Reporter: Craig McClanahan
> Assigned To: Wendy Smoak
> Fix For: 1.0.3
>
>
> Version 1.2 of the JSF RI is available in a Maven repository at java.net, so 
> it should be made possible to optionally build Shale against this version as 
> well as MyFaces 1.1 (the default) and the JSF RI 1.1.

-- 
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] Assigned: (SHALE-221) Make build environment support JSF RI 1.2 as an option for the JSF dependency

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-221?page=all ]

Wendy Smoak reassigned SHALE-221:
-

Assignee: Wendy Smoak

> Make build environment support JSF RI 1.2 as an option for the JSF dependency
> -
>
> Key: SHALE-221
> URL: http://issues.apache.org/struts/browse/SHALE-221
> Project: Shale
>  Issue Type: Task
>Affects Versions: 1.0.2
>Reporter: Craig McClanahan
> Assigned To: Wendy Smoak
> Fix For: 1.0.3
>
>
> Version 1.2 of the JSF RI is available in a Maven repository at java.net, so 
> it should be made possible to optionally build Shale against this version as 
> well as MyFaces 1.1 (the default) and the JSF RI 1.1.

-- 
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: (SHALE-218) Change dtd doctype URLs to shale.apache.org

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-218?page=all ]

Wendy Smoak updated SHALE-218:
--

Description: 
Change the dtd DOCTYPE URLs to shale.apache.org rather than 
struts.apache.org/shale.

Rename dialog.dtd to shale-dialog-config_1_0.dtd and update ConfigurationParser.

Publish the dtds to http://shale.apache.org/dtds as part of the website build.

  was:
Change the dtd DOCTYPE URLs to shale.apache.org rather than 
struts.apache.org/shale.

Rename dialog.dtd to shale-dialog-config.dtd and update ConfigurationParser.

Publish the dtds to http://shale.apache.org/dtds as part of the website build.


Fixed dialog dtd filename.

> Change dtd doctype URLs to shale.apache.org
> ---
>
> Key: SHALE-218
> URL: http://issues.apache.org/struts/browse/SHALE-218
> Project: Shale
>  Issue Type: Task
>  Components: Core, Clay, Dialog
>Affects Versions: Nightly
>Reporter: Wendy Smoak
> Assigned To: Gary VanMatre
> Fix For: 1.0.3
>
>
> Change the dtd DOCTYPE URLs to shale.apache.org rather than 
> struts.apache.org/shale.
> Rename dialog.dtd to shale-dialog-config_1_0.dtd and update 
> ConfigurationParser.
> Publish the dtds to http://shale.apache.org/dtds as part of the website build.

-- 
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] Created: (SHALE-219) Add xsd for Clay html namespace support

[Wendy Smoak (JIRA)]

Add xsd for Clay html namespace support
---

 Key: SHALE-219
 URL: http://issues.apache.org/struts/browse/SHALE-219
 Project: Shale
Type: Task

  Components: Clay  
Versions: Nightly
Reporter: Wendy Smoak
Priority: Minor
 Fix For: 1.0.3


Gary: I have one XSD that I could publish for clay html namespace support.  In 
the future, we might have a couple more for Clay's version of the core and html 
schema.  The clay markup parser is not validating so these would only be needed 
for tool support.

Publish xsd files with the website at http://shale.apache.org/xml/clay



-- 
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] Created: (SHALE-218) Change dtd doctype URLs to shale.apache.org

[Wendy Smoak (JIRA)]

Change dtd doctype URLs to shale.apache.org
---

 Key: SHALE-218
 URL: http://issues.apache.org/struts/browse/SHALE-218
 Project: Shale
Type: Task

  Components: Core, Clay, Dialog  
Versions: Nightly
Reporter: Wendy Smoak
 Fix For: 1.0.3


Change the dtd DOCTYPE URLs to shale.apache.org rather than 
struts.apache.org/shale.

Rename dialog.dtd to shale-dialog-config.dtd and update ConfigurationParser.

Publish the dtds to http://shale.apache.org/dtds as part of the website build.

-- 
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: (SHALE-211) Add Shale to the projects.apache.org site

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-211?page=all ]

Wendy Smoak updated SHALE-211:
--

Assign To: James Mitchell

> Add Shale to the projects.apache.org site
> -
>
>  Key: SHALE-211
>  URL: http://issues.apache.org/struts/browse/SHALE-211
>  Project: Shale
> Type: Task

>   Components: Documentation
> Reporter: Wendy Smoak
> Assignee: James Mitchell
> Priority: Minor
>  Fix For: 1.0.3

>
> We should be listed on projects.apache.org.  There is a utility to create the 
> file:  http://projects.apache.org/create.html
> shale/trunk/src/site/resources seems like a good place for it.

-- 
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: (SHALE-211) Add Shale to the projects.apache.org site

[Wendy Smoak (JIRA)]

 [ http://issues.apache.org/struts/browse/SHALE-211?page=all ]
 
Wendy Smoak resolved SHALE-211:
---

Fix Version: 1.0.3
 Resolution: Fixed

http://svn.apache.org/viewvc?rev=420032&view=rev

http://svn.apache.org/viewvc?rev=420034&view=rev

> Add Shale to the projects.apache.org site
> -
>
>  Key: SHALE-211
>  URL: http://issues.apache.org/struts/browse/SHALE-211
>  Project: Shale
> Type: Task

>   Components: Documentation
> Reporter: Wendy Smoak
> Priority: Minor
>  Fix For: 1.0.3

>
> We should be listed on projects.apache.org.  There is a utility to create the 
> file:  http://projects.apache.org/create.html
> shale/trunk/src/site/resources seems like a good place for it.

-- 
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] Created: (SHALE-211) Add Shale to the projects.apache.org site

[Wendy Smoak (JIRA)]

Add Shale to the projects.apache.org site
-

 Key: SHALE-211
 URL: http://issues.apache.org/struts/browse/SHALE-211
 Project: Shale
Type: Task

  Components: Documentation  
Reporter: Wendy Smoak
Priority: Minor


We should be listed on projects.apache.org.  There is a utility to create the 
file:  http://projects.apache.org/create.html

shale/trunk/src/site/resources seems like a good place for it.

-- 
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