I think you mistakenly used a colon instead of a period. You used http://10.10.20:156 but I guess you mean http://10.10.20.156<http://10.10.20:156>
<http://10.10.20:156>/Bengt 2010/9/7 Daniele Dellafiore <[email protected]> > mm, I have the web console running and answering at > > http://10.10.20.156:8181/system/console/ > > having felix conf/config.properties these two lines > > org.osgi.service.http.port=8181 > org.osgi.service.http.port.secure=443 > > and the project configured with the maven plugin this way > > <plugin> > <groupId>org.apache.sling</groupId> > <artifactId>maven-sling-plugin</artifactId> > <version>2.0.5-SNAPSHOT</version> > <executions> > <execution> > <id>deploy-bundle</id> > <goals> > <goal>deploy</goal> > </goals> > </execution> > </executions> > <configuration> > <obr>http://10.10.20:156</obr> > <user>admin</user> > <password>admin</password> > </configuration> > </plugin> > > and mvn sling:deploy goes timed out: > > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Deployment on http://10.10.20:156 failed, cause: The host did > not accept the connection within timeout of 5000 ms > > If I add the port to the obr parameters, either 8181 or 443, I receive a > > java.lang.IllegalArgumentException: Invalid uri > 'http://10.10.20:156:443': invalid port number > at > org.apache.commons.httpclient.HttpMethodBase.<init>(HttpMethodBase.java:222) > > In the doc there is no reference to authentication for the deploy > goal... I copied it from the install goal, maybe the problem is there > but I have no more ideas... > > On Tue, Sep 7, 2010 at 11:26 AM, Felix Meschberger <[email protected]> > wrote: > > Hi, > > > > On 07.09.2010 11:23, Daniele Dellafiore wrote: > >> thanks for the answer, I am going to try this today. > >> I am a little concerned about the sling maven plugin doc page saying > >> that it deploys over a sling instance but I'll bet it works in some > >> way :) > > > > In fact, it does not require Sling at all. It requires a running Web > > Console instance to which the bundles are posted. Will update those > > docs. Thanks for pointing out. > > > > Regards > > Felix > > > >> > >> On Wed, Aug 25, 2010 at 12:51 PM, Felix Meschberger <[email protected]> > wrote: > >>> Hi, > >>> > >>> If you have the Apache Felix Web Console [1] you can use the Maven > Sling > >>> Plugin [2] to deploy to a running framework using an HTTP request. > >>> > >>> Regards > >>> Felix > >>> > >>> [1] http://felix.apache.org/site/apache-felix-web-console.html > >>> [2] http://sling.apache.org/site/sling.html > >>> > >>> On 25.08.2010 12:17, Daniele Dellafiore wrote: > >>>> Hi. > >>>> > >>>> I can't figure out how to achieve that goal. > >>>> I have a CI environment and my goal is to have a continuous > >>>> deployment, so when Hudson ends his build/test jobs, it runs a job to > >>>> deploy artifacts. The "wars" are deployed to tomcat with the > >>>> maven-tomcat-plugin, I am wondering how to achieve the same with OSGI > >>>> bundles, deploying them to a Felix installation and triggering the > >>>> restart of the bundle. > >>>> > >>>> Thanks. > >>>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >>> > >> > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > > -- > Daniele Dellafiore > http://danieledellafiore.net > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
