[ http://jira.codehaus.org/browse/MNG-1105?page=comments#action_50902 ]
Trent Rosenbaum commented on MNG-1105:
--
Putting the release.properties file in the target directory makes complete
sense. This way the file has a life time that is inline with the
Fabrizio,
This can only be a temporary solution, I am still hoping that we will be
able to make validation work with full namespace awareness. If we
succeed, we'll have to undo this commit.
-Lukas
[EMAIL PROTECTED] wrote:
Author: fgiust
Date: Sun Nov 13 01:21:00 2005
New Revision: 332953
Hi
I get the message:
(Nonexistent component: org.apache.maven.lifecycle.mapping.LifecycleMappingnar)
when I use my own packaging, while the (nar)plugin is indeed in the list and
included,
when I run the "clean" goal.
Any other goal works fine (no message).
I guess this is because the "clean
[ http://jira.codehaus.org/browse/MPXDOC-182?page=all ]
Lukas Theussl closed MPXDOC-182:
Resolution: Duplicate
Duplicate of MPXDOC-174
> xdoc goal crashes
> -
>
> Key: MPXDOC-182
> URL: http://jira.codehaus.org/bro
[ http://jira.codehaus.org/browse/MNG-1105?page=comments#action_50899 ]
Arik Kfir commented on MNG-1105:
What about putting it in the 'target' dir?
Reason: I think this file is both temporary (used for the build only) AND
useful. For instance, I couldn't fi
[ http://jira.codehaus.org/browse/MPXDOC-182?page=all ]
Lukas Theussl moved MAVEN-1723 to MPXDOC-182:
-
Fix Version: (was: 1.1-beta-2)
1.10
Workflow: jira (was: Maven)
Key: MPXDOC-182 (was: MAVEN-1723)
[ http://jira.codehaus.org/browse/MNG-1105?page=comments#action_50897 ]
Trent Rosenbaum commented on MNG-1105:
--
I feel that the release.properties file should not be removed after the perform
method has been run. A message to explain this, (as suggeste
[ http://jira.codehaus.org/browse/CONTINUUM-442?page=all ]
Emmanuel Venisse closed CONTINUUM-442:
--
Resolution: Fixed
fixed in plexus-runtime-builder
> plexus.sh overwrites PLEXUS_OPTS, doesn't delegate processes
> -
[ http://jira.codehaus.org/browse/CONTINUUM-442?page=all ]
Emmanuel Venisse reopened CONTINUUM-442:
Assign To: Emmanuel Venisse
> plexus.sh overwrites PLEXUS_OPTS, doesn't delegate processes
> ---
[ http://jira.codehaus.org/browse/CONTINUUM-442?page=all ]
Emmanuel Venisse closed CONTINUUM-442:
--
Resolution: Fixed
> plexus.sh overwrites PLEXUS_OPTS, doesn't delegate processes
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is going to sound completely ugly, but what I've found to work best
when I have multiple interrelated (ie. same application) projects is to
create one massive eclipse project with all the subprojects' source
roots mapped as src dirs, all the reso
Request for comments:
How should I go about designing a NullSoft Installer plugin so that it works
well with the assembly paradigm?
The assembly plugin seems to have been designed to operate in a stand-alone
fashion, firing off the project's package build, rather than cooperate
within the ex
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051114.163000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051114.163000.txt
[ http://jira.codehaus.org/browse/MNG-1178?page=comments#action_50889 ]
Christian Mouttet commented on MNG-1178:
Brett,
to reproduce the bug you can write a simple TestCase like this (initializing
Log4J):
public class SimpleTest extends TestCase {
btw the same project interdependecies resolution is done in mevenide for
netbeans (both for m1 and m2)
since that one is an IDE plugin, not maven plugin, it allows to dynamically
change the jar/project linking on project open/close.
for example if I work on mevenide, then maven dependencies are onl
Ok.. after some thought I need to reevaluate my opinion on this.
I have now played a little with the eclipse plugin, and well.. i must
admit that i like the way it behaves. So using project references for
projects in the same reactor build where the version of the project in
the reactor, and the v
[ http://jira.codehaus.org/browse/MNG-1324?page=comments#action_50880 ]
fabrizio giustina commented on MNG-1324:
> I updated my m2 to the last svn snapshot this morning, but the eclipse plugin
> still can't handle system dependencies...
sounds stran
>
> Yes, I fine with this too except that I'd name it a bit differently:
>
> dropit/
> |_ logging/
> |_ config/
> |_ interfaces-api/
> |_ frontend-servlet/
> |_ backend-servlet/
> |_ war/
> |_ ear/
>
> But again this is a very simple project that doesn't have everything
> automated? What about func
[ http://jira.codehaus.org/browse/MNG-1050?page=comments#action_50879 ]
Joerg Schaible commented on MNG-1050:
-
IMHO "[2.0,)" is perfect for any new version. It depends on the version naming
policy of the depending artifact's project, if a new release is
xdoc goal crashes
-
Key: MAVEN-1723
URL: http://jira.codehaus.org/browse/MAVEN-1723
Project: Maven
Type: Bug
Environment: Windows XP, SUN JDK 1.4.2 build 08
Reporter: Guy Rixon
Fix For: 1.1-beta-2
The xdoc goal crashes like this:
BUILD F
[ http://jira.codehaus.org/browse/MNG-1324?page=all ]
Giorgio Gallo reopened MNG-1324:
Sorry to bother Fabrizio..
I updated my m2 to the last svn snapshot this morning, but the eclipse plugin
still can't handle system dependencies...
> "System" depe
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051114.134500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051114.134500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Hi guys,
I've recently started monitoring this list as I am very interested in the
Perforce Maven SCM implementation (I recently obtained the source and
started looking at how far along it is).
I'm butting in here as I have some thoughts that may have use to your
implementations. I have used a n
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Maven Wiki" for change
notification.
The following page has been changed by AlexanderHars:
http://wiki.apache.org/maven/AssemblyPlugin
--
- = Assem
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Maven Wiki" for change
notification.
The following page has been changed by AlexanderHars:
http://wiki.apache.org/maven/AssemblyPlugin
New page:
= AssemblyPlugin =
[http://maven.apache.org/guides/mini/guide-assemblies.html
Dependency Ignored
--
Key: MNG-1557
URL: http://jira.codehaus.org/browse/MNG-1557
Project: Maven 2
Type: Bug
Versions: 2.0
Environment: Fedora Core 4
Reporter: Stephen Duncan Jr
Attachments: debug-output.txt, effective-pom.txt
A typical
[ http://jira.codehaus.org/browse/MNG-1557?page=all ]
Stephen Duncan Jr updated MNG-1557:
---
Attachment: debug-output.txt
Added result of running m2 -X clean package (debug-output.txt)
> Dependency Ignored
> --
>
> Key: MNG-1557
[ http://jira.codehaus.org/browse/MNG-1557?page=all ]
Stephen Duncan Jr updated MNG-1557:
---
Attachment: effective-pom.txt
Added output of projecthelp:effective-pom
> Dependency Ignored
> --
>
> Key: MNG-1557
> URL: htt
[ http://jira.codehaus.org/browse/CONTINUUM-443?page=all ]
Brett Porter updated CONTINUUM-443:
---
Summary: Jabber and MSN not working in latest CI build (was: Jabber not
working in latest CI build)
likewise, MSN:
@4000437889311f57a4bc java.lang.Nu
My mistake
You are right Mark. So it seems like the eclipse plugin does it alot
like what Brett are describing.. But again.. this is to automagically
for me ;)
On 14/11/05, Mark Hobson <[EMAIL PROTECTED]> wrote:
> The eclipse plugin *does* create different project files depending on
> where it's
link build number to last build on front page, as per original design
-
Key: CONTINUUM-444
URL: http://jira.codehaus.org/browse/CONTINUUM-444
Project: Continuum
Type: Improvement
Reporter: Brett
Update to work with automatic tagBase resolution of maven-scm-provider-svn
--
Key: MNG-1556
URL: http://jira.codehaus.org/browse/MNG-1556
Project: Maven 2
Type: Bug
Components: maven-release-pl
Jabber not working in latest CI build
-
Key: CONTINUUM-443
URL: http://jira.codehaus.org/browse/CONTINUUM-443
Project: Continuum
Type: Bug
Reporter: Brett Porter
Fix For: 1.0.1
I hvae configured a jabber notifier on ci.c
[ http://jira.codehaus.org/browse/SCM-72?page=all ]
Emmanuel Venisse closed SCM-72:
---
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0-beta-1
Applied, thanks.
For your two point on status mojo and diff command, you can file an
please upload A2J beta2
---
Key: MAVENUPLOAD-588
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-588
Project: maven-upload-requests
Type: Task
Reporter: nicolas de loof
A2J is a tool for converting ASN specifications into a collection of ja
The eclipse plugin *does* create different project files depending on
where it's run. It uses project references if the other projects are
within the reactor build. It's also very particular regarding
versions, as this thread details:
http://www.nabble.com/eclipse%3Aeclipse-and-direct-project-re
Hi,
3 questions:
1) what maven commando's can I try to test my implementation?
2) About the checkout command: In ClearCase, you are looking at
read-only files and you "check out" 1 file to edit that file. After
that you check your file in. This is not the same for SVN for instance,
where checkou
Wim Deblauwe a écrit :
Hi,
3 questions:
1) what maven commando's can I try to test my implementation?
You can try mojos in maven-scm-plugin.
2) About the checkout command: In ClearCase, you are looking at
read-only files and you "check out" 1 file to edit that file. After that
you chec
[ http://jira.codehaus.org/browse/MNG-785?page=comments#action_50860 ]
Mark Hobson commented on MNG-785:
-
Thanks for this, I'll try to incorporate this into the next version. BTW,
probably worth raising future issues against the sandbox component in the MOJ
Custom velocity template error: unable to find resource 'maven.vm' in any class
loader
--
Key: MNG-1555
URL: http://jira.codehaus.org/browse/MNG-1555
Project: Maven 2
Type: Bug
Com
Hi Jesse,
Thanks for restarting this thread!
See below
> -Original Message-
> From: Jesse McConnell [mailto:[EMAIL PROTECTED]
> Sent: lundi 7 novembre 2005 20:00
> To: Maven Developers List
> Subject: Re: [M2][Proposal] J2EE builds best practices and conventions
>
> ok, digging this old
[ http://jira.codehaus.org/browse/SCM-64?page=all ]
Emmanuel Venisse closed SCM-64:
---
Assign To: Emmanuel Venisse
Resolution: Fixed
> ability to store user password in settings.xml
> --
>
> Key:
Assembly plugin fails to resolve dependency when it tries to package the
application
Key: MNG-1554
URL: http://jira.codehaus.org/browse/MNG-1554
Project: Maven 2
Type: Bug
Compone
[ http://jira.codehaus.org/browse/MNG-1526?page=all ]
Anuerin Diaz closed MNG-1526:
-
Resolution: Incomplete
I have decided to close this issue for the mean time until I have more
information. This is in relation to the discussion in
http://www.mail-ar
101 - 144 of 144 matches
Mail list logo
