Work with dwr and eclipse

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Work with dwr and eclipse

fjarenales
Hi folks, I'd like to work with dwr source code in Eclipse but I don't know exactly the lib it uses. Researching about it I was able to solve most of the compilation errors. I add the following jar files to my eclipse project: * itext. * jakarta-oro * log4j * commons-io * commons-fileupload * commons-logging * dwr * dom4j * jdom * bsf * webwork * xwork * xwork-sources * xwork-core. I get the next compilation error: "The type com.opensymphony.xwork.ActionContext cannot be resolved. It is indirectly referenced from required .class files DWRAction.java /dwr-v3.0/src/org/directwebremoting/webwork". I'm not sure if that is due to using wrong libraries. Could you give me a hand with this? Thanks and regards!! Javier
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Work with dwr and eclipse

david@butterdev.com
Eclipse .project and .classpath files existing in SVN. 

On 12/30/2011 01:18 AM, fjarenales wrote:
Hi folks, I'd like to work with dwr source code in Eclipse but I don't know exactly the lib it uses. Researching about it I was able to solve most of the compilation errors. I add the following jar files to my eclipse project: * itext. * jakarta-oro * log4j * commons-io * commons-fileupload * commons-logging * dwr * dom4j * jdom * bsf * webwork * xwork * xwork-sources * xwork-core. I get the next compilation error: "The type com.opensymphony.xwork.ActionContext cannot be resolved. It is indirectly referenced from required .class files DWRAction.java /dwr-v3.0/src/org/directwebremoting/webwork". I'm not sure if that is due to using wrong libraries. Could you give me a hand with this? Thanks and regards!! Javier

View this message in context: Work with dwr and eclipse
Sent from the DWR - Users mailing list archive at Nabble.com.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Work with dwr and eclipse

Darrell Esau
In reply to this post by fjarenales

Use File/Import, then select "Existing Project".  Point to the dwr root.

-d

On Dec 30, 2011 3:18 AM, "fjarenales" <[hidden email]> wrote:
Hi folks, I'd like to work with dwr source code in Eclipse but I don't know exactly the lib it uses. Researching about it I was able to solve most of the compilation errors. I add the following jar files to my eclipse project: * itext. * jakarta-oro * log4j * commons-io * commons-fileupload * commons-logging * dwr * dom4j * jdom * bsf * webwork * xwork * xwork-sources * xwork-core. I get the next compilation error: "The type com.opensymphony.xwork.ActionContext cannot be resolved. It is indirectly referenced from required .class files DWRAction.java /dwr-v3.0/src/org/directwebremoting/webwork". I'm not sure if that is due to using wrong libraries. Could you give me a hand with this? Thanks and regards!! Javier

View this message in context: Work with dwr and eclipse
Sent from the DWR - Users mailing list archive at Nabble.com.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Work with dwr and eclipse

ole ersoy
Check out the dwr maven trunk.  Then run mvn eclipse:eclipse on the trunk.  This will resolve all dependencies.  Then just import the trunk using eclipse.  The "eclipse:eclipse" plugin creates the necessary eclipse project files, so all you need to do is import the project.

On 12/30/2011 09:33 AM, Darrell Esau wrote:
> Use File/Import, then select "Existing Project".  Point to the dwr root.
>
> -d
>
> On Dec 30, 2011 3:18 AM, "fjarenales" <[hidden email] <mailto:[hidden email]>> wrote:
>
>     Hi folks, I'd like to work with dwr source code in Eclipse but I don't know exactly the lib it uses. Researching about it I was able to solve most of the compilation errors. I add the following jar files to my eclipse project: * itext. * jakarta-oro * log4j * commons-io * commons-fileupload * commons-logging * dwr * dom4j * jdom * bsf * webwork * xwork * xwork-sources * xwork-core. I get the next compilation error: "The type com.opensymphony.xwork.ActionContext cannot be resolved. It is indirectly referenced from required .class files DWRAction.java /dwr-v3.0/src/org/directwebremoting/webwork". I'm not sure if that is due to using wrong libraries. Could you give me a hand with this? Thanks and regards!! Javier
>     ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
------
>     View this message in context: Work with dwr and eclipse <http://dwr.2114559.n2.nabble.com/Work-with-dwr-and-eclipse-tp7137598p7137598.html>
>     Sent from the DWR - Users mailing list archive <http://dwr.2114559.n2.nabble.com/DWR-Users-f2114559.html> at Nabble.com.
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Work with dwr and eclipse

