Re: Continuous Build environment?
On 10/13/08, Brett Porter <[EMAIL PROTECTED]> wrote: > Continuum currently runs on Linux - I'm currently investigating > setting up a Windows server for the same. That would be very useful, if we could plan for running a Hudson agent on that server as well would be excellent. /niklas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL - OpenWebBeans Project Proposal]
Hi, First of all, there are lots of places that I could propose my project, but I think that open source development with the Apache Way conveys the real Free and Professional Open Source Project with meritrocracy in action. This code could be part of the Geronimo project as its Web Beans container, or could be the top level project its own. I only know that there is only one effort to create RI, this is the JBoss RI (Pete Muir is responsible for implementing, Gavin King for creating the spec) at the web side http://seamframework.org/WebBeans. And its implementation is in the early stage. Indeed, Apache way implementation makes different from the others, because and most importantly its developed based on the Apache Way and it also creates additions to the RI with creating add-on components that are based on the other Apache projects, such as, OpenEJB, OpenJPA, JSecurity, ActiveMQ etc, possible. Morevoer, It's always good to have multiple implementations of a spec so enterprise community benefits from the different imlpementations, and they choose the best (Like MyFaces and Sun JSF imeplemtnations.) I am ready for doing lots of work to this project progresses. Moreover, I get some great response from the below individuals to help this project succesfull, - Kevan Miller : As a mentor and partly committer - Conny Lundgren : JSR-299 EG member as a committer. And also, I think the committer number is increased by the time. As I said in the beginning, I believe that open source must be transparent, and the community appreciates the heavy working to implement this spec within the Apache Foundation. Sincerely; Gurkan Erdogdu - Original Message From: J Aaron Farr <[EMAIL PROTECTED]> To: general@incubator.apache.org Sent: Monday, October 13, 2008 8:13:05 AM Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] Gurkan Erdogdu <[EMAIL PROTECTED]> writes: > Hi to all; > > I have posted a proposal about the project, named OpenWebBeans. > > It is in the WIKI, its address is > http://wiki.apache.org/incubator/OpenWebBeansProposal I have a number of questions before I can support the proposal: Where do you expect this code / community to end up after the incubator? Will it be part of Geronimo? Part of MySpaces? It's own TLP? I can say now that if the project is to stand on its own, then there's a lot of work to do. It seems as though there are 2 or 3 other Apache licensed efforts in creating a RI for JSR-299: Gavin King's work, JBoss's work and the rumored Guice work. What makes this RI effort any different? Why should the ASF support this project instead of one of the others? I'm concerned that there's only one listed committer. Getting to at least 3 committers is going to have to be the first order of business for this podling. -- J Aaron Farrjadetower.com[US] +1 724-964-4515 馮傑仁cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continuous Build environment?
On Mon, Oct 13, 2008 at 8:00 AM, Brett Porter <[EMAIL PROTECTED]> wrote: > As others mentioned just drop a request into the INFRA JIRA, and > whether you want to use Continuum or Hudson. > > Continuum currently runs on Linux - I'm currently investigating > setting up a Windows server for the same. Hudson runs on Solaris but > I'm sure it could farm builds out to either of those as well if that > was set up. Thanks. We will discuss that further and get back when we are getting there. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL - OpenWebBeans Project Proposal]
Gurkan Erdogdu <[EMAIL PROTECTED]> writes: > Hi to all; > > I have posted a proposal about the project, named OpenWebBeans. > > It is in the WIKI, its address is > http://wiki.apache.org/incubator/OpenWebBeansProposal I have a number of questions before I can support the proposal: Where do you expect this code / community to end up after the incubator? Will it be part of Geronimo? Part of MySpaces? It's own TLP? I can say now that if the project is to stand on its own, then there's a lot of work to do. It seems as though there are 2 or 3 other Apache licensed efforts in creating a RI for JSR-299: Gavin King's work, JBoss's work and the rumored Guice work. What makes this RI effort any different? Why should the ASF support this project instead of one of the others? I'm concerned that there's only one listed committer. Getting to at least 3 committers is going to have to be the first order of business for this podling. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continuous Build environment?
As others mentioned just drop a request into the INFRA JIRA, and whether you want to use Continuum or Hudson. Continuum currently runs on Linux - I'm currently investigating setting up a Windows server for the same. Hudson runs on Solaris but I'm sure it could farm builds out to either of those as well if that was set up. Cheers, Brett 2008/10/13 Niclas Hedhman <[EMAIL PROTECTED]>: > Anyone has information about this?? > > Cheers > Niclas > > -- Forwarded message -- > From: James Dixson <[EMAIL PROTECTED]> > Date: Sun, Oct 12, 2008 at 9:48 PM > Subject: Continuous Build environment? > To: [EMAIL PROTECTED] > > > Does Apache have build-environment resources that we could leverage? Perhaps > a shared Atlassian Bamboo or Apache Continuum or similar? > > We are currently doing Etch builds continuously, but the build server is > locked behind our firewall here at Cisco. I would prefer to be able to have > the builds manageable by non-Cisco folks. > > I would like to see us building continuously on Windows and Linux and OSX. > > -- > James > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accepting OpenWebBeans into the Incubator
+1 Martijn -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continuous Build environment?
On Sun, Oct 12, 2008 at 5:29 PM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > Does Apache have build-environment resources that we could leverage? Perhaps > a shared Atlassian Bamboo or Apache Continuum or similar? As pointed our by Daniel, there is a Continuum install available as well as Hudson (http://hudson.zones.apache.org/hudson/) and the Geronimo guys seems to be setting up AntHill, do know if the idea is to open that up to all projects. > I would like to see us building continuously on Windows and Linux and OSX. This interests me as well. As a user of Hudson, would it be possible to have build agents on other OSes than the one currently used (Solaris)? /niklas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continuous Build environment?
-> http://www.apache.org/dev/ -> http://vmbuild.apache.org/continuum/groupSummary.action If Etch has not been already added to Continuum you might need to talk to the infra folks... Cheers Daniel On Sun, Oct 12, 2008 at 11:29 AM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > Anyone has information about this?? > > Cheers > Niclas > > -- Forwarded message -- > From: James Dixson <[EMAIL PROTECTED]> > Date: Sun, Oct 12, 2008 at 9:48 PM > Subject: Continuous Build environment? > To: [EMAIL PROTECTED] > > > Does Apache have build-environment resources that we could leverage? Perhaps > a shared Atlassian Bamboo or Apache Continuum or similar? > > We are currently doing Etch builds continuously, but the build server is > locked behind our firewall here at Cisco. I would prefer to be able to have > the builds manageable by non-Cisco folks. > > I would like to see us building continuously on Windows and Linux and OSX. > > -- > James > > - > 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: [VOTE] Accepting OpenWebBeans into the Incubator
On Sun, Oct 12, 2008 at 10:50 PM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: > Incubator PMC, > > Please vote on accepting the OpenWebBeans project for incubation. The full > OpenWebBeans proposal is available at the end of this message and as a wiki > page at http://wiki.apache.org/incubator/OpenWebBeansProposal. > > Here is my +1 +1 (binding) to accept OpenWebBeans for incubation. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: Continuous Build environment?
Anyone has information about this?? Cheers Niclas -- Forwarded message -- From: James Dixson <[EMAIL PROTECTED]> Date: Sun, Oct 12, 2008 at 9:48 PM Subject: Continuous Build environment? To: [EMAIL PROTECTED] Does Apache have build-environment resources that we could leverage? Perhaps a shared Atlassian Bamboo or Apache Continuum or similar? We are currently doing Etch builds continuously, but the build server is locked behind our firewall here at Cisco. I would prefer to be able to have the builds manageable by non-Cisco folks. I would like to see us building continuously on Windows and Linux and OSX. -- James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Accepting OpenWebBeans into the Incubator
Incubator PMC, Please vote on accepting the OpenWebBeans project for incubation. The full OpenWebBeans proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/OpenWebBeansProposal. Here is my +1 = OpenWebBeans, Web Beans Container Implementation = === Abstract === Open Web Beans will be an ASL-licensed implementation of the Web Beans Specification which is defined as JSR-299. . === Proposal === Web Beans specification is an effort for defining stateful, contextual component models and its management for the enterprise applications that run on the Java EE 6 containers. It is a big step that it unifies the EJB (Enterprise Java Beans) and JSF (Java Server Faces) standart component models easily with simplifying the complex programming model from the developer perspective. Currently there is no standard based approach for integrating EJB session beans as a JSF based managed bean. Moreover, EJB does not define any contextual component model. Developer is responsible for managing all the lifecycle of the EJB components. Web Beans provides the management and lifecycle of the components within the container with a standart fashion. It uses the Java 5.0 annotation capability to further easing the configuration efforts. Altough Web Beans simplifies the EJB programming model within the enterprise projects, it could also be used outside of the Java EE containers, such as Apache Tomcat with its powerful component and context model. Open Web Beans Project is responsible for implementing the runtime container contract for the Web Beans specification. Besides the implementation, Open Web Beans Project will implement the core built-in components that further simplifies the developer complex interactions with other Java EE specific enterprise operations. For example, it defines the JMS (Java Messaging Service) Web Beans Component used for enterprise messaging, Logging Component for logging, Security Component for security etc. === Background === The development of this project is started by the individual developer as an open source project that is hosted on the sourceforge. Using the Open Web Beans project, enterprise developers unifies the EJB and JSF technlogies together easily. Neither of these standarts solves the all problems of the Java EE environment. While the EJB components solves the security, transactions, concurrency and scalability problems, JSF defines the web-tier presentation framework with its graphical component models, events and managed bean facility. Web Beans enables the developers to unify these component models easily within well defined semantics. Applications that uses the Open Web Beans Project may get more advanced context and component model provided by the project. === Rationale === Current Web Beans specificatin is in the EDR (Early Draft Review) level now, and no reference implementation is available yet. Introducing the early implementation of the specification to the enterprise community with using other Apache related projects, such as Open EJB, Open JPA and MyFaces, will attract a diverse community. Moreover, Open Web Beans will work closely with the other Apache projects such that it depends on the Open EJB, Open JPA and My Faces. Moreover, Geronimo may include it as a Web Beans Container when it implements Java EE 6 specification as a runtime environment in which Web Beans executes. Current Web Beans specification may be used in the Java EE 5 environment. Its very powerful type safe and EL component model injection mechanisms and other very useful stuffs could attracts the community that will use it in their current enterprise projects. === Initial Goals === The initial goals of the Open Web Beans Project are * Fully implement the JSR-299 specification. * Attracts a community around the current code base. * Active relationship with the other dependent projects to further develop some useful Web Beans Components. == Current Status == === Meritocracy === Initial developer of the project is familiar with the meritocracy principles of Apache. He knows that the open source gets power from its great developers and freedom. He also developed some other open source projects. We will follow the normal meritocracy rules also with other potential contributors. === Community === There is a great community within the Open EJB, Open JPA, Geronimo and MyFaces Apache projects. Open Web Beans project is very related with these projects and in the some cases, it enhances these projects. We are thinking that Open Web Beans project gets strong community because it simplifies and unifies the using of these projects. It simplifies the developer effort for building complex enterprise applications. === Core Developers === Open Web Beans project has been developing by the open source developer Gurkan Erdogdu as a sole contributor. === Alignment === Open Web Beans project will be a ca
[jira] Updated: (INCUBATOR-90) Create a Etch project in JIRA under Incubator category
[ https://issues.apache.org/jira/browse/INCUBATOR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman updated INCUBATOR-90: Description: * Create "Etch Notification" scheme. * Create the project * Add etch-developers group * Set the "Permission Scheme" to "Standard Permissions" * Set the "Notification Scheme" to "Etch Notification" * Add Project Roles; - Committers = etch-developers - PMC = the individual mentors (i.e. no group) was: * Create "Etch Notification" scheme. * Create the project * Add etch-developers group * Set the "Permission Scheme" to Incubator. * Set the "Notification Scheme" to "Etch Notification" * Add Project Roles; - Committers = etch-developers - PMC = the individual mentors (i.e. no group) > Create a Etch project in JIRA under Incubator category > -- > > Key: INCUBATOR-90 > URL: https://issues.apache.org/jira/browse/INCUBATOR-90 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman > > * Create "Etch Notification" scheme. > * Create the project > * Add etch-developers group > * Set the "Permission Scheme" to "Standard Permissions" > * Set the "Notification Scheme" to "Etch Notification" > * Add Project Roles; > - Committers = etch-developers > - PMC = the individual mentors (i.e. no group) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-86) Request SVN from INFRA
[ https://issues.apache.org/jira/browse/INCUBATOR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638847#action_12638847 ] James Dixson commented on INCUBATOR-86: --- According to sourceforge the technique would be to rsync the repository locally and then do an svn dump of the repository. The path for rsync command would be: > rsync -av etchproj.svn.sourceforge.net::svn/etchproj/* . I have done this rsync locally already and I could just do the svnadmin dump and post that file to ETCH-1. I am only waiting on the other developers to respond to make certain we do not have any pending check-ins they want to make. > Request SVN from INFRA > -- > > Key: INCUBATOR-86 > URL: https://issues.apache.org/jira/browse/INCUBATOR-86 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman > > Joe has expressed that the SVN directory to be created when the original > codebase is in our hands. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Report] October Report for Empire-db
2008-July Empire-db Incubator status report Empire-db is a lightweight relational database abstraction layer that provides a database vendor independent string free SQL generation API and dynamic bean data handling with a special focus on compile time safety and metadata access. The main concern of the Empire-db committers in the previous month has been the acceptance of the first official Apache release by members of the incubator PMC. Due to legal concerns about the inclusion of two .jar files the distribution was first changed to go without them which however resulted in compilation problems with the build files provided. After a long discussion period the two jars which were taken from a Tomcat distribution where included again and release candidate 2 of Empire-db 2.0.4 and Struts2-extentions 1.0.4 were again put up for voting. Finally the release got accepted incubator PMC. The accepted distribution files will now be offered for download from the Empire-db website. (Yet to be done) Meanwhile a few improvement and bufixing tasks have already been opened for the upcoming 2.0.5 release. Besides that the empire-user mailing list is slowly getting used by uses not belonging to the empire-db development team. A few requests have been answered. Rainer Döbele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-86) Request SVN from INFRA
[ https://issues.apache.org/jira/browse/INCUBATOR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638833#action_12638833 ] Niclas Hedhman commented on INCUBATOR-86: - The codebase is currently sitting on SourceForge. Would it make more sense to pull it straight from there with history preserved, for instance by giving INFRA access to do a tag and dump? > Request SVN from INFRA > -- > > Key: INCUBATOR-86 > URL: https://issues.apache.org/jira/browse/INCUBATOR-86 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman > > Joe has expressed that the SVN directory to be created when the original > codebase is in our hands. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
