I could not reproduce the problem with 4.3 standard with m2e 1.4 install
on top of it. No need to retry with "for java".
I don't really have much to add here though. There is something special
about your environment, see if the you can reproduce the issue on
another system (new virtual machine, for example). If still can't
explain the problem, you'd need to debug m2e.
--
Regards,
Igor
On 2013-07-23 9:58 PM, Mike Grandmaison wrote:
> Trying again...
I downloaded the Eclipse Standard 4.3 then added m2e
> and it had the same behavior. Just re-read your message so now I am
> downloading the "for java developers" edition.
> MG.
> *From:* Igor Fedorenko <
igor@xxxxxxxxxxxxxx>
> *To:* Mike Grandmaison <
java97301@xxxxxxxxx>
> *Cc:* Maven Integration for Eclipse users mailing list
> <
m2e-users@xxxxxxxxxxx>
> *Sent:* Tuesday, July 23, 2013 9:36 AM
> *Subject:* Re: [m2e-users] manual source location for jar resource m2e
>
> The steps work just fine with the provided example for me. I tried
> several transitions between workspace, external and m2e-provided source
> paths,
update project configuration, and in all cases sourcepath was as
> expected.
>
> Can you confirm you can reproduce the problem with fresh clean install
> of Kepler "for java developers" obtained from download.eclipse.org? I
> specifically want to eliminate m2e-wtp and thirdparty eclipse plugins as
> the cause of the problem.
>
> --
> Regards,
> Igor
>
> On 2013-07-23 7:51 PM, Mike Grandmaison wrote:
> >
> > Go into the package explorer. Right Click (RC)
> > logback-classic-0.9.28.jar, choose properties. Choose java source
> > attachment, external location. This location is currently marked with
> > the maven source download. Copy the maven source jar file to a
> > different location and change this location to match by clicking
> > external file and
selecting the jar at the different location. Click
> > apply, click ok. RC logback-classic-0.9.28.jar, choose properties.
> > Notice that the change did not persist.
> >
> > If you have problems with the steps I could provide a video.
> >
> > Thanks for all the great work on m2e !!!!
> >
> > ------------------------------------------------------------------------
> > *From:* Igor Fedorenko <
igor@xxxxxxxxxxxxxx <mailto:
igor@xxxxxxxxxxxxxx>>
> > *To:* Mike Grandmaison <
java97301@xxxxxxxxx> <mailto:
java97301@xxxxxxxxx>>; Maven Integration for
> > Eclipse users mailing list <
m2e-users@xxxxxxxxxxx> <mailto:
m2e-users@xxxxxxxxxxx>>
> > *Sent:* Monday, July 22, 2013 10:42 PM
> > *Subject:* Re: [m2e-users] manual source location for jar resource m2e
> >
> > m2e is expected to preserve manually configured source path. Please
> > provide a small standalone example and exact steps to reproduce the
> > problem and we'll have a look.
> > --
> > Sent from my SGS
> >
> > Mike Grandmaison <
java97301@xxxxxxxxx <mailto:
java97301@xxxxxxxxx>
> <mailto:
java97301@xxxxxxxxx <mailto:
java97301@xxxxxxxxx>>> wrote:
> > >I am using eclipse (20130225-0426) with m2e 1.4.0-...-0317.
> > >
> > >I
> > >can't seem to attach a source location to a maven managed dependency.
> > >The source for this maven dependency exists as a project within my
> > >eclipse workspace. I am able to click edit and browse to the location
> > >but the change never persists. Is this a known issue. Is
there an
> > >easy
> > >fix for it apart from updating the maven repo to include the source for
> > > this library and having maven auto download the source?
> > >
> > >Thank you,
> > >
> > >MG
> > >
> >
> >------------------------------------------------------------------------
> > >
> > >_______________________________________________
> > >m2e-users mailing list
> > >
m2e-users@xxxxxxxxxxx <mailto:
m2e-users@xxxxxxxxxxx>
> <mailto:
m2e-users@xxxxxxxxxxx <mailto:
m2e-users@xxxxxxxxxxx>>
> > >
https://dev.eclipse.org/mailman/listinfo/m2e-users> >
> >
> >
>
>
