
Key: |
QB-451
|
Type: |
New Feature
|
Status: |
Resolved
|
Resolution: |
Won't Fix
|
Priority: |
Major
|
Assignee: |
Robin Shen
|
Reporter: |
Matthew Inger
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 12/Oct/09 01:48 PM
Updated: 25/Jun/10 09:42 AM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
I love the artifact publishing step in quickbuild 2, as opposed to having to build this into your ant / maven builds. However, the one thing that would be nice to include in a future release would be to have some sort of mapping available to take the source artifacts and map them onto a different directory structure in the storage area.
Perhaps using some sort of ant file mappers (flatten, glob, etc...) so that if you publish a list of artifacts like this:
module1/dist/module1.jar
module2/dist/module2.jar
module2/dist/module3.jar
you don't have to have that same structure in your quickbuild storage area. You could map it down to something else, such as:
module1.jar
module2.jar
module3.jar
|
Description
|
I love the artifact publishing step in quickbuild 2, as opposed to having to build this into your ant / maven builds. However, the one thing that would be nice to include in a future release would be to have some sort of mapping available to take the source artifacts and map them onto a different directory structure in the storage area.
Perhaps using some sort of ant file mappers (flatten, glob, etc...) so that if you publish a list of artifacts like this:
module1/dist/module1.jar
module2/dist/module2.jar
module2/dist/module3.jar
you don't have to have that same structure in your quickbuild storage area. You could map it down to something else, such as:
module1.jar
module2.jar
module3.jar |
Show » |
|