Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-573
Here is an overview of the issue:
--
On Wed, 16 Jul 2003, Ben Walding wrote:
> There was a change in the semantics of werkz / attainGoal.I don't
> know the specifics of it, but it was supposed to allow finegrained
> control of prerequisite handling.
>
> Looking for code that added session as a parameter to the attain tags I
:)
Its not just maven-SNAPSHOT, it is maven.jar as well.
If a plugin depends on maven.jar for whatever reason, shouldn't it depend on
maven-1.0-beta-9.jar and so on?
I'm not sure why it breaks so much, but maybe the classloader isolation will
stop it when it happens.
Thanks,
Brett
-Original
The artifact plugin has a reference to maven-SNAPSHOT.
Blame Michal (it is unfair to blame Michal, but unfair blamestorming is
what we do best!)
Brett Porter wrote:
Hi,
It seems I'm being bitten by these again - seems to happen whenever I
upgrade!
On some systems, it fails as it can't find one
There was a change in the semantics of werkz / attainGoal.I don't
know the specifics of it, but it was supposed to allow finegrained
control of prerequisite handling.
Looking for code that added session as a parameter to the attain tags I
think.
Bob / Jason will probably know more.
Wheth
It appears to be a problem with executing more than one goal at a time:
maven clean cdit:build fails
maven clean; maven cdit:build works
This isn't always the case (other projects have just the cdit:build fail),
so there is definitely more to it - but I'm leaving it at that until I can
try it out
Hi,
It seems I'm being bitten by these again - seems to happen whenever I
upgrade!
On some systems, it fails as it can't find one of these dependencies (no
proxy server, so it is my own repo). I need to manually install these on my
own repo, but if they mismatch maven versions, all sorts of thing
I've tried cleaning out my repo, plugin cache, and running again under CVS
HEAD and it isn't working. It does work on some projects which is the
strange thing.
b9 is still working fine after doing all of the above.
It may not be a werkz thing, but I'll see how I go tracking it down with the
werkz
On Tue, 2003-07-15 at 20:35, Brett Porter wrote:
> Hi,
>
> It seems some of the changes made to werkz late in b10 have broken the
> reactor in some cases.
> I was using a build from CVS of about 1 or 2 weeeks ago that was fine, but
> rolling out b10 has caused a lot of "unknown goal" exceptions wh
> Debugging it I have seen WerkzProject return "null" to the eachGoal var in
> the plugin manager, but I can't debug werkz as the source at
> cvs.werkz.sf.net is out of date. I'm guessing the werkz that got dropped
> with b10 is a build from somewhere else?
cvs.codehaus.org:/cvsroot/werkz co werkz
Hi,
It seems some of the changes made to werkz late in b10 have broken the
reactor in some cases.
I was using a build from CVS of about 1 or 2 weeeks ago that was fine, but
rolling out b10 has caused a lot of "unknown goal" exceptions when running
under reactor. Changing into the appropriate dir a
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-572
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: Brett Porter
Created: Tue, 15 Jul 2003 5:49 PM
Body:
I thought about plugging it in to Maven's Java startup, but it would require reading
some XML file like you say to find the files. For a once only task, it seemed like
michal 2003/07/15 12:05:12
Modified:src/plugins-build/ear/xdocs properties.xml
src/plugins-build/ear plugin.jelly
Log:
Just changed my mind about the name of one of the properties.
Still think that 'ear.appxml.war.context-root' is way to lng.
Revision Chan
Message:
The following issue has been resolved as FIXED.
Resolver: Michal Maczka
Date: Tue, 15 Jul 2003 2:26 PM
Fixed
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-565
Here is an ov
michal 2003/07/15 12:00:19
Modified:src/plugins-build/ear/xdocs properties.xml changes.xml
Log:
Fixes for MAVEN-565.
Documentation of some properties was outdated
Revision ChangesPath
1.5 +3 -3 maven/src/plugins-build/ear/xdocs/properties.xml
Index: pro
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-571
Here is an overview of the issue:
--
Hi folks,
I had http://www.maven.org as a bookmark but it contains an old
website of MAVEN (last updated 19.Feb.2003) since the current site is
located at http://maven.apache.org/
Is it possible to forward or redirect it to the official site ... I
made a fool of myself complaining that the ite
jvanzyl 2003/07/15 05:21:44
Modified:xdocsstatus.xml
Log:
o Updating
Revision ChangesPath
1.14 +11 -2 maven/xdocs/status.xml
Index: status.xml
===
RCS file: /home/cvs/maven/xdocs/status.
The following issue has been updated:
Updater: Willie Vu (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Jul 2003 7:15 AM
Comment:
calling shutdown.sh instead of shutdown
Changes:
Attachment changed to shutdown.3.2.patch.txt
The following issue has been updated:
Updater: Willie Vu (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Jul 2003 7:15 AM
Comment:
calling shutdown.sh instead of shutdown
Changes:
Attachment changed to shutdown.3.0.patch.txt
The following issue has been updated:
Updater: Willie Vu (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Jul 2003 7:13 AM
Comment:
1. calling run.sh instead of run
2. must export JAVA_OPTS. otherwise the jboss.server.home.dir and
jboss.server.home.url are not set
Changes:
The following issue has been updated:
Updater: Willie Vu (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Jul 2003 7:10 AM
Comment:
This patch adds implementation to jboss:start and jboss:stop for Linux
Changes:
Attachment changed to plugin.jelly.patch.570.txt
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-570
Here is an overview of the issue:
--
The following issue has been updated:
Updater: Willie Vu (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Jul 2003 6:42 AM
Comment:
The problem is that is missing
Attached is a patch
Changes:
Attachment changed to plugin.jelly.patch.txt
---
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-569
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: Brian Ewins
Created: Tue, 15 Jul 2003 6:16 AM
Body:
See also http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-568
The 'sucks' code is designed to import jars into the local repository - possibly
overkill, but if
The following issue has been updated:
Updater: Brian Ewins (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Jul 2003 5:37 AM
Comment:
sucks plugin, first draft
Changes:
Attachment changed to sucks.zip
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-568
Here is an overview of the issue:
--
Last 500 lines of a clean bootstrap build of maven at 20030715-0317
[exec] [jar] Building jar:
/home/bwalding/src/maven/src/plugins-build/vdoclet/target/maven-vdoclet-plugin-1.0.jar
[exec] [copy] Copying 1 file to /home/bwalding/.maven/repository/maven/jars
[exec
30 matches
Mail list logo
