Brian Burridge wrote:
2) Does anyone have a suggestion as to how to fix classes quickly when
checkstyle reports errors? We have 12,500 errors :), not all of which
need to be fixed (we'll make some changes to the checkstyle format), but
many do. I could use jalopy but then I have to replicate all
You mean like this one?
http://wiki.codehaus.org/maven/TomcatPlugin
That's been knocking around in various formats since last December
(posted to the -dev list back then). The version above doesn't depend on
the catalina ant jar (like my previous versions, and like yours does)
because, as you
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
Total time: 4 seconds
Brian Ewins [EMAIL PROTECTED]
08-08-2003 04:32 PM
Please respond
This is a known problem, see the workaround in this bug report:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-599
The latka fix referred to in dion's response looks like this:
!-- Major hack - set jaxp properties as they are foobared --
Or this:
http://wiki.codehaus.org/maven/TomcatPlugin
Unlike the webserver plugin, this deals with indivdual servlet contexts
using tomcat's management api.
A build cycle with an exploded webapp looks like:
// build and install
maven tomcat:install
// rebuild, reload
maven war:webapp
While some of what happened was pilot error, this bug also bit you:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-430
(a corrupt jar should never make it into the repository, the current
download process checks the md5 after the file has already made it in).
In part I guess this is a
Your dependency specifications are all wrong. Read the section on
dependencies here:
http://maven.apache.org/reference/project-descriptor.html
And look at examples here:
http://maven.apache.org/start/integrate.html
A minimal dependency specification would look like:
dependency
I'm going to patch the war task for some of the devs here and try this
out this week (with 2 new goals as described). If it goes well I'll put
the patch in JIRA. If it goes badly they kick my ass ;)
Ben Walding wrote:
Please update the wiki with the solution that you have been given. That
I wrote a patch for genapp itself quite a while back, to allow it to use
multiple project templates, and user-supplied templates. Its pretty
useful to be able to have templates which match the kind of projects you do.
See
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-426
- Baz
Andy
Dave,
I don't get why you want to use the war plugin *and* in-place editing.
You really want to do one or the other.
It sounds like the only 'goodness' you want from maven is the initial
population of src/webapp/WEB-INF/lib (etc). You only want to go back to
the war plugin to actually create
[resending now my mail is working again...]
Oracle are pretty much unique in still distributing jars as zips, you
are not alone in having this issue. I'm working on the 'sucks'
plugin[1], once its finished we should be able to automatically install
oracle drivers into the correct place in the
Theres another way to do that trick without editing your web.xml.
Instead of using a static error page, use a servlet as the front
controller for error pages. What this servlet does, generally, is
forward on to appropriate 'real' error pages. Alternatively you can get
it to show you stack
I've started some work on installing 'old/non-downloadable' jars into
the local repo:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-568
I'm not attempting to tackle the other side of what you're describing -
converting the old project to maven.
Since our way of working is to use our
Olivier Lamy wrote:
I try to define a snapshot dependency :
dependency
groupIdserviceslayer/groupId
artifactIdservicesstub/artifactId
versionSNAPSHOT/version
/dependency
I have generate a snapshot version in the repository :
servicesstub-20030717.044631.jar
if you do 'maven
:
It sounds well :-)))
But I can't generate the servicesstub-20030717.044631.jar with
jar:install-snapshot
Because I can't use the sybase ant tool in a maven project.
-Message d'origine-
De : Brian Ewins [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 17 juillet 2003 17:45
À : Maven Users List
Objet
You probably want 'pom.artifacts' if you want to get at the jar.
'pom.dependencies' is a list of dependencies, but you can always get to
the dependency via the jar. eg
j:forEach var=lib items=${pom.artifacts}
j:set var=dep value=lib.dependency/
/j:forEach
this would give you the
did wrote:
Hi all,
We are developping a JSP taglib project. In this project we would like
to provide the following artifacts:
- The taglib jar
- The Tld definition file
- A sample web site demonstrating the lib features. (A War containing
the some extra java classes + the taglib jar + JSP
[EMAIL PROTECTED] wrote:
Brian Ewins [EMAIL PROTECTED] wrote on 08/07/2003 09:30:28 PM:
Maximilian A. Ott wrote:
on the bleeding edge, but is there a way to declare the latest on
that
development branch, or in other words the 1.2.x where x denotes
the
latest revision of the 1.2 series
Maximilian A. Ott wrote:
Thanks that was very instructive. I understand that SNAPSHOT is the one
on the bleeding edge, but is there a way to declare the latest on that
development branch, or in other words the 1.2.x where x denotes the
latest revision of the 1.2 series.
We are following the
I can't see any other replies to this so...
You appear to have an extra '/' at the end of maven.repo.remote. Try:
maven.repo.remote=http://sxserver.semandex.net/maven
If you looked in the logs of your webserver, you'd find it would be
reporting errors for
SNAPSHOT is saying you depend on the 'cutting edge' build. Working with
snapshots of everything for releases is frowned upon as it means your
builds aren't actually repeatable; however its useful during development.
maven jar:install-snapshot
builds a jar with a timestamp instead of the usual
Brian Ewins wrote:
Project releases should have no snapshot dependencies. Since your
project.xml should be under version control with the rest of your code,
building an old version means getting the code /and its project.xml/
from cvs or whatever, so you know what
Whoops. The paragraph above
You do know that all the tlds are in the jar (under
META-INF/tlds/*.tld), and should have autoregistered under your webapp?
You're supposed to be able to refer to tlds in jsps like so:
%@ taglib uri=http://jakarta.apache.org/struts/tags-bean; prefix=bean %
...without even registering them in
See http://nagoya.apache.org/wiki/apachewiki.cgi?BrokenManifestInBeta9
There is a patch there you can download.
Vipul Vij wrote:
Hi List,
Well, I have been using Maven to generate WARs using JARs as you would. I have tried to deploy the WARs onto IBM's WAS and found it was unable to do this.
It looks like the problem could be in the checkstyle ant task, or that
your code doesn't compile. See:
http://sourceforge.net/tracker/index.php?func=detailaid=696335group_id=29721atid=397078
http://sourceforge.net/tracker/index.php?func=detailaid=76group_id=29721atid=397078
There are
goals on the
menu, and the error messages parsed into clickable links.
Get hold of the demo and try it out. http://www.intellij.com/idea/
[1] Mine is attached, so you can see what I mean.
Verma, Nitin (GECP, OTHER, 529706) wrote:
Which IDE do you use now?
-Original Message-
From: Brian
michal.maczka wrote:
Yeap you right.
And I guess that I am right too ... becouse I believe that,
we alredy have a workflow of goals in Maven.
Yup, I agree.
so basically B should not update the path.
and in A (when needed)you should use something like:
B:getUpatedOutputPath()
which will
Colin Sampaleanu wrote:
I completely agree with you about having plugins actually be the ones
doing their stuff with the sources. However, maven has to provide basic
facilities to plugins for dealing with source directories, and for
expressing these in the POM (in a section specific to that
28 matches
Mail list logo
