Hello,
You can also try to specify your jre/jdk6 as J2SE-1.2 Execution Environment
(Preferences - Java - Installed JREs - Execution Environments).
I guess your eclipse actually picks jdk6 automatically, unless you have a
separate 1.2 version of java configured on Installed JREs page.
On Tue, Aug
Hi,
There's a small problem with Import Maven Project action when using
[groupId], [artifactId] and/or [version] project name templates for
projects that have property placeholders withing respective values.
ProjectImportConfiguration#getProjectName() uses those values as a
replacement value for S
> --
> Regards,
> Igor
>
>
> On 2014-03-29, 11:22, Anton Tanasenko wrote:
>
>> Hi,
>>
>> There's a small problem with Import Maven Project action when using
>> [groupId], [artifactId] and/or [version] project name templates for
>> projects that
rarely used within
eclipse, it is for headless jenkins build.
On Sat, Mar 29, 2014 at 5:49 PM, Anton Tanasenko wrote:
> Well, actually, I thought about making it to treat placeholders as plain
> text or maybe event better ignoring them completely.
> At the moment import just fails with an
Hi,
Should I create an issue, or just submit a patch to gerrit without one?
On Sat, Mar 29, 2014 at 5:55 PM, Anton Tanasenko wrote:
> Oh and I mean that only in the context of project name template. I do
> understand that this might cause troubles or at least inconsistencies with
> d
ugzilla and gerrit we require regression test(s)
> submitted through github.
>
> [1] https://wiki.eclipse.org/M2E_Development_Environment
>
> --
> Regards,
> Igor
>
>
> On 2014-03-30, 6:46, Anton Tanasenko wrote:
>
>> Hi,
>> Should I create an issue, or
On Sun, Mar 30, 2014 at 6:12 PM, Anton Tanasenko wrote:
> Hi,
> I probably confused you with my explanation.
> I submitted https://bugs.eclipse.org/bugs/show_bug.cgi?id=431580 with a
> description that probably makes more sense.
>
> Best regards
>
>
> On Sun, Ma
No problem at all :)
Thanks!
On Tue, Apr 1, 2014 at 9:05 PM, Igor Fedorenko wrote:
> Yes, I've seen the patches, plan to look at them over the weekend. Need
> to take care of $DAY_JOB, you know ;-)
>
> --
> Regards,
> Igor
>
>
> On 2014-04-01, 13:56, Anton T
Hi,
While trying to reuse m2e's refactoring mechanism
(PomHelper.createChange()) for my plugin I encountered several issues with
ChangeCreate.createChange() and was able to reproduce them using Lock
transitive dependencies and Exclude artifact actions in Dependency
Hierarchy view of pom editor.
Th
Hi,
As I understand, it is PDE that manages Plug-in dependencies and resolves
workspace plugins, m2e basically only provides ways for tycho to configure
the project correctly.
You should expect the following nature in .project (in addition to java and
m2e ones): org.eclipse.pde.PluginNature
And fol
Hi,
A couple of questions.
Is parent's packaging set to 'pom'?
Do you use maven import wizard?
If not, are eclipse project files (.project, .classpath, .settings) shared
in svn?
Regards,
Anton.
2014-09-16 19:07 GMT+03:00 Jason W. King :
> All,
>
>
>
> As a follow up to my initial question regard
Hi,
Default is 64M IIRC, setting it to 256M should be enough.
Also, Java 1.8 removed the notion of PermGen space completely, it will
dynamically allocated its new Metaspace from native memory.
2014-10-02 22:38 GMT+03:00 Jason W. King :
> I'm in the process of updating to a 1.6 milestone build. D
Hi,
It does seem that m2e BuildProblemInfo cannot cope with nulls in exception
error message and fails to log the root problem.
Until this is fixed, you can consult the 0.log file in
/.metadata/.plugins/org.eclipse.m2e.logback.configuration
but since
mojo execution exceptions are logged with debug
* m2e-users-boun...@eclipse.org [mailto:m2e-users-boun...@eclipse.org]
> *De la part de* Anton Tanasenko
> *Envoyé :* jeudi 23 octobre 2014 12:13
> *À :* Maven Integration for Eclipse users mailing list
> *Objet :* Re: [m2e-users] Errors running builder 'Maven Project Builder'
> on
that’s because I didn’t choose to use this feature.
>
>
>
> -Julien
>
>
>
> *De :* m2e-users-boun...@eclipse.org [mailto:m2e-users-boun...@eclipse.org]
> *De la part de* Anton Tanasenko
> *Envoyé :* jeudi 23 octobre 2014 15:18
>
> *À :* Maven Integration for Eclipse users mailin
pse-webby/issues/8
>
>
>
> Thanks
>
> -Julien
>
>
>
> *De :* m2e-users-boun...@eclipse.org [mailto:m2e-users-boun...@eclipse.org]
> *De la part de* Anton Tanasenko
> *Envoyé :* jeudi 23 octobre 2014 15:46
>
> *À :* Maven Integration for Eclipse users mailing list
>
It should also be possible to define those properties in eclipse.ini, this
way they are applied to the whole workspace.
2014-10-24 15:38 GMT+03:00 CoderPlus Team :
> Thanks Igor,
>
> I temporarily got around this by defining the property within my
> settings.xml file.
>
>
>
> On Fri, Oct 24, 2014
Hi,
I also started to work on similar extension but it was left unfinished.
The idea was to have a persistent ui element (I used a button in the lower
right trim) that would allow easily updating
any out-of-date projects in one click.
This way you can always get developer's attention that there ar
As a side note: with [1], one can turn off the workspace autobuild (Project
-> Build automatically) before making a number of changes
that would otherwise cause a lengthy projects refresh (and with this
extension, a projects update) phase.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=445675
a) Maven is capable of resolving modules from within reactor. You need to
make sure your module poms refer to the parent pom via their
sections.
2015-04-24 10:36 GMT+03:00 Daniel P. :
> Hello everyone,
>
> I'm currently developing a multi module Tapestry web application split
> into multiple mo
Hi,
I'd suggest against putting knowledge of m2e into maven plugin.
Instead, you could add a flag to your mojo configuration which controls the
mode of operation (copying vs. pointing to m2 repo), and control it from
your project's pom.xml using m2e profile.
Something along the lines of:
default v
Hi,
Maven 2.x is no longer supported in m2e 1.6
https://bugs.eclipse.org/bugs/show_bug.cgi?id=438922
2015-07-02 9:46 GMT+03:00 Jean Pierre Froud :
> Hi,
>
> I'm having a weird issue this morning. The plugin just decided my usual
> maven home isn't valid anymore:
>
> It says "NOT AVAILABLE" (cap
gt;> Hi,
>>
>> Thanks! I don't recall when I upgraded to 1.6...
>>
>> Regards,
>> JP
>>
>> 2015-07-02 10:35 GMT+02:00 Anton Tanasenko :
>>
>>> Hi,
>>> Maven 2.x is no longer supported in m2e 1.6
>>>
>>> ht
Maven launches are not tied to projects, but are executed in a specified
directory, which might span several eclipse projects or none at all.
There's no way to see which projects are affected, since maven plugins have
basically full access to the hard drive and might change anything outside
of thei
Hi,
Select any number of entries under Maven Dependencies node in
Project/Package Explorer, right click - Maven - Import projects from scm.
It requires corresponding maven scm connectors to be installed
(m2eclipse-egit for git projects) and it basically checks selected
dependencies out and shows yo
l honestly forget this conversation in 48
> hours if you don’t remind me :-)
>
> > On Sep 11, 2015, at 3:25 AM, Barrie Treloar wrote:
> >
> >
> >
> > On 11 September 2015 at 15:37, Anton Tanasenko
> wrote:
> > Hi,
> > Select any number of ent
Hi,
By using executionContext/executionRequest API, you perform a so-called
workspace build of the project, which m2e itself uses to execute various
mojos/phases.
In this mode some (interesting) mojo executions are either replaced by a
configurator - a special plugin that does its own stuff - or ar
Hi,
M2e does support custom packaging types without problems as long as the
plugins used in those packaging types' lifecycles are themselves supported
(either by m2e out of the box or through connectors [1]).
In fact, m2e does not even look at the pom's value, but instead
delegates execution plan
Hi,
1.
If you are talking about a 'maven launch', not a workspace build, then it's
the intended behavior of eclipse launch framework and it should stay that
way.
Otherwise you are risking stability of jvm running eclipse.
2-3-4.
All projects might (and it usually is the case) have a different clas
Looking at the error message in the gist [1], it seems that
org.glassfish.jaxb:jaxb-core jar is not added to the class realm for some
reason.
Does m2e report any other errors (about unresolved jaxb-core dependency in
particular)?
[1] https://gist.github.com/cptwunderlich/b088e8e5d6116084ba94
2015
This looks to be a bug with takari plugin testing harness:
https://github.com/takari/takari-plugin-testing-project/issues/11
2015-12-21 5:49 GMT+02:00 Fred Bricon :
> If it runs fine with a previous M build (like [1]) then it's very likely
> this is a regression caused by the fix for bug #444262
Hi, please provide a full stack trace of this error as found in Window ->
Show View -> Error log.
2015-12-26 22:14 GMT+02:00 Steinar Bang :
> Platform: Windows 7
> Java SE DK 8 Update 65 (64 bit) 8.0.650.17
> Java 8 Update 66 (64-bit) 8.0.660.18
> Windows Mars 64-bit
empty.
>
> Probably it is more related to the fix implemented in m2e in #444262 bug.
>
> The workaround that I used was to copy the same value from user settings
> to the global settings.
>
> regards,
>
> Cristiano
>
>
>
> On 23-12-2015 13:55, Anton Tanasenko
This is probably related to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=438161
2015-12-28 9:48 GMT+02:00 Steinar Bang :
> >>>>> Anton Tanasenko :
>
> > Hi, please provide a full stack trace of this error as found in Window ->
> > Show View -> Error l
Can you share your eclipse config?
Help -> Installation details -> Configuration
2015-12-28 12:53 GMT+02:00 Steinar Bang :
> >>>>> Anton Tanasenko :
>
> > This is probably related to
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=438161
>
> N
Can you try it without installing Komma?
It does include some weird-looking library bundles in its sources [1] which
might affect m2e.
[1] https://github.com/komma/komma-libraries
2015-12-28 16:06 GMT+02:00 Steinar Bang :
> >>>>> Anton Tanasenko :
>
> > Can yo
Hi,
M2e has a separate project classpath container for repository jars and
workspace projects (Java Build Path -> Libraries -> Maven dependencies).
'Referenced projects' mechanism is meant to be modifiable by users, while
m2e derives project's classpath from pom.xml. And it also cannot be used
sin
t add to the project.
Those project classpath containers might be contributed by an arbitrary
eclipse plugin and m2e happens to be one such plugin.
2016-01-03 21:35 GMT+02:00 Sony Antony :
> Thank you Anton :
> Read your response carefully. Some more questions inline below
>
> On S
Hi,
You should send those questions to the tycho user list [1], since you are
building eclipse projects using maven tycho plugin.
[1] https://dev.eclipse.org/mailman/listinfo/tycho-user
2016-01-06 14:03 GMT+02:00 Christelle BURGUERA :
> Hello,
>
>
>
> I’ve already maven projects :
>
> - On
M2E contains what basically is a vanilla maven runtime (its version should
be visible in the runtime list) and it always uses this embedded runtime
for workspace resolution irregardless of which one you have selected in the
preferences.
The preference applies to 'Run as Maven' launch configurations
Hi,
You can make your maven plugin compatible by following this topic:
https://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html
2016-01-24 16:18 GMT+02:00 Art Kaufmann :
> I have a Maven plugin that provides a custom lifecycle for a custom
> packaging type. This works fine
Hi,
M2e-tucho mapping should probably take precedence in such case.
See
https://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/lifecyclemapping/LifecycleMappingFactory.java#n265
2016-03-12 13:14 GMT+02:00 Anders Hammar :
> As I understand the plug
Hi Eric,
Every eclipse project must reside in its own dir, it doesn't allow mixing
multiple projects in the same directory.
Eclipse also doesn't allow storing any of its resources outside of their
respective project's dir.
So you should definitely convert your project into a proper multimodule
bui
Try running eclipse with -consoleLog. Jaxws dumps output to System.out,
which during the mojo execution in eclipse should be plain System.out of
eclipse itself.
2016-05-19 21:01 GMT+03:00 Eric B :
> Great idea. I did. It worked flawlessly - as expected:
>
> $ wsimport -d /tmp/ws/bin -p jaxws.se
Hi, just downloading the file by that url in a browser is extremely slow,
so it's probably an eclipse infra problem.
2016-06-01 11:56 GMT+03:00 Jochen Wiedmann :
> Hi,
>
> whenever I try to install M2E into Eclipse 4.6RC3, I get an error like
> below
>
> Is there any other possibility to get M2E
Hey,
M2e does not configure jdt-apt itself (which is a pain to configure
manually), but there is m2e-apt [1] which would do that for your.
As its description says, it's not enabled by default, you can either enable
it globally in preferences or for each project separately (which is more
preferable)
e Annotation
> Processor
>
> I'm really not sure what I'm missing here.
>
>
> On Sun, Feb 5, 2017 at 2:13 PM, Anton Tanasenko
> wrote:
>
>> Hey,
>> M2e does not configure jdt-apt itself (which is a pain to configure
>> manually), but there is m2
Hi, there is a documentation page on setting up dev environment:
https://www.eclipse.org/m2e/documentation/m2e-development-environment.html
2017-02-14 1:19 GMT+02:00 Dessie K :
> Hi,
>
> How do I build m2e. Trying to build m2e-core tag '
> releases/1.7/1.7.0.20160603-1933' locally and getting mis
Hi Andreas,
While repository.takari.io is down, you can use this one instead:
http://repo1.maven.org/maven2/.m2e/connectors/
пт, 28 дек. 2018 г. в 14:03, Andreas Weise :
> hi folks,
>
> all takari repository urls seems down?
> https://repository.takari.io/content/repositories/releases/
> http://
Hey, do you have something in your poms that generates plugin configuration
from timestamps or some other dynamic values?
I did encounter such problems sometimes with large enough workspaces and
timestamps within poms.
чт, 19 дек. 2019 г. в 17:18, :
> I fear I have stepped into the infamous endl
50 matches
Mail list logo
