-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You could write your own Maven goal that runs the batch file then
use the ant:echo file=.../ task upon completion. You would not be
able to properly catch errors this way unless the batch file was
written to return an error code and your Maven
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I ran into what I think was the same problem about a month ago
(it's hard to tell because the original post in this thread did not
include the error messages or line number). I guess there is something
in RC2 that works in Windows does not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I ran into that exact problem a few days ago. It seems the xdoc
plugin in RC2 is broken and you will have to edit line 345 of the
plugin.jelly file:
http://nagoya.apache.org/eyebrowse/ReadMsg?
[EMAIL PROTECTED]msgNo=11599
-Brian
On Mar
I am not sure if this is a problem with my usage or a bug, but I
seem to be having difficulty with the scm:perform-release goal in both
RC1 and RC2. The project has been properly tagged with
prepare-release, as I can manually do a cvs export and grab all the
correct files. Running a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I upgraded from RC1 to RC2 today, and I thought I did everything
correctly. I wiped out my ~/.maven/plugins folder (as per suggestions
of other messages on the list). I also use a /usr/local/maven symlink,
which used to point to the RC1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Out of the box, ssh supports both key files and passwords--using
the key files if they exist, then falling back to passwords if they do
not (or if the keys are incorrect). It is not an either/or
configuration. Disabling key files takes a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A little more complex and slightly less straightforward, I would
assume you could do this using XML entity trickery. For instance:
!DOCTYPE project [
!ENTITY pomBaseUrl http://server.com;
]
project
...
urlpomBaseUrl;/adept-open/url
...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was kind of looking for a solution that didn't involve shuffling
around stuff too much on the CVS server. We would probably drop Maven
and continue using Ant if we had to break the single source folder into
twelve separate ones. I hate to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That is what I originally had, but got a parsing error when Maven
starts up:
$ maven -p project-util.xml java:compile
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v.
nested sourceModifications with a
slight change in capitalization fixed everything: sourceModifications
sourceModification className ...etc
Everyone: thanks for your help!
-Brian
On Mar 5, 2004, at 11:27 AM, Brian Enigma wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That is what I
10 matches
Mail list logo
