Releasing Camel 3.0 Milestone 1

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

Releasing Camel 3.0 Milestone 1

Andrea Cosentino-2
Hello everybody,

I think  we have enough material and we did enough development to release a first milestone for Camel 3.

We can use the next week to finalize what we have and fixing the remaining tests 

Thoughts?

Gregor, are you available to cut the release the weekend 16-17 February?

Thanks

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd
Reply | Threaded
Open this post in threaded view
|

Re: Releasing Camel 3.0 Milestone 1

Gregor Zurowski-2
Hi,

Yes, I'd be available for cutting the release next weekend.

Thanks,
Gregor

On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
<[hidden email]> wrote:

>
> Hello everybody,
>
> I think  we have enough material and we did enough development to release a first milestone for Camel 3.
>
> We can use the next week to finalize what we have and fixing the remaining tests
>
> Thoughts?
>
> Gregor, are you available to cut the release the weekend 16-17 February?
>
> Thanks
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
Reply | Threaded
Open this post in threaded view
|

Re: Releasing Camel 3.0 Milestone 1

Claus Ibsen-2
Hi

Sounds good.

We have about 150 checkstyles to fix.
And there is 1 unit test error from camel-zipkin which is a known
issue. I added a section to the migration document.

On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:

>
> Hi,
>
> Yes, I'd be available for cutting the release next weekend.
>
> Thanks,
> Gregor
>
> On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> <[hidden email]> wrote:
> >
> > Hello everybody,
> >
> > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> >
> > We can use the next week to finalize what we have and fixing the remaining tests
> >
> > Thoughts?
> >
> > Gregor, are you available to cut the release the weekend 16-17 February?
> >
> > Thanks
> >
> > --
> > Andrea Cosentino
> > ----------------------------------
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: [hidden email]
> > Twitter: @oscerd2
> > Github: oscerd



--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Reply | Threaded
Open this post in threaded view
|

Re: Releasing Camel 3.0 Milestone 1

Jean-Baptiste Onofré
In reply to this post by Andrea Cosentino-2
Hi,

it sounds good.

I ran a build on my machine, and I have some failure (tests). I will
take a look.

Regards
JB

On 08/02/2019 10:09, Andrea Cosentino wrote:

> Hello everybody,
>
> I think  we have enough material and we did enough development to release a first milestone for Camel 3.
>
> We can use the next week to finalize what we have and fixing the remaining tests 
>
> Thoughts?
>
> Gregor, are you available to cut the release the weekend 16-17 February?
>
> Thanks
>
> --
> Andrea Cosentino 
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Releasing Camel 3.0 Milestone 1

Claus Ibsen-2
In reply to this post by Gregor Zurowski-2
Hi

Just a thought, what about the version number

For 2.0 we did 1 milestone, which was named

https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle


So for 3.0 milestone 1, should we do that same?

3.0-M1

Or is it

3.0.0-M1

or 3.0.M1

Just wonder what other projects do, and is there any implications for
OSGi etc we need to consider?


On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:

>
> Hi,
>
> Yes, I'd be available for cutting the release next weekend.
>
> Thanks,
> Gregor
>
> On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> <[hidden email]> wrote:
> >
> > Hello everybody,
> >
> > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> >
> > We can use the next week to finalize what we have and fixing the remaining tests
> >
> > Thoughts?
> >
> > Gregor, are you available to cut the release the weekend 16-17 February?
> >
> > Thanks
> >
> > --
> > Andrea Cosentino
> > ----------------------------------
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: [hidden email]
> > Twitter: @oscerd2
> > Github: oscerd



--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Reply | Threaded
Open this post in threaded view
|

Re: Releasing Camel 3.0 Milestone 1

Andrea Cosentino-2
In reply to this post by Jean-Baptiste Onofré
Ok, Gregor. I think we're fine for the M1 release.

I think we can use the 3.0-M1 as version, since we did the same for 2.0-M1 in 2009 :-)

Let us know when you start the release process so we can freeze :-)

Thanks!

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Thursday, February 14, 2019, 2:47:01 PM GMT+1, Jean-Baptiste Onofré <[hidden email]> wrote:





Hi,

it sounds good.

I ran a build on my machine, and I have some failure (tests). I will
take a look.

Regards
JB

On 08/02/2019 10:09, Andrea Cosentino wrote:

> Hello everybody,
>
> I think  we have enough material and we did enough development to release a first milestone for Camel 3.
>
> We can use the next week to finalize what we have and fixing the remaining tests 
>
> Thoughts?
>
> Gregor, are you available to cut the release the weekend 16-17 February?
>
> Thanks
>
> --
> Andrea Cosentino 
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd

>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply | Threaded
Open this post in threaded view
|

R: Re: Releasing Camel 3.0 Milestone 1

Andrea Cosentino-2
In reply to this post by Claus Ibsen-2
I think it's fine to have 3.0-M1 even from OSGi perspective

Inviato da Yahoo Mail su Android
 
  Il gio, 14 feb, 2019 alle 17:04, Claus Ibsen<[hidden email]> ha scritto:   Hi

Just a thought, what about the version number

For 2.0 we did 1 milestone, which was named

https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle


So for 3.0 milestone 1, should we do that same?

3.0-M1

Or is it

3.0.0-M1

or 3.0.M1

Just wonder what other projects do, and is there any implications for
OSGi etc we need to consider?


On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:

>
> Hi,
>
> Yes, I'd be available for cutting the release next weekend.
>
> Thanks,
> Gregor
>
> On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> <[hidden email]> wrote:
> >
> > Hello everybody,
> >
> > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> >
> > We can use the next week to finalize what we have and fixing the remaining tests
> >
> > Thoughts?
> >
> > Gregor, are you available to cut the release the weekend 16-17 February?
> >
> > Thanks
> >
> > --
> > Andrea Cosentino
> > ----------------------------------
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: [hidden email]
> > Twitter: @oscerd2
> > Github: oscerd



--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
 
Reply | Threaded
Open this post in threaded view
|

Re: Re: Releasing Camel 3.0 Milestone 1

Gregor Zurowski-2
Hi Everyone:

I will start looking into the release tomorrow.  I'd suggest to use
version "3.0.0-M1" or "3.0.0.M1" as this will be the first milestone
for the 3.0.0 release.

Thanks,
Gregor

On Thu, Feb 14, 2019 at 7:12 PM Andrea Cosentino
<[hidden email]> wrote:

