On 8 Jun 2011, at 14:04, Manik Surtani wrote:
>
> On 8 Jun 2011, at 13:54, Sanne Grinovero wrote:
>
>> On Wed, Jun 8, 2011 at 1:52 PM, Pete Muir wrote:
>>>
>>> This may be old news, but if something is missing from the "new" (ish ;-)
>>> r.j.o, but available in another repo, you can email Pa
On 8 Jun 2011, at 13:54, Sanne Grinovero wrote:
> On Wed, Jun 8, 2011 at 1:52 PM, Pete Muir wrote:
>>
>>
>> This may be old news, but if something is missing from the "new" (ish ;-)
>> r.j.o, but available in another repo, you can email Paul Gier and ask for
>> that repo to be added to the r
On Wed, Jun 8, 2011 at 1:52 PM, Pete Muir wrote:
>
> On 8 Jun 2011, at 13:50, Sanne Grinovero wrote:
>
>> On Wed, Jun 8, 2011 at 12:59 PM, Manik Surtani wrote:
>>>
>>> What was the fix around this? To remove the hard-coded repo in the poms?
>>
>> No, I removed the old deprecated repository.jboss
On 8 Jun 2011, at 13:50, Sanne Grinovero wrote:
> On Wed, Jun 8, 2011 at 12:59 PM, Manik Surtani wrote:
>>
>> What was the fix around this? To remove the hard-coded repo in the poms?
>
> No, I removed the old deprecated repository.jboss.org/maven2 as this
> was offline and pretty urgent, and
On Wed, Jun 8, 2011 at 12:59 PM, Manik Surtani wrote:
>
> What was the fix around this? To remove the hard-coded repo in the poms?
No, I removed the old deprecated repository.jboss.org/maven2 as this
was offline and pretty urgent, and re-adapted the build to be able to
build without it (needed t
What was the fix around this? To remove the hard-coded repo in the poms?
On 31 May 2011, at 09:46, Galder Zamarreño wrote:
> I'm fine with it. I think Adrian added it but clearly, all jars should be
> available in the Nexus maven profile.
>
> This has been fixed and integrated and build looks
I'm fine with it. I think Adrian added it but clearly, all jars should be
available in the Nexus maven profile.
This has been fixed and integrated and build looks fine.
On May 26, 2011, at 4:12 PM, Sanne Grinovero wrote:
> So this got quite urgent right now:
>
> http://repository.jboss.org/mav
So this got quite urgent right now:
http://repository.jboss.org/maven2
is now returning "not authorized", we all knew it was deprecated since
long time, but now it's gone and this is affecting my build and
blocking my work.
Even if I fix it locally, it's still troublesome as people depending
on
On 19 May 2011, at 11:40, Sanne Grinovero wrote:
> 2011/5/19 Pete Muir :
>> The one argument for putting the (new) repo in the pom is that does make
>> getting started contributing easier, and buildable on a clean system with no
>> changes.
>>
>> Maven guys used to recommend not putting repos
On 19 May 2011, at 11:47, Tristan Tarrant wrote:
> On Thu, May 19, 2011 at 12:40, Sanne Grinovero
> wrote:
>> I also assume that at some point we might want to have our artifacts
>> synched with central, I doubt they will accept poms pointing to other
>> repositories, that was not the case befor
On 19 May 2011, at 11:39, Tristan Tarrant wrote:
> On Thu, May 19, 2011 at 12:18, Pete Muir wrote:
>> Maven guys used to recommend not putting repos in poms, but they changed
>> that a while back and now don't discourage it.
>
> Don't know about that, but if you want something in Maven Central
On Thu, May 19, 2011 at 12:40, Sanne Grinovero
wrote:
> I also assume that at some point we might want to have our artifacts
> synched with central, I doubt they will accept poms pointing to other
> repositories, that was not the case before but it might have changed.
For reference, here are the
2011/5/19 Pete Muir :
> The one argument for putting the (new) repo in the pom is that does make
> getting started contributing easier, and buildable on a clean system with no
> changes.
>
> Maven guys used to recommend not putting repos in poms, but they changed that
> a while back and now don'
On Thu, May 19, 2011 at 12:18, Pete Muir wrote:
> Maven guys used to recommend not putting repos in poms, but they changed that
> a while back and now don't discourage it.
Don't know about that, but if you want something in Maven Central, it
cannot depend on external repos. You can refer to exte
The one argument for putting the (new) repo in the pom is that does make
getting started contributing easier, and buildable on a clean system with no
changes.
Maven guys used to recommend not putting repos in poms, but they changed that a
while back and now don't discourage it.
On 19 May 2011,
On 19 May 2011, at 09:52, Galder Zamarreño wrote:
> Hi all,
>
> So, what's our current approach towards hardcoding maven repositories in the
> pom.xml files?
>
> Should we allow JBoss repos to be defined master/parent/pom.xml? This was
> added by Adrian C when he upgraded JClouds:
>
>
On Thu, May 19, 2011 at 10:52, Galder Zamarreño wrote:
> Hi all,
>
> So, what's our current approach towards hardcoding maven repositories in the
> pom.xml files?
>
> Should we allow JBoss repos to be defined master/parent/pom.xml? This was
> added by Adrian C when he upgraded JClouds:
I'm fine
17 matches
Mail list logo
