[RESULT] [VOTE] Retire Maven Eclipse Plugin / Donation to Mojohaus

[Robert Scholte]

Hi,

The vote has passed with the following result:

+1 (binding): Barrie Treloar, Arnaud Héritier, Tamás Cservenák, Dennis  
Lundberg, Hervé BOUTEMY, Olivier Lamy, Karl Heinz Marbaise, Kristian  
Rosenvold, Jason van Zyl, Robert Scholte
+1 (non binding): Tibor Digana, Anders Hammar, Michael Osipov, Andreas  
Gudian

+0.5 (non binding): Baptiste Mathus

thanks for the huge number of votes!!

I will continue with the steps required to retire this plugin.

Robert

Op Sun, 04 Oct 2015 11:18:55 +0200 schreef Robert Scholte  
<rfscho...@apache.org>:



Hi,

during the latest upgrade of the plugin-parent I faced several issues  
with the maven-eclipse-plugin.
It will take quite some time to fix these issues, but is it worth  
maintaining it here?

Nowadays the Maven support for Eclipse is good and stable.
The maven-eclipse-plugin has a lot of integration tests which should be  
rewritten, because it always launches a new Maven fork and it takes ages  
to complete. This simply blocks good continuous integration of the  
plugins.
I know there are still some projects with can't use the Maven  
Integration of Eclipse and depend on this plugin, so the sources need to  
stay available for users so the can extend it for their own usage.


I therefor propose that we retire maven-eclipse-plugin for the Apache  
Maven project and donate it to the Mojohaus project


If this vote is successful I will make one final release of the plugin,  
making
it clear on the plugin site that it has been retired. After that the  
source code

will be moved into the "retired" area in Subversion.

The process for retiring a plugin is described here:
http://maven.apache.org/developers/retirement-plan-plugins.html

The vote is open for 72 hours.

[ ] +1 Yes, it's about time
[ ] -1 No, because...

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Eclipse Plugin 2.10 Released

[Andreas Gudian]

The Apache Maven team is pleased to announce the release of the Apache
Maven Eclipse Plugin, version 2.10

This plugin is used to generate Eclipse IDE files (*.classpath, *.project,
*.wtpmodules and the .settings folder) for use with a project - if the M2E
Eclipse-Plugin does not fit you.

This release is the last one supporting Maven 2.

http://maven.apache.org/plugins/maven-eclipse-plugin/

You should specify the version in your project's plugin configuration:

plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-eclipse-plugin/artifactId
  version2.10/version
/plugin

Release Notes - Maven Eclipse Plugin - Version 2.10

** Bug
* [MECLIPSE-731] - eclipse:clean not deleting ./settings folder that it
creates
* [MECLIPSE-738] - NullPointerException in LinkedResource if
locationURI is present in .project

** Improvement
* [MECLIPSE-697] - Delete deprecated code
* [MECLIPSE-721] - Improve documentation to explain why Eclipse
sometimes does not import projects with correct project names.
* [MECLIPSE-754] - UPdate plexus-archiver to 2.9,plexus-utils to 3.0.18
and maven-archiver to 2.5
* [MECLIPSE-756] - Fix RAT Report
* [MECLIPSE-757] - Add proper classpath entry names for Java 7 / 8
* [MECLIPSE-758] - Use mojo annotations

** New Feature
* [MECLIPSE-759] - Add goal to resolve dependencies in .classpath files
of a workspace


Enjoy,

-The Apache Maven team

Re: M2Eclipse vs. maven-eclipse-plugin: which is preferred?

[Ron Wheeler]

If you just use the Eclipse/STS delivered by the Spring team, you get 
everything that you need to use Maven without worrying about plug-ins.


Ron

On 15/05/2014 7:50 PM, Barrie Treloar wrote:

On 9 May 2014 18:49, Thomas Broyer t.bro...@gmail.com wrote:


Hi all,

Does the Apache Maven Project/Community has an official stance about
whether M2Eclipse or maven-eclipse-plugin is preferred way of importing
Maven projects into Eclipse?

I thought M2Eclipse was the blessed way, but I cannot find anything
official online.
Only that the maven-eclipse-plugin hasn't been updated for a while, but
that could also be a sign that it has no issue and Eclipse offers backwards
compatibility.

Note: this is not a poll about what you as a developer prefers, I'm looking
for whether there's an official position and which one it is.
Background: I'm in a argument in a code review for an archetype about
whether to include maven-eclipse-plugin configuration within the POM or
not; and any official choice would help us avoid bikeshedding.


There isn't anything really official.

The maven-eclipse-plugin doesn't get much love any more these days, but
still works fine for some people.

However you will probably find the m2eclipse experience better.

Other alternatives to consider are other editors.
I've never used NetBeans or IntelliJ but others report good experiences.




--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: M2Eclipse vs. maven-eclipse-plugin: which is preferred?

[Barrie Treloar]

On 9 May 2014 18:49, Thomas Broyer t.bro...@gmail.com wrote:

 Hi all,

 Does the Apache Maven Project/Community has an official stance about
 whether M2Eclipse or maven-eclipse-plugin is preferred way of importing
 Maven projects into Eclipse?

 I thought M2Eclipse was the blessed way, but I cannot find anything
 official online.
 Only that the maven-eclipse-plugin hasn't been updated for a while, but
 that could also be a sign that it has no issue and Eclipse offers backwards
 compatibility.

 Note: this is not a poll about what you as a developer prefers, I'm looking
 for whether there's an official position and which one it is.
 Background: I'm in a argument in a code review for an archetype about
 whether to include maven-eclipse-plugin configuration within the POM or
 not; and any official choice would help us avoid bikeshedding.


There isn't anything really official.

The maven-eclipse-plugin doesn't get much love any more these days, but
still works fine for some people.

However you will probably find the m2eclipse experience better.

Other alternatives to consider are other editors.
I've never used NetBeans or IntelliJ but others report good experiences.

Re: M2Eclipse vs. maven-eclipse-plugin: which is preferred?

[Jason van Zyl]

There is nothing official from the Maven itself. There used to be competing 
Maven Eclipse integration from different people here, and there has always been 
the command line generation vs IDE integration. So there is no officially 
blessed integration from the Maven project proper.

Also note that M2Eclipse and the maven-eclipse-plugin are not compatible. In 
M2E it specifically looks for project files created with the 
maven-eclipse-plugin and disables them.

On May 9, 2014, at 2:19 AM, Thomas Broyer t.bro...@gmail.com wrote:

 Hi all,
 
 Does the Apache Maven Project/Community has an official stance about
 whether M2Eclipse or maven-eclipse-plugin is preferred way of importing
 Maven projects into Eclipse?
 
 I thought M2Eclipse was the blessed way, but I cannot find anything
 official online.
 Only that the maven-eclipse-plugin hasn't been updated for a while, but
 that could also be a sign that it has no issue and Eclipse offers backwards
 compatibility.
 
 Note: this is not a poll about what you as a developer prefers, I'm looking
 for whether there's an official position and which one it is.
 Background: I'm in a argument in a code review for an archetype about
 whether to include maven-eclipse-plugin configuration within the POM or
 not; and any official choice would help us avoid bikeshedding.
 
 
 -- 
 Thomas Broyer
 /tɔ.ma.bʁwa.je/ http://xn--nna.ma.xn--bwa-xxb.je/

Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

We all have problems. How we deal with them is a measure of our worth.

 -- Unknown

M2Eclipse vs. maven-eclipse-plugin: which is preferred?

[Thomas Broyer]

Hi all,

Does the Apache Maven Project/Community has an official stance about
whether M2Eclipse or maven-eclipse-plugin is preferred way of importing
Maven projects into Eclipse?

I thought M2Eclipse was the blessed way, but I cannot find anything
official online.
Only that the maven-eclipse-plugin hasn't been updated for a while, but
that could also be a sign that it has no issue and Eclipse offers backwards
compatibility.

Note: this is not a poll about what you as a developer prefers, I'm looking
for whether there's an official position and which one it is.
Background: I'm in a argument in a code review for an archetype about
whether to include maven-eclipse-plugin configuration within the POM or
not; and any official choice would help us avoid bikeshedding.


-- 
Thomas Broyer
/tɔ.ma.bʁwa.je/ http://xn--nna.ma.xn--bwa-xxb.je/

mvn-eclipse-plugin problem with pde projects and linked resources

[Jennifer Vendetti]

Hello,

I just took over the maintenance of several OSGi bundles.  I added the 
mvn-eclipse-plugin to the POM files for each of the bundles because I'd 
like to generate the necessary Eclipse project files to work with the 
source code and use the OSGi Framework launcher in the Eclipse IDE:


plugin
artifactIdmaven-eclipse-plugin/artifactId
version2.9/version
configuration
pdetrue/pde
/configuration
/plugin

For reasons I don't understand, running mvn eclipse:eclipse generates 
a .project file with an incomplete set of linked resources.  For 
example, I have a POM file for one of the bundles that has the following 
3 dependencies:


dependency
 groupIdlog4j/groupId
 artifactIdlog4j/artifactId
 version1.2.17/version
 /dependency

dependency
groupIdorg.apache.felix/groupId
artifactIdorg.apache.felix.main/artifactId
version4.2.1/version
/dependency

dependency
groupIdcom.jgoodies/groupId
artifactIdlooks/artifactId
version2.2.2/version
/dependency

The generated .project file for this bundle only has one linked resource 
to one of the artifacts:


?xml version=1.0 encoding=UTF-8?
projectDescription
  nameorg.protege.common/name
  commentCore Protege Libraries. NO_M2ECLIPSE_SUPPORT: Project files 
created with the maven-eclipse-plugin are not supported in 
M2Eclipse./comment

  projects/
  buildSpec
buildCommand
  nameorg.eclipse.jdt.core.javabuilder/name
/buildCommand
buildCommand
  nameorg.eclipse.pde.ManifestBuilder/name
/buildCommand
buildCommand
  nameorg.eclipse.pde.SchemaBuilder/name
/buildCommand
  /buildSpec
  natures
natureorg.eclipse.jdt.core.javanature/nature
natureorg.eclipse.pde.PluginNature/nature
  /natures
  linkedResources
link
  namelooks-2.2.2.jar/name
  type1/type
locationC:/Users/vendetti/.m2/repository/com/jgoodies/looks/2.2.2/looks-2.2.2.jar/location
/link
  /linkedResources
/projectDescription

When I try to import the existing PDE project into Eclipse, I get 
compiler errors since the other two artifacts aren't listed as linked 
resources.


Is there something I'm missing about how to properly use this plug-in?  
I'm using Maven version 3.1.0.  Any help and/or advice would be very 
much appreciated.


Jennifer




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: mvn-eclipse-plugin problem with pde projects and linked resources

[Alejandro . Endo]

I use pde + maven-bundle-plugin + osgi framework launcher but i don't use 
mvn-eclipse-plugin. You should be using m2e, which works completely 
different than m-eclipse-p. Just do a final eclipse:clean and forget about 
that plugin. 

Then make sure that your eclipse has m2e (comes by default with any recent 
eclipse) and do a File  import  maven  Existing Maven project if your 
project is already in the filesystem. If not choose checkout maven 
project from SCM instead

good luck
Alejandro Endo | Software Designer/Concepteur de logiciels




From:   Jennifer Vendetti vende...@stanford.edu
To: users@maven.apache.org, 
Date:   2013-10-23 03:49 PM
Subject:mvn-eclipse-plugin problem with pde projects and linked 
resources



Hello,

I just took over the maintenance of several OSGi bundles.  I added the 
mvn-eclipse-plugin to the POM files for each of the bundles because I'd 
like to generate the necessary Eclipse project files to work with the 
source code and use the OSGi Framework launcher in the Eclipse IDE:

plugin
artifactIdmaven-eclipse-plugin/artifactId
version2.9/version
configuration
pdetrue/pde
/configuration
/plugin

For reasons I don't understand, running mvn eclipse:eclipse generates 
a .project file with an incomplete set of linked resources.  For 
example, I have a POM file for one of the bundles that has the following 
3 dependencies:

dependency
  groupIdlog4j/groupId
  artifactIdlog4j/artifactId
  version1.2.17/version
  /dependency

dependency
groupIdorg.apache.felix/groupId
artifactIdorg.apache.felix.main/artifactId
version4.2.1/version
/dependency

dependency
groupIdcom.jgoodies/groupId
artifactIdlooks/artifactId
version2.2.2/version
/dependency

The generated .project file for this bundle only has one linked resource 
to one of the artifacts:

?xml version=1.0 encoding=UTF-8?
projectDescription
   nameorg.protege.common/name
   commentCore Protege Libraries. NO_M2ECLIPSE_SUPPORT: Project files 
created with the maven-eclipse-plugin are not supported in 
M2Eclipse./comment
   projects/
   buildSpec
 buildCommand
   nameorg.eclipse.jdt.core.javabuilder/name
 /buildCommand
 buildCommand
   nameorg.eclipse.pde.ManifestBuilder/name
 /buildCommand
 buildCommand
   nameorg.eclipse.pde.SchemaBuilder/name
 /buildCommand
   /buildSpec
   natures
 natureorg.eclipse.jdt.core.javanature/nature
 natureorg.eclipse.pde.PluginNature/nature
   /natures
   linkedResources
 link
   namelooks-2.2.2.jar/name
   type1/type
locationC:/Users/vendetti/.m2/repository/com/jgoodies/looks/2.2.2/looks-2.2.2.jar/location
 /link
   /linkedResources
/projectDescription

When I try to import the existing PDE project into Eclipse, I get 
compiler errors since the other two artifacts aren't listed as linked 
resources.

Is there something I'm missing about how to properly use this plug-in? 
I'm using Maven version 3.1.0.  Any help and/or advice would be very 
much appreciated.

Jennifer




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you are not the addressee of this message, you may not
copy, use or deliver this message to anyone. In such event, you
should destroy the message and kindly notify the sender by reply
e-mail. It is understood that opinions or conclusions that do not
relate to the official business of the company are neither given
nor endorsed by the company.
Thank You.

Re: mvn-eclipse-plugin problem with pde projects and linked resources

[Jennifer Vendetti]

Hello Alejandro,

Thank you very much for the reply, but there is something I don't 
understand.


I'm using Eclipse Kepler, which has m2e.  I tried what you suggested.  
Importing as existing Maven projects works very well, with all 
dependencies detected and no compilation errors.  However, since Eclipse 
sees these as Maven projects rather than PDE projects, I'm unable to 
create a new Runnable of type OSGi Framework in the Run Configurations 
dialog.  Eclipse doesn't detect my projects as bundles.


How are you able to create Runnables with the OSGi Framework launcher?  
Any guidance is very much appreciated.


Best,
Jennifer


On 10/23/2013 12:56 PM, alejandro.e...@miranda.com wrote:

I use pde + maven-bundle-plugin + osgi framework launcher but i don't use
mvn-eclipse-plugin. You should be using m2e, which works completely
different than m-eclipse-p. Just do a final eclipse:clean and forget about
that plugin.

Then make sure that your eclipse has m2e (comes by default with any recent
eclipse) and do a File  import  maven  Existing Maven project if your
project is already in the filesystem. If not choose checkout maven
project from SCM instead

good luck
Alejandro Endo | Software Designer/Concepteur de logiciels




From:   Jennifer Vendetti vende...@stanford.edu
To: users@maven.apache.org,
Date:   2013-10-23 03:49 PM
Subject:mvn-eclipse-plugin problem with pde projects and linked
resources



Hello,

I just took over the maintenance of several OSGi bundles.  I added the
mvn-eclipse-plugin to the POM files for each of the bundles because I'd
like to generate the necessary Eclipse project files to work with the
source code and use the OSGi Framework launcher in the Eclipse IDE:

plugin
artifactIdmaven-eclipse-plugin/artifactId
version2.9/version
configuration
pdetrue/pde
/configuration
/plugin

For reasons I don't understand, running mvn eclipse:eclipse generates
a .project file with an incomplete set of linked resources.  For
example, I have a POM file for one of the bundles that has the following
3 dependencies:

dependency
   groupIdlog4j/groupId
   artifactIdlog4j/artifactId
   version1.2.17/version
   /dependency

dependency
groupIdorg.apache.felix/groupId
artifactIdorg.apache.felix.main/artifactId
version4.2.1/version
/dependency

dependency
groupIdcom.jgoodies/groupId
artifactIdlooks/artifactId
version2.2.2/version
/dependency

The generated .project file for this bundle only has one linked resource
to one of the artifacts:

?xml version=1.0 encoding=UTF-8?
projectDescription
nameorg.protege.common/name
commentCore Protege Libraries. NO_M2ECLIPSE_SUPPORT: Project files
created with the maven-eclipse-plugin are not supported in
M2Eclipse./comment
projects/
buildSpec
  buildCommand
nameorg.eclipse.jdt.core.javabuilder/name
  /buildCommand
  buildCommand
nameorg.eclipse.pde.ManifestBuilder/name
  /buildCommand
  buildCommand
nameorg.eclipse.pde.SchemaBuilder/name
  /buildCommand
/buildSpec
natures
  natureorg.eclipse.jdt.core.javanature/nature
  natureorg.eclipse.pde.PluginNature/nature
/natures
linkedResources
  link
namelooks-2.2.2.jar/name
type1/type
locationC:/Users/vendetti/.m2/repository/com/jgoodies/looks/2.2.2/looks-2.2.2.jar/location
  /link
/linkedResources
/projectDescription

When I try to import the existing PDE project into Eclipse, I get
compiler errors since the other two artifacts aren't listed as linked
resources.

Is there something I'm missing about how to properly use this plug-in?
I'm using Maven version 3.1.0.  Any help and/or advice would be very
much appreciated.

Jennifer




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you are not the addressee of this message, you may not
copy, use or deliver this message to anyone. In such event, you
should destroy the message and kindly notify the sender by reply
e-mail. It is understood that opinions or conclusions that do not
relate to the official business of the company are neither given
nor endorsed by the company.
Thank You.




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: mvn-eclipse-plugin problem with pde projects and linked resources

[Alejandro . Endo]

it all depends if you are going the maven bundle plugin route (which is 
POM-centric and the manifest is auto generated) or manifest first, where 
the manifest is generated by hand (eclipse tooling helps with this though) 
and the pom is also generated by hand but it has a much smaller role (to 
be exact, there is a way to generate the pom, but you generate it once and 
manage it by hand after, whereas in the first way you never manage the 
manifest and it gets regenerated every time you build, in fact, you don't 
even commit the manifest in your VCS). The major difference is where are 
the dependencies managed. So this is the first decision you will need to 
make, if you haven't already made it
https://docs.sonatype.org/display/TYCHO/OSGiDevelopmentWithMaven
http://stackoverflow.com/questions/11373009/should-i-use-pom-first-or-manifest-first-when-developing-osgi-application-with-m

For the launcher to recognize the project as a bundle I think you just 
need the META-INF folder in the root of the project with an osgi-friendly 
MANIFEST.MF inside

I'm not sure what you mean by Runnables, you mean a new launcher? the fact 
that you capitalise it makes me think of the java interface, but i don't 
see the connection

good luck,
Alejandro Endo | Software Designer/Concepteur de logiciels
Miranda Technologies is a brand of Belden Inc. 



From:   Jennifer Vendetti vende...@stanford.edu
To: Maven Users List users@maven.apache.org, 
Date:   2013-10-23 04:20 PM
Subject:Re: mvn-eclipse-plugin problem with pde projects and 
linked resources



Hello Alejandro,

Thank you very much for the reply, but there is something I don't 
understand.

I'm using Eclipse Kepler, which has m2e.  I tried what you suggested. 
Importing as existing Maven projects works very well, with all 
dependencies detected and no compilation errors.  However, since Eclipse 
sees these as Maven projects rather than PDE projects, I'm unable to 
create a new Runnable of type OSGi Framework in the Run Configurations 
dialog.  Eclipse doesn't detect my projects as bundles.

How are you able to create Runnables with the OSGi Framework launcher? 
Any guidance is very much appreciated.

Best,
Jennifer


On 10/23/2013 12:56 PM, alejandro.e...@miranda.com wrote:
 I use pde + maven-bundle-plugin + osgi framework launcher but i don't 
use
 mvn-eclipse-plugin. You should be using m2e, which works completely
 different than m-eclipse-p. Just do a final eclipse:clean and forget 
