Any Help on maven 2
I am not able to use pde-maven-plugin in my existing PDE project?
-Original Message-
From: Singh, Harsimranjit (NSN - IN/Bangalore)
Sent: Monday, January 30, 2012 11:38 AM
To: Maven Users List
Subject: RE: Maven Setup for Existing Plugin Development Project(Eclipse
Ok, I only put the properties needed directly by the pom into a
settings.xml profile and kept everything else in a properties file used for
filtering. That's not so bad.
On Mon, Jan 30, 2012 at 6:58 PM, Shane StClair wrote:
> Ugh...really not a fan of keeping project specific configuration
> prop
Ugh...really not a fan of keeping project specific configuration properties
in a global file like settings.xml (and of course not in the project pom).
That's really the Maven way, eh?
On Mon, Jan 30, 2012 at 4:51 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On 30 January 2012
On 30 January 2012 19:01, Michael Norman wrote:
> Running maven 3.0.4 via m2e (Maven Integration for Eclipse version
> 1.0.100.20110804-1717).
> Here is my pom.xml file:
>
> 2.11
>
> 2.11
> 2.3
>
>
>
>
> junit
> junit
> 4.8.2
> te
On 30 January 2012 20:09, Shane StClair wrote:
> Hello all,
>
> I have a project with a parent pom and child modules. Configuration
> properties are kept in a build.properties file and an overriding
> custom.build.properties. The properties-maven-plugin is defined in the
You are off the reservati
On Tue, Jan 31, 2012 at 5:31 AM, Michael Norman
wrote:
> Running maven 3.0.4 via m2e (Maven Integration for Eclipse version
> 1.0.100.20110804-1717).
>
Google will tell you (
https://www.google.com/search?q=surefire+report+missing+css) that its a
known issue http://jira.codehaus.org/browse/SUREF
Hello all,
I have a project with a parent pom and child modules. Configuration
properties are kept in a build.properties file and an overriding
custom.build.properties. The properties-maven-plugin is defined in the
parent pom to load these properties, and the plugin is inherited by the
child poms.
Running maven 3.0.4 via m2e (Maven Integration for Eclipse version
1.0.100.20110804-1717).
Here is my pom.xml file:
2.11
2.11
2.3
junit
junit
On Mon, Jan 30, 2012 at 4:38 PM, Singh, Harsimranjit (NSN -
IN/Bangalore) wrote:
> Hi
>
> I have to use maven and that maven 2 only so option left
Why Maven 2 only?
Maven 3 should be backwards compatible for your needs.
> 1) Upgrade to latest version of Eclipse PDE:
> Can you explain about this
Am 30.01.2012 17:46, schrieb Maven User:
> I think the difference between the drools plugin and what I'm trying to do
> is, I'm trying to manage several different maven modules that are released
> together, but live in different repositories.
>From my experience, this does not work. If you want to
Hi all,
I'm writing a plugin which analyzes the dependencies of a large project
consisting of loosely related maven projects. In this plugin, I need the
remoteProjectRepositories in a plexus component. I'm using the plexus
annotation @Component(...) to indicate my class is a component, plus
JFrog'
Hi Alec,
I was wondering if I could build a repository on a server here and make it
> available to all the machines that will build the project. Basically, a
> local version of the maven global repository. Is that a good approach?
>
Yes, this is exactly what Repository Managers like Nexus and
Hello,
I'm new to maven so this may be a bad question. If so, please forgive me.
I'm building a project that includes a lot of jars that are given to me by
other groups but that are not in the maven remote repository, there are several
of us all working on the same project so for each of us to
Cool -
Here's the exact error:
hg commit --message "[maven-release-plugin] prepare release
some-new-tag-cool-jar-aggregate-1.0" C:\views\buildsource\jar-A\pom.xml"
abort: C:\views\buildsource\jar-A\pom.xml not under root
I think the difference between the drools plugin and what I'm trying to do
Hello,
have a look at updatePolicy:
http://maven.apache.org/settings.html#Repositories
Cheers,
Guillaume
Le 30/01/2012 14:21, frank.ja...@tolina.de a écrit :
Hello,
we shortly switched our company's infrastructure to maven and are now
experiencing a strange behaviour of dependency resolutio
Hello,
we shortly switched our company's infrastructure to maven and are now
experiencing a strange behaviour of dependency resolution.
Say my.project:1.0.0 requires my.cool.component:jar:3.7.0 and I try to
build my.project:1.0.0 before the dependency was deployed to my central
repository, my
16 matches
Mail list logo