>
> I think it's fine to have 3.0-M1 even from OSGi perspective
>
> Inviato da Yahoo Mail su Android
>
>   Il gio, 14 feb, 2019 alle 17:04, Claus Ibsen<[hidden email]> ha scritto:   Hi
>
> Just a thought, what about the version number
>
> For 2.0 we did 1 milestone, which was named
>
> https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle
>
>
> So for 3.0 milestone 1, should we do that same?
>
> 3.0-M1
>
> Or is it
>
> 3.0.0-M1
>
> or 3.0.M1
>
> Just wonder what other projects do, and is there any implications for
> OSGi etc we need to consider?
>
>
> On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:
> >
> > Hi,
> >
> > Yes, I'd be available for cutting the release next weekend.
> >
> > Thanks,
> > Gregor
> >
> > On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> > <[hidden email]> wrote:
> > >
> > > Hello everybody,
> > >
> > > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> > >
> > > We can use the next week to finalize what we have and fixing the remaining tests
> > >
> > > Thoughts?
> > >
> > > Gregor, are you available to cut the release the weekend 16-17 February?
> > >
> > > Thanks
> > >
> > > --
> > > Andrea Cosentino
> > > ----------------------------------
> > > Apache Camel PMC Chair
> > > Apache Karaf Committer
> > > Apache Servicemix PMC Member
> > > Email: [hidden email]
> > > Twitter: @oscerd2
> > > Github: oscerd
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Reply | Threaded
Open this post in threaded view
|

Re: Releasing Camel 3.0 Milestone 1

Andrea Cosentino-2
If everybody agree on 3.0.0-M1  I'm fine with that.

I was suggesting to use 2.0-M1 because we did in that way 9 years ago :-D

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Friday, February 15, 2019, 9:02:03 AM GMT+1, Gregor Zurowski <[hidden email]> wrote:





Hi Everyone:

I will start looking into the release tomorrow.  I'd suggest to use
version "3.0.0-M1" or "3.0.0.M1" as this will be the first milestone
for the 3.0.0 release.

Thanks,
Gregor

On Thu, Feb 14, 2019 at 7:12 PM Andrea Cosentino
<[hidden email]> wrote:

>
> I think it's fine to have 3.0-M1 even from OSGi perspective
>
> Inviato da Yahoo Mail su Android
>
>  Il gio, 14 feb, 2019 alle 17:04, Claus Ibsen<[hidden email]> ha scritto:  Hi
>
> Just a thought, what about the version number
>
> For 2.0 we did 1 milestone, which was named
>
> https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle
>
>
> So for 3.0 milestone 1, should we do that same?
>
> 3.0-M1
>
> Or is it
>
> 3.0.0-M1
>
> or 3.0.M1
>
> Just wonder what other projects do, and is there any implications for
> OSGi etc we need to consider?
>
>
> On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:
> >
> > Hi,
> >
> > Yes, I'd be available for cutting the release next weekend.
> >
> > Thanks,
> > Gregor
> >
> > On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> > <[hidden email]> wrote:
> > >
> > > Hello everybody,
> > >
> > > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> > >
> > > We can use the next week to finalize what we have and fixing the remaining tests
> > >
> > > Thoughts?
> > >
> > > Gregor, are you available to cut the release the weekend 16-17 February?
> > >
> > > Thanks
> > >
> > > --
> > > Andrea Cosentino
> > > ----------------------------------
> > > Apache Camel PMC Chair
> > > Apache Karaf Committer
> > > Apache Servicemix PMC Member
> > > Email: [hidden email]
> > > Twitter: @oscerd2
> > > Github: oscerd
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Reply | Threaded
Open this post in threaded view
|

Re: Releasing Camel 3.0 Milestone 1

Andrea Cosentino-2
I meant to say 3.0-M1

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Friday, February 15, 2019, 9:41:22 AM GMT+1, Andrea Cosentino <[hidden email]> wrote:





If everybody agree on 3.0.0-M1  I'm fine with that.

I was suggesting to use 2.0-M1 because we did in that way 9 years ago :-D

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Friday, February 15, 2019, 9:02:03 AM GMT+1, Gregor Zurowski <[hidden email]> wrote:





Hi Everyone:

I will start looking into the release tomorrow.  I'd suggest to use
version "3.0.0-M1" or "3.0.0.M1" as this will be the first milestone
for the 3.0.0 release.

Thanks,
Gregor

On Thu, Feb 14, 2019 at 7:12 PM Andrea Cosentino
<[hidden email]> wrote:

>
> I think it's fine to have 3.0-M1 even from OSGi perspective
>
> Inviato da Yahoo Mail su Android
>
>  Il gio, 14 feb, 2019 alle 17:04, Claus Ibsen<[hidden email]> ha scritto:  Hi
>
> Just a thought, what about the version number
>
> For 2.0 we did 1 milestone, which was named
>
> https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle
>
>
> So for 3.0 milestone 1, should we do that same?
>
> 3.0-M1
>
> Or is it
>
> 3.0.0-M1
>
> or 3.0.M1
>
> Just wonder what other projects do, and is there any implications for
> OSGi etc we need to consider?
>
>
> On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:
> >
> > Hi,
> >
> > Yes, I'd be available for cutting the release next weekend.
> >
> > Thanks,
> > Gregor
> >
> > On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> > <[hidden email]> wrote:
> > >
> > > Hello everybody,
> > >
> > > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> > >
> > > We can use the next week to finalize what we have and fixing the remaining tests
> > >
> > > Thoughts?
> > >
> > > Gregor, are you available to cut the release the weekend 16-17 February?
> > >
> > > Thanks
> > >
> > > --
> > > Andrea Cosentino
> > > ----------------------------------
> > > Apache Camel PMC Chair
> > > Apache Karaf Committer
> > > Apache Servicemix PMC Member
> > > Email: [hidden email]
> > > Twitter: @oscerd2
> > > Github: oscerd
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Reply | Threaded
Open this post in threaded view
|

Re: Releasing Camel 3.0 Milestone 1

Gregor Zurowski-2
I've briefly looked into the current state of the master branch and
noticed that module camel-itest-performance has errors and is not
building. I won't be able to look into this today. Can someone take a
look at this?

Thanks,
Gregor


On Fri, Feb 15, 2019 at 10:04 AM Andrea Cosentino <[hidden email]> wrote:

