You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicemix.apache.org by jb...@apache.org on 2010/02/28 18:53:17 UTC

svn commit: r917227 - /servicemix/servicemix-pom/trunk/pom.xml

Author: jbonofre
Date: Sun Feb 28 17:53:17 2010
New Revision: 917227

URL: http://svn.apache.org/viewvc?rev=917227&view=rev
Log:
Upgrade to the latest apache POM and begin the repositories cleanup.

Modified:
    servicemix/servicemix-pom/trunk/pom.xml

Modified: servicemix/servicemix-pom/trunk/pom.xml
URL: http://svn.apache.org/viewvc/servicemix/servicemix-pom/trunk/pom.xml?rev=917227&r1=917226&r2=917227&view=diff
==============================================================================
--- servicemix/servicemix-pom/trunk/pom.xml (original)
+++ servicemix/servicemix-pom/trunk/pom.xml Sun Feb 28 17:53:17 2010
@@ -22,7 +22,7 @@
   <parent>
     <groupId>org.apache</groupId>
     <artifactId>apache</artifactId>
-    <version>6</version>
+    <version>7</version>
   </parent>
   
   <groupId>org.apache.servicemix</groupId>
@@ -189,28 +189,10 @@
   </scm>
   
   <repositories>
-    <!--This is a hack to short circuit the jencks 2.1 problem with servicemix.org repo
-        It can probably be deleted if we update to jencks 2.2 in ServiceMix 3.3.x -->
     <repository>
-        <id>servicemix-repo</id>
-        <name>ServiceMix Repository</name>
-        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
-        <releases>
-            <enabled>true</enabled>
-        </releases>
-        <snapshots>
-            <enabled>false</enabled>
-        </snapshots>
-    </repository>
-    <repository>
-        <id>servicemix.m2</id>
-        <name>Apache ServiceMix Maven2 Repository</name>
-        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
-    </repository>
-    <repository>
-        <id>apache.incubating</id>
-        <name>Apache Incubating Repository</name>
-        <url>http://people.apache.org/repo/m2-incubating-repository</url>
+        <id>java.net</id>
+        <name>Java.net Maven Repository</name>
+        <url>http://download.java.net/maven/2/</url>
     </repository>
     <repository>
         <id>codehaus</id>



Re: svn commit: r917227 - /servicemix/servicemix-pom/trunk/pom.xml

Posted by Guillaume Nodet <gn...@gmail.com>.
AFAIK, there has been some incompatibilities between java.net
repository and central, so i'd strongly advise not to use it at all
and put any necessary artifacts in our private repo if needed.  I
can't recall the details though.

