You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/09/14 14:26:33 UTC
[jira] Resolved: (SLING-1774) OSGi Installer Integration Tests
installs test bundles
[ https://issues.apache.org/jira/browse/SLING-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1774.
-------------------------------------
Resolution: Fixed
Instead of creating the bundles with the jar plugin, i've switched to use an ant task for this; this avoids adding the artifact to the project artifacts
Changed in revision 996865
> OSGi Installer Integration Tests installs test bundles
> ------------------------------------------------------
>
> Key: SLING-1774
> URL: https://issues.apache.org/jira/browse/SLING-1774
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: OSGi Installer 3.0.0
> Reporter: Felix Meschberger
> Assignee: Carsten Ziegeler
> Fix For: OSGi Installer 3.0.0
>
>
> When running "mvn clean install" of the OSGi Installer Integration Tests (installer/osgi/it) project the test JAR files are all installed as artifacts attached to the project.
> This does not do any harm (probably, because I would assume this project is never deployed anyway), it is probably just overkill.
> We should try to prevent installing/deploying these test bundles.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.