are you sure about this? i did never personally experience, and never
heard that somebody had to add e.g. jsse.jar to the classpath, if it
is in the jre/lib.
-solo.
On 8/9/05, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
> On Tue, 9 Aug 2005, solo turn wrote:
>
> It's missing from the eclipse plu
On Tue, 9 Aug 2005, Thomas Van de Velde wrote:
It already does in svn. It'll make dependencies on eclipse projects
rather than on the jars. This will be available in beta-1.
It can also create the project structure someplace else, using
links to the sources/resources, so nesting projects is no lo
Kenney,
Will the M2 Eclipse plugin support the generation of a .classpath for
multiprojects?
T
On 8/9/05, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
>
> On Tue, 9 Aug 2005, solo turn wrote:
>
> It's missing from the eclipse plugin. I've been meaning to change that,
> but from what I could
On Tue, 9 Aug 2005, solo turn wrote:
It's missing from the eclipse plugin. I've been meaning to change that,
but from what I could see there was some path/jdk specific content in the
3.0 version. Can't find any reason not to change this for 3.1 though,
besides the fact that per default java apps d
running "m2 eclipse:eclipse" adds just rt.jar to the java build path,
while creating a project with eclipse 3.1 adds:
i'd prefer if the whole java libraries are added like eclipse does it.
do i have to set this somewhere in the pom, or is it just a thing
which is missing in the eclipse goal?
-so
