eclipse-maven-plugin v3.0 breaks sample projects

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

eclipse-maven-plugin v3.0 breaks sample projects

David Witherspoon

I have a groovy-only project that I was building with gmaven, but wanted to switch it over to using the groovy eclipse compiler.

So I followed the info here. And that works.

But there's a new 3.0 version of the maven-compiler-plugin. When I switched to that version, it would show source folders being added to the list to compile, but then exit saying that everything was up to date.

So I took the sample project (bottom of the linked page) and compiled it as is...no problem. I switched that simple project to maven-compiler-plugin v3.0...and it fails to build anything in the same way.

What's up?
 
- DaveyBob
Reply | Threaded
Open this post in threaded view
|

Re: eclipse-maven-plugin v3.0 breaks sample projects

Andrew Eisenberg
Unless you have at least one java file, there are some hoops you need
to go through to get maven to find the groovy files.  The easiest
thing to do is to have a single dummy java file in your sources and
another in your test sources.  Do you have one already?

On Thu, Jan 10, 2013 at 5:10 AM, David Witherspoon <[hidden email]> wrote:

>
> I have a groovy-only project that I was building with gmaven, but wanted to
> switch it over to using the groovy eclipse compiler.
>
> So I followed the info here. And that works.
>
> But there's a new 3.0 version of the maven-compiler-plugin. When I switched
> to that version, it would show source folders being added to the list to
> compile, but then exit saying that everything was up to date.
>
> So I took the sample project (bottom of the linked page) and compiled it as
> is...no problem. I switched that simple project to maven-compiler-plugin
> v3.0...and it fails to build anything in the same way.
>
> What's up?
>
> - DaveyBob

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: eclipse-maven-plugin v3.0 breaks sample projects

David Witherspoon
Well, the groovy-eclipse-maven-tests project itself has .java files under both src/main and src/java.

Making no other change but switching maven-compiler-plugin version to 3.0 causes mvn clean compile to emit this:

[INFO] Scanning for projects...
[INFO]                                                                        
[INFO] ------------------------------------------------------------------------
[INFO] Building Groovy-Eclipse and Maven can play nicely together! 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ groovy-eclipse-maven-tests ---
[INFO] Deleting /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/target
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ groovy-eclipse-maven-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ groovy-eclipse-maven-tests ---
[INFO] Nothing to compile - all classes are up to date
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.955s
[INFO] Finished at: Fri Jan 11 07:26:02 EST 2013
[INFO] Final Memory: 5M/150M
[INFO] ------------------------------------------------------------------------