about
 that plugin.

 Then make sure that your eclipse has m2e (comes by default with any 
recent
 eclipse) and do a File  import  maven  Existing Maven project if your
 project is already in the filesystem. If not choose checkout maven
 project from SCM instead

 good luck
 Alejandro Endo | Software Designer/Concepteur de logiciels




 From:   Jennifer Vendetti vende...@stanford.edu
 To: users@maven.apache.org,
 Date:   2013-10-23 03:49 PM
 Subject:mvn-eclipse-plugin problem with pde projects and linked
 resources



 Hello,

 I just took over the maintenance of several OSGi bundles.  I added the
 mvn-eclipse-plugin to the POM files for each of the bundles because I'd
 like to generate the necessary Eclipse project files to work with the
 source code and use the OSGi Framework launcher in the Eclipse IDE:

 plugin
 artifactIdmaven-eclipse-plugin/artifactId
 version2.9/version
 configuration
 pdetrue/pde
 /configuration
 /plugin

 For reasons I don't understand, running mvn eclipse:eclipse generates
 a .project file with an incomplete set of linked resources.  For
 example, I have a POM file for one of the bundles that has the following
 3 dependencies:

 dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
version1.2.17/version
/dependency

 dependency
 groupIdorg.apache.felix/groupId
 artifactIdorg.apache.felix.main/artifactId
 version4.2.1/version
 /dependency

 dependency
 groupIdcom.jgoodies/groupId
 artifactIdlooks/artifactId
 version2.2.2/version
 /dependency

 The generated .project file for this bundle only has one linked resource
 to one of the artifacts:

 ?xml version=1.0 encoding=UTF-8?
 projectDescription
 nameorg.protege.common/name
 commentCore Protege Libraries. NO_M2ECLIPSE_SUPPORT: Project files
 created with the maven-eclipse-plugin are not supported in
 M2Eclipse./comment
 projects/
 buildSpec
   buildCommand
 nameorg.eclipse.jdt.core.javabuilder/name
   /buildCommand
   buildCommand
 nameorg.eclipse.pde.ManifestBuilder/name
   /buildCommand
   buildCommand
 nameorg.eclipse.pde.SchemaBuilder/name
   /buildCommand
 /buildSpec
 natures
   natureorg.eclipse.jdt.core.javanature/nature
   natureorg.eclipse.pde.PluginNature/nature
 /natures
 linkedResources
   link
 namelooks-2.2.2.jar/name
 type1/type
 
locationC:/Users/vendetti/.m2/repository/com/jgoodies/looks/2.2.2/looks-2.2.2.jar/location
   /link

Re: mvn-eclipse-plugin problem with pde projects and linked resources

[Barrie Treloar]

 Oddly, the bundles run fine outside of the Eclipse environment.  My first
 few attempts at using the OSGi Framework launcher has left me with a slew
 of ClassNotFoundException errors at runtime.  Will need to investigate this
 further.

 Thanks for your help in getting me this far along.


Please post your problems and resolutions here.

Getting Eclipse PDE to work with Maven is still not an easy task and the
more material for google searches the better.

Re: maven-eclipse-plugin - configure source and output-folders

[Jörg Schaible]

Hi Andreas,

Andreas Dolk wrote:

 Hi all,
 
 we have a rather complex project structure with a lot of projects and a
 couple of code generators that produce java classes for production and
 test. The challenge now is to configure the build files so that a mvn
 eclipse:eclipse run will create all required source folders and set the
 correct output folders, for example:
 
 src folder: src/main/code-gen
 out folder: (default) - target/classes
 
 src folder: src/test/code-gen
 out folder: target/test-classes
 
 Currently we use the maven build helper to set the source folders but I
 still don't know how to set the out dirs - now it creates a project config
 that compiles production and test classes into the same out folder which
 actually causes conflicts.

Isn't that automatically done using build-helper:add-source vs. build-
helper:add-test-source?

 Is there any way to fine-tune the .classpath file programmatically?

- Jörg


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-eclipse-plugin - configure source and output-folders

[Daniel Kulp]

On Oct 4, 2013, at 5:18 PM, Andreas Dolk andreas.dolk.mo...@googlemail.com 
wrote:

 Hi all,
 
 we have a rather complex project structure with a lot of projects and a
 couple of code generators that produce java classes for production and
 test. The challenge now is to configure the build files so that a mvn
 eclipse:eclipse run will create all required source folders and set the
 correct output folders, for example:

What happens if you run:

mvn test-compile eclipse:eclipse 

instead of just

mvn eclipse:eclipse


By default, eclipse:eclipse just runs far enough to get the source directories, 
not all the test directories.   If you force maven to run to the test-compile 
phase, then it should be able to pick everything up.

Dan



 
 src folder: src/main/code-gen
 out folder: (default) - target/classes
 
 src folder: src/test/code-gen
 out folder: target/test-classes
 
 Currently we use the maven build helper to set the source folders but I
 still don't know how to set the out dirs - now it creates a project config
 that compiles production and test classes into the same out folder which
 actually causes conflicts.
 
 Is there any way to fine-tune the .classpath file programmatically?
 
 Cheers,
 
 Andreas

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-eclipse-plugin - configure source and output-folders

[Wayne Fay]

 test. The challenge now is to configure the build files so that a mvn
 eclipse:eclipse run will create all required source folders and set the
 correct output folders, for example:

Are you aware of m2e and other options for using Maven in Eclipse? I'm
just not convinced you will get what you want from m-e-p in any
reasonable timeframe without adjusting the code yourself and donating
changes back.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

maven-eclipse-plugin - configure source and output-folders

[Andreas Dolk]

Hi all,

we have a rather complex project structure with a lot of projects and a
couple of code generators that produce java classes for production and
test. The challenge now is to configure the build files so that a mvn
eclipse:eclipse run will create all required source folders and set the
correct output folders, for example:

src folder: src/main/code-gen
out folder: (default) - target/classes

src folder: src/test/code-gen
out folder: target/test-classes

Currently we use the maven build helper to set the source folders but I
still don't know how to set the out dirs - now it creates a project config
that compiles production and test classes into the same out folder which
actually causes conflicts.

Is there any way to fine-tune the .classpath file programmatically?

Cheers,

Andreas

eclipse plugin SUCCESS but no project?

[Giovanni Azua]

Hello,

I am trying to build Spring RCP and I'm very interested in the
spring-richclient-jide-sample-google but when I run the following I see
SUCCESS but no project? How can I troubleshoot this?

TIA,
Best regards,
Giovanni

/Users/bravegag/code/spring-rich-c/tags/spring-richclient-1.1.0/spring-richclient/spring-richclient-integrations/spring-richclient-jide/spring-richclient-jide-samples/spring-richclient-jide-sample-google$
$M2_HOME/bin/mvn eclipse:eclipse -DdownloadSources=true
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for
org.springframework.richclient:spring-richclient-jide-sample-google:pom:1.1.0
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing. @
org.springframework.richclient:spring-richclient:1.1.0,
/Users/bravegag/code/spring-rich-c/tags/spring-richclient-1.1.0/spring-richclient/pom.xml,
line 468, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]

[INFO]

[INFO] Building Spring Rich Client integrations : JIDE Google Sample 1.1.0
[INFO]

[INFO]
[INFO]  maven-eclipse-plugin:2.5.1:eclipse (default-cli) @
spring-richclient-jide-sample-google 
[INFO]
[INFO]  maven-eclipse-plugin:2.5.1:eclipse (default-cli) @
spring-richclient-jide-sample-google 
[INFO]
[INFO] --- maven-eclipse-plugin:2.5.1:eclipse (default-cli) @
spring-richclient-jide-sample-google ---
[INFO] Not running eclipse plugin goal for pom project
[INFO] Using as WTP server : null
[INFO] Adding default classpath contaigner:
org.eclipse.jdt.launching.JRE_CONTAINER
[INFO]

[INFO] BUILD SUCCESS
[INFO]

[INFO] Total time: 1.928s
[INFO] Finished at: Tue May 07 11:53:10 CEST 2013
[INFO] Final Memory: 6M/528M
[INFO]

/Users/bravegag/code/spring-rich-c/tags/spring-richclient-1.1.0/spring-richclient/spring-richclient-integrations/spring-richclient-jide/spring-richclient-jide-samples/spring-richclient-jide-sample-google$
ll
total 8
drwxr-xr-x  5 bravegag  staff   170 May  7 11:37 .
drwxr-xr-x  5 bravegag  staff   170 May  7 11:30 ..
-rw-r--r--  1 bravegag  staff  3141 May  7 11:30 pom.xml
drwxr-xr-x  9 bravegag  staff   306 May  7 11:17 .svn
drwxr-xr-x  4 bravegag  staff   136 May  7 11:17 src
/Users/bravegag/code/spring-rich-c/tags/spring-richclient-1.1.0/spring-richclient/spring-richclient-integrations/spring-richclient-jide/spring-richclient-jide-samples/spring-richclient-jide-sample-google$

Re: eclipse plugin SUCCESS but no project?

[Wayne Fay]

 I am trying to build Spring RCP and I'm very interested in the
 spring-richclient-jide-sample-google but when I run the following I see
 SUCCESS but no project? How can I troubleshoot this?
...
 [INFO] --- maven-eclipse-plugin:2.5.1:eclipse (default-cli) @
 spring-richclient-jide-sample-google ---
 [INFO] Not running eclipse plugin goal for pom project

Apparently the eclipse plugin does not run the eclipse goal for pom
projects. Can I suggest you simply use M2E like everyone else?

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: eclipse plugin SUCCESS but no project?

[Giovanni Azua]

Hi Wayne,

Thank you. I tried that using Import - Maven - Existing Maven Project
then choose the corresponding directory but the dependencies are not
resolved even though they are all in the local repo and all other projects
above this where generated using the eclipse plugin and work fine i.e.
compile from Eclipse np.

Best regards,
Giovanni


On Tue, May 7, 2013 at 4:24 PM, Wayne Fay wayne...@gmail.com wrote:

  I am trying to build Spring RCP and I'm very interested in the
  spring-richclient-jide-sample-google but when I run the following I see
  SUCCESS but no project? How can I troubleshoot this?
 ...
  [INFO] --- maven-eclipse-plugin:2.5.1:eclipse (default-cli) @
  spring-richclient-jide-sample-google ---
  [INFO] Not running eclipse plugin goal for pom project

 Apparently the eclipse plugin does not run the eclipse goal for pom
 projects. Can I suggest you simply use M2E like everyone else?

 Wayne

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Re: eclipse plugin SUCCESS but no project?

[Ron Wheeler]

You might also try the Eclipse STS from Spring.
It has everything that you need for developing Spring applications with 
Maven, all packaged up in a single download.


Ron


On
 07/05/2013 10:38 AM, Giovanni Azua wrote:

Hi Wayne,

Thank you. I tried that using Import - Maven - Existing Maven Project
then choose the corresponding directory but the dependencies are not
resolved even though they are all in the local repo and all other projects
above this where generated using the eclipse plugin and work fine i.e.
compile from Eclipse np.

Best regards,
Giovanni


On Tue, May 7, 2013 at 4:24 PM, Wayne Fay wayne...@gmail.com wrote:


I am trying to build Spring RCP and I'm very interested in the
spring-richclient-jide-sample-google but when I run the following I see
SUCCESS but no project? How can I troubleshoot this?

...

[INFO] --- maven-eclipse-plugin:2.5.1:eclipse (default-cli) @
spring-richclient-jide-sample-google ---
[INFO] Not running eclipse plugin goal for pom project

Apparently the eclipse plugin does not run the eclipse goal for pom
projects. Can I suggest you simply use M2E like everyone else?

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: eclipse plugin SUCCESS but no project?

[Wayne Fay]

 Thank you. I tried that using Import - Maven - Existing Maven Project
 then choose the corresponding directory but the dependencies are not
 resolved even though they are all in the local repo and all other projects
 above this where generated using the eclipse plugin and work fine i.e.
 compile from Eclipse np.

I have no relationship to M2E so you'd have to ask the Eclipse
Foundation for support there. Or ask for help in the Spring RCP
forums.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Eclipse plugin and project references

[Stiffler82]

I have a problem and can not find any support for it, also not in google. I
created my own lib called core.jar and when I try to refer it as a
dependency in from my POM all works fine: 

dependency
   groupIdcom.innosquared/groupId
   artifactIdcore/artifactId
   version1.1.10/version
/dependency

But when I run mvn eclipse:eclipse Maven creates wrong .classpath and
.project files. It resolves my jar as a java project instead of a jar
library. The following entry will be created in my classpath:

  classpathentry kind=src path=/core/

In my .projects file there is now:

 projects
projectcore/project
  /projects

I do not define anything in my Build-Cycle in POM, so I don't understand
this strange behaviour. What can I do to prevent Maven from resolving my jar
as a java project and resolving it as a normal dependency instead?



--
View this message in context: 
http://maven.40175.n5.nabble.com/Eclipse-plugin-and-project-references-tp99838p5748396.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Eclipse plugin and project references

[Andreas Gudian]

The plugin will always resolve the artifact as eclipse project, if it
detects that project within your eclipse workspace, or if it is in the
reactor (i.e. part of the maven build).
Remove the other project from the workspace and you should be fine. Or make
sure that core now has a new version (it should be some -SNAPSHOT version
after you created that 1.1.10 version, right?)

Andreas

2013/2/25 Stiffler82 hauptstep...@gmail.com

 I have a problem and can not find any support for it, also not in google. I
 created my own lib called core.jar and when I try to refer it as a
 dependency in from my POM all works fine:

 dependency
groupIdcom.innosquared/groupId
artifactIdcore/artifactId
version1.1.10/version
 /dependency

 But when I run mvn eclipse:eclipse Maven creates wrong .classpath and
 .project files. It resolves my jar as a java project instead of a jar
 library. The following entry will be created in my classpath:

   classpathentry kind=src path=/core/

 In my .projects file there is now:

  projects
 projectcore/project
   /projects

 I do not define anything in my Build-Cycle in POM, so I don't understand
 this strange behaviour. What can I do to prevent Maven from resolving my
 jar
 as a java project and resolving it as a normal dependency instead?



 --
 View this message in context:
 http://maven.40175.n5.nabble.com/Eclipse-plugin-and-project-references-tp99838p5748396.html
 Sent from the Maven - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Re: Eclipse plugin and project references

[Lyons, Roy]

From my experience to date, it has proven far better to use the m2eclipse
plugin and import the maven project directly.  It will then perform the
build using maven...

When people come to me with issues such as yours, I generally tell them to
delete the project and re-import using m2eclipse (and never use mvn
eclipse:eclipse again) -- and then everything works wonderfully for them.


Thanks,

Roy Lyons




On 2/25/13 11:03 AM, Stiffler82 hauptstep...@gmail.com wrote:

I have a problem and can not find any support for it, also not in google.
I
created my own lib called core.jar and when I try to refer it as a
dependency in from my POM all works fine:

   dependency
  groupIdcom.innosquared/groupId
  artifactIdcore/artifactId
  version1.1.10/version
   /dependency

But when I run mvn eclipse:eclipse Maven creates wrong .classpath and
.project files. It resolves my jar as a java project instead of a jar
library. The following entry will be created in my classpath:

  classpathentry kind=src path=/core/

In my .projects file there is now:

 projects
projectcore/project
  /projects

I do not define anything in my Build-Cycle in POM, so I don't understand
this strange behaviour. What can I do to prevent Maven from resolving my
jar
as a java project and resolving it as a normal dependency instead?



--
View this message in context:
http://maven.40175.n5.nabble.com/Eclipse-plugin-and-project-references-tp9
9838p5748396.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Eclipse plugin and project references

[Baptiste MATHUS]

+1.
Even the maven-eclipse-plugin developers advice to use M2Eclipse instead.

Cheers


2013/2/25 Lyons, Roy roy.ly...@cmegroup.com

 From my experience to date, it has proven far better to use the m2eclipse
 plugin and import the maven project directly.  It will then perform the
 build using maven...

 When people come to me with issues such as yours, I generally tell them to
 delete the project and re-import using m2eclipse (and never use mvn
 eclipse:eclipse again) -- and then everything works wonderfully for them.


 Thanks,

 Roy Lyons




 On 2/25/13 11:03 AM, Stiffler82 hauptstep...@gmail.com wrote:

 I have a problem and can not find any support for it, also not in google.
 I
 created my own lib called core.jar and when I try to refer it as a
 dependency in from my POM all works fine:
 
dependency
   groupIdcom.innosquared/groupId
   artifactIdcore/artifactId
   version1.1.10/version
/dependency
 
 But when I run mvn eclipse:eclipse Maven creates wrong .classpath and
 .project files. It resolves my jar as a java project instead of a jar
 library. The following entry will be created in my classpath:
 
   classpathentry kind=src path=/core/
 
 In my .projects file there is now:
 
  projects
 projectcore/project
   /projects
 
 I do not define anything in my Build-Cycle in POM, so I don't understand
 this strange behaviour. What can I do to prevent Maven from resolving my
 jar
 as a java project and resolving it as a normal dependency instead?
 
 
 
 --
 View this message in context:
 
 http://maven.40175.n5.nabble.com/Eclipse-plugin-and-project-references-tp9
 9838p5748396.html
 Sent from the Maven - Users mailing list archive at Nabble.com.
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-- 
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

maven-eclipse-plugin generates wrong eclipse project

[Nikolay Skachkov]

Hi!

I have a source directory structure like below (1). 
I have maven project that compiles uses include in the pom.xml and all builds 
OK. When I run mvn eclipse:eclipse in same directory I do not get a usable 
Eclipse project. The classes dir after compilation looks like (2). I suggest 
that in general maven-eclipse-pluging would like to accept any maven project 
that is accepted by maven.

Is there anyone who can advice about it?  

1)
+---gen
|   \---com
|       \---HybridJava
|           \---Sample
|                   A.java
+---src
|   \---com
|       \---HybridJava
|           \---Sample
|                   B.java

2)
+---classes
|   +---gen
|   |   \---com
|   |       \---HybridJava
|   |           \---Sample
|   |                   A.class
|   +---src
|   |   \---com
|   |       \---HybridJava
|   |           \---Sample
|   |                   B.class

Nikolay





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: JDT compiler compliance level as a parameter for eclipse:eclipse target of maven-eclipse-plugin

[Mikhail Kalkov]

Thanks for suggestions, Barrie and Wayne! I will have a look at 
maven-eclipse-plugin source code later.

To clarify,
  source1.5/source corresponds to javac -source option and to ECJ 
org.eclipse.jdt.core.compiler.source setting
  target1.6/target corresponds to javac -target option and to ECJ 
org.eclipse.jdt.core.compiler.codegen.targetPlatform setting
  org.eclipse.jdt.core.compiler.compliance is an ECJ setting, which doesn't 
have a direct counterpart either in javac options or in maven-compiler-plugin 
settings. I've really tried hard to figure out what exactly it means but 
Eclipse documentation [1] is vague about the meaning of this option. According 
to the JDT settings compatibility table [2], codegen.targetPlatform specifies 
the target VM version, and should never be less then the source version, 
whereas the source version and compliance settings are quite similar, but the 
former seems to be a refinement of the latter. After reading [3], [4] and [5] 
my best guess is that
   - compliance corresponds to Java language version,
   - source corresponds to Java class library version (see -bootclasspath 
option for javac),
   - target corresponds to Java VM version,
   - and Execution Environment setting would correspond to Java runtime version 
(see [6]).

At least, this explanation clarifies why I was able to use Java6 syntax sugar 
(@Override on interface implementation) with compliance set to 1.6, whereas 
source and target were set to 1.5. Still I may be wrong and the only way to get 
an authoritative answer is to ask on the JDT DEV mailing list. I'll ask them 
and hopefully come back later with an answer.

As for Sun's javac, it seems that compliance is always set to the jdk level, 
e.g. javac -source 1.5 -target 1.5 with javac from jdk6u27 allows using 
@Override annotation on interface implementation.

[1] 
http://help.eclipse.org/juno/topic/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-compiler.htm
[2] Open 
http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.jdt.doc.isv%2Fguide%2Fjdt_api_options.htm
 , scroll down to JDT Core options descriptions, click on Builder options 
and scroll a bit up to see the compatibility table
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=323633#c23
[4] 
http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.7/org.eclipse.jdt/core/3.7.0/org/eclipse/jdt/internal/compiler/batch/Main.java#Main.validateOptions%28boolean%29
[5] http://wiki.eclipse.org/index.php/Execution_Environment
[6] http://wiki.eclipse.org/PDE/Resources/Execution_Environments

Regards,
Mikhail

- Original Message -
From: Barrie Treloar baerr...@gmail.com
To: Maven Users List users@maven.apache.org
Sent: Friday, July 27, 2012 12:29:04 AM
Subject: Re: JDT compiler compliance level as a parameter for eclipse:eclipse 
target of maven-eclipse-plugin