david@butterdev.com
I do not recommend building or using Maven to set-up your project.  We
don't build with Maven and the Maven build has always been
experimental.  One reason why we have been experimenting with Maven was
because we thought it would make the process of releasing our artifacts
into Maven central much easier.  Recently, I have found a way to release
our artifacts into Maven central and still use our Ant build process.  
Because of this and to avoid further confusion I will be removing the
poms (except the main pom which is required for releases) from
Subversion in the near future.

I like Maven, I just don't think it makes sense for us to spend time
working on and maintaining two build processes (Ant and Maven).  We have
a perfectly fine build process with Ant and our project is so small that
managing the dependencies is not an issue.

If we ever start up a DWR 4.0 project we will start off with a Maven build.

-David

On 12/30/2011 06:19 PM, Ole Ersoy wrote:

> Check out the dwr maven trunk.  Then run mvn eclipse:eclipse on the
> trunk.  This will resolve all dependencies.  Then just import the
> trunk using eclipse.  The "eclipse:eclipse" plugin creates the
> necessary eclipse project files, so all you need to do is import the
> project.
>
> On 12/30/2011 09:33 AM, Darrell Esau wrote:
>> Use File/Import, then select "Existing Project".  Point to the dwr root.
>>
>> -d
>>
>> On Dec 30, 2011 3:18 AM, "fjarenales" <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>>     Hi folks, I'd like to work with dwr source code in Eclipse but I
>> don't know exactly the lib it uses. Researching about it I was able
>> to solve most of the compilation errors. I add the following jar
>> files to my eclipse project: * itext. * jakarta-oro * log4j *
>> commons-io * commons-fileupload * commons-logging * dwr * dom4j *
>> jdom * bsf * webwork * xwork * xwork-sources * xwork-core. I get the
>> next compilation error: "The type
>> com.opensymphony.xwork.ActionContext cannot be resolved. It is
>> indirectly referenced from required .class files DWRAction.java
>> /dwr-v3.0/src/org/directwebremoting/webwork". I'm not sure if that is
>> due to using wrong libraries. Could you give me a hand with this?
>> Thanks and regards!! Javier
>>    
>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ------
>>     View this message in context: Work with dwr and eclipse
>> <http://dwr.2114559.n2.nabble.com/Work-with-dwr-and-eclipse-tp7137598p7137598.html>
>>     Sent from the DWR - Users mailing list archive
>> <http://dwr.2114559.n2.nabble.com/DWR-Users-f2114559.html> at
>> Nabble.com.
>>
>


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Work with dwr and eclipse

ole ersoy
Once the maven build is modified will it still be possible to use maven to build DWR?  I usually work against the trunk and the maven build takes care of installing dependencies into my local maven repository, setting up my eclipse project, etc. so I'm wondering whether all these "Simplicities" will go away?

Ole  

On 12/30/2011 08:57 PM, David Marginian wrote:

> I do not recommend building or using Maven to set-up your project. We don't build with Maven and the Maven build has always been experimental. One reason why we have been experimenting with Maven was because we thought it would make the process of releasing our artifacts into Maven central much easier. Recently, I have found a way to release our artifacts into Maven central and still use our Ant build process. Because of this and to avoid further confusion I will be removing the poms (except the main pom which is required for releases) from Subversion in the near future.
>
> I like Maven, I just don't think it makes sense for us to spend time working on and maintaining two build processes (Ant and Maven). We have a perfectly fine build process with Ant and our project is so small that managing the dependencies is not an issue.
>
> If we ever start up a DWR 4.0 project we will start off with a Maven build.
>
> -David
>
> On 12/30/2011 06:19 PM, Ole Ersoy wrote:
>> Check out the dwr maven trunk. Then run mvn eclipse:eclipse on the trunk. This will resolve all dependencies. Then just import the trunk using eclipse. The "eclipse:eclipse" plugin creates the necessary eclipse project files, so all you need to do is import the project.
>>
>> On 12/30/2011 09:33 AM, Darrell Esau wrote:
>>> Use File/Import, then select "Existing Project". Point to the dwr root.
>>>
>>> -d
>>>
>>> On Dec 30, 2011 3:18 AM, "fjarenales" <[hidden email] <mailto:[hidden email]>> wrote:
>>>
>>> Hi folks, I'd like to work with dwr source code in Eclipse but I don't know exactly the lib it uses. Researching about it I was able to solve most of the compilation errors. I add the following jar files to my eclipse project: * itext. * jakarta-oro * log4j * commons-io * commons-fileupload * commons-logging * dwr * dom4j * jdom * bsf * webwork * xwork * xwork-sources * xwork-core. I get the next compilation error: "The type com.opensymphony.xwork.ActionContext cannot be resolved. It is indirectly referenced from required .class files DWRAction.java /dwr-v3.0/src/org/directwebremoting/webwork". I'm not sure if that is due to using wrong libraries. Could you give me a hand with this? Thanks and regards!! Javier
>>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>> ------
>>> View this message in context: Work with dwr and eclipse <http://dwr.2114559.n2.nabble.com/Work-with-dwr-and-eclipse-tp7137598p7137598.html>
>>> Sent from the DWR - Users mailing list archive <http://dwr.2114559.n2.nabble.com/DWR-Users-f2114559.html> at Nabble.com.
>>>
>>
>
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Work with dwr and eclipse

