You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "David Savage (JIRA)" <ji...@apache.org> on 2009/07/16 10:58:15 UTC
[jira] Created: (FELIX-1366) Bundle classpath should verify that
internal bundle classpath elements actually exist inside bundle before
adding them to eclipse classpath
Bundle classpath should verify that internal bundle classpath elements actually exist inside bundle before adding them to eclipse classpath
-------------------------------------------------------------------------------------------------------------------------------------------
Key: FELIX-1366
URL: https://issues.apache.org/jira/browse/FELIX-1366
Project: Felix
Issue Type: Bug
Components: Sigil
Reporter: David Savage
Priority: Minor
Consider the following bundle from eclipse:
$ unzip -p bldcommon/lib/org.eclipse.ui.workbench_3.4.1.M20080827-0800a.jar META-INF/MANIFEST.MF | grep jar
Bundle-ClassPath: compatibility.jar,.
It claims to have an internal compatability jar inside it. But analysis shows otherwise
$ jar -tf bldcommon/lib/org.eclipse.ui.workbench_3.4.1.M20080827-0800a.jar | grep jar
$
Would be better to silently discard.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1366) Bundle classpath should verify that
internal bundle classpath elements actually exist inside bundle before
adding them to eclipse classpath
Posted by "David Savage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Savage updated FELIX-1366:
--------------------------------
Description:
Consider the following bundle from eclipse:
$ unzip -p bldcommon/lib/org.eclipse.ui.workbench_3.4.1.M20080827-0800a.jar META-INF/MANIFEST.MF | grep jar
Bundle-ClassPath: compatibility.jar,.
It claims to have an internal compatability jar inside it. But analysis shows otherwise
$ jar -tf bldcommon/lib/org.eclipse.ui.workbench_3.4.1.M20080827-0800a.jar | grep jar
$
This leads to the error:
Description Resource Path Location Type
Project 'org.cauldron.sigil.core' is missing required library: '/opt/development/eclipse/workspace/sigil-apache/.metadata/.plugins/org.cauldron.sigil.core/bundle-cache/org.eclipse.ui.workbench_version_3.4.1.M20080827-0800a/compatibility.jar' org.cauldron.sigil.core Build path Build Path Problem
Would be better to silently discard.
was:
Consider the following bundle from eclipse:
$ unzip -p bldcommon/lib/org.eclipse.ui.workbench_3.4.1.M20080827-0800a.jar META-INF/MANIFEST.MF | grep jar
Bundle-ClassPath: compatibility.jar,.
It claims to have an internal compatability jar inside it. But analysis shows otherwise
$ jar -tf bldcommon/lib/org.eclipse.ui.workbench_3.4.1.M20080827-0800a.jar | grep jar
$
Would be better to silently discard.
> Bundle classpath should verify that internal bundle classpath elements actually exist inside bundle before adding them to eclipse classpath
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-1366
> URL: https://issues.apache.org/jira/browse/FELIX-1366
> Project: Felix
> Issue Type: Bug
> Components: Sigil
> Reporter: David Savage
> Priority: Minor
>
> Consider the following bundle from eclipse:
> $ unzip -p bldcommon/lib/org.eclipse.ui.workbench_3.4.1.M20080827-0800a.jar META-INF/MANIFEST.MF | grep jar
> Bundle-ClassPath: compatibility.jar,.
> It claims to have an internal compatability jar inside it. But analysis shows otherwise
> $ jar -tf bldcommon/lib/org.eclipse.ui.workbench_3.4.1.M20080827-0800a.jar | grep jar
> $
> This leads to the error:
> Description Resource Path Location Type
> Project 'org.cauldron.sigil.core' is missing required library: '/opt/development/eclipse/workspace/sigil-apache/.metadata/.plugins/org.cauldron.sigil.core/bundle-cache/org.eclipse.ui.workbench_version_3.4.1.M20080827-0800a/compatibility.jar' org.cauldron.sigil.core Build path Build Path Problem
> Would be better to silently discard.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1366) Bundle classpath should verify that
internal bundle classpath elements actually exist inside bundle before
adding them to eclipse classpath
Posted by "David Savage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Savage closed FELIX-1366.
-------------------------------
Resolution: Fixed
Fix Version/s: sigil-0.1.0
fixed on trunk by testing file exists:
Path p = ".".equals(cp) ? path : cache.append(cp);
f ( p.toFile().exists() ) {
// do previous logic
}
> Bundle classpath should verify that internal bundle classpath elements actually exist inside bundle before adding them to eclipse classpath
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-1366
> URL: https://issues.apache.org/jira/browse/FELIX-1366
> Project: Felix
> Issue Type: Bug
> Components: Sigil
> Reporter: David Savage
> Priority: Minor
> Fix For: sigil-0.1.0
>
>
> Consider the following bundle from eclipse:
> $ unzip -p bldcommon/lib/org.eclipse.ui.workbench_3.4.1.M20080827-0800a.jar META-INF/MANIFEST.MF | grep jar
> Bundle-ClassPath: compatibility.jar,.
> It claims to have an internal compatability jar inside it. But analysis shows otherwise
> $ jar -tf bldcommon/lib/org.eclipse.ui.workbench_3.4.1.M20080827-0800a.jar | grep jar
> $
> This leads to the error:
> Description Resource Path Location Type
> Project 'org.cauldron.sigil.core' is missing required library: '/opt/development/eclipse/workspace/sigil-apache/.metadata/.plugins/org.cauldron.sigil.core/bundle-cache/org.eclipse.ui.workbench_version_3.4.1.M20080827-0800a/compatibility.jar' org.cauldron.sigil.core Build path Build Path Problem
> Would be better to silently discard.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.