You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Pascal Schumacher <pa...@gmx.net> on 2018/05/07 19:09:41 UTC
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
The AS2 related failure is gone! :)
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/284/console
Sadly the build remains broken due because of the recently added
camel-example-ceylon:
[ERROR] Failed to execute goal
org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency (dependency)
on project camel-example-ceylon: Cannot import module
maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT: Jar file
/home/jenkins/jenkins-slave/workspace/Camel_master-CIGY56HHEDNGVJBWJRRHBZ64GKNJTCSYDKOPJS46W5IZTMAS3I2Q/camel-core/target/classes
is a directory (must be a file) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency
(dependency) on project camel-example-ceylon: Cannot import module
maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT
Despite numerous tries (and already some hacky commits) we haven't been
able to fix this.
At this point I suggest we revert this addition.
Are there any objections?
-Pascal
Am 07.05.2018 um 19:27 schrieb Pascal Schumacher:
> Hi Zoran,
>
> great work and great explanation, thank you very much! :)
>
> It now works for me locally.
>
> -Pascal
>
> Am 07.05.2018 um 11:52 schrieb Zoran Regvart:
>> Hi Cameleers,
>> I think I've found the core issue and committed a solution, we'll see
>> how the build goes.
>>
>> The issue was that we were using <classifier> to reference a javadoc
>> dependency, whereas we should be using <type>. I think when a
>> multi-module Maven build is run without the goal that produces the
>> artifact the <classifier> resolves the dependency as pointing to the
>> modules `target/classes` directory instead of the artifact that is
>> previously built, cached or available in a remote repository. This
>> changes if the artifact is already present in the Maven reactor, and
>> then it points to the artifact built in the target directory. And
>> again it changes if <classifier> is switched with <type> to resolve
>> from local repository or, I would assume, from remote repository.
>>
>> I could see this when running `mvn -X install` and `mvn -X test` -
>> that would fail; in `components/camel-as2` directory. The first would
>> output:
>>
>> [DEBUG] Adding project path
>> file:/.../components/camel-as2/camel-as2-api/target/camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar
>>
>>
>> And the second would output:
>>
>> [DEBUG] Adding project path
>> file:/.../components/camel-as2/camel-as2-api/target/classes/
>>
>> This changed when I changed the <classifier> to a <type> and now when
>> I run `mvn test` the javadoc dependency is picked up from my local
>> repository:
>>
>> [DEBUG] Adding project path
>> file:/.../.m2/repository/org/apache/camel/camel-as2-api/2.22.0-SNAPSHOT/camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar
>>
>>
>> I've changed all components that had <classifier>javadoc</classifier>
>> to <type>javadoc</type>, I hope this helps :)
>>
>> zoran
>
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Andrea,
I've commented on the PR, I don't think that will fix the issue. I
have a workaround in the works and after tests complete successfully I
will push. In a nutshell the workaround consists of doing the work of
`ceylon-maven-plugin:import-dependencies` via `ant-run-plugin`, i.e.
copying camel-core and camel-jetty dependencies into a directory
structure that Ceylon compiler expects.
Fingers crossed :)
zoran
On Tue, May 8, 2018 at 10:40 AM, Andrea Cosentino
<an...@yahoo.com.invalid> wrote:
> We have this fix now to merge:
>
> https://github.com/apache/camel/pull/2325
>
> Thinking on long-term I believe we need to move examples like these in other repositories, with other stuff like camel-scala etc.
>
> --
> Andrea Cosentino
> ----------------------------------
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1985@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Tuesday, May 8, 2018, 12:13:09 AM GMT+2, Willem Jiang <wi...@gmail.com> wrote:
>
>
>
>
>
> It looks like the ceylon-maven-plugin doesn't look up the jar files from
> the .m2 repository.
> Not sure if we can do the same magic of java doc here.
>
> BTW, I build the example separately without any issue.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, May 8, 2018 at 5:26 AM, Zoran Regvart <zo...@regvart.com> wrote:
>
>> Hi Pascal, Cameleers,
>> let me have a stab at it tomorrow, but baring that yeah I agree -- we
>> don't have the resources to maintain such an example perhaps it would
>> be best to remove it...
>>
>> zoran
>>
>> On Mon, May 7, 2018 at 9:09 PM, Pascal Schumacher
>> <pa...@gmx.net> wrote:
>> > The AS2 related failure is gone! :)
>> >
>> > https://builds.apache.org/view/C/view/Apache%20Camel/
>> job/Camel/job/master/284/console
>> >
>> > Sadly the build remains broken due because of the recently added
>> > camel-example-ceylon:
>> >
>> > [ERROR] Failed to execute goal
>> > org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency
>> (dependency) on
>> > project camel-example-ceylon: Cannot import module
>> > maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT: Jar file
>> > /home/jenkins/jenkins-slave/workspace/Camel_master-
>> CIGY56HHEDNGVJBWJRRHBZ64GKNJTCSYDKOPJS46W5IZTMAS3I2Q/camel-
>> core/target/classes
>> > is a directory (must be a file) -> [Help 1]
>> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute
>> > goal org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency
>> > (dependency) on project camel-example-ceylon: Cannot import module
>> > maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT
>> >
>> > Despite numerous tries (and already some hacky commits) we haven't been
>> able
>> > to fix this.
>> >
>> > At this point I suggest we revert this addition.
>> >
>> > Are there any objections?
>> >
>> > -Pascal
>> >
>> > Am 07.05.2018 um 19:27 schrieb Pascal Schumacher:
>> >>
>> >> Hi Zoran,
>> >>
>> >> great work and great explanation, thank you very much! :)
>> >>
>> >> It now works for me locally.
>> >>
>> >> -Pascal
>> >>
>> >> Am 07.05.2018 um 11:52 schrieb Zoran Regvart:
>> >>>
>> >>> Hi Cameleers,
>> >>> I think I've found the core issue and committed a solution, we'll see
>> >>> how the build goes.
>> >>>
>> >>> The issue was that we were using <classifier> to reference a javadoc
>> >>> dependency, whereas we should be using <type>. I think when a
>> >>> multi-module Maven build is run without the goal that produces the
>> >>> artifact the <classifier> resolves the dependency as pointing to the
>> >>> modules `target/classes` directory instead of the artifact that is
>> >>> previously built, cached or available in a remote repository. This
>> >>> changes if the artifact is already present in the Maven reactor, and
>> >>> then it points to the artifact built in the target directory. And
>> >>> again it changes if <classifier> is switched with <type> to resolve
>> >>> from local repository or, I would assume, from remote repository.
>> >>>
>> >>> I could see this when running `mvn -X install` and `mvn -X test` -
>> >>> that would fail; in `components/camel-as2` directory. The first would
>> >>> output:
>> >>>
>> >>> [DEBUG] Adding project path
>> >>>
>> >>> file:/.../components/camel-as2/camel-as2-api/target/
>> camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar
>> >>>
>> >>> And the second would output:
>> >>>
>> >>> [DEBUG] Adding project path
>> >>> file:/.../components/camel-as2/camel-as2-api/target/classes/
>> >>>
>> >>> This changed when I changed the <classifier> to a <type> and now when
>> >>> I run `mvn test` the javadoc dependency is picked up from my local
>> >>> repository:
>> >>>
>> >>> [DEBUG] Adding project path
>> >>>
>> >>> file:/.../.m2/repository/org/apache/camel/camel-as2-api/2.
>> 22.0-SNAPSHOT/camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar
>> >>>
>> >>> I've changed all components that had <classifier>javadoc</classifier>
>> >>> to <type>javadoc</type>, I hope this helps :)
>> >>>
>> >>> zoran
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Zoran Regvart
>>
--
Zoran Regvart
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
We have this fix now to merge:
https://github.com/apache/camel/pull/2325
Thinking on long-term I believe we need to move examples like these in other repositories, with other stuff like camel-scala etc.
--
Andrea Cosentino
----------------------------------
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Tuesday, May 8, 2018, 12:13:09 AM GMT+2, Willem Jiang <wi...@gmail.com> wrote:
It looks like the ceylon-maven-plugin doesn't look up the jar files from
the .m2 repository.
Not sure if we can do the same magic of java doc here.
BTW, I build the example separately without any issue.
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Tue, May 8, 2018 at 5:26 AM, Zoran Regvart <zo...@regvart.com> wrote:
> Hi Pascal, Cameleers,
> let me have a stab at it tomorrow, but baring that yeah I agree -- we
> don't have the resources to maintain such an example perhaps it would
> be best to remove it...
>
> zoran
>
> On Mon, May 7, 2018 at 9:09 PM, Pascal Schumacher
> <pa...@gmx.net> wrote:
> > The AS2 related failure is gone! :)
> >
> > https://builds.apache.org/view/C/view/Apache%20Camel/
> job/Camel/job/master/284/console
> >
> > Sadly the build remains broken due because of the recently added
> > camel-example-ceylon:
> >
> > [ERROR] Failed to execute goal
> > org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency
> (dependency) on
> > project camel-example-ceylon: Cannot import module
> > maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT: Jar file
> > /home/jenkins/jenkins-slave/workspace/Camel_master-
> CIGY56HHEDNGVJBWJRRHBZ64GKNJTCSYDKOPJS46W5IZTMAS3I2Q/camel-
> core/target/classes
> > is a directory (must be a file) -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute
> > goal org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency
> > (dependency) on project camel-example-ceylon: Cannot import module
> > maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT
> >
> > Despite numerous tries (and already some hacky commits) we haven't been
> able
> > to fix this.
> >
> > At this point I suggest we revert this addition.
> >
> > Are there any objections?
> >
> > -Pascal
> >
> > Am 07.05.2018 um 19:27 schrieb Pascal Schumacher:
> >>
> >> Hi Zoran,
> >>
> >> great work and great explanation, thank you very much! :)
> >>
> >> It now works for me locally.
> >>
> >> -Pascal
> >>
> >> Am 07.05.2018 um 11:52 schrieb Zoran Regvart:
> >>>
> >>> Hi Cameleers,
> >>> I think I've found the core issue and committed a solution, we'll see
> >>> how the build goes.
> >>>
> >>> The issue was that we were using <classifier> to reference a javadoc
> >>> dependency, whereas we should be using <type>. I think when a
> >>> multi-module Maven build is run without the goal that produces the
> >>> artifact the <classifier> resolves the dependency as pointing to the
> >>> modules `target/classes` directory instead of the artifact that is
> >>> previously built, cached or available in a remote repository. This
> >>> changes if the artifact is already present in the Maven reactor, and
> >>> then it points to the artifact built in the target directory. And
> >>> again it changes if <classifier> is switched with <type> to resolve
> >>> from local repository or, I would assume, from remote repository.
> >>>
> >>> I could see this when running `mvn -X install` and `mvn -X test` -
> >>> that would fail; in `components/camel-as2` directory. The first would
> >>> output:
> >>>
> >>> [DEBUG] Adding project path
> >>>
> >>> file:/.../components/camel-as2/camel-as2-api/target/
> camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar
> >>>
> >>> And the second would output:
> >>>
> >>> [DEBUG] Adding project path
> >>> file:/.../components/camel-as2/camel-as2-api/target/classes/
> >>>
> >>> This changed when I changed the <classifier> to a <type> and now when
> >>> I run `mvn test` the javadoc dependency is picked up from my local
> >>> repository:
> >>>
> >>> [DEBUG] Adding project path
> >>>
> >>> file:/.../.m2/repository/org/apache/camel/camel-as2-api/2.
> 22.0-SNAPSHOT/camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar
> >>>
> >>> I've changed all components that had <classifier>javadoc</classifier>
> >>> to <type>javadoc</type>, I hope this helps :)
> >>>
> >>> zoran
> >>
> >>
> >
>
>
>
> --
> Zoran Regvart
>
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Willem Jiang <wi...@gmail.com>.
It looks like the ceylon-maven-plugin doesn't look up the jar files from
the .m2 repository.
Not sure if we can do the same magic of java doc here.
BTW, I build the example separately without any issue.
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Tue, May 8, 2018 at 5:26 AM, Zoran Regvart <zo...@regvart.com> wrote:
> Hi Pascal, Cameleers,
> let me have a stab at it tomorrow, but baring that yeah I agree -- we
> don't have the resources to maintain such an example perhaps it would
> be best to remove it...
>
> zoran
>
> On Mon, May 7, 2018 at 9:09 PM, Pascal Schumacher
> <pa...@gmx.net> wrote:
> > The AS2 related failure is gone! :)
> >
> > https://builds.apache.org/view/C/view/Apache%20Camel/
> job/Camel/job/master/284/console
> >
> > Sadly the build remains broken due because of the recently added
> > camel-example-ceylon:
> >
> > [ERROR] Failed to execute goal
> > org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency
> (dependency) on
> > project camel-example-ceylon: Cannot import module
> > maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT: Jar file
> > /home/jenkins/jenkins-slave/workspace/Camel_master-
> CIGY56HHEDNGVJBWJRRHBZ64GKNJTCSYDKOPJS46W5IZTMAS3I2Q/camel-
> core/target/classes
> > is a directory (must be a file) -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute
> > goal org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency
> > (dependency) on project camel-example-ceylon: Cannot import module
> > maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT
> >
> > Despite numerous tries (and already some hacky commits) we haven't been
> able
> > to fix this.
> >
> > At this point I suggest we revert this addition.
> >
> > Are there any objections?
> >
> > -Pascal
> >
> > Am 07.05.2018 um 19:27 schrieb Pascal Schumacher:
> >>
> >> Hi Zoran,
> >>
> >> great work and great explanation, thank you very much! :)
> >>
> >> It now works for me locally.
> >>
> >> -Pascal
> >>
> >> Am 07.05.2018 um 11:52 schrieb Zoran Regvart:
> >>>
> >>> Hi Cameleers,
> >>> I think I've found the core issue and committed a solution, we'll see
> >>> how the build goes.
> >>>
> >>> The issue was that we were using <classifier> to reference a javadoc
> >>> dependency, whereas we should be using <type>. I think when a
> >>> multi-module Maven build is run without the goal that produces the
> >>> artifact the <classifier> resolves the dependency as pointing to the
> >>> modules `target/classes` directory instead of the artifact that is
> >>> previously built, cached or available in a remote repository. This
> >>> changes if the artifact is already present in the Maven reactor, and
> >>> then it points to the artifact built in the target directory. And
> >>> again it changes if <classifier> is switched with <type> to resolve
> >>> from local repository or, I would assume, from remote repository.
> >>>
> >>> I could see this when running `mvn -X install` and `mvn -X test` -
> >>> that would fail; in `components/camel-as2` directory. The first would
> >>> output:
> >>>
> >>> [DEBUG] Adding project path
> >>>
> >>> file:/.../components/camel-as2/camel-as2-api/target/
> camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar
> >>>
> >>> And the second would output:
> >>>
> >>> [DEBUG] Adding project path
> >>> file:/.../components/camel-as2/camel-as2-api/target/classes/
> >>>
> >>> This changed when I changed the <classifier> to a <type> and now when
> >>> I run `mvn test` the javadoc dependency is picked up from my local
> >>> repository:
> >>>
> >>> [DEBUG] Adding project path
> >>>
> >>> file:/.../.m2/repository/org/apache/camel/camel-as2-api/2.
> 22.0-SNAPSHOT/camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar
> >>>
> >>> I've changed all components that had <classifier>javadoc</classifier>
> >>> to <type>javadoc</type>, I hope this helps :)
> >>>
> >>> zoran
> >>
> >>
> >
>
>
>
> --
> Zoran Regvart
>
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Pascal, Cameleers,
let me have a stab at it tomorrow, but baring that yeah I agree -- we
don't have the resources to maintain such an example perhaps it would
be best to remove it...
zoran
On Mon, May 7, 2018 at 9:09 PM, Pascal Schumacher
<pa...@gmx.net> wrote:
> The AS2 related failure is gone! :)
>
> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/284/console
>
> Sadly the build remains broken due because of the recently added
> camel-example-ceylon:
>
> [ERROR] Failed to execute goal
> org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency (dependency) on
> project camel-example-ceylon: Cannot import module
> maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT: Jar file
> /home/jenkins/jenkins-slave/workspace/Camel_master-CIGY56HHEDNGVJBWJRRHBZ64GKNJTCSYDKOPJS46W5IZTMAS3I2Q/camel-core/target/classes
> is a directory (must be a file) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.ceylon-lang:ceylon-maven-plugin:1.3.3:import-dependency
> (dependency) on project camel-example-ceylon: Cannot import module
> maven:org.apache.camel.camel-core/2.22.0-SNAPSHOT
>
> Despite numerous tries (and already some hacky commits) we haven't been able
> to fix this.
>
> At this point I suggest we revert this addition.
>
> Are there any objections?
>
> -Pascal
>
> Am 07.05.2018 um 19:27 schrieb Pascal Schumacher:
>>
>> Hi Zoran,
>>
>> great work and great explanation, thank you very much! :)
>>
>> It now works for me locally.
>>
>> -Pascal
>>
>> Am 07.05.2018 um 11:52 schrieb Zoran Regvart:
>>>
>>> Hi Cameleers,
>>> I think I've found the core issue and committed a solution, we'll see
>>> how the build goes.
>>>
>>> The issue was that we were using <classifier> to reference a javadoc
>>> dependency, whereas we should be using <type>. I think when a
>>> multi-module Maven build is run without the goal that produces the
>>> artifact the <classifier> resolves the dependency as pointing to the
>>> modules `target/classes` directory instead of the artifact that is
>>> previously built, cached or available in a remote repository. This
>>> changes if the artifact is already present in the Maven reactor, and
>>> then it points to the artifact built in the target directory. And
>>> again it changes if <classifier> is switched with <type> to resolve
>>> from local repository or, I would assume, from remote repository.
>>>
>>> I could see this when running `mvn -X install` and `mvn -X test` -
>>> that would fail; in `components/camel-as2` directory. The first would
>>> output:
>>>
>>> [DEBUG] Adding project path
>>>
>>> file:/.../components/camel-as2/camel-as2-api/target/camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar
>>>
>>> And the second would output:
>>>
>>> [DEBUG] Adding project path
>>> file:/.../components/camel-as2/camel-as2-api/target/classes/
>>>
>>> This changed when I changed the <classifier> to a <type> and now when
>>> I run `mvn test` the javadoc dependency is picked up from my local
>>> repository:
>>>
>>> [DEBUG] Adding project path
>>>
>>> file:/.../.m2/repository/org/apache/camel/camel-as2-api/2.22.0-SNAPSHOT/camel-as2-api-2.22.0-SNAPSHOT-javadoc.jar
>>>
>>> I've changed all components that had <classifier>javadoc</classifier>
>>> to <type>javadoc</type>, I hope this helps :)
>>>
>>> zoran
>>
>>
>
--
Zoran Regvart
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Zoran Regvart <zo...@regvart.com>.
Awesome work everyone, I see we got a successful build!
Thanks!
zoran
On Thu, May 10, 2018 at 2:57 PM, Tomohisa Igarashi
<tm...@gmail.com> wrote:
> Good morning - whoa, it was supposed to be my breakfast ;-)
>
> Anyway good catch guys!
>
> Thanks,
> Tomo
>
>
> On Thu, 2018-05-10 at 14:15 +0300, Onder SEZGIN wrote:
>> yes i managed to do it same locally.
>> the reason of the issue is still here.
>>
>> https://www.mail-archive.com/search?l=users@tomee.apache.org&q=subject:%22Re%5C%3A+Java+8+Type+Annotations+cause+error+%5C-+is+that+expected%5C%3F%22&o=newest&f=1
>>
>> excluding shaded dependency from latest release of openejb and adding it
>> dependency list of component seems resolving it.
>> not sure if it is a good practice but maybe we can do it till xbean
>> upgraded in openejb.
>>
>> On Thu, May 10, 2018 at 1:38 PM, Babak Vahdat <ba...@swissonline.ch>
>> wrote:
>>
>> > Hi
>> >
>> > I managed to fix the failing camel-ejb tests locally. Let’s wait for the
>> > next CI-build.
>> >
>> > Babak
>> >
>> > > On 10 May 2018, at 07:39, Onder SEZGIN <on...@gmail.com> wrote:
>> > >
>> > > Interestingly, it does not fail in IDE(intellij).
>> > > It fails on mvn prompt as Tomohisa mentioned.
>> > > after running mvn clean on the prompt and fire the test on IDE, it is ok.
>> > > i did not dive into it yet.
>> > > this is my initial observation.
>> > >
>> > > On Thu, May 10, 2018 at 1:16 AM, Tomohisa Igarashi <
>> >
>> > tm.igarashi@gmail.com>
>> > > wrote:
>> > >
>> > > > Yep, actually this fails for me. I noticed that I get this weird
>> >
>> > exception
>> > > > when I run "mvn test -Dtest=GreaterTest"
>> > > > -----------------------------
>> > > > WARNING - Unable to scrape for @Stateful, @Stateless, @Singleton or
>> > > > @MessageDriven annotations. AnnotationFinder failed.
>> > > > java.lang.RuntimeException
>> > > > at org.apache.xbean.asm5.MethodVisitor.visitParameter(Unknown
>> > > > Source)
>> > > > at org.apache.xbean.asm5.ClassReader.b(Unknown Source)
>> > > > at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
>> > > > at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
>> > > > at org.apache.xbean.finder.AnnotationFinder.readClassDef(
>> > > > AnnotationFinder.java:1170)
>> > > > ...
>> > > > -----------------------------
>> > > >
>> > > > I found a SO thread saying OpenEJB 4.6 + JDK8 get similar symptom, but
>> > > > we're using OpenEJB 4.7.5 and shouldn't be a problem...
>> > > >
>> > > > Thanks,
>> > > > Tomo
>> > > >
>> > > > On Thu, 2018-05-10 at 00:09 +0200, Zoran Regvart wrote:
>> > > > > On Wed, May 9, 2018 at 5:40 PM, Onder SEZGIN <on...@apache.org>
>> >
>> > wrote:
>> > > > > > I can help with some of them by tomorrow.
>> > > > >
>> > > > > Awesome, thank you. I think Tomohisa is also taking a look. Now only
>> > > > > the camel-ejb tests are failing[1]. Its strange I can't reproduce this
>> > > > > locally, other failures were pretty straightforward to fix, I can't
>> > > > > wrap my head around this one,
>> > > > >
>> > > > > zoran
>> > > > >
>> > > > > [1] https://builds.apache.org/view/C/view/Apache%20Camel/
>> > > >
>> > > > job/Camel/job/master/lastCompletedBuild/testReport/
>> > > >
>> >
>> >
--
Zoran Regvart
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Tomohisa Igarashi <tm...@gmail.com>.
Good morning - whoa, it was supposed to be my breakfast ;-)
Anyway good catch guys!
Thanks,
Tomo
On Thu, 2018-05-10 at 14:15 +0300, Onder SEZGIN wrote:
> yes i managed to do it same locally.
> the reason of the issue is still here.
>
> https://www.mail-archive.com/search?l=users@tomee.apache.org&q=subject:%22Re%5C%3A+Java+8+Type+Annotations+cause+error+%5C-+is+that+expected%5C%3F%22&o=newest&f=1
>
> excluding shaded dependency from latest release of openejb and adding it
> dependency list of component seems resolving it.
> not sure if it is a good practice but maybe we can do it till xbean
> upgraded in openejb.
>
> On Thu, May 10, 2018 at 1:38 PM, Babak Vahdat <ba...@swissonline.ch>
> wrote:
>
> > Hi
> >
> > I managed to fix the failing camel-ejb tests locally. Let’s wait for the
> > next CI-build.
> >
> > Babak
> >
> > > On 10 May 2018, at 07:39, Onder SEZGIN <on...@gmail.com> wrote:
> > >
> > > Interestingly, it does not fail in IDE(intellij).
> > > It fails on mvn prompt as Tomohisa mentioned.
> > > after running mvn clean on the prompt and fire the test on IDE, it is ok.
> > > i did not dive into it yet.
> > > this is my initial observation.
> > >
> > > On Thu, May 10, 2018 at 1:16 AM, Tomohisa Igarashi <
> >
> > tm.igarashi@gmail.com>
> > > wrote:
> > >
> > > > Yep, actually this fails for me. I noticed that I get this weird
> >
> > exception
> > > > when I run "mvn test -Dtest=GreaterTest"
> > > > -----------------------------
> > > > WARNING - Unable to scrape for @Stateful, @Stateless, @Singleton or
> > > > @MessageDriven annotations. AnnotationFinder failed.
> > > > java.lang.RuntimeException
> > > > at org.apache.xbean.asm5.MethodVisitor.visitParameter(Unknown
> > > > Source)
> > > > at org.apache.xbean.asm5.ClassReader.b(Unknown Source)
> > > > at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
> > > > at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
> > > > at org.apache.xbean.finder.AnnotationFinder.readClassDef(
> > > > AnnotationFinder.java:1170)
> > > > ...
> > > > -----------------------------
> > > >
> > > > I found a SO thread saying OpenEJB 4.6 + JDK8 get similar symptom, but
> > > > we're using OpenEJB 4.7.5 and shouldn't be a problem...
> > > >
> > > > Thanks,
> > > > Tomo
> > > >
> > > > On Thu, 2018-05-10 at 00:09 +0200, Zoran Regvart wrote:
> > > > > On Wed, May 9, 2018 at 5:40 PM, Onder SEZGIN <on...@apache.org>
> >
> > wrote:
> > > > > > I can help with some of them by tomorrow.
> > > > >
> > > > > Awesome, thank you. I think Tomohisa is also taking a look. Now only
> > > > > the camel-ejb tests are failing[1]. Its strange I can't reproduce this
> > > > > locally, other failures were pretty straightforward to fix, I can't
> > > > > wrap my head around this one,
> > > > >
> > > > > zoran
> > > > >
> > > > > [1] https://builds.apache.org/view/C/view/Apache%20Camel/
> > > >
> > > > job/Camel/job/master/lastCompletedBuild/testReport/
> > > >
> >
> >
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Onder SEZGIN <on...@gmail.com>.
yes i managed to do it same locally.
the reason of the issue is still here.
https://www.mail-archive.com/search?l=users@tomee.apache.org&q=subject:%22Re%5C%3A+Java+8+Type+Annotations+cause+error+%5C-+is+that+expected%5C%3F%22&o=newest&f=1
excluding shaded dependency from latest release of openejb and adding it
dependency list of component seems resolving it.
not sure if it is a good practice but maybe we can do it till xbean
upgraded in openejb.
On Thu, May 10, 2018 at 1:38 PM, Babak Vahdat <ba...@swissonline.ch>
wrote:
> Hi
>
> I managed to fix the failing camel-ejb tests locally. Let’s wait for the
> next CI-build.
>
> Babak
>
> > On 10 May 2018, at 07:39, Onder SEZGIN <on...@gmail.com> wrote:
> >
> > Interestingly, it does not fail in IDE(intellij).
> > It fails on mvn prompt as Tomohisa mentioned.
> > after running mvn clean on the prompt and fire the test on IDE, it is ok.
> > i did not dive into it yet.
> > this is my initial observation.
> >
> > On Thu, May 10, 2018 at 1:16 AM, Tomohisa Igarashi <
> tm.igarashi@gmail.com>
> > wrote:
> >
> >> Yep, actually this fails for me. I noticed that I get this weird
> exception
> >> when I run "mvn test -Dtest=GreaterTest"
> >> -----------------------------
> >> WARNING - Unable to scrape for @Stateful, @Stateless, @Singleton or
> >> @MessageDriven annotations. AnnotationFinder failed.
> >> java.lang.RuntimeException
> >> at org.apache.xbean.asm5.MethodVisitor.visitParameter(Unknown
> >> Source)
> >> at org.apache.xbean.asm5.ClassReader.b(Unknown Source)
> >> at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
> >> at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
> >> at org.apache.xbean.finder.AnnotationFinder.readClassDef(
> >> AnnotationFinder.java:1170)
> >> ...
> >> -----------------------------
> >>
> >> I found a SO thread saying OpenEJB 4.6 + JDK8 get similar symptom, but
> >> we're using OpenEJB 4.7.5 and shouldn't be a problem...
> >>
> >> Thanks,
> >> Tomo
> >>
> >> On Thu, 2018-05-10 at 00:09 +0200, Zoran Regvart wrote:
> >>> On Wed, May 9, 2018 at 5:40 PM, Onder SEZGIN <on...@apache.org>
> wrote:
> >>>> I can help with some of them by tomorrow.
> >>>
> >>> Awesome, thank you. I think Tomohisa is also taking a look. Now only
> >>> the camel-ejb tests are failing[1]. Its strange I can't reproduce this
> >>> locally, other failures were pretty straightforward to fix, I can't
> >>> wrap my head around this one,
> >>>
> >>> zoran
> >>>
> >>> [1] https://builds.apache.org/view/C/view/Apache%20Camel/
> >> job/Camel/job/master/lastCompletedBuild/testReport/
> >>
>
>
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi
I managed to fix the failing camel-ejb tests locally. Let’s wait for the next CI-build.
Babak
> On 10 May 2018, at 07:39, Onder SEZGIN <on...@gmail.com> wrote:
>
> Interestingly, it does not fail in IDE(intellij).
> It fails on mvn prompt as Tomohisa mentioned.
> after running mvn clean on the prompt and fire the test on IDE, it is ok.
> i did not dive into it yet.
> this is my initial observation.
>
> On Thu, May 10, 2018 at 1:16 AM, Tomohisa Igarashi <tm...@gmail.com>
> wrote:
>
>> Yep, actually this fails for me. I noticed that I get this weird exception
>> when I run "mvn test -Dtest=GreaterTest"
>> -----------------------------
>> WARNING - Unable to scrape for @Stateful, @Stateless, @Singleton or
>> @MessageDriven annotations. AnnotationFinder failed.
>> java.lang.RuntimeException
>> at org.apache.xbean.asm5.MethodVisitor.visitParameter(Unknown
>> Source)
>> at org.apache.xbean.asm5.ClassReader.b(Unknown Source)
>> at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
>> at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
>> at org.apache.xbean.finder.AnnotationFinder.readClassDef(
>> AnnotationFinder.java:1170)
>> ...
>> -----------------------------
>>
>> I found a SO thread saying OpenEJB 4.6 + JDK8 get similar symptom, but
>> we're using OpenEJB 4.7.5 and shouldn't be a problem...
>>
>> Thanks,
>> Tomo
>>
>> On Thu, 2018-05-10 at 00:09 +0200, Zoran Regvart wrote:
>>> On Wed, May 9, 2018 at 5:40 PM, Onder SEZGIN <on...@apache.org> wrote:
>>>> I can help with some of them by tomorrow.
>>>
>>> Awesome, thank you. I think Tomohisa is also taking a look. Now only
>>> the camel-ejb tests are failing[1]. Its strange I can't reproduce this
>>> locally, other failures were pretty straightforward to fix, I can't
>>> wrap my head around this one,
>>>
>>> zoran
>>>
>>> [1] https://builds.apache.org/view/C/view/Apache%20Camel/
>> job/Camel/job/master/lastCompletedBuild/testReport/
>>
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Onder SEZGIN <on...@gmail.com>.
Interestingly, it does not fail in IDE(intellij).
It fails on mvn prompt as Tomohisa mentioned.
after running mvn clean on the prompt and fire the test on IDE, it is ok.
i did not dive into it yet.
this is my initial observation.
On Thu, May 10, 2018 at 1:16 AM, Tomohisa Igarashi <tm...@gmail.com>
wrote:
> Yep, actually this fails for me. I noticed that I get this weird exception
> when I run "mvn test -Dtest=GreaterTest"
> -----------------------------
> WARNING - Unable to scrape for @Stateful, @Stateless, @Singleton or
> @MessageDriven annotations. AnnotationFinder failed.
> java.lang.RuntimeException
> at org.apache.xbean.asm5.MethodVisitor.visitParameter(Unknown
> Source)
> at org.apache.xbean.asm5.ClassReader.b(Unknown Source)
> at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
> at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
> at org.apache.xbean.finder.AnnotationFinder.readClassDef(
> AnnotationFinder.java:1170)
> ...
> -----------------------------
>
> I found a SO thread saying OpenEJB 4.6 + JDK8 get similar symptom, but
> we're using OpenEJB 4.7.5 and shouldn't be a problem...
>
> Thanks,
> Tomo
>
> On Thu, 2018-05-10 at 00:09 +0200, Zoran Regvart wrote:
> > On Wed, May 9, 2018 at 5:40 PM, Onder SEZGIN <on...@apache.org> wrote:
> > > I can help with some of them by tomorrow.
> >
> > Awesome, thank you. I think Tomohisa is also taking a look. Now only
> > the camel-ejb tests are failing[1]. Its strange I can't reproduce this
> > locally, other failures were pretty straightforward to fix, I can't
> > wrap my head around this one,
> >
> > zoran
> >
> > [1] https://builds.apache.org/view/C/view/Apache%20Camel/
> job/Camel/job/master/lastCompletedBuild/testReport/
>
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Tomohisa Igarashi <tm...@gmail.com>.
Yep, actually this fails for me. I noticed that I get this weird exception when I run "mvn test -Dtest=GreaterTest"
-----------------------------
WARNING - Unable to scrape for @Stateful, @Stateless, @Singleton or @MessageDriven annotations. AnnotationFinder failed.
java.lang.RuntimeException
at org.apache.xbean.asm5.MethodVisitor.visitParameter(Unknown Source)
at org.apache.xbean.asm5.ClassReader.b(Unknown Source)
at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
at org.apache.xbean.asm5.ClassReader.accept(Unknown Source)
at org.apache.xbean.finder.AnnotationFinder.readClassDef(AnnotationFinder.java:1170)
...
-----------------------------
I found a SO thread saying OpenEJB 4.6 + JDK8 get similar symptom, but we're using OpenEJB 4.7.5 and shouldn't be a problem...
Thanks,
Tomo
On Thu, 2018-05-10 at 00:09 +0200, Zoran Regvart wrote:
> On Wed, May 9, 2018 at 5:40 PM, Onder SEZGIN <on...@apache.org> wrote:
> > I can help with some of them by tomorrow.
>
> Awesome, thank you. I think Tomohisa is also taking a look. Now only
> the camel-ejb tests are failing[1]. Its strange I can't reproduce this
> locally, other failures were pretty straightforward to fix, I can't
> wrap my head around this one,
>
> zoran
>
> [1] https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/lastCompletedBuild/testReport/
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Zoran Regvart <zo...@regvart.com>.
On Wed, May 9, 2018 at 5:40 PM, Onder SEZGIN <on...@apache.org> wrote:
> I can help with some of them by tomorrow.
Awesome, thank you. I think Tomohisa is also taking a look. Now only
the camel-ejb tests are failing[1]. Its strange I can't reproduce this
locally, other failures were pretty straightforward to fix, I can't
wrap my head around this one,
zoran
[1] https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/lastCompletedBuild/testReport/
--
Zoran Regvart
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Onder SEZGIN <on...@apache.org>.
I can help with some of them by tomorrow.
On Wed, 9 May 2018 at 17:56, Pascal Schumacher <pa...@gmx.net>
wrote:
> Hi Zoran,
>
> thank you very much for fixing this. :)
>
> -Pascal
>
> Am 09.05.2018 um 10:10 schrieb Zoran Regvart:
> > Hi Cameleers,
> > we managed to get the Ceylon example to compile without the JAR
> > artefact being attached to the Maven reactor, this was required by the
> > Ceylon Maven plugin's goal to import dependencies. You can take a look
> > at this commit[1] for the details of the workaround.
> >
> > Now we have 21 tests that have failed, I'll try to take a look at some
> > of those, if anyone else has some time to take a look that would be
> > very welcome, ping me on IRC or Gitter so we don't overlap.
> >
> > Thanks to everyone on this effort, I now it's a bit tedious and the
> > long iteration times slow you down
> >
> > zoran
> >
> > [1]
> https://gitbox.apache.org/repos/asf?p=camel.git;a=commitdiff;h=4851da7738ac9dede4cb7f823ccce85bf6a8d4e5
>
>
>
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Pascal Schumacher <pa...@gmx.net>.
Hi Zoran,
thank you very much for fixing this. :)
-Pascal
Am 09.05.2018 um 10:10 schrieb Zoran Regvart:
> Hi Cameleers,
> we managed to get the Ceylon example to compile without the JAR
> artefact being attached to the Maven reactor, this was required by the
> Ceylon Maven plugin's goal to import dependencies. You can take a look
> at this commit[1] for the details of the workaround.
>
> Now we have 21 tests that have failed, I'll try to take a look at some
> of those, if anyone else has some time to take a look that would be
> very welcome, ping me on IRC or Gitter so we don't overlap.
>
> Thanks to everyone on this effort, I now it's a bit tedious and the
> long iteration times slow you down
>
> zoran
>
> [1] https://gitbox.apache.org/repos/asf?p=camel.git;a=commitdiff;h=4851da7738ac9dede4cb7f823ccce85bf6a8d4e5
Re: Build fails since AS2 component was added (camel-example-ceylon
breaks build)
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
we managed to get the Ceylon example to compile without the JAR
artefact being attached to the Maven reactor, this was required by the
Ceylon Maven plugin's goal to import dependencies. You can take a look
at this commit[1] for the details of the workaround.
Now we have 21 tests that have failed, I'll try to take a look at some
of those, if anyone else has some time to take a look that would be
very welcome, ping me on IRC or Gitter so we don't overlap.
Thanks to everyone on this effort, I now it's a bit tedious and the
long iteration times slow you down
zoran
[1] https://gitbox.apache.org/repos/asf?p=camel.git;a=commitdiff;h=4851da7738ac9dede4cb7f823ccce85bf6a8d4e5
--
Zoran Regvart