On Fri, Jul 27, 2012 at 7:57 AM, Barrie Treloar baerr...@gmail.com wrote:
 On Fri, Jul 27, 2012 at 7:13 AM, Wayne Fay wayne...@gmail.com wrote:
 Long story short, I tried to modify eclipse project generation so that
 in the .settings/org.eclipse.jdt.core.prefs instead of this:
 org.eclipse.jdt.core.compiler.compliance=1.5
 I get this (look at the compliance):
 org.eclipse.jdt.core.compiler.compliance=1.6
 but didn't find a way to configure maven-eclipse-plugin.

 Most likely you are the first person to want this specific
 configuration of the plugin, thus it does not currently exist. You'll
 probably need to scratch your own itch.

 Pull down the source code for maven-eclipse-plugin, tweak it somehow
 to add this feature, and contribute the code back for (possible)
 inclusion in a future release.

 Here's a hint: you're going to want to adjust EclipseSettingsWriter
 and probably some Eclipse plugin Mojo code too since this should be an
 extra configuration item in the plugin...
 http://maven.apache.org/plugins/maven-eclipse-plugin/xref/org/apache/maven/plugin/eclipse/writers/workspace/EclipseSettingsWriter.html

 Also remember, that the maven-eclipse-plugin reads the configuration
 of the maven-compiler-plugin.
 See 
 http://maven.apache.org/plugins/maven-eclipse-plugin/trouble-shooting/jdk-being-used-is-different-than-expected.html

 So you ideally need to configure that the way you want.
 I'm not sure what
 org.eclipse.jdt.core.compiler.compliance=1.6
 actually does.
 Is this equivalent to

 plugin
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.6/target
/configuration
 /plugin

Alternatively, you can fix your problem with the overrides and mark it
as something to worry about manually.
The time invested to fix this automatically may not be worth the effort.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

JDT compiler compliance level as a parameter for eclipse:eclipse target of maven-eclipse-plugin

[Mikhail Kalkov]

Hi,

I've tried to checkout Jenkins CI source code and generate an Eclipse project 
for it (see instructions in [1]). Unfortunately generated Eclipse projects 
seemed to contain errors, which I first reported as a Jenkins bug [2]. Further 
investigation revealed that even though Jenkins is build with javac -source 
1.5 -target 1.5 parameters, they use javac from JDK6u18 or later and rely on 
animal-sniffer plug-in to ensure that their code is java5-compliant. 
Unfortunately, it seems that neither Sun's javac nor Animal Sniffer noticed the 
presence of @Override annotations on methods implementing interfaces, which is 
not allowed in Java 5 and is ok in Java 6 [3]. On the other hand, Eclipse Java 
Compiler does notice them and mark each one as error.

Long story short, I tried to modify eclipse project generation so that in the 
.settings/org.eclipse.jdt.core.prefs instead of this:
org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.5
eclipse.preferences.version=1
org.eclipse.jdt.core.compiler.source=1.5
org.eclipse.jdt.core.compiler.compliance=1.5
I get this (look at the compliance):
org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.5
eclipse.preferences.version=1
org.eclipse.jdt.core.compiler.source=1.5
org.eclipse.jdt.core.compiler.compliance=1.6
but didn't find a way to configure maven-eclipse-plugin.

Has anybody else experienced this problem? Can you suggest any ideas?

[1] https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins
[2] https://issues.jenkins-ci.org/browse/JENKINS-14579
[3] http://stackoverflow.com/questions/8220786/java-eclipse-override-error

Kind regards,
Mikhail Kalkov

Purple Scout AB
Software Developer

Address: Östra Hamngatan 31, SE- 41110 Gothenburg, Sweden
Phone:   +46 (0) 732 - 051405
E-mail:  mikhail.kal...@purplescout.se
Web: www.purplescout.se

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: JDT compiler compliance level as a parameter for eclipse:eclipse target of maven-eclipse-plugin

[Wayne Fay]

 Long story short, I tried to modify eclipse project generation so that
 in the .settings/org.eclipse.jdt.core.prefs instead of this:
 org.eclipse.jdt.core.compiler.compliance=1.5
 I get this (look at the compliance):
 org.eclipse.jdt.core.compiler.compliance=1.6
 but didn't find a way to configure maven-eclipse-plugin.

Most likely you are the first person to want this specific
configuration of the plugin, thus it does not currently exist. You'll
probably need to scratch your own itch.

Pull down the source code for maven-eclipse-plugin, tweak it somehow
to add this feature, and contribute the code back for (possible)
inclusion in a future release.

Here's a hint: you're going to want to adjust EclipseSettingsWriter
and probably some Eclipse plugin Mojo code too since this should be an
extra configuration item in the plugin...
http://maven.apache.org/plugins/maven-eclipse-plugin/xref/org/apache/maven/plugin/eclipse/writers/workspace/EclipseSettingsWriter.html

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: JDT compiler compliance level as a parameter for eclipse:eclipse target of maven-eclipse-plugin

[Barrie Treloar]

On Fri, Jul 27, 2012 at 7:13 AM, Wayne Fay wayne...@gmail.com wrote:
 Long story short, I tried to modify eclipse project generation so that
 in the .settings/org.eclipse.jdt.core.prefs instead of this:
 org.eclipse.jdt.core.compiler.compliance=1.5
 I get this (look at the compliance):
 org.eclipse.jdt.core.compiler.compliance=1.6
 but didn't find a way to configure maven-eclipse-plugin.

 Most likely you are the first person to want this specific
 configuration of the plugin, thus it does not currently exist. You'll
 probably need to scratch your own itch.

 Pull down the source code for maven-eclipse-plugin, tweak it somehow
 to add this feature, and contribute the code back for (possible)
 inclusion in a future release.

 Here's a hint: you're going to want to adjust EclipseSettingsWriter
 and probably some Eclipse plugin Mojo code too since this should be an
 extra configuration item in the plugin...
 http://maven.apache.org/plugins/maven-eclipse-plugin/xref/org/apache/maven/plugin/eclipse/writers/workspace/EclipseSettingsWriter.html

Also remember, that the maven-eclipse-plugin reads the configuration
of the maven-compiler-plugin.
See 
http://maven.apache.org/plugins/maven-eclipse-plugin/trouble-shooting/jdk-being-used-is-different-than-expected.html

So you ideally need to configure that the way you want.
I'm not sure what
org.eclipse.jdt.core.compiler.compliance=1.6
actually does.
Is this equivalent to

plugin
   artifactIdmaven-compiler-plugin/artifactId
   version2.0.2/version
   configuration
   source1.5/source
   target1.6/target
   /configuration
/plugin

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: JDT compiler compliance level as a parameter for eclipse:eclipse target of maven-eclipse-plugin

[Barrie Treloar]

On Fri, Jul 27, 2012 at 7:57 AM, Barrie Treloar baerr...@gmail.com wrote:
 On Fri, Jul 27, 2012 at 7:13 AM, Wayne Fay wayne...@gmail.com wrote:
 Long story short, I tried to modify eclipse project generation so that
 in the .settings/org.eclipse.jdt.core.prefs instead of this:
 org.eclipse.jdt.core.compiler.compliance=1.5
 I get this (look at the compliance):
 org.eclipse.jdt.core.compiler.compliance=1.6
 but didn't find a way to configure maven-eclipse-plugin.

 Most likely you are the first person to want this specific
 configuration of the plugin, thus it does not currently exist. You'll
 probably need to scratch your own itch.

 Pull down the source code for maven-eclipse-plugin, tweak it somehow
 to add this feature, and contribute the code back for (possible)
 inclusion in a future release.

 Here's a hint: you're going to want to adjust EclipseSettingsWriter
 and probably some Eclipse plugin Mojo code too since this should be an
 extra configuration item in the plugin...
 http://maven.apache.org/plugins/maven-eclipse-plugin/xref/org/apache/maven/plugin/eclipse/writers/workspace/EclipseSettingsWriter.html

 Also remember, that the maven-eclipse-plugin reads the configuration
 of the maven-compiler-plugin.
 See 
 http://maven.apache.org/plugins/maven-eclipse-plugin/trouble-shooting/jdk-being-used-is-different-than-expected.html

 So you ideally need to configure that the way you want.
 I'm not sure what
 org.eclipse.jdt.core.compiler.compliance=1.6
 actually does.
 Is this equivalent to

 plugin
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.6/target
/configuration
 /plugin

Alternatively, you can fix your problem with the overrides and mark it
as something to worry about manually.
The time invested to fix this automatically may not be worth the effort.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Eclipse Plugin and Project Links to Independent Projects

[Chris Redekop]

On Mon, Jun 4, 2012 at 8:08 PM, Barrie Treloar baerr...@gmail.com wrote:
 On Tue, Jun 5, 2012 at 3:19 AM, Chris Redekop chris.rede...@gmail.com wrote:
 (How) can I use the Eclipse plugin to create Eclipse project files
 that refer to an dependency A) with an Eclipse project link instead of
 B) as a JAR in the repo?  The dependency in this case is A) NOT a
 module of the parent project (where 'mvn eclipse:eclipse' is executed)
 and B) NOT built with Maven.

 Project links work well between modules in a multi-module project, and
 the -Declipse.workspace property provides some related functionality;
 but its workspace scan only seems to recognize other Maven projects.

 You can't.
Thanks for the confirmation, Barrie.  I figured that this is currently
not supported, but part of me wondered if I just hadn't found the
right (combination of) options.


 mvn eclipse:eclipse will automatically configure the .classpath to
 reference any dependency that is already configured in Eclipse and is
 a Maven project.

 If you think about it, how do you expect eclipse:eclipse to work out
 that your non-Maven project just happens to be the same as one of your
 Maven dependencies?

The most straight-forward way that I can think of is a new plugin
configuration: a map of dependency - project.  When the Eclipse
plugin handles a dependency, in can first check the map.  If there is
an entry, then the specified project is used; otherwise, the JAR is
used.

The old Maven 1 plugin had something like this, in the form of a project flag:

http://maven.apache.org/maven-1.x/plugins/eclipse/faq.html#project_dependencies


 I am looking for something like -Declipse.workspace but more direct
 and fully contained within the plugin configuration: a map between
 dependencies and Eclipse projects that says, when you are generating
 Eclipse project files and hit this dependency, refer to this Eclipse
 project instead of the artifact's JAR in the repo.

 The use case here is migrating one of an organization's existing
 builds to Maven while NOT migrating ALL an organization's builds.  We
 currently have a mix of Maven/non-Maven builds cohabitating in the
 same Eclipse workspace.  In this environment, dependencies from
 Maven-built projects to non-Maven-built projects appear twice:
 1) as a JAR dependency and
 2) as an Eclipse project where active development takes place.

 The duplicate project/class definition is causing confusion.

 You have some of options:
 1) Dont use mvn eclipse:eclipse
 2) Use mvn eclipse:eclipse to kick-start the .classpath creation and
 then manually tweak this to work with the non-Maven project.  You then
 check-in the eclipse files: .project, .classpath into your source
 control.
Both of these run counter to DRY: maintaining dependencies in POMs and
Eclipse project files.  Do not want.

 3) Migrate your non-Maven builds to Maven.  If these are Ant builds it
 should be a simple process to create a dumb Maven wrapper that just
 calls out to Ant to do the build.  This will give you a pom.xml that
 specifies the correct dependency coordinates for mvn eclipse:eclipse
 to then use.  Then when you are ready to migrate these projects, you
 take out the Ant stuff and replace it with the equivalent Maven
 plugins.

 I would recommend 3).
The use case of a mixed-build environment will be valid into the
foreseeable future.  3) is not an option.

A fourth option would enhance the plugin to support a map
configuration as described here.  It *seems* straightforward to me at
this point, but the history of a similar feature disappearing from the
Maven 1 plugin makes me wonder: maybe this is a Bad Idea?

Comments?


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Eclipse Plugin and Project Links to Independent Projects

[Chris Redekop]

(How) can I use the Eclipse plugin to create Eclipse project files
that refer to an dependency A) with an Eclipse project link instead of
B) as a JAR in the repo?  The dependency in this case is A) NOT a
module of the parent project (where 'mvn eclipse:eclipse' is executed)
and B) NOT built with Maven.

Project links work well between modules in a multi-module project, and
the -Declipse.workspace property provides some related functionality;
but its workspace scan only seems to recognize other Maven projects.

I am looking for something like -Declipse.workspace but more direct
and fully contained within the plugin configuration: a map between
dependencies and Eclipse projects that says, when you are generating
Eclipse project files and hit this dependency, refer to this Eclipse
project instead of the artifact's JAR in the repo.

The use case here is migrating one of an organization's existing
builds to Maven while NOT migrating ALL an organization's builds.  We
currently have a mix of Maven/non-Maven builds cohabitating in the
same Eclipse workspace.  In this environment, dependencies from
Maven-built projects to non-Maven-built projects appear twice:
1) as a JAR dependency and
2) as an Eclipse project where active development takes place.

The duplicate project/class definition is causing confusion.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Eclipse Plugin and Project Links to Independent Projects

[Barrie Treloar]

On Tue, Jun 5, 2012 at 3:19 AM, Chris Redekop chris.rede...@gmail.com wrote:
 (How) can I use the Eclipse plugin to create Eclipse project files
 that refer to an dependency A) with an Eclipse project link instead of
 B) as a JAR in the repo?  The dependency in this case is A) NOT a
 module of the parent project (where 'mvn eclipse:eclipse' is executed)
 and B) NOT built with Maven.

 Project links work well between modules in a multi-module project, and
 the -Declipse.workspace property provides some related functionality;
 but its workspace scan only seems to recognize other Maven projects.

You can't.

mvn eclipse:eclipse will automatically configure the .classpath to
reference any dependency that is already configured in Eclipse and is
a Maven project.

If you think about it, how do you expect eclipse:eclipse to work out
that your non-Maven project just happens to be the same as one of your
Maven dependencies?

 I am looking for something like -Declipse.workspace but more direct
 and fully contained within the plugin configuration: a map between
 dependencies and Eclipse projects that says, when you are generating
 Eclipse project files and hit this dependency, refer to this Eclipse
 project instead of the artifact's JAR in the repo.

 The use case here is migrating one of an organization's existing
 builds to Maven while NOT migrating ALL an organization's builds.  We
 currently have a mix of Maven/non-Maven builds cohabitating in the
 same Eclipse workspace.  In this environment, dependencies from
 Maven-built projects to non-Maven-built projects appear twice:
 1) as a JAR dependency and
 2) as an Eclipse project where active development takes place.

 The duplicate project/class definition is causing confusion.

You have some of options:
1) Dont use mvn eclipse:eclipse
2) Use mvn eclipse:eclipse to kick-start the .classpath creation and
then manually tweak this to work with the non-Maven project.  You then
check-in the eclipse files: .project, .classpath into your source
control.
3) Migrate your non-Maven builds to Maven.  If these are Ant builds it
should be a simple process to create a dumb Maven wrapper that just
calls out to Ant to do the build.  This will give you a pom.xml that
specifies the correct dependency coordinates for mvn eclipse:eclipse
to then use.  Then when you are ready to migrate these projects, you
take out the Ant stuff and replace it with the equivalent Maven
plugins.

I would recommend 3).

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: eclipse plugin for maven using jdk 1.3

[sarmahdi]

Thanks for the reply  Thorsten Heit,

the problem is that on my machine i commented out the compiler plugin part
but it was still using 1.6 and i thought copying the pom.xml from my
workspace to other workspace would work. but it did not, so i uncommented my
compiler plugin entry and it worked fine. I was only surprised how. The
Effective POM does not have any source entry either to wind it up to 1.3\


but yes i added the same thing you said and it worked fine,

Thanks appreciate it
Syed... 



--
View this message in context: 
http://maven.40175.n5.nabble.com/eclipse-plugin-for-maven-using-jdk-1-3-tp5611951p5614453.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

eclipse plugin for maven using jdk 1.3

[sarmahdi]

Hello guys,

I installed a maven plugin in eclipse when i ran my pavne project and tried
to build it there it used jdk 1.3 to build and compile. here is the verbose
out put sections related to this:


