Does anyone know how to fix this? I tried using darwin ports to
upgrade but leopard keeps overlaying the install with 2.0.6 which does
not work for my application. What were they thinking baking this into
the operating system. This is almost as bad as the Java Story. Are
they trying
PROTECTED]
On Nov 15, 2007, at 10:02 AM, Graham Leggett wrote:
On Thu, November 15, 2007 7:00 pm, Ryan Scott wrote:
Does anyone know how to fix this? I tried using darwin ports to
upgrade but leopard keeps overlaying the install with 2.0.6 which
does
not work for my application. What
I noticed this thread from a while back but there was never a
resolution. We are trying to get our parasoft jtest generated test
cases to run under Maven 2 and the surefire plugin with not much
success. It looks like parasoft itself it spinning up its own
classloader with the incorrect
We are trying to do a release:prepare using maven 2 and cvs. We are
getting the following error message:
[INFO] Executing: cvs -z3 -f -d
:pserver:[EMAIL PROTECTED]:/home/als_source/src -n -q update -d
[INFO] Working directory: /local/0/scm/dev_release/schema-framework
[INFO]
I get the following stack trace when trying to access Archiva for the
first time when pulling new code from the trunk. It looks like some
sort of configuration I missed. Can someone point me to the file I need
to configure?
Thanks
jvm 1| [INFO] The appserver server has started.
jvm 1|
Any status on this one? I would love to make the change or use the change. It
appears that about 25-30% of what I need has bad checksums including most of
the native plugins such as clean, deploy etc. This means that I can't do much
without being able to turn off the checksum feature.
Any
That is an ongoing discussion that everyone is having with the current repos.
There was a suggested fix proposed on the mailing list earlier this week but no
details or description of when or how to get it into the source tree. It seems
like if you cannot download most of the maven base
I will give the line 187 thing a shot and see how it works although with
the latest build it seems to be working again and all repositories are
accessed via the proxy. This has shown me that I really need some way to
control what is accessed via the proxy and the order so it looks like I
have to
I am having a similar issue. I have defined several managed
repositories but the only ones that are consulted for artifacts are
those that have proxies defined. I got around that by creating dummy
managed repositories and proxying them out to the real ones but that is
not a very secure solution.
I am trying to set up a fairly complex set of repositories and am
running into some challenges. I think most of it is my understanding of
the details of how Archiva is structured. Once I get a better
understanding I hope to help provide feedback in the user guide to help
other users.
So I have
I recently upgraded from Continuum 1.0.2 to 1.0.3 using a Maven 1
project.xml and I was using parameter substitution from my
build.properties file to fill in a parameter on my SCM URL string. The
current string is as follows:
scm:cvs:pserver:[EMAIL PROTECTED]:/somedirectory/src:modulen
ame
I
maven1 use it.
So you need to add the real scm url in your pom without parameters (same for
the name, artifactId, groupId, version), for other part, you can use parameters
if they aren't use by continuum but only by maven1
Emmanuel
Ryan, Scott D a écrit :
I recently upgraded from Continuum 1.0.2
I noticed a posting on JIRA for this issue but no activity since
November. We were getting this problem on some of our projects but it
seems now that non of our projects will build due to this error. Has
anyone found a cause or workaround for this issue.
] mailto:[EMAIL PROTECTED]
-Original Message-
From: Manny Nainu [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 26, 2005 11:17 AM
To: users@maven.apache.org
Cc: Ryan, Scott; [EMAIL PROTECTED]
Subject: Weblogic 8.1 plugin for Maven 2 ?
I can see the weblogic plugin for M1
You can add the Weblogic plugin to the list as I am working on the M2
version as we speak and M1 has been out for a while.
Scott Damon Ryan
Developer
(720) 514-5389
[EMAIL PROTECTED]
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 06, 2005 9:08 AM
order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
Ryan, Scott
The group id on the xjavadoc dependency in the project.xml is incorrect.
You can change the groupid to xdoclet for the xjavadoc artifact dependency
and that will download the library from the correct library. I believe
someone placed the xjavadoc jars into the incorrect groupid in the ibiblio
to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
Ryan, Scott
You might want to check out the project cargo and see if there are some
ideas there.
Scott Damon Ryan
Developer
(720) 514-5389
[EMAIL PROTECTED]
-Original Message-
From: Tom Bostelmann [mailto:[EMAIL PROTECTED]
Sent: Monday, January 10, 2005 2:10 PM
To: Maven Users List
Subject: Maven
How do we get these issues resolved? Should we make up a list of
capabilities we want and determine which project serves them best. I am not
sure where the workshop stuff would reside. Maybe a separate project for
the workshop plugin and use Cargo and the Weblogic plugin for the rest. I
think
already and
having two plugin projects is pain in the a** ... Jason, any comments?
Cheers,
Siegfried Goeschl
Ryan, Scott wrote:
We have enhanced the Weblogic deployment plugin to support inplace, ear
and
war deployments.
I have developed a rudimentary workshop plugin as well
two plugin projects is pain in the a** ... Jason, any comments?
Cheers,
Siegfried Goeschl
Ryan, Scott wrote:
We have enhanced the Weblogic deployment plugin to support inplace, ear
and
war deployments.
I have developed a rudimentary workshop plugin as well.
Scott Damon Ryan
PROTECTED]
Sent: Tuesday, January 04, 2005 10:09 AM
To: Maven Users List
Subject: RE: weblogic tools for maven
On Tue, 2005-01-04 at 07:20, Ryan, Scott wrote:
How do we get started? I could begin to contribute back some of our
enhancements as soon as I can package them.
If you guys want to get
is fine since the JAR is huge (37 MB for 8.1.2.0)
and includes a lot of stuff which could result into conflicts depending
on BEA and Maven version.
Cheers,
Siegfried Goeschl
Jason van Zyl wrote:
On Tue, 2005-01-04 at 09:16, Ryan, Scott wrote:
What do you mean by m1? Sorry I am involved
I would be interested in contributing and participating.
Scott Damon Ryan
Developer
(720) 514-5389
[EMAIL PROTECTED]
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, January 03, 2005 2:22 PM
To: Maven Users List
Subject: weblogic tools for maven
Howdy,
We have enhanced the Weblogic deployment plugin to support inplace, ear and
war deployments.
I have developed a rudimentary workshop plugin as well.
Scott Damon Ryan
Developer
(720) 514-5389
[EMAIL PROTECTED]
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent:
comment on this ticket:
http://jira.codehaus.org/browse/MPECLIPSE-60
Regards,
Stéphane
-Original Message-
From: Ryan, Scott [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 6:23 PM
To: 'Maven Users List'
Subject: Eclipse Source when EJB's are used
I am trying to include EJB
We have written a couple of plug-ins for our WebLogic installation. We have
one that supports deployment and one that supports building and deploying
Workshop projects. We have some scripts that automate our domain creation
but they are not built into plugins yet.
Scott Damon Ryan
Developer
I am trying to include EJB implementation source code in my eclipse projects
for web projects that only use the client jars. I have the several web
projects that access EJB's via their home and remote interfaces. In the
project XML I include a dependency for the jar version of the artifact which
One thing to note is that this will not by default support remote
deployment. You need to either FTP the files to the source directory for
the server or use a shared directory structure. The remote deploy will
remotely deploy the EAR or WAR but only if the code is already accessible by
the
-0600, Ryan, Scott [EMAIL PROTECTED]
wrote:
I am trying to run the jar:deploy goal. It is adding an extra : between
the
file location and the artifactId so that the directory cannot be located.
Here is an example of the bad location:
scp:
C:/apachehtdocs/maven/dev/:echostar-toolkit/poms
interprets something
as a cvs-connection string.
Per
On Fri, 27 Aug 2004 08:31:17 -0600, Ryan, Scott
[EMAIL PROTECTED] wrote:
Thanks for the tip but we do not use CVS. I have checked
all my files
project.xml, maven.xml, build.properties and project.properties and
there are no colons
.
Per
On Fri, 27 Aug 2004 08:31:17 -0600, Ryan, Scott
[EMAIL PROTECTED] wrote:
Thanks for the tip but we do not use CVS. I have checked
all my files
project.xml, maven.xml, build.properties and project.properties and
there are no colons anywhere in those files so it must be getting
I am trying to run the jar:deploy goal. It is adding an extra : between the
file location and the artifactId so that the directory cannot be located.
Here is an example of the bad location:
scp:
C:/apachehtdocs/maven/dev/:echostar-toolkit/poms/echostar-toolkit-1.0.0.0.po
m
I cannot figure
34 matches
Mail list logo
