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> <groupId>java-specs.apache.org</groupId> <artifactId>jsf-api</artifactId> <version>1.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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