/
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ CorpWeb
---
[DEBUG] Created new class realm
pluginorg.apache.maven.plugins:maven-compiler-plugin:2.0.2
[DEBUG] Populating class realm
pluginorg.apache.maven.plugins:maven-compiler-plugin:2.0.2
[DEBUG]   Included:
org.apache.maven.plugins:maven-compiler-plugin:maven-plugin:2.0.2
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.0.4
[DEBUG]   Included: org.codehaus.plexus:plexus-compiler-api:jar:1.5.3
[DEBUG]   Included: junit:junit:jar:3.8.1
[DEBUG]   Included: org.codehaus.plexus:plexus-compiler-manager:jar:1.5.3
[DEBUG]   Included: org.codehaus.plexus:plexus-compiler-javac:jar:1.5.3
[DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0
[DEBUG]   Excluded:
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
[DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile' with basic
configurator --
[DEBUG]   (f) basedir = C:\RSA75Workspace\workspace\Corpweb
[DEBUG]   (f) buildDirectory = C:\RSA75Workspace\workspace\Corpweb\target
[
[DEBUG]   (f) compileSourceRoots = [C:\RSA75Workspace\workspace\Corpweb\src]
[DEBUG]   (f) compilerId = javac
[DEBUG]   (f) debug = true
[DEBUG]   (f) failOnError = true
[DEBUG]   (f) fork = false
[DEBUG]   (f) optimize = false
[DEBUG]   (f) outputDirectory =
C:\RSA75Workspace\workspace\Corpweb\target\classes
[DEBUG]   (f) outputFileName = CorpWeb
[DEBUG]   (f) projectArtifact = CorpWeb:CorpWeb:war:1.0
[DEBUG]   (f) showDeprecation = false
[DEBUG]   (f) showWarnings = false
[DEBUG]   (f) staleMillis = 0
[DEBUG]   (f) verbose = false
[DEBUG] -- end configuration –/

here it doesnt indicate to me which JDK it is using but then it fails on
compile:

/ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project CorpWeb: Compilation failure: Compilation
failure: 
C:\RSA75Workspace\workspace\Corpweb\src\com\ejada\ecorp\domain\administration\GroupsUserAssignmentSummaryBO.java:[84,2]
annotations are not supported in *-source 1.3*
(use -source 5 or higher to enable annotations)
  @Override

C:\RSA75Workspace\workspace\Corpweb\src\com\ejada\ecorp\domain\beneficiaries\BeneficiaryIdBO.java:[56,2]
annotations are not supported in *-source 1.3*
(use -source 5 or higher to enable annotations)
  @Override

C:\RSA75Workspace\workspace\Corpweb\src\com\ejada\ecorp\domain\beneficiaries\BeneficiaryIdBO.java:[57,18]
generics are not supported in *-source 1.3*
(use -source 5 or higher to enable generics)
  public LinkedListTuple generateSpecificDetails()/

I checked if the JRE in the Run AS configuration was 1.3 but it was not. Why
is the maven plugin using 1.3 is beyond my understanding. 

Also: i couldnt find the settings.xml of the plugin or maven installation i
had to add a new one manually. neither could i find mvn,bat any where on my
harddisk . even though when i try to Run it through maven i can see that it
issued a command 
mvn -B -Dmaven.test.skip=true -s C:\Documents and
Settings\5510041\.m2\settings.xml clean install

so everything seems to be embedded in the plugin. 

any help in understanding this would be appreciated.
Thanks.
Syed...

--
View this message in context: 
http://maven.40175.n5.nabble.com/eclipse-plugin-for-maven-using-jdk-1-3-tp5611951p5611951.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: eclipse plugin for maven using jdk 1.3

[Thorsten Heit]

Hi,

 I checked if the JRE in the Run AS configuration was 1.3 but it was not. 
Why
 is the maven plugin using 1.3 is beyond my understanding.

http://maven.apache.org/general.html#Compiling-J2SE-5


HTH

Thorsten

Re: Re: Antwort: eclipse plugin has a POM of its own

[sarmahdi]

i replaced my project path to  ${basedir} this is where the maven POM is
located so it knows its root or ${basedir}

Can any one tell me if maven knows the workspace directory where the
${basedir} is located. I know impossible i guess but doesnt hurt to try.

Thanks.
Syed..

--
View this message in context: 
http://maven.40175.n5.nabble.com/eclipse-plugin-has-a-POM-of-its-own-tp5535417p5541066.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Antwort: eclipse plugin has a POM of its own

[Thorsten Heit]

Hi,

 build
 
 
 
sourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src/sourceDirectory
 
 scriptSourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src\main
 \scripts/scriptSourceDirectory
 
 testSourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src\test
 \java/testSourceDirectory
 
 outputDirectoryC:\RSA75Workspace\workspace\finAppWeb\target\build
 \classes/outputDirectory
 
 testOutputDirectoryC:\RSA75Workspace\workspace\finAppWeb\target\test-
 classes/testOutputDirectory

*snip*

Just a side note:
I have made the experience that backslashes in files are treated by Java 
more or less often as a quoting character. To prevent strange errors I'd 
recommend either using forward slashes ('/'; should also work as directory 
separator under Java in Windows environments), or a double backslash '\\'.


HTH

Thorsten

Re: eclipse plugin has a POM of its own

[sarmahdi]

Thanks Anders,

Yes you are right the plugin that installed with eclipse was different than
the one i installed with netbeans(thats what i was using outside the IDE as
well)

but here is the thing now, whihc is ticking me off with eclipse plugin for
maven.

I dont know why but now when I am running the goals clean install it is
doing everything as per my wishes with one exception when i was doing it
outside the IDES, (using the maven installed with netbeans) the classes
folder only had classes but now the java classes are also added within them.
the maven with netbeans didnt had to be configured SO much, this eclipse one
needs to be baby feed every configuration hence making my POM more absurdly
verbose than the previous one. AND its accomplishing the same things I was
achieving before.

this is just uselessly wasting my time, my POM was good enough to complete
the build, I even changed the maven run time (going into Run As..  Run
Configurations changing the maven runtime to Maven inside Netbeans )

Do you think that becuase i changed the source directory and listed the
webapp directory that it is now ADDing the java files as well with the
classes. I dont think they should be related in any way.

Thanks for the comments and hints and suggestions.

Syed...


--
View this message in context: 
http://maven.40175.n5.nabble.com/eclipse-plugin-has-a-POM-of-its-own-tp5535417p5537027.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Antwort: eclipse plugin has a POM of its own

[sarmahdi]

Thanks Thorsten,

Yeah thats a good suggestion. Also can you tell me how to remove the
C:\RSA75Workspace\workspace/ blah blah to some thing relative to workspace??
so that the POM is portable to another workspace.

Thanks
Syed...

--
View this message in context: 
http://maven.40175.n5.nabble.com/eclipse-plugin-has-a-POM-of-its-own-tp5535417p5537029.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Antwort: eclipse plugin has a POM of its own

[sarmahdi]

Thanks Thorsten,

Yeah thats a good suggestion. Also can you tell me how to remove the
C:\RSA75Workspace\workspace/ blah blah to some thing relative to workspace??
so that the POM is portable to another workspace.

Thanks
Syed...

--
View this message in context: 
http://maven.40175.n5.nabble.com/eclipse-plugin-has-a-POM-of-its-own-tp5535417p5537030.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Antwort: eclipse plugin has a POM of its own

[sarmahdi]

Thanks Thorsten,

Yeah thats a good suggestion. Also can you tell me how to remove the
C:\RSA75Workspace\workspace/ blah blah to some thing relative to workspace??
so that the POM is portable to another workspace.

Thanks
Syed...

--
View this message in context: 
http://maven.40175.n5.nabble.com/eclipse-plugin-has-a-POM-of-its-own-tp5535417p5537031.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Re: Antwort: eclipse plugin has a POM of its own

[Thorsten Heit]

Hi Syed,

 Yeah thats a good suggestion. Also can you tell me how to remove the
 C:\RSA75Workspace\workspace/ blah blah to some thing relative to 
workspace??
 so that the POM is portable to another workspace.

According to your initial post the effective pom lets me guess that you're 
using the standard directory layout. The absolute paths are the ones Maven 
resolves from your pom.
As long as you don't have hardcoded entries in that file, your project 
should be perfectly portable to other workspaces/machines/users. You only 
have to take care if you're using relative paths, but as long as they are 
relative to your project, that shouldn't matter.

If you have to use a different directory layout, I suggest you have a look 
at the documentation ([1]), especially [2]. Depending on the plugins 
you're using you should also have a look at their documentation ([3]); 
perhaps their configuration has to be adapted to fit your project layout.


[1] http://maven.apache.org/guides/index.html
[2] 
http://maven.apache.org/guides/mini/guide-using-one-source-directory.html
[3] http://maven.apache.org/plugins/index.html


Regards

Thorsten

eclipse plugin has a POM of its own

[sarmahdi]

Hello All,

I was using maven standalone and working fine. but then i wanted to port
this project into eclipse so I downloaded the maven plugin me2Eclipse and
imported the project into eclipse. When I opened the POM.xml the file opened
as forms. so for all the sections there was a form which is a good thing.
BUT, there was an uneditable POM called *Effective POM* besides the pom.xml
source. what is happening is that the things that were missing from my POM
are read from there. and things that are missing from my POM the maven
outside the IDE was adjusting them quite favorably for my project.

When i was using maven outside the IDE it was working fine: but now the
Effective POM has some plugins listed in the pluginmanagement area that
are of older versions than the ones I was using and are in my repo already.
and because its uneditable i cant modify it so i have to over ride those in
my pom.xml. 

(I understand that eclipse is only telling me the actual Effective POM thats
gonna play when my maven runs on it) but how do i over ride it or what to do
now. My old structure was in place and all working with this new POM
although it shows me how to write a good POM but its confusing to get things
configured at two places.

Has any body had this issue and tried to work with it. the best thing was
that it showed me these tags and  how to specify my own project structure
(similar to eclipse) so I dont need to follow maven conventions



build


sourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src/sourceDirectory
  
scriptSourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src\main\scripts/scriptSourceDirectory
   
testSourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src\test\java/testSourceDirectory
   
outputDirectoryC:\RSA75Workspace\workspace\finAppWeb\target\build\classes/outputDirectory
   
testOutputDirectoryC:\RSA75Workspace\workspace\finAppWeb\target\test-classes/testOutputDirectory
resources
  resource
   
directoryC:\RSA75Workspace\workspace\finAppWeb\src\main\resources/directory
  /resource
/resources
testResources
  testResource
   
directoryC:\RSA75Workspace\workspace\finAppWeb\src\test\resources/directory
  /testResource
/testResources
directoryC:\RSA75Workspace\workspace\finAppWeb\target/directory
finalNamefinAppWeb-0.0.1-SNAPSHOT/finalName
plugins
/build

Is there a way to specify where my webApp folder is like the
sourceDirectory. The Effective POM doesn't list it. Also they are all
local paths, can I not give workspace specific path so that they can be
ported to some other directory and still work.

Thanks
Syed...



--
View this message in context: 
http://maven.40175.n5.nabble.com/eclipse-plugin-has-a-POM-of-its-own-tp5535417p5535417.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

eclipse plugin has a POM of its own

[sarmahdi]

Hello All,

I was using maven standalone and working fine. but then i wanted to port
this project into eclipse so I downloaded the maven plugin me2Eclipse and
imported the project into eclipse. When I opened the POM.xml the file opened
as forms. so for all the sections there was a form which is a good thing.
BUT, there was an uneditable POM called *Effective POM* besides the pom.xml
source. what is happening is that the things that were missing from my POM
are read from there. and things that are missing from my POM the maven
outside the IDE was adjusting them quite favorably for my project.

When i was using maven outside the IDE it was working fine: but now the
Effective POM has some plugins listed in the pluginmanagement area that
are of older versions than the ones I was using and are in my repo already.
and because its uneditable i cant modify it so i have to over ride those in
my pom.xml. 

(I understand that eclipse is only telling me the actual Effective POM thats
gonna play when my maven runs on it) but how do i over ride it or what to do
now. My old structure was in place and all working with this new POM
although it shows me how to write a good POM but its confusing to get things
configured at two places.

Has any body had this issue and tried to work with it. the best thing was
that it showed me these tags and  how to specify my own project structure
(similar to eclipse) so I dont need to follow maven conventions



build


sourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src/sourceDirectory
  
scriptSourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src\main\scripts/scriptSourceDirectory
   
testSourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src\test\java/testSourceDirectory
   
outputDirectoryC:\RSA75Workspace\workspace\finAppWeb\target\build\classes/outputDirectory
   
testOutputDirectoryC:\RSA75Workspace\workspace\finAppWeb\target\test-classes/testOutputDirectory
resources
  resource
   
directoryC:\RSA75Workspace\workspace\finAppWeb\src\main\resources/directory
  /resource
/resources
testResources
  testResource
   
directoryC:\RSA75Workspace\workspace\finAppWeb\src\test\resources/directory
  /testResource
/testResources
directoryC:\RSA75Workspace\workspace\finAppWeb\target/directory
finalNamefinAppWeb-0.0.1-SNAPSHOT/finalName
plugins
/build

Is there a way to specify where my webApp folder is like the
sourceDirectory. The Effective POM doesn't list it. Also they are all
local paths, can I not give workspace specific path so that they can be
ported to some other directory and still work.

Thanks
Syed...



--
View this message in context: 
http://maven.40175.n5.nabble.com/eclipse-plugin-has-a-POM-of-its-own-tp5535418p5535418.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: eclipse plugin has a POM of its own

[Ron Wheeler]

The effective POM is just your project POM merged with the Maven super 
POM, the project's parent POM, your settings.XML and the settings in 
Eclipse for Maven and Java.


You need to check your Eclipse workspace and project properties to see 
how Maven and Java are set up in your Eclipse settings.


You should be overriding your plug-in versions in your project POM or 
parent POM so that you control what versions are in use and so that you 
get the same build inside Eclipse and outside.


This is normal behaviour for Eclipse and Maven.


Ron


On 04/03/2012 10:58 AM, sarmahdi wrote:

Hello All,

I was using maven standalone and working fine. but then i wanted to port
this project into eclipse so I downloaded the maven plugin me2Eclipse and
imported the project into eclipse. When I opened the POM.xml the file opened
as forms. so for all the sections there was a form which is a good thing.
BUT, there was an uneditable POM called *Effective POM* besides the pom.xml
source. what is happening is that the things that were missing from my POM
are read from there. and things that are missing from my POM the maven
outside the IDE was adjusting them quite favorably for my project.

When i was using maven outside the IDE it was working fine: but now the
Effective POM has some plugins listed in thepluginmanagement  area that
are of older versions than the ones I was using and are in my repo already.
and because its uneditable i cant modify it so i have to over ride those in
my pom.xml.

(I understand that eclipse is only telling me the actual Effective POM thats
gonna play when my maven runs on it) but how do i over ride it or what to do
now. My old structure was in place and all working with this new POM
although it shows me how to write a good POM but its confusing to get things
configured at two places.

Has any body had this issue and tried to work with it. the best thing was
that it showed me these tags and  how to specify my own project structure
(similar to eclipse) so I dont need to follow maven conventions



build


sourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src/sourceDirectory

scriptSourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src\main\scripts/scriptSourceDirectory

testSourceDirectoryC:\RSA75Workspace\workspace\finAppWeb\src\test\java/testSourceDirectory

outputDirectoryC:\RSA75Workspace\workspace\finAppWeb\target\build\classes/outputDirectory

testOutputDirectoryC:\RSA75Workspace\workspace\finAppWeb\target\test-classes/testOutputDirectory
 resources
   resource

directoryC:\RSA75Workspace\workspace\finAppWeb\src\main\resources/directory
   /resource
 /resources
 testResources
   testResource

directoryC:\RSA75Workspace\workspace\finAppWeb\src\test\resources/directory
   /testResource
 /testResources
 directoryC:\RSA75Workspace\workspace\finAppWeb\target/directory
 finalNamefinAppWeb-0.0.1-SNAPSHOT/finalName
plugins
/build

Is there a way to specify where my webApp folder is like the
sourceDirectory. The Effective POM doesn't list it. Also they are all
local paths, can I not give workspace specific path so that they can be
ported to some other directory and still work.

Thanks
Syed...



--
View this message in context: 
http://maven.40175.n5.nabble.com/eclipse-plugin-has-a-POM-of-its-own-tp5535417p5535417.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Ivalo]

My day job company is associate member of Eclipse so of course Eclipse 
is tool to use.


Markku

On 2.3.2012 18:14, Wayne Fay wrote:

You don't understand how Eclipse IDE works. Eclipse does not have different
classpaths for testing and actual runtime. So Eclipse basic design is
faulty. There is bug open since 2008 to provide means to tell Eclipse that

...

Of course NetBeans and IntelliJ has correct way to do things but they are
not an option.

Help me understand this line of thinking...

Product A is demonstrably broken for what we need and has been since 2008.
Products B and C support our needs perfectly well. One is free, one is not.
And yet B and C are not an option.

This doesn't sound rational to me. Why are they not an option for you?
I would challenge that assertion with whoever is making the decision.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Ivalo]

My day job company is assosiate member of Eclipse so of course Eclipse 
is tool to use.


Markku

On 2.3.2012 18:14, Wayne Fay wrote:

You don't understand how Eclipse IDE works. Eclipse does not have different
classpaths for testing and actual runtime. So Eclipse basic design is
faulty. There is bug open since 2008 to provide means to tell Eclipse that

...

Of course NetBeans and IntelliJ has correct way to do things but they are
not an option.

Help me understand this line of thinking...

Product A is demonstrably broken for what we need and has been since 2008.
Products B and C support our needs perfectly well. One is free, one is not.
And yet B and C are not an option.

This doesn't sound rational to me. Why are they not an option for you?
I would challenge that assertion with whoever is making the decision.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Barrie Treloar]

On Sat, Mar 3, 2012 at 6:28 AM, Markku Saarela markku.saar...@iki.fi wrote:
 Our releases do not have any configuration files in artifact's, instead
 manifest classpaths has directory name to point directory that has those
 files. We use separate build to assembly different configurations into
 different environments putting configurations in place.

 I like to use Eclipse ability to hot deploy modifications of code into
 server while debugging development trunk code.

 So what you say and my experience it is impossible to use multi-module
 project imported with project references for developing software with hot
 deployment and also unit testing without having profiles to set resource
 directories for Eclipse unit testing and deploying into server.

There is nothing stopping you creating an extra level of abstraction,
i.e. mymodule-unittests
You move all your unit tests out of the original module mymodule
and into mymodule-unittests.
Obviously mymodule-unittests would depend on mymodule

That way you can run unit tests, but you would only ever deploy
mymodule, with no way to pollute with unit tests.

p.s. Given Eclipse is open source, if this was a defect that you
*really* cared about, you should provide a patch.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: eclipse plugin has a POM of its own

[sarmahdi]

Thanks for the reply Ron, appreciate it

The question is that why would i need to overriding your plug-in versions
now that I am in eclipse, outside of my eclipse i was doing fine and running
the POM as IS . now that I have ported it into eclipse why are the settings
different. I know your answer would be settings in eclipse for maven and
java. but I am only saying that why are they so different or OLD. I am
thinking that the eclipse maven plugin i downloaded was the older version
and it is the one making problems. 
but i appreciate your answer. 

I guess you are right. it was confusing me esp because i just started to
work with maven and it was awesomely working for me. 

Anyways thanks.

I will post another question for the webappsources location in POM. if there
is such a thing like that.

Thanks.
Syed...



--
View this message in context: 
http://maven.40175.n5.nabble.com/eclipse-plugin-has-a-POM-of-its-own-tp5535417p5536744.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: eclipse plugin has a POM of its own

[Anders Hammar]

It might be that you're using different Maven versions. What version
of Maven are you using from command-line? m2e (Eclipse) is using Maven
3.0.2+some patches (or 3.0.3 if you've installed the upgraded
embedder).

If you're using different Maven versions, different Super-POMs are
used with different versions specified for the plugins. Thus, you
should ALWAYS specify the version of the plugins your project is
using!

/Anders

On Mon, Mar 5, 2012 at 08:23, sarmahdi sarma...@hotmail.com wrote:
 Thanks for the reply Ron, appreciate it

 The question is that why would i need to overriding your plug-in versions
 now that I am in eclipse, outside of my eclipse i was doing fine and running
 the POM as IS . now that I have ported it into eclipse why are the settings
 different. I know your answer would be settings in eclipse for maven and
 java. but I am only saying that why are they so different or OLD. I am
 thinking that the eclipse maven plugin i downloaded was the older version
 and it is the one making problems.
 but i appreciate your answer.

 I guess you are right. it was confusing me esp because i just started to
 work with maven and it was awesomely working for me.

 Anyways thanks.

 I will post another question for the webappsources location in POM. if there
 is such a thing like that.

 Thanks.
 Syed...



 --
 View this message in context: 
 http://maven.40175.n5.nabble.com/eclipse-plugin-has-a-POM-of-its-own-tp5535417p5536744.html
 Sent from the Maven - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Ron Wheeler]

On 02/03/2012 1:32 AM, Markku Saarela wrote:

Hi,

Developing with Eclipse IDE and JavaEE server using 
maven-eclipse-plugin you have to use profiles, because Eclipse does 
not isolate test code and test resources.

Eclipse does
/src/main/   code
/src/test   ... test code and resources

You need to set your maven properly but it works fine unless I don't 
understand your issue.




Only way to do it what i have figured out is to have two profiles one 
for running application in app server and another for unit testing 
same code.  Those profiles has only resources and testResources 
definitions.


Separating test code for separate code is not an option, because then 
Sonar reports 0 % coverage.


rgds,

Markku

On 1.3.2012 22:55, Ron Wheeler wrote:

On 01/03/2012 2:43 PM, offbyone wrote:
Ok so I should create a base pom with a war configuration and then a 
separate

pom for each site that depends on this with overlays to add the extra
configuration file.
I will try.

If I am interpreting your comments correctly, profiles allow for a 
user to
flaten a maven build deployment, but this is a bad practice and it 
is better

to make your maven structure deep.

So are profiles going to be deprecated?   I would think I am not 
alone in
getting turned down the wrong path because most of the 
documentation/howtos

I have found point to using profiles.
There are some uses for profiles that seem harmless so it is a 
documentation issue.


It is fairly common in Apache documentation for the programmers to 
make a big deal about all the wonderful things that the package can do.

They are not particularly concerned about Best Practices.

The most common usage is often left out of the documentation since it 
is dull or not very impressive.
This sometimes means that obscure usage of features or seldom used 
features are heavily documented while the main use case is  not 
described.


New Maven users often fall into the trap that you were headed into.

A really simple Best Practice that most people use, is hard to find 
in the documentation while an obscure Worst Practice is described 
because it shows how clever the software developers are and how 
powerful the product is.


There should be a Best Practice section on the Maven site 
describing the best way to implement the common software development 
patterns.


There are not really a lot of cases to consider but every new Maven 
user has to sort out their own case.


Ron



--
View this message in context: 
http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5528994.html

Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org







-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org






--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Markku Saarela]

Hi,

You don't understand how Eclipse IDE works. Eclipse does not have 
different classpaths for testing and actual runtime. So Eclipse basic 
design is faulty. There is bug open since 2008 to provide means to tell 
Eclipse that which are test sources and not include them to runtime 
classpath. https://bugs.eclipse.org/bugs/show_bug.cgi?id=224708


So everything under src/test goes also into GlassFish server if you 
deploy application in Eclipse. That causes that those unit test 
properties and configuration and classes are picked first and they are 
effective and application does not work.


Even worst if you have multi-module project and B module is dependent 
from A and A project defines SPI interface and has in src/test/java test 
implementation for that and of course in 
src/test/resources/META-INF/services SPI file for exposing that test SPI 
implementation then if B implements also that SPI interface and put SPI 
file in src/main/resources/META-INF/services, you cannot test you 
implementation via ServiceLoader because it pick's that module A test 
implementation. Same goes for properties and everything else.


Of course NetBeans and IntelliJ has correct way to do things but they 
are not an option.


Markku


On 2.3.2012 15:15, Ron Wheeler wrote:

On 02/03/2012 1:32 AM, Markku Saarela wrote:

Hi,

Developing with Eclipse IDE and JavaEE server using 
maven-eclipse-plugin you have to use profiles, because Eclipse does 
not isolate test code and test resources.

Eclipse does
/src/main/   code
/src/test   ... test code and resources

You need to set your maven properly but it works fine unless I don't 
understand your issue.




Only way to do it what i have figured out is to have two profiles one 
for running application in app server and another for unit testing 
same code.  Those profiles has only resources and testResources 
definitions.


Separating test code for separate code is not an option, because then 
Sonar reports 0 % coverage.


rgds,

Markku

On 1.3.2012 22:55, Ron Wheeler wrote:

On 01/03/2012 2:43 PM, offbyone wrote:
Ok so I should create a base pom with a war configuration and then 
a separate

pom for each site that depends on this with overlays to add the extra
configuration file.
I will try.

If I am interpreting your comments correctly, profiles allow for a 
user to
flaten a maven build deployment, but this is a bad practice and it 
is better

to make your maven structure deep.

So are profiles going to be deprecated?   I would think I am not 
alone in
getting turned down the wrong path because most of the 
documentation/howtos

I have found point to using profiles.
There are some uses for profiles that seem harmless so it is a 
documentation issue.


It is fairly common in Apache documentation for the programmers to 
make a big deal about all the wonderful things that the package can do.

