• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

not sure where to run this VM Options line in Eclipse and what it is for ?

 
Ranch Hand
Posts: 821
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I need to set this line below in Eclipse but am unsure where to do it and would appreciate some help:



and there was also a step but i am not sure if i am running on ecalipse will it apply at all because it seems to be relevant to IntelliJ ide



So, I read that it is a maven plug in  and

Goal for generating IDEA files from a POM. This plug-in provides the ability to generate project files (.ipr, .iml and .iws files) for IDEA.

This IDEA is it referring to IntelliJ IDEA ?

How do I do it in the context of Eclipse?

Tks.
 
Saloon Keeper
Posts: 24321
167
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
To make a Maven project Eclipse-friendly, it's very simple:

And incidentally, since Eclipse and IntelliJ use separate project config files, a project can support Maven, Idea, and Eclipse all that the same time.

Eclipse keeps a collection of run/debug profiles ("Configurations") for applications and tasks that it executes. The same profile works for both run and debug - the only difference being whether the debugger is turned on when Eclipse executes the profile. Don't let the Run menu confuse you!

Since Maven is a Java application, when you run it as an Eclipse task, you can have a Run Configuration for Maven (there's a special category for Maven in the Run Configurations Dialog). You can give these configurations meaningful names, define the goal(s) that they will run  - and set VM parameters for the Maven run: it's on the second (JRE) tab of the Configuration details pane in the Run Configurations Dialog.
 
tangara goh
Ranch Hand
Posts: 821
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Tim Holloway wrote:To make a Maven project Eclipse-friendly, it's very simple:


Since Maven is a Java application, when you run it as an Eclipse task, you can have a Run Configuration for Maven (there's a special category for Maven in the Run Configurations Dialog). You can give these configurations meaningful names, define the goal(s) that they will run  - and set VM parameters for the Maven run: it's on the second (JRE) tab of the Configuration details pane in the Run Configurations Dialog.



Thanks Tim for the detailed explanation.

But, when I right click on run maven build, there are two maven build.  Which one should I use then ?
So far when I did mvn: eclipse:eclipse, it started to download alot of stuff and then it gives me a build failure....
the error is


Unknown lifecycle phase "mvn".  You must specify a lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. etc etc



Have I done things wrongly ?

Furthermore, I am not sure what the below lines mean :


Could you explain to me ? tks.

Besides that, I need to make Eclipse accept a cert..but I am not sure where to get the cert from ...I think it may have to do with the SSL thing... Could you let me know normally where is the cert come from?
Tks.
 
Tim Holloway
Saloon Keeper
Posts: 24321
167
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Only got TWO Maven build configurations? I had about 6 at one point.

Each Maven build configuration defines a specific set of Maven run options, including the goal(s), environment variables (if any) and so forth. Just pick the one that matches what you want to do.

Unknown lifecycle phase "mvn".  You must specify a lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. etc etc



That sounds like you explicitly typed "mvn" into your Maven run configuration dialog (probably in the "goals" control). It already knows its running Maven, so you don't need (want!) to do that.

The first time you run Maven, there will be a massive inrush of dependencies being downloaded. They get stored in your local Maven cache, however, so subsequent runs are much faster.

If you don't know what those JVM options are for, you probably shouldn't be using them at all. I was figuring that perhaps you were trying to pull extra stuff in from a third-party repository, but that's advanced work even for Maven old-timers.

Maven should generally be getting its SSL certs from the JVM's installed cert database that comes with Java itself and they're good enough for most purposes.

I'm adding this thread to our Maven forum, since I think you're beginning to cross over from Eclipse-specific questions to Maven-specific questions.
 
reply
    Bookmark Topic Watch Topic
  • New Topic