[
https://issues.apache.org/jira/browse/FLEX-33296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jose Barragan resolved FLEX-33296.
----------------------------------
Resolution: Fixed
Fix Version/s: InstalApacheFlex 1.0
Revision #1421004
[FLEX-33296] Fixed.
Generator: Fix the groupMetadataId when main directory pom is defining.
Deployer: Grant has only one execution command for each ProcessBuilder
> Apache Flex Mavenized SDK Bug
> -----------------------------
>
> Key: FLEX-33296
> URL: https://issues.apache.org/jira/browse/FLEX-33296
> Project: Apache Flex
> Issue Type: Bug
> Components: Installation & Packaging
> Affects Versions: InstalApacheFlex 1.0
> Environment: Windows, MacOSX, Linux
> Reporter: Jose Barragan
> Assignee: Jose Barragan
> Fix For: InstalApacheFlex 1.0
>
>
> Mavenizer creates a main directories poms for use in the new scope "import",
> but the contain of those poms are wrong in reference with the structure
> position expected.
> SDKGenerator
> The position of i.e.: framework-4.6.0.23201.pom implied this expected GAV:
> <groupId>com.adobe.flex</groupId>
> <artifactId>framework</artifactId>
> <version>4.6.0.23201</version>
> <packaging>pom</packaging>
> however the contain of pom file is:
> <groupId>com.adobe.flex.framework</groupId>
> <artifactId>framework</artifactId>
> <version>4.6.0.23201</version>
> <packaging>pom</packaging>
> And it's overwrite when is deployed over remote Nexus.
> SDKDeployer:
> I got a newer error too when I revised the deployment result on Nexus and
> find another issue too, a lot of artifacts was deployed with a wrong name or
> in a wrong structure position.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
