________________________________
From: Mark Struberg <[email protected]>
To: [email protected]
Sent: Tuesday, January 20, 2009 11:38:27 PM
Subject: Re: maven generated site - 1st try
>Hi Gurkan!
>It would not be that much of an effort, but I _currently_ don't feel it's
>necessary. I mentioned the version issue because we have to take care of that
>in the >_future_.
>I think it's the easiest to currently maintain the site at the parent level
>and change this when needed. That's the reason why I checked it in there
>yesterday.
Ok fine, Mark. Then can we start to deploy our new site to the
people.apache.org with removing the old Apache Forrest web site?
>Another thing which is fine _yet_ but we maybe have to change in the future:
>when Gavin finishes the Spec, and we will release OpenWebBeans, then we will
>>have to remove the API module from the release builds! This is then an
>official Sun approved API which must not be touched anymore, isn't? So while
>fixing >bugs, we must not touch the API but only the impl. Maybe we should
>then move the API over to geronimo-specs as the OpenJPA guys did? Who knows,
>time >will tell.
Yes you are absolutely correct. But currently our API is more correct than
JBoss :)
>See what I mean? There are many things to consider if one likes to be
>future-proof, but not all of them must be executed immediately. So sorry if I
>caused >confusion, sometimes I come up with ideas without to explaining the
>ulterior motive good enough ;)
You can create jira-tickets for all those items that it may/must be handled at
the future phase of the project. So, we can think about it in starting from
today :)
Thanks;
/Gurkan
--- Gurkan Erdogdu <[email protected]> schrieb am Di, 20.1.2009:
> Von: Gurkan Erdogdu <[email protected]>
> Betreff: Re: maven generated site - 1st try
> An: [email protected]
> Datum: Dienstag, 20. Januar 2009, 14:28
> I think that it is more sense to make the site as a separate
> module. does it take so much effort?
>
> What do you think guys?
>
> Thanks;
>
> /Gurkan
>
>
>
>
> ________________________________
> From: Mark Struberg <[email protected]>
> To: [email protected]
> Sent: Tuesday, January 20, 2009 2:48:00 PM
> Subject: Re: maven generated site - 1st try
>
> Some of them maintain a separate site module (also via
> maven) which is not part of the release process (manual
> site:deploy)
>
> LieGrue,
> strub
>
>
> --- Gurkan Erdogdu <[email protected]> schrieb
> am Di, 20.1.2009:
>
> > Von: Gurkan Erdogdu <[email protected]>
> > Betreff: Re: maven generated site - 1st try
> > An: [email protected]
> > Datum: Dienstag, 20. Januar 2009, 7:55
> > Thanks Mark !
> >
> > I will look at it this evening :)
> >
> > How other project are using the mvn:site for its
> different
> > versions? Maybe Matthias can help us on this .
> > Matthias, how do you use mvn:site within MyFaces
> project?
> >
> > Thanks;
> >
> > /Gurkan
> >
> >
> >
> >
> > ________________________________
> > From: Mark Struberg <[email protected]>
> > To: [email protected]
> > Sent: Tuesday, January 20, 2009 2:05:03 AM
> > Subject: maven generated site - 1st try
> >
> > Hi!
> >
> > I'v committed the first version of a general
> > OpenWebBeans site maven configuration.
> >
> > You can find all the stuff under src/site
> >
> > simply run
> > $> mvn clean site
> > $> firefox target/site/index.html &
> >
> > This will take a few seconds since all modules and
> hence
> > also all impl test cases will run subsequently.
> > If you like to NOT run mvn nested then simply use
> > $> mvn -N clean site
> >
> > Don't be afraid, the links to the submodule sites
> do
> > not work locally, but only after being site:deploy ed.
> > So just imagine it and open
> > openwebbeans-impl/target/site/index.html manually ;)
> >
> > Any comments/wishes/slaps etc are welcome!
> >
> > Open discussion: how do we generally cope with
> multiple
> > versions of OpenWebBeans in the future? What about a
> 1.1 or
> > 1.2 Impl site concurrently?
> >
> > LieGrue,
> > strub