On Mon, Mar 1, 2010 at 20:45, Gert Vanthienen <ge...@gmail.com> wrote:
> Jean-Baptiste,
>
> For now, I would personally prefer if we just removed the java.net
> repository from our root pom.  We probably only need that particular
> repository for one or two of the components and a few of the other
> builds anyway, so there's no need to add the repo to every other build
> we have.
>
> For now, the javamail 1.4.3 jar isn't available in central repo at the
> moment, but as soon as it becomes available (I see some of the older
> versions are there), we could even remove the java.net repo entirely
> again.
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> On 1 March 2010 14:45, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>> Gert,
>>
>> If we putted the central repo in first place, I guess it's enough ?
>> Else we can deploy javamail 1.4.3 on the apache central repo, can't we ?
>> Regards
>> JB
>> -----Original Message-----
>> From: Gert Vanthienen <ge...@gmail.com>
>> Date: Mon, 1 Mar 2010 14:37:00
>> To: <de...@servicemix.apache.org>
>> Subject: Re: svn commit: r917227 - /servicemix/servicemix-pom/trunk/pom.xml
>>
>> L.S.,
>>
>> Are we sure we want to include the java.net repo in our parent pom?
>> Personally, I would try to avoid putting any additional repositories
>> in there by default -- most of the things we depend on should be in
>> central repo anyway and the less repositories we have, the less time
>> the maven build needs to spend hitting the different repositories.
>>
>> Regards,
>>
>> Gert Vanthienen
>> ------------------------
>> Open Source SOA: http://fusesource.com
>> Blog: http://gertvanthienen.blogspot.com/
>>
>>
>>
>> On 28 February 2010 18:53,  <jb...@apache.org> wrote:
>>> Author: jbonofre
>>> Date: Sun Feb 28 17:53:17 2010
>>> New Revision: 917227
>>>
>>> URL: http://svn.apache.org/viewvc?rev=917227&view=rev
>>> Log:
>>> Upgrade to the latest apache POM and begin the repositories cleanup.
>>>
>>> Modified:
>>>    servicemix/servicemix-pom/trunk/pom.xml
>>>
>>> Modified: servicemix/servicemix-pom/trunk/pom.xml
>>> URL: http://svn.apache.org/viewvc/servicemix/servicemix-pom/trunk/pom.xml?rev=917227&r1=917226&r2=917227&view=diff
>>> ==============================================================================
>>> --- servicemix/servicemix-pom/trunk/pom.xml (original)
>>> +++ servicemix/servicemix-pom/trunk/pom.xml Sun Feb 28 17:53:17 2010
>>> @@ -22,7 +22,7 @@
>>>   <parent>
>>>     <groupId>org.apache</groupId>
>>>     <artifactId>apache</artifactId>
>>> -    <version>6</version>
>>> +    <version>7</version>
>>>   </parent>
>>>
>>>   <groupId>org.apache.servicemix</groupId>
>>> @@ -189,28 +189,10 @@
>>>   </scm>
>>>
>>>   <repositories>
>>> -    <!--This is a hack to short circuit the jencks 2.1 problem with servicemix.org repo
>>> -        It can probably be deleted if we update to jencks 2.2 in ServiceMix 3.3.x -->
>>>     <repository>
>>> -        <id>servicemix-repo</id>
>>> -        <name>ServiceMix Repository</name>
>>> -        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
>>> -        <releases>
>>> -            <enabled>true</enabled>
>>> -        </releases>
>>> -        <snapshots>
>>> -            <enabled>false</enabled>
>>> -        </snapshots>
>>> -    </repository>
>>> -    <repository>
>>> -        <id>servicemix.m2</id>
>>> -        <name>Apache ServiceMix Maven2 Repository</name>
>>> -        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
>>> -    </repository>
>>> -    <repository>
>>> -        <id>apache.incubating</id>
>>> -        <name>Apache Incubating Repository</name>
>>> -        <url>http://people.apache.org/repo/m2-incubating-repository</url>
>>> +        <id>java.net</id>
>>> +        <name>Java.net Maven Repository</name>
>>> +        <url>http://download.java.net/maven/2/</url>
>>>     </repository>
>>>     <repository>
>>>         <id>codehaus</id>
>>>
>>>
>>>
>>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: svn commit: r917227 - /servicemix/servicemix-pom/trunk/pom.xml

Posted by Gert Vanthienen <ge...@gmail.com>.
Jean-Baptiste,

For now, I would personally prefer if we just removed the java.net
repository from our root pom.  We probably only need that particular
repository for one or two of the components and a few of the other
builds anyway, so there's no need to add the repo to every other build
we have.

For now, the javamail 1.4.3 jar isn't available in central repo at the
moment, but as soon as it becomes available (I see some of the older
versions are there), we could even remove the java.net repo entirely
again.

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



