It's clear to me that we need to break out our plugins build and get the
plugins published ASAP. I asked this in another thread, what will it
take to get this published? I don't think that it's too much trouble,
just an RTC to break the plugin out and then we just start publishing
the snapshots. We can shoot for a plugin release around the time of G
v1.2.0>
Regards,
Alan
Jason Dillon wrote:
IMO we should have a completely separate tree for our build support
tools. And once the plugins are stable we release them, until they
are stable we make regular snaps, so that the main tree(s) can just
build w/o having to worry about building plugins first.
--jason
On Jun 26, 2006, at 1:05 PM, Prasad Kashyap wrote:
Alan,
You'd have to build the geronimo-packaging-plugin manually first. It's
under geronimo/m2-plugins
cd geronimo/m2-plugins
mvn clean
mvn -N
mvn
Cheers
Prasad
On 6/25/06, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
I get this error:
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.geronimo.plugins
-DartifactId=geronimo-packaging-plugin \
-Dversion=1.2.0 -Dpackaging=maven-plugin -Dfile=/path/to/file
org.apache.geronimo.plugins:geronimo-packaging-plugin:maven-plugin:1.2.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
codehaus-dist (http://dist.codehaus.org/mojo/m2-snapshots),
snapshots (http://snapshots.maven.codehaus.org/maven2)
org.apache.geronimo.plugins:geronimo-packaging-plugin:maven-plugin:1.2.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
codehaus-dist (http://dist.codehaus.org/mojo/m2-snapshots),
snapshots (http://snapshots.maven.codehaus.org/maven2)
Regards,
Alan
