We recently started including m2e v1.0 in our Eclipse distribution
that we put out. A full run of our tests used to take about 2 hours.
Now, with the new version of m2e, they are taking over 4 hours (and
many of our tests are timing out before succeeding.
Our headless build uses Tycho. And in our
STS (SpringSource Tool Suite) is moving from m2eclipse to m2e as of
version 2.8.0, which is due out in a few weeks. We expect that this
will cause some major confusion for our users, many of whom have
multiple maven projects in their workspace. Manually upgrading a
single project is not a problem
se 0.12 and earlier to m2e 1.0.
>
> --
> Regards,
> Igor
>
> On 11-10-05 1:57 PM, Andrew Eisenberg wrote:
>>
>> STS (SpringSource Tool Suite) is moving from m2eclipse to m2e as of
>> version 2.8.0, which is due out in a few weeks. We expect that this
>> w
I would be surprised if this problem has anything to do with STS, but
you never know and it would be good to try to reproduce the problem in
a vanilla Eclipse install. FWIW, I tried to naively reproduce
jacquie's bug using this simple pom file, but could not.
It would be very helpful if you could
Hi all,
I'm working through this issue and have hit a bit of a wall.
https://jira.codehaus.org/browse/GRECLIPSE-1372
I'm hoping that someone familier with WTP's M2E integration can help me
further.
When scanning a classpath, WTP is including test classes in the
deployed application. This only h
e.eclipse.wtp/src/org/maven/ide/eclipse/wtp/WTPProjectsUtil.java#L492
>
> HIH
>
> Fred Bricon
>
> On Thu, Mar 8, 2012 at 12:51 AM, Andrew Eisenberg
> wrote:
>>
>> Hi all,
>>
>> I'm working through this issue and have hit a bit of a wall.
>> ht
gt; As long as you're patch doesn't have groovy stuff hardcoded everywhere,
>> please be my guest :-)
>>
>> Fred Bricon
>>
>>
>> On Thu, Mar 8, 2012 at 1:19 AM, Andrew Eisenberg
>> wrote:
>>>
>>> Hi Fred,
>>>
>>>
You need to install the AspectJ project configurator in order for your
aspectj projects to work from inside of Eclipse. Go to Preferences ->
Maven -> Discovery and find the aspectj configurator. Install and
restart. Then try updating configuration again.again.
On Fri, Mar 30, 2012 at 8:07 AM, H
The project configurator needs to inject extra dependencies into a
project so that when it delegates to the maven plugin for execution
these dependencies are included.
More precisely, there is a maven extension
http://maven.apache.org/guides/mini/guide-using-extensions.html that
injects things dur
Great work!
Some questions:
* Do we have to do anything to make sure our old configurators remain
available?
* Will old configurators automatically be available for both m2e 1.0 and 1.1?
* What happens if you have different versions of your configurator
that is only installable on either juno or
t; execute them before delegating to m2e default dependency resolution
> logic. Beware that I have not actually tried this, so m2e may need some
> fixing to make this work.
>
> --
> Regards,
> Igor
>
>
> On 12-06-08 12:05 PM, Andrew Eisenberg wrote:
>>
>> T
Thanks Pascal. This looks excellent! I'll hope to try it out next week.
On Mon, Aug 6, 2012 at 12:36 PM, Pascal Rapicault wrote:
> I considered this option, however as soon as you start editing parent poms,
> you end up having to switch back and forth between pom editors to see the
> result of
s and other
> improvements [1]. Big thank you goes to Andrew Eisenberg for driving
> implementation of workspace lifecycle mapping.
>
> The new release is already available from p2 repository specified m2e
> download page [2] and Eclipse Marketplace. It will also become available
> as par
I suspect that the problem is related to your install from Ubuntu.
More than likely, the version you installed doesn't have the correct
update sites pre-configured. The distributions from Ubuntu are always
slightly different than what you get at eclipse.org. And this causes
all sorts of subtle up
M2e 1.2 now supports placing your lifecycle mapping metadata in a
global location so that it doesn't need to pollute individual project
poms. This at least addresses one of your original concerns. To do
this, there is now a second quickfix in your pom editor to handle
lifecycle mapping metadata m
Hey,
The AJDT guy here (piping in a bit late). I have never tried AspectJ
in Tycho before. I am guessing that we need to update the ajdt
configurator to get this working properly. I think the ajdt
configurator would be specific to the regular maven-compiler-plugin.
I need to have a look to make
Hi Igor,
David has already raised 2 bugs with us
https://issuetracker.springsource.com/browse/STS-3481 and
https://issuetracker.springsource.com/browse/STS-3482. There is
nothing to suggest that this is coming from STS. But, I will give
some suggestions on how to fix these.
David,
It may be that
One of the benefits of downloading a pre-packaged distro is that all
the pieces you need come pre-installed. I'm guessing that one of the
update sites you used before grabbed some Juno-based plugins.
This latest problem is likely because you didn't install the Spring
IDE AJDT integration and the S
to:m2e-users-boun...@eclipse.org] On
>> Behalf Of Andrew Eisenberg
>> Sent: Friday, July 19, 2013 11:44 AM
>> To: Maven Integration for Eclipse users mailing list
>> Subject: Re: [m2e-users] After STS 3.3.0 (Kepler), getting two different very
>> annoying exception
On Wed, Oct 2, 2013 at 10:41 AM, Cristiano Gavião wrote:
> But besides the good fact that the wizard now suggest and mark the
> checkbox for a working set name every time you import an aggregator
> project, I still prefer the old one that give us the possibility to choose
> an existent working set
20 matches
Mail list logo
