Re: JAXB API target
On 6/8/06, robert burrell donkin [EMAIL PROTECTED] wrote: On 6/8/06, Noel J. Bergman [EMAIL PROTECTED] wrote: snip/ OT, but how tightly will you have to work with Tomcat to support the common EL? isn't EL maintained in jakarta? snap/ Jakarta Commons EL is pretty much Chapter 2 out of JSR 152 (JSP 2.0). The new unified EL implementation (for JSP 2.1 and JSF 1.2 -- see JSR 245) is no longer at Jakarta, its part of Tomcat (6) as of now. -Rahul - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB API target
On 6/7/06, Jochen Wiedmann [EMAIL PROTECTED] wrote: Hi, this is possibly OT, so I apologize in advance. A while ago there has been a discussion around a separate project for specifications on this list, which grew into nothing. Currently I am on the way to publish a clean room implementation of the JAXB 2.0 API. There are no IP issues: It is based on the jaxme-api (clean room JAXB 1.0 API), written by me, an existing committer and, as of yet, unpublished. However, the question arises: What would be a possible target project? I could imagine geronimo-specs (the API will be a part of J2EE 1.5), harmony (the API will be a part of a future J2SE release), ws commons, or again JaxMe. FWIW, I've already begun typing in the JAXB 2.0 spec APIs and I'm using the Apache License. My intention is to check them into the Castor (http://castor.codehaus.org/) Subversion repo, but anyone is welcome to them. I'm only partially through the specs, but many of the ideas in JAXB 2.0 came from the Castor project, so I'm hoping that providing the implementation (or at least most of it, say maybe 80%) will be pretty easy because it's already there. Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://incubator.apache.org/activemq/ Apache ServiceMix - http://incubator.apache.org/servicemix/ Castor - http://castor.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB API target
On 6/8/06, Noel J. Bergman [EMAIL PROTECTED] wrote: in [the JSF API] there are lots of classes with lots of code and logic. Not uncommon, which is why I generally consider an API project to be a bit of a waste. depends on what you mean by project :) if a top level project is meant, i now think you're right. if a focussed effort to improve cross-cut links communication channels for API specification implementations is meant, then IMO it's definitely not at all a waste of energy. downstream consumers who care of OSS are despirate for open source implementations. there are a host of legal issues which could be understood more easily if developers could break free and discuss this issue across projects. Instead, projects that implement specifications should populate the standards part of http://projects.apache.org: http://projects.apache.org/indexes/standards.html darn - you've already uncovered my cunning plan :-) i has been thinking of suggesting that a lot of this could be done by just adding more meta-data and reusing the projects mojo... i can think of a few downsides with just using projects.apache.org: 1 very low visibility (even downstream packagers really don't know about the number of API) 2 they are specification implementations. there are also a number of API implementations at apache: clean room, redistributable API implementations are very useful for building. 3 inability to home code. would we every need to do that? 4 inability to create releases (see Manfred's idea about re-releases with separate meta-data for maven) WS, Geronimo, Harmony, etc., projects are all unrepresented. yep. one of the major elements of an effort would be cateloging the available APIs and i'd the information added to the meta data. might be some questions about some clean room specification APIs without implementations that have passed the TCK... when I think of JSF API 1.2, I doubt that it would be easy to separate api development from impl development. OT, but how tightly will you have to work with Tomcat to support the common EL? isn't EL maintained in jakarta? - robert
Re: JAXB API target
Jochen, Awesome!!! Personally, my preference would be JaxMe as it is the next rev of the JAXB spec. thanks, dims On 6/7/06, Jochen Wiedmann [EMAIL PROTECTED] wrote: Hi, this is possibly OT, so I apologize in advance. A while ago there has been a discussion around a separate project for specifications on this list, which grew into nothing. Currently I am on the way to publish a clean room implementation of the JAXB 2.0 API. There are no IP issues: It is based on the jaxme-api (clean room JAXB 1.0 API), written by me, an existing committer and, as of yet, unpublished. However, the question arises: What would be a possible target project? I could imagine geronimo-specs (the API will be a part of J2EE 1.5), harmony (the API will be a part of a future J2SE release), ws commons, or again JaxMe. Jochen -- Whenever you find yourself on the side of the majority, it is time to pause and reflect. (Mark Twain) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://wso2.com/blogs/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB API target
There was a thread about a java spec central repository back in december. I wish it exists as it would be the best location... Cheers, Guillaume Nodet Jochen Wiedmann wrote: Hi, this is possibly OT, so I apologize in advance. A while ago there has been a discussion around a separate project for specifications on this list, which grew into nothing. Currently I am on the way to publish a clean room implementation of the JAXB 2.0 API. There are no IP issues: It is based on the jaxme-api (clean room JAXB 1.0 API), written by me, an existing committer and, as of yet, unpublished. However, the question arises: What would be a possible target project? I could imagine geronimo-specs (the API will be a part of J2EE 1.5), harmony (the API will be a part of a future J2SE release), ws commons, or again JaxMe. Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB API target
Agreed - I think a shared java spec project makes sense where we can unify stuff across all projects like jaxb, geronimo-spec, harmony, servicemix (we've got the JBI API) into one place. On 6/7/06, Guillaume Nodet [EMAIL PROTECTED] wrote: There was a thread about a java spec central repository back in december. I wish it exists as it would be the best location... Cheers, Guillaume Nodet Jochen Wiedmann wrote: Hi, this is possibly OT, so I apologize in advance. A while ago there has been a discussion around a separate project for specifications on this list, which grew into nothing. Currently I am on the way to publish a clean room implementation of the JAXB 2.0 API. There are no IP issues: It is based on the jaxme-api (clean room JAXB 1.0 API), written by me, an existing committer and, as of yet, unpublished. However, the question arises: What would be a possible target project? I could imagine geronimo-specs (the API will be a part of J2EE 1.5), harmony (the API will be a part of a future J2SE release), ws commons, or again JaxMe. Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James --- http://radio.weblogs.com/0112098/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB API target
+1 Guillaume Davanum Srinivas wrote: Ah. I got confused between the API and the IMPL. Sure, we have talked about it before, maybe this will generate the momentum :) +1 to a java spec project. thanks, dims On 6/7/06, James Strachan [EMAIL PROTECTED] wrote: Agreed - I think a shared java spec project makes sense where we can unify stuff across all projects like jaxb, geronimo-spec, harmony, servicemix (we've got the JBI API) into one place. On 6/7/06, Guillaume Nodet [EMAIL PROTECTED] wrote: There was a thread about a java spec central repository back in december. I wish it exists as it would be the best location... Cheers, Guillaume Nodet Jochen Wiedmann wrote: Hi, this is possibly OT, so I apologize in advance. A while ago there has been a discussion around a separate project for specifications on this list, which grew into nothing. Currently I am on the way to publish a clean room implementation of the JAXB 2.0 API. There are no IP issues: It is based on the jaxme-api (clean room JAXB 1.0 API), written by me, an existing committer and, as of yet, unpublished. However, the question arises: What would be a possible target project? I could imagine geronimo-specs (the API will be a part of J2EE 1.5), harmony (the API will be a part of a future J2SE release), ws commons, or again JaxMe. Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James --- http://radio.weblogs.com/0112098/ - 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: JAXB API target
So, then the APIs will be in that special spec project and impls will be done in their own projects? For MyFaces this would mean javax.faces.** will be developed in that spec project and the JSF runtime in the *traditional* MyFaces project, right ? -Matthias On 6/7/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Ah. I got confused between the API and the IMPL. Sure, we have talked about it before, maybe this will generate the momentum :) +1 to a java spec project. thanks, dims On 6/7/06, James Strachan [EMAIL PROTECTED] wrote: Agreed - I think a shared java spec project makes sense where we can unify stuff across all projects like jaxb, geronimo-spec, harmony, servicemix (we've got the JBI API) into one place. On 6/7/06, Guillaume Nodet [EMAIL PROTECTED] wrote: There was a thread about a java spec central repository back in december. I wish it exists as it would be the best location... Cheers, Guillaume Nodet Jochen Wiedmann wrote: Hi, this is possibly OT, so I apologize in advance. A while ago there has been a discussion around a separate project for specifications on this list, which grew into nothing. Currently I am on the way to publish a clean room implementation of the JAXB 2.0 API. There are no IP issues: It is based on the jaxme-api (clean room JAXB 1.0 API), written by me, an existing committer and, as of yet, unpublished. However, the question arises: What would be a possible target project? I could imagine geronimo-specs (the API will be a part of J2EE 1.5), harmony (the API will be a part of a future J2SE release), ws commons, or again JaxMe. Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James --- http://radio.weblogs.com/0112098/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://wso2.com/blogs/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthias Wessendorf Aechterhoek 18 48282 Emsdetten blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB API target
On 6/7/06, Matthias Wessendorf [EMAIL PROTECTED] wrote: So, then the APIs will be in that special spec project and impls will be done in their own projects? Yes - as there could be many implementations For MyFaces this would mean javax.faces.** will be developed in that spec project and the JSF runtime in the *traditional* MyFaces project, right ? Yes. If a particular project really wants to keep ownership of a particular spec jar/project thats fine too - it just makes lots of sense to release the specs in line with when the specs actually change - rather than include them in each implementation release. Then if any JSF implementation wanted to reuse the spec jar they could. -- James --- http://radio.weblogs.com/0112098/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB API target
I wonder if Jakarta would be willing to mange the specs. When I think of Java at Apache, I think of Jakarta so it seems like a natural place to keep specs. Also Jakarta has experience dealing with lots of small code bases. just an idea... -dain On Jun 7, 2006, at 9:08 AM, James Strachan wrote: Agreed - I think a shared java spec project makes sense where we can unify stuff across all projects like jaxb, geronimo-spec, harmony, servicemix (we've got the JBI API) into one place. On 6/7/06, Guillaume Nodet [EMAIL PROTECTED] wrote: There was a thread about a java spec central repository back in december. I wish it exists as it would be the best location... Cheers, Guillaume Nodet Jochen Wiedmann wrote: Hi, this is possibly OT, so I apologize in advance. A while ago there has been a discussion around a separate project for specifications on this list, which grew into nothing. Currently I am on the way to publish a clean room implementation of the JAXB 2.0 API. There are no IP issues: It is based on the jaxme-api (clean room JAXB 1.0 API), written by me, an existing committer and, as of yet, unpublished. However, the question arises: What would be a possible target project? I could imagine geronimo-specs (the API will be a part of J2EE 1.5), harmony (the API will be a part of a future J2SE release), ws commons, or again JaxMe. Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James --- http://radio.weblogs.com/0112098/ - 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: JAXB API target
Am kinda thinking it needs a very different kind of pmc/committer model so a new top level project might be simplest. e.g. any comitter at apache should be pretty much welcome to come in and add a spec or fix any errors in the specs or build system or documentation - as they are generally static and don't change (until a new spec comes along or a spec changes). So its kindof a cross-project project with a low barrier to entry for any apache committer (since no real development happens other than typing in the specs from the javadoc). On 6/7/06, Dain Sundstrom [EMAIL PROTECTED] wrote: I wonder if Jakarta would be willing to mange the specs. When I think of Java at Apache, I think of Jakarta so it seems like a natural place to keep specs. Also Jakarta has experience dealing with lots of small code bases. just an idea... -dain On Jun 7, 2006, at 9:08 AM, James Strachan wrote: Agreed - I think a shared java spec project makes sense where we can unify stuff across all projects like jaxb, geronimo-spec, harmony, servicemix (we've got the JBI API) into one place. On 6/7/06, Guillaume Nodet [EMAIL PROTECTED] wrote: There was a thread about a java spec central repository back in december. I wish it exists as it would be the best location... Cheers, Guillaume Nodet Jochen Wiedmann wrote: Hi, this is possibly OT, so I apologize in advance. A while ago there has been a discussion around a separate project for specifications on this list, which grew into nothing. Currently I am on the way to publish a clean room implementation of the JAXB 2.0 API. There are no IP issues: It is based on the jaxme-api (clean room JAXB 1.0 API), written by me, an existing committer and, as of yet, unpublished. However, the question arises: What would be a possible target project? I could imagine geronimo-specs (the API will be a part of J2EE 1.5), harmony (the API will be a part of a future J2SE release), ws commons, or again JaxMe. Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James --- http://radio.weblogs.com/0112098/ - 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] -- James --- http://radio.weblogs.com/0112098/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB API target
+1 for tlp I think folks like Geronimo or Myfaces should be able to commit to *their* API (sub)project of the Java Spec TLP -Matthias On 6/7/06, James Strachan [EMAIL PROTECTED] wrote: Am kinda thinking it needs a very different kind of pmc/committer model so a new top level project might be simplest. e.g. any comitter at apache should be pretty much welcome to come in and add a spec or fix any errors in the specs or build system or documentation - as they are generally static and don't change (until a new spec comes along or a spec changes). So its kindof a cross-project project with a low barrier to entry for any apache committer (since no real development happens other than typing in the specs from the javadoc). On 6/7/06, Dain Sundstrom [EMAIL PROTECTED] wrote: I wonder if Jakarta would be willing to mange the specs. When I think of Java at Apache, I think of Jakarta so it seems like a natural place to keep specs. Also Jakarta has experience dealing with lots of small code bases. just an idea... -dain On Jun 7, 2006, at 9:08 AM, James Strachan wrote: Agreed - I think a shared java spec project makes sense where we can unify stuff across all projects like jaxb, geronimo-spec, harmony, servicemix (we've got the JBI API) into one place. On 6/7/06, Guillaume Nodet [EMAIL PROTECTED] wrote: There was a thread about a java spec central repository back in december. I wish it exists as it would be the best location... Cheers, Guillaume Nodet Jochen Wiedmann wrote: Hi, this is possibly OT, so I apologize in advance. A while ago there has been a discussion around a separate project for specifications on this list, which grew into nothing. Currently I am on the way to publish a clean room implementation of the JAXB 2.0 API. There are no IP issues: It is based on the jaxme-api (clean room JAXB 1.0 API), written by me, an existing committer and, as of yet, unpublished. However, the question arises: What would be a possible target project? I could imagine geronimo-specs (the API will be a part of J2EE 1.5), harmony (the API will be a part of a future J2SE release), ws commons, or again JaxMe. Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James --- http://radio.weblogs.com/0112098/ - 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] -- James --- http://radio.weblogs.com/0112098/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthias Wessendorf Aechterhoek 18 48282 Emsdetten blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB API target
On 6/7/06, James Strachan [EMAIL PROTECTED] wrote: Am kinda thinking it needs a very different kind of pmc/committer model so a new top level project might be simplest. e.g. any comitter at apache should be pretty much welcome to come in and add a spec or fix any errors in the specs or build system or documentation - as they are generally static and don't change (until a new spec comes along or a spec changes). So its kindof a cross-project project with a low barrier to entry for any apache committer (since no real development happens other than typing in the specs from the javadoc). jakarta already has a low barrier for existing apache committers and has the advantage of no setup overhead (the pmc and lists already exists). might be worth considering kickstarting at jakarta and then look to move it to a top level pmc later. - robert
Re: JAXB API target
On 6/7/06, James Strachan [EMAIL PROTECTED] wrote: On 6/7/06, robert burrell donkin [EMAIL PROTECTED] wrote: On 6/7/06, James Strachan [EMAIL PROTECTED] wrote: Am kinda thinking it needs a very different kind of pmc/committer model so a new top level project might be simplest. e.g. any comitter at apache should be pretty much welcome to come in and add a spec or fix any errors in the specs or build system or documentation - as they are generally static and don't change (until a new spec comes along or a spec changes). So its kindof a cross-project project with a low barrier to entry for any apache committer (since no real development happens other than typing in the specs from the javadoc). jakarta already has a low barrier for existing apache committers and has the advantage of no setup overhead (the pmc and lists already exists). might be worth considering kickstarting at jakarta and then look to move it to a top level pmc later. Sounds fine with me; whatever's easiest to get going really. i'll try to get something started kickstarted over at jakarta but feel free to go ahead and start the ball rolling for a new pmc for java specifications. - robert
Re: JAXB API target
Don't forget, that the JSF API is a little bit different to other spec APIs. Other than common spec APIs that almost consist of interfaces only, in JSF there are lots of classes with lots of code and logic. So, when I think of JSF API 1.2, I doubt that it would be easy to separate api development from impl development. And: Don't forget about TCK testing. We are not allowed to publish a final version of any spec API if it did not pass the TCK. But, AFAIK, TCK testing is not possible without the according impl classes. This applies to all API classes, not only MyFaces! So, what sense would it make to separate API from the impl development? My proposal is to - Put the API sources where they belong to: the corresponding ASF project that is: JAXB API -- JaxMe, JSF API -- MyFaces, ... - Possibly establish a dummy TLP project that collects all API jars under one umbrella and that acts as a base (resp. eponym) for the Maven repository. This way people who only need an API jar would not have to search for the corresponding ASF project. They go to the central java-specs project and download the API jar there or they use java-specs.apache.org as Maven groupId when they define their dependencies. For an example, this way someone could write a JSF application without any (Maven) dependency to the MyFaces project. The dependeny would look like this: dependency groupIdjava-specs.apache.org/groupId artifactIdjsf-api/artifactId version1.2/version /dependency Just my 2 cents... Manfred On 6/7/06, Matthias Wessendorf [EMAIL PROTECTED] wrote: +1 for tlp I think folks like Geronimo or Myfaces should be able to commit to *their* API (sub)project of the Java Spec TLP -Matthias On 6/7/06, James Strachan [EMAIL PROTECTED] wrote: Am kinda thinking it needs a very different kind of pmc/committer model so a new top level project might be simplest. e.g. any comitter at apache should be pretty much welcome to come in and add a spec or fix any errors in the specs or build system or documentation - as they are generally static and don't change (until a new spec comes along or a spec changes). So its kindof a cross-project project with a low barrier to entry for any apache committer (since no real development happens other than typing in the specs from the javadoc). On 6/7/06, Dain Sundstrom [EMAIL PROTECTED] wrote: I wonder if Jakarta would be willing to mange the specs. When I think of Java at Apache, I think of Jakarta so it seems like a natural place to keep specs. Also Jakarta has experience dealing with lots of small code bases. just an idea... -dain On Jun 7, 2006, at 9:08 AM, James Strachan wrote: Agreed - I think a shared java spec project makes sense where we can unify stuff across all projects like jaxb, geronimo-spec, harmony, servicemix (we've got the JBI API) into one place. On 6/7/06, Guillaume Nodet [EMAIL PROTECTED] wrote: There was a thread about a java spec central repository back in december. I wish it exists as it would be the best location... Cheers, Guillaume Nodet Jochen Wiedmann wrote: Hi, this is possibly OT, so I apologize in advance. A while ago there has been a discussion around a separate project for specifications on this list, which grew into nothing. Currently I am on the way to publish a clean room implementation of the JAXB 2.0 API. There are no IP issues: It is based on the jaxme-api (clean room JAXB 1.0 API), written by me, an existing committer and, as of yet, unpublished. However, the question arises: What would be a possible target project? I could imagine geronimo-specs (the API will be a part of J2EE 1.5), harmony (the API will be a part of a future J2SE release), ws commons, or again JaxMe. Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James --- http://radio.weblogs.com/0112098/ - 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] -- James --- http://radio.weblogs.com/0112098/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthias Wessendorf Aechterhoek 18 48282 Emsdetten blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB API target
An alternative would be XML Commons Externals where we already have the whole JAXP and W3C DOM family of APIs. Maybe we should make an inventory of all those APIs on a Wiki page and write down where they are currently located. That should give us a better overall picture. Charging into uncontrolled action might not be the best thing to do. Maintaining APIs also requires some amount of coordination among projects which also means that everybody should know what our idea is. Not everybody is on this list. That said: +1 for a TLP and for consolidating all API efforts in one place. Will be back after a good night's sleep... On 07.06.2006 21:27:30 robert burrell donkin wrote: On 6/7/06, James Strachan [EMAIL PROTECTED] wrote: Am kinda thinking it needs a very different kind of pmc/committer model so a new top level project might be simplest. e.g. any comitter at apache should be pretty much welcome to come in and add a spec or fix any errors in the specs or build system or documentation - as they are generally static and don't change (until a new spec comes along or a spec changes). So its kindof a cross-project project with a low barrier to entry for any apache committer (since no real development happens other than typing in the specs from the javadoc). jakarta already has a low barrier for existing apache committers and has the advantage of no setup overhead (the pmc and lists already exists). might be worth considering kickstarting at jakarta and then look to move it to a top level pmc later. - robert Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB API target
i've posted a first draft at http://wiki.apache.org/jakarta/SpecificationRepository but luckily i did see this point coming :-) (it's rough so please feel free to dive in and improve) On 6/7/06, Manfred Geiler [EMAIL PROTECTED] wrote: Don't forget, that the JSF API is a little bit different to other spec APIs. Other than common spec APIs that almost consist of interfaces only, in JSF there are lots of classes with lots of code and logic. So, when I think of JSF API 1.2, I doubt that it would be easy to separate api development from impl development. yep - that's cool. this must not be some attempt to grab specifications from projects if it doesn't make sense. the problem is ATM that there isn't any place for specifications even if a project wanted (for whatever reason) to maintain the codebase elsewhere. And: Don't forget about TCK testing. We are not allowed to publish a final version of any spec API if it did not pass the TCK. But, AFAIK, TCK testing is not possible without the according impl classes. This applies to all API classes, not only MyFaces! So, what sense would it make to separate API from the impl development? (i'll refrain from commenting on the legal aspects) but there may come a time when the TCK is passed :-) My proposal is to - Put the API sources where they belong to: the corresponding ASF project that is: JAXB API -- JaxMe, JSF API -- MyFaces, ... i think the option should be with the project. if a project feels it makes sense to host an API, that's cool, if they want to maintain it separate, then that should be cool too. - Possibly establish a dummy TLP project that collects all API jars under one umbrella and that acts as a base (resp. eponym) for the Maven repository. This way people who only need an API jar would not have to search for the corresponding ASF project. They go to the central java-specs project and download the API jar there or they use java-specs.apache.org as Maven groupId when they define their dependencies. For an example, this way someone could write a JSF application without any (Maven) dependency to the MyFaces project. The dependeny would look like this: dependency groupIdjava-specs.apache.org/groupId artifactIdjsf-api/artifactId version1.2/version /dependency top level projects take quite a lot of overhead. establishing a dummy top level project would not only take a long time and energy but would beg the question: why bother? it should be possible to create a central contact point at jakarta without this overhead. - robert
RE: JAXB API target
in [the JSF API] there are lots of classes with lots of code and logic. Not uncommon, which is why I generally consider an API project to be a bit of a waste. Instead, projects that implement specifications should populate the standards part of http://projects.apache.org: http://projects.apache.org/indexes/standards.html WS, Geronimo, Harmony, etc., projects are all unrepresented. when I think of JSF API 1.2, I doubt that it would be easy to separate api development from impl development. OT, but how tightly will you have to work with Tomcat to support the common EL? --- Moel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
