You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Arnaud HERITIER <ah...@gmail.com> on 2009/04/16 10:42:43 UTC

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

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

Re: how to define license?

Posted by Wayne Fay <wa...@gmail.com>.
> When building the project's site with 'mvn site' I can't figure out how
> to configure the license. "Project Information > Project License" on the
> website maven builds the page says " No project license is defined for
> this project"  So how do I define a license?

Google "maven pom license" brought me to this page:
http://tomionsoftware.blogspot.com/2005/12/maven-2-how-to-add-licensetxt.html

Wayne

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

how to define license?

Posted by "REMIJAN, MICHAEL J [AG/1000]" <mi...@monsanto.com>.
When building the project's site with 'mvn site' I can't figure out how
to configure the license. "Project Information > Project License" on the
website maven builds the page says " No project license is defined for
this project"  So how do I define a license?

Thanks,
Mike 


---------------------------------------------------------------------------------------------------------
This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited.


All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment.
---------------------------------------------------------------------------------------------------------


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

Re: Including Javadocs (API) with project website

Posted by Wendy Smoak <ws...@gmail.com>.
On Mon, Apr 27, 2009 at 4:35 PM, REMIJAN, MICHAEL J [AG/1000]
<mi...@monsanto.com> wrote:
> Two part question,
>
> 1) is it possible for 'mvn site' to automatically generate javadocs or
> do I always have to do javadoc:javadoc before running 'mvn site'

Put it in the <reporting> section, as described on
http://maven.apache.org/plugins/maven-javadoc-plugin/usage.html

> 2) Is there standard <menu> in site.xml to generate the hyperlink to the
> javadocs?

I think it shows up automatically in the Project Reports section.  You
can add a link from other pages/menus if you want.

-- 
Wendy

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

Including Javadocs (API) with project website

Posted by "REMIJAN, MICHAEL J [AG/1000]" <mi...@monsanto.com>.
Two part question,

1) is it possible for 'mvn site' to automatically generate javadocs or
do I always have to do javadoc:javadoc before running 'mvn site'

2) Is there standard <menu> in site.xml to generate the hyperlink to the
javadocs?

Thanks!
Mike

---------------------------------------------------------------------------------------------------------
This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited.


All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment.
---------------------------------------------------------------------------------------------------------


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

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

Posted by Arnaud HERITIER <ah...@gmail.com>.
thx for this feedbackI deployed a new snapshot : 2.7-20090427.230850-4
It includes the fixe for
MECLIPSE-455<http://jira.codehaus.org/browse/MECLIPSE-455>
 : Invalid dependent module archive name for EJB artifact
*
*
Cheers

Arnaud

On Tue, Apr 21, 2009 at 2:15 PM, Martijn Dashorst <
martijn.dashorst@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
> <ma...@gmail.com> 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 <ah...@gmail.com>
> 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 <aheritier@gmail.com
> >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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Arnaud

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

Posted by Martijn Dashorst <ma...@gmail.com>.
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
<ma...@gmail.com> 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 <ah...@gmail.com> 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 <ah...@gmail.com>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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Martijn Dashorst <ma...@gmail.com>.
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 <ah...@gmail.com> 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 <ah...@gmail.com>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.

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

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

Posted by Arnaud HERITIER <ah...@gmail.com>.
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 <ah...@gmail.com>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

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

Posted by Barrie Treloar <ba...@gmail.com>.
Anything else?

Should we start the release process again then?

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

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

Posted by Jim Sellers <ji...@gmail.com>.
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 <di...@xanthippe.ping.de> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

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

Posted by Dirk Olmes <di...@xanthippe.ping.de>.
>>>> 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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Arnaud HERITIER <ah...@gmail.com>.
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 <jo...@gmx.de>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 <jo...@gmx.de>
> > 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Arnaud

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

Posted by Jörg Schaible <jo...@gmx.de>.
Hi Barrie,

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

> On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaible <jo...@gmx.de>
> 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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Barrie Treloar <ba...@gmail.com>.
On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaible <jo...@gmx.de> 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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Jörg Schaible <jo...@gmx.de>.
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by "ari.meyer" <ar...@gmail.com>.
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 <ar...@gmail.com> 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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Dirk Olmes <di...@xanthippe.ping.de>.
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Kalle Korhonen <ka...@gmail.com>.
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.dashorst@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 <ah...@gmail.com>
> 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.dashorst@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 <resources> 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 <ah...@gmail.com>
> >> 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 <ar...@gmail.com>
> 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-unsubscribe@maven.apache.org
> >> >> For additional commands, e-mail: users-help@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-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

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

Posted by Martijn Dashorst <ma...@gmail.com>.
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 <ah...@gmail.com> 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.dashorst@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 <resources> 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 <ah...@gmail.com>
>> 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 <ar...@gmail.com> 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-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: users-help@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Arnaud HERITIER <ah...@gmail.com>.
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.dashorst@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 <resources> 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 <ah...@gmail.com>
> 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 <ar...@gmail.com> 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-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

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

Posted by Barrie Treloar <ba...@gmail.com>.
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Martijn Dashorst <ma...@gmail.com>.
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
<ma...@gmail.com> 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 <ah...@gmail.com> 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 <ba...@gmail.com> wrote:
>>
>>> On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
>>> <ma...@gmail.com> wrote:
>>> > On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar <ba...@gmail.com>
>>> 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-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@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.
>



-- 
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Martijn Dashorst <ma...@gmail.com>.
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 <ah...@gmail.com> 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 <ba...@gmail.com> wrote:
>
>> On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
>> <ma...@gmail.com> wrote:
>> > On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar <ba...@gmail.com>
>> 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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Arnaud HERITIER <ah...@gmail.com>.
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 <ba...@gmail.com> wrote:

> On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
> <ma...@gmail.com> wrote:
> > On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar <ba...@gmail.com>
> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

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

Posted by Barrie Treloar <ba...@gmail.com>.
On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
<ma...@gmail.com> wrote:
> On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar <ba...@gmail.com> 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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Martijn Dashorst <ma...@gmail.com>.
On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar <ba...@gmail.com> 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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Barrie Treloar <ba...@gmail.com>.
On Wed, May 27, 2009 at 5:17 PM, Martijn Dashorst
<ma...@gmail.com> 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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Martijn Dashorst <ma...@gmail.com>.
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 <ba...@gmail.com> wrote:
> On Wed, May 27, 2009 at 3:58 PM, Martijn Dashorst
> <ma...@gmail.com> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Barrie Treloar <ba...@gmail.com>.
On Wed, May 27, 2009 at 3:58 PM, Martijn Dashorst
<ma...@gmail.com> 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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Martijn Dashorst <ma...@gmail.com>.
On Wed, May 27, 2009 at 1:17 AM, Barrie Treloar <ba...@gmail.com> wrote:
> On Tue, May 26, 2009 at 11:03 PM, Martijn Dashorst
> <ma...@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?
>
> 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 <resources> 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 <resources> 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 <resources>
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Barrie Treloar <ba...@gmail.com>.
On Tue, May 26, 2009 at 11:03 PM, Martijn Dashorst
<ma...@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?

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 <resources> 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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Martijn Dashorst <ma...@gmail.com>.
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 <resources> 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 <ah...@gmail.com> 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 <ar...@gmail.com> 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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Arnaud HERITIER <ah...@gmail.com>.
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 <ar...@gmail.com> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

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

Posted by "ari.meyer" <ar...@gmail.com>.
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org