Hi,
I tried building one eclipse RCP Application @
http://mojo.codehaus.org/pde-maven-plugin/examples/simple_product.html .
But the error ---BUILD FAILED - Target `and' does not exist in
this project.is coming.
See the log below...
C:\Documents and
What is the easiest way to prevent maven from building subprojects, which
haven't been modified since last build? I wrote a plugin, executed before
clean:clean, that check the source code changes in submodules and removes
them from MavenProject object, but it does not affect the build at all.
Pretty sure this is because of your folder name (Documents and Settings). Try
placing your fodler name in quotes.
Better still, checkout to D:\projects or some saner named folder ;)
HTH
Pankaj
Ramesh Babu Pokala - TLS, Chennai wrote:
Hi,
I tried building one eclipse RCP
Hi,
I was unable to compile multi directory project... I tried in different
ways (follwed from maven - getting started site) but still did not get
the solution.
I have directory structure like
abc
|
|___src
|
I've searched the archive and Jira, but I don't see the answer to this
one...
Using the 2.2-beta-1 version of assembly:attached
(jar-with-dependencies), I don't get the pom.properties or pom.xml files
that should be in the META-INF folder for the artifact currently being
built (= bad idea).
Hi,
I. Maven Directory Layout
If you follow the 'Getting Started Guide' you should have a directory
structure like the one below:
my-app
|-- pom.xml
`-- src
|-- main
| `-- java
| `-- package1
| `-- package2
| `-- package3
I've got a quick question about repository metadata. If you take a
look at
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
it has all of the versioning information, which makes sense, but it
also has a version tag with a version
Started with Maven1 or Maven2? I assume maven2, in which case your
configuration (the default is for Maven 1) http://www.ibiblio.org/maven is
wrong - it's http://www.ibiblio.org/maven2 and it's enough to throw off
maven-proxy. Happened to me more than once. maven-proxy works fine for
Maven2, but
I'd stay away from Archiva for now, until it gets a little more mature. From
experience I suggest Proximity (I've used all 4... it's the most mature).
Also, point your central repos to http://repo1.maven.org/maven2 ... that's
the official central. Of course, it's not a bad thing to use mirrors,
Hi,
in a plugin, I am attempting to traverse through the projects list of
transitive dependencies like this:
artifactResolver.resolveTransitively( artifacts,
project.getArtifact(),
localRepository, remoteRepositories,
artifactMetadataSource,
10 matches
Mail list logo