You can use the verbose syntax to ignore a specific goal from being
executed during an Eclipse build:
https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html#ignore-plugin-goal
I suggest you look at the effective pom of your project to find where the
deploy goal is being executed
Simon's explanation is correct, this is documented in the m2e FAQ:
https://www.eclipse.org/m2e/documentation/m2e-faq.html
Le dim. 15 déc. 2019 à 13:49, Michael Moser a
écrit :
> Ah - I see. The fog is lifting a bit.
>
> I obviously hadn't grasped how these two co-operate and share duties.
>
>
>
son
wrote:
> Here are the 2 sections tagged maven-compiler-plugin:
>
> https://gist.github.com/wsorenson/e61e3ad60a0755ae8525b588d3a59551
>
>
>
>
> On Wed, Dec 4, 2019 at 12:26 PM Fred Bricon wrote:
>
>> The Java nature is added automatically and the Java configurat
The Java nature is added automatically and the Java configuration done
according to the maven-compiler-plugin configuration.
Can you share the content of you maven-compiler-plugin config, from
running mvn help:effective-pom?
On Wed, Dec 4, 2019 at 6:19 PM Whitney Sorenson
wrote:
> Hello,
>
> I'v
'Project and External Dependencies' is a classpath container provided by
Buildship, for Gradle projects. No Maven projects should have it. i.e.
there should be no org.eclipse.buildship.core.gradleclasspathcontainer
classpath entry. Long story short, this is not m2e misbehaving.
Does your project ha
Sorry but m2e doesn't support .mvn extensions at this time. It's a
non-trivial project to solve. The same maven runtime is used for all
projects of the workspace.
If you add extensions to the mix, those would leak into unrelated projects
in the same Eclipse workspace, leading to unexpected issues.
34 AM KARR, DAVID wrote:
> That’s really just the pom.xml file itself, right?
>
>
>
> *From:* m2e-users-boun...@eclipse.org *On
> Behalf Of *Fred Bricon
> *Sent:* Wednesday, July 10, 2019 2:58 PM
> *To:* Maven Integration for Eclipse users mailing list <
> m2e-users
Can you attach the projects (before import), without the source code, and
after anonymizing the poms?
On Wed, Jul 10, 2019 at 10:30 PM KARR, DAVID wrote:
> I work on a team with a bunch of git repos that are Java, Maven, and
> Spring Boot projects. We all configure Eclipse somewhat similarly,
>
ng to be pretty unlikely, but if I don’t get any other ideas
> I’ll try copying this project and pulling everything I can out of it.
>
>
>
> *From:* m2e-users-boun...@eclipse.org *On
> Behalf Of *Fred Bricon
> *Sent:* Saturday, May 25, 2019 7:58 AM
> *To:* Maven Integration
can you provide a sample project reproducing this issue?
On Sat, May 25, 2019 at 10:56 AM KARR, DAVID wrote:
> The “Sources” entry for “src/test/java” has “Contains test sources: Yes”.
>
>
>
> The effective pom shows the “junit” artifact with “test”.
> Curiously, the same search for “mockito-cor
Have you tried reproducing the problem with a plain Eclipse Java project? I
could be wrong but that smells like a JDT issue to me.
On Thu, Apr 18, 2019, 05:24 Thorsten Heit wrote:
> Hi,
>
> I see a strange behaviour in Eclipse (2019-03) that I don't know where it
> comes from nor how to solve it
You can try to install the latest version from this p2 repo:
https://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.15.1/N/LATEST/
We're currently not able to update the m2e discovery catalog, as the takari
CI server that could build it and upload the results to Maven Central has
been di
Do you have the "m2e connector for mavenarchiver pom properties" plugin
installed? It's available in the Eclipse update site.
I'd expect it would generate proper Manifests in target/classes, that would
be picked up by M2E/JDT to compute the project's module name. But I might
be wrong.
On Mon, Feb
CLI Maven doesn't use OkHttp for transport. I believe OkHttp was chosen for
m2e for performance reasons, but Igor might certainly know more about it.
Looks like aether-connector-okhttp[1] needs to accept both custom and
platform certificates, as per SO[1][2].
[1] https://github.com/takari/aether-c
On Mon, Sep 17, 2018 at 9:46 AM Fred Bricon wrote:
> The problem occurs in "serve modules without publishing" too. The best way
> to workaround it is by disabling Advanced source lookup, in Preferences >
> Java > Debug, as Igor mentioned.
>
Correction: "serve
The problem occurs in "serve modules without publishing" too. The best way
to workaround it is by disabling Advanced source lookup, in Preferences >
Java > Debug, as Igor mentioned.
I did contribute advanced source lookup support in the Tomcat server
adapter for Photon, so navigating into the Tomc
In its current implementation, the modulepath is entirely inferred from the
module-info.java's required modules (and their transitive dependencies, in
m2e 1.9/Photon).
m2e ignores Java 9 options from the maven-compiler-plugin configuration
section.
I suggest you create a sample project, try it Pho
Hi,
while we make no commitment to keep m2e backward compatible with previous
Eclipse versions, we generally try to make it work with at least one
previous Eclipse release.
Since m2e 1.8.2 (released along the Eclipse Oxygen.1 stream), we're
depending on internal APIs in JDT to provide minimal Jav
m2e 1.9 will be released in June 2018.
It's highly unlikely the archetype plugin will be updated since the plugin
removed an important feature [1], some APIs changed which would require
non-trivial work to update support in m2e.
[1] https://issues.apache.org/jira/browse/ARCHETYPE-438.
On Tue,
This is a known issue in JDT[1], which also requires some changes in
m2e[2]. Until a fix is available, you can try this ugly workaround[3].
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=520713
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=529398
[3] https://bugs.eclipse.org/bugs/show_bug.c
This is a bug in JDT[1]. You need to wait for a new build, in a day or 2.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=525382
On Oct 8, 2017 23:53, "Clément Guillaume" wrote:
Hello all,
I'm testing eclipse (oxygen 1a RC2 linux 64) and java 9 (oracle linux 64
release) and I'm encountering
latest releases are:
- m2e 1.8.1, install from [1]
- m2e-wtp 1.3.2, install from [2]
[1] http://download.eclipse.org/technology/m2e/releases/
[2] http://download.eclipse.org/m2e-wtp/releases/oxygen/
On Wed, Oct 4, 2017 at 4:25 PM, Bahram Sanaei wrote:
> Hello,
>
>
> What is the latest official
...
> >
> >
> >
> >
> >
> > My problem is that the EAR builds successfully on the command line and
> > contains all specified resources in their correct place, but with WTP /
> > m2e-wtp problems arise:
> >
Oxygen is borked at the moment:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=514672
My advice is to stay on Neon.2 (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=511793 ruins Neon.3 for me)
at the moment, until a fix is released
On Fri, Apr 7, 2017 at 2:14 AM, Thorsten Heit wrote:
> Hi,
>
> w
;>
>>> I believe this message comes from IBM websphere developer tools and not
>>> m2e. Are you using those?
>>>
>>> Regards, Marcel
>>>
>>> Op 6 apr. 2017 21:18 schreef "Anders Hammar" :
>>>
>>> Thanks Fred, I'll
Integration for WTP 1.2.1.20150819-2220
>
> Attached is a simple project to reproduce. If you want I can create a
> ticket for this instead?
>
> /Anders
>
> On Thu, Apr 6, 2017 at 2:18 PM, Fred Bricon wrote:
>
>> Anders, I haven't seen or heard about that warning in y
Anders, I haven't seen or heard about that warning in years. What version
of Eclipse are you using? Does it include m2e-wtp? Do you mind sharing a
simple project reproducing this warning?
On Thu, Apr 6, 2017 at 7:56 AM, Anders Hammar wrote:
> I'm trying to solve some long time annoying warnings
There's a limitation in Eclipse JDT where you can't have a workspace
project running annotation processors loaded from another workspace project.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=259230 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=280542
There's nothing we can do at the m2e-
FYI secondaryTo is now deprecated and superseded by the more granular
runsAfter/runsBefore attributes. See [1].
Only configurators can be ordered. You can't mix n' match mojo execution
with configurators for a given goal.
[1]
https://www.eclipse.org/m2e/documentation/release-notes-16.html#improve
have you tried importing the project in a new, clean workspace?
It'd help if you could share your pom
On Mon, Oct 3, 2016 at 2:16 PM, Shelli Orton wrote:
> Hi,
>
> Hoping somebody has a suggestion for this issue. Otherwise, I'm going to
> have to downgrade my Eclipse install.
>
> Shelli
>
> ---
the source preferences set in JDT match the values inferred from your
pom.xml. By default the maven compiler plugin settings set it to 1.5 [1].
If you want to use 1.8, make sure your compiler plugin uses the proper
settings:
maven-compiler-plugin
3.5.1
1.8
1.8
As for
- Carsten Pfeiffer
- Rastislav Wagner
- Konrad Windszus
Please, keep them contributions coming!
As usual, please do not hesitate to give us your feedback on this mailing
list
or open bugs at [4].
Enjoy,
Fred Bricon
https://twitter.com/fbricon
[1] http://download.eclipse.org/technology/m2e/re
d
>
> Thanks
>
> -Dan
>
> On Tue, Jun 14, 2016 at 1:14 PM, Fred Bricon wrote:
>
>> Corresponding https://github.com/tesla/m2eclipse-mavenarchiver/issues/9
>> has been fixed, which you can test by installing the latest CI build from
>> https://otto.takari.io/conten
Corresponding https://github.com/tesla/m2eclipse-mavenarchiver/issues/9 has
been fixed, which you can test by installing the latest CI build from
https://otto.takari.io/content/sites/m2e.extras/m2eclipse-mavenarchiver/0.17.2/N/LATEST/
.
On Tue, Jun 14, 2016 at 1:45 AM, Fred Bricon wrote
I'll investigate tomorrow, but I 'm surprised to see such an error in a
maintenance release
On Jun 13, 2016 10:06 PM, "Dan Tran" wrote:
> Confirm, i encounter the same issue, ended up to revert back to jar-plugin
> 2.6
>
> Thanks
>
> -D
>
> On Mon, Jun 13, 2016 at 6:49 AM, Thorsten Heit
> wrote:
ers mailing list
> *Subject:* Re: [m2e-users] maven-war-plugin with m2e
>
>
> Hmm, which version of eclipse/maven/m2e?
>
>
>
>
> ------
> *From:* m2e-users-boun...@eclipse.org on
> behalf of Fred Bricon
> *Sent:* June 13, 2016 12:35 PM
>
maven update from inside eclipse the
> Web-ContextPath gets changed.
>
>
> Thanks!
>
>
> --
> *From:* m2e-users-boun...@eclipse.org on
> behalf of Fred Bricon
> *Sent:* June 10, 2016 7:09 AM
> *To:* Maven Integration for Eclipse users m
Do you have a sample project I could take a look at?
On Thu, Jun 9, 2016 at 6:59 PM, Randy Toor wrote:
> Hi,
>
>
> I'm using maven to build a war file that uses my own MANIFEST file,
> configured as such -
>
>
>
> org.apache.maven.plugins
> maven-war-
Not yet, but I'm planning on getting it done soon(TM)
On Mon, May 23, 2016 at 2:29 PM, Lars Vogel wrote:
> Hi,
>
> Do you have N&N for m2e releases to find what is new in every release?
>
> Would be nice to be able to point users to it a similar to our platform
> news like for example https://ww
Please try the CI build from this p2 repo:
https://otto.takari.io/content/sites/m2e.extras/m2eclipse-mavenarchiver/0.17.0/N/LATEST/
On Fri, May 20, 2016 at 11:36 PM, Fred Bricon wrote:
> I'll push a fix over the week-end
>
> On Fri, May 20, 2016 at 7:32 PM, Sandip Ch
I'll push a fix over the week-end
On Fri, May 20, 2016 at 7:32 PM, Sandip Chitale
wrote:
>
>
> On Fri, May 20, 2016, 12:45 PM Karl Heinz Marbaise
> wrote:
>
>> Hi,
>>
>> On 5/20/16 5:10 PM, Fred Bricon wrote:
>> > the m2eclipse-mavenarchiver plug
http://maven.apache.org/plugins/maven-ejb-plugin/examples/generating-ejb-client.html
states it supports clientIncludes elements. See
http://maven.apache.org/plugins/maven-ejb-plugin/ejb-mojo.html#clientIncludes
On Fri, May 20, 2016 at 5:01 PM, Eric B wrote:
> @Matthew - good call. I started to
the m2eclipse-mavenarchiver plugin is doing some reflection (boooh) on the
maven-archiver plugin in order to manipulate the manifests. Seems like the
latest maven-archiver release changed some internal methods, which breaks
the eclipse integration.
Please open a bug at https://github.com/tesla/m2e
could even eliminate the nonFilteredExtensions if it helps me come to a
> semblance of a resolution.
>
> Thanks,
>
> Eric
>
> On Tue, Mar 15, 2016 at 1:20 AM, Fred Bricon wrote:
>
>> target/m2e-wtp/web-resources is used to keep generated stuff, like the
>>
s the root path.
>
> Is there a way to "remove" the /target/m2e-wtp/web-resources from the
> equation? What is supposed to end up in there? Can I redirect the output
> to the /WEB-INF/classes folder instead?
>
> I'm not precompiling my JSPs, if that makes any diff
ferently in the case of a Maven nature vs an Eclipse nature. Oh
>>> boy - I can foresee this is as being a tough one to resolve.
>>>
>>> Even if I were to manually add entries into my Deployment Assembly, m2e
>>> tends to overwrite them whenever updating my proj
And I've already failed
> at getting m2e 1.6 into an older Eclipse install.
>
> Thanks,
>
> Eric
>
>
>
>
> On Fri, Mar 11, 2016 at 1:39 PM, Fred Bricon wrote:
>
>> m2e-wtp 1.2 keeps manual deployment assembly settings.
>> https://wiki.eclipse.org
o my pom/etc to force certain entries into my
> Deployment Assembly?
>
> Thanks,
>
> Eric
>
> On Fri, Mar 11, 2016 at 1:31 PM, Fred Bricon wrote:
>
>> Tomcat and JBoss server adapters use a deployment directory by default.
>> Publishing is incremental, i.e. onl
deploy/structure classpaths/etc.
>
> Chuck/Roberto - are you able to provide any additional info for this? I'm
> using RAD 9.1.1 with the WAS 8.5 tools (but it has been tried in Luna with
> the WAS 8.5 tools and the same result as well)
>
> Thanks!
> Eric
>
>
> O
This is a question for the IBM team. Cc'ing Chuck and Roberto on this.
I know Tomcat and JBoss server adapters work just fine, but I can't test
WebSphere.
Fred
On Fri, Mar 11, 2016 at 10:41 AM, Eric B wrote:
> I'm confused as to why this is happening in my m2e projects vs standard
> Eclipse pro
It's probably easier to hack a Mars distro to make it display the Juno
splashscreen
On Thu, Feb 25, 2016 at 3:27 PM, Fred Bricon wrote:
> It's *probably* possible to hack m2e sources to make it work against juno,
> but that'd be a fork of your own, and it's also very p
would double
> check just in case there was something that could be done.
>
> Thanks,
>
> Eric
>
>
> On Thu, Feb 25, 2016 at 3:10 PM, Fred Bricon wrote:
>
>> Apparently no. m2e 1.6 requires a more recent core eclipse component.
>> Missing requirement: M
://stackoverflow.com/a/24659711/827480
> ).
>
> Any ideas if there is a similar workaround for 1.6? Upgrading from Juno
> is unfortunately not an option.
>
> Thanks,
>
> Eric
>
>
> On Thu, Feb 25, 2016 at 2:56 PM, Fred Bricon wrote:
>
>> Both releases sa
Both releases saw some performance improvements :
https://www.eclipse.org/m2e/documentation/release-notes-15.html
https://www.eclipse.org/m2e/documentation/release-notes-16.html
Latest version should be the best m2e release ever, until next time.
On Thu, Feb 25, 2016 at 2:37 PM, Eric B wrote:
>
ric
>
>
> On Thu, Feb 18, 2016 at 8:04 PM, Eric B wrote:
>
>> Don't I feel like the NOOB. I can't believe I missed that! Nor can I
>> believe how much time I wasted reinstalling m2e! I wonder what could have
>> possibly caused the preference change.
>
e even the
>> option in the interface?
>>
>> Thanks,
>>
>> Eric
>>
>>
>> On Thu, Feb 18, 2016 at 8:04 PM, Eric B wrote:
>>
>>> Don't I feel like the NOOB. I can't believe I missed that! Nor can I
>>> believe how much t
Try Preferences > Maven > Java EE integration > check `Generate
application.xml under the build directory`
On Thu, Feb 18, 2016 at 4:08 PM, Eric B wrote:
> I have no idea what I did to break my m2e/m2e-wtp installation, but my
> maven project is now generating my application.xml file in my
> sr
Looks like you're trying to use m2e with a really old Eclipse version. This
error looks like m2e-wtp (the JSF integration) is expecting to use a more
*recent* WTP API, that can't be found in your Eclipse installation.
If upgrading Eclipse is not an option, then you can try to uncheck
Preferences >
To be honest, m2e-wtp is not responsible for running/reloading Tomcat, this
is really something happening under WTP's umbrella.
You could try setting up a set of sample (non-maven) projects to reproduce
the problem, see if the same problems happen without m2e-wtp in the mix.
Fred
On Thu, Jan 21,
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.
In that case, please open a ticket in BZ.
[1]
http://download.eclipse.org/technology/m2e/milestones/1.7/1.7.0.20151110-2248/
[2] https://bugs.eclipse.org/444262
Fred
m2e doesn't deserialize anything from remote connections (doesn't even rely
on commons-collections for deserializing it's local state). The archetype
plugin simply downloads xml and jars, I'm not aware it uses the
deserialization mechanism either. I don't believe, unless proven otherwise,
that m2e
Yes it should
On Nov 11, 2015 12:16 AM, "Manfred Moser" wrote:
> Excellent news Fred. Just out of curiosity .. does this also work with
> Mars?
>
> Manfred
>
> Jason van Zyl wrote on 2015-11-10 17:21:
>
> Thanks Fred!
>
> > On Nov 10, 2015, at 6:20
Hello World,
m2e 1.7.0 (1.7.0.20151110-2248) M3 for Neon is now available. It can be
installed from [1].
Highlights of this release include
- maven archetype plugin updated to 2.4
- Maven Launch configurations now use the PROJECT_LOC variable expression,
instead of absolute paths, making launch co
Works for me too
On Thu, Nov 5, 2015 at 10:49 AM, Konrad Windszus wrote:
> No proxy in between. And I am not the only one with the problem:
> https://github.com/tesla/m2eclipse-egit/issues/13
>
> On 05 Nov 2015, at 16:47, Matthew Piggott wrote:
>
> That URL also works for me, is there a proxy o
Nils,
I'm sorry, but I don't currently have the bandwidth to do as much as I'd
like on m2e/m2e-wtp, I am absolutely unable to tell whether/when that'll
change.
The best option would be for you to provide a gerrit changeset, see [1].
[1] https://wiki.eclipse.org/M2E-WTP-Dev_Environment#Submitting
;
>>
>>
>>
>>
>>
>> org.apache.maven.plugins
>>
>> maven-surefire-plugin
>>
>> 2.18.1
>>
>>
>>
>>
>>
>> org.
This is not really an m2e question, you should rather ask the Maven Users
list.
Anyways, first hit on google for "Cucumber Maven Project" :
http://blog.czeczotka.com/2014/07/22/cucumber-jvm-with-maven-in-minutes/
On Thu, Oct 15, 2015 at 4:23 PM, Kashif BHATTI wrote:
> Hello,
>
> I have created
For those interested, as posted on https://bugs.eclipse.org/478647:
I got a POC running some time ago, that I pushed to github[1], you can
install it from bintray[2] (I rebased it against latest m2e 1.7 code,
requires Java 8 to run)
- it only covers the search engine used during content assist in
Lars
>
> On Tue, Sep 29, 2015 at 4:38 PM, Fred Bricon wrote:
> > About network consumption, we're talking about an initial 150MB index
> > download per workspace, then incremental updates once a week.
> > As for the inter-process file locks, I'm curious to kno
About network consumption, we're talking about an initial 150MB index
download per workspace, then incremental updates once a week.
As for the inter-process file locks, I'm curious to know how Intellij and
Netbeans solved that issue.
Anyways, the plan is to get rid of the whole nexus index altoge
Hi,
on behalf of the m2e team, I'm pleased to announce that m2e 1.6.2 (git tag:
releases/1.6/1.6.2.20150902-0002) is now generally available for Eclipse
Mars.
This maintenance release fixes some critical bugs related to m2e
configurators, as well as a few more issues. See the changelog here [1].
Hello World,
m2e 1.6.2 (1.6.2.20150902-0001) RC2 for Mars.1 has been released. 3 small
bugs were fixed, as you can see in the changelog[1]. I didn't initially
planned on pushing a new RC for m2e 1.6.2, but thanks to Konrad Windszus'
contributions, here we are.
m2e 1.6.2 can be installed from [2].
> Yes. Takari feature requires specific versions of everything. But
> mavenarchiver configurator version must be locked elsewhere too, otherwise
> installation would have succeeded.
>
> --
> Regards,
> Igor
>
> On August 23, 2015 3:34:34 PM Fred Bricon wrote:
>
>> I
Igor m2e-wtp requires mavenarchiver 0.17.0+, but doesn't lock to any
specific version.
The version embedded in Java EE (0.17.0.201502101659-signed-20150525172209)
is the same as
http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.17.0/N/0.17.0.201502101659/
only
repackaged and
Hi,
I re-spun the staged 1.6.2 and 1.7.0 RCs in order to include a fix for [1].
New builds are now 1.6.2.20150819-1555 and 1.7.0.20150819-1552.
Sorry for the inconvenience.
[1] https://bugs.eclipse.org/471843
Fred
On Tue, Aug 18, 2015 at 10:02 PM, Fred Bricon wrote:
> Hello World,
>
Hello World,
m2e 1.6.2 (1.6.2.20150818-2354) RC1 for Mars has been released. It notably
fixes a regression introduced in 1.6.1 that broke the groovy configurator.
See the changelog here [1]. It can be installed from [2]. 3rd party
configurator providers are *strongly* encouraged to check 1.6.2 wor
ttps://github.com/takari/m2e-discovery-catalog/pull/58
> Bindul Bhowmik
>
>
> On Wed, Jul 22, 2015 at 2:45 PM, Bhowmik, Bindul
> wrote:
> > Fred,
> >
> > Thank you. I will give it a shot.
> >
> > Regards,
> > Bindul
> >
> >
> > On
If someone creates a PR to update the m2e subversive connector in the
discovery catalog[1], I'll be happy to merge it.
[1]
https://github.com/takari/m2e-discovery-catalog/blob/master/org.eclipse.m2e.discovery.oss/src/main/resources-filtered/connectors.xml
On Wed, Jul 22, 2015 at 2:18 PM, Bhowmik,
Yup, sorry, seems I broke something.
Anyway, I won't be able to investigate until the next couple weeks. So
don't hesitate to take a look at the code and submit Gerrit patches[1]
[1]
https://www.eclipse.org/m2e/documentation/m2e-development-environment.html
On Fri, Jul 3, 2015 at 4:26 PM, Max
Hi,
we just released m2e 1.6.1 (git tag releases/1.6/1.6.1.20150625-2338),
fixing a bug with the new runsAfter/runsBefore directives[1], found by the
m2e-android team.
m2e 1.6.1 can be installed manually from this p2 update site[2].
m2e 1.6.1 will be added to the next Eclipse Mars SR1 release, i
Hi,
the m2e-android team found a serious issue with the way project
configurators are ordered with the new runsAfter/runsBefore directives[1]
in m2e 1.6.0. This would lead to configurators being completely ignored and
generate Plugins Execution Not Covered errors.
Hence, I staged m2e 1.6.1, fixin
Gerrit for this
1.2 release :
- Wei Cai
- Michael Schieder
- John Serock
Keep them coming!
As usual, please do not hesitate to give us your feedback on this mailing
list
or open bugs at [4].
Enjoy.
Fred Bricon
https://twitter.com/fbricon
[1] http://download.eclipse.org/m2e-wtp/releases/
gs at [3].
The master branch on git now builds m2e 1.7.0-SNAPSHOT, which requires 1.8.
Enjoy.
Fred Bricon
https://twitter.com/fbricon
[1] http://download.eclipse.org/technology/m2e/releases/
[2] https://www.eclipse.org/m2e/documentation/release-notes-16.html
[3] https://bugs.eclipse.org/bug
oh that's very simple actually, IBM JVMs are not supported. Until IBM or
someone is willing to step up and provide a fix.
Please use an Oracle JVM instead (OpenJDK _might_ work).
On Jun 22, 2015 6:54 PM, "Juan" wrote:
>
> Fred Bricon gmail.com> writes:
>
>
m2e is embedded in a number of Eclipse distros :
https://www.eclipse.org/downloads/compare.php?release=luna
So it's expected to work OOTB for these.
Additionally, it'd be useful if you could provide a complete log leading to
the error.
On Mon, Jun 22, 2015 at 5:22 PM, Juan wrote:
> Igor Fedoren
http://download.eclipse.org/technology/m2e/releases/ shows the m2e 1.5.2
release
http://download.eclipse.org/technology/m2e/milestones/1.6/ is the update
site url for the latest milestone release (m2e 1.6.0)
Fred
On Fri, Jun 12, 2015 at 1:57 PM, Dunkle, Edward
wrote:
> I have configured other
I would suggest trying http://eclipse-jetty.github.io/ to manage jetty
instances directly from eclipse. I haven't tried in a while but there's a
chance it might suit your workflow, provided your maven configuration is
"standard-ish" (i.e doesn't require fancy maven plugin executions to build).
Now
Yes it does
On Apr 21, 2015 8:22 AM, "Jochen Wiedmann"
wrote:
> Does this one contain a fix for the maven.multiModuleProjectDirectory?
>
>
> On Wed, Apr 15, 2015 at 10:02 PM, Fred Bricon wrote:
> > Hello World,
> >
> > m2e 1.5.2 (git tag 'release
3, 2015 at 6:35 PM, Fred Bricon wrote:
> Hi,
>
> we decided to release m2e 1.5.2 (a.k.a 1.5.2.20150413-2215), in order to
> fix support for
> running external Maven 3.3.x launch configurations [1].
>
> The new build is available from the m2e 1.5 milestones repository[2].
&g
Hi,
we decided to release m2e 1.5.2 (a.k.a 1.5.2.20150413-2215), in order to
fix support for
running external Maven 3.3.x launch configurations [1].
The new build is available from the m2e 1.5 milestones repository[2].
Please give it a try and report any problems you find either here or in
bugzil
Hi,
FYI, we've updated the m2e 1.6 contribution for Mars M6, new version is
1.6.0.20150325-2013, due to a critical bug found yesterday and fixed a few
moment ago by Igor [1].
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=463075
Fred
--
"Have you tried turning it off and on again" - The IT
Hi,
we've published m2e 1.6 M6 (a.k.a 1.6.0.20150324-2020) to the milestones
repository [1]. The full changelog is available at [2].
This milestone release contains a couple interesting enhancement/bugs fixes
:
- the embedded Maven is now 3.3.1 [3]. Please note Run As > Maven is still
broken tho
On Wed, Mar 18, 2015 at 5:42 PM, Bruno Haible
wrote:
> Hi,
>
> > we have decided to turn the workspace preference on by
> > default (Preferences > Maven > Automatically update Maven projects
> > configuration (experimental))
>
> Does this automatically update only the Maven dependencies in memory
Hi,
FYI, the latest m2e 1.6 CI build provides a way to automatically update
out-of-date project configuration [1].
We've been experimenting it for a while, as a standalone extension provided
by JBoss Tools Playground [2], and haven't faced any issue so far. So we
have decided to turn the workspac
m2e-wtp currently doesn't support artifacts generated by
maven-assembly-plugin within the workspace. i.e a workspace project cannot
reference a zip classifier artifact matching another workspace project.
You basically have 2 solutions :
- force the consumers to reference the zip file directly : ei
I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=460959.
Basically, you should update to the latest maven-ear-plugin version (2.10
as we speak)
On Wed, Feb 25, 2015 at 1:52 PM, Fred Bricon wrote:
> Please open a ticket at [1] with a sample project reproducing the error.
>
Please open a ticket at [1] with a sample project reproducing the error.
As a workaround, either use no-version [2]
or specifically set the jarModule's bundleFileName in
maven-ear-plugin>configuration>modules [3][4]
[1] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E-WTP
[2]
https://ma
Ok, so missing (filtered) resources is a bug in m2e-wtp, can you please
open a ticket in BugZilla[1]?
As a workaround, you can move your src/main/resources/APP-INF folder
to src/main/application/APP-INF/ and enable filtering in
maven-ear-plugin
This has been fixed with m2eclipse-mavenarchiver 0.17.0 you can install
from
http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.17.0/N/LATEST/
On Thu, Feb 12, 2015 at 9:30 PM, Eric B wrote:
> So I'm running into this old ugly problem of seeing this error in my build:
>
>
> o
Hi,
we've published m2e 1.6 M5 (a.k.a 1.6.0.20150203-1921) to the milestones
repository [1]
This milestone release contains a few bugs fixes [2]. Most notably, Anton
Tanasenko provided smarter plugin configuration autocompletion in the
pom.xml editor[3].
Please give it a try and let us now about
1 - 100 of 410 matches
Mail list logo