On 1 March 2010 14:45, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Gert,
>
> If we putted the central repo in first place, I guess it's enough ?
> Else we can deploy javamail 1.4.3 on the apache central repo, can't we ?
> Regards
> JB
> -----Original Message-----
> From: Gert Vanthienen <ge...@gmail.com>
> Date: Mon, 1 Mar 2010 14:37:00
> To: <de...@servicemix.apache.org>
> Subject: Re: svn commit: r917227 - /servicemix/servicemix-pom/trunk/pom.xml
>
> L.S.,
>
> Are we sure we want to include the java.net repo in our parent pom?
> Personally, I would try to avoid putting any additional repositories
> in there by default -- most of the things we depend on should be in
> central repo anyway and the less repositories we have, the less time
> the maven build needs to spend hitting the different repositories.
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> On 28 February 2010 18:53,  <jb...@apache.org> wrote:
>> Author: jbonofre
>> Date: Sun Feb 28 17:53:17 2010
>> New Revision: 917227
>>
>> URL: http://svn.apache.org/viewvc?rev=917227&view=rev
>> Log:
>> Upgrade to the latest apache POM and begin the repositories cleanup.
>>
>> Modified:
>>    servicemix/servicemix-pom/trunk/pom.xml
>>
>> Modified: servicemix/servicemix-pom/trunk/pom.xml
>> URL: http://svn.apache.org/viewvc/servicemix/servicemix-pom/trunk/pom.xml?rev=917227&r1=917226&r2=917227&view=diff
>> ==============================================================================
>> --- servicemix/servicemix-pom/trunk/pom.xml (original)
>> +++ servicemix/servicemix-pom/trunk/pom.xml Sun Feb 28 17:53:17 2010
>> @@ -22,7 +22,7 @@
>>   <parent>
>>     <groupId>org.apache</groupId>
>>     <artifactId>apache</artifactId>
>> -    <version>6</version>
>> +    <version>7</version>
>>   </parent>
>>
>>   <groupId>org.apache.servicemix</groupId>
>> @@ -189,28 +189,10 @@
>>   </scm>
>>
>>   <repositories>
>> -    <!--This is a hack to short circuit the jencks 2.1 problem with servicemix.org repo
>> -        It can probably be deleted if we update to jencks 2.2 in ServiceMix 3.3.x -->
>>     <repository>
>> -        <id>servicemix-repo</id>
>> -        <name>ServiceMix Repository</name>
>> -        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
>> -        <releases>
>> -            <enabled>true</enabled>
>> -        </releases>
>> -        <snapshots>
>> -            <enabled>false</enabled>
>> -        </snapshots>
>> -    </repository>
>> -    <repository>
>> -        <id>servicemix.m2</id>
>> -        <name>Apache ServiceMix Maven2 Repository</name>
>> -        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
>> -    </repository>
>> -    <repository>
>> -        <id>apache.incubating</id>
>> -        <name>Apache Incubating Repository</name>
>> -        <url>http://people.apache.org/repo/m2-incubating-repository</url>
>> +        <id>java.net</id>
>> +        <name>Java.net Maven Repository</name>
>> +        <url>http://download.java.net/maven/2/</url>
>>     </repository>
>>     <repository>
>>         <id>codehaus</id>
>>
>>
>>
>

Re: svn commit: r917227 - /servicemix/servicemix-pom/trunk/pom.xml

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Gert,

If we putted the central repo in first place, I guess it's enough ?
Else we can deploy javamail 1.4.3 on the apache central repo, can't we ?
Regards
JB
-----Original Message-----
From: Gert Vanthienen <ge...@gmail.com>
Date: Mon, 1 Mar 2010 14:37:00 
To: <de...@servicemix.apache.org>
Subject: Re: svn commit: r917227 - /servicemix/servicemix-pom/trunk/pom.xml

L.S.,

Are we sure we want to include the java.net repo in our parent pom?
Personally, I would try to avoid putting any additional repositories
in there by default -- most of the things we depend on should be in
central repo anyway and the less repositories we have, the less time
the maven build needs to spend hitting the different repositories.

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



