Title: Message Title
Lennart Jörelid commented on an issue
Title: Message Title
Lennart Jörelid commented on an issue
The 2.0 release was cancelled, and since some features were added and some
code was refactored in the plugin I felt it better to release version 2.1
instead.
If someone who actually uses Eclipse feels like pinpointing the problem
with why the m2e descriptor below does not work with the 2.x branch,
Title: Message Title
Anders Hammar commented on an issue
As I earlier stated, after some investigation, there is some other change
in the code that causes this to stop functioning. It worked in v1.x, but
after your refactoring it doesn't any more. IMHO it's very unfortunate to
just ignore such a key feature for anyone on Eclipse, especially as it
worked
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Marek Winkler commented on an issue
Title: Message Title
Lennart Jörelid commented on an issue
Title: Message Title
Lennart Jörelid edited a comment on an issue
Title: Message Title
Lennart Jörelid updated an issue
I am somewhat split about the concept of doing special development within a
Maven plugin project to support any of the IDEs in the development
community.
An IDE claiming a tooling integration with Maven ought to be able to use
the POM and the plugin descriptors out of the box. This seems certainly
Hello all,
Is the process described at
http://mojo.codehaus.org/development/performing-a-release.html
still valid for release?
--
--
+==+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - K
The vote has passed by lazy consensus.
I'll continue with the release.
Kind regards
Karl Heinz Marbaise
On 4/25/15 10:13 PM, Karl Heinz Marbaise wrote:
Hi,
I'd like to release version 2.2 of the Versions Maven Plugin
We solved 19 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?pro
Yes. If Codehaus hasn't started to disable some of those things.
But Nexus@Codehaus is supposed to stay longer, and that's the main part of
the release, that should be OK.
Try mvn site-deploy on the site project for example to test you're still
allowed to deploy the maven site.
Don't really know
Thanks, Baptiste.
:)
I'll go ahead and start the release.
2015-04-29 21:43 GMT+02:00 Baptiste Mathus :
> Yes. If Codehaus hasn't started to disable some of those things.
> But Nexus@Codehaus is supposed to stay longer, and that's the main part
> of the release, that should be OK.
>
> Try mvn si
Hi Lennart,
I often curse the day when I out of good will decided to support M2E in my
Maven plugin (I am a happy user of IntelliJ IDEA), but hopefully my experience
helps you.
Note that in M2E prior to 1.5 there was a major classloading issue, which broke
quite a few plugins.
I took a look a
Title: Message Title
Dan Tran updated an issue
Title: Message Title
Dan Tran created an issue
Title: Message Title
Dan Tran updated an issue
Technically there is no need for 1) and 2) to make it m2e compatible. The
jaxb2 plugin used to be m2e compatible through 3) and a home-grown
staleness check instead of 1) and 2).
/Anders
On Wed, Apr 29, 2015 at 11:35 PM, Sergei Ivanov
wrote:
> Hi Lennart,
>
> I often curse the day when I out of
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
22 matches
Mail list logo