was that just hitting the localhost:9090/ ?
I don't think that has been fixed up yet, I mostly just go straight to
a page, like http://localhost:9090/groupSummary.jsp
I'll take a look at that though and get the / working if its not,
pretty sure it wasn't
jesse
On 8/22/06, Brett Porter [EMAIL
I'll be updating the white-site...
Please see my inline comments below
Brett Porter wrote:
Feedback:
- I'd rather Release be equivalent to build now (ie, we might need
an icon for it), so added to the right-hand tasks per project, and
added to the individual project page as a button.
-
The summary page shows only a few of the release parameters. So the
Edit link is there to direct the user to the more detailed
release configuration page. But since we'll be releasing projects
one at a time, I guess I can incorporate what you mean into the new
white-site.
Just to be
Please, attach your patch to an issue.
Emmanuel
Juan F. Codagnone a écrit :
Hi,
I have some random fixes for the twiki parser (table related) and for the
rest of the Sinks.
juanpatches.diff is the whole diff, and the juanpatches.tar.gz has the
incrementals patches with a comment.
I can only guess incomplete checkout. I've never seen anything like
it, and it should just work.
However, installing Maven first is not cheating. I think it should be
the recommended way for building Maven unless you have a reason to
need to start from scratch. All the bootstrap does is
Hello guys,
I've just tried Archiva as a replacement for my maven proxy. It works
fine, but I had issues when trying to proxy my corporate repo. It is
accessed as a Windows SMB drive and proxied using a
file:/server/shared/repo URL. When Tomcat is ran as a service,
this path seems not
Hilco Wijbenga [EMAIL PROTECTED] writes:
Anyone?
Maybe you could try building maven setting the property
maven.online=false such that build does not try to download artifacts
from remote repos.
$ export MAVEN_OPTS=-Dmaven.online=false
$ sh bootstrap.sh
(assume bash...)
HTH,
--
OQube
On 8/22/06, Brett Porter [EMAIL PROTECTED] wrote:
I can only guess incomplete checkout. I've never seen anything like
it, and it should just work.
Well, don't I feel special. :-)
I removed everything and checked out again. I made sure I had the same
revision in every directory. Running
On 8/22/06, Arnaud Bailly [EMAIL PROTECTED] wrote:
Maybe you could try building maven setting the property
maven.online=false such that build does not try to download artifacts
from remote repos.
$ export MAVEN_OPTS=-Dmaven.online=false
$ sh bootstrap.sh
I tried this and it fails even quicker
On 23/08/2006, at 5:09 PM, Hilco Wijbenga wrote:
However, installing Maven first is not cheating. I think it should be
the recommended way for building Maven unless you have a reason to
need to start from scratch. All the bootstrap does is build a
functional Maven, then use that to build
Sorry, what are you expecting to happen? I would expect you to get
ResourceDoesNotExistException on every request - was this not the case?
- Brett
On 23/08/2006, at 4:53 PM, Nicolas De Loof wrote:
Hello guys,
I've just tried Archiva as a replacement for my maven proxy. It
works fine,
Hi,
Brett Porter wrote:
Should we separate them in the docs then?
+1
Mirrors we have contact with:
- planetmirror
- dotsrc
- ibiblio
There's also maven.sateh.com (really fast! :))
(http://mail-archives.apache.org/mod_mbox/maven-users/200605.mbox/[EMAIL
PROTECTED])
-- Kenney
Brett Porter wrote:
+1 under current circumstances.
Bearing in mind the following:
a) we agreed to eliminate expression over time to an explicit property
(or some other name) that would just be property=jar.forcedCreate -
this doesn't actually change anything
b) I'd actually like to be able
Hi,
You probably have a settings.xml with
localRepository~/.m2/repository/localRepository
in there.
The ~ is not expanded, so you should find a '~' directory in the same
directory where you ran bootstrap.sh.
Replace ~ with the full path to your home dir and you're good to go.
-- Kenney
The trunk version preserves the builder's name, but not its triggers
and arguments. Patch http://jira.codehaus.org/browse/MECLIPSE-139
mainly does something else, but also solves this problem (I hope
correctly ;-).
Regards,
Jochen
On 2006-08-23 02:35:39 +0200, Barrie Treloar [EMAIL
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: vendredi 11 août 2006 13:05
To: Maven Developers List
Subject: Re: Integration testing plugins
Vincent Massol wrote:
Also, Kenney do you know if the it plugin can now be used to test a
plugin
ok. fixed.
On 23/08/2006, at 11:29 PM, Jesse McConnell wrote:
ack, ya I meant .action...force of habit, did that to jason the
other day too
welcome-file-list
welcome-fileIndex.action/welcome-file
/welcome-file-list
that is in the web.xml that I thought might be source of the issue
Finally getting around to replying :)
I spoke to Edwin on IRC and he's proposed the following steps:
1) go to the project group...
2) then click on the release project icon ( a new icon )
3) then a page will prompt for the release version and the next dev
version...
4) after filling the
Some thoughts.
I could see the need to go back into the build history and creating a
release off of an older build to be quite likely too.
Also, should the locking of the project be at the Continuum/filesystem
side, or on the SCM side? If scm side, we should add
On 24/08/2006, at 12:17 AM, Joakim Erdfelt wrote:
Some thoughts.
I could see the need to go back into the build history and creating
a release off of an older build to be quite likely too.
absolutely. I think Jason has talked about checking in the release
model and tagging that in the
+1. All the JIRA issues look reasonable to push out.
Does this require a maven-archiver release first?
- Brett
On 22/08/2006, at 10:55 PM, Jason van Zyl wrote:
Hi,
There are 39 issues that have been resolved since the last release
of the JAR plugin:
+1 (also nonbinding)
Jason van Zyl wrote:
Hi,
There are 39 issues that have been resolved since the last release of
the JAR plugin:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11137fixfor=12241
I've also applied the most recent patches for optional archive
I don't have any opposition to a promoted build, whatever we call it.
I think it's a good idea.
However, I'm really over the idea of having alpha and beta releases
(even though I've been planning the latter one myself), at least in
the form we have now.
I like the idea of having promoted
Thanks brett for posting that.
white-site is available at
http://people.apache.org/~epunzalan/continuum-white-site/groupStatus.html.
It does not comply 100% with what brett and I have discussed, but it does
give the flexibility to release the whole project group or just a selected
few... which
On 23 Aug 06, at 10:49 AM 23 Aug 06, Brett Porter wrote:
+1. All the JIRA issues look reasonable to push out.
Does this require a maven-archiver release first?
Yes, so I'll call a vote for that and sync it with the JAR plugin.
Might be nice to make dependencies implicit in the vote to
The Apache Shale committers have voted to release version 1.0.3. Please
rsync the Apache repository (
http://people.apache.org/repo/m2-ibiblio-rsync-repository) to the public
Maven repositories.
Craig
On 8/23/06, Craig McClanahan [EMAIL PROTECTED] wrote:
The Apache Shale committers have voted to release version 1.0.3. Please
rsync the Apache repository (
http://people.apache.org/repo/m2-ibiblio-rsync-repository) to the public
Maven repositories.
Craig, how did you deploy this? I don't
On 23 Aug 06, at 2:40 PM 23 Aug 06, Wendy Smoak wrote:
On 8/23/06, Craig McClanahan [EMAIL PROTECTED] wrote:
The Apache Shale committers have voted to release version 1.0.3.
Please
rsync the Apache repository (
http://people.apache.org/repo/m2-ibiblio-rsync-repository) to the
public
On 8/23/06, Jason van Zyl [EMAIL PROTECTED] wrote:
If you are building with m2 there is no reason for the metadata not
to be there. If the release plugin was used then the metadata would
be there. How was this release made?
Shale and Struts both use a 'test build' stage where we tag and build
On 23 Aug 06, at 3:32 PM 23 Aug 06, Wendy Smoak wrote:
On 8/23/06, Jason van Zyl [EMAIL PROTECTED] wrote:
If you are building with m2 there is no reason for the metadata not
to be there. If the release plugin was used then the metadata would
be there. How was this release made?
Shale and
On 8/23/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 8/23/06, Jason van Zyl [EMAIL PROTECTED] wrote:
If you are building with m2 there is no reason for the metadata not
to be there. If the release plugin was used then the metadata would
be there. How was this release made?
Shale and Struts
On 23 Aug 06, at 3:59 PM 23 Aug 06, Craig McClanahan wrote:
On 8/23/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 8/23/06, Jason van Zyl [EMAIL PROTECTED] wrote:
If you are building with m2 there is no reason for the metadata not
to be there. If the release plugin was used then the metadata
On 8/23/06, Jason van Zyl [EMAIL PROTECTED] wrote:
I think here you could just use the release plugin instead of the
deploy. You would release:prepare to tag a release and then
release:perform to build and deploy it. If you do this to a staging
area you can still vote on it and move it
On 8/23/06, Jason van Zyl [EMAIL PROTECTED] wrote:
On 23 Aug 06, at 3:59 PM 23 Aug 06, Craig McClanahan wrote:
Would a quick and dirty fix be just to allow the deploy-to URL be
overridden on the command line? That way we could leave our POMs
defaulting
to the test builds repository, and
On 23 Aug 06, at 4:03 PM 23 Aug 06, Wendy Smoak wrote:
On 8/23/06, Jason van Zyl [EMAIL PROTECTED] wrote:
I think here you could just use the release plugin instead of the
deploy. You would release:prepare to tag a release and then
release:perform to build and deploy it. If you do this to a
On 23 Aug 06, at 4:06 PM 23 Aug 06, Wendy Smoak wrote:
On 8/23/06, Jason van Zyl [EMAIL PROTECTED] wrote:
On 23 Aug 06, at 3:59 PM 23 Aug 06, Craig McClanahan wrote:
Would a quick and dirty fix be just to allow the deploy-to URL be
overridden on the command line? That way we could leave
+1
Vincent
2006/8/22, Jason van Zyl [EMAIL PROTECTED]:
Hi,
There are 39 issues that have been resolved since the last release of
the JAR plugin:
http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=truepid=11137fixfor=12241
I've also applied the most recent patches for optional
Jason van Zyl wrote:
Hi,
There are 39 issues that have been resolved since the last release of
the JAR plugin:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11137fixfor=12241
I've also applied the most recent patches for optional archive creation.
+1
Jason van Zyl
Allan Ramirez wrote:
maven-antrun-plugin documentation is now ready for review.
Staging site can be found here:
http://people.apache.org/~aramirez/maven-antrun-plugin/
jira issue:
http://jira.codehaus.org/browse/MANTRUN-55
Thank you very much Franz See for your great work here.
Cheers,
allan
On 23 Aug 06, at 4:51 PM 23 Aug 06, Dennis Lundberg wrote:
Jason van Zyl wrote:
Hi,
There are 39 issues that have been resolved since the last release
of the JAR plugin:
http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=truepid=11137fixfor=12241 I've also applied the most
recent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
what is the actual state about javax JARs at ibiblio?
I have seen that javax.mail is available as JAR in the central repo.
Does this mean that potentially other javax JARs could be made available there?
I would love to java javax.annotation
On 23 Aug 06, at 10:02 AM 23 Aug 06, Brett Porter wrote:
Finally getting around to replying :)
I spoke to Edwin on IRC and he's proposed the following steps:
1) go to the project group...
2) then click on the release project icon ( a new icon )
3) then a page will prompt for the release
sun jars come through http://maven-repository.dev.java.net/
You have to ask there.
On 8/23/06, Joerg Hohwiller [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
what is the actual state about javax JARs at ibiblio?
I have seen that javax.mail is available as JAR
That's partially synced to ibiblio (some javax.* and all com.sun.*)
On 8/23/06, Mike Perham [EMAIL PROTECTED] wrote:
You might try this instead of ibiblio:
https://maven-repository.dev.java.net/nonav/
On 8/23/06, Joerg Hohwiller [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Yes, I usually wrap them as one vote so people know what they are
voting for. I think that's a good idea (and additionally, marking the
SVN rev/snapshot number so that we know to restart the vote if it
changes).
I think the 72h is wise even in unanimous situations as something
usually
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (29 issues)
Subscriber: mavendevlist
Key Summary
MEV-436 JOTM 2.0.10 incorrectly specifies javax.resource/connector-1.0 it
needs connector-1.5.
http://jira.codehaus.org/browse/MEV-436
MEV-435
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (21 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-1079serp
http://jira.codehaus.org/browse/MAVENUPLOAD-1079
MAVENUPLOAD-1078subethasmtp 1.0.3 bundles
The original proposal was web services based, but the entire
process occurring from Continuum is definitely useful. I think the
concrete drivers are:
Right, so like other stuff there is a backend service, and it is
exposed in the same way to both a web interface and an xmlrpc client,
but
Feedback:
- I'd rather Release be equivalent to build now (ie, we might need
an icon for it), so added to the right-hand tasks per project, and
added to the individual project page as a button.
- I don't think this should operate on a group. It doesn't
necessarily equate to a multi-module
Hi,
On 8/23/06, Kenney Westerhof [EMAIL PROTECTED] wrote:
You probably have a settings.xml with
localRepository~/.m2/repository/localRepository
in there.
Yup, that was the problem.
After about a dozen tries I seem to have a successful build ...
however ... Maven doesn't get installed so the
Mmmh, it's being installed to M2_HOME/../maven-2.1-SNAPSHOT instead of
simply M2_HOME. This is to avoid overwriting a previous installation?
Obviously, M2_HOME/../maven-2.1-SNAPSHOT/bin is not in $PATH... Am I
required to use an M2_HOME that ends with maven-2.1-SNAPSHOT?
On 8/23/06, Hilco
51 matches
Mail list logo