>
> I meant to say 3.0-M1
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, February 15, 2019, 9:41:22 AM GMT+1, Andrea Cosentino <[hidden email]> wrote:
>
>
>
>
>
> If everybody agree on 3.0.0-M1  I'm fine with that.
>
> I was suggesting to use 2.0-M1 because we did in that way 9 years ago :-D
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, February 15, 2019, 9:02:03 AM GMT+1, Gregor Zurowski <[hidden email]> wrote:
>
>
>
>
>
> Hi Everyone:
>
> I will start looking into the release tomorrow.  I'd suggest to use
> version "3.0.0-M1" or "3.0.0.M1" as this will be the first milestone
> for the 3.0.0 release.
>
> Thanks,
> Gregor
>
> On Thu, Feb 14, 2019 at 7:12 PM Andrea Cosentino
> <[hidden email]> wrote:
> >
> > I think it's fine to have 3.0-M1 even from OSGi perspective
> >
> > Inviato da Yahoo Mail su Android
> >
> >  Il gio, 14 feb, 2019 alle 17:04, Claus Ibsen<[hidden email]> ha scritto:  Hi
> >
> > Just a thought, what about the version number
> >
> > For 2.0 we did 1 milestone, which was named
> >
> > https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle
> >
> >
> > So for 3.0 milestone 1, should we do that same?
> >
> > 3.0-M1
> >
> > Or is it
> >
> > 3.0.0-M1
> >
> > or 3.0.M1
> >
> > Just wonder what other projects do, and is there any implications for
> > OSGi etc we need to consider?
> >
> >
> > On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:
> > >
> > > Hi,
> > >
> > > Yes, I'd be available for cutting the release next weekend.
> > >
> > > Thanks,
> > > Gregor
> > >
> > > On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> > > <[hidden email]> wrote:
> > > >
> > > > Hello everybody,
> > > >
> > > > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> > > >
> > > > We can use the next week to finalize what we have and fixing the remaining tests
> > > >
> > > > Thoughts?
> > > >
> > > > Gregor, are you available to cut the release the weekend 16-17 February?
> > > >
> > > > Thanks
> > > >
> > > > --
> > > > Andrea Cosentino
> > > > ----------------------------------
> > > > Apache Camel PMC Chair
> > > > Apache Karaf Committer
> > > > Apache Servicemix PMC Member
> > > > Email: [hidden email]
> > > > Twitter: @oscerd2
> > > > Github: oscerd
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
Reply | Threaded
Open this post in threaded view
|

Re: Releasing Camel 3.0 Milestone 1

Andrea Cosentino-2
It's only part of the release profile, that's why we didn't notice it. I'm on it.
--Andrea Cosentino ----------------------------------Apache Camel PMC ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: [hidden email]: @oscerd2Github: oscerd

    On Friday, February 15, 2019, 10:09:09 AM GMT+1, Gregor Zurowski <[hidden email]> wrote:  
 
 I've briefly looked into the current state of the master branch and
noticed that module camel-itest-performance has errors and is not
building. I won't be able to look into this today. Can someone take a
look at this?

Thanks,
Gregor


On Fri, Feb 15, 2019 at 10:04 AM Andrea Cosentino <[hidden email]> wrote:

>
> I meant to say 3.0-M1
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, February 15, 2019, 9:41:22 AM GMT+1, Andrea Cosentino <[hidden email]> wrote:
>
>
>
>
>
> If everybody agree on 3.0.0-M1  I'm fine with that.
>
> I was suggesting to use 2.0-M1 because we did in that way 9 years ago :-D
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, February 15, 2019, 9:02:03 AM GMT+1, Gregor Zurowski <[hidden email]> wrote:
>
>
>
>
>
> Hi Everyone:
>
> I will start looking into the release tomorrow.  I'd suggest to use
> version "3.0.0-M1" or "3.0.0.M1" as this will be the first milestone
> for the 3.0.0 release.
>
> Thanks,
> Gregor
>
> On Thu, Feb 14, 2019 at 7:12 PM Andrea Cosentino
> <[hidden email]> wrote:
> >
> > I think it's fine to have 3.0-M1 even from OSGi perspective
> >
> > Inviato da Yahoo Mail su Android
> >
> >  Il gio, 14 feb, 2019 alle 17:04, Claus Ibsen<[hidden email]> ha scritto:  Hi
> >
> > Just a thought, what about the version number
> >
> > For 2.0 we did 1 milestone, which was named
> >
> > https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle
> >
> >
> > So for 3.0 milestone 1, should we do that same?
> >
> > 3.0-M1
> >
> > Or is it
> >
> > 3.0.0-M1
> >
> > or 3.0.M1
> >
> > Just wonder what other projects do, and is there any implications for
> > OSGi etc we need to consider?
> >
> >
> > On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:
> > >
> > > Hi,
> > >
> > > Yes, I'd be available for cutting the release next weekend.
> > >
> > > Thanks,
> > > Gregor
> > >
> > > On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> > > <[hidden email]> wrote:
> > > >
> > > > Hello everybody,
> > > >
> > > > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> > > >
> > > > We can use the next week to finalize what we have and fixing the remaining tests
> > > >
> > > > Thoughts?
> > > >
> > > > Gregor, are you available to cut the release the weekend 16-17 February?
> > > >
> > > > Thanks
> > > >
> > > > --
> > > > Andrea Cosentino
> > > > ----------------------------------
> > > > Apache Camel PMC Chair
> > > > Apache Karaf Committer
> > > > Apache Servicemix PMC Member
> > > > Email: [hidden email]
> > > > Twitter: @oscerd2
> > > > Github: oscerd
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
 
Reply | Threaded
Open this post in threaded view
|

Re: Releasing Camel 3.0 Milestone 1

Andrea Cosentino-2
It should be fixed now.

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Friday, February 15, 2019, 10:15:33 AM GMT+1, Andrea Cosentino <[hidden email]> wrote:





It's only part of the release profile, that's why we didn't notice it. I'm on it.
--Andrea Cosentino ----------------------------------Apache Camel PMC ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: [hidden email]: @oscerd2Github: oscerd

    On Friday, February 15, 2019, 10:09:09 AM GMT+1, Gregor Zurowski <[hidden email]> wrote: 

I've briefly looked into the current state of the master branch and
noticed that module camel-itest-performance has errors and is not
building. I won't be able to look into this today. Can someone take a
look at this?

Thanks,
Gregor


On Fri, Feb 15, 2019 at 10:04 AM Andrea Cosentino <[hidden email]> wrote:

