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

[Daniel Kulp]

On Oct 4, 2013, at 5:18 PM, 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:

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

[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

[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

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

[Stephen Coy]

We're building bundles with the following build configuration:

bundle




org.apache.felix
org.osgi.core
1.2.0








org.apache.felix
maven-bundle-plugin
true

META-INF

<_nouses>true

com.foobar.platform.rules.deployer.config;singleton:=true
Foobar Deployer Configuration

JavaSE-1.6

!*

com.foobar.platform.rules.deployer.config.*


com.foobar.platform.rules.deployer.config.plugin.DeployerConfigPlugin
lazy

*;scope=compile|runtime;inline=false
true

plugin.xml,src/main/resources

.,{maven-dependencies}

org.eclipse.core.runtime,org.eclipse.ui,com.foobar.core,com.foobar.core.deployer.rc.config,com.axegroup.rcp.plugins.log4j,org.apache.commons.lang

com.foobar.core,com.axegroup.rcp.plugins.log4j






maven-dependency-plugin

false



copy-dependencies

copy-dependencies


provided
${basedir}
false
false
true






maven-clean-plugin



${basedir}

*.jar

false







maven-eclipse-plugin

true
false


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

org.eclipse.pde.core.requiredPlugins




run eclipse plugin
prepare-package

clean
eclipse







On 28/09/2011, at 2:14 PM, Barrie Treloar wrote:

> On Wed, Sep 28, 2011 at 11:40 AM, Stephen Coy  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
> 


-
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  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]

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

[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 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



--
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

[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

[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  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 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  wrote:
> On Thu, Jul 14, 2011 at 3:09 AM, Jeff MAURY  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
  
  


  
org.eclipse.jdt.groovy.core.groovyNature
  

  
  ...
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, Jul 14, 2011 at 3:09 AM, Jeff MAURY  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

[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  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

[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

[Barrie Treloar]

> On Thu, Jun 30, 2011 at 12:45 AM, Sebastian Goldt  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

[Anders Hammar]

On Thu, Jun 30, 2011 at 09:13, Guillaume Polet wrote:

> 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/
>>
>>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.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  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

  
default


  
  
  
  


  

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

  
  
  
  
  
  
  


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

[Barrie Treloar]

On Thu, Jun 30, 2011 at 4:43 PM, Guillaume Polet
 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

[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

[Barrie Treloar]

On Mon, Apr 18, 2011 at 11:48 PM, Fernando Wermus
 wrote:
> Hi all,
>    I am trying to set up code styles, work space and so on, but it doesn't
> work. Does anybody know if maven plug in eclipse is working for these kind
> of set up? I am using eclipse helios

If you are talking about m2e, this isn't the correct mailing list.

If you are talking about maven-eclipse-plugin then:
* Coding Styles:
http://maven.apache.org/plugins/maven-eclipse-plugin/examples/load-code-styles.html
* Checkstyle: 
http://maven.apache.org/plugins/maven-eclipse-plugin/examples/configure-checkstyle.html

I put all this guff into your parent project's pom in
build/pluginManagement so you dont have to specify it per project.

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

Re: maven eclipse plugin

[Ron Wheeler]

On 18/04/2011 10:18 AM, Fernando Wermus wrote:

Hi all,
 I am trying to set up code styles, work space and so on, but it doesn't
work. Does anybody know if maven plug in eclipse is working for these kind
of set up? I am using eclipse helios

thanks in advance

You might want to move to the STS version of Eclipse. All the required 
Java development plug-ins are preloaded and the Maven integration works 
very well since M2 is built-in.


We have used it for almost 2 years and is much easier to get started 
with STS than an out-of-the-box Eclipse since you just install and go 
(still need to add Subversion for licensing reasons but it is made easy)


Ron



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

RE: Maven Eclipse Plugin - how to remove M2_REPO classpath variable

[Ludwig Magnusson]

I don’t know how to remove it. But in eclipse you can go to preferences -> 
maven -> user settings and “reindex” the location. Perhaps that helps depending 
on what the problem is.

/Ludwig

 

From: Wayne Fay [mailto:wayne...@gmail.com] 
Sent: den 5 februari 2011 16:25
To: Maven Users List
Subject: Re: Maven Eclipse Plugin - how to remove M2_REPO classpath variable

 

> Does anyone know a way to remove the M2_REPO classpath variable that was
> added using
>
>  mvn -Declipse.workspace= eclipse:configure-workspace?

I don't know how (or even if) you can do this with the Eclipse plugin,
but nothing is stopping you from doing it manually by editing the dot
files (.classpath, .project, etc) in your project directory with
Notepad or another editor.

Wayne

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

  _  

No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3423 - Release Date: 02/04/11

Re: Maven Eclipse Plugin - how to remove M2_REPO classpath variable

[Wayne Fay]

> Does anyone know a way to remove the M2_REPO classpath variable that was
> added using
>
>  mvn -Declipse.workspace= eclipse:configure-workspace?

I don't know how (or even if) you can do this with the Eclipse plugin,
but nothing is stopping you from doing it manually by editing the dot
files (.classpath, .project, etc) in your project directory with
Notepad or another editor.

Wayne

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

Re: maven-eclipse-plugin

[Barrie Treloar]

On Mon, Dec 6, 2010 at 10:39 AM, Brian Topping  wrote:
> On a related note, can anyone summarize what the best way of maintaining 
> eclipse projects from Maven is?  I use IDEA, and the best way from there is 
> IDEA itself, not with the IDEA plugin for Maven.
>
> Is the same true for Eclipse that the IDE plugin for Maven is better than the 
> Maven plugin for the IDE?  If so, what is the best plugin for Eclipse (there 
> seems to be more than one).

You won't get any consensus here.

I've tried M2Eclipse (a number of times) and it hasn't worked well
enough for me, so I have stuck with m-eclipse-p.

But there are plenty of people who are happy with M2Eclipse.

Or as Ron points out, you can give Eclipse/STS a go.
(Just remember to read the T&Cs)

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

Re: maven-eclipse-plugin

[Ron Wheeler]

On 05/12/2010 7:09 PM, Brian Topping wrote:

On a related note, can anyone summarize what the best way of maintaining 
eclipse projects from Maven is?  I use IDEA, and the best way from there is 
IDEA itself, not with the IDEA plugin for Maven.

Is the same true for Eclipse that the IDE plugin for Maven is better than the 
Maven plugin for the IDE?  If so, what is the best plugin for Eclipse (there 
seems to be more than one).

The Eclipse/STS from Springsource is the easiest way to get Eclipse 
integrated with Maven.



Thanks, Brian

On Dec 5, 2010, at 6:41 PM, Barrie Treloar wrote:


On Mon, Dec 6, 2010 at 12:51 AM, Asmann, Roland  wrote:

Hi all,

Does anybody know in which version the support for wtp 2.x was added?

Not really, you'd have to trawl through the code base to see for sure.
http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html lists
the versions available


And when will support for wtp 3.x be added?

There is no active development for adding wtp 3.x support.
Feel free to create a jira, integration tests and patches.

-
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: maven-eclipse-plugin

[Brian Topping]

On a related note, can anyone summarize what the best way of maintaining 
eclipse projects from Maven is?  I use IDEA, and the best way from there is 
IDEA itself, not with the IDEA plugin for Maven.  

Is the same true for Eclipse that the IDE plugin for Maven is better than the 
Maven plugin for the IDE?  If so, what is the best plugin for Eclipse (there 
seems to be more than one).

Thanks, Brian

On Dec 5, 2010, at 6:41 PM, Barrie Treloar wrote:

> On Mon, Dec 6, 2010 at 12:51 AM, Asmann, Roland  
> wrote:
>> Hi all,
>> 
>> Does anybody know in which version the support for wtp 2.x was added?
> 
> Not really, you'd have to trawl through the code base to see for sure.
> http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html lists
> the versions available
> 
>> And when will support for wtp 3.x be added?
> 
> There is no active development for adding wtp 3.x support.
> Feel free to create a jira, integration tests and patches.
> 
> -
> 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

[Barrie Treloar]

On Mon, Dec 6, 2010 at 12:51 AM, Asmann, Roland  wrote:
> Hi all,
>
> Does anybody know in which version the support for wtp 2.x was added?

Not really, you'd have to trawl through the code base to see for sure.
http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html lists
the versions available

> And when will support for wtp 3.x be added?

There is no active development for adding wtp 3.x support.
Feel free to create a jira, integration tests and patches.

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

Re: maven-eclipse-plugin Does not resolve workspace project name

[Jörg Schaible]

john.vint wrote:

> 
> 
>> This is not m-e-p's problem. Stop renaming your projects if you want
>> to use m-e-p and use it to regenerate the .project files. Keep the
>> name as the artifactId, or change the artifactId in the pom to meet
>> your needs.
> 
> Lets assume a person is working on two different version (two releases
> being
> developed in parallel).  They will both have the same artifact ID but
> eclipse forces a different project name.  I don't think asking m-e-p to
> offer this functionality is really an isnane request.

An alternative:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-
mojo.html#projectNameTemplate

- 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 Does not resolve workspace project name

[Barrie Treloar]

On Sat, Oct 30, 2010 at 2:34 AM, john.vint  wrote:
>
>
>> This is not m-e-p's problem. Stop renaming your projects if you want
>> to use m-e-p and use it to regenerate the .project files. Keep the
>> name as the artifactId, or change the artifactId in the pom to meet
>> your needs.
>
> Lets assume a person is working on two different version (two releases being
> developed in parallel).  They will both have the same artifact ID but
> eclipse forces a different project name.  I don't think asking m-e-p to
> offer this functionality is really an isnane request.
>
> The eclipse:eclipse plugin has worked perfectly fine as I have used it minus
> this one issue.  The resolution was extremely easy.
>
> Including a new configuration parameter the method createEclipseWriterConfig
> just needs
>
>        if(evaluateArtifactsFromEclipseWorkspace){
>                        projectName = projectBaseDir.getName();
>        }
>
> Problem solved.

Sure, the other way to solve it is to have two workspaces, one for
each release you are working on.
And this doesn't require changes to the code.

The other benefit is that if you are using Ctrl+Shift+T to find
classes you only get the release you are working on.
I've tried using the one workspace with multiple releases and it drove me nuts.
(Your sanity may vary)

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

Re: maven-eclipse-plugin Does not resolve workspace project name

[john.vint]

> This is not m-e-p's problem. Stop renaming your projects if you want
> to use m-e-p and use it to regenerate the .project files. Keep the
> name as the artifactId, or change the artifactId in the pom to meet
> your needs.

Lets assume a person is working on two different version (two releases being
developed in parallel).  They will both have the same artifact ID but
eclipse forces a different project name.  I don't think asking m-e-p to
offer this functionality is really an isnane request.  

The eclipse:eclipse plugin has worked perfectly fine as I have used it minus
this one issue.  The resolution was extremely easy.  

Including a new configuration parameter the method createEclipseWriterConfig
just needs 

if(evaluateArtifactsFromEclipseWorkspace){
projectName = projectBaseDir.getName(); 
}

Problem solved.  


-- 
View this message in context: 
http://maven.40175.n5.nabble.com/maven-eclipse-plugin-Does-not-resolve-workspace-project-name-tp3237890p3242262.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 Does not resolve workspace project name

[Benson Margulies]

Yup, it's in ASF svn, and if the project isn't willing to own it, they
should attic it.

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

Re: maven-eclipse-plugin Does not resolve workspace project name

[Ron Wheeler]

On 28/10/2010 9:35 AM, Martijn Dashorst wrote:

On Thu, Oct 28, 2010 at 2:54 PM, Ron Wheeler
  wrote:

It is hard to get enthusiastic about maintaining old software that has been
replaced by better stuff that is free.

maven-eclipse-plugin works roughly 100% of the time here, but the
m2eclipse plugin fails miserably with our maven project setup. And yes
we tried the latest version. It always results in having to download
and install vanilla eclipse.


Get Eclipse/STS and you have a much more current supported set of code and
everything that you need to develop with Maven.

Meh. sounds like having a commercial stake in the project. I happen to
like commandline mvn eclipse:eclipse without having to bloat my
eclipse installation with unnecessary plugins—eclipse has trouble
enough keeping up with the size of our projects.

No commercial interest.
It is free and I love getting everything I need installed in one 
download. Just add Hibernate plug-in and I am set to go.
We used vanilla Eclipse for a few years but every time we installed a 
new version we lost a day. Now we are done in1/2 an hour or less.


I will not say that it is a small download or does not include stuff 
that I do not use.


I love the Maven tools.


You can also get training and commercial level support if you want it.
Why would anyone want to invest in older technology?

Why is it older? Because you don't like command line tools? Happening
to like command line tools make someone a dinosaur?
I am too old to be enamoured with command line tools. I first started 
editing with Teco (after abandoning punched cards in the 60s). I can 
still get around in vi.

I like editing XML by hand but prefer to use the POM GUI editor.
I like pointing and clicking and checking off some buttons to get Maven 
to do what I want.


I guess that I regard "liking command line tools" as eccentric at most.
I am old enough to be careful with the word "dinosaur" in a forum that 
caters to a younger high-tech crowd. :-)



Is the maven-eclipse-plugin old because it is not given any resources
by sonatype which happens to maintain the m2eclipse plugin?

Why bother with building a release for maven at all? Doesn't m2eclipse
supplant that too?

Martijn

-
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 Does not resolve workspace project name

[Jason van Zyl]

I agree, there are many plugins that Maven developers just don't look after and 
they should be ejected and taken out of the org.maven.plugins name space. 
Anything there people assume are maintained which simply is not the case.

On Oct 28, 2010, at 10:58 AM, Antonio Petrelli wrote:

> 2010/10/28 Wayne Fay :
> So how does one get ownership of the plugin? I've contributed 2
>> 
>> This is open source so no one is stopping you from creating a fork.
> 
> Sorry to jump in but, in the Apache Committers' FAQ I read:
> http://www.apache.org/dev/committers.html#committer-responsibilities
> 
> 
> Applying patches
> In order to grow and maintain healthy communities, committers need to
> discuss, review and apply patches submitted by volunteers. The
> Committers are also responsible for the quality and IP clearance of
> the code that goes into ASF repositories.
> 
> 
> If you don't want to apply patches to m.e.p, please deprecate it, move
> it to archive, and abandon it *explicitly*. Or, if you don't want it,
> you have the responsibility *at least* to discuss them.
> Otherwise, contributors and committers are simply wasting time.
> 
> Antonio
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 

Thanks,

Jason

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

A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.

  -- Jakob Burckhardt

Re: maven-eclipse-plugin Does not resolve workspace project name

[Antonio Petrelli]

2010/10/28 Wayne Fay :
 So how does one get ownership of the plugin? I've contributed 2
>
> This is open source so no one is stopping you from creating a fork.

Sorry to jump in but, in the Apache Committers' FAQ I read:
http://www.apache.org/dev/committers.html#committer-responsibilities


Applying patches
In order to grow and maintain healthy communities, committers need to
discuss, review and apply patches submitted by volunteers. The
Committers are also responsible for the quality and IP clearance of
the code that goes into ASF repositories.


If you don't want to apply patches to m.e.p, please deprecate it, move
it to archive, and abandon it *explicitly*. Or, if you don't want it,
you have the responsibility *at least* to discuss them.
Otherwise, contributors and committers are simply wasting time.

Antonio

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

Re: maven-eclipse-plugin Does not resolve workspace project name

[Wayne Fay]

> m-e-p works better than M2ECLIPSE in many cases. Further, you have no
> proof here that I can see that the m-e-p is dead. To quote the plugin

I am the one who said "for all intents, m-e-p is dead" based entirely
on JIRA activity and releases, as well as the existence of newer (and
largely perceived as superior) tooling that is now available if you
are using Maven and Eclipse.

> If someone posts a patch, I don't think there/s much evidence that it
> will be ignored.

I'm also the one who said to go ahead and hack it to add this
functionality and submit a patch. You may also end up supporting your
own internal release of this plugin indefinitely, so realize that
right up front.

>>> So how does one get ownership of the plugin? I've contributed 2

This is open source so no one is stopping you from creating a fork.

Wayne

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

Re: maven-eclipse-plugin Does not resolve workspace project name

[Ron Wheeler]

Wrong person.
I was not the person claiming that patches were not being deployed.

Ron

On 28/10/2010 9:36 AM, Benson Margulies wrote:

Ron,

m-e-p works better than M2ECLIPSE in many cases. Further, you have no
proof here that I can see that the m-e-p is dead. To quote the plugin
site:

Last Published: 2010-02-25  | Version: 2.8

If someone posts a patch, I don't think there/s much evidence that it
will be ignored.

--benson


On Thu, Oct 28, 2010 at 8:54 AM, Ron Wheeder
  wrote:

On 28/10/2010 5:13 AM, Martijn Dashorst wrote:

So how does one get ownership of the plugin? I've contributed 2
patches with an implied promise that they would be included when the
failing ITs on Barrie's workspace were resolved. Unfortunately that is
the last of it.

I guess that you could take a copy and continue to maintain it.
If you want to build a team to maintain it and share it, then you probably
want to get the Maven group to cooperate.
If you are the only user/developer, you are off to the races.


Why the constant commercials for the m2eclipse plugin? Instead why not
ask for some interested developer to take over the
maven-eclipse-plugin? Isn't this an open source community?


It is hard to get enthusiastic about maintaining old software that has been
replaced by better stuff that is free.
Get Eclipse/STS and you have a much more current supported set of code and
everything that you need to develop with Maven.
You can also get training and commercial level support if you want it.
Why would anyone want to invest in older technology?

Ron


Martijn

On Wed, Oct 27, 2010 at 7:28 PM, Wayne Faywrote:

When I run eclipse:eclipse the project name in the .project file will be
the
artifactId (by default) despite the eclipse project name being something
different.

Yes, this is how m-e-p works. The .project file is overwritten by
m-e-p and so you will lose all settings that you set up in Eclipse
unless you also set them up in your pom via configuration:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html


This causes a problem when eclipse tries to build new projects workspace
because the eclipse workspace project is one thing and the .project's
project is something completely different.

This is not m-e-p's problem. Stop renaming your projects if you want
to use m-e-p and use it to regenerate the .project files. Keep the
name as the artifactId, or change the artifactId in the pom to meet
your needs.


How come the maven-eclipse-plugin will never resolve the workspace
project
name to the .project project name.  Or even offer a flag like
trueto override the
original
functionality?

In the last 180 days, there have been zero issues in MECLIPSE resolved.
At the same time, 40 have been updated and 20 were created.
http://jira.codehaus.org/browse/MECLIPSE

For all intents, m-e-p is dead. If you require this functionality,
feel free to hack the plugin to add it and donate your changes back to
be included in a future release -- but bear in mind there may never be
another release. The last release was Feb 23, 2010 and before that was
June 13, 2009.

I suggest upgrading to m2eclipse:
http://m2eclipse.sonatype.org/

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



-
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 Does not resolve workspace project name

[Jason van Zyl]

We're not stopping you from taking it. Put it in Github and hack away.

On Oct 28, 2010, at 5:13 AM, Martijn Dashorst wrote:

> So how does one get ownership of the plugin? I've contributed 2
> patches with an implied promise that they would be included when the
> failing ITs on Barrie's workspace were resolved. Unfortunately that is
> the last of it.
> 
> Why the constant commercials for the m2eclipse plugin? Instead why not
> ask for some interested developer to take over the
> maven-eclipse-plugin? Isn't this an open source community?
> 
> Martijn
> 
> On Wed, Oct 27, 2010 at 7:28 PM, Wayne Fay  wrote:
>>> When I run eclipse:eclipse the project name in the .project file will be the
>>> artifactId (by default) despite the eclipse project name being something
>>> different.
>> 
>> Yes, this is how m-e-p works. The .project file is overwritten by
>> m-e-p and so you will lose all settings that you set up in Eclipse
>> unless you also set them up in your pom via configuration:
>> http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
>> 
>>> This causes a problem when eclipse tries to build new projects workspace
>>> because the eclipse workspace project is one thing and the .project's
>>> project is something completely different.
>> 
>> This is not m-e-p's problem. Stop renaming your projects if you want
>> to use m-e-p and use it to regenerate the .project files. Keep the
>> name as the artifactId, or change the artifactId in the pom to meet
>> your needs.
>> 
>>> How come the maven-eclipse-plugin will never resolve the workspace project
>>> name to the .project project name.  Or even offer a flag like
>>> true to override the original
>>> functionality?
>> 
>> In the last 180 days, there have been zero issues in MECLIPSE resolved.
>> At the same time, 40 have been updated and 20 were created.
>> http://jira.codehaus.org/browse/MECLIPSE
>> 
>> For all intents, m-e-p is dead. If you require this functionality,
>> feel free to hack the plugin to add it and donate your changes back to
>> be included in a future release -- but bear in mind there may never be
>> another release. The last release was Feb 23, 2010 and before that was
>> June 13, 2009.
>> 
>> I suggest upgrading to m2eclipse:
>> http://m2eclipse.sonatype.org/
>> 
>> Wayne
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>> 
>> 
> 
> 
> 
> -- 
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 

Thanks,

Jason

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

Re: maven-eclipse-plugin Does not resolve workspace project name

[Benson Margulies]

Ron,

m-e-p works better than M2ECLIPSE in many cases. Further, you have no
proof here that I can see that the m-e-p is dead. To quote the plugin
site:

Last Published: 2010-02-25  | Version: 2.8

If someone posts a patch, I don't think there/s much evidence that it
will be ignored.

--benson


On Thu, Oct 28, 2010 at 8:54 AM, Ron Wheeder
 wrote:
> On 28/10/2010 5:13 AM, Martijn Dashorst wrote:
>>
>> So how does one get ownership of the plugin? I've contributed 2
>> patches with an implied promise that they would be included when the
>> failing ITs on Barrie's workspace were resolved. Unfortunately that is
>> the last of it.
>
> I guess that you could take a copy and continue to maintain it.
> If you want to build a team to maintain it and share it, then you probably
> want to get the Maven group to cooperate.
> If you are the only user/developer, you are off to the races.
>
>> Why the constant commercials for the m2eclipse plugin? Instead why not
>> ask for some interested developer to take over the
>> maven-eclipse-plugin? Isn't this an open source community?
>>
> It is hard to get enthusiastic about maintaining old software that has been
> replaced by better stuff that is free.
> Get Eclipse/STS and you have a much more current supported set of code and
> everything that you need to develop with Maven.
> You can also get training and commercial level support if you want it.
> Why would anyone want to invest in older technology?
>
> Ron
>
>> Martijn
>>
>> On Wed, Oct 27, 2010 at 7:28 PM, Wayne Fay  wrote:

 When I run eclipse:eclipse the project name in the .project file will be
 the
 artifactId (by default) despite the eclipse project name being something
 different.
>>>
>>> Yes, this is how m-e-p works. The .project file is overwritten by
>>> m-e-p and so you will lose all settings that you set up in Eclipse
>>> unless you also set them up in your pom via configuration:
>>> http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
>>>
 This causes a problem when eclipse tries to build new projects workspace
 because the eclipse workspace project is one thing and the .project's
 project is something completely different.
>>>
>>> This is not m-e-p's problem. Stop renaming your projects if you want
>>> to use m-e-p and use it to regenerate the .project files. Keep the
>>> name as the artifactId, or change the artifactId in the pom to meet
>>> your needs.
>>>
 How come the maven-eclipse-plugin will never resolve the workspace
 project
 name to the .project project name.  Or even offer a flag like
 true  to override the
 original
 functionality?
>>>
>>> In the last 180 days, there have been zero issues in MECLIPSE resolved.
>>> At the same time, 40 have been updated and 20 were created.
>>> http://jira.codehaus.org/browse/MECLIPSE
>>>
>>> For all intents, m-e-p is dead. If you require this functionality,
>>> feel free to hack the plugin to add it and donate your changes back to
>>> be included in a future release -- but bear in mind there may never be
>>> another release. The last release was Feb 23, 2010 and before that was
>>> June 13, 2009.
>>>
>>> I suggest upgrading to m2eclipse:
>>> http://m2eclipse.sonatype.org/
>>>
>>> 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
>
>

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

Re: maven-eclipse-plugin Does not resolve workspace project name

[Martijn Dashorst]

On Thu, Oct 28, 2010 at 2:54 PM, Ron Wheeler
 wrote:
> It is hard to get enthusiastic about maintaining old software that has been
> replaced by better stuff that is free.

maven-eclipse-plugin works roughly 100% of the time here, but the
m2eclipse plugin fails miserably with our maven project setup. And yes
we tried the latest version. It always results in having to download
and install vanilla eclipse.

> Get Eclipse/STS and you have a much more current supported set of code and
> everything that you need to develop with Maven.

Meh. sounds like having a commercial stake in the project. I happen to
like commandline mvn eclipse:eclipse without having to bloat my
eclipse installation with unnecessary plugins—eclipse has trouble
enough keeping up with the size of our projects.

> You can also get training and commercial level support if you want it.
> Why would anyone want to invest in older technology?

Why is it older? Because you don't like command line tools? Happening
to like command line tools make someone a dinosaur?
Is the maven-eclipse-plugin old because it is not given any resources
by sonatype which happens to maintain the m2eclipse plugin?

Why bother with building a release for maven at all? Doesn't m2eclipse
supplant that too?

Martijn

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

Re: maven-eclipse-plugin Does not resolve workspace project name

[Ron Wheeler]

On 28/10/2010 5:13 AM, Martijn Dashorst wrote:

So how does one get ownership of the plugin? I've contributed 2
patches with an implied promise that they would be included when the
failing ITs on Barrie's workspace were resolved. Unfortunately that is
the last of it.

I guess that you could take a copy and continue to maintain it.
If you want to build a team to maintain it and share it, then you 
probably want to get the Maven group to cooperate.

If you are the only user/developer, you are off to the races.


Why the constant commercials for the m2eclipse plugin? Instead why not
ask for some interested developer to take over the
maven-eclipse-plugin? Isn't this an open source community?

It is hard to get enthusiastic about maintaining old software that has 
been replaced by better stuff that is free.
Get Eclipse/STS and you have a much more current supported set of code 
and everything that you need to develop with Maven.

You can also get training and commercial level support if you want it.
Why would anyone want to invest in older technology?

Ron


Martijn

On Wed, Oct 27, 2010 at 7:28 PM, Wayne Fay  wrote:

When I run eclipse:eclipse the project name in the .project file will be the
artifactId (by default) despite the eclipse project name being something
different.

Yes, this is how m-e-p works. The .project file is overwritten by
m-e-p and so you will lose all settings that you set up in Eclipse
unless you also set them up in your pom via configuration:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html


This causes a problem when eclipse tries to build new projects workspace
because the eclipse workspace project is one thing and the .project's
project is something completely different.

This is not m-e-p's problem. Stop renaming your projects if you want
to use m-e-p and use it to regenerate the .project files. Keep the
name as the artifactId, or change the artifactId in the pom to meet
your needs.


How come the maven-eclipse-plugin will never resolve the workspace project
name to the .project project name.  Or even offer a flag like
true  to override the original
functionality?

In the last 180 days, there have been zero issues in MECLIPSE resolved.
At the same time, 40 have been updated and 20 were created.
http://jira.codehaus.org/browse/MECLIPSE

For all intents, m-e-p is dead. If you require this functionality,
feel free to hack the plugin to add it and donate your changes back to
be included in a future release -- but bear in mind there may never be
another release. The last release was Feb 23, 2010 and before that was
June 13, 2009.

I suggest upgrading to m2eclipse:
http://m2eclipse.sonatype.org/

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: maven-eclipse-plugin Does not resolve workspace project name

[Martijn Dashorst]

So how does one get ownership of the plugin? I've contributed 2
patches with an implied promise that they would be included when the
failing ITs on Barrie's workspace were resolved. Unfortunately that is
the last of it.

Why the constant commercials for the m2eclipse plugin? Instead why not
ask for some interested developer to take over the
maven-eclipse-plugin? Isn't this an open source community?

Martijn

On Wed, Oct 27, 2010 at 7:28 PM, Wayne Fay  wrote:
>> When I run eclipse:eclipse the project name in the .project file will be the
>> artifactId (by default) despite the eclipse project name being something
>> different.
>
> Yes, this is how m-e-p works. The .project file is overwritten by
> m-e-p and so you will lose all settings that you set up in Eclipse
> unless you also set them up in your pom via configuration:
> http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
>
>> This causes a problem when eclipse tries to build new projects workspace
>> because the eclipse workspace project is one thing and the .project's
>> project is something completely different.
>
> This is not m-e-p's problem. Stop renaming your projects if you want
> to use m-e-p and use it to regenerate the .project files. Keep the
> name as the artifactId, or change the artifactId in the pom to meet
> your needs.
>
>> How come the maven-eclipse-plugin will never resolve the workspace project
>> name to the .project project name.  Or even offer a flag like
>> true to override the original
>> functionality?
>
> In the last 180 days, there have been zero issues in MECLIPSE resolved.
> At the same time, 40 have been updated and 20 were created.
> http://jira.codehaus.org/browse/MECLIPSE
>
> For all intents, m-e-p is dead. If you require this functionality,
> feel free to hack the plugin to add it and donate your changes back to
> be included in a future release -- but bear in mind there may never be
> another release. The last release was Feb 23, 2010 and before that was
> June 13, 2009.
>
> I suggest upgrading to m2eclipse:
> http://m2eclipse.sonatype.org/
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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

Re: maven-eclipse-plugin Does not resolve workspace project name

[Ron Wheeler]

On 27/10/2010 1:28 PM, Wayne Fay wrote:

When I run eclipse:eclipse the project name in the .project file will be the
artifactId (by default) despite the eclipse project name being something
different.

Yes, this is how m-e-p works. The .project file is overwritten by
m-e-p and so you will lose all settings that you set up in Eclipse
unless you also set them up in your pom via configuration:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html


This causes a problem when eclipse tries to build new projects workspace
because the eclipse workspace project is one thing and the .project's
project is something completely different.

This is not m-e-p's problem. Stop renaming your projects if you want
to use m-e-p and use it to regenerate the .project files. Keep the
name as the artifactId, or change the artifactId in the pom to meet
your needs.


How come the maven-eclipse-plugin will never resolve the workspace project
name to the .project project name.  Or even offer a flag like
true  to override the original
functionality?

In the last 180 days, there have been zero issues in MECLIPSE resolved.
At the same time, 40 have been updated and 20 were created.
http://jira.codehaus.org/browse/MECLIPSE

For all intents, m-e-p is dead. If you require this functionality,
feel free to hack the plugin to add it and donate your changes back to
be included in a future release -- but bear in mind there may never be
another release. The last release was Feb 23, 2010 and before that was
June 13, 2009.

I suggest upgrading to m2eclipse:
http://m2eclipse.sonatype.org/

Or just move to Eclipse/STS(free) and get everything, all included.


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: maven-eclipse-plugin and POM packaging projects

[Stephen Connolly]

you can right click on one of the project root folders, select the maven
item and one of the sub-menu items will do what you want

-S

On 17 June 2010 12:28, Daniele Dellafiore  wrote:

> M2Eclipse does some things fine but not all.
>
> Use case:
>
> pom A define a resource folder
> I have in eclipse, imported with M2E, project A and B, the latter inherit
> from A.
>
> Change the resource folder in A from eclipse, save.
> Nothing change in eclipse.
>
> So while changing a dep in the pom make the builder run, changing resourcer
> requires maven-eclipse-plugin.
>
> Or maybe I am making something wrong.
>
> On Wed, Jun 16, 2010 at 9:18 PM, Wayne Fay  wrote:
>
> > > Actually, m-e-p does not create any .project while M2Eclipse import
> both
> > of
> > > them... and the multi-module is useless and I will just delete it.
> >
> > IMO you are better off just switching over to m2eclipse full time
> > instead of continuing to fight with m-e-p.
> >
> > Wayne
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
>
> --
> Daniele Dellafiore
> http://danieledellafiore.net
>

Re: maven-eclipse-plugin and POM packaging projects

[Daniele Dellafiore]

M2Eclipse does some things fine but not all.

Use case:

pom A define a resource folder
I have in eclipse, imported with M2E, project A and B, the latter inherit
from A.

Change the resource folder in A from eclipse, save.
Nothing change in eclipse.

So while changing a dep in the pom make the builder run, changing resourcer
requires maven-eclipse-plugin.

Or maybe I am making something wrong.

On Wed, Jun 16, 2010 at 9:18 PM, Wayne Fay  wrote:

> > Actually, m-e-p does not create any .project while M2Eclipse import both
> of
> > them... and the multi-module is useless and I will just delete it.
>
> IMO you are better off just switching over to m2eclipse full time
> instead of continuing to fight with m-e-p.
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Daniele Dellafiore
http://danieledellafiore.net

Re: maven-eclipse-plugin and POM packaging projects

[Wayne Fay]

> Actually, m-e-p does not create any .project while M2Eclipse import both of
> them... and the multi-module is useless and I will just delete it.

IMO you are better off just switching over to m2eclipse full time
instead of continuing to fight with m-e-p.

Wayne

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

Re: maven-eclipse-plugin and POM packaging projects

[Daniele Dellafiore]

Mixed feeling for me.

MultiModule pom project aren't to be imported as a project, I do agree.
But parent kind of pom project, I would like to see them imported. Problem
is that there is no way in maven to make a distinction.

Actually, m-e-p does not create any .project while M2Eclipse import both of
them... and the multi-module is useless and I will just delete it.

On Wed, Jun 16, 2010 at 5:14 PM, Martijn Dashorst <
martijn.dasho...@gmail.com> wrote:

> On Tue, Jun 15, 2010 at 12:04 PM, Daniele Dellafiore 
> wrote:
> > I have "patched" maven-eclipse-plugin to create an eclipse project also
> for
> > projects with "pom" packaging type.
> > I was wondering if this was a bug or a feature and if someone is
> interested
> > in the plugin behaving this way other than me.
>
> I am glad the pom packaging projects don't generate .project files
> anymore. It was a drag with importing multimodule projects in eclipse.
> Far more easy to get all non-pom projects in one go, and just add the
> three pom type projects.
>
> My €0.02 (which isn't that much worth nowadays)
>
> Martijn
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Daniele Dellafiore
http://danieledellafiore.net

Re: maven-eclipse-plugin and POM packaging projects

[Martijn Dashorst]

On Tue, Jun 15, 2010 at 12:04 PM, Daniele Dellafiore  wrote:
> I have "patched" maven-eclipse-plugin to create an eclipse project also for
> projects with "pom" packaging type.
> I was wondering if this was a bug or a feature and if someone is interested
> in the plugin behaving this way other than me.

I am glad the pom packaging projects don't generate .project files
anymore. It was a drag with importing multimodule projects in eclipse.
Far more easy to get all non-pom projects in one go, and just add the
three pom type projects.

My €0.02 (which isn't that much worth nowadays)

Martijn

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

Re: [maven-eclipse-plugin] Spring dependencies omitted

[Barrie Treloar]

On Thu, Mar 11, 2010 at 6:39 PM, Pascal Kesseli
wrote:

> Hi everyone
>
> Being a typical maven fan, I tried to manage our eclipse plugins using
> maven. To do so, I configured the maven-eclipse-plugin as follows:
>
> 
>org.apache.maven.plugins
>maven-eclipse-plugin
>2.8
>
>true
>META-INF/MANIFEST.MF
>
>2.5.6
>spring.cfg.xml
>src/main/resources
>
>
> 
>
> First off, I am not even sure what exactly the spring-tag in here is good
> for? What does the plugin do with that information? Secondly, as described
> on the apache website, the plugin is supposed to copy all the dependencies
> as jars to my project root. While that works well with almost any
> dependency, the plugin constantly ignores any Spring dependency I have
> added
> to my project, such as spring-aspects, spring-core or spring-test.
>
> Does anybody know where that behavior evolves from?
>

I'm not sure that the pde mode does what you think it does.

See http://maven.apache.org/plugins/maven-eclipse-plugin/pde.html

"Note that the scope of the *maven-eclipse-plugin* is to synchronise the
Eclipse *.project* and *.classpath* files with the configuration found in
the pom file. Once you have finished configuring the Eclipse plugin as
below, and once you have run the *eclipse:eclipse* goal, you will be in a
position to build your plugin code with the Eclipse IDE, or the Eclipse
headless PDE 
build.
The Eclipse headless PDE build can be triggered from within Maven using the
pde-maven-plugin "

To get maven to build PDE projects I have used (3 years ago) the plugin (now
unmaintained) http://mojo.codehaus.org/pde-maven-plugin/

You may also be able to use Tycho
http://docs.codehaus.org/display/M2ECLIPSE/Tycho+project+overview

I also cant see any documentation about using the configuration section as
you have done - which tends to indicate its not supported.

Re: maven-eclipse-plugin configuration for pom packaging

[Barrie Treloar]

On Fri, Nov 6, 2009 at 7:34 AM, james.w.jackson
 wrote:
> In the end it was a pyrrhic victory.  I was hoping to use the eclipse
> Import...->Existing Projects into Workspace, but it stops recursing once it
> finds a folder with a .project file--which is not terribly useful for a
> multi-module projects with many component and sub-component parent poms.

p.s. I missed this.
See http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html
Right towards the bottom is this

"Note, you have to delete the .project-file of your parent project
before. The result is the same as checking out the whole project from
the command line, running mvn eclipse:eclipse and finally importing
the projects into your Eclipse workspace. In both cases you will be
able to synchronize your changes using Eclipse."

Eclipse doesn't really support projects within projects, but by
deleting the .project file of the parent project you can then use
Import Existing and it will find the modules.
Don't worry about deleting this file, it is regenerated via Eclipse 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 configuration for pom packaging

[Barrie Treloar]

If you checkout your project from your revision control system via
eclipse, it should already be available as a project.

Otherwise, you have to cheat to get it into eclipse.

File > New Project
General > Project
Specify "Project name"
Uncheck "Use default location"
Browse to where the top level project is.
Click "Finish"

You should now have your top level project in eclipse.

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

Re: maven-eclipse-plugin configuration for pom packaging

[james.w.jackson]

I was afraid of that.

I eventually manhandled the plugin in my pom.xml files that had pom
packaging to get the .project files, but it doesn't feel right: 


org.apache.maven.plugins
maven-eclipse-plugin

jar



In the end it was a pyrrhic victory.  I was hoping to use the eclipse
Import...->Existing Projects into Workspace, but it stops recursing once it
finds a folder with a .project file--which is not terribly useful for a
multi-module projects with many component and sub-component parent poms.

Thanks for the response,
Jim


Arnaud HERITIER wrote:
> 
> The plugin doesn't support it.
> I think there's a an issue already opened about that.
> You can vote for it.
> 
> It is supported by m2eclipse or Q4E.
> 
> Cheers,
> 
> Arnaud Héritier
> Software Factory Manager
> eXo platform - http://www.exoplatform.com
> ---
> http://www.aheritier.net
> 
> 
> On Thu, Nov 5, 2009 at 5:39 PM, james.w.jackson <
> james.w.jack...@baesystems.com> wrote:
> 
>>
>> I'm using maven 2.2.1 and maven-eclipse-plugin 2.7 with a multi-module
>> project.
>>
>> When I run 'mvn eclipse:eclipse' in the multi-module project, it doesn't
>> generate .project eclipse files for the projects that are marked as
>> pom.
>>
>> How can I configure the plugin to generate .project files for projects
>> that
>> have the pom packaging?
>>
>> Thanks,
>> Jim
>> --
>> View this message in context:
>> http://old.nabble.com/maven-eclipse-plugin-configuration-for-pom-packaging-tp26215800p26215800.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
>>
>>
> 
> 

-- 
View this message in context: 
http://old.nabble.com/maven-eclipse-plugin-configuration-for-pom-packaging-tp26215800p26222157.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 configuration for pom packaging

[Arnaud HERITIER]

The plugin doesn't support it.
I think there's a an issue already opened about that.
You can vote for it.

It is supported by m2eclipse or Q4E.

Cheers,

Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net


On Thu, Nov 5, 2009 at 5:39 PM, james.w.jackson <
james.w.jack...@baesystems.com> wrote:

>
> I'm using maven 2.2.1 and maven-eclipse-plugin 2.7 with a multi-module
> project.
>
> When I run 'mvn eclipse:eclipse' in the multi-module project, it doesn't
> generate .project eclipse files for the projects that are marked as
> pom.
>
> How can I configure the plugin to generate .project files for projects that
> have the pom packaging?
>
> Thanks,
> Jim
> --
> View this message in context:
> http://old.nabble.com/maven-eclipse-plugin-configuration-for-pom-packaging-tp26215800p26215800.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 and src/main/webapp with Eclipse

[Barrie Treloar]

On Sat, Oct 24, 2009 at 1:58 AM, Vincent F  wrote:
>
> OK, thanks everyone for these additional infos. I may stick with WTP
> organisation then (using /WebContent/ instead of /src/main/webapp/) just for
> convenience in Eclipse.

You should be able to use /src/main/webapp thats what the file
.settings/org.eclipse.wst.common.component is for.

Why not have a look at what is in this file for a standard WTP project
and then see if you can set the values to point to /src/main/webapp.
eclipse:eclipse is meant to support it from my understanding.
Maybe it is out of sync with your version of WTP.

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

Re: maven-eclipse-plugin and src/main/webapp with Eclipse

[Vincent F]

OK, thanks everyone for these additional infos. I may stick with WTP
organisation then (using /WebContent/ instead of /src/main/webapp/) just for
convenience in Eclipse.

-- 
Vincent



baerrach wrote:
> 
> On Fri, Oct 23, 2009 at 10:50 AM, Benson Margulies
>  wrote:
>> An Eclipse project type, or perspective, can decide to show the tree any
>> way
>> it likes. The default Java perspective shows all folders as ordinary
>> folders
>> except source folders. It hauls source folders to the top of the project,
>> gives them a special icon, and labels them with the full pathname (e.g.
>> "src/main/java"). In a WTP project, the web content root is also hauled
>> to
>> the top and specially labelled.  There is no general scheme for marking
>> some
>> arbitrary folder for this treatment. So, unless you are using WTP, and
>> telling eclipse:eclipse to write configuration for WTP, you are stuck
>> with
>> the irritating folder location. Unless you want to write your own Eclipse
>> plugin that rearranged the display in this case.
> 
> Thanks Benson, not working with WTP myself, this was exactly what I
> wanted to explain to Vincent.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/maven-eclipse-plugin-and-src-main-webapp-with-Eclipse-tp25996692p26028471.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 and src/main/webapp with Eclipse

[Barrie Treloar]

On Fri, Oct 23, 2009 at 10:50 AM, Benson Margulies
 wrote:
> An Eclipse project type, or perspective, can decide to show the tree any way
> it likes. The default Java perspective shows all folders as ordinary folders
> except source folders. It hauls source folders to the top of the project,
> gives them a special icon, and labels them with the full pathname (e.g.
> "src/main/java"). In a WTP project, the web content root is also hauled to
> the top and specially labelled.  There is no general scheme for marking some
> arbitrary folder for this treatment. So, unless you are using WTP, and
> telling eclipse:eclipse to write configuration for WTP, you are stuck with
> the irritating folder location. Unless you want to write your own Eclipse
> plugin that rearranged the display in this case.

Thanks Benson, not working with WTP myself, this was exactly what I
wanted to explain to Vincent.

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

Re: maven-eclipse-plugin and src/main/webapp with Eclipse

[Benson Margulies]

An Eclipse project type, or perspective, can decide to show the tree any way
it likes. The default Java perspective shows all folders as ordinary folders
except source folders. It hauls source folders to the top of the project,
gives them a special icon, and labels them with the full pathname (e.g.
"src/main/java"). In a WTP project, the web content root is also hauled to
the top and specially labelled.  There is no general scheme for marking some
arbitrary folder for this treatment. So, unless you are using WTP, and
telling eclipse:eclipse to write configuration for WTP, you are stuck with
the irritating folder location. Unless you want to write your own Eclipse
plugin that rearranged the display in this case.

On Thu, Oct 22, 2009 at 6:21 PM, Barrie Treloar  wrote:

> On Fri, Oct 23, 2009 at 6:31 AM, Vincent F 
> wrote:
> >
> > My plugin configuration is the following
> >
> > 
> >  org.apache.maven.plugins
> >  maven-eclipse-plugin
> >  2.7
> > 
> > war
> > false
> > 2.0
> > true
> > 
> > 
> >
> > So as you can see, packaging is "war" but /src/main/webapp is not added
> as a
>
> You dont need to specify packaging, its default value is
> ${project.packaging} so it should already be set to war.
>
> > I don't see warSourceDirectory as a maven-eclipse-plugin's property, but
> > rather maven-war-plugin. How would that have an impact on
> > maven-eclipse-plugin ?
>
> The code pulls the value out from the maven war plugin configuration,
> and defaults to /src/main/webapp as below:
>
>File warSourceDirectory =
>new File( IdeUtils.getPluginSetting(
> config.getProject(), JeeUtils.ARTIFACT_MAVEN_WAR_PLUGIN,
>
> "warSourceDirectory", //$NON-NLS-1$
>
> config.getProject().getBasedir() + "/src/main/webapp" ) );
> //$NON-NLS-1$
>
> > source. In the .classpath file, the 2 only relevant lines are
> >  
> >   > excluding="**/*.java"/>
> >
> > but nothing about src/main/webapp
> >
>
> I dont use WTP so I am only going by the docs and the code.
>
> From the looks of the code /src/main/webapp doesn't get added to the
> .classpath file, it gets added to
>  .settings/org.eclipse.wst.common.component
> file as
>  
>
> And looking at the integration tests, I dont think what you are asking
> for is how eclipse:eclipse works.
>
> From the little reading I have done on the documentation
> src/main/webapp refers to your web sources and thus they shouldn't be
> on the classpath.
> I think you are stuck drilling down those directories manually.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: maven-eclipse-plugin and src/main/webapp with Eclipse

[Barrie Treloar]

On Fri, Oct 23, 2009 at 6:31 AM, Vincent F  wrote:
>
> My plugin configuration is the following
>
> 
>      org.apache.maven.plugins
>      maven-eclipse-plugin
>      2.7
>         
>             war
>             false
>             2.0
>             true
>         
> 
>
> So as you can see, packaging is "war" but /src/main/webapp is not added as a

You dont need to specify packaging, its default value is
${project.packaging} so it should already be set to war.

> I don't see warSourceDirectory as a maven-eclipse-plugin's property, but
> rather maven-war-plugin. How would that have an impact on
> maven-eclipse-plugin ?

The code pulls the value out from the maven war plugin configuration,
and defaults to /src/main/webapp as below:

File warSourceDirectory =
new File( IdeUtils.getPluginSetting(
config.getProject(), JeeUtils.ARTIFACT_MAVEN_WAR_PLUGIN,

"warSourceDirectory", //$NON-NLS-1$

config.getProject().getBasedir() + "/src/main/webapp" ) );
//$NON-NLS-1$

> source. In the .classpath file, the 2 only relevant lines are
>  
>   excluding="**/*.java"/>
>
> but nothing about src/main/webapp
>

I dont use WTP so I am only going by the docs and the code.

>From the looks of the code /src/main/webapp doesn't get added to the
.classpath file, it gets added to
  .settings/org.eclipse.wst.common.component
file as
  

And looking at the integration tests, I dont think what you are asking
for is how eclipse:eclipse works.

>From the little reading I have done on the documentation
src/main/webapp refers to your web sources and thus they shouldn't be
on the classpath.
I think you are stuck drilling down those directories manually.

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

Re: maven-eclipse-plugin and src/main/webapp with Eclipse

[Vincent F]

My plugin configuration is the following


  org.apache.maven.plugins
  maven-eclipse-plugin
  2.7
 
 war
 false
 2.0
 true
 


So as you can see, packaging is "war" but /src/main/webapp is not added as a
source. In the .classpath file, the 2 only relevant lines are
  
  

but nothing about src/main/webapp

I don't see warSourceDirectory as a maven-eclipse-plugin's property, but
rather maven-war-plugin. How would that have an impact on
maven-eclipse-plugin ?


Thanks

-- 
Vincent 





baerrach wrote:
> 
> On Thu, Oct 22, 2009 at 9:37 AM, Vincent F 
> wrote:
>>
>> Thanks for your answer. I'm going to be very picky here, but is there a
>> way
>> to have the src/main/webapp folder " folded as one in Eclipse, just like
>> the
>> src/main/java and src/main/resources are ?
> 
> Can you please post how you are running eclipse:eclipse?
> I suspect that you are not enabling wtp support.
> 
> Have you read
> http://maven.apache.org/plugins/maven-eclipse-plugin/examples/multi-module-projects.html
> 
> I can see from the eclipse plugins code that if packaging = "war" then
> a source directory is added.
> The default is /src/main/webapp
> You can configure this via the warSourceDirectory property.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/maven-eclipse-plugin-and-src-main-webapp-with-Eclipse-tp25996692p26016271.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 and src/main/webapp with Eclipse

[Roland Asmann]

Also, if you use WTP in Eclipse, it will work this way. I'd guess that if
you would get it to work, Eclipse would probably build incorrect WAR-files
because it would include the contents of that folder as both resources and
as real web-application.

So, just get used to it, it isn't broken and therefor doesn't need fixing!

Roland


> It doesn't really make sense for src/main/webapp to be a source folder -
> it doesn't contain compilable source files.
>
> Justin
>
> -Original Message-
> From: Vincent F [mailto:vincent.fu...@sgcib.com]
> Sent: Wednesday, October 21, 2009 1:22 PM
> To: users@maven.apache.org
> Subject: maven-eclipse-plugin and src/main/webapp with Eclipse
>
>
> Hi,
>
> I'm trying to move my current project structure to Maven Standard
> Directory Layout, so that everything I had in /WebContent is now in
> src/main/webapp .
> It works fine for the packaging.
>
> However, when using maven-eclipse-plugin 2.7 to update my Eclipse
> project and configuration files, I was expecting that src/main/webapp
> would be seen by Eclipse like a source folder, just like src/main/java
> and src/main/resources. Instead, it is seens as a regular folder, so I
> have to drill down from src to main to webapp to access my files.
>
> I've tried several things in maven-eclipse-plugin configuration, like
>
> 
> src/main/webapp/**/*.*
> 
>
> for example, but it doesn't work.
>
> Is there a way to fix this ? Or maybe it is not meant to be fixed
> because I shouldn't have src/main/webapp as a source folder ?
> Any piece of advice would be appreciated
>
> Thanks
>
> --
> Vincent
>
>
>
>
>
> --
> View this message in context:
> http://www.nabble.com/maven-eclipse-plugin-and-src-main-webapp-with-Ecli
> pse-tp25996692p25996692.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: maven-eclipse-plugin and src/main/webapp with Eclipse

[Barrie Treloar]

On Thu, Oct 22, 2009 at 9:37 AM, Vincent F  wrote:
>
> Thanks for your answer. I'm going to be very picky here, but is there a way
> to have the src/main/webapp folder " folded as one in Eclipse, just like the
> src/main/java and src/main/resources are ?

Can you please post how you are running eclipse:eclipse?
I suspect that you are not enabling wtp support.

Have you read 
http://maven.apache.org/plugins/maven-eclipse-plugin/examples/multi-module-projects.html

I can see from the eclipse plugins code that if packaging = "war" then
a source directory is added.
The default is /src/main/webapp
You can configure this via the warSourceDirectory property.

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

RE: maven-eclipse-plugin and src/main/webapp with Eclipse

[Vincent F]

Thanks for your answer. I'm going to be very picky here, but is there a way
to have the src/main/webapp folder " folded as one in Eclipse, just like the
src/main/java and src/main/resources are ?

Vincent



justinedelson wrote:
> 
> It doesn't really make sense for src/main/webapp to be a source folder -
> it doesn't contain compilable source files.
> 
> Justin 
> 
> -Original Message-
> From: Vincent F [mailto:vincent.fu...@sgcib.com] 
> Sent: Wednesday, October 21, 2009 1:22 PM
> To: users@maven.apache.org
> Subject: maven-eclipse-plugin and src/main/webapp with Eclipse
> 
> 
> Hi,
> 
> I'm trying to move my current project structure to Maven Standard
> Directory Layout, so that everything I had in /WebContent is now in
> src/main/webapp .
> It works fine for the packaging.
> 
> However, when using maven-eclipse-plugin 2.7 to update my Eclipse
> project and configuration files, I was expecting that src/main/webapp
> would be seen by Eclipse like a source folder, just like src/main/java
> and src/main/resources. Instead, it is seens as a regular folder, so I
> have to drill down from src to main to webapp to access my files. 
> 
> I've tried several things in maven-eclipse-plugin configuration, like
> 
> 
> src/main/webapp/**/*.*
> 
> 
> for example, but it doesn't work.
> 
> Is there a way to fix this ? Or maybe it is not meant to be fixed
> because I shouldn't have src/main/webapp as a source folder ?
> Any piece of advice would be appreciated
> 
> Thanks
> 
> --
> Vincent
> 
> 
> 
> 
>  
> -- 
> View this message in context:
> http://www.nabble.com/maven-eclipse-plugin-and-src-main-webapp-with-Ecli
> pse-tp25996692p25996692.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
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/maven-eclipse-plugin-and-src-main-webapp-with-Eclipse-tp25996692p26001637.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 and src/main/webapp with Eclipse

[Edelson, Justin]

It doesn't really make sense for src/main/webapp to be a source folder -
it doesn't contain compilable source files.

Justin 

-Original Message-
From: Vincent F [mailto:vincent.fu...@sgcib.com] 
Sent: Wednesday, October 21, 2009 1:22 PM
To: users@maven.apache.org
Subject: maven-eclipse-plugin and src/main/webapp with Eclipse


Hi,

I'm trying to move my current project structure to Maven Standard
Directory Layout, so that everything I had in /WebContent is now in
src/main/webapp .
It works fine for the packaging.

However, when using maven-eclipse-plugin 2.7 to update my Eclipse
project and configuration files, I was expecting that src/main/webapp
would be seen by Eclipse like a source folder, just like src/main/java
and src/main/resources. Instead, it is seens as a regular folder, so I
have to drill down from src to main to webapp to access my files. 

I've tried several things in maven-eclipse-plugin configuration, like


src/main/webapp/**/*.*


for example, but it doesn't work.

Is there a way to fix this ? Or maybe it is not meant to be fixed
because I shouldn't have src/main/webapp as a source folder ?
Any piece of advice would be appreciated

Thanks

--
Vincent




 
-- 
View this message in context:
http://www.nabble.com/maven-eclipse-plugin-and-src-main-webapp-with-Ecli
pse-tp25996692p25996692.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: maven-eclipse-plugin issue

[Barrie Treloar]

Did you check the plugin documentation?

http://maven.apache.org/plugins/maven-eclipse-plugin/examples/ajdt-projects.html

AspectJ needs more than just the dependencies for the eclipse .project to work.

You need

  1.5

See the above link as you may also need to configure
org.codehaus.mojo
aspectj-maven-plugin

Caveat: I've never used AspectJ so I am just linking from the docs.

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

RE: maven eclipse plugin and wtp

[massive.boisson]

Let me answer my own question. 

After searching the m2 forum, I found: 
http://www.nabble.com/How-to-convert-or-use-a-Maven-project-as-a-dynamic-web-project--to23430177.html#a23432587

For anyone looking to do this, it's very simple, you just need to make sure
you have installed "m2e WTP
Integration optional feature installed". You just import/general/maven
project

Again, thanks, and sorry for extra posting.


massive.boisson wrote:
> 
> Thank you guys,
> 
> I do need to debug. 
> 
> It was not obvious at all to me how to import existing java web maven
> project into eclipse wtp project using m2 eclipse plugin. And I tried to
> figure it out.
> 
> Do you have a hint or two?
> 
> Thanks
> 
> -MB
> 
> 
> mgainty wrote:
>> 
>> 
>> m2 is the better solution if you need to debug
>> curious as to what term CI means?
>> 
>> Martin 
>> Ask about "software clunker upgrade program"
>> __ 
>> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>>  
>> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
>> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede
>> unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese
>> Nachricht dient lediglich dem Austausch von Informationen und entfaltet
>> keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit
>> von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
>> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas
>> le destinataire prévu, nous te demandons avec bonté que pour satisfaire
>> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la
>> copie de ceci est interdite. Ce message sert à l'information seulement et
>> n'aura pas n'importe quel effet légalement obligatoire. Étant donné que
>> les email peuvent facilement être sujets à la manipulation, nous ne
>> pouvons accepter aucune responsabilité pour le contenu fourni.
>> 
>> 
>> 
>> 
>>> Date: Tue, 4 Aug 2009 09:39:17 -0400
>>> Subject: Re: maven eclipse plugin and wtp
>>> From: w...@wantii.com
>>> To: users@maven.apache.org
>>> 
>>> On Tue, Aug 4, 2009 at 9:27 AM,
>>> massive.boisson wrote:
>>> >
>>> > Hi, I have a maven project (that is web project by its nature) and I
>>> want to
>>> > run it in eclipse as WTP project.
>>> >
>>> > I found command (on
>>> > http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html):
>>> > mvn -Dwtpversion=R7 eclipse:eclipse
>>> > Where wtpversion can be R7, 1.0, 1.5, 2.0 or none (default).
>>> >
>>> >
>>> > As current wtp version is 3.1, can I use
>>> > mvn -Dwtpversion=3.1 eclipse:eclipse
>>> >
>>> >
>>> > Or is there a new or prefered way to do this?
>>> >
>>> >
>>> 
>>> When you specify the WTP version, you are telling the plugin which
>>> type of configuration to generate. Eclipse has the ability to "import"
>>> from older versions, so even though WTP version 2.0 is from '08, it
>>> shouldn't hurt to use 2.0, then let eclipse import it.
>>> 
>>> At the same time, when using the eclipse plugin, you should ask
>>> yourself which you want to depend on more, eclipse or maven? Eclipse
>>> and maven both handle many similar tasks, but if you use the eclipse
>>> functionality, you are locked into eclipse... There are many eclipse
>>> tools that are helpful, but for building and testing, I prefer to
>>> leave it to maven. That being the case, what does WTP give you that is
>>> most important? IMO, it's the ability to run your web-app right from
>>> the IDE... You can install a tomcat runtime right in WTP and tell
>>> eclipse to run your web-app in it. If this is the feature you are
>>> looking for, then I would say that you could do one better and use the
>>> maven-tomcat-plugin to get the same functionality.
>>> 
>>> Instead of using the maven-eclipse-plugin to generate eclipse
>>> configuration files, try using the m2eclipse eclipse plugin to have
>>> eclipse become more "maven-aware". Then, you can create an eclipse run
>>> configuration that launches 'mvn tomcat:run'. You will have the
>>> ability to debug your web-app using the eclipse debugger. In addition,
>>> you will also have the nifty pom editory th

RE: maven eclipse plugin and wtp

[massive.boisson]

Thank you guys,

I do need to debug. 

It was not obvious at all to me how to import existing java web maven
project into eclipse wtp project using m2 eclipse plugin. And I tried to
figure it out.

Do you have a hint or two?

Thanks

-MB


mgainty wrote:
> 
> 
> m2 is the better solution if you need to debug
> curious as to what term CI means?
> 
> Martin 
> Ask about "software clunker upgrade program"
> __ 
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>  
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> dient lediglich dem Austausch von Informationen und entfaltet keine
> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
> destinataire prévu, nous te demandons avec bonté que pour satisfaire
> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la
> copie de ceci est interdite. Ce message sert à l'information seulement et
> n'aura pas n'importe quel effet légalement obligatoire. Étant donné que
> les email peuvent facilement être sujets à la manipulation, nous ne
> pouvons accepter aucune responsabilité pour le contenu fourni.
> 
> 
> 
> 
>> Date: Tue, 4 Aug 2009 09:39:17 -0400
>> Subject: Re: maven eclipse plugin and wtp
>> From: w...@wantii.com
>> To: users@maven.apache.org
>> 
>> On Tue, Aug 4, 2009 at 9:27 AM,
>> massive.boisson wrote:
>> >
>> > Hi, I have a maven project (that is web project by its nature) and I
>> want to
>> > run it in eclipse as WTP project.
>> >
>> > I found command (on
>> > http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html):
>> > mvn -Dwtpversion=R7 eclipse:eclipse
>> > Where wtpversion can be R7, 1.0, 1.5, 2.0 or none (default).
>> >
>> >
>> > As current wtp version is 3.1, can I use
>> > mvn -Dwtpversion=3.1 eclipse:eclipse
>> >
>> >
>> > Or is there a new or prefered way to do this?
>> >
>> >
>> 
>> When you specify the WTP version, you are telling the plugin which
>> type of configuration to generate. Eclipse has the ability to "import"
>> from older versions, so even though WTP version 2.0 is from '08, it
>> shouldn't hurt to use 2.0, then let eclipse import it.
>> 
>> At the same time, when using the eclipse plugin, you should ask
>> yourself which you want to depend on more, eclipse or maven? Eclipse
>> and maven both handle many similar tasks, but if you use the eclipse
>> functionality, you are locked into eclipse... There are many eclipse
>> tools that are helpful, but for building and testing, I prefer to
>> leave it to maven. That being the case, what does WTP give you that is
>> most important? IMO, it's the ability to run your web-app right from
>> the IDE... You can install a tomcat runtime right in WTP and tell
>> eclipse to run your web-app in it. If this is the feature you are
>> looking for, then I would say that you could do one better and use the
>> maven-tomcat-plugin to get the same functionality.
>> 
>> Instead of using the maven-eclipse-plugin to generate eclipse
>> configuration files, try using the m2eclipse eclipse plugin to have
>> eclipse become more "maven-aware". Then, you can create an eclipse run
>> configuration that launches 'mvn tomcat:run'. You will have the
>> ability to debug your web-app using the eclipse debugger. In addition,
>> you will also have the nifty pom editory that comes with m2eclipse.
>> This will leave you with a project that is more portable across IDEs,
>> in case someone on your team later decides to use something other than
>> eclipse. In addition, your build/test process can be run in a CI
>> environment like hudson.
>> 
>> -Wes
>> 
>> -- 
>> Wes Wannemacher
>> 
>> Head Engineer, WanTii, Inc.
>> Need Training? Struts, Spring, Maven, Tomcat...
>> Ask me for a quote!
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>> 
> 
> _
> Get free photo software from Windows Live
> http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009
> 

-- 
View this message in context: 
http://www.nabble.com/maven-eclipse-plugin-and-wtp-tp24808685p24811939.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 and wtp

[Wes Wannemacher]

On Tue, Aug 4, 2009 at 9:56 AM, Martin Gainty wrote:
>
> m2 is the better solution if you need to debug
> curious as to what term CI means?
>

CI = continuous integration... Things like Hudson, Bamboo, Continuum.

-Wes

-- 
Wes Wannemacher

Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!

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

RE: maven eclipse plugin and wtp

[Martin Gainty]

m2 is the better solution if you need to debug
curious as to what term CI means?

Martin 
Ask about "software clunker upgrade program"
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




> Date: Tue, 4 Aug 2009 09:39:17 -0400
> Subject: Re: maven eclipse plugin and wtp
> From: w...@wantii.com
> To: users@maven.apache.org
> 
> On Tue, Aug 4, 2009 at 9:27 AM,
> massive.boisson wrote:
> >
> > Hi, I have a maven project (that is web project by its nature) and I want to
> > run it in eclipse as WTP project.
> >
> > I found command (on
> > http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html):
> > mvn -Dwtpversion=R7 eclipse:eclipse
> > Where wtpversion can be R7, 1.0, 1.5, 2.0 or none (default).
> >
> >
> > As current wtp version is 3.1, can I use
> > mvn -Dwtpversion=3.1 eclipse:eclipse
> >
> >
> > Or is there a new or prefered way to do this?
> >
> >
> 
> When you specify the WTP version, you are telling the plugin which
> type of configuration to generate. Eclipse has the ability to "import"
> from older versions, so even though WTP version 2.0 is from '08, it
> shouldn't hurt to use 2.0, then let eclipse import it.
> 
> At the same time, when using the eclipse plugin, you should ask
> yourself which you want to depend on more, eclipse or maven? Eclipse
> and maven both handle many similar tasks, but if you use the eclipse
> functionality, you are locked into eclipse... There are many eclipse
> tools that are helpful, but for building and testing, I prefer to
> leave it to maven. That being the case, what does WTP give you that is
> most important? IMO, it's the ability to run your web-app right from
> the IDE... You can install a tomcat runtime right in WTP and tell
> eclipse to run your web-app in it. If this is the feature you are
> looking for, then I would say that you could do one better and use the
> maven-tomcat-plugin to get the same functionality.
> 
> Instead of using the maven-eclipse-plugin to generate eclipse
> configuration files, try using the m2eclipse eclipse plugin to have
> eclipse become more "maven-aware". Then, you can create an eclipse run
> configuration that launches 'mvn tomcat:run'. You will have the
> ability to debug your web-app using the eclipse debugger. In addition,
> you will also have the nifty pom editory that comes with m2eclipse.
> This will leave you with a project that is more portable across IDEs,
> in case someone on your team later decides to use something other than
> eclipse. In addition, your build/test process can be run in a CI
> environment like hudson.
> 
> -Wes
> 
> -- 
> Wes Wannemacher
> 
> Head Engineer, WanTii, Inc.
> Need Training? Struts, Spring, Maven, Tomcat...
> Ask me for a quote!
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 

_
Get free photo software from Windows Live
http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009

Re: maven eclipse plugin and wtp

[Wes Wannemacher]

On Tue, Aug 4, 2009 at 9:27 AM,
massive.boisson wrote:
>
> Hi, I have a maven project (that is web project by its nature) and I want to
> run it in eclipse as WTP project.
>
> I found command (on
> http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html):
> mvn -Dwtpversion=R7 eclipse:eclipse
> Where wtpversion can be R7, 1.0, 1.5, 2.0 or none (default).
>
>
> As current wtp version is 3.1, can I use
> mvn -Dwtpversion=3.1 eclipse:eclipse
>
>
> Or is there a new or prefered way to do this?
>
>

When you specify the WTP version, you are telling the plugin which
type of configuration to generate. Eclipse has the ability to "import"
from older versions, so even though WTP version 2.0 is from '08, it
shouldn't hurt to use 2.0, then let eclipse import it.

At the same time, when using the eclipse plugin, you should ask
yourself which you want to depend on more, eclipse or maven? Eclipse
and maven both handle many similar tasks, but if you use the eclipse
functionality, you are locked into eclipse... There are many eclipse
tools that are helpful, but for building and testing, I prefer to
leave it to maven. That being the case, what does WTP give you that is
most important? IMO, it's the ability to run your web-app right from
the IDE... You can install a tomcat runtime right in WTP and tell
eclipse to run your web-app in it. If this is the feature you are
looking for, then I would say that you could do one better and use the
maven-tomcat-plugin to get the same functionality.

Instead of using the maven-eclipse-plugin to generate eclipse
configuration files, try using the m2eclipse eclipse plugin to have
eclipse become more "maven-aware". Then, you can create an eclipse run
configuration that launches 'mvn tomcat:run'. You will have the
ability to debug your web-app using the eclipse debugger. In addition,
you will also have the nifty pom editory that comes with m2eclipse.
This will leave you with a project that is more portable across IDEs,
in case someone on your team later decides to use something other than
eclipse. In addition, your build/test process can be run in a CI
environment like hudson.

-Wes

-- 
Wes Wannemacher

Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!

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

Re: maven eclipse plugin and wtp

[massive.boisson]

Sorry that came out wrong, I know I cannot do -Dwtpversion=3.1, but I am
wondering what are my alternatives.

It seems there should be a new new way to do this, and I cannot find it.

Or maybe 2.0 works as good as 3.1


Thanks

-MB


massive.boisson wrote:
> 
> As current wtp version is 3.1, can I use 
> mvn -Dwtpversion=3.1 eclipse:eclipse
> 

-- 
View this message in context: 
http://www.nabble.com/maven-eclipse-plugin-and-wtp-tp24808685p24808760.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: how to specify custom compiler settings?

[Barrie Treloar]

On Wed, Jul 15, 2009 at 12:17 PM, Dirk Olmes wrote:
> Hi,
>
> I'm trying to nail down some compiler settings for a project. Those are
> stored in .settings/org.eclipse.jdt.core.prefs, e.g.
>
> org.eclipse.jdt.core.compiler.problem.autoboxing=warning
>
> A quick look in the m-e-p's source makes me think that there is
> currently no easy way to augment the .settings file with custom
> settings. Is there?

There is no way to augment but you can manually make the changes after
the file has been generated.

m-e-p will read in the current preferences and anything that m-e-p
does not modify are preserved.

See EclipseSettingsWriter.java - write() - line 91+

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

Re: [maven-eclipse-plugin]: MECLIPSE-548 requires attention

[Arnaud HERITIER]

We asked several times to test the 2.7-SNAPSHOT before the release and we
had no feedback about this issue which wasn't solved. Thus I don't know if
it impacts so many projects.We'll try to fix it in 2.8, but I don't know in
how many weeks/monthes, we'll be able to do it

Cheers


Cheers,

Arnaud

# Arnaud Héritier
# http://blog.aheritier.net


On Tue, Jun 16, 2009 at 8:08 AM, Ben Caradoc-Davies
 wrote:

> MECLIPSE-548 is a showstopper for many projects that would otherwise use
> maven-eclipse-plugin. I suspect many projects using the plugin are now
> pinned to 2.5. This issue is marked as Critical priority, has six votes
> and four watchers. Can anyone take at look at this issue? If you do not
> intend to address this issue, or cannot address it at this time, please
> comment on it to explain the situation.
>
> Kind regards,
> Ben.
>
>
>  Original Message 
> Subject: [jira] Commented: (MECLIPSE-548) MECLIPSE-442 should be
> reverted. Classpath container entries should come before 3rd party jars
> in .classpath
> Date: Tue, 16 Jun 2009 01:25:42 +0800
> From: Joe Freeman (JIRA) 
> To: Caradoc-Davies, Ben (E&M, Kensington) 
>
>
>[
>
> http://jira.codehaus.org/browse/MECLIPSE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180352#action_180352
> ]
>
> Joe Freeman commented on MECLIPSE-548:
> --
>
> How many votes does this have to have before it makes a release.
> Version 2.7 just came out and it still has the same incorrect classpath
> ordering for the JDK/JRE :-(
>
>  MECLIPSE-442 should be reverted. Classpath container entries should come
>> before 3rd party jars in .classpath
>>
>> 
>>
>>Key: MECLIPSE-548
>>URL: http://jira.codehaus.org/browse/MECLIPSE-548
>>Project: Maven 2.x Eclipse Plugin
>> Issue Type: Bug
>> Components: Core : Dependencies resolution and build path
>> (.classpath)
>>   Affects Versions: 2.6
>>Environment: all
>>   Reporter: Joe Freeman
>>   Priority: Critical
>>
>> A patch was accepted into maven 2.6 as part of jira  MECLIPSE-442
>>  that configures eclipse to compile with a different order than the jre will
>> load with.  This patch moved the container classpaths to the end of the
>> classpath in eclipse.  This behavior is incorrect.  The JRE's jar files
>> should come before any 3rd party libraries on the classpath because those
>> classes will be loaded before any of the 3rd party jars and because the
>> JRE's classes cannot be overridden by classes in a 3rd party jar.  I
>> understand why MECLIPSE-442 wanted to reverse the order so they could pick
>> up the properties files. The best way to do this was to create properties
>> files in the indvidual projects if he needed at run time or in the
>> test/resources directory if it was only needed for unit  testing. project
>> resources come before everything in eclipse
>> With this patch added to maven 2.6, we have a situation where eclipse
>> tells us we have compiler error when maven command line compilations do not.
>>
>>
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://jira.codehaus.org/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
>
> --
> Ben Caradoc-Davies 
> Software Engineer, CSIRO Exploration and Mining
> Australian Resources Research Centre
> 26 Dick Perry Ave, Kensington WA 6151, Australia
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Barrie Treloar]

Ok a 2.7 is being built and voting has started.

If you would like to participate in testing please see "Guide to
testing staged releases":
http://maven.apache.org/guides/development/guide-testing-releases.html

And the nabble archive of the vote at
http://www.nabble.com/-VOTE--Release-Maven-Eclipse-plugin-version-2.7-to23845855.html

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

We also tested it with an AspectJ project, and that works as well.

Martijn

On Fri, May 29, 2009 at 10:09 AM, Martijn Dashorst
 wrote:
> Works great! Thanks Barrie!!!
>
> Here's the log entry for my run:
>
> macbookpro:myproject dashorst$ mvn eclipse:eclipse
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'eclipse'.
> Downloading: 
> http://repository/artifactory/repo/org/apache/maven/plugins/maven-eclipse-plugin/2.7-SNAPSHOT/maven-eclipse-plugin-2.7-20090529.071922-5.pom
> 9K downloaded
> Downloading: 
> http://repository/artifactory/repo/org/apache/maven/plugins/maven-eclipse-plugin/2.7-SNAPSHOT/maven-eclipse-plugin-2.7-20090529.071922-5.jar
> 203K downloaded
> [INFO] 
> 
> [INFO] Building quickstart
> [INFO]    task-segment: [eclipse:eclipse]
> [INFO] 
> 
> [INFO] Preparing eclipse:eclipse
> [INFO] snapshot org.mortbay.jetty:maven-jetty-plugin:6.1-SNAPSHOT:
> checking for updates from topicus-plugin-snapshot-repository
> [INFO] snapshot org.mortbay.jetty:project:6.1-SNAPSHOT: checking for
> updates from topicus-plugin-snapshot-repository
> [INFO] No goals needed for project - skipping
> [WARNING] Attempting to build MavenProject instance for Artifact
> (org.apache.maven.plugins:maven-eclipse-plugin:2.7-20090529.071922-5)
> of type: maven-plugin; constructing POM artifact instead.
> [INFO] [eclipse:eclipse]
> [INFO] Using Eclipse Workspace: /Workspaces/eduarte
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
> [INFO] Adding default classpath container:
> org.eclipse.jdt.launching.JRE_CONTAINER
> [INFO] Resource directory's path matches an existing source directory.
> Resources will be merged with the source directory src/main/java
> [INFO] Resource directory's path matches an existing source directory.
> Resources will be merged with the source directory src/test/java
> [INFO] Not writing settings - defaults suffice
> [INFO] Wrote Eclipse project for "myproject" to /Workspaces/eduarte/myproject.
> [INFO]
>       Javadoc for some artifacts is not available.
>       Please run the same goal with the -DdownloadJavadocs=true
> parameter in order to check remote repositories for javadoc.
>       List of artifacts without a javadoc archive:
>         o junit:junit:3.8.2
>         o log4j:log4j:1.2.14
>         o org.slf4j:slf4j-api:1.4.2
>         o org.mortbay.jetty:jetty:6.1.4
>         o org.mortbay.jetty:jetty-util:6.1.4
>         o org.mortbay.jetty:servlet-api-2.5:6.1.4
>         o org.mortbay.jetty:jetty-management:6.1.4
>         o mx4j:mx4j:3.0.1
>         o mx4j:mx4j-tools:3.0.1
>         o org.slf4j:slf4j-log4j12:1.4.2
>
> [INFO] 
> 
> [INFO] BUILD SUCCESSFUL
> [INFO] 
> 
> [INFO] Total time: 18 seconds
> [INFO] Finished at: Fri May 29 10:06:15 CEST 2009
> [INFO] Final Memory: 9M/16M
> [INFO] 
> 
>
>
> On Fri, May 29, 2009 at 9:20 AM, Arnaud HERITIER  wrote:
>> I just deployed it in the snapshots repo. It's numbered
>> : 2.7-20090529.071922-5Thx for your hard work Barrie.
>> Cheers
>>
>>
>> Arnaud
>>
>>
>> On Fri, May 29, 2009 at 6:05 AM, Barrie Treloar  wrote:
>>
>>> On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
>>>  wrote:
>>> > On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar 
>>> wrote:
>>> >> I went quickly hacking an existing IT test to include the resources
>>> >> definition you provided and some debugging output (as ERROR so I could
>>> >> see it)
>>> >
>>> > Great!
>>> >
>>> >> So src/main/resources is correctly on the resources list.
>>> >> The problem is that the list of directories to parse is a Set and the
>>> >> second addition is returning false to add() but nothing is checking
>>> >> this condition.
>>> >>
>>> >

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

Works great! Thanks Barrie!!!

Here's the log entry for my run:

macbookpro:myproject dashorst$ mvn eclipse:eclipse
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
Downloading: 
http://repository/artifactory/repo/org/apache/maven/plugins/maven-eclipse-plugin/2.7-SNAPSHOT/maven-eclipse-plugin-2.7-20090529.071922-5.pom
9K downloaded
Downloading: 
http://repository/artifactory/repo/org/apache/maven/plugins/maven-eclipse-plugin/2.7-SNAPSHOT/maven-eclipse-plugin-2.7-20090529.071922-5.jar
203K downloaded
[INFO] 
[INFO] Building quickstart
[INFO]task-segment: [eclipse:eclipse]
[INFO] 
[INFO] Preparing eclipse:eclipse
[INFO] snapshot org.mortbay.jetty:maven-jetty-plugin:6.1-SNAPSHOT:
checking for updates from topicus-plugin-snapshot-repository
[INFO] snapshot org.mortbay.jetty:project:6.1-SNAPSHOT: checking for
updates from topicus-plugin-snapshot-repository
[INFO] No goals needed for project - skipping
[WARNING] Attempting to build MavenProject instance for Artifact
(org.apache.maven.plugins:maven-eclipse-plugin:2.7-20090529.071922-5)
of type: maven-plugin; constructing POM artifact instead.
[INFO] [eclipse:eclipse]
[INFO] Using Eclipse Workspace: /Workspaces/eduarte
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
[INFO] Adding default classpath container:
org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Resource directory's path matches an existing source directory.
Resources will be merged with the source directory src/main/java
[INFO] Resource directory's path matches an existing source directory.
Resources will be merged with the source directory src/test/java
[INFO] Not writing settings - defaults suffice
[INFO] Wrote Eclipse project for "myproject" to /Workspaces/eduarte/myproject.
[INFO]
   Javadoc for some artifacts is not available.
   Please run the same goal with the -DdownloadJavadocs=true
parameter in order to check remote repositories for javadoc.
   List of artifacts without a javadoc archive:
 o junit:junit:3.8.2
 o log4j:log4j:1.2.14
 o org.slf4j:slf4j-api:1.4.2
 o org.mortbay.jetty:jetty:6.1.4
 o org.mortbay.jetty:jetty-util:6.1.4
 o org.mortbay.jetty:servlet-api-2.5:6.1.4
 o org.mortbay.jetty:jetty-management:6.1.4
 o mx4j:mx4j:3.0.1
 o mx4j:mx4j-tools:3.0.1
 o org.slf4j:slf4j-log4j12:1.4.2

[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 18 seconds
[INFO] Finished at: Fri May 29 10:06:15 CEST 2009
[INFO] Final Memory: 9M/16M
[INFO] 


On Fri, May 29, 2009 at 9:20 AM, Arnaud HERITIER  wrote:
> I just deployed it in the snapshots repo. It's numbered
> : 2.7-20090529.071922-5Thx for your hard work Barrie.
> Cheers
>
>
> Arnaud
>
>
> On Fri, May 29, 2009 at 6:05 AM, Barrie Treloar  wrote:
>
>> On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
>>  wrote:
>> > On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar 
>> wrote:
>> >> I went quickly hacking an existing IT test to include the resources
>> >> definition you provided and some debugging output (as ERROR so I could
>> >> see it)
>> >
>> > Great!
>> >
>> >> So src/main/resources is correctly on the resources list.
>> >> The problem is that the list of directories to parse is a Set and the
>> >> second addition is returning false to add() but nothing is checking
>> >> this condition.
>> >>
>> >> Now I need to work out how to handle the collision
>> >
>> > Let me know when there's a new snapshot to try.
>>
>> http://jira.codehaus.org/browse/MECLIPSE-551 has code committed to fix
>> this problem with a suitable IT as well.
>>
>> But I can't create snapshots at work.
>>
>> You might want to pull down the source and 

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Arnaud HERITIER]

I just deployed it in the snapshots repo. It's numbered
: 2.7-20090529.071922-5Thx for your hard work Barrie.
Cheers


Arnaud


On Fri, May 29, 2009 at 6:05 AM, Barrie Treloar  wrote:

> On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
>  wrote:
> > On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar 
> wrote:
> >> I went quickly hacking an existing IT test to include the resources
> >> definition you provided and some debugging output (as ERROR so I could
> >> see it)
> >
> > Great!
> >
> >> So src/main/resources is correctly on the resources list.
> >> The problem is that the list of directories to parse is a Set and the
> >> second addition is returning false to add() but nothing is checking
> >> this condition.
> >>
> >> Now I need to work out how to handle the collision
> >
> > Let me know when there's a new snapshot to try.
>
> http://jira.codehaus.org/browse/MECLIPSE-551 has code committed to fix
> this problem with a suitable IT as well.
>
> But I can't create snapshots at work.
>
> You might want to pull down the source and build a snapshot yourself.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Barrie Treloar]

On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
 wrote:
> On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar  wrote:
>> I went quickly hacking an existing IT test to include the resources
>> definition you provided and some debugging output (as ERROR so I could
>> see it)
>
> Great!
>
>> So src/main/resources is correctly on the resources list.
>> The problem is that the list of directories to parse is a Set and the
>> second addition is returning false to add() but nothing is checking
>> this condition.
>>
>> Now I need to work out how to handle the collision
>
> Let me know when there's a new snapshot to try.

http://jira.codehaus.org/browse/MECLIPSE-551 has code committed to fix
this problem with a suitable IT as well.

But I can't create snapshots at work.

You might want to pull down the source and build a snapshot yourself.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar  wrote:
> I went quickly hacking an existing IT test to include the resources
> definition you provided and some debugging output (as ERROR so I could
> see it)

Great!

> So src/main/resources is correctly on the resources list.
> The problem is that the list of directories to parse is a Set and the
> second addition is returning false to add() but nothing is checking
> this condition.
>
> Now I need to work out how to handle the collision

Let me know when there's a new snapshot to try.

Martijn


-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Barrie Treloar]

On Wed, May 27, 2009 at 5:17 PM, Martijn Dashorst
 wrote:
> http://wicket.apache.org/quickstart.html
>
> Select for example Wicket 1.3.6
>

I went quickly hacking an existing IT test to include the resources
definition you provided and some debugging output (as ERROR so I could
see it)

[ERROR] Resources = [Resource {targetPath: null, filtering: false,
FileSet {directory:
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\project-53-MECLIPSE-551\src\main\java,
PatternSet [includes: {**/*}, excludes: {**/*.java, **/*.sample}]}}]
[DEBUG] Processing resource dir:
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\project-53-MECLIPSE-551\src\main\java
[DEBUG] Making relative and fixing separator: {
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\project-53-MECLIPSE-551,
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\project-53-MECLIPSE-551\target\classes,
false }.
[DEBUG] Adding eclipse source dir: { src/main/java, target/classes,
true, false, **/*, **/*.java|**/*.sample|**/*.java }.
[ERROR] Failed to add eclipse source dir: src/main/java as it already
exists in the set.

So src/main/resources is correctly on the resources list.
The problem is that the list of directories to parse is a Set and the
second addition is returning false to add() but nothing is checking
this condition.

Now I need to work out how to handle the collision

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

http://wicket.apache.org/quickstart.html

Select for example Wicket 1.3.6

Martijn

On Wed, May 27, 2009 at 8:44 AM, Barrie Treloar  wrote:
> On Wed, May 27, 2009 at 3:58 PM, Martijn Dashorst
>  wrote:
>> With Wicket, we have Page.html, Page.properties, Page.properties_ru,
>> Page.js, Page.css, Page.younameit next to the Java files. This has
>> been the official way to work with Wicket, and was 100% supported by
>> maven by defining src/main/java as a resources element in our poms.
>> 443 breaks this. And no, we don't take put them in src/main/resources
>> as an answer.
>
> Can you attach to http://jira.codehaus.org/browse/MECLIPSE-551 a test
> project that is configured the way you expect.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Barrie Treloar]

On Wed, May 27, 2009 at 3:58 PM, Martijn Dashorst
 wrote:
> With Wicket, we have Page.html, Page.properties, Page.properties_ru,
> Page.js, Page.css, Page.younameit next to the Java files. This has
> been the official way to work with Wicket, and was 100% supported by
> maven by defining src/main/java as a resources element in our poms.
> 443 breaks this. And no, we don't take put them in src/main/resources
> as an answer.

Can you attach to http://jira.codehaus.org/browse/MECLIPSE-551 a test
project that is configured the way you expect.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

On Wed, May 27, 2009 at 1:17 AM, Barrie Treloar  wrote:
> On Tue, May 26, 2009 at 11:03 PM, Martijn Dashorst
>  wrote:
>> In my opinion  MECLIPSE-443 is a very bad idea. Should every plugin be
>> configured so that the resources available in src/main/java are
>> treated as classpath entries?
>
> It was my understanding that if you had resources in src/main/java
> that Maven would not package these.
> They must be in src/main/resources.

Unless you define src/main/java inside a  element as I
already mentioned. This should be the canonical place for defining
such project descriptions, *NOT* in every frakking plugin that doesn't
want to read the pom.

> What is wrong with configuring your ide to behave how Maven behaves?
> This will stop you having moments where it works in Eclipse but Maven fails.

Because the plugin doesn't configure my IDE as maven behaves: see above...

>> According to me the eclipse plugin
>> should take the  part of the pom into account, rather than
>> invent yet another way of specifying where resources live.
>
> The plugin takes it diirectly from the in memory copy of the pom via
> project.getBuild().getResources() as can be seen in the code below.
> It does not invent another way of specifying where resources live.

Then why doesn't it work? I don't care about how it is implemented in
Java code. Just either roll back 443, or implement it correctly.

>> This "fix" break so many existing builds and archetypes it is not fun
>> anymore. I for one don't like being the helpdesk for maven on the
>> Wicket user list.
>
> Can you be specific about what breaks?
> Which files, why they are in src/main/java and not somewhere else, etc.

With Wicket, we have Page.html, Page.properties, Page.properties_ru,
Page.js, Page.css, Page.younameit next to the Java files. This has
been the official way to work with Wicket, and was 100% supported by
maven by defining src/main/java as a resources element in our poms.
443 breaks this. And no, we don't take put them in src/main/resources
as an answer.

> For other edge cases 2.7 added
> http://jira.codehaus.org/browse/MECLIPSE-104, which allows you to
> configure what files can be included/excluded from source directories.

I'd qualify thousands of Wicket users as hardly an edge case thank you
very much/

> Without specifics it is impossible to fix your complaint.

I've complained about this earlier in the maven-eclipse-plugin-2.6
thread, together with specifics.

I don't want to have to configure my resources with every plugin that
is going to be part of the build. That is not the Maven way. If the
compiler plugin can copy all my resources by reading the 
part of my pom, why should the maven-eclipse-plugin behave any
different?

Martijn

-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[ari.meyer]

Hi Arnaud,

Sorry, my bad -- missed reading those changes.  I re-tested it and it works
fine with the inclusions setting, but I agree with Martijn that MECLIPSE-443
is not the best way to go.

Thanks again,
Ari


Arnaud HERITIER wrote:
> 
> Hi Ari,
> Thanks for your feedback.
> 
> Did you follow this doc to setup your eclipse project :
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
> ??
> 
> Arnaud
> 
> 
> On Tue, May 26, 2009 at 2:29 AM, ari.meyer  wrote:
> 
>>
>> Hi Arnaud,
>>
>> I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and I'm
>> getting the same error when using Wicket:
>>
>> org.apache.wicket.markup.MarkupNotFoundException: Markup not found.
>>
>> Reverting again back to 2.5.1, everything worked properly.
>>
>> Best regards,
>> Ari
>>
>>
>> Arnaud HERITIER wrote:
>> >
>> > Hi Community,
>> >   The recent release 2.6 of the maven-eclipse-plugin created many
>> problems
>> > for all of those who had/wanted to store non-java files under
>> src/*/java
>> > (which is required for wicket, ajdt, and probably others usecases).
>> >   Even we have many integration tests in this plugin we didn't notice
>> this
>> > issue because our testcases allow us to check that generated
>> configuration
>> > files aren't evolving and that we are able to import and use a project
>> in
>> > eclipse (too heavy to do).
>> >
>> >   To fix this issue we (Barrie to be honest) improved the plugin to
>> allow
>> > the usage of includes and excludes. :
>> > http://jira.codehaus.org/browse/MECLIPSE-104
>> >   The documentation of these feature is here :
>> >
>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
>> > There are many broken links on the site and I don't know why. I'll
>> > investigate later.
>> > Others pages are the same in
>> > http://maven.apache.org/plugins/maven-eclipse-plugin/
>> > For AJDT project you can have a look at this page :
>> > http://maven.apache.org/plugins/maven-eclipse-plugin-
>> > 2.7-SNAPSHOT/examples/ajdt-projects.html
>> >
>> > To test the plugin you have to add in your project or in your settings
>> > this
>> > repository :
>> > https://repository.apache.org/content/repositories/snapshots/
>> > (be careful to the https protocol)
>> > The last version I deployed is : 2.7-20090416.000603-3
>> >
>> > Please, test it and give us your feedback. If it is positive this week,
>> > we'll launch the release process the next one.
>> >
>> > cheers,
>> >
>> > --
>> > Arnaud
>> >
>> >
>>
>> --
>> View this message in context:
>> http://n2.nabble.com/-maven-eclipse-plugin--We-need-your-help-to-test-the-future-2.7-tp2646905p2972277.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
>>
>>
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/-maven-eclipse-plugin--We-need-your-help-to-test-the-future-2.7-tp2646905p2979309.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] We need your help to test the future 2.7

[Dirk Olmes]

Martijn Dashorst wrote:
> Yes, and I've been burned by m2eclipse, and haven't heard loving
> reports from co-workers about q4e either. Not installing any of them
> anytime soon.

The same here. I'd rather maintain a fork of the m-e-p that does exactly
what I want than installing one of the eclipse plugins.

-dirk

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Kalle Korhonen]

Well, here's one for q4e. Ever since they implemented the incremental
builder, I haven't had any issues with it and it's been fast enough for me
(got 30 or so linked Eclipse projects on my workspace).

Kalle

On Tue, May 26, 2009 at 7:35 AM, Martijn Dashorst <
martijn.dasho...@gmail.com> wrote:

> Yes, and I've been burned by m2eclipse, and haven't heard loving
> reports from co-workers about q4e either. Not installing any of them
> anytime soon.
>
> Martijn
>
> On Tue, May 26, 2009 at 4:09 PM, Arnaud HERITIER 
> wrote:
> > Did you try to use m2eclipse or q4e ?They'll be the future.
> >
> > maven-eclipse-plugin will probably die under its own weight. There are
> too
> > many use cases and testing coverage isn't conclusive because we only
> checks
> > what we generate and not that we are able to import/use it in eclipse .
> We
> > have really few developpers involved in it and the darkness of the
> eclipse
> > configuration doesn't help. Now many settings are stored in files.
> >
> > I'll try to have a look at MECLIPSE-443 but I cannot say when it will be.
> I
> > think it sould be better for you to be able to use plugins like m2eclipse
> or
> > q4e.
> >
> > Arnaud
> >
> > On Tue, May 26, 2009 at 3:33 PM, Martijn Dashorst <
> > martijn.dasho...@gmail.com> wrote:
> >
> >> In my opinion  MECLIPSE-443 is a very bad idea. Should every plugin be
> >> configured so that the resources available in src/main/java are
> >> treated as classpath entries? According to me the eclipse plugin
> >> should take the  part of the pom into account, rather than
> >> invent yet another way of specifying where resources live.
> >>
> >> This "fix" break so many existing builds and archetypes it is not fun
> >> anymore. I for one don't like being the helpdesk for maven on the
> >> Wicket user list.
> >>
> >> Martijn
> >>
> >> On Tue, May 26, 2009 at 9:21 AM, Arnaud HERITIER 
> >> wrote:
> >> > Hi Ari,
> >> > Thanks for your feedback.
> >> >
> >> > Did you follow this doc to setup your eclipse project :
> >> >
> >>
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
> >> > ??
> >> >
> >> > Arnaud
> >> >
> >> >
> >> > On Tue, May 26, 2009 at 2:29 AM, ari.meyer 
> wrote:
> >> >
> >> >>
> >> >> Hi Arnaud,
> >> >>
> >> >> I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and
> >> I'm
> >> >> getting the same error when using Wicket:
> >> >>
> >> >> org.apache.wicket.markup.MarkupNotFoundException: Markup not found.
> >> >>
> >> >> Reverting again back to 2.5.1, everything worked properly.
> >> >>
> >> >> Best regards,
> >> >> Ari
> >> >>
> >> >>
> >> >> Arnaud HERITIER wrote:
> >> >> >
> >> >> > Hi Community,
> >> >> >   The recent release 2.6 of the maven-eclipse-plugin created many
> >> >> problems
> >> >> > for all of those who had/wanted to store non-java files under
> >> src/*/java
> >> >> > (which is required for wicket, ajdt, and probably others usecases).
> >> >> >   Even we have many integration tests in this plugin we didn't
> notice
> >> >> this
> >> >> > issue because our testcases allow us to check that generated
> >> >> configuration
> >> >> > files aren't evolving and that we are able to import and use a
> project
> >> in
> >> >> > eclipse (too heavy to do).
> >> >> >
> >> >> >   To fix this issue we (Barrie to be honest) improved the plugin to
> >> allow
> >> >> > the usage of includes and excludes. :
> >> >> > http://jira.codehaus.org/browse/MECLIPSE-104
> >> >> >   The documentation of these feature is here :
> >> >> >
> >> >>
> >>
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
> >> >> > There are many broken links on the site and I don't know why. I'll
> >> >> > investigate later.
> >> >> > Others pages are the same in
> >> >> > http://maven.apache.org/plugins/maven-eclipse-plugin/
> >> >> > For AJDT project you can have a look at this page :
> >> >> > http://maven.apache.org/plugins/maven-eclipse-plugin-
> >> >> > 2.7-SNAPSHOT/examples/ajdt-projects.html
> >> >> >
> >> >> > To test the plugin you have to add in your project or in your
> settings
> >> >> > this
> >> >> > repository :
> >> >> > https://repository.apache.org/content/repositories/snapshots/
> >> >> > (be careful to the https protocol)
> >> >> > The last version I deployed is : 2.7-20090416.000603-3
> >> >> >
> >> >> > Please, test it and give us your feedback. If it is positive this
> >> week,
> >> >> > we'll launch the release process the next one.
> >> >> >
> >> >> > cheers,
> >> >> >
> >> >> > --
> >> >> > Arnaud
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://n2.nabble.com/-maven-eclipse-plugin--We-need-your-help-to-test-the-future-2.7-tp2646905p2972277.html
> >> >> Sent from the maven users mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >> -
> >> >

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Barrie Treloar]

On Tue, May 26, 2009 at 11:03 PM, Martijn Dashorst
 wrote:
> In my opinion  MECLIPSE-443 is a very bad idea. Should every plugin be
> configured so that the resources available in src/main/java are
> treated as classpath entries?

It was my understanding that if you had resources in src/main/java
that Maven would not package these.
They must be in src/main/resources.

What is wrong with configuring your ide to behave how Maven behaves?
This will stop you having moments where it works in Eclipse but Maven fails.

> According to me the eclipse plugin
> should take the  part of the pom into account, rather than
> invent yet another way of specifying where resources live.

The plugin takes it diirectly from the in memory copy of the pom via
project.getBuild().getResources() as can be seen in the code below.
It does not invent another way of specifying where resources live.

>From EclipsePlugin.buildDirectoryList():
extractResourceDirs( mainDirectories,
project.getBuild().getResources(), basedir, projectBaseDir, false,
 mainOutput );

> This "fix" break so many existing builds and archetypes it is not fun
> anymore. I for one don't like being the helpdesk for maven on the
> Wicket user list.

Can you be specific about what breaks?
Which files, why they are in src/main/java and not somewhere else, etc.

We are aware that this has caused pain, especially for AJDT, which is
why 2.7 automatically includes *.aj on the source directories. See
http://jira.codehaus.org/browse/MECLIPSE-538

For other edge cases 2.7 added
http://jira.codehaus.org/browse/MECLIPSE-104, which allows you to
configure what files can be included/excluded from source directories.

Without specifics it is impossible to fix your complaint.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

Yes, and I've been burned by m2eclipse, and haven't heard loving
reports from co-workers about q4e either. Not installing any of them
anytime soon.

Martijn

On Tue, May 26, 2009 at 4:09 PM, Arnaud HERITIER  wrote:
> Did you try to use m2eclipse or q4e ?They'll be the future.
>
> maven-eclipse-plugin will probably die under its own weight. There are too
> many use cases and testing coverage isn't conclusive because we only checks
> what we generate and not that we are able to import/use it in eclipse . We
> have really few developpers involved in it and the darkness of the eclipse
> configuration doesn't help. Now many settings are stored in files.
>
> I'll try to have a look at MECLIPSE-443 but I cannot say when it will be. I
> think it sould be better for you to be able to use plugins like m2eclipse or
> q4e.
>
> Arnaud
>
> On Tue, May 26, 2009 at 3:33 PM, Martijn Dashorst <
> martijn.dasho...@gmail.com> wrote:
>
>> In my opinion  MECLIPSE-443 is a very bad idea. Should every plugin be
>> configured so that the resources available in src/main/java are
>> treated as classpath entries? According to me the eclipse plugin
>> should take the  part of the pom into account, rather than
>> invent yet another way of specifying where resources live.
>>
>> This "fix" break so many existing builds and archetypes it is not fun
>> anymore. I for one don't like being the helpdesk for maven on the
>> Wicket user list.
>>
>> Martijn
>>
>> On Tue, May 26, 2009 at 9:21 AM, Arnaud HERITIER 
>> wrote:
>> > Hi Ari,
>> > Thanks for your feedback.
>> >
>> > Did you follow this doc to setup your eclipse project :
>> >
>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
>> > ??
>> >
>> > Arnaud
>> >
>> >
>> > On Tue, May 26, 2009 at 2:29 AM, ari.meyer  wrote:
>> >
>> >>
>> >> Hi Arnaud,
>> >>
>> >> I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and
>> I'm
>> >> getting the same error when using Wicket:
>> >>
>> >> org.apache.wicket.markup.MarkupNotFoundException: Markup not found.
>> >>
>> >> Reverting again back to 2.5.1, everything worked properly.
>> >>
>> >> Best regards,
>> >> Ari
>> >>
>> >>
>> >> Arnaud HERITIER wrote:
>> >> >
>> >> > Hi Community,
>> >> >   The recent release 2.6 of the maven-eclipse-plugin created many
>> >> problems
>> >> > for all of those who had/wanted to store non-java files under
>> src/*/java
>> >> > (which is required for wicket, ajdt, and probably others usecases).
>> >> >   Even we have many integration tests in this plugin we didn't notice
>> >> this
>> >> > issue because our testcases allow us to check that generated
>> >> configuration
>> >> > files aren't evolving and that we are able to import and use a project
>> in
>> >> > eclipse (too heavy to do).
>> >> >
>> >> >   To fix this issue we (Barrie to be honest) improved the plugin to
>> allow
>> >> > the usage of includes and excludes. :
>> >> > http://jira.codehaus.org/browse/MECLIPSE-104
>> >> >   The documentation of these feature is here :
>> >> >
>> >>
>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
>> >> > There are many broken links on the site and I don't know why. I'll
>> >> > investigate later.
>> >> > Others pages are the same in
>> >> > http://maven.apache.org/plugins/maven-eclipse-plugin/
>> >> > For AJDT project you can have a look at this page :
>> >> > http://maven.apache.org/plugins/maven-eclipse-plugin-
>> >> > 2.7-SNAPSHOT/examples/ajdt-projects.html
>> >> >
>> >> > To test the plugin you have to add in your project or in your settings
>> >> > this
>> >> > repository :
>> >> > https://repository.apache.org/content/repositories/snapshots/
>> >> > (be careful to the https protocol)
>> >> > The last version I deployed is : 2.7-20090416.000603-3
>> >> >
>> >> > Please, test it and give us your feedback. If it is positive this
>> week,
>> >> > we'll launch the release process the next one.
>> >> >
>> >> > cheers,
>> >> >
>> >> > --
>> >> > Arnaud
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://n2.nabble.com/-maven-eclipse-plugin--We-need-your-help-to-test-the-future-2.7-tp2646905p2972277.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
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.3.5 is released
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>



-- 
Become a Wicket expert,

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Arnaud HERITIER]

Did you try to use m2eclipse or q4e ?They'll be the future.

maven-eclipse-plugin will probably die under its own weight. There are too
many use cases and testing coverage isn't conclusive because we only checks
what we generate and not that we are able to import/use it in eclipse . We
have really few developpers involved in it and the darkness of the eclipse
configuration doesn't help. Now many settings are stored in files.

I'll try to have a look at MECLIPSE-443 but I cannot say when it will be. I
think it sould be better for you to be able to use plugins like m2eclipse or
q4e.

Arnaud

On Tue, May 26, 2009 at 3:33 PM, Martijn Dashorst <
martijn.dasho...@gmail.com> wrote:

> In my opinion  MECLIPSE-443 is a very bad idea. Should every plugin be
> configured so that the resources available in src/main/java are
> treated as classpath entries? According to me the eclipse plugin
> should take the  part of the pom into account, rather than
> invent yet another way of specifying where resources live.
>
> This "fix" break so many existing builds and archetypes it is not fun
> anymore. I for one don't like being the helpdesk for maven on the
> Wicket user list.
>
> Martijn
>
> On Tue, May 26, 2009 at 9:21 AM, Arnaud HERITIER 
> wrote:
> > Hi Ari,
> > Thanks for your feedback.
> >
> > Did you follow this doc to setup your eclipse project :
> >
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
> > ??
> >
> > Arnaud
> >
> >
> > On Tue, May 26, 2009 at 2:29 AM, ari.meyer  wrote:
> >
> >>
> >> Hi Arnaud,
> >>
> >> I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and
> I'm
> >> getting the same error when using Wicket:
> >>
> >> org.apache.wicket.markup.MarkupNotFoundException: Markup not found.
> >>
> >> Reverting again back to 2.5.1, everything worked properly.
> >>
> >> Best regards,
> >> Ari
> >>
> >>
> >> Arnaud HERITIER wrote:
> >> >
> >> > Hi Community,
> >> >   The recent release 2.6 of the maven-eclipse-plugin created many
> >> problems
> >> > for all of those who had/wanted to store non-java files under
> src/*/java
> >> > (which is required for wicket, ajdt, and probably others usecases).
> >> >   Even we have many integration tests in this plugin we didn't notice
> >> this
> >> > issue because our testcases allow us to check that generated
> >> configuration
> >> > files aren't evolving and that we are able to import and use a project
> in
> >> > eclipse (too heavy to do).
> >> >
> >> >   To fix this issue we (Barrie to be honest) improved the plugin to
> allow
> >> > the usage of includes and excludes. :
> >> > http://jira.codehaus.org/browse/MECLIPSE-104
> >> >   The documentation of these feature is here :
> >> >
> >>
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
> >> > There are many broken links on the site and I don't know why. I'll
> >> > investigate later.
> >> > Others pages are the same in
> >> > http://maven.apache.org/plugins/maven-eclipse-plugin/
> >> > For AJDT project you can have a look at this page :
> >> > http://maven.apache.org/plugins/maven-eclipse-plugin-
> >> > 2.7-SNAPSHOT/examples/ajdt-projects.html
> >> >
> >> > To test the plugin you have to add in your project or in your settings
> >> > this
> >> > repository :
> >> > https://repository.apache.org/content/repositories/snapshots/
> >> > (be careful to the https protocol)
> >> > The last version I deployed is : 2.7-20090416.000603-3
> >> >
> >> > Please, test it and give us your feedback. If it is positive this
> week,
> >> > we'll launch the release process the next one.
> >> >
> >> > cheers,
> >> >
> >> > --
> >> > Arnaud
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://n2.nabble.com/-maven-eclipse-plugin--We-need-your-help-to-test-the-future-2.7-tp2646905p2972277.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
> >>
> >>
> >
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.5 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

In my opinion  MECLIPSE-443 is a very bad idea. Should every plugin be
configured so that the resources available in src/main/java are
treated as classpath entries? According to me the eclipse plugin
should take the  part of the pom into account, rather than
invent yet another way of specifying where resources live.

This "fix" break so many existing builds and archetypes it is not fun
anymore. I for one don't like being the helpdesk for maven on the
Wicket user list.

Martijn

On Tue, May 26, 2009 at 9:21 AM, Arnaud HERITIER  wrote:
> Hi Ari,
> Thanks for your feedback.
>
> Did you follow this doc to setup your eclipse project :
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
> ??
>
> Arnaud
>
>
> On Tue, May 26, 2009 at 2:29 AM, ari.meyer  wrote:
>
>>
>> Hi Arnaud,
>>
>> I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and I'm
>> getting the same error when using Wicket:
>>
>> org.apache.wicket.markup.MarkupNotFoundException: Markup not found.
>>
>> Reverting again back to 2.5.1, everything worked properly.
>>
>> Best regards,
>> Ari
>>
>>
>> Arnaud HERITIER wrote:
>> >
>> > Hi Community,
>> >   The recent release 2.6 of the maven-eclipse-plugin created many
>> problems
>> > for all of those who had/wanted to store non-java files under src/*/java
>> > (which is required for wicket, ajdt, and probably others usecases).
>> >   Even we have many integration tests in this plugin we didn't notice
>> this
>> > issue because our testcases allow us to check that generated
>> configuration
>> > files aren't evolving and that we are able to import and use a project in
>> > eclipse (too heavy to do).
>> >
>> >   To fix this issue we (Barrie to be honest) improved the plugin to allow
>> > the usage of includes and excludes. :
>> > http://jira.codehaus.org/browse/MECLIPSE-104
>> >   The documentation of these feature is here :
>> >
>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
>> > There are many broken links on the site and I don't know why. I'll
>> > investigate later.
>> > Others pages are the same in
>> > http://maven.apache.org/plugins/maven-eclipse-plugin/
>> > For AJDT project you can have a look at this page :
>> > http://maven.apache.org/plugins/maven-eclipse-plugin-
>> > 2.7-SNAPSHOT/examples/ajdt-projects.html
>> >
>> > To test the plugin you have to add in your project or in your settings
>> > this
>> > repository :
>> > https://repository.apache.org/content/repositories/snapshots/
>> > (be careful to the https protocol)
>> > The last version I deployed is : 2.7-20090416.000603-3
>> >
>> > Please, test it and give us your feedback. If it is positive this week,
>> > we'll launch the release process the next one.
>> >
>> > cheers,
>> >
>> > --
>> > Arnaud
>> >
>> >
>>
>> --
>> View this message in context:
>> http://n2.nabble.com/-maven-eclipse-plugin--We-need-your-help-to-test-the-future-2.7-tp2646905p2972277.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
>>
>>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Arnaud HERITIER]

Hi Ari,
Thanks for your feedback.

Did you follow this doc to setup your eclipse project :
http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
??

Arnaud


On Tue, May 26, 2009 at 2:29 AM, ari.meyer  wrote:

>
> Hi Arnaud,
>
> I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and I'm
> getting the same error when using Wicket:
>
> org.apache.wicket.markup.MarkupNotFoundException: Markup not found.
>
> Reverting again back to 2.5.1, everything worked properly.
>
> Best regards,
> Ari
>
>
> Arnaud HERITIER wrote:
> >
> > Hi Community,
> >   The recent release 2.6 of the maven-eclipse-plugin created many
> problems
> > for all of those who had/wanted to store non-java files under src/*/java
> > (which is required for wicket, ajdt, and probably others usecases).
> >   Even we have many integration tests in this plugin we didn't notice
> this
> > issue because our testcases allow us to check that generated
> configuration
> > files aren't evolving and that we are able to import and use a project in
> > eclipse (too heavy to do).
> >
> >   To fix this issue we (Barrie to be honest) improved the plugin to allow
> > the usage of includes and excludes. :
> > http://jira.codehaus.org/browse/MECLIPSE-104
> >   The documentation of these feature is here :
> >
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
> > There are many broken links on the site and I don't know why. I'll
> > investigate later.
> > Others pages are the same in
> > http://maven.apache.org/plugins/maven-eclipse-plugin/
> > For AJDT project you can have a look at this page :
> > http://maven.apache.org/plugins/maven-eclipse-plugin-
> > 2.7-SNAPSHOT/examples/ajdt-projects.html
> >
> > To test the plugin you have to add in your project or in your settings
> > this
> > repository :
> > https://repository.apache.org/content/repositories/snapshots/
> > (be careful to the https protocol)
> > The last version I deployed is : 2.7-20090416.000603-3
> >
> > Please, test it and give us your feedback. If it is positive this week,
> > we'll launch the release process the next one.
> >
> > cheers,
> >
> > --
> > Arnaud
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/-maven-eclipse-plugin--We-need-your-help-to-test-the-future-2.7-tp2646905p2972277.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] We need your help to test the future 2.7

[ari.meyer]

Hi Arnaud,

I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and I'm
getting the same error when using Wicket:

org.apache.wicket.markup.MarkupNotFoundException: Markup not found.

Reverting again back to 2.5.1, everything worked properly.

Best regards,
Ari


Arnaud HERITIER wrote:
> 
> Hi Community,
>   The recent release 2.6 of the maven-eclipse-plugin created many problems
> for all of those who had/wanted to store non-java files under src/*/java
> (which is required for wicket, ajdt, and probably others usecases).
>   Even we have many integration tests in this plugin we didn't notice this
> issue because our testcases allow us to check that generated configuration
> files aren't evolving and that we are able to import and use a project in
> eclipse (too heavy to do).
> 
>   To fix this issue we (Barrie to be honest) improved the plugin to allow
> the usage of includes and excludes. :
> http://jira.codehaus.org/browse/MECLIPSE-104
>   The documentation of these feature is here :
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
> There are many broken links on the site and I don't know why. I'll
> investigate later.
> Others pages are the same in
> http://maven.apache.org/plugins/maven-eclipse-plugin/
> For AJDT project you can have a look at this page :
> http://maven.apache.org/plugins/maven-eclipse-plugin-
> 2.7-SNAPSHOT/examples/ajdt-projects.html
> 
> To test the plugin you have to add in your project or in your settings
> this
> repository :
> https://repository.apache.org/content/repositories/snapshots/
> (be careful to the https protocol)
> The last version I deployed is : 2.7-20090416.000603-3
> 
> Please, test it and give us your feedback. If it is positive this week,
> we'll launch the release process the next one.
> 
> cheers,
> 
> -- 
> Arnaud
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/-maven-eclipse-plugin--We-need-your-help-to-test-the-future-2.7-tp2646905p2972277.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] We need your help to test the future 2.7

[Barrie Treloar]

Anything else?

Should we start the release process again then?

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Jim Sellers]

I agree.  I find that developer moan about *any* change, but within a week
or 2 they don't want it changed back.

Personally if the src folders that show up in eclipse change from a group of
src folders followed by a group of test folders to alternating test / src /
test / src, I would find that more confusing (but maybe that's just me).

For the number of hours I've wasted tracking down classpath ordering
differences between eclipse and maven, I don't understand why we would
diverge from maven for any reason.

I agree about the ctrl-shift-t and ctrl-shift-r as well.  So much easier
than actually looking for the types / resources. ;-)

Jim


On Wed, Apr 29, 2009 at 6:02 AM, Dirk Olmes  wrote:

>  The recent release 2.6 of the maven-eclipse-plugin created many
> problems
>  for all of those who had/wanted to store non-java files under
> src/*/java
>  (which is required for wicket, ajdt, and probably others usecases).
>  Even we have many integration tests in this plugin we didn't notice
> this
>  issue because our testcases allow us to check that generated
>  configuration files aren't evolving and that we are able to import and
>  use a project in eclipse (too heavy to do).
> >>> Regarding the new classpath ordering invented with 2.6, can you please
> >>> comment again in MECLIPSE-544 for my proposal (I mention it here, since
> >>> the issue is already closed). A classpath order like
> >>>
> >>> src/test/resource
> >>> src/main/java
> >>> src/test/java
> >>> src/main/resource
> >>>
> >>> Will solve also the test "resources first" problem. Since Eclipse will
> >>> complain anyway if you have to classes with the same name in
> >>> src/main/java and src/test/java, their order does not really matter for
> >>> Eclipse projects.
> >> What is wrong with having a classpath that matches Maven?
> >
> > Because every developer I've seen using the new plugin immediately thinks
> > something is broken after refreshing the IDE. And when you explain them
> the
> > situation, most of them moan about opening always the wrong node looking
> > for the code. Actually, it is confusing, since Maven projects are now
> even
> > more alienated in Eclipse as usual.
>
> Noting beats correctness! I'd say let developers moan for a while,
> they'll get used to the classpath ordering.
>
> Besides that: I hardly don't use any kind of explorer in Eclipse any
> more. Any project with a non-trivial codebase can be better handled
> opening types directly through Ctrl-Shift-T. But that's just my personal
> way of working...
>
> -dirk
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Dirk Olmes]

 The recent release 2.6 of the maven-eclipse-plugin created many problems
 for all of those who had/wanted to store non-java files under src/*/java
 (which is required for wicket, ajdt, and probably others usecases).
 Even we have many integration tests in this plugin we didn't notice this
 issue because our testcases allow us to check that generated
 configuration files aren't evolving and that we are able to import and
 use a project in eclipse (too heavy to do).
>>> Regarding the new classpath ordering invented with 2.6, can you please
>>> comment again in MECLIPSE-544 for my proposal (I mention it here, since
>>> the issue is already closed). A classpath order like
>>>
>>> src/test/resource
>>> src/main/java
>>> src/test/java
>>> src/main/resource
>>>
>>> Will solve also the test "resources first" problem. Since Eclipse will
>>> complain anyway if you have to classes with the same name in
>>> src/main/java and src/test/java, their order does not really matter for
>>> Eclipse projects.
>> What is wrong with having a classpath that matches Maven?
> 
> Because every developer I've seen using the new plugin immediately thinks
> something is broken after refreshing the IDE. And when you explain them the
> situation, most of them moan about opening always the wrong node looking
> for the code. Actually, it is confusing, since Maven projects are now even
> more alienated in Eclipse as usual.

Noting beats correctness! I'd say let developers moan for a while,
they'll get used to the classpath ordering.

Besides that: I hardly don't use any kind of explorer in Eclipse any
more. Any project with a non-trivial codebase can be better handled
opening types directly through Ctrl-Shift-T. But that's just my personal
way of working...

-dirk

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Arnaud HERITIER]

How is doing the m2eclipse/q4e plugins (these are now for me references on
how to integrate eclipse and maven).
Arnaud

On Wed, Apr 29, 2009 at 11:50 AM, Jörg Schaible wrote:

> Hi Barrie,
>
> Barrie Treloar wrote at Mittwoch, 29. April 2009 09:03:
>
> > On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaible 
> > wrote:
> >> Arnaud HERITIER wrote at Donnerstag, 16. April 2009 10:42:
> >>
> >>> Hi Community,
> >>> The recent release 2.6 of the maven-eclipse-plugin created many
> problems
> >>> for all of those who had/wanted to store non-java files under
> src/*/java
> >>> (which is required for wicket, ajdt, and probably others usecases).
> >>> Even we have many integration tests in this plugin we didn't notice
> this
> >>> issue because our testcases allow us to check that generated
> >>> configuration files aren't evolving and that we are able to import and
> >>> use a project in eclipse (too heavy to do).
> >>
> >> Regarding the new classpath ordering invented with 2.6, can you please
> >> comment again in MECLIPSE-544 for my proposal (I mention it here, since
> >> the issue is already closed). A classpath order like
> >>
> >> src/test/resource
> >> src/main/java
> >> src/test/java
> >> src/main/resource
> >>
> >> Will solve also the test "resources first" problem. Since Eclipse will
> >> complain anyway if you have to classes with the same name in
> >> src/main/java and src/test/java, their order does not really matter for
> >> Eclipse projects.
> >
> > What is wrong with having a classpath that matches Maven?
>
> Because every developer I've seen using the new plugin immediately thinks
> something is broken after refreshing the IDE. And when you explain them the
> situation, most of them moan about opening always the wrong node looking
> for the code. Actually, it is confusing, since Maven projects are now even
> more alienated in Eclipse as usual.
>
> > Since "mvn test" will fail with a different error than Eclipse with
> > your suggestion.
>
> Not really. It simply means that you created a situation (class files with
> same name in target/classes and target/test-classes) that is always
> reported as error in Eclipse and it does not matter which path comes first
> in this situation. In contrast will Maven simply compile, possibly even run
> the tests and actually behaves therefore always different. For an own test
> simply create a class Foo in src/main/java and interface Foo in
> src/test/java.
>
> Therefore I'd rather like to have my generated .classpath file to match
> what
> I'm used since years. I'd be willing to change my habits if there's
> actually a necessity, but obviously it is not.
>
> - Jörg
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Arnaud

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Jörg Schaible]

Hi Barrie,

Barrie Treloar wrote at Mittwoch, 29. April 2009 09:03:

> On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaible 
> wrote:
>> Arnaud HERITIER wrote at Donnerstag, 16. April 2009 10:42:
>>
>>> Hi Community,
>>> The recent release 2.6 of the maven-eclipse-plugin created many problems
>>> for all of those who had/wanted to store non-java files under src/*/java
>>> (which is required for wicket, ajdt, and probably others usecases).
>>> Even we have many integration tests in this plugin we didn't notice this
>>> issue because our testcases allow us to check that generated
>>> configuration files aren't evolving and that we are able to import and
>>> use a project in eclipse (too heavy to do).
>>
>> Regarding the new classpath ordering invented with 2.6, can you please
>> comment again in MECLIPSE-544 for my proposal (I mention it here, since
>> the issue is already closed). A classpath order like
>>
>> src/test/resource
>> src/main/java
>> src/test/java
>> src/main/resource
>>
>> Will solve also the test "resources first" problem. Since Eclipse will
>> complain anyway if you have to classes with the same name in
>> src/main/java and src/test/java, their order does not really matter for
>> Eclipse projects.
> 
> What is wrong with having a classpath that matches Maven?

Because every developer I've seen using the new plugin immediately thinks
something is broken after refreshing the IDE. And when you explain them the
situation, most of them moan about opening always the wrong node looking
for the code. Actually, it is confusing, since Maven projects are now even
more alienated in Eclipse as usual.

> Since "mvn test" will fail with a different error than Eclipse with
> your suggestion.

Not really. It simply means that you created a situation (class files with
same name in target/classes and target/test-classes) that is always
reported as error in Eclipse and it does not matter which path comes first
in this situation. In contrast will Maven simply compile, possibly even run
the tests and actually behaves therefore always different. For an own test
simply create a class Foo in src/main/java and interface Foo in
src/test/java.

Therefore I'd rather like to have my generated .classpath file to match what
I'm used since years. I'd be willing to change my habits if there's
actually a necessity, but obviously it is not.

- 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] We need your help to test the future 2.7

[Barrie Treloar]

On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaible  wrote:
> Arnaud HERITIER wrote at Donnerstag, 16. April 2009 10:42:
>
>> Hi Community,
>>   The recent release 2.6 of the maven-eclipse-plugin created many problems
>> for all of those who had/wanted to store non-java files under src/*/java
>> (which is required for wicket, ajdt, and probably others usecases).
>>   Even we have many integration tests in this plugin we didn't notice this
>> issue because our testcases allow us to check that generated configuration
>> files aren't evolving and that we are able to import and use a project in
>> eclipse (too heavy to do).
>
> Regarding the new classpath ordering invented with 2.6, can you please
> comment again in MECLIPSE-544 for my proposal (I mention it here, since the
> issue is already closed). A classpath order like
>
> src/test/resource
> src/main/java
> src/test/java
> src/main/resource
>
> Will solve also the test "resources first" problem. Since Eclipse will
> complain anyway if you have to classes with the same name in src/main/java
> and src/test/java, their order does not really matter for Eclipse projects.

What is wrong with having a classpath that matches Maven?
Since "mvn test" will fail with a different error than Eclipse with
your suggestion.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Jörg Schaible]

Arnaud HERITIER wrote at Donnerstag, 16. April 2009 10:42:

> Hi Community,
>   The recent release 2.6 of the maven-eclipse-plugin created many problems
> for all of those who had/wanted to store non-java files under src/*/java
> (which is required for wicket, ajdt, and probably others usecases).
>   Even we have many integration tests in this plugin we didn't notice this
> issue because our testcases allow us to check that generated configuration
> files aren't evolving and that we are able to import and use a project in
> eclipse (too heavy to do).

Regarding the new classpath ordering invented with 2.6, can you please
comment again in MECLIPSE-544 for my proposal (I mention it here, since the
issue is already closed). A classpath order like

src/test/resource
src/main/java
src/test/java
src/main/resource

Will solve also the test "resources first" problem. Since Eclipse will
complain anyway if you have to classes with the same name in src/main/java
and src/test/java, their order does not really matter for Eclipse projects.

- 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] We need your help to test the future 2.7

[Arnaud HERITIER]

thx for this feedbackI deployed a new snapshot : 2.7-20090427.230850-4
It includes the fixe for
MECLIPSE-455
 : Invalid dependent module archive name for EJB artifact
*
*
Cheers

Arnaud

On Tue, Apr 21, 2009 at 2:15 PM, Martijn Dashorst <
martijn.dasho...@gmail.com> wrote:

> The co-worker reported back that the plugin works as advertised
> (latest snapshot)
>
> Martijn
>
> On Tue, Apr 21, 2009 at 10:27 AM, Martijn Dashorst
>  wrote:
> > A co-worker tested it, and found it not working. He'll comment later.
> >
> > Martijn
> >
> > On Tue, Apr 21, 2009 at 12:20 AM, Arnaud HERITIER 
> wrote:
> >> Ping ??Nobody wants to test it ?
> >> Without your help, will never be able to produce a plugin which replies
> to
> >> your needs.
> >> Cheers,
> >>
> >> Arnaud
> >>
> >> On Thu, Apr 16, 2009 at 10:42 AM, Arnaud HERITIER  >wrote:
> >>
> >>> Hi Community,
> >>>   The recent release 2.6 of the maven-eclipse-plugin created many
> problems
> >>> for all of those who had/wanted to store non-java files under
> src/*/java
> >>> (which is required for wicket, ajdt, and probably others usecases).
> >>>   Even we have many integration tests in this plugin we didn't notice
> this
> >>> issue because our testcases allow us to check that generated
> configuration
> >>> files aren't evolving and that we are able to import and use a project
> in
> >>> eclipse (too heavy to do).
> >>>
> >>>   To fix this issue we (Barrie to be honest) improved the plugin to
> allow
> >>> the usage of includes and excludes. :
> >>> http://jira.codehaus.org/browse/MECLIPSE-104
> >>>   The documentation of these feature is here :
> >>>
> >>>
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
> >>> There are many broken links on the site and I don't know why. I'll
> >>> investigate later.
> >>> Others pages are the same in
> >>> http://maven.apache.org/plugins/maven-eclipse-plugin/
> >>> For AJDT project you can have a look at this page :
> >>> http://maven.apache.org/plugins/maven-eclipse-plugin-
> >>> 2.7-SNAPSHOT/examples/ajdt-projects.html
> >>>
> >>> To test the plugin you have to add in your project or in your settings
> this
> >>> repository :
> >>> https://repository.apache.org/content/repositories/snapshots/
> >>> (be careful to the https protocol)
> >>> The last version I deployed is : 2.7-20090416.000603-3
> >>>
> >>> Please, test it and give us your feedback. If it is positive this week,
> >>> we'll launch the release process the next one.
> >>>
> >>> cheers,
> >>>
> >>> --
> >>> Arnaud
> >>>
> >>
> >>
> >>
> >> --
> >> Arnaud
> >>
> >
> >
> >
> > --
> > Become a Wicket expert, learn from the best: http://wicketinaction.com
> > Apache Wicket 1.3.5 is released
> > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
> >
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.5 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Arnaud

Re: maven eclipse plugin problem with ejb projects

[Arnaud HERITIER]

hi Steffen,
  Thx a lot.
  I'll apply it soon (I'll try this WE)

cheers

Arnaud

On Fri, Apr 24, 2009 at 2:24 AM, Steffen Grunwald <
steffen.grunw...@gmail.com> wrote:

> Hello Arnaud,
>
> > Can you also provide an integration test to validate the issue ?
> > If you give me ne, I'll apply them on 2.7
>
> Great. There you go. I attached the testcase to [1].
>
> Thanks, Steffen
>
> [1] http://jira.codehaus.org/browse/MECLIPSE-455
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Arnaud

Re: maven eclipse plugin problem with ejb projects

[Steffen Grunwald]

Hello Arnaud,

> Can you also provide an integration test to validate the issue ?
> If you give me ne, I'll apply them on 2.7

Great. There you go. I attached the testcase to [1].

Thanks, Steffen

[1] http://jira.codehaus.org/browse/MECLIPSE-455

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

Re: maven eclipse plugin problem with ejb projects

[Arnaud HERITIER]

I just reviewed it.Thx for your help.
Can you also provide an integration test to validate the issue ?
If you give me ne, I'll apply them on 2.7
Cheers,

Thx

On Thu, Apr 23, 2009 at 1:03 PM, Steffen Grunwald <
steffen.grunw...@gmail.com> wrote:

> Hello,
>
> I'm facing an issue mentioned in bug [1] and [2] that causes a wrong
> extension in the eclipse .settings files. This problem still exists in
> the 2.6 release.
> I submitted a patch quite a while ago and would like to know, if there
> are some plans to commit the patch or fix the problem in another way
> for a next release.
>
> Thanks, Steffen
>
> [1] http://jira.codehaus.org/browse/MECLIPSE-451
> [2] http://jira.codehaus.org/browse/MECLIPSE-455
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Arnaud