You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Steve Vinoski <VI...@iona.com> on 2006/11/12 18:40:47 UTC

[java] mvn branch

Under branches/mvn is a first cut at building and testing the java  
code with maven. I would appreciate it if others could checkout the  
branch and try it, especially on platforms other than OS X. All  
feedback welcomed.

BTW, be sure to get "mvn" and not "maven" as the latter is an old  
branch that doesn't work and needs to go away.

--steve

Re: [java] mvn branch

Posted by Daniel Kulp <da...@iona.com>.
Steve,

On Sunday November 12 2006 12:40 pm, Steve Vinoski wrote:
> Under branches/mvn is a first cut at building and testing the java
> code with maven. I would appreciate it if others could checkout the
> branch and try it, especially on platforms other than OS X. All
> feedback welcomed.
>
> BTW, be sure to get "mvn" and not "maven" as the latter is an old
> branch that doesn't work and needs to go away.
>
> --steve

One note:
Your builds would be a bit faster if you remove the "repositories" section 
from the top level pom as it wouldn't connect to them to download stuff 
before connecting to central.

The two you have:
java.net - all the non-plugin stuff is synced to central everyday. (might 
be every 4 hours, the maven folks have been moving to a 4 hour sync 
window)  Thus, unless you need something released immediately, you 
shouldn't need this.

apache.snapshots -  Right now, the only SNAPSHOTs you are grabbing are the 
plugins (for surefire), but those are grabbed from the pluginRepositories 
section.   You can probably comment this out for now.   If you need a 
snapshot for mina, then you would have to leave this.

Enjoy!
-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194   F:781-902-8001
daniel.kulp@iona.com

Re: [java] mvn branch

Posted by Carl Trieloff <cc...@redhat.com>.
I am also not seeing a clean run on the tests on main-line since 
changes. hanging in a few places.

Still looking into it.

Carl.

Daniel Kulp wrote:
> On Sunday November 12 2006 12:40 pm, Steve Vinoski wrote:
>   
>> Under branches/mvn is a first cut at building and testing the java
>> code with maven. I would appreciate it if others could checkout the
>> branch and try it, especially on platforms other than OS X. All
>> feedback welcomed.
>>
>> BTW, be sure to get "mvn" and not "maven" as the latter is an old
>> branch that doesn't work and needs to go away.
>>
>> --steve
>>     
>
> It doesn't seem to build in client due to a dependency on jms jar which 
> isn't available in the maven repositories.
>
> I've included a patch below.
>
>   


Re: [java] mvn branch

Posted by Daniel Kulp <da...@iona.com>.
On Sunday November 12 2006 12:40 pm, Steve Vinoski wrote:
> Under branches/mvn is a first cut at building and testing the java
> code with maven. I would appreciate it if others could checkout the
> branch and try it, especially on platforms other than OS X. All
> feedback welcomed.
>
> BTW, be sure to get "mvn" and not "maven" as the latter is an old
> branch that doesn't work and needs to go away.
>
> --steve

It doesn't seem to build in client due to a dependency on jms jar which 
isn't available in the maven repositories.

I've included a patch below.

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194   F:781-902-8001
daniel.kulp@iona.com




Index: client/pom.xml
===================================================================
--- client/pom.xml      (revision 474414)
+++ client/pom.xml      (working copy)
@@ -86,6 +86,12 @@
       <artifactId>jmscts</artifactId>
       <version>0.5-b2</version>
       <scope>test</scope>
+      <exclusions>
+          <exclusion>
+              <groupId>jms</groupId>
+              <artifactId>jms</artifactId>
+          </exclusion>
+      </exclusions>
     </dependency>
     <dependency>
       <groupId>xml-security</groupId>

Re: [java] mvn branch

Posted by Steve Vinoski <vi...@iona.com>.
On Nov 13, 2006, at 5:07 AM, Marnie McCormack wrote:
> fscontext has been removed from svn and the test disabled so we  
> shouldn't be
> trying to auto download this one imho ?

