[jira] Updated: (MCHANGES-145) Error when trying to send email for multi-module projects
[
http://jira.codehaus.org/browse/MCHANGES-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriele Columbro updated MCHANGES-145:
---
Attachment: MCHANGES-145-CORRECT.patch
This is the correct patch :)
Ignore latest one, WDYT?
> Error when trying to send email for multi-module projects
> -
>
> Key: MCHANGES-145
> URL: http://jira.codehaus.org/browse/MCHANGES-145
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.1
> Environment: maven 2.0.9
> JDK 1.6.011
> WinXP
>Reporter: Jean-Paul GUIGUI
> Attachments: MCHANGES-145-CORRECT.patch, MCHANGES-145.patch
>
>
> If the pom.xml is containing some sub-modules, the goal
> changes:announcement-mail is trying to send it for each module, and fail
> because it could not find the template.
>Announcement template
> C:\Dev\MyProject\SubmoduleA\target\announcement\announcement.vm not found...
> Should be possible to configure the pom to send only the email for the root
> project.
> Working with "mvn --non-recursive" option, but we need to be able to
> configure this behaviour into the pom.xml
> The same issue for the changes:announcement-generate, but it's only a warning
> and the build can finish successfully.
> Should include something like:
> /**
>* @parameter expression="${project}"
>**/
> private MavenProject mavenProject;
> /**
>* If true, will generate the changes only for the root module in case
> of project with sub-modules.
>*
>* @parameter expression="${plugin.aggregate}" default-value = "false"
>*/
> private boolean aggregate;
> public void execute() {
> if (!mavenProject.isExecutionRoot() && aggregate) {
> // Execute only for the main module in case of
> project with sub-modules
> return;
> }
>..
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-145) Error when trying to send email for multi-module projects
[
http://jira.codehaus.org/browse/MCHANGES-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197555#action_197555
]
Gabriele Columbro commented on MCHANGES-145:
I implemented and tested the specified "aggregate" behavior and it definitely
works, and at least I can use the maven-changes-plugin in my multimodule
releases.
Still, sounds like a workaround as I'd like to be able to send an announcement
for each and every of my submodules.
Once/if this workaround is committed, I suggest to open a related issue for an
improvement in the multimodule behavior of the changes plugin.
WDYT?
> Error when trying to send email for multi-module projects
> -
>
> Key: MCHANGES-145
> URL: http://jira.codehaus.org/browse/MCHANGES-145
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.1
> Environment: maven 2.0.9
> JDK 1.6.011
> WinXP
>Reporter: Jean-Paul GUIGUI
> Attachments: MCHANGES-145.patch
>
>
> If the pom.xml is containing some sub-modules, the goal
> changes:announcement-mail is trying to send it for each module, and fail
> because it could not find the template.
>Announcement template
> C:\Dev\MyProject\SubmoduleA\target\announcement\announcement.vm not found...
> Should be possible to configure the pom to send only the email for the root
> project.
> Working with "mvn --non-recursive" option, but we need to be able to
> configure this behaviour into the pom.xml
> The same issue for the changes:announcement-generate, but it's only a warning
> and the build can finish successfully.
> Should include something like:
> /**
>* @parameter expression="${project}"
>**/
> private MavenProject mavenProject;
> /**
>* If true, will generate the changes only for the root module in case
> of project with sub-modules.
>*
>* @parameter expression="${plugin.aggregate}" default-value = "false"
>*/
> private boolean aggregate;
> public void execute() {
> if (!mavenProject.isExecutionRoot() && aggregate) {
> // Execute only for the main module in case of
> project with sub-modules
> return;
> }
>..
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGES-145) Error when trying to send email for multi-module projects
[
http://jira.codehaus.org/browse/MCHANGES-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriele Columbro updated MCHANGES-145:
---
Attachment: MCHANGES-145.patch
Patch for implementing the described behavior of inhibition for multimodule
projects
> Error when trying to send email for multi-module projects
> -
>
> Key: MCHANGES-145
> URL: http://jira.codehaus.org/browse/MCHANGES-145
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.1
> Environment: maven 2.0.9
> JDK 1.6.011
> WinXP
>Reporter: Jean-Paul GUIGUI
> Attachments: MCHANGES-145.patch
>
>
> If the pom.xml is containing some sub-modules, the goal
> changes:announcement-mail is trying to send it for each module, and fail
> because it could not find the template.
>Announcement template
> C:\Dev\MyProject\SubmoduleA\target\announcement\announcement.vm not found...
> Should be possible to configure the pom to send only the email for the root
> project.
> Working with "mvn --non-recursive" option, but we need to be able to
> configure this behaviour into the pom.xml
> The same issue for the changes:announcement-generate, but it's only a warning
> and the build can finish successfully.
> Should include something like:
> /**
>* @parameter expression="${project}"
>**/
> private MavenProject mavenProject;
> /**
>* If true, will generate the changes only for the root module in case
> of project with sub-modules.
>*
>* @parameter expression="${plugin.aggregate}" default-value = "false"
>*/
> private boolean aggregate;
> public void execute() {
> if (!mavenProject.isExecutionRoot() && aggregate) {
> // Execute only for the main module in case of
> project with sub-modules
> return;
> }
>..
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-545) Enable custom JAR and resource loading in Surefire classpath
[ http://jira.codehaus.org/browse/SUREFIRE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181616#action_181616 ] Gabriele Columbro commented on SUREFIRE-545: Anyone has something to say about this? :) Thanks in advance. > Enable custom JAR and resource loading in Surefire classpath > > > Key: SUREFIRE-545 > URL: http://jira.codehaus.org/browse/SUREFIRE-545 > Project: Maven Surefire > Issue Type: Improvement > Components: classloading >Affects Versions: 2.4.3 > Environment: any >Reporter: Gabriele Columbro >Priority: Minor > Attachments: SurefireResourceLoading.diff > > > There are situations in which you would want to add to surefire classpath an > arbitrary resourceSet to have your tests running properly. > To clarify, there are cases in which maven transitive dependency management > cannot be enough for having your classpath populated properly, cases in which > not even the of surefire can be enough, unless > you pollute your pom with a huge numer of lines > (tough to write and maintain). > Maybe an example can clarify the situation: > if you're working with a legacy Webapp, say a WAR built with Ant, that has > no POM, but you want to use Maven features to improve testing and to provide > a standard approach to lifecycle management. You'd like be able to test in > isolation (outside of a container) against the webapp classpath, but while > WEB-INF/classes can be loaded with , you'd name > each and every JAR in the WEB-INF/lib to have the classpath properly populate. > This is infact my case when trying to support Alfresco ECM [1] testing with > my maven archetypes [2]. > So, after playing around with Java6 classpath wildcard loading [3] (which > seems not to be honored by surefire), I wrote this little patch which adds to > surefire a new configuration parameter: > > > > > > which allows to load arbitrary resources in the surefire classpath, using the > usual directory/include/exclude format supported by the Maven > DirectoryScanner. This solves my problems as now I can happily load the > Alfresco's WEB-INF/lib/*.jar resourceSet. > It does not check for duplicates so it's left to the developer to check it > the maven transitive classpath clashes with the added resources (as this > should be discouraged, I think it should stay like this). > I understand this should be discouraged, but I could not find a way to work > this around (until Alfresco release his POM [4]) in the current surefire > setup. > WDYT? Shall I write a test case or you think is never going to make it to the > trunk? ;) > [1] http://www.alfresco.com/ > [2] http://repository.sourcesense.com/maven2-sites/maven-alfresco-archetypes > [3] http://www.javabeat.net/qna/90-adding-jars-to-the-classpath/ > [4] https://issues.alfresco.com/jira/browse/ETHREEOH-1090 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-545) Enable custom JAR and resource loading in Surefire classpath
[ http://jira.codehaus.org/browse/SUREFIRE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=178185#action_178185 ] Gabriele Columbro commented on SUREFIRE-545: Any comments? Bad bad bad ? :) > Enable custom JAR and resource loading in Surefire classpath > > > Key: SUREFIRE-545 > URL: http://jira.codehaus.org/browse/SUREFIRE-545 > Project: Maven Surefire > Issue Type: Improvement > Components: classloading >Affects Versions: 2.4.3 > Environment: any >Reporter: Gabriele Columbro >Priority: Minor > Attachments: SurefireResourceLoading.diff > > > There are situations in which you would want to add to surefire classpath an > arbitrary resourceSet to have your tests running properly. > To clarify, there are cases in which maven transitive dependency management > cannot be enough for having your classpath populated properly, cases in which > not even the of surefire can be enough, unless > you pollute your pom with a huge numer of lines > (tough to write and maintain). > Maybe an example can clarify the situation: > if you're working with a legacy Webapp, say a WAR built with Ant, that has > no POM, but you want to use Maven features to improve testing and to provide > a standard approach to lifecycle management. You'd like be able to test in > isolation (outside of a container) against the webapp classpath, but while > WEB-INF/classes can be loaded with , you'd name > each and every JAR in the WEB-INF/lib to have the classpath properly populate. > This is infact my case when trying to support Alfresco ECM [1] testing with > my maven archetypes [2]. > So, after playing around with Java6 classpath wildcard loading [3] (which > seems not to be honored by surefire), I wrote this little patch which adds to > surefire a new configuration parameter: > > > > > > which allows to load arbitrary resources in the surefire classpath, using the > usual directory/include/exclude format supported by the Maven > DirectoryScanner. This solves my problems as now I can happily load the > Alfresco's WEB-INF/lib/*.jar resourceSet. > It does not check for duplicates so it's left to the developer to check it > the maven transitive classpath clashes with the added resources (as this > should be discouraged, I think it should stay like this). > I understand this should be discouraged, but I could not find a way to work > this around (until Alfresco release his POM [4]) in the current surefire > setup. > WDYT? Shall I write a test case or you think is never going to make it to the > trunk? ;) > [1] http://www.alfresco.com/ > [2] http://repository.sourcesense.com/maven2-sites/maven-alfresco-archetypes > [3] http://www.javabeat.net/qna/90-adding-jars-to-the-classpath/ > [4] https://issues.alfresco.com/jira/browse/ETHREEOH-1090 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-545) Enable custom JAR and resource loading in Surefire classpath
Enable custom JAR and resource loading in Surefire classpath Key: SUREFIRE-545 URL: http://jira.codehaus.org/browse/SUREFIRE-545 Project: Maven Surefire Issue Type: Improvement Components: classloading Affects Versions: 2.4.3 Environment: any Reporter: Gabriele Columbro Priority: Minor Attachments: SurefireResourceLoading.diff There are situations in which you would want to add to surefire classpath an arbitrary resourceSet to have your tests running properly. To clarify, there are cases in which maven transitive dependency management cannot be enough for having your classpath populated properly, cases in which not even the of surefire can be enough, unless you pollute your pom with a huge numer of lines (tough to write and maintain). Maybe an example can clarify the situation: if you're working with a legacy Webapp, say a WAR built with Ant, that has no POM, but you want to use Maven features to improve testing and to provide a standard approach to lifecycle management. You'd like be able to test in isolation (outside of a container) against the webapp classpath, but while WEB-INF/classes can be loaded with , you'd name each and every JAR in the WEB-INF/lib to have the classpath properly populate. This is infact my case when trying to support Alfresco ECM [1] testing with my maven archetypes [2]. So, after playing around with Java6 classpath wildcard loading [3] (which seems not to be honored by surefire), I wrote this little patch which adds to surefire a new configuration parameter: which allows to load arbitrary resources in the surefire classpath, using the usual directory/include/exclude format supported by the Maven DirectoryScanner. This solves my problems as now I can happily load the Alfresco's WEB-INF/lib/*.jar resourceSet. It does not check for duplicates so it's left to the developer to check it the maven transitive classpath clashes with the added resources (as this should be discouraged, I think it should stay like this). I understand this should be discouraged, but I could not find a way to work this around (until Alfresco release his POM [4]) in the current surefire setup. WDYT? Shall I write a test case or you think is never going to make it to the trunk? ;) [1] http://www.alfresco.com/ [2] http://repository.sourcesense.com/maven2-sites/maven-alfresco-archetypes [3] http://www.javabeat.net/qna/90-adding-jars-to-the-classpath/ [4] https://issues.alfresco.com/jira/browse/ETHREEOH-1090 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-500) puzzling NoClassDefFoundError instead of meaningfull stacktrace
[ http://jira.codehaus.org/browse/SUREFIRE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171919#action_171919 ] Gabriele Columbro commented on SUREFIRE-500: I'm also experiencing this issue with maven 2.0.9, with a weird NoClassDefFoundError on the base Spring test class AbstractDependencyInjectionSpringContextTests, which is instead declared with 'test' scope in the pom. Luckily a 'mvn clean' saved the day :) > puzzling NoClassDefFoundError instead of meaningfull stacktrace > --- > > Key: SUREFIRE-500 > URL: http://jira.codehaus.org/browse/SUREFIRE-500 > Project: Maven Surefire > Issue Type: Bug > Components: classloading >Affects Versions: 2.4.2 > Environment: maven 2.0.9 , linux/ubuntu, jdk-sun-1.5.0_13 >Reporter: Johan Romme > > We are using maven-2.0.9 for some project using spring/hibernate. > When I made an incorrect change to the spring configuration (or actually I > removed a hbm.xml file that was still referenced in the spring config), > maven/surefire failed with an NoClassDefFoundError on one of our abstract > test classes (where the spring config was loaded). Running in debug mode (-X) > or increasing log4j levels did not reveal more info as to the cause of the > problem. > After some time I switched back to maven-2.0.7, maven/surefire also failed > but with a meaningfull stacktrace that pointed immediately to the cause of > the problem. > So I fixed the problem, switched again to maven-2.0.9, with a succesfull > build as result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-103) No SCM URL was provided to perform the release from
[
http://jira.codehaus.org/browse/MRELEASE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170083#action_170083
]
Gabriele Columbro commented on MRELEASE-103:
I'm having this issue with 2.0-beta-8 and pom completely configured with:
scm:svn:${svn.url}
${svn.url}
scm:svn:${svn.url}
and
http://mysvnurl.com/repos/project/trunk
Am I missing something?
> No SCM URL was provided to perform the release from
> ---
>
> Key: MRELEASE-103
> URL: http://jira.codehaus.org/browse/MRELEASE-103
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Environment: solaris
>Reporter: Olivier Lamy
>Priority: Blocker
> Fix For: 2.0-beta-5
>
> Attachments: olamy.tar.gz
>
>
> The stack trace says :
> DEBUG] Trace
> org.apache.maven.BuildFailureException: No SCM URL was provided to perform
> the release from
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor
> .java:555)
> I included a test case with multi modules project (you need to change scm url
> in all poms to complete the test).
> Strange because all scm parts are filled in all modules.
> To test it, I launch ./buildis.sh $svnuser $svnpwd
> Olivier
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-100) War overlay with merged web.xml
[ http://jira.codehaus.org/browse/MWAR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169057#action_169057 ] Gabriele Columbro commented on MWAR-100: An Xpatch kind of thing is not applicable? http://cocoon.apache.org/2.2/maven-plugins/maven-plugin/1.0/1360_1_1.html > War overlay with merged web.xml > --- > > Key: MWAR-100 > URL: http://jira.codehaus.org/browse/MWAR-100 > Project: Maven 2.x War Plugin > Issue Type: Wish >Affects Versions: 2.0 >Reporter: Anders Romin > > I'm looking for a way to use the war overlay feature and have the web.xml > merged with the content of both the parent war and the child war. > For example, we have two wars A and B, and B is depending on A using the > overlay feature. Now, I'd like all filters, servlets etc that are configured > in A to be available in the resulting war, as well as all filters, servlets > etc from B. If the id attributes clash, then the objects from B should be > used. > Any ideas how this could be accomplished? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1144) List 2 or more maven goals in the of the POM.
[ http://jira.codehaus.org/browse/MNG-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163880#action_163880 ] Gabriele Columbro commented on MNG-1144: How tough will it be to add it to 2.0.x or 2.1.x releases? As it will make a real nice improvement in controlling behavior of the build using just profiles. Thanks! > List 2 or more maven goals in the of the POM. > --- > > Key: MNG-1144 > URL: http://jira.codehaus.org/browse/MNG-1144 > Project: Maven 2 > Issue Type: New Feature > Components: Plugins and Lifecycle, POM >Affects Versions: 2.0-beta-3 > Environment: Windows >Reporter: Alexandre Vivien > Fix For: 3.x > > > In the maven 2.0-beta-3 release we can't list more than one goal in the > of the POM. For example, this : > clean:clean install > doesn't work. > It can be useful to add this feature in the maven 2.0 final release. > Thanks. > Alexandre Vivien -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WAGON-54) Scm Wagon not expanding ${user.home}
[
http://jira.codehaus.org/browse/WAGON-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92108
]
Gabriele Columbro commented on WAGON-54:
I'm experiencing the same issue under a Macbook Pro OSX 10.4 environment, so
it's probably not due to space in filename, but of the plugin itself.
I'm not exactly a mvn internals expert, but I'm going to work on this issue for
a project I'm working on, hoping to file a patch soon.
For the moment, any hint would be lovely appreciated ;-)
> Scm Wagon not expanding ${user.home}
>
>
> Key: WAGON-54
> URL: http://jira.codehaus.org/browse/WAGON-54
> Project: wagon
> Issue Type: Bug
> Components: wagon-scm
>Affects Versions: 1.0-alpha-5
> Environment: windows xp, maven 2.0.4
>Reporter: Jean Deruelle
>
> when trying to deploy a jar to a svn repository , wagon-scm doesn't translate
> ${user.home} (because of space in the user home's windows path?) and create
> this directory in the current directory
> ...
>
>
> svn-repository
> scm:svn:https://[EMAIL
> PROTECTED]/svn/maven2-repository/trunk/repository
>
>
>
>
> org.apache.maven.wagon
> wagon-scm
> 1.0-alpha-5
>
>
> Here is the log :
> [INFO] [deploy:deploy]
> Uploading:
> scm:svn:https://maven2-repository.dev.java.net/svn/maven2-repository/trunk/repository/org/apache/maven/plugins/maven-slee-du-plugin/1.0/maven-slee-du-plugin-1.0.jar
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository
> [INFO] Command line: svn add --non-recursive ${user.home}/.m2/repository/org
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org
> [INFO] Command line: svn add --non-recursive
> ${user.home}/.m2/repository/org/apache
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache
> [INFO] Command line: svn add --non-recursive
> ${user.home}/.m2/repository/org/apache/maven
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven
> [INFO] Command line: svn add --non-recursive
> ${user.home}/.m2/repository/org/apache/maven/plugins
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins
> [INFO] Command line: svn add --non-recursive
> ${user.home}/.m2/repository/org/apache/maven/plugins/maven-slee-du-plugin
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins\maven-slee-du-plugin
> [INFO] Command line: svn add --non-recursive
> ${user.home}/.m2/repository/org/apache/maven/plugins/maven-slee-du-plugin/1.0
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins\maven-slee-du-plugin\1.0
> [INFO] Command line: svn --username deruelle_jean --password L0veSt1nks
> --non-interactive checkout
> https://maven2-repository.dev.java.net/svn/maven2-repository/
> trunk/repository/org/apache/maven/plugins/maven-slee-du-plugin/1.0 1.0
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins\maven-slee-du-plugin
> [INFO] Command line: svn --username deruelle_jean --password L0veSt1nks
> --non-interactive commit --file
> C:\DOCUME~1\T405732\LOCALS~1\Temp\maven-scm-465347372.commit
> ${user.home}/.m2/repository/org/apache/maven/plugins/maven-slee-du-plugin/1.0
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error deploying artifact: Unable to commit file svn:
> 'C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins\ma
> ven-slee-du-plugin' is not a working copy
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