>
> I meant to say 3.0-M1
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, February 15, 2019, 9:41:22 AM GMT+1, Andrea Cosentino <[hidden email]> wrote:
>
>
>
>
>
> If everybody agree on 3.0.0-M1  I'm fine with that.
>
> I was suggesting to use 2.0-M1 because we did in that way 9 years ago :-D
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, February 15, 2019, 9:02:03 AM GMT+1, Gregor Zurowski <[hidden email]> wrote:
>
>
>
>
>
> Hi Everyone:
>
> I will start looking into the release tomorrow.  I'd suggest to use
> version "3.0.0-M1" or "3.0.0.M1" as this will be the first milestone
> for the 3.0.0 release.
>
> Thanks,
> Gregor
>
> On Thu, Feb 14, 2019 at 7:12 PM Andrea Cosentino
> <[hidden email]> wrote:
> >
> > I think it's fine to have 3.0-M1 even from OSGi perspective
> >
> > Inviato da Yahoo Mail su Android
> >
> >  Il gio, 14 feb, 2019 alle 17:04, Claus Ibsen<[hidden email]> ha scritto:  Hi
> >
> > Just a thought, what about the version number
> >
> > For 2.0 we did 1 milestone, which was named
> >
> > https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle
> >
> >
> > So for 3.0 milestone 1, should we do that same?
> >
> > 3.0-M1
> >
> > Or is it
> >
> > 3.0.0-M1
> >
> > or 3.0.M1
> >
> > Just wonder what other projects do, and is there any implications for
> > OSGi etc we need to consider?
> >
> >
> > On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:
> > >
> > > Hi,
> > >
> > > Yes, I'd be available for cutting the release next weekend.
> > >
> > > Thanks,
> > > Gregor
> > >
> > > On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> > > <[hidden email]> wrote:
> > > >
> > > > Hello everybody,
> > > >
> > > > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> > > >
> > > > We can use the next week to finalize what we have and fixing the remaining tests
> > > >
> > > > Thoughts?
> > > >
> > > > Gregor, are you available to cut the release the weekend 16-17 February?
> > > >
> > > > Thanks
> > > >
> > > > --
> > > > Andrea Cosentino
> > > > ----------------------------------
> > > > Apache Camel PMC Chair
> > > > Apache Karaf Committer
> > > > Apache Servicemix PMC Member
> > > > Email: [hidden email]
> > > > Twitter: @oscerd2
> > > > Github: oscerd
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
 
Reply | Threaded
Open this post in threaded view
|

R: Re: Releasing Camel 3.0 Milestone 1

Andrea Cosentino-2
In reply to this post by Gregor Zurowski-2
Hello Gregor, what's the status of the release cut? Thanks

Inviato da Yahoo Mail su Android
 
  Il ven, 15 feb, 2019 alle 10:09, Gregor Zurowski<[hidden email]> ha scritto:   I've briefly looked into the current state of the master branch and
noticed that module camel-itest-performance has errors and is not
building. I won't be able to look into this today. Can someone take a
look at this?

Thanks,
Gregor


On Fri, Feb 15, 2019 at 10:04 AM Andrea Cosentino <[hidden email]> wrote:

>
> I meant to say 3.0-M1
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, February 15, 2019, 9:41:22 AM GMT+1, Andrea Cosentino <[hidden email]> wrote:
>
>
>
>
>
> If everybody agree on 3.0.0-M1  I'm fine with that.
>
> I was suggesting to use 2.0-M1 because we did in that way 9 years ago :-D
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: [hidden email]
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Friday, February 15, 2019, 9:02:03 AM GMT+1, Gregor Zurowski <[hidden email]> wrote:
>
>
>
>
>
> Hi Everyone:
>
> I will start looking into the release tomorrow.  I'd suggest to use
> version "3.0.0-M1" or "3.0.0.M1" as this will be the first milestone
> for the 3.0.0 release.
>
> Thanks,
> Gregor
>
> On Thu, Feb 14, 2019 at 7:12 PM Andrea Cosentino
> <[hidden email]> wrote:
> >
> > I think it's fine to have 3.0-M1 even from OSGi perspective
> >
> > Inviato da Yahoo Mail su Android
> >
> >  Il gio, 14 feb, 2019 alle 17:04, Claus Ibsen<[hidden email]> ha scritto:  Hi
> >
> > Just a thought, what about the version number
> >
> > For 2.0 we did 1 milestone, which was named
> >
> > https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle
> >
> >
> > So for 3.0 milestone 1, should we do that same?
> >
> > 3.0-M1
> >
> > Or is it
> >
> > 3.0.0-M1
> >
> > or 3.0.M1
> >
> > Just wonder what other projects do, and is there any implications for
> > OSGi etc we need to consider?
> >
> >
> > On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:
> > >
> > > Hi,
> > >
> > > Yes, I'd be available for cutting the release next weekend.
> > >
> > > Thanks,
> > > Gregor
> > >
> > > On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> > > <[hidden email]> wrote:
> > > >
> > > > Hello everybody,
> > > >
> > > > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> > > >
> > > > We can use the next week to finalize what we have and fixing the remaining tests
> > > >
> > > > Thoughts?
> > > >
> > > > Gregor, are you available to cut the release the weekend 16-17 February?
> > > >
> > > > Thanks
> > > >
> > > > --
> > > > Andrea Cosentino
> > > > ----------------------------------
> > > > Apache Camel PMC Chair
> > > > Apache Karaf Committer
> > > > Apache Servicemix PMC Member
> > > > Email: [hidden email]
> > > > Twitter: @oscerd2
> > > > Github: oscerd
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
 
Reply | Threaded
Open this post in threaded view
|

Re: Re: Releasing Camel 3.0 Milestone 1

Gregor Zurowski-2
Hi Everyone:

I ran into some issues with the build.  The build fails when building
module platforms/karaf/features with the following message:

===
[INFO] [ERROR] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:4.2.1:verify (validate) on
project apache-camel: Verification failures: Verification failures:
[INFO] [ERROR] Feature resolution failed for [camel-catalog/3.0.0.M1]
===

The full error output is as follows:

