Looks like there was a network glitch.  Did it happen more than once?

-Alex

On 1/21/18, 1:20 PM, "Olaf Krueger" <[email protected]> wrote:

>Hi,
>I've stumbled over a new issue [1].
>
>Any ideas?
>
>Thanks,
>Olaf
>
>
>[1]
>                    Downloaded from central:
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.mave
>n.apache.org%2Fmaven2%2Forg%2Ftukaani%2Fxz%2F1.2%2Fxz-1.2.pom&data=02%7C01
>%7Caharui%40adobe.com%7Cf5346727bdea48e68f6008d56123b3d7%7Cfa7b1b5a7b34438
>794aed2c178decee1%7C0%7C0%7C636521728358181646&sdata=tPzg97%2Ffi6a7ivJUxjD
>hdsvVw%2FX%2FW5IL01eInCjobRw%3D&reserved=0 (1.9 kB
>at 15 kB/s)[INFO]
>------------------------------------------------------------------------
>[INFO] Reactor Summary:
>[INFO]
>[INFO] Apache Royale: Build Tools ......................... SUCCESS [01:13
>min]
>[INFO] Apache Royale: JBurg Types ......................... SUCCESS [
>0.765
>s]
>[INFO] Apache Royale: Compiler: Parent .................... FAILURE [55:55
>min]
>[INFO]
>------------------------------------------------------------------------
>[INFO] BUILD FAILURE
>[INFO]
>------------------------------------------------------------------------
>[INFO] Total time: 57:10 min
>[INFO] Finished at: 2018-01-21T22:15:18+01:00
>[INFO] Final Memory: 41M/451M
>[INFO]
>------------------------------------------------------------------------
>[ERROR] Failed to execute goal
>org.apache.maven.plugins:maven-site-plugin:3.4:attach-descriptor
>(attach-descriptor) on project royale-compiler-parent: Execution
>attach-descriptor of goal
>org.apache.maven.plugins:maven-site-plugin:3.4:attach-descriptor failed:
>Plugin org.apache.maven.plugins:maven-site-plugin:3.4 or one of its
>dependencies could not be resolved: Failed to collect dependencies at
>org.apache.maven.plugins:maven-site-plugin:jar:3.4 ->
>lt.velykis.maven.skins:reflow-velocity-tools:jar:1.1.1: Failed to read
>artifact descriptor for
>lt.velykis.maven.skins:reflow-velocity-tools:jar:1.1.1: Could not transfer
>artifact lt.velykis.maven.skins:reflow-velocity-tools:pom:1.1.1 from/to
>apache-plugins-release
>(https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freposito
>ry.apache.org%2Fcontent%2Frepositories%2Freleases&data=02%7C01%7Caharui%40
>adobe.com%7Cf5346727bdea48e68f6008d56123b3d7%7Cfa7b1b5a7b34438794aed2c178d
>ecee1%7C0%7C0%7C636521728358181646&sdata=DrVI27ls%2BMGp1fqJ%2BL3qny3Q%2FHt
>Qj7%2F8S8A26qU28sU%3D&reserved=0): Read timed
>out -> [Help 1]
>[ERROR]
>[ERROR] To see the full stack trace of the errors, re-run Maven with the
>-e
>switch.
>[ERROR] Re-run Maven using the -X switch to enable full debug logging.
>[ERROR]
>[ERROR] For more information about the errors and possible solutions,
>please
>read the following articles:
>[ERROR] [Help 1]
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apac
>he.org%2Fconfluence%2Fdisplay%2FMAVEN%2FPluginResolutionException&data=02%
>7C01%7Caharui%40adobe.com%7Cf5346727bdea48e68f6008d56123b3d7%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636521728358181646&sdata=LVK57ILMoFBVAxTvz
>7QUJ2OHfhe2i%2FR3G6XrtiEZQks%3D&reserved=0
>[ERROR]
>[ERROR] After correcting the problems, you can resume the build with the
>command
>[ERROR]   mvn <goals> -rf :royale-compiler-parent
>
>BUILD FAILED
>C:\local\apache-royale\approval_0_9_0_RC2\ApproveRoyale.xml:755: exec
>returned: 1
>
>
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>Cf5346727bdea48e68f6008d56123b3d7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636521728358181646&sdata=EAVg%2FlwGCYkAMSs8kXocZOuK%2B%2FPnmvnjCIoT3q
>hQ9HU%3D&reserved=0

Reply via email to