You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2013/10/22 16:47:43 UTC
[jira] [Resolved] (SLING-3134) Bundle deployment mechanism does not
deploy on the configured server
[ https://issues.apache.org/jira/browse/SLING-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu resolved SLING-3134.
------------------------------------
Resolution: Fixed
With the latest fixes for SLING-3019, we no longer need to use Maven to deploy bundles. Therefore we now pick up the directory and create a jar file out of it.
This is faster and less error-prone than building and invoking maven launch configurations.
Fixed in http://svn.apache.org/viewvc?view=revision&revision=1534649
> Bundle deployment mechanism does not deploy on the configured server
> --------------------------------------------------------------------
>
> Key: SLING-3134
> URL: https://issues.apache.org/jira/browse/SLING-3134
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Critical
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> The maven deployment mechanism must pass in the:
> - url
> - username
> - password
> for the configured server, otherwise deployment follows the pom.xml definition, not the one from Eclipse
--
This message was sent by Atlassian JIRA
(v6.1#6144)