On 28 February 2010 18:53,  <jb...@apache.org> wrote:
> Author: jbonofre
> Date: Sun Feb 28 17:53:17 2010
> New Revision: 917227
>
> URL: http://svn.apache.org/viewvc?rev=917227&view=rev
> Log:
> Upgrade to the latest apache POM and begin the repositories cleanup.
>
> Modified:
>    servicemix/servicemix-pom/trunk/pom.xml
>
> Modified: servicemix/servicemix-pom/trunk/pom.xml
> URL: http://svn.apache.org/viewvc/servicemix/servicemix-pom/trunk/pom.xml?rev=917227&r1=917226&r2=917227&view=diff
> ==============================================================================
> --- servicemix/servicemix-pom/trunk/pom.xml (original)
> +++ servicemix/servicemix-pom/trunk/pom.xml Sun Feb 28 17:53:17 2010
> @@ -22,7 +22,7 @@
>   <parent>
>     <groupId>org.apache</groupId>
>     <artifactId>apache</artifactId>
> -    <version>6</version>
> +    <version>7</version>
>   </parent>
>
>   <groupId>org.apache.servicemix</groupId>
> @@ -189,28 +189,10 @@
>   </scm>
>
>   <repositories>
> -    <!--This is a hack to short circuit the jencks 2.1 problem with servicemix.org repo
> -        It can probably be deleted if we update to jencks 2.2 in ServiceMix 3.3.x -->
>     <repository>
> -        <id>servicemix-repo</id>
> -        <name>ServiceMix Repository</name>
> -        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
> -        <releases>
> -            <enabled>true</enabled>
> -        </releases>
> -        <snapshots>
> -            <enabled>false</enabled>
> -        </snapshots>
> -    </repository>
> -    <repository>
> -        <id>servicemix.m2</id>
> -        <name>Apache ServiceMix Maven2 Repository</name>
> -        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
> -    </repository>
> -    <repository>
> -        <id>apache.incubating</id>
> -        <name>Apache Incubating Repository</name>
> -        <url>http://people.apache.org/repo/m2-incubating-repository</url>
> +        <id>java.net</id>
> +        <name>Java.net Maven Repository</name>
> +        <url>http://download.java.net/maven/2/</url>
>     </repository>
>     <repository>
>         <id>codehaus</id>
>
>
>

Re: svn commit: r917227 - /servicemix/servicemix-pom/trunk/pom.xml

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I prepared servicemix-pom but not yet released it.

Regards
JB
-----Original Message-----
From: Gert Vanthienen <ge...@gmail.com>
Date: Mon, 1 Mar 2010 14:37:00 
To: <de...@servicemix.apache.org>
Subject: Re: svn commit: r917227 - /servicemix/servicemix-pom/trunk/pom.xml

L.S.,

Are we sure we want to include the java.net repo in our parent pom?
Personally, I would try to avoid putting any additional repositories
in there by default -- most of the things we depend on should be in
central repo anyway and the less repositories we have, the less time
the maven build needs to spend hitting the different repositories.

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