I also did mvn -X compile (after doing a clean), and attached that output to this email (just in case there's something to look at there).

In my own project, which is groovy only, I did add the groovy-eclipse-compiler plugin reference with extensions=true.  But that did not help.

For now, I am using version 2.3.2 of the maven-compiler-plugin, and that's working fine.

- David

From: Andrew Eisenberg <[hidden email]>
To: [hidden email]
Sent: Thursday, January 10, 2013 6:25 PM
Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks sample projects

Unless you have at least one java file, there are some hoops you need
to go through to get maven to find the groovy files.  The easiest
thing to do is to have a single dummy java file in your sources and
another in your test sources.  Do you have one already?

On Thu, Jan 10, 2013 at 5:10 AM, David Witherspoon <[hidden email]> wrote:

>
> I have a groovy-only project that I was building with gmaven, but wanted to
> switch it over to using the groovy eclipse compiler.
>
> So I followed the info here. And that works.
>
> But there's a new 3.0 version of the maven-compiler-plugin. When I switched
> to that version, it would show source folders being added to the list to
> compile, but then exit saying that everything was up to date.
>
> So I took the sample project (bottom of the linked page) and compiled it as
> is...no problem. I switched that simple project to maven-compiler-plugin
> v3.0...and it fails to build anything in the same way.
>
> What's up?
>
> - DaveyBob

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email






---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

mvncompiledebugoutput.txt (41K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: eclipse-maven-plugin v3.0 breaks sample projects

Andrew Eisenberg-2
Thanks.  I will take a look.

On Friday, January 11, 2013, David Witherspoon wrote:
Well, the groovy-eclipse-maven-tests project itself has .java files under both src/main and src/java.

Making no other change but switching maven-compiler-plugin version to 3.0 causes mvn clean compile to emit this:

[INFO] Scanning for projects...
[INFO]                                                                        
[INFO] ------------------------------------------------------------------------
[INFO] Building Groovy-Eclipse and Maven can play nicely together! 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ groovy-eclipse-maven-tests ---
[INFO] Deleting /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/target
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ groovy-eclipse-maven-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ groovy-eclipse-maven-tests ---
[INFO] Nothing to compile - all classes are up to date
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.955s
[INFO] Finished at: Fri Jan 11 07:26:02 EST 2013
[INFO] Final Memory: 5M/150M
[INFO] ------------------------------------------------------------------------

I also did mvn -X compile (after doing a clean), and attached that output to this email (just in case there's something to look at there).

In my own project, which is groovy only, I did add the groovy-eclipse-compiler plugin reference with extensions=true.  But that did not help.

For now, I am using version 2.3.2 of the maven-compiler-plugin, and that's working fine.

- David

From: Andrew Eisenberg <<a href="javascript:_e({}, &#39;cvml&#39;, &#39;andrew@eisenberg.as&#39;);" target="_blank">andrew@...>
To: <a href="javascript:_e({}, &#39;cvml&#39;, &#39;eclipse-plugin-user@groovy.codehaus.org&#39;);" target="_blank">eclipse-plugin-user@...
Sent: Thursday, January 10, 2013 6:25 PM
Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks sample projects

Unless you have at least one java file, there are some hoops you need
to go through to get maven to find the groovy files.  The easiest
thing to do is to have a single dummy java file in your sources and
another in your test sources.  Do you have one already?

On Thu, Jan 10, 2013 at 5:10 AM, David Witherspoon <<a href="javascript:_e({}, &#39;cvml&#39;, &#39;dbw.online@yahoo.com&#39;);" target="_blank">dbw.online@...> wrote:
>
> I have a groovy-only project that I was building with gmaven, but wanted to
> switch it over to using the groovy eclipse compiler.
>
> So I followed the info here. And that works.
>
> But there's a new 3.0 version of the maven-compiler-plugin. When I switched
> to that version, it would show source folders being added to the list to
> compile, but then exit saying that everything was up to date.
>
> So I took the sample project (bottom of the linked page) and compiled it as
> is...no problem. I switched that simple project to maven-compiler-plugin
> v3.0...and it fails to build anything in the same way.
>
> What's up?
>
> - DaveyBob

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email




Reply | Threaded
Open this post in threaded view
|

Re: eclipse-maven-plugin v3.0 breaks sample projects

David Witherspoon
Has there been any development on this?
- David Witherspoon

From: Andrew Eisenberg <[hidden email]>
To: "[hidden email]" <[hidden email]>
Sent: Friday, January 11, 2013 10:49 AM
Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks sample projects

Thanks.  I will take a look.

On Friday, January 11, 2013, David Witherspoon wrote:
Well, the groovy-eclipse-maven-tests project itself has .java files under both src/main and src/java.

Making no other change but switching maven-compiler-plugin version to 3.0 causes mvn clean compile to emit this:

[INFO] Scanning for projects...
[INFO]                                                                        
[INFO] ------------------------------------------------------------------------
[INFO] Building Groovy-Eclipse and Maven can play nicely together! 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ groovy-eclipse-maven-tests ---
[INFO] Deleting /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/target
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ groovy-eclipse-maven-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ groovy-eclipse-maven-tests ---
[INFO] Nothing to compile - all classes are up to date
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.955s
[INFO] Finished at: Fri Jan 11 07:26:02 EST 2013
[INFO] Final Memory: 5M/150M
[INFO] ------------------------------------------------------------------------

I also did mvn -X compile (after doing a clean), and attached that output to this email (just in case there's something to look at there).

In my own project, which is groovy only, I did add the groovy-eclipse-compiler plugin reference with extensions=true.  But that did not help.

For now, I am using version 2.3.2 of the maven-compiler-plugin, and that's working fine.

- David

From: Andrew Eisenberg <andrew@...>
To: eclipse-plugin-user@...
Sent: Thursday, January 10, 2013 6:25 PM
Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks sample projects

Unless you have at least one java file, there are some hoops you need
to go through to get maven to find the groovy files.  The easiest
thing to do is to have a single dummy java file in your sources and
another in your test sources.  Do you have one already?

On Thu, Jan 10, 2013 at 5:10 AM, David Witherspoon <dbw.online@...> wrote:
>
> I have a groovy-only project that I was building with gmaven, but wanted to
> switch it over to using the groovy eclipse compiler.
>
> So I followed the info here. And that works.
>
> But there's a new 3.0 version of the maven-compiler-plugin. When I switched
> to that version, it would show source folders being added to the list to
> compile, but then exit saying that everything was up to date.
>
> So I took the sample project (bottom of the linked page) and compiled it as
> is...no problem. I switched that simple project to maven-compiler-plugin
> v3.0...and it fails to build anything in the same way.
>
> What's up?
>
> - DaveyBob

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email






Reply | Threaded
Open this post in threaded view
|

Re: eclipse-maven-plugin v3.0 breaks sample projects

Andrew Eisenberg
Sorry, I haven't been able to touch this yet.  We are busy trying to
get GGTS 3.2.0.M2 out.  I will be able to get to this shortly.

On Tue, Jan 22, 2013 at 4:08 AM, David Witherspoon <[hidden email]> wrote:

> Has there been any development on this?
> - David Witherspoon
> ________________________________
> From: Andrew Eisenberg <[hidden email]>
> To: "[hidden email]"
> <[hidden email]>
> Sent: Friday, January 11, 2013 10:49 AM
>
> Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks
> sample projects
>
> Thanks.  I will take a look.
>
> On Friday, January 11, 2013, David Witherspoon wrote:
>
> Well, the groovy-eclipse-maven-tests project itself has .java files under
> both src/main and src/java.
>
> Making no other change but switching maven-compiler-plugin version to 3.0
> causes mvn clean compile to emit this:
>
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Groovy-Eclipse and Maven can play nicely together!
> 1.0-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> groovy-eclipse-maven-tests ---
> [INFO] Deleting
> /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
> groovy-eclipse-maven-tests ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @
> groovy-eclipse-maven-tests ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 0.955s
> [INFO] Finished at: Fri Jan 11 07:26:02 EST 2013
> [INFO] Final Memory: 5M/150M
> [INFO]
> ------------------------------------------------------------------------
>
> I also did mvn -X compile (after doing a clean), and attached that output to
> this email (just in case there's something to look at there).
>
> In my own project, which is groovy only, I did add the
> groovy-eclipse-compiler plugin reference with extensions=true.  But that did
> not help.
>
> For now, I am using version 2.3.2 of the maven-compiler-plugin, and that's
> working fine.
>
> - David
> ________________________________
> From: Andrew Eisenberg <[hidden email]>
> To: [hidden email]
> Sent: Thursday, January 10, 2013 6:25 PM
> Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks
> sample projects
>
> Unless you have at least one java file, there are some hoops you need
> to go through to get maven to find the groovy files.  The easiest
> thing to do is to have a single dummy java file in your sources and
> another in your test sources.  Do you have one already?
>
> On Thu, Jan 10, 2013 at 5:10 AM, David Witherspoon <[hidden email]>
> wrote:
>>
>> I have a groovy-only project that I was building with gmaven, but wanted
>> to
>> switch it over to using the groovy eclipse compiler.
>>
>> So I followed the info here. And that works.
>>
>> But there's a new 3.0 version of the maven-compiler-plugin. When I
>> switched
>> to that version, it would show source folders being added to the list to
>> compile, but then exit saying that everything was up to date.
>>
>> So I took the sample project (bottom of the linked page) and compiled it
>> as
>> is...no problem. I switched that simple project to maven-compiler-plugin
>> v3.0...and it fails to build anything in the same way.
>>
>> What's up?
>>
>> - DaveyBob
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: eclipse-maven-plugin v3.0 breaks sample projects

Andrew Eisenberg
Having a look now.  This is unfortunate since when I tried a
3.0-SNAPSHOT version just before the release, things were working.

On Tue, Jan 22, 2013 at 4:53 PM, Andrew Eisenberg <[hidden email]> wrote:

> Sorry, I haven't been able to touch this yet.  We are busy trying to
> get GGTS 3.2.0.M2 out.  I will be able to get to this shortly.
>
> On Tue, Jan 22, 2013 at 4:08 AM, David Witherspoon <[hidden email]> wrote:
>> Has there been any development on this?
>> - David Witherspoon
>> ________________________________
>> From: Andrew Eisenberg <[hidden email]>
>> To: "[hidden email]"
>> <[hidden email]>
>> Sent: Friday, January 11, 2013 10:49 AM
>>
>> Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks
>> sample projects
>>
>> Thanks.  I will take a look.
>>
>> On Friday, January 11, 2013, David Witherspoon wrote:
>>
>> Well, the groovy-eclipse-maven-tests project itself has .java files under
>> both src/main and src/java.
>>
>> Making no other change but switching maven-compiler-plugin version to 3.0
>> causes mvn clean compile to emit this:
>>
>> [INFO] Scanning for projects...
>> [INFO]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building Groovy-Eclipse and Maven can play nicely together!
>> 1.0-SNAPSHOT
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO]
>> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
>> groovy-eclipse-maven-tests ---
>> [INFO] Deleting
>> /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/target
>> [INFO]
>> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
>> groovy-eclipse-maven-tests ---
>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>> [INFO] skip non existing resourceDirectory
>> /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/src/main/resources
>> [INFO]
>> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @
>> groovy-eclipse-maven-tests ---
>> [INFO] Nothing to compile - all classes are up to date
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 0.955s
>> [INFO] Finished at: Fri Jan 11 07:26:02 EST 2013
>> [INFO] Final Memory: 5M/150M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> I also did mvn -X compile (after doing a clean), and attached that output to
>> this email (just in case there's something to look at there).
>>
>> In my own project, which is groovy only, I did add the
>> groovy-eclipse-compiler plugin reference with extensions=true.  But that did
>> not help.
>>
>> For now, I am using version 2.3.2 of the maven-compiler-plugin, and that's
>> working fine.
>>
>> - David
>> ________________________________
>> From: Andrew Eisenberg <[hidden email]>
>> To: [hidden email]
>> Sent: Thursday, January 10, 2013 6:25 PM
>> Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks
>> sample projects
>>
>> Unless you have at least one java file, there are some hoops you need
>> to go through to get maven to find the groovy files.  The easiest
>> thing to do is to have a single dummy java file in your sources and
>> another in your test sources.  Do you have one already?
>>
>> On Thu, Jan 10, 2013 at 5:10 AM, David Witherspoon <[hidden email]>
>> wrote:
>>>
>>> I have a groovy-only project that I was building with gmaven, but wanted
>>> to
>>> switch it over to using the groovy eclipse compiler.
>>>
>>> So I followed the info here. And that works.
>>>
>>> But there's a new 3.0 version of the maven-compiler-plugin. When I
>>> switched
>>> to that version, it would show source folders being added to the list to
>>> compile, but then exit saying that everything was up to date.
>>>
>>> So I took the sample project (bottom of the linked page) and compiled it
>>> as
>>> is...no problem. I switched that simple project to maven-compiler-plugin
>>> v3.0...and it fails to build anything in the same way.
>>>
>>> What's up?
>>>
>>> - DaveyBob
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>>
>>
>>
>>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: eclipse-maven-plugin v3.0 breaks sample projects

Andrew Eisenberg
Looks like the 3.0 compiler has changed the way it looks for source
files.  If you add the following to your maven-compiler-plugin
configuration, it should work:

  <includes>
                                                <include>**/*.groovy</include>
                                                <include>**/*.java</include>
                                        </includes>
                                        <testIncludes>
                                                <testInclude>**/*.groovy</testInclude>
                                                <testInclude>**/*.java</testInclude>
                                        </testIncludes>

There should also be a way for the groovy-eclipse-compiler to inject
this configuration automatically, and I'll put out a new version that
does this when I can.

Let me know if this works for you.


On Wed, Jan 23, 2013 at 10:06 AM, Andrew Eisenberg <[hidden email]> wrote:

> Having a look now.  This is unfortunate since when I tried a
> 3.0-SNAPSHOT version just before the release, things were working.
>
> On Tue, Jan 22, 2013 at 4:53 PM, Andrew Eisenberg <[hidden email]> wrote:
>> Sorry, I haven't been able to touch this yet.  We are busy trying to
>> get GGTS 3.2.0.M2 out.  I will be able to get to this shortly.
>>
>> On Tue, Jan 22, 2013 at 4:08 AM, David Witherspoon <[hidden email]> wrote:
>>> Has there been any development on this?
>>> - David Witherspoon
>>> ________________________________
>>> From: Andrew Eisenberg <[hidden email]>
>>> To: "[hidden email]"
>>> <[hidden email]>
>>> Sent: Friday, January 11, 2013 10:49 AM
>>>
>>> Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks
>>> sample projects
>>>
>>> Thanks.  I will take a look.
>>>
>>> On Friday, January 11, 2013, David Witherspoon wrote:
>>>
>>> Well, the groovy-eclipse-maven-tests project itself has .java files under
>>> both src/main and src/java.
>>>
>>> Making no other change but switching maven-compiler-plugin version to 3.0
>>> causes mvn clean compile to emit this:
>>>
>>> [INFO] Scanning for projects...
>>> [INFO]
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Building Groovy-Eclipse and Maven can play nicely together!
>>> 1.0-SNAPSHOT
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO]
>>> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
>>> groovy-eclipse-maven-tests ---
>>> [INFO] Deleting
>>> /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/target
>>> [INFO]
>>> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
>>> groovy-eclipse-maven-tests ---
>>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>>> [INFO] skip non existing resourceDirectory
>>> /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/src/main/resources
>>> [INFO]
>>> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @
>>> groovy-eclipse-maven-tests ---
>>> [INFO] Nothing to compile - all classes are up to date
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD SUCCESS
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 0.955s
>>> [INFO] Finished at: Fri Jan 11 07:26:02 EST 2013
>>> [INFO] Final Memory: 5M/150M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> I also did mvn -X compile (after doing a clean), and attached that output to
>>> this email (just in case there's something to look at there).
>>>
>>> In my own project, which is groovy only, I did add the
>>> groovy-eclipse-compiler plugin reference with extensions=true.  But that did
>>> not help.
>>>
>>> For now, I am using version 2.3.2 of the maven-compiler-plugin, and that's
>>> working fine.
>>>
>>> - David
>>> ________________________________
>>> From: Andrew Eisenberg <[hidden email]>
>>> To: [hidden email]
>>> Sent: Thursday, January 10, 2013 6:25 PM
>>> Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks
>>> sample projects
>>>
>>> Unless you have at least one java file, there are some hoops you need
>>> to go through to get maven to find the groovy files.  The easiest
>>> thing to do is to have a single dummy java file in your sources and
>>> another in your test sources.  Do you have one already?
>>>
>>> On Thu, Jan 10, 2013 at 5:10 AM, David Witherspoon <[hidden email]>
>>> wrote:
>>>>
>>>> I have a groovy-only project that I was building with gmaven, but wanted
>>>> to
>>>> switch it over to using the groovy eclipse compiler.
>>>>
>>>> So I followed the info here. And that works.
>>>>
>>>> But there's a new 3.0 version of the maven-compiler-plugin. When I
>>>> switched
>>>> to that version, it would show source folders being added to the list to
>>>> compile, but then exit saying that everything was up to date.
>>>>
>>>> So I took the sample project (bottom of the linked page) and compiled it
>>>> as
>>>> is...no problem. I switched that simple project to maven-compiler-plugin
>>>> v3.0...and it fails to build anything in the same way.
>>>>
>>>> What's up?
>>>>
>>>> - DaveyBob
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>     http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>>
>>>
>>>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: eclipse-maven-plugin v3.0 breaks sample projects

David Witherspoon
Thanks much, Andrew, for looking into this!

Yes, this change works.

- David Witherspoon

From: Andrew Eisenberg <[hidden email]>
To: [hidden email]
Sent: Wednesday, January 23, 2013 6:46 PM
Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks sample projects

Looks like the 3.0 compiler has changed the way it looks for source
files.  If you add the following to your maven-compiler-plugin
configuration, it should work:

                    <includes>
                        <include>**/*.groovy</include>
                        <include>**/*.java</include>
                    </includes>
                    <testIncludes>
                        <testInclude>**/*.groovy</testInclude>
                        <testInclude>**/*.java</testInclude>
                    </testIncludes>

There should also be a way for the groovy-eclipse-compiler to inject
this configuration automatically, and I'll put out a new version that
does this when I can.

Let me know if this works for you.


On Wed, Jan 23, 2013 at 10:06 AM, Andrew Eisenberg <[hidden email]> wrote:

> Having a look now.  This is unfortunate since when I tried a
> 3.0-SNAPSHOT version just before the release, things were working.
>
> On Tue, Jan 22, 2013 at 4:53 PM, Andrew Eisenberg <[hidden email]> wrote:
>> Sorry, I haven't been able to touch this yet.  We are busy trying to
>> get GGTS 3.2.0.M2 out.  I will be able to get to this shortly.
>>
>> On Tue, Jan 22, 2013 at 4:08 AM, David Witherspoon <[hidden email]> wrote:
>>> Has there been any development on this?
>>> - David Witherspoon
>>> ________________________________
>>> From: Andrew Eisenberg <[hidden email]>
>>> To: "[hidden email]"
>>> <[hidden email]>
>>> Sent: Friday, January 11, 2013 10:49 AM
>>>
>>> Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks
>>> sample projects
>>>
>>> Thanks.  I will take a look.
>>>
>>> On Friday, January 11, 2013, David Witherspoon wrote:
>>>
>>> Well, the groovy-eclipse-maven-tests project itself has .java files under
>>> both src/main and src/java.
>>>
>>> Making no other change but switching maven-compiler-plugin version to 3.0
>>> causes mvn clean compile to emit this:
>>>
>>> [INFO] Scanning for projects...
>>> [INFO]
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Building Groovy-Eclipse and Maven can play nicely together!
>>> 1.0-SNAPSHOT
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO]
>>> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
>>> groovy-eclipse-maven-tests ---
>>> [INFO] Deleting
>>> /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/target
>>> [INFO]
>>> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
>>> groovy-eclipse-maven-tests ---
>>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>>> [INFO] skip non existing resourceDirectory
>>> /data/dwitherspoon/projects/Panacea-trunk/groovy-eclipse-maven-tests/src/main/resources
>>> [INFO]
>>> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @
>>> groovy-eclipse-maven-tests ---
>>> [INFO] Nothing to compile - all classes are up to date
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD SUCCESS
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 0.955s
>>> [INFO] Finished at: Fri Jan 11 07:26:02 EST 2013
>>> [INFO] Final Memory: 5M/150M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> I also did mvn -X compile (after doing a clean), and attached that output to
>>> this email (just in case there's something to look at there).
>>>
>>> In my own project, which is groovy only, I did add the
>>> groovy-eclipse-compiler plugin reference with extensions=true.  But that did
>>> not help.
>>>
>>> For now, I am using version 2.3.2 of the maven-compiler-plugin, and that's
>>> working fine.
>>>
>>> - David
>>> ________________________________
>>> From: Andrew Eisenberg <[hidden email]>
>>> To: [hidden email]
>>> Sent: Thursday, January 10, 2013 6:25 PM
>>> Subject: Re: [groovy-eclipse-plugin-user] eclipse-maven-plugin v3.0 breaks
>>> sample projects
>>>
>>> Unless you have at least one java file, there are some hoops you need
>>> to go through to get maven to find the groovy files.  The easiest
>>> thing to do is to have a single dummy java file in your sources and
>>> another in your test sources.  Do you have one already?
>>>
>>> On Thu, Jan 10, 2013 at 5:10 AM, David Witherspoon <[hidden email]>
>>> wrote:
>>>>
>>>> I have a groovy-only project that I was building with gmaven, but wanted
>>>> to
>>>> switch it over to using the groovy eclipse compiler.
>>>>
>>>> So I followed the info here. And that works.
>>>>
>>>> But there's a new 3.0 version of the maven-compiler-plugin. When I
>>>> switched
>>>> to that version, it would show source folders being added to the list to
>>>> compile, but then exit saying that everything was up to date.
>>>>
>>>> So I took the sample project (bottom of the linked page) and compiled it
>>>> as
>>>> is...no problem. I switched that simple project to maven-compiler-plugin
>>>> v3.0...and it fails to build anything in the same way.
>>>>
>>>> What's up?
>>>>
>>>> - DaveyBob
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>>
>>>
>>>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email