| Maven and Eclipse [message #329364] |
Sat, 21 June 2008 02:47  |
Eclipse User |
|
|
|
Originally posted by: raghuraman1.yahoo.com
Hi,
Is it not about time Eclipse Plugin developers were able to use maven.
When can we have eclipse plugins that use the maven 2 repository?
This would reduce the download size of the plugins too.
Can eclipse OSGI work with the Maven 2 repo?
Raghu
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Maven and Eclipse [message #329387 is a reply to message #329382] |
Sun, 22 June 2008 12:06  |
| Eclipse User |
|
|
|
Originally posted by: cold.phusion.gmail.com
Raghu,
I think you misunderstood the purpose of Maven. It is not a dependency
management tool - it is a >>build<< management tool with integrated
dependency repository. There is a big difference - you don't need Maven
to run your application, only to build it, right? So how do you expect
it to download the dependencies at runtime if the end user doesn't have
it installed?
When Maven builds an application, it includes every single dependency in
the final bundle - so whether you manually add your JARs to /lib or let
Maven do it for you, doesn't really matter (size-wise).
You are right, though, that when it comes to external libraries, the
Eclipse RCP environment has very poor options. Actually only one -
include all libraries as JAR bundles as Runtime Dependencies. There are
no options for resolving transitive dependencies, automated fetching of
dependency repositories (not only for external libraries but also for
Eclipse plugins), etc - as in comparisson to Maven (again only for
building), the Ports in *BSD and technically every good package manager.
And I do agree, that this topic deserves attention :)
Cheerz,
Alex
Raghu schrieb:
> I am not requesting anyone to drop any part of eclipse. Anyways the
> change needs to happen from all players for the overall benefit of Java.
> Eclipse is one of the players. Maven might have joined the party a bit
> later. But it is an opportunity. Hopefully we don't miss the bus. Of
> course these are just my personal views am someone who remains a fan of
> eclipse.
>
> If the industry were to use the maven repository more the following
> benefits will lead to more efficient, effective tools and project life
> cycles. It all depends on whether we think these are real benefits in
> the long run or not.
> 1. We could have smaller downloads for eclipse and application servers
> themselves. (a minor benefit)
>
> 2. And if this were to happen consequently additional jars referred to
> by applications will not need to be packaged and pushed into servers as
> part of build and release or WTP builds/deploys for ears or wars.
> Admittedly this impacts J2ee.
>
> 3. But if we get our acts together and do this its worth-wile because
> each enabling product we use for development be it eclipse, WTP or maven
> will consequently being doing less work and hence be performing even
> faster with less overhead because most of the jars will simply remain in
> one place - the local maven repository.
> (A major benefit[I repeat myself]: any build deploy tool eg Ant, Maven
> including WTP for Rapid build and deploy and debug is to a large part
> currently copying third party jars from one location to another and then
> assembling them alongwith other code and then pushing all this into the
> server and consuming CPU. A small change in J2EE classpath approach and
> we can all get more productive.)
>
> No?
>
|
|
|
|
|
| Re: Maven and Eclipse [message #329393 is a reply to message #329389] |
Sun, 22 June 2008 20:29 |
| Eclipse User |
|
|
|
"Raghu" <raghuraman1@yahoo.com> wrote in message
news:479f049b0f7e89fa9e82fd9b5951008a$1@www.eclipse.org...
> And when you package an application as an ear or a war why can you not
> just have a "link" to the jars contained inside the ear or inside the
> war's WEB-INF/lib folder instead of the jars being physically being
> present there. Because the ear and war is supposed to be self contained
> and because we so far did not have a standard location to locate jars does
> not mean we should continue to do so.
>
> I am hoping with a small tweak in JEE class path resolution for ears and
> wars the applications can be built without all that copying and pushing of
> the jars and ultmately into the server.
Raghu, I'm feeling confused about what it is you are asking for.
If you're talking about something that would affect the behavior of JEE
applications written with Eclipse, I don't understand why you're posting
this to eclipse.platform, nor why you're suggesting that Eclipse plugins
should be built this way (since they are not JEE apps).
If you're talking about something that would affect the runtime behavior of
the Eclipse platform, I don't understand why you're talking about ears and
wars, and I don't understand what runtime behavior has to do with Maven.
If you're talking about using Maven to manage build dependencies in the
Eclipse project, I don't understand how that would interact with OSGi and
PDE, nor what the benefit would be except to help popularize Maven; and I
don't see why we would want to add another external technology dependency to
the Eclipse build process.
So I feel like I'm still missing your point. Sorry if I'm being obtuse, but
looking over the thread I think I might not be the only one who'se having
difficulty following you. Can you clarify exactly what your proposal is,
what aspects of Eclipse would be affected, what work you think is entailed,
and who should be doing it?
|
|
|
| Re: Maven and Eclipse [message #329395 is a reply to message #329393] |
Mon, 23 June 2008 00:15 |
| Eclipse User |
|
|
|
Originally posted by: raghuraman1.yahoo.com
Right, I use eclipse and Maven and like both. I find its a bit difficult
to use the combination. There are some efforts to smooth all of this. But
they dont yet integrate as well as say Ant does with Eclipse. Things are
getting better. Yes.
But I felt that there is room for improvement. This is obviously limited
due to budgeting as pointed out by you.
I added a wild thought (for a carrot) that if we really embrace it more we
can also use it for runtime jars and not just a build tool and thereby get
more efficient tools and build processes. That however may be science
fiction till every player in Java [read - IDEs, App Servers] thinks the
same. I also pointed out that if this thought were to become a reality
tools like WTP will have a easier job publishing the ears and wars into
the servers because the contained jars will really be sitting just in one
place and not being pushed around. But thats not how I started this
discussion. You are right I should just limit it to saying that I wish
Maven and Eclipse were better integrated. This is after all a eclipse
forum.
|
|
|
Powered by
FUDForum. Page generated in 0.04203 seconds
Home