Archiva 1.0-alpha-2 is out in the wild... what's next? 1.0-beta-1
seems reasonable, but /topic in #archiva says coming soon, the
Archiva 1.0 (the Ship It release).
Joakim has mentioned wanting to get reporting in order, and I'm
interested in making sure all the links in the web ui work
On 03/07/2007, at 3:28 AM, Wendy Smoak wrote:
Archiva 1.0-alpha-2 is out in the wild... what's next? 1.0-beta-1
seems reasonable, but /topic in #archiva says coming soon, the
Archiva 1.0 (the Ship It release).
I was kidding (but that should be the focus from now on. Get it
done.) I agree
I agree.
I view 1.0-beta-1 as feature complete.
The current missing features ...
* Reporting (about 80% there right now, just some UI pieces left to hook up)
* Maven 1 Client Support (about 40% complete. need to hook up
DynamicGetServlet)
* Live documentation. (present in archiva.war)
-
Sounds good. With the M1 client support, can you post a small design
proposal first since last I remember we didn't reach consensus on how
it should be implemented?
- Brett
On 03/07/2007, at 8:15 AM, Joakim Erdfelt wrote:
I agree.
I view 1.0-beta-1 as feature complete.
The current
Just to capture some talk on irc today...
I think the strategy moving forward is going to be get some of jira
cleaned up a la the recent maven jira push and continuum 1.1 is going
to get wrapped up a bit for the first feature complete beta release
very soon.
there are some cool things going on
Wendy Smoak a écrit :
On 7/2/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
The latest docs is there:
http://docs.codehaus.org/pages/viewpage.action?pageId=73595
Thanks. This is actually someone trying to put it behind a different
proxy (not httpd + mod_proxy). I don't have enough info
Jesse McConnell a écrit :
Just to capture some talk on irc today...
I think the strategy moving forward is going to be get some of jira
cleaned up a la the recent maven jira push and continuum 1.1 is going
to get wrapped up a bit for the first feature complete beta release
very soon.
I'll
On 03/07/2007, at 5:54 AM, Emmanuel Venisse wrote:
Jesse McConnell a écrit :
Just to capture some talk on irc today...
I think the strategy moving forward is going to be get some of jira
cleaned up a la the recent maven jira push and continuum 1.1 is going
to get wrapped up a bit for the
On 7/2/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Wendy Smoak a écrit :
I can (sort of) get it to work if I visit
http://otherserver/apps/continuum/index.action. The complaint is that
Continuum is sending Location headers/redirects with hostnames in
them. That's apparently why the
Harish Kachoria wrote:
Hello All,
I'm trying to integrating Maven in my project.
I was quite comfortable using maven 1.0.
But with Maven 2.0 I have one problem to define dependency of a jar file.
I wants to define dependency without having a version number. how can
I do
that ??
Please
Ok, we already really had a passing vote to bring this over here that
was sat on due to the controversy raised, so I haven't changed my
vote there:
+1 to ArchetypeNG coming in
(Please make sure an IP clearance form is submitted for the code).
I already believe Raphaël has demonstrated
2007/7/2, Brett Porter [EMAIL PROTECTED]:
I'm interested to know if anyone else is having success with the
current code, though, given the number of +1's. I couldn't get it to
run at all - after 5 attempts and fixes I'd need to code read to get
any further. Not a blocker to bringing it across,
On 7/2/07, Ralph Goers [EMAIL PROTECTED] wrote:
Harish Kachoria wrote:
I'm really curious as to how you got that to work in maven 1.0? AFAIK
version numbers have always been required.
+1
Stéphane
Ralph
-
To unsubscribe,
The latest docs is there:
http://docs.codehaus.org/pages/viewpage.action?pageId=73595
Brett Porter a écrit :
I believe you can use that configuration, but like you I never have,
just pointing it directly at :8080 from httpd.
On 01/07/2007, at 3:11 PM, Wendy Smoak wrote:
Is the Jetty
Hi,
Pumping this out to the list, since I don't have time to flood JIRA,
and some may be answerable beforehand or get taken care of before the
import. I'll take responsibility for collating this and any
responses, retesting against the final imported code, and getting
into JIRA (Which
Probably referring to the jar tag which let you hack the repository
path. It's forbidden in Maven 2 (and was deprecated in 1.1 too I think?)
- Brett
On 02/07/2007, at 5:39 PM, Stephane Nicoll wrote:
On 7/2/07, Ralph Goers [EMAIL PROTECTED] wrote:
Harish Kachoria wrote:
I'm really curious
On 02/07/2007, at 4:54 PM, Raphaël Piéroni wrote:
Please add some jira and assign them to me.
I will only have time for this after the 15/07
(after holidays)
Bit too much to get in there just now - we don't need to rush that
part, I just wanted to make sure they were known.
Most
No, it's still supported and not deprecated in Maven 1.1:
http://maven.apache.org/maven-1.x/reference/maven-model/3.0.2/maven.html#class_dependency
-Lukas
Brett Porter wrote:
Probably referring to the jar tag which let you hack the repository
path. It's forbidden in Maven 2 (and was
Lukas Theussl wrote:
No, it's still supported and not deprecated in Maven 1.1:
http://maven.apache.org/maven-1.x/reference/maven-model/3.0.2/maven.html#class_dependency
-Lukas
It should have been. I can certainly understand why support for this was
removed in version 2.
Ralph
On 2 Jul 07, at 12:57 AM 2 Jul 07, Brett Porter wrote:
On 02/07/2007, at 4:54 PM, Raphaël Piéroni wrote:
Please add some jira and assign them to me.
I will only have time for this after the 15/07
(after holidays)
Bit too much to get in there just now - we don't need to rush that
part, I
On 29/06/07, Jason van Zyl [EMAIL PROTECTED] wrote:
Put it in the wiki.
Consider it put:
http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers
Feedback welcome.
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On 2 Jul 07, at 7:37 AM 2 Jul 07, Mark Hobson wrote:
On 29/06/07, Jason van Zyl [EMAIL PROTECTED] wrote:
Put it in the wiki.
Consider it put:
http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers
Very nice, thanks.
Feedback welcome.
Will take a look today.
Mark
Did you put this on the branch as well?
On 30 Jun 07, at 10:31 AM 30 Jun 07, [EMAIL PROTECTED] wrote:
Author: pschneider
Date: Sat Jun 30 10:31:45 2007
New Revision: 552182
URL: http://svn.apache.org/viewvc?view=revrev=552182
Log:
[MNG-2919] Add fix for depMan scope overwriting to the trunk.
Yes -- I put it in the branch for the 2.0.7 release, but hadn't ported it
up. This, of course, was before I asked you for clarification about putting
code in the trunk first and then merging to the branch ;o)
On 7/2/07, Jason van Zyl [EMAIL PROTECTED] wrote:
Did you put this on the branch as
Thanks guys, new version doesn't work.
I get the following error when I type mvn idea:idea
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Internal error in
Works fine here.
Show your pom and a debug execution of mvn idea:idea (mvn idea:idea -X
debug.log
Stéphane
On 7/2/07, Fustrated [EMAIL PROTECTED] wrote:
Thanks guys, new version doesn't work.
I get the following error when I type mvn idea:idea
[INFO]
On 2 Jul 07, at 8:18 AM 2 Jul 07, Fustrated wrote:
Thanks guys, new version doesn't work.
I suggest you learn some basic OSS etiquette rules.
Sarcasm will win your requests for help a one way ticket to /dev/null.
Something like:
Is anyone having any problems with the IDEA plugin, I am
On 2 Jul 07, at 8:15 AM 2 Jul 07, Patrick Schneider wrote:
Yes -- I put it in the branch for the 2.0.7 release, but hadn't
ported it
up. This, of course, was before I asked you for clarification
about putting
code in the trunk first and then merging to the branch ;o)
Cool, thanks. Not
I have been given a requirement to put our tagdocs inside a project WAR
file. Unfortunately, the tagdocs get generated as part of the site
phase, which comes AFTER 'mvn install', which creates the desired war
file. Does anybody have any ideas how to do this?
In maven 1.0 we were using jar tag to define jar dependancy. which I think
deprecated.
How ever in my current project I'm trying to integrating Maven 2.0 (Before
that we make jar using javac and used it).
Problems which I have -
- I have many jars which are third party/inbuild libraries and
Le vendredi 29 juin 2007, Hervé BOUTEMY a écrit :
Le vendredi 29 juin 2007, Hervé BOUTEMY a écrit :
patch MANTTASKS-76_site-release.diff added to MANTTASKS-76
added patch MANTTASKS-76_license.diff too, while we're at it...
are these patches ok to get the release out, or should I change
On 2 Jul 07, at 2:20 PM 2 Jul 07, Hervé BOUTEMY wrote:
Le vendredi 29 juin 2007, Hervé BOUTEMY a écrit :
Le vendredi 29 juin 2007, Hervé BOUTEMY a écrit :
patch MANTTASKS-76_site-release.diff added to MANTTASKS-76
added patch MANTTASKS-76_license.diff too, while we're at it...
are these
Hi,
Does anyone mind if I add a non lifecycle forking version of the
eclipse:eclipse and eclipse:m2eclipse commands. I am using these
commands in a set of tooling and we know that the generate sources
phase has executed. Using the existing mojo forks a lifecycle so
anything up to and
http://maven.apache.org/maven-1.x/faq.html#unversioned-jars
You can name that what you wish in build/deployment/production, they
just need a version in the repository.
On 03/07/2007, at 6:27 AM, Harish Kachoria wrote:
In maven 1.0 we were using jar tag to define jar dependancy.
which I
+1. A nice future feature in plexus would be the ability to control
these parameters in a pre-run/initialize phase.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 8:00 PM
To: Maven Developers List
Subject: Non lifecycle forking
I'm getting an error building the 2.0.7-snapshot invoker:
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.861
sec FAILURE!
testBuildShouldFail(org.apache.maven.shared.invoker.DefaultInvokerTest)
Time elapsed: 3.782 sec FAILURE!
junit.framework.AssertionFailedError:
I can confirm this. It was messing up the invoker tests even until I
changed it manually. I'll write it up if it's not already and fix it.
Thanks,
Brian
-Original Message-
From: Tom Huybrechts [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 23, 2007 2:48 PM
To: Maven Developers List
Brett Porter wrote:
http://maven.apache.org/maven-1.x/faq.html#unversioned-jars
You can name that what you wish in build/deployment/production, they
just need a version in the repository.
Brett, He wants to do this in Maven 2, not Maven 1.
Ralph
I know, the material is the same (it maybe should be in the m2 faq
too :)
ie, the answer in m1 is you can but you shouldn't and here's how to
workaround. In m2, it's you can't, and here's how to work around.
On 03/07/2007, at 12:34 PM, Ralph Goers wrote:
Brett Porter wrote:
I can rename jar in my development env, not a isssue.
Problem is,
We want build scripts in such way so that we can use same build scripts on
dev as well as on production.
and for this purpose I wants to give dependancy of jar in the same way as
they are reffered in production.
and because of
This still getting moved over to the sandbox here? Maybe good to do
it at the same time as archetype?
- Brett
On 15/06/2007, at 3:10 PM, Brett Porter wrote:
On 15/06/2007, at 3:02 PM, Jason van Zyl wrote:
On 14 Jun 07, at 9:33 PM 14 Jun 07, Brett Porter wrote:
Hi,
Took a look at
41 matches
Mail list logo