===
[INFO] [ERROR] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:4.2.1:verify (validate) on
project apache-camel: Verification failures: Verification failures:
[INFO] [ERROR] Feature resolution failed for [camel-catalog/3.0.0.M1]
[INFO] [ERROR] Message:
org.apache.karaf.features.internal.util.MultiException: Error:
[INFO] [ERROR] Error downloading mvn:org.apache.camel/camel-catalog/3.0.0.M1
[INFO] [ERROR] Repositories: {
[INFO] [ERROR] file:///home/camel/camel/platforms/karaf/features/target/classes/features.xml
[INFO] [ERROR] mvn:ca.uhn.hapi.fhir.karaf/hapi-fhir/3.5.0/xml/features
[INFO] [ERROR] mvn:org.apache.aries.jpa/jpa-features/2.7.0/xml/features
[INFO] [ERROR] mvn:org.apache.cxf.karaf/apache-cxf/3.3.0/xml/features
[INFO] [ERROR] mvn:org.apache.jclouds.karaf/jclouds-karaf/2.1.1/xml/features
[INFO] [ERROR] mvn:org.apache.karaf.features/enterprise/4.2.1/xml/features
[INFO] [ERROR] mvn:org.apache.karaf.features/framework/4.2.1/xml/features
[INFO] [ERROR] mvn:org.apache.karaf.features/spring-legacy/4.2.1/xml/features
[INFO] [ERROR] mvn:org.apache.karaf.features/spring/4.2.1/xml/features
[INFO] [ERROR] mvn:org.apache.karaf.features/standard/4.2.1/xml/features
[INFO] [ERROR] mvn:org.apache.openjpa/openjpa-features/3.0.0/xml/features
[INFO] [ERROR] mvn:org.hibernate.validator/hibernate-validator-osgi-karaf-features/6.0.12.Final/xml/features
[INFO] [ERROR] mvn:org.hibernate.validator/hibernate-validator-osgi-karaf-features/6.0.14.Final/xml/features
[INFO] [ERROR] mvn:org.hibernate/hibernate-osgi/5.2.9.Final/xml/karaf
[INFO] [ERROR] mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features
[INFO] [ERROR] mvn:org.ops4j.pax.jdbc/pax-jdbc-features/1.3.0/xml/features
[INFO] [ERROR] mvn:org.ops4j.pax.jms/pax-jms-features/1.0.1/xml/features
[INFO] [ERROR] mvn:org.ops4j.pax.transx/pax-transx-features/0.3.0/xml/features
[INFO] [ERROR] mvn:org.ops4j.pax.transx/pax-transx-features/0.4.0/xml/features
[INFO] [ERROR] mvn:org.ops4j.pax.web/pax-web-features/7.2.3/xml/features
[INFO] [ERROR] }
[INFO] [ERROR] Resources: {
[INFO] [ERROR] mvn:org.apache.camel/camel-catalog/3.0.0.M1
[INFO] [ERROR] mvn:org.apache.felix/org.apache.felix.configadmin/1.9.4
[INFO] [ERROR] mvn:org.apache.felix/org.apache.felix.coordinator/1.0.2
[INFO] [ERROR] mvn:org.apache.felix/org.apache.felix.fileinstall/3.6.4
[INFO] [ERROR] mvn:org.apache.karaf.features/org.apache.karaf.features.core/4.2.1
[INFO] [ERROR] mvn:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.1
[INFO] [ERROR] mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-impl/2.2.11_1
[INFO] [ERROR] mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.activation-api-1.1/2.5.0
[INFO] [ERROR] mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.jaxb-api-2.2/2.5.0
[INFO] [ERROR] mvn:org.fusesource.jansi/jansi/1.17.1
[INFO] [ERROR] mvn:org.ops4j.pax.logging/pax-logging-api/1.10.1
[INFO] [ERROR] mvn:org.ops4j.pax.logging/pax-logging-log4j2/1.10.1
[INFO] [ERROR] mvn:org.ops4j.pax.url/pax-url-aether/2.5.4
[INFO] [ERROR] }
===

All features can be verified without issues except for catalog:

===
[INFO] [INFO] Features verified: 231, failures: 1, ignored: 0
[INFO] [INFO] Failures: camel-catalog/3.0.0.M1
===

I was able to work around this issue by first doing a clean build of
the catalog module and installing it in the local m2 repository, and
then triggering the release process. This is obviously nothing we want
to keep doing moving forward.

I am currently still working on the release, hopefully it will fully
build now.  All release related work is done on a separate release
branch, so you can continue to make changes on master.

Thanks,
Gregor

On Sun, Feb 17, 2019 at 3:34 PM Andrea Cosentino <[hidden email]> wrote:

>
> Hello Gregor, what's the status of the release cut? Thanks
>
> Inviato da Yahoo Mail su Android
>
> Il ven, 15 feb, 2019 alle 10:09, Gregor Zurowski
> <[hidden email]> ha scritto:
> I've briefly looked into the current state of the master branch and
> noticed that module camel-itest-performance has errors and is not
> building. I won't be able to look into this today. Can someone take a
> look at this?
>
> Thanks,
> Gregor
>
>
> On Fri, Feb 15, 2019 at 10:04 AM Andrea Cosentino <[hidden email]> wrote:
> >
> > I meant to say 3.0-M1
> >
> > --
> > Andrea Cosentino
> > ----------------------------------
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: [hidden email]
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> >
> >
> >
> > On Friday, February 15, 2019, 9:41:22 AM GMT+1, Andrea Cosentino <[hidden email]> wrote:
> >
> >
> >
> >
> >
> > If everybody agree on 3.0.0-M1  I'm fine with that.
> >
> > I was suggesting to use 2.0-M1 because we did in that way 9 years ago :-D
> >
> > --
> > Andrea Cosentino
> > ----------------------------------
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: [hidden email]
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> >
> >
> >
> > On Friday, February 15, 2019, 9:02:03 AM GMT+1, Gregor Zurowski <[hidden email]> wrote:
> >
> >
> >
> >
> >
> > Hi Everyone:
> >
> > I will start looking into the release tomorrow.  I'd suggest to use
> > version "3.0.0-M1" or "3.0.0.M1" as this will be the first milestone
> > for the 3.0.0 release.
> >
> > Thanks,
> > Gregor
> >
> > On Thu, Feb 14, 2019 at 7:12 PM Andrea Cosentino
> > <[hidden email]> wrote:
> > >
> > > I think it's fine to have 3.0-M1 even from OSGi perspective
> > >
> > > Inviato da Yahoo Mail su Android
> > >
> > >  Il gio, 14 feb, 2019 alle 17:04, Claus Ibsen<[hidden email]> ha scritto:  Hi
> > >
> > > Just a thought, what about the version number
> > >
> > > For 2.0 we did 1 milestone, which was named
> > >
> > > https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle
> > >
> > >
> > > So for 3.0 milestone 1, should we do that same?
> > >
> > > 3.0-M1
> > >
> > > Or is it
> > >
> > > 3.0.0-M1
> > >
> > > or 3.0.M1
> > >
> > > Just wonder what other projects do, and is there any implications for
> > > OSGi etc we need to consider?
> > >
> > >
> > > On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:
> > > >
> > > > Hi,
> > > >
> > > > Yes, I'd be available for cutting the release next weekend.
> > > >
> > > > Thanks,
> > > > Gregor
> > > >
> > > > On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> > > > <[hidden email]> wrote:
> > > > >
> > > > > Hello everybody,
> > > > >
> > > > > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> > > > >
> > > > > We can use the next week to finalize what we have and fixing the remaining tests
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > Gregor, are you available to cut the release the weekend 16-17 February?
> > > > >
> > > > > Thanks
> > > > >
> > > > > --
> > > > > Andrea Cosentino
> > > > > ----------------------------------
> > > > > Apache Camel PMC Chair
> > > > > Apache Karaf Committer
> > > > > Apache Servicemix PMC Member
> > > > > Email: [hidden email]
> > > > > Twitter: @oscerd2
> > > > > Github: oscerd
> > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
Reply | Threaded
Open this post in threaded view
|

