[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9136) mismatch between MANIFEST.MF and build.properties in org.jboss.ide.eclipse.as.archives.integration.test

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim commented on JBIDE-9136:
-----------------------------------------

removed the nested jar since this is a very exotic approach and I doubt we really need it.

> mismatch between MANIFEST.MF and build.properties in org.jboss.ide.eclipse.as.archives.integration.test
> -------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-9136
>                 URL: https://issues.jboss.org/browse/JBIDE-9136
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS, testing
>    Affects Versions: 3.3.0.M2
>            Reporter: Nick Boldt
>            Assignee: Rob Stryker
>
> In http://anonsvn.jboss.org/repos/jbosstools/trunk/as/tests/org.jboss.ide.eclipse.as.archives.integration.test/,
> build.properties defines that this plugin will have a nested jar in it:
> jars.compile.order = jbossasarchivesintegrationtest.jar
> output.jbossasarchivesintegrationtest.jar = bin/
> however, MANIFEST.MF points its classpath definition at the root, assuming there'll be a classes/*.class folder, not a rooted jar:
> Bundle-ClassPath: .
> You can't have it both ways -- suggest replacing "jbossasarchivesintegrationtest.jar" with "." in build.properties.

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