Done. I've committed the change to client/pom.xml to remove the need  
for these jars.

--steve

>
> Marnie
>
>
> On 11/13/06, Steve Vinoski <vi...@iona.com> wrote:
>>
>>
>> On Nov 12, 2006, at 8:34 PM, Rafael Schloming wrote:
>>
>> > Steve Vinoski wrote:
>> >> Under branches/mvn is a first cut at building and testing the java
>> >> code with maven. I would appreciate it if others could checkout
>> >> the branch and try it, especially on platforms other than OS X.
>> >> All feedback welcomed.
>> >> BTW, be sure to get "mvn" and not "maven" as the latter is an old
>> >> branch that doesn't work and needs to go away.
>> >
>> > This is what happens for me:
>> >
>> > [INFO]
>> >  
>> --------------------------------------------------------------------- 
>> -
>> > --
>> > [ERROR] BUILD ERROR
>> > [INFO]
>> >  
>> --------------------------------------------------------------------- 
>> -
>> > --
>> > [INFO] Failed to resolve artifact.
>> >
>> > Missing:
>> > ----------
>> > 1) fscontext:fscontext:jar:1.2-beta3
>> >
>> >   Try downloading the file manually from the project website.
>> >
>> >   Then, install it using the command:
>> >       mvn install:install-file -DgroupId=fscontext -
>> > DartifactId=fscontext \
>> >           -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/path/to/file
>>
>> Yes, fscontext is a current problem because there's no maven release
>> for it. I raised this as an issue on this list last week.
>>
>> But as a temporary workaround, you can do exactly what the error
>> message says. If you download the fscontext zip file from Sun [1],
>> you can extract the fscontext and providerutil jars and install them
>> into your local repository just as the error message indicates:
>>
>> mvn install:install-file -DgroupId=fscontext -DartifactId=fscontext \
>>     -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/your/path/to/
>> fscontext-1.2-beta3.jar
>> mvn install:install-file -DgroupId=fscontext - 
>> DartifactId=providerutil \
>>     -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/your/path/to/
>> providerutil-1.2-beta3.jar
>>
>> Another alternative, depending on whether we want the build to
>> require these jars or not, would be to remove their dependencies from
>> the pom files.
>>
>> --steve
>>
>> [1] <http://java.sun.com/products/jndi/downloads/index.html>
>>


Re: [java] mvn branch

Posted by Marnie McCormack <ma...@googlemail.com>.
fscontext has been removed from svn and the test disabled so we shouldn't be
trying to auto download this one imho ?

Marnie


On 11/13/06, Steve Vinoski <vi...@iona.com> wrote:
>
>
> On Nov 12, 2006, at 8:34 PM, Rafael Schloming wrote:
>
> > Steve Vinoski wrote:
> >> Under branches/mvn is a first cut at building and testing the java
> >> code with maven. I would appreciate it if others could checkout
> >> the branch and try it, especially on platforms other than OS X.
> >> All feedback welcomed.
> >> BTW, be sure to get "mvn" and not "maven" as the latter is an old
> >> branch that doesn't work and needs to go away.
> >
> > This is what happens for me:
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> > [ERROR] BUILD ERROR
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> > [INFO] Failed to resolve artifact.
> >
> > Missing:
> > ----------
> > 1) fscontext:fscontext:jar:1.2-beta3
> >
> >   Try downloading the file manually from the project website.
> >
> >   Then, install it using the command:
> >       mvn install:install-file -DgroupId=fscontext -
> > DartifactId=fscontext \
> >           -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/path/to/file
>
> Yes, fscontext is a current problem because there's no maven release
> for it. I raised this as an issue on this list last week.
>
> But as a temporary workaround, you can do exactly what the error
> message says. If you download the fscontext zip file from Sun [1],
> you can extract the fscontext and providerutil jars and install them
> into your local repository just as the error message indicates:
>
> mvn install:install-file -DgroupId=fscontext -DartifactId=fscontext \
>     -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/your/path/to/
> fscontext-1.2-beta3.jar
> mvn install:install-file -DgroupId=fscontext -DartifactId=providerutil \
>     -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/your/path/to/
> providerutil-1.2-beta3.jar
>
> Another alternative, depending on whether we want the build to
> require these jars or not, would be to remove their dependencies from
> the pom files.
>
> --steve
>
> [1] <http://java.sun.com/products/jndi/downloads/index.html>
>