On 28 February 2010 18:53,  <jb...@apache.org> wrote:
> Author: jbonofre
> Date: Sun Feb 28 17:53:17 2010
> New Revision: 917227
>
> URL: http://svn.apache.org/viewvc?rev=917227&view=rev
> Log:
> Upgrade to the latest apache POM and begin the repositories cleanup.
>
> Modified:
>    servicemix/servicemix-pom/trunk/pom.xml
>
> Modified: servicemix/servicemix-pom/trunk/pom.xml
> URL: http://svn.apache.org/viewvc/servicemix/servicemix-pom/trunk/pom.xml?rev=917227&r1=917226&r2=917227&view=diff
> ==============================================================================
> --- servicemix/servicemix-pom/trunk/pom.xml (original)
> +++ servicemix/servicemix-pom/trunk/pom.xml Sun Feb 28 17:53:17 2010
> @@ -22,7 +22,7 @@
>   <parent>
>     <groupId>org.apache</groupId>
>     <artifactId>apache</artifactId>
> -    <version>6</version>
> +    <version>7</version>
>   </parent>
>
>   <groupId>org.apache.servicemix</groupId>
> @@ -189,28 +189,10 @@
>   </scm>
>
>   <repositories>
> -    <!--This is a hack to short circuit the jencks 2.1 problem with servicemix.org repo
> -        It can probably be deleted if we update to jencks 2.2 in ServiceMix 3.3.x -->
>     <repository>
> -        <id>servicemix-repo</id>
> -        <name>ServiceMix Repository</name>
> -        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
> -        <releases>
> -            <enabled>true</enabled>
> -        </releases>
> -        <snapshots>
> -            <enabled>false</enabled>
> -        </snapshots>
> -    </repository>
> -    <repository>
> -        <id>servicemix.m2</id>
> -        <name>Apache ServiceMix Maven2 Repository</name>
> -        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
> -    </repository>
> -    <repository>
> -        <id>apache.incubating</id>
> -        <name>Apache Incubating Repository</name>
> -        <url>http://people.apache.org/repo/m2-incubating-repository</url>
> +        <id>java.net</id>
> +        <name>Java.net Maven Repository</name>
> +        <url>http://download.java.net/maven/2/</url>
>     </repository>
>     <repository>
>         <id>codehaus</id>
>
>
>

Re: svn commit: r917227 - /servicemix/servicemix-pom/trunk/pom.xml

Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,

Are we sure we want to include the java.net repo in our parent pom?
Personally, I would try to avoid putting any additional repositories
in there by default -- most of the things we depend on should be in
central repo anyway and the less repositories we have, the less time
the maven build needs to spend hitting the different repositories.

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



On 28 February 2010 18:53,  <jb...@apache.org> wrote:
> Author: jbonofre
> Date: Sun Feb 28 17:53:17 2010
> New Revision: 917227
>
> URL: http://svn.apache.org/viewvc?rev=917227&view=rev
> Log:
> Upgrade to the latest apache POM and begin the repositories cleanup.
>
> Modified:
>    servicemix/servicemix-pom/trunk/pom.xml
>
> Modified: servicemix/servicemix-pom/trunk/pom.xml
> URL: http://svn.apache.org/viewvc/servicemix/servicemix-pom/trunk/pom.xml?rev=917227&r1=917226&r2=917227&view=diff
> ==============================================================================
> --- servicemix/servicemix-pom/trunk/pom.xml (original)
> +++ servicemix/servicemix-pom/trunk/pom.xml Sun Feb 28 17:53:17 2010
> @@ -22,7 +22,7 @@
>   <parent>
>     <groupId>org.apache</groupId>
>     <artifactId>apache</artifactId>
> -    <version>6</version>
> +    <version>7</version>
>   </parent>
>
>   <groupId>org.apache.servicemix</groupId>
> @@ -189,28 +189,10 @@
>   </scm>
>
>   <repositories>
> -    <!--This is a hack to short circuit the jencks 2.1 problem with servicemix.org repo
> -        It can probably be deleted if we update to jencks 2.2 in ServiceMix 3.3.x -->
>     <repository>
> -        <id>servicemix-repo</id>
> -        <name>ServiceMix Repository</name>
> -        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
> -        <releases>
> -            <enabled>true</enabled>
> -        </releases>
> -        <snapshots>
> -            <enabled>false</enabled>
> -        </snapshots>
> -    </repository>
> -    <repository>
> -        <id>servicemix.m2</id>
> -        <name>Apache ServiceMix Maven2 Repository</name>
> -        <url>http://svn.apache.org/repos/asf/servicemix/m2-repo/</url>
> -    </repository>
> -    <repository>
> -        <id>apache.incubating</id>
> -        <name>Apache Incubating Repository</name>
> -        <url>http://people.apache.org/repo/m2-incubating-repository</url>
> +        <id>java.net</id>
> +        <name>Java.net Maven Repository</name>
> +        <url>http://download.java.net/maven/2/</url>
>     </repository>
>     <repository>
>         <id>codehaus</id>
>
>
>