OK thanks. IMO to avoid confusion we should just list github on the source
repository page, for both browsing the source + checking it out, etc.
Colm.
On Mon, Sep 11, 2017 at 3:01 PM, Daniel Kulp wrote:
>
>
> > On Sep 11, 2017, at 9:56 AM, Colm O hEigeartaigh
> wrote:
> >
> > What is the canon
> On Sep 11, 2017, at 9:56 AM, Colm O hEigeartaigh wrote:
>
> What is the canonical git repo that we should be using now?
>
> Do we now use github or gitbox? We should update the page at:
>
> https://cwiki.apache.org/confluence/display/CXF/Source+Repository
It shouldn’t matter. It’s a “dua
What is the canonical git repo that we should be using now?
The old one was:
git clone https://git-wip-us.apache.org/repos/asf/cxf.git
Do we now use github or gitbox? We should update the page at:
https://cwiki.apache.org/confluence/display/CXF/Source+Repository
Colm.
On Mon, Sep 11, 2017 at
We have 13 +1 votes. This vote passes.
Since this is a “.0” release, I do expect a relatively quick turnaround for a
.1 to fix any major issues that are found.
Thanks!
Dan
> On Sep 6, 2017, at 2:14 PM, Daniel Kulp wrote:
>
> It’s been 2 years since the last major CXF release.We have w
Or just use
git remote set-url origin newurl
Am 11. September 2017 15:41:01 MESZ schrieb Daniel Kulp :
>
>Cool…. Looks like things are working as I see more Team members today
>and commits from the new repo.
>
>However, I also see a couple commits in the old git-wip repo.Can
>everyone make s
We have 10 +1 votes. This vote passes.
Dan
> On Sep 6, 2017, at 2:12 PM, Daniel Kulp wrote:
>
>
> It’s been over 2 months since the last release. We’ve fixed over 35 JIRA’s
> for 3.1.13. Thus, let’s get them out.
>
> Staging repos:
> 3.0.15:
> https://repository.apache.org/content/repo
Cool…. Looks like things are working as I see more Team members today and
commits from the new repo.
However, I also see a couple commits in the old git-wip repo.Can everyone
make sure they update their git checkout to point to the new location. Not
sure the “right” way to do it, but I j
> I just checked with Guillaume to get some other opinion. He also
> approves going ahead with the release.
> So I am back to +1 again but we should not wait too long with a 3.2.1.
Good to hear this. After 3.2.0 is public there may be other bug reports
anyway so we can release 3.2.1 soon to fix t
I just checked with Guillaume to get some other opinion. He also
approves going ahead with the release.
So I am back to +1 again but we should not wait too long with a 3.2.1.
Christian
On 11.09.2017 12:57, Sergey Beryozkin wrote:
3.2.0 has been open for 2 years so I doubt major OSGI integrators
3.2.0 has been open for 2 years so I doubt major OSGI integrators will
start using it immediately, will try it, not all of them necessarily use
karaf-maven-plugin. 3.2.1 will follow in a few weeks...
By the way, I see
[INFO] Verification of feature cxf-jaxrs-cdi/3.2.1.SNAPSHOT succeeded
(and i
Updating cxf-dosgi would of course not be a blocker.
The problem is that I think this might also block people from building
custom distros that include cxf 3.2.0.
Christian
On 11.09.2017 12:33, Sergey Beryozkin wrote:
Christian
Looks like it is only happening with the DOSGI, if you try to up
Christian
Looks like it is only happening with the DOSGI, if you try to update it
to 3.2.0 - but does the issue you see with updating DOSGi to 3.2.0
warrants -1 ?
Can't you just wait till 3.2.1 ?
Cheers, Sergey
On 11/09/17 11:30, Christian Schneider wrote:
Reverting my vote to -1 until we hav
Reverting my vote to -1 until we have a decision about the issues I
found below.
I just tried to update cxf-dosgi to cxf 3.2.0. I get an error when
building the multi bundle distro.
[ERROR] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:4.1.2:features-export-meta-data
(f
+1 (non-binding)
> On 11 Sep 2017, at 11:19, Christian Schneider wrote:
>
> +1
>
> Christian
>
> On 06.09.2017 20:14, Daniel Kulp wrote:
>> It’s been 2 years since the last major CXF release.We have well over 100
>> JIRA’s of new features and enhancements that are only targeted toward 3.2
+1
Christian
On 06.09.2017 20:14, Daniel Kulp wrote:
It’s been 2 years since the last major CXF release.We have well over 100
JIRA’s of new features and enhancements that are only targeted toward 3.2.
Let’s get it out!
Staging repo:
https://repository.apache.org/content/repositories/o
+1
Christian
On 06.09.2017 20:12, Daniel Kulp wrote:
It’s been over 2 months since the last release. We’ve fixed over 35 JIRA’s for
3.1.13. Thus, let’s get them out.
Staging repos:
3.0.15:
https://repository.apache.org/content/repositories/orgapachecxf-1100/
3.1.13:
https://repository.apach
Yeah, need wait for about 30 mins in my case…...
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
> On Sep 11, 2017, at 4:25 PM, Christian Schneider
> wrote:
>
> I also just did the migration to gitbox. Some remarks:
>
> After activating the 2FA it takes a wh
I also just did the migration to gitbox. Some remarks:
After activating the 2FA it takes a while until the asf bot adds you to
the team. You will get a mail once that is completed.
The link to the cxf committers team only works once you are added to the
team. So it is normal to get a 404 unti
18 matches
Mail list logo
