Alan, we have the exact problem that you have. We just upgraded from Maven
2.2.1 to Maven 3.0.4 when this started to happen.
Did you manage to resolve your problem? Do you have any hints as to what is
going on?
/Bengt
2013/7/8 Alan Buck alan.b...@pharmacyonesource.com
I forgot to show the
with 3.0.4 ? You'd be
missing
the credentials?
My 2 cents
-- Baptiste
Le 16 août 2013 08:57, Bengt Rodehav be...@rodehav.com a écrit :
Alan, we have the exact problem that you have. We just upgraded from
Maven
2.2.1 to Maven 3.0.4 when this started to happen.
Did you manage
? Why not full client + some reasonable (small)
handful of other dependencies?
Wayne
On Fri, Nov 11, 2011 at 5:00 PM, Bengt Rodehav be...@rodehav.com wrote:
It works but the full client is not enough for us to be able to build our
application.
Den 11 nov 2011 23:11 skrev Ryan Connolly ryn
We are using maven 3.0.3 and have problems using property values defined in
our local settings.xml for specifying systemPath values for system-scoped
dependencies. It seems this possibility has been removed in maven 3.
The system-scoped variable is necessary because we depend directly on a
third
Stephen and Wayne,
I agree that using system scope is undesirable. However, there is a reason
why maven has had this support - it is needed in real life. In my case, I
use Weblogic. When first trying to migrate our old ant based build system
to maven, I started out by trying to put the Weblogic
It works but the full client is not enough for us to be able to build our
application.
Den 11 nov 2011 23:11 skrev Ryan Connolly ryn...@gmail.com:
Does this no longer work?
http://docs.oracle.com/cd/E12840_01/wls/docs103/client/t3.html
On Nov 11, 2011 3:38 PM, Bengt Rodehav be...@rodehav.com
for the release,
this appears to work.
Ron
On 15/09/2010 6:09 AM, Bengt Rodehav wrote:
Thanks for your input Baptiste,
Yes, we have been debating the relase process a bit here. Keeping the
relase
process separate would e g mean that we know beforehand that we want to
build a release candidate
We've had similar questions where I work. The question has been related to
how and when to create tags in CVS (preferrably using the
maven-release-plugin).
Some people advocate tagging every build so that it can be recreated in case
it was fit for delivery. This is a problem when using CVS since
it.
For the dev process, only in my opinion, I think automatically releasing
every nights isn't a very good pratice. I rather think the release process
should be actually 100% standalone, but *manually* initiated (giving the
new
version and so).
Cheers
2010/9/15 Bengt Rodehav be...@rodehav.com
No I haven't but it's a good idea - I will do that.
Thanks,
/Bengt
2010/5/9 Justin Edelson justinedel...@gmail.com:
Have you posted this to a pax mailing list?
On May 9, 2010, at 5:42 AM, Bengt Rodehav be...@rodehav.com wrote:
Thanks for you reply Marshal,
I've tried to add the artifacts
for the features-maven-plugin, and
insure it has the pax-url-mvn artifact.
And, also, check that the pax-url-mvn artifact does indeed provide the
mvn: protocol implementation.
HTH. -Marshall
On 5/9/2010 8:42 AM, Bengt Rodehav wrote:
Thanks for you reply Marshal,
I've tried to add
ideas?
/Bengt
2010/5/8 Marshall Schor m...@schor.com:
On 5/8/2010 2:55 AM, Bengt Rodehav wrote:
No one has any ideas?
Here's an idea - Maven 3 has been doing more class loader isolation
stuff. Perhaps an extensions element is needed? See
https://cwiki.apache.org/MAVEN/maven-3x-class
to
the beta version that could break url handlers.
/Bengt
2010/5/7 Bengt Rodehav be...@rodehav.com:
I'm using the features-maven-plugin included in Apache Felix. It in
turn uses pax-url-mvn (version 1.1.2) to enable the protocol mvn:.
This works fine in maven 2.2.1 and also in maven 3.0-alpha-7
I'm using the features-maven-plugin included in Apache Felix. It in
turn uses pax-url-mvn (version 1.1.2) to enable the protocol mvn:.
This works fine in maven 2.2.1 and also in maven 3.0-alpha-7. However,
with everything else the same, it fails under maven 3.0-beta-1. I get
14 matches
Mail list logo
