[mojo-dev] [jira] (MAPPASM-224) Make Plugin Java 5 Ready

[Dennis Lundberg (JIRA)]

Title: Message Title










 

 Dennis Lundberg updated an issue











 






 Mojo's AppAssembler Maven Plugin /  MAPPASM-224



  Make Plugin Java 5 Ready 










This means that we need to update mojo-parent to version 31 or newer.










Change By:

 Dennis Lundberg




Fix Version/s:

 1.8












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] Re: [Bamboo] MOJO > appassembler-plugin > #251 has FAILED. Change made by dennisl.

[Dennis Lundberg]

Does anyone know how I can access the workspace folder in Bamboo? So that I
can have a look at what the failing IT actually produced.
This might be OS-related, because the ITs passed on my Windows machine.
Will try on my virtual Ubuntu later.


On Fri, Mar 14, 2014 at 5:18 PM, Codehaus Bamboo  wrote:

>  [image: Failed]  MOJO  ›
> appassembler-plugin ›
> #251  failed
>
> Changes by dennisl 
>
> *0/43* tests failed.
>   Responsible  dennisl 
> Automatically
> assigned
>   Failing Jobs 
> Job Duration Tests[image: Failed]  Integration 
> Tests (Default
> Stage)  3 minutes  43 passed  
> Logs|
> Artifacts
>  Code
> Changes   View
> full change 
> details
> dennisl 
> Add used but undeclared dependencies.  19551 View 
> Online
> | Add 
> Comments
>
> This message was sent by Atlassian Bamboo .
>
> If you wish to stop receiving these emails edit your user 
> profileor 
> notify
> your administrator
> .
>



-- 
Dennis Lundberg

Re: [mojo-dev] Re: [Bamboo] MOJO > appassembler-plugin > #251 has FAILED. Change made by dennisl.

[Anders Hammar]

You need to configure an artifact in bamboo. Have a look at the jaxb2-m-p
job and what we've done there.

/Anders (mobile)
Den 14 mar 2014 23:25 skrev "Dennis Lundberg" :

> Does anyone know how I can access the workspace folder in Bamboo? So that
> I can have a look at what the failing IT actually produced.
> This might be OS-related, because the ITs passed on my Windows machine.
> Will try on my virtual Ubuntu later.
>
>
> On Fri, Mar 14, 2014 at 5:18 PM, Codehaus Bamboo <
> bamboo-ser...@codehaus.org> wrote:
>
>>  [image: Failed]  MOJO ›
>> appassembler-plugin ›
>> #251  failed
>>
>> Changes by dennisl 
>>
>> *0/43* tests failed.
>>   Responsible  
>> dennisl Automatically
>> assigned
>>Failing Jobs 
>> Job
>> Duration Tests[image: Failed]  Integration 
>> Tests (Default
>> Stage)  3 minutes  43 passed  
>> Logs|
>> Artifacts
>>  Code
>> Changes   View
>> full change 
>> details
>> dennisl 
>> Add used but undeclared dependencies.  19551 View 
>> Online
>> | Add 
>> Comments
>>
>> This message was sent by Atlassian Bamboo 
>> .
>>
>> If you wish to stop receiving these emails edit your user 
>> profileor 
>> notify
>> your administrator
>> .
>>
>
>
>
> --
> Dennis Lundberg
>

Re: [mojo-dev] Re: [Bamboo] MOJO > appassembler-plugin > #251 has FAILED. Change made by dennisl.

[Karl Heinz Marbaise]

Hi Dennis,

It looks like an ordering problem...Maven 2.2.1 on my Mac fails as 
well...I would assume that the ordering within the classpath
is different but the verify script checks only the complete line which 
is sensible on changed orders of artifacts.



build	14-Mar-2014 11:17:56	[INFO]   The post-build script did not 
succeed. The expected content in 
/opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-5.3/xml-data/build-dir/MOJO-MAPPASM-JOB1/appassembler-maven-plugin/target/it/shellDaemonGeneratorTest/target/appassembler/bin/app 
couldn't be 
found.CLASSPATH="$BASEDIR"/etc:"$REPO"/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar:"$REPO"/org/codehaus/mojo/appassembler/appassembler-booter/1.8-SNAPSHOT/appassembler-booter-1.8-SNAPSHOT.jar:"$REPO"/stax/stax-api/1.0.1/stax-api-1.0.1.jar:"$REPO"/org/codehaus/mojo/appassembler/appassembler-model/1.8-SNAPSHOT/appassembler-model-1.8-SNAPSHOT.jar:"$REPO"/net/java/dev/stax-utils/stax-utils/20060502/stax-utils-20060502.jar:"$REPO"/stax/stax/1.1.1-dev/stax-1.1.1-dev.jar:"$REPO"/junit/junit/3.8.1/junit-3.8.1.jar:"$REPO"/org/codehaus/mojo/appassembler-maven-plugin/it/shellDaemonGeneratorTest/1.0-SNAPSHOT/shellDaemonGeneratorTest-1.0-SNAPSHOT.jar


With Maven 3.0.5 on a different machine it works...

Kind regards
Karl-Heinz Marbaise

On 3/14/14 11:19 PM, Dennis Lundberg wrote:

Does anyone know how I can access the workspace folder in Bamboo? So
that I can have a look at what the failing IT actually produced.
This might be OS-related, because the ITs passed on my Windows machine.
Will try on my virtual Ubuntu later.


On Fri, Mar 14, 2014 at 5:18 PM, Codehaus Bamboo
mailto:bamboo-ser...@codehaus.org>> wrote:

Failed  MOJO  ›
appassembler-plugin
 › #251
 failed

Changes by dennisl 

*0/43* tests failed.


  Responsible

dennisl 
Automatically assigned


  Failing Jobs
  

Job DurationTests   
Failed  Integration Tests

(Default Stage) 3 minutes   43 passed   Logs
 |
Artifacts



  Code Changes
  

View full change details


dennisl 
Add used but undeclared dependencies.   19551

View Online 
| Add Comments



This message was sent by Atlassian Bamboo
.

If you wish to stop receiving these emails edit your user profile
 or
notify your administrator
.




--
Dennis Lundberg



Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen   http://www.soebes.de

-
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email