[
https://issues.apache.org/activemq/browse/CAMEL-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59267#action_59267
]
Christian Mueller commented on CAMEL-2703:
------------------------------------------
Hello Jonathan,
thanks for the hint. I already run in an issue by upgrading the
maven-antrun-plugin to version 1.3 ... :o(
Now, my plan is a bit more time consuming than I thought:
- grep a Camel version in which all tests succeed (hopefully the latest) and
"store" all generated artifacts
- upgrade plugin by plugin and run a complete build between each update
(including executing all tests)
- ensures, that each generated artifact is still the same (may be with a diff)
or the differences are ok
- may be run manual tests like "mvn jetty:run" to ensure that the upgrade
didn't broke anything
Sounds like a plan for you?
Cheers,
Christian
> Upgrade the maven plugin dependencies
> -------------------------------------
>
> Key: CAMEL-2703
> URL: https://issues.apache.org/activemq/browse/CAMEL-2703
> Project: Apache Camel
> Issue Type: Improvement
> Environment: All
> Reporter: Christian Mueller
> Assignee: Christian Mueller
> Fix For: 2.3.0
>
>
> {code}
> christian-muellers-macbook-pro:camel muellerc$ mvn
> versions:display-plugin-updates
> ...
> [INFO] Searching repository for plugin with prefix: 'versions'.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Camel
> [INFO] task-segment: [versions:display-plugin-updates]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [versions:display-plugin-updates {execution: default-cli}]
> [INFO]
> [INFO] The following plugin updates are available:
> [INFO] maven-war-plugin .......................... 2.1-alpha-2 -> 2.1-beta-1
> [INFO] maven-antrun-plugin ...................................... 1.2 -> 1.3
> [INFO] maven-assembly-plugin ...................... 2.2-beta-4 -> 2.2-beta-5
> [INFO] maven-checkstyle-plugin .................................. 2.2 -> 2.3
> [INFO] maven-clean-plugin ....................................... 2.3 -> 2.4
> [INFO] maven-compiler-plugin .................................. 2.0.2 -> 2.1
> [INFO] maven-dependency-plugin .................................. 2.0 -> 2.1
> [INFO] maven-deploy-plugin ...................................... 2.4 -> 2.5
> [INFO] maven-eclipse-plugin ................................... 2.5.1 -> 2.8
> [INFO] maven-install-plugin ..................................... 2.2 -> 2.3
> [INFO] maven-jar-plugin ......................................... 2.2 -> 2.3
> [INFO] maven-javadoc-plugin ................................... 2.5 -> 2.6.1
> [INFO] maven-plugin-plugin .................................... 2.5 -> 2.5.1
> [INFO] maven-release-plugin .............................. 2.0-beta-9 -> 2.0
> [INFO] maven-remote-resources-plugin ............................ 1.0 -> 1.1
> [INFO] maven-resources-plugin ................................. 2.3 -> 2.4.2
> [INFO] maven-shade-plugin ..................................... 1.2.1 -> 1.3
> [INFO] maven-site-plugin ........................................ 2.0 -> 2.1
> [INFO] maven-source-plugin .................................. 2.0.4 -> 2.1.1
> [INFO] maven-surefire-plugin .................................. 2.4.3 -> 2.5
> [INFO] maven-surefire-report-plugin ........................... 2.4.3 -> 2.5
> [INFO] org.codehaus.mojo:findbugs-maven-plugin ................ 1.2 -> 2.3.1
> [INFO] org.codehaus.mojo:taglist-maven-plugin ................... 2.2 -> 2.4
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
