incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Barragan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-33296) Apache Flex Mavenized SDK Bug
Date Wed, 12 Dec 2012 22:17:21 GMT

    [ https://issues.apache.org/jira/browse/FLEX-33296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530420#comment-13530420
] 

Jose Barragan commented on FLEX-33296:
--------------------------------------

It's more slow, but the processor load is the same in order to my experience.
However, I can revised the process to optimise it, or tell me some thing.

When the instruction was queue in unique command some artifacts are not processed, o get malformed
names, or whatever. 
                
> 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

Mime
View raw message