[
https://issues.apache.org/jira/browse/FELIX-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch resolved FELIX-3222.
-------------------------------------
Resolution: Fixed
Fix Version/s: maven-bundle-plugin-2.3.6
Assignee: Stuart McCulloch
Resolved in r1203895
Note that the WagonConfigurationException is the right type to catch for the
Maven2 API, but it has been deprecated in Maven3 and a legacy compatibility
class added to the exception hierarchy.
Normally this would be fine (ie. build against Maven 2, run against Maven 2 or
3) but you appear to have your own custom build setup that's specifically
targeting Maven 3. The safest solution in this case is to catch a common
superclass.
Note: to make such issues easier to fix it would be good to mention any custom
build setup, along with any changes to the project dependencies (ie. Maven 2 vs
Maven 3)
> [PATCH] build fails with "unreported exception"
> -----------------------------------------------
>
> Key: FELIX-3222
> URL: https://issues.apache.org/jira/browse/FELIX-3222
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.5
> Environment: fedora-rawhide-x86_64
> Reporter: Jaromír Cápík
> Assignee: Stuart McCulloch
> Fix For: maven-bundle-plugin-2.3.6
>
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> The following error appears when building in the latest fedora-rawhide
> environment:
> [ERROR]
> /projects/maven-plugin-bundle/maven-bundle-plugin-2.3.5/src/main/java/org/apache/felix/obrplugin/RemoteFileManager.java:[118,45]
> unreported exception
> org.apache.maven.repository.legacy.WagonConfigurationException; must be
> caught or declared to be thrown
> The following patch solved the build issue (i know, that exception catchall
> is not the best solution):
> http://jcapik.fedorapeople.org/files/maven-bundle-plugin/maven-bundle-plugin-unreported-exception.patch
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
