Implement 'remember me' in the web interface
Key: CONTINUUM-513
URL: http://jira.codehaus.org/browse/CONTINUUM-513
Project: Continuum
Type: New Feature
Reporter: Trygve Laugstol
--
This message is automatically
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051214.163000.txt
Consistency in layout of Continuum download page to the Maven 2.0 download page
---
Key: CONTINUUM-514
URL: http://jira.codehaus.org/browse/CONTINUUM-514
Project: Continuum
Type: Task
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051214.17.txt
+1
I'm all for splitting up into action components, but retaining a
Continuum interface as a single entry point to those
- Brett
John Casey wrote:
I think we have to be careful when splitting up a public api like
this. It's possible Continuum may need to be embedded someday, and if
so, it
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051214.180001.txt
ok, so we'll have some data object store access (ProjectStore, BuildStore...) and DefaultContinuum
will use them. Webwork actions will use them too or they'll use Continuum interface?
Emmanuel
Brett Porter a écrit :
+1
I'm all for splitting up into action components, but retaining a
[ http://jira.codehaus.org/browse/CONTINUUM-514?page=all ]
Brett Porter updated CONTINUUM-514:
---
Fix Version: (was: 1.0.2)
1.1
Consistency in layout of Continuum download page to the Maven 2.0 download
page
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051214.183002.txt
[ http://jira.codehaus.org/browse/SCM-114?page=comments#action_53418 ]
Neil Padgen commented on SCM-114:
-
We wouldn't be able to use the last directory in the SCM URL, as we use that
last directory for branches; e.g. //depot/project1/MAIN and
[ http://jira.codehaus.org/browse/SCM-113?page=comments#action_53419 ]
mike perham commented on SCM-113:
-
Good idea on the Description. Note that Maven SCM does not know anything about
the context in which it is running. It does not know that it is
[ http://jira.codehaus.org/browse/SCM-114?page=comments#action_53464 ]
Zabli commented on SCM-114:
---
The perforce plugin ignores the environment variables P4CLIENT, P4PASSWD.
The plugin should check these variable and then use them if they are present.
Clientspec
Some of you expressed an interest.
Please note that it is close, but not quite, ready to be tested on a wider
scale (such as the users list). I'm still stummped at how to inject certain
values into the Ruby object. But the projects and sourcecode can be
downloaded from here:
built-in property containing current timestamp
--
Key: MNG-1832
URL: http://jira.codehaus.org/browse/MNG-1832
Project: Maven 2
Type: New Feature
Versions: 2.0.1
Reporter: Michal Stochmialek
Current timestamp
[ http://jira.codehaus.org/browse/MRM-53?page=all ]
Edwin Punzalan closed MRM-53:
-
Resolution: Fixed
Patch applied, thanks!
repoort on invalid POMs
---
Key: MRM-53
URL: http://jira.codehaus.org/browse/MRM-53
[ http://jira.codehaus.org/browse/MNG-1833?page=comments#action_53398 ]
Olivier Lamy commented on MNG-1833:
---
Look at MNG-1655.
war:clean goal
--
Key: MNG-1833
URL: http://jira.codehaus.org/browse/MNG-1833
Project:
[ http://jira.codehaus.org/browse/MNG-1833?page=all ]
Jochen Wiedmann closed MNG-1833:
Resolution: Duplicate
Sorry, I missed MNG-1655. Clearly, this is a duplicate.
However, given the fact that closing MNG-1655 in favour of MNG-1669 (with a
more
[ http://jira.codehaus.org/browse/MNG-1509?page=comments#action_53401 ]
David Boden commented on MNG-1509:
--
Morning. This is marked as fixed in 2.0.1 (which is now available on the
ibiblio repository).
I'm using the following:
activation
maven-reporting-impl version 2.0.1 missing component
org.codehaus.doxia.site.renderer.SiteRenderer
--
Key: MNG-1834
URL: http://jira.codehaus.org/browse/MNG-1834
Project: Maven
Ability to specify more than 1 check configuration file and file sets for each
of these configurations
--
Key: MNG-1835
URL: http://jira.codehaus.org/browse/MNG-1835
inherited plugin dependencies
-
Key: MNG-1836
URL: http://jira.codehaus.org/browse/MNG-1836
Project: Maven 2
Type: Bug
Versions: 2.0
Reporter: Gilles Scokart
I have project composed of a reactor/parent pom.xml and a few
Hi all,
I'm working on a maven 2 plugin to compile IDL files. Alan Cabrera
created an initial plugin, and I am adding some additional features.
I have a couple of questions I'd like to have some help with.
I need to be specify various parameters to pass to the compiler backend.
For each idl
[ http://jira.codehaus.org/browse/MNG-1837?page=all ]
Dan Tran updated MNG-1837:
--
Attachment: MVN-1837.patch
deploy-file succeeds even when local file not found
---
Key: MNG-1837
URL:
jar plugin recreates jar files all the time
---
Key: MNG-1838
URL: http://jira.codehaus.org/browse/MNG-1838
Project: Maven 2
Type: Bug
Components: maven-jar-plugin
Versions: 2.0.1
Reporter: Jochen Wiedmann
System Scope dependencies don't work
Key: MNG-1839
URL: http://jira.codehaus.org/browse/MNG-1839
Project: Maven 2
Type: Bug
Components: maven-compiler-plugin
Versions: 2.0.1
Reporter: David Boden
I've added the
[
http://jira.codehaus.org/browse/MAVENUPLOAD-625?page=comments#action_53412 ]
Takayuki Kaneko commented on MAVENUPLOAD-625:
-
Sorry, I found it in jfreechart groupId.
It is both in jfreechart and jfree groupId. I searched it in jfree. :-)
Support persistent and transient clientspecs
Key: SCM-113
URL: http://jira.codehaus.org/browse/SCM-113
Project: Maven SCM
Type: New Feature
Components: maven-scm-provider-perforce
Versions: 1.0-beta-3
Clientspec naming
-
Key: SCM-114
URL: http://jira.codehaus.org/browse/SCM-114
Project: Maven SCM
Type: Improvement
Components: maven-scm-provider-perforce
Versions: 1.0-beta-3
Reporter: mike perham
Fix For: 1.0-beta-3
Several
[ http://jira.codehaus.org/browse/SCM-114?page=comments#action_53413 ]
mike perham commented on SCM-114:
-
That should be - ${user} -. Cursed wiki formatting!
Clientspec naming
-
Key: SCM-114
URL:
[ http://jira.codehaus.org/browse/SCM-114?page=comments#action_53414 ]
Wim Deblauwe commented on SCM-114:
--
I can answer for Emmanuel, because I have asked the same question for
ClearCase. It does not :(.
For ClearCase, I implemented it with using the last
[ http://jira.codehaus.org/browse/SCM-113?page=comments#action_53415 ]
Wim Deblauwe commented on SCM-113:
--
For ClearCase, we only support what you call a persistent clientspec. The scm
url points to the location of the spec on some server. The
[ http://jira.codehaus.org/browse/MNG-1838?page=comments#action_53416 ]
Eric Andresen commented on MNG-1838:
I am most definitely interested in this suggestion; we have a 20-module
project, which has at least 5 major projects (with wars and a jar
Comments inline.
Eric Redmond wrote:
Some of you expressed an interest.
Please note that it is close, but not quite, ready to be tested on a wider
scale (such as the users list). I'm still stummped at how to inject certain
values into the Ruby object. But the projects and sourcecode can be
[ http://jira.codehaus.org/browse/SCM-110?page=all ]
mike perham updated SCM-110:
Attachment: (was: force.txt)
Perforce should force sync
--
Key: SCM-110
URL: http://jira.codehaus.org/browse/SCM-110
I think we have to be careful when splitting up a public api like this.
It's possible Continuum may need to be embedded someday, and if so, it
would be much better to have a single interface for controlling
it...even if it means that interface delegates most of its work. While I
think you can
Preview generated site
--
Key: CONTINUUM-512
URL: http://jira.codehaus.org/browse/CONTINUUM-512
Project: Continuum
Type: Wish
Components: Web interface
Reporter: Aviran Mordo
Priority: Minor
It will be nice to have a way to make
[ http://jira.codehaus.org/browse/SCM-113?page=comments#action_53417 ]
Neil Padgen commented on SCM-113:
-
I can see the advantages of both persistent and transient clientspecs. I would
expect the persistent clientspec to be used more often than the
Reason: Parent: null:plexus-compiler:jar:1.4 of project:
unknown:plexus-compiler-api has wrong packaging: jar. Must be 'pom'
Key: MEV-258
URL:
Hi All,
I am getting blank report for javadoc when i run mvn site:site using maven
2.0.1 . Please let me know if you guys have any idea or workaround.
Thanks.
[YUGENDER RAYABARAPU]
[ http://jira.codehaus.org/browse/MNG-1509?page=comments#action_53420 ]
Bernd Bohmann commented on MNG-1509:
Added more Testcases to DefaultProfileManagerTest.java m unfortunately they are
os depend (my os is unix):
public void
[ http://jira.codehaus.org/browse/MNG-1819?page=comments#action_53424 ]
Christopher Cobb commented on MNG-1819:
---
I am also running cygwin.
If I open a windows cmd shell, I get:
C:\downloads\maven-2.0.1\binmvn
[INFO] Scanning for projects...
[INFO]
Hi All,
I am getting blank report for javadoc when i run mvn site:site using maven
2.0.1 . Please let me know if you guys have any idea or workaround.
Thanks.
[YUGENDER RAYABARAPU]
[YUGENDER RAYABARAPU]
[ http://jira.codehaus.org/browse/SCM-113?page=comments#action_53427 ]
skylab commented on SCM-113:
Hi Mike,
can we add some additional parameters to the SCM URL? Just the client-name or
something else:
[ http://jira.codehaus.org/browse/MNG-1839?page=comments#action_53429 ]
David Boden commented on MNG-1839:
--
Sorry, please ignore for the moment.
I've just downloaded a newer version than I thought I had installed. I'll close
this issue if the bug is fixed
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051214.173000.txt
Increment Model Version and enable stricter checks.
---
Key: MNG-1840
URL: http://jira.codehaus.org/browse/MNG-1840
Project: Maven 2
Type: Bug
Components: POM
Versions: 2.1
Reporter: Joakim Erdfelt
maven-site-plugin break maven-javadoc-plugin JavaDocs
-
Key: MPSITE-46
URL: http://jira.codehaus.org/browse/MPSITE-46
Project: maven-site-plugin
Type: Bug
Components: plugin
Environment:
[ http://jira.codehaus.org/browse/MNG-1278?page=all ]
Brett Porter closed MNG-1278:
-
Resolution: Fixed
confirmed (I used the firefox linkcheck plugin)
Broken Links on Getting Started page
Key: MNG-1278
[ http://jira.codehaus.org/browse/MEV-257?page=all ]
Carlos Sanchez closed MEV-257:
--
Assign To: Carlos Sanchez
Resolution: Incomplete
The structure is right
To upload the binaries, read
[ http://jira.codehaus.org/browse/MNG-1835?page=comments#action_53436 ]
Joakim Erdfelt commented on MNG-1835:
-
I was working on a ...
configuration
configLocations
configLocation.../configLocation
configLocation.../configLocation
[ http://jira.codehaus.org/browse/MNG-1835?page=comments#action_53435 ]
Joakim Erdfelt commented on MNG-1835:
-
I was working on a ...
configuration
configLocations
configLocation.../configLocation
configLocation.../configLocation
[ http://jira.codehaus.org/browse/MNG-1834?page=all ]
John Casey updated MNG-1834:
Assign To: John Casey
Fix Version: 2.0.1-1
Remaining Estimate: 30 minutes
Original Estimate: 30 minutes
maven-reporting-impl version 2.0.1
[ http://jira.codehaus.org/browse/MNG-1819?page=all ]
John Casey updated MNG-1819:
Assign To: John Casey
Fix Version: 2.0.1-1
StringIndexOutOfBoundsException when running maven
--
Key:
Hi all,
If you've been watching this list, the users list, or JIRA, I'm sure
you've noticed that we managed to introduce some new bugs in 2.0.1. Some
of these are critical, and will block the use of this version.
What I'd like to do is release a bugfix version, 2.0.1-1, to address
these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Casey wrote, On 12/14/2005 11:41 AM:
Hi all,
If you've been watching this list, the users list, or JIRA, I'm sure
you've noticed that we managed to introduce some new bugs in 2.0.1. Some
of these are critical, and will block the use of this
That's what happen when you make a release while you drink beer ;) No
more releases during the Hackathon !
Why not call it 2.0.3 ?
On 12/14/05, John Casey [EMAIL PROTECTED] wrote:
Hi all,
If you've been watching this list, the users list, or JIRA, I'm sure
you've noticed that we managed to
John Casey wrote:
Hi all,
If you've been watching this list, the users list, or JIRA, I'm sure
you've noticed that we managed to introduce some new bugs in 2.0.1. Some
of these are critical, and will block the use of this version.
What I'd like to do is release a bugfix version, 2.0.1-1, to
[ http://jira.codehaus.org/browse/MNG-1841?page=all ]
Emmanuel Venisse updated MNG-1841:
--
Fix Version: 2.0.1-1
maven-site-plugin break maven-javadoc-plugin JavaDocs
-
Key: MNG-1841
+1
I'd prefer too 2.0.2
I added MNG-1841 because it's blocker for site generation. All our reports are empty in maven site
(http://maven.apache.org/maven-reports.html)
Emmanuel
John Casey a écrit :
Hi all,
If you've been watching this list, the users list, or JIRA, I'm sure
you've
[ http://jira.codehaus.org/browse/MNG-1509?page=all ]
John Casey updated MNG-1509:
Fix Version: (was: 2.0.1)
2.0.2
Profile activation by os doesn't work
-
Key: MNG-1509
URL:
[ http://jira.codehaus.org/browse/MNG-1841?page=all ]
Brett Porter closed MNG-1841:
-
Assign To: Brett Porter
Resolution: Duplicate
Fix Version: (was: 2.0.2)
maven-site-plugin break maven-javadoc-plugin JavaDocs
John Casey wrote:
I'm not too interested in which version number we use; I only suggested
this notation since it's definitely a lot smaller than what we did for
2.0.1, and what we've got slated for 2.0.2...that, and it's meant to
modify the 2.0.1 release so it'll work.
2.0.2 is fine with me.
Hi,
We've been receiving a lot of questions about the javadoc report, and
we've got some critical fixes ready for release which should solve a
good deal of these problems. It looks like it's time to release the next
beta of this plugin.
I'll give it the customary 72 hrs.
Here's my +1.
+1
On 12/14/05, John Casey [EMAIL PROTECTED] wrote:
Hi,
We've been receiving a lot of questions about the javadoc report, and
we've got some critical fixes ready for release which should solve a
good deal of these problems. It looks like it's time to release the next
beta of this plugin.
On Wed, 2005-12-14 at 19:30 +0100, Emmanuel Venisse wrote:
ok, so we'll have some data object store access (ProjectStore, BuildStore...)
and DefaultContinuum
will use them. Webwork actions will use them too or they'll use Continuum
interface?
I still disagree with splitting up the
[ http://jira.codehaus.org/browse/MNG-1800?page=all ]
Matthew Beermann closed MNG-1800:
-
Resolution: Fixed
Fix Version: (was: 2.0.3)
Turns out that this wasn't directly caused by MNG-441 or MNG-1303, but the
resolution of those allowed me
[
http://jira.codehaus.org/browse/MAVENUPLOAD-629?page=comments#action_53447 ]
Chris Sterling commented on MAVENUPLOAD-629:
I had seen all of the jar files pushed to the Maven 1.x and 2.x repositories,
but do not see the zip files uploaded as
[ http://jira.codehaus.org/browse/MNG-1373?page=comments#action_53448 ]
Dennis Lundberg commented on MNG-1373:
--
See MNG-1686 that also has a patch for this.
Broken links and improperly formatted headings in
On 12/14/05, Trygve Laugstøl [EMAIL PROTECTED] wrote:
I still disagree with splitting up the ContinuumStore into a set of
DAOs. I've never seen the advantage of having a single DAO for each
domain object.
They will be reusable in other applicaitons. If we're thinking about
creting other
[ http://jira.codehaus.org/browse/MNG-1842?page=all ]
Joakim Erdfelt updated MNG-1842:
Attachment: MNG-1842-pom-version.patch
maven/plugins/trunk fails to build on clean system
--
Key:
[ http://jira.codehaus.org/browse/MNG-1529?page=all ]
John Casey closed MNG-1529:
---
Assign To: John Casey
Resolution: Fixed
Fix Version: (was: 2.0.3)
2.0.1
forgot to close earlier
NPE when inheriting report sets
[ http://jira.codehaus.org/browse/MNG-1842?page=all ]
John Casey closed MNG-1842:
---
Assign To: John Casey
Resolution: Fixed
fixed.
maven/plugins/trunk fails to build on clean system
--
[ http://jira.codehaus.org/browse/MPJAR-35?page=all ]
Lukas Theussl closed MPJAR-35:
--
Assign To: (was: Jason van Zyl)
Resolution: Fixed
Documentation does not mention need for jar.manifest.classpath property
This debug output seems to imply that execute()'ing a process is not
setting the working directory correctly:
- Executing: p4 -cbuilder-wsfteam01-maven sync -f ...
- stderr: Path '/opt/continuum-1.0.2/bin/linux/...' is not under
client's root '/tmp/continuum-work/1'.
Bypassing the
[ http://jira.codehaus.org/browse/MRM-42?page=all ]
Maria Odea Ching updated MRM-42:
Remaining Estimate: 18 hours
Original Estimate: 18 hours
discover repository metadata
Key: MRM-42
URL:
[ http://jira.codehaus.org/browse/MEV-258?page=all ]
Edwin Punzalan closed MEV-258:
--
Assign To: Edwin Punzalan
Resolution: Fixed
Fixed.
NOTE: May take up to 4 hours for the fix to reach central repo.
Reason: Parent:
Step missing in online Maven Getting Started Guide
Key: MNG-1843
URL: http://jira.codehaus.org/browse/MNG-1843
Project: Maven 2
Type: Bug
Components: documentation - guides
Versions: 2.0.1
Upload cglib-2.1.3 to ibiblio
-
Key: MAVENUPLOAD-631
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-631
Project: maven-upload-requests
Type: Task
Reporter: Matt Raible
Hibernate 3.1 depends on cglib 2.1.3
--
This message is
Upload antlr-2.7.6-rc1 to ibiblio
-
Key: MAVENUPLOAD-632
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-632
Project: maven-upload-requests
Type: Task
Reporter: Matt Raible
Hibernate 3.1 depends on antlr 2.7.6 RC1
--
This
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (30 issues)
Subscriber: mavendevlist
Key Summary
MEV-256 jdom 1.0 has invalid dependency: xerces-2.6.0
http://jira.codehaus.org/browse/MEV-256
MEV-251 struts 1.1 pom has servlet-api in compile
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (4 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-632Upload antlr-2.7.6-rc1 to ibiblio
http://jira.codehaus.org/browse/MAVENUPLOAD-632
MAVENUPLOAD-631Upload cglib-2.1.3 to ibiblio
Please Upload Registry CDC
--
Key: MAVENUPLOAD-633
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-633
Project: maven-upload-requests
Type: Task
Reporter: Shane Isbell
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051214.190005.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051214.190005.txt
Hi,
POMStrap is a really simple application boostrap and classloader trick
that allows dependency classloading without side effect.
POMStrap uses Maven2 pom files to resolve dependencies required to
launch an application.
see http://pomstrap.prefetch.com/
In few words, if your application
[ http://jira.codehaus.org/browse/MNG-1844?page=all ]
Allan Ramirez closed MNG-1844:
--
Resolution: Fixed
Applied. Thanks
Allow users to disable appending of assembly id to final name.
--
85 matches
Mail list logo
