You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by solo turn <so...@gmail.com> on 2005/08/09 18:21:33 UTC
[m2] alpha-3, eclipse java build path
running "m2 eclipse:eclipse" adds just rt.jar to the java build path,
while creating a project with eclipse 3.1 adds:
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
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?
-solo.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m2] alpha-3, eclipse java build path
Posted by Kenney Westerhof <fo...@neonics.com>.
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 longer
an issue.
-- Kenney
> Kenney,
> Will the M2 Eclipse plugin support the generation of a .classpath for
> multiprojects?
> T
>
> On 8/9/05, Kenney Westerhof <ke...@apache.org> 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 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 don't get anything but
> > a rt.jar when run in a JRE. You can't be sure that the app is run from
> > within a full JDK.
> >
> > > running "m2 eclipse:eclipse" adds just rt.jar to the java build path,
> > > while creating a project with eclipse 3.1 adds:
> > > <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER
> > "/>
> > >
> > > 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?
> > >
> > > -solo.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> > --
> > Kenney Westerhof
> > http://www.neonics.com
> > GPG public key: http://www.gods.nl/~forge/kenneyw.key
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m2] alpha-3, eclipse java build path
Posted by Thomas Van de Velde <th...@gmail.com>.
Kenney,
Will the M2 Eclipse plugin support the generation of a .classpath for
multiprojects?
T
On 8/9/05, Kenney Westerhof <ke...@apache.org> 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 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 don't get anything but
> a rt.jar when run in a JRE. You can't be sure that the app is run from
> within a full JDK.
>
> > running "m2 eclipse:eclipse" adds just rt.jar to the java build path,
> > while creating a project with eclipse 3.1 adds:
> > <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER
> "/>
> >
> > 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?
> >
> > -solo.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> --
> Kenney Westerhof
> http://www.neonics.com
> GPG public key: http://www.gods.nl/~forge/kenneyw.key
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [m2] alpha-3, eclipse java build path
Posted by solo turn <so...@gmail.com>.
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 <ke...@apache.org> 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 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 don't get anything but
> a rt.jar when run in a JRE. You can't be sure that the app is run from
> within a full JDK.
>
> > running "m2 eclipse:eclipse" adds just rt.jar to the java build path,
> > while creating a project with eclipse 3.1 adds:
> > <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> >
> > 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?
> >
> > -solo.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> --
> Kenney Westerhof
> http://www.neonics.com
> GPG public key: http://www.gods.nl/~forge/kenneyw.key
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m2] alpha-3, eclipse java build path
Posted by Kenney Westerhof <ke...@apache.org>.
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 don't get anything but
a rt.jar when run in a JRE. You can't be sure that the app is run from
within a full JDK.
> running "m2 eclipse:eclipse" adds just rt.jar to the java build path,
> while creating a project with eclipse 3.1 adds:
> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>
> 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?
>
> -solo.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org