Bug 1107750
| Summary: | WAS:Unable to download dependencies from business central maven repo when building project | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Radovan Synek <rsynek> | ||||||
| Component: | Business Central | Assignee: | Maciej Swiderski <mswiders> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Radovan Synek <rsynek> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.0.2 | CC: | etirelli, mfusco, mswiders, rrajasek, zkrejcov | ||||||
| Target Milestone: | CR1 | ||||||||
| Target Release: | 6.1.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-08-06 19:53:05 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 907297 [details]
project's dependency
Radek,
I just tried it on WAS and was able to run it properly with your project as dependency. Though when jar is uploaded it will get installed to maven local repo as well. So I removed it explicitly before I build and deploy. Not sure what configuration you used for server/repository authentication but here is one I used:
Following does work:
<servers>
<server>
<id>guvnor-m2-repo</id>
<username>user</username>
<password>password</password>
<configuration>
<httpConfiguration>
<put>
<params>
<param>
<name>http.authentication.preemptive</name>
<value>%b,true</value>
</param>
</params>
</put>
</httpConfiguration>
</configuration>
</server>
</servers>
when using another approach found in some other bz the issue was indeed present:
Following does not work
<servers>
<server>
<id>guvnor-m2-repo</id>
<username>user</username>
<password>password</password>
<configuration>
<wagonProvider>httpclient</wagonProvider>
<httpConfiguration>
<all>
<usePreemptive>true</usePreemptive>
</all>
</httpConfiguration>
</configuration>
</server>
</servers>
in server logs there was additional warning message indicating incorrect configuration for server:
[WARNING] Could not apply configuration for guvnor-m2-repo to wagon org.apache.maven.wagon.providers.http.HttpWagon:Cannot find setter, adder nor field in org.apache.maven.wagon.shared.http.HttpMethodConfiguration for 'usePreemptive'
could you please let me know what settings you use for servers authentication?
I was able to reproduce the issue with both configurations, but also to see it working. As we (me and Maciej) agreed on IRC, the issue could be influenced by bug 1107741, so I will retest it with the next build. Radovan, if this is going to be tested with the next build, I am then setting the status to MODIFIED, so it is picked up. Verified with BRMS-6.0.2.CR2 |
Created attachment 907284 [details] error stacktrace - building a project Description of problem: When building a project in Business Central which have a dependency, that had been uploaded via Artifact Repository, build fails because of Unauthorized:401 in the time maven tries to download pom.xml of the dependency. Business Central with EAP gives the same result, which can be changed by providing authentication details in settings.xml. However, with WebSphere this does not help. Version-Release number of selected component (if applicable): 6.0.2.ER3 Steps to Reproduce: 1. deploy business-central to WebSphere AS, log in to business-central 2. upload a mavenized jar to artifact repository 3. create a project, add a dependency to the jar uploaded in previous step. 4. save & build the project => fails, there is Unauthorized:401 as root cause in server log 5. create a settings.xml containing authentization info to the Business Central maven repository where the project's dependency is available. 6. configure business central to use this settings.xml via system property "kie.maven.settings.custom" 7. restart business-central or even WebSphere as needed. 8. again, try to build the project. Still fails with the same error => settings.xml did not help