Hi Devs,

I tried to build the IS 5.4.0 alpha9 and when I build the v5.4.0-alpha9 tag
in product-is skipping the tests, I got the following error.

[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1.215 s
[INFO] Finished at: 2017-11-23T11:33:53+05:30
[INFO] Final Memory: 45M/1237M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project identity-server-parent: Error finding remote resources
manifests:
/home/tharindu/Desktop/alpha9/product-is/target/maven-shared-archive-resources/META-INF/NOTICE
(No such file or directory) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project identity-server-parent: Error finding remote resources
manifests
    at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
    at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
    at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
    at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error finding
remote resources manifests
    at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1238)
    at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:520)
    at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
    at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
    ... 20 more
Caused by: java.io.FileNotFoundException:
/home/tharindu/Desktop/alpha9/*product-is/target/maven-shared-archive-resources/META-INF/NOTICE
(No such file or directory)*
    at java.io.FileOutputStream.open0(Native Method)
    at java.io.FileOutputStream.open(FileOutputStream.java:270)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
    at java.io.FileWriter.<init>(FileWriter.java:90)
    at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1146)
    ... 23 more


*Java Version*

java version "1.8.0_65"

*Maven Version*
Maven home: /home/tharindu/ProgramFiles/apache-maven-3.3.9
Java version: 1.8.0_65, vendor: Oracle Corporation
OS name: "linux", version: "3.19.0-44-generic", arch: "amd64", family:
"unix"

I manually created an empty file for the missing file
product-is/target/maven-shared-archive-resources/META-INF/NOTICE and then I
could build the pack successfully.

Thanks,
TharinduE

On Thu, Nov 16, 2017 at 11:57 PM, Farasath Ahamed <[email protected]>
wrote:

> The WSO2 Identity and Access Management team is pleased to announce the
> release of WSO2 Identity Server 5.4.0 Alpha 9.
>
> You can build the distribution from the source tag
> https://github.com/wso2/product-is/releases/tag/v5.4.0-alpha9 following
> the steps below.
>
>
> *Building from the source*
>
>    1. Install Java8 or above
>    2. Install Apache Maven 3.x.x(https://maven.apache.org/download.cgi#)
>    3. Get a clone from https://github.com/wso2/product-is.git and
>    checkout to v5.4.0-alpha9 tag or you can directly download the source for
>    the tag from https://github.com/wso2/product-is/releases/tag/v5.4.0-
>    alpha9
>    4. Run the one of the below maven commands from product-is directory,
>       - *mvn** clean install* (To build the binary and source
>       distributions with the tests)
>       - *mvn** clean install -Dmaven.test.skip=true* (To build the binary
>       and source distributions, without running any of the unit/integration 
> tests)
>    5. You can find the wso2is-5.4.0-alpha9.zip binary distribution in
>    product-is/modules/distribution/target directory.
>
> Please note that you need to have Java SE Development Kit *1.8 *to run
> the binary distribution.
>
> The following list contains all the features, improvements, and bug fixes
> available with the WSO2 Identity Server 5.4.0 Alpha 9 release.
> Patch
>
>    - [IDENTITY-6488 <https://wso2.org/jira/browse/IDENTITY-6488>] - SAML
>    Error when IDP init login, ACS not sent to notification.do
>
> Bug
>
>    - [IDENTITY-3355 <https://wso2.org/jira/browse/IDENTITY-3355>] -
>    Better if only warning is shown for siganture varification failures (not
>    the whole exception)
>    - [IDENTITY-4956 <https://wso2.org/jira/browse/IDENTITY-4956>] -
>    Inconsistency in displaying the subject claim when a domain is set
>    - [IDENTITY-4995 <https://wso2.org/jira/browse/IDENTITY-4995>] -
>    Cannot change the certificate alias for a service provider when there's
>    more than one certificate
>    - [IDENTITY-5866 <https://wso2.org/jira/browse/IDENTITY-5866>] - KeyId
>    hard-coded in DefaultIDTokenBuilder
>    - [IDENTITY-5922 <https://wso2.org/jira/browse/IDENTITY-5922>] - When
>    invoking OAuth2TokenValidationService, updated user roles are not reflected
>    in retrieved claims of the JWT token, till cache timeout or server restart
>    - [IDENTITY-5994 <https://wso2.org/jira/browse/IDENTITY-5994>] - NPE
>    thrown when testing cause of exception in OAuth2Service.issueAccessToken
>    ()
>    - [IDENTITY-6075 <https://wso2.org/jira/browse/IDENTITY-6075>] -
>    Receives the Primary-IS admin user info, when calling userinfo endpoint
>    with SAML2 Bearer grant type with SAML federated scenario
>    - [IDENTITY-6288 <https://wso2.org/jira/browse/IDENTITY-6288>] - Move
>    the common code in id token and userinfo, to util
>    - [IDENTITY-6327 <https://wso2.org/jira/browse/IDENTITY-6327>] - List
>    of claims returned in IDToken and Userinfo don't get updated when we update
>    requested claims configuration
>    - [IDENTITY-6331 <https://wso2.org/jira/browse/IDENTITY-6331>] - alg
>    header in JWT token is not valid for IS 5.0.0
>    - [IDENTITY-6332 <https://wso2.org/jira/browse/IDENTITY-6332>] - The
>    “exp” value in the JWT tokens must in RFC7519 compliant format
>    - [IDENTITY-6354 <https://wso2.org/jira/browse/IDENTITY-6354>] - Two
>    confirmation windows coming when updating the user with all existing roles
>    - [IDENTITY-6358 <https://wso2.org/jira/browse/IDENTITY-6358>] - Error
>    when adding workflows in tenant mode for external BPS profiles
>    - [IDENTITY-6376 <https://wso2.org/jira/browse/IDENTITY-6376>] - SAML2
>    Web SSO Configuration (Federated Authenticator) default Signature Algorithm
>    is set to DSA with SHA1
>    - [IDENTITY-6385 <https://wso2.org/jira/browse/IDENTITY-6385>] -
>    Internal Server Error for Client Credential Grant with openid scope OOB
>    - [IDENTITY-6386 <https://wso2.org/jira/browse/IDENTITY-6386>] - self
>    sign up not working in tenant mode
>    - [IDENTITY-6391 <https://wso2.org/jira/browse/IDENTITY-6391>] -
>    [Service Provider SAML2 Web SSO configuration] Default Value of Certificate
>    Alias should be wso2carbon
>    - [IDENTITY-6404 <https://wso2.org/jira/browse/IDENTITY-6404>] - Error
>    in SAML2 Bear token grant validation for tenant users when "Use tenant
>    domain in local subject identifier" option is unchecked
>    - [IDENTITY-6480 <https://wso2.org/jira/browse/IDENTITY-6480>] -
>    Calling OAuth2ValidationService with a valid token when
>    AuthorizationContextTokenGeneration is enabled throws a back end error
>    - [IDENTITY-6496 <https://wso2.org/jira/browse/IDENTITY-6496>] - A
>    white-space in-between Authorization: Basic and
>    <Base64Encoded(Client_Id:Client_Secret)> leads to a Nullpointer when
>    generating access token using refresh token
>    - [IDENTITY-6505 <https://wso2.org/jira/browse/IDENTITY-6505>] -
>    Invoking user-info endpoint using playground sample fails when using email
>    as the user name
>    - [IDENTITY-6558 <https://wso2.org/jira/browse/IDENTITY-6558>] -
>    SAML2.IsPassiveAuthn=true is not available in travelocity.properties
>    - [IDENTITY-6581 <https://wso2.org/jira/browse/IDENTITY-6581>] - Error
>    with SAML Extension Grant Type
>    - [IDENTITY-6703 <https://wso2.org/jira/browse/IDENTITY-6703>] - Bad
>    Grammar in the exception: "SAML Assertion not found in the Response"
>    - [IDENTITY-6736 <https://wso2.org/jira/browse/IDENTITY-6736>] - All
>    the query params in "Additional Query Parameters" of federated oauth/openid
>    connect IDP config is not visible in management console
>    - [IDENTITY-6797 <https://wso2.org/jira/browse/IDENTITY-6797>] - Stack
>    trace of exception displayed in web browser in case of empty SAMLRequest
>    - [IDENTITY-6805 <https://wso2.org/jira/browse/IDENTITY-6805>] - NPE
>    possibility in NTLMAuthenticationGrantHandler
>    - [IDENTITY-6895 <https://wso2.org/jira/browse/IDENTITY-6895>] -
>    Claims not returned properly after SP requested claims updated
>    - [IDENTITY-6896 <https://wso2.org/jira/browse/IDENTITY-6896>] -
>    Oauth2 Revoke endpoint does not validate repeated parameters
>    - [IDENTITY-6897 <https://wso2.org/jira/browse/IDENTITY-6897>] - Claim
>    filtering not handled in UserInfoJWTResponseBuilder
>    - [IDENTITY-6898 <https://wso2.org/jira/browse/IDENTITY-6898>] -
>    Revoke endpoint sends an Unauthorized response when Invalid Authorization
>    header exists, but the token is empty.
>    - [IDENTITY-6901 <https://wso2.org/jira/browse/IDENTITY-6901>] -
>    Validate subjectConfirmationData time limits to fall within the time window
>    given in the Conditions in the saml assertion
>    - [IDENTITY-6909 <https://wso2.org/jira/browse/IDENTITY-6909>] - HTML
>    tags should be closed properly
>
> Improvement
>
>    - [IDENTITY-2530 <https://wso2.org/jira/browse/IDENTITY-2530>] - Make
>    refresh tokens optional for SAML2 Bearer grant type
>    - [IDENTITY-4980 <https://wso2.org/jira/browse/IDENTITY-4980>] -
>    Exception during access token generation right after expiration
>    - [IDENTITY-5483 <https://wso2.org/jira/browse/IDENTITY-5483>] -
>    Validate user against given user store and save correct user domain in
>    saml2-bearer grant type.
>    - [IDENTITY-5975 <https://wso2.org/jira/browse/IDENTITY-5975>] - Need
>    to handle errors in oAuth Endpoints
>    - [IDENTITY-6224 <https://wso2.org/jira/browse/IDENTITY-6224>] -
>    Improve logs in controlClaimsFromScope() of SAMLAssertionClaimsCallback
>    class
>    - [IDENTITY-6900 <https://wso2.org/jira/browse/IDENTITY-6900>] - Make
>    subject claim consistent across all grant types
>
>
>
> *Contribute to WSO2 Identity Server*
>
> *Mailing Lists*
>
> Join our mailing lists and correspond with the developers directly. We
> also encourage you to take part in discussions related to the product in
> the architecture mailing list. If you have any questions regarding the
> product you can use our StackOverflow forum to raise them as well.
>
>    - Developer List: [email protected]
>    - Architecture List: [email protected]
>    - User Forum: StackOverflow
>    <http://stackoverflow.com/questions/tagged/wso2is>
>
> Reporting Issues
> We encourage you to report issues, improvements, and feature requests
> regarding WSO2 Identity Server through our public WSO2 Identity Server
> JIRA <https://wso2.org/jira/projects/IDENTITY/issues>.
>
> ~ The WSO2 Identity and Access Management Team ~
>
>
>
> Thanks,
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 <https://twitter.com/farazath619>
> <http://wso2.com/signature>
>
>
>


-- 

Tharindu Edirisinghe
Senior Software Engineer | WSO2 Inc
Platform Security Team
Blog : http://tharindue.blogspot.com
mobile : +94 775181586
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to