They are not particularly concerned about Best Practices.

The most common usage is often left out of the documentation since 
it is dull or not very impressive.
This sometimes means that obscure usage of features or seldom used 
features are heavily documented while the main use case is  not 
described.


New Maven users often fall into the trap that you were headed into.

A really simple Best Practice that most people use, is hard to 
find in the documentation while an obscure Worst Practice is 
described because it shows how clever the software developers are 
and how powerful the product is.


There should be a Best Practice section on the Maven site 
describing the best way to implement the common software development 
patterns.


There are not really a lot of cases to consider but every new Maven 
user has to sort out their own case.


Ron



--
View this message in context: 
http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5528994.html

Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org







-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Ron Wheeler]

We have been developing and maintaining a large  portal application with 
over 70 WAR files in Eclipse with Maven since 2007 and several smaller 
portals and standalone applications. We have not had this problem.


That is not to say that I am an expert in Eclipse but we know enough to 
make it work.


We do not use maven-eclipse-plug-in. We use the assembly plug-in to 
build our war files.

Perhaps that is the difference.

We also deploy to Tomcat which might be a better servlet engine than 
Glassfish.


I am not sure how relevant our experience is to your problem but if I 
can provide any additional information that you think might help, let me 
know.


Ron


On 02/03/2012 10:19 AM, Markku Saarela wrote:

Hi,

You don't understand how Eclipse IDE works. Eclipse does not have 
different classpaths for testing and actual runtime. So Eclipse basic 
design is faulty. There is bug open since 2008 to provide means to 
tell Eclipse that which are test sources and not include them to 
runtime classpath. https://bugs.eclipse.org/bugs/show_bug.cgi?id=224708


So everything under src/test goes also into GlassFish server if you 
deploy application in Eclipse. That causes that those unit test 
properties and configuration and classes are picked first and they are 
effective and application does not work.


Even worst if you have multi-module project and B module is dependent 
from A and A project defines SPI interface and has in src/test/java 
test implementation for that and of course in 
src/test/resources/META-INF/services SPI file for exposing that test 
SPI implementation then if B implements also that SPI interface and 
put SPI file in src/main/resources/META-INF/services, you cannot test 
you implementation via ServiceLoader because it pick's that module A 
test implementation. Same goes for properties and everything else.


Of course NetBeans and IntelliJ has correct way to do things but they 
are not an option.


Markku


On 2.3.2012 15:15, Ron Wheeler wrote:

On 02/03/2012 1:32 AM, Markku Saarela wrote:

Hi,

Developing with Eclipse IDE and JavaEE server using 
maven-eclipse-plugin you have to use profiles, because Eclipse does 
not isolate test code and test resources.

Eclipse does
/src/main/   code
/src/test   ... test code and resources

You need to set your maven properly but it works fine unless I don't 
understand your issue.




Only way to do it what i have figured out is to have two profiles 
one for running application in app server and another for unit 
testing same code.  Those profiles has only resources and 
testResources definitions.


Separating test code for separate code is not an option, because 
then Sonar reports 0 % coverage.


rgds,

Markku

On 1.3.2012 22:55, Ron Wheeler wrote:

On 01/03/2012 2:43 PM, offbyone wrote:
Ok so I should create a base pom with a war configuration and then 
a separate

pom for each site that depends on this with overlays to add the extra
configuration file.
I will try.

If I am interpreting your comments correctly, profiles allow for a 
user to
flaten a maven build deployment, but this is a bad practice and it 
is better

to make your maven structure deep.

So are profiles going to be deprecated?   I would think I am not 
alone in
getting turned down the wrong path because most of the 
documentation/howtos

I have found point to using profiles.
There are some uses for profiles that seem harmless so it is a 
documentation issue.


It is fairly common in Apache documentation for the programmers to 
make a big deal about all the wonderful things that the package can 
do.

They are not particularly concerned about Best Practices.

The most common usage is often left out of the documentation since 
it is dull or not very impressive.
This sometimes means that obscure usage of features or seldom used 
features are heavily documented while the main use case is  not 
described.


New Maven users often fall into the trap that you were headed into.

A really simple Best Practice that most people use, is hard to 
find in the documentation while an obscure Worst Practice is 
described because it shows how clever the software developers are 
and how powerful the product is.


There should be a Best Practice section on the Maven site 
describing the best way to implement the common software 
development patterns.


There are not really a lot of cases to consider but every new Maven 
user has to sort out their own case.


Ron



--
View this message in context: 
http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5528994.html

Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org







-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Wayne Fay]

 You don't understand how Eclipse IDE works. Eclipse does not have different
 classpaths for testing and actual runtime. So Eclipse basic design is
 faulty. There is bug open since 2008 to provide means to tell Eclipse that
...
 Of course NetBeans and IntelliJ has correct way to do things but they are
 not an option.

Help me understand this line of thinking...

Product A is demonstrably broken for what we need and has been since 2008.
Products B and C support our needs perfectly well. One is free, one is not.
And yet B and C are not an option.

This doesn't sound rational to me. Why are they not an option for you?
I would challenge that assertion with whoever is making the decision.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Markku Saarela]

In multi-module project i hit the same problem with m2e and 
maven-eclipse-plugin. Are you saying not to import multi-module projects 
into Eclipse, instead every module separately? Or you don't use server 
plugins to deploy application instead you deploy outside Eclipse and use 
remote application debugging? But still this does not prevent unit tests 
failing with multi-module configuration because of this dependent 
project classpath has those artifacts in it's classpath before it's own 
ones.


So if you have solution to this i am more than happy to hear it.

Markku

On 2.3.2012 17:50, Ron Wheeler wrote:
We have been developing and maintaining a large  portal application 
with over 70 WAR files in Eclipse with Maven since 2007 and several 
smaller portals and standalone applications. We have not had this 
problem.


That is not to say that I am an expert in Eclipse but we know enough 
to make it work.


We do not use maven-eclipse-plug-in. We use the assembly plug-in to 
build our war files.

Perhaps that is the difference.

We also deploy to Tomcat which might be a better servlet engine than 
Glassfish.


I am not sure how relevant our experience is to your problem but if I 
can provide any additional information that you think might help, let 
me know.


Ron


On 02/03/2012 10:19 AM, Markku Saarela wrote:

Hi,

You don't understand how Eclipse IDE works. Eclipse does not have 
different classpaths for testing and actual runtime. So Eclipse basic 
design is faulty. There is bug open since 2008 to provide means to 
tell Eclipse that which are test sources and not include them to 
runtime classpath. https://bugs.eclipse.org/bugs/show_bug.cgi?id=224708


So everything under src/test goes also into GlassFish server if you 
deploy application in Eclipse. That causes that those unit test 
properties and configuration and classes are picked first and they 
are effective and application does not work.


Even worst if you have multi-module project and B module is dependent 
from A and A project defines SPI interface and has in src/test/java 
test implementation for that and of course in 
src/test/resources/META-INF/services SPI file for exposing that test 
SPI implementation then if B implements also that SPI interface and 
put SPI file in src/main/resources/META-INF/services, you cannot test 
you implementation via ServiceLoader because it pick's that module A 
test implementation. Same goes for properties and everything else.


Of course NetBeans and IntelliJ has correct way to do things but they 
are not an option.


Markku


On 2.3.2012 15:15, Ron Wheeler wrote:

On 02/03/2012 1:32 AM, Markku Saarela wrote:

Hi,

Developing with Eclipse IDE and JavaEE server using 
maven-eclipse-plugin you have to use profiles, because Eclipse does 
not isolate test code and test resources.

Eclipse does
/src/main/   code
/src/test   ... test code and resources

You need to set your maven properly but it works fine unless I don't 
understand your issue.




Only way to do it what i have figured out is to have two profiles 
one for running application in app server and another for unit 
testing same code.  Those profiles has only resources and 
testResources definitions.


Separating test code for separate code is not an option, because 
then Sonar reports 0 % coverage.


rgds,

Markku

On 1.3.2012 22:55, Ron Wheeler wrote:

On 01/03/2012 2:43 PM, offbyone wrote:
Ok so I should create a base pom with a war configuration and 
then a separate
pom for each site that depends on this with overlays to add the 
extra

configuration file.
I will try.

If I am interpreting your comments correctly, profiles allow for 
a user to
flaten a maven build deployment, but this is a bad practice and 
it is better

to make your maven structure deep.

So are profiles going to be deprecated?   I would think I am not 
alone in
getting turned down the wrong path because most of the 
documentation/howtos

I have found point to using profiles.
There are some uses for profiles that seem harmless so it is a 
documentation issue.


It is fairly common in Apache documentation for the programmers to 
make a big deal about all the wonderful things that the package 
can do.

They are not particularly concerned about Best Practices.

The most common usage is often left out of the documentation since 
it is dull or not very impressive.
This sometimes means that obscure usage of features or seldom used 
features are heavily documented while the main use case is  not 
described.


New Maven users often fall into the trap that you were headed into.

A really simple Best Practice that most people use, is hard to 
find in the documentation while an obscure Worst Practice is 
described because it shows how clever the software developers are 
and how powerful the product is.


There should be a Best Practice section on the Maven site 
describing the best way to implement the common software 
development patterns.


There are not really a lot of cases

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Ron Wheeler]

I am not sure if this directly answers your question but perhaps a bit 
of background helps.


We use Eclipse STS which comes with Maven support built in. We used to 
waste so much time upgrading Eclipse and getting everyone configured in 
the same way.
Now it is a single download (BIG) to get everything that you need except 
Subversion.


We have individual projects since the project is divided up on 
functional lines with core modules for the database access and some 
modules that can best be described as utilities (messaging for example).
This means that for any maintenance activity almost all of the modules 
are not affected.

In addition, modules are worked on by different people.
No one would have all of modules checked out at once. Certainly you 
would not have them open in Eclipse.


We use SNAPSHOTs during development and maintenance.
We do not make all of the 70 modules carry the same release version. It 
is possible to see a version 1.10.3 of the overall application running 
with most of the WAR files as version 1.10 if they were bug free up to 
the 1.10.3 release.


We do some unit testing and do most of our testing on the developer's 
workstation.
We have at least 1 test server where developers can test in an 
environment that is almost identical to production and can be tested by 
the client(s). More than 1 if we have a big maintenance issue while we 
are trying to get a major development tested. We are starting to use the 
cloud for this so the actual number of test servers potentially 
available is close to infinite.


We deploy the WAR files by hand to the appropriate server.

We use JNDI to support our Spring configurations so we do not have any 
variation in the WARs between test and different production servers.


This is certainly not the only way to do things but I have never heard 
of any problems with test classes or test configurations leaking into 
production.


The build is described in the master POM for the project. The master POM 
is the key to every project and contains everything that is common 
between modules so the module poms are pretty small.


Below is the build description from the master POM for a project.
I hope that this helps a bit.

Ron

build
sourceDirectorysrc/main/sourceDirectory
scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory
testSourceDirectorysrc/test/testSourceDirectory
outputDirectorytarget/classes/outputDirectory
testOutputDirectorytarget/test-classes/testOutputDirectory
resources
resource
directorysrc/main/directory
excludes
exclude**/*.java/exclude
/excludes
/resource
/resources
testResources
testResource
directorytest/directory
excludes
exclude**/*.java/exclude
/excludes
/testResource
/testResources
directorytarget/directory
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
configuration
encodingUTF-8/encoding
source1.6/source
target1.6/target
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-resources-plugin/artifactId
version2.5/version
configuration
encodingUTF-8/encoding
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.2/version
configuration
warSourceDirectoryWebContent/warSourceDirectory
archive
manifest
addDefaultImplementationEntriestrue/addDefaultImplementationEntries
addDefaultSpecificationEntriestrue/addDefaultSpecificationEntries
/manifest
/archive
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
version2.4/version
configuration
archive
manifest
addDefaultImplementationEntriestrue/addDefaultImplementationEntries
addDefaultSpecificationEntriestrue/addDefaultSpecificationEntries
/manifest
/archive
/configuration
/plugin

/plugins
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.3/version
executions
execution
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
archive
manifest
addDefaultImplementationEntriestrue/addDefaultImplementationEntries
addDefaultSpecificationEntriestrue/addDefaultSpecificationEntries
/manifest
/archive
descriptorRefs
descriptorRef
jar-with-dependencies
/descriptorRef
/descriptorRefs

/configuration
/execution
/executions
/plugin

/plugins
/pluginManagement
/build

Ron


On 02/03/2012 2:00 PM, Markku Saarela wrote:
In multi-module project i hit the same problem with m2e and 
maven-eclipse-plugin. Are you saying not to import multi-module 
projects into Eclipse, instead every module separately? Or you don't 
use server plugins to deploy application instead you deploy outside 
Eclipse and use remote application debugging? But still this does not 
prevent unit tests failing with multi-module configuration because of 
this dependent project classpath has those artifacts in it's classpath 
before it's own ones.


So if you have solution to this i am more than

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Markku Saarela]

/addDefaultSpecificationEntries
/manifest
/archive
descriptorRefs
descriptorRef
jar-with-dependencies
/descriptorRef
/descriptorRefs

/configuration
/execution
/executions
/plugin

/plugins
/pluginManagement
/build

Ron


On 02/03/2012 2:00 PM, Markku Saarela wrote:
In multi-module project i hit the same problem with m2e and 
maven-eclipse-plugin. Are you saying not to import multi-module 
projects into Eclipse, instead every module separately? Or you don't 
use server plugins to deploy application instead you deploy outside 
Eclipse and use remote application debugging? But still this does not 
prevent unit tests failing with multi-module configuration because of 
this dependent project classpath has those artifacts in it's 
classpath before it's own ones.


So if you have solution to this i am more than happy to hear it.

Markku

On 2.3.2012 17:50, Ron Wheeler wrote:
We have been developing and maintaining a large  portal application 
with over 70 WAR files in Eclipse with Maven since 2007 and several 
smaller portals and standalone applications. We have not had this 
problem.


That is not to say that I am an expert in Eclipse but we know enough 
to make it work.


We do not use maven-eclipse-plug-in. We use the assembly plug-in to 
build our war files.

Perhaps that is the difference.

We also deploy to Tomcat which might be a better servlet engine than 
Glassfish.


I am not sure how relevant our experience is to your problem but if 
I can provide any additional information that you think might help, 
let me know.


Ron


On 02/03/2012 10:19 AM, Markku Saarela wrote:

Hi,

You don't understand how Eclipse IDE works. Eclipse does not have 
different classpaths for testing and actual runtime. So Eclipse 
basic design is faulty. There is bug open since 2008 to provide 
means to tell Eclipse that which are test sources and not include 
them to runtime classpath. 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=224708


So everything under src/test goes also into GlassFish server if you 
deploy application in Eclipse. That causes that those unit test 
properties and configuration and classes are picked first and they 
are effective and application does not work.


Even worst if you have multi-module project and B module is 
dependent from A and A project defines SPI interface and has in 
src/test/java test implementation for that and of course in 
src/test/resources/META-INF/services SPI file for exposing that 
test SPI implementation then if B implements also that SPI 
interface and put SPI file in src/main/resources/META-INF/services, 
you cannot test you implementation via ServiceLoader because it 
pick's that module A test implementation. Same goes for properties 
and everything else.


Of course NetBeans and IntelliJ has correct way to do things but 
they are not an option.


Markku


On 2.3.2012 15:15, Ron Wheeler wrote:

On 02/03/2012 1:32 AM, Markku Saarela wrote:

Hi,

Developing with Eclipse IDE and JavaEE server using 
maven-eclipse-plugin you have to use profiles, because Eclipse 
does not isolate test code and test resources.

Eclipse does
/src/main/   code
/src/test   ... test code and resources

You need to set your maven properly but it works fine unless I 
don't understand your issue.




Only way to do it what i have figured out is to have two profiles 
one for running application in app server and another for unit 
testing same code.  Those profiles has only resources and 
testResources definitions.


Separating test code for separate code is not an option, because 
then Sonar reports 0 % coverage.


rgds,

Markku





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Markku Saarela]

Hi,

Developing with Eclipse IDE and JavaEE server using maven-eclipse-plugin 
you have to use profiles, because Eclipse does not isolate test code and 
test resources.


Only way to do it what i have figured out is to have two profiles one 
for running application in app server and another for unit testing same 
code.  Those profiles has only resources and testResources definitions.


Separating test code for separate code is not an option, because then 
Sonar reports 0 % coverage.


rgds,

Markku

On 1.3.2012 22:55, Ron Wheeler wrote:

On 01/03/2012 2:43 PM, offbyone wrote:
Ok so I should create a base pom with a war configuration and then a 
separate

pom for each site that depends on this with overlays to add the extra
configuration file.
I will try.

If I am interpreting your comments correctly, profiles allow for a 
user to
flaten a maven build deployment, but this is a bad practice and it is 
better

to make your maven structure deep.

So are profiles going to be deprecated?   I would think I am not 
alone in
getting turned down the wrong path because most of the 
documentation/howtos

I have found point to using profiles.
There are some uses for profiles that seem harmless so it is a 
documentation issue.


It is fairly common in Apache documentation for the programmers to 
make a big deal about all the wonderful things that the package can do.

They are not particularly concerned about Best Practices.

The most common usage is often left out of the documentation since it 
is dull or not very impressive.
This sometimes means that obscure usage of features or seldom used 
features are heavily documented while the main use case is  not 
described.


New Maven users often fall into the trap that you were headed into.

A really simple Best Practice that most people use, is hard to find 
in the documentation while an obscure Worst Practice is described 
because it shows how clever the software developers are and how 
powerful the product is.


There should be a Best Practice section on the Maven site describing 
the best way to implement the common software development patterns.


There are not really a lot of cases to consider but every new Maven 
user has to sort out their own case.


Ron



--
View this message in context: 
http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5528994.html

Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org







-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

difference between eclipse plugin for maven and maven plugin for eclipse

[sarmahdi]

Hello All!

I am confused and i cant seem to undertand this thing :

There is a eclipse plugin for maven that can be downloaded from eclipse ( I
am trying to download one for RSA 7.0 but cannot find it)

Then there is a maven plugin for eclipse 
http://maven.apache.org/plugins/maven-eclipse-plugin/ mave-eclipse-plugin  

If i use this will i be able to use that project as an eclipse project. then
what is the difference between the first plugin that eclipse downloads or do
i need both?

Thank
Syed...

--
View this message in context: 
http://maven.40175.n5.nabble.com/difference-between-eclipse-plugin-for-maven-and-maven-plugin-for-eclipse-tp5515369p5515369.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: difference between eclipse plugin for maven and maven plugin for eclipse

[Barrie Treloar]

On Sun, Feb 26, 2012 at 2:55 AM, sarmahdi sarma...@hotmail.com wrote:
 Hello All!

 I am confused and i cant seem to undertand this thing :

It's very simple.

 There is a eclipse plugin for maven that can be downloaded from eclipse ( I
 am trying to download one for RSA 7.0 but cannot find it)

This is an Eclipse plugin (not a Maven one) so it runs directly inside eclipse.
It allows you to run maven command from within Eclipse and also
provides Eclipse editors for pom.xml files.
RSA is often too far behind the main Eclipse release, so you may need
to convince it to find things, etc, but it should just be a matter of
following the instructions at http://www.eclipse.org/m2e/

 Then there is a maven plugin for eclipse
 http://maven.apache.org/plugins/maven-eclipse-plugin/ mave-eclipse-plugin

This is a Maven plugin (not an Eclipse one)
It will build the Eclipse files .classpath, .project and a few others
so that you can import your Maven project into Eclipse all configured
and ready to go.
It saves you from manually doing this.
Since it does not run in Eclipse, every time you want to do anything
you need to use a console prompt to run Maven (just like you normally
would).
If your dependencies change, you will need to re-run the
maven-eclipse-plugin to reconfigure Eclipse with the changes.

 If i use this will i be able to use that project as an eclipse project. then
 what is the difference between the first plugin that eclipse downloads or do
 i need both?

Be warned: You can not run both.

m2e will not load a project that has had maven-eclipse-plugin run against it.

However you can try one or the other and see which you prefer.
Just remember to start with a clean checkout each time.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: difference between eclipse plugin for maven and maven plugin for eclipse

[Ron Wheeler]

Just in case you have not found this; the Eclipse STS from Springsource 
comes all set up to work with Maven right out of the box with no extra 
downloads required.
Saves a lot of screwing around that you have to do with a stock Eclipse 
to get a useful IDE.


Ron


On 25/02/2012 5:41 PM, Barrie Treloar wrote:

On Sun, Feb 26, 2012 at 2:55 AM, sarmahdisarma...@hotmail.com  wrote:

Hello All!

I am confused and i cant seem to undertand this thing :

It's very simple.


