Hmm..actually, in most cases it's even easier than that. I hadn't
noticed, but the root apache parent pom now defines and enables the
snapshot repository by default *for dependencies*. So normally there is
nothing to do (and I've tested this).
But at the moment, as your error message shows, there is a
snapshot-level *plugin* required to build tomahawk. And the root apache
pom does not enable the snapshot repo for plugins, just for dependencies.
So it is still necessary to add the apache snapshot repo to your
~/.m2/settings.xml, at least in this case.
Stick the following in your ~/.m2/settings.xml file:
<profiles>
<profile>
<id>apache.snapshots.profile</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<repositories>
<repository>
<id>apache.org</id>
<name>Maven Snapshots</name>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>apache.org</id>
<name>Maven Plugin Snapshots</name>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
Regards,
Simon
[EMAIL PROTECTED] schrieb:
Not true, Matthias.
One way to build tomahawk is to check out the root of the tomahawk
project, and build it all. But even that will probably not work
because tomahawk trunk can depend on myfaces trunk etc.
The right solution is to add the myfaces snapshot repository to your
~/.m2/settings.xml file. This is described on the wiki somewhere. Then
you can build just one module without problems. The snapshot repo
lives at:
http://people.apache.org/repo/m2-snapshot-repository
This snapshot repo cannot be defined in the pom.xml (well, at least it
must never be defined in any actual release). I guess we could add it
as a profile, though, and have that profile not enabled by default.
Probably not a lot easier though...
Regards,
Simon
Matthias Wessendorf schrieb:
That was already discussed.
You need to build everything... in order to build something from
(tomahawk) trunk
-M
On Tue, Jul 22, 2008 at 5:29 PM, Gertjan van Oosten <[EMAIL PROTECTED]>
wrote:
Hi devs!
I'm having some trouble getting Tomahawk to build (see also
TOMAHAWK-1304).
Since I was unable to find any documentation about how to set up a
local
Tomahawk development environment, I'm trying my luck...
I've checked out myfaces/tomahawk/trunk/assembly now, and I am able to
install that into my local repository using:
mvn -N -Dmyfaces-shared.version=2.0.7 install
Is that the correct command to use? If not, what is it (and is there
some documentation somewhere where I can read about this and more)?
Then, after checking out myfaces/tomahawk/trunk/core, I am unable to
build that because of the following error:
[INFO] A required plugin was not found: Plugin could not be found -
check that the goal name is correct: Unable to download the artifact
from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file
-DgroupId=org.apache.myfaces.buildtools
-DartifactId=myfaces-builder-plugin \
-Dversion=1.0.1-SNAPSHOT -Dpackaging=maven-plugin
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the
file there: mvn deploy:deploy-file
-DgroupId=org.apache.myfaces.buildtools
-DartifactId=myfaces-builder-plugin \
-Dversion=1.0.1-SNAPSHOT -Dpackaging=maven-plugin
-Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
org.apache.myfaces.buildtools:myfaces-builder-plugin:maven-plugin:1.0.1-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
What now?
Kind regards,
--
-- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15
2191 600
