Hi,

I've added the enforceBytecodeVersion rule to see which jar(s) are causing problems.
It seems that aspectjtools can't run with JDK5.
As long as org.aspectj.tools.ajc.Main.Main() is called within the same JVM, we need to upgrade the JDK requirement. Otherwise we need to start a new JVM, preferably with toolchains to manage the JDK versions. Not sure if it's worth it to implement, though.

For me this is a valid reason to change the required JDK, I'll leave it up to you.

Robert

Op Tue, 02 Sep 2014 23:00:26 +0200 schreef Robert Scholte <codeh...@sourcegrounds.com>:

Hi,

I've fixed the unittest, next step is to fix the integration tests.
I've added a JDK8 task to the integration tests, so now it will be tested with the minimum (JDK5) and maximum, both with Maven-2.2.1. There are only linux bambooo-agents available right now. According to JIRA[1] there has never been a request to support more operating systems, so go ahead and ask. In the meantime I can verify it with Win7 + most of the JDKs available at home.

thanks,
Robert

ps. to log on and configure: https://bamboo-ci.codehaus.org/userlogin!default.action

[1] https://jira.codehaus.org/browse/HAUS/component/12684


Op Tue, 02 Sep 2014 21:25:33 +0200 schreef Dan Tran <dant...@gmail.com>:

Hi Anders, Robert, Karl

Are you able to help with this issue at bamboo setup?

Thanks

-D


On Tue, Sep 2, 2014 at 10:33 AM, Lennart Jörelid <lennart.jore...@gmail.com>
wrote:

We need to set up a few projects in Bamboo where the aspectj_maven_plugin
is compiled using different kinds of JDKs. This is to validate that the
AspectJ compiler options for the respective JDKs do not cause

java.lang.UnsupportedClassVersionError: Bad version number in .class file
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)


... as is currently the case with a unit/integration test for the AspectJ
maven plugin.

We would also really need a Windows execution environment on Codehaus
Bamboo - although I'm aware that this is stretching things a bit. This is simply to ensure that none of our ITs and plugins fail to properly encode
paths and other OS-specific things.


2014-09-02 18:30 GMT+02:00 Dan Tran <dant...@gmail.com>:

what do we need from codehaus bamboo?

Thanks

-D


On Tue, Sep 2, 2014 at 9:06 AM, Lennart Jörelid <
lennart.jore...@gmail.com> wrote:

No, we should not.

https://bamboo-ci.codehaus.org/browse/MOJO-MASPECTJ

Fails since we have been unable - thus far - to create a new project
with JDK 8 support.
If we could get that done, we would be one step closer to release.


2014-09-02 17:46 GMT+02:00 Dan Tran <dant...@gmail.com>:

should we go ehead to push this release out?

Thanks

-D


On Wed, Aug 20, 2014 at 12:08 PM, Anders Hammar <and...@hammar.net>
wrote:

I filed a ticket for this:
http://jira.codehaus.org/browse/MASPECTJ-135

Feel free to add more info as you see fit.

/Anders


On Wed, Aug 20, 2014 at 3:56 PM, Dan Tran <dant...@gmail.com> wrote:

Hi Sergei, you are right, i have a convenient script to 'cd' into my
dev tree like this

@echo off
cd c:\views\dev


so the fix is ( for now)

@echo off
cd C:\views\dev





On Tue, Aug 19, 2014 at 11:35 PM, Sergei Ivanov <
sergei_iva...@mail.ru> wrote:

Hi Dan,

Looks like the drive letter C: differs in case between expected and actual. You may want to change the test script to use case-insensitive
comparison on windows.

Regards,
--
Sergei Ivanov



Wednesday, 20 August 2014 07:26 +0100 from Dan Tran <
dant...@gmail.com>:

no problem building on linux for both java 7 and 8

also works inside my windows eclipse IDE.

Must have someting to do with my env.

Thanks

-D

