You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by Gurkan Erdogdu <gu...@yahoo.com> on 2009/01/30 19:33:49 UTC
[VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Hi;
Finally I have uploaded the project necessary artifacts into the staging repository.
I've staged the releases artifacts here:
Plugins repository
--------------------------
http://people.apache.org/~gerdogdu/staging-repo/OWB/1.0.0-incubating-M1/plugins/org/apache/openwebbeans
Distribution content
----------------------------
http://people.apache.org/~gerdogdu/staging-repo/OWB/1.0.0-incubating-M1/distribution/org/apache/openwebbeans/distribution/1.0.0-incubating-M1
SVN Tag (Revision: 739366)
----------------------------
http://svn.apache.org/repos/asf/incubator/openwebbeans/tags/openwebbeans-1.0.0-incubating-M1/
Please verify that this release package is correct and vote for the
motion to publish this as a openwebbeans M1 release. All votes are welcome and
will be counted.
This is my +1
Thanks;
/Gurkan
Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Kevan Miller <ke...@gmail.com>.
On Feb 2, 2009, at 4:39 PM, Mark Struberg wrote:
> but the release-tag will be on that branch in this case, isn't? So
> deleting it afterwards is maybe not such a good idea. Imho all
> releases must have a tag in the repo which exactly matches the
> released artifacts. But maybe I'm too fussy.
I probably left a few things unsaid... The release "branch" can be
deleted, the release "tag" would be in tags/1.0.0-M1.
svn copy trunk/ branches/1.0.0-M1
perform release process (part of the release process will create a
tags/1.0.0-M1 "tag"). The only difference is you're releasing from
branches rather than trunk.
After vote passes:
svn delete branches/1.0.0-M1 (this is optional, but encouraged, since
we don't really plan on supporting 1.0.0-M1).
--kevan
Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Matthias Wessendorf <ma...@apache.org>.
On Tue, Feb 3, 2009 at 7:59 AM, Gurkan Erdogdu <gu...@yahoo.com> wrote:
> +1
> I will re-start release process today. I will run RAT before deploying to staging-repo.
you can integrate it on the maven build
>
> Mark,
> In the samples/guess/pom.xml, there is a myfaces JSF dependencies as *compile* scope. Is there any reason why its scope has not a *provided*? When the scope is *compile*, all dependencies are injected into WEB-INF/lib. I think that we mark the Java EE related libraries as *provided*.
>
> WDYT?
>
>
>
>
> ________________________________
> From: Mark Struberg <st...@yahoo.de>
> To: openwebbeans-dev@incubator.apache.org
> Sent: Monday, February 2, 2009 11:39:50 PM
> Subject: Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
>
> but the release-tag will be on that branch in this case, isn't? So deleting it afterwards is maybe not such a good idea. Imho all releases must have a tag in the repo which exactly matches the released artifacts. But maybe I'm too fussy.
>
> Anyway, it's probably better I let Gurkan do the release and only make the changes in my local GIT archive.
>
> LieGrue,
> strub
>
>
> --- Kevan Miller <ke...@gmail.com> schrieb am Mo, 2.2.2009:
>
>> Von: Kevan Miller <ke...@gmail.com>
>> Betreff: Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
>> An: openwebbeans-dev@incubator.apache.org
>> Datum: Montag, 2. Februar 2009, 22:32
>> On Feb 2, 2009, at 4:08 PM, Mark Struberg wrote:
>>
>> > Gurkan, Kevan, should I wait with the SPI
>> implementation as long as you do the release?
>>
>> I'd wait.
>>
>> One way you can handle this type of conflict, is to create
>> a release branch (e.g. svn copy trunk branches/1.0.0-M1) and
>> finalize the release. This allows new development to
>> continue, even if release voting takes a while...). Does
>> require merging of changes, if updates are made to the
>> release branch. Since you don't really plan on
>> supporting the M1 branch, you can delete it after the
>> release vote passes...
>>
>> --kevan
>
>
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Gurkan Erdogdu <gu...@yahoo.com>.
I think that, we do not depend on any web or Java EE server. There are two different dependencies for the sample guess project;
1* Java EE API dependencies (example; servlet-api, jsp-api, jsf-api, jta,jpa etc.)
2* Third party dependencies (jsf-facelet)
Moreover, we can not depend on any Java EE API implementation, like JSF-RI or Myfaces RI, just depend on Java EE API.
IMHO, we can set the third party dependencies as *compile* and Java EE dependecies as *provided*. In the README.txt, I explain how to run samples.
WDYT?
________________________________
From: Mark Struberg <st...@yahoo.de>
To: openwebbeans-dev@incubator.apache.org
Sent: Tuesday, February 3, 2009 9:57:04 AM
Subject: Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
oh good point!
There is nowhere mentioned on which server the samples has to run (or I did not read it carefully enough).
Currently there are a lot of assumptions for the installations (basically all the dependencies the samples denote as 'provided'), so most people will fail to run the samples because they need to install those jars first.
On my notebook I did run via jetty, so I changed all API scopes to <scope>compile</scope> and all implementation jars to <scope>runtime</scope>.
So maybe I forgot to undo my change for MyFaces, but at least this is a good point for discussing the issue ;)
Imho samples have to run out of the box, without forcing the users to manually add jars, etc.
What I did sometimes is to set the scope via a ${webappscope} variable which is set to compile in the jetty profile and to runtime in a JBoss profile.
LieGrue,
strub
--- Gurkan Erdogdu <gu...@yahoo.com> schrieb am Di, 3.2.2009:
> Von: Gurkan Erdogdu <gu...@yahoo.com>
> Betreff: Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
> An: openwebbeans-dev@incubator.apache.org
> Datum: Dienstag, 3. Februar 2009, 7:59
> +1
> I will re-start release process today. I will run RAT
> before deploying to staging-repo.
>
> Mark,
> In the samples/guess/pom.xml, there is a myfaces JSF
> dependencies as *compile* scope. Is there any reason why its
> scope has not a *provided*? When the scope is *compile*, all
> dependencies are injected into WEB-INF/lib. I think that we
> mark the Java EE related libraries as *provided*.
>
> WDYT?
>
>
>
>
> ________________________________
> From: Mark Struberg <st...@yahoo.de>
> To: openwebbeans-dev@incubator.apache.org
> Sent: Monday, February 2, 2009 11:39:50 PM
> Subject: Re: AW: [CANCELED] Publish OpenWebBeans
> 1.0.0-incubating-M1
>
> but the release-tag will be on that branch in this case,
> isn't? So deleting it afterwards is maybe not such a
> good idea. Imho all releases must have a tag in the repo
> which exactly matches the released artifacts. But maybe
> I'm too fussy.
>
> Anyway, it's probably better I let Gurkan do the
> release and only make the changes in my local GIT archive.
>
> LieGrue,
> strub
>
>
> --- Kevan Miller <ke...@gmail.com> schrieb am
> Mo, 2.2.2009:
>
> > Von: Kevan Miller <ke...@gmail.com>
> > Betreff: Re: AW: [CANCELED] Publish OpenWebBeans
> 1.0.0-incubating-M1
> > An: openwebbeans-dev@incubator.apache.org
> > Datum: Montag, 2. Februar 2009, 22:32
> > On Feb 2, 2009, at 4:08 PM, Mark Struberg wrote:
> >
> > > Gurkan, Kevan, should I wait with the SPI
> > implementation as long as you do the release?
> >
> > I'd wait.
> >
> > One way you can handle this type of conflict, is to
> create
> > a release branch (e.g. svn copy trunk
> branches/1.0.0-M1) and
> > finalize the release. This allows new development to
> > continue, even if release voting takes a while...).
> Does
> > require merging of changes, if updates are made to the
> > release branch. Since you don't really plan on
> > supporting the M1 branch, you can delete it after the
> > release vote passes...
> >
> > --kevan
Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Mark Struberg <st...@yahoo.de>.
oh good point!
There is nowhere mentioned on which server the samples has to run (or I did not read it carefully enough).
Currently there are a lot of assumptions for the installations (basically all the dependencies the samples denote as 'provided'), so most people will fail to run the samples because they need to install those jars first.
On my notebook I did run via jetty, so I changed all API scopes to <scope>compile</scope> and all implementation jars to <scope>runtime</scope>.
So maybe I forgot to undo my change for MyFaces, but at least this is a good point for discussing the issue ;)
Imho samples have to run out of the box, without forcing the users to manually add jars, etc.
What I did sometimes is to set the scope via a ${webappscope} variable which is set to compile in the jetty profile and to runtime in a JBoss profile.
LieGrue,
strub
--- Gurkan Erdogdu <gu...@yahoo.com> schrieb am Di, 3.2.2009:
> Von: Gurkan Erdogdu <gu...@yahoo.com>
> Betreff: Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
> An: openwebbeans-dev@incubator.apache.org
> Datum: Dienstag, 3. Februar 2009, 7:59
> +1
> I will re-start release process today. I will run RAT
> before deploying to staging-repo.
>
> Mark,
> In the samples/guess/pom.xml, there is a myfaces JSF
> dependencies as *compile* scope. Is there any reason why its
> scope has not a *provided*? When the scope is *compile*, all
> dependencies are injected into WEB-INF/lib. I think that we
> mark the Java EE related libraries as *provided*.
>
> WDYT?
>
>
>
>
> ________________________________
> From: Mark Struberg <st...@yahoo.de>
> To: openwebbeans-dev@incubator.apache.org
> Sent: Monday, February 2, 2009 11:39:50 PM
> Subject: Re: AW: [CANCELED] Publish OpenWebBeans
> 1.0.0-incubating-M1
>
> but the release-tag will be on that branch in this case,
> isn't? So deleting it afterwards is maybe not such a
> good idea. Imho all releases must have a tag in the repo
> which exactly matches the released artifacts. But maybe
> I'm too fussy.
>
> Anyway, it's probably better I let Gurkan do the
> release and only make the changes in my local GIT archive.
>
> LieGrue,
> strub
>
>
> --- Kevan Miller <ke...@gmail.com> schrieb am
> Mo, 2.2.2009:
>
> > Von: Kevan Miller <ke...@gmail.com>
> > Betreff: Re: AW: [CANCELED] Publish OpenWebBeans
> 1.0.0-incubating-M1
> > An: openwebbeans-dev@incubator.apache.org
> > Datum: Montag, 2. Februar 2009, 22:32
> > On Feb 2, 2009, at 4:08 PM, Mark Struberg wrote:
> >
> > > Gurkan, Kevan, should I wait with the SPI
> > implementation as long as you do the release?
> >
> > I'd wait.
> >
> > One way you can handle this type of conflict, is to
> create
> > a release branch (e.g. svn copy trunk
> branches/1.0.0-M1) and
> > finalize the release. This allows new development to
> > continue, even if release voting takes a while...).
> Does
> > require merging of changes, if updates are made to the
> > release branch. Since you don't really plan on
> > supporting the M1 branch, you can delete it after the
> > release vote passes...
> >
> > --kevan
Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Gurkan Erdogdu <gu...@yahoo.com>.
+1
I will re-start release process today. I will run RAT before deploying to staging-repo.
Mark,
In the samples/guess/pom.xml, there is a myfaces JSF dependencies as *compile* scope. Is there any reason why its scope has not a *provided*? When the scope is *compile*, all dependencies are injected into WEB-INF/lib. I think that we mark the Java EE related libraries as *provided*.
WDYT?
________________________________
From: Mark Struberg <st...@yahoo.de>
To: openwebbeans-dev@incubator.apache.org
Sent: Monday, February 2, 2009 11:39:50 PM
Subject: Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
but the release-tag will be on that branch in this case, isn't? So deleting it afterwards is maybe not such a good idea. Imho all releases must have a tag in the repo which exactly matches the released artifacts. But maybe I'm too fussy.
Anyway, it's probably better I let Gurkan do the release and only make the changes in my local GIT archive.
LieGrue,
strub
--- Kevan Miller <ke...@gmail.com> schrieb am Mo, 2.2.2009:
> Von: Kevan Miller <ke...@gmail.com>
> Betreff: Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
> An: openwebbeans-dev@incubator.apache.org
> Datum: Montag, 2. Februar 2009, 22:32
> On Feb 2, 2009, at 4:08 PM, Mark Struberg wrote:
>
> > Gurkan, Kevan, should I wait with the SPI
> implementation as long as you do the release?
>
> I'd wait.
>
> One way you can handle this type of conflict, is to create
> a release branch (e.g. svn copy trunk branches/1.0.0-M1) and
> finalize the release. This allows new development to
> continue, even if release voting takes a while...). Does
> require merging of changes, if updates are made to the
> release branch. Since you don't really plan on
> supporting the M1 branch, you can delete it after the
> release vote passes...
>
> --kevan
Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Mark Struberg <st...@yahoo.de>.
but the release-tag will be on that branch in this case, isn't? So deleting it afterwards is maybe not such a good idea. Imho all releases must have a tag in the repo which exactly matches the released artifacts. But maybe I'm too fussy.
Anyway, it's probably better I let Gurkan do the release and only make the changes in my local GIT archive.
LieGrue,
strub
--- Kevan Miller <ke...@gmail.com> schrieb am Mo, 2.2.2009:
> Von: Kevan Miller <ke...@gmail.com>
> Betreff: Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
> An: openwebbeans-dev@incubator.apache.org
> Datum: Montag, 2. Februar 2009, 22:32
> On Feb 2, 2009, at 4:08 PM, Mark Struberg wrote:
>
> > Gurkan, Kevan, should I wait with the SPI
> implementation as long as you do the release?
>
> I'd wait.
>
> One way you can handle this type of conflict, is to create
> a release branch (e.g. svn copy trunk branches/1.0.0-M1) and
> finalize the release. This allows new development to
> continue, even if release voting takes a while...). Does
> require merging of changes, if updates are made to the
> release branch. Since you don't really plan on
> supporting the M1 branch, you can delete it after the
> release vote passes...
>
> --kevan
Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Kevan Miller <ke...@gmail.com>.
On Feb 2, 2009, at 4:08 PM, Mark Struberg wrote:
> Gurkan, Kevan, should I wait with the SPI implementation as long as
> you do the release?
I'd wait.
One way you can handle this type of conflict, is to create a release
branch (e.g. svn copy trunk branches/1.0.0-M1) and finalize the
release. This allows new development to continue, even if release
voting takes a while...). Does require merging of changes, if updates
are made to the release branch. Since you don't really plan on
supporting the M1 branch, you can delete it after the release vote
passes...
--kevan
AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Mark Struberg <st...@yahoo.de>.
Gurkan, Kevan, should I wait with the SPI implementation as long as you do the release?
LieGrue,
strub
--- Gurkan Erdogdu <gu...@yahoo.com> schrieb am Mo, 2.2.2009:
> Von: Gurkan Erdogdu <gu...@yahoo.com>
> Betreff: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
> An: openwebbeans-dev@incubator.apache.org
> Datum: Montag, 2. Februar 2009, 21:41
> Hi
>
> The M1 release [VOTE] is canceled due to the some
> shortcomings. I will start a new VOTE after re-release
> process.
>
> Thanks;
>
> /Gurkan
[CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Gurkan Erdogdu <gu...@yahoo.com>.
Hi
The M1 release [VOTE] is canceled due to the some shortcomings. I will start a new VOTE after re-release process.
Thanks;
/Gurkan
Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Kevan Miller <ke...@gmail.com>.
On Feb 2, 2009, at 4:42 PM, Mark Struberg wrote:
> Sorry Kevan, I did not get your opinion. What do you prefer:
>
> a) removing the SVN tag and doing the same version again
> or
> b) keeping the old tag and simply releasing a new -M1-RC2 or
> something?
a) would be my preference.
--kevan
Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Mark Struberg <st...@yahoo.de>.
Sorry Kevan, I did not get your opinion. What do you prefer:
a) removing the SVN tag and doing the same version again
or
b) keeping the old tag and simply releasing a new -M1-RC2 or something?
In case 2, what will we do with the -M1 artifacts and tag?
For this case we should have been starting with -RC1, don't we?
LieGrue,
strub
--- Kevan Miller <ke...@gmail.com> schrieb am Mo, 2.2.2009:
> Von: Kevan Miller <ke...@gmail.com>
> Betreff: Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
> An: openwebbeans-dev@incubator.apache.org
> Datum: Montag, 2. Februar 2009, 22:27
> On Feb 2, 2009, at 3:44 PM, Mark Struberg wrote:
>
> >> Some projects will name their release candidates
> >> and corresponding votes
> >
> > Or delete the SVN tag and do it again?
> > The artifacts have not been published yet...
> >
> > There is a release:rollback mojo which will do all the
> pom-renaming back (which is not needed in our case). The tag
> removal is not implemented yet (because tag-removal is not
> supported in maven-scm-1.1) and has to be done manually. But
> this is marked as TODO in the release plugin code, so my
> guess is that that's the way it _should_ work.
> >
> > btw: I would not use -RC1 but only -M1.1, M1.2, etc
> because I personally prefer to use the term 'RC'
> only for release candicates of final versions.
>
> I got a little carried away implying that the artifacts
> would contain the RCx name. Can just be used in the
> vote/staging directory (unique prefix, etc). Just letting
> you know how other projects have handle this. It's not
> uncommon to see a RC5 and higher... I think "1.0
> RC1" and a "1.0-M1 RC1" are pretty
> descriptive and distinct. However, don't really care...
> As long as the project knows what is being voted on, even if
> we're having multiple rounds of voting, I'm fine...
>
> --kevan
Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Kevan Miller <ke...@gmail.com>.
On Feb 2, 2009, at 3:44 PM, Mark Struberg wrote:
>> Some projects will name their release candidates
>> and corresponding votes
>
> Or delete the SVN tag and do it again?
> The artifacts have not been published yet...
>
> There is a release:rollback mojo which will do all the pom-renaming
> back (which is not needed in our case). The tag removal is not
> implemented yet (because tag-removal is not supported in maven-
> scm-1.1) and has to be done manually. But this is marked as TODO in
> the release plugin code, so my guess is that that's the way it
> _should_ work.
>
> btw: I would not use -RC1 but only -M1.1, M1.2, etc because I
> personally prefer to use the term 'RC' only for release candicates
> of final versions.
I got a little carried away implying that the artifacts would contain
the RCx name. Can just be used in the vote/staging directory (unique
prefix, etc). Just letting you know how other projects have handle
this. It's not uncommon to see a RC5 and higher... I think "1.0 RC1"
and a "1.0-M1 RC1" are pretty descriptive and distinct. However, don't
really care... As long as the project knows what is being voted on,
even if we're having multiple rounds of voting, I'm fine...
--kevan
Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Mark Struberg <st...@yahoo.de>.
> Some projects will name their release candidates
> and corresponding votes
Or delete the SVN tag and do it again?
The artifacts have not been published yet...
There is a release:rollback mojo which will do all the pom-renaming back (which is not needed in our case). The tag removal is not implemented yet (because tag-removal is not supported in maven-scm-1.1) and has to be done manually. But this is marked as TODO in the release plugin code, so my guess is that that's the way it _should_ work.
btw: I would not use -RC1 but only -M1.1, M1.2, etc because I personally prefer to use the term 'RC' only for release candicates of final versions.
LieGrue,
strub
--- Kevan Miller <ke...@gmail.com> schrieb am Mo, 2.2.2009:
> Von: Kevan Miller <ke...@gmail.com>
> Betreff: Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
> An: openwebbeans-dev@incubator.apache.org
> Datum: Montag, 2. Februar 2009, 21:29
> On Feb 2, 2009, at 3:23 PM, Gurkan Erdogdu wrote:
>
> > Hi Kevan,
> >
> > Do we have to re-do the whole release process,( I mean
> release:prepare and release:perform) . Or is it enough to
> update the artifacts in the stage?
>
> To be clean, the vote should be cancelled and the process
> restarted. Some projects will name their release candidates
> and corresponding votes (e.g. 1.0.0-incubating-M1-RC1, RC2,
> etc).
>
> --kevan
Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Kevan Miller <ke...@gmail.com>.
On Feb 2, 2009, at 3:23 PM, Gurkan Erdogdu wrote:
> Hi Kevan,
>
> Do we have to re-do the whole release process,( I mean
> release:prepare and release:perform) . Or is it enough to update the
> artifacts in the stage?
To be clean, the vote should be cancelled and the process restarted.
Some projects will name their release candidates and corresponding
votes (e.g. 1.0.0-incubating-M1-RC1, RC2, etc).
--kevan
Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Kevan Miller <ke...@gmail.com>.
On Feb 2, 2009, at 4:07 PM, Gurkan Erdogdu wrote:
> OK, I got the point, it contains the other libs in WEB-INF so its
> notice file must contains these libraries notices. Is it required to
> add all licenses to the META-INF also?
Sorry I wasn't clear... Yes, you need licenses and notices for all of
the libs that are included in the war.
--kevan
Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Gurkan Erdogdu <gu...@yahoo.com>.
OK, I got the point, it contains the other libs in WEB-INF so its notice file must contains these libraries notices. Is it required to add all licenses to the META-INF also?
Thanks;
________________________________
From: Gurkan Erdogdu <gu...@yahoo.com>
To: openwebbeans-dev@incubator.apache.org
Sent: Monday, February 2, 2009 10:31:40 PM
Subject: Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
With respect to WAR, I added the NOTICE and LICENCE file into the META-INF folder like any other jars. What is the problem in these files?
Thanks;
________________________________
From: Gurkan Erdogdu <gu...@yahoo.com>
To: openwebbeans-dev@incubator.apache.org
Sent: Monday, February 2, 2009 10:23:24 PM
Subject: Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Hi Kevan,
Do we have to re-do the whole release process,( I mean release:prepare and release:perform) . Or is it enough to update the artifacts in the stage?
Thanks;
Gurkan
________________________________
From: Kevan Miller <ke...@gmail.com>
To: openwebbeans-dev@incubator.apache.org
Sent: Monday, February 2, 2009 9:40:12 PM
Subject: Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
On Jan 30, 2009, at 1:33 PM, Gurkan Erdogdu wrote:
>
> Please verify that this release package is correct and vote for the
> motion to publish this as a openwebbeans M1 release. All votes are welcome and
> will be counted.
>
>
> This is my +1
-1
Running RAT shows the following files don't have Apache src license headers. Not all of these files need a header (e.g. the licences/* files), but looks like many of them do... Certainly all of the *.java and *.xml files.
!????? ./distribution/src/assembly/dist-all.xml
!????? ./distribution/src/assembly/dist-binary.xml
!????? ./distribution/src/assembly/dist-sources.xml
!????? ./licences/MPL-1.1.txt
!????? ./licences/cddl-1.0.txt
!????? ./licences/cpl-1.0.txt
!????? ./licences/dom4j-licence.txt
!????? ./licences/hsqldb_lic.txt
!????? ./licences/hypersonic_lic.txt
!????? ./samples/pom.xml
!????? ./samples/guess/pom.xml
!????? ./samples/guess/src/main/resources/log4j.properties
!????? ./samples/guess/src/main/webapp/home.xhtml
!????? ./samples/guess/src/main/webapp/index.html
!????? ./samples/guess/src/main/webapp/login.xhtml
!????? ./samples/guess/src/main/webapp/META-INF/MANIFEST.MF
!????? ./samples/guess/src/site/apt/index.apt
!????? ./samples/src/site/apt/index.apt
!????? ./src/site/apt/contributing.apt
!????? ./src/site/apt/index.apt
!????? ./src/site/apt/irc.apt
!????? ./src/site/apt/jsr299.apt
!????? ./src/site/apt/examples/guess.apt
!????? ./src/site/apt/extensions/index.apt
!????? ./src/site/fml/faq.fml
!????? ./webbeans-api/src/main/java/META-INF/MANIFEST.MF
!????? ./webbeans-api/src/main/java/javax/event/Observer.java
!????? ./webbeans-api/src/site/apt/index.apt
!????? ./webbeans-impl/src/main/java/log4j.properties
!????? ./webbeans-impl/src/main/java/META-INF/MANIFEST.MF
!????? ./webbeans-impl/src/main/java/META-INF/faces-config.xml
!????? ./webbeans-impl/src/site/apt/index.apt
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/mock/MockServletContext.java
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/unittests/config/ScannerTestBean.java
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/unittests/config/WebBeansScannerTest.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/BeansImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/ContainersImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/ContextsImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/ManagersImpl.java
!????? ./webbeans-tck/src/test/resources/log4j.properties
!????? ./webbeans-tck/src/test/resources/META-INF/web-beans-tck.properties
The license/notice files in http://people.apache.org/~gerdogdu/staging-repo/OWB/1.0.0-incubating-M1/plugins/org/apache/openwebbeans/guess/1.0.0-incubating-M1/guess-1.0.0-incubating-M1.war is almost certainly incorrect. I didn't see any obvious problems in any other jars.
Less serious, but should be fixed: the build instructions in README.txt are incorrect.
--kevan
Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Gurkan Erdogdu <gu...@yahoo.com>.
With respect to WAR, I added the NOTICE and LICENCE file into the META-INF folder like any other jars. What is the problem in these files?
Thanks;
________________________________
From: Gurkan Erdogdu <gu...@yahoo.com>
To: openwebbeans-dev@incubator.apache.org
Sent: Monday, February 2, 2009 10:23:24 PM
Subject: Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Hi Kevan,
Do we have to re-do the whole release process,( I mean release:prepare and release:perform) . Or is it enough to update the artifacts in the stage?
Thanks;
Gurkan
________________________________
From: Kevan Miller <ke...@gmail.com>
To: openwebbeans-dev@incubator.apache.org
Sent: Monday, February 2, 2009 9:40:12 PM
Subject: Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
On Jan 30, 2009, at 1:33 PM, Gurkan Erdogdu wrote:
>
> Please verify that this release package is correct and vote for the
> motion to publish this as a openwebbeans M1 release. All votes are welcome and
> will be counted.
>
>
> This is my +1
-1
Running RAT shows the following files don't have Apache src license headers. Not all of these files need a header (e.g. the licences/* files), but looks like many of them do... Certainly all of the *.java and *.xml files.
!????? ./distribution/src/assembly/dist-all.xml
!????? ./distribution/src/assembly/dist-binary.xml
!????? ./distribution/src/assembly/dist-sources.xml
!????? ./licences/MPL-1.1.txt
!????? ./licences/cddl-1.0.txt
!????? ./licences/cpl-1.0.txt
!????? ./licences/dom4j-licence.txt
!????? ./licences/hsqldb_lic.txt
!????? ./licences/hypersonic_lic.txt
!????? ./samples/pom.xml
!????? ./samples/guess/pom.xml
!????? ./samples/guess/src/main/resources/log4j.properties
!????? ./samples/guess/src/main/webapp/home.xhtml
!????? ./samples/guess/src/main/webapp/index.html
!????? ./samples/guess/src/main/webapp/login.xhtml
!????? ./samples/guess/src/main/webapp/META-INF/MANIFEST.MF
!????? ./samples/guess/src/site/apt/index.apt
!????? ./samples/src/site/apt/index.apt
!????? ./src/site/apt/contributing.apt
!????? ./src/site/apt/index.apt
!????? ./src/site/apt/irc.apt
!????? ./src/site/apt/jsr299.apt
!????? ./src/site/apt/examples/guess.apt
!????? ./src/site/apt/extensions/index.apt
!????? ./src/site/fml/faq.fml
!????? ./webbeans-api/src/main/java/META-INF/MANIFEST.MF
!????? ./webbeans-api/src/main/java/javax/event/Observer.java
!????? ./webbeans-api/src/site/apt/index.apt
!????? ./webbeans-impl/src/main/java/log4j.properties
!????? ./webbeans-impl/src/main/java/META-INF/MANIFEST.MF
!????? ./webbeans-impl/src/main/java/META-INF/faces-config.xml
!????? ./webbeans-impl/src/site/apt/index.apt
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/mock/MockServletContext.java
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/unittests/config/ScannerTestBean.java
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/unittests/config/WebBeansScannerTest.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/BeansImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/ContainersImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/ContextsImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/ManagersImpl.java
!????? ./webbeans-tck/src/test/resources/log4j.properties
!????? ./webbeans-tck/src/test/resources/META-INF/web-beans-tck.properties
The license/notice files in http://people.apache.org/~gerdogdu/staging-repo/OWB/1.0.0-incubating-M1/plugins/org/apache/openwebbeans/guess/1.0.0-incubating-M1/guess-1.0.0-incubating-M1.war is almost certainly incorrect. I didn't see any obvious problems in any other jars.
Less serious, but should be fixed: the build instructions in README.txt are incorrect.
--kevan
Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Gurkan Erdogdu <gu...@yahoo.com>.
Hi Kevan,
Do we have to re-do the whole release process,( I mean release:prepare and release:perform) . Or is it enough to update the artifacts in the stage?
Thanks;
Gurkan
________________________________
From: Kevan Miller <ke...@gmail.com>
To: openwebbeans-dev@incubator.apache.org
Sent: Monday, February 2, 2009 9:40:12 PM
Subject: Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
On Jan 30, 2009, at 1:33 PM, Gurkan Erdogdu wrote:
>
> Please verify that this release package is correct and vote for the
> motion to publish this as a openwebbeans M1 release. All votes are welcome and
> will be counted.
>
>
> This is my +1
-1
Running RAT shows the following files don't have Apache src license headers. Not all of these files need a header (e.g. the licences/* files), but looks like many of them do... Certainly all of the *.java and *.xml files.
!????? ./distribution/src/assembly/dist-all.xml
!????? ./distribution/src/assembly/dist-binary.xml
!????? ./distribution/src/assembly/dist-sources.xml
!????? ./licences/MPL-1.1.txt
!????? ./licences/cddl-1.0.txt
!????? ./licences/cpl-1.0.txt
!????? ./licences/dom4j-licence.txt
!????? ./licences/hsqldb_lic.txt
!????? ./licences/hypersonic_lic.txt
!????? ./samples/pom.xml
!????? ./samples/guess/pom.xml
!????? ./samples/guess/src/main/resources/log4j.properties
!????? ./samples/guess/src/main/webapp/home.xhtml
!????? ./samples/guess/src/main/webapp/index.html
!????? ./samples/guess/src/main/webapp/login.xhtml
!????? ./samples/guess/src/main/webapp/META-INF/MANIFEST.MF
!????? ./samples/guess/src/site/apt/index.apt
!????? ./samples/src/site/apt/index.apt
!????? ./src/site/apt/contributing.apt
!????? ./src/site/apt/index.apt
!????? ./src/site/apt/irc.apt
!????? ./src/site/apt/jsr299.apt
!????? ./src/site/apt/examples/guess.apt
!????? ./src/site/apt/extensions/index.apt
!????? ./src/site/fml/faq.fml
!????? ./webbeans-api/src/main/java/META-INF/MANIFEST.MF
!????? ./webbeans-api/src/main/java/javax/event/Observer.java
!????? ./webbeans-api/src/site/apt/index.apt
!????? ./webbeans-impl/src/main/java/log4j.properties
!????? ./webbeans-impl/src/main/java/META-INF/MANIFEST.MF
!????? ./webbeans-impl/src/main/java/META-INF/faces-config.xml
!????? ./webbeans-impl/src/site/apt/index.apt
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/mock/MockServletContext.java
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/unittests/config/ScannerTestBean.java
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/unittests/config/WebBeansScannerTest.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/BeansImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/ContainersImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/ContextsImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/ManagersImpl.java
!????? ./webbeans-tck/src/test/resources/log4j.properties
!????? ./webbeans-tck/src/test/resources/META-INF/web-beans-tck.properties
The license/notice files in http://people.apache.org/~gerdogdu/staging-repo/OWB/1.0.0-incubating-M1/plugins/org/apache/openwebbeans/guess/1.0.0-incubating-M1/guess-1.0.0-incubating-M1.war is almost certainly incorrect. I didn't see any obvious problems in any other jars.
Less serious, but should be fixed: the build instructions in README.txt are incorrect.
--kevan
Re: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Kevan Miller <ke...@gmail.com>.
On Jan 30, 2009, at 1:33 PM, Gurkan Erdogdu wrote:
>
> Please verify that this release package is correct and vote for the
> motion to publish this as a openwebbeans M1 release. All votes are
> welcome and
> will be counted.
>
>
> This is my +1
-1
Running RAT shows the following files don't have Apache src license
headers. Not all of these files need a header (e.g. the licences/*
files), but looks like many of them do... Certainly all of the *.java
and *.xml files.
!????? ./distribution/src/assembly/dist-all.xml
!????? ./distribution/src/assembly/dist-binary.xml
!????? ./distribution/src/assembly/dist-sources.xml
!????? ./licences/MPL-1.1.txt
!????? ./licences/cddl-1.0.txt
!????? ./licences/cpl-1.0.txt
!????? ./licences/dom4j-licence.txt
!????? ./licences/hsqldb_lic.txt
!????? ./licences/hypersonic_lic.txt
!????? ./samples/pom.xml
!????? ./samples/guess/pom.xml
!????? ./samples/guess/src/main/resources/log4j.properties
!????? ./samples/guess/src/main/webapp/home.xhtml
!????? ./samples/guess/src/main/webapp/index.html
!????? ./samples/guess/src/main/webapp/login.xhtml
!????? ./samples/guess/src/main/webapp/META-INF/MANIFEST.MF
!????? ./samples/guess/src/site/apt/index.apt
!????? ./samples/src/site/apt/index.apt
!????? ./src/site/apt/contributing.apt
!????? ./src/site/apt/index.apt
!????? ./src/site/apt/irc.apt
!????? ./src/site/apt/jsr299.apt
!????? ./src/site/apt/examples/guess.apt
!????? ./src/site/apt/extensions/index.apt
!????? ./src/site/fml/faq.fml
!????? ./webbeans-api/src/main/java/META-INF/MANIFEST.MF
!????? ./webbeans-api/src/main/java/javax/event/Observer.java
!????? ./webbeans-api/src/site/apt/index.apt
!????? ./webbeans-impl/src/main/java/log4j.properties
!????? ./webbeans-impl/src/main/java/META-INF/MANIFEST.MF
!????? ./webbeans-impl/src/main/java/META-INF/faces-config.xml
!????? ./webbeans-impl/src/site/apt/index.apt
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/mock/
MockServletContext.java
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/
unittests/config/ScannerTestBean.java
!????? ./webbeans-impl/src/test/java/org/apache/webbeans/test/
unittests/config/WebBeansScannerTest.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/
BeansImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/
ContainersImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/
ContextsImpl.java
!????? ./webbeans-tck/src/test/java/org/apache/webbeans/test/tck/
ManagersImpl.java
!????? ./webbeans-tck/src/test/resources/log4j.properties
!????? ./webbeans-tck/src/test/resources/META-INF/web-beans-
tck.properties
The license/notice files in http://people.apache.org/~gerdogdu/staging-repo/OWB/1.0.0-incubating-M1/plugins/org/apache/openwebbeans/guess/1.0.0-incubating-M1/guess-1.0.0-incubating-M1.war
is almost certainly incorrect. I didn't see any obvious problems in
any other jars.
Less serious, but should be fixed: the build instructions in
README.txt are incorrect.
--kevan
AW: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
Posted by Mark Struberg <st...@yahoo.de>.
finally looked at the packaged modules, so here is my
+1
LieGrue,
strub
--- Gurkan Erdogdu <gu...@yahoo.com> schrieb am Fr, 30.1.2009:
> Von: Gurkan Erdogdu <gu...@yahoo.com>
> Betreff: [VOTE] Publish OpenWebBeans 1.0.0-incubating-M1
> An: openwebbeans-dev@incubator.apache.org
> Datum: Freitag, 30. Januar 2009, 19:33
> Hi;
>
> Finally I have uploaded the project necessary artifacts
> into the staging repository.
>
> I've staged the releases artifacts here:
>
> Plugins repository
> --------------------------
> http://people.apache.org/~gerdogdu/staging-repo/OWB/1.0.0-incubating-M1/plugins/org/apache/openwebbeans
>
> Distribution content
> ----------------------------
> http://people.apache.org/~gerdogdu/staging-repo/OWB/1.0.0-incubating-M1/distribution/org/apache/openwebbeans/distribution/1.0.0-incubating-M1
>
> SVN Tag (Revision: 739366)
> ----------------------------
> http://svn.apache.org/repos/asf/incubator/openwebbeans/tags/openwebbeans-1.0.0-incubating-M1/
>
>
> Please verify that this release package is correct and vote
> for the
> motion to publish this as a openwebbeans M1 release. All
> votes are welcome and
> will be counted.
>
>
> This is my +1
>
> Thanks;
>
> /Gurkan