Jason Dillon wrote:
Why does it fail the first time?  This seems fishy too...

I'm rebuild again to see what it does, but that is painfully slow...

If we really do depend on a development version of the plugin, then we should either...

  Lobby to get the plugin released

or

  Checkin and manage our own version of that plugin

The later is not ideal, but in an open-source world that we live in, sometimes that is the only option as we need stability and can not always rely on other groups to provide that for us.

 * * *

Also, on a side note, we should explicitly list the versions of maven and mojo plugins that we use. I have run into problems many many times when these teams release new versions of the plugins which effectively break the build.

It is _nice_ that Maven can download the latest and greatest release of artifacts... but since those latest versions might behave differently that the project is configured to use... it will just end up breaking things.

So, don't buy into the "magic" be explicit and tell Maven what version to use.

Seems sensible to me to be explicit as it would also increase the likelihood that builds are repeatable years down the track.

John
--jason


On Jun 26, 2006, at 8:13 PM, Prasad Kashyap wrote:

http://www.mail-archive.com/[email protected]/msg25378.html

On 6/26/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
What the heck is up with the xmlbeans plugin?

I keep getting this from the top-level:

<snip>
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) xmlbeans:xmlbeans-jsr173-api:jar:2.0-dev

   Try downloading the file manually from the project website.

   Then, install it using the command:
       mvn install:install-file -DgroupId=xmlbeans -
DartifactId=xmlbeans-jsr173-api \
           -Dversion=2.0-dev -Dpackaging=jar -Dfile=/path/to/file

   Path to dependency:
         1) org.apache.geronimo.modules:geronimo-j2ee-builder:jar:1.2-
SNAPSHOT
         2) stax:stax:jar:1.1.1-dev
         3) xmlbeans:xmlbeans-jsr173-api:jar:2.0-dev

----------
1 required artifact is missing.

for artifact:
   org.apache.geronimo.modules:geronimo-j2ee-builder:jar:1.2-SNAPSHOT

from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   codehaus-dist (http://dist.codehaus.org),
   Apache CVS (http://people.apache.org/maven-snapshot-repository),
   maven1-ibiblio (http://www.ibiblio.org/maven),
   snapshots (http://snapshots.maven.codehaus.org/maven2),
   apache-cvs (http://cvs.apache.org/repository)


</snip>

But when I build from the directory it is fine and then the top-level
will continue.  Something is horked... not sure why though...

Where did this jsr plugin come from?

--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
>>
>>
>>





Reply via email to