+1 (non binding)
-Chris
+1
2012/6/12 Robert Scholte :
> Hi,
>
> We solved 7 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144&version=18564
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11144&status=1
>
> Staging repo:
>
Hi Hervé,
this already looks better, but I'm still a bit surprised be the result.
After removing all maven-plugin-api's I got this result:
E:\java-workspace\codehaus-mojo\idlj-maven-plugin>mvn
org.apache.maven.plugins:maven-project-info-reports-plugin:2.5-SNAPSHOT:dependencies
[INFO] Scanning
> I have two projects as follows, in neighbouring directories on the filesystem:
> * project_a (-SNAPSHOT)
> * project_b (-SNAPSHOT, depends on project_a)
This list is dedicated to discussion of the ongoing development of Maven itself.
Please post your question(s) on the Maven Use
+1
Op Tue, 12 Jun 2012 18:32:58 +0200 schreef Robert Scholte
:
Hi,
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144&version=18564
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11144&st
The Eclipse plugin currently has a "workspace" configuration option.
This option directs the plugin to figure out
repo-artifact-to-Eclipse-project dependency substitutions by analyzing
the existing projects in the specified Eclipse workspace.
Rather than have the Eclipse plugin figure out these su
I have two projects as follows, in neighbouring directories on the filesystem:
* project_a (-SNAPSHOT)
* project_b (-SNAPSHOT, depends on project_a)
I'd like to build project_b and for Maven to discover that project_a exists on
the filesystem and thus build it rather than look in