R: Re: Re: Releasing Camel 3.0 Milestone 1

Andrea Cosentino-2
Thanks much Gregor.. can you please raise a JIRA for this? So we can fix it for M2?
Thanks for your time!

Inviato da Yahoo Mail su Android
 
  Il dom, 17 feb, 2019 alle 21:21, Gregor Zurowski<[hidden email]> ha scritto:   Hi Everyone:

I ran into some issues with the build.  The build fails when building
module platforms/karaf/features with the following message:

===
[INFO] [ERROR] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:4.2.1:verify (validate) on
project apache-camel: Verification failures: Verification failures:
[INFO] [ERROR] Feature resolution failed for [camel-catalog/3.0.0.M1]
===

The full error output is as follows:

===
[INFO] [ERROR] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:4.2.1:verify (validate) on
project apache-camel: Verification failures: Verification failures:
[INFO] [ERROR] Feature resolution failed for [camel-catalog/3.0.0.M1]
[INFO] [ERROR] Message:
org.apache.karaf.features.internal.util.MultiException: Error:
[INFO] [ERROR] Error downloading mvn:org.apache.camel/camel-catalog/3.0.0.M1
[INFO] [ERROR] Repositories: {
[INFO] [ERROR] file:///home/camel/camel/platforms/karaf/features/target/classes/features.xml
[INFO] [ERROR] mvn:ca.uhn.hapi.fhir.karaf/hapi-fhir/3.5.0/xml/features
[INFO] [ERROR] mvn:org.apache.aries.jpa/jpa-features/2.7.0/xml/features
[INFO] [ERROR] mvn:org.apache.cxf.karaf/apache-cxf/3.3.0/xml/features
[INFO] [ERROR] mvn:org.apache.jclouds.karaf/jclouds-karaf/2.1.1/xml/features
[INFO] [ERROR] mvn:org.apache.karaf.features/enterprise/4.2.1/xml/features
[INFO] [ERROR] mvn:org.apache.karaf.features/framework/4.2.1/xml/features
[INFO] [ERROR] mvn:org.apache.karaf.features/spring-legacy/4.2.1/xml/features
[INFO] [ERROR] mvn:org.apache.karaf.features/spring/4.2.1/xml/features
[INFO] [ERROR] mvn:org.apache.karaf.features/standard/4.2.1/xml/features
[INFO] [ERROR] mvn:org.apache.openjpa/openjpa-features/3.0.0/xml/features
[INFO] [ERROR] mvn:org.hibernate.validator/hibernate-validator-osgi-karaf-features/6.0.12.Final/xml/features
[INFO] [ERROR] mvn:org.hibernate.validator/hibernate-validator-osgi-karaf-features/6.0.14.Final/xml/features
[INFO] [ERROR] mvn:org.hibernate/hibernate-osgi/5.2.9.Final/xml/karaf
[INFO] [ERROR] mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features
[INFO] [ERROR] mvn:org.ops4j.pax.jdbc/pax-jdbc-features/1.3.0/xml/features
[INFO] [ERROR] mvn:org.ops4j.pax.jms/pax-jms-features/1.0.1/xml/features
[INFO] [ERROR] mvn:org.ops4j.pax.transx/pax-transx-features/0.3.0/xml/features
[INFO] [ERROR] mvn:org.ops4j.pax.transx/pax-transx-features/0.4.0/xml/features
[INFO] [ERROR] mvn:org.ops4j.pax.web/pax-web-features/7.2.3/xml/features
[INFO] [ERROR] }
[INFO] [ERROR] Resources: {
[INFO] [ERROR] mvn:org.apache.camel/camel-catalog/3.0.0.M1
[INFO] [ERROR] mvn:org.apache.felix/org.apache.felix.configadmin/1.9.4
[INFO] [ERROR] mvn:org.apache.felix/org.apache.felix.coordinator/1.0.2
[INFO] [ERROR] mvn:org.apache.felix/org.apache.felix.fileinstall/3.6.4
[INFO] [ERROR] mvn:org.apache.karaf.features/org.apache.karaf.features.core/4.2.1
[INFO] [ERROR] mvn:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.1
[INFO] [ERROR] mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-impl/2.2.11_1
[INFO] [ERROR] mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.activation-api-1.1/2.5.0
[INFO] [ERROR] mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.jaxb-api-2.2/2.5.0
[INFO] [ERROR] mvn:org.fusesource.jansi/jansi/1.17.1
[INFO] [ERROR] mvn:org.ops4j.pax.logging/pax-logging-api/1.10.1
[INFO] [ERROR] mvn:org.ops4j.pax.logging/pax-logging-log4j2/1.10.1
[INFO] [ERROR] mvn:org.ops4j.pax.url/pax-url-aether/2.5.4
[INFO] [ERROR] }
===

All features can be verified without issues except for catalog:

===
[INFO] [INFO] Features verified: 231, failures: 1, ignored: 0
[INFO] [INFO] Failures: camel-catalog/3.0.0.M1
===

I was able to work around this issue by first doing a clean build of
the catalog module and installing it in the local m2 repository, and
then triggering the release process. This is obviously nothing we want
to keep doing moving forward.

I am currently still working on the release, hopefully it will fully
build now.  All release related work is done on a separate release
branch, so you can continue to make changes on master.

Thanks,
Gregor

On Sun, Feb 17, 2019 at 3:34 PM Andrea Cosentino <[hidden email]> wrote:

