search

wildside96 / bst-player

Automatically exported from code.google.com/p/bst-player
0 stars 0 forks source link

Two small build problems #40

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. mvn -Pdev-mode install

What is the expected output? What do you see instead?
The maven build should complete without error.  Instead, there are two errors.

What version of the product are you using? On what operating system?
trunk 1.2.1-SNAPSHOT
Linux, Kubuntu 10.10

$ mvn --version
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_23
Java home: /opt/java/jdk1.6.0_23/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.35-25-generic" arch: "amd64" Family: "unix"

Please provide any additional information below.

The first problem is a maven execution that is commented out.

The second is a non-UTF8 character in a javadoc comment which causes the 
compile to fail.  An alternative solution is to set explicit character 
encodings in the build so that you can keep the fancy apostrophe.

I'm attaching a small patch which fixes both issues.

Below is snipped maven output from the two errors.

------------------------------------------------------------------------

[INFO] Unable to find artifact.
Embedded error: Unable to download the artifact from any repository

Try downloading the file manually from the project website.

Then, install it using the command: 
    mvn install:install-file -DgroupId=com.bramosystems.oss.player -DartifactId=bst-flash-player -Dversion=1.2.1-SNAPSHOT -Dclassifier=lo -Dpackaging=swf -Dfile=/path/to/file

------------------------------------------------------------------------

[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
build is platform dependent!
[ERROR] BUILD FAILURE
[INFO] Compilation failure 
bst-player/bst-player-api/src/main/java/com/bramosystems/oss/player/core/client/
ui/QuickTimePlayer.java:[732,16] unmappable character for encoding UTF8

Original issue reported on code.google.com by lpur...@gmail.com on 29 Jan 2011 at 8:54

Attachments:

GoogleCodeExporter commented 9 years ago 
The commented maven execution is intentional, the build with 'lo' classifier is 
not confirmed yet and may(may not) be part of the next release.  However its 
dependency in bst-player-api is removed in trunk for now, so the build should 
be error free.

Original comment by sbrah...@gmail.com on 2 Feb 2011 at 11:11