Re: Unable to build using m2

Mon, 26 Jun 2006 19:15:44 -0700 

FYI... if I comment the openejb/modules and `mvn install` I get:

<snip>
[INFO] ------------------------------------------------------------------------ 
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------ [INFO] 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.geronimo.plugins - DartifactId=geronimo-packaging-plug 
in \
        -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)
</snip>
I'm also a little bit mystified as to why we are managing versions of modules that we build with properties in each module. There should be one <version> tag in the top-level module, and all children omit this tag and pick it up be inheritance. The added properties and tag configuration is just adding extra complexity to the build with no reason. I understand that some of this might be legacy picked up from exp using m1, but m2 is a different beast and IMO we should drop any of the m1-isms whenever possible/prudent.
Also, why is the main-build using 1.2-SNAPSHOT and the plugin is 1.2.0? This all seems kinda fishy to me.
And, I don't see any reason why the root pom needs to define properties and then use those properties for each and every dependency in the dependencyManagement section. I believe that when a version number is used more than once, say for the spring jars that it is easier/better to manage a single property that is used by all of the dependencies. But to force all dependencies to use these properties when the property is used in only one place is added overhead which means more complex and fragile builds when configuration changes. 

--jason


On Jun 26, 2006, at 6:46 PM, Prasad Kashyap wrote:


I'm sorry but I'm confused about this main build and the plugins
build. I thought they are all one single build like we did in m1 with
all the new(xx).

This is how the build order is specified in the geronimo/pom.xml

<modules>
    <module>modules</module>
     <module>m2-plugins</module>
     <module>applications</module>
     <module>openejb/modules</module>
     <module>configs</module>
     <module>assemblies</module>
<modules>

There's no cyclical dependency there.


Jason, as for the <relativePath>, I tried that. It didn't help. Also,
the default value of <relativePath> is ../pom.xml anyways.

Cheers
Prasad




On 6/26/06, Jason Dillon <[EMAIL PROTECTED]> wrote:

FYI, seems that you need to build trunk first (probably until it
fails with a missing plugin), then build the plugins, then rebuild
trunk.  Just building m2-plugins pukes with:

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

Missing:
----------
1) org.apache.geronimo.modules:geronimo-deploy-tool:jar:1.2-SNAPSHOT

   Try downloading the file manually from the project website.

   Then, install it using the command:
       mvn install:install-file -DgroupId=org.apache.geronimo.modules
-DartifactId=geronimo-deploy-tool \
-Dversion=1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/ file 

   Path to dependency:
         1) org.apache.geronimo.plugins:geronimo-packaging-
plugin:maven-plugin:1.2.0
         2) org.apache.geronimo.modules:geronimo-deploy-tool:jar:1.2-
SNAPSHOT

2) org.apache.geronimo.modules:geronimo-kernel:jar:1.2-SNAPSHOT

   Try downloading the file manually from the project website.

   Then, install it using the command:
       mvn install:install-file -DgroupId=org.apache.geronimo.modules
-DartifactId=geronimo-kernel \
-Dversion=1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/ file 

   Path to dependency:
         1) org.apache.geronimo.plugins:geronimo-packaging-
plugin:maven-plugin:1.2.0
2) org.apache.geronimo.modules:geronimo-kernel:jar:1.2- SNAPSHOT
3) org.apache.geronimo.modules:geronimo-service-builder:jar:1.2- SNAPSHOT 

   Try downloading the file manually from the project website.

   Then, install it using the command:
       mvn install:install-file -DgroupId=org.apache.geronimo.modules
-DartifactId=geronimo-service-builder \
-Dversion=1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/ file 

   Path to dependency:
         1) org.apache.geronimo.plugins:geronimo-packaging-
plugin:maven-plugin:1.2.0
         2) org.apache.geronimo.modules:geronimo-service-builder:jar:
1.2-SNAPSHOT

4) org.apache.geronimo.modules:geronimo-system:jar:1.2-SNAPSHOT

   Try downloading the file manually from the project website.

   Then, install it using the command:
       mvn install:install-file -DgroupId=org.apache.geronimo.modules
-DartifactId=geronimo-system \
-Dversion=1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/ file 

   Path to dependency:
         1) org.apache.geronimo.plugins:geronimo-packaging-
plugin:maven-plugin:1.2.0
2) org.apache.geronimo.modules:geronimo-system:jar:1.2- SNAPSHOT 

----------
4 required artifacts are missing.

for artifact:
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),
   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>

Looks like bad news... if the main build needs the plugin, and the
plugin needs the main build, and m2 won't let it all run/build at the
same time due to its plugin resolution fluff.

May need to provide a bootstrap, which builds a few select modules,
then the entire system... but that is not very friendly either.

  * * *

Also, start adding <relativePath>../pom.xml</relativePath> to the
parent element, so that you can skip the mvn -N install bits.

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