>
> Hello Gregor, what's the status of the release cut? Thanks
>
> Inviato da Yahoo Mail su Android
>
> Il ven, 15 feb, 2019 alle 10:09, Gregor Zurowski
> <[hidden email]> ha scritto:
> I've briefly looked into the current state of the master branch and
> noticed that module camel-itest-performance has errors and is not
> building. I won't be able to look into this today. Can someone take a
> look at this?
>
> Thanks,
> Gregor
>
>
> On Fri, Feb 15, 2019 at 10:04 AM Andrea Cosentino <[hidden email]> wrote:
> >
> > I meant to say 3.0-M1
> >
> > --
> > Andrea Cosentino
> > ----------------------------------
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: [hidden email]
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> >
> >
> >
> > On Friday, February 15, 2019, 9:41:22 AM GMT+1, Andrea Cosentino <[hidden email]> wrote:
> >
> >
> >
> >
> >
> > If everybody agree on 3.0.0-M1  I'm fine with that.
> >
> > I was suggesting to use 2.0-M1 because we did in that way 9 years ago :-D
> >
> > --
> > Andrea Cosentino
> > ----------------------------------
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: [hidden email]
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> >
> >
> >
> > On Friday, February 15, 2019, 9:02:03 AM GMT+1, Gregor Zurowski <[hidden email]> wrote:
> >
> >
> >
> >
> >
> > Hi Everyone:
> >
> > I will start looking into the release tomorrow.  I'd suggest to use
> > version "3.0.0-M1" or "3.0.0.M1" as this will be the first milestone
> > for the 3.0.0 release.
> >
> > Thanks,
> > Gregor
> >
> > On Thu, Feb 14, 2019 at 7:12 PM Andrea Cosentino
> > <[hidden email]> wrote:
> > >
> > > I think it's fine to have 3.0-M1 even from OSGi perspective
> > >
> > > Inviato da Yahoo Mail su Android
> > >
> > >  Il gio, 14 feb, 2019 alle 17:04, Claus Ibsen<[hidden email]> ha scritto:  Hi
> > >
> > > Just a thought, what about the version number
> > >
> > > For 2.0 we did 1 milestone, which was named
> > >
> > > https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle
> > >
> > >
> > > So for 3.0 milestone 1, should we do that same?
> > >
> > > 3.0-M1
> > >
> > > Or is it
> > >
> > > 3.0.0-M1
> > >
> > > or 3.0.M1
> > >
> > > Just wonder what other projects do, and is there any implications for
> > > OSGi etc we need to consider?
> > >
> > >
> > > On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:
> > > >
> > > > Hi,
> > > >
> > > > Yes, I'd be available for cutting the release next weekend.
> > > >
> > > > Thanks,
> > > > Gregor
> > > >
> > > > On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> > > > <[hidden email]> wrote:
> > > > >
> > > > > Hello everybody,
> > > > >
> > > > > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> > > > >
> > > > > We can use the next week to finalize what we have and fixing the remaining tests
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > Gregor, are you available to cut the release the weekend 16-17 February?
> > > > >
> > > > > Thanks
> > > > >
> > > > > --
> > > > > Andrea Cosentino
> > > > > ----------------------------------
> > > > > Apache Camel PMC Chair
> > > > > Apache Karaf Committer
> > > > > Apache Servicemix PMC Member
> > > > > Email: [hidden email]
> > > > > Twitter: @oscerd2
> > > > > Github: oscerd
> > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
 
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Releasing Camel 3.0 Milestone 1

Claus Ibsen-2
Hi

I created a ticket
https://issues.apache.org/jira/browse/CAMEL-13212

On Sun, Feb 17, 2019 at 9:48 PM Andrea Cosentino
<[hidden email]> wrote:

