flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric THOMAS <webdoubl...@hotmail.com>
Subject RE: Add Mavenizer functionality to Installer
Date Mon, 28 Oct 2013 09:01:43 GMT
Miguel,

For you issue, you can anyway create a JIRA ticket with the command and args
you used, I'll have a look.

Thanks,
-Fred

-----Message d'origine-----
De : Miguel Ferreira [mailto:miguel.cd.ferreira@hotmail.com] 
Envoyé : lundi 28 octobre 2013 09:49
À : dev@flex.apache.org
Objet : RE: Add Mavenizer functionality to Installer

@ Thomas
Can you give me the 4.10 Mavenized sdk.
I have some problems here because when i run the mavenizer for the SDK i get
a java error that i can not connect.
Exception in thread "main"
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException:
Connection refused: connect

        at
com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle

(URLConnectionClientHandler.java:149)
I think that is because of the policies here inside of the institution and i
could not found a work around.
Any help would be really apreciated.
Best regards,Miguel Ferreira
> From: webdoublefx@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: Add Mavenizer functionality to Installer
> Date: Mon, 28 Oct 2013 09:38:30 +0100
> 
> Hi,
> 
> I maybe found a faster way to give the users a legal access to all the 
> mavenized SDKs to use used with FlexMojos 6.x:
> 
> From the Installer, users already have to accept licenses for the 
> third party artifacts, for those users I can grant access to a online 
> maven repo which serves the Mavenized SDKs, I can even add the lasts 
> nightly mavenized build versions.
> 
> It would be faster than add a maven converter feature to the installer.
> It would make the Mavenized SDKs served from one public server with 
> restricted access to the Installer users who have accepted the licenses.
> I would not allowed anonymous users to download the Mavenized SDKs I 
> would provide them settings with credentials to add to their 
> settings.xml
> 
> In the installer, it could be 1 button along with the checkbox, 
> clickable only if they checked all the third party first, once click 
> it would display the Maven user settings with credentials to add to their
settings.xml.
> 
> The server exist today as it serves me, it serves up to the 4.11 
> version, I would have to restrict it and create a job for the nightly
builds.
> 
> So at the end, it is a minimal work still to do compare to the adding 
> the Installer a maven converter feature and is more in the Maven 
> spirit while meeting the Adobe requirements.
> 
> Tell me what you think pls
> 
> Thanks,
> -Fred
 		 	   		  

Mime
View raw message