You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by li...@apache.org on 2008/04/05 21:53:07 UTC
svn commit: r645167 - /incubator/shindig/trunk/java/gadgets/pom.xml
Author: lindner
Date: Sat Apr 5 12:53:04 2008
New Revision: 645167
URL: http://svn.apache.org/viewvc?rev=645167&view=rev
Log:
Fix for SHINDIG-156
Modified:
incubator/shindig/trunk/java/gadgets/pom.xml
Modified: incubator/shindig/trunk/java/gadgets/pom.xml
URL: http://svn.apache.org/viewvc/incubator/shindig/trunk/java/gadgets/pom.xml?rev=645167&r1=645166&r2=645167&view=diff
==============================================================================
--- incubator/shindig/trunk/java/gadgets/pom.xml (original)
+++ incubator/shindig/trunk/java/gadgets/pom.xml Sat Apr 5 12:53:04 2008
@@ -28,7 +28,7 @@
<groupId>org.apache.shindig</groupId>
<artifactId>gadgets</artifactId>
<version>1-SNAPSHOT</version>
- <packaging>war</packaging>
+ <packaging>jar</packaging>
<name>Apache Shindig Java Gadget Server</name>
<description>
Server part of Shindig for hosting OpenSocial applications.
@@ -62,6 +62,14 @@
</resource>
</webResources>
</configuration>
+ <executions>
+ <execution>
+ <phase>package</phase>
+ <goals>
+ <goal>war</goal>
+ </goals>
+ </execution>
+ </executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins </groupId>
Re: svn commit: r645167 - /incubator/shindig/trunk/java/gadgets/pom.xml
Posted by John Norman <jo...@caret.cam.ac.uk>.
I thought Sakai had switched to ECL 2.0. It turns out Sakai Board has
decided we *will* switch to ECL 2.0 but it is not yet implemented. Any
Sakai contribution can be released using ECL 2.0 while the licensing
machine grinds fine and of course the authors can release their work
themselves under whatever additional license(s) they like.
John
On 8 Apr 2008, at 13:09, Ian Boston wrote:
> Vincent,
> your right, sorry, *if* (in the unlikely event that) anyone wants it,
> I will relicense it as ECL2 of AL2 (after checking with all the
> copyright holders.... there have been some patches from one person)
> However, its not that hard to recreate and the ideas are almost
> certainly out in the public.
>
> Ian
>
>
>
> On 8 Apr 2008, at 12:22, Vincent Siveton wrote:
>> Hi Ian,
>>
>> Happy to see you there :)
>>
>> 2008/4/6, Ian Boston <ie...@tfd.co.uk>:
>>
>> [SNIP]
>>
>>> The license on all of this is Educational Community License which is
>>> compatible with A2, so you could just take it if you wanted or
>>> look at it
>>
>> I am not a Lawyer but Sakai is distributed under ECL1 [1], *not* ECL2
>> (which is AL2 compatible).
>>
>> Cheers,
>>
>> Vincent
>>
>> [1] http://sakaiproject.org/index.php?option=com_content&task=view&id=132&Itemid=261
>> [2] http://www.opensource.org/licenses/ecl2.php
>>
>>> and take the ideas...its very simple and extends the basic maven-
>>> war-plugin.
>>>
>>> There is also something very similar in the deployment plugin
>>> used by
>>> Apache Pluto.
>>>
>>>
>>> but this is just the way I have done it... officially, maven is
>>> not really
>>> targeted at deployment to app servers.
>>>
>>> Ian
>>>
>>>
>>>
>>>
>>> On 6 Apr 2008, at 13:10, Alejandro Rivero wrote:
>>>
>>>> 2008/4/6 Santiago Gala <sa...@gmail.com>:
>>>>
>>>>
>>>>> Doh! forget it. I needed to do mvn *install* (which actually
>>>>> does not
>>>>> install anything) to copy them to the hidden storage under my
>>>>> home.
>>>>>
>>>>>
>>>>
>>>> Now I mention it, I whould thank to know some maven magic for this,
>>>> non for cp but for scp.
>>>>
>>>> Point is, we installed all the shindig in a server machine, and our
>>>> people are more of php/py/etc than of java. As it happens,
>>>> Eclipse can
>>>> do remote debug of a maven-jetty conumdrum without needing any new
>>>> plug-in beyond the default "java project" mode, but we need to do
>>>> an
>>>> "mvn package" and scopy the xxx-source.jar file into Eclipse scope.
>>>>
>>>> Some instructions for debug could actually do a pair of lines in
>>>> the
>>>> README, after the hint of mnv jetty:run-war.
>>>>
>>>> Alejandro
>>>>
>>>
>>>
>
Re: svn commit: r645167 - /incubator/shindig/trunk/java/gadgets/pom.xml
Posted by Ian Boston <ie...@tfd.co.uk>.
Vincent,
your right, sorry, *if* (in the unlikely event that) anyone wants it,
I will relicense it as ECL2 of AL2 (after checking with all the
copyright holders.... there have been some patches from one person)
However, its not that hard to recreate and the ideas are almost
certainly out in the public.
Ian
On 8 Apr 2008, at 12:22, Vincent Siveton wrote:
> Hi Ian,
>
> Happy to see you there :)
>
> 2008/4/6, Ian Boston <ie...@tfd.co.uk>:
>
> [SNIP]
>
>> The license on all of this is Educational Community License which is
>> compatible with A2, so you could just take it if you wanted or
>> look at it
>
> I am not a Lawyer but Sakai is distributed under ECL1 [1], *not* ECL2
> (which is AL2 compatible).
>
> Cheers,
>
> Vincent
>
> [1] http://sakaiproject.org/index.php?
> option=com_content&task=view&id=132&Itemid=261
> [2] http://www.opensource.org/licenses/ecl2.php
>
>> and take the ideas...its very simple and extends the basic maven-
>> war-plugin.
>>
>> There is also something very similar in the deployment plugin
>> used by
>> Apache Pluto.
>>
>>
>> but this is just the way I have done it... officially, maven is
>> not really
>> targeted at deployment to app servers.
>>
>> Ian
>>
>>
>>
>>
>> On 6 Apr 2008, at 13:10, Alejandro Rivero wrote:
>>
>>> 2008/4/6 Santiago Gala <sa...@gmail.com>:
>>>
>>>
>>>> Doh! forget it. I needed to do mvn *install* (which actually
>>>> does not
>>>> install anything) to copy them to the hidden storage under my
>>>> home.
>>>>
>>>>
>>>
>>> Now I mention it, I whould thank to know some maven magic for this,
>>> non for cp but for scp.
>>>
>>> Point is, we installed all the shindig in a server machine, and our
>>> people are more of php/py/etc than of java. As it happens,
>>> Eclipse can
>>> do remote debug of a maven-jetty conumdrum without needing any new
>>> plug-in beyond the default "java project" mode, but we need to do an
>>> "mvn package" and scopy the xxx-source.jar file into Eclipse scope.
>>>
>>> Some instructions for debug could actually do a pair of lines in the
>>> README, after the hint of mnv jetty:run-war.
>>>
>>> Alejandro
>>>
>>
>>
Re: svn commit: r645167 - /incubator/shindig/trunk/java/gadgets/pom.xml
Posted by Vincent Siveton <vs...@apache.org>.
Hi Ian,
Happy to see you there :)
2008/4/6, Ian Boston <ie...@tfd.co.uk>:
[SNIP]
> The license on all of this is Educational Community License which is
> compatible with A2, so you could just take it if you wanted or look at it
I am not a Lawyer but Sakai is distributed under ECL1 [1], *not* ECL2
(which is AL2 compatible).
Cheers,
Vincent
[1] http://sakaiproject.org/index.php?option=com_content&task=view&id=132&Itemid=261
[2] http://www.opensource.org/licenses/ecl2.php
> and take the ideas...its very simple and extends the basic maven-war-plugin.
>
> There is also something very similar in the deployment plugin used by
> Apache Pluto.
>
>
> but this is just the way I have done it... officially, maven is not really
> targeted at deployment to app servers.
>
> Ian
>
>
>
>
> On 6 Apr 2008, at 13:10, Alejandro Rivero wrote:
>
> > 2008/4/6 Santiago Gala <sa...@gmail.com>:
> >
> >
> > > Doh! forget it. I needed to do mvn *install* (which actually does not
> > > install anything) to copy them to the hidden storage under my home.
> > >
> > >
> >
> > Now I mention it, I whould thank to know some maven magic for this,
> > non for cp but for scp.
> >
> > Point is, we installed all the shindig in a server machine, and our
> > people are more of php/py/etc than of java. As it happens, Eclipse can
> > do remote debug of a maven-jetty conumdrum without needing any new
> > plug-in beyond the default "java project" mode, but we need to do an
> > "mvn package" and scopy the xxx-source.jar file into Eclipse scope.
> >
> > Some instructions for debug could actually do a pair of lines in the
> > README, after the hint of mnv jetty:run-war.
> >
> > Alejandro
> >
>
>
Re: svn commit: r645167 - /incubator/shindig/trunk/java/gadgets/pom.xml
Posted by Ian Boston <ie...@tfd.co.uk>.
Ok, good point, "want", "maven" and "plugin" should be replace by
"forced to write a plugin in the absence of anything else that works"
somewhere. :)
I think you can use an Ant Task http://maven.apache.org/ant-
tasks.html to perform what you want inside maven2 and then either
invoke a shell script http://ant.apache.org/manual/CoreTasks/
exec.html or if you want it to work on multiple platforms, use the
ant scp http://ant.apache.org/manual/OptionalTasks/scp.html
Ian
On 6 Apr 2008, at 21:01, Santiago Gala wrote:
> El dom, 06-04-2008 a las 20:46 +0100, Ian Boston escribió:
>> You probably want the Cargo plugin for maven, that deals with
>> deployment into a remote Tomcat, but I have found that buggy at
>> times.
>>
>
> <ranting>
> "want" and "(plugin)?.*maven" in the same sentence is actually bad
> thinking. I'd say, at most: "You will probably be forced to use..."
>
> I mean, maven should just take a simple local shell file with a
> parameter to do
> scp <artifact> <host>:<path>;
> ssh <host> "cd <path> && mvn jetty:run-war"
>
> or something similar, as any sane Makefile would do. Instead it
> requires
> a lot of (hidden,buggy,xml-configured) java code to do every trivial
> task. Which leads to a big documentation nightmare.
> </ranting>
>
> Regards
> Santiago
>
>
>> or as you mention you can run inside maven with jetty, but then the
>> startup may take time.
>>
>>
>> In Sakai we (I) wrote a plugin to do the deployment to a tomcat
>> instance (https://source.sakaiproject.org/svn/maven2/trunk/)
>>
>> this works on a special target and just copies the war into a space
>> defined by maven.tomcat.home, it also deploys to shared, common,
>> server and a special target of component (which you can ignore)
>>
>> The repo is at https://source.sakaiproject.org/maven2/org/
>> sakaiproject/maven/plugins/1.0/
>>
>> the config is
>> <pluginRepositories>
>> .........
>> <pluginRepository>
>> <id>Sakai Plugin Repo</id>
>> <url>http://source.sakaiproject.org/maven2</url>
>> <releases>
>> <enabled>true</enabled>
>> </releases>
>> </pluginRepository>
>> ........
>> </pluginRepositories>
>>
>> <build>
>> ....
>> <plugins>
>> .....
>> <plugin>
>> <inherited>true</inherited>
>> <groupId>org.sakaiproject.maven.plugins</groupId>
>> <artifactId>sakai</artifactId>
>> <version>1.0</version>
>> <extensions>true</extensions>
>> <configuration>
>> <deployDirectory>${maven.tomcat.home}</deployDirectory>
>> <warSourceDirectory>${basedir}/src/webapp</
>> warSourceDirectory>
>> </configuration>
>> </plugin>
>> ....
>> </plugins>
>> ...
>> </build>
>>
>>
>> mvn clean install sakai:deploy -Dmaven.tomcat.home=/opt/mytomcat
>>
>> will build and deploy wars to a running instance. (with the sakai
>> plugin installed)
>>
>> If you webdav (or something else) mount the target tomcat space, you
>> can deploy to a running server elsewhere.
>>
>> The license on all of this is Educational Community License which is
>> compatible with A2, so you could just take it if you wanted or look
>> at it and take the ideas...its very simple and extends the basic
>> maven-war-plugin.
>>
>> There is also something very similar in the deployment plugin used
>> by Apache Pluto.
>>
>>
>> but this is just the way I have done it... officially, maven is not
>> really targeted at deployment to app servers.
>>
>> Ian
>>
>>
>>
>> On 6 Apr 2008, at 13:10, Alejandro Rivero wrote:
>>> 2008/4/6 Santiago Gala <sa...@gmail.com>:
>>>
>>>> Doh! forget it. I needed to do mvn *install* (which actually does
>>>> not
>>>> install anything) to copy them to the hidden storage under my
>>>> home.
>>>>
>>>
>>> Now I mention it, I whould thank to know some maven magic for this,
>>> non for cp but for scp.
>>>
>>> Point is, we installed all the shindig in a server machine, and our
>>> people are more of php/py/etc than of java. As it happens,
>>> Eclipse can
>>> do remote debug of a maven-jetty conumdrum without needing any new
>>> plug-in beyond the default "java project" mode, but we need to do an
>>> "mvn package" and scopy the xxx-source.jar file into Eclipse scope.
>>>
>>> Some instructions for debug could actually do a pair of lines in the
>>> README, after the hint of mnv jetty:run-war.
>>>
>>> Alejandro
>>
> --
> Santiago Gala
> http://memojo.com/~sgala/blog/
>
Re: svn commit: r645167 -
/incubator/shindig/trunk/java/gadgets/pom.xml
Posted by Santiago Gala <sa...@gmail.com>.
El dom, 06-04-2008 a las 20:46 +0100, Ian Boston escribió:
> You probably want the Cargo plugin for maven, that deals with
> deployment into a remote Tomcat, but I have found that buggy at times.
>
<ranting>
"want" and "(plugin)?.*maven" in the same sentence is actually bad
thinking. I'd say, at most: "You will probably be forced to use..."
I mean, maven should just take a simple local shell file with a
parameter to do
scp <artifact> <host>:<path>;
ssh <host> "cd <path> && mvn jetty:run-war"
or something similar, as any sane Makefile would do. Instead it requires
a lot of (hidden,buggy,xml-configured) java code to do every trivial
task. Which leads to a big documentation nightmare.
</ranting>
Regards
Santiago
> or as you mention you can run inside maven with jetty, but then the
> startup may take time.
>
>
> In Sakai we (I) wrote a plugin to do the deployment to a tomcat
> instance (https://source.sakaiproject.org/svn/maven2/trunk/)
>
> this works on a special target and just copies the war into a space
> defined by maven.tomcat.home, it also deploys to shared, common,
> server and a special target of component (which you can ignore)
>
> The repo is at https://source.sakaiproject.org/maven2/org/
> sakaiproject/maven/plugins/1.0/
>
> the config is
> <pluginRepositories>
> .........
> <pluginRepository>
> <id>Sakai Plugin Repo</id>
> <url>http://source.sakaiproject.org/maven2</url>
> <releases>
> <enabled>true</enabled>
> </releases>
> </pluginRepository>
> ........
> </pluginRepositories>
>
> <build>
> ....
> <plugins>
> .....
> <plugin>
> <inherited>true</inherited>
> <groupId>org.sakaiproject.maven.plugins</groupId>
> <artifactId>sakai</artifactId>
> <version>1.0</version>
> <extensions>true</extensions>
> <configuration>
> <deployDirectory>${maven.tomcat.home}</deployDirectory>
> <warSourceDirectory>${basedir}/src/webapp</
> warSourceDirectory>
> </configuration>
> </plugin>
> ....
> </plugins>
> ...
> </build>
>
>
> mvn clean install sakai:deploy -Dmaven.tomcat.home=/opt/mytomcat
>
> will build and deploy wars to a running instance. (with the sakai
> plugin installed)
>
> If you webdav (or something else) mount the target tomcat space, you
> can deploy to a running server elsewhere.
>
> The license on all of this is Educational Community License which is
> compatible with A2, so you could just take it if you wanted or look
> at it and take the ideas...its very simple and extends the basic
> maven-war-plugin.
>
> There is also something very similar in the deployment plugin used
> by Apache Pluto.
>
>
> but this is just the way I have done it... officially, maven is not
> really targeted at deployment to app servers.
>
> Ian
>
>
>
> On 6 Apr 2008, at 13:10, Alejandro Rivero wrote:
> > 2008/4/6 Santiago Gala <sa...@gmail.com>:
> >
> >> Doh! forget it. I needed to do mvn *install* (which actually does
> >> not
> >> install anything) to copy them to the hidden storage under my home.
> >>
> >
> > Now I mention it, I whould thank to know some maven magic for this,
> > non for cp but for scp.
> >
> > Point is, we installed all the shindig in a server machine, and our
> > people are more of php/py/etc than of java. As it happens, Eclipse can
> > do remote debug of a maven-jetty conumdrum without needing any new
> > plug-in beyond the default "java project" mode, but we need to do an
> > "mvn package" and scopy the xxx-source.jar file into Eclipse scope.
> >
> > Some instructions for debug could actually do a pair of lines in the
> > README, after the hint of mnv jetty:run-war.
> >
> > Alejandro
>
--
Santiago Gala
http://memojo.com/~sgala/blog/
Re: svn commit: r645167 - /incubator/shindig/trunk/java/gadgets/pom.xml
Posted by Ian Boston <ie...@tfd.co.uk>.
You probably want the Cargo plugin for maven, that deals with
deployment into a remote Tomcat, but I have found that buggy at times.
or as you mention you can run inside maven with jetty, but then the
startup may take time.
In Sakai we (I) wrote a plugin to do the deployment to a tomcat
instance (https://source.sakaiproject.org/svn/maven2/trunk/)
this works on a special target and just copies the war into a space
defined by maven.tomcat.home, it also deploys to shared, common,
server and a special target of component (which you can ignore)
The repo is at https://source.sakaiproject.org/maven2/org/
sakaiproject/maven/plugins/1.0/
the config is
<pluginRepositories>
.........
<pluginRepository>
<id>Sakai Plugin Repo</id>
<url>http://source.sakaiproject.org/maven2</url>
<releases>
<enabled>true</enabled>
</releases>
</pluginRepository>
........
</pluginRepositories>
<build>
....
<plugins>
.....
<plugin>
<inherited>true</inherited>
<groupId>org.sakaiproject.maven.plugins</groupId>
<artifactId>sakai</artifactId>
<version>1.0</version>
<extensions>true</extensions>
<configuration>
<deployDirectory>${maven.tomcat.home}</deployDirectory>
<warSourceDirectory>${basedir}/src/webapp</
warSourceDirectory>
</configuration>
</plugin>
....
</plugins>
...
</build>
mvn clean install sakai:deploy -Dmaven.tomcat.home=/opt/mytomcat
will build and deploy wars to a running instance. (with the sakai
plugin installed)
If you webdav (or something else) mount the target tomcat space, you
can deploy to a running server elsewhere.
The license on all of this is Educational Community License which is
compatible with A2, so you could just take it if you wanted or look
at it and take the ideas...its very simple and extends the basic
maven-war-plugin.
There is also something very similar in the deployment plugin used
by Apache Pluto.
but this is just the way I have done it... officially, maven is not
really targeted at deployment to app servers.
Ian
On 6 Apr 2008, at 13:10, Alejandro Rivero wrote:
> 2008/4/6 Santiago Gala <sa...@gmail.com>:
>
>> Doh! forget it. I needed to do mvn *install* (which actually does
>> not
>> install anything) to copy them to the hidden storage under my home.
>>
>
> Now I mention it, I whould thank to know some maven magic for this,
> non for cp but for scp.
>
> Point is, we installed all the shindig in a server machine, and our
> people are more of php/py/etc than of java. As it happens, Eclipse can
> do remote debug of a maven-jetty conumdrum without needing any new
> plug-in beyond the default "java project" mode, but we need to do an
> "mvn package" and scopy the xxx-source.jar file into Eclipse scope.
>
> Some instructions for debug could actually do a pair of lines in the
> README, after the hint of mnv jetty:run-war.
>
> Alejandro
Re: svn commit: r645167 - /incubator/shindig/trunk/java/gadgets/pom.xml
Posted by Alejandro Rivero <al...@gmail.com>.
2008/4/6 Santiago Gala <sa...@gmail.com>:
> Doh! forget it. I needed to do mvn *install* (which actually does not
> install anything) to copy them to the hidden storage under my home.
>
Now I mention it, I whould thank to know some maven magic for this,
non for cp but for scp.
Point is, we installed all the shindig in a server machine, and our
people are more of php/py/etc than of java. As it happens, Eclipse can
do remote debug of a maven-jetty conumdrum without needing any new
plug-in beyond the default "java project" mode, but we need to do an
"mvn package" and scopy the xxx-source.jar file into Eclipse scope.
Some instructions for debug could actually do a pair of lines in the
README, after the hint of mnv jetty:run-war.
Alejandro
Re: svn commit: r645167 -
/incubator/shindig/trunk/java/gadgets/pom.xml
Posted by Santiago Gala <sa...@gmail.com>.
El dom, 06-04-2008 a las 09:24 +0200, Santiago Gala escribió:
> I'm -1 on this change unless someone proves me that it actually does
> something. With or without it "mvn package" generates the same war and
> jar files in the target directory. Is it making a difference, then? can
> anyone tell me where and how? I can't find any difference in
>
Doh! forget it. I needed to do mvn *install* (which actually does not
install anything) to copy them to the hidden storage under my home.
God, how I hate maven lack of documentation and obscure commands and
output!
Regards
Santiago
> ls /home/sgala/.m2/repository/org/apache/shindig/gadgets/1-SNAPSHOT/
> gadgets-1-SNAPSHOT.pom gadgets-1-SNAPSHOT.war
> gadgets-1-SNAPSHOT-sources.jar maven-metadata-local.xml
>
> after mvn package, either.
>
> Regards
> Santiago
>
> El sáb, 05-04-2008 a las 19:53 +0000, lindner@apache.org escribió:
> > Author: lindner
> > Date: Sat Apr 5 12:53:04 2008
> > New Revision: 645167
> >
> > URL: http://svn.apache.org/viewvc?rev=645167&view=rev
> > Log:
> > Fix for SHINDIG-156
> >
> > Modified:
> > incubator/shindig/trunk/java/gadgets/pom.xml
> >
> > Modified: incubator/shindig/trunk/java/gadgets/pom.xml
> > URL: http://svn.apache.org/viewvc/incubator/shindig/trunk/java/gadgets/pom.xml?rev=645167&r1=645166&r2=645167&view=diff
> > ==============================================================================
> > --- incubator/shindig/trunk/java/gadgets/pom.xml (original)
> > +++ incubator/shindig/trunk/java/gadgets/pom.xml Sat Apr 5 12:53:04 2008
> > @@ -28,7 +28,7 @@
> > <groupId>org.apache.shindig</groupId>
> > <artifactId>gadgets</artifactId>
> > <version>1-SNAPSHOT</version>
> > - <packaging>war</packaging>
> > + <packaging>jar</packaging>
> > <name>Apache Shindig Java Gadget Server</name>
> > <description>
> > Server part of Shindig for hosting OpenSocial applications.
> > @@ -62,6 +62,14 @@
> > </resource>
> > </webResources>
> > </configuration>
> > + <executions>
> > + <execution>
> > + <phase>package</phase>
> > + <goals>
> > + <goal>war</goal>
> > + </goals>
> > + </execution>
> > + </executions>
> > </plugin>
> > <plugin>
> > <groupId>org.apache.maven.plugins </groupId>
> >
> >
--
Santiago Gala
http://memojo.com/~sgala/blog/
Re: svn commit: r645167 -
/incubator/shindig/trunk/java/gadgets/pom.xml
Posted by Santiago Gala <sa...@gmail.com>.
I'm -1 on this change unless someone proves me that it actually does
something. With or without it "mvn package" generates the same war and
jar files in the target directory. Is it making a difference, then? can
anyone tell me where and how? I can't find any difference in
ls /home/sgala/.m2/repository/org/apache/shindig/gadgets/1-SNAPSHOT/
gadgets-1-SNAPSHOT.pom gadgets-1-SNAPSHOT.war
gadgets-1-SNAPSHOT-sources.jar maven-metadata-local.xml
after mvn package, either.
Regards
Santiago
El sáb, 05-04-2008 a las 19:53 +0000, lindner@apache.org escribió:
> Author: lindner
> Date: Sat Apr 5 12:53:04 2008
> New Revision: 645167
>
> URL: http://svn.apache.org/viewvc?rev=645167&view=rev
> Log:
> Fix for SHINDIG-156
>
> Modified:
> incubator/shindig/trunk/java/gadgets/pom.xml
>
> Modified: incubator/shindig/trunk/java/gadgets/pom.xml
> URL: http://svn.apache.org/viewvc/incubator/shindig/trunk/java/gadgets/pom.xml?rev=645167&r1=645166&r2=645167&view=diff
> ==============================================================================
> --- incubator/shindig/trunk/java/gadgets/pom.xml (original)
> +++ incubator/shindig/trunk/java/gadgets/pom.xml Sat Apr 5 12:53:04 2008
> @@ -28,7 +28,7 @@
> <groupId>org.apache.shindig</groupId>
> <artifactId>gadgets</artifactId>
> <version>1-SNAPSHOT</version>
> - <packaging>war</packaging>
> + <packaging>jar</packaging>
> <name>Apache Shindig Java Gadget Server</name>
> <description>
> Server part of Shindig for hosting OpenSocial applications.
> @@ -62,6 +62,14 @@
> </resource>
> </webResources>
> </configuration>
> + <executions>
> + <execution>
> + <phase>package</phase>
> + <goals>
> + <goal>war</goal>
> + </goals>
> + </execution>
> + </executions>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins </groupId>
>
>
--
Santiago Gala
http://memojo.com/~sgala/blog/