search

HughP / simal

Automatically exported from code.google.com/p/simal
0 stars 0 forks source link

Simal webapp not building on CI server #321

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
http://www.16degrees.com.au/hudson/job/SimalWebappSVN/2865/

Unfortunatley, since Hudson has been down for a while there have been many 
changes since the last successful build.

The good news is that it just looks like a POM versioning issue:

http://www.16degrees.com.au/hudson/job/SimalWebappSVN/2865/console

Original issue reported on code.google.com by ross.gardler on 11 Jul 2010 at 1:12

GoogleCodeExporter commented 9 years ago 
Message on the list [1] 

The Simal Web project has been failing for some time now and 
unfortunately I don't have the karma on the machine to fix it.

The error is that a folder can't be found which should
have been created in the [resources:resource] part of the
Maven build cycle. On my local Windows (similarly to a Linux 
server I checked with) the resources:resources task outputs:

[INFO] [resources:resources {execution: default-cli}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 6 resources to C:\dev\simal\simal-webapp\target/filteredWidgets
[INFO] Copying 46 resources

That's expected.
On the Hudson the same task outputs: 

[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[TASKS] Skipping maven reporter: there is already a result available.

Then further on the error is that the folder 
[...]/target/filteredWidgets/doapcreator
is not found, but this should have been created by the resources:resources
task. So I suspect the task should not be skipped but I don't have the
karma to change these settings.

Could someone give me the needed rights (I am registered as svanderwaal on
the machine) or have a look to see if the settings can be changed to fix this?

[1] 
http://groups.google.com/group/simal-contributors/browse_thread/thread/3dfcaaa48
6d0a05f

Original comment by sander.v...@oucs.ox.ac.uk on 20 Jul 2010 at 10:27

GoogleCodeExporter commented 9 years ago

Original comment by sander.v...@oucs.ox.ac.uk on 20 Jul 2010 at 3:07

GoogleCodeExporter commented 9 years ago 
The problem was not that a task was skipped, but that the output folder used by 
the resources:resources task was different from the folder used by the 
maven-antrun-plugin.

In both cases the folder was defined as :

${project.build.directory}/filteredWidgets/doapcreator

On the build server ${project.build.directory} was replaced by the 
maven-antrun-plugin but not by the resources:resources task, therefore putting 
the resources in a subfolder of a folder named "${project.build.directory}". 

The fact that the behaviour is different on the build server may have to do 
with the fact that it's an old Maven version (2.0.8). 

Fixed by not using ${project.build.directory} in the resources but the relative 
path ../filteredWidgets instead.

Original comment by sander.v...@oucs.ox.ac.uk on 28 Jul 2010 at 7:52