Hi
I'm new to Maven plugin M2Eclipse integration. I've imported my plugin
(with custom packaging)
I want to integrate with M2Eclipse and some test projects using this
packaging.
When playing with lifecycle-mapping-metedata.xml (changing actions for
different mojos)
I found that I have to delete
Hi,
We fixed 11 issues. The new feature is the jgit provider (based on jgit).
Details:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527version=18783
Staging repository:
https://repository.apache.org/content/repositories/maven-002/
Staged site:
-1, for the following reasons
* No checksum of the source bundle in the email, per current vote email
format: FTR SHA1 of bundle I checked is
a0fdae255eebc2dfbd0f973073f7c97284b5f9f9.
* The source bundle does not build.
If I look at the difference between the tag and the source bundle I see the
This list is meant to discuss development of maven itself. If you
haven't already, please ask your question of m2e-us...@eclipse.org.
--
Regards,
Igor
On 12/2/2013, 3:06, Grzegorz Słowikowski wrote:
Hi
I'm new to Maven plugin M2Eclipse integration. I've imported my plugin
(with custom
On 2 December 2013 22:34, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
-1, for the following reasons
* No checksum of the source bundle in the email, per current vote email
format: FTR SHA1 of bundle I checked is
a0fdae255eebc2dfbd0f973073f7c97284b5f9f9.
* The source bundle does
On Monday, 2 December 2013, Olivier Lamy wrote:
On 2 December 2013 22:34, Stephen Connolly
stephen.alan.conno...@gmail.com javascript:; wrote:
-1, for the following reasons
* No checksum of the source bundle in the email, per current vote email
format: FTR SHA1 of bundle I checked is
On 3 December 2013 11:18, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On Monday, 2 December 2013, Olivier Lamy wrote:
On 2 December 2013 22:34, Stephen Connolly
stephen.alan.conno...@gmail.com javascript:; wrote:
-1, for the following reasons
* No checksum of the source
Am 03.12.2013, 02:47 Uhr, schrieb Olivier Lamy ol...@apache.org:
For some reasons I don't understand yet why defaultExclude=false
doesn't work for CVS directories.
Uh, isnt that supposed to be yes to enable the exclusion of default
patterns?
Gruss
Bernd
On 3 December 2013 12:52, Bernd Eckenfels e...@zusammenkunft.net wrote:
Am 03.12.2013, 02:47 Uhr, schrieb Olivier Lamy ol...@apache.org:
For some reasons I don't understand yet why defaultExclude=false
doesn't work for CVS directories.
Uh, isnt that supposed to be yes to enable the
I dunno, change the version to 2.0 and remove support for CVS?
On Mon, Dec 2, 2013 at 8:57 PM, Olivier Lamy ol...@apache.org wrote:
On 3 December 2013 12:52, Bernd Eckenfels e...@zusammenkunft.net wrote:
Am 03.12.2013, 02:47 Uhr, schrieb Olivier Lamy ol...@apache.org:
For some reasons I don't
now that:
1. the problem is known
2. its impact estimated low: only tests for CVS provider
IMHO, we can afford releasing as is and creating a Jira issue to find a better
solution later
Regards,
Hervé
Le mardi 3 décembre 2013 12:47:55 Olivier Lamy a écrit :
On 3 December 2013 11:18, Stephen
+1
need to find a workaround for CVS provider unit tests later
Regards,
Hervé
Le lundi 2 décembre 2013 19:38:41 Olivier Lamy a écrit :
Hi,
We fixed 11 issues. The new feature is the jgit provider (based on jgit).
Details:
http://jira.codehaus.org/browse/SCM-737 created
Le mardi 3 décembre 2013 03:05:17 Hervé BOUTEMY a écrit :
+1
need to find a workaround for CVS provider unit tests later
Regards,
Hervé
Le lundi 2 décembre 2013 19:38:41 Olivier Lamy a écrit :
Hi,
We fixed 11 issues. The new
I am trying to stage maven-verifier 1.5 but having some troubles
creating the release tag during release:prepare. The error message I
get shows some odd SVN URL, but I am not sure where it comes from. Here
is the error
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd
It looks the pom contains the wrong scm information:
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-verifier/pom.xml
scm
connectionscm:svn:http://svn.apache.org/repos/asf/maven/shared/tags/maven-verifier-1.5/connection
Sorry guys, during the week I’m usually a bit short in time…
But is ist possible, that my commit d1f102e5223e5fe0f852e1a5becb497f0e860d6a is
actually causing this issue?
Its an exclude of some CVS stuff I had in my untracked list all the time when
doing a full build...
regards Domi
On
Thank you, Olivier, it'd have taken me forever to figure this out by myself!
(I had troubles with svn authentication earlier today and accidentally
committed modified pom.xml while I was troubleshooting it).
--
Regards,
Igor
On 12/2/2013, 23:31, Olivier Lamy wrote:
It looks the pom contains
No worries.
IMHO it's not the problem. Issue is cvs-commons module.
--
Olivier
On Dec 3, 2013 3:34 PM, Dominik Bartholdi d...@fortysix.ch wrote:
Sorry guys, during the week I’m usually a bit short in time…
But is ist possible, that my commit
d1f102e5223e5fe0f852e1a5becb497f0e860d6a is
18 matches
Mail list logo