david@butterdev.com
No, you will not be able to use Maven.  I am sorry if I wasn't clear in
my email.  I am removing the Maven build process - all poms except the
main pom which is required for getting releases into Maven central will
be removed.

If you have the DWR source you have all of the dependencies as they are
checked into SVN.  You also have the .classpath and .project files which
you can easily import and have a complete working project set-up.  So
building with Maven results in you having two copies of all the
dependencies (local Maven Repo and DWR source tree).  It also requires
one more step for creating/importing your projects - running mvn
eclipse:eclipse.  It seems to me that the Ant process is actually
easier.  Can you please provide more information on what you will be
missing?

Also, you can always keep the poms and still use them we are just not
going to maintain them.  That is why I want to remove them from SVN.  I
don't want to confuse or mislead people into thinking that we  build
with and maintain the Maven build process.



On 12/31/2011 09:59 AM, Ole Ersoy wrote:

> Once the maven build is modified will it still be possible to use
> maven to build DWR?  I usually work against the trunk and the maven
> build takes care of installing dependencies into my local maven
> repository, setting up my eclipse project, etc. so I'm wondering
> whether all these "Simplicities" will go away?
>
> Ole
> On 12/30/2011 08:57 PM, David Marginian wrote:
>> I do not recommend building or using Maven to set-up your project. We
>> don't build with Maven and the Maven build has always been
>> experimental. One reason why we have been experimenting with Maven
>> was because we thought it would make the process of releasing our
>> artifacts into Maven central much easier. Recently, I have found a
>> way to release our artifacts into Maven central and still use our Ant
>> build process. Because of this and to avoid further confusion I will
>> be removing the poms (except the main pom which is required for
>> releases) from Subversion in the near future.
>>
>> I like Maven, I just don't think it makes sense for us to spend time
>> working on and maintaining two build processes (Ant and Maven). We
>> have a perfectly fine build process with Ant and our project is so
>> small that managing the dependencies is not an issue.
>>
>> If we ever start up a DWR 4.0 project we will start off with a Maven
>> build.
>>
>> -David
>>
>> On 12/30/2011 06:19 PM, Ole Ersoy wrote:
>>> Check out the dwr maven trunk. Then run mvn eclipse:eclipse on the
>>> trunk. This will resolve all dependencies. Then just import the
>>> trunk using eclipse. The "eclipse:eclipse" plugin creates the
>>> necessary eclipse project files, so all you need to do is import the
>>> project.
>>>
>>> On 12/30/2011 09:33 AM, Darrell Esau wrote:
>>>> Use File/Import, then select "Existing Project". Point to the dwr
>>>> root.
>>>>
>>>> -d
>>>>
>>>> On Dec 30, 2011 3:18 AM, "fjarenales" <[hidden email]
>>>> <mailto:[hidden email]>> wrote:
>>>>
>>>> Hi folks, I'd like to work with dwr source code in Eclipse but I
>>>> don't know exactly the lib it uses. Researching about it I was able
>>>> to solve most of the compilation errors. I add the following jar
>>>> files to my eclipse project: * itext. * jakarta-oro * log4j *
>>>> commons-io * commons-fileupload * commons-logging * dwr * dom4j *
>>>> jdom * bsf * webwork * xwork * xwork-sources * xwork-core. I get
>>>> the next compilation error: "The type
>>>> com.opensymphony.xwork.ActionContext cannot be resolved. It is
>>>> indirectly referenced from required .class files DWRAction.java
>>>> /dwr-v3.0/src/org/directwebremoting/webwork". I'm not sure if that
>>>> is due to using wrong libraries. Could you give me a hand with
>>>> this? Thanks and regards!! Javier
>>>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>>
>>> ------
>>>> View this message in context: Work with dwr and eclipse
>>>> <http://dwr.2114559.n2.nabble.com/Work-with-dwr-and-eclipse-tp7137598p7137598.html>
>>>> Sent from the DWR - Users mailing list archive
>>>> <http://dwr.2114559.n2.nabble.com/DWR-Users-f2114559.html> at
>>>> Nabble.com.
>>>>
>>>
>>
>>
>>
>


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Work with dwr and eclipse

