Hi Bret
What does updateReleaseInfo exactly do? There are no descriptions
on install plugin site:
http://maven.apache.org/plugins/maven-install-plugin/install-mojo.html
Thanks
Greg
- Original Message -
From: Brett Porter [EMAIL PROTECTED]
To: Maven Developers List
[ http://jira.codehaus.org/browse/MPEAR-8?page=all ]
Stephane Nicoll updated MPEAR-8:
Fix Version: 1.8
Need maven.ear.src similar to maven.war.src
---
Key: MPEAR-8
URL:
[ http://jira.codehaus.org/browse/MPEAR-17?page=all ]
Stephane Nicoll updated MPEAR-17:
-
Fix Version: 1.9
plugin could generate more elements in application.xml
--
Key: MPEAR-17
[ http://jira.codehaus.org/browse/MPEAR-42?page=all ]
Stephane Nicoll updated MPEAR-42:
-
Assign To: Stephane Nicoll
Fix Version: 1.8
ear.bundle.name does not work properly with other types than jar.
application.xml is allso generated wrongly
The correct list is continuum-users@maven.apache.org
Open your wrapper.conf and change all log level to DEBUG, so you'll can find
the problem.
It's certainly a space in a path.
Emmanuel
Dave Maung a écrit :
I am trying to set up continum. However, I am not able to do so.
I launched
[ http://jira.codehaus.org/browse/MDEPLOY-19?page=all ]
updated MDEPLOY-19:
Attachment: MDEPLOY19.diff
Ability to deploy-file as classifier
Key: MDEPLOY-19
URL: http://jira.codehaus.org/browse/MDEPLOY-19
[ http://jira.codehaus.org/browse/MDEPLOY-23?page=comments#action_57176 ]
Jerome Lacoste commented on MDEPLOY-23:
---
MDEPLOY-19 is now fixed on top of that one. So don't rearrange too much the
code, if you don't want to break it...
deploy:file favors
[ http://jira.codehaus.org/browse/MDEPLOY-19?page=comments#action_57175 ]
Jerome Lacoste commented on MDEPLOY-19:
---
I attached the fix. I haven't tested it thoroughly apart from a quick
mvn install mvn deploy:deploy-file -Durl=file:///tmp/
Vote result:
5 positive votes from PMC members (Arnaud, Brett, Emmanuel, John, Lukas)
3 from committers (Vincent S., Mike Perham and me)
I will tag the release shortly
fabrizio
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Vote result:
5 positive votes from PMC members (Arnaud, Brett, Emmanuel, John, Lukas)
2 from committers (Vincent S. and me)
I will tag the release shortly
fabrizio
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
[ http://jira.codehaus.org/browse/MPEAR-42?page=all ]
Stephane Nicoll closed MPEAR-42:
Resolution: Cannot Reproduce
Tested with latest SVN and I cant' reproduce.
Both war and ejb are handled properly ; application.xml is generated properly
as
[ http://jira.codehaus.org/browse/MPEAR-8?page=all ]
Stephane Nicoll closed MPEAR-8:
---
Resolution: Duplicate
Fix Version: (was: 1.8)
maven.ear.src is available.
Need maven.ear.src similar to maven.war.src
[ http://jira.codehaus.org/browse/MPEAR-33?page=all ]
Stephane Nicoll updated MPEAR-33:
-
Assign To: Stephane Nicoll
Fix Version: 1.8
Summary: support wsr module in application.xml (was: support modules
in application.xml with any file
[ http://jira.codehaus.org/browse/MPEAR-33?page=all ]
Stephane Nicoll resolved MPEAR-33:
--
Resolution: Fixed
wsr module can now be included in application.xml generation.
support wsr module in application.xml
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060128.151503.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060128.151503.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MPRAR-2?page=all ]
Stephane Nicoll resolved MPRAR-2:
-
Resolution: Fixed
Added maven.rar.final.name property
Create property maven.ear.final.name
Key: MPRAR-2
Site descriptor resolution never falls back to site.xml
---
Key: MSITE-81
URL: http://jira.codehaus.org/browse/MSITE-81
Project: Maven 2.x Site Plugin
Type: Bug
Reporter: Indrajit Raychaudhuri
Priority:
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060128.16.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060128.16.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MPRAR-2?page=comments#action_57181 ]
Lukas Theussl commented on MPRAR-2:
---
Stephane, did you check if this is consistent with the properties in jar, war,
ejb, ear (see MPJAVA-8)? Do you think we can close this issue?
[ http://jira.codehaus.org/browse/MPRAR-2?page=comments#action_57182 ]
Stephane Nicoll commented on MPRAR-2:
-
it is. Yes we can close it.
Create property maven.ear.final.name
Key: MPRAR-2
URL:
[ http://jira.codehaus.org/browse/MPRAR-1?page=all ]
Stephane Nicoll resolved MPRAR-1:
-
Resolution: Fixed
This is fixed, ra.xml file is now included wherever it is located.
plugin properties are not used correctly
Hi all,
I would like to release the following m1 plugins for inclusion in m1.1-beta3:
[] javacc: no more open issues
[] rar: no more open issues (fixed MPRAR-1 and MPRAR-2)
[] ear: fixed a couple of things ; still open issues which will be
addressed later on
The future documentation is here:
Stephane,
Don't you want to wait for the ear release until the j2ee issue is
resolved? (If j2ee gets demoted, you will have to do another release).
-Lukas
Stephane Nicoll wrote:
Hi all,
I would like to release the following m1 plugins for inclusion in m1.1-beta3:
[] javacc: no more open
Ah, yes forgot that one sorry. What is the Jira issue ID?
Thanks,
Stéphane
On 1/28/06, Lukas Theussl [EMAIL PROTECTED] wrote:
Stephane,
Don't you want to wait for the ear release until the j2ee issue is
resolved? (If j2ee gets demoted, you will have to do another release).
-Lukas
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=comments#action_57184 ]
Gunnar Hillert commented on MSUREFIRE-23:
-
While the TestNG jars are now in the official Maven repository, the patches
don't use them. I believe the TestNG jars itself are
There is none yet, I wanted to wait for the result of the vote. I think
you can open an issue now, I just haven't had time to wrap up the results.
-Lukas
Stephane Nicoll wrote:
Ah, yes forgot that one sorry. What is the Jira issue ID?
Thanks,
Stéphane
On 1/28/06, Lukas Theussl [EMAIL
[ http://jira.codehaus.org/browse/MNGECLIPSE-61?page=all ]
fabrizio giustina moved MECLIPSE-60 to MNGECLIPSE-61:
-
Key: MNGECLIPSE-61 (was: MECLIPSE-60)
Project: Maven 2.x Extension for Eclipse (was: Maven 2.x Eclipse Plugin)
[ http://jira.codehaus.org/browse/MNGECLIPSE-63?page=all ]
fabrizio giustina moved MECLIPSE-63 to MNGECLIPSE-63:
-
Key: MNGECLIPSE-63 (was: MECLIPSE-63)
Project: Maven 2.x Extension for Eclipse (was: Maven 2.x Eclipse Plugin)
[ http://jira.codehaus.org/browse/MNGECLIPSE-65?page=all ]
fabrizio giustina moved MECLIPSE-62 to MNGECLIPSE-65:
-
Key: MNGECLIPSE-65 (was: MECLIPSE-62)
Project: Maven 2.x Extension for Eclipse (was: Maven 2.x Eclipse Plugin)
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=comments#action_57185 ]
Jesse Kuhnert commented on MSUREFIRE-23:
Hmmm Well yes, that is how I thought I had packaged them. I must have done
somthing wrong with my mvn-upload request. This doesn't
[ http://jira.codehaus.org/browse/MNGECLIPSE-62?page=all ]
fabrizio giustina moved MECLIPSE-59 to MNGECLIPSE-62:
-
Key: MNGECLIPSE-62 (was: MECLIPSE-59)
Project: Maven 2.x Extension for Eclipse (was: Maven 2.x Eclipse Plugin)
[ http://jira.codehaus.org/browse/MNGECLIPSE-64?page=all ]
fabrizio giustina moved MECLIPSE-61 to MNGECLIPSE-64:
-
Key: MNGECLIPSE-64 (was: MECLIPSE-61)
Project: Maven 2.x Extension for Eclipse (was: Maven 2.x Eclipse Plugin)
[ http://jira.codehaus.org/browse/MECLIPSE-9?page=all ]
fabrizio giustina closed MECLIPSE-9:
Resolution: Fixed
Fix Version: 2.1
fixed (again)
the initial bug was fixed by manually escaping the path, but then we switched
from directly
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060128.181501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060128.181501.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MECLIPSE-55?page=all ]
fabrizio giustina updated MECLIPSE-55:
--
Assign To: fabrizio giustina
Fix Version: 2.1
Documentation: eclipse:eclipse creates Projects or Libraries link
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060128.183001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060128.183001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[
http://jira.codehaus.org/browse/MAVENUPLOAD-693?page=comments#action_57189 ]
fabrizio giustina commented on MAVENUPLOAD-693:
---
Carlos,
the repository is at:
scp://shell.sourceforge.net/home/groups/m/ma/maven-taglib/htdocs/m2repo
you need to
[ http://jira.codehaus.org/browse/MASSEMBLY-56?page=comments#action_57190 ]
John Didion commented on MASSEMBLY-56:
--
I'll give you our use case: we have several tool components, basically
command-line tools for admin tasks. I've written a plugin to
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=all ]
fabrizio giustina closed MECLIPSE-47:
-
Assign To: fabrizio giustina
Resolution: Fixed
Fix Version: 2.1
WTP 1.0 support is complete and will be released shortly.
The plugin
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060128.190001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060128.190001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
unable to find artifacts from attached tests
Key: MNGECLIPSE-66
URL: http://jira.codehaus.org/browse/MNGECLIPSE-66
Project: Maven 2.x Extension for Eclipse
Type: Bug
Components: Dependency Resolver
Versions:
I tested and it works. Thanks!
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Friday, January 27, 2006 12:32 AM
To: Maven Developers List
Subject: Re: Maven-dashboard 1.9, Maven 1.0.2 and Cobertura
My mistake, sorry about that. I removed one line that contained
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060128.191500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060128.191500.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MECLIPSE-55?page=all ]
fabrizio giustina closed MECLIPSE-55:
-
Resolution: Fixed
goal description improved
Documentation: eclipse:eclipse creates Projects or Libraries link
I would like to release a new version of the maven 2 eclipse plugin.
The main enhancement is the support for WTP 1.x (release 2.0 ony had
support for WTP R7).
The plugin will require WTP 1.0.1, which will be released in february,
or a recent I/M build (WTP 1.0 has a bug which prevents external
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060128.203000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060128.203000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
+1
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fabrizio
Giustina
Sent: Saturday, January 28, 2006 2:42 PM
To: Maven Developers List
Subject: [vote] maven2 eclipse plugin 2.1 release
I would like to release a new version of the maven 2 eclipse
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060128.204500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060128.204500.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/CONTINUUM-446?page=comments#action_57203
]
Jamie Flournoy commented on CONTINUUM-446:
--
The attached diff and jar implement this functionality. I've only tested this
with the MailContinuumNotifier but the change
deploy-bundle: license files is unused in upload bundle (should not be required)
Key: MRM-65
URL: http://jira.codehaus.org/browse/MRM-65
Project: Maven Repository Manager
Type:
[
http://jira.codehaus.org/browse/MAVENUPLOAD-692?page=comments#action_57205 ]
fabrizio giustina commented on MAVENUPLOAD-692:
---
Patch for deploy-bundle filed as MRM-65
tlddoc 1.3
--
Key: MAVENUPLOAD-692
URL:
[+1] javacc: no more open issues
[+1] rar: no more open issues (fixed MPRAR-1 and MPRAR-2)
I did a few cosmetic clean-ups (docs, code formatting, broken links).
Btw: for rar there is still one issue open (MPRAR-3) but I think it can
be closed as incomplete.
[-1] ear: fixed a couple of
Hi,
I see that Maven JXR 1.0 is tagged (but it's not at ibiblio yet). I
seems that it's not a Maven plugin. So how do we use it? I thought I
could use it during site generation process but of course it's not
accepted as a plugin.
(I had asked a question on a previous thread and it was in fact
Summary:
We have 4 binding votes (Carlos, Brett, Vincent M, Arnaud, Lukas) and
one non-binding (Stephane) for demoting the following plugins:
[] repository - (move create-upload-bundle to artifact)
[] release - (move used classes to scm)
[] j2ee - (move resolver tag into ear and
I agree for EAR,we should fix the j2ee issue first.
Stéphane
On 1/28/06, Lukas Theussl [EMAIL PROTECTED] wrote:
[+1] javacc: no more open issues
[+1] rar: no more open issues (fixed MPRAR-1 and MPRAR-2)
I did a few cosmetic clean-ups (docs, code formatting, broken links).
Btw: for rar
[ http://jira.codehaus.org/browse/MPJAVA-8?page=comments#action_57213 ]
Lukas Theussl commented on MPJAVA-8:
I don't think this is completely fixed, the war plugin still has
maven.war.final.name = ${pom.artifactId}.war, while all the others
Move create-upload-bundle goal from repository-plugin to artifact
-
Key: MPARTIFACT-64
URL: http://jira.codehaus.org/browse/MPARTIFACT-64
Project: maven-artifact-plugin
Type: Task
Reporter: Lukas
+1
Alex
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Glazedlists 1.5.0
-
Key: MAVENUPLOAD-707
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-707
Project: maven-upload-requests
Type: Task
Reporter: Geoffrey De Smet
JTable with sorting filtering, used in spring-rich and many Swing
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060129.02.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060129.02.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
I notify you that files linked on
http://maven.apache.org/plugins/maven-site-plugin/i18n.html
are not found on server.
C.Dutoit/Switzerland
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Thanks. The SVN location moved.
Replace components/trunk/maven-plugins with plugins/trunk
- Brett
Cedric DUTOIT wrote:
I notify you that files linked on
http://maven.apache.org/plugins/maven-site-plugin/i18n.html
are not found on server.
C.Dutoit/Switzerland
It's a temporary solution, but it currently links the latest release
to the version you are installing.
- Brett
Grzegorz Slowikowski wrote:
Hi Bret
What does updateReleaseInfo exactly do? There are no descriptions
on install plugin site:
Hibernate Annotations 3.1 beta 8 upload request
---
Key: MAVENUPLOAD-708
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-708
Project: maven-upload-requests
Type: Task
Reporter: Nathan Hamblen
Please upload.
--
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060129.003000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060129.003000.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MAVEN-1668?page=all ]
Lukas Theussl closed MAVEN-1668:
Resolution: Fixed
On the maven site the links reported by, file-activity-report and
changelog-report, is broken.
[ http://jira.codehaus.org/browse/MSITE-81?page=comments#action_57220 ]
Brett Porter commented on MSITE-81:
---
I don't think this patch is correct. If the site descriptor is not found (as
originally), it will fallback. This change would fall back if there
Is there way to include and exclude java source out of the box in maven
instead of using maven-compiler-plugin?
build
sourceDirectory../main/src/java/sourceDirectory
includes
includ.java/include
/includes
Dave
I meant in Maven2
On 1/28/06, Dave Maung [EMAIL PROTECTED] wrote:
Is there way to include and exclude java source out of the box in maven
instead of using maven-compiler-plugin?
build
sourceDirectory../main/src/java/sourceDirectory
includes
includ.java/include
/includes
Dave
Dave,
Please don't send these questions to the developer list - they belong on
the users list, which you have also posted to. Cross posting is a big no-no.
Thanks,
- Brett
Dave Maung wrote:
I meant in Maven2
On 1/28/06, Dave Maung [EMAIL PROTECTED] wrote:
Is there way to include and
[ http://jira.codehaus.org/browse/MNG-671?page=comments#action_57223 ]
Brett Porter commented on MNG-671:
--
while this would just be simple at first, the more complete solution I was
thinking of:
* have option of failing/ignoring in a non-interactive build
[ http://jira.codehaus.org/browse/MSITE-81?page=all ]
Indrajit Raychaudhuri updated MSITE-81:
---
Attachment: site.log
Site descriptor resolution never falls back to site.xml
---
Key:
[ http://jira.codehaus.org/browse/MNG-1455?page=comments#action_57226 ]
domi commented on MNG-1455:
---
When is this fix within an official releade? I'think I run the latest version
and still have this problem!
Possible NPE in DefaultArtifactResolver
Hi all, I have a couple of questions regarding continuum's webapp. I've
been looking through jira and haven't found these issues tackled.
1. Is it just me or permissions are not checked when adding/removing
projects? If I log in, copy the url for deleting a project and then
logout, it seems
[ http://jira.codehaus.org/browse/CONTINUUM-446?page=all ]
updated CONTINUUM-446:
---
Attachment: notification-edits.txt
Mail notification should be configurable to notify on every build
-
Why do you want to build sources?
Emmanuel
Thats a good question. I wanted to change the build report to be briefer. In particular
we like to keep the Subject line as ProjcectName BUILD-NUM PASS. We also
like the summary to just include the tests that fail (our project has 3000 tests.)
... and we certainly encourage folks wanting to do that. Even more so if
they want to contribute changes back :) Email customisation would be a
useful feature to have.
I think the main thing we try to discourage is people just wanting to
check out the latest features building from sources -
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060129.013000.war
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060129.013000.txt
78 matches
Mail list logo
