|Re: [m2eclipse-user] m2eclipse 0.9.4 candidate [message #9609]
||Fri, 30 May 2008 23:21
Originally posted by: igor.ifedorenko.com|
We just posed second 0.9.4 release candidate to the dev update site at
Compared to the first 0.9.4 release candidate, this build only contains
fixes to restore compatibility with Eclipse 3.2. Please give this new
build a try.
Eugene Kuleshov wrote:
> We posted m2eclipse release 0.9.4 candidate to the dev update site at
> The most significant changes are around default project configuration
> (there is no /target-eclipse folder anymore) and Maven settings .
> User settings location is now not editable and it is always taken from
> ~/.m2/settings.xml (same as for Maven CLI) and global settings either
> taken from specified location (similarly to -s option in Maven CLI), or
> if not specified and External Maven installation is chosen as default,
> then settings are taken from its conf/settings.xml. Everything working
> the same way as in Maven CLI.
> You can see new features and improvements on New and Noteworthy page
>  and list of fixed bugs in JIRA .
> We will appreciate if you'd try this and give us feedback. If there
> won't be any major issues we are planning to release 0.9.4 version on
>  http://docs.codehaus.org/display/M2ECLIPSE/Maven+Settings
>  http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworth y
>  http://tinyurl.com/6rutmz
|Re: m2eclipse 0.9.4 released [message #9699 is a reply to message #9678]
||Fri, 06 June 2008 11:45
Originally posted by: ossipetz.myrealbox.com|
thanks for the reply. i think the mentioned configuration does not work
(eclipse 3.3 started with java 5 jdk, m2eclipse 0.9.3, one jdk 1.4
configured in eclipse)
i run into a class version exception:
(Unsupported major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.security.SecureClassLoader.defineClass(SecureClassLoade r.java:123)
at java.security.AccessController.doPrivileged(Native Method)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274 )
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302 )
Exception in thread "main"
as soon as the project is configured with a jdk 1.5 things work. should
i try to make an example project and report it in jira or is it kinda
obvious whats going on?
thanks a lot
Eugene Kuleshov schrieb:
> ossipetz wrote:
>> what decision was made concerning the java version required for 0.9.4?
> Starting from 0.9.4, m2eclipse require Eclipse to run on Java 5.
>> http://docs.codehaus.org/display/M2ECLIPSE/Requirements still states
>> 1.4 but on the m2eclipse mailinglist it was mentioned java 1.5 is a
> Thanks for catching that. I've updated wiki page to clarify required
> Java runtime.
>> (so proects based on 1.4 should stick with 0.9.3?)
> Not really. You need to run Eclipse on Java 5, but you can add any JRE
> in your Eclipse at Window / Preference... / Java / Installed JREs and
> you can have non-Java 5 JRE set as default there or in your projects
> configurations (actually in maven-compiler-plugin settings in pom.xmls
> if you will be using Maven project configurators).
|m2eclipse 0.9.5 released [message #11533 is a reply to message #9609]
||Fri, 18 July 2008 21:31
| Eugene Kuleshov
Registered: July 2009
We are glad to announce 0.9.5 release of m2eclipse, which can be|
installed from the update site at http://m2eclipse.sonatype.org/update/
This release includes number of bug fixes and the most notable new
feature is the form-based editor for Maven pom.xml. You can see more
details for new features and improvements on New and Noteworthy page 
and list of fixed bugs in JIRA .
Please note that POM editor is still in an incubation state and may
have some glitches, but we believe it is already solid enough for a
daily use. Here is a few examples of the features provided by the POM
* support of the full POM schema, including Maven profiles
* integrated code assistance and Maven repository search for Maven artifacts
* hyperlinking between POMs, including dependencies, plugins, parent
* hyperlinking to the artifacts and Maven plugin project pages
* hyperlinking to xml configuration for Maven plugins from the form
* interactive dependency hierarchy and dependency graph viewers
* viewing effective pom for any Maven POM
* viewing POMs from local Maven repository, as well as from
CVS, SVN and other sources in the IDE
There is a known issue when form is not updated after making changes
on the XML source tab and it can be worked around by using "Refresh"
action from the top right hand corner of the POM editor.
We also would like to thank everyone who helped us with this release,
including early feedback, bug reports, test projects, discussions in
the mailing list and the news group. We appreciate all of it, but
especially the time it takes to create test projects, etc. that allow us
to reproduce a bug. As always, bug reports and feature requests are
welcome in the project issue tracker .
 http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworth y
Powered by FUDForum
. Page generated in 0.01733 seconds