You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Stefan Seelmann <se...@apache.org> on 2008/09/02 20:44:17 UTC
Re: svn commit: r690978 - /directory/studio/trunk/pom.xml
Hi Felix,
I have a problem with the 2.5.1 maven-eclipse-plugin. An 'mvn
eclipse:eclipse' does not generate the .classpath and .project files. I
switched locally back to 2.3 to make it working again.
Do others have the same problem with the 2.5.1?
Kind Regards,
Stefan
felixk@apache.org wrote:
> Author: felixk
> Date: Mon Sep 1 07:35:04 2008
> New Revision: 690978
>
> URL: http://svn.apache.org/viewvc?rev=690978&view=rev
> Log:
> Update version
>
> Modified:
> directory/studio/trunk/pom.xml
>
> Modified: directory/studio/trunk/pom.xml
> URL: http://svn.apache.org/viewvc/directory/studio/trunk/pom.xml?rev=690978&r1=690977&r2=690978&view=diff
> ==============================================================================
> --- directory/studio/trunk/pom.xml (original)
> +++ directory/studio/trunk/pom.xml Mon Sep 1 07:35:04 2008
> @@ -2543,7 +2543,7 @@
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-eclipse-plugin</artifactId>
> - <version>2.3</version>
> + <version>2.5.1</version>
> </plugin>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
>
>
Re: svn commit: r690978 - /directory/studio/trunk/pom.xml
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> On Wed, Sep 3, 2008 at 7:15 AM, Felix Knecht <felixk@apache.org
> <ma...@apache.org>> wrote:
>
> Hi Stefan
>
> > I have a problem with the 2.5.1 maven-eclipse-plugin. An 'mvn
> > eclipse:eclipse' does not generate the .classpath and .project
> files. I
> > switched locally back to 2.3 to make it working again.
>
> Your right, thanks for pointing to. Even mvn eclipse:eclipse
> doesn't created .project or .classpath.
> I'm going to revert this to 2.3.
> It wasn't easy at that time to make it work and it seems to
> becaome even more complicated as the maven-eclipse-plugin
> isn't backwards compatible.
>
>
> Woaw... That's crazy... mvn eclipse:eclipse now does not generate any
> .project or .classpath file ?!?...
> Then, what's the purpose of this goal in this plugin ?!?.. Theres's
> something I don't understand...
I think I've found the culprit. In the studio/pom.xml we set
configuration/skip=true in the builds/maven-eclipse.... . For version
2.5.1 this seems now to be inherited by all the subprojects. Speaking
that we were lucky up to now that it was working because I think it was
a bug which is now fixed.
I give it a try to get the .project and .classpath files back with
eclipse-plugin 2.5.1.
Felix
Re: svn commit: r690978 - /directory/studio/trunk/pom.xml
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
On Wed, Sep 3, 2008 at 7:15 AM, Felix Knecht <fe...@apache.org> wrote:
> Hi Stefan
>
> > I have a problem with the 2.5.1 maven-eclipse-plugin. An 'mvn
> > eclipse:eclipse' does not generate the .classpath and .project files. I
> > switched locally back to 2.3 to make it working again.
>
> Your right, thanks for pointing to. Even mvn eclipse:eclipse doesn't
> created .project or .classpath.
> I'm going to revert this to 2.3.
> It wasn't easy at that time to make it work and it seems to becaome even
> more complicated as the maven-eclipse-plugin
> isn't backwards compatible.
Woaw... That's crazy... mvn eclipse:eclipse now does not generate any
.project or .classpath file ?!?...
Then, what's the purpose of this goal in this plugin ?!?.. Theres's
something I don't understand...
IMO we should think about putting all the functionality we need into the
> studio plugin and get rid of the maven-eclipse
> plugin. I think it's only generation of the .project and the .classpath
> which are missing.
>
> WDOT?
>
Yeah maybe... Having something reliable and trustful for the generation of
these files is really important.
We could maybe also commit these files in SVN... I know other projects try
to avoid committing such files to source configuration, but since we're
building Eclipse plugins, it does not make to try to generate project files
for Idea of NetBeans. Our Eclipse plugin projects will always be used with
Eclipse.
So, I'm wondering if it makes sense not to commit the .project and
.classpath files with the projects.
Regards,
Pierre-Arnaud
Re: svn commit: r690978 - /directory/studio/trunk/pom.xml
Posted by Felix Knecht <fe...@apache.org>.
Hi Stefan
> I have a problem with the 2.5.1 maven-eclipse-plugin. An 'mvn
> eclipse:eclipse' does not generate the .classpath and .project files. I
> switched locally back to 2.3 to make it working again.
Your right, thanks for pointing to. Even mvn eclipse:eclipse doesn't created .project or .classpath.
I'm going to revert this to 2.3.
It wasn't easy at that time to make it work and it seems to becaome even more complicated as the maven-eclipse-plugin
isn't backwards compatible.
IMO we should think about putting all the functionality we need into the studio plugin and get rid of the maven-eclipse
plugin. I think it's only generation of the .project and the .classpath which are missing.
WDOT?
Felix