Hi Bertrand, Sounds usefull.
Can we name it "autoInstallBundle" to not mixup the meaning of "deploy" with what maven thinks id deployment. In addition, the sling plugin supports a "deploy" goal, which deploys the bundle(s) to an OBR. Apart from that, I think, this is certainly a valid addition. I usually just rely on my command line history or hack the 30-some characters in. Regards Felix Am Donnerstag, den 17.01.2008, 09:45 +0100 schrieb Bertrand Delacretaz: > Hi, > > The patch shown below allows one to auto-install Sling bundles when > building them, using "-P autoDeployBundle" on the mvn command line. > > WDYT, should we do this? I find it useful for development, but maybe > you guys are doing this differently? > > -Bertrand > > Index: parent/pom.xml > =================================================================== > --- parent/pom.xml (revision 612756) > +++ parent/pom.xml (working copy) > @@ -206,6 +206,35 @@ > </pluginManagement> > </build> > > + <profiles> > + <profile> > + <!-- > + Use this profile to deploy the bundle automatically, > + during development > + --> > + <id>autoDeployBundle</id> > + <activation> > + <activeByDefault>false</activeByDefault> > + </activation> > + <build> > + <plugins> > + <plugin> > + <groupId>org.apache.sling</groupId> > + <artifactId>maven-sling-plugin</artifactId> > + <executions> > + <execution> > + <id>install-bundle</id> > + <goals> > + <goal>install</goal> > + </goals> > + </execution> > + </executions> > + </plugin> > + </plugins> > + </build> > + </profile> > + </profiles> > + > <mailingLists> > <mailingList> > <name>Sling Development List</name>