There is a eclipse plugin for maven that can be downloaded from eclipse ( I
am trying to download one for RSA 7.0 but cannot find it)

This is an Eclipse plugin (not a Maven one) so it runs directly inside eclipse.
It allows you to run maven command from within Eclipse and also
provides Eclipse editors for pom.xml files.
RSA is often too far behind the main Eclipse release, so you may need
to convince it to find things, etc, but it should just be a matter of
following the instructions at http://www.eclipse.org/m2e/


Then there is a maven plugin for eclipse
http://maven.apache.org/plugins/maven-eclipse-plugin/ mave-eclipse-plugin

This is a Maven plugin (not an Eclipse one)
It will build the Eclipse files .classpath, .project and a few others
so that you can import your Maven project into Eclipse all configured
and ready to go.
It saves you from manually doing this.
Since it does not run in Eclipse, every time you want to do anything
you need to use a console prompt to run Maven (just like you normally
would).
If your dependencies change, you will need to re-run the
maven-eclipse-plugin to reconfigure Eclipse with the changes.


If i use this will i be able to use that project as an eclipse project. then
what is the difference between the first plugin that eclipse downloads or do
i need both?

Be warned: You can not run both.

m2e will not load a project that has had maven-eclipse-plugin run against it.

However you can try one or the other and see which you prefer.
Just remember to start with a clean checkout each time.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Eclipse Plugin 2.9 Released

[Barrie Treloar]

The Maven team is pleased to announce the release of the Maven Eclipse
Plugin, version 2.9

The Maven Eclipse Plugin is used to generate Eclipse IDE files
(*.classpath, *.wtpmodules and the .settings folder) for use with a
project.

http://maven.apache.org/plugins/maven-eclipse-plugin/

[Please see  Maven Integration for Eclipse m2e
(http://eclipse.org/m2e/) if you want Maven embedded in Eclipse.]

You should specify the version in your project's plugin configuration:

plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-eclipse-plugin/artifactId
  version2.9/version
/plugin

Release Notes - Maven 2.x Eclipse Plugin - Version 2.9

** Bug
* [MECLIPSE-388] - Correct classpath ordering in .classpath
* [MECLIPSE-434] - WTP 2.0 Documentation
* [MECLIPSE-472] - Bad dependencies (version  list) in .classpath
whereas compilation (and dependency:tree) use the rigth one
* [MECLIPSE-548] - MECLIPSE-442 should be reverted. Classpath
container entries should come before 3rd party jars in .classpath
* [MECLIPSE-576] - Merge resource dirs shall pass gracefully
* [MECLIPSE-585] - [regression] plugin fails to create Eclipse
projects in 2.7
* [MECLIPSE-587] - maven-eclipse-plugin creates wrong
org.eclipse.wst.common.project.facet.core.xml for ear-projects when
javaee:javaee-api s used
* [MECLIPSE-597] - Workspace dependencies not resolved for
SNAPSHOT dependencies (artifact has a different version from that in
dependency management)
* [MECLIPSE-599] - Broken link to j2ee-simple.tar.gz on
multi-module-projects.html
* [MECLIPSE-605] - JRE position in Eclipse generated classpath is
different from the one used in Maven compiler
* [MECLIPSE-621] - mvn eclipse:eclipse fails or doesn't generate
proper .classpath when specifying the same resource directory with
different filtering rules
* [MECLIPSE-627] - Wrong classname used in documentation at
additionalBuildcommands
* [MECLIPSE-642] - String index out of range during
eclipse:eclipse for a project that works with 2.7
* [MECLIPSE-665] - wrong classpath order generated in .classpath
file for transitive dependencies
* [MECLIPSE-669] - Don't report missing source/javadoc jars when
download is false
* [MECLIPSE-676] - linkedResources: location vs locationURI
* [MECLIPSE-692] - .project contains projects which were skipped
during reactor build

** Improvement
* [MECLIPSE-350] - Allow to bypass the automatic search of JEE
(and related) APIs versions
* [MECLIPSE-499] - Improve eclipse:eclipse excludes option
* [MECLIPSE-652] - Ability to map a webapp to the root context
* [MECLIPSE-691] - Add Websphere 7 runtime support
* [MECLIPSE-693] - Some generated xml files are missing their xml-header
* [MECLIPSE-694] - Add JEE6 support
* [MECLIPSE-696] - Allow file contents to be obtained from url or
location does not work behind a firewall

** New Feature
* [MECLIPSE-561] - Provide a way to choose .classpath ordering
test-first vs. test-last

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Setup for Existing Plugin Development Project(Eclipse Plugin)

[Barrie Treloar]

On Mon, Jan 30, 2012 at 4:38 PM, Singh, Harsimranjit (NSN -
IN/Bangalore) harsimranjit.si...@nsn.com wrote:
 Hi

 I have to use maven and that maven 2 only so option left

Why Maven 2 only?
Maven 3 should be backwards compatible for your needs.

 1) Upgrade to latest version of Eclipse PDE:
 Can you explain about this I am not suire how it will help?

I assume you are using an older Eclipse PDE version.
You will need to go through more steps, e.g. populating your local
Repository Manager with Eclipse artefacts, if you don't upgrade.

The newer eclipse artefacts are available in a Maven repository.
e.g. http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.eclipse%22
I'm not sure where 3.3+ jars are located, I went looking but couldn't
locate the documentation.
I thought sonatype were providing a Nexus instance which had this stuff in it.


 2) pde-maven-plugin:

 Which approach you follow to use pde-maven-plugin?.Some reference apart
 from that link?

Not really.

Try googling.

All pde-maven-plugin does is call out via a shell to invoke the
Eclipse PDE ant build scripts.
Its ugly but it will work.

If you go down this path beware of the dragons.

You would have more chances of success by trying tycho instead.
At least there is a user list where you could ask questions.
You are on your own with pde-maven-plugin.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Maven Setup for Existing Plugin Development Project(Eclipse Plugin)

[Singh, Harsimranjit (NSN - IN/Bangalore)]

Any Help on maven 2 

I am not able to use pde-maven-plugin in my existing PDE project?


-Original Message-
From: Singh, Harsimranjit (NSN - IN/Bangalore) 
Sent: Monday, January 30, 2012 11:38 AM
To: Maven Users List
Subject: RE: Maven Setup for Existing Plugin Development Project(Eclipse
Plugin)

Hi 

I have to use maven and that maven 2 only so option left

1) Upgrade to latest version of Eclipse PDE:
Can you explain about this I am not suire how it will help?

2) pde-maven-plugin:

Which approach you follow to use pde-maven-plugin?.Some reference apart
from that link?



-Original Message-
From: ext Barrie Treloar [mailto:baerr...@gmail.com] 
Sent: Monday, January 30, 2012 11:26 AM
To: Maven Users List
Subject: Re: Maven Setup for Existing Plugin Development Project(Eclipse
Plugin)

On Mon, Jan 30, 2012 at 3:46 PM, Singh, Harsimranjit (NSN -
IN/Bangalore) harsimranjit.si...@nsn.com wrote:
 Hi

 Thanks for reply . I am using Maven 2.2.1

 Is sonatype support maven 2?

 Also I found:
 http://mojo.codehaus.org/pde-maven-plugin/


 So which one I should use?

pde-maven-plugin is dead, but usable.

Your options include:
* Upgrade to Maven 3+
* Upgrade to latest version of Eclipse PDE
* Dont use Maven

I'd recommend upgrading Eclipse PDE anyway as you not find any Eclipse
jars available for the older environment.

We are stuck on Eclipse RCP 3.2.2 and use pde-maven-plugin fine.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven Setup for Existing Plugin Development Project(Eclipse Plugin)

[Singh, Harsimranjit (NSN - IN/Bangalore)]

Hi 

I have Old Project for Eclipse plug-in Development.I want to  bring that
in maven but not helping.

Is this possible?

I searched lot but not find much details\help.Please provide help me or
provide some reference link.

Thanks
Harsimran

Re: Maven Setup for Existing Plugin Development Project(Eclipse Plugin)

[Dan Tran]

lookup tycho-maven-plugin from sonatype

-D

On Sun, Jan 29, 2012 at 7:31 PM, Singh, Harsimranjit (NSN -
IN/Bangalore) harsimranjit.si...@nsn.com wrote:
 Hi

 I have Old Project for Eclipse plug-in Development.I want to  bring that
 in maven but not helping.

 Is this possible?

 I searched lot but not find much details\help.Please provide help me or
 provide some reference link.

 Thanks
 Harsimran

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Maven Setup for Existing Plugin Development Project(Eclipse Plugin)

[Singh, Harsimranjit (NSN - IN/Bangalore)]

Hi 

Thanks for reply . I am using Maven 2.2.1

Is sonatype support maven 2?

Also I found:
http://mojo.codehaus.org/pde-maven-plugin/


So which one I should use?

thanks

-Original Message-
From: ext Dan Tran [mailto:dant...@gmail.com] 
Sent: Monday, January 30, 2012 9:32 AM
To: Maven Users List
Subject: Re: Maven Setup for Existing Plugin Development Project(Eclipse Plugin)

lookup tycho-maven-plugin from sonatype

-D

On Sun, Jan 29, 2012 at 7:31 PM, Singh, Harsimranjit (NSN -
IN/Bangalore) harsimranjit.si...@nsn.com wrote:
 Hi

 I have Old Project for Eclipse plug-in Development.I want to  bring that
 in maven but not helping.

 Is this possible?

 I searched lot but not find much details\help.Please provide help me or
 provide some reference link.

 Thanks
 Harsimran

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Setup for Existing Plugin Development Project(Eclipse Plugin)

[Barrie Treloar]

On Mon, Jan 30, 2012 at 3:46 PM, Singh, Harsimranjit (NSN -
IN/Bangalore) harsimranjit.si...@nsn.com wrote:
 Hi

 Thanks for reply . I am using Maven 2.2.1

 Is sonatype support maven 2?

 Also I found:
 http://mojo.codehaus.org/pde-maven-plugin/


 So which one I should use?

pde-maven-plugin is dead, but usable.

Your options include:
* Upgrade to Maven 3+
* Upgrade to latest version of Eclipse PDE
* Dont use Maven

I'd recommend upgrading Eclipse PDE anyway as you not find any Eclipse
jars available for the older environment.

We are stuck on Eclipse RCP 3.2.2 and use pde-maven-plugin fine.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Maven Setup for Existing Plugin Development Project(Eclipse Plugin)

[Singh, Harsimranjit (NSN - IN/Bangalore)]

Hi 

I have to use maven and that maven 2 only so option left

1) Upgrade to latest version of Eclipse PDE:
Can you explain about this I am not suire how it will help?

2) pde-maven-plugin:

Which approach you follow to use pde-maven-plugin?.Some reference apart
from that link?



-Original Message-
From: ext Barrie Treloar [mailto:baerr...@gmail.com] 
Sent: Monday, January 30, 2012 11:26 AM
To: Maven Users List
Subject: Re: Maven Setup for Existing Plugin Development Project(Eclipse
Plugin)

On Mon, Jan 30, 2012 at 3:46 PM, Singh, Harsimranjit (NSN -
IN/Bangalore) harsimranjit.si...@nsn.com wrote:
 Hi

 Thanks for reply . I am using Maven 2.2.1

 Is sonatype support maven 2?

 Also I found:
 http://mojo.codehaus.org/pde-maven-plugin/


 So which one I should use?

pde-maven-plugin is dead, but usable.

Your options include:
* Upgrade to Maven 3+
* Upgrade to latest version of Eclipse PDE
* Dont use Maven

I'd recommend upgrading Eclipse PDE anyway as you not find any Eclipse
jars available for the older environment.

We are stuck on Eclipse RCP 3.2.2 and use pde-maven-plugin fine.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Anyone help me about classpathContainers in maven-eclipse-plugin?

[Barrie Treloar]

On Tue, Dec 20, 2011 at 4:45 PM, zuxiong lin linzuxiong1...@gmail.com wrote:
 I have a webapp project under eclipse by my colleage. So it has WEB-INF/lib
 directory
 and dependcy packages are put in by my colleage.

 Now I have create a pom file for the project. But import the maven project ,
 I also need to configurate the classpath for it through
 project --properties--Java Build Path--Libraries -- Add Library -- Web
 App Libraries--...
 Why does it still need the classpath ???How do I fix it ?
 By the way , we use eclipse-jee version 3.7 SR1

 like :
 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-eclipse-plugin/artifactId
 version2.8/version
 configuration
 wtpmanifesttrue/wtpmanifest
 wtpapplicationxmltrue/wtpapplicationxml
 projectnatures
 projectnatureorg.eclipse.jdt.core.javanature/projectnature
 projectnatureorg.eclipse.wst.common.modulecore.ModuleCoreNature/projectnature
 projectnatureorg.eclipse.jem.workbench.JavaEMFNature/projectnature
 projectnatureorg.eclipse.wst.common.project.facet.core.nature/projectnature
 /projectnatures
 classpathContainers
 classpathContainerorg.eclipse.jdt.launching.JRE_CONTAINER/classpathContainer
 !--
 classpathContainerorg.eclipse.jst.j2ee.internal.web.container/artifact/classpathContainer
 --
 classpathContainerorg.eclipse.jst.j2ee.internal.web.container/classpathContainer
 !--
 classpathContainerorg.eclipse.jst.j2ee.internal.module.container/classpathContainer
 --
 /classpathContainers
 /configuration
 /plugin

I dont see a WTP specification in your plugin settings.
http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html

I dont use WTP so you will have to read the docs and do some fiddling.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Anyone help me about classpathContainers in maven-eclipse-plugin?

[zuxiong lin]

classpathContainerorg.eclipse.jst.j2ee.internal.web.container/classpathContainer
is not right???
wtpapplicationxmltrue/wtpapplicationxml is not right , too??
But I donot get any useful details in
http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html

2011/12/20 Barrie Treloar baerr...@gmail.com

 On Tue, Dec 20, 2011 at 4:45 PM, zuxiong lin linzuxiong1...@gmail.com
 wrote:
  I have a webapp project under eclipse by my colleage. So it has
 WEB-INF/lib
  directory
  and dependcy packages are put in by my colleage.
 
  Now I have create a pom file for the project. But import the maven
 project ,
  I also need to configurate the classpath for it through
  project --properties--Java Build Path--Libraries -- Add Library --
 Web
  App Libraries--...
  Why does it still need the classpath ???How do I fix it ?
  By the way , we use eclipse-jee version 3.7 SR1
 
  like :
  plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-eclipse-plugin/artifactId
  version2.8/version
  configuration
  wtpmanifesttrue/wtpmanifest
  wtpapplicationxmltrue/wtpapplicationxml
  projectnatures
  projectnatureorg.eclipse.jdt.core.javanature/projectnature
 
 projectnatureorg.eclipse.wst.common.modulecore.ModuleCoreNature/projectnature
  projectnatureorg.eclipse.jem.workbench.JavaEMFNature/projectnature
 
 projectnatureorg.eclipse.wst.common.project.facet.core.nature/projectnature
  /projectnatures
  classpathContainers
 
 classpathContainerorg.eclipse.jdt.launching.JRE_CONTAINER/classpathContainer
  !--
 
 classpathContainerorg.eclipse.jst.j2ee.internal.web.container/artifact/classpathContainer
  --
 
 classpathContainerorg.eclipse.jst.j2ee.internal.web.container/classpathContainer
  !--
 
 classpathContainerorg.eclipse.jst.j2ee.internal.module.container/classpathContainer
  --
  /classpathContainers
  /configuration
  /plugin

 I dont see a WTP specification in your plugin settings.
 http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html

 I dont use WTP so you will have to read the docs and do some fiddling.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Anyone help me about classpathContainers in maven-eclipse-plugin?

[zuxiong lin]

I have a webapp project under eclipse by my colleage. So it has WEB-INF/lib
directory
and dependcy packages are put in by my colleage.

Now I have create a pom file for the project. But import the maven project
, I also need to configurate the classpath for it through
project --properties--Java Build Path--Libraries -- Add Library -- Web
App Libraries--...
Why does it still need the classpath ???How do I fix it ?
By the way , we use eclipse-jee version 3.7 SR1

like :
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.8/version
configuration
wtpmanifesttrue/wtpmanifest
wtpapplicationxmltrue/wtpapplicationxml
projectnatures
projectnatureorg.eclipse.jdt.core.javanature/projectnature
projectnatureorg.eclipse.wst.common.modulecore.ModuleCoreNature/projectnature
projectnatureorg.eclipse.jem.workbench.JavaEMFNature/projectnature
projectnatureorg.eclipse.wst.common.project.facet.core.nature/projectnature
/projectnatures
classpathContainers
classpathContainerorg.eclipse.jdt.launching.JRE_CONTAINER/classpathContainer
!--
classpathContainerorg.eclipse.jst.j2ee.internal.web.container/artifact/classpathContainer
--
classpathContainerorg.eclipse.jst.j2ee.internal.web.container/classpathContainer
!--
classpathContainerorg.eclipse.jst.j2ee.internal.module.container/classpathContainer
--
/classpathContainers
/configuration
/plugin
More details in the POM of attachment.
Thanks.
project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
	xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;

	modelVersion4.0.0/modelVersion
	groupIdcom.kingsoft.tpan/groupId
	artifactIdappsvr/artifactId
	packagingwar/packaging
	version3.1.${BUILD_NUMBER}-RELEASE/version
	nameappsvr3.1/name
	urlhttp://maven.apache.org/url
	dependencies
		dependency
			groupIdjunit/groupId
			artifactIdjunit/artifactId
			version4.8.1/version
			scopetest/scope
		/dependency
		!--这里下面的两个dependency, servlet-api与jsp-api所需 --
		dependency
			groupIdjavax.servlet/groupId
			artifactIdservlet-api/artifactId
			version2.5/version
			scopeprovided/scope
		/dependency
		dependency
			groupIdjavax.servlet.jsp/groupId
			artifactIdjsp-api/artifactId
			version2.1/version
			scopeprovided/scope
		/dependency
	/dependencies
	build
		finalName${project.artifactId}-${project.version}/finalName
		plugins
			plugin
groupIdcom.google.code.maven-replacer-plugin/groupId
artifactIdmaven-replacer-plugin/artifactId
version1.3.8/version
executions
	execution
		phaseprepare-package/phase
		goals
			goalreplace/goal
		/goals
	/execution
/executions
configuration
	ignoreMissingFiletrue/ignoreMissingFile
	filesrc/main/resources/build.version/file
	outputFiletarget/classes/build.version/outputFile
	regexfalse/regex
	replacements
		replacement
			token$BUILD_NUMBER$/token
			value${BUILD_NUMBER}/value
		/replacement
		replacement
			token$LABEL$/token
			value${project.artifactId}-${project.version}/value
		/replacement
	/replacements
/configuration
			/plugin
			plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-resources-plugin/artifactId
version2.5/version
configuration
	encodingUTF-8/encoding
/configuration
			/plugin
			plugin
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
configuration
	compilerArguments
		extdirs${basedir}/src/main/webapp/WEB-INF/lib/extdirs
	/compilerArguments
	source1.6/source
	target1.6/target
	encodingUTF-8/encoding
/configuration
			/plugin
			plugin
artifactIdmaven-surefire-plugin/artifactId
version2.9/version
configuration
	argLine-Xmx256m -XX:PermSize=256m -XX:MaxPermSize=256m/argLine
	skipfalse/skip
	includes
		include**/AppSvrPBApiTest.java/include
		include**/AppSvrPBApiPartitionTest.java/include
	/includes
	disableXmlReportfalse/disableXmlReport
	printSummarytrue/printSummary
	enableAssertionsfalse/enableAssertions
	useManifestOnlyJarfalse/useManifestOnlyJar
	forkModealways/forkMode
	additionalClasspathElements
		additionalClasspathElement${basedir}/src/main/webapp/WEB-INF/lib/apache-mime4j-0.6.jar/additionalClasspathElement
		additionalClasspathElement${basedir}/src/main/webapp/WEB-INF/lib/commons-io-1.4.jar/additionalClasspathElement
		additionalClasspathElement${basedir}/src/main/webapp/WEB-INF/lib/httpclient-4.0.jar/additionalClasspathElement
		additionalClasspathElement${basedir}/src/main/webapp/WEB-INF/lib/httpcore-4.0.1.jar/additionalClasspathElement
		additionalClasspathElement${basedir}/src/main/webapp/WEB-INF/lib/httpcore-nio-4.0.1.jar/additionalClasspathElement
		additionalClasspathElement${basedir}/src/main/webapp/WEB-INF/lib/httpmime-4.0.jar/additionalClasspathElement
		additionalClasspathElement${basedir}/src/main/webapp/WEB

