Yes Yoav, the artifactory migration is in the pipeline. You're right. Once we
do that we won't need the workaround anymore.
--
View this message in context:
http://maven.40175.n5.nabble.com/Migration-to-Maven-3-0-1-Deploy-fails-with-Error-500-only-for-top-most-maven-metadata-xml-tp3332094p333287
On Thu, Jan 6, 2011 at 11:27 AM, Phillip Hellewell wrote:
>
> Thanks. Maybe I should take a closer look at NPanday. But given all
> the other custom logic I need, I'm pretty sure I'll still need my own
> plugin.
For anyone who is curious, this is what I ended up using for my plugin:
1. org.cod
Hello
Our svn repos are configured with only trunk/tags/branches
at the top level. If I remember correctly this is recommended
by maven.
I suppose in theory there is no reason not to have other
top level folders as long as maven ignores them.
Is anyone doing this?
Our developers need access to a
You must specify the version of the parent (can't use a property). However,
you don't have to specify the version of the project, it will then use the
version specified for the parent.
/Anders
On Fri, Jan 7, 2011 at 23:48, Thomas Sundberg wrote:
> Hi!
>
> I'm trying to set up up a multi module
Hi!
I'm trying to set up up a multi module project.
My simple approach is this:
4.0.0
se.sigma
aggregation
1.0
pom
foo
bar
./foo:
4.0.0
se.sigma
aggregation
${project.version}
foo
jar
./bar:
You can also upgrade Artifactory to 2.3.0+ which is compatible with the new
format, so you wouldn't need to specify the legacy deployment mode on the
client side.
On Fri, Jan 7, 2011 at 11:28 PM, vratnagiri wrote:
>
> Thanks Ben! That was the problem and setting maven.metadata.legacy=true
> solv
On 2011-01-07 17:14, Gordon Cody wrote:
> Hello List
>
> Svn repositories allow for access permissions to be set at the directory
> level.
>
> Maven seems to expect that developers have access to the entire repository.
What makes you think so?
I use Maven against an SVN repo where I do not have
Thanks Ben! That was the problem and setting maven.metadata.legacy=true
solves it.
--
View this message in context:
http://maven.40175.n5.nabble.com/Migration-to-Maven-3-0-1-Deploy-fails-with-Error-500-only-for-top-most-maven-metadata-xml-tp3332094p3332497.html
Sent from the Maven - Users mailin
> "France3 Franche-Comt?" != "France3 Franche-Comté" only when it is maven 3.
> Not in maven 2 on Hudson, why ?
>
> With JUnit : ok no message
At least in Gmail, those characters come through differently. Are you
sure that they are the same in your tests?
I'm seeing Comt? and Comté. Perhaps Maven
vratnagiri wrote:
Caused by: org.sonatype.aether.deployment.DeploymentException: Failed to
deploy metadata: Could not transfer metadata
com.***.deployment:ThirdPartyDeploymentProject:0.0.1-SNAPSHOT/maven-metadata.xml
from/to deploymentRepoSnapshot
(http://mvn.***.com:8080/artifactory/***-project
Hello,
I'm testing out migration to Maven 3.0.1 from 2.2.1.
All phases run fine except for the deploy phase.
When I first run with 2.2.1, everything runs fine.
Then I make the switch to 3.0.1 and run the same command and everything goes
fine except for the top most maven-metadata.xml file. Wh
Hello List
Svn repositories allow for access permissions to be set at the directory
level.
Maven seems to expect that developers have access to the entire repository.
Is there a way to reconcile these differences such that some people (for
example
junior, qa or non technical people have access o
Sorry.. I'm out of suggestions then.. Hopefully someone else has an idea
On Fri, Jan 7, 2011 at 10:54 AM, Carpentier Xavier (GreenIvory) <
x.carpent...@greenivory.com> wrote:
> Yes I do :
>
> 1.6
> 1.6
> UTF-8
>
>
> --
> Carpentier Xavier
> Ingénieur Développement - x.carpent...@greenivo
"France3 Franche-Comt?" != "France3 Franche-Comté" only when it is maven 3. Not
in maven 2 on Hudson, why ?
With JUnit : ok no message
With maven3 :
---
Test set: com.greenivory.redlion.commons.utils.ProjectConverter
Is there a way to configure logging in a properties file? Something like
log4j.properties?
I would want, for example, to output to a file, in DEBUG level...
Thanks, Csaba
-
To unsubscribe, e-mail: users-unsubscr...@maven.apac
Carpentier Xavier wrote:
I test m3 3.0.2-RC1 and maybe it's regression :
[WARNING] The metadata
/Users/carpentierxqvier/.m2/repository/com/greenivory/redmole/client/commons/com.greenivory.redmole.client.commons/2.3.0-SNAPSHOT/maven-metadata-local.xml
is invalid: Snapshot information corrupted
On Fri, Jan 7, 2011 at 4:49 AM, Carpentier Xavier (GreenIvory)
wrote:
> Hi,
>
> Some differences occur when executing JUnit test between maven 3 in eclipse
> (fail) and JUnit embedded eclipse, hudson maven 2 (ok). Maybe because it's an
> UTF-8 problem.
Could be, I supposed.. Can you share the e
Hi,
Some differences occur when executing JUnit test between maven 3 in eclipse
(fail) and JUnit embedded eclipse, hudson maven 2 (ok). Maybe because it's an
UTF-8 problem.
Has somebody heard about that ?
Twitter @xcapetir
m...@xavier-carpentier.fr
Hi Adrian,
thank you for the fast response! I am using the "manifest-first"
strategy to generate the pom.xml from the eclipse-manifest.
As far as I understand the inheritance of poms I have to reference the
"parent" from the "child" (I had that already working with manually
generated poms).
I
Hi Moritz,
Why don't you simply make a parent pom for all your poms to inherit from?
--
Best Regards,
AdRiAN ShUM
-Original Message-
From: Moritz Maisel [mailto:mai...@sipgate.de]
Sent: Friday, January 07, 2011 4:00 PM
To: users@maven.apache.org
Subject: specify "" section outside p
I have the following directory structure.
.
|-- my-module
| `-- pom.xml
`-- parent
`-- pom.xml
The my-module pom.xml is defined as:
com.mycompany.app
my-app
${test.version}
.../parent/pom.xml
4.0.0
my-module
and the parent pom.xml is defined as:
4.0.0
Hi all,
I am using maven with tycho to build osgi bundles. In my project's
pom.xml I need the following section:
org.sonatype.tycho
tycho-maven-plugin
0.9.0
true
I don't want to repeat that in all my projects, but would rather like to
have that specified in one single place from where
22 matches
Mail list logo