I am trying to write some TCK test cases for a new provider and I keep
hitting an error at ScmTestCase.assertFile(). As far as I can see, this
method asserts that the contents of a file equals the file's name (?). And
ScmTckTestCase is using this method in setUp() to assert on '/pom.xml' whose
Ralph Goers schrieb:
On May 12, 2009, at 9:30 PM, Christian Schulte wrote:
Ralph Goers schrieb:
Imagine that you could get a pom.xml for all of Apache Commons that
contained the dependency management for it. Every time a commons
project released a new Commons bill of materials would go with
On Tue, May 12, 2009 at 11:01 PM, Joerg Hohwiller jo...@j-hohwiller.dewrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Milos,
relying on the reactor and giving up on being able to build the one
project
separately is very bad (read: completely breaks) any IDE integration.
I
On May 12, 2009, at 7:02 PM, Ralph Goers wrote:
On May 12, 2009, at 6:20 PM, David Jencks wrote:
On May 12, 2009, at 3:43 PM, Ralph Goers wrote:
On May 12, 2009, at 2:43 PM, Brian Fox wrote:
As I already said, I talked about release-plugin and my view of
the world
and it seems
Hi
You may have noticed discussion on user list about checkstyle plugin to
upgrade to checkstyle 5.
(http://jira.codehaus.org/browse/MCHECKSTYLE-105)http://jira.codehaus.org/browse/MCHECKSTYLE-105
Such upgrade would require Java5 as plugin runtime.
What's the best option here ?
- upgrade
Hi John,
I just came across that same issue as reported before:
http://www.mail-archive.com/dev@maven.apache.org/msg80592.html
There is no conclusion in this thread (apart from that it works with maven 2.1,
which I verified) and I haven't found a jira, did I miss it or should I open one?
Hi developers
I was wondering if there is a schedule for the maven-ejb-plugin 2.2
release?
All issues are closed since month, none has been created and our project
is waiting for an official release to solve one of the issues fixed in the
2.2 SNAPSHOT version.
thanks
Michael
Michael
On May 13, 2009, at 12:53 AM, David Jencks wrote:
I'm even more mystified and understand how you want to use scm even
less. One of the basic principles I have for scm is that stuff
shouldn't be duplicated, in the sense that if some artifact is
released at version 1.2.3.4 say, the scm
On May 13, 2009, at 7:02 AM, Ralph Goers wrote:
On May 13, 2009, at 12:53 AM, David Jencks wrote:
I'm even more mystified and understand how you want to use scm even
less. One of the basic principles I have for scm is that stuff
shouldn't be duplicated, in the sense that if some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
[cut.]
Sorry I wasn't more specific last night at 2:00 am :-). I need more scm
context to understand. I'm assuming something like svn with
+tags
+root-1.0 (1.0)
+A(1.0)
\B(1.0)
+root-1.1 (1.1)
+A(1.0)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Milos,
mvn eclipse:eclipse does perform a build (partially) and might even produce
1 eclipse project for multiple maven projects (correct me if I'm wrong)
No it does not. But I hope it will one finest day.
And it will definitely do NOT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ralph,
I've been promised by Jason that the work on Maven 3 is going to fix
some of these issues. I simply haven't had the time to look at the work
on Maven 3 and even if I had, it has been changing at a fairly rapid
pace for months.
On May 13, 2009, at 10:41 AM, David Jencks wrote:
Sorry I wasn't more specific last night at 2:00 am :-). I need more
scm context to understand. I'm assuming something like svn with
+tags
+root-1.0 (1.0)
+A(1.0)
\B(1.0)
+root-1.1 (1.1)
+A(1.0)
\B(1.1)
\root-1.2 (1.1)
On May 13, 2009, at 12:33 PM, Joerg Hohwiller wrote:
Okay. So thats what I guessed when I said that the MavenProject/
Model is
just a stupid POJO and various plugins manipulate it with side
effects.
Sounds a little hacky to me but thats the way it is. So my
serialization
idea is nuts
On May 13, 2009, at 12:55 PM, Ralph Goers wrote:
On May 13, 2009, at 10:41 AM, David Jencks wrote:
Sorry I wasn't more specific last night at 2:00 am :-). I need
more scm context to understand. I'm assuming something like svn with
+tags
+root-1.0 (1.0)
+A(1.0)
\B(1.0)
+root-1.1
Ralph Goers schrieb:
So the tree really looks like:
+tags
+root-1.0 (trunk revision 1)
+A(1.0)
+B(1.0)
+root-1.1 (trunk revision 2)
+A(1.0)
+B(1.1)
+root-1.2 (trunk revision 3)
+A(1.0)
+B(1.2)
/trunk at revision 4
+root(1.2-SNAPSHOT)
On May 13, 2009, at 5:09 PM, Christian Schulte wrote:
Ralph Goers schrieb:
So the tree really looks like:
+tags
+root-1.0 (trunk revision 1)
+A(1.0)
+B(1.0)
+root-1.1 (trunk revision 2)
+A(1.0)
+B(1.1)
+root-1.2 (trunk revision 3)
+A(1.0)
+B(1.2)
/trunk at
17 matches
Mail list logo
