Bug 1112758 - Workbench's Maven Repository is not "cluster-aware"
Summary: Workbench's Maven Repository is not "cluster-aware"
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: manstis
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-24 15:54 UTC by manstis
Modified: 2020-03-27 20:00 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:00:16 UTC
Type: Feature Request
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1112062 0 high CLOSED mvn deploy to workbench artifact repository 2021-02-22 00:41:40 UTC

Internal Links: 1112062

Description manstis 2014-06-24 15:54:30 UTC
Description of problem:

Various operations within the business-central publish JARs to business-central's internal Maven Repository (e.g. "Upload artifact", "Build&Deploy project"). 

Furthermore following completion of https://bugzilla.redhat.com/show_bug.cgi?id=1112062 "mvn deploy" of Maven projects to business-central's Maven Repository (that have been correctly configured to include the remote repository in their <distributionManagement> pom.xml settings).

This is all well and good, however these operations write to the underlying file-system which is not, by default, "cluster-aware". This is not a problem when business-central is not deployed in a cluster however when it is the aforementioned operations will lead to sporadic results on nodes within the cluster.  

Version-Release number of selected component (if applicable):

6.0.2.

Steps to Reproduce:
1. Set-up a business-central cluster
2. Create an external Maven project (see the referenced BZ)
3. mvn deploy

Actual results:

Only the node in the cluster directly referenced in the project's pom's <distributionManagement> section will have the deployed JAR. At worse, if the pom was configured to point to a load-balancer the node on which the JAR is deployed will be inconsistent.

Expected results:

Nodes in a cluster are synchronized.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.