Re: Does maven eclipse plugin downloads unnecesary artifacts?

[Gabriel Belingueres]

Thanks Barrie!

2011/11/18 Barrie Treloar baerr...@gmail.com:
 On Fri, Nov 18, 2011 at 6:19 AM, Gabriel Belingueres
 belingue...@gmail.com wrote:
 Hi!

 I usually use the maven eclipse plugin (v2.8) using the
 downloadSources and downloadJavadocs properties, however I added some
 runtime scoped dependency but the eclipse plugin downloads the
 sources.jar and javadoc.jar too of that library (also no other
 dependency depends on that runtime scoped library).

 I agree beforehand that it is no harm to download the sources or
 javadocs, I just wonder if it is really needed, it is a plugin bug or
 it is just how maven works for all plugins.

 I'm not really awake enough to remember the details, but I think the
 eclipse plugin needs to setup your classpath to also include the
 runtime dependencies.
 When configuring the classpath Eclipse does not know about Maven's
 scopes so everything is treated the same - i.e. attempting to get
 sources or javadocs.
 This may come in handy when you run your app inside eclipse and you
 find a bug in a runtime depenendency.
 When you debug and step into the .class file you will have the sources
 available.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Does maven eclipse plugin downloads unnecesary artifacts?

[Gabriel Belingueres]

Hi!

I usually use the maven eclipse plugin (v2.8) using the
downloadSources and downloadJavadocs properties, however I added some
runtime scoped dependency but the eclipse plugin downloads the
sources.jar and javadoc.jar too of that library (also no other
dependency depends on that runtime scoped library).

I agree beforehand that it is no harm to download the sources or
javadocs, I just wonder if it is really needed, it is a plugin bug or
it is just how maven works for all plugins.

Regards,
Gabriel

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Does maven eclipse plugin downloads unnecesary artifacts?

[Barrie Treloar]

On Fri, Nov 18, 2011 at 6:19 AM, Gabriel Belingueres
belingue...@gmail.com wrote:
 Hi!

 I usually use the maven eclipse plugin (v2.8) using the
 downloadSources and downloadJavadocs properties, however I added some
 runtime scoped dependency but the eclipse plugin downloads the
 sources.jar and javadoc.jar too of that library (also no other
 dependency depends on that runtime scoped library).

 I agree beforehand that it is no harm to download the sources or
 javadocs, I just wonder if it is really needed, it is a plugin bug or
 it is just how maven works for all plugins.

I'm not really awake enough to remember the details, but I think the
eclipse plugin needs to setup your classpath to also include the
runtime dependencies.
When configuring the classpath Eclipse does not know about Maven's
scopes so everything is treated the same - i.e. attempting to get
sources or javadocs.
This may come in handy when you run your app inside eclipse and you
find a bug in a runtime depenendency.
When you debug and step into the .class file you will have the sources
available.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Execution default-cli of goal org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse failed. NullPointerException

[Pankaj Pai]

Hi Everyone,

I am receiving the below error when I try to use the maven plugin for
eclipse. Could you please take a look and let me know what is that I am
doing wrong.

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse (default-cli) on
project chapter6: Execution default-cli of goal
org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse failed.
NullPointerException - [Help 1]

LogFile contents;

Apache Maven 3.0.3 (r1075438; 2011-02-28 23:01:09+0530)
Maven home: F:\Maven\apache-maven-3.0.3
Java version: 1.7.0, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from
F:\Maven\apache-maven-3.0.3\conf\settings.xml
[DEBUG] Reading user settings from C:\Users\pankaj\.m2\settings.xml
[DEBUG] Using local repository at C:\Users\pankaj\.m2\repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for
C:\Users\pankaj\.m2\repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project ruleplayer:chapter6:jar:1.0-SNAPSHOT:
(none)
[DEBUG] Looking up lifecyle mappings for packaging jar from
ClassRealm[plexus.core, parent: null]
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for ruleplayer:chapter6:jar:1.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-jar-plugin is missing. @ line 78, column 21
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-eclipse-plugin is missing. @ line 69, column
21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[DEBUG] Resolving plugin version for
org.apache.maven.plugins:maven-eclipse-plugin
[DEBUG] Could not find metadata
org.apache.maven.plugins:maven-eclipse-plugin/maven-metadata.xml in local
(C:\Users\pankaj\.m2\repository)
[DEBUG] Skipped remote update check for
org.apache.maven.plugins:maven-eclipse-plugin/maven-metadata.xml, locally
cached metadata up-to-date.
[DEBUG] Resolved plugin version for
org.apache.maven.plugins:maven-eclipse-plugin to 2.8 from repository
central (http://repo1.maven.org/maven2, releases)
[DEBUG] Resolving plugin prefix eclipse from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Resolved plugin prefix eclipse to
org.apache.maven.plugins:maven-eclipse-plugin from POM
ruleplayer:chapter6:jar:1.0-SNAPSHOT
[DEBUG] Resolving plugin prefix eclipse from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Resolved plugin prefix eclipse to
org.apache.maven.plugins:maven-eclipse-plugin from POM
ruleplayer:chapter6:jar:1.0-SNAPSHOT
[DEBUG] === REACTOR BUILD PLAN

[DEBUG] Project: ruleplayer:chapter6:jar:1.0-SNAPSHOT
[DEBUG] Tasks:   [eclipse:clean, eclipse:eclipse]
[DEBUG] Style:   Regular
[DEBUG]
===
[INFO]

[INFO]

[INFO] Building Drools-book-samples 1.0-SNAPSHOT
[INFO]

[DEBUG] Resolving plugin prefix eclipse from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Resolved plugin prefix eclipse to
org.apache.maven.plugins:maven-eclipse-plugin from POM
ruleplayer:chapter6:jar:1.0-SNAPSHOT
[DEBUG] Resolving plugin prefix eclipse from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Resolved plugin prefix eclipse to
org.apache.maven.plugins:maven-eclipse-plugin from POM
ruleplayer:chapter6:jar:1.0-SNAPSHOT
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] === PROJECT BUILD PLAN