Re: [java] mvn branch

Posted by Steve Vinoski <vi...@iona.com>.
On Nov 12, 2006, at 8:34 PM, Rafael Schloming wrote:

> Steve Vinoski wrote:
>> Under branches/mvn is a first cut at building and testing the java  
>> code with maven. I would appreciate it if others could checkout  
>> the branch and try it, especially on platforms other than OS X.  
>> All feedback welcomed.
>> BTW, be sure to get "mvn" and not "maven" as the latter is an old  
>> branch that doesn't work and needs to go away.
>
> This is what happens for me:
>
> [INFO]  
> ---------------------------------------------------------------------- 
> --
> [ERROR] BUILD ERROR
> [INFO]  
> ---------------------------------------------------------------------- 
> --
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) fscontext:fscontext:jar:1.2-beta3
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>       mvn install:install-file -DgroupId=fscontext - 
> DartifactId=fscontext \
>           -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/path/to/file

Yes, fscontext is a current problem because there's no maven release  
for it. I raised this as an issue on this list last week.

But as a temporary workaround, you can do exactly what the error  
message says. If you download the fscontext zip file from Sun [1],  
you can extract the fscontext and providerutil jars and install them  
into your local repository just as the error message indicates:

mvn install:install-file -DgroupId=fscontext -DartifactId=fscontext \
     -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/your/path/to/ 
fscontext-1.2-beta3.jar
mvn install:install-file -DgroupId=fscontext -DartifactId=providerutil \
     -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/your/path/to/ 
providerutil-1.2-beta3.jar

Another alternative, depending on whether we want the build to  
require these jars or not, would be to remove their dependencies from  
the pom files.

--steve

[1] <http://java.sun.com/products/jndi/downloads/index.html>

Re: [java] mvn branch

Posted by Rafael Schloming <ra...@redhat.com>.
Steve Vinoski wrote:
> Under branches/mvn is a first cut at building and testing the java code 
> with maven. I would appreciate it if others could checkout the branch 
> and try it, especially on platforms other than OS X. All feedback welcomed.
> 
> BTW, be sure to get "mvn" and not "maven" as the latter is an old branch 
> that doesn't work and needs to go away.

This is what happens for me:

[INFO] 
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] 
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) fscontext:fscontext:jar:1.2-beta3

   Try downloading the file manually from the project website.

   Then, install it using the command:
       mvn install:install-file -DgroupId=fscontext -DartifactId=fscontext \
           -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/path/to/file

   Path to dependency:
         1) org.apache.qpid:qpid-client:jar:1.0-incubator-M1-SNAPSHOT
         2) fscontext:fscontext:jar:1.2-beta3

2) fscontext:providerutil:jar:1.2-beta3

   Try downloading the file manually from the project website.

   Then, install it using the command:
       mvn install:install-file -DgroupId=fscontext 
-DartifactId=providerutil \
           -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/path/to/file

   Path to dependency:
         1) org.apache.qpid:qpid-client:jar:1.0-incubator-M1-SNAPSHOT
         2) fscontext:providerutil:jar:1.2-beta3

----------
2 required artifacts are missing.

for artifact:
   org.apache.qpid:qpid-client:jar:1.0-incubator-M1-SNAPSHOT

from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   java.net (https://maven-repository.dev.java.net/nonav/repository/),
   apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository)


[INFO] 
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] 
------------------------------------------------------------------------