You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flex.apache.org by "christofer.dutz@c-ware.de" <ch...@c-ware.de> on 2013/11/03 16:00:21 UTC

Updated Mavenizer

Hi,

today I committed some changes to the Mavenizer Tool.

Change 1 made sure all SDKs (Flex and Air) are processed in the right order regarding the versions of the SDKs.

Change 2 is a new Deployer "SDKInVMDeployer" which no longer needs Maven to deploy the Mavenized files as it uses Aether directly to deploy files directly inside the VM, causing a dramatic speedup of the time needed to deploy stuff as well as being able to execute without the reliance on an already installed Maven system. This should make it easy to add the new Deployer to any sort of installer.

Chris

Re: AW: AW: Updated Mavenizer

Posted by "piotr.zarzycki" <pi...@gmail.com>.

Thanks Christofer. :) I'll check it tomorrow.



-----
Flex/Air developer open to new job offers and challenges.
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Updated-Mavenizer-tp31841p31892.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: AW: AW: Updated Mavenizer

Posted by "piotr.zarzycki" <pi...@gmail.com>.

Just checked and everything is ok. :)
Thank you Christofer.



-----
Flex/Air developer open to new job offers and challenges.
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Updated-Mavenizer-tp31841p31905.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

AW: AW: Updated Mavenizer

Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.

Ok ... so I updated the class ... should work now :-)
Thanks for reporting this.

Chris

-----Ursprüngliche Nachricht-----
Von: christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de] 
Gesendet: Montag, 4. November 2013 16:07
An: dev@flex.apache.org
Betreff: AW: AW: Updated Mavenizer

Hi Piotr,

Having a look at the code and the exception, I find this error relatively strange. Googling a Little, I could see that Integer.compare was introduced in Java 1.7 ... think I'll overwork this to make the mavenizer work in 1.6 too.

For now changing the line in the exception to this:
    return Integer.valueOf(versionSegments1.length).compareTo(versionSegments2.length);

should do the trick. Unfortunately I can't commit here at work and I'll have to do this this eavening.

Chris

________________________________________
Von: piotr.zarzycki [piotrzarzycki21@gmail.com]
Gesendet: Montag, 4. November 2013 15:07
An: dev@flex.apache.org
Betreff: Re: AW: Updated Mavenizer

Hi Christofer,

I'm getting exception when i try to generate FDK.

Exception in thread "main" java.lang.NoSuchMethodError:
java.lang.Integer.compare(II)I
        at common.ConversionPlan$1.compare(ConversionPlan.java:29)
        at common.ConversionPlan$1.compare(ConversionPlan.java:16)
        at java.util.TreeMap.getEntryUsingComparator(Unknown Source)
        at java.util.TreeMap.getEntry(Unknown Source)
        at java.util.TreeMap.containsKey(Unknown Source)
        at java.util.TreeSet.contains(Unknown Source)
        at common.ConversionPlan.addVersion(ConversionPlan.java:38)
        at SDKGenerator.buildAirConversionPlan(SDKGenerator.java:49)
        at SDKGenerator.main(SDKGenerator.java:156)



-----
Flex/Air developer open to new job offers and challenges.
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Updated-Mavenizer-tp31841p31882.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

AW: AW: Updated Mavenizer

Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.

Hi Piotr,

Having a look at the code and the exception, I find this error relatively strange. Googling a Little, I could see that Integer.compare was introduced in Java 1.7 ... think I'll overwork this to make the mavenizer work in 1.6 too.

For now changing the line in the exception to this:
    return Integer.valueOf(versionSegments1.length).compareTo(versionSegments2.length);

should do the trick. Unfortunately I can't commit here at work and I'll have to do this this eavening.

Chris

________________________________________
Von: piotr.zarzycki [piotrzarzycki21@gmail.com]
Gesendet: Montag, 4. November 2013 15:07
An: dev@flex.apache.org
Betreff: Re: AW: Updated Mavenizer

Hi Christofer,

I'm getting exception when i try to generate FDK.

Exception in thread "main" java.lang.NoSuchMethodError:
java.lang.Integer.compare(II)I
        at common.ConversionPlan$1.compare(ConversionPlan.java:29)
        at common.ConversionPlan$1.compare(ConversionPlan.java:16)
        at java.util.TreeMap.getEntryUsingComparator(Unknown Source)
        at java.util.TreeMap.getEntry(Unknown Source)
        at java.util.TreeMap.containsKey(Unknown Source)
        at java.util.TreeSet.contains(Unknown Source)
        at common.ConversionPlan.addVersion(ConversionPlan.java:38)
        at SDKGenerator.buildAirConversionPlan(SDKGenerator.java:49)
        at SDKGenerator.main(SDKGenerator.java:156)



-----
Flex/Air developer open to new job offers and challenges.
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Updated-Mavenizer-tp31841p31882.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: AW: Updated Mavenizer

Posted by "piotr.zarzycki" <pi...@gmail.com>.

Hi Christofer,

I'm getting exception when i try to generate FDK.

Exception in thread "main" java.lang.NoSuchMethodError:
java.lang.Integer.compare(II)I
        at common.ConversionPlan$1.compare(ConversionPlan.java:29)
        at common.ConversionPlan$1.compare(ConversionPlan.java:16)
        at java.util.TreeMap.getEntryUsingComparator(Unknown Source)
        at java.util.TreeMap.getEntry(Unknown Source)
        at java.util.TreeMap.containsKey(Unknown Source)
        at java.util.TreeSet.contains(Unknown Source)
        at common.ConversionPlan.addVersion(ConversionPlan.java:38)
        at SDKGenerator.buildAirConversionPlan(SDKGenerator.java:49)
        at SDKGenerator.main(SDKGenerator.java:156)



