axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harshana Eranga Martin (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (AXIS2-4937) Creating Eclipse Features and a p2 Repository for Axis2 Eclipse IDE plugins
Date Fri, 19 Aug 2011 18:36:27 GMT

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

Harshana Eranga Martin edited comment on AXIS2-4937 at 8/19/11 6:35 PM:
------------------------------------------------------------------------

Hi Andreas,

Correct and Point taken!

But the issue is if there is no manifest present at the build time, Tycho does not work. Which
means we have to rule it out as a solution. So we have no solution at the moment to fix this
issue. 

If we are developing any Eclipse related plugins, it requires certain level of manual process
at least to keep the manifest in sync since we omit a set of dependencies using 

<Embed-Dependency>*;scope=compile|runtime;groupId=!org.eclipse.*;artifactId=!commons-logging|wstx-asl|geronimo-activation_1.1_spec|geronimo-javamail_1.4_spec|geronimo-stax-api_1.0_spec|ant*</Embed-Dependency>

<Embed-Transitive>true</Embed-Transitive> 
<Import-Package>!org.dom4j*,!nu.xom,!org.jdom*,!javax.portlet,!org.apache.commons.io*,*</Import-Package>


rules. 

So we have no other option to proceed on this task unless we agree to use this solution with
someone taking the responsibility of keep the manifest in sync. 

And if we are completely thinking of doing this with Maven only, i don't think there are solution
at the moment.

Thanks and Regards,
Harshana

      was (Author: harshana05):
    Hi Andreas,

Correct and Point taken!

But the issue is if there is no manifest present at the build time, Tycho does not work. Which
means we have to rule it out as a solution. So we have no solution at the moment to fix this
issue. 

If we are developing any Eclipse related plugins, it requires certain level of manual process
at least to keep the manifest in sync since we omit a set of dependencies using 

<Embed-Dependency>*;scope=compile|runtime;groupId=!org.eclipse.*;artifactId=!commons-logging|wstx-asl|geronimo-activation_1.1_spec|geronimo-javamail_1.4_spec|geronimo-stax-api_1.0_spec|ant*</Embed-Dependency>

<Embed-Transitive>true</Embed-Transitive> 
<Import-Package>!org.dom4j*,!nu.xom,!org.jdom*,!javax.portlet,!org.apache.commons.io*,*</Import-Package>


rules. 

So we have no other option to proceed on this task unless we agree to use this solution with
someone taking the responsibility of keep the manifest in sync. 

Thanks and Regards,
Harshana
  
> Creating Eclipse Features and a p2 Repository for Axis2 Eclipse IDE plugins
> ---------------------------------------------------------------------------
>
>                 Key: AXIS2-4937
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4937
>             Project: Axis2
>          Issue Type: New Feature
>          Components: ide plugins
>    Affects Versions: 1.5.4
>            Reporter: Harshana Eranga Martin
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: Axis2_4937_Eclipse_plugins.patch
>
>
> This jira will be used to track the progress of creating Eclipse Features and a p2 repository
for Axis2 Eclipse IDE plugins.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message