[
https://issues.apache.org/jira/browse/CAMEL-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994129#comment-12994129
]
Christian Müller commented on CAMEL-3268:
-----------------------------------------
Today, I could run all of the following commands in the Camel root directory
without any failures:
{code}
mvn clean install
{code}
{code}
mvn -Pfastinstall clean install
{code}
{code}
mvn -sourcecheck clean install
{code}
{code}
mvn clean source:jar install -Dtest=false
{code}
{code}
mvn eclipse:eclipse
{code}
{code}
mvn -Psetup.eclipse
-Declipse.workspace.dir=/Users/cmueller/workspaceApacheGitSVN
{code}
{code}
mvn eclipse:configure-workspace
-Declipse.workspace=/Users/cmueller/workspaceApacheGitSVN
{code}
and the following command in camel/platforms
{code}
mvn -Pvalidate clean install
{code}
Only the command
{code}
mvn idea:idea
{code}
hangs on camel-jms without any exception or error. This command also didn't
download the javadoc from maven central with Maven 3 (it does with maven
2.2.1). I think this is not a blocker to close this issue.
These are the commands, documented on the [Camel
Building|http://camel.apache.org/building.html] page.
Afterward, I tried the commands listed on the [Release
Guide|http://camel.apache.org/release-guide.html] page:
{code}
mvn rat:check
{code}
runs without any problems.
Running
{code}
mvn release:prepare -DdryRun=true
{code}
hangs on the gpg:sign execution with Maven 3 and Maven 2.2.1. I think it's
because of missing some gpg key or passphrase on my settings file.
{code}
mvn release:clean
{code}
runs also no errors or exceptions.
I didn't try the
{code}
mvn release:perform
{code}
command. Maybe someone else (Hadrian, Claus?) will try this out?
I think Camel works now very well with Maven 3 and I would like to close this
issue, if nobody has doubts (until end of next week).
Christian
P.S. I tried also the (undocumented) rat profile, but without luck.It fails in
Maven 3 and 2.2.1. The rat.txt file was not written and it fails with:
Maven 2.2.1:
{code}
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Too many unapproved licenses: 156
{code}
Maven 2.2.1:
{code}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12.372s
[INFO] Finished at: Sun Feb 13 19:17:58 CET 2011
[INFO] Final Memory: 82M/227M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.codehaus.mojo:rat-maven-plugin:1.0-alpha-3:check (default-cli) on project
camel-bindy: Too many unapproved licenses: 156 -> [Help 1]
[ERROR]
{code}
I wanted to use it because I would add the excludes for my '**/.git/**/*'
files...
> Maven 3 to build source
> -----------------------
>
> Key: CAMEL-3268
> URL: https://issues.apache.org/jira/browse/CAMEL-3268
> Project: Camel
> Issue Type: Task
> Affects Versions: 2.5.0
> Reporter: Claus Ibsen
> Assignee: Christian Müller
> Priority: Minor
> Fix For: 2.7.0, 3.0.0
>
> Attachments: CAMEL-3268_maven-checkstyle-plugin_upgrade.patch
>
>
> It should be possible to build the project with Maven 3 without any issues.
> Dan Kulp says there is an issue with using old Maven 1 repo style.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
