You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Lahiru Gunathilake (JIRA)" <ji...@apache.org> on 2011/07/26 00:47:09 UTC
[jira] [Created] (AIRAVATA-43) Artifact naming convention
Artifact naming convention
--------------------------
Key: AIRAVATA-43
URL: https://issues.apache.org/jira/browse/AIRAVATA-43
Project: Airavata
Issue Type: Improvement
Components: WS-Messenger
Environment: mac
Reporter: Lahiru Gunathilake
Currently the jar files and .aar files generated in WS-messenger doesn't have the name airavata, so I propose it will be nice to have airavata-* to all the jar files which are created under airavata (ex: all the ws-messenger artifacts and xbaya gfac artifacts), so anybody can identify and it looks more consistent.
Regards
Lahiru
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AIRAVATA-43) Artifact naming convention
Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lahiru Gunathilake closed AIRAVATA-43.
--------------------------------------
> Artifact naming convention
> --------------------------
>
> Key: AIRAVATA-43
> URL: https://issues.apache.org/jira/browse/AIRAVATA-43
> Project: Airavata
> Issue Type: Improvement
> Components: WS-Messenger
> Environment: mac
> Reporter: Lahiru Gunathilake
> Assignee: Suresh Marru
>
> Currently the jar files and .aar files generated in WS-messenger doesn't have the name airavata, so I propose it will be nice to have airavata-* to all the jar files which are created under airavata (ex: all the ws-messenger artifacts and xbaya gfac artifacts), so anybody can identify and it looks more consistent.
> Regards
> Lahiru
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AIRAVATA-43) Artifact naming convention
Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lahiru Gunathilake resolved AIRAVATA-43.
----------------------------------------
Resolution: Fixed
Fixed with commit 1151470.
> Artifact naming convention
> --------------------------
>
> Key: AIRAVATA-43
> URL: https://issues.apache.org/jira/browse/AIRAVATA-43
> Project: Airavata
> Issue Type: Improvement
> Components: WS-Messenger
> Environment: mac
> Reporter: Lahiru Gunathilake
> Assignee: Suresh Marru
>
> Currently the jar files and .aar files generated in WS-messenger doesn't have the name airavata, so I propose it will be nice to have airavata-* to all the jar files which are created under airavata (ex: all the ws-messenger artifacts and xbaya gfac artifacts), so anybody can identify and it looks more consistent.
> Regards
> Lahiru
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (AIRAVATA-43) Artifact naming convention
Posted by "Suresh Marru (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Marru reassigned AIRAVATA-43:
------------------------------------
Assignee: Suresh Marru
> Artifact naming convention
> --------------------------
>
> Key: AIRAVATA-43
> URL: https://issues.apache.org/jira/browse/AIRAVATA-43
> Project: Airavata
> Issue Type: Improvement
> Components: WS-Messenger
> Environment: mac
> Reporter: Lahiru Gunathilake
> Assignee: Suresh Marru
>
> Currently the jar files and .aar files generated in WS-messenger doesn't have the name airavata, so I propose it will be nice to have airavata-* to all the jar files which are created under airavata (ex: all the ws-messenger artifacts and xbaya gfac artifacts), so anybody can identify and it looks more consistent.
> Regards
> Lahiru
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira