Sorry I didn't get to it sooner (got caught away in some deadlines), but I
have opened a JIRA and attached a patch (extremely simple) to fix this. If
someone wants to commit the patch, it will clear away the compiler errors
without overriding the checked-in settings.
The other option, of course,
If you use the subversive plugin you can check out trunk as a project
(e.g. wicket-parent) then run mvn eclipse:eclipse and import existing
projects in the workspace. the plugin will then keep all projects in
sync.
Maurice
On Sat, May 10, 2008 at 5:57 AM, Jeremy Thomerson
[EMAIL PROTECTED]
Well, I'm not sure exactly why the settings are in SVN... I assumed to keep
everyone on the same page, but obviously most developers are overriding them
(or their IDE would bother them with compile errors like mine does).
If one of the committers wants to commit the following patch, new devs can
make a jira issue for that patch
else it will be lost.
Did eclipse report those errors?
Because that would be strange, why dont i have those problems.. You should
use the project settings
Maybe those are not completely correct then and need some more tuning
On Fri, May 9, 2008 at 9:19 AM,
those settings are in SVN at the project level because then everybody uses
the same formatter
and the same kind of settings so that code is not constantly changing
completely if everybody uses
there own After Save actions.
On Fri, May 9, 2008 at 9:19 AM, Jeremy Thomerson [EMAIL PROTECTED]
really?
is the maven eclipse plugin tampering with my project settings!!??
On Fri, May 9, 2008 at 11:28 AM, Maurice Marrink [EMAIL PROTECTED] wrote:
Maven eclipse plugin can sometimes mess with the settings but now they
have this new feature
Yes - Eclipse reported these compiler errors, which is strange because in my
projects, I have the setting for these to appear as a compiler warning.
This means I must be using the settings from SVN or they wouldn't have
immediately appeared as errors.
I do have a theory why they don't appear as
On 5/6/08, Jeremy Thomerson [EMAIL PROTECTED] wrote:
2: Maven error - SimplePageTest is failing in Maven, but when I run it in
Eclipse to see where it is failing, it succeeds (in Eclipse) - any ideas?
Does maven run using java6?
Martijn
--
Buy Wicket in Action: http://manning.com/dashorst
Sorry, here's the error:
Battery: org.apache.wicket.markup.html.basic.SimplePageTest
---
Tests run: 18, Failures: 0, Errors: 1, Time elapsed: 0.331 sec
On 5/6/08, Jeremy Thomerson [EMAIL PROTECTED] wrote:
No - it's using:
java version 1.5.0_13
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05)
Java HotSpot(TM) Server VM (build 1.5.0_13-b05, mixed mode)
Strange. Teamcity runs the build using maven as well and none of
The eclipse settings look to be more for code style enforcement - to make
sure everyone uses the same standards. But, obviously they are overridden
or something on some machines
Jeremy
On Tue, May 6, 2008 at 8:45 AM, James Carman [EMAIL PROTECTED]
wrote:
Should there really be Eclipse
I'm trying to get Eclipse set up to let me do some development on Wicket and
submit some patches, but I have a two questions:
1: Because of the checked-in Eclipse settings, I receive seven of the
following error (each with different class, obviously, all in the test
folder):
The
12 matches
Mail list logo
