Details
Description
The current solution that handles ejb, über war, and jboss types, is hard-coded. A better solution would be a generic way of handling project packaging <-> artifact type.
In Maven, type, packaging and extension are often the same but not always. Type
sources actually means classifier sources and extension jar for
example. Packaging maven-plugin actually means extension jar.
Issue Links
- relates to
-
CARGO-710
The CARGO maven2 plugin's project type check creates a warning for JBoss' special types
-
Activity
Anders Hammar
made changes -
Anders Hammar
made changes -
| Assignee | Anders Hammar [ afloom ] |
Anders Hammar
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Anders Hammar
made changes -
| Status | In Progress [ 3 ] | Open [ 1 ] |
Savas Ali Tokmen
made changes -
| Fix Version/s | 1.3.0 [ 17389 ] |
Savas Ali Tokmen
made changes -
| Fix Version/s | 1.4.0 [ 18875 ] | |
| Fix Version/s | 1.3.0 [ 17389 ] |
Anders Hammar
made changes -
| Assignee | Anders Hammar [ afloom ] |
Savas Ali Tokmen
made changes -
| Fix Version/s | 1.5.0 [ 19140 ] | |
| Fix Version/s | 1.4.0 [ 18875 ] |
One comment about why this is important. In Maven, the data in the pom is metadata. So, creating a custom packaging is good. So, someone having a special case of a war (for example), could create a custom packing for that. With the current solution in Cargo, that person would run into trouble when he/she wants to use Cargo, which is not good.