You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Brian Eaton (JIRA)" <ji...@apache.org> on 2008/04/22 19:45:21 UTC
[jira] Created: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
simplify dependencies, document how to get eclipse working
----------------------------------------------------------
Key: SHINDIG-207
URL: https://issues.apache.org/jira/browse/SHINDIG-207
Project: Shindig
Issue Type: Bug
Reporter: Brian Eaton
Attachments: build-cleanup.patch
Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by David Primmer <da...@gmail.com>.
On Tue, Apr 22, 2008 at 2:00 PM, Ian Boston <ie...@tfd.co.uk> wrote:
> I still think that using
> mvn eclipse:eclipse and setting M2_REPO is the way to import the project
> into eclipse
I found that mvn eclipse:m2eclipse actually worked a little better. I
think it's the same thing as eclipse:eclipse but turns on dependency
mgmt, but I can't find clear evidence of what it does, other than the
recommendation to use it if you're using the m2eclipse eclipse plugin.
Also, beware that the pom.xml for gadgets has a setting that may alter
your eclipse setup.
<plugin>
<groupId>org.apache.maven.plugins </groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<wtpversion>1.0</wtpversion>
</configuration>
</plugin>
if you run the eclipse:eclipse command for the gadgets folder, you'll
add the WTP facet to your project. I mentioned before that I think
this should be removed.
created and added patch https://issues.apache.org/jira/browse/SHINDIG-209
davep
>
> doc is at
> http://maven.apache.org/plugins/maven-eclipse-plugin/index.html
> also see
> http://maven.apache.org/guides/mini/guide-ide-eclipse.html
>
> There also maven goals for
> NetBeans and ntelliJ IDEA
>
>
>
>
> Ian
>
>
>
>
>
> On 22 Apr 2008, at 18:45, Brian Eaton (JIRA) wrote:
>
> > simplify dependencies, document how to get eclipse working
> > ----------------------------------------------------------
> >
> > Key: SHINDIG-207
> > URL: https://issues.apache.org/jira/browse/SHINDIG-207
> > Project: Shindig
> > Issue Type: Bug
> > Reporter: Brian Eaton
> > Attachments: build-cleanup.patch
> >
> > Got a patch for this.
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the issue online.
> >
> >
>
>
Re: [jira] Created: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
Ok had a look at the patch, some points.
Dependency management.
in the base pom there should be a <dependencyManagement> tag not a
<dependency> tag since putting a dependency tag in the base pom will
make everything depend on everything in the base pom... which is not
right.
When dependencies are placed in the child poms (with
dependencyManagement) you only need to put in the artifact and group,
as the dependency management manages scope and version.
A good example of a base pom.
http://svn.apache.org/repos/asf/jackrabbit/trunk/pom.xml
Build.
I still think that using
mvn eclipse:eclipse and setting M2_REPO is the way to import the
project into eclipse
doc is at
http://maven.apache.org/plugins/maven-eclipse-plugin/index.html
also see
http://maven.apache.org/guides/mini/guide-ide-eclipse.html
There also maven goals for
NetBeans and ntelliJ IDEA
Ian
On 22 Apr 2008, at 18:45, Brian Eaton (JIRA) wrote:
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/
> SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch
>
> Got a patch for this.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Michael Angerman <zr...@gmail.com>.
Ian,
Congratulations !! It all worked as you said it would on WINDOWS...
I blew away my maven repository and started over
and pulled the latest code (revision 651956)
I patched revision 651956 with reorganize-poms5.patch...
I ran the following steps from the base directory...
mvn
mvn -Prun
The jetty server came up fine...
I tested the samples and they all came up fine...
And of course it all worked with the following maven environment variable
set...
MAVEN_OPTS
-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y
Excellent job,
Michael I Angerman
On Sat, Apr 26, 2008 at 2:51 PM, Ian Boston (JIRA) <ji...@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Ian Boston updated SHINDIG-207:
> -------------------------------
>
> Attachment: (was: reorganize-poms4.patch)
>
> > simplify dependencies, document how to get eclipse working
> > ----------------------------------------------------------
> >
> > Key: SHINDIG-207
> > URL: https://issues.apache.org/jira/browse/SHINDIG-207
> > Project: Shindig
> > Issue Type: Bug
> > Reporter: Brian Eaton
> > Attachments: build-cleanup.patch, reorganize-poms5.patch
> >
> >
> > Got a patch for this.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
I think it will be possible to launch jetty without changing
directory and without ant. The plugin has lots of config, I just nee
to put it in.
Ian
On 26 Apr 2008, at 14:08, Michael Angerman wrote:
> ------=_Part_522_5189317.1209215329281
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> Ian,
>
> I am not taking off till Monday morning so I will be available
> today and tomorrow (Saturday and Sunday) to do some
> more testing of the build...
>
> Leaving on Monday and back on Monday May 5.
>
> Maven can be installed anywhere you want to put it,
> I put mine in that spot out of my own personal convention...
>
> So, to answer your question it is a variable...
>
> Part II of your questions
>
> I read over the Maven installation notes and there is no
> requirement to set a MAVEN_HOME....
>
> Unlike Ant, if you read the installation instructions for ant
> you will note that an ANT_HOME is required
>
> So, we can NOT assume that people on Windows systems
> will have MAVEN_HOME set...
>
> Also, from what I can read of your pom.xml the reason you are
> invoking Ant is to simplify the build process so people don't have
> to do two things...
>
> 1) switch directories to java/server and
> 2) don't have to type mvn jetty:run or mvn jetty:run-war
>
> I am not proposing you do the following but if you did,
> these are the issues you will have to deal with...
>
> If you asked people to set a MAVEN_HOME then Ant has
> the ability to find maven and execute it... There is a task
> in Ant that allows one to read environment variables.
>
> However, and this is a big however ---
>
> In order to run the webapp in debug mode using the Java Platform
> Debugger
> Architecture (JPDA) ; which is required for
>
> http://cwiki.apache.org/WICKET/maven-jetty-plugin.html
> The following environment variable has to be set
>
> MAVEN_OPTS -Xdebug -Xnoagent -Djava.compiler=NONE
> -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y
>
> And when you do this --- then your code doesn't work at all,
> even with the hard code of the path to Maven
>
> I had to uncomment this whole environment variable MAVEN_OPTS
> in order for the maven to launch as an executable inside Ant...
>
> For some reason, and this will require more research and testing,
> Ant doesn't play well with Maven when these environment variables
> are set.... Granted, I didn't spend much time trying different
> options
> and if someone has time on a Windows box they can play with these
> environment variables and see if they can get things to work...
>
> This is what I was going to do if I had more time before I leave but
> it will have to wait until I get back in town...
>
> There is a new guy working at Webtide -- they are the consulting arm
> of the Jetty folks and his name is Jesse, he just started working with
> the Jetty folks a couple of months back and he is an expert on Maven
> and is helping the Jetty folks come up to speed on developing the
> whole Maven - Jetty interface better...
>
> Here is his blog and contact info...
>
> http://blogs.webtide.com/jesse/
>
> I was going to contact him and spend more time understanding the whole
> plugin architecture of maven as it relates to Jetty -- and ask
> Jesse some
> questions on the direction they are going with Jetty and Maven
> combined...
>
> So, in the mean time I would recommend the simple solution for now,
> and then go for the fancier one on the next round of pom.xml
> updates...
>
> Just have people manually do the following....
>
> 1) Switch to the java/server directory by hand,
> 2) Execute maven by hand with the mvn jetty:run
>
> And then you will be set...
>
> Otherwise, talk to Jesse about the environment variables above,
> or some other person who knows about this topic...
>
> This also leads in to the whole issue of Eclipse and how to properly
> integrate Maven - Eclipse - Jetty and get it all right and simple
> to use...
>
> I have not done any testing with Eclipse at all on this go round...
>
> I am simply trying to get our build tested and working at the
> command line,
> which has clearly not been an easy task...
>
> When I get back in town -- I would also like to address the whole
> Eclipse
> issue
> myself -- and how to do the Jetty Launcher which is a task on the
> JIRA...
>
> I believe this Jesse guy will make some good strides on making
> Jetty as easy
> to use in Eclipse as Tomcat currently is... As you know, Tomcat
> basically
> comes
> out of the box in Eclipse and the debugging environment CURRENTLY
> is much
> easier with Tomcat/Eclipse than it is with Jetty, especially when
> you throw
> the Maven
> Eclipse plugin into the fray...
>
> Enough mumbling,
>
> Thanks for all of your work on this topic,
> Michael I Angerman
>
>
> On Sat, Apr 26, 2008 at 2:54 AM, Ian Boston <ie...@tfd.co.uk> wrote:
>
>> Anyone know if maven is normally installed in the same place on
>> windows,
>> ie
>> c:\apache\maven\bin\mvn.bat
>>
>> Or is it variable ?
>>
>> or... is there any other way of finding the full patch of the
>> executable
>> eg MAVE_HOME, arg0
>>
>> Ian
>>
>>
>>
>>
>> On 26 Apr 2008, at 02:54, Michael Angerman wrote:
>>
>> Ian,
>>>
>>> Excellent call, that was it -- when I hard coded the path in
>>> there the
>>> jetty
>>> server comes up and the samples all run fine...
>>>
>>> Ian/Cassie
>>>
>>> I am heading out of town on Monday morning and will be back the
>>> following
>>> Monday May 5.
>>>
>>> Will be happy to do more testing on Windows upon my return -- but by
>>> then
>>> everything should be working :)
>>>
>>> Have fun !
>>> Michael I Angerman
>>>
>>>
>>> <exec dir="java/server"
>>> executable="c:\apache\maven\bin\mvn.bat" failonerror="true" >
>>> <arg value="jetty:run"/>
>>> <arg
>>> value="-DrunType=${runType}"/>
>>> </exec>
>>>
>>>
>>> On Fri, Apr 25, 2008 at 5:07 PM, Ian Boston <ie...@tfd.co.uk> wrote:
>>>
>>> I have a feeling that this might be a path thing.
>>>>
>>>> where it says
>>>> <exec dir="java/server" executable="mvn" failonerror="true" >
>>>> <arg value="jetty:run"/>
>>>> <arg
>>>> value="-DrunType=${runType}"/>
>>>>
>>>> can you try replacing the mvn with the absolute path to your mvn
>>>> command.
>>>> Thanks
>>>> Ian
>>>>
>>>>
>>>>
>>>>
>>>> On 25 Apr
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Michael Angerman <zr...@gmail.com>.
Ian,
I am not taking off till Monday morning so I will be available
today and tomorrow (Saturday and Sunday) to do some
more testing of the build...
Leaving on Monday and back on Monday May 5.
Maven can be installed anywhere you want to put it,
I put mine in that spot out of my own personal convention...
So, to answer your question it is a variable...
Part II of your questions
I read over the Maven installation notes and there is no
requirement to set a MAVEN_HOME....
Unlike Ant, if you read the installation instructions for ant
you will note that an ANT_HOME is required
So, we can NOT assume that people on Windows systems
will have MAVEN_HOME set...
Also, from what I can read of your pom.xml the reason you are
invoking Ant is to simplify the build process so people don't have
to do two things...
1) switch directories to java/server and
2) don't have to type mvn jetty:run or mvn jetty:run-war
I am not proposing you do the following but if you did,
these are the issues you will have to deal with...
If you asked people to set a MAVEN_HOME then Ant has
the ability to find maven and execute it... There is a task
in Ant that allows one to read environment variables.
However, and this is a big however ---
In order to run the webapp in debug mode using the Java Platform Debugger
Architecture (JPDA) ; which is required for
http://cwiki.apache.org/WICKET/maven-jetty-plugin.html
The following environment variable has to be set
MAVEN_OPTS -Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y
And when you do this --- then your code doesn't work at all,
even with the hard code of the path to Maven
I had to uncomment this whole environment variable MAVEN_OPTS
in order for the maven to launch as an executable inside Ant...
For some reason, and this will require more research and testing,
Ant doesn't play well with Maven when these environment variables
are set.... Granted, I didn't spend much time trying different options
and if someone has time on a Windows box they can play with these
environment variables and see if they can get things to work...
This is what I was going to do if I had more time before I leave but
it will have to wait until I get back in town...
There is a new guy working at Webtide -- they are the consulting arm
of the Jetty folks and his name is Jesse, he just started working with
the Jetty folks a couple of months back and he is an expert on Maven
and is helping the Jetty folks come up to speed on developing the
whole Maven - Jetty interface better...
Here is his blog and contact info...
http://blogs.webtide.com/jesse/
I was going to contact him and spend more time understanding the whole
plugin architecture of maven as it relates to Jetty -- and ask Jesse some
questions on the direction they are going with Jetty and Maven combined...
So, in the mean time I would recommend the simple solution for now,
and then go for the fancier one on the next round of pom.xml updates...
Just have people manually do the following....
1) Switch to the java/server directory by hand,
2) Execute maven by hand with the mvn jetty:run
And then you will be set...
Otherwise, talk to Jesse about the environment variables above,
or some other person who knows about this topic...
This also leads in to the whole issue of Eclipse and how to properly
integrate Maven - Eclipse - Jetty and get it all right and simple to use...
I have not done any testing with Eclipse at all on this go round...
I am simply trying to get our build tested and working at the command line,
which has clearly not been an easy task...
When I get back in town -- I would also like to address the whole Eclipse
issue
myself -- and how to do the Jetty Launcher which is a task on the JIRA...
I believe this Jesse guy will make some good strides on making Jetty as easy
to use in Eclipse as Tomcat currently is... As you know, Tomcat basically
comes
out of the box in Eclipse and the debugging environment CURRENTLY is much
easier with Tomcat/Eclipse than it is with Jetty, especially when you throw
the Maven
Eclipse plugin into the fray...
Enough mumbling,
Thanks for all of your work on this topic,
Michael I Angerman
On Sat, Apr 26, 2008 at 2:54 AM, Ian Boston <ie...@tfd.co.uk> wrote:
> Anyone know if maven is normally installed in the same place on windows,
> ie
> c:\apache\maven\bin\mvn.bat
>
> Or is it variable ?
>
> or... is there any other way of finding the full patch of the executable
> eg MAVE_HOME, arg0
>
> Ian
>
>
>
>
> On 26 Apr 2008, at 02:54, Michael Angerman wrote:
>
> Ian,
> >
> > Excellent call, that was it -- when I hard coded the path in there the
> > jetty
> > server comes up and the samples all run fine...
> >
> > Ian/Cassie
> >
> > I am heading out of town on Monday morning and will be back the
> > following
> > Monday May 5.
> >
> > Will be happy to do more testing on Windows upon my return -- but by
> > then
> > everything should be working :)
> >
> > Have fun !
> > Michael I Angerman
> >
> >
> > <exec dir="java/server"
> > executable="c:\apache\maven\bin\mvn.bat" failonerror="true" >
> > <arg value="jetty:run"/>
> > <arg
> > value="-DrunType=${runType}"/>
> > </exec>
> >
> >
> > On Fri, Apr 25, 2008 at 5:07 PM, Ian Boston <ie...@tfd.co.uk> wrote:
> >
> > I have a feeling that this might be a path thing.
> > >
> > > where it says
> > > <exec dir="java/server" executable="mvn" failonerror="true" >
> > > <arg value="jetty:run"/>
> > > <arg
> > > value="-DrunType=${runType}"/>
> > >
> > > can you try replacing the mvn with the absolute path to your mvn
> > > command.
> > > Thanks
> > > Ian
> > >
> > >
> > >
> > >
> > > On 25 Apr 2008, at 23:29, Michael Angerman wrote:
> > >
> > > Embedded error: Execute failed: java.io.IOException: CreateProcess:
> > > mvn
> > >
> > > > jetty:run -DrunType=full error=2
> > > >
> > > >
> > >
> > >
>
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
Anyone know if maven is normally installed in the same place on
windows, ie
c:\apache\maven\bin\mvn.bat
Or is it variable ?
or... is there any other way of finding the full patch of the
executable eg MAVE_HOME, arg0
Ian
On 26 Apr 2008, at 02:54, Michael Angerman wrote:
> Ian,
>
> Excellent call, that was it -- when I hard coded the path in there
> the jetty
> server comes up and the samples all run fine...
>
> Ian/Cassie
>
> I am heading out of town on Monday morning and will be back the
> following
> Monday May 5.
>
> Will be happy to do more testing on Windows upon my return -- but
> by then
> everything should be working :)
>
> Have fun !
> Michael I Angerman
>
>
> <exec dir="java/server"
> executable="c:\apache\maven\bin\mvn.bat" failonerror="true" >
> <arg value="jetty:run"/>
> <arg
> value="-DrunType=${runType}"/>
> </exec>
>
>
> On Fri, Apr 25, 2008 at 5:07 PM, Ian Boston <ie...@tfd.co.uk> wrote:
>
>> I have a feeling that this might be a path thing.
>>
>> where it says
>> <exec dir="java/server" executable="mvn" failonerror="true" >
>> <arg value="jetty:run"/>
>> <arg
>> value="-DrunType=${runType}"/>
>>
>> can you try replacing the mvn with the absolute path to your mvn
>> command.
>> Thanks
>> Ian
>>
>>
>>
>>
>> On 25 Apr 2008, at 23:29, Michael Angerman wrote:
>>
>> Embedded error: Execute failed: java.io.IOException:
>> CreateProcess: mvn
>>> jetty:run -DrunType=full error=2
>>>
>>
>>
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Michael Angerman <zr...@gmail.com>.
Ian,
Excellent call, that was it -- when I hard coded the path in there the jetty
server comes up and the samples all run fine...
Ian/Cassie
I am heading out of town on Monday morning and will be back the following
Monday May 5.
Will be happy to do more testing on Windows upon my return -- but by then
everything should be working :)
Have fun !
Michael I Angerman
<exec dir="java/server"
executable="c:\apache\maven\bin\mvn.bat" failonerror="true" >
<arg value="jetty:run"/>
<arg
value="-DrunType=${runType}"/>
</exec>
On Fri, Apr 25, 2008 at 5:07 PM, Ian Boston <ie...@tfd.co.uk> wrote:
> I have a feeling that this might be a path thing.
>
> where it says
> <exec dir="java/server" executable="mvn" failonerror="true" >
> <arg value="jetty:run"/>
> <arg
> value="-DrunType=${runType}"/>
>
> can you try replacing the mvn with the absolute path to your mvn command.
> Thanks
> Ian
>
>
>
>
> On 25 Apr 2008, at 23:29, Michael Angerman wrote:
>
> Embedded error: Execute failed: java.io.IOException: CreateProcess: mvn
>> jetty:run -DrunType=full error=2
>>
>
>
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
I have a feeling that this might be a path thing.
where it says
<exec dir="java/server" executable="mvn" failonerror="true" >
<arg value="jetty:run"/>
<arg value="-DrunType=$
{runType}"/>
can you try replacing the mvn with the absolute path to your mvn
command.
Thanks
Ian
On 25 Apr 2008, at 23:29, Michael Angerman wrote:
> Embedded error: Execute failed: java.io.IOException: CreateProcess:
> mvn
> jetty:run -DrunType=full error=2
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Michael Angerman <zr...@gmail.com>.
OK --
In the base directory I do a
mvn
and that works fine and then the second step fails...
mvn -Prun
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[INFO] Building Apache Shindig Project
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-antrun-plugin/1.1/maven-antrun-plugin-1.1.pom
1K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin-parent/2.0.1/maven-plugin-parent-2.0.1
.
pom
7K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-antrun-plugin/1.1/maven-antrun-plugin-1.1.jar
11K downloaded
[INFO] [site:attach-descriptor]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] [install:install]
[INFO] Installing C:\z01shindig\pom.xml to C:\Documents and
Settings\Administrator\.m2\repository\org\apache\shindig\shi
ndig-project\1-SNAPSHOT\shindig-project-1-SNAPSHOT.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-project/2.0.1/maven-project-2.0.1.pom
1K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.1/maven-2.0.1.pom
11K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-profile/2.0.1/maven-profile-2.0.1.pom
1K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-model/2.0.1/maven-model-2.0.1.pom
2K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-artifact-manager/2.0.1/maven-artifact-manager-2.0.1.po
m
1K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-repository-metadata/2.0.1/maven-repository-metadata-2
.
0.1.pom
1K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-artifact/2.0.1/maven-artifact-2.0.1.pom
765b downloaded
Downloading:
http://repo1.maven.org/maven2/ant/ant-launcher/1.6.5/ant-launcher-1.6.5.pom
149b downloaded
Downloading: http://repo1.maven.org/maven2/ant/ant/1.6.5/ant-1.6.5.pom
764b downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-api/2.0.1/maven-plugin-api-2.0.1.pom
643b downloaded
Downloading:
http://repo1.maven.org/maven2/ant/ant-launcher/1.6.5/ant-launcher-1.6.5.jar
8K downloaded
Downloading: http://repo1.maven.org/maven2/ant/ant/1.6.5/ant-1.6.5.jar
1009K downloaded
[INFO] [antrun:run {execution: pack-demo-clean}]
[INFO] Executing tasks
[echo] Running Server of Type full, use -DrunType=full|social|gadgets
to change type
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error executing ant tasks
Embedded error: Execute failed: java.io.IOException: CreateProcess: mvn
jetty:run -DrunType=full error=2
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 18 seconds
[INFO] Finished at: Fri Apr 25 16:25:49 MDT 2008
[INFO] Final Memory: 10M/19M
[INFO]
------------------------------------------------------------------------
On Fri, Apr 25, 2008 at 4:08 PM, Ian Boston <ie...@tfd.co.uk> wrote:
> I think reorganize-poms4.patch should be the current patch.
>
> Can you give it a go,
>
> Thanks
> Ian
>
>
>
>
> On 25 Apr 2008, at 23:04, Michael Angerman wrote:
>
> OK, I found your notes...
>>
>> After you update the patch file, let me know and then I will
>> start over and do the whole thing...
>>
>> Once I run the patch on the trunk then I will do this...
>>
>> In the top level (base) directory....
>>
>> mvn
>>
>> and then
>>
>> mvn -Prun
>>
>> And at this point the Jetty Server should be up and running....
>>
>> On Fri, Apr 25, 2008 at 3:50 PM, Michael Angerman <zr...@gmail.com>
>> wrote:
>>
>> We are making progress here...
>>>
>>> The first thing I do is blow away my Maven repository (just to be sure we
>>> are starting with a clean slate)
>>>
>>> Then I do a clean code checkout...
>>>
>>> Then I ran the
>>>
>>> reorganize-poms4.patch and that worked fine -- no failures...
>>>
>>> I am now in the base directory and I run
>>>
>>> mvn
>>>
>>> And that works --
>>>
>>> Then, at this point I try to run
>>>
>>> mvn jetty:run
>>>
>>> and it can't find jetty...
>>>
>>> Do I have the correct reorganize-poms4.patch file...
>>>
>>> It shows (71kb) and when I put my mouse over the file it shows a
>>> timestamp
>>> of...
>>>
>>> 01:21PM
>>>
>>> Just to be brutally clear...
>>>
>>> Can you send the line by line instructions of how to build and run one
>>> more
>>> time,
>>> assuming that the patch works fine and I have the correct patch file...
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Apr 25, 2008 at 3:17 PM, Ian Boston <ie...@tfd.co.uk> wrote:
>>>
>>> only the reorganize patch,
>>>>
>>>> I based my patch on the ideas build-cleanup.patch, but effectively
>>>> replaced it.
>>>>
>>>> sorry, I don't have editing rights on the jira, buried in the long list
>>>> of
>>>> comments there is an indication.
>>>> Ian
>>>>
>>>>
>>>>
>>>>
>>>> On 25 Apr 2008, at 22:02, Michael Angerman wrote:
>>>>
>>>> Ian,
>>>>
>>>>>
>>>>> I am going to do some testing on a WINDOWS platform...
>>>>>
>>>>> I am going to do a clean checkout of the trunk and then try and run
>>>>> your
>>>>> patches...
>>>>>
>>>>> I tried running a couple of minutes ago and they don't BOTH seem to
>>>>> work...
>>>>>
>>>>> reorganize-poms4.patch goes fine without problems but the
>>>>>
>>>>> build-cleanup.patch fails in certain spots...
>>>>>
>>>>> Am I only supposed to run reorganize or both of them and in what
>>>>> order...
>>>>>
>>>>> Thanks,
>>>>> Michael
>>>>>
>>>>> On Fri, Apr 25, 2008 at 2:21 PM, Ian Boston (JIRA) <ji...@apache.org>
>>>>> wrote:
>>>>>
>>>>>
>>>>> [
>>>>>> https://issues.apache.org/jira/browse/SHINDIG-207
>>>>>> ?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>>>>>
>>>>>> Ian Boston updated SHINDIG-207:
>>>>>> -------------------------------
>>>>>>
>>>>>> Attachment: reorganize-poms4.patch
>>>>>>
>>>>>> Updated patch to include jetty version
>>>>>>
>>>>>> Also changed defaultGoal to install from package.
>>>>>>
>>>>>> There will be some emails following this post (or perhapse before,
>>>>>> depending on how cleaver jira is)
>>>>>>
>>>>>> simplify dependencies, document how to get eclipse working
>>>>>>
>>>>>>> ----------------------------------------------------------
>>>>>>>
>>>>>>> Key: SHINDIG-207
>>>>>>> URL: https://issues.apache.org/jira/browse/SHINDIG-207
>>>>>>> Project: Shindig
>>>>>>> Issue Type: Bug
>>>>>>> Reporter: Brian Eaton
>>>>>>> Attachments: build-cleanup.patch, reorganize-poms4.patch
>>>>>>>
>>>>>>>
>>>>>>> Got a patch for this.
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> This message is automatically generated by JIRA.
>>>>>> -
>>>>>> You can reply to this email to add a comment to the issue online.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
I think reorganize-poms4.patch should be the current patch.
Can you give it a go,
Thanks
Ian
On 25 Apr 2008, at 23:04, Michael Angerman wrote:
> OK, I found your notes...
>
> After you update the patch file, let me know and then I will
> start over and do the whole thing...
>
> Once I run the patch on the trunk then I will do this...
>
> In the top level (base) directory....
>
> mvn
>
> and then
>
> mvn -Prun
>
> And at this point the Jetty Server should be up and running....
>
> On Fri, Apr 25, 2008 at 3:50 PM, Michael Angerman
> <zr...@gmail.com> wrote:
>
>> We are making progress here...
>>
>> The first thing I do is blow away my Maven repository (just to be
>> sure we
>> are starting with a clean slate)
>>
>> Then I do a clean code checkout...
>>
>> Then I ran the
>>
>> reorganize-poms4.patch and that worked fine -- no failures...
>>
>> I am now in the base directory and I run
>>
>> mvn
>>
>> And that works --
>>
>> Then, at this point I try to run
>>
>> mvn jetty:run
>>
>> and it can't find jetty...
>>
>> Do I have the correct reorganize-poms4.patch file...
>>
>> It shows (71kb) and when I put my mouse over the file it shows a
>> timestamp
>> of...
>>
>> 01:21PM
>>
>> Just to be brutally clear...
>>
>> Can you send the line by line instructions of how to build and run
>> one more
>> time,
>> assuming that the patch works fine and I have the correct patch
>> file...
>>
>>
>>
>>
>>
>>
>> On Fri, Apr 25, 2008 at 3:17 PM, Ian Boston <ie...@tfd.co.uk> wrote:
>>
>>> only the reorganize patch,
>>>
>>> I based my patch on the ideas build-cleanup.patch, but effectively
>>> replaced it.
>>>
>>> sorry, I don't have editing rights on the jira, buried in the
>>> long list of
>>> comments there is an indication.
>>> Ian
>>>
>>>
>>>
>>>
>>> On 25 Apr 2008, at 22:02, Michael Angerman wrote:
>>>
>>> Ian,
>>>>
>>>> I am going to do some testing on a WINDOWS platform...
>>>>
>>>> I am going to do a clean checkout of the trunk and then try and
>>>> run your
>>>> patches...
>>>>
>>>> I tried running a couple of minutes ago and they don't BOTH seem to
>>>> work...
>>>>
>>>> reorganize-poms4.patch goes fine without problems but the
>>>>
>>>> build-cleanup.patch fails in certain spots...
>>>>
>>>> Am I only supposed to run reorganize or both of them and in what
>>>> order...
>>>>
>>>> Thanks,
>>>> Michael
>>>>
>>>> On Fri, Apr 25, 2008 at 2:21 PM, Ian Boston (JIRA)
>>>> <ji...@apache.org>
>>>> wrote:
>>>>
>>>>
>>>>> [
>>>>> https://issues.apache.org/jira/browse/SHINDIG-207
>>>>> ?page=com.atlassian.jira.plugin.system.issuetabpanels:all-
>>>>> tabpanel]
>>>>>
>>>>> Ian Boston updated SHINDIG-207:
>>>>> -------------------------------
>>>>>
>>>>> Attachment: reorganize-poms4.patch
>>>>>
>>>>> Updated patch to include jetty version
>>>>>
>>>>> Also changed defaultGoal to install from package.
>>>>>
>>>>> There will be some emails following this post (or perhapse before,
>>>>> depending on how cleaver jira is)
>>>>>
>>>>> simplify dependencies, document how to get eclipse working
>>>>>> ----------------------------------------------------------
>>>>>>
>>>>>> Key: SHINDIG-207
>>>>>> URL: https://issues.apache.org/jira/browse/
>>>>>> SHINDIG-207
>>>>>> Project: Shindig
>>>>>> Issue Type: Bug
>>>>>> Reporter: Brian Eaton
>>>>>> Attachments: build-cleanup.patch, reorganize-poms4.patch
>>>>>>
>>>>>>
>>>>>> Got a patch for this.
>>>>>>
>>>>>
>>>>> --
>>>>> This message is automatically generated by JIRA.
>>>>> -
>>>>> You can reply to this email to add a comment to the issue online.
>>>>>
>>>>>
>>>>>
>>>
>>
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Michael Angerman <zr...@gmail.com>.
OK, I found your notes...
After you update the patch file, let me know and then I will
start over and do the whole thing...
Once I run the patch on the trunk then I will do this...
In the top level (base) directory....
mvn
and then
mvn -Prun
And at this point the Jetty Server should be up and running....
On Fri, Apr 25, 2008 at 3:50 PM, Michael Angerman <zr...@gmail.com> wrote:
> We are making progress here...
>
> The first thing I do is blow away my Maven repository (just to be sure we
> are starting with a clean slate)
>
> Then I do a clean code checkout...
>
> Then I ran the
>
> reorganize-poms4.patch and that worked fine -- no failures...
>
> I am now in the base directory and I run
>
> mvn
>
> And that works --
>
> Then, at this point I try to run
>
> mvn jetty:run
>
> and it can't find jetty...
>
> Do I have the correct reorganize-poms4.patch file...
>
> It shows (71kb) and when I put my mouse over the file it shows a timestamp
> of...
>
> 01:21PM
>
> Just to be brutally clear...
>
> Can you send the line by line instructions of how to build and run one more
> time,
> assuming that the patch works fine and I have the correct patch file...
>
>
>
>
>
>
> On Fri, Apr 25, 2008 at 3:17 PM, Ian Boston <ie...@tfd.co.uk> wrote:
>
>> only the reorganize patch,
>>
>> I based my patch on the ideas build-cleanup.patch, but effectively
>> replaced it.
>>
>> sorry, I don't have editing rights on the jira, buried in the long list of
>> comments there is an indication.
>> Ian
>>
>>
>>
>>
>> On 25 Apr 2008, at 22:02, Michael Angerman wrote:
>>
>> Ian,
>>>
>>> I am going to do some testing on a WINDOWS platform...
>>>
>>> I am going to do a clean checkout of the trunk and then try and run your
>>> patches...
>>>
>>> I tried running a couple of minutes ago and they don't BOTH seem to
>>> work...
>>>
>>> reorganize-poms4.patch goes fine without problems but the
>>>
>>> build-cleanup.patch fails in certain spots...
>>>
>>> Am I only supposed to run reorganize or both of them and in what order...
>>>
>>> Thanks,
>>> Michael
>>>
>>> On Fri, Apr 25, 2008 at 2:21 PM, Ian Boston (JIRA) <ji...@apache.org>
>>> wrote:
>>>
>>>
>>>> [
>>>> https://issues.apache.org/jira/browse/SHINDIG-207
>>>> ?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>>>
>>>> Ian Boston updated SHINDIG-207:
>>>> -------------------------------
>>>>
>>>> Attachment: reorganize-poms4.patch
>>>>
>>>> Updated patch to include jetty version
>>>>
>>>> Also changed defaultGoal to install from package.
>>>>
>>>> There will be some emails following this post (or perhapse before,
>>>> depending on how cleaver jira is)
>>>>
>>>> simplify dependencies, document how to get eclipse working
>>>>> ----------------------------------------------------------
>>>>>
>>>>> Key: SHINDIG-207
>>>>> URL: https://issues.apache.org/jira/browse/SHINDIG-207
>>>>> Project: Shindig
>>>>> Issue Type: Bug
>>>>> Reporter: Brian Eaton
>>>>> Attachments: build-cleanup.patch, reorganize-poms4.patch
>>>>>
>>>>>
>>>>> Got a patch for this.
>>>>>
>>>>
>>>> --
>>>> This message is automatically generated by JIRA.
>>>> -
>>>> You can reply to this email to add a comment to the issue online.
>>>>
>>>>
>>>>
>>
>
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Michael Angerman <zr...@gmail.com>.
We are making progress here...
The first thing I do is blow away my Maven repository (just to be sure we
are starting with a clean slate)
Then I do a clean code checkout...
Then I ran the
reorganize-poms4.patch and that worked fine -- no failures...
I am now in the base directory and I run
mvn
And that works --
Then, at this point I try to run
mvn jetty:run
and it can't find jetty...
Do I have the correct reorganize-poms4.patch file...
It shows (71kb) and when I put my mouse over the file it shows a timestamp
of...
01:21PM
Just to be brutally clear...
Can you send the line by line instructions of how to build and run one more
time,
assuming that the patch works fine and I have the correct patch file...
On Fri, Apr 25, 2008 at 3:17 PM, Ian Boston <ie...@tfd.co.uk> wrote:
> only the reorganize patch,
>
> I based my patch on the ideas build-cleanup.patch, but effectively replaced
> it.
>
> sorry, I don't have editing rights on the jira, buried in the long list of
> comments there is an indication.
> Ian
>
>
>
>
> On 25 Apr 2008, at 22:02, Michael Angerman wrote:
>
> Ian,
>>
>> I am going to do some testing on a WINDOWS platform...
>>
>> I am going to do a clean checkout of the trunk and then try and run your
>> patches...
>>
>> I tried running a couple of minutes ago and they don't BOTH seem to
>> work...
>>
>> reorganize-poms4.patch goes fine without problems but the
>>
>> build-cleanup.patch fails in certain spots...
>>
>> Am I only supposed to run reorganize or both of them and in what order...
>>
>> Thanks,
>> Michael
>>
>> On Fri, Apr 25, 2008 at 2:21 PM, Ian Boston (JIRA) <ji...@apache.org>
>> wrote:
>>
>>
>>> [
>>> https://issues.apache.org/jira/browse/SHINDIG-207
>>> ?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>>
>>> Ian Boston updated SHINDIG-207:
>>> -------------------------------
>>>
>>> Attachment: reorganize-poms4.patch
>>>
>>> Updated patch to include jetty version
>>>
>>> Also changed defaultGoal to install from package.
>>>
>>> There will be some emails following this post (or perhapse before,
>>> depending on how cleaver jira is)
>>>
>>> simplify dependencies, document how to get eclipse working
>>>> ----------------------------------------------------------
>>>>
>>>> Key: SHINDIG-207
>>>> URL: https://issues.apache.org/jira/browse/SHINDIG-207
>>>> Project: Shindig
>>>> Issue Type: Bug
>>>> Reporter: Brian Eaton
>>>> Attachments: build-cleanup.patch, reorganize-poms4.patch
>>>>
>>>>
>>>> Got a patch for this.
>>>>
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> -
>>> You can reply to this email to add a comment to the issue online.
>>>
>>>
>>>
>
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
only the reorganize patch,
I based my patch on the ideas build-cleanup.patch, but effectively
replaced it.
sorry, I don't have editing rights on the jira, buried in the long
list of comments there is an indication.
Ian
On 25 Apr 2008, at 22:02, Michael Angerman wrote:
> Ian,
>
> I am going to do some testing on a WINDOWS platform...
>
> I am going to do a clean checkout of the trunk and then try and run
> your
> patches...
>
> I tried running a couple of minutes ago and they don't BOTH seem to
> work...
>
> reorganize-poms4.patch goes fine without problems but the
>
> build-cleanup.patch fails in certain spots...
>
> Am I only supposed to run reorganize or both of them and in what
> order...
>
> Thanks,
> Michael
>
> On Fri, Apr 25, 2008 at 2:21 PM, Ian Boston (JIRA)
> <ji...@apache.org> wrote:
>
>>
>> [
>> https://issues.apache.org/jira/browse/SHINDIG-207?
>> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>
>> Ian Boston updated SHINDIG-207:
>> -------------------------------
>>
>> Attachment: reorganize-poms4.patch
>>
>> Updated patch to include jetty version
>>
>> Also changed defaultGoal to install from package.
>>
>> There will be some emails following this post (or perhapse before,
>> depending on how cleaver jira is)
>>
>>> simplify dependencies, document how to get eclipse working
>>> ----------------------------------------------------------
>>>
>>> Key: SHINDIG-207
>>> URL: https://issues.apache.org/jira/browse/
>>> SHINDIG-207
>>> Project: Shindig
>>> Issue Type: Bug
>>> Reporter: Brian Eaton
>>> Attachments: build-cleanup.patch, reorganize-poms4.patch
>>>
>>>
>>> Got a patch for this.
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Michael Angerman <zr...@gmail.com>.
Ian,
I am going to do some testing on a WINDOWS platform...
I am going to do a clean checkout of the trunk and then try and run your
patches...
I tried running a couple of minutes ago and they don't BOTH seem to work...
reorganize-poms4.patch goes fine without problems but the
build-cleanup.patch fails in certain spots...
Am I only supposed to run reorganize or both of them and in what order...
Thanks,
Michael
On Fri, Apr 25, 2008 at 2:21 PM, Ian Boston (JIRA) <ji...@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Ian Boston updated SHINDIG-207:
> -------------------------------
>
> Attachment: reorganize-poms4.patch
>
> Updated patch to include jetty version
>
> Also changed defaultGoal to install from package.
>
> There will be some emails following this post (or perhapse before,
> depending on how cleaver jira is)
>
> > simplify dependencies, document how to get eclipse working
> > ----------------------------------------------------------
> >
> > Key: SHINDIG-207
> > URL: https://issues.apache.org/jira/browse/SHINDIG-207
> > Project: Shindig
> > Issue Type: Bug
> > Reporter: Brian Eaton
> > Attachments: build-cleanup.patch, reorganize-poms4.patch
> >
> >
> > Got a patch for this.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: reorganize-poms6.patch
Updated patch to take into account issues reported, hope this is right.
patch created against r652383
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms5.patch, reorganize-poms6.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Vincent Siveton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592341#action_12592341 ]
Vincent Siveton commented on SHINDIG-207:
-----------------------------------------
Ian's patch sounds good to me.
Here are some potential addons:
- using dependencyManagement for project dependencies like org.apache.shindig:shindig-common. The maintenance will be more easier.
- using pluginManagement for eclipse and war plugins.
Finally, I recommend to have a parent POM for project properties like issueManagement, distributionManagement, mailingLists, developers. These properties change rarely.
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, pom-reord-README.patch, reorganize-poms2.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: (was: reorganize-poms2.patch)
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms3.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SHINDIG-207) simplify dependencies, document
how to get eclipse working
Posted by Cassie <do...@google.com>.
2. oh i see your note at the bottom of the file now. i don't actually use
eclipse so was just pulling in brian eaton's comment from above. this looks
like something we can easily change later if we want. lets defer for now.
6. looks like it was just line 76 - a ciManagement section?
8. okay, cool, we can just get rid of it later if we want to. lets defer for
now.
Alright, with all that, if you can attach a new patch I'll go and check it
in.
Thanks!
- Cassie
On Wed, Apr 30, 2008 at 4:02 PM, Ian Boston <ie...@tfd.co.uk> wrote:
> 1, yes sorry, cut and paste error, fixed, will updated.
> 2. The problem is MECLIPSE-444 which will be fixed in 2.5.2, not certain
> what to do here ? Users can edit the eclipse project to fix the errors.....
> but it would be nice to make it work.
>
> Alternatively,
> svn mv javascript jstemp
> svn commit
> svn mkdir javascript
> svn mv jstemp javascript/src
>
> and then add a pom with a zip target so the javascript can be packaged.
>
> features probably want to be a jar
>
> ..... but I dont know if that is acceptable for other languages ? (please
> advise)
>
> 3. I should probably update my local copy and recreate the branch and fix.
> Will do.
> 4. Fixed, yes
> 5. Fixed, yes
> 6. Really, checked and couldn't see anything ?
> 7. Will update and regen the patch
>
> 8.
> There was a pom there already so I thought that was the right place.
> For those that open up, read the read me, build and want to just build the
> java code, they don't have to cd anywhere....... but that might not be right
> as more servers come in. It could all be moved into java, along with the
> build instructions. (please advise)
>
> moving will mean we have to get MECLIPSE-444 fixed.
>
>
> Ian
>
>
>
>
> On 30 Apr 2008, at 14:32, Cassie Doll (JIRA) wrote:
>
>
>> [ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593327#action_12593327
>> ]
>>
>> Cassie Doll commented on SHINDIG-207:
>> -------------------------------------
>>
>> So before we commit this patch it looks like:
>>
>> 1. The root/README file should not be changed to remove the php and
>> javascript references. (I think this might be just a copy and paste error)
>> 2. the eclipse instructions don't work for everyone
>> 3. the web.social.xml and web.full.xml files are missing the new rest
>> servlet
>> 4. there is a commented out section in server/pom.xml for the execution
>> war thing, can we just delete it?
>> 5. why does server/README have different build instructions than
>> BUILD-JAVA
>> 6. java/pom.xml - there is some more commented out stuff in here which can
>> probably just be deleted
>> 7. java/social-api/pom.xml - unfortunately the patch is out of date with
>> head for this file
>> 8. just curious - why do we have a pom.xml file in our root directory?
>> this seems weird as the root directory also has the php project in it, and
>> all the java specific stuff should go in the java dir. right?
>>
>> simplify dependencies, document how to get eclipse working
>>> ----------------------------------------------------------
>>>
>>> Key: SHINDIG-207
>>> URL: https://issues.apache.org/jira/browse/SHINDIG-207
>>> Project: Shindig
>>> Issue Type: Bug
>>> Reporter: Brian Eaton
>>> Attachments: build-cleanup.patch, reorganize-poms5.patch
>>>
>>>
>>> Got a patch for this.
>>>
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
Re: [jira] Commented: (SHINDIG-207) simplify dependencies, document
how to get eclipse working
Posted by Cassie <do...@google.com>.
I thought the instructions weren't actually broken Brian. Do these two lines
at the bottom of the file:
"At the moment, you will have to edit the source dependencies to remove
nested folders.
On each project, edit properties, Build Path, Source and remove missing
Source folders."
Not fix the issue?
Perhaps you are talking about a different bug than Ian?
- Cassie
On Wed, Apr 30, 2008 at 5:27 PM, Brian Eaton <be...@google.com> wrote:
> On Wed, Apr 30, 2008 at 7:02 AM, Ian Boston <ie...@tfd.co.uk> wrote:
> > 2. The problem is MECLIPSE-444 which will be fixed in 2.5.2, not certain
> > what to do here ? Users can edit the eclipse project to fix the
> errors.....
> > but it would be nice to make it work.
> >
> > Alternatively,
> > svn mv javascript jstemp
> > svn commit
> > svn mkdir javascript
> > svn mv jstemp javascript/src
> >
> > and then add a pom with a zip target so the javascript can be packaged.
> >
> > features probably want to be a jar
> >
> > ..... but I dont know if that is acceptable for other languages ?
> (please
> > advise)
>
> I can't advise on the other languages, but having broken instructions
> in the README is not cool. We should remove them entirely if we can't
> fix them.
>
> (The Maven eclipse plug-in does work, so my opinion is we ought to
> document how to use it, if we doc anything.)
>
Re: [jira] Commented: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Brian Eaton <be...@google.com>.
On Wed, Apr 30, 2008 at 7:02 AM, Ian Boston <ie...@tfd.co.uk> wrote:
> 2. The problem is MECLIPSE-444 which will be fixed in 2.5.2, not certain
> what to do here ? Users can edit the eclipse project to fix the errors.....
> but it would be nice to make it work.
>
> Alternatively,
> svn mv javascript jstemp
> svn commit
> svn mkdir javascript
> svn mv jstemp javascript/src
>
> and then add a pom with a zip target so the javascript can be packaged.
>
> features probably want to be a jar
>
> ..... but I dont know if that is acceptable for other languages ? (please
> advise)
I can't advise on the other languages, but having broken instructions
in the README is not cool. We should remove them entirely if we can't
fix them.
(The Maven eclipse plug-in does work, so my opinion is we ought to
document how to use it, if we doc anything.)
Re: [jira] Commented: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
1, yes sorry, cut and paste error, fixed, will updated.
2. The problem is MECLIPSE-444 which will be fixed in 2.5.2, not
certain what to do here ? Users can edit the eclipse project to fix
the errors..... but it would be nice to make it work.
Alternatively,
svn mv javascript jstemp
svn commit
svn mkdir javascript
svn mv jstemp javascript/src
and then add a pom with a zip target so the javascript can be packaged.
features probably want to be a jar
..... but I dont know if that is acceptable for other languages ?
(please advise)
3. I should probably update my local copy and recreate the branch and
fix. Will do.
4. Fixed, yes
5. Fixed, yes
6. Really, checked and couldn't see anything ?
7. Will update and regen the patch
8.
There was a pom there already so I thought that was the right place.
For those that open up, read the read me, build and want to just
build the java code, they don't have to cd anywhere....... but that
might not be right as more servers come in. It could all be moved
into java, along with the build instructions. (please advise)
moving will mean we have to get MECLIPSE-444 fixed.
Ian
On 30 Apr 2008, at 14:32, Cassie Doll (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/SHINDIG-207?
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=12593327#action_12593327 ]
>
> Cassie Doll commented on SHINDIG-207:
> -------------------------------------
>
> So before we commit this patch it looks like:
>
> 1. The root/README file should not be changed to remove the php and
> javascript references. (I think this might be just a copy and paste
> error)
> 2. the eclipse instructions don't work for everyone
> 3. the web.social.xml and web.full.xml files are missing the new
> rest servlet
> 4. there is a commented out section in server/pom.xml for the
> execution war thing, can we just delete it?
> 5. why does server/README have different build instructions than
> BUILD-JAVA
> 6. java/pom.xml - there is some more commented out stuff in here
> which can probably just be deleted
> 7. java/social-api/pom.xml - unfortunately the patch is out of date
> with head for this file
> 8. just curious - why do we have a pom.xml file in our root
> directory? this seems weird as the root directory also has the php
> project in it, and all the java specific stuff should go in the
> java dir. right?
>
>> simplify dependencies, document how to get eclipse working
>> ----------------------------------------------------------
>>
>> Key: SHINDIG-207
>> URL: https://issues.apache.org/jira/browse/
>> SHINDIG-207
>> Project: Shindig
>> Issue Type: Bug
>> Reporter: Brian Eaton
>> Attachments: build-cleanup.patch, reorganize-poms5.patch
>>
>>
>> Got a patch for this.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
[jira] Commented: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593327#action_12593327 ]
Cassie Doll commented on SHINDIG-207:
-------------------------------------
So before we commit this patch it looks like:
1. The root/README file should not be changed to remove the php and javascript references. (I think this might be just a copy and paste error)
2. the eclipse instructions don't work for everyone
3. the web.social.xml and web.full.xml files are missing the new rest servlet
4. there is a commented out section in server/pom.xml for the execution war thing, can we just delete it?
5. why does server/README have different build instructions than BUILD-JAVA
6. java/pom.xml - there is some more commented out stuff in here which can probably just be deleted
7. java/social-api/pom.xml - unfortunately the patch is out of date with head for this file
8. just curious - why do we have a pom.xml file in our root directory? this seems weird as the root directory also has the php project in it, and all the java specific stuff should go in the java dir. right?
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms5.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: pom-reord-README.patch
Patch to modify the build and run instructions.
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, pom-reord-README.patch, reorganize-poms2.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Eaton updated SHINDIG-207:
--------------------------------
Attachment: build-cleanup.patch
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
Found it,
change the defaultGoal from package to install in the base pom.xml
line 410,
I will update the patch
Ian
On 25 Apr 2008, at 19:17, Brian Eaton (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/SHINDIG-207?
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=12592459#action_12592459 ]
>
> Brian Eaton commented on SHINDIG-207:
> -------------------------------------
>
> Definitely making progress.
>
> BUILD-JAVA: I love that this file exists. The instructions don't
> quite work, for me at least, but I think this is the right
> direction to be headed.
>
> Specific comment: Numbering is wrong (too items numbered "3")
>
> Specific comment: mvn -Prun does not work
> [exec] [INFO]
> ----------------------------------------------------------------------
> --
> [exec] [ERROR] BUILD ERROR
> [exec] [INFO]
> ----------------------------------------------------------------------
> --
> [exec] [INFO] Failed to resolve artifact.
>
> [exec] Missing:
> [exec] ----------
> [exec] 1) org.apache.shindig:gadgets:jar:1-SNAPSHOT
>
> [exec] Try downloading the file manually from the project
> website.
>
> [exec] Then, install it using the command:
> [exec] mvn install:install-file -
> DgroupId=org.apache.shindig -DartifactId=gadgets -Dversion=1-
> SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>
>
>
> Specific comment: these steps don't work, or maybe they are just
> vague and I'm doing the wrong thing. What directory should be
> specified as the root of the project? When I add shindig, shindig/
> java, or shindig/java/gadgets, I still get errors saying "Project
> 'gadgets' is missing required source folder: '/home/beaton/sb/
> shindig/config'"
>
>
>
> The POMs look cleaner, looks like most version numbers only need to
> be changed in one place. The Shindig version numbers are still
> duplicated, but using the maven snapshot plugin will fix that,
> right? That could happen later.
>
>> simplify dependencies, document how to get eclipse working
>> ----------------------------------------------------------
>>
>> Key: SHINDIG-207
>> URL: https://issues.apache.org/jira/browse/
>> SHINDIG-207
>> Project: Shindig
>> Issue Type: Bug
>> Reporter: Brian Eaton
>> Attachments: build-cleanup.patch, reorganize-poms3.patch
>>
>>
>> Got a patch for this.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
Re: [jira] Commented: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
Did you try a
mvn
and then
mvn -Prun
?
I will wipe my local repo to check what I have here works.
Ian
On 25 Apr 2008, at 19:17, Brian Eaton (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/SHINDIG-207?
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=12592459#action_12592459 ]
>
> Brian Eaton commented on SHINDIG-207:
> -------------------------------------
>
> Definitely making progress.
>
> BUILD-JAVA: I love that this file exists. The instructions don't
> quite work, for me at least, but I think this is the right
> direction to be headed.
>
> Specific comment: Numbering is wrong (too items numbered "3")
>
> Specific comment: mvn -Prun does not work
> [exec] [INFO]
> ----------------------------------------------------------------------
> --
> [exec] [ERROR] BUILD ERROR
> [exec] [INFO]
> ----------------------------------------------------------------------
> --
> [exec] [INFO] Failed to resolve artifact.
>
> [exec] Missing:
> [exec] ----------
> [exec] 1) org.apache.shindig:gadgets:jar:1-SNAPSHOT
>
> [exec] Try downloading the file manually from the project
> website.
>
> [exec] Then, install it using the command:
> [exec] mvn install:install-file -
> DgroupId=org.apache.shindig -DartifactId=gadgets -Dversion=1-
> SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>
>
>
> Specific comment: these steps don't work, or maybe they are just
> vague and I'm doing the wrong thing. What directory should be
> specified as the root of the project? When I add shindig, shindig/
> java, or shindig/java/gadgets, I still get errors saying "Project
> 'gadgets' is missing required source folder: '/home/beaton/sb/
> shindig/config'"
>
>
>
> The POMs look cleaner, looks like most version numbers only need to
> be changed in one place. The Shindig version numbers are still
> duplicated, but using the maven snapshot plugin will fix that,
> right? That could happen later.
>
>> simplify dependencies, document how to get eclipse working
>> ----------------------------------------------------------
>>
>> Key: SHINDIG-207
>> URL: https://issues.apache.org/jira/browse/
>> SHINDIG-207
>> Project: Shindig
>> Issue Type: Bug
>> Reporter: Brian Eaton
>> Attachments: build-cleanup.patch, reorganize-poms3.patch
>>
>>
>> Got a patch for this.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
Re: [jira] Commented: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
I can reproduce, my mistake, I will fix, sorry
Ian
On 25 Apr 2008, at 19:17, Brian Eaton (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/SHINDIG-207?
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=12592459#action_12592459 ]
>
> Brian Eaton commented on SHINDIG-207:
> -------------------------------------
>
> Definitely making progress.
>
> BUILD-JAVA: I love that this file exists. The instructions don't
> quite work, for me at least, but I think this is the right
> direction to be headed.
>
> Specific comment: Numbering is wrong (too items numbered "3")
>
> Specific comment: mvn -Prun does not work
> [exec] [INFO]
> ----------------------------------------------------------------------
> --
> [exec] [ERROR] BUILD ERROR
> [exec] [INFO]
> ----------------------------------------------------------------------
> --
> [exec] [INFO] Failed to resolve artifact.
>
> [exec] Missing:
> [exec] ----------
> [exec] 1) org.apache.shindig:gadgets:jar:1-SNAPSHOT
>
> [exec] Try downloading the file manually from the project
> website.
>
> [exec] Then, install it using the command:
> [exec] mvn install:install-file -
> DgroupId=org.apache.shindig -DartifactId=gadgets -Dversion=1-
> SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>
>
>
> Specific comment: these steps don't work, or maybe they are just
> vague and I'm doing the wrong thing. What directory should be
> specified as the root of the project? When I add shindig, shindig/
> java, or shindig/java/gadgets, I still get errors saying "Project
> 'gadgets' is missing required source folder: '/home/beaton/sb/
> shindig/config'"
>
>
>
> The POMs look cleaner, looks like most version numbers only need to
> be changed in one place. The Shindig version numbers are still
> duplicated, but using the maven snapshot plugin will fix that,
> right? That could happen later.
>
>> simplify dependencies, document how to get eclipse working
>> ----------------------------------------------------------
>>
>> Key: SHINDIG-207
>> URL: https://issues.apache.org/jira/browse/
>> SHINDIG-207
>> Project: Shindig
>> Issue Type: Bug
>> Reporter: Brian Eaton
>> Attachments: build-cleanup.patch, reorganize-poms3.patch
>>
>>
>> Got a patch for this.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
[jira] Commented: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592459#action_12592459 ]
Brian Eaton commented on SHINDIG-207:
-------------------------------------
Definitely making progress.
BUILD-JAVA: I love that this file exists. The instructions don't quite work, for me at least, but I think this is the right direction to be headed.
Specific comment: Numbering is wrong (too items numbered "3")
Specific comment: mvn -Prun does not work
[exec] [INFO] ------------------------------------------------------------------------
[exec] [ERROR] BUILD ERROR
[exec] [INFO] ------------------------------------------------------------------------
[exec] [INFO] Failed to resolve artifact.
[exec] Missing:
[exec] ----------
[exec] 1) org.apache.shindig:gadgets:jar:1-SNAPSHOT
[exec] Try downloading the file manually from the project website.
[exec] Then, install it using the command:
[exec] mvn install:install-file -DgroupId=org.apache.shindig -DartifactId=gadgets -Dversion=1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Specific comment: these steps don't work, or maybe they are just vague and I'm doing the wrong thing. What directory should be specified as the root of the project? When I add shindig, shindig/java, or shindig/java/gadgets, I still get errors saying "Project 'gadgets' is missing required source folder: '/home/beaton/sb/shindig/config'"
The POMs look cleaner, looks like most version numbers only need to be changed in one place. The Shindig version numbers are still duplicated, but using the maven snapshot plugin will fix that, right? That could happen later.
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms3.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594232#action_12594232 ]
Cassie Doll commented on SHINDIG-207:
-------------------------------------
Alright, I'm sure we can probably do more cleanup here but I think this patch is a good start. And most importantly it works for our windows users while head does not. I am going to patch and submit now.
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms5.patch, reorganize-poms6.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592418#action_12592418 ]
Ian Boston commented on SHINDIG-207:
------------------------------------
Ahh, no, the reorganize-poms3.patch was built from the first patch. but is standalone,
the Vincents patch on 213, is partially included, but in a different place. I decided to put the maven-eclipse plugin in as a concrete plugin with its version number. I sent an email about the project/artifact naming in eclipse.... for your consideration.
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms3.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: reorganize-poms2.patch
New version with the ability to run with a full, gadgets only or social only test container
mvn -Prun
runs a full container
mvn -Prun -DrunType=social
runs social only
mvn -Prun -DrunType=gadgets
runs gadgets only
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms.patch, reorganize-poms2.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
Just to add, I renamed some of the final artifacts so that they
didn't loose the fact they were part of Shindig, and they didn't
loose the version number. My heart sinks when I find a jar with no
version in the name.... and no version in the manifest, fortunately
maven handles the manifest for us.
Ian
On 24 Apr 2008, at 17:43, Ian Boston (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/SHINDIG-207?
> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Ian Boston updated SHINDIG-207:
> -------------------------------
>
> Attachment: reorganize-poms.patch
>
> This patch is a reorganization of the poms. The existing build
> targets work but now the build only produces jars and wars.
>
> I have moved repos, dependencymanagement into the base pom along
> with the repos, lists, committers etc. This makes the base pom full
> and the other poms relatively empty.
>
> The dependency management will allow the versions to be set in the
> base pom, and I have added servlet api as provided, and the
> standard junit test harness as a default test dependency.
>
> there are several targets to build with
> in the base
> To build
> mvn
>
> on its own
>
> once this is done for your machine....
>
> mvn -Pgadgets
> to build only gadgets
>
> mvn -Psocial-api
> to build only the social api
>
>
> mvn -Rrun
> to run jetty.
>
>
> There were some other profiles that I havent touched, but I am not
> certain a) the purpose of them b) if they worked, eg reporting and
> release. These can be handled by the site plugin and the release
> plugin, which I will have a look at next.
>
>
>
>
>> simplify dependencies, document how to get eclipse working
>> ----------------------------------------------------------
>>
>> Key: SHINDIG-207
>> URL: https://issues.apache.org/jira/browse/
>> SHINDIG-207
>> Project: Shindig
>> Issue Type: Bug
>> Reporter: Brian Eaton
>> Attachments: build-cleanup.patch, reorganize-poms.patch
>>
>>
>> Got a patch for this.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: reorganize-poms.patch
This patch is a reorganization of the poms. The existing build targets work but now the build only produces jars and wars.
I have moved repos, dependencymanagement into the base pom along with the repos, lists, committers etc. This makes the base pom full and the other poms relatively empty.
The dependency management will allow the versions to be set in the base pom, and I have added servlet api as provided, and the standard junit test harness as a default test dependency.
there are several targets to build with
in the base
To build
mvn
on its own
once this is done for your machine....
mvn -Pgadgets
to build only gadgets
mvn -Psocial-api
to build only the social api
mvn -Rrun
to run jetty.
There were some other profiles that I havent touched, but I am not certain a) the purpose of them b) if they worked, eg reporting and release. These can be handled by the site plugin and the release plugin, which I will have a look at next.
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592945#action_12592945 ]
Brian Eaton commented on SHINDIG-207:
-------------------------------------
All looks good to me, with the exception of the Eclipse integration instructions. Those don't work. I still get errors saying "Project 'gadgets' is missing required source folder: '/home/beaton/sb/shindig/config'"
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms5.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: (was: reorganize-poms3.patch)
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms4.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: reorganize-poms5.patch
Removed the need to re-execute maven so that this should now work on Windows.
All the instructions remain the same.
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms4.patch, reorganize-poms5.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
I am not 100% certain about this
The project names in eclipse become
org.apache.shindig-shindig-commons
org.apache.shindig-social-api
org.apache.shindig-gadgets
org.apache.shindig-shindig-server
at the moment they are the artifactId's which is
shindig-commons
social-api
gadgets
shindig-server
IMHO, we might consider having artifact ID's of
shindig-commons
shindig-social-api
shindig-gadgets
shindig-server
because if you see a jar named
gadgets-0.8.jar
in a list of 100 jars, its not really clear what it is, I renamed
commons for just that reason
commons-0.8.jar
would be really confusing mixed in with other jars, commons what ?
If you want the project names as suggested I can easily put it in, I
already have the version number in, but I have moved the eclipse
plugin out of pluginManagement, because we want it in the base pom.
Ian
On 25 Apr 2008, at 14:45, Cassie Doll (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/SHINDIG-207?
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=12592378#action_12592378 ]
>
> Cassie Doll commented on SHINDIG-207:
> -------------------------------------
>
> Should this also add in Vincent's other thing:
> https://issues.apache.org/jira/browse/SHINDIG-212
>
> (or maybe it does already? still trying to wrap my head round
> everything)
>
>> simplify dependencies, document how to get eclipse working
>> ----------------------------------------------------------
>>
>> Key: SHINDIG-207
>> URL: https://issues.apache.org/jira/browse/
>> SHINDIG-207
>> Project: Shindig
>> Issue Type: Bug
>> Reporter: Brian Eaton
>> Attachments: build-cleanup.patch, reorganize-poms3.patch
>>
>>
>> Got a patch for this.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
[jira] Commented: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592378#action_12592378 ]
Cassie Doll commented on SHINDIG-207:
-------------------------------------
Should this also add in Vincent's other thing:
https://issues.apache.org/jira/browse/SHINDIG-212
(or maybe it does already? still trying to wrap my head round everything)
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms3.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: (was: reorganize-poms.patch)
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms2.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Michael I Angerman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592648#action_12592648 ]
Michael I Angerman commented on SHINDIG-207:
--------------------------------------------
Ian,
Congratulations !! It all worked as you said it would on WINDOWS...
I blew away my maven repository and started over
and pulled the latest code (revision 651956)
I patched revision 651956 with reorganize-poms5.patch...
I ran the following steps from the base directory...
mvn
mvn -Prun
The jetty server came up fine...
I tested the samples and they all came up fine...
And of course it all worked with the following maven environment variable set...
MAVEN_OPTS
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y
Excellent job,
Michael I Angerman
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms5.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Issue Comment Edited: (SHINDIG-207) simplify dependencies, document how to get eclipse working
Posted by Ian Boston <ie...@tfd.co.uk>.
Excellent news, thank you for the testing.
Ian
On 27 Apr 2008, at 15:38, Michael I Angerman (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/SHINDIG-207?
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=12592648#action_12592648 ]
>
> zroller edited comment on SHINDIG-207 at 4/27/08 7:38 AM:
> ---------------------------------------------------------------------
>
>
> Ian,
>
> Congratulations !! It all worked as you said it would on WINDOWS...
>
> I blew away my maven repository and started over
> and pulled the latest code (revision 651956)
>
> I patched revision 651956 with reorganize-poms5.patch...
>
> I ran the following steps from the base directory...
>
> mvn
> mvn -Prun
>
> The jetty server came up fine...
>
> I tested the samples and they all came up fine...
>
> And of course it all worked with the following maven environment
> variable set
>
> MAVEN_OPTS
>
> -Xdebug -Xnoagent -Djava.compiler=NONE -
> Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y
>
> And it works with no MAVEN_OPTS at all too...
>
> Excellent job,
> Michael I Angerman
>
>
> was (Author: zroller):
>
> Ian,
>
> Congratulations !! It all worked as you said it would on WINDOWS...
>
> I blew away my maven repository and started over
> and pulled the latest code (revision 651956)
>
> I patched revision 651956 with reorganize-poms5.patch...
>
> I ran the following steps from the base directory...
>
> mvn
> mvn -Prun
>
> The jetty server came up fine...
>
> I tested the samples and they all came up fine...
>
> And of course it all worked with the following maven environment
> variable set...
>
>
> MAVEN_OPTS
>
> -Xdebug -Xnoagent -Djava.compiler=NONE -
> Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y
>
> Excellent job,
> Michael I Angerman
>
>
>> simplify dependencies, document how to get eclipse working
>> ----------------------------------------------------------
>>
>> Key: SHINDIG-207
>> URL: https://issues.apache.org/jira/browse/
>> SHINDIG-207
>> Project: Shindig
>> Issue Type: Bug
>> Reporter: Brian Eaton
>> Attachments: build-cleanup.patch, reorganize-poms5.patch
>>
>>
>> Got a patch for this.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
[jira] Issue Comment Edited: (SHINDIG-207) simplify dependencies,
document how to get eclipse working
Posted by "Michael I Angerman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592648#action_12592648 ]
zroller edited comment on SHINDIG-207 at 4/27/08 7:38 AM:
---------------------------------------------------------------------
Ian,
Congratulations !! It all worked as you said it would on WINDOWS...
I blew away my maven repository and started over
and pulled the latest code (revision 651956)
I patched revision 651956 with reorganize-poms5.patch...
I ran the following steps from the base directory...
mvn
mvn -Prun
The jetty server came up fine...
I tested the samples and they all came up fine...
And of course it all worked with the following maven environment variable set
MAVEN_OPTS
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y
And it works with no MAVEN_OPTS at all too...
Excellent job,
Michael I Angerman
was (Author: zroller):
Ian,
Congratulations !! It all worked as you said it would on WINDOWS...
I blew away my maven repository and started over
and pulled the latest code (revision 651956)
I patched revision 651956 with reorganize-poms5.patch...
I ran the following steps from the base directory...
mvn
mvn -Prun
The jetty server came up fine...
I tested the samples and they all came up fine...
And of course it all worked with the following maven environment variable set...
MAVEN_OPTS
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=y
Excellent job,
Michael I Angerman
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms5.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: reorganize-poms3.patch
Updated with comments from Vincent, (thank you) all in one patch now.
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms3.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: reorganize-poms4.patch
Updated patch to include jetty version
Also changed defaultGoal to install from package.
There will be some emails following this post (or perhapse before, depending on how cleaver jira is)
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms4.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "David Primmer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591431#action_12591431 ]
David Primmer commented on SHINDIG-207:
---------------------------------------
Regarding the README, I think the debug instructions are good and workable, but the existing shindig site has developer info on how to setup eclipse and it has a pointer to basically the same info here: http://cwiki.apache.org/WICKET/maven-jetty-plugin.html. So maybe this should just an update of the shindig java developer info and pointer to it in this README? I also think the suspend=n should be explained so that people know that it will start the java server independently of any attached debugger. Some may want y (as it recommends in the above instructions) and some may want n.
Regarding moving the dependencies, and speaking only for the social-api ones, I'm not sure why you're moving stuff that is really only for social-api (abdera) to the root. It shouldn't need to be there and just introduces dependencies where there aren't any. So, yeah, move things like junit and easymock to the java root, they are global java packages for shindig, but leave caja and abdera in their respective pom's. (caja and abdera are only examples. there are others I'm sure)
davep
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: (was: reorganize-poms4.patch)
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms5.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cassie Doll resolved SHINDIG-207.
---------------------------------
Resolution: Fixed
Assignee: Cassie Doll
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Assignee: Cassie Doll
> Attachments: build-cleanup.patch, reorganize-poms5.patch, reorganize-poms6.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Vincent Siveton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592344#action_12592344 ]
Vincent Siveton commented on SHINDIG-207:
-----------------------------------------
Forgot to mention that a prerequisite for Maven is missing, at least for 2.0.4.
{noformat}
<project ...>
...
<prerequisites>
<maven>2.0.4</maven>
</prerequisites>
...
</project>
{noformat}
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, pom-reord-README.patch, reorganize-poms2.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SHINDIG-207:
-------------------------------
Attachment: (was: pom-reord-README.patch)
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms3.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-207) simplify dependencies, document how
to get eclipse working
Posted by "Vincent Siveton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592388#action_12592388 ]
Vincent Siveton commented on SHINDIG-207:
-----------------------------------------
Cassie, it is two distinct patches but I guess you could easily merge them in /trunk/pom.xml
> simplify dependencies, document how to get eclipse working
> ----------------------------------------------------------
>
> Key: SHINDIG-207
> URL: https://issues.apache.org/jira/browse/SHINDIG-207
> Project: Shindig
> Issue Type: Bug
> Reporter: Brian Eaton
> Attachments: build-cleanup.patch, reorganize-poms3.patch
>
>
> Got a patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.