-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: jboss-fuse-6.2.1
-
Fix Version/s: jboss-fuse-6.2.1
-
Component/s: Patching
-
Labels:None
The patch-management-621069-for-620133.zip contains components that look like they are currently not productised as a whole. Most importantly those artifacts found in io.fabric8.patch.
My understanding of the zip file is jboss-fuse-full-6.2.0.redhat-133-baseline.zip are already productised artifacts and this can be confirmed with -
for hash in `awk '{print $1}' jboss-fuse-baseline.sha256`; do if ! grep -q $hash ../jboss-fuse-6.2.0.redhat-133.sha256; then echo $hash; fi; done |
How is this baseline package generated? is it likely to change in future?
However io.fabric8.patch artifacts are not from brew, do these differ from artifacts produced as part of fabric8? -
https://brewweb.devel.redhat.com/archiveinfo?archiveID=1179269
https://brewweb.devel.redhat.com/archiveinfo?archiveID=1179259
https://brewweb.devel.redhat.com/archiveinfo?archiveID=1179191
https://brewweb.devel.redhat.com/archiveinfo?archiveID=1179394
├── patches
|
│ └── jboss-fuse-full-6.2.0.redhat-133-baseline.zip
|
└── system
|
└── io
|
└── fabric8
|
└── patch
|
├── patch-commands
|
│ └── 1.2.0.redhat-621069
|
│ └── patch-commands-1.2.0.redhat-621069.jar
|
├── patch-core
|
│ └── 1.2.0.redhat-621069
|
│ └── patch-core-1.2.0.redhat-621069.jar
|
├── patch-features
|
│ └── 1.2.0.redhat-621069
|
│ └── patch-features-1.2.0.redhat-621069-features.xml
|
└── patch-management
|
└── 1.2.0.redhat-621069
|
└── patch-management-1.2.0.redhat-621069.jar
|