[DEBUG

Re: Execution default-cli of goal org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse failed. NullPointerException

[Barrie Treloar]

On Fri, Nov 4, 2011 at 7:13 AM, Pankaj Pai 84.pan...@gmail.com wrote:
 Hi Everyone,

 I am receiving the below error when I try to use the maven plugin for
 eclipse. Could you please take a look and let me know what is that I am
 doing wrong.

[del]

Are you able to boil this down into a small, simple and reproducible problem?

There is way too much output to make much sense of what your problem is.

I can see
  Caused by: java.lang.NullPointerException at

org.apache.maven.artifact.versioning.ComparableVersion.parseVersion(ComparableVersion.java:353)

But I can only guess that you are missing a version in one of your
dependency declarations, or that what you have provided is junk.
However, either of these cases should not NPE.

Hence a small test case showing the problem would help in getting it fixed.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: eclipse plugin does not generate org.eclipse.jdt.core.prefs file

[Gabriel Belingueres]

Hi Barrie!

Finally, I had some time to checkout the eclipse plugin and do some
modifications to make it work.

If the explicit configuration is not found for the compiler
source/target, it searches for the
maven.compiler.source/maven.compiler.target properties. Even if the
properties are not found, if the compiler plugin version is = 2.3,
then it defaults to 1.5 (as documented in the maven compiler
plugin).

I attached the patch for the IdeUtils.java class.

Regards,
Gabriel

2011/9/23 Barrie Treloar baerr...@gmail.com:
 On Sat, Sep 24, 2011 at 12:43 AM, Gabriel Belingueres
 belingue...@gmail.com wrote:
 Thanks Barrie!
 That modification made the trick.

 I also don't actually know if configuring the plugin using the command
 line properties is a best practice.
 But seeing the source code of the eclipse plugin, I traced it to the
 IdeUtils.java [1], and it seems that the properties are not tacked
 into account.

 [1] 
 http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/main/java/org/apache/maven/plugin/ide/IdeUtils.java

 Yup.
 I guess we could take the properties into account, we hard code the
 configuration setting already...
 It would mean that we'd need to look up the property settings for each
 plugin/configuration combination to include the property as well.

 Your the first person I'm aware of that has noticed this as a problem.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

[Carlos Sanchez]

I guess there wouldn't be any issue removing it adding a warning
pointing to the Felix plugin.
Osgi manifests are better handled there.

On Fri, Sep 23, 2011 at 8:01 AM, Barrie Treloar baerr...@gmail.com wrote:
 Does anyone actually use pde mode in maven-eclipse-plugin?

 The support looks pretty basic and there are other better options like
 tycho and felix for doing this stuff.

 EclipseOSGiManifestWriter has been deprecated in favour of felix and I
 wonder whether its worth keeping the other stuff around.

 I realise that not every use of the plugin is going to be on the user
 list - but it can give a gauge of sentiment.

 Opinions welcome.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

[Jörg Schaible]

Carlos Sanchez wrote:

 I guess there wouldn't be any issue removing it adding a warning
 pointing to the Felix plugin.
 Osgi manifests are better handled there.

+1

- Jörg


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

[John Casey]

+1

Having fewer partial implementations to confuse folks is always better IMO.

On 9/27/11 2:08 AM, Carlos Sanchez wrote:

I guess there wouldn't be any issue removing it adding a warning
pointing to the Felix plugin.
Osgi manifests are better handled there.

On Fri, Sep 23, 2011 at 8:01 AM, Barrie Treloarbaerr...@gmail.com  wrote:

Does anyone actually use pde mode in maven-eclipse-plugin?

The support looks pretty basic and there are other better options like
tycho and felix for doing this stuff.

EclipseOSGiManifestWriter has been deprecated in favour of felix and I
wonder whether its worth keeping the other stuff around.

I realise that not every use of the plugin is going to be on the user
list - but it can give a gauge of sentiment.

Opinions welcome.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



--
John Casey
Developer, PMC Chair - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

[Stephen Coy]

FWIW, we're using pde mode at present.

We have a largish (~ 40 modules) framework that builds both RCP applications 
and web applications.

I haven't had a chance to figure out how to integrate Tycho into this 
arrangement. On the surface it looks like you're either using p2 dependencies 
or maven dependencies but not both.

Thanks,

Steve C


On 23/09/2011, at 4:01 PM, Barrie Treloar wrote:

 Does anyone actually use pde mode in maven-eclipse-plugin?
 
 The support looks pretty basic and there are other better options like
 tycho and felix for doing this stuff.
 
 EclipseOSGiManifestWriter has been deprecated in favour of felix and I
 wonder whether its worth keeping the other stuff around.
 
 I realise that not every use of the plugin is going to be on the user
 list - but it can give a gauge of sentiment.
 
 Opinions welcome.
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

[Barrie Treloar]

On Wed, Sep 28, 2011 at 11:40 AM, Stephen Coy st...@resolvesw.com wrote:
 FWIW, we're using pde mode at present.

 We have a largish (~ 40 modules) framework that builds both RCP applications 
 and web applications.

 I haven't had a chance to figure out how to integrate Tycho into this 
 arrangement. On the surface it looks like you're either using p2 dependencies 
 or maven dependencies but not both.

I don't suppose you have some documentation that describes your setup?

For the RCP application I was building we used (the now defunct)
org.codehaus.mojo:pde-maven-plugin.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-eclipse-plugin: pde support and OSGiManifest writer

[Stephen Coy]

We're building bundles with the following build configuration:

packagingbundle/packaging

build
extensions
extension
groupIdorg.apache.felix/groupId
artifactIdorg.osgi.core/artifactId
version1.2.0/version
/extension
/extensions

plugins

!-- configure the bundle plugin executed as part of the bundle 
packaging type --
!-- generate an OSGI manifest --
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-bundle-plugin/artifactId
extensionstrue/extensions
configuration
manifestLocationMETA-INF/manifestLocation
instructions
_nousestrue/_nouses

Bundle-SymbolicNamecom.foobar.platform.rules.deployer.config;singleton:=true/Bundle-SymbolicName
Bundle-NameFoobar Deployer Configuration/Bundle-Name

Bundle-RequiredExecutionEnvironmentJavaSE-1.6/Bundle-RequiredExecutionEnvironment
Bundle-DocURL /
Import-Package!*/Import-Package

Private-Packagecom.foobar.platform.rules.deployer.config.*/Private-Package
Export-Package /

Bundle-Activatorcom.foobar.platform.rules.deployer.config.plugin.DeployerConfigPlugin/Bundle-Activator
Bundle-ActivationPolicylazy/Bundle-ActivationPolicy

Embed-Dependency*;scope=compile|runtime;inline=false/Embed-Dependency
Embed-Transitivetrue/Embed-Transitive

Include-Resourceplugin.xml,src/main/resources/Include-Resource

Bundle-ClassPath.,{maven-dependencies}/Bundle-ClassPath

Require-Bundleorg.eclipse.core.runtime,org.eclipse.ui,com.foobar.core,com.foobar.core.deployer.rc.config,com.axegroup.rcp.plugins.log4j,org.apache.commons.lang/Require-Bundle

Eclipse-RegisterBuddycom.foobar.core,com.axegroup.rcp.plugins.log4j/Eclipse-RegisterBuddy
/instructions
/configuration
/plugin

!-- Unpack jar dependencies into the target directory so they can 
be used by the pde plugin --
plugin
artifactIdmaven-dependency-plugin/artifactId
configuration
excludeTransitivefalse/excludeTransitive
/configuration
executions
execution
idcopy-dependencies/id
goals
goalcopy-dependencies/goal
/goals
configuration
excludeScopeprovided/excludeScope
outputDirectory${basedir}/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotsfalse/overWriteSnapshots
overWriteIfNewertrue/overWriteIfNewer
/configuration
/execution
/executions
/plugin
!-- clean up all the dependency jars dumped in the plugin root 
directory for the pde plugin --
plugin
artifactIdmaven-clean-plugin/artifactId
configuration
filesets
fileset
directory${basedir}/directory
includes
include*.jar/include
/includes
followSymlinksfalse/followSymlinks
/fileset
/filesets
/configuration
/plugin

!-- configuration for the Eclipse IDE --
plugin
artifactIdmaven-eclipse-plugin/artifactId
configuration
pdetrue/pde
useProjectReferencesfalse/useProjectReferences
classpathContainers

classpathContainerorg.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6/classpathContainer

classpathContainerorg.eclipse.pde.core.requiredPlugins/classpathContainer
/classpathContainers
/configuration
executions
execution
idrun eclipse plugin/id
phaseprepare-package/phase
goals
goalclean/goal
goaleclipse/goal
/goals
/execution
/executions
/plugin

maven-eclipse-plugin: pde support and OSGiManifest writer

[Barrie Treloar]

Does anyone actually use pde mode in maven-eclipse-plugin?

The support looks pretty basic and there are other better options like
tycho and felix for doing this stuff.

EclipseOSGiManifestWriter has been deprecated in favour of felix and I
wonder whether its worth keeping the other stuff around.

I realise that not every use of the plugin is going to be on the user
list - but it can give a gauge of sentiment.

Opinions welcome.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: eclipse plugin does not generate org.eclipse.jdt.core.prefs file

[Gabriel Belingueres]

Thanks Barrie!
That modification made the trick.

I also don't actually know if configuring the plugin using the command
line properties is a best practice.
But seeing the source code of the eclipse plugin, I traced it to the
IdeUtils.java [1], and it seems that the properties are not tacked
into account.

[1] 
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/main/java/org/apache/maven/plugin/ide/IdeUtils.java

2011/9/22 Barrie Treloar baerr...@gmail.com:
 On Fri, Sep 23, 2011 at 3:51 AM, Gabriel Belingueres
 belingue...@gmail.com wrote:
 Hi,

 I'm using Maven 3.0.3.

 My current project pom.xml file uses a parent pom where is defined the
 maven-compiler-plugin configuration:

  properties
        maven.compiler.source1.6/maven.compiler.source
        maven.compiler.target1.6/maven.compiler.target
        maven.compiler.showWarningstrue/maven.compiler.showWarnings
        maven.compiler.showDeprecationtrue/maven.compiler.showDeprecation
        
 maven.compiler.debuglevellines,vars,source/maven.compiler.debuglevel
        maven.compiler.verbosetrue/maven.compiler.verbose
  /properties

  build
    pluginManagement
      plugins
        plugin
          groupIdorg.apache.maven.plugins/groupId
          artifactIdmaven-compiler-plugin/artifactId
          version2.3.2/version
          configuration
            compilerArgument-Xlint:all/compilerArgument
          /configuration
        /plugin
       ...
      /plugins
    /pluginManagement

    plugins
      !-- all projects inherites the compiler configuration --
      plugin
        groupIdorg.apache.maven.plugins/groupId
        artifactIdmaven-compiler-plugin/artifactId
      /plugin
    /plugins


 If in the actual project pom.xml I do not declare the compiler plugin,
 or if I declare it like this:

    plugins
      plugin
        groupIdorg.apache.maven.plugins/groupId
        artifactIdmaven-compiler-plugin/artifactId
      /plugin
    /plugins

 or with the version number:

    plugins
      plugin
        groupIdorg.apache.maven.plugins/groupId
        artifactIdmaven-compiler-plugin/artifactId
        version2.3.2/version
      /plugin
    /plugins

 then the .settings/org.eclipse.jdt.core.prefs file is NOT generated.

 However, it is generated if I redeclare it fully like this:

      plugin
        groupIdorg.apache.maven.plugins/groupId
        artifactIdmaven-compiler-plugin/artifactId
        version2.3.2/version
        configuration
          source1.6/source
          target1.6/target
          compilerArgument-Xlint:all/compilerArgument
          showWarningstrue/showWarnings
          showDeprecationtrue/showDeprecation
          debuglevellines,vars,source/debuglevel
          verbosetrue/verbose
        /configuration
      /plugin

 is there a bug with the eclipse plugin? or am I doing something wrong?

 The answer is kind of.

 There is no standard way (that I'm aware of) for a mojo to ask for the
 metadata of another mojo.
 That is, the maven-eclipse-plugin can't ask maven-compiler-plugin what
 its configuration is.
 So what we do is to scan the pom model file that Maven builds up
 looking in both the build/plugins and pluginManagement sections for
 the maven compiler.
 Then look for the specific option of interest (i.e. the source property).

 What you are doing is setting the source value by indirection.
 You are setting the equivalent of -Dmaven.compiler.source on the
 command line, which is not showing up in the model representation.
 (This may be where the bug is)

 I'm not sure what best practice is, but I think using properties to
 set values in plugins indirectly is probably not the way to go.
 Use the property definitions but then configure the plugin with that property.

 You already have a pluginManagement section, so I would specify the
 configuration values there:

  properties
       maven.compiler.source1.6/maven.compiler.source
       maven.compiler.target1.6/maven.compiler.target
       maven.compiler.showWarningstrue/maven.compiler.showWarnings
       maven.compiler.showDeprecationtrue/maven.compiler.showDeprecation
       maven.compiler.debuglevellines,vars,source/maven.compiler.debuglevel
       maven.compiler.verbosetrue/maven.compiler.verbose
  /properties
  build
   pluginManagement
     plugins
       plugin
         groupIdorg.apache.maven.plugins/groupId
         artifactIdmaven-compiler-plugin/artifactId
         version2.3.2/version
         configuration
           compilerArgument-Xlint:all/compilerArgument
           source${maven.compiler.source}/source
           target${maven.compiler.target}/target
 etc...
         /configuration
       /plugin

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org

Re: eclipse plugin does not generate org.eclipse.jdt.core.prefs file

[Barrie Treloar]

On Sat, Sep 24, 2011 at 12:43 AM, Gabriel Belingueres
belingue...@gmail.com wrote:
 Thanks Barrie!
 That modification made the trick.

 I also don't actually know if configuring the plugin using the command
 line properties is a best practice.
 But seeing the source code of the eclipse plugin, I traced it to the
 IdeUtils.java [1], and it seems that the properties are not tacked
 into account.

 [1] 
 http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/main/java/org/apache/maven/plugin/ide/IdeUtils.java

Yup.
I guess we could take the properties into account, we hard code the
configuration setting already...
It would mean that we'd need to look up the property settings for each
plugin/configuration combination to include the property as well.

Your the first person I'm aware of that has noticed this as a problem.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

eclipse plugin does not generate org.eclipse.jdt.core.prefs file

[Gabriel Belingueres]

Hi,

I'm using Maven 3.0.3.

My current project pom.xml file uses a parent pom where is defined the
maven-compiler-plugin configuration:

  properties
maven.compiler.source1.6/maven.compiler.source
maven.compiler.target1.6/maven.compiler.target
maven.compiler.showWarningstrue/maven.compiler.showWarnings
maven.compiler.showDeprecationtrue/maven.compiler.showDeprecation
maven.compiler.debuglevellines,vars,source/maven.compiler.debuglevel
maven.compiler.verbosetrue/maven.compiler.verbose
  /properties

  build
pluginManagement
  plugins
plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-compiler-plugin/artifactId
  version2.3.2/version
  configuration
compilerArgument-Xlint:all/compilerArgument
  /configuration
/plugin
   ...
  /plugins
/pluginManagement

plugins
  !-- all projects inherites the compiler configuration --
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
  /plugin
/plugins


If in the actual project pom.xml I do not declare the compiler plugin,
or if I declare it like this:

plugins
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
  /plugin
/plugins

or with the version number:

plugins
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
  /plugin
/plugins

then the .settings/org.eclipse.jdt.core.prefs file is NOT generated.

However, it is generated if I redeclare it fully like this:

  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
configuration
  source1.6/source
  target1.6/target
  compilerArgument-Xlint:all/compilerArgument
  showWarningstrue/showWarnings
  showDeprecationtrue/showDeprecation
  debuglevellines,vars,source/debuglevel
  verbosetrue/verbose
/configuration
  /plugin

is there a bug with the eclipse plugin? or am I doing something wrong?

Thanks in advance,
Gabriel

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: eclipse plugin does not generate org.eclipse.jdt.core.prefs file

[Barrie Treloar]

On Fri, Sep 23, 2011 at 3:51 AM, Gabriel Belingueres
belingue...@gmail.com wrote:
 Hi,

 I'm using Maven 3.0.3.

 My current project pom.xml file uses a parent pom where is defined the
 maven-compiler-plugin configuration:

  properties
        maven.compiler.source1.6/maven.compiler.source
        maven.compiler.target1.6/maven.compiler.target
        maven.compiler.showWarningstrue/maven.compiler.showWarnings
        maven.compiler.showDeprecationtrue/maven.compiler.showDeprecation
        
 maven.compiler.debuglevellines,vars,source/maven.compiler.debuglevel
        maven.compiler.verbosetrue/maven.compiler.verbose
  /properties

  build
    pluginManagement
      plugins
        plugin
          groupIdorg.apache.maven.plugins/groupId
          artifactIdmaven-compiler-plugin/artifactId
          version2.3.2/version
          configuration
            compilerArgument-Xlint:all/compilerArgument
          /configuration
        /plugin
       ...
      /plugins
    /pluginManagement

    plugins
      !-- all projects inherites the compiler configuration --
      plugin
        groupIdorg.apache.maven.plugins/groupId
        artifactIdmaven-compiler-plugin/artifactId
      /plugin
    /plugins


 If in the actual project pom.xml I do not declare the compiler plugin,
 or if I declare it like this:

    plugins
      plugin
        groupIdorg.apache.maven.plugins/groupId
        artifactIdmaven-compiler-plugin/artifactId
      /plugin
    /plugins

 or with the version number:

    plugins
      plugin
        groupIdorg.apache.maven.plugins/groupId
        artifactIdmaven-compiler-plugin/artifactId
        version2.3.2/version
      /plugin
    /plugins

 then the .settings/org.eclipse.jdt.core.prefs file is NOT generated.

 However, it is generated if I redeclare it fully like this:

      plugin
        groupIdorg.apache.maven.plugins/groupId
        artifactIdmaven-compiler-plugin/artifactId
        version2.3.2/version
        configuration
          source1.6/source
          target1.6/target
          compilerArgument-Xlint:all/compilerArgument
          showWarningstrue/showWarnings
          showDeprecationtrue/showDeprecation
          debuglevellines,vars,source/debuglevel
          verbosetrue/verbose
        /configuration
      /plugin

 is there a bug with the eclipse plugin? or am I doing something wrong?

The answer is kind of.

There is no standard way (that I'm aware of) for a mojo to ask for the
metadata of another mojo.
That is, the maven-eclipse-plugin can't ask maven-compiler-plugin what
its configuration is.
So what we do is to scan the pom model file that Maven builds up
looking in both the build/plugins and pluginManagement sections for
the maven compiler.
Then look for the specific option of interest (i.e. the source property).

What you are doing is setting the source value by indirection.
You are setting the equivalent of -Dmaven.compiler.source on the
command line, which is not showing up in the model representation.
(This may be where the bug is)

I'm not sure what best practice is, but I think using properties to
set values in plugins indirectly is probably not the way to go.
Use the property definitions but then configure the plugin with that property.

You already have a pluginManagement section, so I would specify the
configuration values there:

 properties
   maven.compiler.source1.6/maven.compiler.source
   maven.compiler.target1.6/maven.compiler.target
   maven.compiler.showWarningstrue/maven.compiler.showWarnings
   maven.compiler.showDeprecationtrue/maven.compiler.showDeprecation
   maven.compiler.debuglevellines,vars,source/maven.compiler.debuglevel
   maven.compiler.verbosetrue/maven.compiler.verbose
 /properties
 build
   pluginManagement
 plugins
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-compiler-plugin/artifactId
 version2.3.2/version
 configuration
   compilerArgument-Xlint:all/compilerArgument
   source${maven.compiler.source}/source
   target${maven.compiler.target}/target
etc...
 /configuration
   /plugin

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

[DaveyBob]

I essentially have the same problem.  I am just getting started with Groovy
for this project.

Environment:
  Ubuntu 11.04
  Eclipse 3.7
  Groovy Eclipse plugin 2.5.1
  Maven 2.2.1

Following the instructions in the Groovy Eclipse Plugin page
(http://groovy.codehaus.org/Groovy-Eclipse+compiler+plugin+for+Maven), I ran
the mvn archetype:generate command, and it generated a project for me.  Then
I did mvn eclipse:eclipse and then imported that project into Eclipse.

But the project flags errors in src/test/java/JavaTest because the package
is not right.  Fixed that.

Next src/main/java/JavaMain.java is in error because it cannot find
GroovyHello.  Sure enough, that is not compiled.  So I checked the build
path, and like Sebastian found, src/main/groovy does not include groovy
files at all...so I added an include of **/*.groovy.

That still doesn't fix it, though.  None of the groovy files ever get
compiled to .class files in the output folder.  At this point I don't have a
clue how to get Eclipse to build these files.

I think I'll come at it from the Eclipse side and create a Groovy project.


--
View this message in context: 
http://maven.40175.n5.nabble.com/Maven-Eclipse-Plugin-doesn-t-include-all-source-paths-in-generated-classpath-file-in-a-Java-Groovy-pt-tp4535545p4583476.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

[Jeff MAURY]

You probably need to configure your Eclipse project as a Groovy project
(through a nature I think).
Please not that you can configure the Maven Eclipse plugin to add specific
natures when eclipse:eclipse is run.

Regards
Jeff


On Wed, Jul 13, 2011 at 7:26 PM, DaveyBob psyn...@yahoo.com wrote:

 I essentially have the same problem.  I am just getting started with Groovy
 for this project.

 Environment:
  Ubuntu 11.04
  Eclipse 3.7
  Groovy Eclipse plugin 2.5.1
  Maven 2.2.1

 Following the instructions in the Groovy Eclipse Plugin page
 (http://groovy.codehaus.org/Groovy-Eclipse+compiler+plugin+for+Maven), I
 ran
 the mvn archetype:generate command, and it generated a project for me.
  Then
 I did mvn eclipse:eclipse and then imported that project into Eclipse.

 But the project flags errors in src/test/java/JavaTest because the package
 is not right.  Fixed that.

 Next src/main/java/JavaMain.java is in error because it cannot find
 GroovyHello.  Sure enough, that is not compiled.  So I checked the build
 path, and like Sebastian found, src/main/groovy does not include groovy
 files at all...so I added an include of **/*.groovy.

 That still doesn't fix it, though.  None of the groovy files ever get
 compiled to .class files in the output folder.  At this point I don't have
 a
 clue how to get Eclipse to build these files.

 I think I'll come at it from the Eclipse side and create a Groovy project.


 --
 View this message in context:
 http://maven.40175.n5.nabble.com/Maven-Eclipse-Plugin-doesn-t-include-all-source-paths-in-generated-classpath-file-in-a-Java-Groovy-pt-tp4535545p4583476.html
 Sent from the Maven - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-- 
Legacy code often differs from its suggested alternative by actually
working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

[Barrie Treloar]

On Thu, Jul 14, 2011 at 3:09 AM, Jeff MAURY jeffma...@jeffmaury.com wrote:
 You probably need to configure your Eclipse project as a Groovy project
 (through a nature I think).
 Please not that you can configure the Maven Eclipse plugin to add specific
 natures when eclipse:eclipse is run.

Groovy support in maven-eclipse-plugin may not be complete.
You are welcome to provide patches with test cases to fix this.

And Sebastian, it would be nice to hear how you went.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

[Barrie Treloar]

On Thu, Jul 14, 2011 at 9:07 AM, Barrie Treloar baerr...@gmail.com wrote:
 On Thu, Jul 14, 2011 at 3:09 AM, Jeff MAURY jeffma...@jeffmaury.com wrote:
 You probably need to configure your Eclipse project as a Groovy project
 (through a nature I think).
 Please not that you can configure the Maven Eclipse plugin to add specific
 natures when eclipse:eclipse is run.

 Groovy support in maven-eclipse-plugin may not be complete.
 You are welcome to provide patches with test cases to fix this.

I can see from the IT pom that there are no Groovy natures installed.

But when you run mvn compile it will compile the Groovy files.
See 
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/test/resources/projects/groovy/pom.xml

Their documentation
(http://groovy.codehaus.org/Groovy-Eclipse+compiler+plugin+for+Maven)
has a bug
  !-- Optional, include this piece for integration with Eclipse --
  plugin
artifactId/artifactId
configuration
  additionalProjectnatures
projectnatureorg.eclipse.jdt.groovy.core.groovyNature/projectnature
  /additionalProjectnatures
/configuration
  /plugin
  ...
What's the artifactId?
I think it should be maven-eclipse-plugin.

And their archetype also needs updating to match their documentation
as it does not include this configuration.

I've updated the IT pom to include the nature now.
But its still a manual job for any groovy users to do this, its not
something maven-eclipse-plugin can do automatically for you.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

[Barrie Treloar]

 On Thu, Jun 30, 2011 at 12:45 AM, Sebastian Goldt sd...@cam.ac.uk wrote:

Sebastian, its been five days and no feedback.

Have you worked out your problem?
Has any of this thread been useful?

It would be nice from an archive perspective if you could comment on
your resolution so others can avoid this problem in the future.
Especially if there was something not clear that caused you to make a
mistake, that would be a good opportunity to fix up any documentation
so others don't have the same problems.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

[Guillaume Polet]

It's an M2Eclipse problem. I think you should rather user their ML.

--
Guillaume

Le 29/06/2011 17:15, Sebastian Goldt a écrit :

Hi all,

today, I run into some problems with the Maven Eclipse Plugin 2.8 using
Maven 3.0.3 on an Ubuntu 11.04 while setting up a mixed Java / Groovy
project. It seems as if the eclipse plugin doesn't include all source code
folders in the generated .project file. I haven't found anything on the
internet on that particular issue so far...

*Details:*

My project in question contains both tests and main source code in java as
well as in groovy, so I have the four folders src/main/java,
src/main/groovy, src/test/java and src/test/groovy which are added to the
project with the Build Helper Maven Plugin (1.6). When I generate the
eclipse project files using eclipse:eclipse, the generated .classpath file
only contains the src/main/groovy folder and not the src/test/groovy folder.

*Reproduction:*
The easiest way to reproduce the problem is by using a java/groovy project
quickstarter from codehaus:

1. Create a dummy groovy/java project by using typing:

mvn archetype:generate -DarchetypeGroupId=org.codehaus.groovy
-DarchetypeArtifactId=groovy-eclipse-quickstart
-DarchetypeVersion=2.5.1-M3-SNAPSHOT -DgroupId=foo -DartifactId=bar
-Dversion=1 -DinteractiveMode=false -DarchetypeRepository=
https://nexus.codehaus.org/content/repositories/snapshots/

2. Create Eclipse project files

mvn eclipse:eclipse

When inspecting the generated .classpath file, you will notice that the
src/test/groovy path is missing.

Note that if you wanted to import the project into eclipse, you would have
to set up the eclipse plugin in your pom as to include *.groovy classes on
your build path and properly organise the files in packages; however, this
wouldn't change the actual problem in any way.

*Workaround:*
Simply import the project into Eclipse and declare the src/test/groovy
folder as source folder.

Is this a bug or is there another mistake?

Regards,
Sebastian




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

[Barrie Treloar]

On Thu, Jun 30, 2011 at 4:43 PM, Guillaume Polet
guillaume.po...@gmail.com wrote:
 It's an M2Eclipse problem. I think you should rather user their ML.
[del]
    mvn eclipse:eclipse

He's not using m2e.

I'm looking into it...

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

[Barrie Treloar]

On Thu, Jun 30, 2011 at 12:45 AM, Sebastian Goldt sd...@cam.ac.uk wrote:
[del]
 My project in question contains both tests and main source code in java as
 well as in groovy, so I have the four folders src/main/java,
 src/main/groovy, src/test/java and src/test/groovy which are added to the
 project with the Build Helper Maven Plugin (1.6). When I generate the
 eclipse project files using eclipse:eclipse, the generated .classpath file
 only contains the src/main/groovy folder and not the src/test/groovy folder.

 *Reproduction:*
 The easiest way to reproduce the problem is by using a java/groovy project
 quickstarter from codehaus:

   1. Create a dummy groovy/java project by using typing:

   mvn archetype:generate     -DarchetypeGroupId=org.codehaus.groovy
   -DarchetypeArtifactId=groovy-eclipse-quickstart
   -DarchetypeVersion=2.5.1-M3-SNAPSHOT     -DgroupId=foo     -DartifactId=bar
       -Dversion=1     -DinteractiveMode=false     -DarchetypeRepository=
   https://nexus.codehaus.org/content/repositories/snapshots/

Created an IT for this case to see what happens

   2. Create Eclipse project files

   mvn eclipse:eclipse

 When inspecting the generated .classpath file, you will notice that the
 src/test/groovy path is missing.

 Note that if you wanted to import the project into eclipse, you would have
 to set up the eclipse plugin in your pom as to include *.groovy classes on
 your build path and properly organise the files in packages; however, this
 wouldn't change the actual problem in any way.

m-e-p will run anything else bound to
lifecycles
  lifecycle
iddefault/id
!-- START SNIPPET: eclipse-plugin-lifecycle --
phases
  generate-sources/
  generate-resources/
  generate-test-sources/
  generate-test-resources/
/phases
!-- END SNIPPET: eclipse-plugin-lifecycle --
  /lifecycle

So it should run build-helper to attach the groovy directories.

I can see in the debug logs
[DEBUG] testOutput toRelativeAndFixSeparator
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\groovy
, 
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\groovy\target\test-classes
[DEBUG] testOutput after toRelative : target/test-classes
[DEBUG] Processing resource dir:
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\groovy\src\main\resources
[DEBUG] Resource dir:
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\groovy\src\main\resources
either missing or not a directory.
[DEBUG] Processing resource dir:
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\groovy\src\test\resources
[DEBUG] Resource dir:
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\groovy\src\test\resources
either missing or not a directory.
[INFO] Not writing settings - defaults suffice
[DEBUG] Processing classpath for: source src/test/java:
output=target/test-classes, include=[**/*.java], exclude=[],
test=true, filtering=false; default output=target/classes
[DEBUG] Processing classpath for: source src/main/java: output=null,
include=[**/*.java], exclude=[], test=false, filtering=false; default
output=target/classes
[DEBUG] Processing classpath for: source src/main/groovy: output=null,
include=[**/*.java], exclude=[], test=false, filtering=false; default
output=target/classes
[INFO] Wrote Eclipse project for bar to
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\groovy.

So groovy is available in the src directory list.

The generated .classpath
classpath
  classpathentry kind=src path=src/test/java
output=target/test-classes including=**/*.java/
  classpathentry kind=src path=src/main/java including=**/*.java/
  classpathentry kind=src path=src/main/groovy including=**/*.java/
  classpathentry kind=output path=target/classes/
  classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/
  classpathentry kind=var
path=M2_REPO/org/codehaus/groovy/groovy-all/1.8.0/groovy-all-1.8.0.jar/
  classpathentry kind=var path=M2_REPO/junit/junit/4.8.2/junit-4.8.2.jar/
/classpath

This is using the latest released m-eclipse-p of 2.8.

Try running
  mvn -X eclipse:eclipse

This will print out the debug statements.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

[Anders Hammar]

On Thu, Jun 30, 2011 at 09:13, Guillaume Polet guillaume.po...@gmail.comwrote:

 It's an M2Eclipse problem. I think you should rather user their ML.


No, he's using the maven-eclipse-plugin. Not m2eclipse.

/Anders


 --
 Guillaume

 Le 29/06/2011 17:15, Sebastian Goldt a écrit :

 Hi all,

 today, I run into some problems with the Maven Eclipse Plugin 2.8 using
 Maven 3.0.3 on an Ubuntu 11.04 while setting up a mixed Java / Groovy
 project. It seems as if the eclipse plugin doesn't include all source code
 folders in the generated .project file. I haven't found anything on the
 internet on that particular issue so far...

 *Details:*

 My project in question contains both tests and main source code in java as
 well as in groovy, so I have the four folders src/main/java,
 src/main/groovy, src/test/java and src/test/groovy which are added to the
 project with the Build Helper Maven Plugin (1.6). When I generate the
 eclipse project files using eclipse:eclipse, the generated .classpath file
 only contains the src/main/groovy folder and not the src/test/groovy
 folder.

 *Reproduction:*
 The easiest way to reproduce the problem is by using a java/groovy project
 quickstarter from codehaus:

1. Create a dummy groovy/java project by using typing:

mvn archetype:generate -DarchetypeGroupId=org.**codehaus.groovy
-DarchetypeArtifactId=groovy-**eclipse-quickstart
-DarchetypeVersion=2.5.1-M3-**SNAPSHOT -DgroupId=foo
 -DartifactId=bar
-Dversion=1 -DinteractiveMode=false -DarchetypeRepository=

 https://nexus.codehaus.org/**content/repositories/**snapshots/https://nexus.codehaus.org/content/repositories/snapshots/

2. Create Eclipse project files

mvn eclipse:eclipse

 When inspecting the generated .classpath file, you will notice that the
 src/test/groovy path is missing.

 Note that if you wanted to import the project into eclipse, you would have
 to set up the eclipse plugin in your pom as to include *.groovy classes on
 your build path and properly organise the files in packages; however, this
 wouldn't change the actual problem in any way.

 *Workaround:*
 Simply import the project into Eclipse and declare the src/test/groovy
 folder as source folder.

 Is this a bug or is there another mistake?

 Regards,
 Sebastian



 --**--**-
 To unsubscribe, e-mail: 
 users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Maven Eclipse Plugin doesn't include all source paths in generated .classpath file in a Java / Groovy project

[Sebastian Goldt]

Hi all,

today, I run into some problems with the Maven Eclipse Plugin 2.8 using
Maven 3.0.3 on an Ubuntu 11.04 while setting up a mixed Java / Groovy
project. It seems as if the eclipse plugin doesn't include all source code
folders in the generated .project file. I haven't found anything on the
internet on that particular issue so far...

*Details:*

My project in question contains both tests and main source code in java as
well as in groovy, so I have the four folders src/main/java,
src/main/groovy, src/test/java and src/test/groovy which are added to the
project with the Build Helper Maven Plugin (1.6). When I generate the
eclipse project files using eclipse:eclipse, the generated .classpath file
only contains the src/main/groovy folder and not the src/test/groovy folder.

*Reproduction:*
The easiest way to reproduce the problem is by using a java/groovy project
quickstarter from codehaus:

   1. Create a dummy groovy/java project by using typing:

   mvn archetype:generate -DarchetypeGroupId=org.codehaus.groovy
   -DarchetypeArtifactId=groovy-eclipse-quickstart
   -DarchetypeVersion=2.5.1-M3-SNAPSHOT -DgroupId=foo -DartifactId=bar
   -Dversion=1 -DinteractiveMode=false -DarchetypeRepository=
   https://nexus.codehaus.org/content/repositories/snapshots/

   2. Create Eclipse project files

   mvn eclipse:eclipse

When inspecting the generated .classpath file, you will notice that the
src/test/groovy path is missing.

Note that if you wanted to import the project into eclipse, you would have
to set up the eclipse plugin in your pom as to include *.groovy classes on
your build path and properly organise the files in packages; however, this
wouldn't change the actual problem in any way.

*Workaround:*
Simply import the project into Eclipse and declare the src/test/groovy
folder as source folder.

Is this a bug or is there another mistake?

Regards,
Sebastian