I've set my new project with dependency to springframework [2,)
I expect maven to get the latest 2.0.2 version.
This fails. the
maven-metadata.xmlhttp://repo1.maven.org/maven2/org/springframework/spring-jdbc/maven-metadata.xml
has not been updated since 2.0-m4.
As those jars are in sync with
On 17 Feb 07, at 7:35 AM 17 Feb 07, nicolas de loof wrote:
I've set my new project with dependency to springframework [2,)
I expect maven to get the latest 2.0.2 version.
This fails. the
maven-metadata.xmlhttp://repo1.maven.org/maven2/org/
springframework/spring-jdbc/maven-metadata.xml
has
Dan Tran wrote:
you hit the limit of windows path which is 256 chars :-)
Try to set your checkout directory to the shorttest and see if it helps
( ie
c:/t )
What confuses me is that both the native svn command line client, and
tortoisesvn, are capable of checking this same directory out
in your msg
checkout\alchemy-quant\src\matlabdevelopment\Toolbox\CreditDerivatives\ParRecovHazardRateTreeModel\UnexposedCode\.svn\tmp\text-base\GetCalibratedOneFactorHullWhiteHazardRateTreeFromCdsSpreadsRP.m.svn-base
I has 205 not counting the parent dir oabove 'checkout/'
so you mean you
we sync from https://svn.sourceforge.net/svnroot/springframework/repos/repo/
and they don't have metadata.
Their jira is in
http://opensource.atlassian.com/projects/spring
If they provide the metadata make sure they start with what is in central now.
We still have the problem with upload
Would it perhaps be sufficient to add a skip configuration to all
plugins, such that you could declare the plugin the parent, and then
add a skiptrue in the plugin definition in the children which would
cause that plugin to be skipped for that specific child/module?
Just trying to think of some
Issue Subscription
Filter: Design Best Practices (37 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
Hi Wendy,
Somebody will correct me if i'm wrong ;) but the convention for
closing jira issues is to assign to yourself, and if there's no needed
work, like this case, it wouldn't be fixed (or it'll show up in the
changelog) but one of the others won't fix, incomplete or cannot
reproduce
On
On 2/17/07, Carlos Sanchez [EMAIL PROTECTED] wrote:
Somebody will correct me if i'm wrong ;) but the convention for
closing jira issues is to assign to yourself, and if there's no needed
work, like this case, it wouldn't be fixed (or it'll show up in the
changelog) but one of the others won't
It's been a little bit more than 72 hours, here are the results:
+1 (5): Jason Dillon, Jason van Zyl, Stephane Nicoll, Vincent
Siveton, Arnaud Heritier
+0 (0)
-1 (0)
I'm not sure who's vote is binding or not, so I just put them all
together. My assumption is that this is a passing vote.
Hi Jason,
On Feb 16, 2007, at 7:36 PM, Jason van Zyl wrote:
On 16 Feb 07, at 4:43 PM 16 Feb 07, Eric Brown wrote:
Hi Jason,
On Feb 16, 2007, at 5:29 AM, Jason van Zyl wrote:
[snip]
Project with full test cases that can be easily absorbed will
be taken before anything else anything else.
On 2/17/07, Eric Brown [EMAIL PROTECTED] wrote:
It took me a bit to figure out the example(s). I went to the maven
wiki to add a page about writing tests, but I don't have write
permission.
Try this one instead:
http://docs.codehaus.org/display/MAVENUSER
--
Wendy
No, I don't think so - I wonder if it is using the wrong local
repository?
I used the Maven builder helper to obtain it, which should use the
same location.
- Brett
On 16/02/2007, at 10:33 PM, Stephane Nicoll wrote:
I have also the following situation for the company pom.
My company
On 17 Feb 07, at 7:02 PM 17 Feb 07, Jason Dillon wrote:
It's been a little bit more than 72 hours, here are the results:
+1 (5): Jason Dillon, Jason van Zyl, Stephane Nicoll, Vincent
Siveton, Arnaud Heritier
+0 (0)
-1 (0)
I'm not sure who's vote is binding or not, so I just put them all
Hi,
Can folks take a look at:
http://jira.codehaus.org/browse/doxia
And see if there are any pressing issues for 1.0-alpha-9 as I would
like to release it so that I can fix and release the site plugin.
Thanks,
Jason.
-
Hi,
For anyone attempting to use the repositorytools plugin for copying
plugin releases be aware that it is currently not updating the plugin
metadata file to bump it to the latest release when merging the
metadata. I've notified Tom, he's looking into it. You have just have
to prepare
Thanks Jason!
--jason
On Feb 17, 2007, at 6:19 PM, Jason van Zyl wrote:
On 17 Feb 07, at 7:02 PM 17 Feb 07, Jason Dillon wrote:
It's been a little bit more than 72 hours, here are the results:
+1 (5): Jason Dillon, Jason van Zyl, Stephane Nicoll, Vincent
Siveton, Arnaud Heritier
+0
Hey, looks like something is whack, the 2.2 pom is empty:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-rar-
plugin/2.2/maven-rar-plugin-2.2.pom
--jason
On Feb 17, 2007, at 6:19 PM, Jason van Zyl wrote:
On 17 Feb 07, at 7:02 PM 17 Feb 07, Jason Dillon wrote:
It's
Can you please copy this:
http://people.apache.org/~jvanzyl/staging/maven-rar-plugin/org/
apache/maven/plugins/maven-rar-plugin/2.2/maven-rar-plugin-2.2.pom
to this:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-rar-
plugin/2.2/maven-rar-plugin-2.2.pom
--jason
On
Done.
On 17 Feb 07, at 11:13 PM 17 Feb 07, Jason Dillon wrote:
Can you please copy this:
http://people.apache.org/~jvanzyl/staging/maven-rar-plugin/org/
apache/maven/plugins/maven-rar-plugin/2.2/maven-rar-plugin-2.2.pom
to this:
20 matches
Mail list logo
