incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric THOMAS (JIRA) <>
Subject [jira] [Commented] (FLEX-33296) Apache Flex Mavenized SDK Bug
Date Thu, 13 Dec 2012 11:38:12 GMT


Frédéric THOMAS commented on FLEX-33296:

On windows with what you committed but the emails you sent me last night with the weird results,
I wasn't able to reproduce them, maybe I missed something...
> Apache Flex Mavenized SDK Bug
> -----------------------------
>                 Key: FLEX-33296
>                 URL:
>             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- implied this expected GAV:
> 	<groupId>com.adobe.flex</groupId>
>     	<artifactId>framework</artifactId>
>     	<version></version>
>     	<packaging>pom</packaging>
> however the contain of pom file is:
> 	<groupId>com.adobe.flex.framework</groupId>
>     	<artifactId>framework</artifactId>
>     	<version></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:

View raw message