-----
Flex/Air developer open to new job offers and challenges.
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Updated-Mavenizer-tp31841p31882.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

AW: Updated Mavenizer

Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.

Hi Toni,

I haven't managed to fee enough time to successfully continue working on that plugin as my work situation has changed quite a bit so nut much progress here, but I have been making sure that we are able to work with Flexmojos 6.0.1, which should work nicely and the 7.x branch which I am intending on optimizing for Apache Flex and stripping out stuff related to Adobe Flex which is causing problems with Apache Flex (such as "caching/signed rsls").

Chris

-----Ursprüngliche Nachricht-----
Von: Toni Vega [mailto:tonivega82@gmail.com] 
Gesendet: Sonntag, 3. November 2013 16:17
An: dev@flex.apache.org
Betreff: Re: Updated Mavenizer

Hi Christofer,

Sorry if I'm a little bit disconnected but, which is the current state of the new maven-flex-plugin and when will it be released?

Thanks!


2013/11/3 christofer.dutz@c-ware.de <ch...@c-ware.de>

> Hi,
>
> today I committed some changes to the Mavenizer Tool.
>
> Change 1 made sure all SDKs (Flex and Air) are processed in the right 
> order regarding the versions of the SDKs.
>
> Change 2 is a new Deployer "SDKInVMDeployer" which no longer needs 
> Maven to deploy the Mavenized files as it uses Aether directly to 
> deploy files directly inside the VM, causing a dramatic speedup of the 
> time needed to deploy stuff as well as being able to execute without 
> the reliance on an already installed Maven system. This should make it 
> easy to add the new Deployer to any sort of installer.
>
> Chris
>

Re: Updated Mavenizer

Posted by Toni Vega <to...@gmail.com>.

Hi Christofer,

Sorry if I'm a little bit disconnected but, which is the current state of
the new maven-flex-plugin and when will it be released?

Thanks!


2013/11/3 christofer.dutz@c-ware.de <ch...@c-ware.de>

> Hi,
>
> today I committed some changes to the Mavenizer Tool.
>
> Change 1 made sure all SDKs (Flex and Air) are processed in the right
> order regarding the versions of the SDKs.
>
> Change 2 is a new Deployer "SDKInVMDeployer" which no longer needs Maven
> to deploy the Mavenized files as it uses Aether directly to deploy files
> directly inside the VM, causing a dramatic speedup of the time needed to
> deploy stuff as well as being able to execute without the reliance on an
> already installed Maven system. This should make it easy to add the new
> Deployer to any sort of installer.
>
> Chris
>

AW: Updated Mavenizer

Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.

I'm just using Aether for deploying mavenized FDKs so it has nothing to do with the actual execution of FM. So there shouldn't be a Problem.

Chris

________________________________________
Von: Frédéric THOMAS [webdoublefx@hotmail.com]
Gesendet: Dienstag, 5. November 2013 00:38
An: dev@flex.apache.org
Betreff: RE: Updated Mavenizer

Thanks Chris, sounds good, I don't have the time at the moment to look at
the code because of my work and I'm between Paris and London but will check
it as soon as I can, just a question, are you aware there is an issue with
FM and Aether running FM with maven 3.1.1 ? Should I raise an issue
somewhere ?

-Fred

-----Message d'origine-----
De : christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de]
Envoyé : dimanche 3 novembre 2013 16:00
À : dev@flex.apache.org
Objet : Updated Mavenizer

Hi,

today I committed some changes to the Mavenizer Tool.

Change 1 made sure all SDKs (Flex and Air) are processed in the right order
regarding the versions of the SDKs.

Change 2 is a new Deployer "SDKInVMDeployer" which no longer needs Maven to
deploy the Mavenized files as it uses Aether directly to deploy files
directly inside the VM, causing a dramatic speedup of the time needed to
deploy stuff as well as being able to execute without the reliance on an
already installed Maven system. This should make it easy to add the new
Deployer to any sort of installer.

Chris

RE: Updated Mavenizer

Posted by Frédéric THOMAS <we...@hotmail.com>.

Thanks Chris, sounds good, I don't have the time at the moment to look at
the code because of my work and I'm between Paris and London but will check
it as soon as I can, just a question, are you aware there is an issue with
FM and Aether running FM with maven 3.1.1 ? Should I raise an issue
somewhere ?

-Fred

-----Message d'origine-----
De : christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de] 
Envoyé : dimanche 3 novembre 2013 16:00
À : dev@flex.apache.org
Objet : Updated Mavenizer

Hi,

today I committed some changes to the Mavenizer Tool.

Change 1 made sure all SDKs (Flex and Air) are processed in the right order
regarding the versions of the SDKs.

Change 2 is a new Deployer "SDKInVMDeployer" which no longer needs Maven to
deploy the Mavenized files as it uses Aether directly to deploy files
directly inside the VM, causing a dramatic speedup of the time needed to
deploy stuff as well as being able to execute without the reliance on an
already installed Maven system. This should make it easy to add the new
Deployer to any sort of installer.

Chris