ole ersoy
When I run the maven build it produces and installs all the dependencies I need like:

                <dependency>
                        <groupId>org.directwebremoting</groupId>
                        <artifactId>dwr-ui-dojo</artifactId>
                        <version>3.0.0-rc3-SNAPSHOT</version>
                        <type>jar</type>
                        <scope>compile</scope>
                </dependency>

....

My maven web-app projects then pull these and indirect dependencies from my local repository and include them in my war files.  If the maven build is no longer maintained, then it seems like all dependencies will have to be manually installed (At least when working with the trunk)?

Ole
   


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Work with dwr and eclipse

david@butterdev.com
The ant build is not componentized so you will only need one jar -
dwr.jar.  So you can either build dwr.jar and install it into your local
maven repo or when DWR RC2 is released it will be in Maven central so
you can pull it from there.  As I said you can always keep the poms and
do your own thing - we will just not maintain them and they will not be
in our source tree.

Please note the reason why I am doing this is because our Maven builds
are not 100% complete.  They may be around 80-90% complete.  Getting the
next 10-20% requires a lot of fiddling and time.  If they were 100% I
would be getting rid of the Ant build and keeping Maven.  I just can't
justify spending the time getting the next 10-20% when we have a
perfectly fine build process with Ant and have issues to work.

On 12/31/2011 11:04 AM, Ole Ersoy wrote:

> When I run the maven build it produces and installs all the
> dependencies I need like:
>
> <dependency>
> <groupId>org.directwebremoting</groupId>
> <artifactId>dwr-ui-dojo</artifactId>
> <version>3.0.0-rc3-SNAPSHOT</version>
> <type>jar</type>
> <scope>compile</scope>
> </dependency>
>
> ....
>
> My maven web-app projects then pull these and indirect dependencies
> from my local repository and include them in my war files.  If the
> maven build is no longer maintained, then it seems like all
> dependencies will have to be manually installed (At least when working
> with the trunk)?
>
> Ole
>
>
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Work with dwr and eclipse

ole ersoy
I'm assuming all the dependencies are included in the one jar?  The only drawback I see to that is that now there is most likely duplication on my classpath, as maven will pull in dependencies that might already be included in the dwr jar.

What is the 10-20% that's missing?  I'm hoping I'll be able to plug the gap.

Happy New Year!!
- Ole
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Work with dwr and eclipse

david@butterdev.com
No, the dwr.jar only includes dwr classes and configuration files.  As
far as runtime dependencies, the only one we have is commons-logging
(assuming you aren't using integrating with Spring, Hibernate, etc.,
those dependencies will be required by your application anyway).  There
will be no duplication on your classpath.

As far as the 10-20% that is missing - I don't have a solid list.  A few
things don't work in the demo, I can't get the release stuff working
(which is odd since it was easy to set this up in Ant), etc.  I know
there is more and there is also more that we would find that I am not
currently aware of.

I really appreciate your offer to help but I would rather you help out
with other things :).

Happy New Year

On 12/31/2011 04:37 PM, Ole Ersoy wrote:

> I'm assuming all the dependencies are included in the one jar?  The
> only drawback I see to that is that now there is most likely
> duplication on my classpath, as maven will pull in dependencies that
> might already be included in the dwr jar.
>
> What is the 10-20% that's missing?  I'm hoping I'll be able to plug
> the gap.
>
> Happy New Year!!
> - Ole
>

Loading...