On Tue, Aug 19, 2014 at 11:04 PM, Dan Tran < dant...@gmail.com >
wrote:
>not sure why, but i am not able to build it locally using both java
7 and 8  on windows (have not try it on linux yet )
>
>[INFO] Building: JavaSourcesDefault\pom.xml
>[INFO] run script verify.groovy
>[INFO] ..FAILED (2.7 s)
>[INFO]   The post-build script did not succeed. assert
execLine.endsWith( fooClazz.getAbsolutePath() )
>       |        |         |        |
>       |        false     |
 
c:\views\dev\mojo\mojo\aspectj-maven-plugin\target\it\JavaSourcesDefault\src\main\java\foo\Clazz.java
>       |
 
c:\views\dev\mojo\mojo\aspectj-maven-plugin\target\it\JavaSourcesDefault\src\main\java\foo\Clazz.java
>       [DEBUG] Running : ajc -1.4 -classpath
C:\views\dev\mojo\mojo\aspectj-maven-plugin\target\local-repo\org\aspectj\aspectjrt\1.8.0\aspectjrt-1.8.0.jar;C:\views\dev\mojo\mojo\aspectj-maven-plugin\t
>arget\it\JavaSourcesDefault\target\classes -d
C:\views\dev\mojo\mojo\aspectj-maven-plugin\target\it\JavaSourcesDefault\target\classes
C:\views\dev\mojo\mojo\aspectj-maven-plugin\target\it\JavaSourcesD
>efault\src\main\java\foo\Clazz.java
>[INFO] Building: JavaSourcesEmpty\pom.xml
>[INFO] run script verify.groovy
>[INFO] ..SUCCESS (2.1 s)
>[INFO] Building: JavaSourcesList\pom.xml
>[INFO] run script verify.groovy
>[INFO] ..FAILED (2.5 s)
>[INFO]   The post-build script did not succeed. assert
execLine.endsWith( fooClazz.getAbsolutePath() )
>       |        |         |        |
>       |        false     |
 
c:\views\dev\mojo\mojo\aspectj-maven-plugin\target\it\JavaSourcesList\src\java\foo\Clazz.java
>       |
 
c:\views\dev\mojo\mojo\aspectj-maven-plugin\target\it\JavaSourcesList\src\java\foo\Clazz.java
>       [DEBUG] Running : ajc -1.4 -classpath
C:\views\dev\mojo\mojo\aspectj-maven-plugin\target\local-repo\org\aspectj\aspectjrt\1.8.0\aspectjrt-1.8.0.jar;C:\views\dev\mojo\mojo\aspectj-maven-plugin\t
>arget\it\JavaSourcesList\target\classes -d
C:\views\dev\mojo\mojo\aspectj-maven-plugin\target\it\JavaSourcesList\target\classes
C:\views\dev\mojo\mojo\aspectj-maven-plugin\target\it\JavaSourcesList\sr
>c\java\foo\Clazz.java
>
>
>
>On Tue, Aug 19, 2014 at 10:44 PM, Lennart Jörelid <
lennart.jore...@gmail.com > wrote:
>>Yes.
>>
>>We have presently some Bamboo setup issues, but the code has built
locally for me since quite awhile.
>>Thus, it is presently more of a Bamboo issue than a development
one.
>>
>>
>>2014-08-19 22:42 GMT+02:00 Dan Tran < dant...@gmail.com > :
>>
>>>Hello MOJO team,
>>>
>>>any plan to push 1.7 out for JDK 8 support?
>>>
>>>Thanks
>>>
>>>-D
>>
>>
>>--
>>--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: l...@jguru.se
| URL: www.jguru.se
| Phone
| (skype): jgurueurope
| (intl): +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+







--

--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: l...@jguru.se
| URL:   www.jguru.se
| Phone
| (skype):    jgurueurope
| (intl):     +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+





--

--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: l...@jguru.se
| URL:   www.jguru.se
| Phone
| (skype):    jgurueurope
| (intl):     +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to