[jbosstools-issues] [JBoss JIRA] (JBDS-2071) studio/plugins/org.hamcrest.core_1.1.0.v20090501071000 is included in JBDS5.0.beta1 - is this needed?

Nick Boldt (JIRA) jira-events at lists.jboss.org
Thu Mar 15 16:51:47 EDT 2012


    [ https://issues.jboss.org/browse/JBDS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677147#comment-12677147 ] 

Nick Boldt edited comment on JBDS-2071 at 3/15/12 4:50 PM:
-----------------------------------------------------------

Yes, it does - m2e requires it so it's included in com.jboss.jbds.m2e.feature. 

{code:title=https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jbds.m2e.feature/feature.xml}
<!-- dependent 3rd party plugins needed to install m2e -->
<plugin id="ch.qos.logback.classic" version="0.9.27" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="ch.qos.logback.core" version="0.9.27" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="ch.qos.logback.slf4j" version="0.9.27" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.slf4j.api" version="1.6.1" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="com.ning.async-http-client" version="1.6.3" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.jboss.netty" version="3.2.4" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.eclipse.equinox.p2.discovery.compatibility" version="1.0.1" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.eclipse.equinox.p2.discovery" version="1.0.100" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.eclipse.equinox.p2.ui.discovery" version="1.0.0" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.hamcrest.core" version="1.1.0" match="greaterOrEqual" download-size="0" install-size="0" />
{code}


Why is it bad to include it? License terms? Incompatible version? Need a newer/older version? Makes the install base bloated (it's 28K zipped, 152K unpacked, so I doubt that's the case)? 

Contents of Target platform used to build JBDS 5.0.0.Beta1:
{core}
./plugins/org.hamcrest.text_1.1.0.v20090501071000.jar
./plugins/org.hamcrest.library_1.1.0.v20090501071000.jar
./plugins/org.hamcrest_1.1.0.v20090501071000.jar
./plugins/org.hamcrest.core_1.1.0.v20090501071000.jar
./plugins/org.hamcrest.integration_1.1.0.v20090501071000.jar
{core}

Contents of JBDS install footprint (JBDS 5.0.0.Beta1):
{core}
./plugins/org.hamcrest.core_1.1.0.v20090501071000
{core}

                
      was (Author: nickboldt):
    Yes, it does - m2e requires it so it's included in com.jboss.jbds.m2e.feature. 

[^https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jbds.m2e.feature/feature.xml]
{code}
<!-- dependent 3rd party plugins needed to install m2e -->
<plugin id="ch.qos.logback.classic" version="0.9.27" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="ch.qos.logback.core" version="0.9.27" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="ch.qos.logback.slf4j" version="0.9.27" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.slf4j.api" version="1.6.1" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="com.ning.async-http-client" version="1.6.3" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.jboss.netty" version="3.2.4" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.eclipse.equinox.p2.discovery.compatibility" version="1.0.1" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.eclipse.equinox.p2.discovery" version="1.0.100" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.eclipse.equinox.p2.ui.discovery" version="1.0.0" match="greaterOrEqual" download-size="0" install-size="0" />
<plugin id="org.hamcrest.core" version="1.1.0" match="greaterOrEqual" download-size="0" install-size="0" />
{code}


Why is it bad to include it? License terms? Incompatible version? Need a newer/older version? Makes the install base bloated (it's 28K zipped, 152K unpacked, so I doubt that's the case)? 

Contents of Target platform used to build JBDS 5.0.0.Beta1:
{core}
./plugins/org.hamcrest.text_1.1.0.v20090501071000.jar
./plugins/org.hamcrest.library_1.1.0.v20090501071000.jar
./plugins/org.hamcrest_1.1.0.v20090501071000.jar
./plugins/org.hamcrest.core_1.1.0.v20090501071000.jar
./plugins/org.hamcrest.integration_1.1.0.v20090501071000.jar
{core}

Contents of JBDS install footprint (JBDS 5.0.0.Beta1):
{core}
./plugins/org.hamcrest.core_1.1.0.v20090501071000
{core}

                  
> studio/plugins/org.hamcrest.core_1.1.0.v20090501071000 is included in JBDS5.0.beta1 - is this needed?
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-2071
>                 URL: https://issues.jboss.org/browse/JBDS-2071
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Build
>    Affects Versions: 5.0.0.Beta1
>         Environment: Version: 5.0.0.Beta1
> Build id: v20120308-2315-H106-Beta1
> Build date: 20120308-2315
>            Reporter: Len DiMaggio
>            Assignee: Max Rydahl Andersen
>             Fix For: 5.0.0.Beta2
>
>
> studio/plugins/org.hamcrest.core_1.1.0.v20090501071000
> Does JBDS5 depend on this? If not - we should remove it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list