Hi,
> Adding the following to the pluginManagement section did the trick for
me:
>
>
> org.eclipse.m2e
> lifecycle-mapping
> 1.0.0
>
>
>
>
>
> org.apache.maven.pl
Hi,
> What version of Maven CLI are you using?
thorsten$ mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: /Users/thorsten/bin/apache-maven-3.0.3
Java version: 1.6.0_24, vendor: Apple Inc.
Java home:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> lifecycle-mapping is only expected to be used inside
> pom.xml section, and Maven itself does not perform any validation of
> lifecycle-mapping poms, etc. Some projects put lifecycle-mapping to
> special profile activated inside m2e only to be extra sure m2e
> configuration is not affecting thei
Hi Igor,
> lifecycle mapping is just xml, there is no code anywhere and no plugin.
Ok, thanks for clarifying.
> But, again, it is only used under pluginManagement section. This section
> by itself does not affect maven build in any way.
Yes, I know. I just wondered why m-versions-p printed som
Hi,
after having installed a fresh copy of Eclipse 3.7 and m2e, I tried to
install a couple of m2e connectors. Unfortunately the m2e-cvs team
provider refuses the installation process: Clicking the "Finish" button
results in the message "Operation details" prepended by a red cross icon
being s
Hi Igor,
> I realize that lack of out-of-the-box support for many popular maven
> plugins appears to be a significant regression compared to 0.12, but I
> am hopeful that we, as a community, will be able to quickly populate m2e
> extensions discovery catalog and effectively solve this problem. For
Hi,
> I have the exact same issue. I am behind a corporate proxy. I use native
setting
> in preferences. Marketplace has same issue, unable to connect. I don't
use any
> truststore settings so can't remove them.
> I do am able to access the maven discovery catalog url and also the
mentioned
Hi,
> I tried to develop with spring and m2eclipse. I have installed m2e using
> eclipse marketplace - plugin maven integration for eclipse. Installation
> was without any problems. However there is a problem that when I try to
> add m2e functionality to my project (right click on project and
Hi,
> I tried that already problem is that when I right-click my project ->
> configure -> the only option is confvert to plug-in projects. Putting
it
> simply I cannont convert to Maven Project atm. I thought that maybe you
> have to enable this plug-in for maven m2e and asked such question
Hi Igor,
> m2e deliberately creates "forward" references to all source/resource
> folders found in pom.xml in .classpath. These are marked as optional, so
> jdt builder silently ignores folders that do not actually exist on
> filesystem. This behaviour is consistent with maven command line build,
Hi Adam,
> I'm having a pretty significant problem with m2e in eclipse. First,
> build info. I'm using
>
> Eclipse Indigo Service Release 1, 20110916-0149
> m2e 1.0.200.20111228-1245
> JDK 1.7.0_02
>
> I also have installed
> JRE7 (important later)
>
> My problem is that when I right click on
Hi,
> I'm really disappointed in this product. I'm sure it works fine for
> many, but after a clean installation of elcipse and M2E, creating a
> maven project with arch type maven-archetype-webapp with artifactid of
> hallo word, produces the following issues:
>
> 1. src/main/java was not create
Hi,
> It looks fine:
Obviously not:
*snip*
>
> net.sourceforge.wurfl
> wurfl
> 1.4.0.1
>
This dependency doesn't exist on central; the latest version according to
http://search.maven.org/#search|ga|1|wurfl is 1.3.1.1
Regards
Thorsten___
Hi,
> I think eclipse does not know where to find my class files. It was
> advertised that you dont need to do mvn eclipse:eclipse anymore, so I
> didnt.
Did you enable Maven dependency management for your project at all?
I.e. right-click on your project => Configure => Convert to Maven Project
Hi,
> update:
>
> Changed wurfl from 1.4 to 1.3
> Ran Maven > Update Project..
> Fixed a wurfl coding change issue (red line)
> Ran Project > Clean
>
> problems:
> "The import javax.servlet.annotation cannot be resolved"
> "WebListener cannot be resolved to a type"
What do these problems tell y
Hi,
> Sure, I'll create a job and deploy it. I'll let you know if there
> are any problems.
What about my Axistools connector?
https://github.com/theit/m2e-lifecycle-axistools
I followed all the discussions recently, but I'm not sure if there's I
need to do...?
Apart from that, thanks for all
Hi Aaron,
> I am new here and m2e as well, I downloaded JUNO and installed m2e
latest
> version 1.2, but counter null point issue while doing some action.
What’s
> the stable suite for maven+eclipse+m2e ? btw, I still don’t know if all
> the usage guide for m2eclipse works for m2e.
A little
Hi,
> Anyone can provide me the recommended steps of installation of the
> m2e plugin. Like which update site(s) with what kind of
> preconditions and with what kind of orders?
This depends on which version and distribution of Eclipse you have
installed.
The simplest way is via the Marketplace
Hi,
> Marketplace Client isn't part of all Eclipse distributions ;)
Whoops, indeed, my bad :-)
But at least it can be installed separately:
http://www.eclipse.org/mpc/
=> http://download.eclipse.org/mpc/helios/ (for Eclipse 3.6)
=> http://download.eclipse.org/mpc/indigo/ (for Eclipse 3.7)
=> ht
Hi Ulrich,
> That's it. Now the pom.xml is in error with message:
> Multiple annotations found at this line:
> - Plugin execution not covered by lifecycle configuration:
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (execution: default-compile,
> phase: compile)
>
Hi,
> You are right; I need to use a proxy server to connect to the internet.
For my
> project, I don't need internet access. Why does Maven need it.
Maven needs either an Internet connection or a repository manager with a
valid Internet connection to download plugins for building your project.
Hi Ulrich,
> Thank you for the links.
You're welcome.
> It's almost exhausting. Now I'm down to the fourth
> level of application layer I need to know to do what I originally meant
to do:
> to work with CQ5.
> I will try to become familiar with the repository (I choosed archiva)
then. I
> had
Hi,
> I'm now directly connected to the Internet; it is still not possible
> to create a
> Java Package to crx/main/java - with the same errormessage.
^
If you haven't configured anything special in your pom.xml
(/), this should be src/main/java, not crx/...
> The
Hi,
> I believe Kepler comes with m2e 1.3. The subclipse scm connector
> does not work (install) with that version m2e, at least not when I
> checked a few days ago. I've fixed the subversive connector though
> and you can find it here:
> http://repository.tesla.io:8081/nexus/content/sites/m2e.
Hi,
> I fixed one of the subclipse connectors about a week ago, but as
> there are two of them out there we haven't been able to decide which
> one should go into the catalog. So for the time being you have to
> install it manually.
> Here's the one I've fixed and verified with m2e 1.3 and lates
Hi,
> That's the other one. More info about the discussion here:
> https://github.com/tesla/m2e-discovery-catalog/pull/15
Ok, thanks. I'll be watching this :-)
Thorsten___
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/li
Hi,
> Looks like a permission problem.
> Did you build it previously with another user ?
> Can you read/delete manually the files in the directory ?
>
> …
> Caused by: java.io.FileNotFoundException: D:\dev\workspace\SSORest
> Common Tools\target\classes (Access is denied)
Perhaps it's simply a
Hi,
I'm in the process of creating Maven builds for a few applications. These
applications use Ant build scripts to create WAR and EAR files.
Initial situation:
* All source code is stored in our Subversion repository.
* Each application depends on several internal projects P1, P2, ... that
a
Hello,
when I use the recently released maven-jar-plugin 3.0.0, Eclipse shows the
following error in the problems view after updating the project:
Error:
org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject,
org.apache.maven.archiver.MavenArchiveConfigurat
Hi,
> Please try the CI build from this p2 repo: https://otto.takari.io/
> content/sites/m2e.extras/m2eclipse-mavenarchiver/0.17.0/N/LATEST/
I just installed it, and the errors magically disappear :-)
Thanks for the fast fix!
Regards
Thorsten___
m2e
Hi,
using maven-jar-plugin version 3.0.1 inside Eclipse, I now get the
following error after updating my project(s):
Error message:
org.codehaus.plexus.archiver.jar.Manifest.write(java.io.PrintWriter)
Resource: pom.xml
Path: /
Location: line 1
Type: Maven Configuration Problem
This sounds like
Hi,
> I'm using
> - Eclipse Neon (4.6.0RC3)
> - m2e 1.7.0.20160531-2022
> - m2e connector for mavenarchiver from the link in MJAR-222
> - Java 1.8.0_92
>
>
> Side note:
> - Building from the command line works; the error only occurs in
Eclipse.
> - downgrading to 3.0.0 lets the error disappear
Hi Fred,
> 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/.
Great, the error disappears :-)
Thanks
Hi,
with the latest Eclipse 4.7 (Oxygen) milestone M6 I'm having problems
updating Maven projects that contain EAR modules:
Plug-in: org.eclipse.core.jobs
Severity: Error
Date: Fri Apr 07 07:52:16 CEST 2017
Message: An internal error occurred during: "Updating Maven Project".
Exception S
Hi,
> 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
Ok, thanks for these hints.
Best regards
Thors
s type to jar. Move all your web resources to
src/
> main/resources and reference :
>
>
> mygroup
> mvn-Q-resources
> jar
> /WEB-INF
>
> /xsl/**
>
>
>
> That s
hints what is causing this behaviour?
- Eclipse Oxygen (20170620-1800)
- m2e 1.8.1.20170728-1531
- m2e-wtp 1.3.2.20170517-2015
together with the m2e-wtp JAX-RS, JPA and JSF configurators for WTP
(same version)
- Oracle JDK 8u141
- Windows 8.1 x64
[1] https://wiki.eclipse.org/M2E-WTP
Regar
>
> On Thu, Aug 10, 2017 at 8:55 AM, Thorsten Heit
wrote:
> Hi,
>
> once again I'm having troubles with shared resources I'm using in a WAR
> project. The basic structure is:
>
> - mvn-p1-resources
> ...
> - mvn-pn-resources
> - app-main
&
Hi,
> Can you link to a sample project reproducing the issue?
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=521181
Regards
Thorsten___
m2e-users mailing list
m2e-users@eclipse.org
To change your delivery options, retrieve your password, or unsubs
Hi,
assume the following scenario:
Project A:
- older project, not fully modularized
- uses m-jar-p in the build section to add the entry
"Automatic-Module-Name" into its manifest
Project B:
- depends on A
- modular project
Project A can be compiled and deployed on the command line to my inter
Hi,
> 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 wr
Hi,
I see a strange behaviour in Eclipse (2019-03) that I don't know where it
comes from nor how to solve it:
Assume you have the following dependency in your pom.xml:
org.slf4j
slf4j-api
1.8.0-beta4
This Jar contains a module descriptor for Java >= 9 not in the root
Hi,
> 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.
Sorry for the late response because of easter weekend and a few days
off... ;-)
I just tried what you suggested: Same behaviour in a plain Java project.
I'
Hi,
> Hi,
>
> > 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.
>
> Sorry for the late response because of easter weekend and a few days
off... ;-)
>
> I just tried what you suggested: Same behaviour in
Hi,
> Every few weeks I run into a situation when I try to update plugins,
> where it gives various dependency errors that are effectively
> impossible for me to resolve on my own. The current one involves m2e.
>
> The error message in the update dialog says this:
> ---
> Cannot com
Hi,
I'm working on some projects that actually target Java 8, but are already
prepared to be used in modular applications, i.e. Java 11. I'm following
the multirelease/single project runtime pattern shown here:
https://github.com/apache/maven-compiler-plugin/blob/master/src/it/multirelease-patte
46 matches
Mail list logo
