Hi all,
I have a minimal pom defined with my maven eclipse plugin.
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
Hello,
For the problem reported below, I created ticket SCM-609 and provided
a patch. The link to the Github branch is in the ticket. Can someone
review and integrate this in 1.5-SNAPSHOT?
Tnx,
Ringo
On 14 February 2011 16:21, Ringo De Smet ringo.des...@gmail.com wrote:
Hello,
I am re-using
Hi Yusuf,
a couple of notices:
- first of your command line seems wrong as mvn compiler: compile -X has a
whitespace between the compiler (plugin name) and the compile (pluging
goal). Using mvn compiler:compile should work.
- more in general, unless you have any specific needs for invoking plugin
Evening, Morning, Hello,
I'm wondering if their is a roadmap for repository
design/functionality. I'm thinking something along the lines of
Debian's repository structure and standards.
I've been working with Maven since 2005 usually in Off-Line
environments, where Companies question using it
Hi John,
For companies which are this paranoid, perhaps they should not download
artifacts from public repositories at all. Have you considered setting up a
Nexus / Archiva installation which does not connect to any public repos? Then
you can manually deploy any artifacts you wish to this
On Thursday, 17 February 2011, Siegmann Daniel, NY
daniel.siegm...@fja-us.com wrote:
Hi John,
For companies which are this paranoid, perhaps they should not download
artifacts from public repositories at all. Have you considered setting up a
Nexus / Archiva installation which does not
But I cant get rid of the error Project build error: The property name is
required to activate the profile .
What the hell does that mean and how can I avoid it. Its really annoying.
The command I executed from the command line is mvn compiler: compile -X
These kinds of questions should be
the baseline version. Any tips on how I might tackle this would be
greatly appreciated!
You should probably take a look a the Sonar project and their Maven
plugin to see how they are doing similar things, and perhaps Cobertura
as well, and then use that as a basis for some of your own work.
There's also japex.java.net, where I just added a maven plugin.
On Thu, Feb 17, 2011 at 12:38 PM, Wayne Fay wayne...@gmail.com wrote:
the baseline version. Any tips on how I might tackle this would be
greatly appreciated!
You should probably take a look a the Sonar project and their Maven
On 17 February 2011 09:38, Wayne Fay wayne...@gmail.com wrote:
the baseline version. Any tips on how I might tackle this would be
greatly appreciated!
You should probably take a look a the Sonar project and their Maven
plugin to see how they are doing similar things, and perhaps Cobertura
Hi,
Now that the parent POMs are released, let's get some products out there
as well.
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761styleName=Htmlversion=16231
There are still a couple of issues left in JIRA:
+1
Emmanuel
On Tue, Feb 15, 2011 at 9:32 PM, Brian Fox bri...@infinity.nu wrote:
Plugin is staged at:
https://repository.apache.org/content/repositories/maven-009
This release is dependent upon the maven-dependency-analyzer vote and
staged artifacts.
We fixed a boat load of issues:
On 18/02/2011, at 2:56 AM, John Patrick wrote:
Evening, Morning, Hello,
I'm wondering if their is a roadmap for repository
design/functionality. I'm thinking something along the lines of
Debian's repository structure and standards.
I've been working with Maven since 2005 usually in
I for one am not very impressed by the generic 'corporate' bogeyman.
Many people in corporate environments use maven. It's no more or less
scary then any other piece of FOSS. At most, it's a highly efficient
engine for sucking in FOSS, and as such might be viewed as increasing
the risk of a
Issue Subscription
Filter: Design Best Practices (24 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
15 matches
Mail list logo
