Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2)
If so, maybe the best thing to provide is a portlet wrapper that can work with an s2 app (similar to MyFacesGenericPortlet for MyFaces). Then let the portal vendors provide the deployment script. From my limited knowledge of Portlets, I think this is what Struts2 / WebWork is doing. There's a Jsr168Dispatcher that work as a controller dispatching portlet request to WebWork/Struts2. Nils and Rainer could provide more useful information on this. :-) - Original Message From: Greg Reddin [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Monday, 24 July, 2006 12:39:03 AM Subject: Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2) On Jul 22, 2006, at 7:29 PM, Ted Husted wrote: What about this? * http://www.twdata.org/backups/WW/how-to-build-the-portlet-war-for- a-specific-portal-server.html Meanwhile, what's involved in setting up Tomcat 5.5. for portlets? It's a bit more involved than just getting portlets to work in Tomcat. You have to install a portal server like Liferay, Jetspeed, or JBoss Portal. Liferay can be downloaded as a bundle that includes Tomcat. Jetspeed portals can be deployed into Tomcat using Maven 1 (They may have upgraded their scripts to m2 or ant. There was some talk about that but I'm not real sure where it went.) JBoss Portal comes with JBoss, of course. Liferay also has an ant portlet deployment script that you can use. It seems to me that portlet deployment is more of a function of the portal server than the framework. Is this question related to deploying a Struts 2.0 app as a portlet? If so, maybe the best thing to provide is a portlet wrapper that can work with an s2 app (similar to MyFacesGenericPortlet for MyFaces). Then let the portal vendors provide the deployment script. Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2)
About the ant build that creating a skeleton for various portlet container, what if we build a maven arcetype specific for each of the portlet container? Maybe, mvn archetype:create .. portlet-liferay-archetype-starter will create a template/skeleton for liferay portal, just like what we did for struts2-archetype-starter. What do you guys think, feasible? - Original Message From: tm jee [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Monday, 24 July, 2006 10:35:47 PM Subject: Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2) If so, maybe the best thing to provide is a portlet wrapper that can work with an s2 app (similar to MyFacesGenericPortlet for MyFaces). Then let the portal vendors provide the deployment script. From my limited knowledge of Portlets, I think this is what Struts2 / WebWork is doing. There's a Jsr168Dispatcher that work as a controller dispatching portlet request to WebWork/Struts2. Nils and Rainer could provide more useful information on this. :-) - Original Message From: Greg Reddin [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Monday, 24 July, 2006 12:39:03 AM Subject: Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2) On Jul 22, 2006, at 7:29 PM, Ted Husted wrote: What about this? * http://www.twdata.org/backups/WW/how-to-build-the-portlet-war-for- a-specific-portal-server.html Meanwhile, what's involved in setting up Tomcat 5.5. for portlets? It's a bit more involved than just getting portlets to work in Tomcat. You have to install a portal server like Liferay, Jetspeed, or JBoss Portal. Liferay can be downloaded as a bundle that includes Tomcat. Jetspeed portals can be deployed into Tomcat using Maven 1 (They may have upgraded their scripts to m2 or ant. There was some talk about that but I'm not real sure where it went.) JBoss Portal comes with JBoss, of course. Liferay also has an ant portlet deployment script that you can use. It seems to me that portlet deployment is more of a function of the portal server than the framework. Is this question related to deploying a Struts 2.0 app as a portlet? If so, maybe the best thing to provide is a portlet wrapper that can work with an s2 app (similar to MyFacesGenericPortlet for MyFaces). Then let the portal vendors provide the deployment script. Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2)
On Jul 24, 2006, at 9:47 AM, tm jee wrote: About the ant build that creating a skeleton for various portlet container, what if we build a maven arcetype specific for each of the portlet container? Maybe, mvn archetype:create .. portlet-liferay-archetype-starter will create a template/skeleton for liferay portal, just like what we did for struts2-archetype-starter. What do you guys think, feasible? To me this is no different than building maven archetypes to deploy a Struts app into specific app servers. Do we want to provide tools with the framework to deploy apps into Tomcat, JBoss, WebLogic, etc. or do we just use tools provided by the server vendors and provide documentation to help people use them? Honestly, I don't know what the WebWork approach has been in the past. I think with Struts, we've just provided helper documentation for those kinds of things. With portlets I'm learning there are multiple levels of integration. There are bridges that help you turn your app into a portlet: i.e. a Struts-portlet bridge, a JSF-portlet bridge, etc. That's what the MyFacesGenericPortlet class is and the Apache Portals Bridges subproject[1]. Then, there's portlet integration with various portal vendors. JBoss, Liferay, Jetspeed, BEA, IBM, Oracle, etc. all have their own deployment strategies. (Sorry if I'm bombarding you with information you already know. I'm just now going deep with portlets and portals). With Liferay, for example, you create a liferay- portlet.xml and a liferay-display.xml and they provide an ant script that turns your .war file into a Liferay portlet and hot deploy it. With JBoss (IIRC) you create a jboss-portlet.xml and drop your .war file in the right directory. I can't remember the process with Jetspeed. And I haven't tried any of the others. Given what I've learned so far, my preferred approach would be to write a generic bridge to ensure that Struts apps could work within portlets with as little difficulty as possible. I'm getting closer to being able to just drop a JSF app into a portal using the vendor- provided deployment strategy. That would be the ideal for me. I never (or very rarely) will have to write a portlet if I can help it. I just write to my favorite framework and I can deploy it as a web app or as a portlet. Thoughts? Greg [1] http://portals.apache.org/bridges/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2)
On 7/24/06, Greg Reddin [EMAIL PROTECTED] wrote: Honestly, I don't know what the WebWork approach has been in the past. I think with Struts, we've just provided helper documentation for those kinds of things. There's a portlet tutorial here: * http://www.twdata.org/backups/WW/portlet-tutorial.html I was just wondering if there were a quick and easy way to deploy the portlet example on Tomcat 5.5, so that I could test it for the 2.0.x distributions. Documentation-wise, I'm begining to think we might want to segregate the portlet material into its own guide, since it sounds like a rarified topic. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2)
I'd love to be able to use a Maven plugin, like the Jetty one, to easily test the portlet w/o any extra installation. Using 'mvn jetty6:run-war is just too handy. This is one of my many personal todo projects :) Don Ted Husted wrote: On 7/24/06, Greg Reddin [EMAIL PROTECTED] wrote: Honestly, I don't know what the WebWork approach has been in the past. I think with Struts, we've just provided helper documentation for those kinds of things. There's a portlet tutorial here: * http://www.twdata.org/backups/WW/portlet-tutorial.html I was just wondering if there were a quick and easy way to deploy the portlet example on Tomcat 5.5, so that I could test it for the 2.0.x distributions. Documentation-wise, I'm begining to think we might want to segregate the portlet material into its own guide, since it sounds like a rarified topic. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2)
This bridge is really what exists today in Struts 2/WebWork 2. You can write an app, test it in Tomcat as a webapp, then run it as a portlet without any code changes. I think what Toby is talking about is helping with the extra configuration files that the different portals require. I think it is a good idea to create maven archetypes for each of the major portals, since they are really easy to create and make portlet development that much easier. The Maven archetype projects are currently outside the Struts 2.0 codebase, so their development wouldn't affect the Struts releases. Don Greg Reddin wrote: On Jul 24, 2006, at 9:47 AM, tm jee wrote: About the ant build that creating a skeleton for various portlet container, what if we build a maven arcetype specific for each of the portlet container? Maybe, mvn archetype:create .. portlet-liferay-archetype-starter will create a template/skeleton for liferay portal, just like what we did for struts2-archetype-starter. What do you guys think, feasible? To me this is no different than building maven archetypes to deploy a Struts app into specific app servers. Do we want to provide tools with the framework to deploy apps into Tomcat, JBoss, WebLogic, etc. or do we just use tools provided by the server vendors and provide documentation to help people use them? Honestly, I don't know what the WebWork approach has been in the past. I think with Struts, we've just provided helper documentation for those kinds of things. With portlets I'm learning there are multiple levels of integration. There are bridges that help you turn your app into a portlet: i.e. a Struts-portlet bridge, a JSF-portlet bridge, etc. That's what the MyFacesGenericPortlet class is and the Apache Portals Bridges subproject[1]. Then, there's portlet integration with various portal vendors. JBoss, Liferay, Jetspeed, BEA, IBM, Oracle, etc. all have their own deployment strategies. (Sorry if I'm bombarding you with information you already know. I'm just now going deep with portlets and portals). With Liferay, for example, you create a liferay-portlet.xml and a liferay-display.xml and they provide an ant script that turns your .war file into a Liferay portlet and hot deploy it. With JBoss (IIRC) you create a jboss-portlet.xml and drop your .war file in the right directory. I can't remember the process with Jetspeed. And I haven't tried any of the others. Given what I've learned so far, my preferred approach would be to write a generic bridge to ensure that Struts apps could work within portlets with as little difficulty as possible. I'm getting closer to being able to just drop a JSF app into a portal using the vendor-provided deployment strategy. That would be the ideal for me. I never (or very rarely) will have to write a portlet if I can help it. I just write to my favorite framework and I can deploy it as a web app or as a portlet. Thoughts? Greg [1] http://portals.apache.org/bridges/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2)
On 7/24/06, Don Brown [EMAIL PROTECTED] wrote: I'd love to be able to use a Maven plugin, like the Jetty one, to easily test the portlet w/o any extra installation. Using 'mvn jetty6:run-war is just too handy. This is one of my many personal todo projects :) Don I believe the Pluto 1.1 project is developing a m2 plugin that will do something like that. Take a look at http://portals.apache.org/pluto/v11/deploying.html. As for other portal containers, it shouldn't be a big problem generating the deployment descriptors needed with some m2 magic. Nils-H
Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2)
Yeah, that is a step, but to really make it useful, it should work without Tomcat and/or Pluto installed anywhere on the hard drive. The Jetty plugin embeds Jetty so that no external files are needed. Don Nils-Helge Garli wrote: On 7/24/06, Don Brown [EMAIL PROTECTED] wrote: I'd love to be able to use a Maven plugin, like the Jetty one, to easily test the portlet w/o any extra installation. Using 'mvn jetty6:run-war is just too handy. This is one of my many personal todo projects :) Don I believe the Pluto 1.1 project is developing a m2 plugin that will do something like that. Take a look at http://portals.apache.org/pluto/v11/deploying.html. As for other portal containers, it shouldn't be a big problem generating the deployment descriptors needed with some m2 magic. Nils-H - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2)
On Jul 22, 2006, at 7:29 PM, Ted Husted wrote: What about this? * http://www.twdata.org/backups/WW/how-to-build-the-portlet-war-for- a-specific-portal-server.html Meanwhile, what's involved in setting up Tomcat 5.5. for portlets? It's a bit more involved than just getting portlets to work in Tomcat. You have to install a portal server like Liferay, Jetspeed, or JBoss Portal. Liferay can be downloaded as a bundle that includes Tomcat. Jetspeed portals can be deployed into Tomcat using Maven 1 (They may have upgraded their scripts to m2 or ant. There was some talk about that but I'm not real sure where it went.) JBoss Portal comes with JBoss, of course. Liferay also has an ant portlet deployment script that you can use. It seems to me that portlet deployment is more of a function of the portal server than the framework. Is this question related to deploying a Struts 2.0 app as a portlet? If so, maybe the best thing to provide is a portlet wrapper that can work with an s2 app (similar to MyFacesGenericPortlet for MyFaces). Then let the portal vendors provide the deployment script. Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Portlet App and Ant (was Re: Would like to remove Ant build from Struts 2)
What about this? * http://www.twdata.org/backups/WW/how-to-build-the-portlet-war-for-a-specific-portal-server.html Meanwhile, what's involved in setting up Tomcat 5.5. for portlets? -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Would like to remove Ant build from Struts 2
Don Brown proposed: I'd like to remove the Ant build from Struts 2. I don't think it has worked for a little while and the new Maven 2 layout discourages it for any complex builds. Unless someone seriously wants to put the effort into keeping it up, I think it should be removed. From the peanut gallery, I would like to see a minimal Ant build kept so that users would be able to download the Struts 2 source, patch it for their needs, and build a working jar file. I think that Ant is much more commonly used than Maven 2, that it's valuable for users to be able to try small changes to suit their needs, and that requiring Maven 2 significantly raises the work required to do so. Perhaps I am wrong, and either maintaining such a minimal Ant build is prohibitively expensive or installing and learning Maven 2 is trivially easy. - George - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
It realy comes down to managing the dependencies. I could forsee someone building an ant build that ran against the compiled code and dependencies. (Similar to Atlassians build system with JIRA.) However I personally dont think its appropriate to be part of the project. (At least not as a source level) As someone whom fought to keep ant (and even managed to supply a few patches to fix the unit tests and the build at the begining of SAF2) my feeling is that managing ant, ivy, and maven just isn't worth the effort. Any developer whom needs to patch the source is going to be able to handle maven. Just my .02. Cheers, Eric On 7/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Don Brown proposed: I'd like to remove the Ant build from Struts 2. I don't think it has worked for a little while and the new Maven 2 layout discourages it for any complex builds. Unless someone seriously wants to put the effort into keeping it up, I think it should be removed. From the peanut gallery, I would like to see a minimal Ant build kept so that users would be able to download the Struts 2 source, patch it for their needs, and build a working jar file. I think that Ant is much more commonly used than Maven 2, that it's valuable for users to be able to try small changes to suit their needs, and that requiring Maven 2 significantly raises the work required to do so. Perhaps I am wrong, and either maintaining such a minimal Ant build is prohibitively expensive or installing and learning Maven 2 is trivially easy. - George - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
The one case I wouldn't mind seeing an Ant build is in the source distribution. Many times, I'm downloading source distros, and have to make some change, but I'm on a network where I don't have connectivity to the outside world. If we could make a source distro that was completely self-contained, complete with an Ant build, I'd be fine with that. Don Eric Molitor wrote: It realy comes down to managing the dependencies. I could forsee someone building an ant build that ran against the compiled code and dependencies. (Similar to Atlassians build system with JIRA.) However I personally dont think its appropriate to be part of the project. (At least not as a source level) As someone whom fought to keep ant (and even managed to supply a few patches to fix the unit tests and the build at the begining of SAF2) my feeling is that managing ant, ivy, and maven just isn't worth the effort. Any developer whom needs to patch the source is going to be able to handle maven. Just my .02. Cheers, Eric On 7/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Don Brown proposed: I'd like to remove the Ant build from Struts 2. I don't think it has worked for a little while and the new Maven 2 layout discourages it for any complex builds. Unless someone seriously wants to put the effort into keeping it up, I think it should be removed. From the peanut gallery, I would like to see a minimal Ant build kept so that users would be able to download the Struts 2 source, patch it for their needs, and build a working jar file. I think that Ant is much more commonly used than Maven 2, that it's valuable for users to be able to try small changes to suit their needs, and that requiring Maven 2 significantly raises the work required to do so. Perhaps I am wrong, and either maintaining such a minimal Ant build is prohibitively expensive or installing and learning Maven 2 is trivially easy. - George - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Would like to remove Ant build from Struts 2
That's precisely the sort of scenario I had in mind. - George Don Brown wrote: The one case I wouldn't mind seeing an Ant build is in the source distribution. Many times, I'm downloading source distros, and have to make some change, but I'm on a network where I don't have connectivity to the outside world. If we could make a source distro that was completely self-contained, complete with an Ant build, I'd be fine with that. Don Eric Molitor wrote: It realy comes down to managing the dependencies. I could forsee someone building an ant build that ran against the compiled code and dependencies. (Similar to Atlassians build system with JIRA.) However I personally dont think its appropriate to be part of the project. (At least not as a source level) As someone whom fought to keep ant (and even managed to supply a few patches to fix the unit tests and the build at the begining of SAF2) my feeling is that managing ant, ivy, and maven just isn't worth the effort. Any developer whom needs to patch the source is going to be able to handle maven. Just my .02. Cheers, Eric On 7/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Don Brown proposed: I'd like to remove the Ant build from Struts 2. I don't think it has worked for a little while and the new Maven 2 layout discourages it for any complex builds. Unless someone seriously wants to put the effort into keeping it up, I think it should be removed. From the peanut gallery, I would like to see a minimal Ant build kept so that users would be able to download the Struts 2 source, patch it for their needs, and build a working jar file. I think that Ant is much more commonly used than Maven 2, that it's valuable for users to be able to try small changes to suit their needs, and that requiring Maven 2 significantly raises the work required to do so. Perhaps I am wrong, and either maintaining such a minimal Ant build is prohibitively expensive or installing and learning Maven 2 is trivially easy. - George - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
FYI, you can get a similar auto-downloading of dependencies with an Ant script using the ant-dependencies task: http://www.httpunit.org/doc/dependencies.html For a working example, see the build script for Java Web Parts: http://javawebparts.sourceforge.net This actually downloads from the Maven repo, for a bit of irony :) I personally wouldn't mind seeing a minimal Ant script maintained either, but frankly, Maven is easy enough to install and work with that I don't really see it being a big hassle for anyone, so I'm essentially with Eric. Perhaps just adding one minimal goal that someone could use in place of an Ant script would do? (I'm not too familiar with Maven, I'm guessing this might already be present? Just a matter of telling people how to do it). Frank Eric Molitor wrote: It realy comes down to managing the dependencies. I could forsee someone building an ant build that ran against the compiled code and dependencies. (Similar to Atlassians build system with JIRA.) However I personally dont think its appropriate to be part of the project. (At least not as a source level) As someone whom fought to keep ant (and even managed to supply a few patches to fix the unit tests and the build at the begining of SAF2) my feeling is that managing ant, ivy, and maven just isn't worth the effort. Any developer whom needs to patch the source is going to be able to handle maven. Just my .02. Cheers, Eric On 7/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Don Brown proposed: I'd like to remove the Ant build from Struts 2. I don't think it has worked for a little while and the new Maven 2 layout discourages it for any complex builds. Unless someone seriously wants to put the effort into keeping it up, I think it should be removed. From the peanut gallery, I would like to see a minimal Ant build kept so that users would be able to download the Struts 2 source, patch it for their needs, and build a working jar file. I think that Ant is much more commonly used than Maven 2, that it's valuable for users to be able to try small changes to suit their needs, and that requiring Maven 2 significantly raises the work required to do so. Perhaps I am wrong, and either maintaining such a minimal Ant build is prohibitively expensive or installing and learning Maven 2 is trivially easy. - George - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] Java Web Parts - http://javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
+1 for this I'm surprised Maven can't build a source distribution with a bundled standard ant build with maven dependency ant task calls. I'd think this would be a common need. The one case I wouldn't mind seeing an Ant build is in the source distribution. Many times, I'm downloading source distros, and have to make some change, but 'm on a network where I don't have connectivity to the outside world. If we could make a source distro that was completely self-contained, complete with an Ant build, I'd be fine with that. Don - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=36712messageID=72369#72369 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
What about using the Maven2 ant tasks and integrating that way? I just started reading http://maven.apache.org/ant-tasks.html this morning. artifact:dependencies filesetId=my.dependency.fileset verbose=true pom id=project file=pom.xml/ /artifact:dependencies Of course you'll need maven and ant... On 7/10/06, Don Brown [EMAIL PROTECTED] wrote: The one case I wouldn't mind seeing an Ant build is in the source distribution. Many times, I'm downloading source distros, and have to make some change, but I'm on a network where I don't have connectivity to the outside world. If we could make a source distro that was completely self-contained, complete with an Ant build, I'd be fine with that. Don Eric Molitor wrote: It realy comes down to managing the dependencies. I could forsee someone building an ant build that ran against the compiled code and dependencies. (Similar to Atlassians build system with JIRA.) However I personally dont think its appropriate to be part of the project. (At least not as a source level) As someone whom fought to keep ant (and even managed to supply a few patches to fix the unit tests and the build at the begining of SAF2) my feeling is that managing ant, ivy, and maven just isn't worth the effort. Any developer whom needs to patch the source is going to be able to handle maven. Just my .02. Cheers, Eric On 7/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Don Brown proposed: I'd like to remove the Ant build from Struts 2. I don't think it has worked for a little while and the new Maven 2 layout discourages it for any complex builds. Unless someone seriously wants to put the effort into keeping it up, I think it should be removed. From the peanut gallery, I would like to see a minimal Ant build kept so that users would be able to download the Struts 2 source, patch it for their needs, and build a working jar file. I think that Ant is much more commonly used than Maven 2, that it's valuable for users to be able to try small changes to suit their needs, and that requiring Maven 2 significantly raises the work required to do so. Perhaps I am wrong, and either maintaining such a minimal Ant build is prohibitively expensive or installing and learning Maven 2 is trivially easy. - George - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
On 7/10/06, Jason Carreira [EMAIL PROTECTED] wrote: +1 for this I'm surprised Maven can't build a source distribution with a bundled standard ant build with maven dependency ant task calls. I'd think this would be a common need. A lot of Jakarta Commons projects deal with this sort of thing by having a developer run mvn ant:ant to create a build.xml that (in theory at least) replicates the functionality of the current Maven build environment, and then check that in. It seems to work fairly well on simple single module projects like your typical Commons library ... but I've never tried it in something as complicated as our build systems. Craig The one case I wouldn't mind seeing an Ant build is in the source distribution. Many times, I'm downloading source distros, and have to make some change, but 'm on a network where I don't have connectivity to the outside world. If we could make a source distro that was completely self-contained, complete with an Ant build, I'd be fine with that. Don - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=36712messageID=72369#72369 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
Ted, the javadocs problem may be the case, but remember we can get around those glitches by utilizing the ant plugin and doing that kind of stuff in Ant. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=36712messageID=72168#72168 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
So, would that also be a solution for Struts 1 aggregation too? * http://issues.apache.org/struts/browse/STR-2839 -Ted. On 7/9/06, Patrick Lightbody [EMAIL PROTECTED] wrote: Ted, the javadocs problem may be the case, but remember we can get around those glitches by utilizing the ant plugin and doing that kind of stuff in Ant. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
On 7/9/06, Ted Husted [EMAIL PROTECTED] wrote: So, would that also be a solution for Struts 1 aggregation too? * http://issues.apache.org/struts/browse/STR-2839 -Ted. On 7/9/06, Patrick Lightbody [EMAIL PROTECTED] wrote: Ted, the javadocs problem may be the case, but remember we can get around those glitches by utilizing the ant plugin and doing that kind of stuff in Ant. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
Probably, though I haven't looked in to it too much yet. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=36712messageID=72174#72174 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
Another issue for using Maven-only for Struts 2 right now today is aggregated Javadocs. It's very helpful to aggregate the XWork Javadocs with the Struts 2 Javadocs, and I understand Maven is broken in that regard right now. * http://issues.apache.org/struts/browse/STR-2839 -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Would like to remove Ant build from Struts 2
I'd like to remove the Ant build from Struts 2. I don't think it has worked for a little while and the new Maven 2 layout discourages it for any complex builds. Unless someone seriously wants to put the effort into keeping it up, I think it should be removed. Don - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
I think we should not remove these ant targets, - xdoclet-taglib - xdoclet-tagdocs They are used to generate the tld and docs for struts2 tags. - Original Message From: Don Brown [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Saturday, 8 July, 2006 9:00:41 AM Subject: Would like to remove Ant build from Struts 2 I'd like to remove the Ant build from Struts 2. I don't think it has worked for a little while and the new Maven 2 layout discourages it for any complex builds. Unless someone seriously wants to put the effort into keeping it up, I think it should be removed. Don - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
tm jee wrote: I think we should not remove these ant targets, - xdoclet-taglib - xdoclet-tagdocs They are used to generate the tld and docs for struts2 tags. On 7/7/06, Don Brown [EMAIL PROTECTED] wrote: We do that already with Maven 2 for Struts 1. I'm sure we could do the same here. Wendy? For the Struts 1 build, the tlds are the source documents, and taglib-maven-plugin generates the documentation. * http://maven-taglib.sourceforge.net/m2/index.html If you are currently generating the tlds from something else (I haven't looked...) then I'd suggest generating them one final time and committing them to src/main/resources/META-INF/tlds. (or META-INF/tld? Is there a standard location?) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Would like to remove Ant build from Struts 2
taglib-maven-plugin generates the documentation. If not mistaken, i think the taglib-macen-plugin generates document (html) from taglib.tld. The struts2 xdoclet-taglib ant task actually generates taglib.tld based on some tagging (eg. a2.tagattribute ) in the javadoc. If you are currently generating the tlds from something else (I haven't looked...) then I'd suggest generating them one final time and committing them to src/main/resources/META-INF/tlds. (or META-INF/tld? Is there a standard location?) In struts2, its in /src/main/resource/META-INF. The generated tld file will be in /src/main/resource/META-INF/taglib.tld. Do you mean that we generate the tld for the last time and don't use xdoclet-taglib ant task anymore, but instead alter the taglib.tld by hand? There's another xdoclet-tagdoc that generate some html files regarding the attribute a particular struts2 has. Its being refered to by snippets in confluence. I am not sure but i think it could be replaced by taglib-maven-plugin, but we need to figure out how to solve the snippet refered by confluence. regards - Original Message From: Wendy Smoak [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Saturday, 8 July, 2006 9:54:18 AM Subject: Re: Would like to remove Ant build from Struts 2 tm jee wrote: I think we should not remove these ant targets, - xdoclet-taglib - xdoclet-tagdocs They are used to generate the tld and docs for struts2 tags. On 7/7/06, Don Brown [EMAIL PROTECTED] wrote: We do that already with Maven 2 for Struts 1. I'm sure we could do the same here. Wendy? For the Struts 1 build, the tlds are the source documents, and taglib-maven-plugin generates the documentation. * http://maven-taglib.sourceforge.net/m2/index.html If you are currently generating the tlds from something else (I haven't looked...) then I'd suggest generating them one final time and committing them to src/main/resources/META-INF/tlds. (or META-INF/tld? Is there a standard location?) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
