At the moment I have no idea which tool is causing the problem. I still have
problems with artifactory 2.3.1. Just a quick question: Does artifactory 2.3.0+
supports the m3 format with both, unique and non-unique repositories? Currently
the build system is running with 2.3.1 and non-unique snaps
We witnessed the same issue here at work. While the latest Maven 2
works properly, our developpers using Maven 3 had the problem and had
to go through the same procedure of deleting the jar within the local
repo.
We, on the other hand, use archiva for our artifact deployement.
It is a major blocke
Hello,
Due to a restructuring in a maven project, I am experiencing problems with
the following POM. I have two classes in the maven project below:
com.jeanbaptistemartin.annotations.MethodLevelAnnotation (an annotation)
com.jeanbaptistemartin.annotations.TestAnnotationsProcessor (my annotation
pro
Hi,
Artifactory 2.3.0+ supports the m3 format for maven-metadata.xml
for snapshot artifacts. But, if you upgraded to 2.3.x and still think there
is something wrong on the Artifactory side, better ask on the Artifactory
user list and we'll be happy to assist you there.
Thanks,
On Wed, Nov 24, 201
The Maven team is pleased to announce the release of the Maven Doxia
Tools shared component, version 1.3
This component assists in using Doxia for site generation and report
creation.
http://maven.apache.org/shared/maven-doxia-tools/
You should specify the version in your project's dependency co
Why not follow the maven way, leave the version in SCM as a SNAPSHOT, and
let hudson do the releases for you... If you object to maven-release -plugin
effectively running the build twice, then switch the preparationGoals to
"validate"
- Stephen
---
Sent from my Android phone, so random spelling m
http://jira.codehaus.org/browse/MRELEASE-621 will be needed to get the hooks
in place for v-m-p... once I have that done (and pushed a m-r-p release)
then I will do the v-m-p stuff (assuming I have got v-m-p's integration
tests portable by then!)
-Stephen
On 24 November 2010 20:02, Stephen Connol
It works very well.
Thanks to both of you!
J.
2010/11/25 Julien Martin
> Thanks Wayne.
> I'll try that and post here according to the results.
> J.
>
> 2010/11/25 Wayne Fay
>
> >war
>> >
>> >
>>
>> A dependency of type war means basica
The problem doesn't occur with Maven 2.2.1 either, so it's related to
something different between 2.2.1 et 3.0.0
Gérald
2010/11/25 Gérald Quintana :
> Hello,
>
> I have just migrated from Maven 2.0.9 to Maven 3.0.0. Everything
> compiles, tests as expected, but it doesn't run. I get some useless
Hello,
I use Hudson with Maven for building my Java Application. I have one
Maven project, where i want to increment automatically the version of
the project in the pom-file everytime when a Hudson-build runs. The
Maven-Release-Plugin isn't suitable in this case because i don't use
Snapshot-version
On Thu, Nov 25, 2010 at 7:49 AM, Ilya Basin wrote:
> WS> Set a property elsewhere in the pom (or further up the hierarchy) and
> WS> use that for both versions: ${foo.version}
>
> I don't know the version of foo-api and foo-impl.
If your project code depends on it, you need to know.
If it's a t
On 11/17/2010 07:36 PM, uwe schaefer wrote:
Hello,
i am sorry, but i am really puzzled about this. the way i get it,
(Snapshots aside) maven, from 2.2 on, does no longer work as documented
here:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
can someone
foo-impl:1.2.3 should depend on foo-api:1.2.3. Then add a dependency
on foo-impl:1.2.3, and you'll get a dependency on foo-api:1.2.3.
Gérald
2010/11/25 Ilya Basin :
> WS> Set a property elsewhere in the pom (or further up the hierarchy) and
> WS> use that for both versions: ${foo.version}
>
> I
Hello,
I would like to use the maven-release-plugin and set a different
release tag without the need of interacting.
Additional I need to use the computed release version as part of the tag.
I tried to configure it like this:
org.apache.maven.plugins
maven-release-plugin
${project.gro
WS> Set a property elsewhere in the pom (or further up the hierarchy) and
WS> use that for both versions: ${foo.version}
I don't know the version of foo-api and foo-impl.
--
-
To unsubscribe, e-mail: users-unsubscr...@maven.a
Vincent,
You're right for ojdbc14 but not for ehcache (tree contains
ehcache-core:jar:2.1.0) and fwk-i18nImpl:jar:1.5.
The effective POM doesn't help me to find the culprit.
Gérald
2010/11/25 Vincent Latombe :
> Hello,
>
> check your dependency:tree again, I can see net.sf.ehcache:ehcache:jar:1
On Thu, Nov 25, 2010 at 6:59 AM, Ilya Basin wrote:
> Now I need to add the foo-impl.jar to my dependencies, and it must be
> the same version as foo-api.jar. How?
Set a property elsewhere in the pom (or further up the hierarchy) and
use that for both versions: ${foo.version}
You'll see this in
Hi. A project indirectly depends on foo-api.jar via some meta artifact
foo-client.
I know the version of this meta artifact, but not the version of
foo-api.jar.
There's also foo-impl.jar that depends on foo-api.jar with the same
version. For example, if foo-client 1.3 depends on foo-api 1.1, I need
Thanks Wayne.
I'll try that and post here according to the results.
J.
2010/11/25 Wayne Fay
> >war
> >
> >
>
> A dependency of type war means basically nothing to Javac. You're
> basically just putting the War file on the classpath and
Hi,
one project = one artifact. You'll get hurt (to various degrees) if you try
to fight that principle.
Here are a few hints to explore though :
- build-helper-plugin to attach additional artifacts to your build
- dependency-plugin to copy/unpack resources from other artifacts
Vincent
2010/11
Hello,
check your dependency:tree again, I can see net.sf.ehcache:ehcache:jar:1.5.0
and com.oracle:ojdbc14:jar:10.2.0.4.0 at least.
I also recommend you to check help:effective-pom to check if these
dependencies didn't get included through your pom hierarchy.
Vincent
2010/11/25 Gérald Quintana
Hi,
we need to create a jar that only contains 2 xml files but nothing more.
Because we have just those 2 files, we don't want to create a new project
for that (especially since Eclipse can't display projects hierarchically).
So the question is:
Is it possible to create a JAR containing those 2
Hello,
I have just migrated from Maven 2.0.9 to Maven 3.0.0. Everything
compiles, tests as expected, but it doesn't run. I get some useless
librairies in my WEB-INF\lib with old versions. Looking in the
dependency tree for the origin of theses dependencies, they are not
present. But they are prese
> I am using maven-jetty-jspc-plugin in my pom to pre-compile jsps. I tried
> the parallel build of maven 3 but it fails for this plugin as its not
> threadsafe. I then tried jspc-maven-plugin also but its not not threadsafe.
> Anybody have any idea about these plugins or any other plugin to pre-co
On Thu, Nov 25, 2010 at 12:24 AM, Moser, Christian wrote:
> I wonder in which specific time/timezone maven 3.0 writes the timestamp
> into maven-metadata for local and remote artifacts? Is it supposed to
> write GMT + 0:0 or the same time set on the local machine, in my case
Maven 2.x writes the
> war
>
>
A dependency of type war means basically nothing to Javac. You're
basically just putting the War file on the classpath and javac doesn't
know how to deal with wars (only jars) so it just gets ignored.
Try again after you package
Hi,
I am using maven-jetty-jspc-plugin in my pom to pre-compile jsps. I tried
the parallel build of maven 3 but it fails for this plugin as its not
threadsafe. I then tried jspc-maven-plugin also but its not not threadsafe.
Anybody have any idea about these plugins or any other plugin to pre-compi
This is a good example of my belief, that it should be possible to
invoke other plugins dynamically by supplying an own configuration
section from your own plugin.
On Thu, Nov 25, 2010 at 6:00 AM, Peter Niederwieser wrote:
> Over time, I have written several Maven plugins that configure other pl
Over time, I have written several Maven plugins that configure other plugins
by manipulating their section (with the Xpp3Dom API). This
technique has often proved to be a life saver. For example, I have a plugin
that determines dynamically which JUnit tests should be run, and configures
Surefire
Over time, I have written several Maven plugins that configure other plugins by
manipulating their section (with the Xpp3Dom API). This
technique has often proved to be a life saver. For example, I have a plugin
that determines dynamically which JUnit tests should be run, and configures
Surefi
30 matches
Mail list logo