>
> Thanks much Gregor.. can you please raise a JIRA for this? So we can fix it for M2?
> Thanks for your time!
>
> Inviato da Yahoo Mail su Android
>
>   Il dom, 17 feb, 2019 alle 21:21, Gregor Zurowski<[hidden email]> ha scritto:   Hi Everyone:
>
> I ran into some issues with the build.  The build fails when building
> module platforms/karaf/features with the following message:
>
> ===
> [INFO] [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.2.1:verify (validate) on
> project apache-camel: Verification failures: Verification failures:
> [INFO] [ERROR] Feature resolution failed for [camel-catalog/3.0.0.M1]
> ===
>
> The full error output is as follows:
>
> ===
> [INFO] [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.2.1:verify (validate) on
> project apache-camel: Verification failures: Verification failures:
> [INFO] [ERROR] Feature resolution failed for [camel-catalog/3.0.0.M1]
> [INFO] [ERROR] Message:
> org.apache.karaf.features.internal.util.MultiException: Error:
> [INFO] [ERROR] Error downloading mvn:org.apache.camel/camel-catalog/3.0.0.M1
> [INFO] [ERROR] Repositories: {
> [INFO] [ERROR] file:///home/camel/camel/platforms/karaf/features/target/classes/features.xml
> [INFO] [ERROR] mvn:ca.uhn.hapi.fhir.karaf/hapi-fhir/3.5.0/xml/features
> [INFO] [ERROR] mvn:org.apache.aries.jpa/jpa-features/2.7.0/xml/features
> [INFO] [ERROR] mvn:org.apache.cxf.karaf/apache-cxf/3.3.0/xml/features
> [INFO] [ERROR] mvn:org.apache.jclouds.karaf/jclouds-karaf/2.1.1/xml/features
> [INFO] [ERROR] mvn:org.apache.karaf.features/enterprise/4.2.1/xml/features
> [INFO] [ERROR] mvn:org.apache.karaf.features/framework/4.2.1/xml/features
> [INFO] [ERROR] mvn:org.apache.karaf.features/spring-legacy/4.2.1/xml/features
> [INFO] [ERROR] mvn:org.apache.karaf.features/spring/4.2.1/xml/features
> [INFO] [ERROR] mvn:org.apache.karaf.features/standard/4.2.1/xml/features
> [INFO] [ERROR] mvn:org.apache.openjpa/openjpa-features/3.0.0/xml/features
> [INFO] [ERROR] mvn:org.hibernate.validator/hibernate-validator-osgi-karaf-features/6.0.12.Final/xml/features
> [INFO] [ERROR] mvn:org.hibernate.validator/hibernate-validator-osgi-karaf-features/6.0.14.Final/xml/features
> [INFO] [ERROR] mvn:org.hibernate/hibernate-osgi/5.2.9.Final/xml/karaf
> [INFO] [ERROR] mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features
> [INFO] [ERROR] mvn:org.ops4j.pax.jdbc/pax-jdbc-features/1.3.0/xml/features
> [INFO] [ERROR] mvn:org.ops4j.pax.jms/pax-jms-features/1.0.1/xml/features
> [INFO] [ERROR] mvn:org.ops4j.pax.transx/pax-transx-features/0.3.0/xml/features
> [INFO] [ERROR] mvn:org.ops4j.pax.transx/pax-transx-features/0.4.0/xml/features
> [INFO] [ERROR] mvn:org.ops4j.pax.web/pax-web-features/7.2.3/xml/features
> [INFO] [ERROR] }
> [INFO] [ERROR] Resources: {
> [INFO] [ERROR] mvn:org.apache.camel/camel-catalog/3.0.0.M1
> [INFO] [ERROR] mvn:org.apache.felix/org.apache.felix.configadmin/1.9.4
> [INFO] [ERROR] mvn:org.apache.felix/org.apache.felix.coordinator/1.0.2
> [INFO] [ERROR] mvn:org.apache.felix/org.apache.felix.fileinstall/3.6.4
> [INFO] [ERROR] mvn:org.apache.karaf.features/org.apache.karaf.features.core/4.2.1
> [INFO] [ERROR] mvn:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.1
> [INFO] [ERROR] mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-impl/2.2.11_1
> [INFO] [ERROR] mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.activation-api-1.1/2.5.0
> [INFO] [ERROR] mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.jaxb-api-2.2/2.5.0
> [INFO] [ERROR] mvn:org.fusesource.jansi/jansi/1.17.1
> [INFO] [ERROR] mvn:org.ops4j.pax.logging/pax-logging-api/1.10.1
> [INFO] [ERROR] mvn:org.ops4j.pax.logging/pax-logging-log4j2/1.10.1
> [INFO] [ERROR] mvn:org.ops4j.pax.url/pax-url-aether/2.5.4
> [INFO] [ERROR] }
> ===
>
> All features can be verified without issues except for catalog:
>
> ===
> [INFO] [INFO] Features verified: 231, failures: 1, ignored: 0
> [INFO] [INFO] Failures: camel-catalog/3.0.0.M1
> ===
>
> I was able to work around this issue by first doing a clean build of
> the catalog module and installing it in the local m2 repository, and
> then triggering the release process. This is obviously nothing we want
> to keep doing moving forward.
>
> I am currently still working on the release, hopefully it will fully
> build now.  All release related work is done on a separate release
> branch, so you can continue to make changes on master.
>
> Thanks,
> Gregor
>
> On Sun, Feb 17, 2019 at 3:34 PM Andrea Cosentino <[hidden email]> wrote:
> >
> > Hello Gregor, what's the status of the release cut? Thanks
> >
> > Inviato da Yahoo Mail su Android
> >
> > Il ven, 15 feb, 2019 alle 10:09, Gregor Zurowski
> > <[hidden email]> ha scritto:
> > I've briefly looked into the current state of the master branch and
> > noticed that module camel-itest-performance has errors and is not
> > building. I won't be able to look into this today. Can someone take a
> > look at this?
> >
> > Thanks,
> > Gregor
> >
> >
> > On Fri, Feb 15, 2019 at 10:04 AM Andrea Cosentino <[hidden email]> wrote:
> > >
> > > I meant to say 3.0-M1
> > >
> > > --
> > > Andrea Cosentino
> > > ----------------------------------
> > > Apache Camel PMC Chair
> > > Apache Karaf Committer
> > > Apache Servicemix PMC Member
> > > Email: [hidden email]
> > > Twitter: @oscerd2
> > > Github: oscerd
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Friday, February 15, 2019, 9:41:22 AM GMT+1, Andrea Cosentino <[hidden email]> wrote:
> > >
> > >
> > >
> > >
> > >
> > > If everybody agree on 3.0.0-M1  I'm fine with that.
> > >
> > > I was suggesting to use 2.0-M1 because we did in that way 9 years ago :-D
> > >
> > > --
> > > Andrea Cosentino
> > > ----------------------------------
> > > Apache Camel PMC Chair
> > > Apache Karaf Committer
> > > Apache Servicemix PMC Member
> > > Email: [hidden email]
> > > Twitter: @oscerd2
> > > Github: oscerd
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Friday, February 15, 2019, 9:02:03 AM GMT+1, Gregor Zurowski <[hidden email]> wrote:
> > >
> > >
> > >
> > >
> > >
> > > Hi Everyone:
> > >
> > > I will start looking into the release tomorrow.  I'd suggest to use
> > > version "3.0.0-M1" or "3.0.0.M1" as this will be the first milestone
> > > for the 3.0.0 release.
> > >
> > > Thanks,
> > > Gregor
> > >
> > > On Thu, Feb 14, 2019 at 7:12 PM Andrea Cosentino
> > > <[hidden email]> wrote:
> > > >
> > > > I think it's fine to have 3.0-M1 even from OSGi perspective
> > > >
> > > > Inviato da Yahoo Mail su Android
> > > >
> > > >  Il gio, 14 feb, 2019 alle 17:04, Claus Ibsen<[hidden email]> ha scritto:  Hi
> > > >
> > > > Just a thought, what about the version number
> > > >
> > > > For 2.0 we did 1 milestone, which was named
> > > >
> > > > https://search.maven.org/artifact/org.apache.camel/camel-core/2.0-M1/bundle
> > > >
> > > >
> > > > So for 3.0 milestone 1, should we do that same?
> > > >
> > > > 3.0-M1
> > > >
> > > > Or is it
> > > >
> > > > 3.0.0-M1
> > > >
> > > > or 3.0.M1
> > > >
> > > > Just wonder what other projects do, and is there any implications for
> > > > OSGi etc we need to consider?
> > > >
> > > >
> > > > On Sat, Feb 9, 2019 at 2:01 PM Gregor Zurowski <[hidden email]> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > Yes, I'd be available for cutting the release next weekend.
> > > > >
> > > > > Thanks,
> > > > > Gregor
> > > > >
> > > > > On Fri, Feb 8, 2019 at 10:18 AM Andrea Cosentino
> > > > > <[hidden email]> wrote:
> > > > > >
> > > > > > Hello everybody,
> > > > > >
> > > > > > I think  we have enough material and we did enough development to release a first milestone for Camel 3.
> > > > > >
> > > > > > We can use the next week to finalize what we have and fixing the remaining tests
> > > > > >
> > > > > > Thoughts?
> > > > > >
> > > > > > Gregor, are you available to cut the release the weekend 16-17 February?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > --
> > > > > > Andrea Cosentino
> > > > > > ----------------------------------
> > > > > > Apache Camel PMC Chair
> > > > > > Apache Karaf Committer
> > > > > > Apache Servicemix PMC Member
> > > > > > Email: [hidden email]
> > > > > > Twitter: @oscerd2
> > > > > > Github: oscerd
> > > >
> > > >
> > > >
> > > > --
> > > > Claus Ibsen
> > > > -----------------
> > > > http://davsclaus.com @davsclaus
> > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > >
>


--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2